2.5.2 Publish Secure Content to Media Server - Encoder

In this use case, the encoder encapsulates the media content by using a Digital Rights Management (DRM) packager to publish it to the media server.

Context of use: To publish secure content to the media server by using a DRM packager to encapsulate the content. This use case is illustrated in the following diagram.

Figure 9: Use case diagram for publishing secure content to a media server

Goal: To publish secure content to the media server.

Actors

• Encoder

  The encoder is the primary actor. It is an application for converting both live and prerecorded audio and video content to digitized media format.

• Media Server

  The media server is the supporting actor. It is the server that receives media from an encoder and streams it to the media player clients. The media server can act as an origin server or a distribution server.

• DRM packager

  The DRM packager is the supporting actor. It is a tool that is used to package media files that conform to the Advanced Systems Format (ASF) specification in an encrypted file format. When an ASF file is packaged, a DRM-specific section is added to the ASF file header containing business usage and distribution rules.

Stakeholders

• Internet Content Provider (ICP)

• Administrators

Preconditions

The encoder already has the license key seed, certificate values, and signing keys as described in [MSDN-LPS-WME].

Main Success Scenario

1. Trigger: Administrators instruct the encoder to protect the streaming content.

2. The encoder requests encryption for the stream that it is going to capture.

3. The DRM packager encrypts the stream.

4. The media server receives the encrypted content. Media files that are encrypted cannot be decrypted unless the client has a certificate, (as specified [MS-DRM] section 2.2.3.2.7), that assigns it rights to decrypt the content.

Postcondition

Secure media content is published to the media server.

Extensions

None.