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.14 Uplink media streaming using content preparation with AF and AS in the external domain
...

A.14 Uplink media streaming using content preparation with AF and AS in the external domain |R18| p. 208

In this collaboration scenario, both the 5GMSu AS and 5GMSu AF are present and follow 3GPP specifications. Both the 5GMSu AS and 5GMSu AF reside in the external DN/domain. The Provisioning API (M1u') and Ingest API (M2u') may follow 5GMS specifications.

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

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

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

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

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

Steps:

Step 1.

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

Step 2.

The 5GMSu Application Provider creates a Content Publishing Configuration as part of the Provisioning Session that defines the instructions for content egest (M1u').

Step 3.

The 5GMSu AF, based on the received publishing configuration, requests the 5GMSu AS to confirm the availability of content resources for egest (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 requests that the 5GMSu AF initialises the content preparation process (M1u').

Step 6.

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

Step 7.

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

Step 8.

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

Step 9.

The 5GMSu AF acknowledges the initialisation of the cotent preparation process (M1u').

Step 10.

The 5GMSu Application Provider provides Service Access Information to the 5GMS-Aware Application (M8).

Step 11.

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

Step 12.

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

Alternatively:

Step 13.

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

Step 14.

The 5GMSu Client requests Service Access Information from the 5GSMu AF (M5u).

Step 15.

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

Step 16.

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

Step 17.

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

Step 18.

The 5GMSMu AF provides Service Access Information to the 5GMSu Client (M5u).

Then:

Step 19.

Uplink media streaming starts from the 5GMSu Client to the 5GMSu AS via reference point M4u.

Step 20.

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

Step 21.

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

Finally:

Step 22.

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