Defining the metadata and price for all content formats is done once

Publishing and stocking for all content formats is done once

Choosing and delivering compatible content formats to subscribers is automatically done for them

For example, a content provider has a ring tone, Melody, to submit. The content is submitted with the ringtone content type. After the content is submitted, the content provider then submits an edition of Melody that has a monophonic format. The monophonic version of Melody is automatically assigned the metadata and price of the initial submission.

Content Protection

Previously the 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 the Content Delivery Server offers additional DRM agents that can be applied to content, as described in TABLE 2-1.

TABLE 2-1 DRM Types

DRM Type

Description

 

 

CDS DRM Agents

Content is protected using the CDS DRM Agents available in this

 

release of the Content Delivery Server. CDS DRM can only be used

 

for MIDlets.

CDS OMA DRM

Content is protected using the OMA DRM 1.0 Forward Lock format

Forward Lock

only.

Open Mobile

Content is protected per the guidelines defined by OMA DRM 1.0.

Alliance (OMA)

OMA DRM 1.0 offers three types of protection formats: Forward

DRM 1.0

Lock, Combined Delivery, and Separate Delivery.

 

 

The system administrator determines which DRM types are available in the Content Delivery Server at deployment time. The system administrator can choose one or more of the following DRM options:

None (no DRM protection)

CDS DRM

CDS OMA DRM 1.0 Forward Lock

OMA DRM 1.0

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.

20 Administrator Guide • 2005Q4

Page 38
Image 38
Sun Microsystems 5 manual Content Protection, Cds Oma Drm