Content for TS 26.501 Word version: 18.6.0

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…

6.4 Termination of an uplink Media Streaming session 6.5 Providing 5GMSu AF-based Network Assistance 6.6 Providing Remote Control 6.7 RAN Signalling based Support for Uplink Network Assistance
...

6.4 Termination of an uplink Media Streaming session p. 167

The procedure defines the termination of an uplink media streaming session.

Copy of original 3GPP image for 3GPP TS 26.501, Fig. 6.4-1: Uplink streaming session teardown

Figure 6.4-1: Uplink streaming session teardown
(⇒ copy of original 3GPP image)

Steps:

Step 1.

An uplink media streaming session is active and should be terminated.

Step 2.

The 5GMSu-Aware Application sends a Stop command to the 5GMSu Client.

Step 3.

The 5GMSu Client stops the capturing process.

Step 4.

The uplink transport session is released.

When client assistance was established:

Step 5.

The 5GMSu AF is notified that the uplink media streaming session is terminated.

When server assistance was established:

Step 6.

The 5GMSu AS is notified the 5GMSu AF that the uplink media streaming session is terminated.

6.5 Providing 5GMSu AF-based Network Assistance p. 168

The procedure a 5GMSu Client uses to obtain network assistance from a 5GMSu AF is defined in Figure 6.5-1 below.

Copy of original 3GPP image for 3GPP TS 26.501, Fig. 6.5-1: Providing 5GMSu AF-based Network Assistance

Figure 6.5-1: Providing 5GMSu AF-based Network Assistance
(⇒ copy of original 3GPP image)

Steps:

Step 1.

An uplink streaming session is active. A Network Assistance Session is established with the 5GMSu AF.

Step 2.

The Media Session Handler in the 5GMSu Client requests assistance information from the 5GMSu AF.

Step 2a.

The 5GMSu AF interacts with the PCF (or, if the AF is deployed outside the Trusted DN, with the PCF via the NEF) to obtain the requested assistance information.

Step 3.

The assistance information is returned to the Media Session Handler in the 5GMSu Client.

Step 4.

The Media Streamer in the 5GMSu Client takes an appropriate action based on the information received.

6.6 Providing Remote Control p. 169

The procedure defines the remote control from a Remote Controller through the 5GMSu-Aware Application.

Copy of original 3GPP image for 3GPP TS 26.501, Fig. 6.6-1: High-level procedure for remote control of a 5GMS uplink streaming session

Figure 6.6-1: High-level procedure for remote control of a 5GMS uplink streaming session
(⇒ copy of original 3GPP image)

Steps:

Step 1.

The 5GMSu Application Provider creates a Provisioning Session at reference point M1u, providing its 5GMSu Application Provider identifier as input. 5GMSu Application Provider queries the capabilities and authorized features.

Step 2.

The 5GMSu Application Provider requests Content Publish Configuration provisioning at reference point M1u.

Step 3.

The 5GMSu AF interacts with the 5GMSu AS at reference point M3u to allocate resources for the M2u egest protocol and format. Then the 5GMSu AS responds with the M2u address.

Step 4.

The 5GMSu AF compiles the Service Access Information. The Service Access Information contains access details and options such as the Provisioning Session identifier, and M5u (Media Session Handling) address for an uplink entry point.

Step 5.

The 5GMSu AF provides the results of the provisioning request (step 1) to the 5GMSu Application Provider via reference point M1u.

When the 5GMSu Application Provider has selected full-Service Access Information, the results are provided in the form of addresses and configurations for M2u (egest), M5u (Media Session Handling), M4u (Media Uplink Streaming).
When the 5GMSu Application Provider has delegated the Service Access Information handling to the 5GMS System, then a reference to the Service Access Information (e.g. an URL) is provided. The Media Session Handler fetches the full-Service Access Information later from the 5GMSu AF.

Step 6.

The 5GMSu-Aware Application, the 5GMSu Application Provider and the third party Remote Controller negotiate the communication protocol and the command dictionary for remote control, and reach an agreement (if any).

Step 7.

The 5GMSu Application Provider announces the uplink streaming service to the 5GMSu-Aware Application at reference point M8u (during the lifetime of the Provisioning Session).

Step 8.

The 5GMSu Application Provider sends the remote control information to the Remote Controller.

Step 9.

The Remote Controller sends a remote control command to the 5GMSu-Aware Application using the protocol negotiated in step 6.

Step 10.

Based on the received the remote control command, the 5GMSu-Aware Application sends a corresponding request to the 5GMSu Client.

Step 11.

The 5GMSu Client takes the required action based on the received request.

Step 12.

The 5GMSu Client acknowledges execution of the received request to the 5GMSu-Aware Application, including the results (if any).

Step 13.

The 5GMSu-Aware Application acknowledges execution of the remote control command to the Remote Controller, including the results (if any).

6.7 RAN Signalling based Support for Uplink Network Assistance p. 170

Figure 6.7-1 depicts an uplink streaming architecture where RAN signalling is employed to support uplink Network Assistance functionality.

The RAN in the architecture contains control plane and user plane entities that interact with peer control and user plane entities in the UE, in the request/response for uplink bit rate recommendations, or boost of the uplink streaming data rate, and subsequent media transport. The user plane functionality as shown in Figure 6.7-1 (solid line going from UE to RAN to 5GMSu AS) illustrates the scheduling/passthrough functionality associated with user plane communications, governed by the RAN, as result of the uplink assistance messaging over the control plane (shown by dotted line between the UE and RAN). It is assumed in this case that 5GMSu AF-based Network Assistance is not utilized.

It should be noted that although the 5GMSu AF is not utilized when RAN signalling based network assistance is performed, it is assumed that there is a higher-level network entity which coordinates and tracks network assistance performed using RAN signalling versus application signalling for individual UEs.

Copy of original 3GPP image for 3GPP TS 26.501, Fig. 6.7-1: RAN Signalling based Uplink Network Assistance

Figure 6.7-1: RAN Signalling based Uplink Network Assistance
(⇒ copy of original 3GPP image)