Description
Non-5G Capable (N5GC) is a capability indicator defined within the 5G System (5GS) architecture to denote entities—typically User Equipment (UE) or network nodes—that do not support 5G Core Network (5GC) functionalities. This status is crucial for network discovery and selection procedures, particularly during initial attach or mobility events. When a UE indicates N5GC, it informs the network that it cannot utilize 5G-specific protocols, services, or interfaces, such as those defined for the Service-Based Interface (SBI) architecture or the 5G QoS model. This triggers the network to steer the UE towards appropriate legacy core networks, like the Evolved Packet Core (EPC), or to provide limited service access within a 5GS context using fallback mechanisms.
The technical implementation of N5GC involves signaling within Non-Access Stratum (NAS) protocols, as specified in 3GPP TS 24.501. During registration or session management procedures, a UE includes its capability information in messages like the Registration Request. The Access and Mobility Management Function (AMF) processes this information. If N5GC is indicated, the AMF may restrict the UE's access to 5G-specific network slices, prevent the establishment of PDU Sessions with certain 5G QoS characteristics, or initiate a redirection to an EPC via inter-system mobility procedures. The network uses this to enforce policies, ensure service continuity, and manage radio and core network resources efficiently by not allocating 5G-dedicated resources to incapable devices.
From a network architecture perspective, N5GC plays a role in the interworking between 5GS and Evolved Packet System (EPS). It is a key parameter in the N26 interface interworking (when present) and in the handover and fallback procedures defined between 5GC and EPC. The concept ensures backward compatibility, allowing for a gradual migration from 4G to 5G networks. It prevents incompatible UEs from attempting procedures that would fail, thereby reducing signaling overhead and improving overall network reliability. Management systems also utilize this capability for subscriber provisioning and reporting, distinguishing between 5G-capable and non-5G-capable device populations for network planning and service offering strategies.
Purpose & Motivation
The N5GC indicator was introduced to address the transitional phase of mobile network evolution, where 5G networks are deployed alongside existing 4G LTE networks. Its primary purpose is to manage the coexistence of 5G-capable and non-5G-capable devices and network elements seamlessly. Without such a capability indicator, network selection and attachment procedures could become inefficient or fail, as 5G networks might incorrectly assume support for advanced features from all connecting devices. This could lead to service disruptions, increased signaling load from failed procedures, and a poor user experience during the long period of heterogeneous network deployment.
Historically, similar capability indicators existed for transitions between 2G/3G and 4G. The creation of N5GC continues this pattern, specifically for the 5G era defined from 3GPP Release 15 onwards. It solves the problem of clear capability negotiation, allowing network operators to implement graceful fallback policies. For instance, a legacy IoT device or an older smartphone model can still obtain basic connectivity services via 4G networks while being identified as N5GC, ensuring it does not consume 5G-specific resources or trigger unsupported network functions. This enables operators to optimize their 5G investments by dedicating 5G resources to devices that can actually utilize them, while maintaining service for the vast installed base of pre-5G devices.
Furthermore, N5GC supports regulatory and service requirements by ensuring that emergency services or mandatory communications are not hindered by capability mismatches. It allows the network to apply the correct policy and charging rules based on the device's core network capability. The indicator is essential for the success of network slicing, as a slice designed for ultra-reliable low-latency communication (URLLC) would be inappropriate for an N5GC device. Thus, its purpose extends beyond simple compatibility to enabling efficient resource management, service differentiation, and a controlled migration path towards full 5G adoption.
Classification
Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (11 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 16, 3GPP introduced the "N5GC" function to enable Non-5G Capable devices to access the 5G Core Network via a wireline access network. This was achieved by defining a new role for the Wireline Access Gateway Function (W-AGF) to act on behalf of the N5GC device, handling its NAS signalling, registration, and primary authentication using EAP methods, while also managing a single PDU session establishment on the device's behalf. The specifications also detailed the use of the device's MAC address as a PEI and defined service area restrictions for such access scenarios.
- Registration of N5GC devices via wireline access TS 24.501CR2020
- Primary authentication of an N5GC device TS 24.501CR2218
- N5GC NAS aspects TS 24.501CR2390
- N5GC service area restrictions TS 24.501CR2391
- Support of authentication and registration of N5GC devices via wireline access TS 24.502CR0116
- SUPI/SUCI of N5GC devices TS 24.502CR0143
+ 3 more changes
In Release 17, the specification for the Non-5G Capable (N5GC) device function was refined, including a correction to the format of the N5GC indication Information Element. The release further detailed procedures for EAP-based primary authentication of N5GC devices and clarified the role of the Wireline Access Gateway Function (W-AGF) acting on behalf of such devices for NAS signalling and PDU session establishment over wireline access.
- Correction on N5GC indication IE Format TS 24.501CR3549
In Release 18, the specification introduced explicit procedures for using EAP methods, such as EAP-TLS, for the primary authentication of an N5GC device. This included defining the roles where the AUSF acts as the EAP server and, as corrected in this release, the N5GC device supports acting as the EAP peer. The update also detailed the handling of parameters like the ngKSI value between the network and the W-AGF acting on behalf of the N5GC device during this EAP-based authentication.
- Correction related to N5GC device supporting acting as EAP peer TS 24.501CR5817
Explore further
Broader topics and technologies where N5GC plays a role.
Defining Specifications
3GPP specifications that define or reference N5GC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 24.501 vj50 | 5G NAS Protocols Specification | Rel-19 |
| TS 24.502 vj20 | 5G Core Access via Non-3GPP Networks; Stage 3 | Rel-19 |
| TS 29.571 vj50 | Common Data Types for 5G Service Based Interfaces | Rel-19 |
