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

Glossary term · Core Network

MGF

Media Gateway Function

Core Network →

MGF is a core network function that converts media streams between circuit-switched and packet-switched networks to enable interoperability for services like voice and video calls.

Introduced
Rel-2
Where
Services › IMS
Specifications
4 specs
Also in
Core Network
MGF Description Purpose What changed Neighbours Specifications

Description

The Media Gateway Function (MGF) is a critical component within the 3GPP architecture, specifically in the IP Multimedia Subsystem (IMS) and later in the 5G Core (5GC). Its primary role is to act as a translation point for media traffic, converting between different transmission and coding formats. In practical terms, this means it can receive a traditional TDM (Time-Division Multiplexing) voice stream from the Public Switched Telephone Network (PSTN) or a legacy 2G/3G mobile network and transcode it into a packet-based stream (like RTP over IP) for transport over an IP network, and vice-versa. This process involves not just format conversion but also potential adjustments to codecs, packetization timers, and echo cancellation.

Architecturally, the MGF is controlled by a separate signaling entity, historically the Media Gateway Control Function (MGCF) in IMS. This separation of control and media planes (as per the H.248/Megaco protocol) allows for scalable and flexible network design. The MGCF handles the session signaling (e.g., SIP, ISUP), while the MGF executes the media-related commands. In the 5G Core, similar functionality is often integrated into the User Plane Function (UPF) or provided by dedicated network elements for interworking with legacy systems. The MGF interfaces with transport networks on both sides—the circuit-switched trunk interfaces (e.g., E1/T1) and the packet-switched network interfaces (e.g., Ethernet).

Its role extends beyond simple voice. The MGF can handle video media streams and support various codecs like AMR, G.711, and EVS. It is a key enabler for services like VoLTE (Voice over LTE) and VoNR (Voice over New Radio) when calls need to terminate on or originate from a traditional telephone. Without the MGF, seamless communication between next-generation packet networks and the vast installed base of circuit-switched infrastructure would be impossible, making it a cornerstone for network migration and service continuity.

Purpose & Motivation

The MGF was created to solve the fundamental problem of interoperability between the emerging, efficient packet-switched networks (like those based on IP for IMS and later 5G) and the entrenched, global circuit-switched telephony infrastructure. Historically, all telephony was circuit-switched, requiring dedicated physical or logical connections for the duration of a call. The rise of IP promised more efficient bandwidth usage and integrated services but could not communicate natively with the PSTN. The MGF provides the necessary bridge.

Its development was motivated by the need for a smooth, phased migration from legacy networks to all-IP networks like IMS. Operators could not replace their entire network overnight. The MGF allowed them to introduce IP-based core networks while still connecting to existing revenue-generating PSTN services and subscribers on older mobile generations (2G/3G). It addressed the limitations of previous monolithic switches by decomposing the gateway into a separate media plane (MGF) and control plane (MGCF), following the softswitch architecture paradigm. This separation offered greater scalability, vendor interoperability, and the ability to independently upgrade control logic and media processing capabilities.

What changed in its specifications

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

TS 23.228Rel-18 → Rel-19

Rel-19 TS 23.228 adds SBI service operations for IMS data channels, event subscription, and user information, plus HSS lookup of the serving IMS AS. It adds PS Data Off handling for IMS Data Channel services and Multimedia Priority Service for Messaging.

Full comparison in TS 23.228 →

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-2 Initial

Introduced as part of the initial IMS architecture in 3GPP Release 2. The MGF was defined as the media processing entity, separate from the MGCF which handled signaling. Its initial role was to provide the bearer path interworking between the CS domain and the IMS IP network, establishing the foundational model for media gateway decomposition.

Defining Specifications

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

SpecificationTitleRelease
TS 23.228 vk10 IP Multimedia Core Network Subsystem Rel-20 read
TS 23.417 v700 IMS Core Component for NGN Architecture Rel-7 read
TS 23.517 v800 IMS Core Architecture for TISPAN NGN Rel-8 read
TS 24.524 vj00 Hosted Enterprise Services Architecture Rel-19 read