Access Transfer Gateway

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.

Key Features

• Seamless IP session continuity during handovers between 3GPP and non-3GPP access
• Per-IP-flow mobility and routing based on network policies (IFOM)
• Common IP address anchor point for multi-access PDN connections
• Integration with PCRF for dynamic policy and charging enforcement
• Support for multiple tunneling protocols (GTP, PMIP, DSMIPv6)
• Enables simultaneous use of multiple radios for traffic steering and aggregation

Evolution Across Releases

Defining Specifications