Content for TS 26.512 Word version: 18.2.1

4 Procedures for Downlink Media Streaming p. 26

4.1 General p. 26

This clause defines all procedures for Downlink Media Streaming using the different 5G Media Streaming Reference Points.

4.2 APIs relevant to downlink media streaming p. 26

Table 4.2-1 summarises the APIs used to provision and use the various downlink media streaming features specified in TS 26.501.

Table 4.2-1: Summary of APIs relevant to downlink media streaming features

5GMSd feature	Abstract	Relevant APIs
5GMSd feature	Abstract	Interface	API name	Clause
Content protocols discovery	Used by the 5GMSd Application Provider to interrogate which content ingest protocols are supported by 5GMSd AS(s).	M1d	Content Protocols Discovery API	7.5
Content hosting	Content is ingested, hosted and distributed by the 5GMSd AS according to a Content Hosting Configuration associated with a Provisioning Session.	M1d	Provisioning Sessions API	7.2
			Server Certificates Provisioning API	7.3
			Content Preparation Templates Provisioning API	7.4
			Content Hosting Provisioning API	7.6
		M2d	HTTP pull-based content ingest protocol	8.2
		M2d	DASH-IF push-based content ingest protocol	8.3
		M3d	Server Certificates configuration API	9.2
			Content Preparation Templates configuration API	9.3
			Content Hosting configuration API	9.4
		M4d	MPEG-DASH [4] or 3GP-DASH [37] or DASH-IF push-based content distribution	10
		M5d	Service Access Information API	11.2
Metrics reporting	The 5GMSd Client uploads metrics reports to the 5GMSd AF according to a provisioned Metrics Reporting Configuration it obtains from the Service Access Information for its Provisioning Session.	M1d	Provisioning Sessions API	7.2
		M1d	Metrics Reporting Provisioning API	7.8
		M5d	Service Access Information API	11.2
		M5d	Metrics Reporting API	11.4
Consumption reporting	The 5GMSd Client provides feedback reports on currently consumed content according to a provisioned Consumption Reporting Configuration it obtains from the Service Access Information for its Provisioning Session.	M1d	Provisioning Sessions API	7.2
		M1d	Consumption Reporting Provisioning API	7.7
		M5d	Service Access Information API	11.2
		M5d	Consumption Reporting API	11.3
Dynamic Policy invocation	The 5GMSd Client activates different traffic treatment policies selected from a set of Policy Templates configured in its Provisioning Session.	M1d	Provisioning Sessions API	7.2
		M1d	Policy Templates Provisioning API	7.9
		M5d	Service Access Information API	11.2
		M5d	Dynamic Policies API	11.5
Network Assistance	The 5GMSd Client requests bit rate recommendations and delivery boosts from the 5GMSd AF.	M5d	Service Access Information API	11.2
Network Assistance		M5d	Network Assistance API	11.6
Edge content processing	Edge resources are provisioned for processing content in 5GMS downlink media streaming sessions.	M1d	Provisioning Sessions API	7.2
		M1d	Edge Resources Provisioning API	7.10
		M5d	Service Access Information API	11.2
5GMS via eMBMS	The 5GMSd AF provisions the delivery of content via eMBMS and MBMS User Services.	M1d	Provisioning Sessions API	7.2
		M5d	Service Access Information API	11.2
		M4d	MPEG-DASH [4] or 3GP-DASH [37] or HLS	10
5GMS via MBS	The 5GMSd AF provisions the delivery of content via MBS User Services.	M1d	Provisioning Sessions API	7.2
		M5d	Service Access Information API	11.2
		M4d	MPEG-DASH [4] or 3GP-DASH [37] or HLS	10
5GMS via eMBMS	The 5GMSd AF provisions the delivery of content via eMBMS.	M1d	Provisioning Sessions API	7.2
		M5d	Service Access Information API	11.2
		M4d	MPEG-DASH [4] or 3GP-DASH [37] or HLS content distribution	10
UE data collection, reporting and exposure	UE data related to downlink 5G Media Streaming is reported to the Data Collection AF instantiated in the 5GMSd AF for exposure to Event consumers.	M1d	Event Data Processing Provisioning API	7.11
		R4	Ndcaf_DataReporting service	17
		R5, R6	Naf_EventExposure service	18

4.3 Procedures of the M1 (5GMS Provisioning) interface p. 27

A 5GMS Application Provider may use the procedures in this clause to provision the network for media streaming sessions that are operated by that 5GMS Application Provider. For downlink media streaming, these sessions may be DASH streaming sessions, progressive download sessions, or any other type of media streaming or distribution (e.g. HLS) sessions. For uplink media streaming, the content format and delivery protocol are defined by the 5GMSu Application Provider, and may be either non-fully standardized or employ standardized HTTP-based streaming of ISO BMFF content fragments as profiled by CMAF [39].

Reference point M1 offers three different sets of procedures:

For downlink media streaming, configuration of content ingest at reference point M2d for onward distribution by the 5GMSd AS over reference point M4d or via other distribution systems such as eMBMS or MBS. The API at this reference point is designed to offer equivalent functionality as that exposed by a public CDN. For uplink media streaming, configuration of content egest at reference point M2u for the media content received by the 5GMSu AS from the 5GMSu Client over reference point M4u. The resource types involved in content hosting configuration are provisioning session (see clause 4.3.2), content hosting procedures (see clause 4.3.3), ingest protocols (see clause 4.3.4), content preparation template (see clause 4.3.5), and server certificates (see clause 4.3.6).
Configuration of dynamic policies: allows the configuration of Policy Templates at M5 that can be applied to M4 downlink/uplink media streaming sessions.
Configuration of reporting: permits the MNO to collect, at M5, QoE metrics and consumption reports about M4 downlink sessions, as well as permits the MNO to collect, at M5, QoE metrics reports about M4 uplink sessions.

A 5GMS Application Provider may use any of these procedures, in any combination, to support its media streaming sessions.

4.3.2 Provisioning Session procedures p. 28

4.3.2.1 General p. 28

Prior to configuring content hosting, dynamic policies, or reporting, the 5GMS Application Provider shall create a new Provisioning Session in the 5GMS AF. The 5GMS Application Provider shall use the operations specified in clause 5.2.2 of TS 26.510 at reference point M1 to create and subsequently manipulate Provisioning Sessions in the 5GMS AF.

4.3.2.2 Void

4.3.2.3 Void

4.3.2.4 Void

4.3.2.5 Void

4.3.3 Content Hosting provisioning procedures p. 28

4.3.3.1 General p. 28

The 5GMSd Application Provider shall use the operations specified in clause 5.2.8 of TS 26.510 at reference point M1d when it wants to create and subsequently manipulate Content Hosting Configurations in the 5GMSd AF in order to provision the content hosting feature for downlink media streaming.

4.3.3.2 Void

4.3.3.3 Void

4.3.3.4 Void

4.3.3.5 Void

4.3.3.6 Void

4.3.3A Content Publishing provisioning procedures |R18| p. 29

4.3.3A.1 General p. 29

The 5GMSu Application Provider shall use the operations specified in clause 5.2.9 of TS 26.510 at reference point M1u when it wants to create and subsequently manipulate Content Publishing Configurations in the 5GMSu AF in order to provision the content publishing feature for uplink media streaming.

4.3.4 Content Protocols Discovery procedures p. 29

4.3.4.1 General p. 29

The 5GMS Application Provider shall use the operations specified in clause 5.2.3 of TS 26.510 at reference point M1 when it wants to discover the set of downlink content ingest or uplink content egest protocols supported by the 5GMS AS at reference point M2.

4.3.4.2 Void

4.3.4.3 Void

4.3.4.4 Void

4.3.4.5 Void

4.3.5 Content Preparation Template provisioning procedures p. 29

4.3.5.1 General p. 29

For downlink media streaming, the 5GMSd AS may be required to process content ingested at interface M2d before serving it on interface M4d. For uplink media streaming, the 5GMSu AS may be required to process content it receives from the 5GMSu Client before passing it to the 5GMSu Application Provider on the egest interface M2u.

The 5GMS Application Provider shall use the operations specified in clause 5.2.5 of TS 26.510 at reference point M1 when it wants to create and subsequently manipulate Content Preparation Templates in the 5GMS AF.

4.3.5.2 Void

4.3.5.3 Void

4.3.5.4 Void

4.3.5.5 Void

4.3.6 Server Certificate provisioning procedures p. 29

4.3.6.1 General p. 29

Each X.509 server certificate [8] presented by the 5GMSd AS at reference point M4d or at reference point xMB-U is represented by a Server Certificate resource at M1d. The 5GMS Application Provider shall use the operations specified in clause 5.2.4 of TS 26.510 at reference point M1 when it wants to create and subsequently manipulate Server Certificates in the 5GMS AF. These enable a Server Certificate resource to be created within the scope of a Provisioning Session, and subsequently referenced by a Content Hosting Configuration created in the scope of the same Provisioning Session.

4.3.6.2 Void

4.3.6.3 Void

4.3.6.4 Void

4.3.6.5 Void

4.3.6.6 Void

4.3.6.7 Void

4.3.7 Dynamic Policy provisioning procedures p. 30

4.3.7.1 General p. 30

The 5GMS Application Provider shall use the operations specified in clause 5.2.7 of TS 26.510 at reference point M1 when it wants to create and subsequently manipulate Policy Templates available for the use of downlink or uplink media streaming sessions of a particular Provisioning Session in the 5GMS AF.

4.3.7.2 Void

4.3.7.3 Void

4.3.7.4 Void

4.3.7.5 Void

4.3.8 Consumption Reporting Configuration provisioning procedures p. 31

4.3.8.1 General p. 31

The 5GMSd Application Provider shall use the interactions specified in clause 5.2.12 of TS 26.510 at reference point M1 when it wants to activate and configure consumption reporting for a Provisioning Session in the 5GMSd AF.

4.3.8.2 Void

4.3.8.3 Void

4.3.8.4 Void

4.3.8.5 Void

4.3.9 Metrics Reporting provisioning procedures p. 31

4.3.9.1 General p. 31

The 5GMS Application Provider shall use the operations specified in clause 5.2.11 of TS 26.510 at reference point M1 when it wants to configure QoE metrics reporting functionality associated with a downlink or uplink media streaming Provisioning Session in the 5GMS AF.

4.3.9.2 Void

4.3.9.3 Void

4.3.9.4 Void

4.3.9.5 Void

4.3.10 Edge Resources provisioning procedures |R17| p. 31

4.3.10.1 General p. 31

The 5GMS Application Provider shall use the operations specified in clause 5.2.6 of TS 26.510 at reference point M1 when it wants to provision edge resources for downlink or uplink media streaming associated with a Provisioning Session in the 5GMS AF.

4.3.10.2 Void

4.3.10.3 Void

4.3.10.4 Void

4.3.10.5 Void

4.3.11 Event Data Processing provisioning procedures |R17| p. 32

4.3.11.1 General p. 32

The 5GMS Application Provider shall use the operations specified in clause 5.2.13 of TS 26.510 at reference point M1 to configure the collection and processing of UE data related to 5G Media Streaming and to restrict its exposure over reference points R5 and R6 by configuring the Data Collection AF instantiated in the 5GMS AF (as defined in TS 26.531 and clause 4.7 of TS 26.501) with one or more Event Data Processing Configurations and Data Access Profiles for a particular Event ID.

Each instance of a Data Access Profile specifies a set of data processing operations to be performed by the Data Collection AF on its collected UE data in order to synthesize the event data to be exposed to a specific Event service consumer entity. In this release, eligible Event service consumer entities of 5GMS event data are the NWDAF, the Event Consumer AF and the NEF.