Description
The Trusted WLAN Interworking Function (TWIF) is a critical component within the 5G Core (5GC) architecture, specifically defined for Non-3GPP Interworking. It functions as a Network Function (NF) that provides a secure, standardized interface for User Equipment (UE) to connect to the 5GC via a trusted Wireless Local Area Network (WLAN), such as a carrier-managed or enterprise Wi-Fi network. The TWIF terminates the N1, N2, and N3 reference points over the non-3GPP access, effectively bridging the WLAN access network to the 5GC's control and user planes. On the network side, it interfaces with other core functions like the Access and Mobility Management Function (AMF) over N2 for control signaling, the Session Management Function (SMF) via the N4 interface for user plane policy, and the Unified Data Management (UDM) for authentication credentials.
Architecturally, the TWIF comprises two main logical entities: the Trusted WLAN Access Point (TWAP) and the Trusted WLAN AAA Proxy (TWAP). The TWAP handles the lower-layer WLAN-specific protocols and the IPsec/IKEv2 or TLS-based secure tunnel establishment with the UE. The TWAP acts as an Authentication, Authorization, and Accounting (AAA) proxy, interfacing with the 3GPP AAA Server (part of the UDM) to perform 5G-compliant authentication using the 5G Authentication and Key Agreement (5G-AKA) or EAP-AKA' methods. This ensures the UE is authenticated with the same credentials and security level as for 3GPP radio access.
In operation, when a UE attempts to attach via a trusted WLAN, it establishes a secure tunnel (IPsec or TLS) with the TWIF. The TWIF facilitates the primary authentication procedure with the 5GC, relaying Extensible Authentication Protocol (EAP) messages between the UE and the 3GPP AAA Server. Upon successful authentication, the TWIF registers the UE with the AMF, enabling mobility and session management. For user plane traffic, the TWIF acts as a Network Address Translation (NAT) point or a User Plane Function (UPF) N3 termination point, routing data packets between the WLAN and the 5GC's data network. It also enforces policies received from the Policy Control Function (PCF), such as quality of service (QoS) and charging rules, ensuring a consistent service experience across access types.
Its role is pivotal for converged access, allowing operators to offload traffic to Wi-Fi networks while maintaining core network security, subscriber management, and service continuity. It integrates WLAN into the 5G service-based architecture, making it a managed, trusted access type rather than an untrusted external network.
Purpose & Motivation
The TWIF was created to address the growing need for seamless and secure integration of high-performance WLAN networks into the 5G ecosystem. Prior to 3GPP Release 16, non-3GPP access (like Wi-Fi) was often treated as an untrusted network, requiring the UE to establish a VPN-like tunnel (via a Non-3GPP Interworking Function, N3IWF) for secure access, which added complexity and overhead. For operator-managed or certified Wi-Fi networks that meet specific security requirements, this untrusted model was inefficient.
The purpose of the TWIF is to define a "trusted" non-3GPP access path, where the access network itself is considered secure, eliminating the need for per-UE IPsec tunnels for security. This reduces signaling load, connection setup time, and processing overhead on both the UE and the network. It solves the problem of providing a streamlined, carrier-grade Wi-Fi experience that is fully integrated with 5G core services, including authentication, policy control, charging, and mobility support. This enables new use cases like fixed wireless access (FWA) over Wi-Fi, seamless mobility between 5G NR and Wi-Fi, and efficient traffic steering.
Historically, interworking with WLAN was defined in earlier releases (e.g., S2a-based trusted access in EPS), but these were not natively integrated into the new service-based architecture of 5GC. TWIF in Release 16 redefined this interworking for the 5G era, aligning it with cloud-native principles, network slicing, and unified policy framework. It addresses the limitation of previous approaches by providing a native 5GC Network Function with standard service-based interfaces (e.g., Ntwif), enabling automation, scalability, and consistent service exposure.
What changed in its specifications
The latest release-to-release comparison of specifications that define TWIF. Each summary describes the whole specification, not only this term.
Rel-19 added MPQUIC steering to multi-access PDU sessions, XR and media handling, and an Energy Information Function. It also added Local Offloading Management for edge computing, Vertical Federated Learning for AI/ML, and Ambient IoT text.
Full comparison in TS 23.501 →Rel-19 adds satellite NG-RAN access text, LP-WUS/WUR assistance and disabling, ATUC RAT utilization control, and network-controlled slice selection with S-NSSAI time validity to TS 24.501. It also adds ATSSS Phase 4 multi-access and 5G ProSe multi-hop relay support.
Full comparison in TS 24.501 →Architecture
Where it sits in the network
- Mobile Network → 5G Core → TWIF (Access Networks)
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 4 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 TWIF is specified for the first time in Rel-16 as the trusted WLAN function that registers N5CW devices to 5GC and establishes PDU sessions on their behalf using NAS signalling.
- “Trusted WLAN Interworking Function (TWIF): It provides interworking functionality that enables N5CW devices to access 5GC.” TS 23.501 v16.20.0
- “The TWIF creates a 5GC Registration Request message on behalf of the N5CW device.” TS 23.502 v16.19.0
- “A trusted WLAN interworking function (TWIF) provides functionalities for a non-5G capable over WLAN (N5CW) device to access 5GCN, including:” TS 24.501 v16.15.0
TWIF behaviour was changed in Rel-17: Decorated NAI handling no longer depends on TWIF support, and AMF selection, TAI configuration and slicing clarifications for TWIF scenarios were revised.
- “If the TWIF receives a Decorated NAI, in Registration Request message the TWIF send the NAI which corresponds to the HPLMN by removing the decoration” TS 23.502 v17.15.0
- Clarification on support of slicing in TWIF scenario TS 23.501CR3422
- “TWIF procedure correction” TS 33.501 v17.16.0
In Rel-18 TWIF behaviour was extended to SNPNs and to decorated NAI handling: the TWIF selects the visited AMF from the decoration part and converts the decorated NAI to a SUPI-format NAI in the Registration Request.
- “the TWIF shall select the AMF in the visited PLMN/SNPN as per decoration part and remove the decoration part from the Decorated NAI” TS 23.502 v18.14.0
- “the TWIF shall first convert the decorated NAI into an NAI as specified in TS 23.502 [9]” TS 24.501 v18.14.0
- “may access 5GC in an SNPN via a trusted WLAN access network that supports a TWIF function” TS 23.501 v18.12.0
Rel-19 adds mobility support for N5CW devices moving between TNAPs or TWAPs connected to the same TWIF, with re-authentication that reuses the fast transition procedures with KTWIF.
- “Clause 7A.2.4.2 describes how WLAN UEs that do not support 5GC NAS (N5CW) moves from one TNAP to another TNAP connecting to the same TWIF” TS 33.501 v19.7.0
- “The FT procedures given in clause 7A.2.1.2 are followed with TNGF being replaced by TWIF and KTNGF being replaced by KTWIF .” TS 33.501 v19.7.0
- Mobility of the N5CW device connected to a TWAP to another TWAP connected to the same TWIF TS 24.502CR0317
Defining Specifications
3GPP specifications that define or reference TWIF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.501 vk30 | 5G System Architecture | Rel-20 read |
| TS 24.501 vk10 | 5GS NAS Protocol Specification | Rel-20 read |
| TS 24.502 vk00 | Non-3GPP Access Network Discovery and Selection | Rel-20 read |
| TS 29.214 vk00 | Rx Interface for Policy and Charging Control | Rel-20 read |
| TS 29.413 vj00 | NGAP for Non-3GPP Access | Rel-19 read |
| TS 29.502 vk10 | 5G SMF Service Based Interface Stage 3 | Rel-20 read |
| TS 29.510 vk10 | NRF Service-Based Interface | Rel-20 read |
| TS 33.127 vj80 | Lawful Interception Architecture | Rel-19 read |
| TS 33.128 vj80 | Lawful Interception Protocols and Procedures | Rel-19 read |
| TS 33.501 vk30 | 5G Security Architecture | Rel-20 read |
| TS 38.413 vj40 | NG Application Protocol (NGAP) Specification | Rel-19 read |