5.4 Content Hosting Configuration for Downlink Media Streaming

26.5013GPP5G Media Streaming (5GMS)General description and architectureRelease 18TS

5.4.1 General

The 5G Media Streaming architecture defines an interface (M2d) for provisioning which offers the procedures to configure content ingest for downlink media streaming over 5G. Once a Provisioning Session is established using the API at interface M1d, content hosting can be configured. The control part of the ingest interface may be performed through the NEF. Ingested content is accessible from the 5GMSd AS at interface M4d through a new location identifier.

The M2d interface supports the ingest of the following types of content:

– Live streaming content.

– On-demand streaming content.

– Static files such as images, scene descriptions, etc.

The 5GMSd AF provides an API at interface M1d that allows a 5GMSd Application Provider to create/update/delete an Content Hosting Configuration. A Content Hosting configuration contains all the parameters for a particular content ingest and distribution setup.

NOTE: In the current version of the present document, the M2d ingest interface only supports Unicast downlink streaming.

5.4.2 Media ingest procedure

The media ingest procedure is as follows:

Figure 5.4-1: Media Ingest procedure

The steps are as follows:

1: Initialization: the 5GMSd Application Provider discovers the entry point and authenticates itself with the 5GMSd AF.

2: Create Content Hosting Configuration: the 5GMSd Application Provider creates a new Content Hosting Configuration for its content through the 5GMSd AF. The configuration specifies a domain name, supplies a certificate for HTTPS access to the content, sets the caching rules per media type, indicates the distribution area (e.g. through geofencing), distribution protocol, the desired content preparation, URL signing, etc. Upon successful configuration, the 5GMSd AF responds with a Content Hosting Configuration identifier, and the location of the 5GMSd AS to which to send the content (if using the push mode).

3: Provision 5GMSd AS(s): The 5GMSd AF configures the related 5GMSd AS(s) to prepare for media ingest for that particular Content Hosting Configuration. This step may involve instructing the 5GMSd AS(s) to set appropriate caching rules, to perform URL signature validation and to limit access through geofencing. The 5GMSd AS(s) will respond whether the configuration is successful or not.

4: Confirm configuration information: The 5GMSd AF communicates the Content Hosting Configuration of the 5GMSd AS(s) back to the 5GMSd Application Provider for further media push or pull.

5: Publish Media Player Entry: The 5GMSd Application Provider shall then publish the Media Player Entry to the 5GMSd-Aware Application to enable access to the content.

6: Media ingest: The 5GMSd AS(s) may start pulling or receiving content (if using push mode) from the 5GMSd Application Provider. The 5GMSd AS performs the requested content preparation prior to providing access to the content.

NOTE: Pull of media content from the external 5GMSd AS(s) may be triggered by a request from the 5MGSd Client.

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