Description
The N3AN is a critical reference point defined in the 5G System (5GS) architecture, specifically between the Non-3GPP Interworking Function (N3IWF) in the core network and the user plane function of a trusted non-3GPP access network. It is not a physical interface but a logical point that standardizes how external, non-cellular networks interconnect with the 5G Core (5GC). The primary protocol stack for N3AN involves IPsec tunnels established over the underlying IP transport. These tunnels carry both control plane signaling (e.g., for NAS messages between the UE and the AMF) and user plane data packets between the UE and the UPF. The N3IWF acts as the termination point in the core, de-encapsulating traffic from the IPsec tunnel and forwarding it to the appropriate 5GC network functions. This architecture allows the 5GC to treat a UE connected via a trusted non-3GPP access (like a carrier-managed Wi-Fi network) similarly to a UE connected via 3GPP Radio Access Network (RAN), enabling key 5GS features like network slicing and consistent QoS to be extended over these alternative accesses.
From a security perspective, the N3AN interface is protected by established IPsec Security Associations (SAs), which provide confidentiality, integrity, and replay protection for all traffic traversing the untrusted IP network between the UE/N3AN access point and the N3IWF. The establishment of these IPsec tunnels is tightly integrated with the 5G authentication and key agreement (5G-AKA or EAP-AKA') procedures. The N3AN's definition ensures that the core network does not need to be aware of the specific link-layer technologies used in the non-3GPP access, as the N3IWF provides a uniform, IP-based interface. This abstraction is key to the 5GS's access-agnostic design principle.
In terms of mobility, the N3AN supports handovers between 3GPP and non-3GPP accesses. When a UE moves, for instance, from a 5G NR cell to a trusted Wi-Fi network, the N3AN provides the continued connectivity path, and the core network can manage the session continuity (e.g., using ATSSS) without the application layer being aware of the underlying access change. The specifications governing N3AN, such as TS 24.502 and TS 29.525, detail the precise message flows, tunnel management procedures, and QoS mapping rules required for this interworking, making it a cornerstone for converged network offerings.
Purpose & Motivation
The N3AN was created to address the fundamental 5G requirement of converged access. Prior to 5G, non-3GPP access (primarily Wi-Fi) was often treated as a separate, second-class network with limited integration, using solutions like S2a-based Trusted WLAN Access to the EPC. This resulted in disjointed user experiences, separate authentication, and an inability to apply consistent cellular-grade policies and charging. The 5G System was designed from the ground up to be access-agnostic, and the N3AN is the realization of that principle for trusted non-3GPP accesses.
Its purpose is to solve the problem of seamless service continuity and unified policy enforcement across heterogeneous networks. By providing a standardized, secure interface, it allows mobile network operators to integrate their Wi-Fi, fixed wireless, or even satellite networks deeply into their 5G service fabric. This enables operators to leverage these alternative networks for traffic offload, coverage extension, and creating multi-access bundled services, all managed from a single 5G core with a unified subscriber identity and policy profile. The N3AN, therefore, is a key enabler for the vision of a truly converged 'one network' experience, breaking down the traditional silos between cellular and other access technologies.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (33 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, the Non-3GPP Access Network (N3AN) node configuration information was formally introduced as a component of the Access Network Discovery and Selection Policy (ANDSP), used by the UE to select an N3IWF or ePDG. This release also defined procedures for N3AN node selection, including the use of a constructed or provisioned N3IWF FQDN and the handling of slice-specific N3IWF prefix configurations, particularly when roaming.
In Release 16, key enhancements for the Non-3GPP Access Network (N3AN) function included the introduction of specific FQDN configuration rules for N3IWF selection to support access to PLMN services via an SNPN and vice-versa. The release also extended congestion notification mechanisms to cover N3IWF or TNGF overload scenarios and introduced the capability for the N3IWF to initiate TCP connection establishment upon failure. Furthermore, corrections and clarifications were made to the N3AN node selection procedures, particularly in scenarios involving SNPNs and Lawful Interception (LI).
- N3IWF FQDN configured in a UE to support access to PLMN/SNPN services via SNPN/PLMN TS 24.502CR0079
- FQDN for N3IWF selection to access PLMN services via an SNPN TS 24.502CR0102
- Extending congestion notification to capture N3IWF or TNGF overload TS 24.502CR0130
- Enable N3IWF to initiate TCP connection establishment upon failure TS 24.502CR0131
- Correction in N3AN node selection involving SNPN TS 24.502CR0148
- Correct N3AN node selection due to LI TS 24.502CR0120
In Release 17, enhancements were made to the Non-3GPP Access Network (N3AN) function, specifically for the N3IWF selection procedure. These updates included mechanisms for N3IWF selection for emergency services and for access to SNPN services via a PLMN. Furthermore, the release introduced refinements to the N3AN node configuration information, making certain fields optional, and corrected the N3AN node selection logic to account for permitted home routing scenarios.
In Release 18, enhancements for N3AN (Non-3GPP Access Network) functions focused on refining N3IWF selection mechanisms. Key additions included support for slice-specific N3IWF prefix configuration and extended home N3IWF identifier configuration, enabling more granular selection based on network slice (S-NSSAI) and service type (e.g., IMS, onboarding, emergency). The release also introduced clarifications and corrections for UE behavior and node selection procedures, particularly for scenarios involving SNPNs (Standalone Non-Public Networks) and roaming.
- Resolving the EN related to N3IWF selection based on N3IWF identifier information in the REGISTRATION REJECT message TS 24.502CR0230
- Update N3AN node configuration information provisioning TS 24.502CR0222
- Prefixed OI/TAI Identifier FQDN for N3IWF selection TS 24.502CR0223
- Update of SNPN N3IWF selection TS 24.502CR0221
- N3IWF selection enhancement for support of S-NSSAI needed by UE TS 24.502CR0210
- N3IWF selection for non-IMS services supporting extended home N3IWF identifier configuration and slice-specific N3IWF prefix configuration TS 24.502CR0248
+ 15 more changes
Explore further
Broader topics and technologies where N3AN plays a role.
Defining Specifications
3GPP specifications that define or reference N3AN, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 24.502 vj20 | 5G Core Access via Non-3GPP Networks; Stage 3 | Rel-19 |
| TS 24.526 vj30 | UE Policies for 5GS; Stage 3 | Rel-19 |
| TS 29.525 vj40 | 5G UE Policy Control Service Stage 3 | Rel-19 |