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

Glossary term · Core Network

TGW

Trunking GateWay

Core Network →

TGW is a core network element that interconnects the 3GPP IMS/CS domain with external trunking networks, handling media and signalling interworking at the boundary between operator domains.

Introduced
Rel-8
Where
Core Network › 5G Core
Specifications
2 specs
TGW Description Purpose Neighbours Specifications

Description

The Trunking Gateway (TGW) is a functional entity defined in 3GPP Release 8 specifications 29.412 and 29.424 that sits at the boundary between a 3GPP network and external trunking networks. It acts as a media and signalling interworking point, terminating bearer channels on one side and packet-based media streams on the other. In the context of the IMS and the circuit-switched domain, the TGW provides the functions needed to connect operator networks that use different transport technologies, ensuring that voice and multimedia sessions can be established and maintained across domain boundaries.

Architecturally, the TGW is closely related to the Media Gateway (MGW) and the Media Gateway Control Function (MGCF) in the IMS. The TGW terminates trunking interfaces — typically TDM trunks or IP-based trunks — and performs transcoding, echo cancellation, and media stream adaptation. It is controlled by a media gateway controller using the H.248/Megaco protocol, which allows the control plane to remain separate from the bearer plane. This separation of call control and bearer control is a fundamental principle of the 3GPP core network architecture, enabling scalability and flexible deployment.

The TGW plays a critical role in inter-operator interconnection. When a call originates in one operator's network and terminates in another, the TGW provides the demarcation point where signalling (such as ISUP or SIP-I) and media are handled. It supports the necessary interworking functions to translate between different signalling protocols and media formats, ensuring end-to-end service continuity. In the context of 29.412, the TGW is described as part of the signalling architecture for trunking, while 29.424 addresses the media gateway control aspects.

Key components of the TGW include trunk interfaces (E1/T1, STM-1, or IP), media processing resources (codecs, transcoders, conferencing bridges), and a control interface to the media gateway controller. The TGW also supports lawful interception, QoS marking, and security functions such as IPsec for transport protection. Its role in the network is analogous to a border gateway, enforcing policy and providing a clean separation between trusted and untrusted domains.

In summary, the TGW is a foundational element for interconnection in 3GPP networks, enabling seamless communication between heterogeneous networks while maintaining the separation of control and bearer planes that characterizes the 3GPP core network design.

Purpose & Motivation

The Trunking Gateway exists to solve the problem of interconnecting networks that use different transport and signalling technologies. Before the widespread adoption of all-IP networks, operators relied on TDM-based trunking, and connecting these networks to emerging packet-based core networks required a gateway that could translate between the two worlds. The TGW provides this translation, allowing legacy circuit-switched infrastructure to interoperate with modern IMS and packet core networks.

Historically, the need for trunking gateways arose as operators began migrating from circuit-switched to packet-switched transport. The TGW allowed a gradual migration path, where parts of the network could remain TDM-based while other parts moved to IP, without disrupting service. This was particularly important for international interconnect, where different operators might be at different stages of their migration.

The TGW also addresses the need for centralized media processing and policy enforcement at network boundaries. By terminating trunks at a single point, operators can apply consistent QoS, security, and lawful interception policies. The separation of control and bearer planes, enabled by the TGW architecture, allows operators to scale media resources independently of call control, which is essential for handling traffic growth and for deploying virtualized network functions.

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 definition of the Trunking Gateway in 3GPP specifications 29.412 and 29.424, establishing the architecture for interconnecting 3GPP networks with external trunking networks, including media and signalling interworking functions.

Defining Specifications

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

SpecificationTitleRelease
TS 29.412 v810 Control Procedures for Trunk Gateways in NGN Networks Rel-8 read
TS 29.424 v801 H.248 Profile for Trunking Media Gateways Rel-8 read