When 5G arrived, it came with extraordinary promises: multi-gigabit speeds, sub-millisecond latency, and the capacity to connect billions of devices simultaneously. For smartphones and fixed wireless broadband, those promises made sense. For the vast majority of IoT applications — the sensors, trackers, meters, and monitors that form the backbone of connected industry — they were largely irrelevant, and the cost and complexity of full 5G modems made the technology impractical. That gap is what 5G RedCap was designed to close.
Standardised by 3GPP in Release 17, RedCap — short for Reduced Capability — defines a new class of 5G device specifically engineered for the middle tier of IoT: applications that need more than LTE-M or NB-IoT can offer, but far less than a full 5G NR modem. Understanding what RedCap trades away, and what it retains, is essential for any organisation evaluating cellular connectivity for IoT deployments in the coming years.
Key Takeaways
5G RedCap is a 3GPP Release 17 specification that reduces 5G NR complexity to create cost-efficient, lower-power devices suited to mid-tier IoT use cases.
RedCap devices support narrower bandwidth, fewer antennas, and half-duplex operation compared to full 5G NR, substantially lowering modem cost and power draw.
The technology targets applications such as industrial wireless sensors, video surveillance, wearables, and asset tracking — segments poorly served by both high-end 5G and low-power LPWAN standards.
Release 18 introduces Enhanced RedCap (eRedCap), pushing capabilities further toward the lower end to compete more directly with LTE-M on power and cost.
Commercial RedCap modules and network support began emerging in 2024, with broader ecosystem maturity expected through 2025 and 2026.
What is 5G RedCap?
5G RedCap (Reduced Capability, also referred to as NR-Light) is a 3GPP specification introduced in Release 17 that defines a simplified category of 5G New Radio device with intentionally constrained radio capabilities. Rather than supporting the full bandwidth, antenna configurations, and duplex complexity of mainstream 5G NR, a RedCap device operates within a reduced feature set — sufficient for a defined range of IoT and industrial applications, but not designed for high-throughput consumer broadband. The goal is to bring genuine 5G connectivity, including access to mid-band and high-band spectrum, network slicing, and 5G core infrastructure, to device categories where the cost and power demands of full 5G have previously been prohibitive.
In the cellular IoT hierarchy, RedCap occupies a deliberate middle ground. Below it sit NB-IoT and LTE-M, which excel at low-power, low-data-rate applications but lack the throughput and latency performance that many industrial and commercial IoT systems require. Above it sits full 5G NR, capable of extraordinary performance but expensive, power-hungry, and overspecified for most connected devices. RedCap addresses the gap — a segment that includes tens of billions of potential device connections in manufacturing, logistics, healthcare monitoring, and smart infrastructure.
How 5G RedCap Works
At its core, RedCap works by selectively removing capabilities from the full 5G NR specification to reduce the complexity and cost of the modem chipset. Three principal reductions define the standard. First, the maximum supported bandwidth is capped: 20 MHz in sub-6 GHz spectrum (compared to up to 100 MHz for full NR) and 100 MHz in mmWave (compared to 400 MHz). Second, the number of receive antenna branches is reduced — typically to one or two, compared to four or more in high-end NR devices — which simplifies the RF front end and reduces processing requirements. Third, RedCap supports half-duplex frequency division duplexing (HD-FDD) as an optional mode, meaning the device does not need to transmit and receive simultaneously, which further reduces hardware complexity.
These reductions translate directly into smaller, cheaper modem dies, lower peak power consumption, and simpler device designs. The theoretical peak downlink throughput for a Release 17 RedCap device in sub-6 GHz spectrum is in the range of 150–220 Mbps — well below full 5G NR, but significantly above what LTE-M supports. Uplink rates similarly sit in the tens of megabits per second range. For applications such as video surveillance cameras, industrial sensor aggregators, or connected medical monitors, these figures are not only adequate but represent a genuine upgrade over current LTE alternatives.
RedCap devices connect to standard 5G NR base stations (gNBs) and are managed through the 5G core network (5GC). From a network perspective, the infrastructure differentiates RedCap devices through dedicated identifiers, allowing operators to apply appropriate quality of service policies, network slices, and resource scheduling. This integration with 5GC is a key architectural advantage: RedCap inherits 5G’s security framework, including 256-bit encryption and improved authentication procedures, as well as core capabilities such as network slicing and edge computing integration.
Key Technologies and Standards
Several technical components and standards define the RedCap ecosystem:
3GPP Release 17: The foundational specification for RedCap, published in 2022. It defines the bandwidth limitations, antenna requirements, duplex modes, and device categories (Type 1 for sub-6 GHz, Type 2 for mmWave).
3GPP Release 18 — Enhanced RedCap (eRedCap): An evolution that further reduces minimum bandwidth to 5 MHz in sub-6 GHz, targeting even lower-cost and lower-power devices and beginning to overlap with the upper range of LTE-M performance.
5G NR air interface: RedCap uses the same underlying NR physical layer as full 5G, including OFDM waveforms, flexible numerology, and the same time-frequency resource structure, which simplifies base station support.
5G Core Network (5GC): RedCap requires a 5G standalone (SA) core, not the non-standalone (NSA) architecture used in early 5G rollouts. This has implications for deployment timelines, as SA networks are less universally available than NSA infrastructure.
Network slicing: RedCap devices can be assigned dedicated logical network slices, enabling operators to guarantee throughput and latency for specific IoT application classes.
RRC Inactive state: A 5G NR feature that RedCap inherits, allowing devices to suspend radio activity while maintaining context at the network, significantly reducing the signalling overhead and energy cost of reconnection for intermittently active IoT devices.
eDRX and PSM: Extended Discontinuous Reception and Power Saving Mode features from LTE are carried forward, supporting battery-operated RedCap devices with highly duty-cycled operation.
Main IoT Use Cases
The 3GPP specification itself identifies three primary application categories for RedCap, and these map neatly onto real deployment requirements across industries.
Industrial wireless sensors represent perhaps the most significant volume opportunity. Modern manufacturing and process industries are deploying increasing numbers of wireless sensors for condition monitoring, vibration analysis, temperature and pressure measurement, and predictive maintenance. Many of these applications generate data at rates — several hundred kilobits per second, often bursty — that exceed what NB-IoT or LTE-M can reliably handle, particularly when aggregating multiple sensors. RedCap’s throughput profile, combined with the low latency of 5G NR, makes it well suited to time-sensitive monitoring in factory automation and energy infrastructure.
Video surveillance and visual monitoring is a category where LTE connectivity has long been used but where limitations in bandwidth and latency have constrained image quality and real-time responsiveness. A RedCap-connected camera operating at 1080p with moderate compression generates roughly 2–4 Mbps continuously — within RedCap’s sustained throughput envelope. Applications include smart city camera networks, construction site monitoring, retail analytics, and critical infrastructure surveillance, all of which benefit from cellular connectivity without fixed network infrastructure.
Connected wearables, including medical-grade monitors, worker safety devices, and consumer health trackers, require reliable low-latency connectivity, moderate data rates for telemetry and firmware updates, and compact form factors with manageable battery life. RedCap’s reduced antenna count and lower peak power draw directly support the industrial and clinical wearable segment, where device size and battery longevity are often primary design constraints.
Beyond these three anchor categories, asset tracking applications with higher update frequencies — refrigerated transport, high-value equipment, pharmaceutical cold chain — and smart grid infrastructure including advanced metering with real-time grid telemetry are increasingly cited as deployment targets. Healthcare remote monitoring devices, such as portable ECG monitors or connected infusion pumps, also align well with RedCap’s capability profile.
Benefits and Limitations
The primary benefit of 5G RedCap is straightforward: it extends 5G network access to a device category that full 5G NR cannot economically serve. A RedCap modem is expected to cost roughly 20–40% less than a full 5G NR modem at comparable production volumes, with the gap expected to narrow further as the ecosystem matures. For devices produced at scale — industrial sensors, utility meters, fleet trackers — this cost differential is commercially significant.
The performance advantages over legacy LPWAN standards are equally concrete. Compared to LTE-M, RedCap offers substantially higher throughput, access to 5G spectrum assets, and integration with 5G core features including slicing and edge compute proximity. Compared to NB-IoT, the gap is even wider. For applications that have historically been forced onto LTE Cat 4 or Cat 6 modules to meet throughput requirements, RedCap offers a path to equivalent or better performance with lower power consumption and a migration trajectory toward 5G infrastructure.
The limitations, however, are material. 5G Standalone (SA) dependency is the most significant near-term constraint. RedCap requires SA 5G core deployment; it cannot operate on the NSA architecture that underpins a majority of current 5G commercial rollouts. As of 2024–2025, SA deployment remains uneven globally, concentrated among operators in China, parts of Asia-Pacific, and select European and North American markets. Enterprises planning RedCap deployments must carefully assess operator SA coverage in their target geographies.
Power consumption, while reduced relative to full 5G NR, remains higher than NB-IoT and LTE-M in sleep-dominated duty cycles. For applications where a device transmits only a few hundred bytes per day, RedCap is not the appropriate technology. The battery life achievable with RedCap — measured in months rather than years under typical IoT duty cycles — positions it firmly in applications where periodic charging or line power is feasible.
Ecosystem maturity is another acknowledged constraint. Chipset availability has been limited to a handful of vendors through early commercialisation, and certified module options have expanded more slowly than the broader LTE-M/NB-IoT ecosystem. This is expected to normalise as Release 18 eRedCap and the associated device ecosystem develop through 2025 and 2026.
Market Landscape and Ecosystem
The RedCap ecosystem spans chipset and module vendors, network operators, and the broader IoT platform and integration layer.
On the semiconductor side, the major cellular chipset vendors began sampling RedCap-capable silicon in 2023, with commercial availability broadening through 2024. The module ecosystem — which translates chipsets into certifiable, deployable hardware for OEMs — has followed, with a growing number of compact form-factor modules targeting the industrial and wearable segments.
Network operators in China have led commercial RedCap deployment, with several carriers announcing nationwide or near-nationwide RedCap support on their 5G SA networks. In Europe and North America, operator timelines have been tied to SA rollout progress, with commercial RedCap service becoming available in select markets through 2024 and 2025. Mobile network operators with significant enterprise IoT portfolios have been particularly active in positioning RedCap as a migration path for LTE Cat 4 device fleets reaching end-of-life.
Platform and integration vendors — cloud IoT platforms, MVNO connectivity managers, and IoT solution integrators — are progressively adding RedCap device management and connectivity orchestration capabilities, though the tooling remains less mature than for established LPWAN standards. Industrial automation vendors and systems integrators in manufacturing, energy, and logistics are among the earliest enterprise adopters, typically in pilot and early production deployments.
Future Outlook
The near-term trajectory for RedCap is shaped by two parallel developments: the continued expansion of 5G SA infrastructure globally, and the maturation of the Release 18 eRedCap specification into commercial silicon and modules.
Enhanced RedCap, standardised in 3GPP Release 18, reduces the minimum channel bandwidth further and introduces additional power optimisation features. Its target is a device that can compete on cost and power consumption with LTE-M while retaining 5G core integration. If eRedCap achieves commercially viable chipset pricing — a question of production volume and semiconductor roadmap execution — it could accelerate the transition away from LTE-M in new deployments, particularly in markets where operators are actively planning LTE spectrum refarming.
The longer-term picture intersects with 6G research and standardisation timelines, which remain speculative, but the structural logic that produced RedCap — that most IoT devices need modest, reliable connectivity at low cost, not maximum performance — will persist regardless of generation. The question of where the boundary sits between low-power LPWAN, mid-tier cellular IoT, and high-performance 5G is likely to be renegotiated with each standards cycle.
Industry analysts broadly expect RedCap to account for a significant share of new cellular IoT connections in the second half of this decade, particularly in industrial and enterprise segments. The commercial momentum in China, where both operator infrastructure and device manufacturing are most advanced, will likely set the pace for global ecosystem development.
Frequently Asked Questions
What is the difference between 5G RedCap and NB-IoT?
NB-IoT is a narrowband LPWAN standard optimised for very low data rates and multi-year battery life on minimal data budgets. 5G RedCap targets substantially higher throughput — up to 150+ Mbps downlink — and lower latency, and operates on 5G NR infrastructure rather than LTE or legacy networks. RedCap is appropriate where NB-IoT lacks the bandwidth or latency performance required.
Does 5G RedCap require a new network infrastructure?
RedCap requires 5G Standalone (SA) infrastructure, including a 5G Core network. It cannot operate on Non-Standalone (NSA) 5G deployments, which are still common in many markets. Existing 5G SA base stations can support RedCap devices through software and configuration updates in most cases.
What is the battery life of a 5G RedCap device?
Battery life depends heavily on the application’s duty cycle and data transmission frequency. With power-saving features such as eDRX and PSM, RedCap devices in intermittent-transmission applications can achieve battery life measured in months. They are not suited to applications requiring years of operation on a small primary cell, where NB-IoT or LTE-M remain more appropriate.
What is Enhanced RedCap (eRedCap)?
Enhanced RedCap is a 3GPP Release 18 evolution of the original Release 17 RedCap specification. It further reduces minimum supported bandwidth to 5 MHz in sub-6 GHz spectrum, targeting lower device cost and power consumption, and is intended to serve use cases at the boundary between mid-tier IoT and the upper range of LPWAN applications.
Which industries are most likely to adopt 5G RedCap?
Industrial manufacturing, energy and utilities, logistics, healthcare, and smart city infrastructure are among the most cited early adopter segments. Applications involving video monitoring, high-frequency sensor telemetry, connected wearables, and asset tracking with moderate data requirements are well aligned with RedCap’s capability profile.
When will 5G RedCap modules be widely commercially available?
Commercial RedCap chipsets and modules began appearing in 2023–2024. Broader availability and competitive pricing are expected to develop through 2025 and 2026, tracking the maturation of the 5G SA network infrastructure needed to support them.
Related IoT topics
NB-IoT (Narrowband IoT)
LTE-M (LTE Cat-M1)
5G Standalone (SA)
Edge computing
eSIM and iSIM technologies
LPWAN connectivity
The post 5G RedCap: What Reduced Capability Means for IoT Deployments appeared first on IoT Business News.