2.5.1 Publish Content to Media Server - Encoder

In this use case, the encoder publishes content to a media server.

Context of use: To push captured media content to a media server for distribution on the network. This use case is illustrated in the following diagram.

Use case diagram for publishing content to a media server

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

Goal: To publish content to 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.

Stakeholders

  • Internet Content Provider (ICP):

    An ICP is the primary user of the Media Streaming Server protocols. The role of an ICP is to provide high quality media to the consumer. Which protocol is used depends on the scenario that content providers are trying to achieve and the reach that the content providers are trying to have.

    The ICP initially needs to decide if the content is to be a live stream, a download, or an on-demand broadcast stream. Depending on the selection, the ICP will choose the protocol to broadcast in most appropriate to his needs.

    ICPs often extend their activities beyond streaming and incorporate Digital Rights Management (DRM) over the files or streams or create complex playlists in order to achieve their scenario goals.

  • Administrators:

    Administrators in the corporate environment are responsible for setting up the network and broadcasts. They configure clients and servers to guarantee a certain level of quality and security of the content. For example, administrators can limit the client access to the server or direct user access to the server through a proxy server. In addition, to avoid bandwidth concerns, administrators can select a protocol that multicasts rather than streams unicast in order to eliminate some network overhead.

Preconditions

  • The encoder is available on the Media Streaming Server (MSS) system network.

  • The encoder has to be configured to capture live streams or recordings.

  • When pushing content, the encoder has to have access to the media server publishing point or be able to create a publishing point on the server.

  • If the encoder is pushing to the media server, then the ports are required to be opened on the server to receive the media stream.

  • If the server is pulling from the encoder, then the ports have to be opened on the encoder. If the Windows Media HTTP Streaming Protocol (WMSP) is used, any port is possible. Generally, the server initiates an HTTP connection with the encoder through port 8080.

  • The network supports HTTP and TCP, or UDP.<2>

Main Success Scenario - Push Mode

  1. Trigger: Administrators or ICPs trigger the encoder to send the stream to media server.

  2. The encoder establishes a connection to the server.

  3. The encoder sends a push request to the media server.

  4. The encoder begins to capture content and pushes the multimedia stream to the media server.

  5. The media server receives the streamed content. Failure on the network prevents the multimedia content from reaching the media server.

Postcondition

Media content is published to the media server.

Extensions

  • DRM can be used to extend this scenario by packing the contents within a protected package as described in section 2.5.2.

Variation - Pull mode

  1. Trigger: The media server triggers the connection to the encoder to pull media content.

  2. The encoder begins to capture content.

  3. The media server connects to the encoder.

  4. The encoder and server then exchange messages that allow the server to pull the multimedia stream to the media server.