White Paper V600
of times or for a limited period of time. Rights can also be defined so that the user is not able to forward content to other devices.
Note: All supported image, audio and video formats can be protected by DRM.
encrypted, users cannot access it before the rights have also arrived in the device. In this case, the content can be freely distributed on the network, only users with the rights file can access the con- tent. Content providers can deliver the rights to the user using push technology.
Packaging of rights and content
Rights and content can be packaged together and delivered to the device as one DRM package. As an alternative, content can be delivered to the device first, followed by the rights later being pushed to the device, for example via SMS. The kind of service and business model adopted by the content provider determines how the content and rights should be packaged and delivered to the device.
Protection properties
Content protection according to the OMA DRM standard gets special properties. Content with forward lock protection has the “Send to” option disa- bled, which prevents it from further distribution.
Unless the content is encrypted, the user cannot copy DRM content to other devices since the “Send to” option is disabled for pictures, music tones, etc. that are OMA DRM protected. Content providers may choose to protect some content, but leave some content unprotected.
Package and delivery
The OMA DRM standard defines two ways to package and deliver rights and content to a device: combined or separated.
Combined delivery
Rights and content are packaged together into one DRM Package and delivered to the device. In the simplest case, no special rights are defined. The content is just put into a DRM package, thus protected from being copied out from the device by the user. This special case is called
Separate delivery
Rights are defined and sent in a push message. The content is encrypted and made available for users to download to their devices. The decryption key is put into the rights file. Since the content is
Downloading servers and publishing servers
When using a mobile phone, the users do not have to be aware of the network architecture. During a content downloading session, typically many physical servers are involved. Sometimes transactions may take place between different companies’ serv- ers.
The actual content may be put on one server, the downloading server. The content can be reached, for example, through references from one or many other servers, the publishing servers. The content creator puts his or her content on the downloading server through an interface to the content provider.
The user navigates to the publishing server and selects the content, or rather a link to or description of the content. The content is then downloaded from the actual downloading server.
When content is downloaded to the device, operators generate revenues from the user via, for exam- ple, their billing system. Operators might in their turn be billed for rights by the content aggregator, content provider or directly by the content creator.
25 | August 2005 |