Open Mobile Alliance (OMA) DRM is a mechanism used for protecting distributed content. Using DRM, the content can be accessed on authenticated devices depending on the usage rights set by the content owner. OMA DRM addresses the various technical aspects of this system by providing appropriate specifications for content formats, protocols, and a rights expression language.
Application developers are directly affected by the manner in which content is distributed, such as whether content can be freely copied between devices or not. The introduction of OMA DRM technology changes the way content is distributed and consumed. Understanding and using the OMA DRM standard enables your applications to gain access to high-quality branded content.
Because OMA DRM is an industry-wide standard, no other DRM solution can provide access to as many mobile users. OMA DRM contains a client component, providing a mechanism to control not only piracy via the mobile network but also via local connections, such as Bluetooth, infrared, and MultiMediaCard (MMC) memory cards. OMA continues to develop DRM standards as a joint effort among its members.
The following OMA DRM versions are supported:
OMA DRM v2.0 offers improved protection and support features, but due to higher licensing fee it is not as widely used as v1.0.
Nokia Mobile Internet Toolkit is an example of a tool that can be used to create mobile content with OMA DRM protection.
For more information on OMA DRM, see:
S60 3rd Edition supports OMA DRM v.1.0, and as optional feature (which might not be available in all devices) OMA DRM v2.0 for music and audio content, only. The following table summarizes the differences between OMA DRM v1.0 and v2.0.
Feature |
OMA DRM v1.0 |
OMA DRM v2.0 |
|---|---|---|
Security level during content transfer |
Content is delivered in unprotected format and encrypted in the device. |
Content is delivered in encrypted DRM content format (DCF). Use the DRM CAF Agent API methods to encrypt content. |
Receiving rights objects |
Using unconfirmed wireless application protocol (WAP) push. |
Using the rights object acquisition protocol (ROAP). |
Constraints |
|
|
Use the DRM CAF Agent API methods to determine the DRM version of a file.