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.
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 →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 →Technology family
Radio access technologies · Radio Access Network
- Phase 1 GSM
- R97 GPRS
- R99 EDGE, EGPRS, UTRA, UTRA-FDD, UTRA-TDD, UTRA-WTDD
- Rel-4 GERAN, UTRA-NTDD
- Rel-7 EGPRS2
- Rel-8 E-UTRA
- Rel-13 EC-GSM-IoT, LTE-M, NB-IoT
- Rel-15 NR
- Rel-17 NR RedCap
- Rel-18 NR eRedCap
- NR RedCap extended by NR eRedCap
“It is up to the E-UTRA network, if possible, to avoid handover attempts of an (e)RedCap UE to a target NR cell not supporting (e)RedCap” TS 38.300
- NR RedCap builds on NR
“It is up to the E-UTRA network, if possible, to avoid handover attempts of an (e)RedCap UE to a target NR cell not supporting (e)RedCap” TS 38.300
Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.
Release Timeline
Detected Changes Across Releases
verified against 3GPP sourcesDocumented changes in 3 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.
NR RedCap is defined for the first time as a core-network-only RAT type sub-type of NR, with a UE differentiation function (clause 5.41) and RAT type support in the AMF, SMF, PCF and CHF.
- “a 3GPP RAT type Identifier used in the Core Network only, which is a sub-type of NR RAT type” TS 23.501 v17.15.0
- “the AMF shall store the NR RedCap Indication in the UE context, consider that the RAT type is NR RedCap” TS 23.501 v17.15.0
- “The NFs interacting with CHF shall include the NR RedCap as RAT type.” TS 23.501 v17.15.0
In Rel-18 the NR RedCap RAT type was extended to cover NR eRedCap, with the indication carried in handover, AMF change and radio capability update procedures, and NR RedCap UE information was added for MBS broadcast.
- “During handover from E-UTRA to NR, the target NG-RAN (i.e. gNB) provides the NR RedCap indication or NR eRedCap indication to AMF” TS 23.501 v18.12.0
- “Upon AMF change, the source AMF shall provide the "NR RedCap Indication" or "NR eRedCap Indication" to the target AMF.” TS 23.501 v18.12.0
- “The MB-SMF then forwards the "NR RedCap UEs Information" parameter in N2 SM Information to the NG-RAN via the AMF” TS 23.247 v18.8.0
NR RedCap RAT type handling was clarified in IMS P-Access-Network-Info: UEs may set 3GPP-NR-REDCAP/EREDCAP or normal NR values by implementation, and NR RedCap UE indication was corrected.
- “For the NR RedCap UEs, whether to set the values "3GPP‑NR‑REDCAP"/"3GPP-NR-EREDCAP" or the normal values of NR access” TS 24.229 v19.7.0
- Clarification on NR RedCap RAT type within P-Access-Network-Info header field TS 24.229CR6759
- Corrections to the NR RedCap UE indication TS 29.580CR0059
Defining Specifications
3GPP specifications that define or reference NR RedCap, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.501 vk30 | 5G System Architecture | Rel-20 read |
| TS 29.061 vk10 | Packet Domain Interworking Requirements | Rel-20 read |