9 Media Codec Profiles

26.2383GPPRelease 17TSUplink streaming

9.1 General

This clause specifies media codec profiles recommended for use with the Framework for Live Uplink Streaming. However, as a framework, FLUS is flexible enough to support use of other codecs and encapsulations that are not specified in any of the profiles.

9.2 IMS-based FLUS

If the FLUS source supports the default profile for live uplink streaming it shall support encoding requirements specified in clauses 5.3.2, 5.3.4, and 5.3.5 of [23] and the following encapsulation:

If the transmission of video is supported, then the RTP payload format of H.265/HEVC as specified in RFC 7798 [24] shall be supported

If the transmission of speech is supported, then the:

– RTP payload format of EVS as specified in TS 26.445 [25] shall be supported

– RTP payload format of AMR-WB as specified in RFC 4867 [26] should be supported

– RTP payload format of AMR as specified in RFC 4867 [26] may be supported

If the transmission of audio is supported, then RTP payload format of eAAC+ as specified in RFC 6416 [27] shall be supported

9.3 Non-IMS-based FLUS

If the FLUS source supports the default profile for live uplink streaming it shall support the encoding and encapsulation requirements specified in clause 5.3 of [23].

If the FLUS source supports the 360 Virtual Reality profile for live uplink streaming it shall support the encoding and encapsulation requirements specified in clause 5.6 of [23].