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

Glossary term · Core Network

UNAN

Untrusted Non-3GPP Access Network

Core Network →

UNAN is a non-3GPP access network, such as Wi-Fi or fixed broadband, that the operator does not trust for direct 5G core connectivity and whose traffic must traverse the N3IWF or TNGF to reach the 5GC securely.

Introduced
Rel-16
Where
Core Network › 5G Core
Specifications
2 specs
UNAN Description Purpose What changed Neighbours Specifications

Description

The Untrusted Non-3GPP Access Network (UNAN) concept defines how user equipment connects to the 5G Core (5GC) through access technologies that are not defined by 3GPP and are not trusted by the home operator. Typical examples include public Wi-Fi hotspots, residential Wi-Fi, and fixed broadband networks. Because the operator cannot assume any security association with the access network, all traffic from the UE to the 5GC must be protected end-to-end at the IPsec or higher layer, and the UE must first authenticate to the core before any user-plane traffic is allowed.

Architecturally, the UNAN is connected to the 5GC through a Non-3GPP InterWorking Function (N3IWF) for untrusted non-3GPP access, or through a Trusted Non-3GPP Gateway Function (TNGF) when the access is trusted. The N3IWF terminates the IKEv2/IPsec signaling with the UE, establishes a secure tunnel, and then acts as a NAS relay toward the AMF over the N2 reference point. For the user plane, the N3IWF terminates the IPsec tunnel and forwards traffic over N3 to the UPF, applying GTP-U encapsulation. In this way, the UNAN is effectively hidden from the rest of the 5GC: from the AMF's perspective, the UE appears to be attached via a non-3GPP access, and the same session management, policy, and charging functions apply as for 3GPP access.

The registration procedure over UNAN begins with the UE selecting a PLMN and discovering the N3IWF via DNS or configured information. The UE then establishes an IPsec tunnel using IKEv2, during which it performs EAP-based authentication (EAP-5G) with the AUSF/UDM. Only after successful authentication does the UE send NAS registration messages through the tunnel to the AMF. This two-stage approach ensures that no NAS signaling is exposed to the untrusted network before mutual authentication completes. The UE may also establish multiple PDU sessions over the same tunnel, each mapped to a separate UPF N3 connection.

Key components of the UNAN architecture include the UE, the untrusted access network itself (which is transparent to 3GPP), the N3IWF, the AMF, the SMF, the UPF, and the AUSF/UDM for authentication. The N3IWF is a core network function that may be deployed in the operator's network or at the edge. It maintains UE context, manages the IKEv2 security associations, and enforces QoS by mapping IPsec child SAs to 5G QoS flows. The N2 interface between N3IWF and AMF carries NAS messages, while N3 carries user-plane packets to the UPF.

UNAN support is important for operators seeking to integrate Wi-Fi and fixed access into their 5G service offerings without compromising security. It enables use cases such as Wi-Fi calling, seamless session continuity between 3GPP and non-3GPP access (via ATSSS), and fixed-mobile convergence where a single 5GC serves both mobile and broadband subscribers. The concept was introduced in Release 16 as part of the broader non-3GPP access enhancements and is specified in TS 23.273 and the study in TR 23.700.

Purpose & Motivation

The UNAN concept exists to allow 5G core connectivity over access networks that the operator does not control or trust, such as public Wi-Fi and third-party fixed broadband. Before its definition, non-3GPP access in 4G and early 5G was handled with limited trust models and often required separate gateways or vendor-specific solutions. Operators wanted a standardized, secure way to extend 5G services over any IP access while keeping the 5GC protected from untrusted traffic.

The main problem UNAN solves is security: without a trusted relationship, user traffic and signaling could be intercepted or spoofed. By mandating IPsec/IKEv2 tunnels terminated at the N3IWF and EAP-based authentication before NAS signaling, UNAN ensures that the untrusted access network only sees encrypted packets. This also enables regulatory and lawful interception requirements to be met at the N3IWF/UPF rather than in the access network.

A secondary motivation is convergence and coverage. Mobile operators can offload traffic to Wi-Fi in dense areas, extend coverage indoors, and offer fixed-wireless access using the same 5GC. The UNAN architecture, standardized in Release 16, provides a common framework that supports both untrusted and trusted non-3GPP access, giving operators deployment flexibility while maintaining a consistent subscriber experience.

What changed in its specifications

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

TS 23.273Rel-18 → Rel-19

Rel-19 adds LMF-based AI/ML positioning support with Nlmf_DataExposure services. It also adds periodic location event procedures based on NRPPa measurements, MWAB location service clauses, and enhanced network automation enablers.

Full comparison in TS 23.273 →

Release Timeline

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-16 Initial

Initial definition and architecture of Untrusted Non-3GPP Access Network introduced in TS 23.273, specifying N3IWF-based connectivity, IKEv2/IPsec tunneling, and EAP-5G authentication for UE access to 5GC over untrusted Wi-Fi and fixed networks.

The definition text carried over unchanged from Release 16; UNAN remains specified in TS 23.273 with the same architectural meaning, while related non-3GPP access enhancements (e.g., trusted access and ATSSS evolution) were addressed in other work items.

Defining Specifications

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

SpecificationTitleRelease
TS 23.273 vj70 5G Location Services Architecture Stage 2 Rel-19 read
TS 23.700 vk10 AI/ML Application Layer Support Phase 2 Rel-20 read