Add files using upload-large-folder tool

marked/Rel-18/26_series/26110/raw.md

@@ -0,0 +1,407 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Codec for circuit switched multimedia telephony service; General description (Release 18)**
+
+![3GPP logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+---
+
+The 3GPP logo features the letters '3GPP' in a stylized, bold font. The '3' is black, the 'G' is black with a red signal icon at its base, the 'P' is black, and the 'P' is black with a small 'TM' symbol to its right.
+
+3GPP logo
+
+A GLOBAL INITIATIVE
+
+## --- **Keywords**
+
+UMTS, codec, telephony, circuit mode,  
+multimedia
+
+## **3GPP**
+
+## --- **Postal address**
+
+## --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- Contents
+
+|                                                            |           |
+|------------------------------------------------------------|-----------|
+| Foreword .....                                             | 4         |
+| Introduction .....                                         | 4         |
+| 1 Scope.....                                               | 5         |
+| 2 References.....                                          | 5         |
+| 3 Definitions and abbreviations .....                      | 6         |
+| 3.1 Definitions.....                                       | 6         |
+| 3.2 Abbreviations .....                                    | 6         |
+| 4 General.....                                             | 7         |
+| 5 ITU-T H.324 .....                                        | 8         |
+| 6 Modifications to H.324 (3GPP TS 26.111).....             | 8         |
+| 7 Call set-up requirements .....                           | 8         |
+| 8 Terminal implementor's guide (3GPP TR 26.911) .....      | 8         |
+| <b>Annex A (informative): Background information .....</b> | <b>9</b>  |
+| A.1 Video I/O Equipment.....                               | 9         |
+| A.2 Video Codec.....                                       | 9         |
+| A.2.1 H.261 .....                                          | 10        |
+| A.2.2 H.263 .....                                          | 10        |
+| A.2.3 MPEG-4 .....                                         | 10        |
+| A.3 Audio I/O Codec .....                                  | 10        |
+| A.4 Speech Codec.....                                      | 10        |
+| A.4.1 3GPP AMR .....                                       | 10        |
+| A.4.2 G.723.1 .....                                        | 11        |
+| A.5 User Data Applications .....                           | 11        |
+| A.5.1 Data conferencing – T.120 .....                      | 11        |
+| A.5.2 Text conversation – T.140.....                       | 12        |
+| A.6 Data Protocols.....                                    | 12        |
+| A.7 System Control.....                                    | 12        |
+| A.8 Call Set-up.....                                       | 12        |
+| A.9 H.245.....                                             | 12        |
+| A.10 H.223.....                                            | 12        |
+| A.10.1 Level 0.....                                        | 13        |
+| A.10.2 Level 1.....                                        | 13        |
+| A.10.3 Level 2.....                                        | 13        |
+| A.10.4 Level 3.....                                        | 13        |
+| <b>Annex B (informative): Bibliography .....</b>           | <b>13</b> |
+| <b>Annex C (informative): Change history.....</b>          | <b>14</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3GPP.
+
+The present document introduces the set of specifications which apply to 3G-324M multimedia terminals within the 3GPP system.
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of this TS, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version 3.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 Indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the specification;
+
+# --- Introduction
+
+This document contains a specification for H.324 based multimedia codecs for circuit switched 3GPP networks. The term codec is usually associated with a single media type. However, many multimedia services require a close integration of disparate media types. In this sense, the representations of these media types (in the form of media streams) are at least logically bound into a single multimedia stream. As such, a H.324 based multimedia codec must handle multiplexing/de-multiplexing and skew. It will also have to provide codecs for each of the derived media streams. End-to-end, in-band control is also required for the purposes of configuration and establishing individual media streams. Finally, since 3GPP networks are inherently error prone, error detection and/or correction must also be provided by the multimedia codec since it has a comprehensive view of the bit stream it produces and therefore can apply the most efficient form of error detection and/or correction.
+
+# --- 1 Scope
+
+This specification introduces the set of specifications which apply to 3G-324M multimedia terminals.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] ITU-T Recommendation H.223: "Multiplexing protocol for low bitrate multimedia communication"
+- [2] ITU-T Recommendation H.223 — Annex A: "Multiplexing protocol for low bitrate multimedia communication over low error-prone channels"
+- [3] ITU-T Recommendation H.223 — Annex B: "Multiplexing protocol for low bitrate multimedia communication over moderate error-prone channels"
+- [4] ITU-T Recommendation H.223 — Annex C: "Multiplexing protocol for low bitrate multimedia communication over highly error-prone channels"
+- [5] ITU-T Recommendation H.223 — Annex D: "Optional multiplexing protocol for low bitrate multimedia communication over highly error-prone channels"
+- [6] ITU-T Recommendation H.245: "Control protocol for multimedia communication"
+- [7] ITU-T Recommendation G.723.1: "Dual rate speech coder for multimedia communication transmitting at 5.3 & 6.3 kbit/s"
+- [8] ITU-T Recommendation H.263: "Video coding for low bitrate communication"
+- [9] ITU-T Recommendation H.261: "Video CODEC for audiovisual services at p X 64 kbit/s"
+- [10] ITU-T Recommendation H.324: "Terminal for low bitrate multimedia communication"
+- [11] 3GPP TS 26.111: "Modifications to H.324"
+- [12] 3GPP TR 26.911: "Terminal Implementor's Guide"
+- [13] ITU-T Recommendation X.691: "Information Technology - ASN.1 Encoding Rules - Specification of Packed Encoding Rules (PER)"
+- [14] International Standard ISO/IEC 14494-2: "Information technology — Generic coding of audiovisual object — Part 2: Visual, 1999"
+- [15] 3GPP TS 26.071: "Mandatory Speech Codec; General Description"
+- [16] 3GPP TS 26.090: "Mandatory Speech Codec; Speech Transcoding Functions"
+- [17] 3GPP TS 26.073: "Mandatory Speech Codec; ANSI C-Code"
+- [18] ITU-T T.140 (1998) Presentation protocol for text conversation application.
+- [19] 3GPP TS 22.226: "Global Text Telephony; Stage 1"
+
+- [20] 3GPP TS 24.008: "Mobile Radio Interface - Layer 3 MM/CC Specification".
+- [21] 3GPP TS 27.001: "General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)".
+- [22] 3GPP TS 29.007: "General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)".
+- [23] 3GPP TS 23.108: "Mobile radio interface layer 3 specification; Core Network protocols; stage 2".
+- [24] ITU-T Recommendation G.712: "Transmission performance characteristics of pulse code modulation channels".
+- [25] ITU-T Recommendation T.120: "Data protocols for multimedia conferencing".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply.
+
+**H.324 terminal:** ITU-T H.324 recommendation, including Annex C
+
+**3G-324M terminal:** Based on ITU-T H.324 recommendation modified by 3GPP for purposes of 3GPP circuit switched network based video telephony
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|          |                                                   |
+|----------|---------------------------------------------------|
+| ACELP    | Algebraic-Code-Excited Linear-Prediction          |
+| ADC      | Analogue Digital Converter                        |
+| AEC      | Acoustic Echo Cancellation                        |
+| AL       | Adaptation Layer                                  |
+| CCSRL    | Control Channel Segmentation and Reassembly Layer |
+| CELP     | Code-Excited Linear-Prediction                    |
+| CT       | Correlation Threshold                             |
+| DAC      | Digital Analogue Converter                        |
+| DCT      | Discrete Cosine Transformation                    |
+| EI       | Error Indication                                  |
+| EOB      | End Of Block                                      |
+| FEC      | Forward Error Correction                          |
+| GOB      | Group Of Blocks                                   |
+| GQUANT   | Group Quantizer information                       |
+| GTT      | Global Text Telephony                             |
+| HDLC     | High-Level Data Link Control                      |
+| HEC      | Header Error Control                              |
+| ISDN     | Integrated Services Digital Network               |
+| LAPM     | Link Access Procedure for Modems                  |
+| LC       | Logical Channel                                   |
+| MC       | Multiplex Code                                    |
+| MCU      | Multipoint Communication Unit                     |
+| MP-MLQ   | Multipulse Maximum Likelihood Quantization        |
+| MPL      | Multiplex Payload Length                          |
+| MR-ACELP | Multi-rate ACELP                                  |
+| PC       | Personal Computer                                 |
+| MCU      | Multipoint Conference Unit                        |
+| MUX      | H.223 Multiplex layer                             |
+| PDU      | Protocol Data Unit                                |
+
+|     |                      |
+|-----|----------------------|
+| SN  | Sequence Number      |
+| VLC | Variable Length Code |
+
+# 4 General
+
+3G-324M terminals provide real-time video, audio, or data, in any combination, including none, over 3GPP circuit-switched, radio networks. They are based on ITU-T H.324 with Annex C, and Annex H when mobile multilink operation is supported. Communication may be either 1-way or 2-way. Such terminals may be part of a portable device or integrated into an automobile or other non fixed location device. They may also be fixed, stand-alone devices; for example, a video telephone or kiosk. 3G-324M terminals may also be integrated into PCs and workstations.
+
+In addition to 3G-324M to 3G-324M communication, interoperation with other types of multimedia telephone terminals is possible, however a gateway may be required.
+
+Multipoint communication between more than two 3G-324M terminals is possible using a Multipoint Communication Unit (MCU). MCU functionality is for further study.
+
+3G-324M terminals are based on ITU-T H.324 with Annex C, and Annex H when mobile multilink operation is supported. For performance reasons and to reference the call set-up procedures, some modifications to H.324 were made. These are described in 3GPP TS 26.111, except call set-up procedures are described in 3GPP TS 24.008, 27.001, 29.007 and 23.108. 3G-324M terminals shall conform to these specifications. Because of the many options in H.324, an implementor's guide, 3GPP TR 26.911, provides preferred options for 3G-324M implementations.
+
+Figure 1 below shows the functional components of a generic 3GPP multimedia terminal. The video, speech, data and multilink components are optional. If a media type is supported, the standards indicated are mandatory except those enclosed in square brackets are optional.
+
+![Figure 1: Scope of circuit switched multimedia 3GPP specification. This block diagram illustrates the functional components of a generic 3GPP multimedia terminal. On the left, external components include Video I/O Equipment, Audio I/O Equipment, User Data Applications [T.120, ...], and System Control. These connect to internal processing blocks: Video Codec (H.263, [MPEG-4, H.261 ...]), Speech Codec (3GPP-AMR, [G.723.1 ...]), Data Protocols [V.14, LAPM, ...], H.245, CCSRL, and NSRP[LAP M/V.42]. An Optional Receive Path Delay is shown between the Speech Codec and the Multiplex/Demultiplex block. All internal blocks connect to a central Multiplex/Demultiplex block (H.223, H.223 Annex A, H.223 Annex B, [H.223 Annex C, H.223 Annex D]). This block connects to an Optional Multilink block (H.324 Annex H), which in turn connects to the 3GPP Network. The System Control block also connects to a Call Set-up block, which is connected to the 3GPP Network.](e2c1c672349c10dccb2563eff6d8260e_img.jpg)
+
+Figure 1: Scope of circuit switched multimedia 3GPP specification. This block diagram illustrates the functional components of a generic 3GPP multimedia terminal. On the left, external components include Video I/O Equipment, Audio I/O Equipment, User Data Applications [T.120, ...], and System Control. These connect to internal processing blocks: Video Codec (H.263, [MPEG-4, H.261 ...]), Speech Codec (3GPP-AMR, [G.723.1 ...]), Data Protocols [V.14, LAPM, ...], H.245, CCSRL, and NSRP[LAP M/V.42]. An Optional Receive Path Delay is shown between the Speech Codec and the Multiplex/Demultiplex block. All internal blocks connect to a central Multiplex/Demultiplex block (H.223, H.223 Annex A, H.223 Annex B, [H.223 Annex C, H.223 Annex D]). This block connects to an Optional Multilink block (H.324 Annex H), which in turn connects to the 3GPP Network. The System Control block also connects to a Call Set-up block, which is connected to the 3GPP Network.
+
+**Figure 1** Scope of circuit switched multimedia 3GPP specification. Items in [brackets] are optional.
+
+Short descriptions of ITU-T H.324, 3GPP TS 26.111, and 3GPP TR 26.911 are given below.
+
+# --- 5 ITU-T H.324
+
+ITU-T H.324 describes terminals for low bitrate multimedia communication. That ITU-T recommendation contains "ANNEX C, Multimedia Telephone Terminals Over Error Prone Channels" (sometimes referred to as H.324/M) and "ANNEX H, Mobile Multilink Operation". These annexes are considered an integral part of the recommendation. Therefore, herewith H.324 shall mean ITU-T H.324 with Annex C. When multilink operation is utilized, H.324 shall also mean to include H.324 Annex H.
+
+Originally designed for V.34 modems, H.324 now supports ISDN and wireless networks. Therefore, it is well suited as a basis for 3GPP multimedia codecs. Relevant to wireless networks, H.324 describes the overall system architecture and introduces control (H.245), mux (H.223), video (H.261 and H.263), text (T.140), and audio (G.723.1).
+
+Annex A provides a short overview of H.324 and multimedia codecs.
+
+# --- 6 Modifications to H.324 (3GPP TS 26.111)
+
+To enable cost-effective, high-quality H.324 terminals for 3GPP networks, some modifications were made to H.324. These modifications are described in 3GPP TS 26.111. Terminals adhering to this specification are herewith known as 3G-324M terminals. 3G-324M terminals shall conform to 3GPP TS 26.111.
+
+# --- 7 Call set-up requirements
+
+H.324 does not describe call set-up procedures for 3GPP networks. These are described in 3GPP TS 24.008, 27.001, 29.007, 23.108 and shall be used for 3G-324M terminals.
+
+# --- 8 Terminal implementor's guide (3GPP TR 26.911)
+
+A successful 3G-324M terminal will have to function well at bandwidths as low as 32 KBPS and in potentially high error rate environments. 3G-324M contains many options that may be employed by an implementor. To help choose which options and combinations of options are useful, an implementor's guide is provided in 3GPP TR 26.911.
+
+# --- Annex A (informative): Background information
+
+The section is intended for informational purposes only. This is not an integral part of this specification. Each section below relates to the functional components in figure 1.
+
+## --- A.1 Video I/O Equipment
+
+For a video telephone this would most likely consist of a video camera and display monitor. Other possible input sources could be a VCR or disk drive. While most applicable I/O equipment relies on a standard format for the video signal or bit stream, this format is likely to differ from that mandated by the video codec. In such cases, circuitry or software is used to transcode between the two formats.
+
+## --- A.2 Video Codec
+
+ITU-R 601 (NTSC or PAL) is a typical video input signal and represents a bit stream of 20.7 Mbyte/s for the actual image (excluding blanking intervals). The first order of compression occurs by reducing the resolution of the input signal.<sup>1</sup> For example, CIF resolution at 30 fps produces a bit stream 4.6 Mbyte/s. Additional savings occur by dropping frames. In a videoconference, where motion is relatively slow, 10 fps is considered adequate. Thus, the original signal of 20.7 Mbytes/s could be reduced to 1.5 Mbyte/s with just these techniques. However, this is still 188 times greater than can be transmitted on, for example, a 64 KBPS channel. Substantial compression is still required, especially considering that framing, control, and audio would as well require a portion of the available bandwidth.
+
+To achieve the degree of compression required for video telephony, all of the video codecs that can currently be employed in a 3GPP multimedia codec use a combination of spatial and temporal redundancy reduction to reduce the bandwidth required by the video media stream. Spatial redundancy can be reduced by converting the input signal from the time domain to the frequency domain using a DCT. This produces a DC value and other coefficients, where most of the scene energy is concentrated in the coefficients corresponding to the lower frequencies. Next, a coarse quantizer is applied (which, in this domain, has little effect on image quality). This results in many of the coefficients being encoded to 0. The significant coefficients are encoded to a much smaller range of values. The coefficients are then reordered so that, typically, the larger magnitude values will occur first followed by 0 value coefficients. Finally, the coefficients are replaced with a count of the number of zero value coefficients followed by the value of a nonzero coefficient. This combination is translated into a VLC. Applying this type of compression to the entire video frame produces an intra frame.
+
+Despite the efficiency of intra coding, significantly more compression is required. In addition to removing spatial redundancy, all video codecs apply temporal reduction as well. This is achieved by comparing the current frame to the previous and estimating the set of vectors which when applied to their respective areas of the scene would create the new, current frame based on the old, previous frame. The match is usually not perfect, so an error component is transmitted as well. The error component is also transformed to the frequency domain, so the same compression efficiency achieved in the intra frame is achieved here as well — enhanced by the fact the range of error coefficients is less than intra coefficients. Since generally only a few areas of a scene change from frame to frame, high compression can be achieved by sending a series of inter frames. If the error component for a particular block is too large, it can be encoded as an intra block.
+
+Since, by their nature, VLCs are not fixed length, a single bit error can make it impossible to decode an entire frame. Unfortunately, each inter coded frame relies on its previous frame to be decoded. Thus, a single bit error can destroy the entire remaining bit stream. Video codecs have various ways of handling errors. The simplest is to use error detection to determine if a frame contains an error. The transmitter is then signalled that an error occurred. It then sends an intra coded frame, which does not depend on any previous frames. This approach consumes considerable bandwidth and is only practical for very low error networks. Other, more sophisticated schemes are available using the video codecs available to 3G-324M terminals.
+
+---
+
+<sup>1</sup> Note that ITU-R 601 represents 16 bit precision colour, whereas true colour is usually considered to require 24 bit precision. Also, the spatial resolution of ITU-R 601 is substantially less than can be achieved with normal human vision.
+
+### A.2.1 H.261
+
+H.261 supports CIF and QCIF images as input. It provides good video quality at 64 kbit/s or higher. It uses BCH codes for Forward Error Correction (FEC). However, this is not recommended for H.324.
+
+### A.2.2 H.263
+
+H.263 is an extension of H.261. It allows sub-QCIF, 4CIF and 16CIF as additional input formats. H.263, in its original version, provides four annexes that describe optional modes for enhanced coding.
+
+- Advanced prediction mode (Annex F) provides half-pel motion estimation, median-based motion vector prediction, 4 motion vectors per macroblock (one per block), and overlapped block motion compensation
+- Unrestricted motion vectors (Annex D) work in conjunction with advanced prediction mode and allow motion vectors to point outside the picture area
+- Arithmetic coding (Annex E) can be used instead of variable length coding
+- PB-frames (Annex G) allow bi-directional prediction similar to MPEG
+
+Other significant differences exist, but require a level of detail to explain that renders them outside the scope of this document.
+
+A second version of H.263 (known as H.263+) adds annexes I through T, some of which address error prone environments and are therefore of special interest to 3GPP multimedia codecs.
+
+### A.2.3 MPEG-4
+
+MPEG-4 Visual (ISO/IEC 14496-2) is a generic video codec. One of its target areas is mobile communications. Error resiliency and high efficiency make this codec particularly well suited for 3G-324M.
+
+MPEG-4 Visual is organised into Profiles. Within a Profile, various Levels are defined. Profiles define subsets of tool sets. Levels are related to computational complexity. Among these Profiles, Simple Visual Profile provides error resilience (through data partitioning, RVLC, resynchronization marker and header extension code) and low complexity.
+
+MPEG-4 allows various input formats, including general formats such as QCIF and CIF. It is also baseline compatible with H.263.
+
+## --- A.3 Audio I/O Codec
+
+Generally, a video telephone would require a handset, headset, or microphone and speaker. Often, integrated circuits are employed that convert the typically analogue input signal to a PCM format bit stream (ADC) and convert PCM to an analogue signal for acoustic output (DAC). This is helpful since many speech codecs use PCM for input and output. Video telephones often use a separate microphone and speaker. This allows the user to be seen without a handset or headset. However, if this is so, AEC will be required.
+
+## --- A.4 Speech Codec
+
+### A.4.1 3GPP AMR
+
+The AMR codec uses eight source codecs with bit-rates of 12.2, 10.2, 7.95, 7.40, 6.70, 5.90, 5.15 and 4.75 kbit/s. The coder operates on speech frames of 20 ms corresponding to 160 samples at the sampling frequency of 8000 sample/s. It performs the mapping from input blocks of 160 speech samples in 13-bit uniform PCM format to encoded blocks of 95, 103, 118, 134, 148, 159, 204, and 244 bits and from encoded blocks of 95, 103, 118, 134, 148, 159, 204, and 244 bits to output blocks of 160 reconstructed speech samples. The coding scheme for the multi-rate coding modes is the so-called Algebraic Code Excited Linear Prediction Coder (ACELP). The multi-rate ACELP coder is referred to as MR-ACELP.
+
+At each 160 speech samples, the speech signal is analysed to extract the parameters of the CELP model (LP filter coefficients, adaptive and fixed codebooks' indices and gains). These parameters are encoded and transmitted. At the decoder, these parameters are decoded and speech is synthesised by filtering the reconstructed excitation signal through the LP synthesis filter.
+
+The adaptive multi-rate speech codec is described in a bit-exact arithmetic in form of a fixed-point ANSI-C code to allow for easy type approval as well as general testing purposes of the adaptive multi-rate speech codec.
+
+The DTX mechanism includes a Voice Activity Detector (VAD) on the TX side; evaluation of the background acoustic noise on the TX side, in order to transmit characteristic parameters to the RX side; and generation of comfort noise on the RX side during periods where the radio transmission is turned off.
+
+The AMR specification contains error concealment. The purpose of frame substitution is to conceal the effect of lost AMR speech frames. The purpose of muting the output in the case of several lost frames is to indicate the breakdown of the channel to the user and to avoid generating possible annoying sounds as a result from the frame substitution procedure.
+
+### A.4.2 G.723.1
+
+G.723.1 can be used for compressing the speech or other audio signal component of multimedia services at a very low bitrate as part of H.324. This coder has two bit-rates associated with it, 5.3 and 6.3 kbit/s. The higher bitrate has greater quality. The lower bit-rate gives good quality and provides system designers with additional flexibility. Both rates are a mandatory part of the encoder and decoder. It is possible to switch between the two rates at any frame boundary. An option for variable rate operation using discontinuous transmission and noise fill during non-speech intervals is also possible using a series of silence frames or a single silence frame followed by no frames until speech is detected.
+
+G.723.1 encodes speech or other audio signals in frames using linear predictive analysis-by-synthesis coding. The excitation signal for the high rate coder is Multipulse Maximum Likelihood Quantization (MP-MLQ) and for the low rate coder is Algebraic-Code-Excited Linear-Prediction (ACELP). The frame size is 30 ms and there is an additional look ahead of 7.5 msec,. This coder is designed to operate with a digital signal obtained by first performing telephone bandwidth filtering (ITU-T Recommendation G.712) of the analogue input, then sampling at 8000 Hz and then converting to 16-bit linear PCM for the input to the encoder. The output of the decoder is converted back to analogue by similar means.
+
+G.723.1 has been designed to be robust for indicated frame erasures. An error concealment strategy for frame erasures has been included in the decoder. However, this strategy must be triggered by an external indication that the bit stream for the current frame has been erased. This can be achieved in H.324 using the AL2 Error Indication (EI) flag and the optional AL2 Sequence Number (SN). Because the coder was designed for burst errors, there is no error correction mechanism provided for random bit errors. If a frame erasure has occurred, the decoder switches from regular decoding to frame erasure concealment mode.
+
+G.723.1 contains three annexes. Annex A describes the silence compression system designed for the G.723.1 speech coder (mentioned above). Annex B describes an alternative implementation of G.723.1 contained in floating point C source code. Annex C specifies a channel coding scheme which can be used with the triple rate speech codec G.723.1. The channel codec is scalable in bit-rate and is designed for mobile multimedia applications as a part of the overall H.324 family of standards.
+
+## --- A.5 User Data Applications
+
+### A.5.1 Data conferencing – T.120
+
+An example of a User Data Application is T.120. This protocol allows multipoint data conferencing that includes data and image transferral. Other functions, such as shared whiteboards and applications, are possible.
+
+### A.5.2 Text conversation – T.140
+
+The real time text conversation application, is supported by the presentation protocol ITU-T T.140 [19]. The Global Text Telephony feature is implemented in the CS Multimedia environment by applying T.140, as specified in H.324.
+
+The text stream may be opened simultaneously with voice, video and other data applications. Text-only sessions are also possible. Further requirements applicable to the Global Text Telephony feature are specified in TS 22.226 [20].
+
+The data protocol for T.140 is specified in H.324 to be AL1.
+
+## --- A.6 Data Protocols
+
+Various data protocols can be supported. These always support data applications (see A.5 User Data Applications). A specific protocol or set of protocols is often stipulated by the data application. Each protocol provides varying degrees of error detection and/or correction.
+
+## --- A.7 System Control
+
+In general, system control constitutes the overall state machine for the terminal. It usually has to be aware of when a connection has been established. At that point it can begin H.245 procedures such as master/slave determination, capabilities exchange, and opening logical channels. Upon call termination, either initiated at the near or far ends, system control generally initiates H.245 end session procedures.
+
+## --- A.8 Call Set-up
+
+All out-of-band network signalling for the purpose of call control is handled by call set-up, which is usually implemented as a state machine. This includes initiating, answering, and tearing down calls.
+
+## --- A.9 H.245
+
+H.245 specifies the syntax and semantics for in-band, terminal-to-terminal control messages and the procedures for their use. Most importantly, H.245 is used for master/slave determination, capabilities exchange, H.223 mux table transmission, and opening and closing logical channels. There is also a large array of general control and indication messages. H.245 addresses a wide range of terminals and applications. Therefore, only a subset of the messages listed in H.245 pertain to 3G-324M terminals. Messages fall into one of four categories: Request (requires a Response), Response (in response to a Request), Command (requires an action), and Indication (informative only).
+
+H.245 messages are carried on a single logical channel within the H.223 mux. This channel is labelled LC 0 and is considered to be open upon establishing digital communications end-to-end and survives until digital communication is terminated. Due to the characteristics of the H.223 mux, bandwidth for H.245 messages is allocated on an as-needed basis. Since most H.245 traffic occurs at the beginning and end of the session, this conserves much needed bandwidth for video and audio. Error control is not provided for within H.245 and is specified elsewhere.
+
+## --- A.10 H.223
+
+H.223 describes the multiplexing protocol used between H.324 terminals. It is packet oriented and each packet can contain a subset of a maximum of 65536 LCs. Each LC represents a single media, information, or control channel. The H.223 protocol is split into two layers, the lowest being the Multiplex Layer.
+
+The Multiplex Layer exchanges data with the end terminal via MUX-PDUs. Multiplex table entries, of which there are 16 (and can be changed during a session), describe which octets from within the PDU are allocated to which logical channels. The multiplex table entry employed for a particular PDU is indicated by the 4 bit MC field in the MUX-PDU header. MUX-PDUs contain an integer number of octets. Errors within the MUX-PDU header are controlled using the HEC field in the MUX-PDU header. H.324 terminals utilising the V.34 transmission protocol frame MUX-PDUs with HDLC. Bit stuffing is used for data transparency in this case.
+
+Above the Multiplex Layer is the Adaptation Layer, of which there are three different types.
+
+- 1) AL1 is designed primarily for control information and data protocols. It can be either framed or unframed and does not provide any error control.
+- 2) AL2 is designed primarily for the transfer of digital audio. AL2 PDUs contain 1 octet for an 8-bit CRC and an optional octet for a sequence number.
+- 3) AL3 is designed primarily for the transfer of digital video. AL3 PDUs contain 2 octets for a 16-bit CRC. There is also optionally 1 or 2 octets for control. AL3 also allows limited retransmission.
+
+For purposes of video telecommunications over wireless networks, four annexes to H.223 have been created. These create four levels of error detection and error correction.
+
+### A.10.1 Level 0
+
+Level 0 applies to H.223 as described above.
+
+### A.10.2 Level 1
+
+Level 1, described in Annex A, replaces HDLC framing with 1 or 2 16 bit flags. Unlike HDLC, Level 1 does not guarantee data transparency. However, if the MUX-PDU header is constructed in such a way as to make emulating the Level 1 framing flags impossible, data transparency can be achieved by correctly decoding the MUX-PDU. Should there be an error in the MUX-PDU header, resynchronization techniques will have to be applied.
+
+### A.10.3 Level 2
+
+Level 2, described in Annex B, uses the same framing as Level 1, but utilises a 3 octet header. This header starts with a 4 bit MC, which is the same as in Level 0. This is followed by an 8-bit MPL-field, with a range of values 0 – 254. Lastly, a 12 bit extended Golay code is used for parity bits. The PM in Level 2 is signalled through the polarity of the MUX-PDU flag. If the output of the correlator is greater than or equal to CT, the PM is 0. If it is less than or equal to -CT, the PM equals 1. After the parity bits, there can be an optional MUX-PDU header for the previous (corrupted) MUX-PDU. This 1 octet field uses the format described in Level 0. Level 2 also offers enhanced packet resynchronization.
+
+### A.10.4 Level 3
+
+Level 3, described in Annexes C and D, provides error correction capabilities at the mux level.
+
+# --- Annex B (informative): Bibliography
+
+(void)
+
+# Annex C (informative): Change history
+
+| Change history |       |           |     |     |                                                                   |        |        |
+|----------------|-------|-----------|-----|-----|-------------------------------------------------------------------|--------|--------|
+| Date           | TSG # | TSG Doc.  | CR  | Rev | Subject/Comment                                                   | Old    | New    |
+| 06-1999        | 04    |           |     |     | Approved at TSG-SA#4                                              |        | 3.0.0  |
+| 09-2000        | 09    | SP-000395 | 001 |     | CS Multimedia Codec specification for real time text conversation | 3.0.1  | 4.0.0  |
+| 03-2001        | 011   | SP-010105 | 002 | 1   | Support of mobile multi-link operation in 3G-324M                 | 4.0.0  | 4.1.0  |
+| 03-2001        | 011   | SP-010105 | 004 | 1   | Correction of incorrect reference                                 | 4.0.0  | 4.1.0  |
+| 06-2002        | 016   |           |     |     | Version for Release 5                                             | 4.1.0  | 5.0.0  |
+| 12-2004        | 026   |           |     |     | Version for Release 6                                             | 5.0.0  | 6.0.0  |
+| 06-2007        | 036   |           |     |     | Version for Release 7                                             | 6.0.0  | 7.0.0  |
+| 12-2008        | 042   |           |     |     | Version for Release 8                                             | 7.0.0  | 8.0.0  |
+| 12-2009        | 046   |           |     |     | Version for Release 9                                             | 8.0.0  | 9.0.0  |
+| 03-2011        | 051   |           |     |     | Version for Release 10                                            | 9.0.0  | 10.0.0 |
+| 09-2012        | 057   |           |     |     | Version for Release 11                                            | 10.0.0 | 11.0.0 |
+| 09-2014        | 065   |           |     |     | Version for Release 12                                            | 11.0.0 | 12.0.0 |
+| 12-2015        | 070   |           |     |     | Version for Release 13                                            | 12.0.0 | 13.0.0 |
+
+| Change history |         |      |    |     |     |                                |               |
+|----------------|---------|------|----|-----|-----|--------------------------------|---------------|
+| Date           | Meeting | TDoc | CR | Rev | Cat | Subject/Comment                | New version   |
+| 2017-03        | 75      |      |    |     |     | Version for Release 14         | 14.0.0        |
+| 2018-06        | 80      |      |    |     |     | Version for Release 15         | 15.0.0        |
+| 2020-07        | -       | -    | -  | -   | -   | Update to Rel-16 version (MCC) | <b>16.0.0</b> |
+| 2022-04        | -       | -    | -  | -   | -   | Update to Rel-17 version (MCC) | <b>17.0.0</b> |
+| 2024-03        | -       | -    | -  | -   | -   | Update to Rel-18 version (MCC) | <b>18.0.0</b> |

marked/Rel-18/26_series/26111/raw.md

@@ -0,0 +1,378 @@
+
+
+# 3GPP TS 26.111 V18.0.0 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Codec for circuit switched multimedia telephony service; Modifications to H.324 (Release 18)**
+
+![3GPP logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+---
+
+The 3GPP logo features the letters '3GPP' in a stylized, bold font. The '3' is black, the 'G' is black with a red signal icon at its base, the 'P' is black, and the 'P' is black with a red signal icon at its base. A small 'TM' trademark symbol is located to the right of the 'P'.
+
+3GPP logo
+
+A GLOBAL INITIATIVE
+
+## --- **Keywords**
+
+UMTS, telephony, multimedia, codec,  
+circuit mode
+
+## **3GPP**
+
+### --- **Postal address**
+
+### --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## --- Contents
+
+|                                                       |           |
+|-------------------------------------------------------|-----------|
+| Foreword .....                                        | 4         |
+| Introduction .....                                    | 4         |
+| 1 Scope.....                                          | 5         |
+| 2 References.....                                     | 5         |
+| 3 Definitions and abbreviations .....                 | 6         |
+| 3.1 Definitions.....                                  | 6         |
+| 3.2 Abbreviations .....                               | 6         |
+| 4 General.....                                        | 6         |
+| 5 Document structure .....                            | 6         |
+| 6 Functional requirements.....                        | 7         |
+| 6.1 Required elements .....                           | 7         |
+| 6.2 Information streams.....                          | 7         |
+| 6.3 Modem .....                                       | 7         |
+| 6.4 Multiplex .....                                   | 7         |
+| 6.5 Control channel .....                             | 7         |
+| 6.6 Video channels .....                              | 7         |
+| 6.6.1 MPEG-4 interface to multiplex .....             | 10        |
+| 6.6.2 H.264 (MPEG-4 AVC) interface to multiplex ..... | 10        |
+| 6.7 Audio channels.....                               | 11        |
+| 6.8 Data channels .....                               | 11        |
+| 7 Terminal procedures .....                           | 11        |
+| 8 Optional enhancements .....                         | 11        |
+| 9 Interoperation with other terminals.....            | 11        |
+| 10 Multipoint considerations .....                    | 11        |
+| 11 Maintenance.....                                   | 12        |
+| <b>Annex A (informative): Change History.....</b>     | <b>13</b> |
+
+# --- Foreword
+
+This Technical Specification (TS) has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- Introduction
+
+In the present document is described additions, deletions, and changes made to ITU-T Recommendation H.324 [10] with annex C for the purpose of using that recommendation as a basis for the technical specification for circuit switched multimedia service in 3GPP networks. The present document does not address call setup procedures, but references to the specifications which cover call setup are found in 3GPP TS 26.110 [11].
+
+# --- 1 Scope
+
+In ITU-T Recommendation H.324 [10] with annex C describes a generic multimedia codec for use in error-prone, wireless networks. The scope of the present document are the changes, deletions, and additions to those texts necessary to fully specify a multimedia codec for use in 3GPP networks. Note that this implicitly excludes the network interface and call setup procedures. Also excluded are any general introductions to the system components.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] ITU-T Recommendation H.223: "Multiplexing protocol for low bit rate multimedia communication".
+- [2] ITU-T Recommendation H.223 - Annex A: "Multiplexing protocol for low bit rate multimedia mobile communication over low error-prone channels".
+- [3] ITU-T Recommendation H.223 - Annex B: "Multiplexing protocol for low bit rate multimedia mobile communication over moderate error-prone channels".
+- [4] ITU-T Recommendation H.223 - Annex C: "Multiplexing protocol for low bit rate multimedia mobile communication over highly error-prone channels".
+- [5] ITU-T Recommendation H.223 - Annex D: "Optional multiplexing protocol for low bit rate multimedia mobile communication over highly error-prone channels".
+- [6] ITU-T Recommendation H.245: "Control protocol for multimedia communication".
+- [7] ITU-T Recommendation G.723.1: "Dual rate speech coder for multimedia communication transmitting at 5,3 and 6,3 kbit/s".
+- [8] ITU-T Recommendation H.263: "Video coding for low bitrate communication".
+- [9] ITU-T Recommendation H.261: "Video CODEC for audiovisual services at px64 kbit/s".
+- [10] ITU-T Recommendation H.324: "Terminal for low bitrate multimedia communication".
+- [11] 3GPP TS 26.110: "Codec for Circuit Switched Multimedia Telephony Service; General description".
+- [12] 3GPP TR 26.911: "Codec for circuit switched multimedia telephony service; terminal implementor's Guide (Release 4)".
+- [13] ITU-T Recommendation X.691: "Information Technology - ASN.1 Encoding Rules - Specification of Packed Encoding Rules (PER)".
+- [14] ISO/IEC 14496-2: "Information technology - Coding of audio-visual objects - Part 2: Visual".
+- [15] 3GPP TS 26.071: "General description".
+- [16] 3GPP TS 26.090: "Transcoding functions".
+
+- [17] 3GPP TS 26.073: "Adaptive Multi-Rate (AMR); ANSI C source code".
+- [18] 3GPP TS 26.171: "AMR Wideband Speech codec; General Description".
+- [19] ITU-T Recommendation H.264 (2003): "Advanced video coding for generic audiovisual services" | ISO/IEC 14496-10:2003: "Information technology – Coding of audio-visual objects – Part 10: Advanced Video Coding".
+- [20] ITU-T Recommendation H.241 (2003): "Extended video procedures and control signals for H.300 series terminals".
+- [21] ITU-T Recommendation G.722.2 Annex F (2002): "AMR-WB usage in H.245".
+- [22] 3GPP TS 26.201 : "Adaptive Multi-Rate – Wideband (AMR-WB) speech codec ; Frame Structure."
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply:
+
+**H.324:** ITU-T H.324 [10] with annex C
+
+**3G-324M terminal:** based on ITU-T H.324 [10] recommendation modified by 3GPP for purposes of 3GPP circuit switched network based video telephony
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|        |                              |
+|--------|------------------------------|
+| AMR    | Adaptive Multi-Rate          |
+| AMR-WB | AMR Wide-Band                |
+| AVC    | Advanced Video Codec         |
+| FLC    | Fixed Length Code            |
+| RVLC   | Reverse Variable Length Code |
+| DP     | Data Partitioning            |
+| RM     | Resynchronization Marker     |
+| MCU    | Multipoint Control Unit      |
+
+# --- 4 General
+
+The present document contains any deviations to ITU-T H.324 [10] required for the specification of 3G-324M Terminals.
+
+# --- 5 Document structure
+
+The structure of H.324 [10] is followed in the present document. Where there are no differences in a specific section, that section is skipped. Where differences are minor, only the differences are described. Where major differences exist, the section is rewritten in the present document. It is important to note that for wireless terminals, Annex C of H.324 [10] supersedes respective portions of the main body of H.324 [10] For the present document, these modifications are treated as if they are part of the main body of H.324 [10] Therefore, a reader must keep in mind both the main body and Annex C of H.324 [10] when reading the present document.
+
+# 6 Functional requirements
+
+## 6.1 Required elements
+
+3G-324M implementations are not required to have each functional element except a wireless interface, H.223 [1] with Annex A and B multiplex, and H.245 [6] version 3 or later versions for system control protocol.
+
+3G-324M terminals offering audio communication shall support the AMR audio codec. Support for G.723.1 [7] is not mandatory, but recommended.
+
+3G-324M terminals offering video communication shall support the H.263 [8] video codec. Support for MPEG-4 simple profile and H.261 [9] is optional.
+
+3G-324M terminals shall support H.223 [1] with annex A and annex B.
+
+3G-324M terminals shall support at least 32 kbit/s minimum bit rate at the mux to wireless network interface.
+
+## 6.2 Information streams
+
+V.25ter discussion does not apply.
+
+## 6.3 Modem
+
+Does not apply.
+
+## 6.4 Multiplex
+
+3G-324M terminals shall support H.223 [1] with annex A and annex B. All other aspects shall follow H.324 [10] with annex C. H.223 [1] Annex C and D are optional.
+
+## 6.5 Control channel
+
+No differences with H.324 [10].
+
+Should it not be possible to signal an element of the 3G-324M terminal using a published version of H.245 [6], a procedure will be defined here.
+
+## 6.6 Video channels
+
+Support for H.261 [9] is optional.
+
+Support for MPEG-4 Visual is optional. When supported, MPEG-4 Visual codecs shall support Simple Profile @ Level 0. The FLC code 0000 1000 in Table G-1 – "FLC table for profile\_and\_level\_indication" in ISO/IEC 14496-2 [14] is assigned to it. Additional information can be found in [14].
+
+MPEG-4 Visual Simple Profile @ level 0 provides error concealment as part of the simple profile through Data Partitioning (DP), Reversible Variable Length Coding (RVLC), Resynchronization Marker (RM) and header extension code. MPEG-4 Visual is baseline compatible with H.263 [8].
+
+When opening a logical channel for MPEG-4 Visual, configuration information (Visual Object Sequence Header, Visual Object Header, and Video Object Layer Header) shall be sent in the decoderConfigurationInformation parameter. The same information shall also be sent in the MPEG-4 video bitstream. If the operational mode of MPEG-4 Visual encoder needs to be changed, the existing MPEG-4 video logical channel shall be closed and H.245 [6] procedures for opening a new MPEG-4 video logical channel shall be started. The new operational mode shall be indicated in the parameters of the new logical channel.
+
+Support for H.264 (MPEG-4 AVC) [19] is optional. When supported, H.264 codecs shall support Baseline level 1, without requirements on output timing conformance (Annex C of [19]).
+
+Support for H.264 [19] shall be signalled according to H.241 chapter 8 "Capability Exchange signalling" [20].
+
+When opening a logical channel for H.264 [19], initial sequence parameter set(s) and picture parameter set(s) should be sent in a H.264 DecoderConfigurationInformation (DCI) defined in Table 1 below, amending H.241 parameters [20]. Additionally, decoder capabilities may be sent in a H.264 AcceptRedundantSlices and a H.264 ProfileIOP defined in Table 2 and 3 below, amending H.241 parameters [20].
+
+NOTE: The H.264 DCI parameter can also be used when either party signals a H.245 [6] MasterSlaveDetermination terminalType parameter greater than 128, such as e.g. a Multipoint Conference Unit (MCU).
+
+A sequence parameter set or a picture parameter set with a particular value of seq\_parameter\_set\_id or pic\_parameter\_set\_id, respectively, sent in the H.264 [19] DCI shall be identical to the earliest occurrence of the sequence parameter set or picture parameter set with the same value of seq\_parameter\_set\_id or pic\_parameter\_set\_id, respectively, sent in the H.264 bitstream.
+
+If DCI was used when a H.264 [19] logical channel was opened and H.264 sequence parameter sets need to be changed or new sets need to be added during the session, the existing H.264 logical channel shall be closed and H.245 [6] procedures for opening a new H.264 logical channel shall be started, in which sequence parameter set(s) and picture parameter set(s) shall be sent in a DCI. Each sequence parameter set of H.264 [19] shall contain the vui\_parameters syntax structure including the num\_reorder\_frames syntax element set equal to 0.
+
+If H.264 picture parameter sets need to be changed or new sets need to be added during a session, it may be done either by opening a new logical channel using the same procedure as described above or within the current channel, by including picture parameter set NAL units directly in the bitstream.
+
+**Table 1 / TS 26.111 – H.264 Capability Parameter – DecoderConfigurationInformation (DCI)**
+
+|                            |                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Parameter name             | DecoderConfigurationInformation                                                                                                                                                                                                                                                                                                                                                                                                           |
+| Parameter description      | This is a nonCollapsing GenericParameter.<br><br>DecoderConfigurationInformation indicates how to configure the decoder for a particular H.264 video sequence [19]. It contains sequence parameter set NAL units, picture parameter set NAL units, or both, using the byte stream format specified in Annex B/H.264, separating NAL units with a start code. The use of a start code before the first parameter set NAL unit is optional. |
+| Parameter identifier value | 43                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| Parameter status           | Optional. Shall not be present for Capability Exchange and Mode Request. May be present exactly once for Logical Channel Signalling.                                                                                                                                                                                                                                                                                                      |
+| Parameter type             | OctetString                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| Supersedes                 | -                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+
+A decoder may indicate its' capability to make use of H.264 redundant slices by the following parameter.
+
+**Table 2 / TS 26.111 – H.264 Capability Parameter – AcceptRedundantSlices**
+
+|                            |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Parameter name             | AcceptRedundantSlices                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| Parameter description      | <p>This is a collapsing GenericParameter.</p> <p>AcceptRedundantSlices indicates the capability to use H.264 redundant slices and corresponds to the MIME video/H264 parameter "redundant-pic-cap".</p> <p>When False or when the parameter is not present, it indicates that the receiver makes no attempt to use redundant coded pictures to correct incorrectly decoded primary coded pictures and a sender should not send redundant slices.</p> <p>When True, it indicates that the receiver is capable of decoding any such redundant slice that covers a corrupted area in a primary decoded picture (at least partly), and a sender may send redundant slices.</p> <p>When using a H.264 profile (or subset of a profile as indicated by the H.264 ProfileIOP parameter defined in Table 3) and level that disallows the use of redundant slices, this parameter shall be ignored.</p> |
+| Parameter identifier value | 44                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| Parameter status           | Optional. May be present exactly once for Capability Exchange Signalling.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| Parameter type             | Logical                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| Supersedes                 | -                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+
+NOTE: An encoder should only code redundant slices if it knows that the far-end decoder makes use of this feature. Encoders should also pay attention to potential implications on end-to-end delay.
+
+A decoder may indicate additional limitations that only the common subset of the algorithmic features and limitations of the Baseline level 1 are supported by the following parameter.
+
+**Table 3 / TS 26.111 – H.264 Capability Parameter – ProfileIOP**
+
+|                            |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Parameter name             | ProfileIOP                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| Parameter description      | <p>ProfileIOP indicates that the capability to decode H.264 streams is limited to a common subset of the algorithmic features included in the indicated profile and level.</p> <p>This parameter is a Boolean array.</p> <p>bit 1 (value 128) is constraint_set0_flag.</p> <p>bit 2 (value 64) is constraint_set1_flag.</p> <p>bit 3 (value 32) is constraint_set2_flag.</p> <p>All other bits are reserved, shall be set to 0, and shall be ignored by receivers.</p> <p>constraint_set0_flag, constraint_set1_flag and constraint_set2_flag are defined in [18].</p> <p>As an example, a receiver indicating decoding support of the intersection of the baseline and main profile will signal value 11000000 (constraint_set0_flag = 1, constraint_set1_flag = 1, constraint_set2_flag = 0).</p> |
+| Parameter identifier value | 46                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| Parameter status           | Optional. May be present exactly once for Capability Exchange Signalling.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| Parameter type             | BooleanArray                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| Supersedes                 | -                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+
+A terminal supporting H.264 encoding should respond to all `videoFastUpdatePicture` commands received via the H.245 control channel. If an H.264 encoder responds to `videoFastUpdatePicture`, it shall use the procedure specified in subclause 6.2.2 of H.241.
+
+A terminal supporting H.264 shall start decoding immediately when it receives data (even if the stream does not start with an IDR access unit) or alternatively no later than it receives the next IDR access unit or the next recovery point SEI message, whichever is earlier in decoding order. The decoding process for a stream not starting with an IDR access unit shall be the same as for a valid H.264 bitstream. However, the client shall be aware that such a stream may contain references to picture not available in the decoded picture buffer. The display behaviour of the client is out of scope of this specification.
+
+NOTE: Terminals may use full-frame freeze and full-frame freeze release SEI messages of H.264 to control the display process.
+
+### 6.6.1 MPEG-4 interface to multiplex
+
+As H.263 [8] encoders align picture start codes with the start of an AL-SDU, the same concept applies to MPEG-4 encoders. The following are the requirements of the MPEG-4 interface to the H.223 [1] multiplex.
+
+- Each 3G-324M MPEG-4 encoder shall align each `visual_object_sequence_start_code` with the start of an AL-SDU.
+- Each 3G-324M MPEG-4 encoder shall align each `group_of_vop_start_code` (the beginning of a GOV field) with the start of an AL-SDU unless the GOV field immediately follows configuration information.
+- Each 3G-324M MPEG-4 encoder shall align each `vop_start_code` with the start of an AL-SDU unless the `vop_start_code` immediately follows configuration information or a GOV field.
+
+In these requirements, GOV stands for `Group_of_VideoObjectPlane()` and Configuration information consists of Visual Object Sequence Header, Visual Object Header, and Video Object Layer Header.
+
+### 6.6.2 H.264 (MPEG-4 AVC) interface to multiplex
+
+Shall conform to the byte stream format according to H.241 chapter 7.1.5 "Transport of H.264 streams in H.324 systems" [20].
+
+More strict alignment of AL-SDU and NAL units may optionally be used. To signal capability for and use of this mode, the generic parameter described in Table 3 shall be used, amending the H.264 Generic Capability in H.241 [20].
+
+**Table 3 / TS 26.111 – H.264 Capability Parameter – NalAlignedMode**
+
+|                            |                                                                                                                                                                                                                                                                                                                                                                                                                |
+|----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Parameter name             | NalAlignedMode                                                                                                                                                                                                                                                                                                                                                                                                 |
+| Parameter description      | This is a collapsing GenericParameter.<br><br>NalAlignedMode indicates that every AL-SDU carrying H.264 shall contain an integer number of NAL units and that the start of the AL-SDU shall be aligned with the start of a NAL. Individual NAL units within the AL-SDU shall be separated by start codes as described in Annex B/H.264. The use of a start code before the first NAL in an AL-SDU is optional. |
+| Parameter identifier value | 45                                                                                                                                                                                                                                                                                                                                                                                                             |
+| Parameter status           | Optional. May be present exactly once for Capability Exchange, Logical Channel, or Mode Request Signalling.                                                                                                                                                                                                                                                                                                    |
+| Parameter type             | Logical                                                                                                                                                                                                                                                                                                                                                                                                        |
+| Supersedes                 | -                                                                                                                                                                                                                                                                                                                                                                                                              |
+
+## 6.7 Audio channels
+
+AMR is the mandatory speech codec. Support for G.723.1 [7] is not mandatory, but recommended. Support for AMR-WB [18] is also recommended.
+
+When AMR-WB is supported, the AMR-WB speech data shall be carried in IF2 frame format as defined in Annex A of 3GPP TS 26.201 [22], and the signalling for AMR-WB shall be according to G.722.2 Annex F [21] with the following additional restrictions:
+
+- octetAlign shall be present
+- The following parameters are not compatible with IF2 frame format, and so shall not be used:
+  - crc
+  - robustSorting
+  - interleaving
+
+When both the receiving and transmitting terminals support multiple codecs in common, the use of AMR and AMR-WB is preferred:
+
+- If both the receiving and transmitting terminals support AMR and other codecs (e.g. G.723.1) but not AMR-WB, then AMR shall be used.
+- If both the receiving and transmitting terminals support AMR and other codecs including AMR-WB, either AMR or AMR-WB shall be used.
+
+Asymmetric configurations with one codec in one direction and another one in the other direction (e.g. AMR in one direction and AMR-WB in the other direction) are allowed, if supported by both terminals.
+
+This applies to connections without an Multipoint Control Unit (MCU).
+
+## 6.8 Data channels
+
+No differences with H.324 [10].
+
+# --- 7 Terminal procedures
+
+See 3GPP TS 26.110 [11].
+
+# --- 8 Optional enhancements
+
+No differences with H.324 [10].
+
+# --- 9 Interoperation with other terminals
+
+For further study.
+
+# --- 10 Multipoint considerations
+
+For further study.
+
+# --- 11 Maintenance
+
+No differences with H.324 [10].
+
+# Annex A (informative): Change History
+
+| History |           |        |                  |              |      |     |                                                                  |
+|---------|-----------|--------|------------------|--------------|------|-----|------------------------------------------------------------------|
+| TSG_#   | TSG_DOC   | SPEC   | VERS_CURRE<br>NT | VERS_<br>NEW | CR   | REV | SUBJECT                                                          |
+| SP-05   | SP-99359  | 26.111 | 3.0.1            | 3.0.2        | 001  |     | Changes to editorial notes.                                      |
+| SP-06   | SP-99434  | 26.111 | 3.0.2            | 3.1.0        | 002  | 2   | Specification of coding parameters for MPEG-4 video codec        |
+| SP-06   | SP-99514  | 26.111 | 3.0.2            | 3.1.0        | 003  |     | Transmission of MPEG-4 configuration information in 3G-324M      |
+| SP-08   | SP-00263  | 26.111 | 3.1.0            | 3.2.0        | 004  |     | Changes to editorial notes                                       |
+| SP-09   | SP-000396 | 26.111 | 3.2.0            | 3.3.0        | 006  |     | MPEG-4 interface to multiplex                                    |
+| SP-10   | SP-000653 | 26.111 | 3.3.0            | 3.4.0        | 005  | 1   | MPEG4 visual simple profile @ level 0                            |
+| SP-11   |           |        |                  | 4.0.0        |      |     | Version for Release 4                                            |
+| SP-16   |           | 26.111 | 4.0.0            | 5.0.0        |      |     | Version for Release 5                                            |
+| SP-20   | SP-030215 | 26.111 | 5.0.0            | 5.1.0        | 009  | 1   | Removal of Reference to TS 26.112                                |
+| SP-25   | SP-040659 | 26.111 | 5.1.0            | 6.0.0        | 010  | 3   | 3G-324M Improvements                                             |
+| SP-25   | SP-040648 | 26.111 | 5.1.0            | 6.0.0        | 011  | 1   | 3G-324M Improvements: Addition of optional AMR-WB support        |
+| SP-26   | SP-040842 | 26.111 | 6.0.0            | 6.1.0        | 012  | 1   | Addition of the missing signalling of H.264 decoder capabilities |
+| SP-26   | SP-040842 | 26.111 | 6.0.0            | 6.1.0        | 013  | 1   | Reference Corrections                                            |
+| SP-36   |           | 26.111 | 6.1.0            | 7.0.0        |      |     | Version for Release 7                                            |
+| SP-40   | SP-080247 | 26.111 | 7.0.0            | 7.1.0        | 0015 | 1   | Use of AMR-WB in 3G-324M                                         |
+| SP-42   |           | 26.111 | 7.1.0            | 8.0.0        |      |     | Version for Release 8                                            |
+| SP-46   |           | 26.111 | 8.0.0            | 9.0.0        |      |     | Version for Release 9                                            |
+| SP-51   |           | 26.111 | 9.0.0            | 10.0.0       |      |     | Version for Release 10                                           |
+| SP-57   |           | 26.111 | 10.0.0           | 11.0.0       |      |     | Version for Release 11                                           |
+| SP-65   |           | 26.111 | 11.0.0           | 12.0.0       |      |     | Version for Release 12                                           |
+| SP-70   |           | 26.111 | 12.0.0           | 13.0.0       |      |     | Version for Release 13                                           |
+
+| Change history |         |      |    |     |     |                                |             |
+|----------------|---------|------|----|-----|-----|--------------------------------|-------------|
+| Date           | Meeting | TDoc | CR | Rev | Cat | Subject/Comment                | New version |
+| 2017-03        | 75      |      |    |     |     | Version for Release 14         | 14.0.0      |
+| 2018-06        | 80      |      |    |     |     | Version for Release 14         | 15.0.0      |
+| 2020-07        | -       | -    | -  | -   | -   | Update to Rel-16 version (MCC) | 16.0.0      |
+| 2022-04        | -       | -    | -  | -   | -   | Update to Rel-17 version (MCC) | 17.0.0      |
+| 2024-03        | -       | -    | -  | -   | -   | Update to Rel-18 version (MCC) | 18.0.0      |

marked/Rel-18/26_series/26117/raw.md

@@ -0,0 +1,874 @@
+
+
+# 3GPP TS 26.117 V18.1.0 (2023-06) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 5G Media Streaming (5GMS); Speech and audio profiles (Release 18)** ---
+
+![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The 5G logo, featuring the text "5G" in a bold, black, sans-serif font. Above the "5G" text are three green, curved lines representing signal waves.
+
+5G logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, featuring the text "3GPP" in a stylized, bold, black font. The "3" and "G" are connected at the top, and the "P" has a small red signal wave icon at its base. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, all-caps, sans-serif font.
+
+3GPP logo
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                               |    |
+|---------------------------------------------------------------|----|
+| Foreword .....                                                | 5  |
+| 1 Scope.....                                                  | 7  |
+| 2 References.....                                             | 7  |
+| 3 Definitions of terms, symbols and abbreviations.....        | 9  |
+| 3.1 Terms.....                                                | 9  |
+| 3.2 Symbols.....                                              | 9  |
+| 3.3 Abbreviations .....                                       | 9  |
+| 4 Overview.....                                               | 9  |
+| 5 Media Capabilities .....                                    | 10 |
+| 5.1 Introduction .....                                        | 10 |
+| 5.2 Decoding Capabilities .....                               | 10 |
+| 5.3 Encoding Capabilities .....                               | 10 |
+| 6 Operation Points.....                                       | 11 |
+| 6.1 Introduction .....                                        | 11 |
+| 6.2 Speech Operation Points .....                             | 11 |
+| 6.2.1 Introduction .....                                      | 11 |
+| 6.2.2 AMR.....                                                | 12 |
+| 6.2.2.1 Bitstream Encoding Requirements .....                 | 12 |
+| 6.2.2.2 Receiver Requirements.....                            | 12 |
+| 6.2.2.3 Sender Requirements .....                             | 12 |
+| 6.2.3 AMR-WB .....                                            | 12 |
+| 6.2.3.1 Bitstream Requirements.....                           | 12 |
+| 6.2.3.2 Receiver Requirements.....                            | 12 |
+| 6.2.3.3 Sender Requirements .....                             | 12 |
+| 6.2.4 EVS.....                                                | 12 |
+| 6.2.4.1 Bitstream Encoding Requirements .....                 | 12 |
+| 6.2.4.2 Receiver Requirements.....                            | 13 |
+| 6.2.4.3 Sender Requirements .....                             | 13 |
+| 6.3 Audio Operation Points.....                               | 13 |
+| 6.3.1 Introduction .....                                      | 13 |
+| 6.3.2 eAAC+ stereo .....                                      | 13 |
+| 6.3.2.1 Bitstream Encoding Requirements .....                 | 13 |
+| 6.3.2.2 Receiver Requirements.....                            | 13 |
+| 6.3.2.3 Sender Requirements .....                             | 13 |
+| 6.3.3 AMR-WB+ .....                                           | 13 |
+| 6.3.3.1 Bitstream Encoding Requirements .....                 | 13 |
+| 6.3.3.2 Receiver Requirements.....                            | 14 |
+| 6.3.3.3 Sender Requirements .....                             | 14 |
+| 6.3.4 xHE-AAC stereo .....                                    | 14 |
+| 6.3.4.1 Bitstream Encoding Requirements .....                 | 14 |
+| 6.3.4.2 Receiver Requirements.....                            | 14 |
+| 6.3.4.3 Sender Requirements .....                             | 14 |
+| 7 Mapping to 5GMS delivery .....                              | 14 |
+| 7.1 Introduction .....                                        | 14 |
+| 7.2 AMR Media Profile.....                                    | 15 |
+| 7.2.1 Mapping to ISO BMFF .....                               | 15 |
+| 7.2.2 Media Profile Definition.....                           | 15 |
+| 7.2.2.1 CMAF Track Definition .....                           | 15 |
+| 7.2.2.2 CMAF Switching Set and Media Profile Definition ..... | 15 |
+| 7.2.2.3 Mapping to DASH Adaptation Set.....                   | 15 |
+| 7.2.2.4 Playback Requirements.....                            | 15 |
+| 7.2.2.5 Content Generation Requirements.....                  | 16 |
+| 7.3 AMR-WB Media Profile.....                                 | 16 |
+
+|                                                              |                                                       |           |
+|--------------------------------------------------------------|-------------------------------------------------------|-----------|
+| 7.3.1                                                        | Mapping to ISO BMFF .....                             | 16        |
+| 7.3.2                                                        | Media Profile Definition.....                         | 16        |
+| 7.3.2.1                                                      | CMAF Track Definition .....                           | 16        |
+| 7.3.2.2                                                      | CMAF Switching Set and Media Profile Definition ..... | 16        |
+| 7.3.2.3                                                      | Mapping to DASH Adaptation Set.....                   | 16        |
+| 7.3.2.4                                                      | Playback Requirements.....                            | 17        |
+| 7.3.2.5                                                      | Content Generation Requirements.....                  | 17        |
+| 7.4                                                          | EVS Media Profile .....                               | 17        |
+| 7.4.1                                                        | Mapping to ISO BMFF .....                             | 17        |
+| 7.4.2                                                        | Media Profile Definition.....                         | 18        |
+| 7.4.2.1                                                      | CMAF Track Definition .....                           | 18        |
+| 7.4.2.2                                                      | CMAF Switching Set and Media Profile Definition ..... | 18        |
+| 7.4.2.3                                                      | Mapping to DASH Adaptation Set.....                   | 18        |
+| 7.4.2.4                                                      | Playback Requirements.....                            | 18        |
+| 7.4.2.5                                                      | Content Generation Requirements.....                  | 19        |
+| 7.5                                                          | void.....                                             | 19        |
+| 7.6                                                          | eAAC+ stereo Media Profile.....                       | 19        |
+| 7.6.1                                                        | Void.....                                             | 19        |
+| 7.6.2                                                        | Media Profile Definition.....                         | 19        |
+| 7.6.2.1                                                      | CMAF Track Definition .....                           | 19        |
+| 7.6.2.2                                                      | CMAF Switching Set and Media Profile Definition ..... | 19        |
+| 7.6.2.3                                                      | Mapping to DASH Adaptation Set.....                   | 19        |
+| 7.6.2.4                                                      | Playback Requirements.....                            | 20        |
+| 7.6.2.5                                                      | Content Generation Requirements.....                  | 20        |
+| 7.7                                                          | AMR-WB+ Media Profiles .....                          | 20        |
+| 7.7.1                                                        | Mapping to ISO BMFF .....                             | 20        |
+| 7.7.2                                                        | Media Profile Definition.....                         | 21        |
+| 7.7.2.1                                                      | CMAF Track Definition .....                           | 21        |
+| 7.7.2.2                                                      | CMAF Switching Set and Media Profile Definition ..... | 21        |
+| 7.7.2.3                                                      | Mapping to DASH Adaptation Set.....                   | 21        |
+| 7.7.2.4                                                      | Playback Requirements.....                            | 21        |
+| 7.7.2.5                                                      | Content Generation Requirements.....                  | 22        |
+| 7.8                                                          | xHE-AAC Media Profile.....                            | 22        |
+| 7.8.1                                                        | CMAF Track Definition .....                           | 22        |
+| 7.8.2                                                        | CMAF Switching Set and Media Profile Definition ..... | 22        |
+| 7.8.3                                                        | Mapping to DASH Adaptation Set.....                   | 22        |
+| 7.8.4                                                        | Playback Requirements .....                           | 23        |
+| 7.8.5                                                        | Content Generation Requirements .....                 | 23        |
+| <b>Annex A (informative): Registration Information .....</b> |                                                       | <b>24</b> |
+| A.1                                                          | 3GPP Registered URIs.....                             | 24        |
+| <b>Annex B (informative): Change history .....</b>           |                                                       | <b>25</b> |
+
+# Foreword
+
+This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+In the present document, modal verbs have the following meanings:
+
+- shall** indicates a mandatory requirement to do something
+- shall not** indicates an interdiction (prohibition) to do something
+
+The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+- should** indicates a recommendation to do something
+- should not** indicates a recommendation not to do something
+- may** indicates permission to do something
+- need not** indicates permission not to do something
+
+The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
+
+- can** indicates that something is possible
+- cannot** indicates that something is impossible
+
+The constructions "can" and "cannot" are not substitutes for "may" and "need not".
+
+- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+In addition:
+
+**is** (or any other verb in the indicative mood) indicates a statement of fact
+
+**is not** (or any other negative verb in the indicative mood) indicates a statement of fact
+
+The constructions "is" and "is not" do not indicate requirements.
+
+# --- 1 Scope
+
+The present document specifies speech and audio media capabilities, operation points and media profiles for 5G Media Streaming in the context of 3GPP services and deployments. Speech and audio media capabilities, operation points and media profiles are also provided for usage in other streaming applications.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 26.501: "5G Media Streaming (5GMS); General description and architecture".
+- [3] 3GPP TS 26.071: "Mandatory Speech Codec speech processing functions; AMR Speech CODEC; General description".
+- [4] 3GPP TS 26.090: "Mandatory Speech Codec speech processing functions; Adaptive Multi-Rate (AMR) speech codec; Transcoding functions".
+- [5] 3GPP TS 26.073: "ANSI-C code for the Adaptive Multi Rate (AMR) speech codec".
+- [6] 3GPP TS 26.104: "ANSI-C code for the floating-point Adaptive Multi Rate (AMR) speech codec".
+- [7] 3GPP TS 26.093: "Mandatory speech codec speech processing functions; Adaptive Multi-Rate (AMR) speech codec; Source controlled rate operation".
+- [8] 3GPP TS 26.171: "Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec; General description".
+- [9] 3GPP TS 26.190: "Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec; Transcoding functions".
+- [10] 3GPP TS 26.173: "ANSI-C code for the Adaptive Multi Rate - Wideband (AMR-WB) speech codec".
+- [11] 3GPP TS 26.204: "Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec; ANSI-C code".
+- [12] 3GPP TS 26.193: "Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec; Source controlled rate operation".
+- [13] 3GPP TS 26.441: "Codec for Enhanced Voice Services (EVS); General Overview".
+- [14] 3GPP TS 26.442: "Codec for Enhanced Voice Services (EVS); ANSI C code (fixed-point)".
+- [15] 3GPP TS 26.443: "Codec for Enhanced Voice Services (EVS); ANSI C code (floating-point)".
+- [16] 3GPP TS 26.445: "Codec for Enhanced Voice Services (EVS); Detailed Algorithmic Description".
+- [17] 3GPP TS 26.446: "Codec for Enhanced Voice Services (EVS); Adaptive Multi-Rate - Wideband (AMR-WB) backward compatible functions".
+
+- [18] 3GPP TS 26.450: "Codec for Enhanced Voice Services (EVS); Discontinuous Transmission (DTX)".
+- [19] 3GPP TS 26.401: "General audio codec audio processing functions; Enhanced aacPlus general audio codec; General description".
+- [20] 3GPP TS 26.402: "General audio codec audio processing functions; Enhanced aacPlus general audio codec; Additional decoder tools".
+- [21] 3GPP TS 26.403: "General audio codec audio processing functions; Enhanced aacPlus general audio codec; Encoder specification; Advanced Audio Coding (AAC) part".
+- [22] 3GPP TS 26.404: "General audio codec audio processing functions; Enhanced aacPlus general audio codec; Enhanced aacPlus encoder Spectral Band Replication (SBR) part".
+- [23] 3GPP TS 26.405: "General audio codec audio processing functions; Enhanced aacPlus general audio codec; Encoder specification parametric stereo part".
+- [24] 3GPP TS 26.410: "General audio codec audio processing functions; Enhanced aacPlus general audio codec; Floating-point ANSI-C code".
+- [25] 3GPP TS 26.411: "General audio codec audio processing functions; Enhanced aacPlus general audio codec; Fixed-point ANSI-C code".
+- [26] 3GPP TS 26.290: "Audio codec processing functions; Extended Adaptive Multi-Rate - Wideband (AMR-WB+) codec; Transcoding functions".
+- [27] 3GPP TS 26.304: "Extended Adaptive Multi-Rate - Wideband (AMR-WB+) codec; Floating-point ANSI-C code".
+- [28] 3GPP TS 26.273: "ANSI-C code for the fixed-point Extended Adaptive Multi-Rate - Wideband (AMR-WB+) speech codec".
+- [29] 3GPP TS 26.244: "Transparent end-to-end streaming service; 3GPP file format (3GP)".
+- [30] ISO/IEC 23000-19:2023 "Information Technology Multimedia Application Format (MPEG-A) – Part 19: Common Media Application Format (CMAF) for segmented media".
+- [31] ISO/IEC 23009-1:2022: "Information technology -- Dynamic adaptive streaming over HTTP (DASH) -- Part 1: Media presentation description and segment formats."
+- [32] CTA-5003: "Web Application Video Ecosystem (WAVE): Device Playback Capabilities Specification" available here <https://cdn.cta.tech/cta/media/media/resources/standards/pdfs/cta-5003-final.pdf>.
+- [33] 3GPP TS 26.244: "Transparent end-to-end streaming service; 3GPP file format (3GP)".
+- [34] 3GPP TS 26.452: "Codec for Enhanced Voice Services (EVS); ANSI C code; Alternative fixed-point using updated basic operators".
+- [35] 3GPP TS 26.447: "Codec for Enhanced Voice Services (EVS); Error concealment of lost packets".
+- [36] 3GPP TS 26.511: "5G Media Streaming (5GMS); Profiles, Codecs and Formats".
+- [37] ISO/IEC 23003-3: "Information technology — MPEG audio technologies — Part 3: Unified speech and audio coding".
+- [38] ISO/IEC 23003-4: "Information technology — MPEG audio technologies — Part 4: Dynamic range control"
+
+# 3 Definitions of terms, symbols and abbreviations
+
+## 3.1 Terms
+
+For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+**Bitstream:** A media bitstream that conforms to an audio/speech encoding format and certain Operation Point.
+
+**Media Profile:** A combination of a Bitstream encapsulated into a media container suitable for 5G Media Streaming Delivery.
+
+**Operation Point:** A collection of discrete combinations of different content formats and the encoding format.
+
+**Receiver:** A receiver that can decode and render any bitstream that is conforming to a certain Operation Point.
+
+**Sender:** An entity that can process and encode formats associated to an Operation Point.
+
+## 3.2 Symbols
+
+Void.
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+|          |                                                      |
+|----------|------------------------------------------------------|
+| AAC      | Advanced Audio Coding                                |
+| ABR      | Adaptive BitRate                                     |
+| AMR      | Adaptive MultiRate                                   |
+| CMAF     | Common Media Application Format                      |
+| DASH     | Dynamic Adaptive Streaming over HTTP                 |
+| DRC      | Dynamic Range Control DTX Discontinuous Transmission |
+| EVS      | Enhanced Voice Services                              |
+| ISO BMFF | ISO Based Media File Format                          |
+| HTTP     | Hyper Text Transfer Protocol                         |
+| SBR      | Spectral Band Replication                            |
+| URN      | Universal Resource Name                              |
+| WAVE     | Web Application Video Ecosystem                      |
+
+# 4 Overview
+
+The speech and audio media capabilities defined in this specification are primarily introduced in order to be used as content format in the context of 5G Media Streaming, but not restricted to this use case. Parameters for audio encoder/decoder, content format and transport are defined.
+
+The present document defines:
+
+- Media decoding capabilities: the requirements for a receiver in terms of decoding
+- Media encoding capabilities: the requirements for a sender in terms of encoding
+- Operation Points: A collection of discrete combinations of different content formats and the encoding formats. Operation Points are supported by
+  - Bitstream Requirements: A media bitstream that conforms to an audio or speech encoding format and certain Operation Point.
+
+- Receiver Requirements: A function that can decode and playback any Bitstream that is conforming to a certain Operation Point in real-time.
+  - Sender Requirements: A function that can process and encode any Bitstream that is conforming to a certain Operation Point in real-time.
+- 
+- The integration of each Operation Point in 5G Media Streaming as defined in TS 26.501 [2] and TS 26.511 [36].
+
+# 5 Media Capabilities
+
+## 5.1 Introduction
+
+This clause documents speech and audio media capabilities in terms of decoding capabilities.
+
+## 5.2 Decoding Capabilities
+
+The following speech media decoding capabilities are defined:
+
+- *AMR*: All decoding requirements for the AMR speech codec as specified in 3GPP TS 26.071 [3], 3GPP TS 26.090 [4], 3GPP TS 26.073 [5] and 3GPP TS 26.104 [6]) including all 8 modes and source-controlled rate operation 3GPP TS 26.093 [7].
+- *AMR-WB*: All decoding requirements for the AMR-WB codec as specified in 3GPP TS 26.171 [8], 3GPP TS 26.190 [9], 3GPP TS 26.173 [10] and 3GPP TS 26.204 [11] including all 9 modes and source-controlled rate operation 3GPP TS 26.193 [12].
+- *EVS*: All decoding requirements for the EVS codec as specified in 3GPP TS 26.441 [13], 3GPP TS 26.445 [16], 3GPP TS 26.442 [14] and 3GPP TS 26.443 [15] as described below including functions for backwards compatibility with AMR-WB (3GPP TS 26.446 [17]) and discontinuous transmission (3GPP TS 26.450 [18]).
+
+The following audio media decoding capabilities are defined:
+
+- *eAAC+*: All decoding requirements for the eAAC+ audio codec as specified in 3GPP TS 26.401 [19], 3GPP TS 26.402 [20], 3GPP TS 26.410 [24] and 3GPP TS 26.411 [25].
+- *AMR-WB+*: All decoding requirements for the AMR-WB+ audio codec as specified in 3GPP TS 26.290 [26], 3GPP TS 26.304 [27] and 3GPP TS 26.273 [28].
+- *xHE-AAC stereo*: All decoding requirements for the *xHE-AAC stereo* audio codec as specified in the MPEG-D USAC "Extended high efficiency AAC profile" as defined in ISO/IEC 23003-3 [37] as well as all processing requirements applicable to the MPEG-D DRC loudness control profile and to the dynamic range control profile, level 1 or higher, as specified in ISO/IEC 23003-4 [38].
+
+NOTE: xHE-AAC® is a registered trademark of Fraunhofer in Germany and other countries and is used with Fraunhofer's permission.
+
+## 5.3 Encoding Capabilities
+
+The following speech media encoding capabilities are defined:
+
+- *AMR*: The encoding requirements for the AMR speech codec as specified in 3GPP TS 26.401 [19], clause 7, as well as 3GPP TS 26.403 [21], 3GPP TS 26.404 [22] and 3GPP TS 26.405 [23].
+- *AMR-WB*: The encoding requirements for the AMR-WB by one of the following methods:
+  - according to 3GPP TS 26.173 [10]
+  - according to 3GPP TS 26.204 [11];
+  - the AMR-WB IO mode according to TS 26.442 [14] and TS 26.443 [15],
+
+- the AMR-WB IO mode according to TS 26.452 [34].
+- *EVS*: The encoding requirements for the EVS codec by one of the following methods:
+  - TS 26.442 [14] and TS 26.443 [15] encoding functions; or
+  - TS 26.452 [34] encoding functions.
+
+The following audio media encoding capabilities are defined:
+
+- *eAAC+*: The encoding requirements for the AAC+ audio codec as specified 3GPP TS 26.401 [19], clause 7, as well as 3GPP TS 26.403 [21], 3GPP TS 26.404 [22] and 3GPP TS 26.405 [23].
+- *AMR-WB+*: The encoding requirements for the AMR-WB+ audio codec by one of the following methods
+  - according to 3GPP TS 26.273 [28]; or
+  - according to 3GPP TS 26.304 [27].
+- *xHE-AAC stereo*: All encoding requirements for the *xHE-AAC stereo* audio codec as specified in the MPEG-D USAC "Baseline USAC" profile as defined in ISO/IEC 23003-3 [37] and with the additional requirements that all encoded media contains the required metadata sets conforming to the MPEG-D DRC loudness control profile or to the dynamic range control profile, level 1 or higher, as specified in ISO/IEC 23003-4 [38].
+
+# 6 Operation Points
+
+## 6.1 Introduction
+
+The speech and audio Operation Points defined in this clause are primarily introduced in order to be used as content format in the context of 5G Media Streaming, but not restricted to this use case.
+
+An operation point is a combination of rendering formats and media decoding capabilities.
+
+For each Operation Point, Bitstream and Receiver requirements are detailed in the remainder of clause 6.
+
+Table 6.1 provides an overview of the Operation Points defined in the present document.
+
+**Table 6.1: Speech and Audio Operation Points**
+
+| Operation Point name | Format Properties                     | Decoding and Encoding Capabilities | Reference |
+|----------------------|---------------------------------------|------------------------------------|-----------|
+| AMR speech           | Sampling frequency: 8 kHz             | <i>AMR</i>                         | 6.2.2     |
+| AMR-WB speech        | Sampling frequency: 16 kHz            | <i>AMR-WB</i>                      | 6.2.3     |
+| EVS mono             | Sampling frequency: 8, 16, 32, 48 kHz | <i>EVS</i>                         | 6.2.4     |
+| eAAC+ stereo         | Sampling frequency: 32, 44.1, 48 kHz  | <i>eAAC+</i>                       | 6.3.2     |
+| AMR-WB+              | Sampling frequency: 8, 16, 32, 48 kHz | <i>AMR-WB+</i>                     | 6.3.3     |
+| xHE-AAC stereo       | Sampling frequency: 32, 44.1, 48 kHz  | <i>xHE-AAC stereo</i>              | 6.3.4     |
+
+## 6.2 Speech Operation Points
+
+### 6.2.1 Introduction
+
+This clause defines speech operation points. For each operation point, the requirements for the bitstream as well as for the receiver are defined.
+
+### 6.2.2 AMR
+
+#### 6.2.2.1 Bitstream Encoding Requirements
+
+The following requirements apply to the **AMR** Operation Point.
+
+- The sampling frequency shall be 8 kHz.
+- The bitstream shall be encoded according to either 3GPP TS 26.073 [5] or 3GPP TS 26.104 [6].
+
+Note that the bitstream produced by the AMR encoder consists of 20ms encoded speech frames.
+
+#### 6.2.2.2 Receiver Requirements
+
+Receivers conforming to the **AMR** Operation Point shall support the *AMR* speech media decoding capability according to clause 5.2 and shall support playback of the decoded signal.
+
+#### 6.2.2.3 Sender Requirements
+
+Senders conforming to the **AMR** Operation Point shall support the *AMR* speech media encoding capability according to clause 5.3 in real-time for any speech source format with sampling frequency 8kHz.
+
+### 6.2.3 AMR-WB
+
+#### 6.2.3.1 Bitstream Requirements
+
+The following requirements apply to the **AMR-WB** Operation Point.
+
+- The sampling frequency shall be 16 kHz.
+- The bitstream shall be encoded by one of the following methods:
+  - according to 3GPP TS 26.173 [10]
+  - according to 3GPP TS 26.204 [11];
+  - the AMR-WB IO mode according to TS 26.442 [14] and TS 26.443 [15],
+  - the AMR-WB IO mode according to TS 26.452 [34].
+
+Note that the bitstream produced by the AMR-WB encoder consists of 20 ms encoded speech frames.
+
+#### 6.2.3.2 Receiver Requirements
+
+Receivers conforming to the **AMR-WB** Operation Point shall support the *AMR-WB* speech media decoding capability according to clause 5.2 and shall support playback of the decoded signal.
+
+#### 6.2.3.3 Sender Requirements
+
+Senders conforming to the **AMR-WB** Operation Point shall support the *AMR-WB* speech media encoding capability according to clause 5.3 in real-time for any speech source format with sampling frequency 16kHz.
+
+### 6.2.4 EVS
+
+#### 6.2.4.1 Bitstream Encoding Requirements
+
+The following requirements apply to the **EVS** Operation Point:
+
+- The sampling frequency shall be one of the following: 8, 16, 32, 48 kHz.
+
+- The bitstream shall be encoded according to one of the following methods
+  - TS 26.442 [14] and TS 26.443 [15] encoding functions; or
+  - TS 26.452 [34] encoding functions.
+
+Note that the bitstream produced by the EVS encoder consists of 20ms encoded speech frames.
+
+#### 6.2.4.2 Receiver Requirements
+
+Receivers conforming to the **EVS** Operation Point shall support the *EVS* speech media decoding capability according to clause 5.2 and shall support playback of the decoded signal.
+
+#### 6.2.4.3 Sender Requirements
+
+Senders conforming to the **EVS** Operation Point shall support the *EVS* speech media encoding capability according to clause 5.3 in real-time for any speech source format with sampling frequency 8, 16, 32, 48 kHz.
+
+## 6.3 Audio Operation Points
+
+### 6.3.1 Introduction
+
+This clause defines audio operation points. For each operation point, the requirements for the bitstream as well as for the receiver are defined.
+
+### 6.3.2 eAAC+ stereo
+
+#### 6.3.2.1 Bitstream Encoding Requirements
+
+The following requirements apply to the **eAAC+ stereo** Operation Point.
+
+- The sampling frequency shall be either 32 kHz, 44.1 kHz or 48 kHz.
+- The bitstream shall be encoded according to 3GPP TS 26.401 [19], clause 7, as well as 3GPP TS 26.403 [21], 3GPP TS 26.404 [22] and 3GPP TS 26.405 [23].
+
+NOTE: The specified eAAC+ encoder consists of AAC-LC with additional tools that can be enabled (SBR, PS and more), see [19].
+
+#### 6.3.2.2 Receiver Requirements
+
+Receivers conforming to the **eAAC+ stereo** Operation Point shall support the *eAAC+ stereo* media decoding capability according to clause 5.2 and shall support playback of the decoded signal.
+
+NOTE: The eAAC+ decoder supports decoding of streams encoded with AAC-LC or aacPlus, see [19].
+
+#### 6.3.2.3 Sender Requirements
+
+Senders conforming to the **eAAC+ stereo** Operation Point shall support the *eAAC+ stereo* audio media encoding capability according to clause 5.3 in real-time for any stereo audio source format with sampling frequency 32kHz, 44.1kHz, 48kHz.
+
+### 6.3.3 AMR-WB+
+
+#### 6.3.3.1 Bitstream Encoding Requirements
+
+The following requirements apply to the **AMR-WB+** Operation Point.
+
+- The sampling frequency shall be either 8, 16, 32 or 48 kHz.
+
+- The bitstream shall be encoded by one of the following methods
+  - according to 3GPP TS 26.273 [28]; or
+  - according to 3GPP TS 26.304 [27].
+
+#### 6.3.3.2 Receiver Requirements
+
+Receivers conforming to the **AMR-WB+** Operation Point shall support the *AMR-WB+* media decoding capability according to clause 5.2 and shall support playback of the decoded signal.
+
+#### 6.3.3.3 Sender Requirements
+
+Senders conforming to the **AMR-WB+** Operation Point shall support the *AMR-WB+* audio media encoding capability according to clause 5.3 in real-time for any stereo audio source format with sampling frequency 8, 16, 32 or 48 kHz.
+
+### 6.3.4 xHE-AAC stereo
+
+#### 6.3.4.1 Bitstream Encoding Requirements
+
+The following requirements apply to the **xHE-AAC stereo** Operation Point.
+
+- The sampling frequency shall be either 32 kHz, 44.1 kHz or 48 kHz.
+- The bitstream shall be encoded according to the MPEG-D USAC "Baseline USAC" profile as defined in ISO/IEC 23003-3 [37] and shall contain the metadata sets conforming to the MPEG-D DRC loudness control profile or to the dynamic range control profile, level 1 or higher, as specified in ISO/IEC 23003-4 [38].
+
+#### 6.3.4.2 Receiver Requirements
+
+Receivers conforming to the **xHE-AAC stereo** Operation Point shall support the *xHE-AAC stereo* media decoding capability according to clause 5.2 and shall support playback of the decoded signal.
+
+NOTE: The xHE-AAC decoder supports decoding of streams encoded with eAAC+ [19]. Therefore support of xHE-AAC stereo media decoding capabilities implies support of eAAC+ media decoding capabilities.
+
+#### 6.3.4.3 Sender Requirements
+
+Senders conforming to the **xHE-AAC stereo** Operation Point shall support the xHE-AAC audio media encoding capability according to clause 5.3 in real-time for any stereo audio source format with sampling frequency 32kHz, 44.1kHz, or 48kHz.
+
+# --- 7 Mapping to 5GMS delivery
+
+## 7.1 Introduction
+
+This clause defines the mapping of the Operation Points as defined in clause 6 to 5G Media Streaming delivery. In particular the following aspects are addressed:
+
+- Encapsulation of a bitstream into an ISO BMFF track.
+- Definition of media content and receivers conforming to media profile including:
+  - Encapsulation of a bitstream into a CMAF track
+  - Providing the content in a CMAF Switching Set
+  - Mapping to DASH-based distribution
+
+- Playback Requirements for a receiver conforming to this media profile
+
+## 7.2 AMR Media Profile
+
+### 7.2.1 Mapping to ISO BMFF
+
+If media is provided following the operation point **AMR** and is encapsulated in the ISO BMFF, then the file format track shall conform to the requirements of the codec entry 'samr' as defined in TS 26.244 [29].
+
+### 7.2.2 Media Profile Definition
+
+#### 7.2.2.1 CMAF Track Definition
+
+If media is provided following the operation point **AMR** and is encapsulated in a CMAF track, then the CMAF track shall conform to the requirements of the codec entry 'samr' as defined in TS 26.244 [29], the general CMAF Track constraints in ISO/IEC 23000-19 [30], clause 7 as well as the general audio track constraints defined in ISO/IEC 23000-19 [30], clause 10.
+
+#### 7.2.2.2 CMAF Switching Set and Media Profile Definition
+
+If media is provided following the operation point **AMR** and is provided in a CMAF Switching Set, then every CMAF track in the CMAF Switching Set shall conform to the requirements of the codec entry 'samr' as defined in TS 26.244 [29], the general CMAF Switching Set constraints in ISO/IEC 23000-19 [30], clause 7 as well as the general CMAF audio track Switching Set constraints defined in ISO/IEC 23000-19 [30], clause 10. A CMAF Switching Set following these requirements is defined as the CMAF AMR media profile 'camr'.
+
+#### 7.2.2.3 Mapping to DASH Adaptation Set
+
+If media is provided following the operation point **AMR** and is provided in a DASH Media Presentation in an Adaptation Set, then the Adaptation Set shall conform to the DASH profile for CMAF as defined in ISO/IEC 23009-1 [31]. The following parameters shall be present on Adaptation Set level and set:
+
+- @codecs is set to 'samr'
+- @mimeType is set to be compatible with "audio/mp4 profiles='camr'"
+- @audioSamplingRate is set to '8000'
+
+If the Adaptation Set conforms to the constraints for the **AMR** Operation Point as defined in this clause, then the @profiles parameter in the Adaptation Set may signal conformance to this Media Profile by using "urn:3GPP:audio:mp:amr".
+
+#### 7.2.2.4 Playback Requirements
+
+For a receiver supporting the **AMR** media profile the following applies:
+
+- It shall support the receiver requirements as documented in clause 6.2.2.2 for any CMAF Track conforming to the CMAF **AMR** media profile 'camr' as defined in clause 7.2.2.1.
+- It shall support the following playback requirements as documented in clause 8 of CTA-WAVE 5003 [32] for any content conforming to a CMAF Switching Set according to CMAF **AMR** media profile 'camr' as defined in clause 7.2.2.2, namely:
+  - 8.2 Sequential Track Playback
+  - 8.3 Random Access to Fragment
+  - 8.4 Random Access to Time
+  - 8.5 Switching Set Playback
+
+- 8.6 Regular Playback of Chunked Content
+- 8.7 Regular Playback of Chunked Content, non-aligned append
+- It should support the following playback requirements as documented in clause 8 of CTA-WAVE 5003 [29] for any content conforming to a CMAF Switching Set according to CMAF AMR media profile 'camr' as defined in clause 7.2.2.2, namely:
+  - 8.9 Out-Of-Order Loading
+  - 8.10 Overlapping Fragments
+  - 8.12 Playback of Encrypted Content
+
+#### 7.2.2.5 Content Generation Requirements
+
+For a transmitter supporting the AMR media profile the following applies:
+
+- It shall support all media encoding capabilities for AMR as defined in clause 5.3.
+- It shall support the sender requirements for AMR as defined in clause 6.2.2.3.
+- It shall support the generation of a CMAF Track as defined in clause 7.2.2.2 that conforms to the CMAF Media Profile 'camr' as defined in clause 7.2.2.3.
+- If used for Adaptive Bit Rate (ABR) distribution, it shall support the generation of a CMAF Switching Set as defined in clause 7.2.2.4.
+
+## 7.3 AMR-WB Media Profile
+
+### 7.3.1 Mapping to ISO BMFF
+
+If media is provided following the operation point **AMR-WB** and is encapsulated in the ISO BMFF, then the file format track shall conform to the requirements of the codec entry 'sawb' as defined in TS 26.244 [29].
+
+### 7.3.2 Media Profile Definition
+
+#### 7.3.2.1 CMAF Track Definition
+
+If media is provided following the operation point **AMR-WB** and is encapsulated in a CMAF track, then the CMAF track shall conform to the requirements of the codec entry 'sawb' as defined in TS 26.244 [29], the general CMAF Track constraints in ISO/IEC 23000-19, clause 7 as well as the general audio track constraints defined in ISO/IEC 23000-19 [30], clause 10.
+
+#### 7.3.2.2 CMAF Switching Set and Media Profile Definition
+
+If media is provided following the operation point **AMR-WB** and is provided in a CMAF Switching Set, then every CMAF track in the CMAF Switching Set shall conform to the requirements of the codec entry 'sawb' as defined in TS 26.244 [29], the general CMAF Switching Set constraints in ISO/IEC 23000-19 [30], clause 7 as well as the general CMAF audio track Switching Set constraints defined in ISO/IEC 23000-19 [30], clause 10. A CMAF Switching Set following these requirements is defined as the CMAF AMR-WB media profile 'camw'.
+
+#### 7.3.2.3 Mapping to DASH Adaptation Set
+
+If media is provided following the operation point **AMR-WB** and is provided in a DASH Media Presentation in an Adaptation Set, then the Adaptation Set shall conform to the DASH profile for CMAF as defined in ISO/IEC 23009-1 [31]. The following parameters shall be present on Adaptation Set level and set:
+
+- @codecs is set to 'sawb'
+
+- `@mimeType` is set to be compatible with "audio/mp4 profiles='camw'"
+- `@audioSamplingRate` is set to '16000'
+
+If the Adaptation Set conforms to the constraints for the **AMR-WB** Operation Point as defined in this clause, then the `@profiles` parameter in the Adaptation Set may signal conformance to this Media Profile by using "urn:3GPP:audio:mp:amr-wb".
+
+#### 7.3.2.4 Playback Requirements
+
+For a receiver supporting the AMR-WB media profile the following applies:
+
+- It shall support the receiver requirements as documented in clause 6.2.3.2 for any CMAF Track conforming to the CMAF AMR-WB media profile 'camw' as defined in clause 7.3.2.2.
+- It shall support the following playback requirements as documented in clause 8 of CTA-WAVE 5003 [32] for any content conforming to a CMAF Switching Set according to CMAF AMR-WB media profile 'camw' as defined in clause 7.3.2.2, namely:
+  - 8.2 Sequential Track Playback
+  - 8.3 Random Access to Fragment
+  - 8.4 Random Access to Time
+  - 8.5 Switching Set Playback
+  - 8.6 Regular Playback of Chunked Content
+  - 8.7 Regular Playback of Chunked Content, non-aligned append
+- It should support the following playback requirements as documented in clause 8 of CTA-WAVE 5003 [32] for any content conforming to a CMAF Switching Set according to CMAF AMR-WB media profile 'camw' as defined in clause 7.3.2.2, namely:
+  - 8.9 Out-Of-Order Loading
+  - 8.10 Overlapping Fragments
+  - 8.12 Playback of Encrypted Content
+
+#### 7.3.2.5 Content Generation Requirements
+
+For a transmitter supporting the AMR-WB media profile the following applies:
+
+- It shall support all media encoding capabilities for AMR-WB as defined in clause 5.3.
+- It shall support the sender requirements for AMR-WB as defined in clause 6.2.3.3.
+- It shall support the generation of a CMAF Track as defined in clause 7.3.2.2 that conforms to the CMAF Media Profile 'camw' as defined in clause 7.3.2.3.
+- If used for Adaptive Bit Rate (ABR) distribution, it shall support the generation of a CMAF Switching Set as defined in clause 7.3.2.4.
+
+## 7.4 EVS Media Profile
+
+### 7.4.1 Mapping to ISO BMFF
+
+If media is provided following the operation point **EVS** and is encapsulated in the ISO BMFF, then the file format track shall conform to the requirements of the codec entry 'sevs' as defined in TS 26.244 [29].
+
+### 7.4.2 Media Profile Definition
+
+#### 7.4.2.1 CMAF Track Definition
+
+If media is provided following the operation point **EVS** and is encapsulated in a CMAF track, then the CMAF track shall conform to the requirements of the codec entry 'sevs' as defined in TS 26.244 [29], the general CMAF Track constraints in ISO/IEC 23000-19 [30], clause 7 as well as the general audio track constraints defined in ISO/IEC 23000-19 [30], clause 10.
+
+#### 7.4.2.2 CMAF Switching Set and Media Profile Definition
+
+If media is provided following the operation point **EVS** and is provided in a CMAF Switching Set, then every CMAF track in the CMAF Switching Set shall conform to the requirements of the codec entry 'sevs' as defined in TS 26.244 [29], the general CMAF Switching Set constraints in ISO/IEC 23000-19 [30], clause 7 as well as the general CMAF audio track Switching Set constraints defined in ISO/IEC 23000-19 [30], clause 10. A CMAF Switching Set following these requirements is defined as the CMAF EVS media profile 'cevs'.
+
+#### 7.4.2.3 Mapping to DASH Adaptation Set
+
+If media is provided following the operation point **EVS** and is provided in a DASH Media Presentation in an Adaptation Set, then the Adaptation Set shall conform to the DASH profile for CMAF as defined in ISO/IEC 23009-1 [31]. The following parameters shall be present on Adaptation Set level and set:
+
+- @codecs is set to 'sevs'
+- @mimeType is set to be compatible with "audio/mp4 profiles='cevs'"
+- @audioSamplingRate is set to one of the following: '8000', '16000', '24000', '32000'
+
+If the Adaptation Set conforms to the constraints for the **EVS** Operation Point as defined in this clause, then the @profiles parameter in the Adaptation Set may signal conformance to this Media Profile by using "urn:3GPP:audio:mp:evs".
+
+#### 7.4.2.4 Playback Requirements
+
+For a receiver supporting the EVS media profile the following applies:
+
+- It shall support the receiver requirements as documented in clause 6.2.4.2 for any CMAF Track conforming to the CMAF EVS media profile 'cevs' as defined in clause 7.4.2.2.
+- It shall support the following playback requirements as documented in clause 8 of CTA-WAVE 5003 [32] for any content conforming to a CMAF Switching Set according to CMAF EVS media profile 'cevs' as defined in clause 7.4.2.2, namely:
+  - 8.2 Sequential Track Playback
+  - 8.3 Random Access to Fragment
+  - 8.4 Random Access to Time
+  - 8.5 Switching Set Playback
+  - 8.6 Regular Playback of Chunked Content
+  - 8.7 Regular Playback of Chunked Content, non-aligned append
+- It should support the following playback requirements as documented in clause 8 of CTA-WAVE 5003 [32] for any content conforming to a CMAF Switching Set according to CMAF EVS media profile 'cevs' as defined in clause 7.2.2.2, namely:
+  - 8.9 Out-Of-Order Loading
+  - 8.10 Overlapping Fragments
+
+- 8.12 Playback of Encrypted Content
+
+#### 7.4.2.5 Content Generation Requirements
+
+For a transmitter supporting the EVS media profile the following applies:
+
+- It shall support all media encoding capabilities for EVS as defined in clause 5.3.
+- It shall support the sender requirements for EVS as defined in clause 6.2.4.3.
+- It shall support the generation of a CMAF Track as defined in clause 7.4.2.1 that conforms to the CMAF Media Profile 'cevs' as defined in clause 7.4.2.2.
+- If used for Adaptive Bit Rate (ABR) distribution, it shall support the generation of a CMAF Switching Set as defined in clause 7.4.2.4.
+
+## 7.5 void
+
+## 7.6 eAAC+ stereo Media Profile
+
+### 7.6.1 Void
+
+### 7.6.2 Media Profile Definition
+
+#### 7.6.2.1 CMAF Track Definition
+
+If media is provided following the operation point **eAAC+ stereo** and is encapsulated in a CMAF track, then the CMAF track shall conform to the requirements of the codec entry 'mp4a' as defined in TS 26.244 [29], the general CMAF Track constraints in ISO/IEC 23000-19 [30], clause 7, the general audio track constraints defined in ISO/IEC 23000-19 [30], clause 10 as well as AAC core constraints in clause 10 of ISO/IEC 23000-19 [30].
+
+NOTE: A CMAF Track conforming to eAAC+ stereo media profile also conforms to the xHE-AAC Media Profile as defined in clause 7.8. Consequently, such CMAF Track can also be played back by receivers conforming to the xHE-AAC Media Profile.
+
+#### 7.6.2.2 CMAF Switching Set and Media Profile Definition
+
+If media is provided following the operation point **eAAC+ stereo** and is provided in a CMAF Switching Set, then every CMAF track in the CMAF Switching Set shall conform to the requirements of the codec entry 'mp4a' as defined in TS 26.244 [29], the general CMAF Switching Set constraints in ISO/IEC 23000-19 [30], clause 7, the general CMAF audio track Switching Set constraints defined in ISO/IEC 23000-19 [30], clause 10 as well as the AAC core Switching Set constraints in clause 10 of ISO/IEC 23000-19 [30]. A CMAF Switching Set following these requirements is defined as the CMAF eAAC+ stereo media profile 'ceac'.
+
+#### 7.6.2.3 Mapping to DASH Adaptation Set
+
+If media is provided following the operation point **eAAC+ stereo** and is provided in a DASH Media Presentation in an Adaptation Set, then the Adaptation Set shall conform to the DASH profile for CMAF as defined in ISO/IEC 23009-1 [31]. The following parameters shall be present on Adaptation Set level and set:
+
+- @codecs is set to 'mp4a'
+- @mimeType is set to be compatible with "audio/mp4 profiles='ceac'"
+- @audioSamplingRate is set to '32000', '44100', or '48000'
+
+If the Adaptation Set conforms to the constraints for the **eAAC+ stereo** Operation Point as defined in this clause, then the `@profiles` parameter in the Adaptation Set may signal conformance to this Media Profile by using "urn:3GPP:audio:mp:eAAC+ ".
+
+NOTE: A DASH Adaptation Set conforming to eAAC+ stereo media profile conforms to the xHE-AAC DASH Adaptation Set as defined in clause 7.8. Hence, such DASH Adaptation Set can also be played back by receivers conforming to the xHE-AAC media profile.
+
+#### 7.6.2.4 Playback Requirements
+
+For a receiver supporting the **eAAC+ stereo** media profile the following applies:
+
+- It shall support the receiver requirements as documented in clause 6.3.2.2 for any CMAF Track conforming to the CMAF eAAC+ stereo media profile 'ceac' as defined in clause 7.6.2.2.
+- It shall support the following playback requirements as documented in clause 8 of CTA-WAVE 5003 [32] for any content conforming to a CMAF Switching Set according to CMAF eAAC+ stereo media profile 'ceac' as defined in clause 7.6.2.2, namely:
+  - 8.2 Sequential Track Playback
+  - 8.3 Random Access to Fragment
+  - 8.4 Random Access to Time
+  - 8.5 Switching Set Playback
+  - 8.6 Regular Playback of Chunked Content
+  - 8.7 Regular Playback of Chunked Content, non-aligned append
+- It should support the following playback requirements as documented in clause 8 of CTA-WAVE 5003 [32] for any content conforming to a CMAF Switching Set according to CMAF eAAC+ stereo media profile 'ceac' as defined in clause 7.6.2.2, namely:
+  - 8.9 Out-Of-Order Loading
+  - 8.10 Overlapping Fragments
+  - 8.12 Playback of Encrypted Content
+
+#### 7.6.2.5 Content Generation Requirements
+
+For a transmitter supporting the **eAAC+ stereo** media profile the following applies:
+
+- It shall support all media encoding capabilities for eAAC+ stereo as defined in clause 5.3.
+- It shall support the sender requirements for eAAC+ stereo as defined in clause 6.3.2.3.
+- It shall support the generation of a CMAF Track as defined in clause 7.6.2.2 that conforms to the CMAF Media Profile 'ceac' as defined in clause 7.6.2.3.
+- If used for Adaptive Bit Rate (ABR) distribution, it shall support the generation of a CMAF Switching Set as defined in clause 7.6.2.4.
+
+## 7.7 AMR-WB+ Media Profiles
+
+### 7.7.1 Mapping to ISO BMFF
+
+If media is provided following the operation point **AMR-WB+** and is encapsulated in the ISO BMFF, then the file format track shall conform to the requirements of the codec entry 'sawp' as defined in TS 26.244 [29].
+
+### 7.7.2 Media Profile Definition
+
+#### 7.7.2.1 CMAF Track Definition
+
+If media is provided following the operation point **AMR-WB+** and is encapsulated in a CMAF track, then the CMAF track shall conform to the requirements of the codec entry 'sawp' as defined in TS 26.244 [29], the general CMAF Track constraints in ISO/IEC 23000-19 [30], clause 7 as well as the general audio track constraints defined in ISO/IEC 23000-19, clause 10.
+
+#### 7.7.2.2 CMAF Switching Set and Media Profile Definition
+
+If media is provided following the operation point **AMR-WB+** and is provided in a CMAF Switching Set, then every CMAF track in the CMAF Switching Set shall conform to the requirements of the codec entry 'sawp' as defined in TS 26.244 [29], the general CMAF Switching Set constraints in ISO/IEC 23000-19 [30], clause 7 as well as the general CMAF audio track Switching Set constraints defined in ISO/IEC 23000-19 [30], clause 10. A CMAF Switching Set following these requirements is defined as the CMAF AMR-WB+ media profile 'camp'.
+
+#### 7.7.2.3 Mapping to DASH Adaptation Set
+
+If media is provided following the operation point **AMR-WB+** and is provided in a DASH Media Presentation in an Adaptation Set, then the Adaptation Set shall conform to the DASH profile for CMAF as defined in ISO/IEC 23009-1 [31]. The following parameters shall be present on Adaptation Set level and set:
+
+- @codecs is set to 'sawp'
+- @mimeType is set to be compatible with "audio/mp4 profiles='camp'"
+- @audioSamplingRate is set to any of the following values: '8000', '16000', '32000', or '38400'
+
+If the Adaptation Set conforms to the constraints for the **AMR-WB+** Operation Point as defined in this clause, then the @profiles parameter in the Adaptation Set may signal conformance to this Media Profile by using "urn:3GPP:audio:mp:amr-wb+".
+
+#### 7.7.2.4 Playback Requirements
+
+For a receiver supporting the AMR-WB+ media profile the following applies:
+
+- It shall support the receiver requirements as documented in clause 6.3.2.2 for any CMAF Track conforming to the CMAF AMR-WB+ stereo media profile 'camp' as defined in clause 7.7.2.2.
+- It shall support the following playback requirements as documented in clause 8 of CTA-WAVE 5003 [32] for any content conforming to a CMAF Switching Set according to CMAF AMR-WB+ media profile 'camp' as defined in clause 7.7.2.2, namely:
+  - 8.2 Sequential Track Playback
+  - 8.3 Random Access to Fragment
+  - 8.4 Random Access to Time
+  - 8.5 Switching Set Playback
+  - 8.6 Regular Playback of Chunked Content
+  - 8.7 Regular Playback of Chunked Content, non-aligned append
+- It should support the following playback requirements as documented in clause 8 of CTA-WAVE 5003 [32] for any content conforming to a CMAF Switching Set according to CMAF AMR-WB media profile 'camp' as defined in clause 7.7.2.2, namely:
+  - 8.9 Out-Of-Order Loading
+  - 8.10 Overlapping Fragments
+
+- 8.12 Playback of Encrypted Content
+
+#### 7.7.2.5 Content Generation Requirements
+
+For a transmitter supporting the AMR-WB+ media profile the following applies:
+
+- It shall support all media encoding capabilities for AMR-WB+ stereo as defined in clause 5.3.
+- It shall support the sender requirements for AMR-WB+ as defined in clause 6.3.3.3.
+- It shall support the generation of a CMAF Track as defined in clause 7.7.2.2 that conforms to the CMAF Media Profile 'cawp' as defined in clause 7.7.2.3.
+- If used for Adaptive Bit Rate (ABR) distribution, it shall support the generation of a CMAF Switching Set as defined in clause 7.7.2.4.
+
+## 7.8 xHE-AAC Media Profile
+
+### 7.8.1 CMAF Track Definition
+
+If media is provided following the operation point **xHE-AAC stereo** and is encapsulated in a CMAF track, then the CMAF track shall conform to the general CMAF Track constraints in ISO/IEC 23000-19:2023 [30], clause 7, the general audio track constraints defined in ISO/IEC 23000-19:2023 [30], clause 10, as well as MPEG-D USAC track format constraints defined in ISO/IEC 23000-19:2023 [30], Annex K.
+
+### 7.8.2 CMAF Switching Set and Media Profile Definition
+
+If media is provided following the operation point **xHE-AAC stereo** and is provided in a CMAF Switching Set, then every CMAF track in the CMAF Switching Set shall conform to the general CMAF Track constraints in ISO/IEC 23000-19:2023 [30], clause 7, the general CMAF audio track Switching Set constraints defined in ISO/IEC 23000-19:2023 [30], clause 10, as well as the MPEG-D USAC CMAF media profile constraints defined in ISO/IEC 23000-19:2023 [30], Annex K.
+
+A CMAF Switching Set following these requirements is defined as the CMAF USAC stereo media profile 'casu'.
+
+### 7.8.3 Mapping to DASH Adaptation Set
+
+If media is provided following the operation point **xHE-AAC stereo** and is provided in a DASH Media Presentation in an Adaptation Set, then the following requirements apply:
+
+- Content representations shall comply with the USAC stereo CMAF media profile 'casu', as defined in ISO/IEC 23000-19:2023 [30].
+- Content representations shall comply with the DASH Profile for CMAF content as defined in ISO/IEC 23009-1:2022 [31]
+- If the **ChannelConfiguration** parameter is present in the Movie header, then the identical channel configuration shall be signaled by means of the AudioChannelConfiguration element in the MPD, according to the values specified in ISO/IEC 23000-19:2023 [30] Table K.2.
+- @audioSamplingRate is set to '32000', '44100', or '48000'
+
+If the Adaptation Set conforms to the constraints for the **xHE-AAC stereo** Operation Point as defined in this clause, then the @profiles parameter in the Adaptation Set may signal conformance to this Media Profile by using "urn:3GPP:audio:mp:xHE-AAC".
+
+### 7.8.4 Playback Requirements
+
+For a receiver supporting the **xHE-AAC** media profile the following applies:
+
+- It shall support the receiver requirements as documented in clause 6.3.4.2 for any CMAF Track conforming to the CMAF USAC stereo media profile 'casu' as defined in clause 7.8.2.
+- It should support the audio related playback requirements as documented in clause 8 of CTA-WAVE 5003 [32] for any content conforming to a CMAF Switching Set according to CMAF USAC stereo media profile 'casu' as defined in clause 7.8.2.
+
+### 7.8.5 Content Generation Requirements
+
+For a transmitter supporting the **xHE-AAC** media profile the following applies:
+
+- It shall support all media encoding capabilities for xHE-AAC stereo as defined in clause 5.3.
+- It shall support the sender requirements for xHE-AAC stereo as defined in clause 6.3.4.3.
+- It shall support the generation of a CMAF Track as defined in clause 7.8.1 that conforms to the CMAF Media Profile 'casu' as defined in clause 7.8.2.
+- If used for Adaptive Bit Rate (ABR) distribution, it shall support the generation of a CMAF Switching Set as defined in clause 7.8.2.
+
+# Annex A (informative): Registration Information
+
+## A.1 3GPP Registered URIs
+
+The clause documents the registered URIs in the present document following the process in <http://www.3gpp.org/specifications-groups/34-uniform-resource-name-urn-list>
+
+Table A-1 lists all registered URN values as well as:
+
+- a brief description of its functionality;
+- a reference to the specification or other publicly available document (if any) containing the definition;
+- the name and email address of the person making the application; and
+- any supplementary information considered necessary to support the application.
+
+**Table A-1: 3GPP Registered URNs**
+
+| URN                       | Description                | Reference                 | Contact                                     | Remarks |
+|---------------------------|----------------------------|---------------------------|---------------------------------------------|---------|
+| urn:3GPP:audio:mp:amr     | AMR Media Profile          | TS 26.117, clause 7.2.2.3 | Thomas Stockhammer<br>tsto@qti.qualcomm.com | none    |
+| urn:3GPP:audio:mp:amr-wb  | AMR-WB Media Profile       | TS 26.117, clause 7.3.2.3 | Thomas Stockhammer<br>tsto@qti.qualcomm.com | none    |
+| urn:3GPP:audio:mp:evs     | EVS Media Profile          | TS 26.117, clause 7.4.2.3 | Thomas Stockhammer<br>tsto@qti.qualcomm.com | none    |
+| urn:3GPP:audio:mp:eAAC+   | eAAC+ stereo Media Profile | TS 26.117, clause 7.6.2.3 | Thomas Stockhammer<br>tsto@qti.qualcomm.com | none    |
+| urn:3GPP:audio:mp:amr-wb+ | AMR-WB+ Media Profile      | TS 26.117, clause 7.7.2.3 | Thomas Stockhammer<br>tsto@qti.qualcomm.com | none    |
+| urn:3GPP:audio:mp:xHE-AAC | xHE-AAC Media Profile      | TS 26.117, clause 7.8.3   | Frédéric Gabin<br>frederic.gabin@dolby.com  | none    |
+
+# Annex B (informative): Change history
+
+| Change history |         |           |          |     |     |                                                          |  |               |
+|----------------|---------|-----------|----------|-----|-----|----------------------------------------------------------|--|---------------|
+| Date           | Meeting | TDoc      | CR       | Rev | Cat | Subject/Comment                                          |  | New version   |
+| 2019-12        | SA#86   | SP-190990 |          |     |     | Presented to TSG SA#86 (for information)                 |  | 1.0.0         |
+| 2020-01        | SA4#107 | S4-200245 |          |     |     | Version agreed by TSG SA WG 4 to be sent for SA approval |  | 1.1.0         |
+| 2020-03        | SA#87-e | SP-200049 |          |     |     | Presented to TSG SA#87-e (for approval)                  |  | 2.0.0         |
+| 2020-03        | SA#87-e | SP-200049 |          |     |     | Approved by TSG SA#87-e                                  |  | 16.0.0        |
+| 2022-04        | -       | -         | -        | -   | -   | Update to Rel-17 version (MCC)                           |  | <b>17.0.0</b> |
+| 2023-03        | SA#99-  | SP-230251 | 000<br>1 | 4   | B   | Introduction of xHE-AAC stereo audio operation point     |  | <b>18.0.0</b> |
+| 2023-06        | SA#100  | SP-230552 | 000<br>2 | -   | F   | Corrections to references                                |  | <b>18.1.0</b> |