Description
Remote Transcoder Operation (RTO) is a network functionality defined in 3GPP TS 23.231 that relocates the transcoding unit (TCU) for speech codecs from the traditional Mobile Switching Center (MSC) to a separate network node, often situated closer to the radio access network. Transcoding is necessary when voice calls involve different codecs, such as between a legacy circuit-switched network using AMR (Adaptive Multi-Rate) and a packet-switched network using AMR-WB (Wideband) or other codecs. In RTO, the TCU is deployed remotely, allowing the MSC to bypass transcoding for calls that use compatible codecs, thereby reducing processing load and improving voice quality.
Architecturally, RTO introduces two key nodes: the Remote Transcoder Unit (RTU) and the Transcoder Control Function (TCF). The RTU performs the actual speech codec conversion, while the TCF, which may be integrated with the MSC or a Media Gateway Control Function (MGCF), controls the RTU's operation based on call signaling. During call setup, the MSC determines if transcoding is needed by comparing the codecs supported by the calling and called parties. If transcoding is required, the MSC instructs the TCF to allocate an RTU resource and routes the voice bearer through it. If not, the voice path can be established directly between endpoints, avoiding unnecessary codec conversions.
How RTO works involves signaling and bearer path separation. The call control signaling (e.g., via ISUP or BICC) still traverses the MSC, but the user plane (voice traffic) may be routed directly between the radio network controller (RNC) or base station and the RTU, or even peer-to-peer if no transcoding is needed. This is often implemented using TrFO (Transcoder Free Operation) and TFO (Tandem Free Operation) principles. RTO reduces the number of coding/decoding stages (tandem coding), which can degrade voice quality due to quantization noise. By placing transcoders remotely, operators can pool these resources efficiently, scale them independently of MSCs, and optimize transmission bandwidth, especially in networks transitioning to VoIP and IMS.
Purpose & Motivation
RTO was developed to address inefficiencies in traditional circuit-switched voice networks where transcoders were physically integrated into every MSC. This architecture forced all voice traffic to pass through the MSC's transcoder, even when both call legs used the same codec, resulting in unnecessary transcoding (tandem coding) that degraded voice quality and consumed additional hardware resources. The limitations included increased latency, higher equipment costs, and suboptimal voice quality, particularly as wideband codecs like AMR-WB were introduced to enhance user experience.
Its creation was motivated by the evolution toward all-IP networks and the desire to optimize voice handling in mixed network environments (2G/3G/4G). As operators deployed packet-switched cores and IMS, they needed a way to handle interworking between legacy circuit-switched codecs and VoIP codecs without mandating transcoding for every call. RTO solves this by decoupling the transcoding function, allowing flexible placement and on-demand use. This reduces operational expenses by centralizing and pooling transcoder resources, and it improves voice quality by enabling transcoder-free operation when possible.
Historically, before RTO, networks relied on fixed transcoder locations, which complicated the introduction of new codecs and limited scalability. The standardization in Release 8 provided a framework for remote transcoder control, aligning with broader trends like network function virtualization and edge computing. RTO addresses the problem of inefficient resource utilization and quality degradation in multi-codec environments, facilitating smoother migration to IP-based voice services like VoLTE and VoNR while maintaining backward compatibility with legacy systems.
Key Features
- Decoupling of transcoding functions from the MSC to remote nodes for flexible deployment
- Support for TrFO (Transcoder Free Operation) to avoid unnecessary codec conversions
- Centralized control via Transcoder Control Function (TCF) for dynamic resource allocation
- Compatibility with multiple speech codecs including AMR, AMR-WB, and EVS
- Optimization of transmission bandwidth by reducing tandem coding instances
- Seamless interworking between circuit-switched and packet-switched voice networks
Evolution Across Releases
Introduced RTO architecture in TS 23.231, defining Remote Transcoder Unit (RTU) and Transcoder Control Function (TCF). Initial capabilities enabled dynamic allocation of remote transcoders based on call codec compatibility, supporting TrFO/TFO to improve voice quality and reduce MSC processing load in UMTS and GSM networks.
Defining Specifications
| Specification | Title |
|---|---|
| TS 23.231 | 3GPP TS 23.231 |