Important:
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
4/8/2010

FDRM-protected content can have a set of rights associated with it. Rights define how the device can use content. For example, a JPEG image may have rights to permit the user to display the image but not to forward the image to another user. The Windows Mobile FDRM API treats content that is not FDRM-protected as if it has all possible rights.

FDRM-protected content can also have limits on how long or how often the content may be used. For example, you might have a sound file that can be played only ten times, or only until March 1, or only for two weeks from the time it is first played, or only ten times until March 1.

Once these limited rights have been exhausted, it can be possible for the user to acquire additional rights. Applications may initiate the acquisition of additional rights or the FDRM provider may initiate the acquisition when it handles the error that is caused by expired rights.

The FDRM provider is responsible for providing most of the user interaction for displaying or renewing rights associated with a content-protected object. For this purpose, some calls require the handle, HWND, of the active window to parent their UI. Additionally some calls may take a long time to complete because an interaction with the rights management server is required.

Applications cannot create protected content. Applications that receive protected content, for example Internet Explorer Mobile and Multimedia Messaging Service (MMS), call a content handler that stores the content in the device's file system and stores the content's rights in a rights store. The FDRM provider supplies the content handler. The rights associated with the content may not be included with the content but are received separately over WAP Push or over direct HTTP. The FDRM provider is responsible for receiving these rights, storing them in the right's store, and notifying the user. The following list shows some of the FDRM content rights:

Prompt-based rights

A general term for content that has count rights or the start of interval-based rights associated with it. Count or interval rights have limits on how long or how often the content may be used. Mobile Operators may require a user to be notified before using content with count or start of interval-based rights.

If you choose to suppress the prompted-based rights use notifications, content should be treated as non-prompted based rights would.

In general the count- and interval-based rights are referred to as prompt-based rights because they may require a user prompt before rendering content.

Note:
Registry keys enable you to turn the count- or interval-based rights notifications on or off. Other Registry keys enable you to notify the user when the last count-based right is being used.
Forward-Locked

Content that is locked to the device and cannot be forwarded for use on another device.

Combined Delivery protected content

Content that is Forward-Locked to the device and includes usage rules.

Separate Delivery content

Content that can be forwarded, but has DRM protection. This content included usage rules, but the usage rules cannot be forwarded from the device.

See Also