中文
English
Español
Pусский
한국어
日本語

5G RedCap, eRedCap and LTE Cat-1bis: The "Three Kingdoms" of Mid- and Low-Rate IoT and a Selection Guide

2026-10-15

A Fork in the Road for Mid- and Low-Rate IoT

As the industrial IoT reaches the "nerve endings" of the network, an apparently basic question keeps troubling engineers: when field devices neither need the gigabit bandwidth of full-scale 5G nor settle for the trickle rate of NB-IoT, which technology route should they choose?

The answer is no longer unique. With the successive emergence of 5G RedCap (Rel-17), eRedCap (Rel-18), and LTE Cat-1bis, the mid- and low-rate IoT market has evolved from a single dominant player into a three-way contest. The three overlap heavily in data rate range, yet each has a different focus — RedCap targets mid-to-high bandwidth and deterministic low latency, eRedCap enters industrial wireless sensing and lightweight wearables as a "5G version of Cat-1bis," while Cat-1bis holds the shipping mainstream with mature 4G nationwide coverage and extremely low module cost.

For industrial enterprises, this means both richer choices and a higher selection threshold. This article follows four main lines — data rate, power consumption, network evolution, and cost — to break down the real differences among these three routes and provide actionable industrial IoT selection boundaries.


1. The Three-Way Landscape: Origins and Coordinates of the Three Routes

(1) LTE Cat-1bis: The Mature Veteran and Cost Killer

LTE Cat-1bis derives from UE Category 1 defined in 3GPP Rel-13. Compared with the original Cat-1 requiring two receive antennas (2Rx), the key improvement of Cat-1bis is support for single-antenna reception (1Rx), greatly simplifying the terminal RF front end, with module design, cost, and power consumption all falling accordingly. It operates on the mature 4G LTE network without waiting for 5G coverage, making it one of the highest-volume and most supply-chain-stable categories in global cellular IoT, widely used in POS, smart meters, asset tracking, and shared devices.

(2) 5G RedCap: The "Lightweight Specialist" of 5G

RedCap (Reduced Capability) is a lightweight branch introduced by 3GPP in Rel-17 for 5G NR. By cutting high-spec features such as large bandwidth, multiple antennas, and 256QAM, it trades for lower terminal complexity and cost, while retaining 5G's native advantages such as low latency, high reliability, and network slicing. Its positioning clearly falls in "the mid-to-high-rate blank zone between 4G Cat-4 and full-scale 5G," a key piece of the puzzle for 5G's large-scale adoption across industries.

(3) eRedCap: The "5G Version of Cat-1bis" for Rel-18

eRedCap (Enhanced RedCap) is the product of further "subtraction" in Rel-18: bandwidth reduced from 20 MHz to 5 MHz, peak rate lowered to about 10 Mbps, single-antenna 1T1R with half-duplex FDD (HD-FDD), with complexity and power consumption approaching Cat-1bis. Its design intent is clear — targeting industrial wireless sensing, lightweight wearables, smart metering, and other scenarios that do not require high bandwidth but wish to migrate to 5G networks, carrying forward the mid- and low-rate connectivity needs after 4G gradually retires.

This is why the industry often calls eRedCap the "5G version of Cat-1bis." The two are nearly on par in rate; the difference is that eRedCap stands on the technical foundation of 5G NR: it naturally inherits 5G's low latency, network slicing, and future-oriented evolution capability, at the cost of depending on 5G standalone networking. In short, eRedCap is "trading Cat-1bis's rate for 5G's architecture," while Cat-1bis is "trading 4G's maturity for the lowest cost" — this mirror relationship forms the core tension of this round of mid- and low-rate IoT competition.

(4) A Three-Dimensional Coordinate Overview

Comparison Dimension5G RedCap (Rel-17)eRedCap (Rel-18)LTE Cat-1bis (Rel-13)
Downlink peak rate85–225 Mbps~10 Mbps10 Mbps
Uplink peak rate50–120 Mbps~5 Mbps5 Mbps
Channel bandwidth20 MHz5 MHz1.4–20 MHz
Receive antennaMainly 2 antennas (1T2R)Single antenna 1T1RSingle antenna 1T1R
Duplex modeFull-duplex FDDHalf-duplex FDDFull-duplex FDD
Network generation5G NR (SA only)5G NR (SA only)4G LTE
Operator upgrade needRequires SA + RedCap software enablementRequires SA + RedCap software enablementNone
Module cost band¥130–180Expected to match Cat-1bis¥20–40
Mass production paceFrom 2024From 2026, volume in 2027–2028Already shipping at scale

One sentence to summarize the three coordinates: RedCap handles "capability," eRedCap handles "evolution," Cat-1bis handles "cost."


2. Technical Anatomy: Differences in Rate, Power, Network and Cost

(1) Rate: Not the Higher the Better, but "Just Enough"

From the table, eRedCap and Cat-1bis are almost in the same order of magnitude (about 10 Mbps downlink, 5 Mbps uplink), while RedCap is a full order of magnitude higher. This means: if a business's per-device data volume stays at the "MB level per day" — such as periodic sensor readings, remote configuration, and firmware upgrades — both eRedCap and Cat-1bis can handle it; only when involving multi-channel HD video backhaul, large industrial vision images, or high-frequency sampling aggregation does RedCap's hundred-megabit capability truly pay off.

It is worth emphasizing that "10 Mbps" here is not a capability ceiling but a carefully drawn coordinate line. In industrial sites, the per-point data volume of most industrial sensor interconnections is between a few KB and a few hundred KB per minute; even with multiple concurrent channels, 5 Mbps uplink is enough to carry it comfortably. In other words, eRedCap and Cat-1bis are "just right" in rate — one point more is waste, one point less is insufficient. RedCap retains hundred-megabit capability to reserve margin for video, large images, and edge AI inference — precisely the range that Cat-1bis and eRedCap cannot reach.

The first criterion for selection is always the actual throughput requirement of a single device, not the paper peak. Treating "peak parameters" as the basis for selection is one of the most common mistakes in industrial IoT selection: a sensor that only reports temperature and humidity once an hour will never run faster because it switches to a RedCap module — only its BOM cost will multiply.

(2) Power Consumption: eRedCap's "Sleep Philosophy" and RedCap's Energy Balance

Power consumption is the lifeline of industrial wireless sensing and wearable devices. RedCap, by streamlining RF channels and protocol stack, can reduce power consumption by about 31%–41% compared with full-scale 5G modules, achieving a good energy efficiency ratio. eRedCap goes further: it introduces 5 MHz narrow bandwidth, a single antenna, and HD-FDD, and supports eDRX (extended discontinuous reception) in RRC_INACTIVE state, allowing devices to sleep for long periods while maintaining connection. At the same data volume, eRedCap's power performance is clearly better than LTE Cat-1, which is exactly its confidence for targeting battery-powered sensing terminals.

It should be noted that eRedCap's power-saving features depend heavily on 5G core network (5GC) support, which is also the fundamental reason it cannot work under NSA networking. In addition, the realization of power advantages is closely related to the terminal's actual duty cycle: for metering devices with extremely low reporting frequency, the gap between eRedCap and NB-IoT is leveled; while in "medium frequency, medium data volume" industrial sensor interconnection scenarios, eRedCap's power-saving mechanisms best demonstrate their value.

(3) Network Evolution: 5G SA Is the "Entry Ticket" for eRedCap and RedCap

This is the most easily overlooked yet most fatal difference among the three routes.

Both RedCap and eRedCap can only work on 5G standalone (SA) — NSA networking uses 4G EPC as the core network, with 5G NR only as an enhanced carrier overlay, unable to carry RedCap's streamlined signaling and eRedCap's power-saving mechanisms. Therefore, the availability of a RedCap/eRedCap link depends on three conditions being met simultaneously: 5G SA core network, RedCap enablement on the radio side, and core network policy recognizing RedCap terminal type during cross-operator roaming. If any one is missing, the device may frequently fall back or fail to access.

In contrast, Cat-1bis directly reuses the mature 4G LTE network, with full coverage and plug-and-play, requiring no operator modification. For industrial parks, underground plants, and remote sites where 4G signals are far more stable than 5G, Cat-1bis often has higher real-world availability.

The conclusion is straightforward: selection should follow wherever the network is. "5G SA is available" does not equal "RedCap is usable" — it must be confirmed operator by operator before deployment. Especially for cross-border and cross-region deployment projects, RedCap's RAT type identification in roaming scenarios is not yet fully mature and requires more careful evaluation — this is often a hidden trap where paper parameters look good but deployment fails repeatedly.

(4) Cost: The Ruler That Determines Penetration Speed

Cost is the most realistic dividing line in this "three-way contest." Current cellular IoT module costs are roughly distributed in four tiers:

Technology TierModule Cost RangeTypical Scenarios
NB-IoT¥10–20Smart water meters, gas meters, environmental monitoring
LTE Cat-1bis¥20–40POS, smart meters, asset tracking, shared devices
LTE-M¥30–50Wearables, fleet management
5G RedCap¥130–180Industrial IoT, smart grid, video backhaul

Compared with full-scale 5G modules, RedCap can reduce cost by 60%–70%, but is still significantly higher than Cat-1bis. eRedCap, due to its more streamlined modem architecture, is expected to have a module cost direction comparable to Cat-1bis — once mass production matures, it will become a realistic option of "getting 5G connectivity at Cat-1bis cost." This is also why the industry generally views eRedCap as the mid-to-long-term replacement for Cat-1bis.

However, eRedCap's ecosystem maturity remains a variable: chips supply from 2026, volume in 2027–2028, and whether price parity with Cat-1bis can be achieved by then remains to be seen. At the current stage, Cat-1bis's "extremely low module cost + mature coverage" remains the most pragmatic cost-sensitive solution.

Understanding the root of Cat-1bis's cost advantage requires returning to the supply chain. Cat-1bis can push module prices into the ¥20–40 range due to three forces: first, the single-antenna 1Rx design greatly simplifies the RF front end, reducing antennas and RF channels, with material and process costs falling together; second, chip solutions are highly mature with sufficient competition, and large-scale shipments from multiple chip vendors keep baseband costs falling; third, downstream application volume amortizes R&D expenses, especially driven by massive scenarios such as payments, two-wheelers, and asset tracking, pushing module makers' marginal costs very low. In contrast, RedCap modules are still in the scale ramp-up phase, and a considerable portion of their ¥130–180 price is R&D and manufacturing cost not yet amortized.

For cost-sensitive industrial enterprises, the significance of Cat-1bis cost is not just "cheap," but that it determines whether a mid- and low-rate IoT project can truly achieve "ten-thousand-point" scale replication. When a factory deploys tens of thousands of sensor nodes, every one-yuan difference in module unit price is magnified into hundreds of thousands of yuan in overall budget difference. This is the fundamental reason Cat-1bis is difficult to replace at present.


3. Selection Guide: Six-Dimensional Decision Boundaries

(1) Six Decision Dimensions

  • Data volume: Single device daily data volume below MB level → Cat-1bis/eRedCap; involving video or large images → RedCap.

  • Network availability: Deployment area has stable 5G SA coverage and operator has enabled RedCap → RedCap/eRedCap; only 4G or unstable 5G → Cat-1bis.

  • Power and supply: Battery-powered, requiring multi-year battery life → eRedCap/Cat-1bis; stable mains power → RedCap.

  • Cost sensitivity: Extremely sensitive to per-point cost, large-scale deployment → Cat-1bis; can accept higher unit price for capability → RedCap.

  • Mobility and latency determinism: Requires high-speed mobility or millisecond-level control determinism → RedCap; static or slow-moving scenarios → Cat-1bis/eRedCap.

  • Evolution expectation: Long project lifecycle, hoping for smooth migration to 5G → eRedCap/RedCap; short lifecycle, pursuing current optimum → Cat-1bis.

(2) Selection Decision Tree

text
Does a single device need video/large images/high-frequency aggregation? ├─ Yes → 【5G RedCap】 │ Prerequisite: On-site 5G SA coverage and operator RedCap enabled │ └─ No → Does it need long battery life + smooth future 5G upgrade? ├─ Yes → 【eRedCap】(Plan from 2026, volume after 2027; currently use Cat-1bis as transition) │ └─ No → Is there mature and stable 4G coverage? ├─ Yes → 【LTE Cat-1bis】 └─ No → Re-evaluate on-site wireless coverage (NB-IoT / wired)

(3) Clear Boundaries for Three Types of Scenarios

Industrial wireless sensing, lightweight wearables: eRedCap's home ground. Low rate requirements, emphasis on power consumption and long-term evolution. If the project lands after 2026, plan eRedCap directly; for current deployment, use Cat-1bis as transition. Typical examples: production line vibration/temperature sensors, smart watches and bands, asset tags.

Cost-sensitive, mature 4G coverage, large-scale M2M: Cat-1bis's home ground. Extremely low module cost combined with full coverage makes it the current shipping mainstream. Typical examples: smart meters, shared devices, mobile POS, vehicle OBD terminals.

Mid-to-high bandwidth, low latency, network slicing required industrial scenarios: RedCap's home ground. Video backhaul, AGV collaboration, distribution automation, machine vision — its irreplaceable value range.

(4) Three Practical Recommendations for Industrial Enterprises

  1. For current projects, prioritize "network status" over "technology trends": Whether on-site 4G is stable and whether 5G SA is enabled directly determines the available routes. Drawing boundaries with a coverage map first is more effective than agonizing over specification sheets.

  2. Reserve "dual-mode" flexibility in mid-term planning: For projects with a lifecycle exceeding 3 years, prioritize dual-mode solutions supporting both Cat-1bis and eRedCap, avoiding passive equipment replacement when 4G retires.

  3. Include TCO, not unit price, in decisions: Cat-1bis modules are cheap, but if the site lacks stable power and requires frequent battery replacement, overall cost may exceed; conversely, RedCap has a higher unit price but may support years of evolution from one deployment. The endgame of industrial IoT selection is a battle over lifecycle cost.


4. Deployment and Practical Recommendations

Technology routes must ultimately land on procurable, deployable products. When we point the decision tree in Chapter 3 to the branch of "needs 5G deterministic connectivity + mid-to-high bandwidth + industrial-grade interfaces," we find that this branch already has mature mass-production carriers.

Taking the ComIn I2105 5G RedCap industrial router as an example, it can serve as a landing reference sample for this selection branch: in 5G SA mode, its theoretical downlink rate reaches 226 Mbps and uplink 120 Mbps, fully carrying RedCap's rate range; hardware uses a 32-bit MIPS dual-core industrial-grade processor and 128 MB memory, and provides WAN/LAN RJ45 ports, RS232/RS485 industrial terminals, and DI/DO and other rich industrial interfaces (over ten categories in total), enabling it to serve as a gateway connecting old and new devices, allowing traditional PLCs and sensors to smoothly access the 5G RedCap network. In terms of reliability, which industrial sites value most, it uses a full metal enclosure, operating temperature covering -35°C to 75°C, supports 9–36V wide-voltage input, and has built-in dual hardware watchdogs and 1.5KV electromagnetic isolation for network ports, 15KV ESD protection for SIM card interfaces; at the software level, it supports mainstream VPNs such as PPTP/L2TP/OpenVPN/IPSec/WireGuard, is compatible with TR069/MQTT cloud management protocols, and reserves secondary development space based on OpenWRT/Linux SDK.

The value of this form lies not in stacking parameters, but in confirming a trend: RedCap has moved from standard text to a stably deliverable industrial-grade product, and when enterprises plan mid-to-high-rate IoT projects, "5G deterministic connectivity" is no longer a paper option.

At the same time, we must be clear-headed: for mature 4G coverage and extremely cost-sensitive large-scale scenarios, sticking with Cat-1bis remains the current optimum; eRedCap is a reserve option for after 2027. The wisdom of selection lies precisely in acknowledging that no single route can cover all scenarios.


Conclusion: No Optimum, Only the Most Suitable

The "three-way contest" among 5G RedCap, eRedCap, and LTE Cat-1bis is essentially not a dispute over technical superiority, but over scenario adaptation. RedCap guards deterministic mid-to-high bandwidth scenarios with hundred-megabit rates and 5G native capabilities; eRedCap carries low-rate, long-battery-life industrial wireless sensing and lightweight wearables with its "5G version of Cat-1bis" positioning, reserving an evolution path for 4G retirement; Cat-1bis continues to secure the foundation of large-scale M2M with mature networks and extremely low module cost.

For industrial enterprises, the correct posture for industrial IoT selection is to first clarify their own data volume, network environment, power constraints, and lifecycle, then let the technology route match the needs, rather than being led by peak parameters. On this mid- and low-rate IoT track, understanding the boundaries is more important than chasing the hype.