Description
The Wireless Access Gateway (WAG) is a standardized network function defined by 3GPP to facilitate secure and managed access from non-3GPP IP networks, primarily Wireless Local Area Networks (WLANs), into the 3GPP mobile core. Architecturally, it resides at the boundary between the untrusted non-3GPP IP access network and the trusted 3GPP core, often interfacing with a Packet Data Gateway (PDG) for tunneling user plane traffic. The WAG's primary function is to enforce policy-based access control. It authenticates and authorizes user equipment (UE) attempting to access 3GPP services via a WLAN hotspot, typically using Extensible Authentication Protocol (EAP) methods over the Ww reference point. This process involves interacting with the 3GPP AAA (Authentication, Authorization, and Accounting) infrastructure, including the Home Subscriber Server (HSS), to validate subscriber credentials and service profiles.
From a data plane perspective, the WAG does not terminate user IP traffic itself but rather acts as an enforcement point. It ensures that only authorized traffic from authenticated UEs is forwarded toward the PDG, which establishes an IPsec tunnel (using IKEv2) with the UE for secure data transmission. The WAG may perform packet filtering, policing, and routing based on policies received from the AAA server. This architecture, defined in the early 3GPP releases for WLAN interworking, creates a clear demarcation: the WAG handles access control and initial routing at the network edge, while the PDG handles secure tunneling and connectivity to external packet data networks (PDNs).
The WAG's role is integral to the 3GPP System Architecture Evolution (SAE) for non-3GPP access. It supports mobility scenarios, allowing a UE to discover and select a WAG for access. While later architectures evolved with the introduction of the ePDG for untrusted non-3GPP access in EPS and the Non-3GPP Interworking Function (N3IWF) in 5GS, the WAG concept laid the foundational principles of a dedicated gateway for managing and securing the ingress point from external wireless networks into the mobile core, ensuring operator control over service access and security.
Purpose & Motivation
The WAG was created to address the growing need for mobile operators to integrate WLAN hotspots with their cellular networks in a controlled and secure manner. In the early 2000s, WLANs offered high bandwidth but lacked the integrated authentication, billing, and security frameworks of cellular networks. The purpose of the WAG was to provide a standardized gateway that could bring WLAN access under the operator's umbrella, enabling new business models like seamless offload and unified service offerings.
Prior to its standardization, ad-hoc WLAN integration posed significant problems: there was no standardized method for a cellular subscriber to use their SIM credentials for WLAN access, no guaranteed security for the access link, and no way for the operator to apply consistent policy and charging. The WAG solved these by defining a clear architectural component that interfaced with the existing 3GPP AAA infrastructure. This allowed operators to leverage their subscriber database (HSS) for WLAN authentication and to enforce access policies uniformly, regardless of the radio technology.
Its creation was motivated by the desire for network convergence and service continuity. It enabled scenarios where a user could start a data session on a cellular network and, upon entering WLAN coverage, have their session securely handed over or offloaded, with the operator maintaining visibility and control. The WAG standardized the critical first hop from an untrusted, non-3GPP network into the trusted core, establishing the security and policy enforcement model that later evolved for other access types in 4G and 5G.
What changed in its specifications
The latest release-to-release comparison of specifications that define WAG. Each summary describes the whole specification, not only this term.
Added QoS provisioning for 3GPP/WLAN interworking, IMS emergency call support over WLAN, private network access, external AAA server authentication/accounting, and external AAA server initiated tunnel disconnection.
Full comparison in TS 23.234 →Formalization of WLAN files adds optional WLAN parameter storage and new direct access conditions to HPLMN, affecting selection procedures.
Full comparison in TS 24.234 →Technology family
Non-3GPP access interworking · Core Network
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 3 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.
The WAG's Wg-interface procedures are specified for the first time: it receives Policy Download Requests to install or modify routing policies and handles routing policy removal with the 3GPP AAA Server.
- “On receipt of the Policy Download Request, the WAG shall check whether or not the user has already routing policies stored:” TS 29.234 v6.18.0
- “the WAG shall take necessary steps to provision the new routing policy indicated in the routing policy AVP for the user” TS 29.234 v6.18.0
- “Wg Reference point between a 3GPP AAA Server/Proxy and a 3GPP WAG” TS 29.234 v6.18.0
The 3GPP AAA Server must now verify PDG-provided routing policies against Operator Determined Barring policies before installing them at the WAG via Wg, returning an error on conflict.
- “The 3GPP AAA Server shall verify that routing policies received from the PDG do not conflict with Operator Determined Barring related routing policies.” TS 29.234 v7.15.0
- “The 3GPP AAA Server shall store the Routing-Policy AVP and use Wg procedures to install this policy at the WAG.” TS 29.234 v7.15.0
TS 28.601 and 28.602 appear for the first time in Rel-12, specifying NRM IRP requirements and an IOC for the WLAN Access Gateway (WAG) for Interworking WLAN management.
- “This IOC represents WLAN Access Gateway (WAG) functionality. For more information about the WAG, see 3GPP TS 23.234 [5].” TS 28.602 v12.0.0
- “REQ-CN_WLAN-CON-001 The NRM defined by this IRP shall contain WAG specific IOCs and related definitions.” TS 28.601 v12.0.0
Defining Specifications
3GPP specifications that define or reference WAG, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.234 vd10 | 3GPP-WLAN Interworking Index | Rel-13 read |
| TS 24.234 vc20 | 3GPP-WLAN Interworking Procedures | Rel-12 read |
| TS 28.601 vc00 | Telecom management; CN and non-3GPP access NRM IRP Requirements | Rel-12 read |
| TS 28.602 vc00 | CN & non-3GPP NRM IRP Information Service | Rel-12 read |
| TS 29.234 vb20 | WLAN-3GPP Interworking Protocols | Rel-11 read |
| TS 32.102 vj00 | Telecom Management Physical Architecture Framework | Rel-19 read |
| TS 32.808 v800 | Common Profile Storage Framework for User Data | Rel-8 read |
| TS 32.820 v801 | Study on Evolved 3GPP Charging Architecture | Rel-8 read |
| TS 33.234 vj00 | 3GPP-WLAN Interworking Security | Rel-19 read |