Tech-invite3GPPspaceIETFspace
idxwho21222324252627282931323334353637384‑5x

Content for  TS 26.501  Word version:  18.0.0

Top   Top   Up   Prev   Next
1…   4…   4.2…   4.2.2…   4.3…   4.5…   4.6…   4.7…   5…   5.2…   5.3…   5.3.2   5.4…   5.5…   5.5.3…   5.6…   5.7…   5.7.3   5.7.4…   5.8   5.9…   5.10…   5.10.5   5.10.6   5.11…   6…   6.2…   6.3…   6.5…   6.8…   7…   8…   8.2   A…   A.3…   A.5…   A.7…   A.9   A.10   A.11   A.12   A.13   A.14   A.15   B…   B.3   C…   C.3   C.4   C.5   D…

 

A.11  Uplink media streaming using content preparation (media plane only) with both AF and AS deployed in the trusted Data Network |R18|p. 118

This uplink collaboration scenario pertains to a media plane only collaboration for which the 5GMSu AS is deployed in the trusted Data Network. Here, the 5GMS System is assumed to offer uplink streaming capabilities as a service to an external 5GMSu Application Provider. This collaboration scenario is analogous to the scenario in clause A.2 in terms of the use of M8u (as opposed to M8d in clause A.2) for the delivery of Service Access Information from the 5GMSu Application Provider to the 5GMSu Client via the 5GMSu Aware Application, and the reporting of UE application data from the 5GMSu Aware Application to the 5GMSu Application Provider.
Copy of original 3GPP image for 3GPP TS 26.501, Fig. A.11-1: Uplink media streaming (media plane only) with AF and AS in the trusted Data Network
Up
Figure A.11-2 provides a high-level call flow for this collaboration scenario.
Copy of original 3GPP image for 3GPP TS 26.501, Fig. A.11-2: Uplink media streaming using content preparation (media plane only) with AF and AS in the trusted Data Network
Up
Steps:
Step 1.
The 5GMSu Application Provider creates a Provisioning Session for uplink streaming with the 5GMSu AF.
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 Content Publishing Configuration, requests the 5GMSu AS to instantiate the content preparation process (M3u).
Step 4.
The 5GMSu AS initialises the content preparation process.
Step 5.
The 5GMSu AS acknowledges the initialisation of the required process (M3u).
Step 6.
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 7.
The 5GMSu Application Provider optionally provides Service Access Information to the 5GMS-Aware Application (M8).
Step 8.
The 5GMS-Aware Application requests the 5GMSu Client to start an uplink streaming session (M6u/M7u).
Step 9.
Uplink media streaming starts from the 5GMSu Client to the 5GMSu AS (M4u).
Step 10.
If content preparation was initialized in step 4, the uplinked media may be manipulated by the 5GMSu AS prior to egest.
Step 11.
Media streaming egest starts from the 5GMSu AS to the 5GMSu Application Provider (M2u).
Finally:
Step 12.
The 5GMSu AS releases its resources after observing a period of inactivity.
Up

Up   Top   ToC