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

Glossary term · Core Network

TWAG

Trusted WLAN Access Gateway

Core Network →

TWAG is a core network gateway in a Trusted WLAN Access Network that provides IP connectivity and mobility management for devices accessing the 3GPP core via a trusted WLAN, terminating the S2a interface.

Introduced
Rel-11
Where
Core Network › Evolved Packet Core
Specifications
10 specs
Also in
Management
TWAG Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Trusted WLAN Access Gateway (TWAG) is a critical functional entity defined within the 3GPP architecture for trusted, non-3GPP access. It resides within the Trusted WLAN Access Network (TWAN) and serves as the gateway between the WLAN and the 3GPP Evolved Packet Core (EPC). Its primary role is to establish and manage IP connectivity sessions for User Equipment (UE) that connect via a trusted WLAN, such as a carrier-managed Wi-Fi hotspot. The TWAG implements the network-side functionality of the S2a reference point, which connects the TWAN to the Packet Data Network Gateway (PGW) in the EPC. This interface can be realized using either the GPRS Tunnelling Protocol (GTP) or the Proxy Mobile IPv6 (PMIPv6) protocol, allowing for flexible deployment scenarios and interworking with existing core network elements.

Architecturally, the TWAG works in conjunction with the Trusted WLAN AAA Proxy (TWAP) and the Trusted WLAN Access Point (TWAP) functions within the TWAN. When a UE attaches to the trusted WLAN, authentication and authorization are handled via the TWAP and the 3GPP AAA Server. Once authenticated, the TWAG is responsible for establishing a bearer path for the UE's data traffic. It creates a tunnel (GTP or PMIP) over the S2a interface to the PGW, which serves as the anchor point for the UE's IP session. This tunnel carries all user plane traffic, ensuring seamless service continuity and allowing the UE to access packet data services (e.g., IMS, internet) as if it were connected via a 3GPP radio access network.

The TWAG performs essential mobility and session management functions. It manages the binding between the UE's local IP address in the WLAN and its core network IP address (assigned by the PGW). For mobility events, such as handovers between different WLAN access points within the same TWAN or to/from a 3GPP access, the TWAG collaborates with the core network to update the bearer path with minimal disruption. It also interfaces with the Policy and Charging Rules Function (PCRF) via the TWAP or directly (depending on architecture) to enforce quality of service (QoS) and charging policies received from the core network. This ensures that service flows are treated appropriately according to the user's subscription and the requested service.

In summary, the TWAG is the central user-plane gateway in the trusted WLAN interworking architecture. It abstracts the underlying WLAN technology from the core network, presenting it as a trusted access network to the EPC. By providing standardized interfaces and protocols, it enables secure, seamless, and policy-controlled integration of high-performance WLAN into the mobile operator's service portfolio, forming a cornerstone for early Wi-Fi offloading and fixed-mobile convergence strategies.

Purpose & Motivation

The TWAG was introduced to solve the problem of seamless and secure integration of operator-controlled Wi-Fi networks into the 3GPP mobile packet core. Prior to its standardization, Wi-Fi was largely treated as an untrusted, external IP access network, requiring users to establish separate connections (often via VPNs) and resulting in a disjointed user experience with broken session continuity. The primary motivation was to leverage the growing deployment of high-quality WLAN infrastructure as a complementary radio access technology to cellular networks, enabling data offloading and improved capacity.

The creation of the TWAG, as part of the broader Trusted WLAN Access Network (TWAN) concept in 3GPP Release 11, was driven by the need for a standardized architecture. This architecture would allow mobile operators to treat their own or partner Wi-Fi networks as a trusted extension of their radio access network. The key problem it addressed was the lack of a standardized gateway function that could terminate core network protocols (GTP/PMIP) from the WLAN side, enabling tight coupling with the EPC for authentication, policy enforcement, and charging. This was a significant advancement over the untrusted access model defined earlier, which relied on IPsec tunnels initiated from the UE (eSWAG), which was more complex and less scalable.

By providing a network-based gateway, the TWAG enabled several crucial capabilities: seamless access to 3GPP packet data services (like IMS) over WLAN, support for network-controlled mobility and handover to/from 3GPP access, and the application of consistent policy and charging rules regardless of the access technology. This facilitated the operator's vision of Fixed-Mobile Convergence (FMC) and laid the groundwork for more integrated access in later 5G systems. It solved the limitations of previous non-integrated approaches by providing a standardized, secure, and efficient path for user plane traffic from a trusted WLAN directly into the mobile core.

What changed in its specifications

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

TS 23.402Rel-17 → Rel-18

Rel-18 added MPS subscription handling, DSCP QoS differentiation, and overload exemptions for WLAN access. It also extended WLAN Selection Policy for SNPN access mode with provisioning and discovery of SNPN-advertising networks.

Full comparison in TS 23.402 →
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

Non-3GPP access interworking · Core Network

  1. Rel-6 I-WLAN, WAG
  2. Rel-8 ANDSF, ePDG
  3. Rel-11 TWAG
  4. Rel-15 N3IWF
  5. Rel-16 TNGF, TWIF, W-AGF
  • TWAG counterpart in another generation: TNGF
    “An untrusted non-3GPP access network shall be connected to the 5G Core Network via a Non-3GPP InterWorking Function (N3IWF), whereas a trusted non-3GPP access network shall be connected to the 5G Core Network via a Trusted Non-3GPP Gateway Function (TNGF).” TS 23.501
  • TWAG coexists with ePDG
    “For authenticated non-roaming UEs, based on operator policy, the ePDG/TWAG may select a PDN GW based on DNS look up for the emergency APN, which is configured in the Emergency Configuration Data.” TS 23.402

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

TWAG is defined for the first time as the Trusted WLAN gateway terminating S2a, acting as default router and DHCP server, and serving as attach-trigger target and charging serving node.

  • “A Trusted WLAN Access Gateway (TWAG). This function terminates S2a. It also acts as the default router for the UE on its access link” TS 23.402 v11.10.0
  • “For GTP on S2a, the TWAG, described in clause 16.1.2, is requesting the PDN Gateway.” TS 23.402 v11.10.0
  • “When the Serving node is TWAG, this field includes the PLMN identifier used for UE authentication” TS 32.251 v11.13.0
Rel-12 specification text

Rel-12 specifies TWAG behaviour in new WLCP signalling over DTLS/UDP, PDN connectivity handling, PDN type selection and IP address allocation, and a TWAG control plane address signalled to the UE.

  • “When the PDN connection is established during the UE initiated WLCP procedure, the TWAG sends a MAC address, which is specific for the PDN connection” TS 23.402 v12.10.0
  • “If the requested PDN connection can be established, the TWAG shall send a PDN CONNECTIVITY ACCEPT message towards the UE.” TS 24.244 v12.3.0
  • “the value field of the item contains one or two TWAG control plane addresses” TS 24.302 v12.12.0
Rel-13 specification text

TWAG gained new behaviour in Rel-13: a TWAG-initiated PDN connectivity modification procedure with T3586 retransmission handling, plus TWAG-CDR charging and Rf reporting.

  • “The TWAG shall initiate the PDN connectivity modification procedure by sending a PDN MODIFICATION REQUEST message to the UE, starting the timer T3586” TS 24.244 v13.4.0
  • “On the first expiry of the timer T3586, the TWAG shall resend the PDN MODIFICATION REQUEST and shall reset and restart timer T3586.” TS 24.244 v13.4.0
  • “TWAG (TWAG-CDR) and P-GW (PGW-CDR)” TS 32.251 v13.6.1
Rel-14 specification text

TWAG gained emergency-service handling: it uses a configured emergency APN or static PDN GW, rejects additional emergency PDN connections, and applies new PDN connectivity request/accept rules for emergency request types.

  • “If the request type is "emergency" or "handover of emergency bearer services", the TWAG uses the APN configured for emergency bearer services” TS 24.244 v14.1.0
  • “When the WLCP PDN Connection Request contains an emergency request indication, the TWAG ignores any APN received from the UE in that message” TS 23.402 v14.7.0
  • “it is the ePDG/TWAG (and not the MME) that shall reject any additional emergency PDN Connection requests” TS 23.402 v14.7.0
Rel-15 specification text

TWAG gained multiple WLCP bearer support per PDN connection: it sets up and modifies a WLCP bearer for each dedicated S2a bearer, with new timers, and maintains the bearer mapping.

  • “The TWAG shall initiate the WLCP bearer setup procedure by sending a WLCP BEARER SETUP REQUEST message to the UE” TS 24.244 v15.2.0
  • “The TWAG shall maintain a 1 to 1 mapping between an S2a bearer and a WLCP bearer.” TS 23.402 v15.3.0
  • “The TWAG shall establish a separate WLCP bearer for each additional S2a dedicated bearer of the PDN connection” TS 24.302 v15.7.0
Rel-18 specification text

TWAG behaviour changed: it may set DSCP for uplink/downlink packets using QCI and ARP per operator policy and MPS notification, and can reject high-priority PDN connection requests only under limited conditions.

  • “The TWAG shall, based on operator policy, use the QCI and the ARP in WLCP bearer level QoS information to derive the DSCP value for downlink packets.” TS 24.302 v18.7.0
  • “The TWAG may set a DiffServ Code Point for uplink packets based on the receipt of the MPS subscription notification from the UE” TS 23.402 v18.3.0
  • “TWAG can reject PDN connection request for an APN from a UE and provide a Tw1 timer value to the UE.” TS 24.244 v18.0.0

Defining Specifications

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

SpecificationTitleRelease
TS 23.402 vj00 EPC for Non-3GPP Access (PMIP) Rel-19 read
TS 23.852 vc00 GTP-Based S2a for WLAN-EPC Access Rel-12 read
TS 24.161 vj00 Network-Based IP Flow Mobility (NBIFOM) Rel-19 read
TS 24.229 vk10 IMS SIP/SDP Call Control Protocol Rel-20 read
TS 24.244 vj00 Wireless LAN Control Plane Protocol Rel-19 read
TS 24.302 vj00 Access to EPC via non-3GPP networks; Stage 3 Rel-19 read
TS 32.240 vk10 3GPP Charging Architecture and Principles Rel-20 read
TS 32.251 vj00 PS Domain Charging Management Rel-19 read
TS 32.298 vk10 Charging Data Record Specification Rel-20 read
TS 32.299 vj00 Diameter Charging Applications for 3GPP Rel-19 read