Digital rights management

MIDlet protection

Java applications can be protected with OMA DRM v1.

OMA DRM v1 specifies the following distribution methods:

• Forward lock

  In forward lock distribution, the JAR package has an additional small header. The JAR file is not encrypted when the application is downloaded to the device, but the device will handle encrypting the JAR file. Forward locked protected applications cannot be sent to other devices.

• Combined delivery

  In combined delivery distribution, the JAR package has an additional header which specifies usage restrictions for the application. The JAR file is not encrypted when the application is downloaded to the device, but the device will handle encrypting the JAR file. Combined delivery protected applications cannot be sent to other devices.

• Separate delivery

  In separate delivery the JAR file is delivered to the device in encrypted format. The encrypted JAR package and the digital rights are delivered to the device separately, for example with a JAR that is delivered with HTTP and digital rights is delivered with a binary SMS.

• Superdistribution

  In superdistribution the JAR file is delivered to the device in encrypted format. Superdistribution of Java applications means that the applications are made available in encrypted format and can be freely distributed by the end users. The end users then buy digital rights to use the application.

DRM protection does not affect MIDlet creation. You can decide whether or not to use DRM when the application is ready for distribution. At the distribution phase DRM tools can be used to add forward-lock and usage restrictions to the application. For detailed information on how to use DRM protection for a Java application, see document Implementation Best Practices For OMA DRM v1.0 Protected MIDlets v1.0 on Nokia Developer.

Symbian devices support Java application DRM protection since S60 2nd Edition, Feature pack 2. From Symbian^3 onwards, the installation of DCF package fails if there is no digital rights available in the device. In earlier releases the phone waits for the digital rights object to be delivered to the device with binary SMS messages. If the binary SMS message does not arrive to the device immediately, the end user experience is problematic - the end user is not able to use the protected JAR (DCF file) in the device.

Superdistribution of Java applications has been supported in S60 3rd Edition devices, but the suggested way to share applications among the users is sending URL which points to the place which provides the application. This way the web site can provide to the device the application optimized for each device.

Series 40 has supported Java application DRM protection since Series 40 1st Edition. These devices store all over the air downloaded Java applications as forward locked. Note that the background MIDlets should not use DRM usage constrains. Series 40 does not support superdistribution.

Content protection

Java applications can access DRM protected content by using Mobile Media (JSR-135) API. The DRM protection is invisible to the developer: Mobile Media API is used in similar manner as in the case when Mobile Media API is used to access unprotected media files. For example:

Player p = Manager.createPlayer("file:///E:/Sounds/Digital/jack_aac.dcf"); 
   p.start();

If a MIDlet downloads DRM protected content by using the HTTP implementation of the phone, the downloaded content and rights are automatically stored to the phone in secure way and content is accessible through Mobile Media API. Nokia Java implementations do not support DRM API (JSR-300). A MIDlet cannot be used to manage DRM rights and Java implementation cannot be used to create new DRM protected files.

Symbian devices are able to play DRM protected content with Mobile Media API (JSR-135) according to the table.

Series 40 devices are able to play DRM protected content with MobileMedia API (JSR-135) according to the table.