Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 26.501  Word version:  18.6.0

Top   Top   Up   Prev   Next
1…   4…   4.0.6…   4.1…   4.2…   4.2.2…   4.3…   4.4   4.5…   4.6…   4.7…   4.7.4…   4.8   4.9…   4.10…   5…   5.2…   5.2.4   5.2.5…   5.3…   5.3.2…   5.4…   5.5…   5.6…   5.7…   5.7.4…   5.7.8   5.8…   5.10…   5.10.5…   5.10.6…   5.11…   5.12…   5.12.4…   5.12.5…   6…   6.2…   6.2.2.2…   6.2.3…   6.3…   6.4…   6.8…   6.9…   6.9.5…   6.9.7   7…   8…   9…   A…   A.4…   A.8   A.9   A.10   A.11   A.12   A.13   A.14   A.15…   A.15.3…   B…   B.3   C…   C.3   C.4   C.5   D…   E… 
5.7 Establishing a Unicast Downlink Media Streaming Session with 5GMSd AF interactions for dynamic policy updates  5.7.1 General  5.7.2 Provisioning  5.7.3 Progressive Download of On-Demand Content 
...

 

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

5.7.1  General  p. 103

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 Service Data Flows within the same PDU Session. The Media Session Handler provides a Policy Template Id together with Service Data Flow Descriptions 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 clause 4.15.6.6 of TS 23.502) 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 clause 4.15.6.5 of TS 23.502).
Up

5.7.2  Provisioning  p. 104

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.
Copy of original 3GPP image for 3GPP TS 26.501, Fig. 5.7.2-1: Domain model for dynamic policies
Figure 5.7.2-1: Domain model for dynamic policies
(⇒ copy of original 3GPP image)
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 Content  p. 105

This procedure describes the establishment of a unicast downlink 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.
Copy of original 3GPP image for 3GPP TS 26.501, Fig. 5.7-1: High Level Procedure for progressive download for on-demand media
Figure 5.7-1: High Level Procedure for progressive download for on-demand media
(⇒ copy of original 3GPP image)
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 clause 6.1.3.22 of TS 23.503). 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 Service Data Flow Description(s) of the transport session established in the previous step (see TS 23.502), as defined in the Service Access Information. This can be for example 5-tuples.
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 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 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 clause 5.2.5.3 of TS 23.502).
    • 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 clause 5.2.5.3 of TS 23.502).
    • 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 clause 5.2.6.9 of TS 23.502. (The complete call flow is described in clause 4.15.6.6 of TS 23.502.)
  2. When the Policy Template relates to a different charging scheme, the 5GMSd AF may use the Nnef_ChargeableParty service as defined in clause 5.2.6.8 of TS 23.502. (The complete call flow is described in clause 4.15.6.4 and clause 4.15.6.5 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.
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 such as the enforcement method and enforcement bit rate.
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

Up   Top   ToC