School of Specs 23.501v20.2.0

3GPP 23.501 v20.2.0 — the document's own text

5.37.2 Policy control enhancements to support multi-modal services

Taught in 23. Very fast, very reliable, very picky (The 5G system architecture, in depth).

A multi-modal service is a communication service that consists of several data flows that relate to each other and that are subject to application coordination. The data flows can transfer different types of data (for example audio, video, positioning, haptic data) and may come from different sources (e.g. a single UE, a single device or multiple devices connected to the single UE, or multiple UEs).

NOTE 1: The term "data flow" used in this clause describes a service data flow from the perspective of the AF.

For the single UE case, it is expected that those data flows are closely related and require strong application coordination for the proper execution of the multi-modal application and therefore, all those data flows are transmitted in a single PDU Session.

The Nnef_AFsessionWithQoS service allows the AF to provide a Multi-modal Service ID and at the same time, for each data flow that belongs to the multi-modal service, the QoS information and service requirements and the QoS monitoring requirements. The Multi-modal Service ID is an explicit indication that data flows are related to a multi-modal service. The PCF uses the AF provided information to derive the correct PCC rules and to apply appropriate QoS policies and QoS Monitoring policies for the data flows that are part of a specific multi-modal application as described in clause 6.1.3.27.3 of TS 23.503 [45]

NOTE 2: In order to start the QoS monitoring for the data flows associated to a multi-modal service within a certain period of time, the PCF needs to receive the QoS monitoring requirements for those data flows from AF within a single request or, in case of multiple requests, within a short period of time.

If the AF provides a Multi-modal Service ID for data flows to 5GS, then the PCF may include it, based on operator configuration, in PCC rules, and the SMF forwards it to NG-RAN in N2 SM information when establishing and/or updating the corresponding QoS Flows.

NOTE 3: Based on an SLA between the network operator and an application service provider, the Multi-modal Service ID can uniquely identify a specific multi-modal communication service instance. The related 5GS behaviour is not further specified in this specification and is assumed to be determined by the operator configuration related to the SLA.

In addition to the features that are provided for the case that the data flows are associated with a single UE, the following features are provided for the case where the data flows are associated with more than one UE:

  • The same DNN/S-NSSAI combination for the multi-modal service should be selected by each of the involved UEs. The URSP Rule evaluation framework is used to ensure that the same DNN/S-NSSAI is selected.
  • The AF should use the same Multi-modal Service ID in the interactions with the PCF(s) for all the involved UEs that relate to a multi-modal service. The PCF may take this information into account (e.g. to apply a specific QoS policy) when processing each AF request independently. The data flows contribute to the service experience, but are still valid stand-alone, as they are transmitted over separate PDU Sessions to/from the involved UEs.
  • If multiple PCFs are involved, the PCFs take policy decisions according to the input provided by the AF. There is no support for policy coordination among the multiple PCFs in this Release of the specification. Policy decisions are taken by each PCF separately on a per PDU Session basis.