Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 26.501  Word version:  16.5.0

Top   Top   Up   Prev   Next
1…   4…   4.2…   4.3…   5…   5.2…   5.3…   5.4…   5.5…   5.6…   5.7…   5.8   5.9…   6…   6.3…   7…   A…   B…

 

5.7  Establishing a Unicast Downlink Media Streaming Session with 5GMSd AF interactions for dynamic policy updates

5.7.1  General

This clause describes the provisioning for dynamic policy invocation and the establishment of a unicast downlink streaming session using the dynamic policy API. The establishment of the unicast downlink media streaming session uses 5GMSd AF interactions, as described in Steps 4 to 8 of clause 5.1. The dynamic policy API allows separate handling of application flows within the same PDU Session. The Media Session Handler provides a Policy Template Id together with a Flow Description when requesting a dynamic policy. An example Policy Template Id value is "background_data".
The Media Session Handler provides needed information to the 5GMSd AF, so that the 5GMSd AF can combine the semi-static parameters from a Policy Template (which is associated with the Policy Template Id) with the API parameters to trigger a dynamic PCC rule update using the NEF or PCF.
The 5GMSd AF may trigger, for example, the "AF session with required QoS procedure" (see TS 23.502, clause 4.15.6.6) for updating QoS related dynamic PCC rules. For changing charging related rules, the 5GMSd AF may trigger the "Change the chargeable party during the session" procedure (see TS 23.502, clause 4.15.6.5).
Up

5.7.2  ProvisioningWord‑p. 47
The provisioning for the dynamic policy procedure follows generally the procedure from clause 5.3. Specifically, the Dynamic Policy feature is activated and, as result, the 5GMSd Application Provider is able to provision one or more Policy Templates.
The domain model of M1d and M5d APIs is depicted in Figure 5.7.2-1. Realization of the dependencies between M1d and M5d data entries are up to implementation.
[not reproduced yet]
Figure 5.7.2-1: Domain model for dynamic policies
Up
A Policy Template is identified by a Policy Template Id and contains semi-static parameters, including the API entry for the PCF/NEF interactions. The list of provisioned Policy Template Ids is communicated as valid Policy Template Ids to the Media Session Handler. The Media Session Handler uses one of the valid Policy Template Ids when invoking a dynamic policy.

5.7.3  Progressive Download of On-Demand ContentWord‑p. 48
This procedure describes the establishment of a unicast downlink media media streaming session with 5GMSd AF interactions for dynamic policy updates. A streaming session may use 3GP File Format (Progressive Download), 3GP Timed Text or other (potentially non-3GPP defined) formats.
[not reproduced yet]
Figure 5.7-1: High Level Procedure for progressive download for on-demand media
Up
Prerequisites:
  • 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 Access Information contains detailed information for the policy related interactions. Specifically, the information includes URL(s) for the 5GMSd AF, an identifier of the 5GMS 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 TS 23.503, clause 6.1.3.22). The PCF is configured with the corresponding QoS parameters and charging information.
Steps:
Step 1.
The 5GMSd-Aware Application triggers the Service Announcement and Content Discovery procedure. 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.
Step 2.
A Media Player Entry is selected.
Step 3.
The 5GMSd-Aware Application triggers the Media Session Handler to start media playback. The Media Player Entry is provided to the Media Session Handler.
Step 4.
When the 5GMSd-Aware Application has received 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.
Step 5.
The Media Session Handler triggers the Media Player to start the session.
Step 6.
The Media Player establishes the transport session, e.g. a TCP connection.
Step 7.
The Media Player notifies the Media Session Handler about the Flow description(s) of the transport session established in the previous step (see TS 23.502), e.g. the 5-tuple.
Step 8.
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 Flow description(s) and the Policy Template identifier (see Table 5.7.4-1) to be applied to the described transport session. The 5GMSd AF uses the Policy Template indication for the related procedure and to identify the related network function.
Step 9.
This step applies when the 5GMSd AF resides in the trusted Data Network. Depending on the Policy Template, the step is executed either:
  1. When the Policy Template relates to QoS, the 5GMSd AF may either directly interact with the PCF or may use a NEF service:
    • when directly interacting with the PCF, the 5GMSd AF uses the Npcf_PolicyAuthorization Service as defined in TS 23.502, clause 5.2.5.3).
    • when interacting via the NEF with the PCF, continue at step 10a.
  2. When the Policy Template relates to a different charging scheme, the 5GMSd AF may either directly interact with the PCF or may use a NEF service:
    • when directly interacting with the PCF, the 5GMSd AF uses the Npcf_PolicyAuthorization Service as defined in TS 23.502, clause 5.2.5.3).
    • when interacting via the NEF with the PCF, continue at step 10b.
Step 10.
This step applies when the 5GMSd AF resides in the external Data Network. Depending on the Policy Template, the step is executed either:
  1. When the Policy Template relates to QoS, the 5GMSd AF may use the Nnef_AFsessionWithQoS service as defined in TS 23.502, clause 5.2.6.9. (The complete call flow is described in TS 23.502, clause 4.15.6.6.)
  2. When the Policy Template relates to a different charging scheme, the 5GMSd AF may use the Nnef_ChargeableParty service as defined in TS 23.502, clause 5.2.6.8. (The complete call flow is described in TS 23.502, clause 4.15.6.4 and clause 4.15.6.5.) 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.
Step 11.
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.
Step 12.
The Media Session Handler notifies the Media Player according to the response from the 5GMSd AF (see Table 5.6.4-2).
Step 13.
The Media Player sends the request for the progressive download content.
Step 14.
The Media Player receives the initialization information of the progressive download content. The initialization information contains configuration parameters for reception of the media, and optionally also DRM information.
Step 15.
The Media Player configures the rendering pipeline for media playback.
Step 16.
The Media Player notifies the Media Session Handler, providing the transport session information and some media content related information.
Step 17.
Optional: Media Player acquires a DRM License from as the 5GMSd Application Provider.
Step 18.
The Media Player receives media content and puts it into the rendering pipeline.
Step 19.
The Media Player continues to receive and play back the media content.
Up

5.7.4  DASH StreamingWord‑p. 51
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.
[not reproduced yet]
Figure 5.7-2: High Level Procedure for DASH content
Up
Prerequisites:
  • 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 TS 23.503, clause 6.1.3.22). The PCF is configured with the corresponding QoS parameters and charging information.
Steps:
Step 1.
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.
Step 2.
A media content item is selected.
Step 3.
The 5GMSd-Aware Application triggers the Media Session Handler to start media playback. The Media Player Entry is provided to the Media Session Handler.
Step 4.
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.
Step 5.
The Media Session Handler triggers the Media Player to start the session.
Step 6.
The Media Player establishes a transport session for acquiring the MPD referenced by the Media Player Entry.
Step 7.
The Media Player requests the MPD.
Step 8.
The Media Player receives the MPD.
Step 9.
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.
Step 10.
The Media Player notifies the Media Session Handler about the MPD. The notification may contain parameters from the MPD.
Step 11.
(Optional) the Media Player acquires the necessary DRM information, for example a DRM License.
Step 12.
The Media Player configures the media rendering pipeline.
Step 13.
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.
Step 14.
The Media Session Handler is notified about the established transport session(s) for the content by providing the description of the application flows e.g. 5-tuples.
Step 15.
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 Flow description(s) and the Policy Template identifier (see Table 5.7.4-1), to be applied to the described transport session. The 5GMSd AF uses the Policy Template for the related procedure and to identify the related network function.
Step 16.
This step applies when the 5GMSd AF resides in the trusted Data Network. Depending on the Policy Template, the step is executed either:
  1. When the Policy Template relates to QoS, the 5GMSd AF may either directly interact with the PCF or may use a NEF service:
    • when directly interacting with the PCF, the 5GMSd AF uses the Npcf_PolicyAuthorization Service as defined in TS 23.502, clause 5.2.5.3).
    • when interacting via the NEF with the PCF, continue at step 17a.
  2. When the Policy Template relates to a different charging scheme, the 5GMSd AF may either directly interact with the PCF or may use a NEF service:
    • when directly interacting with the PCF, the 5GMSd AF uses the Npcf_PolicyAuthorization Service as defined in TS 23.502, clause 5.2.5.3).
    • when interacting via the NEF with the PCF, continue at step 17b.
Step 17.
This step applies when the 5GMSd AF resides in the external Data Network. Depending on the Policy Template, the step is executed either:
  1. When the Policy Template relates to QoS, the 5GMSd AF may use the Nnef_AFsessionWithQoS service as defined in TS 23.502, clause 5.2.6.9. (The complete call flow is described in TS 23.502, clause 4.15.6.6.)
  2. When the Policy Template relates to a different charging scheme, the 5GMSd AF may use the Nnef_ChargeableParty service as defined in TS 23.502, clause 5.2.6.8. (The complete call flow is described in TS 23.502, clause 4.15.6.4 and clause 4.15.6.5.) 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.
Step 18.
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.
Step 19.
The Media Session Handler updates the configuration of the Media Player according to the response from the 5GMSd AF (See Table 5.6.4-2).
Step 20.
The Media Player requests a DASH initialization segment. The Media Player repeats this step for each required initialization segment.
Step 21.
The Media Player receives the initialization segments.
Step 22.
The Media Player requests DASH media segments according to the MPD.
Step 23.
The Media Player receives media segments and feeds them into the appropriate media rendering pipeline.
Step 24.
Previous steps are repeated according to the MPD information.
Up

5.7.5  Parameters for dynamic policy invocation configurationWord‑p. 53
Parameters
Description

Status
Status of a dynamic policy. A dynamic policy has the status granted or rejected.
The status of a policy may change while the streaming session is active.
Policy Enforcement
Information about the policy enforcement system.


Up   Top   ToC