Content for  TS 26.501  Word version:  19.2.0

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.

The media contribution and egest procedure is as follows:

The steps are as follows: One of the following steps: or: Then: 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.

Figure 6.2.3.3-1 shows a variant of the high-level call flow for uplink media contribution and egest in clause 6.2.3.2 in which a 5GMSu AF deployed, for example, in an External DN configures Content Publishing in a 5GMSu AS deployed inside the Trusted DN. This corresponds to a collaboration scenario similar to that depicted in clause A.6 in which reference point M3u crosses the trust boundary. Differences from the baseline procedure in clause 6.2.2.3 are highlighted in boldface. In the context of the OAuth 2.0 architecture [35], the 5GMSu AS acts as resource server and the 5GMSu AF acts as client. When deployed outside the scope of the CAPIF framework [33], the 5GMSu AS may provide the authorization server functionality.

Pre-requisites:

• The endpoint address(es) of relevant 5GMSu AS instance(s), as well as the endpoint address and access credentials of the Authorization server are configured in the 5GMSu AF by the 5GMSu Application Provider as part of the onboarding procedure.

The steps are largely identical to those in clause 6.2.3.2 with differences highlighted in boldface: One of the following steps: or: Then: 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.