Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 26.511  Word version:  16.1.0

Top   Top   Up   Prev   None
1…   3A…   4…   5…

 

5  5GMS Profiles

5.1  Introduction

A 5GMS profile describes a set of capability requirements associated to a service scenario. A default profile is defined for minimum media requirements to be supported in case no other profile is claimed to be supported. The Television (TV) profile covers live and on demand streaming of audio-visual services. The 360 Virtual Reality (VR) profile covers the live and on demand streaming of 360 content.

5.2  Downlink streaming default profile

5.2.1  Introduction

This profile defines selected UE-based 5GMS Client functionalities as defined in TS 26.501 and shown in Figure 4.2.2-1 in TS 26.501. The following functions are defined in this clause:
  • Media Decapsulation
  • Media Decryption
  • Media Decoding
  • Media Presentation and Rendering

5.2.2  Video decodingWord‑p. 22
If the 5GMS client supports the reception of video, then
  • AVC-HD-Dec decoding capability shall be supported as defined in clause 4.2.1.1.
  • HEVC-HD-Dec decoding capability should be supported as defined in clause 4.2.2.1.
If the 5GMS client supports the reception of video and HD-HDR capabilities, then:
  • AVC-FullHD-Dec decoding capability shall be supported as defined in clause 4.2.1.1.
  • HEVC-FullHD-Dec decoding capability shall be supported as defined in clause 4.2.2.1.
Up

5.2.3  Audio decoding

If the 5GMS client supports the reception of audio:

5.2.4  Speech decoding

If the 5GMS client supports the reception of audio:
Up

5.2.5  Subtitles

If the 5GMS client supports the reception of subtitles:
  • the IMSC1.1 Text Track decoding capabilities IMSC1.1-TEXT-DEC as defined in clause 4.5.1.1 should be supported.

5.2.6  Presentation format

If 5GMS client supports presentation, then 3GPP HTML5 Profile as defined in TS 26.307 should be supported.
For a relevant set of media related APIs, please also take into account the Web Media API Snapshot 2019 (CTA-5000-B) [19].

5.2.7  Decapsulation and decryption

5.2.7.1  Introduction

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.

5.2.7.2  Video media profilesWord‑p. 23
If the 5GMSd client supports the reception of video, then the following applies:
If the 5GMSd client supports the reception of video and HD-HDR Capabilities, then the following applies:
Up

5.2.7.3  Speech media profiles

If the 5GMSd client supports the reception of speech, then the following shall be supported:
If the 5GMSd client supports the reception of speech, then the following should be supported:
If the 5GMSd client supports the reception of speech, then the following may be supported:
Up

5.2.7.4  Audio media profiles

If the 5GMSd client supports the reception of audio, then the following should be supported:
  • the eAAC+ stereo playback requirements as defined in TS 26.117, clause 7.5.2.4.
If the 5GMSd client supports the reception of audio, then the following may be supported:

5.2.7.5  Subtitle media profiles

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.

5.2.7.6  Encrypted content

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.
Up

5.2.8  Capability discoveryWord‑p. 24

5.2.8.1  General

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 if a media profile is supported, the 5GMS client may provide an API as defined in TS 26.512 in 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 [11].
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 5GMS 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.
Up

5.2.8.2  Video media profiles

For AVC-HD:
  • the <profiles> parameter is compatible to video/mp4 profiles='cmfc'
  • the <codecs> parameter is compatible to either 'avc1.640028' or 'avc3.640028'
For AVC-FullHD:
  • the <profiles> parameter is compatible to video/mp4 profiles='cmfc'
  • the <codecs> parameter is compatible to either 'avc1.640029' or 'avc3.640029'
For AVC-UHD:
  • the <profiles> parameter is compatible to video/mp4 profiles='cmfc'
  • the <codecs> parameter is compatible to either 'avc1.640028' or 'avc3.640028'
For HEVC-HD:
  • the <profiles> parameter is compatible to video/mp4 profiles='cmfc'
  • the <codecs> parameter is compatible to either 'hvc1.1.2.L93.B0' or 'hev1.1.2.L93.B0'
For HEVC-FullHD:
  • the <profiles> parameter is compatible to video/mp4 profiles='cmfc'
  • the <codecs> parameter is compatible to either 'hvc1.2.4.L123.B0' or 'hev1.2.4.L123.B0'
For HEVC-UHD:
  • the <profiles> parameter is compatible to video/mp4 profiles='cmfc'
  • the <codecs> parameter is compatible to either 'hvc1.2.4.L153.B0' or 'hev1.2.4.L153.B0'
Up

5.2.8.3  Audio media profilesWord‑p. 25
For AMR:
For AMR-WB:
For EVS:
For eAAC+ stereo:
For AMR-WB+:
Up

5.2.8.4  Subtitle media profiles

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'.

5.2.8.5  Encryption mode discoveryWord‑p. 26
Encryption mode discovery will be studied in due course.

5.3  Uplink streaming default profile

5.3.1  Introduction

This profile defines selected UE-based 5GMS Media Streamer functionalities as defined in TS 26.501 and shown in Figure 4.3.2-1 in TS 26.501. The following functions are defined in this clause:
  • Media Encoding
  • Media Upstream Client Encapsulation

5.3.2  Video encoding

If the 5GMS UE supports the transmission of video:
  • the real-time encoding capabilities for HEVC-FullHD-Enc as defined in clause 4.2.2.2 defined as the sender requirements for HEVC-FullHD-Enc Operation Point shall be supported.

5.3.3  Audio encoding

If the 5GMS UE supports the transmission of audio:

5.3.4  Speech encoding

If the 5GMS UE supports the transmission of speech:
Up

5.3.5  Encapsulation

5.3.5.1  Introduction

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.

5.3.5.2  Video media profile

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.

5.3.5.3  Speech media profileWord‑p. 27
If the 5GMS client supports the transmission of speech, then the following shall be supported:
If the 5GMS client supports the transmission of speech, then the following should be supported:
If the 5GMS client supports the transmission of speech, then the following may be supported:
Up

5.3.5.4  Audio media profile

If the 5GMS client supports the transmission of audio, then the following should be supported:

5.4  Television (TV) profile

5.4.1  Video decoding

5.4.1.1  H.264 (AVC)

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

5.4.1.2  H.265 (HEVC)

If the 5GMS client supports the Television (TV) profile, it should support:
If the 5GMS client supports the Television (TV) profile and HD-HDR capabilities, it shall support:
Up

5.4.2  Audio decodingWord‑p. 28
If the 5GMS client supports the Television (TV) profile, it /should support eAAC+ stereo Operation point as defined in TS 26.117, clause 6.3.3.

5.4.3  Subtitle decoding

If the 5GMS client supports the Television (TV) profile, it should support the IMSC-1.1-TEXT-DEC decoding capabilities as defined in clause 4.5.1.1.

5.4.4  Decapsulation and decryption

5.4.4.1  Introduction

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 5GMS 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 to both specifications.
Up

5.4.4.2  Video media profiles

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

5.4.4.3  Audio media profilesWord‑p. 29
If the 5GMSd client supports the Television (TV) profile, then the following should be supported:
  • the eAAC+ stereo playback requirements as defined in TS 26.117 clause 7.5.2.4.

5.4.4.4  Subtitle media profiles

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.

5.4.4.5  Encrypted content

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

5.4.5  Capability discovery

If the 5GMSd client supports the Television (TV) profile it is expected to support capability discovery such that 5GMS-aware applications can identify if a specific media profile is supported.
The same requirements apply as in clause 5.2.8 for the default profile.
A 5GMSd client that supports the Television (TV) profile may support additional capability methods that permits to identify additional capabilities of media profile playback taking into account information provided in the MPD for TV Video Profiles. Examples include the W3C Media Capability APIs [18].
Up

5.5  Downlink 360 Virtual Reality (VR) profile

5.5.1  Video

5.5.1.1  Operation Points

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

5.5.1.2  DASH encapsulationWord‑p. 30
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 TS 26.118, clause 5.2.2.3.
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 TS 26.118, clause 5.2.3.3.
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 TS 26.118, clause 5.2.3.4.
Up

5.5.2  Audio

5.5.2.1  Operation Points

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

5.5.2.2  DASH encapsulation

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 TS 26.118, clause 6.2.2.3.

5.6  Uplink 360 Virtual Reality (VR) profile

5.6.1  Video

5.6.1.1  Operation Points

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:
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:
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:
Up

5.6.1.2  Encapsulation

[TBD]

5.6.2  AudioWord‑p. 31

5.6.2.1  Operation Points

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:

5.6.2.2  Encapsulation

[TBD]

$  Change historyWord‑p. 32

Up   Top