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

Glossary term · Core Network

TNGF

Trusted Non-3GPP Gateway Function

Core Network →

TNGF is a 5G Core Network function that provides secure, trusted gateway access for devices connecting via non-3GPP networks like Wi-Fi, authenticating them and establishing IPsec tunnels into the core.

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

Description

The Trusted Non-3GPP Gateway Function (TNGF) is a critical component within the 5G Core Network (5GC) architecture, specifically defined for the Non-3GPP InterWorking Function (N3IWF) in the context of trusted non-3GPP access. Its primary role is to facilitate secure and controlled connectivity for UEs that utilize non-3GPP radio access technologies, most notably trusted Wi-Fi networks. Architecturally, the TNGF resides in the user plane and control plane, interfacing with other core network functions. On the N1 reference point towards the UE, it terminates the N1 interface over the non-3GPP access, managing the signaling connection. It establishes IPsec Security Associations (SAs) with the UE to create secure tunnels for both control plane (N1) and user plane (N3) traffic. The TNGF connects to the Access and Mobility Management Function (AMF) via the N2 interface for control plane procedures and to the User Plane Function (UPF) via the N3 interface for data forwarding.

Operationally, when a UE initiates access via a trusted non-3GPP network, it discovers and selects a TNGF. The UE and TNGF perform mutual authentication and establish IPsec tunnels. The TNGF then acts as a proxy, relaying the UE's registration and session management signaling to the 5G Core via the AMF. It is responsible for encapsulating and decapsulating user plane packets between the IPsec tunnel and the N3 GTP-U tunnel towards the UPF. The TNGF also interacts with the Authentication Server Function (AUSF) and Unified Data Management (UDM) for credential-based authentication (e.g., using 5G-AKA or EAP-AKA').

A key aspect of the TNGF is its 'trusted' designation, which implies that the 5G Core network operator has a trust relationship with the non-3GPP access network provider. This trust can be based on a roaming agreement or direct ownership, allowing the core network to rely on the access network's security to a certain degree, though the TNGF still enforces its own security at the IPsec layer. The TNGF supports mobility and session continuity procedures, enabling handovers between 3GPP (e.g., NG-RAN) and trusted non-3GPP access without dropping the PDU Session. It is a fundamental enabler for the 5G convergence goal, providing a unified core network experience regardless of the underlying access technology.

Purpose & Motivation

The TNGF was introduced in 3GPP Release 16 to formally define and standardize the gateway function for trusted non-3GPP access within the 5G System (5GS). Prior to 5G, non-3GPP interworking (e.g., via ePDG in EPS) was often treated as an untrusted access, requiring heavy security termination at the gateway. The creation of the TNGF addresses the growing importance of high-quality, carrier-grade Wi-Fi and other fixed wireless accesses as integral parts of the mobile operator's service offering. It solves the problem of providing seamless, secure, and policy-coherent access to 5G core services over these alternative networks.

The motivation stems from the need for true access-agnostic service delivery. Operators sought to leverage their Wi-Fi deployments, or partnerships with Wi-Fi providers, as a trusted extension of their 5G radio coverage, especially for indoor environments and fixed wireless access scenarios. The TNGF provides a standardized architecture that ensures security (through mandatory IPsec), supports 5G-specific features like network slicing and QoS over the non-3GPP link, and enables smooth mobility. It addresses limitations of previous non-3GPP interworking solutions by being natively integrated into the 5G Service-Based Architecture (SBA), using the same authentication frameworks and policy control (via the PCF) as 3GPP access, thereby eliminating functional silos.

What changed in its specifications

The latest release-to-release comparison of specifications that define TNGF. 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

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (27 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-16 4 changes
  • N3 terminations of W-AGF, TNGF and TWIF for UPF selection TS 29.502CR0249
  • Completing the introduction of TNGF in 23.501 TS 23.501CR1553
  • Extending congestion notification to capture N3IWF or TNGF overload TS 24.502CR0130
  • Correction of TNGF procedure TS 24.502CR0135
Rel-17 3 changes
  • Layer below IPsec to enable NAT traversal for TNGF/N3IWF access TS 23.501CR3442
  • R17 Correction on TNGF functionality TS 23.501CR3709
  • Addition of TWIF and TNGF as Non-3GPP Accesses TS 33.127CR0130
Rel-18 15 changes
  • TNGF selection enhancement for support of S-NSSAI needed by UE TS 23.501CR3953
  • UE to indicate its support for Slice-based TNGF selection to the network TS 24.501CR5121
  • Aborting registration procedure when the selected TNGF is not compatible with the allowed NSSAI TS 24.501CR5122
  • Protecting the N3IWF/TNGF identifier information in the REGISTRATION REJECT message TS 24.501CR5932
  • Support of TNGF selection for S-NSSAI TS 29.525CR0255
  • Slice based TNGF and N3IWF selection TS 29.525CR0323

+ 9 more changes

Rel-19 3 changes
  • Mobility of the UE connected to a TNAP to another TNAP connected to the same TNGF TS 24.502CR0313
  • Handling of unprotected REGISTRATION REJECT message with causes #81 and #82 (Selected N3IWF/TNGF is not compatible with the allowed NSSAI) TS 24.501CR6795
  • Correction to Mobility of the UE connected to a TNAP to another TNAP connected to the same TNGF TS 24.502CR0316
Rel-20 2 changes
  • N3IWF/TNGF reselection considering energy related information. TS 23.501CR6493
  • N3IWF/TNGF reselection considering energy related information TS 24.501CR7160

Defining Specifications

3GPP specifications that define or reference TNGF, 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 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 29.525 vk10 UE Policy Control Service 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 33.807 vg01 5G Wireline-Wireless Convergence Security Study Rel-16 read
TS 38.413 vj40 NG Application Protocol (NGAP) Specification Rel-19 read