eRedCap (enhanced Reduced Capability) is the 3GPP Release 18 device type for mass IoT and M2M cellular connectivity. A simplified 5G NR class aimed at the hundreds of millions of LTE Cat-1 and Cat-1bis connections that will need a successor as 4G spectrum is refarmed. Modules began shipping in 2026, with volume availability expected from 2027.
Standards status reviewed
eRedCap Key Parameters
eRedCap - enhanced Reduced Capability - is a 5G NR device type defined in 3GPP Release 18, the first release of what 3GPP terms the 5G Advanced era. Release 18 was frozen in June 2024. eRedCap builds on the Release 17 RedCap work with further complexity reductions, targeting the large-volume, low-to-medium data rate IoT and M2M device market.
Release 17 RedCap reduced 5G NR complexity for wearables, industrial sensors and video surveillance, supporting up to 20 MHz in FR1 and a specified peak of up to 226 Mbps downlink and 120 Mbps uplink, though most commercial modules are quoted nearer 150 Mbps. eRedCap goes further: channel bandwidth reduced to 5 MHz, a single receive chain (1T1R), and half-duplex FDD operation. The result is a device type with peak downlink throughput of approximately 10 Mbps, comparable to LTE Category 1 and its single-antenna variant LTE Cat-1bis.
It is worth being precise about the relationship, because vendors are not consistent about it. Some describe eRedCap as an evolution of RedCap. Others, including Telit, describe it as a separate device type created by capping throughput rather than a successor generation. Both readings are defensible from the specification. What is not in dispute is the commercial target.
That target is straightforward. The global installed base of LTE Cat-1 devices - smart meters, basic asset trackers, vehicle telematics, industrial telemetry, point-of-sale terminals and M2M modems - runs to hundreds of millions. As 4G networks age and spectrum is eventually refarmed, those devices need a successor. eRedCap provides one on 5G NR infrastructure, without the full complexity and cost of mainstream 5G NR or Release 17 RedCap.
eRedCap modules began reaching market in 2026, with volume availability expected from 2027. Chipset platforms are being developed by vendors including Qualcomm, MediaTek, ASR and Sequans. Module manufacturers such as Telit Cinterion, Quectel, Fibocom and SIMCom build on those platforms. Note the distinction: chipset vendors supply the modem silicon, module vendors package it.
Network requirement. eRedCap needs a 5G Standalone core, and it also needs the operator to have enabled RedCap support in the radio network. This is a software matter rather than new hardware, but it is not automatic. The gNB advertises RedCap support in SIB1, identifies RedCap devices during random access via a dedicated initial bandwidth part and specific MAC CE logical channel IDs, and configures them accordingly. A network running 5G SA with RedCap features switched off will not serve these devices. 5G-ACIA states the position plainly: adoption requires upgrades to 5G SA operation plus software updates.
Quick Facts
Name
eRedCap / enhanced RedCap [VERIFY: confirm exact 3GPP spec wording before asserting a formal long-form name]
Standard
3GPP Release 18 (5G Advanced), frozen June 2024
Key Work Item
[RP NUMBER TO VERIFY - check the Rel-18 WID list at 3gpp.org before republishing. The previously listed RP-213700 could not be confirmed.]
Frequency Bands
Sub-6 GHz (FR1 bands)
Network Requirement
5G Standalone core plus operator RedCap enablement (software)
Roaming
Nascent. Requires inter-PLMN agreements and RedCap RAT types in core policy frameworks (GSA)
Target Devices
Smart meters, asset trackers, telematics, M2M modems, industrial telemetry
The short answer, as of 16 July 2026: possibly nothing. The reduced-capability NR family may be complete at two device types, and 3GPP's attention has moved to 6G.
| Release | Status | What it did for reduced-capability NR |
|---|---|---|
| Release 17 | Frozen 2022 | Introduced RedCap. Originally studied as NR-Lite, then NR-Light, renamed to RedCap during the study. Up to 20 MHz FR1, 2 Rx typical, LTE Cat-4 migration path. |
| Release 18 | Frozen June 2024 | Introduced eRedCap. 5 MHz, 1 Rx, HD-FDD, ~10 Mbps. LTE Cat-1 / Cat-1bis replacement. First release of 5G Advanced. |
| Release 19 | Frozen December 2025 | No new reduced-capability device type. Extended RedCap to non-terrestrial networks (satellite), added wake-up receiver work for energy efficiency, and standardised Ambient IoT device type 1 as a separate paradigm. |
| Release 20 | In progress | Final 5G Advanced release, running alongside the first 6G studies. Ambient IoT phase 2 (device types 2a / 2b) is in scope. No third RedCap tier announced. |
| Release 21 | Future | Expected to carry the first 6G specifications. |
Release freeze dates per 3GPP. Reviewed 16 July 2026. Roadmap positions after Release 20 are subject to change.
How eRedCap sits against the device types it is designed to succeed.
| Parameter | eRedCap Release 18 |
RedCap Release 17 |
LTE Cat-1bis 4G LTE |
LTE Cat-1 4G LTE |
|---|---|---|---|---|
| Peak downlink | ~10 Mbps | Up to 226 Mbps specified (~150 Mbps typical in modules) |
10 Mbps | 10 Mbps |
| Peak uplink | [VERIFY] | Up to 120 Mbps specified | 5 Mbps | 5 Mbps |
| Channel bandwidth | 5 MHz (FR1) | Up to 20 MHz (FR1) | 1.4-20 MHz | 1.4-20 MHz |
| Receive antennas | 1 (1T1R) | 2 typical, 1 optional (1T2R) | 1 (1T1R) | 2 (1T2R) |
| Half-duplex FDD | Yes (HD-FDD type A) | Optional [VERIFY] | [VERIFY] | No |
| Network generation | 5G NR (SA only) | 5G NR (SA only) | 4G LTE | 4G LTE |
| Operator enablement needed | Yes (SA + RedCap software) | Yes (SA + RedCap software) | No | No |
| Power vs LTE Cat-1 | Lower (simpler modem) | Comparable | Similar | Baseline |
| Module cost direction | Expected comparable to Cat-1bis | Higher than Cat-1 | Low | Low |
| Primary use case | Mass IoT, M2M, metering | Wearables, industrial sensors, video surveillance | Mass IoT, M2M | Mass IoT, M2M |
| Hardware availability | Modules 2026, volume 2027 | 2024 onwards | Widely available now | Widely available now |
Sources: 3GPP Release 18, GSA / 3GPP RedCap, Ericsson RedCap and eRedCap technical material. Peak throughput figures are theoretical maxima under ideal conditions. Reviewed 16 July 2026.
LTE Cat-1 is the workhorse of the connected device market. It sits between the very low data rate NB-IoT and LTE-M standards and mainstream LTE, providing enough throughput for periodic data uploads, remote configuration and firmware updates without the cost and complexity of higher-category modems.
Cat-1 and Cat-1bis account for a significant share of mid-tier licensed IoT deployments. Smart energy meters in the UK alone number in the tens of millions. Vehicle telematics, point-of-sale systems, industrial PLCs and M2M gateways running on Cat-1 face an eventual 4G sunset.
eRedCap addresses this at the standard level. It is not a workaround or a vendor-specific adaptation. It is a 3GPP-ratified device type that network equipment vendors implement and that chipset makers are building towards.
The practical caveats matter, though. An eRedCap device needs three things, not one: a 5G SA core, RedCap support enabled in the radio network, and - if it is going to roam - inter-PLMN agreements that recognise RedCap RAT types in core policy frameworks. GSA describes roaming support as nascent. Anyone specifying hardware for a multi-country deployment should confirm all three per operator rather than assume that "5G SA is live" is sufficient.
UK position. 5G SA is live on EE and on VodafoneThree (following the Vodafone and Three merger), with Virgin Media O2 building SA capability. Coverage remains uneven and much of the UK's 5G footprint is still Non-Standalone. RedCap feature enablement is a separate question from SA availability and should be confirmed with the operator. [VERIFY current UK operator SA and RedCap feature status before publishing - this changes quarterly.]
Smart Metering
Gas, electricity and water meters requiring periodic data uploads and AMI communication. Current Cat-1 installations are the primary long-term replacement target.
Asset Tracking and Telematics
Vehicle and trailer tracking, fleet management, cold chain monitoring. Note that roaming maturity is the constraint here, not throughput.
Industrial M2M and SCADA
Remote terminal units (RTUs), telemetry modems and M2M gateways in utilities, energy and infrastructure. Low bandwidth requirements, high reliability.
Point-of-Sale and Payments
Fixed and portable payment terminals, vending machines, kiosks. Faster session establishment and lower latency than NB-IoT alternatives.
Building Management and HVAC
BMS controllers, environmental sensors and access control where periodic reporting and remote management are the primary requirements.
Technical guides, hardware coverage and UK operator news for the 3GPP Release 18 standard.
Common questions about the Release 18 device type, how it relates to RedCap and LTE Cat-1, and what it means for IoT deployments.
Answers reviewed
Ask a questioneRedCap stands for enhanced Reduced Capability. It is defined in 3GPP Release 18, the first release of the 5G Advanced programme, which was frozen in June 2024. The "enhanced" prefix distinguishes it from the Release 17 RedCap work, which it extends with further complexity and cost reductions.
RedCap (Release 17, frozen 2022) targets wearables, industrial sensors and video surveillance, supporting up to 20 MHz in FR1 with a specified peak of up to 226 Mbps downlink and typically two receive antennas. eRedCap (Release 18, frozen June 2024) reduces channel bandwidth to 5 MHz, restricts to a single receive antenna, and supports half-duplex FDD. The result is a lower-cost, lower-power device type at approximately 10 Mbps peak downlink, aimed at LTE Cat-1 replacement rather than wearables.
Vendors disagree. Some describe eRedCap as the next step in a RedCap progression. Telit's published material states that eRedCap is not an evolution of RedCap but a distinct device type created by capping throughput. Both readings are defensible. The practical consequence is that a Release 17 RedCap device will not automatically support Release 18 eRedCap features, and you should not assume a generational upgrade path between the two.
As of 16 July 2026, no third reduced-capability NR device type has been standardised. Release 19, frozen in December 2025, did not add one. It extended RedCap to non-terrestrial networks, added wake-up receiver work for energy efficiency, and standardised Ambient IoT device type 1 as a separate paradigm. Release 20 is the final 5G Advanced release and runs alongside the first 6G studies. Release 21 is expected to carry the first 6G specifications. On current evidence, the reduced-capability NR family may be complete at two device types. Informal terms circulate for a hypothetical successor, but none has 3GPP standing.
No. eRedCap operates on 5G NR infrastructure, not LTE. It is positioned as the functional replacement for LTE Cat-1 in terms of data rate (approximately 10 Mbps downlink), device cost tier and target use cases. eRedCap devices require a 5G SA network with RedCap support enabled, whereas LTE Cat-1 operates on 4G LTE. The transition will occur as 4G networks age and operators refarm spectrum.
3GPP Release 18 was frozen in June 2024. eRedCap modules began shipping in 2026, with volume availability expected from 2027. Chipset platforms are being developed by vendors including Qualcomm, MediaTek, ASR and Sequans; modules are built by manufacturers such as Telit Cinterion, Quectel, Fibocom and SIMCom. Timelines are influenced by operator 5G SA deployment and RedCap feature enablement as much as by silicon.
Not automatically. eRedCap requires a 5G Standalone core rather than 5G Non-Standalone, which uses a 4G core. It also requires the operator to have enabled RedCap support in the radio network: the gNB advertises support in SIB1 and identifies RedCap devices via a dedicated initial bandwidth part and specific MAC CE logical channel IDs. This is a software upgrade rather than new hardware, but a 5G SA network with RedCap switched off will not serve these devices. In the UK, 5G SA is live on EE and VodafoneThree, with Virgin Media O2 building SA capability, though much of the UK 5G footprint remains Non-Standalone. Confirm SA availability and RedCap enablement per operator.
Roaming support is nascent. GSA notes that it requires dedicated inter-PLMN agreements and the introduction of RedCap RAT types into core policy frameworks. For multi-country deployments this is currently a bigger constraint than throughput or hardware availability, and should be confirmed with your connectivity provider on a per-market basis rather than assumed.
NB-IoT and LTE-M are 4G-era LPWAN standards for very low data rate applications (NB-IoT around 250 Kbps peak, LTE-M around 1 Mbps). eRedCap sits above both, targeting applications that need roughly 10 Mbps - sufficient for firmware updates, image uploads and moderate data volumes - without the complexity of mainstream 5G NR. The technologies are complementary rather than directly competing, though eRedCap and LTE-M overlap at the margins on cost and power.
Not in the sense of a device family. Ambient IoT, standardised as device type 1 in Release 19 with phase 2 in Release 20, does sit lower on a power axis - roughly 1 µW peak against RedCap's 10 mW and above. But it is a different radio paradigm rather than a further-reduced NR device, using backscatter transmission and envelope-detection receivers with MIMO, HARQ, scrambling and interleaving removed. The Ambient IoT work does not build on RedCap or reference it as a parent standard.
Primary sources for eRedCap, the 3GPP Release 18 standard, and the wider licensed IoT ecosystem.
3GPP Release 18 ↗
Official Release 18 work item list, including the eRedCap specification. Frozen June 2024.
3GPP3GPP Releases Overview ↗
Release timeline and freeze dates - Rel-17 (2022), Rel-18 (2024), Rel-19 (Dec 2025), Rel-20 in progress
GSMAGSMA Mobile IoT ↗
GSMA overview of licensed IoT standards: NB-IoT, LTE-M and the 5G NR IoT progression
GSMAGSMA eSIM for IoT ↗
SGP.32 eUICC specification for IoT - relevant to eRedCap device SIM provisioning
Planning a migration from LTE Cat-1bis, evaluating RedCap hardware, or need clarity on which operators have RedCap actually enabled rather than just 5G SA live? Ask directly.
Get in Touch
Ask a question about eRedCap, 5G RedCap hardware or IoT connectivity.
5gredcap.co.uk covers the Release 17 standard, UK operator deployment status, and hardware across EE, VodafoneThree and Virgin Media O2. The wider 5G NR reduced capability picture.
