MGW

Media Gateway

Core Network →
Introduced in R99 Also in: Management, Services

MGW is a network element that converts media streams between different transmission formats and protocols, such as between circuit-switched and packet-switched networks, to enable communication across legacy and modern networks.

Category
Core Network
Introduced
R99
Where
Core Network › 5G Core
Also touches
2 segments
Specifications
34 specs
MGW Description Purpose Related Classification Specifications

Description

The Media Gateway (MGW) is a critical functional entity within the 3GPP Core Network, specifically in the Circuit-Switched (CS) and IP Multimedia Subsystem (IMS) domains. Its primary role is to perform media conversion and processing. Architecturally, the MGW is controlled by a Media Gateway Controller (MGC) or, in the 3GPP context, by a Mobile Switching Center (MSC) Server or Call Session Control Function (CSCF) using control protocols like H.248 (Megaco) or SIP. The MGW itself handles the user-plane traffic. It contains termination points for various network interfaces: on one side, it connects to legacy circuit-switched networks using Time-Division Multiplexing (TDM) interfaces like E1/T1; on the other side, it connects to packet-switched networks like IP-based networks (e.g., the IMS core or the Internet) using Real-time Transport Protocol (RTP) over IP. The key internal components include codecs for transcoding (e.g., converting between G.711 PCM and AMR), echo cancellers, tone generators, and playout buffers to handle jitter. Its operation involves receiving control plane commands to establish, modify, and release terminations and contexts (logical associations of terminations for a call). For a voice call originating from a legacy PSTN phone to a VoIP client, the MGW would terminate the TDM trunk, decode the G.711 stream, transcode it to a suitable codec (if needed), packetize it into RTP packets, and send it over the IP network. It also performs bearer resource functions like playing announcements and collecting DTMF tones. In the IMS architecture, the MGW is often referred to as a Media Resource Function Processor (MRFP) when providing media processing services like conferencing and transcoding. Its role is foundational for network convergence, allowing operators to migrate from legacy TDM networks to all-IP infrastructures while maintaining service quality and interoperability.

Purpose & Motivation

The MGW was created to address the fundamental challenge of network evolution and convergence. Historically, telecommunications networks were built on circuit-switched TDM technology, which is efficient for voice but rigid and costly for data. The rise of the Internet and IP-based services demanded a more flexible, cost-effective packet-switched infrastructure. The MGW solves the problem of interoperability between these disparate network domains. It allows network operators to introduce IP-based core networks (like IMS) gradually without immediately discarding their massive investments in legacy PSTN and 2G/3G circuit-switched equipment. Before MGWs, interworking required complex and expensive adapters, and services like voice over IP were siloed. The MGW, under the control of a softswitch (MSC Server), enabled the separation of call control (signaling) from media transport, a key principle of next-generation networks. This separation increased scalability, allowed for centralized intelligence, and facilitated the introduction of new multimedia services. The creation of the MGW was motivated by the need for a standardized, vendor-interoperable way to bridge the TDM and IP worlds, which was a central goal of 3GPP from Release 99 onwards as part of defining the All-IP network vision for UMTS and beyond.

Classification

Part ofIMS
Specific typesA-SGWCS-GWMSC-S
Related approachesMRFCMRFP

Release Timeline

Evolution Across Releases

R99 Initial

Introduced the MGW as a core component of the UMTS architecture, separating the media handling function from the call control function of the traditional MSC. The MSC Server (handling signaling) controlled the MGW (handling media) using the H.248 protocol. This enabled the first step towards an All-IP core network for 3G.

Formalized the split architecture (MSC Server and MGW) as the standard for the Core Network CS domain. Enhanced support for bearer-independent call control (BICC) and defined the Nb interface between MGWs for carrying user plane traffic, further solidifying the IP transport path.

Integrated the MGW into the new IP Multimedia Subsystem (IMS) architecture. Defined the MGW's role as a Media Resource Function Processor (MRFP) controlled by a Media Resource Function Controller (MRFC) for advanced media services like conferencing and transcoding within the IMS service layer.

Enhanced MGW capabilities to support the EPS (Evolved Packet System) and SRVCC (Single Radio Voice Call Continuity). The MGW became critical for handovers of voice calls from LTE/IMS to legacy 2G/3G CS networks, ensuring voice service continuity during mobility.

Continued evolution within the 5G System (5GS). While 5GC is fully packet-based, MGWs remain relevant for interworking with legacy networks and for enabling Voice over NR (VoNR) fallback to LTE or 3G via procedures like eSRVCC, requiring media anchoring and transcoding.

Explore further

Broader topics and technologies where MGW plays a role.

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj00 3GPP Technical Terms and Definitions Rel-19
TS 23.205 vj00 Bearer Independent CS Core Network Stage 2 Rel-19
TS 23.221 vj00 3GPP System Architectural Requirements Rel-19
TS 23.231 vj00 SIP-I based CS core network stage 2 Rel-19
TS 23.333 vj00 MRFC-MRFP Mp Interface Requirements Rel-19
TS 24.228 v1500 IP Multimedia Call Control Signaling Flows Rel-5
TS 24.229 vj50 IMS call control protocol based on SIP and SDP Rel-19
TS 24.428 v1700 Common Basic Communication Procedures Rel-7
TS 24.528 v830 Common Basic Communication Procedures for IMS Services Rel-8
TS 24.628 vj00 Common Basic Communication Procedures in IMS Rel-19
TS 26.102 vj00 Mapping of AMR and other codecs to interfaces Rel-19
TS 26.114 vj10 IMS Multimedia Telephony Media Handling Rel-19
TS 26.202 vj00 AMR-WB Speech Codec Mapping Specification Rel-19
TR 26.944 vj00 QoE, ESQoS and SQoS metrics for 3G multimedia services Rel-19
TS 28.702 vj00 Core Network NRM IRP Information Service Rel-19
TS 28.703 vj00 Core Network NRM IRP Solution Set Definitions Rel-19
TS 28.706 vj00 IMS NRM IRP Solution Set definitions Rel-19
TS 29.333 vj00 MRFC-MRFP Mp Interface Protocol Rel-19
TS 29.414 vj00 Nb Interface Bearer Transport & Control Protocols Rel-19
TS 29.415 vj00 Nb User Plane Protocol Specification Rel-19
TS 29.863 v820 IMS-CS Multimedia Interworking Feasibility Study Rel-8
TS 32.240 vj40 Charging Management Architecture & Principles Rel-19
TS 32.272 vj00 Charging for Push-to-Talk over Cellular (PoC) Rel-19
TS 32.632 vb00 Core Network Resources IRP: Network Resource Model Rel-11
TS 32.633 v1920 Core Network Resources IRP CORBA Mapping Rel-9
TS 32.635 v1910 Core Network Resources IRP XML Schema Rel-9
TS 32.636 vb00 CM Core Network Resources IRP Solution Set Rel-11
TS 32.732 vb00 IMS Network Resource Model IRP: Information Service Rel-11
TS 32.733 v910 IMS NRM IRP CORBA Solution Set Rel-9
TS 32.735 v1910 IMS NRM IRP Bulk CM XML Format Rel-9
TS 32.736 vb00 IMS NRM IRP Solution Set Definitions Rel-11
TS 33.107 vj00 Lawful Interception Architecture & Functions Rel-19
TS 36.300 vj00 E-UTRAN Radio Interface Protocol Architecture Overview Rel-19
TS 48.103 vj00 A Interface User Plane Transport Protocols Rel-19
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.