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…

A.8 Downlink media streaming with AFs deployed in two separate trusted Data Networks sharing AS in an external Data Network A.9 Downlink media streaming with both AF and AS deployed in external Data Network and AS delivering content through two trusted Data Networks (OTT) A.10 Uplink media streaming using content preparation with both AF and AS deployed in the trusted Data Network
...

A.8 Downlink media streaming with AFs deployed in two separate trusted Data Networks sharing AS in an external Data Network p. 239

The collaboration scenario shown in Figure A.8-1 represents a multi-MNO distribution scenario where an external CDN (5GMSd AS) is used to deliver content through multiple 5GMSd capable PLMNs. Additional 5GMSd features are used from the serving 5GMS System which need interactions with the PCF of the serving PLMN. The Provisioning API (M1d') and Ingest API (M2d') may follow 5GMS specifications.

Copy of original 3GPP image for 3GPP TS 26.501, Fig. A.8-1: Downlink media streaming with AFs in two trusted Data Networks sharing AS in external Data Network

Figure A.8-1: Downlink media streaming with AFs in two trusted Data Networks sharing AS in external Data Network
(⇒ copy of original 3GPP image)

A.9 Downlink media streaming with both AF and AS deployed in external Data Network and AS delivering content through two trusted Data Networks (OTT) p. 239

This collaboration scenario shown in Figure A.9-1 represents a multi-MNO distribution scenario where an external CDN (5GMSd AS) is used to deliver content through multiple 5GMSd-capable PLMNs. Additional 5GMSd features are used from the serving 5GMSd system which need interactions with the NEF of the serving PLMN. The Provisioning API (M1d') and Ingest API (M2d') may follow 5GMS specifications.

Copy of original 3GPP image for 3GPP TS 26.501, Fig. A.9-1: Downlink media streaming with AF and AS in external Data Network delivering through two trusted Data Networks (OTT)

Figure A.9-1: Downlink media streaming with AF and AS in external Data Network delivering through two trusted Data Networks (OTT)
(⇒ copy of original 3GPP image)

A.10 Uplink media streaming using content preparation with both AF and AS deployed in the trusted Data Network |R18| p. 240

In this collaboration scenario shown in Figure A.10-1, both the 5GMSu AS and 5GMSu reside in the trusted Data Network. Additionally, reference point M2u is used for content egest to the external 5GMSu Application Provider.

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

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

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

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

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

Steps:

Step 1.

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

Step 2.

The 5GMSu Application Provider requests the 5GMSu AF to create one Content Publishing Configuration that defines the instructions for content egest (M1u).

Step 3.

The 5GMSu AF, based on the received Content Publishing Configuration, requests the 5GMSu AS to confirm the availability of content resources for content preparation (M3u).

Step 4.

The 5GMSu AF acknowledges the successful creation of the Content Publishing Configuration to the 5GMSu Application Provider (M1u).

At some later point in time:

Step 5.

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

Step 6.

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

Step 7.

The 5GMSu Client requests that the 5GMSu AF initialises uplink media streaming, including any content preparation required by the Content Publishing Configuration (M5u).

Alternatively:

Step 8.

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

Step 9.

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

As a consequence:

Step 10.

The 5GMSd AF requests initialisation of the content preparation process by the 5GMSd AS (M3u).

Step 11.

The 5GMSd AS initialises the content preparation process, if it is not already running.

Step 12.

The 5GMSd AF acknowledges the initialisation of the content preparation process (M3u).

Then:

Step 13.

The 5GMSu Client performs media session handling for the uplink streaming session (M5u).

Step 14.

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

Step 15.

If content preparation was successfully initialized at step 11 or before, the uplinked media may be manipulated by the 5GMSu AS prior to egest.

Step 16.

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

Finally:

Step 17.

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