10 Media Streaming (M4) APIs

26.5123GPP5G Media Streaming (5GMS)ProtocolsRelease 17TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

10.1 General

This clause deals with the interface and APIs for media streaming for different distribution formats and protocols. TS 26.511 [35] defines the integration of several media codecs into 5G Media Streaming,and provides requirements and recommendations for the support of these media profiles in specific 5G Media Streaming profiles. However, 5GMS is not restricted to the media profiles defined in TS 26.511 [35]. Any CMAF media profile may be used and distributed within 5G Media Streaming as long as it can be used with APIs and interfaces defined in this specification.

10.2 DASH Distribution

In the case of DASH distribution, M4d is relevant for the distribution as shown in figure 10.2-1.

Figure 10.2-1: M4d usage for DASH distribution

For DASH-based distribution according to TS 26.247 [4] and ISO/IEC 23009-1 [32], two main formats are of relevance:

1) The Media Presentation Description (MPD) that is processed in the DASH Access Client.

2) The Segment formats that are passed through the DASH Access Client and processed in the Media Playback and Content Decryption Platform. Note that the DASH Access Client may parse Segments to extract for example Inband Events or producer reference times.

Other resources may be referenced in the MPD, for example DRM related information.

The Segment formats for DASH Streaming in the context of 5G Media Streaming are defined in TS 26.511 [35] based on the CMAF encapsulation. The DASH Access Client downloads the Segments from the 5GMSd AS based on the instructions in the MPD and the instructions from the 5GMSd-Aware Application through M7d (see clause 13 for details).

The interface between the DASH Access Client and the Media Playback and Content Decryption Platform as well as the 5GMSd Client requirements for media codecs are documented in TS 26.511 [35].

The following requirements apply for M4d:

1) The Media Presentation Description (MPD) and Segments shall conform to an MPD according to ISO/IEC 23009-1 [32] or TS 26.247 [4].

2) The Segment formats should conform to CMAF addressable resources as well as to the requirements in TS 26.511 [35].

3) The Media Presentation should conform to the 5G Media Streaming DASH Interoperability Point as defined in clause 7.3.11 of TS 26.247 [4].

A 5GMSd Client shall support the 5G Media Streaming DASH Interoperability Point as defined in TS 26.247 [4], clause 7.3.11. A 5GMSd Client may support additional DASH profiles and interoperability points.

The MPD may contain a one or several ServiceDescription elements that include operational parameters. The MPD may also include multiple configurations for the media (different codecs, different content protection, different resolutions, etc.), for example for playback under different operating policies. The handling of this information is documented in clause 13.2.