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

Glossary term · Identifier

NR RedCap

NR Reduced Capability RAT Type

Identifier →

NR RedCap is a 3GPP RAT type identifier used in the core network to distinguish reduced-capability NR devices, enabling differentiated handling for IoT and wearables.

Introduced
Rel-19
Where
Core Network › 5G Core
Specifications
2 specs
NR RedCap Description Purpose What changed Neighbours Specifications

Description

NR RedCap (NR Reduced Capability) is a 3GPP RAT type identifier introduced in Release 19, defined in 3GPP TS 23.501 and TS 29.061. It is used exclusively within the Core Network (CN) to identify NR when used by a UE that indicates NR Reduced Capability. This identifier is a sub-type of the generic NR RAT type, meaning that while the UE is technically connected via NR, the CN can distinguish it as a RedCap device for policy, charging, and mobility management purposes.

The NR RedCap identifier is not a radio access technology in itself; rather, it is a classification that allows the 5G Core Network (5GC) to apply specific treatments to RedCap UEs. RedCap devices are designed to be lower complexity, lower power, and lower cost compared to full-fledged NR devices, targeting use cases such as industrial wireless sensors, video surveillance, and wearables. By identifying these devices at the CN level, operators can optimize network resources, enforce appropriate QoS policies, and manage mobility and session management differently.

In the 5G architecture, the RAT type is reported by the Radio Access Network (RAN) to the Access and Mobility Management Function (AMF) during UE registration and session establishment. The AMF then uses this information to select appropriate Session Management Functions (SMFs) and to apply policies. With NR RedCap, the RAN indicates that the UE is a RedCap device, and the AMF forwards this RAT type to other CN functions such as the Policy Control Function (PCF) and the Unified Data Management (UDM). This allows the network to enforce specific policies, such as restricted mobility or lower maximum bit rates, tailored for RedCap devices.

The identifier is defined in TS 23.501, which specifies the overall 5G system architecture, and TS 29.061, which covers interworking between the Public Land Mobile Network (PLMN) and Packet Data Networks (PDNs). The NR RedCap RAT type is used in signaling messages such as the N2 interface between the RAN and AMF, and in charging records generated by the SMF. It enables operators to differentiate charging and billing for RedCap devices, which may have different subscription models.

Overall, NR RedCap is a key enabler for the 5G ecosystem to support massive IoT and low-cost devices without compromising the performance of enhanced Mobile Broadband (eMBB) services. It allows the network to treat RedCap UEs as a distinct class, ensuring efficient resource utilization and service differentiation.

Purpose & Motivation

The NR RedCap identifier was created to address the growing need for a unified 5G network that can efficiently serve diverse device types, including low-power, low-complexity IoT devices. Prior to Release 19, the Core Network could not distinguish between standard NR UEs and RedCap UEs based solely on the RAT type, leading to suboptimal policy enforcement and resource allocation. RedCap devices, defined in Release 17, required a way to be identified in the CN so that operators could apply appropriate QoS, charging, and mobility policies.

The introduction of NR RedCap as a RAT type sub-identifier solves this problem by providing a standardized mechanism for the RAN to signal the RedCap capability of a UE to the CN. This allows the CN to apply differentiated treatment without requiring changes to the radio interface or UE procedures. It also enables operators to offer tailored services and pricing for RedCap devices, which is essential for the commercial success of massive IoT deployments.

Furthermore, NR RedCap supports network slicing and edge computing scenarios by allowing the CN to route RedCap traffic to specific network slices or edge applications. This flexibility is crucial for industrial and enterprise use cases where RedCap devices may require dedicated network resources. The identifier thus plays a vital role in the 5G vision of connecting everything, from high-speed broadband to low-power sensors.

What changed in its specifications

The latest release-to-release comparison of specifications that define NR RedCap. 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 29.061Rel-16 → Rel-17

Rel-17 added NR RedCap as a 3GPP RAT type identifier for the core network and extended the headset interface tests of UE.

Full comparison in TS 29.061 →

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-19 Initial

Initial definition: 'a 3GPP RAT type Identifier used in the Core Network only, which is a sub-type of NR RAT type, and defined to identify in the Core Network the NR when used by a UE indicating NR Reduced Capability.' This introduced the concept of a distinct RAT type for RedCap UEs to enable CN differentiation.

Defining Specifications

3GPP specifications that define or reference NR RedCap, 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 29.061 vk10 Packet Domain Interworking Requirements Rel-20 read