Content Protection

C H A P T E R 5

Content Protection

This chapter covers the following topics:

Digital Rights Management

Using CDS DRM Agents and CDS OMA Forward Lock

Using OMA DRM 1.0

Associating Content Types with DRMs

Enabling and Disabling a DRM

Digital Rights Management

Previously Content Delivery Server offered digital rights protection of content with Sun Java System Content Delivery Server Digital Rights Management (CDS DRM) agents. The current version of Content Delivery Server offers additional DRM types that can be applied to content. The system administrator determines which DRM types are available in Content Delivery Server at deployment time. The system administrator can choose one or more of the following DRM options as described in TABLE 5-1.

TABLE 5-1 DRM Types
DRM Type	Description
CDS DRM Agents	Protects Java applications without requiring additional DRM software. Only one CDS DRM agent can be used per deployment.
CDS OMA DRM 1.0 Forward Lock	Prevents unauthorized redistribution of content without requiring additional DRM software.
Open Mobile Alliance (OMA) DRM 1.0	Prevents unauthorized use and redistribution of content. You must have an application that implements the OMA DRM 1.0 guidelines available to handle the rights management when using this DRM type. OMA DRM 1.0 offers three types of protection formats: Forward Lock, Combined Delivery, and Separate Delivery. To use OMA DRM 1.0 in the Content Delivery Server, you must have an OMA DRM 1.0 provider. See the Sun Java System Content Delivery Server Installation Guide for details.

The system administrator can also has the option of not having content protection by choosing None. Use this option when you do not need to control distribution or enforce usage rights. This option cannot be disabled.

Note - Content that is prewrapped with OMA DRM protection must not have additional protection applied. If you are submitting prewrapped content, make sure that the DRM method assigned to the content type by the Catalog Manager administrator is None.

Content Without DRM Protection

The following types of content that cannot have DRM protection:

Short Messaging Service (SMS) content (monophonic ringtone, operator logo, group logo, and sms picture) - Due to the delivery format for SMS content, DRM protection cannot be applied. The No DRM option is associated by default for all SMS content types.

Remotely hosted copyrighted content - Attempts to submit remotely hosted content items that have content types that are associated with one of the DRM options (other than No DRM) fail.

Streaming content types - Because streamed content is delivered directly to subscribers from the streaming server, Content Delivery Server cannot apply DRM protection. Additionally, DRM protection is not applicable for the basic pricing models of free always, first download only, and every download with which streamed content can be associated.

See Chapter 6 for information on the pricing models that can be used for these types of content.

Using CDS DRM Agents and CDS OMA
Forward Lock

The Content Delivery Server provides you with CDS DRM Agents and CDS OMA DRM 1.0 Forward Lock. CDS DRM Agents can only be used for MIDlet content types, while CDS OMA DRM 1.0 Forward Lock can be used for any supported content type in the Content Delivery Server except for inapplicable content described in Content Without DRM Protection.

CDS DRM has several agents that verify a subscriber’s license. TABLE 5-2 describes the CDS DRM Agents.

TABLE 5-2 CDS DRM Agents
Title	Description
Disconnected Time Sensitive	Supports the download-based (free always, first download only, and every download) pricing models and the time-based (recurring subscription and per period) pricing models.
Disconnected Use Sensitive	Supports the download-based (free always, first download only, and every download) pricing models and the usage-based (trial and per use) pricing models.
Disconnected Use and Time Sensitive	Supports all pricing models.
Small Connected Use and Time Sensitive	Supports all pricing models. Note: To prevent runtime errors, do not use this DRM agent with applications that perform the following actions: Show an alert before calling the `startApp` method. List their Record Stores. Modify or remove the Content Delivery Server Record Store.
Midsize Connected Use and Time Sensitive	Supports all pricing models. Note: To prevent runtime errors, do not use this DRM agent with applications that perform the following actions: Show an alert before calling the `startApp` method. Modify or remove the Content Delivery Server Record Store.
Standard Connected Use and Time Sensitive	Supports all pricing models.

For more details about CDS DRM Agents, see the Sun Java System Content Delivery Server Integration and Configuration Guide.

When no DRM agent is selected, only the download-based (free always, first download only, and every download) pricing models are supported. No code is added.

Multiple CDS DRM Agents can be specified per deployment. The Catalog Manager administrator can work with the system administrator to specify the desired agents in the cdsdrmagent.properties file.

Each agent handles license validation differently. For further details of these types, see the Sun Java System Content Delivery Server Integration and Configuration Guide.

CDS OMA DRM 1.0 Forward Lock is simply the OMA DRM 1.0 Forward Lock format (no Combined or Separate Delivery) only and can be used with any content type except for the inapplicable content described in Content Without DRM Protection. It provides basic copy protection with the content and it does not allow content to be forwarded to another device.

The default setting of Enabled is used for CDS DRM Agents and CDS OMA DRM 1.0 Forward Lock. You can disable one or more of these options or enable OMA DRM 1.0 with the cdsi db command. See the Sun Java System Content Delivery Server Integration and Configuration Guide for information on this command.

Using OMA DRM 1.0

OMA DRM 1.0 offers three different formats for applying protection, as described in TABLE 5-3.

TABLE 5-3 OMA DRM 1.0 Formats
DRM Type	Description
Forward Lock	Content is delivered with basic copy protection. Content cannot be forwarded to another device.
Combined Delivery	Content is delivered together with basic copy protection and additional usage rights are included. Content cannot be forwarded to another device.
Separate Delivery	Encrypted content is delivered separately from the digital rights. Content can be forwarded to another device.

For a thorough discussion of OMA DRM 1.0, go to http://www.openmobilealliance.org/. The default setting for OMA DRM 1.0 in the Content Delivery Server is Disabled. You can enable this DRM after deployment (see Enabling and Disabling a DRM for more information).

If OMA DRM 1.0 is selected as an available DRM type, the system administrator can set a preference for the type of rights delivery format, as follows:

Only combined delivery is used

Only separate delivery is used

Separate delivery is used whenever possible, otherwise, combined delivery is used

The last preference option provides flexibility in providing digital rights protection with content. Work with your system administrator to determine what rights delivery preference to use, if desired. The preference is set in the configuration properties file for the Content Delivery Server.

Not all devices fully support all three OMA DRM 1.0 content protection formats although they can support a subset. For example, devices that support Combined Delivery will accept content with Forward Lock or Combined Delivery but cannot accept content with Separate Delivery. To deliver content to these devices, set the delivery preferences to allow these devices to receive content using Combined Delivery when Separate Delivery is not supported.

The possible associations of DRM types to content types are listed in Chapter 6. See “Adding Content Types” in the Catalog Manager online help for information on how to assign DRM types to content types.

OMA DRM 1.0 and Non-Compliant Devices

For devices that are not compliant with OMA DRM 1.0, the Catalog Manager administrator can configure the Content Delivery Server with one of the following options to deliver content with a free always, first download only, or every download pricing model:

Deliver all content to non-compliant devices as unprotected original content (that is, content as received from the content provider). Only content with the free always, first download only, or every download pricing model can be delivered as unprotected content.

Deliver only free content as unprotected original content to non-compliant devices. Only content with the free always pricing model can be delivered as unprotected content.

Make the content unavailable to non-compliant devices.

For a discussion of pricing models, see Chapter 6.

MIME Types for OMA DRM 1.0

To support the OMA DRM 1.0 formats, a device must support the MIME types listed in TABLE 5-4.

TABLE 5-4 Required MIME Types for OMA DRM 1.0
OMA DRM 1.0 Format	Required MIME Type Support
Forward Lock	`application/vnd.oma.drm.message`
Combined Delivery	`application/vnd.oma.drm.message` `application/vnd.oma.drm.rights+xml`
Separate Delivery	`application/vnd.oma.drm.rights+xml` `application/vnd.oma.drm.rights+wbxml` `application/vnd.oma.drm.content`

These MIME types are used to determine the OMA DRM 1.0 format supported on a device. Support for these MIME types must be added to device profiles for devices capable of receiving OMA DRM 1.0 protected content.

Associating Content Types with DRMs

When assigning a DRM type to a content type, be aware that CDS DRM can only be used with MIDlets. Be aware also that SMS and Streaming content types, remotely hosted copyrighted content, and content that is prewrapped with OMA DRM protection cannot be assigned a DRM. Other than these restrictions, the choice of no DRM, CDS OMA DRM 1.0 Forward Lock, and OMA DRM 1.0 can be used with any content type.

This release of the Content Delivery Server contains the default associations of DRM types to content types shown in TABLE 5-5.

TABLE 5-5 DRM Options and Associated DRM Types and Content Types
DRM Type	Content Type	Default Setting for DRM Type
None (no DRM protection)	`group logo` `iappli` `image` `midlet` `monophonic ringtone` `operator logo` `ringtone` `sms picture` `streaming_audio` `streaming_video` `video`	Enabled
CDS DRM	`midlet`	Enabled
CDS OMA DRM 1.0 Forward Lock	none^{^[1]}	Enabled
OMA DRM 1.0: Forward Lock Combined Delivery Separate Delivery	none	Disabled

You can assign a DRM through the MIME types page in the Catalog Manager. During deployment only one DRM type can be associated with a particular content type. That means that even though None, CDS OMA DRM 1.0 Forward Lock, and OMA DRM 1.0 are all enabled, only one of them can be associated with the picture content type. The Content Delivery Server provides six CDS DRM Agents. More than one agent can be specified per deployment. See Chapter 6 for a list of the possible associations of DRM types to content types. See TABLE 5-2 for agent descriptions.

You can assign the DRM options to the associated content types given in TABLE 5-5 but you are not restricted to those combinations, for instance, you can apply None to all content types if you wish. For details on how to assign a DRM, see “Adding Content Types” in the Catalog Manager online help.

You can change the DRM option for a content type after deployment if needed. See Enabling and Disabling a DRM for more information.

Enabling and Disabling a DRM

You can change the DRM selection for a content type after Content Delivery Server is running by switching DRMs. You can also enable or disable DRMs after deployment. For example, if None is assigned to the image content type and you later choose to use OMA DRM 1.0, you can enable that DRM during runtime and assign that DRM to the image content type.

If you decide you no longer want to support the CDS DRM Agent, you can disable that agent during runtime and assign another option, such as None to the midlet type content. Use caution when disabling a DRM. Make sure that the DRM you are disabling is not currently associated with a content type. Follow this sequence:

1. Change the DRM assigned to the content type.

2. Disable the old DRM.

Even though the DRM is disabled, content protected under that DRM can still exist in Content Delivery Server. Content submitted after a new DRM is assigned is protected under the new DRM. Another factor affected by changing the DRM is the pricing model associated with the content type. Changing DRMs can change which pricing models are available. The following section discusses pricing content in more detail.

^{1 (TableFootnote) Although no content type is associated with CDS OMA DRM 1.0 Forward Lock by default, you can assign it to the content type of your choice through the Catalog Manager.}