Description
The Access Transfer Gateway (ATGW) is a critical user plane entity defined within the 3GPP architecture for IP Flow Mobility (IFOM) and seamless Wireless Local Area Network (WLAN) interworking. Functionally, it operates as a packet data network gateway (PGW) or traffic offload function that terminates the S2a, S2b, or S2c reference points for non-3GPP access, while also connecting to the SGi interface towards the packet data network (e.g., the IMS). Its primary architectural role is to serve as a common IP anchor point for a User Equipment's (UE's) IP flows, regardless of whether those flows are being routed via a 3GPP access network (like LTE or 5G NR) or a trusted/untrusted non-3GPP access network (like Wi-Fi). This anchoring is fundamental to the Access Network Discovery and Selection Function (ANDSF) and Multi-Access Packet Data Network Connectivity (MAPCON) procedures.
Technically, the ATGW works in conjunction with control plane functions like the 3GPP AAA Server and the Mobility Management Entity (MME) or Access and Mobility Management Function (AMF). When a UE establishes a multi-access PDN connection, the ATGW is selected as the point where the user plane converges. It maintains the UE's IP address and performs policy enforcement, charging, and lawful interception functions for the anchored flows. During an access transfer—for instance, moving a video call from LTE to Wi-Fi—the ATGW manages the redirection of the specific IP flow(s). It updates the routing and potentially performs deep packet inspection to apply the correct Quality of Service (QoS) and charging policies based on the new access type and network policies.
The ATGW's internal components include interfaces for GTP (GPRS Tunneling Protocol) or PMIP (Proxy Mobile IP) for 3GPP access, as well as support for DSMIPv6 (Dual-Stack Mobile IPv6) or GTP over S2a/S2b for non-3GPP access. It integrates with the Policy and Charging Rules Function (PCRF) via the Gx interface to receive dynamic policy and charging control (PCC) rules. A key capability is its ability to support multiple concurrent tunnels for the same UE associated with different access technologies, allowing for per-flow routing decisions. This enables advanced traffic steering scenarios where, for example, a latency-sensitive gaming flow stays on 5G while a large file download is offloaded to Wi-Fi, all managed from the single ATGW anchor point.
In the broader network ecosystem, the ATGW is a cornerstone for realizing true network convergence. It hides the complexity of the underlying access networks from the service layer (e.g., IMS), presenting a stable IP endpoint. This allows service continuity for IMS-based Voice over Wi-Fi (VoWiFi) and Video over LTE (ViLTE) as defined in specifications like 3GPP TS 23.237 (IMS Service Continuity). Its role has evolved with network function virtualization (NFV), where it can be implemented as a virtualized network function (VNF) for greater scalability and flexibility in cloud-native 5G architectures, though its core anchoring function remains essential for multi-access edge computing (MEC) and uplink classifier (UL CL) scenarios in 5G.
Purpose & Motivation
The ATGW was introduced to solve the critical problem of seamless service continuity and efficient traffic steering across heterogeneous radio access networks. Prior to its standardization, handovers between 3GPP cellular networks and WLANs were typically break-before-make, causing session interruptions for real-time services like voice calls. Early non-3GPP interworking solutions often relied on network-based mobility (e.g., PMIP) which could be inefficient for fine-grained, flow-level steering. The industry needed a standardized mechanism to leverage multiple access radios on a device simultaneously for load balancing and enhanced user experience, without requiring applications to be aware of the underlying network changes.
Historically, the motivation stemmed from the proliferation of Wi-Fi and the desire to integrate it seamlessly into the mobile operator's service portfolio. Operators wanted to use Wi-Fi not just as an offload pipe for best-effort data, but as a trusted, managed extension of their cellular network capable of delivering high-quality voice and video services. The ATGW, as part of the Evolved Packet Core (EPC) defined in 3GPP Release 10, provided the necessary architectural anchor to make this possible. It addressed the limitations of previous loose-coupling approaches by enabling tight coupling for the user plane, allowing policy-controlled, per-IP-flow mobility between accesses based on operator policies, network conditions, and user preferences.
Furthermore, the ATGW enables advanced traffic management paradigms like IP Flow Mobility (IFOM) and Multi-Access PDN Connectivity (MAPCON), which were not feasible with simpler offload gateways. IFOM allows different IP flows of the same PDN connection to be routed over different access networks simultaneously, while MAPCON allows a UE to have multiple PDN connections to the same APN over different accesses. The ATGW is the central node that makes these complex routing decisions actionable in the user plane, solving the problem of how to maintain a consistent IP address and session state while physically moving packets through different network paths. This purpose remains highly relevant in 5G for supporting access traffic steering, switch, and splitting (ATSSS) features.
What changed in its specifications
The latest release-to-release comparison of specifications that define ATGW. Each summary describes the whole specification, not only this term.
Rel-19 brings only minor changes to TS 23.237: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 23.237 →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 →Technology family
IMS functions · Services › IMS
- R99 OSA-SCS
- Rel-5 AS, BGCF, CSCF, I-CSCF, IM-MGW, IM-SSF, MGCF, MRFC, MRFP, P-CSCF, S-CSCF
- Rel-6 IBCF, IMS-ALG, TrGW
- Rel-7 E-CSCF, IMS-AGW
- Rel-8 MRB, SCC AS
- Rel-9 EATF
- Rel-10 ATCF, ATGW
- ATGW used together with ATCF
“The Access Transfer Gateway (ATGW) is controlled by the ATCF” TS 23.237
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 sourcesDocumented changes in 6 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-10 first specifies the ATGW as a media anchor controlled by the ATCF, kept in the media path and updated with the new CS access leg during SRVCC access transfer.
- “The Access Transfer Gateway (ATGW) is controlled by the ATCF and, if SRVCC enhanced with ATCF is used, stays in the session media path” TS 23.237 v10.13.0
- “perform the Access Transfer and update the ATGW with the new media path for the (CS) access leg, without requiring updating the remote leg;” TS 23.237 v10.13.0
- “the Iq reference point is used for IMS sessions that the IMS-ALG (ATCF) decides to anchor at the IMS-AGW (ATGW)” TS 23.334 v10.5.0
ATGW behaviour was extended in TS 23.237: ATCF may anchor voice or voice and video media in the ATGW, with Iq interface to a co-located ATCF and a requirement on media gateways in the path.
- “the ATCF may decide, based on information not available earlier in the procedure, to anchor the session and allocate ATGW resources for voice media or voice and video media” TS 23.237 v11.11.0
- “If the ATCF is co-located with P-CSCF, the interface between ATCF and ATGW is Iq, according to TS 23.334 [30].” TS 23.237 v11.11.0
- “Anchoring Support of CS to PS SRVCC in the serving network requires that there is no other media gateway on the media path between UE and ATGW.” TS 23.237 v11.11.0
The IMS-ALG (ATCF) and IMS-AGW (ATGW) gained image size negotiation for video using the SDP imageattr attribute, with the ATGW's supported image sizes preconfigured in the ATCF and used in access transfer flows.
- “The IMS-ALG (ATCF) and the IMS-AGW (ATGW) may support a media-level SDP image attribute "a=imageattr" defined in IETF RFC 6236 [24]” TS 23.334 v12.13.0
- “The list of image sizes per payload type supported by the IMS-AGW (ATGW) shall be preconfigured in the IMS-ALG (ATCF).” TS 23.334 v12.13.0
TS 23.237 added codec-handling text for ATGW in SRVCC: ATGW or CS MGW may need a codec mode change, and the ATCF selects a codec so ATGW does no transcoding.
- “therefore there is no transcoding in ATGW but there may be transcoding in CS-MGW” TS 23.237 v14.2.0
- “It may be that the CS MGW or ATGW supports the audio Codec that is compatible or equal to the audio Codec” TS 23.237 v14.2.0
ATGW/ATCF functions now also apply when 5G-SRVCC is used, extending the ATGW media anchoring role beyond SRVCC enhanced with ATCF.
- “if (5G-)SRVCC enhanced with ATCF is used, stays in the session media path for the duration of the call” TS 23.237 v16.4.0
- “When (v)SRVCC enhanced with ATCF is used or when 5G-SRVCC is used, additional functions of IMS Service Continuity are provided by the ATCF/ATGW” TS 23.237 v16.4.0
A new IVAS codec clause applies the PS session origination handling to IVAS, with codec 1 information not signalled to the IMS-AGW(ATGW) and IVAS parameters for both offerer and answerer terminations signalled during PS to CS Access Transfer.
- “the IVAS related parameters for the terminations towards the SDP offerer and the SDP answerer shall be signalled towards the IMS-AGW during a PS to CS Access Transfer procedure” TS 23.334 v18.1.0
Defining Specifications
3GPP specifications that define or reference ATGW, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.237 vj00 | IMS Service Continuity (ISC) Stage 2 | Rel-19 read |
| TS 23.334 vj00 | IMS-ALG to IMS-AGW Interface (Iq) Stage 2 | Rel-19 read |
| TS 26.114 vk11 | IMS Multimedia Telephony Client | Rel-20 read |
| TR 26.916 ve20 | eSRVCC Transcoding Minimization Study | Rel-14 read |
| TS 29.162 vj00 | IMS-IP Network Interworking | Rel-19 read |
| TS 29.238 vj00 | H.248 Profile for IBCF-TrGW Interface | Rel-19 read |
| TS 29.334 vj00 | IMS-ALG to IMS-AGW Interface Protocol | Rel-19 read |
| TR 29.949 vj00 | VoLTE IMS Roaming Architecture & Procedures | Rel-19 read |
| TS 32.260 vk10 | IMS Charging Management | Rel-20 read |