It is assumed here that the key information to initialize the media decoding and rendering pipeline is present in the Media Player Entry (or referenced by the Media Player Entry). The intention is to provide the client with information to setup the media decoding and rendering pipeline in such a way that no pipeline reset is needed during the session. Implementations need to consider that parts of the information are provided with the initialization segments.
It is assumed that the client is enabled to use the same media decoding and rendering pipeline during the session.
The 5GMSd Application Provider has provisioned the 5G Media Streaming System and has set up content ingest.
The 5GMSd-Aware Application has received the service announcement from the 5GMSd Application Provider.
The Service Announcement Information contains detailed information for the policy related interactions. Specifically, the information includes URLs for the 5GMSd AF, an identifier of the Provisioning Session and a list of authorized Policy Type indications for that specific application.
The 5GMSd Application Provider has agreed an SLA with the Network Operator defining the possible QoS levels and their charging rates (see clause 22.214.171.124 of TS 23.503). The PCF is configured with the corresponding QoS parameters and charging information.
The 5GMSd-Aware Application triggers the Service Announcement and Content Discovery procedure. The Content Discovery procedure only involves the App 5GMSd-Aware Application and the 5GMSd Application Provider. The Service Announcement includes either the whole Service Access Information (i.e. details for Media Session Handling (M5d) and for Media Streaming access (M4d)) or a reference to the Service Access Information. The configuration parameters are listed in Table 5.7.4-1.
When the 5GMS-Aware Application has received only a reference to the Service Access Information (see step 1), the Media Session Handler interacts with the 5GMSd AF to acquire the whole Service Access Information.
The Media Player processes the MPD. It determines, for example, the number of needed transport sessions for media acquisition. The Media Player should be able to use the MPD information to initialize the media pipelines for each media stream. The MPD should also contain information to start the DRM client initialization, when DRM is used.
The Media Player establishes the necessary transport session(s) for acquiring the content. For example, the Media Player may establish one transport session for each media component (audio, video, etc) and possibly additional transport sessions for other media representations.
The Media Session Handler is notified about the established transport session(s) for the content by providing the Service Data Flow Description of the application flows as defined in the Service Access Information. This can be for example 5-tuples.
The Media Session Handler requests that a dynamic policy be applied to the media session. The request includes at least the Provisioning Session identifier, the Service Data Flow Description(s) and the Policy Template identifier (see Table 5.7.4-1), to be applied to the described transport session. In some cases, a QoS specification is also provided, containing desired QoS information. The 5GMSd AF uses the Policy Template for the related procedure and to identify the related network function.
When the Policy Template relates to a different charging scheme, the 5GMSd AF may use the Nnef_ChargeableParty service as defined in clause 126.96.36.199 of TS 23.502. (The complete call flow is described in clause 188.8.131.52 and clause 184.108.40.206 of TS 23.502.) The Policy Template may contain the Sponsor Information (values, based on SLA negotiation) and Background Data Transfer Reference ID. The Flow Description is provided by the Media Session Handler at API invocation.
The Media Session Handler queries the status of the dynamic policy invocation. The response contains status information (policy accepted, rejected, etc) and information on policy enforcement such as the enforcement method and enforcement bit rate.