This clause defines the requirements in terms of decapsulation and decryption of media for a 5GMSd Media Player in combination with codecs. Media Encapsulation in 5G Media Streaming for downlink is defined based on the MPEG Common Media Application Format (CMAF) [7]. Based on this, this clause documents the requirements and recommendations for the support of media profiles by the definition of media player requirements.

If the 5GMSd Client supports the reception of video, then the following applies:

• the AVC-HD playback requirements as defined in clause 4.2.1.3.1.4 shall be supported.
• the HEVC-HD playback requirements as defined in clause 4.2.2.3.1.4 should be supported.

If the 5GMSd Client supports the reception of video and HD-HDR Capabilities, then the following applies:

• the AVC-FullHD playback requirements as defined in clause 4.2.1.3.2.4 shall be supported.
• the HEVC-FullHD playback requirements as defined in clause 4.2.2.3.2.4 shall be supported.
• the HEVC-UHD playback requirements as defined in clause 4.2.2.3.3.4 may be supported.

If the 5GMSd Client supports the reception of speech, then the following shall be supported:

• the EVS playback requirements as defined in clause 7.4.2.4 of TS 26.117.

If the 5GMSd Client supports the reception of speech, then the following should be supported:

• the AMR-WB playback requirements as defined in clause 7.3.2.4 of TS 26.117.

If the 5GMSd Client supports the reception of speech, then the following may be supported:

• the AMR playback requirements as defined in clause 7.2.2.4 of TS 26.117.

If the 5GMSd Client supports the reception of audio, then the following should be supported:

• the eAAC+ stereo playback requirements as defined in clause 7.6.2.4 of TS 26.117.

If the 5GMSd Client supports the reception of audio, then the following may be supported:

• the AMR-WB+ playback requirements as defined in clause 7.7.2.4 of TS 26.117.

If the 5GMSd Client supports the reception of subtitle, then the following should be supported:

• the IMSC1.1 text track playback requirements as defined in clause 4.5.1.5.

If the 5GMSd Client supports encrypted content and any of the video playback requirement as defined in clause 5.2.7.2, then the 5GMSd Client shall support the playback requirements for encrypted content as documented in clause 8 of CTA-WAVE 5003 [9], clause 8.12 for either:

• video content encrypted according to [7] clause 8, using the 'cenc' AES-CTR subsample pattern encryption scheme, as specified in [8], clause 10.1; or
• video content encrypted according to [7] clause 8, using the 'cbcs' AES-CBC subsample pattern encryption scheme, as specified in [8], clause 10.4, with the following restrictions Pattern Block length of 10 and an encrypt:skip pattern of 1:9 as defined in clause 9.6 of [8].

If the 5GMSd Client supports decrypted content and any of the video playback requirement in clause 5.2.7.2, then the 5GMSd Client should support the playback requirements for encrypted content as documented in clause 8 of CTA-WAVE 5003 [9], clause 8.12 for both:

• video content encrypted according to [7] clause 8, using the 'cenc' AES-CTR subsample pattern encryption scheme, as specified in [8], clause 10.1; and
• video content encrypted according to [7] clause 8, using the 'cbcs' AES-CBC subsample pattern encryption scheme, as specified in [8], clause 10.4, with the following restrictions Pattern Block length of 10 and an encrypt:skip pattern of 1:9 as defined in clause 9.6 of [8].

If the 5GMSd Client supports encrypted content and any of the speech and audio playback requirement in clause 5.2.7.3 and clause 5.2.7.4, then the 5GMSd Client shall support the playback requirements for encrypted content as documented in clause 8 of CTA-WAVE 5003 [9], clause 8.12 for either:

• audio content encrypted according to [7] clause 8, using the 'cenc' AES-CTR subsample pattern encryption scheme, as specified in [8], clause 10.1; or
• audio content encrypted according to [7] clause 8, using the 'cbc1' AES-CBC subsample pattern encryption scheme, as specified in [8], clause 9.7.

If the 5GMSd Client supports encrypted content and any of the speech and audio playback requirement in clause 5.2.7.3 and clause 5.2.7.4, then the 5GMSd Client should support the playback requirements for encrypted content as documented in clause 8 of CTA-WAVE 5003 [9], clause 8.12 for both:

• audio content encrypted according to [7] clause 8, using the 'cenc' AES-CTR subsample pattern encryption scheme, as specified in [8], clause 10.1; and
• audio content encrypted according to [7] clause 8, using the 'cbc1' AES-CBC subsample pattern encryption scheme, as specified in [8], clause 9.7.

Any subtitle track, if present, should not be encrypted.

A 5GMSd Client is expected to support capability discovery such that 5GMS-Aware Applications can identify if a specific media profile is supported. In order to identify whether a media profile is supported, the 5GMSd Client may provide an API as defined in TS 26.512 via the M7d interface, for which the client can be queried with a specific MIME type string, if the media profile is supported. The MIME types follow RFC 6381. A 5GMSd Client should support at least one of the following capability discovery mechanisms for media profiles:

• If isTypeSupported() for the media profile with argument <profiles> results in a yes, then the respective media profile is supported with the requirements defined in a specific clause.
• If isTypeSupported() for the media profile with argument <codecs> results in a yes, then the respective media profile is supported with the requirements defined in a specific clause.
• If a conforming CMAF header is provided for playback initialization and the 5GMSd Client does not throw an error response, then the respective media profile is supported with the requirements defined in a specific clause.

For each media profile mentioned in clause 5.2.6, the <profiles> parameter and the <codecs> parameter are provided in the following. These parameters should be used in the capability exchange.

For AVC-HD:

• the <profiles> parameter is compatible with video/mp4 profiles='cmfc'
• the <codecs> parameter is compatible with either 'avc1.640028' or 'avc3.640028'

For AVC-FullHD:

• the <profiles> parameter is compatible with video/mp4 profiles='cmfc'
• the <codecs> parameter is compatible with either 'avc1.640029' or 'avc3.640029'

For AVC-UHD:

• the <profiles> parameter is compatible with video/mp4 profiles='cmfc'
• the <codecs> parameter is compatible with either 'avc1.640028' or 'avc3.640028'

For HEVC-HD:

• the <profiles> parameter is compatible with video/mp4 profiles='cmfc'
• the <codecs> parameter is compatible with either 'hvc1.1.2.L93.B0' or 'hev1.1.2.L93.B0'

For HEVC-FullHD:

• the <profiles> parameter is compatible with video/mp4 profiles='cmfc'
• the <codecs> parameter is compatible with either 'hvc1.2.4.L123.B0' or 'hev1.2.4.L123.B0'

For HEVC-UHD:

• the <profiles> parameter is compatible with video/mp4 profiles='cmfc'
• the <codecs> parameter is compatible with either 'hvc1.2.4.L153.B0' or 'hev1.2.4.L153.B0'

For AMR:

• the <profiles> parameter is defined in clause 7.2.2.4 of TS 26.117 as audio/mp4 profiles='camr'
• the <codecss> parameter is defined in clause 7.2.2.4 of TS 26.117 as 'samr'

For AMR-WB:

• the <profiles> parameter is defined in clause 7.3.2.4 of TS 26.117 as audio/mp4 profiles='camw'
• the <codecs> parameter is defined in clause 7.3.2.4 of TS 26.117 as 'samw'

For EVS:

• the <profiles> parameter is defined in clause 7.4.2.4 of TS 26.117 as audio/mp4 profiles='cevs'
• the <codecs> parameter is defined in clause 7.4.2.4 of TS 26.117 as 'sevs'

For eAAC+ stereo:

• the <profiles> parameter is defined in clause 7.6.2.4 of TS 26.117 as audio/mp4 profiles='ceac'
• the <codecs> parameter is defined in clause 7.6.2.4 of TS 26.117 as 'mp4a'

For AMR-WB+:

• the <profiles> parameter is defined in clause 7.7.2.4 of TS 26.117 as audio/mp4 profiles='camp'
• the <codecs> parameter is defined in clause 7.7.2.4 of TS 26.117 as 'sawp'

For IMSC1.1 Text Tracks:

• the <profiles> parameter is defined in ISO/IEC 23000-19 [7], clause 11.3.3 as application/mp4 profiles='im2t';
• the <codecs> parameter is defined in ISO/IEC 23000-19 [7], clause 11.3.3 as 'stpp.ttml.im2t'.

Encryption mode discovery will be studied in due course.

This clause defines the requirements in terms of encapsulation of media for a 5GMSu Media Streamer in combination with codecs. Media Encapsulation in 5G Media Streaming for uplink is defined based on the MPEG Common Media Application Format (CMAF) [7]. Based on this, this clause documents the requirements and recommendations for the support of media profiles by the definition of media streamer requirements.

If the 5GMS UE supports the streaming of video, then the following shall be supported:

• the content generation requirements for the HEVC-FullHD Media Profile as defined in clause 4.2.2.3.2.5;
• the sender requirements for the HEVC-FullHD Operation Point as defined in clause 5.3.2.

If the 5GMSu Client supports the transmission of speech, then the following shall be supported:

• the EVS content generation requirements as defined in clause 7.4.2.5 of TS 26.117.

If the 5GMSu Client supports the transmission of speech, then the following should be supported:

• the AMR-WB content generation requirements as defined in clause 7.3.2.5 of TS 26.117.

If the 5GMSu Client supports the transmission of speech, then the following may be supported:

• the AMR content generation requirements as defined in clause 7.2.2.5 of TS 26.117.

If the 5GMSu Client supports the transmission of audio, then the following should be supported:

• the eAAC+ stereo content generation requirements as defined in clause 7.6.2.5 of TS 26.117.

If the 5GMSd Client supports the Television (TV) profile, it shall support the H.264/AVC 720p HD Operation Point Receiver requirements as specified in clause 4.4.2.6 of TS 26.116. If the 5GMSd Client supports the Television (TV) profile, it should support the H.264/AVC Full HD Operation Point Receiver requirements as specified in clause 4.4.3.6 of TS 26.116.

If the 5GMSd Client supports the Television (TV) profile, it should support:

• H.265/HEVC 720p HD Operation Point Receiver requirements as specified in clause 4.5.2.7 of TS 26.116;
• H.265/HEVC Full HD Operation Point Receiver requirements as specified in clause 4.5.3.7 of TS 26.116;
• H.265/HEVC UHD Operation Point Receiver requirements as specified in clause 4.5.4.7 of TS 26.116;
• H.265/HEVC Full HD HDR Operation Point Receiver requirements as specified in clause 4.5.5.8 of TS 26.116;
• H.265/HEVC UHD HDR Operation Point Receiver requirements as specified in clause 4.5.6.8 of TS 26.116;
• H.265/HEVC Full HD HDR HLG Operation Point Receiver requirements as specified in clause 4.5.7.7 of TS 26.116; and
• H.265/HEVC UHD HDR HLG Operation Point Receiver requirements as specified in clause 4.5.8.7 of TS 26.116.

If the 5GMSd Client supports the Television (TV) profile, it may support:

• H.265/HEVC 8K UHD HDR Operation Point Receiver requirements as specified in clause 4.5.9.8 of TS 26.116.

If the 5GMSd Client supports the Television (TV) profile and HD-HDR capabilities, it shall support:

• H.265/HEVC Full HD Operation Point Receiver requirements as specified in clause 4.5.3.7 of TS 26.116.

This clause defines the requirements in terms of decapsulation and decryption of media for a Television (TV) Profile Media Player in combination with codecs. Media Encapsulation in 5G Media Streaming for downlink is defined based on the MPEG Common Media Application Format (CMAF) [7]. However, TS 26.116 defines file format encapsulation and DASH Mapping in clause 5. This clause addresses decapsulation and decryption requirements in a sense that a 5GMSd Client supporting the Television (TV) profile requires to be able to process content that conforms to TS 26.116 encapsulation and CMAF encapsulation. The CMAF Track and Switching Set constraints in the present document and the Representation and Adaptation Set constraints in TS 26.116 are considered almost identical, but it still needs to be checked in detail. In the absence of both, it is expected that content offered for TV Profile receivers conform with both specifications.

If the 5GMSd Client supports the Television (TV) profile, then the following applies:

• the AVC-HD playback requirements as defined in clause 4.2.1.3.1.4 and the H.264/AVC 720p HD Operation Point Receiver requirements as specified in clause 4.4.2.6 of TS 26.116 shall be supported.
• the AVC-FullHD playback requirements as defined in clause 4.2.1.3.1.4 and the H.264/AVC Full HD Operation Point Receiver requirements as specified in clause 4.4.3.6 of TS 26.116 should be supported.
• the HEVC-HD playback requirements as defined in clause 4.2.2.3.1.4 and the H.265/HEVC 720p HD Operation Point Receiver requirements as specified in clause 4.5.2.7 of TS 26.116 should be supported.
• the HEVC-FullHD playback requirements as defined in clause 4.2.2.3.2.4 and the H.265/HEVC Full HD Operation Point Receiver requirements as specified in clause 4.5.3.7 of TS 26.116 should be supported.
• the HEVC-FullHD playback requirements as defined in clause 4.2.2.3.2.4 and the H.265/HEVC Full HD HDR Operation Point Receiver requirements as specified in clause 4.5.5.7 of TS 26.116 should be supported.
• the HEVC-FullHD playback requirements as defined in clause 4.2.2.3.2.4 and the H.265/HEVC Full HD HLG Operation Point Receiver requirements as specified in clause 4.5.7.7 of TS 26.116 should be supported.
• the HEVC-UHD playback requirements as defined in clause 4.2.2.3.3.4 and the H.265/HEVC UHD Operation Point Receiver requirements as specified in clause 4.5.4.7 of TS 26.116 may be supported.
• the HEVC-UHD playback requirements as defined in clause 4.2.2.3.3.4 and the H.265/HEVC UHD HDR Operation Point Receiver requirements as specified in clause 4.5.5.7 of TS 26.116 may be supported.
• the HEVC-UHD playback requirements as defined in clause 4.2.2.3.3.4 and the H.265/HEVC UHD HLG Operation Point Receiver requirements as specified in clause 4.5.8.7 of TS 26.116 may be supported.
• the HEVC-8K playback requirements as defined in clause 4.2.2.3.4.4 and H.265/HEVC 8K UHD HDR Operation Point Receiver requirements as specified in clause 4.5.9.8 of TS 26.116 may be supported.

If the 5GMSd Client supports the Television (TV) profile and HD-HDR capabilities, then the following applies:

• the HEVC-FullHD playback requirements as defined in clause 4.2.2.3.2.4 and the H.265/HEVC Full HD Operation Point Receiver requirements as specified in clause 4.5.3.7 of TS 26.116 shall be supported.
• the HEVC-FullHD playback requirements as defined in clause 4.2.2.3.2.4 and the H.265/HEVC Full HD HDR Operation Point Receiver requirements as specified in clause 4.5.5.7 of TS 26.116 shall be supported.
• the HEVC-FullHD playback requirements as defined in clause 4.2.2.3.2.4 and the H.265/HEVC Full HD HLG Operation Point Receiver requirements as specified in clause 4.5.7.7 of TS 26.116 shall be supported.
• the HEVC-UHD playback requirements as defined in clause 4.2.2.3.3.4 and the H.265/HEVC UHD Operation Point Receiver requirements as specified in clause 4.5.4.7 of TS 26.116 may be supported.
• the HEVC-UHD playback requirements as defined in clause 4.2.2.3.3.4 and the H.265/HEVC UHD HDR Operation Point Receiver requirements as specified in clause 4.5.5.7 of TS 26.116 may be supported.
• the HEVC-UHD playback requirements as defined in clause 4.2.2.3.3.4 and the H.265/HEVC UHD HLG Operation Point Receiver requirements as specified in clause 4.5.8.7 of TS 26.116 may be supported.
• the HEVC-8K playback requirements as defined in clause 4.2.2.3.4.4 and H.265/HEVC 8K UHD HDR Operation Point Receiver requirements as specified in clause 4.5.9.8 of TS 26.116 may be supported.

If the 5GMSd Client supports the Television (TV) profile, then the following should be supported:

• the eAAC+ stereo playback requirements as defined in clause 7.6.2.4 of TS 26.117.

If the 5GMSd Client supports the Television (TV) profile, then the following should be supported:

• the IMSC1.1 text track playback requirements as defined in clause 4.5.1.5.

If the 5GMSd Client supports the Television (TV) profile the same requirements apply as in clause 5.2.7.6 for the default profile.

If the 5GMS UE supports 360 VR video, it shall include a receiver that complies with:

• the Basic H.264/AVC Operation Point Receiver requirements as specified in clause 5.1.4 of TS 26.118.

If the 5GMS UE supports 360 VR video, it should include a receiver that complies with:

• the Main H.265/HEVC Operation Point Receiver requirements as specified in clause 5.1.5 of TS 26.118.

If the 5GMS UE supports 360 VR video, it may include a receiver that complies with:

• the Flexible H.265/HEVC Operation Point Receiver requirements as specified in clause 5.1.6 of TS 26.118.

If the 5GMS UE supports 360 VR video, it may include a receiver that complies with:

• the H.265/HEVC 8K Operation Point Receiver requirements as specified in clause 5.1.7 of TS 26.118 and the HEVC-8K-Dec decoding capabilities as defined in clause 4.2.2.1.

If the 5GMS UE supports 360 VR video for DASH services, it shall include a receiver that complies with:

• the Basic Video Media Profile Receiver requirements for DASH as specified in clause 5.2.2.3 of TS 26.118.

If the 5GMS UE supports 360 VR video for DASH services, it should include a receiver that complies with:

• the Main Video Media Profile Receiver requirements for DASH as specified in clause 5.2.3.3 of TS 26.118.

If the 5GMS UE supports 360 VR video for DASH services, it may include a receiver that complies with:

• the Advanced Video Media Profile Receiver requirements for DASH as specified in clause 5.2.4.3 of TS 26.118.

If the 5GMS UE supports 360 VR video, it may include a receiver that complies with:

• the 8K Media Profile Receiver requirements for DASH as specified in TS 26.118, clause 5.2.3.5 and the HEVC-8K playback requirements as defined in clause 4.2.2.3.4.4.

If the 5GMS UE supports 3D/VR audio, it should include a receiver that complies with:

• the 3GPP MPEG-H Audio Operation Point Receiver requirements as specified in clause 6.1.4 of TS 26.118.

If the 5GMS UE supports 3D/VR audio for DASH services, it should include a receiver that complies with:

• the OMAF 3D Audio Baseline Media Profile Receiver requirements for file format signalling and encapsulation as specified in clause 6.2.2.3 of TS 26.118.

If the 5GMS UE supports 360 VR video, it shall include an encoder that can encode a bitstream at a minimum of 1080p resolution 60 fps that can be decoded by a receiver that complies with:

• the Basic H.264/AVC Operation Point Receiver requirements as specified in clause 5.1.4 of TS 26.118.

If the 5GMS UE supports 360 VR video, it should include an encoder that can encode a bitstream at a minimum of 2160p resolution 60 fps that can be decoded by a receiver that complies with:

• the Main H.265/HEVC Operation Point Receiver requirements as specified in clause 5.1.5 of TS 26.118.

If the 5GMS UE supports 360 VR video, it may include an encoder that can encode a bitstream at a minimum of 2160p resolution 60 fps that can be decoded by a receiver that complies with:

• the Flexible H.265/HEVC Operation Point Receiver requirements as specified in clause 5.1.6 of TS 26.118.

Media Encapsulation in 5G Media Streaming for uplink is defined based on the MPEG Common Media Application Format (CMAF) [7]. A sender shall at least support the generation of CMAF tracks.

If the 5GMS UE supports 3D/VR audio, it should include an encoder that can encode a bitstream that can be decoded by a receiver that complies with:

• the 3GPP MPEG-H Audio Operation Point Receiver requirements as specified in clause 6.1.4 of TS 26.118.

Media Encapsulation in 5G Media Streaming for uplink is defined based on the MPEG Common Media Application Format (CMAF) [7]. A sender shall at least support the generation of CMAF tracks.