Non-5G Capable

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.

Key Features

• Indicates lack of 5G Core Network protocol support in UE or network entities
• Used in NAS signaling during registration and session management procedures
• Triggers network-controlled fallback to Evolved Packet Core (EPC) for access
• Influences network slice selection and availability for the device
• Enables efficient inter-system mobility between 5GS and EPS
• Supports subscriber and device management reporting for network planning

Evolution Across Releases

Defining Specifications