Compartir a través de


PlayReady Technology Concepts

In typical use, Microsoft PlayReady protects content by encrypting data files or data streams. This prevents unauthorized access to the data in those files, or protects the content from unauthorized interception when files or streams are transmitted from system to system. In other words, copying a file and giving it to a friend will not enable that friend to use the file if it's protected by PlayReady. To use an encrypted file or stream, users need a license. A license is granted to a client (such as a EME-enabled Web page) primarily for the for the purpose of controlling decryption and playback of the encrypted content.

Each license contains rights and restrictions that define exactly how the content may be used and under what conditions. For example, a license for a video file rental might be valid for the period between October 1, 2013 and November 1, 2013. There may be multiple licenses for a single file. A user will be able to access and use their content so long as one of the licenses grant the appropriate rights and the restrictions do not prevent access.

This topic reviews some of the basic terminology and concepts used by the Microsoft ReadyPlay technology. This terminology is used throughout this documentation set.

Topic Description

Output Protection Levels

Describes the protection levels associated with devices that support specific technologies.

Individualization

Describes the process of updating the PlayReady runtime on the client device, which allow licenses to be bound to the client device.

Revocation

Describes the process that identifies clients with compromised security and prevents them from getting access to additional licenses.

Reactive and Proactive Licenses

Describes how licenses can be provided on demand or can be obtained in advance of the media playback.

Chained Licenses

Describes how license chaining enables more efficient use of multiple licenses.

Embedded Licenses

Describes how embedding a license into content improves end-user scenarios.