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…

A.13 Uplink media streaming using content preparation with AF in the trusted Data Network and AS in the external domain
...

A.13 Uplink media streaming using content preparation with AF in the trusted Data Network and AS in the external domain |R18| p. 206

In this collaboration scenario, both the 5GMSu AS and 5GMSu AF are present. The 5GMSu AS resides in the external domain. While it employs 5GMS protocol and format for uplink media reception from the 5GMSu Client (M4u), norit performs content egest to the 5GMSu Application Provider over a M2u-like (M2u') protocol and format (and therefore it is called 5GMSu-like AS). The 5GMSu AF is used to interact with the 5GMSu Application Provider at the reference point M1 for uplink media streaming provisioning System, and to interact with the Media Session Handler of the 5GMSu Client for providing Service Access Information, dynamic policy invocation and/or other uplink media streaming related functionality such as metrics reporting and network assistance). The Provisioning API (M1u') and Ingest API (M2u') may follow 5GMS specifications.

Copy of original 3GPP image for 3GPP TS 26.501, Fig. A.13-1: Uplink media streaming AF in the trusted Data Network and AS in the external domain

Figure A.13-1: Uplink media streaming AF in the trusted Data Network and AS in the external domain
(⇒ copy of original 3GPP image)

Figure A.13-2 provides a high-level call flow for this collaboration scenario.

Copy of original 3GPP image for 3GPP TS 26.501, Fig. A.13-2: Call flow for uplink media streaming using content preparation with AF in the trusted Data Network and AS in the external domain

Figure A.13-2: Call flow for uplink media streaming using content preparation with AF in the trusted Data Network and AS in the external domain
(⇒ copy of original 3GPP image)

Steps:

Step 1.

The 5GMSu Application Provider creates a Provisioning Session with its internal Provisioning function (M1u').

Step 2.

The Provisioning function requests the 5GMSu-like AS to initialise the required content preparation process instantiation (M3u').

Step 3.

The 5GMSu-like AS instantiates the content preparation process.

Step 4.

The 5GMSu-like AS acknowledges the Provisioning the instantiation of required process (M3u').

Step 5.

The Provisioning function acknowledges successful provisioning to the 5GMSu Application Provider (M1u').

Step 6.

The 5GMSu Application Provider creates a Provisioning Session for uplink streaming with the 5GMSu AF.

At some later point in time:

Step 7.

The 5GMSu Application Provider provides Service Access Information to the 5GMS-Aware Application at reference point M8u.

Step 8.

The 5GMS-Aware Application requests the 5GMSu Client to start an uplink streaming session (M6u/M7u).

Step 9.

The 5GMSu Client requests that the 5GMSu AF initialises uplink media streaming (M5u).

Alternatively:

Step 10.

The 5GMS-Aware Application requests the 5GMSu Client to start an uplink streaming session (M6u/M7u).

Step 11.

The 5GMSu Client requests Service Access Information from the 5GSMu AF at reference point M5u.

At some later point in time:

Step 12.

Uplink media streaming starts from the 5GMSu Client to the 5GMSu-like AS (M4u').

Step 13.

If content preparation was initialized in step 3, the uplinked media may be manipulated by the 5GMSu AS prior to egest.

Step 14.

Media streaming egest starts from the 5GMSu-like AS to the 5GMSu Application Provider (M2u').

Finally:

Step 15.

The 5GMSu AS releases its resources after observing a period of inactivity.