Accessibility

Table of Contents

  1. Introduction
  2. OMA DRM
  3. Flash Lite content and DRM
  4. Tools to apply OMA DRM 1.0 to Flash Lite content
  5. Applying OMA DRM 1.0 Forward Lock to Flash Lite content
  6. Testing OMA DRM 1.0 Forward protected Flash Lite content

How to protect Flash Lite content with OMA DRM 1.0

OMA DRM

But first a question: Why do would you want to apply DRM to Flash Lite content?

The idea is to increase protection of your Flash Lite files (SWF)  and your intellectual property. Also you might find that DRM is a requirement for operators/carriers and aggregators to distribute your Flash Lite content. So it is important to understand how to use DRM and what options are available for Flash Lite content.

The Open Mobile Alliance is an international body that creates standards on which mobile handsets manufactures (OEM), operators and companies can base their solutions and be interoperable. An OMA DRM protected piece of mobile content that is compliant with these specifications will operate correctly on different mobile phones from different OEM. This is a very important concept since no matter which tool you use for protecting your content, it will work on handsets from different OEM.

OMA DRM 1.0 is defined by the following specification. The specification defines three different ways to protect content:

  • Forward Lock – locks content to the individual handsets.
  • Combined Delivery – locks content to the handsets. Playback rights can be applied to the content.
  • Separate Delivery – playback rights can be applied and allows super distribution.

For more details of the different OMA DRM 1.0 protection methods and distribution you can read the following document from Forum Nokia:

The following MIME types are defined for OMA DRM, you will need to define them into your Web Server so that a OMA DRM protected Flash Lite file will be recognized by the mobile phone upon download.

application/vnd.oma.drm.rights+xml .dr
application/vnd.oma.drm.rights+wbxml .drc
application/vnd.oma.drm.content .dcf
application/vnd.oma.drm.message .dm
application/vnd.oma.drm.dd+xml .dd

Note: the "application/vnd.oma.drm.message" is the only one required for Forward Lock.

Refer to the documentation for more details.

OMA DRM 2.0 is defined by the specification on the OMA web site. It applies the same concepts of OMA DRM 1.0 but it offers a higher degree of protection (Separate Delivery method) by introducing stronger encryption methods and also offers protection methods for streaming media such as audio and video. OMA DRM 2.0 introduces other MIME types.

In this article I will concentrate on OMA DRM 1.0 and in particular on the Forward Lock protection method. This protection method is the most common on handsets and the simplest to implement. It is important to understand that not all protection methods are supported by the handsets for OMA DRM.

I will go through an example using the following scenario:

  1. Apply OMA DRM 1.0 Forward Lock to a Flash Lite file (.swf)
  2. Upload the Forward Lock file (.dm) to a mobile web page
  3. Download the Forward Lock file to a mobile phone
  4. Test the Forward Lock file by executing it and trying to send the file to another handset.
Page 2 of 6
Previous Page
Next Page