The connectivity decision is about fit—not the biggest number
Choosing cellular connectivity for an IoT product is rarely a simple race toward the highest data rate. A connected asset may need to run for years, operate across multiple countries, survive weak-signal conditions, meet a strict bill-of-materials target, or support richer data as the product evolves.
That is why the space between legacy LTE and full 5G matters. LTE Cat-1 and Cat-1bis remain practical, mature options for many connected products. 5G RedCap introduces a middle tier: more capable than LTE IoT categories, but simpler than full 5G New Radio (NR). 5G eRedCap takes that idea further, aiming to bring 5G economics and power characteristics closer to Cat-1-class devices.
The right choice depends on the application, deployment geography, network reality, and support horizon—not on a headline peak rate alone.
A quick comparison
| Technology | Standards context | Approximate theoretical peak | Hardware and power profile | Strongest fit |
|---|---|---|---|---|
| LTE Cat-1 | LTE Release 8 | 10 Mb/s downlink; 5 Mb/s uplink | Conventional LTE complexity; typically two receive chains; PSM/eDRX available | Mobile tracking, telematics, POS, meters, gateways, medical and security devices |
| LTE Cat-1bis | LTE Release 14 | About 10 Mb/s downlink; 5 Mb/s uplink | One receive chain can reduce size, cost, and power; PSM/eDRX available | Cost-sensitive trackers, wearables, POS, and monitoring devices |
| 5G RedCap | 5G NR Release 17 | Commonly cited favorable-configuration peaks up to 226 Mb/s downlink and 120 Mb/s uplink | Reduced bandwidth, antenna, and processing requirements; 5G Standalone required | Industrial equipment, cameras, richer telemetry, gateways, telematics, private 5G |
| 5G eRedCap | 5G NR Release 18 | Target up to 10 Mb/s downlink and uplink | Further-reduced complexity; FR1 and 20 MHz maximum; emerging ecosystem | Simple sensors, wearables, and monitoring products with a 5G migration rationale |
These are standards or favorable-configuration figures, not guaranteed application throughput. Actual performance depends on spectrum, bandwidth, modulation, antenna design, signal conditions, scheduling, and operator configuration.
LTE Cat-1: the established general-purpose option
LTE Cat-1 was designed as a mainstream LTE device category rather than an ultra-low-rate LPWAN technology. With theoretical peak limits around 10 Mb/s downlink and 5 Mb/s uplink, it can support more than periodic sensor messages while remaining simpler than a full high-end broadband modem.
Its maturity is a major advantage. LTE Cat-1 modules, certifications, engineering patterns, and operator support are widely available. It also supports features such as Power Saving Mode (PSM) and extended Discontinuous Reception (eDRX), which can reduce the time a device spends actively communicating. Battery life still depends on the complete system: traffic volume, retry behavior, signal quality, antenna design, firmware, and network configuration all matter.
Cat-1 is a strong fit when a product needs mobility, reliable two-way communication, moderate data rates, or a broad 4G deployment footprint. Common examples include asset trackers, vehicle telematics, payment terminals, meters, security equipment, medical monitoring, and industrial gateways.
The trade-off is hardware. Conventional Cat-1 designs generally use two receive chains and can require more component area, cost, and power than a one-receive-chain design.
LTE Cat-1bis: similar capability with a leaner device design
Cat-1bis keeps the principal Cat-1 transport capability while simplifying the RF design. Its defining distinction is the one-receive-chain architecture. That can enable smaller modules, lower bill-of-materials cost, and lower power consumption in suitable designs.
Cat-1bis is not a new coverage layer. It normally uses existing LTE networks, so the key deployment checks remain the same: supported bands, operator certification, roaming, voice requirements such as VoLTE where applicable, and local 4G shutdown or refarming plans.
For many cost-sensitive products, Cat-1bis is the practical default when 10/5 Mb/s-class performance is sufficient. It is especially attractive for compact trackers, wearables, POS devices, telematics, and industrial or medical monitors.
The one-receive-chain design can affect RF diversity and robustness in particular environments. That does not make Cat-1bis universally better than Cat-1. Instead, compare measured performance in the target bands and physical enclosure. If a second receive chain materially improves reliability for the product, conventional Cat-1 may justify its additional complexity.
5G RedCap: a middle tier for more capable IoT
5G RedCap—short for Reduced Capability NR—was introduced in 3GPP Release 17. It is designed for devices that need more capability than low-power IoT categories but do not need the full complexity of a premium 5G modem.
RedCap reduces device requirements through limits on bandwidth, antennas, processing, and other capabilities. It can support up to 20 MHz in FR1 and, in favorable configurations, is commonly described with peak rates of up to about 226 Mb/s downlink and 120 Mb/s uplink. Those figures put it well above Cat-1 for applications such as richer telemetry, industrial video, cameras, gateways, and connected equipment.
The trade-off is network availability. RedCap is intended for 5G Standalone (SA), not simply any network displaying a 5G icon. A device may be technically capable of RedCap while the target operator, country, or roaming partner does not yet support it. As a result, RedCap should be evaluated together with the deployment plan—not selected from a modem data sheet in isolation.
RedCap also sits between LTE and full 5G in ecosystem maturity. Module and chipset options are expanding, but certification paths, operator support, and global roaming are not as predictable as they are for established LTE categories. For a new product, confirm the target bands, SA coverage, module availability, certification schedule, firmware support, and field-testing plan early.
5G eRedCap: bringing 5G closer to Cat-1 economics
eRedCap is the Release-18 evolution of RedCap. Its goal is to make 5G more appropriate for simpler, lower-cost devices while retaining a path into 5G networks.
The target capability is closer to Cat-1: up to about 10 Mb/s downlink and uplink, with FR1 operation and a maximum 20 MHz channel. Optional approximately 5 MHz unicast processing can reduce device burden while retaining a wider RF capability. Release-18 work also introduces power-saving opportunities, including longer eDRX behavior in RRC-inactive configurations; reported maximums are configuration-dependent and should not be treated as universal battery-life promises.
That makes eRedCap conceptually attractive for simple sensors, wearables, and monitoring products that need a 5G migration story but do not need RedCap's higher data rates. However, eRedCap is an emerging technology. A standard release does not automatically mean certified modules, widespread operator support, or dependable roaming are available in the markets where a product will be sold.
Choose eRedCap when there is a clear 5G SA and lifecycle rationale, and only after confirming the concrete network and module roadmap. If the product must ship broadly today, mature LTE may still be the lower-risk decision.
How to choose the right technology
1. Start with the traffic profile
Define the real workload rather than starting with a radio label. Record typical and peak payload size, uplink-to-downlink ratio, session frequency, firmware-update size, latency sensitivity, and whether the product may later add images, audio, video, or richer diagnostics.
If the application needs only modest telemetry, Cat-1 or Cat-1bis may provide ample headroom. If it needs frequent high-volume uplink, video, or a richer edge experience, RedCap may be more appropriate. eRedCap is aimed at simpler workloads where the strategic value of 5G matters more than additional throughput.
2. Decide how much mobility and RF robustness matter
Vehicle tracking, mobile POS, and telematics have different RF demands from a stationary indoor sensor. Evaluate antenna constraints, metal enclosures, indoor attenuation, weak-signal performance, handovers, and regional band combinations.
Cat-1bis's one-receive-chain design can be valuable for size and cost, but measure it in the final mechanical design. Do not assume a category label alone predicts field reliability.
3. Validate the network before the product architecture
For LTE, confirm 4G longevity, operator certification, roaming, and shutdown commitments in every target market. For RedCap and eRedCap, confirm 5G SA—not just NSA—availability and the operator's actual support for the relevant device category.
Ask operators and module vendors about supported bands, provisioning, eSIM/eUICC options, voice requirements, firmware support, and test approvals. Build a field-validation plan that includes indoor, outdoor, mobile, and congested conditions.
4. Compare total lifecycle cost
The lowest-cost module is not always the lowest-cost product. Include certification, antenna and RF components, power-management requirements, data plans, cloud connectivity, field replacement, firmware maintenance, and the engineering cost of supporting multiple regional variants.
A mature Cat-1bis design may win on near-term deployment risk. A RedCap or eRedCap design may be justified when higher capability, private 5G integration, or a long-term 5G strategy creates measurable value.
5. Treat security and support as selection criteria
Cellular authentication and encryption are important, but they do not secure the complete device. Require secure boot, unique device credentials, protected key storage, signed and integrity-checked OTA updates, a vulnerability-response process, a documented support period, monitoring, and secure decommissioning.
Ask the module and connectivity providers how long they will support firmware, certifications, and network changes. A product that will remain deployed for ten years needs an explicit lifecycle plan, regardless of whether it uses Cat-1bis or eRedCap.
A practical decision guide
- Choose Cat-1bis when the product needs up to roughly 10/5 Mb/s, broad LTE availability, mobility, and a compact, cost-sensitive design.
- Choose Cat-1 when receive diversity or a specific existing carrier/module design materially improves RF performance or deployment certainty.
- Choose RedCap when the application needs richer data, lower-latency 5G capabilities, cameras, industrial connectivity, or private 5G—and the target network supports RedCap over 5G SA.
- Choose eRedCap when Cat-1-class performance is enough, the product benefits from a 5G path, and certified eRedCap modules and SA coverage are confirmed for the target markets.
Futureproofing is a design process
Futureproofing does not mean choosing the newest radio by default. It means matching today's requirements to a platform that can be supported, secured, certified, and supplied throughout the product's intended life.
For many deployments, Cat-1bis remains the pragmatic answer: mature coverage, capable performance, and an efficient device design. RedCap is compelling for the next tier of industrial and media-rich IoT. eRedCap offers an important direction for simpler 5G devices, but its value depends on the pace of real-world network and module adoption.
The best architecture is the one that meets the workload with measurable margin, works in the target markets, and has a credible plan for firmware, security, certification, and network change. Validate those facts early, and the technology choice becomes a business decision grounded in the product's actual future—not a bet on the newest specification.
