Tech-invite3GPPspaceIETF RFCsSIP

Content for  TS 26.501  Word version:  18.0.0

Top   Top   Up   Prev   Next
1…   4…   4.2…   4.2.2…   4.3…   4.5…   4.6…   4.7…   5…   5.2…   5.3…   5.3.2   5.4…   5.5…   5.5.3…   5.6…   5.7…   5.7.3   5.7.4…   5.8   5.9…   5.10…   5.10.5   5.10.6   5.11…   6…   6.2…   6.3…   6.5…   6.8…   7…   8…   8.2   A…   A.3…   A.5…   A.7…   A.9   A.10   A.11   A.12   A.13   A.14   A.15   B…   B.3   C…   C.3   C.4   C.5   D…


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

5.7.1  Generalp. 58

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 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 of TS 23.502).

5.7.2  Provisioningp. 59

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)
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.

Up   Top   ToC