The following table summarizes the OMA DRM v2.0 features that S60 supports.
Feature |
Description |
|---|---|
The rights object acquisition protocol (ROAP) schema parsing and processing over HTTP |
ROAP enables devices to request and acquire rights objects securely over HTTP from a rights issuer. |
Storing rights issuer context information |
The rights issuer context information, such as agreed protocol parameters, protocol versions, and certificate preferences, is stored in a secure location inside the device. |
Certificate checking, including online certificate status protocol (OCSP) response validation |
A device must verify signed rights issuer responses and rights objects as well as check the validity and status of the rights issuer certificate and any other revocable certificates in the rights issuer certificate chain. To enable the device to check the certificate, the rights issuer must include a complete set of OCSP responses for its certificate chain when sending signed responses to the device. |
DRM content and rights object formats, including rights object fields expressing permissions and constraints |
Rights object are formatted in the rights expression language (REL), which is a mobile profile of open digital rights language (ODRL) v1.1. REL enables accurate specification of relevant metadata and actual rights. The DRM content format is specified in the OMA DRM Content Format v2.0 document (included in the OMA DRM v2.0 specification). |
Replay protection for rights objects |
Rights objects that contain counters, intervals, timed counters or accumulated time constraints are monitored by the DRM system to prevent sending the same rights object several times. |
DRM time and DRM time synchronization |
Secure time for rights enforcement. Time is synchronized automatically with ROAP. |
Capability signaling |
Capabilities are signaled using HTTP headers and the user agent profile. |
Domain model support |
Users can create domains for content services. A single domain can include a number of devices, defined by the rights issuer, that share rights to access a set of DRM content formats. This shared rights object is called a domain key. Individual rights objects for a domain are bound to a specific domain key. The devices in the domain can be any devices supporting OMA DRM v2.0, for example mobile phones, PCs or music players. A device can have many domains to many services and also many domains to a single service. The service provider can enable or disable this feature. |
Secure backup and restore of content and usage rights |
Users can take device backups that include DRM protected content and rights objects. The security level is ensured with strong encryption. |
Playback of OMA DRM v2.0 protected audio in third party applications |
Enables third party applications to call and control the playback of DRM protected audio using a secure audio path. For more information, see Playing DRM-protected audio content. |
Binding DRM v2.0 specific rights objects to the SIM card |
If the device supports a SIM/USIM/R-UIM and the |