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

Glossary term · Core Network

IM-MGW

IP Multimedia Media Gateway Function

Core Network →

IM-MGW is a media gateway within the IMS that performs translation and processing between packet-switched and circuit-switched networks, handling functions like transcoding for multimedia sessions.

Introduced
Rel-5
Where
Core Network › Evolved Packet Core
Specifications
10 specs
IM-MGW Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The IP Multimedia Media Gateway Function (IM-MGW) is a critical functional entity in the IP Multimedia Subsystem (IMS) architecture, responsible for all media-related processing in the user plane. It is controlled by the Media Gateway Control Function (MGCF) or, in later architectures, the Multimedia Resource Function Controller (MRFC) using protocols like H.248 (Megaco). The IM-MGW's primary role is to provide interoperability between the packet-switched IMS domain (using RTP/RTCP over IP) and legacy circuit-switched networks like the Public Switched Telephone Network (PSTN) or legacy cellular networks (using TDM or ATM bearer streams). It sits at the boundary between these domains, converting media streams in real-time.

Functionally, the IM-MGW executes several key media processing tasks. The core function is transcoding, which converts audio and video codecs between different formats (e.g., from AMR-NB used in a circuit-switched call to G.711 or EVS used in an IMS VoIP call). It also performs echo cancellation, tone generation and detection (e.g., DTMF), playout of announcements, and supports conferencing by mixing multiple media streams. For a call between an IMS subscriber and a PSTN subscriber, the MGCF sets up the call signalling, and then instructs the IM-MGW via H.248 to create a context with terminations: one termination facing the IMS network (IP-based RTP) and another facing the PSTN (TDM timeslot). The IM-MGW then bridges these terminations, performing the necessary media conversion bi-directionally.

Architecturally, the IM-MGW is part of the broader Media Gateway (MGW) family in 3GPP but is specifically dedicated to IMS services. It interfaces with the MGCF for call-related control, the MRFC for advanced media services like conferencing and announcements, and the Breakout Gateway Control Function (BGCF) for routing decisions. Its internal components include digital signal processors (DSPs) for media processing, IP network interfaces, and legacy network interfaces (e.g., E1/T1 trunks). By centralizing media processing functions, the IM-MGW allows the IMS core to remain purely SIP-based and agnostic to the underlying bearer technology, enabling seamless service delivery across heterogeneous networks.

Purpose & Motivation

The IM-MGW was created to solve the fundamental problem of interworking between the new, all-IP IMS network introduced in Release 5 and the vast installed base of legacy circuit-switched networks (PSTN and 2G/3G PLMN). IMS endpoints communicate using SIP and RTP over IP, while legacy networks use ISUP/TDM or other circuit-switched protocols. Without a media gateway, voice and video calls between these domains would be impossible, severely limiting IMS adoption.

Its creation was motivated by the need for a smooth, phased migration to IMS. Operators could not instantly replace all legacy switches and handsets. The IM-MGW, controlled by the MGCF, provided a bridge that allowed IMS subscribers to call anyone on the PSTN and vice versa, protecting existing investments and ensuring service continuity. It addressed the limitation of earlier VoIP gateways which were not integrated with the IMS control architecture (CSCFs, HSS). The IM-MGW is specifically designed to be controlled via standard protocols (H.248) by IMS control functions, enabling sophisticated service blending and policy-based media manipulation.

Furthermore, the IM-MGW solved the problem of media resource requirements within IMS. Even for pure IMS-to-IMS calls, services like conferencing, transcoding between different IMS codecs, and announcement playback require dedicated media processing resources. The IM-MGW, under the control of an MRFC, provides these resources as a shared, scalable pool for the entire IMS network. This separates media processing from call control, following the IMS principle of a layered architecture, which increases flexibility, scalability, and simplifies the introduction of new media features.

What changed in its specifications

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

TS 29.163Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 29.163: 30 clauses changed, with no change attributed to a release feature.

Full comparison in TS 29.163 →
TS 29.235Rel-12 → Rel-13

Defines SDP Capability Negotiation; adds RFC 5939 reference; adds optional/conditional SDPCapNeg configuration IEs; adds acap, tcap, pcfg, acfg attributes; updates TrGW connection point procedures.

Full comparison in TS 29.235 →

Technology family

IMS functions · Services › IMS

  1. R99 OSA-SCS
  2. Rel-5 AS, BGCF, CSCF, I-CSCF, IM-MGW, IM-SSF, MGCF, MRFC, MRFP, P-CSCF, S-CSCF
  3. Rel-6 IBCF, IMS-ALG, TrGW
  4. Rel-7 E-CSCF, IMS-AGW
  5. Rel-8 MRB, SCC AS
  6. Rel-9 EATF
  7. Rel-10 ATCF, ATGW
  • IM-MGW used together with MGCF
    “When referring specifically to the IP Multimedia CN Subsystem entity, the term IMS-MGW is used.” TS 23.002

Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.

Release Timeline

Detected Changes Across Releases

verified against 3GPP sources

Documented changes in 11 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.

Rel-5 introduced

Introduced in Rel-5 (release dating of the term; no individual change cited).

Rel-6 specification text

The IM-MGW is specified for the first time in this release: its Mn interface with the MGCF (H.248 profile) and its interworking, transcoding and DiffServ marking behaviour between Nb and Mb.

  • “The present document describes the protocol to be used on the Media Gateway Control Function (MGCF) – IM Media Gateway (IM-MGW) interface.” TS 29.332 v6.14.0
  • “It shall be possible for the IM CN subsystem to interwork with the CS networks (e.g. PSTN, ISDN or a CS domain of a PLMN)” TS 29.163 v6.12.1
  • “The IM-MGW shall always correct out-of-sequence delivery between Nb and Mb interfaces, either by re-ordering frames, or by dropping frames that are out of sequence.” TS 29.163 v6.12.1
Rel-7 specification text

IM-MGW gained new Rel-7 behaviour: multimedia interworking with H.245 relayed to the MGCF over H.248, reframing of H.263 and AMR, early-media source filtering, and multiple IP realms.

  • “Upon reception of the H.245 messages from the CS side at the IM-MGW, the IM-MGW shall forward those H.245 messages as binary data within H.248 messages” TS 29.163 v7.28.0
  • “If this information element is set, the IM-MGW shall silently discard incoming user plane data from disallowed sources.” TS 29.163 v7.28.0
  • “the IM-MGW needs to support the reframing of the H.263 video codec and the AMR audio codec between CS transport and PS transport as a minimum” TS 29.163 v7.28.0
Rel-8 specification text

IM-MGW gained MONA preference exchange handling in TS 29.163 and new MONA notification procedures over the Mn interface in TS 29.332, plus new transcoding and framing behaviour.

  • “The IM-MGW shall start sending MONA preference messages after receipt of the corresponding request from the MGCF and CS bearer establishment” TS 29.163 v8.32.0
  • “When the procedure "Notify MONA Preference Completed" is required the following procedure is initiated: the IM-MGW sends a NOT.req command” TS 29.332 v8.12.0
  • “The IM-MGW is in charge of constructing and sending the corresponding RTCP message to the IMS side to request for the media adaption” TS 29.332 v8.12.0
Rel-9 specification text

Rel-9 adds IM-MGW behaviour for Real-Time Text interworking: it monitors the CS side for text telephone signals, detects the text mode, and converts between text modem signals and RTP real-time text.

  • “The Interworking function in the IM-MGW shall support the detection of text modem signals on the CS side and the conversion between text/modem signals and Real-Time Text over RTP.” TS 29.163 v9.26.0
  • “This shall trigger the IM-MGW to insert an IWF to support RTT to PSTN text telephony conversion.” TS 29.163 v9.26.0
  • “The IM-MGW shall be compliant with ITU-T Recommendation G.168 [55] on detecting VBD.” TS 29.332 v9.5.0
Rel-10 specification text

IM-MGW gained new requirements in Rel-10: optional MTSI codec support, RTCP-APP-CMR handling, and ECN endpoint behaviour with rate adaptation and error notification to the MGCF.

  • “Upon receipt of a request to apply Explicit Congestion Notification the IM-MGW shall set the ECN field of the IP header” TS 29.163 v10.22.0
  • “the IM-MGW shall trigger rate adaptation in accordance with TS 26.114 [104].” TS 29.163 v10.22.0
  • “A IM-MGW may support the MTSI service defined in TS 24.173 [88] and may then support codecs according to TS 26.114 [104].” TS 29.163 v10.22.0
Rel-11 specification text

IM-MGW gained support for Multimedia Priority Service: applying MPS DSCP marking, priority resource allocation under congestion, and T.38 fax support at IMS terminations.

  • “If the IM-MGW receives an indication to apply a specific MPS DSCP marking to the user data transport packets, it shall apply this DSCP marking to the IP headers.” TS 29.163 v11.19.0
  • “The IM-MGW may then provide priority allocation of resources once a congestion threshold is reached.” TS 29.163 v11.19.0
  • “An IM-MGW supporting T.38 shall support the "UDPTL/UDP" and may support "TPKT/TCP" transport of FAX.” TS 29.332 v11.3.0
Rel-12 specification text

IM-MGW gained optional ECN endpoint support with rate adaptation on ECN-CE, plus ICE (at least ICE lite) support, and H.248 ICE attribute handling in Rel-12.

  • “Upon receipt of a request to apply Explicit Congestion Notification the IM-MGW shall set the ECN field of the IP header” TS 29.163 v12.16.0
  • “the IM-MGW shall trigger rate adaptation in accordance with” TS 29.163 v12.16.0
  • “if ICE is supported, the MGCF and IM-MGW shall at least support ICE lite” TS 29.163 v12.16.0
Rel-13 specification text

Rel-13 adds IM-MGW requirements for EVS: filtering and modifying EVS-CMR, mapping EVS-CMR to AMR-WB mode-sets, transcoding when configurations are incompatible, and optional rate adaptation with bw-info.

  • “The IM-MGW shall not modify the EVS-CMR to increase the maximum bit rate;” TS 29.163 v13.13.0
  • “The IM-MGW shall map received EVS-CMRs to the selected mode-set of the outgoing AMR-WB termination.” TS 29.163 v13.13.0
  • “the IM-MGW shall apply transcoding and shall handle the independent rate and mode control procedures towards the incoming and the outgoing networks.” TS 29.163 v13.13.0
Rel-17 specification text

IM-MGW ICE support was updated to RFC 8445/8839, adding ICE pacing: the IM-MGW calculates a Ta timer value, defaulting to 50 ms, and uses the higher of the two values for connectivity checks.

  • “the IM-MGW shall calculate Ta timer value based on the characteristics of the associated data or shall use the default value of 50 ms” TS 29.163 v17.3.0
  • “The MGCF and the IM-MGW may support ICE functionality as specified in IETF RFC 8445 [156] and IETF RFC 8839 [157]” TS 29.163 v17.3.0
  • “"a=ice-pacing" with wildcard sign "$" to reques” TS 29.332 v17.0.0
Rel-18 specification text

IM-MGW gains IVAS codec handling: rate control mapping of IVAS-CMRs to EVS/AMR-WB, optional transcoding to/from IVAS, and checks of SDP parameters supported by the IM-MGW.

  • “The IM-MGW shall map received IVAS-CMRs or RTCP-APP packets to the selected bit rates or mode-set of the outgoing EVS or AMR-WB termination.” TS 29.163 v18.1.0
  • “the IM-MGW shall apply transcoding and shall handle the independent rate and mode control procedures towards the incoming and the outgoing networks.” TS 29.163 v18.1.0
  • “The MGCF and the IM-MGW may support transcoding the IVAS speech and audio codec to and from another (mono-format) codec” TS 29.163 v18.1.0

Defining Specifications

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

SpecificationTitleRelease
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
TR 23.981 vj00 IPv4 IMS Interworking and Migration Study Rel-19 read
TS 26.454 vj00 EVS Codec Mapping for 3G CS Networks Rel-19 read
TS 29.163 vj00 Interworking between 3GPP IM CN and CS networks Rel-19 read
TS 29.235 vj00 SIP-I CS Core Network Interworking Rel-19 read
TS 29.332 vj00 MGCF-IM-MGW Interface Protocol (Mn) Rel-19 read
TS 33.107 vj00 Lawful Interception Architecture & Functions Rel-19 read
TS 33.108 vj00 LI Handover Interface Specification Rel-19 read
TS 33.127 vj80 Lawful Interception Architecture Rel-19 read