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

Glossary term · Radio Access Network

RedCap UE

Reduced Capability User Equipment

Radio Access Network →

RedCap UE is a 5G New Radio device with reduced capabilities compared to standard NR UEs, designed to balance cost and complexity for IoT applications like wearables and sensors.

Introduced
Rel-17
Where
User Equipment
Specifications
5 specs
Also in
Radio Access Network
RedCap UE Description Purpose What changed Neighbours Detected Changes Specifications

Description

RedCap UE, or Reduced Capability User Equipment, is a category of 5G New Radio (NR) devices introduced in 3GPP Release 17. These devices are designed to support use cases that require lower complexity, cost, and power consumption than enhanced Mobile Broadband (eMBB) devices, but still benefit from 5G NR features such as low latency, high reliability, and network slicing. RedCap UEs are specified in 3GPP TS 38.306, which defines the UE radio access capabilities, and are further detailed in TS 38.304 (UE procedures in idle and inactive mode), TS 38.321 (MAC protocol), and TS 38.331 (RRC protocol).

The key characteristic of a RedCap UE is its reduced capabilities. Compared to a standard NR UE, a RedCap UE may support a narrower bandwidth (e.g., 20 MHz in FR1 and 100 MHz in FR2), fewer receive antennas (e.g., 1 or 2), lower maximum modulation order (e.g., 64QAM), and half-duplex operation (optional). These reductions simplify the device design, leading to lower cost and power consumption. However, RedCap UEs still support essential 5G features such as beamforming, massive MIMO, and network slicing, making them suitable for applications like industrial wireless sensors, video surveillance, and wearables.

RedCap UEs operate in the same NR networks as standard UEs, but the network must be aware of their capabilities to optimize scheduling and resource allocation. The network can identify a RedCap UE during initial access through a specific indication in the random access procedure or via UE capability signaling. This allows the gNB to configure appropriate bandwidth parts (BWPs), scheduling parameters, and mobility procedures. For example, a RedCap UE may be configured with a dedicated initial BWP that is narrower than the cell's overall bandwidth, reducing power consumption.

In terms of protocol stack, RedCap UEs support the full NR protocol stack but with simplified implementations. The MAC layer, for instance, may support fewer HARQ processes and simplified buffer status reporting. The RRC layer handles RedCap-specific configurations, such as restricted measurement gaps and relaxed radio link monitoring. The physical layer supports reduced bandwidth and antenna configurations, as specified in TS 38.306. These adaptations ensure that RedCap UEs can coexist with standard UEs without degrading network performance.

RedCap UEs are expected to play a crucial role in the expansion of 5G into vertical industries. They enable a new wave of IoT devices that require better performance than NB-IoT and LTE-M can provide, but do not need the full capabilities of eMBB devices. As 5G evolves, RedCap UEs will be further enhanced in Releases 18 and beyond, with features like enhanced positioning, reduced power consumption, and support for new spectrum bands.

Purpose & Motivation

RedCap UEs were created to address a gap in the 5G device ecosystem. While 5G NR was initially designed for eMBB, offering very high data rates and low latency, many IoT and industrial applications do not require such extreme performance. These applications, such as wearables, smart meters, and industrial sensors, need moderate data rates (tens to hundreds of Mbps), low latency, and high reliability, but are highly cost-sensitive and power-constrained. Existing IoT technologies like NB-IoT and LTE-M provide low power and cost but are limited in throughput and latency, making them unsuitable for applications like video surveillance or real-time control.

RedCap UEs fill this gap by providing a middle ground: they offer better performance than NB-IoT/LTE-M but at a lower cost and complexity than eMBB devices. This is achieved by relaxing certain capabilities, such as bandwidth, antenna count, and modulation order, which reduces the silicon complexity and power consumption. The 3GPP standardized RedCap in Release 17 to ensure interoperability and economies of scale, enabling a wide range of new 5G devices.

Historically, the need for RedCap became apparent as 5G deployments expanded beyond smartphones. The industry recognized that a one-size-fits-all approach would not work for the diverse 5G use cases. RedCap provides a standardized solution that leverages the 5G NR framework, including features like network slicing and ultra-reliable low-latency communication (URLLC), while optimizing for cost and power. This allows operators to serve new markets without deploying separate networks, and it ensures that RedCap devices can benefit from ongoing 5G advancements.

What changed in its specifications

The latest release-to-release comparison of specifications that define RedCap UE. Each summary describes the whole specification, not only this term.

TS 28.540Rel-18 → Rel-19

Rel-19 adds management clauses for Ambient IoT, IAB nodes, and regenerative NTN with UE-Satellite-UE communication. It also shifts NTN responsibility from 5GC to 3GPP.

Full comparison in TS 28.540 →
TS 38.304Rel-18 → Rel-19

Rel-19 adds TS 38.304 definitions for multi-hop L2 UE-to-Network sidelink relay roles, including child, parent, intermediate, first and last relay UEs. It also adds paging and system information handling for relays, and NTN IoT Phase 3 text on PLMN access technology restrictions and cell categories.

Full comparison in TS 38.304 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-17 2 changes
  • Correction on the capability of RedCap UE TS 38.306CR0916
  • Correction for the selected band for HD-FDD capability checking by RedCap UE TS 38.331CR4430
Rel-18 4 changes
  • Clarification for RedCap UE supporting MBS broadcast [RedCapMBS_Bcast] TS 38.306CR1111
  • Corrections on some features application to (e)RedCap UE TS 38.306CR1151
  • Mandatory support of Enhanced channel raster by (e)RedCap UE TS 38.306CR1158
  • Correction on FD-FDD capability checking for RedCap UE in TDD band TS 38.331CR4578
Rel-19 3 changes
  • Introduction on the SRS frequency hopping for non-RedCap UE in 38331 [Pos_SRSHop] TS 38.331CR5290
  • Early implementation of R19 (e)RedCap UE capability with FR1-NTN TS 38.331CR5804
  • Less than 5 MHz FR1 for (e)RedCap UE TS 38.306CR1477

Defining Specifications

3GPP specifications that define or reference RedCap UE, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 28.540 vk40 5G Network Resource Model (NRM) Stage 1 Rel-20 read
TS 38.304 vj30 NR UE Idle and Inactive State Procedures Rel-19 read
TS 38.306 vj40 NR UE Radio Access Capability Parameters Rel-19 read
TS 38.321 vj40 NR MAC Protocol Specification Rel-19 read
TS 38.331 vj40 NR Radio Resource Control (RRC) Rel-19 read