Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Core Network

TRANSCODING

Transcoding

Core Network →

TRANSCODING is the process of translating media from one encoded format to another, such as between different speech codecs, to enable interworking between networks that use incompatible codecs.

Introduced
Rel-8
Where
Core Network › Evolved Packet Core
Specifications
2 specs
TRANSCODING Description Purpose What changed Neighbours Specifications

Description

Transcoding, in the context of 3GPP specifications, refers to the process of translating media from one encoded format to a different encoded format. This is a fundamental operation in telecommunications networks that must support interworking between diverse access technologies, codecs, and terminal capabilities. The most common example is the conversion between narrowband PCM codecs like G.711 A-law and μ-law, but transcoding also encompasses conversions between compressed codecs such as G.729 and AMR, or between different modes of the same codec family.

The need for transcoding arises from the heterogeneity of modern communication networks. Mobile networks typically use highly compressed codecs like AMR or EVS to conserve radio spectrum. Fixed networks often use G.711 PCM at 64 kbit/s. When a call traverses between these networks, a transcoding function must convert the media stream to a format compatible with the destination. In the 3GPP architecture, transcoding functions are typically located in Media Gateways (MGWs) or Media Resource Functions (MRFs), under the control of softswitch nodes like the MSC Server or the IMS core.

The technical implementation of transcoding involves decoding the incoming media stream to a linear representation (e.g., PCM samples) and then re-encoding it into the target format. This decode-re-encode cycle is computationally intensive and introduces several impairments: additional processing delay (typically 5-20 ms per transcoding operation), potential loss of speech quality due to tandem coding effects, and the need for sophisticated signal processing to handle codec-specific features like comfort noise generation, packet loss concealment, and jitter buffers. The transcoding function must also handle the signaling aspects, negotiating codec capabilities between endpoints using protocols like SDP within SIP or BICC.

In 3GPP Release 8, the term was introduced with a concise definition: the translation from one type of encoded media format to another different media format. Release 9 expanded this with concrete examples, including G.711 A-law to μ-law and G.729 to AMR with 4.75 rate. These examples illustrate both narrowband PCM conversions and conversions between different compression algorithms. A-law and μ-law are companding standards used in different regions (A-law in Europe and most of the world, μ-law in North America and Japan), and converting between them is a common requirement for international calls. The G.729 to AMR example illustrates a more complex conversion involving different speech coding algorithms.

Despite its necessity for interworking, transcoding is generally considered an impairment that should be minimized. The 3GPP specifications define mechanisms like Transcoder Free Operation (TrFO) and Tandem Free Operation (TFO) specifically to avoid transcoding when possible. In next-generation networks, the trend is to use a single codec family (like AMR-WB or EVS) across all domains, reducing the need for transcoding. However, transcoding remains essential for backward compatibility and for connecting to non-3GPP networks. The specifications 29.238 and 29.334 provide detailed requirements for transcoding functions in the IMS and CS domains respectively.

Purpose & Motivation

Transcoding exists to solve the fundamental problem of interoperability between networks and devices that use different media encoding formats. Without transcoding, a call originating from a mobile phone using AMR could not communicate with a fixed-line phone using G.711 PCM, or a call between two mobile networks using different codec configurations could not be established. The global telecommunications network is inherently diverse, and transcoding provides the necessary translation layer.

The historical context of transcoding is rooted in the evolution from analog to digital telephony. When digital networks were first deployed, different regions adopted different PCM companding laws (A-law and μ-law), creating an immediate need for conversion at international gateways. As mobile networks emerged, they introduced highly compressed codecs that needed to interwork with the fixed network's G.711 PCM. More recently, the proliferation of codecs for different purposes (narrowband, wideband, super-wideband, fullband) and different applications (VoLTE, VoWiFi, OTT services) has made transcoding even more relevant.

The problem that transcoding addresses is clear: without it, the network would be limited to calls where both endpoints support the same codec, which is impractical on a global scale. However, transcoding introduces its own set of problems, including speech quality degradation, increased latency, and additional network costs. This has motivated the development of TrFO and TFO, which aim to minimize or eliminate transcoding in scenarios where both endpoints can support a common codec. The ongoing evolution of 3GPP specifications continues to balance the need for interoperability (requiring transcoding) with the desire for optimal quality (avoiding transcoding).

What changed in its specifications

The latest release-to-release comparison of specifications that define TRANSCODING. Each summary describes the whole specification, not only this term.

TS 29.238Rel-15 → Rel-16

The only new feature is DBI signalling support for RAN delay budget reporting in MTSI. This adds rtcp-fb SDP attribute and RTCP feedback configuration at TrGW connection points.

Full comparison in TS 29.238 →
TS 29.334Rel-18 → Rel-19

Rel-19 added an optional procedure to trigger AGW to send RTCP RR packets via a MODIFY request, and introduced a new subclause for this enhancement.

Full comparison in TS 29.334 →

Release Timeline

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-8 Initial

Initial introduction. Defined transcoding in general as the translation from one type of encoded media format to another different media format.

Wording changed to add concrete examples: G.711 A-law to μ-law or vice versa, and G.729 to AMR with 4.75 rate, providing clearer technical illustration.

Definition text carried over unchanged from Release 9.

Definition text carried over unchanged from Release 9.

Definition text carried over unchanged from Release 9.

Definition text carried over unchanged from Release 9.

Definition text carried over unchanged from Release 9.

Definition text carried over unchanged from Release 9.

Definition text carried over unchanged from Release 9.

Definition text carried over unchanged from Release 9.

Definition text carried over unchanged from Release 9.

Definition text carried over unchanged from Release 9.

Defining Specifications

3GPP specifications that define or reference TRANSCODING, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 29.238 vj00 H.248 Profile for IBCF-TrGW Interface Rel-19 read
TS 29.334 vj00 IMS-ALG to IMS-AGW Interface Protocol Rel-19 read