C H A P T E R 5 |
Content Protection |
This chapter covers the following topics:
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.
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.
The following types of content that cannot have DRM protection:
See Chapter 6 for information on the pricing models that can be used for these types of content.
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.
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.
OMA DRM 1.0 offers three different formats for applying protection, as described in TABLE 5-3.
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:
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.
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:
For a discussion of pricing models, see Chapter 6.
To support the OMA DRM 1.0 formats, a device must support the MIME types listed in TABLE 5-4.
application/vnd.oma.drm.rights+xml |
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.
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.
midlet |
Enabled |
|
none[1] |
Enabled |
|
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.
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.
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.
Copyright © 2008, Sun Microsystems, Inc. All Rights Reserved.