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

Glossary term · Core Network

N3IWF

Non-3GPP access InterWorking Function

Core Network →

N3IWF is a core network function that enables secure integration of non-3GPP access networks into the 5G Core by acting as a gateway that terminates IPsec tunnels and relays traffic.

Introduced
Rel-15
Where
Core Network › 5G Core
Specifications
16 specs
Also in
Security
N3IWF Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Non-3GPP InterWorking Function (N3IWF) is a critical network function within the 5G Core (5GC) architecture, specifically defined to integrate untrusted non-3GPP access networks. Untrusted non-3GPP access refers primarily to access technologies not specified by 3GPP, such as Wi-Fi, which are considered untrusted from a 5G Core security perspective. The N3IWF serves as the secure point of entry for User Equipment (UE) connecting via such access, establishing itself as a termination point within the operator's trusted domain.

Architecturally, the N3IWF interfaces with the UE over the NWu reference point, which utilizes IKEv2 and IPsec protocols to establish secure tunnels. This ensures confidentiality and integrity for user plane traffic and signaling between the UE and the 5GC. On the network side, the N3IWF connects to other 5GC Network Functions via standard interfaces: it connects to the Access and Mobility Management Function (AMF) over the N2 interface for control plane signaling (e.g., registration, authentication) and to the User Plane Function (UPF) over the N3 interface for user data transfer. This allows the UE to be treated as if it were connected via 3GPP radio access, enabling consistent service continuity and policy enforcement.

The N3IWF's operation involves several key procedures. During initial attachment, the UE discovers an N3IWF and performs IKEv2 authentication and IPsec Security Association (SA) establishment, often leveraging 5G authentication credentials (e.g., from a USIM). The N3IWF then relays the UE's NAS messages (encapsulated within the IPsec tunnel) to the AMF over N2. For user plane, the N3IWF decapsulates incoming IPsec packets from the UE and forwards the inner IP packets to the UPF over a GTP-U tunnel on N3, and vice versa. It also plays a role in supporting mobility events, such as handovers between 3GPP and non-3GPP access.

Key components within the N3IWF's logical design include the termination points for IKEv2 and IPsec, the relay function for N1/N2 NAS signaling, and the GTP-U endpoint for the N3 interface. Its role is fundamental in realizing the 5G vision of access-agnostic service delivery, allowing operators to leverage existing Wi-Fi infrastructure to offload traffic, enhance coverage, and provide a seamless user experience without compromising 5G security and service standards.

Purpose & Motivation

The N3IWF was introduced in 3GPP Release 15 as part of the new 5G System (5GS) architecture to solve the critical problem of integrating non-3GPP access networks into the 5G core in a secure and standardized manner. Prior to 5G, integration of Wi-Fi with cellular networks was handled through separate, often proprietary gateways (like ePDG in EPS for untrusted Wi-Fi) that were not fully aligned with the cloud-native, service-based principles of 5GC. The motivation was to create a unified core that could deliver consistent services, security, and policies regardless of the underlying access technology (3GPP or non-3GPP).

Historically, non-3GPP access (especially untrusted Wi-Fi) presented security risks and management complexities. The N3IWF addresses these by providing a standardized, secure interworking function that applies the same robust 5G authentication and security mechanisms (like 5G-AKA or EAP-AKA') to non-3GPP connections. It solves the problem of access fragmentation, enabling seamless session continuity and service-based architecture exposure for devices connecting via Wi-Fi. This was driven by the industry need to leverage dense Wi-Fi deployments for capacity augmentation, indoor coverage, and fixed wireless access scenarios within the 5G service framework.

Furthermore, the creation of the N3IWF was motivated by the limitation of previous interworking solutions which were often bolt-ons to the core network. In 5G, the N3IWF is a first-class citizen within the SBA, interacting with the AMF and UPF via service-based interfaces. This allows for more flexible deployment, better scalability, and integrated policy control, fulfilling the 5G requirement for convergence of fixed and mobile networks.

What changed in its specifications

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

TS 23.501Rel-18 → Rel-19

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 →
TS 24.501Rel-18 → Rel-19

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

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
  • N3IWF counterpart in another generation: ePDG
    “UE performs N3IWF selection based on the ePDG selection procedure” TS 23.501
  • N3IWF coexists with TNGF
    “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

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

N3IWF is specified for the first time in Rel-15: it terminates IPsec tunnels from the UE over untrusted non-3GPP access and connects to the 5GC via N2 and N3.

  • “Non-3GPP access networks shall be connected to the 5G Core Network via a Non-3GPP InterWorking Function (N3IWF).” TS 23.501 v15.13.0
  • “A UE shall establish an IPSec tunnel with the N3IWF to attach to the 5G Core Network over untrusted non-3GPP access.” TS 23.501 v15.13.0
  • “the N3IWF shall determine the number of IPsec Child SAs to establish and the QoS profiles associated with each IPsec Child SA” TS 23.502 v15.17.0
Rel-16 1 CR

In Rel-16 the N3IWF gained new behaviour: it sends a CONGESTION Notify payload on overload, can serve SNPN/PLMN access with FQDN restrictions, and signalling runs over a TCP connection within the IPsec SA.

  • “The N3IWF can also due to internal congestion construct an IKE_AUTH response message including a CONGESTION Notify payload” TS 24.502 v16.11.0
  • “the UE shall not consider an N3IWF FQDN for N3IWF selection configured by an SNPN.” TS 24.502 v16.11.0
  • Enable N3IWF to initiate TCP connection establishment upon failure TS 24.502CR0131
Rel-17 1 CR

In Rel-17 the N3IWF gained new roles and behaviour: support for 5G ProSe Layer-3 UE-to-Network Relay with N3IWF, DSCP-based QoS handling, and overload/congestion handling in IKE_AUTH.

  • “the N3IWF is preconfigured with one or more QoS profiles requiring a dedicated IPsec child SA which can be associated with a DSCP value.” TS 24.502 v17.10.0
  • “the 5G ProSe Layer-3 UE-to-Network Relay with N3IWF shall provide access to the 5GC for the 5G ProSe Layer-3 Remote UE via N3IWF” TS 23.304 v17.8.0
  • N3IWF selection for emergency services TS 24.502CR0194
Rel-18 1 CR

Rel-18 extends N3IWF with slice-based selection (slice-specific FQDNs, AMF may trigger reselection of a different N3IWF), SNPN onboarding selection, and MPS priority treatment at the N3IWF.

  • “the AMF may detect that the N3IWF used by the UE is not compatible with this allowed subset” TS 23.502 v18.14.0
  • “the N3IWF may, if allowed by operator policy, treat further messages for the UE with MPS priority” TS 24.502 v18.8.0
  • N3IWF selection enhancement for support of S-NSSAI needed by UE TS 23.501CR3707
Rel-19 1 CR

In Rel-19 the N3IWF gains ECN marking for L4S support, dedicated IPsec Child SAs for L4S and PDU Set QoS flows, and selection/ProSe multi-hop handling changes.

  • “When ECN marking for L4S at N3IWF is enabled for downlink or uplink, the N3IWF should set the Congestion Experienced (CE) codepoint” TS 23.501 v19.9.0
  • “For each L4S-enabled QoS Flow, the N3IWF may establish a dedicated IPsec Child SA.” TS 23.502 v19.9.0
  • Correction on N3IWF selection TS 23.501CR5536
Rel-20 1 CR

N3IWF selection and reselection changed: the AMF may select a different N3IWF based on energy-related configuration, and slice-based N3IWF selection was added for 5G ProSe Layer-3 Remote UEs.

  • “If the AMF determines that a different N3IWF should be selected (e.g. based on energy related local configuration for the N3IWF)” TS 23.501 v20.3.0
  • “the 5G ProSe Layer-3 Remote UE uses the Extended N3IWF identifier configuration, if configured, to find the IP address of the N3IWF in the HPLMN” TS 23.304 v20.1.0
  • N3IWF/TNGF reselection considering energy related information. TS 23.501CR6493

Defining Specifications

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

SpecificationTitleRelease
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 24.526 vk00 5GS UE Policies Rel-20 read
TS 24.890 vg00 5G NAS Protocol for 5GS Stage 3 Rel-16 read
TR 28.828 vi00 Charging Aspects for Non-Public Networks Rel-18 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.518 vk10 AMF Service Based Interface Rel-20 read
TS 29.525 vk10 UE Policy Control Service Rel-20 read
TS 29.561 vk10 5G Network Interworking Procedures Rel-20 read
TS 32.255 vk30 5G Data Connectivity Converged Charging Rel-20 read
TS 32.256 vk10 5G Connection and Mobility Charging Rel-20 read
TS 33.127 vj80 Lawful Interception Architecture 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