Content for TS 26.501 Word version: 19.2.0

1… 4… 4.1… 4.2… 4.3… 4.4 4.5… 4.6… 4.7… 4.8 4.9… 4.10… 4.11… 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.7.9… 5.8… 5.10… 5.10.3 5.10.4 5.10.5… 5.10.6… 5.10.7 5.11… 5.12… 5.12.3 5.12.4… 5.12.5… 5.13… 5.14… 6… 6.2… 6.2.2.2… 6.2.3… 6.3… 6.4… 6.8… 6.9… 6.9.5… 6.9.7 6.9.8… 7… 8… 8.2 9… A… A.4… A.8… A.11… A.13… A.15… A.16… B… C… D… E… F… G… G.2… G.3… H…

5.13 In-band client data reporting 5.13.1 Scenario 5.13.2 Procedure
...

5.13 In-band client data reporting |R19| p. 176

5.13.1 Scenario p. 176

In the considered scenario, client data is reported in band with media requests at reference point M4d. Client data is initially sent to the 5GMSd AS via reference point M4d, and from there provided to the 5GMSd AF using the QoE metrics reporting mechanism at reference point M3d. The call flow is aligned with QoE metrics collection and reporting as defined in clause 5.5.

5.13.2 Procedure p. 177

Figure 5.13.2-1 illustrates a scenario where client data collection and in-band reporting by the 5GMSd AS is configured by the 5GMSd AF via reference point M3d. In this example, it is assumed that the client data collection information provided by the 5GMSd AF comprises instructions/rules regarding client data reporting. It is further assumed that the 5GMSd AF is required to expose client data events to separate destination entities, upon optionally having performed post-processing on the collected report information. The 5GMSd AF and 5GMSd AS may be either trusted or untrusted.

Copy of original 3GPP image for 3GPP TS 26.501, Fig. 5.13.2-1: Client data collection in 5GMSd reported in band via M4d and M3d

Figure 5.13.2-1: Client data collection in 5GMSd reported in band via M4d and M3d
(⇒ copy of original 3GPP image)

The message sequence steps are described below. Extensions to the basic 5G Media Streaming call flow are highlighted in bold:

Step 1.

The 5GMS System is provisioned to collect, report and expose client data to interested event consumers.

Step 1a.

The 5GMSd AF is provisioned at reference point M1d with in-band client data reporting configuration information pertaining to client data collection by the Media Player and reporting of it to the 5GMSd AF via the 5GMSd AS. This includes different client data collection, in-band reporting and data processing instructions regarding required post-processing functionality and subsequent exposure of processed client data to the 5GMSd Application Provider and/or to the NWDAF.

Step 1b.

The 5GMSd AF configures the Data Collection AF instantiated inside it to receive client data reports from the 5GMSd AS and to make the client data available for exposure to event consumers.

Step 1c.

The 5GMSd AF also configures the 5GMSd AS to extract client data from media requests at reference point M4d and report it to the 5GMSd AF via reference point M3d.

Step 1d.

The 5GMSd Application Provider subscribes to receive events containing client data information.

Step 1e.

The NWDAF may also subscribe to receive events containing client data information.

Step 2.

The 5GMSd-Aware Application triggers the Service Announcement and Content Discovery procedure at reference point M8d. The Service Announcement may include the whole Service Access Information that includes a client data collection and in-band reporting configuration to be used by the Media Player.

Time passes until the 5GMSd Client initiates session establishment and media playback.

Step 3.

Streaming Session and media playback is established.

Step 3a.

The 5GMSd-Aware Application informs the Media Player of impending media playback by invoking a suitable method at reference point M7d.

Step 3b.

The Media Player requests the establishment of a streaming session by invoking a suitable method at reference point M11d on the Media Session Handler, which acknowledges the request.

Step 3c.

The Media Session Handler requests may acquire whole Service Access Information from the 5GMSd AF via reference point M5d if did not already receive this in step 2 above.

Step 3d.

The Media Session Handler informs the Media Player about the successful set-up of the streaming session by means of a suitable notification at reference point M11d.

Step 3e.

The media playback pipeline is set up between the Media Player, the 5GMSd AS at reference point M4d and with the 5GMSd Application Provider at reference point M2d.

Step 4.

Using a suitable interaction at reference point M11d, the Media Session Handler interrogates the Media Player at reference point M11d on its capability to perform client data collection and in-band reporting at reference point M4d and instructs the player to enable client data collection and in-band reporting, including a session identifier. In response the Media Player acknowledges its support for the collection of the required client data.

During the course of media playback, steps 6a to 6f below may be repeated, depending on the duration of the playback.

Step 5a.

The Media Player requests media content from the 5GMSd AS via reference point M4d and includes configured client data in the request according to the configuration obtained in step 4 above.

Step 5b.

The 5GMSd AS extracts and processes client data from this request.

Step 5c.

In the case of a live streaming service, media content may have already been published by the 5GMSd Application Provider to the 5GMSd AS at reference point M2d. However, in this case it is considered that the 5GMSd AS ingests media from the 5GMSd Application Provider in pull mode. The 5GMSd AS checks if the requested data is already cached and if not, requests the data from the upstream 5GMSd Application Provider. The 5GMSd AS may also use information in the client data to request future segments in advance of a request at reference point M4d.

Step 5d.

The 5GMSd AS delivers the requested media data to the Media Player at reference point M4d.

Step 5e.

The Media Player starts playback and informs the Media Session Handler by means of a suitable notification at reference point M11d.

Step 5f.

The 5GMSd AS reports the requested client data to the 5GMSd AF via reference point M3d.

Step 5g.

The 5GMSd AF extracts the relevant client data from the report and processes it.

Step 5h.

Based on reported client data the 5GMSd AF may decide to communicate with the 5G System to initiate media handling functions such as Network Assistance.

In parallel with the media streaming session, the client data received by the 5GMSd AF is prepared for exposure:

Step 6a.

In accordance with its in-band client data reporting configuration as provisioned in step 1, the 5GMSd AF performs separate post-processing in accordance with the received types of client data reports.

Step 6b.

The client data is shared with the Data Collection AF instantiated in the 5GMSd AF.

Step 6c.

The Data Collection AF instantiated in the 5GMSd AF exposes an event containing processed client data to the 5GMSd Application Provider at reference point R6 in accordance with the Event Data Processing Configuration provisioned in step 1.

Step 6d.

The Data Collection AF instantiated in the 5GMSd AF may expose an event containing processed client data to the NWDAF at reference point R6 in accordance with the Event Data Processing Configuration provisioned in step 1.