Home · All Classes · Annotated · Functions

Document System: DRM Integration

• DRM Standards Compliance

Files and content subject to DRM are transparently browsed, launched, moved, deleted and examined for their properties, in the same way as other files. Additionally DRM rights are able to be viewed as part of the properties of a file. Icons have an adornment to indicate that, in addition to their mime-type, the file is a DRM controlled file.

DRM integration requires that:

• DRM content be presented transparently alongside non-DRM content
• back-end abstraction layer provides hooks into the DRM agent
• DRM standards compliance statements must be honored by the implementation
• DRM transactions provide triggers into the server to update with new content
• meta-information is extracted from encrypted DRM files using agent calls, and cached as appropriate.

The DRM architecture is shown in the following diagram:

DRM Standards Compliance

DRM complies with the Open Mobile Alliance (OMA) Version 1.0. When the Qtopia stack is released, a DRM compliance statement is made as part of the release. The Qtopia software integrated into a final ROM image implements compliance with DRM standards as per the compliance statement.

In OMA DRM compliance, compliance with the later-listed compliance points requires compliance with all previous levels as well. When reading the listings of compliance levels below, bear in mind that each level includes rather than supersedes the previous levels.

The only exception to this for devices which support Forward Lock. These are only required to discard messages which contain a rights object. This requirement is removed at higher levels.

Under OMA DRM Version 1.0 devices which only comply with Forward Lock provisions can still be said to be standards compliant - these are the only provisions with the MUST keyword, the others are MAY. Forward Lock does not use any rights object and thus is the simplest to implement.