Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Top   in Index   Prev   Next

TS 26.179
Mission Critical Push To Talk (MCPTT) –
Codecs and Media Handling

Use "3GPP‑Page" to get the Word version, and "ETSI‑search" to get the PDF version
V16.0.0 (PDF)  2019/03  9 p.
V15.0.0  2018/06  11 p.
V14.0.0  2017/03  11 p.
V13.2.0  2016/09  11 p.
Rapporteur:
Mr. Turcotte, Eric

Content for  TS 26.179  Word version:  16.0.0

Here   Top
0  IntroductionWord‑p. 4
Requirements for codecs and media handling in support of the Mission Critical Push To Talk (MCPTT) service are contained in this document.
The MCPTT service supports voice communication between several users (i.e. group call), where each user has the ability to gain access to the permission to talk in an arbitrated manner. The MCPTT service also supports private calls between two users.
Background information in support of this document may be found in TR 26.989.
Up
1  ScopeWord‑p. 5
The present document specifies the codecs and media handling for MCPTT. The corresponding service requirements are defined in TS 22.179. The corresponding functional architecture, procedures and information flows are defined in TS 23.179.
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]  TR 21.905   "Vocabulary for 3GPP Specifications".
[2]  TS 22.179   "Mission Critical Push To Talk (MCPTT) over LTE; Stage 1".
[3]  TS 23.179   "Functional architecture and information flows to support mission critical communication services; Stage 2".
[4]  TR 26.989   "Media codecs and Multimedia Broadcast/Multicast Service (MBMS) enhancements for MCPTT over LTE".
[5]  TS 24.379   "Mission Critical Push To Talk (MCPTT) call control; Protocol specification".
[6]  TS 24.380   "Mission Critical Push To Talk (MCPTT) media plane control; Protocol specification".
[7]  TS 26.171   "Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec; General description".
[8]  TS 26.173   "ANCI-C code for the Adaptive Multi Rate - Wideband (AMR-WB) speech codec".
[9]  TS 26.190   "Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec; Transcoding functions".
[10]  TS 26.191   "Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec; Error concealment of erroneous or lost frames".
[11]  TS 26.192   "Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec; Comfort noise aspects".
[12]  TS 26.193   "Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec; Source controlled rate operation".
[13]  TS 26.194   "Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec; Voice Activity Detector (VAD)".
[14]  TS 26.204   "Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec; ANSI-C code".
[15]  TS 26.441   "Codec for Enhanced Voice Services (EVS); General overview".
[16]  TS 26.442   "Codec for Enhanced Voice Services (EVS); ANSI C code (fixed-point)".
[17]  TS 26.443   "Codec for Enhanced Voice Services (EVS); ANSI C code (floating-point)".
[18]  TS 26.445   "Codec for Enhanced Voice Services (EVS); Detailed algorithmic description".
[19]  TS 26.447   "Codec for Enhanced Voice Services (EVS); Error concealment of lost packets".
[20]  TS 26.449   "Codec for Enhanced Voice Services (EVS); Comfort Noise Generation (CNG) aspects".
[21]  TS 26.450   "Codec for Enhanced Voice Services (EVS); Discontinuous Transmission (DTX)".
[22]  TS 26.451   "Codec for Enhanced Voice Services (EVS); Voice Activity Detection (VAD)".
[23]  RFC 4867  (2007): "RTP Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs", J. Sjoberg, M. Westerlund, A. Lakaniemi and Q. Xie.
[24]  RFC 3550  (2003): "RTP: A Transport Protocol for Real-Time Applications", H. Schulzrinne, S. Casner, R. Frederick, V. Jacobson.
[25]  RFC 3551  (2003): "RTP Profile for Audio and Video Conferences with Minimal Control", H. Schulzerinne, S. Casner.
[26]  RFC 3711  (2004): "The Secure Real-time Transport Protocol (SRTP)", M. Baugher, D. McGrew, M. Naslund, E. Carrara, K. Norrman.
[27]  TS 26.452   "Codec for Enhanced Voice Services (EVS); ANSI C code; Alternative fixed-point using updated basic operators".
Up
3  Definitions and abbreviationsWord‑p. 6
3.1  Definitions
For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
(void)
3.2  Abbreviations
For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
AMR-WB
Adaptive Multi Rate Wideband (codec)
AVP
Audio-Video Profile
EVS
Enhanced Voice Services
FB
Fullband
KPI
Key Performance Indicator
MBMS
Multimedia Broadcast Multicast Services
MBSFN
Multicast Broadcast Single Frequency Network
MCPTT
Mission Critical Push-To-Talk
RTP
Real-time Transport Protocol
SAVP
Secure Audio-Video Profile
SRTP
Secure Real-time Transport Protocol
SWB
Super Wideband
WB
Wideband
Up
4  Codecs and media handling for MCPTTWord‑p. 7
4.1  MCPTT client
4.1.1  Codec
MCPTT clients shall support the AMR-WB codec as specified in TS 26.171, TS 26.190, TS 26.173 and TS 26.204, including all 9 modes and source controlled rate operation as specified in TS 26.193, voice activity detection as specified in TS 26.194, comfort noise generation as specified in TS 26.192 and error concealment as specified in TS 26.191. The MCPTT clients shall be capable of operating with any subset of these 9 codec modes.
Based on operator / MCPTT service provider policy, MCPTT clients may additionally support the EVS codec in super-wideband mode.
If an operator / MCPTT service provider chooses to additionally use SWB according to its policy, then an MCPTT client that offers super-wideband speech communication shall support the EVS codec in SWB mode as defined in TS 26.441, TS 26.445, TS 26.442, TS 26.452, TS 26.443, discontinuous transmission TS 26.450, voice activity detection as specified in TS 26.451, comfort noise generation as specified in TS 26.449 and error concealment as specified in TS 26.447.
Up
4.1.2  Control plane protocol
General MCPTT client procedures for SDP offer-answer are specified in TS 24.379 and TS 24.380.
MCPTT clients shall support both "RTP/AVP" [25] and "RTP/SAVP" [26] profiles in SDP offer/answer. MCPTT clients shall not reject an SDP offer due to offered RTP profile being either "RTP/AVP" or "RTP/SAVP". MCPTT clients may, based on operator / MCPTT service provider policy, offer either "RTP/AVP" or "RTP/SAVP" RTP profiles.
MCPTT clients shall support and offer a payload type with AMR-WB.
If an operator / MCPTT service provider policy enables an MCPTT service using the EVS codec in SWB mode, then MCPTT clients may, based on operator / MCPTT service provider policy, additionally offer a payload type with the EVS codec in SWB mode.
The offer-answer protocol, setting of the codec preference order, and the generation of SDP offer and answer shall be configured according to operator / MCPTT service provider policy.
Up
4.1.3  User plane protocol
MCPTT clients shall support both RTP [24] and SRTP [26] media transport.
An MCPTT client shall understand the payload formats and options as defined in RFC 4867 [23]. The MCPTT client does not have to support operating according to all the options defined in RFC 4867 but shall be capable of properly accepting or rejecting all options.
The following payload format options from RFC 4867 are defined as follows to ensure minimum interoperability:
  • bandwidth-efficient shall be supported
  • mode-set: shall support all modes and shall offer no particular mode set
  • mode-change-period: both "1" and "2" shall be supported, "1" shall be offered (or not included)
  • mode-change-capability: both "1" and "2" shall be supported, "2" shall be offered
  • mode-change-neighbor: both "0" and "1" shall be supported, "0" shall be offered (or not included)
  • channels: shall offer "1"
Other parameters:
  • ptime: shall be supported, "20" shall be offered
  • maxptime: shall be supported, "240" shall be offered
  • max-red: shall be supported, "0" shall be offered
If, based on operator / MCPTT service provider policy, the MCPTT service additionally supports the EVS codec in SWB mode, then an MCPTT client that supports the optional EVS codec in SWB mode shall understand the EVS payload format as specified in TS 26.445 in order to support EVS in SWB mode. The MCPTT client does not have to support operating according to all the options defined in TS 26.445 but must be capable of properly accepting or rejecting all options.
Up
4.1.4  De-jitter bufferWord‑p. 8
When MCPTT voice traffic is received on the MBMS bearer in MBMS/MBSFN, the traffic is scheduled to arrive at intervals of multiples of 40ms. The received traffic could also exhibit time-varying jitter introduced in the backhaul and the uplink transmission by the talker before being scheduled for transmission on the MBMS bearer. The MCPTT UE receiving traffic on an MBMS bearer shall support and use a de-jitter buffer that is able to manage this amount of jitter.
4.2  MCPTT network
4.2.1  Control plane protocol
MCPTT Server procedures are specified in TS 24.379 and TS 24.380.
MCPTT call media codec information shall include codecs according to MCPTT Client capabilities as specified in clause 4.1.1.
$  Change historyWord‑p. 9

Up   Top