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 -->  <!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"><concept id="GUID-60F25F66-8CC5-46BF-9274-BDE8F9A10B74" xml:lang="en"><title>OMA

    10 DRM v1.0</title><shortdesc>The OMA DRM v1.0 specification enables content providers to associate

    11 certain rights to the content objects for defining how the content can be

    12 used. The Symbian platform supports the mandatory features of the OMA DRM

    13 v1.0 specification.</shortdesc><prolog><metadata><keywords></keywords></metadata></prolog><conbody>

    14 <p>The Symbian platform supports the following OMA DRM 1.0 features:</p>

    15 <ul>

    16 <li><p>Forward-lock</p></li>

    17 <li><p>Combined delivery</p></li>

    18 <li><p>Separate delivery</p></li>

    19 </ul>

    20 <p>In addition, the Symbian platform supports time-based constraints for automated

    21 content, such as background images, UI themes, ring tones, and alarm tones.

    22 However, count-based constraints for automated content are not allowed.</p>

    23 <p>The protection of themes and native applications covers not only the SIS

    24 package itself but also the data after the installation. The protection is

    25 achieved through encrypting essential theme and application data (chosen by

    26 the developer). Protected applications and themes can make use of DRM mechanisms,

    27 such as expiry dates or online rights refresh.</p>

    28 <note><p>For file formats that are not DRM protected, the forwarding is restricted

    29 according to the closed content list.</p></note>

    30 <p>Use the DRM

    31 CAF Agent API to implement the OMA DRM v1.0 features in applications.</p>

    32 <section id="GUID-32071397-5AFA-4FB2-BC9F-C4920B7BBC8C"><title>Forward-lock</title><p>Forward-lock

    33 is a simple mechanism that prevents content from leaving the mobile device.

    34 It provides basic copy protection that protects the rights of content owners.

    35 The content is delivered to the device in a DRM message without associating

    36 a rights object to the content. Forward-lock content can be opened and played

    37 freely in the given device but cannot be forwarded or used in any other device.</p></section>

    38 <section id="GUID-EF3B7671-9309-419A-ACC8-8C7FF266B9FA"><title>Combined delivery</title><p>Combined

    39 delivery is similar to OMA forward-lock, but additional usage rights can be

    40 added to the content, such as one-time use, or use for a week. This allows

    41 the previewing of content, or the adoption of various new business models

    42 by applying different usage rights. The content and rights are delivered to

    43 the device within the same DRM message. The device enforces the usage of the

    44 content according to the rights. The device does not allow forwarding the

    45 right or the content to any other device.</p><note><p>Forward-lock and combined

    46 delivery protected content is received to the device as plain text, but is

    47 encrypted as soon as it is received. After the content has been encrypted,

    48 it can only be opened and consumed in the device where it was originally downloaded.</p></note></section>

    49 <section id="GUID-389B54FE-BCEF-4462-9513-147D4ED4565F"><title>Separate delivery</title><p>Separate

    50 delivery is similar to combined delivery but with added security. Content

    51 is delivered as encrypted files separately from usage rights, which are delivered

    52 via a different channel. Separate delivery also enables the superdistribution

    53 business model, in which DRM-protected content can be sent from mobile device

    54 to mobile device, for example sending the content as part of an MMS to a friend.

    55 The recipient can then acquire a license to get a preview or buy the content.

    56 This makes viral marketing a potentially powerful concept. </p><p>In separate

    57 delivery, the content is in the format defined in the OMA DRM Content Format

    58 specification. The content is encrypted using a symmetric encryption key called

    59 content encryption key (CEK). The content can be decrypted only with the same

    60 key that has been used for encryption. With separate delivery, the encrypted

    61 content is delivered to the device separately from the rights (typically over

    62 HTTP download or MMS). The rights object containing the CEK is delivered to

    63 the device using connectionless WAP Push over SMS.</p><p>Symbian applications

    64 that deal with combined delivery and separate delivery protected media objects

    65 are capable of enforcing the usage rights constraints that are defined in

    66 the rights objects. The applications are able to detect when the usage rights

    67 related to a combined delivery and separate delivery protected media object

    68 have become expired. </p><p>The content provider can specify a timeout value

    69 for the delivery of the rights object when delivering content over HTTP. The

    70 user is notified if the rights object does not arrive within the specified

    71 time. The rights object related to a separate delivery protected media object

    72 can also be updated when it expires.</p> </section>

    73 <section id="GUID-4F3BFECA-CBF4-4CFE-9C9D-EADFF4C47D0B"><title>Supported file

    74 types</title><p>The file types that are defined in OMA DRM v1.0 correspond

    75 to the following delivery methods:</p><ul>

    76 <li><p>Delivery message (.dm)</p><p>Contains the content. It is used in both

    77 OMA forward-lock and combined delivery. In an OMA forward-lock delivery message,

    78 the file contains only the protected content, whereas in a combined delivery

    79 message, the file contains both the rights (defined in ODRL) and the content.

    80 The MIME type for this file type is <codeph>application/vnd.oma.drm.message</codeph>. </p></li>

    81 <li><p>DRM content format (.dcf)</p><p>Contains the encrypted content. It

    82 is used in separate delivery where the content is encrypted into the message

    83 without the rights. The key used to encrypt the content is sent separately

    84 with the rights to the device. The MIME type for this file type is <codeph>application/vnd.oma.drm.content</codeph>.</p></li>

    85 <li><p>DRM rights object, binary (.drc)</p><p>Contains the rights object,

    86 specified in binary, as well as the key used to encrypt the content in the

    87 DCF file. The MIME type for this file type is <codeph>application/vnd.oma.drm.rights+wbxml</codeph>.</p></li>

    88 <li><p>DRM rights object, clear text (.dr)</p><p>Contains the rights object,

    89 specified in clear text, as well as the key used to encrypt the content in

    90 the DCF file. The MIME type for this file type is <codeph>application/vnd.oma.drm.rights+xml</codeph>.</p></li>

    91 </ul></section>

    92 <section id="GUID-AE6B6119-D209-4777-A6D8-EBF8B7D8DB6A"><title>Downloading

    93 DRM-protected files</title><p>You can use the following methods to download

    94 DRM-protected files:</p><ul>

    95 <li><p>HTTP download</p></li>

    96 <li><p>Multimedia messaging service (MMS)</p></li>

    97 </ul><p>You can use the following methods to download files in the DCF format:</p><ul>

    98 <li><p>MMS</p></li>

    99 <li><p>HTTP</p></li>

   100 <li><p>Bluetooth</p></li>

   101 <li><p>IrDa</p></li>

   102 <li><p>Multimedia card (MMC)</p></li>

   103 <li><p>E-mail</p></li>

   104 <li><p>Any other connectivity method that supports file transfer</p></li>

   105 </ul><p>For more information, see <xref scope="external" href="http://library.forum.nokia.com/topic/Design_and_User_Experience_Library/GUID-C7E6ACA8-94B4-4A55-A2F2-C4E6EBA46FD4.html">Video distribution channels</xref>.</p></section>

   106 </conbody></concept>