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.2.3 Content Publishing Configuration for uplink streaming 6.2.3.1 General 6.2.3.2 Media egest procedure
...

6.2.3 Content Publishing Configuration for uplink streaming p. 161

6.2.3.1 General |R18| p. 161

The 5G Media Streaming architecture defines a reference point (M1u) for provisioning which offers the procedures to configure content egest for uplink media streaming over a 5GMS System. Once a Provisioning Session is established using the API at reference point M1u, content publishing may be configured. Content can then be uplink streamed by the Media Streamer in the 5GMSu Client to the 5GMSu AS through reference point M4u. The uploaded (and possibly processed) content is accessible via reference point M2u for egest.

Reference point M2u supports the egest of the following types of content:

Live streaming content.
On-demand streaming content. i.e. the content that previously streamed from the UE to 5GMSu AS and is stored in 5GMSu AS.
Static files such as images, scene descriptions, etc. associated with the uplink streaming content.

The 5GMSu AF provides an API at reference point M1u that allows a 5GMSu Application Provider to create/update/delete a Content Publishing Configuration. A Content Publishing Configuration contains all the parameters for a particular content ingest uplink and egest setup, and optionally references one or more Content Preparation Templates.

6.2.3.2 Media egest procedure |R18| p. 162

The media egest procedure is as follows:

Copy of original 3GPP image for 3GPP TS 26.501, Fig. 6.2.3-1: Media egest procedure

Figure 6.2.3-1: Media egest procedure
(⇒ copy of original 3GPP image)

The steps are as follows:

Step 1.

Initialization: the 5GMSu Application Provider discovers the M1u endpoint address and authenticates itself with the 5GMSu AF.

Step 2.

Create Content Publishing Configuration: the 5GMSu Application Provider creates a new Content Publishing Configuration through the 5GMSu AF. The configuration specifies path, protocol, entry point, the egest push/pull mode, and possibly one or more content preparation templates. Upon successful configuration, the 5GMSu AF responds with a Content Publishing Configuration identifier, and the location of the 5GMSu AS from which to pull the content (if using the pull mode).

Step 3.

Provision 5GMSu AS instance(s): The 5GMSu AF configures the related 5GMSu AS instance(s) for a particular Content Publishing Configuration via reference point M3u. This step may involve instructing the 5GMSu AS to establish one or more content preparation processes declared in Content Preparation Templates. The 5GMSu AS(s) responds whether the configuration was successful or not.

Step 4.

Confirm provisioning: Upon successful provisioning, the 5GMSu AF responds with a Content Publishing Configuration identifier, and the location of the 5GMSu AS from which to pull the content (if using the pull mode).

One of the following steps:

Step 5.

Provide the uplink entry point: The 5GMSu Application Provider publishes the uplink entry point to the 5GMSu-Aware Application through reference point M8u to enable it to begin uplink streaming to the 5GMSu AS.

or:

Step 6.

The 5GMSu Client acquires the uplink entry point as part of Service Access Information through reference point M5u.

Step 7.

The 5GMSu-Aware Application requests the 5GMSu Client to start the uplink streaming.

Step 8.

The 5GMSu Client starts uplink streaming of the content to the 5GMSu AS via reference point M4u.

Step 9.

Media egest: The 5GMSu Application Provider may start pulling or receiving content (if using push mode) from the 5GMSu AS. The 5GMSu AS performs the requested content preparation prior to making the uplink content ready for being pulled by or pushed to the 5GMSu Application Provider.

The 5GMSu Application Provider may update a Content Publishing Configuration subsequently to modify some of its parameters. The subset of parameters that can be updated may be limited by the 5GMSu AF.