|
Home · All Namespaces · All Classes · Grouped Classes · Modules · Functions | |
The DRM Agent Plug-in Interface allows DRM agents to be installed into the Qt Extended Document System.
The document system defers all DRM specific tasks to a DRM agent through the plug-in interface, this includes rights management functionality, content activation, and decrypting protected content.
For more information see DRM Agent Integration.
Content received in the OMA DRM message format (application/vnd.oma.drm.message; .dm) is encrypted and bound by the device on which it was received. It is consumed and managed in the same manner as any other content, except that it is emblazoned with a key icon when presented in document lists and that it may not be edited or copied.
Forward lock message impose no limitations on the consumption of the content. Combined delivery messages include a rights object which specifies constraints to be placed on the consumption of the content. Constraints include limiting the number of times it may be consumed, limiting the accumulative time it may be consumed for, a limited period of availability after the first consumption, and absolute dates and times it is available between.
The OMA DRM agent functionality is provided by a reference integration of the BeepScience DRM Agent.
OMA DRM Separate Delivery content (application/vnd.oma.drm.content; .dcf) is received in an encrypted container format. The key required to decrypt the content is delivered separately as part of a rights object (application/vnd.com.drm.rights+xml; .dr, application/vnd.oma.drm.rights+wbxml; .drc) pushed to the device in a WAP push. Once received separate delivery content is subject to the same restrictions as combined delivery content with the exception that the encrypted container may be redistributed.
If the user attempts to consume separate delivery content they do not have rights for they may be prompted to visit a website from which they can purchase rights. The purchased rights are subsequently delivered in a WAP push to the device.
ROAP triggers are the primary method of acquiring rights in OMA DRM v2 and are received either through a download from a web page or in a WAP push, in both case the DRM agent will perform all the actual processing of the trigger once received.
DCF files may contain an embedded preview object; an unprotected and likely reduced quality version of the actual content. Where rights are not available for an item of content this preview is in its place. Before rendering a preview object the user is given the option to activate the full version of the content, if they decline they are then notified that the version rendered is a preview version.
DCF files may contain a URL where preview rights are available. The user is prompted to download these rights when trying to access locked content, or if a global option to download without prompting is enabled they will automatically be downloaded.
DCF files may contain a URL from which rights are downloaded automatically provided a global automatic download option is selected.
Some licenses belong to domains, when trying access content bound to a domain the device does not belong to, the user is prompted to join the domain, or upgrade the domain if the device belongs to a different version of the domain.
| Copyright © 2009 Trolltech | Trademarks | Qt Extended 4.4.3 |