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

Glossary term · Core Network

IMS-AGW

IMS Access Media Gateway

Core Network →

IMS-AGW is a media plane function within the IMS architecture that provides media processing, anchoring, and interworking for services like voice and video, operating under the control of a Media Gateway Control Function.

Introduced
Rel-7
Where
Core Network › 5G Core
Specifications
10 specs
Also in
Management
IMS-AGW Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The IMS Access Media Gateway (IMS-AGW) is a media processing entity defined in the IMS media plane architecture. It is not a signaling element but a bearer plane function responsible for the manipulation and forwarding of user media streams (voice, video). The IMS-AGW operates under the control of a Media Gateway Control Function (MGCF) or, more specifically in later architectures, an IMS Media Gateway Control Function (IMS-MGW-CF) or a Media Resource Function Controller (MRFC). Its operation is governed by protocols like H.248 (Megaco) or its IMS profile, which allows the controller to instruct the IMS-AGW to create, modify, and delete media processing contexts and terminations.

Functionally, the IMS-AGW performs several key roles. First, it acts as a media anchor point. This is crucial for services like Voice Call Continuity (VCC) or Single Radio Voice Call Continuity (SRVCC), where a call needs to be seamlessly transferred between different access networks (e.g., from LTE/VoLTE to 3G circuit-switched). By anchoring the media in the IMS-AGW, the remote party's media path remains unchanged, and only the leg to the moving UE is switched, minimizing interruption. Second, it provides media interworking functions, such as transcoding between different voice codecs (e.g., AMR-NB used in legacy networks to EVS used in VoLTE) and packetization protocol conversion (e.g., RTP to circuit-switched TDM bearers).

Third, the IMS-AGW enables media-based services like conferencing (mixing multiple audio/video streams), playing tones and announcements, and facilitating lawful interception by providing a controlled point for duplicating media streams. Architecturally, it sits at the boundary between the all-IP IMS domain and legacy circuit-switched networks or other IP networks with different capabilities. It contains resources like Digital Signal Processors (DSPs) for codec operations and packet processing engines. The separation of control (MGCF/MRFC) and media (IMS-AGW) follows the gateway decomposition model, promoting scalability, flexibility, and the use of standard interfaces.

Purpose & Motivation

The IMS-AGW was introduced to address specific challenges in the evolution towards a pure, end-to-end IP multimedia network. Early IMS visions imagined direct IP-based media paths between endpoints. However, practical deployment revealed several scenarios where intelligent media plane intervention was necessary. Legacy networks (2G/3G circuit-switched) would coexist with IMS for decades, requiring seamless interworking for voice calls. Furthermore, not all user equipment or access networks support the same set of advanced codecs, necessitating transcoding to ensure interoperability.

A key driver was the need for service continuity during mobility events, particularly SRVCC. Without a media anchor, handing over a VoLTE call from LTE to a 3G circuit-switched network would require re-establishing the entire media path with the remote party, causing unacceptable audio gaps. The IMS-AGW provides a stable anchor point in the home IMS network, allowing for a swift update of only one leg of the call. This solved a major obstacle for the commercial launch of VoLTE, as it guaranteed voice service continuity even when users moved out of LTE coverage.

Additionally, regulatory requirements for lawful interception mandated a network-controlled point where media could be copied. A distributed, peer-to-peer media model made this difficult. Concentrating media processing in a managed network function like the IMS-AGW provided a natural point for such intercepts. The decomposition into a separate control function (MGCF) and media gateway (IMS-AGW) also aligned with broader industry trends towards softswitch architectures, allowing operators to source control and media hardware/software independently and scale them according to different traffic patterns.

What changed in its specifications

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

TS 23.334Rel-17 → Rel-18

Rel-18 adds IVAS codec handling clauses, references to IVAS specifications, a definition, and modifies EVS max-red parameter selection.

Full comparison in TS 23.334 →
TS 24.229Rel-18 → Rel-19

Rel-19 adds Rich Call Data support to TS 24.229, including the DC-Info header, rcd-np Call-Info parameter, and RCD info retrieval and verification across originating, terminating, IBCF and AS behaviour. It also adds MPS for Messaging, eCall alignment with EN 17184:2024 (test eCall and updated-MSD transfer), and satellite identifiers in P-Access-Network-Info.

Full comparison in TS 24.229 →

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
  • IMS-AGW used together with P-CSCF
    “The P-CSCF A allocates an IMS-AGW on the ground as default. P-CSCF A interacts with IMS-AGW on the ground to allocate transport resources based on the mechanism defined in TS 23.334 [74].” TS 23.228

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 13 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-7 introduced

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

Rel-9 specification text

TS 23.334 and TS 29.334 first appear in Rel-9, specifying the IMS-AGW's NAT/NAPT traversal, IP realm handling, latching, policing and Iq procedures under IMS-ALG control.

  • “The IMS-AGW shall provide the NAPT enforcement function, i.e. change the address and port number of the media packets as they traverse the IMS-AGW” TS 23.334 v9.3.0
  • “The IMS-ALG shall request the IMS-AGW to allocate transport addresses/resources to enable media to traverse the IMS-AGW.” TS 23.334 v9.3.0
  • “the IMS-AGW shall dynamically learn the required destination address via the source address/port of incoming media. This mechanism is known as "latching".” TS 23.334 v9.3.0
Rel-10 specification text

IMS-AGW gained ECN support in Rel-10: acting as an ECN endpoint, forwarding ECN bits, triggering rate adaptation on ECN-CE, plus ATCF/ATGW support in the reference model and Iq procedures.

  • “trigger rate adaptation request towards the ECN-capable peer when receiving in the incoming IMS media flow IP packets marked with ECN-CE” TS 23.334 v10.5.0
  • “the IMS-AGW shall forward ECN bits within IP packets unmodified. Any RTCP feedback received shall be passed unchanged.” TS 23.334 v10.5.0
  • “The reference model for the IMS-ALG and the IMS-AGW supporting the ATCF/ATGW function is shown in Figure 1a below.” TS 29.334 v10.7.0
Rel-11 specification text

IMS-AGW gained Multimedia Priority Service support in Rel-11: priority information on contexts, MPS DSCP marking of user-plane packets, priority resource allocation under congestion, and congestion indication to the IMS-ALG.

  • “If the IMS-AGW 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 23.334 v11.2.0
  • “The IMS-AGW may then provide priority allocation of resources once a congestion threshold is reached.” TS 23.334 v11.2.0
  • “The support of the modification of the Priority Indicator value is optional for the IMS-AGW” TS 29.334 v11.3.0
Rel-12 specification text

IMS-AGW gained new capabilities in Rel-12: media plane security (e2ae with TLS/DTLS), ICE support, CVO and image attribute handling, and an enhanced WebRTC variant (eIMS-AGW).

  • “the IMS-AGW enhanced for WebRTC (eIMS-AGW) to support WebRTC client access to IMS” TS 29.334 v12.10.0
  • “may be provided for an SDP m-line in the local and remote descriptor if the IMS-AGW supports ICE” TS 29.334 v12.10.0
  • “the IMS-AGW shall accept TLS renegotiation only if it is secured according to IETF RFC 5746 [47].” TS 23.334 v12.13.0
Rel-13 specification text

IMS-AGW gained new capabilities in Rel-13: video Region-of-Interest handling (Predefined, Arbitrary, FECC modes), SDP capability negotiation, and H.248 attributes for ROI, with IP version interworking and bandwidth adjustment.

  • “if the IMS-AGW applies video transcoding, it shall keep the predefined ROI information unchanged during the transcoding” TS 23.334 v13.13.0
  • “the IMS-AGW shall reserve resources for all of those configurations that it supports” TS 23.334 v13.13.0
  • “may be provided for an m-line in the local and remote descriptor if the IMS-AGW supports the Arbitrary ROI mode” TS 29.334 v13.11.0
Rel-14 specification text

IMS-AGW gained new procedures in Rel-14: RTP-level pause/resume and RTCP codec control (FIR/TMMBR) signalling, with transparent forwarding of the RTCP feedback messages, and updated RTCP port allocation.

  • “The IMS-AGW shall then assign resources for the requested RTCP control flow and shall transparently forward the RTCP "CCM PAUSE" packets between incoming and outgoing networks.” TS 23.334 v14.9.0
  • “the IMS-AGW shall transparently forward received RTCP FIR feedback message, and received RTCP TMMBR and TMMBN feedback messages between the incoming and outgoing networks.” TS 23.334 v14.9.0
  • “to indicate that the IMS-AGW shall be prepared to receive and is allowed to send, respectively, the RTCP CCM feedback messages FIR, and/or TMMBR and TMMBN.” TS 29.334 v14.7.0
Rel-15 specification text

TS 23.228 now states that the IMS-AGW, together with the P-CSCF, may support both IPv4 and IPv6 and may interwork between IP versions for UEs using 5GS PDU sessions.

  • “Here the P-CSCF and IMS-AGW may support both IP versions and/or may do interworking depending IP version used within the IMS.” TS 23.228 v15.5.0
Rel-16 specification text

IMS-AGW now supports transparent forwarding of RTCP Delay Budget Information (DBI) feedback messages, signalled via the "3gpp-delay-budget" rtcp-fb parameter, in addition to the existing CCM messages.

  • “The "rtcp-fb" SDP attribute with the "3gpp-delay-budget" feedback parameter” TS 29.334 v16.4.0
  • “shall transparently forward the RTCP DBI feedback messages between incoming and outgoing networks” TS 23.334 v16.4.0
Rel-17 specification text

IMS-AGW gained ICE pacing (Ta timer) handling and updated DTLS-SRTP e2ae media security behaviour, including fingerprint exchange with the IMS-ALG over Iq and acting as DTLS server or client.

  • “the IMS-AGW shall calculate Ta timer value based on the characteristics of the associated data or shall use the default value of 50 ms” TS 23.334 v17.3.0
  • “the IMS-AGW shall send the fingerprint of its certificate via Iq interface to the IMS-ALG.” TS 23.334 v17.3.0
  • “the IMS-AGW shall act as either a DTLS server or client in the DTLS session.” TS 23.334 v17.3.0
Rel-18 specification text

Rel-18 adds IMS-AGW support for transcoding the IVAS codec with SDP parameter checks, and lets IMS-AGW act as a DC Application Proxy for IMS Data Channels.

  • “The IMS-ALG and the IMS-AGW may support transcoding the IVAS speech and audio codec to and from another (mono-format) codec” TS 23.334 v18.1.0
  • “When acting as DC Application Proxy, the IMS-AGW/TrGW terminates UDP/DTLS/SCTP towards both peer endpoints.” TS 23.228 v18.12.0
Rel-19 1 CR

IMS-AGW gains new roles in Rel-19: it may be deployed on satellites for UE-Satellite-UE media optimization, with P-CSCF selecting and re-selecting it, and it sends RTCP RR on PCRF/PCF failure.

  • “the IMS-AGW may be deployed on the satellite(s) that host the gNB and UPF (UL CL and L-PSA) of the 5GC.” TS 23.228 v19.8.0
  • “The H.248 MOD request IMS-AGW to send the RTCP RR Package to termination T1.” TS 23.334 v19.0.0
  • Call setup of UE-Satellite-UE communication in IMS with IMS-AGW on board TS 23.228CR1492
Rel-20 specification text

IMS-AGW gains new roles in Rel-20: allocating transport resources and gate control for IMS Voice over NB-IoT(GEO) flows, and compressing/restoring RTP headers for RTP header optimized media.

  • “The IMS-AGW compresses the RTP header as per RTP header optimized media;” TS 23.228 v20.1.0
  • “the IMS-AGW restores the RTP header and then forwards the packet to the IMS core.” TS 23.228 v20.1.0
  • “The S-CSCF forwards the 200 OK to the P-CSCF, which then requests the IMS-AGW to open the gate for the media flow.” TS 23.228 v20.1.0

Defining Specifications

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

SpecificationTitleRelease
TS 23.334 vj00 IMS-ALG to IMS-AGW Interface (Iq) Stage 2 Rel-19 read
TS 24.229 vk10 IMS SIP/SDP Call Control Protocol Rel-20 read
TS 29.334 vj00 IMS-ALG to IMS-AGW Interface Protocol Rel-19 read
TS 29.866 vj00 IMS Disaster Prevention & Restoration Enhancement Rel-19 read
TS 32.260 vk10 IMS Charging Management Rel-20 read
TS 32.298 vk10 Charging Data Record Specification Rel-20 read
TS 32.299 vj00 Diameter Charging Applications for 3GPP 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