The mechanism for indicating a ‘forward locked’ status is to set the NDIS bit for the file within the file system.

Combined Delivery

After the download of a DRM message has been completed, the handset will strip out the media object and the rights object that are encapsulated within the DRM message prior to dispatching the object for preview. If the DRM message is received without a descriptor file, the MIME type associated with the encapsulated media object should be used to verify that the OMA download descriptor ‘type’ meta data field matches the MIME type of the media object within the DRM message.

Once the media object has been extracted from the DRM message, the original DRM message can be discarded. Along with passing the media object to the content dispatcher for preview, the handset shall indicate to the content dispatcher that the media object is ‘forward locked’.

If the user selects to store the content from the preview: The media shall be stored in the appropriate file directory and shall be marked as ‘forward-locked’ using the NDIS bit. The rights object shall be stored in a protected portion of the file system. Rights objects are NEVER to be forwarded. Association between the rights object and the media MUST be maintained while stored in the file system.

Separate Delivery

In MOTOKRZR K3 implementation, for Forward Lock and Combined Delivery content, the Media objects will be encrypted (AES128) and packaged according to the same mechanism as Separate delivery, the encryption key is generated randomly and unique to each content on a phone. Thus the encrypted content can be stored anywhere in the phone or TransFlash card. A right object will also be created to save the right constraints and encryption key. The right object is stored in a hidden directory in phone flash memory which can not be accessed by end user. Thus the mechanism for indicating a ‘forward locked’ status is to set a special field in right object.

Right Object

Forward Lock files do not have Right Objects associated with the content. The user has unlimited usage. The handset will mark the file as "do not forward" and the user will be able to consume the content as a normal file. The only limitation is the handset will not allow the user to send the file via any transfer method.

In the case of Combined Delivery there is a Right Object associated with the content. The Right Object will be stored in a secure area and the user will not have access to it. The handset will not allow the user to send it via any delivery method. The Right Object will define the constraints for content usage. This Right Object can have count, time, date, or interval constraints. The application will check the Right Object before consuming the content.

30

Page 30
Image 30
Motorola K3 technical manual Right Object, Separate Delivery