26.5013GPP5G Media Streaming (5GMS)General description and architectureRelease 18TS
Before streaming media data in the uplink direction, a set of parameters are provisioned at the 5GMSu AF/AS and at the 5GMSu Client. On the 5GMSu AF/AS, the M1u API is used for session provisioning. On the UE side, the M8u or M5u API is used for provisioning.
6.2.2 Provisioning session for uplink streaming
126.96.36.199 Domain model
The M1u baseline domain model is depicted in figure 188.8.131.52-1 overleaf. It consists of a Provisioning Session, which contains at least one of the following:
– A Content Publishing Configuration,
– A Policy Template,
– One or more Content Preparation Templates,
– An Edge Resources Configuration specifying the requirements for edge processing as defined in TS 23.548  and TS 23.558  in support of the Provisioning Session, including eligibility criteria that indicate the circumstances in which edge computing is to be used for Media Streaming sessions associated with this Provisioning Session and parameters indicating the tolerance of the application for relocation of the Edge AS, or
Each Provisioning Session is uniquely identified within the 5GMS System by a Provisioning Session identifier.
When a certain 5GMS feature (such as content publishing configuration, policy template, content preparation template or edge resource configuration) is selected, the 5GMSu AF compiles the resulting Service Access Information that the 5GMSu Client needs to have to access the services via M5u.
Figure 184.108.40.206-1: M1u provisioning domain model
220.127.116.11 Baseline provisioning procedure
This clause describes the baseline procedure to provision the features using the 5GMS System.
NOTE 1: SLA negotiations between the 5GMSu Application Provider and the 5GMS System provider are outside the scope of the present specification and are included in the figure below for illustrative purposes only.
Figure 18.104.22.168-1: High Level Procedure for provisioning the 5GMS System for uplink streaming sessions
1. The 5GMSu Application Provider authenticates itself with the system. This procedure reuses existing authentication/authorization procedures, e.g. as defined for CAPIF .
2. The 5GMSu Application Provider creates a Provisioning Session, providing its 5GMSu Application Provider identifier as input. 5GMSu Application Provider queries the capabilities and authorized features.
3. The 5GMSuApplication Provider specifies one or more 5GMSu features in the Provisioning Session. A set of authorized features is activated, such as content dynamic policy; network assistance; and content publishing (including egest).
When the content publishing feature is offered and selected, the 5GMS Application Provider configures the content publishing behaviour of the 5GMSu AS, including selecting the uplink ingest protocol and format, content preparation and egest protocol and format.
When the dynamic policy feature is offered and selected, the 5GMSu Application Provider specifies a set of policies which can be invoked for the uplink streaming session. The UE becomes aware of the selected policies in the form of a list of valid Policy Template Ids.
When the edge computing feature is offered and selected, the 5GMSu Application Provider provides one or more Edge Resources Configurations that can be used to support either client-driven management or Application Provider-driven management of edge resources associated with the Provisioning Session.
4. When content publication is desired, the 5GMSu AF interacts with the 5GMSu AS to allocate resources for M2u egest protocol and format. Then the 5GMSu AS responds to the 5GMSu AF with the M2u content egest address.
5. The 5GMSu AF compiles the Service Access Information. The Service Access Information contains access details and options such as the Provisioning Session identifier, M5u (Media Session Handling) addresses for uplink entry point, dynamic policy, network assistance, etc.
6. The 5GMSu AF provides the results to the 5GMSu Application Provider.
The following steps:
7. When the 5GMSu Application Provider has selected full Service Access Information, the results are provided in the form of addresses and configurations for M2u (content egest), M5u (Media Session Handling) and M4u (Media Uplink Streaming). The 5GMSu Application Provider provides a subset of this information to the 5GMSu-Aware Application through M8u.
8. When the 5GMSu-Aware Application decides to activate the streaming service transmission, the Service Access Information is provided to the 5GMSu Client.
9. The 5GMSu Client requests the 5GMSu AF to initialise uplink media streaming (M5u), including reservation of any resources required for content preparation.
10. The 5GMS-Aware Application requests the 5GMSu Client to start an uplink streaming session (M6u/M7u).
11. When the 5GMSu Application Provider has delegated Service Access Information handling to the 5GMS System, a reference to the Service Access Information (e.g. an URL) is provided. The Media Session Handler fetches the full Service Access Information later from the 5GMSu AF.
12. The 5GMSu Client streams the content to the 5GMSu AS.
13. When content publishing is offered and has been selected in step 4, the 5GMSu Application Provider can start retrieving the content from the M2u egest interface.
14. The 5GMSu Application Provider may update the Provisioning Session.
According to schedule, or upon request by the 5GMSu-Aware Application:
15. The 5GMSu Application Provider may manually terminate the Provisioning Session (at any time). All associated resources are released. Content may be removed from the 5GMSu AS. The 5GMSd Application Provider may configure a schedule for Provisioning Session termination.
16. The 5GMSu AF sends a notification to the 5GMSu Client upon Provisioning Session termination.
The 5GMSu AF may request the creation or reuse of one or more network slices for ingesting the content of the provisioned session. If more than one network slice is provisioned for the ingest of the content of a session, the list of allowed S‑NSSAIs shall be conveyed to the target UE (e.g. through URSP or through M8u, step 7, or M5u, step 10).
NOTE 2: The 5GMSu AS receiving the content is only accessible through the DNN(s) used by the network slice(s) provisioned for the distribution of that content.
6.2.3 Content Publishing Configuration for Uplink Streaming
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.
22.214.171.124 Media egest procedure
The media egest procedure is as follows:
Figure 6.2.3-1: Media egest procedure
The steps are as follows:
1: Initialization: the 5GMSu Application Provider discovers the M1u endpoint address and authenticates itself with the 5GMSu AF.
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).
3: Provision 5GMSu AS instance(s): The 5GMSu AF configures the related 5GMSu AS instance(s) for a particular Content Publishing Configuration. This step may involve instructing the 5GMSu AS to establish one or more content preparation processes. The 5GMSu AS(s) responds whether the configuration was successful or not.
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:
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.
6: The 5GMSu Client acquires the uplink entry point as part of Service Access Information through reference point M5u.
7: The 5GMSu-Aware Application requests the 5GMSu Client to start the uplink streaming.
8: The 5GMSu Client starts uplink streaming of the content to the 5GMSu AS via reference point M4u.
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.
NOTE: Pulling media content from the 5GMSu AS may be triggered by a request from the 5MGSu Client through M8u.
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.