|
1 <?xml version="1.0" encoding="utf-8"?> |
|
2 <!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. --> |
|
3 <!-- This component and the accompanying materials are made available under the terms of the License |
|
4 "Eclipse Public License v1.0" which accompanies this distribution, |
|
5 and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". --> |
|
6 <!-- Initial Contributors: |
|
7 Nokia Corporation - initial contribution. |
|
8 Contributors: |
|
9 --> |
|
10 <!DOCTYPE concept |
|
11 PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> |
|
12 <concept id="GUID-249E8EE2-5334-4CA2-93AB-4010E6404D11" xml:lang="en"><title>OMA |
|
13 DRM v2.0</title><shortdesc>The OMA Digital Rights Management (DRM) v2.0 specification provides |
|
14 stronger content protection and improved functionality for rich media content, |
|
15 such as music and video. The specification enables an end-to-end DRM system |
|
16 that takes into account the need for secure distribution, authentication of |
|
17 devices, revocation and other aspects. The Symbian platform supports the mandatory |
|
18 features of the OMA DRM v2.0 specification.</shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody> |
|
19 <p>The improved security, compared with OMA DRM v1.0, is achieved by using:</p> |
|
20 <ul> |
|
21 <li><p>Bilateral authentication between the rights issuers and devices</p></li> |
|
22 <li><p>Public key infrastructure (PKI) certificates and online revocation |
|
23 checks</p></li> |
|
24 <li><p>Protection of the confidentiality and integrity of the rights objects</p></li> |
|
25 </ul> |
|
26 <p>Improved functionality and usability are achieved, for example, by providing |
|
27 enhanced preview functions and mechanisms for sharing content within a registered |
|
28 community of devices, called a domain. </p> |
|
29 <p>The OMA DRM v2.0 specification as such is not mobile-specific, which means |
|
30 that there can be OMA DRM v2.0 non-mobile devices, such as PC software, thus |
|
31 enabling better interaction and content transferability between devices.</p> |
|
32 <p>In the Symbian platform, OMA DRM v2.0 is enabled for music |
|
33 and video files via HTTP or OMA download. For more information on the OMA |
|
34 DRM v2.0 features that are supported in the Symbian platform, see <xref href="GUID-EAF3FCBE-A68C-4881-A461-774D481DD315.dita">Supported |
|
35 OMA DRM v2.0 features</xref>. |
|
36 For more information on supported OMA DRM v2.1 features, see <xref href="GUID-09A4172E-DB54-4ADF-A718-8100154A6031.dita">OMA DRM |
|
37 v2.1</xref>.</p> |
|
38 <section id="GUID-4D792C94-43D5-44CD-BE3E-677819F4436F"><title>Silent rights |
|
39 object acquisition</title><p>Silent rights object acquisition means that no |
|
40 DRM-specific notifications are shown during the acquisition if the feature |
|
41 is enabled in the media file. The OMA DRM specification defines two types |
|
42 of silent rights URL:</p><ul> |
|
43 <li><p>On-demand</p><p>Rights object is acquired when the user tries to open |
|
44 the file.</p></li> |
|
45 <li><p>In-advanced</p><p>Rights object is acquired at the earliest possible |
|
46 time.</p></li> |
|
47 </ul><p>The Symbian platform supports only on-demand silent rights acquisition. |
|
48 The in-advanced type is treated similarly as on-demand. </p></section> |
|
49 <section id="GUID-D3DD4B99-351F-43FF-B911-5DF87FEF09AA"><title>Transaction |
|
50 tracking</title><p>Transaction tracking allows the <xref href="GUID-788FCBFA-B4FB-4001-B838-4B59995E2E33.dita">rights |
|
51 issuer</xref> to track the content flow from one user to another via superdistribution. |
|
52 The rights issuer includes a <codeph>TransactionID</codeph> in the rights |
|
53 object, which allows the rights issuer to build a reward mechanism, for example.</p></section> |
|
54 <section id="GUID-CBBDB66E-7D4E-4931-A886-524D17529AAD"><title>PKI requirements</title><p>In |
|
55 the PKI, secret data is encrypted with the recipient's public key. Only the |
|
56 recipient can open the content with the private key. This private key system |
|
57 is sometimes known as symmetric cryptography and the public key system as |
|
58 asymmetric cryptography. PKI makes sure that both the mobile device and server |
|
59 are authenticated. The key in the mobile device identifies the mobile device |
|
60 and the key in the server identifies the server. The device key is stored |
|
61 by using data caging. If the key is lost, the downloading rights are revoked, |
|
62 but usage rights still apply.</p><p>In addition to the software implementation |
|
63 in the Symbian platform, each device must have the keys and certificates listed |
|
64 below:</p><ul> |
|
65 <li><p>Device private key</p></li> |
|
66 <li><p>Public certificates</p></li> |
|
67 <li><p>Device certification authority (CA) certificate</p></li> |
|
68 <li><p>CA root certificate</p></li> |
|
69 </ul><note><p>The Symbian platform does not provide PKI keys, certificates, |
|
70 or server infrastructure. <xref href="http://www.cm-la.com" scope="external">Content |
|
71 Management License Administrator</xref> is a known PKI provider for OMA DRM |
|
72 v2.0. The DRM implementation in the Symbian platform is prepared for CMLA, |
|
73 but it is not certified, because only devices can be certified by CMLA.</p></note></section> |
|
74 </conbody></concept> |