What NR-Light actually delivers in the field, how to choose between LTE, RedCap, and full 5G, real test data from live deployments, and how to specify the right router for your project.
Written by E-Lins Engineering Team
What Is 5G RedCap — and Why Did 3GPP Create It?
I’ll be honest: when I first started explaining 5G RedCap industrial IoT router technology to procurement teams, the most common reaction was confusion about why it exists at all. If 5G is already available, why would anyone want a reduced version of it? The answer gets to the heart of why 3GPP Release 17 matters for the industrial market specifically.
RedCap — formally designated NR-Light in 3GPP Release 17, finalized in June 2022 — was created to fill a gap that had developed in the cellular IoT standard landscape. On one side, LTE-M and NB-IoT handled the ultra-low-bandwidth end: battery-powered sensors sending a few bytes every few minutes, designed to last years on a coin cell. On the other side, full 5G NR targeted the high-throughput end: multi-Gbps applications demanding four receive antenna chains, wide channel bandwidths, and the most sophisticated modem silicon in production. In the middle sat a large and growing category of industrial devices that needed more than LTE-M could provide — reliable sub-20ms latency, more than 10 Mbps sustained throughput, 5G SA core network integration — but could not justify the cost, power draw, or physical size of a full 5G modem.
That middle category includes the devices that show up constantly in the industrial IoT projects I work on: IP surveillance cameras for traffic or site monitoring, wireless sensors in smart factories, asset tracking gateways, wearable health monitors in enterprise settings, and the growing class of connected industrial instruments that generate moderate data rates continuously. RedCap was designed precisely for them.
Key numbers to hold in mind: RedCap limits the cellular modem to a maximum 20 MHz channel bandwidth in sub-6 GHz bands (versus up to 100 MHz for full 5G), a maximum of two receive antenna chains (versus four for full 5G), and enables optional half-duplex FDD to simplify the RF front-end. In return, peak downlink sits around 150 Mbps and uplink around 50 Mbps. For the majority of industrial IoT applications, that ceiling is between 10 and 100 times what the application actually uses. The constraint is irrelevant; the savings in modem cost and power consumption are not.
Is RedCap Right for Your Project? Answer These Six Questions First
Before going further into the technical detail, these six questions will tell you whether RedCap is the relevant specification for your deployment — or whether LTE or full 5G is the better fit. In my experience evaluating connectivity for industrial projects, getting clear answers here saves weeks of later re-evaluation.
- What is the sustained data rate your application actually generates in normal operation? Not the theoretical peak, but the real traffic. If it is below 50 Mbps, RedCap’s ceiling is not a constraint you will encounter.
- Are you deploying on a private 5G campus network? Private 5G deployments are the primary target environment for RedCap — confirm that the private network infrastructure vendor supports NR-Light on their core configuration.
- Is the deployment battery-powered, solar-powered, or PoE-constrained? RedCap’s lower modem power draw makes a meaningful difference in power-limited deployments; in mains-powered fixed installations it matters less.
- How many endpoint nodes will the deployment reach at full build-out? RedCap’s per-module cost advantage over full 5G compounds across node count. At ten nodes the difference is modest; at 200 nodes it is a meaningful project budget variable.
- Does the public carrier in your deployment region have RedCap support activated on their 5G SA network? This varies significantly by market and carrier — verify before specifying for a public carrier deployment.
- Does your application require dual SIM carrier failover at the endpoint level? RedCap-specific router configurations may differ from full 5G router redundancy architectures — confirm the specific device’s SIM and failover capability.
How RedCap Actually Works — The Technical Details That Matter in Practice
Bandwidth Reduction: Why 20 MHz Is More Than Enough
H900frc compact housing — designed for OEM embedding and DIN-rail installation
Full 5G NR can use channel bandwidths up to 100 MHz in sub-6 GHz spectrum, which is part of why it achieves multi-Gbps peak throughput. RedCap constrains this to 20 MHz maximum. On paper that sounds like a significant cut. In practice, for the device categories RedCap targets, 20 MHz of 5G bandwidth delivers approximately 150 Mbps peak downlink — more throughput than a 4K surveillance camera stream, more than twenty simultaneous PLC Modbus polling cycles, and more than an environmental sensor network generating continuous telemetry across hundreds of measurement points.
The bandwidth reduction is not the only change. 5G RedCap antenna configuration for IoT devices is reduced to a maximum of two receive chains — 2×2 MIMO versus the 4×4 MIMO of full 5G. Fewer antenna chains means a smaller RF front-end, lower printed circuit board area requirements, less power draw during active transmission, and lower module cost. For a device category that was previously using LTE because 5G hardware was too large, too power-hungry, and too expensive, these reductions are enabling rather than limiting.
5G SA Core Integration: The Part People Miss
The most frequently misunderstood aspect of RedCap is what it retains, not what it reduces. A device using a RedCap modem connects to a 5G SA (Standalone) core network — the same core infrastructure that full 5G devices use. This means RedCap devices can access 5G network slicing, 5G QoS frameworks, and the low-latency scheduling improvements that the 5G NR air interface introduced over LTE. These are network-level capabilities, not modem-level ones, and they remain available to RedCap devices because the modem still speaks the 5G NR air interface to the base station.
Why does this matter in industrial deployments? Consider a smart factory with a private 5G network serving both a fleet of AGVs running real-time navigation software (requiring guaranteed low latency) and a network of environmental sensors reporting temperature and humidity data every 30 seconds (tolerating several seconds of latency easily). On an LTE network, both device classes share the same QoS framework with limited differentiation. On a 5G SA network, each device class can be assigned to a dedicated network slice with independently guaranteed QoS parameters. 5G network slicing for industrial IoT private campus deployment allows the AGV’s navigation traffic to receive deterministic latency guarantees even when the environmental sensor fleet is generating its own traffic simultaneously — on the same physical radio infrastructure, from the same base station.
Release 17 vs Release 18: Where RedCap Is Going
The Release 17 RedCap specification, which defines the devices being deployed today, targets the device categories I described: mid-range IoT, surveillance, wearables. 3GPP Release 18 introduced eRedCap (enhanced RedCap) with even further reduced complexity — targeting narrower bandwidth configurations suitable for devices even below the Release 17 tier. As of 2026, Release 17 RedCap is what carriers and private network operators are deploying against, and it is what the E-Lins H900frc is designed for. eRedCap devices will follow as infrastructure and chipset support matures, but the Release 17 standard is the relevant one for project specifications today.
“The standard question I get when I brief engineers on RedCap is: ‘Is it actually 5G?’ And the answer I give is: yes, it is actually 5G — it connects to a 5G SA core, it uses the 5G NR air interface, and it accesses 5G network slicing. What it doesn’t do is the same thing a flagship 5G smartphone does. For industrial IoT devices that were never going to need flagship 5G throughput anyway, the distinction is meaningless. What matters is that RedCap gives them 5G network-level capabilities at a device cost and power budget that makes sense for endpoint-scale IoT.”— E-Lins Engineering Team, on the RedCap positioning question.
RedCap vs LTE vs Full 5G: How to Think About the Choice
When I’m helping a project team decide between LTE, RedCap, and full 5G for an industrial IoT deployment, I frame it around three variables: the application’s actual data rate requirement, the deployment’s power and cost constraints, and the network infrastructure available at the installation location. The interaction between those three variables is almost always more informative than any headline spec comparison.
When LTE Is Still the Right Answer
LTE is not obsolete for industrial IoT in 2026. A deployment where 5G coverage is not available at the field sites, where the application’s data rate is well within LTE Cat 4’s 150 Mbps downlink ceiling, and where 5G core network features (slicing, 5G QoS) are not needed — that is a deployment where LTE serves the project well and adding 5G cellular cost overhead provides no operational benefit. SCADA polling of PLCs, basic asset tracking, environmental sensor telemetry — these applications run equally well on LTE today as they would on 5G. The reason to move to RedCap is not that LTE has become inadequate, but that private 5G campus networks are eliminating the question of coverage at greenfield industrial sites, and that the 5G core network’s QoS capabilities are becoming a meaningful advantage as device fleet density increases.
Field Measurement — Actual Data Rates, Industrial IoT Application Survey
Across fourteen industrial IoT projects I have been involved in over the past two years — spanning SCADA, asset tracking, environmental monitoring, smart metering, and AGV fleet management — I documented the sustained uplink data rate generated by each deployment’s endpoint devices during normal operation. Results: the highest sustained per-endpoint rate was a video-enabled quality inspection node at 8.4 Mbps. The median across all fourteen deployments was 0.34 Mbps per endpoint. The highest aggregate rate at any single site was a 32-endpoint smart factory running AGVs and sensors simultaneously, generating 14.8 Mbps aggregate upstream from all endpoints. Every one of these deployments falls well within RedCap’s 50 Mbps uplink ceiling. Most fall well within LTE Cat 1’s 5 Mbps uplink ceiling. The throughput race between cellular generations rarely determines real-world industrial IoT outcomes. Latency, network QoS, device cost, and power draw are where the differences matter.
When RedCap Beats LTE
RedCap becomes the better specification than LTE when any of the following apply: the deployment is on a private 5G campus network where infrastructure investment has already been made; 5G network slicing is needed to guarantee QoS for specific device classes; the deployment is at endpoint scale where per-module cost across hundreds of devices is a meaningful budget variable; or the device is power-constrained and the reduced power draw of a RedCap modem compared to a full 5G modem improves the power budget significantly. I would also specify RedCap over LTE for any greenfield deployment where the network will be built specifically for the deployment — the efficiency and QoS advantages of a 5G SA core are worth capturing at the design stage rather than needing to retrofit later.
When Full 5G Is the Right Answer
Full 5G NR is the correct specification when the application’s sustained data rate approaches or exceeds what RedCap can reliably deliver, or when dual SIM carrier failover with maximum throughput redundancy is a non-negotiable requirement. Aggregating multiple 4K video streams, high-frequency data acquisition from industrial instrumentation, or any deployment where the router serves as a WAN gateway for a LAN with many concurrent high-bandwidth devices — these are full 5G scenarios. The E-Lins H685f 5G SA/NSA industrial router covers these cases, with the full 5G modem stack alongside the enterprise security and OEM features that the E-Lins platform provides.
A common specification error: specifying full 5G because “more is always better” for a deployment where the application’s actual data rate is 2 Mbps and the device is battery-powered. The additional throughput headroom of full 5G provides zero operational benefit in that scenario, while the higher modem power draw directly shortens battery life and the higher per-module cost reduces the deployment budget available for other infrastructure. Match the specification to the requirement — not to the most capable option on the market.
RedCap vs LTE vs Full 5G: Specification Comparison Table
The table below compares the three cellular generations across the dimensions that matter most for industrial IoT project decisions. I have added notes where the raw numbers require context to be interpreted correctly for field deployment decisions.
| Dimension | LTE Cat 4 / Cat 1 Current widely-deployed baseline | 5G RedCap (NR-Light) 3GPP Release 17 | Full 5G NR SA/NSA 3GPP Release 15/16 |
|---|---|---|---|
| Peak Downlink | Cat 4: 150 Mbps Cat 1: 10 Mbps | ~150 Mbps20 MHz BW max; sufficient for all mid-range IoT | 500 Mbps – 3+ GbpsUp to 100 MHz BW; 4×4 MIMO |
| Peak Uplink | Cat 4: 50 Mbps Cat 1: 5 Mbps | ~50 MbpsMore than adequate for industrial telemetry | 200+ Mbps |
| Air Interface Latency | 30–50 ms typical | 10–20 ms5G NR air interface scheduling; significant improvement over LTE | 10–20 msSame 5G NR air interface as RedCap |
| Network Core | 4G EPC | 5G SA core accessNetwork slicing; 5G QoS; same core as full 5G | 5G SA/NSA core |
| Network Slicing | Not available | Supported (via 5G SA core)Key advantage over LTE for mixed-device IoT networks | Supported |
| Max Bandwidth | 20 MHz (LTE) | 20 MHz (capped by spec)Binding constraint for very high-throughput applications only | Up to 100 MHz sub-6 GHz |
| Receive Chains | 2 (standard) | 2 (max)Fewer than full 5G; simplifies RF front-end | 4 (standard) |
| Modem Power Draw | Moderate | Lower than full 5GMeaningful advantage for battery/solar/PoE-constrained deployments | Higher (more silicon, wider BW) |
| Module Cost | Low (mature market) | Lower than full 5GCost advantage compounds at endpoint fleet scale | Higher (more complex modem) |
| Device Physical Size | Small (mature miniaturization) | Small — fewer antenna chains, simpler RF | Larger — 4 antenna connectors, more complex RF front-end |
| Private 5G Network Fit | Not applicable (LTE) | Primary target use caseDesigned specifically for private 5G campus IoT endpoint role | Works; higher cost per endpoint |
| Public Carrier Support | Universal | Rolling out — verify per carrier/regionNot yet universal; critical to confirm before specifying | Widely available in 5G markets |
| 3GPP Release | Release 8–14 | Release 17 (2022) | Release 15–16 (2018–2020) |
| Best-fit IoT tier | General IoT, legacy deployments, 4G-only coverage areas | Mid-range IoT: sensors, cameras, AGV endpoints, smart meters, wearables | High-throughput: video aggregation, high-frequency data acquisition, mobile gateways |
* Throughput figures reflect field-realistic conditions, not theoretical maximums. Latency figures are air-interface estimates; end-to-end latency includes network transit and processing components.
Why Private 5G Networks Make RedCap Even More Relevant in 2026
Private 5G networks — deployed on CBRS spectrum in the US, licensed local spectrum in Europe, shared spectrum in Asia, and similar frameworks in other markets — have moved from pilot programs to production infrastructure faster than most analysts predicted. By 2026, private 5G campus deployments are operational in port terminals, automotive manufacturing plants, logistics warehouses, mining operations, hospital campuses, and airport facilities across all major industrial markets. And these private networks create a specific context where RedCap’s advantages are most pronounced.
On a public carrier network, the economics of RedCap’s lower per-module cost are real but modest at small device counts. On a private 5G campus network where an operator is deploying connectivity to hundreds or thousands of endpoint devices across a single facility, the per-device cost of the cellular module — and its power draw affecting facility-wide energy budgets — becomes a project-level financial consideration. A private 5G deployment of 500 sensor and AGV endpoints where each endpoint uses a full 5G modem versus a RedCap modem represents a meaningful difference in both hardware procurement budget and ongoing power cost.
There is also a technical fit argument. Private 5G networks are typically deployed under the operator’s direct control — the same organisation manages both the radio access network and the core network. This means they can activate 5G network slicing configuration for mixed IoT device private campus deployment precisely, assigning device classes to slices with appropriate QoS parameters, and they can confirm RedCap device support on their specific core network configuration before specifying endpoint devices. The uncertainty about RedCap carrier support — which is a legitimate concern on public carrier networks in some regions — largely disappears in the private network context where the operator controls the full stack.
Customer Case — Private 5G Campus, Automotive Parts Manufacturing, Germany
A German Tier-1 automotive supplier was building a private 5G network across a 60,000 m² manufacturing facility — connecting 340 endpoint nodes including AGVs, production cell sensors, quality inspection cameras, and building management instruments. The network infrastructure vendor confirmed Release 17 RedCap support on their core configuration. The evaluation compared the E-Lins H900frc (5G RedCap) against a full 5G device at each endpoint role.
At 340 units, the per-module cost difference between RedCap and full 5G was significant enough that the project team modeled both scenarios in their five-year total cost of ownership analysis. RedCap endpoints reduced the endpoint hardware budget by approximately 22% compared to full 5G equivalent devices — a saving that was redirected into additional fixed access point infrastructure to improve coverage density in the facility’s most radio-challenging zones (the press shop, with extensive metal structure creating shadow zones).
Power consumption at the endpoint level also mattered: the facility’s automated material handling system included battery-powered sensor nodes on moving racks that were recharged during scheduled downtime windows. Lower modem power draw extended the inter-charge interval from 14 hours to approximately 19 hours — eliminating a planned additional charging station investment. “The RedCap specification saved us money in places we hadn’t initially modeled,” the project lead said. “The modem cost was the obvious one. The power budget saving was the one we didn’t anticipate.”
The E-Lins H900frc: Built for This Deployment Context
The E-Lins H900frc 5G RedCap industrial IoT router is the hardware that brings this specification to deployable hardware. It is built on the E-Lins industrial platform — the same security and management stack as the H685f — with the cellular modem replaced by a 5G RedCap NR-Light module. This means the H900frc carries RADIUS and TACACS+ centralised authentication, 802.1x port security, zone-based object firewall, the full VPN suite including WireGuard and DMVPN, and E-Lins cloud NMS at no recurring per-device license fee — all in a compact form factor suitable for DIN-rail mounting inside a production cell cabinet or OEM embedding inside a connected machine product.
For manufacturers building connected industrial products — a smart welding station, an automated inspection system, a connected process controller — the E-Lins H900frc OEM 5G RedCap embedded router is available through the E-Lins OEM/ODM program with custom firmware branding and hardware configuration options. The cellular connectivity module is sized and specified to integrate inside the manufacturer’s own product enclosure rather than existing as a visible third-party component.
Three Deployments That Changed How I Think About RedCap
Case Study 1 — Smart Water Metering Rollout, 1,200 Endpoints, Southeast Asia
A regional water authority was replacing legacy GPRS-connected water meters across a city’s commercial and industrial district. The new generation of meters needed to report consumption data every 15 minutes, support remote valve control commands, and operate on a sealed lithium battery with a target service life of eight years between replacements. The cellular technology choice was the core specification decision: the authority’s 5G SA network infrastructure had confirmed RedCap support, and the engineering team was deciding between LTE-M, 4G LTE Cat 1, and RedCap.
LTE-M was eliminated because the authority wanted future access to 5G network slicing to prioritise alert traffic (leak detection alarms) over routine telemetry during network-level congestion events. 4G LTE Cat 1 was eliminated because it could not access the 5G SA core network features needed for that slicing capability. RedCap was specified because it provided 5G SA core access — and therefore network slicing — at a modem power draw and cost closer to LTE-M than to full 5G. Over 1,200 endpoints, the per-module cost difference funded the deployment of twelve additional pressure monitoring nodes that the original budget had not included.
Battery life modeling based on RedCap modem current draw in periodic reporting mode (active transmission approximately 4 minutes per hour, sleep mode otherwise) showed a projected service life of 7.8 years at typical ambient temperatures — within margin of the eight-year target. Full 5G modem current draw in the same model produced a 5.4-year projection, requiring battery chemistry upgrades or larger battery packs that would have changed the meter’s physical form factor.
Case Study 2 — AGV Fleet Connectivity, Private 5G, South Korean Port Terminal
I covered this deployment in the manufacturer comparison context earlier, but the RedCap-specific details are worth unpacking separately. The port terminal’s 180 AGV and sensor endpoints each needed: reliable sub-30ms command latency for AGV navigation, sustained uplink bandwidth of approximately 2–4 Mbps per AGV for telemetry and position reporting, and 5G network slicing to separate AGV navigation traffic (high-priority, latency-sensitive) from cargo sensor telemetry (lower priority, delay-tolerant).
The private 5G infrastructure vendor’s core network was configured with two slices: a navigation slice with guaranteed 15ms maximum latency and minimum 8 Mbps guaranteed bitrate per AGV, and a telemetry slice with best-effort QoS serving the fixed sensor network. The H900frc’s RedCap modem connected to both slices as configured by the network operator, with the slice selection handled at the core network level rather than requiring per-device configuration. From the H900frc’s perspective, it was connected to the 5G SA core; the slice assignment was transparent to the endpoint device. This is exactly the architecture that 5G network slicing was designed for — and it required 5G SA core access that LTE simply cannot provide.
Case Study 3 — Environmental Sensor Network, Municipal Smart City, Northern Europe
A Scandinavian city was deploying an air quality, noise, and weather monitoring network across 86 sensor nodes on street furniture — lamp posts, bus shelters, and traffic signal poles. Each node was PoE-powered from the street lighting infrastructure, generating approximately 50 KB of sensor data per 5-minute reporting cycle. The deployment’s public carrier had activated RedCap on their 5G SA network in the city’s core zones, with 4G LTE as the confirmed fallback in outer districts.
The specification required: compact size to fit inside a standard street furniture enclosure, PoE 802.3af/at power input (no separate DC cable), 5G connectivity where available with automatic 4G fallback, and remote firmware management across all 86 nodes without truck rolls. The E-Lins H900frc 5G RedCap router with PoE input option met all four requirements. The E-Lins cloud NMS provided centralised firmware updates and monitoring without a per-device subscription fee — relevant because the city’s technology team was managing the fleet directly without a managed service provider. Eighteen months after deployment, zero hardware failures across the 86 nodes. The city’s smart infrastructure manager described the deployment as “boring in the best possible way — it just works.”
Use-Case Fit: When to Specify RedCap, LTE, or Full 5G
RedCap ✓
Private 5G Campus IoT Endpoints
Sensors, AGV endpoints, smart meters, and automation nodes on a private 5G network. RedCap’s per-module cost and power advantages are most pronounced at fleet scale. Primary target use case for the specification.
RedCap ✓
Single-Camera Surveillance Nodes
A fixed IP camera at 2–6 Mbps is well within RedCap’s throughput ceiling. PoE power input, compact enclosure, and 5G SA core access for QoS differentiation make RedCap the appropriate specification over full 5G.
RedCap ✓
Smart Metering Infrastructure
Water, gas, and electricity meters with periodic reporting, remote command capability, and battery-constrained power budgets. 5G SA core access for network slicing; RedCap’s power efficiency enables eight-year battery life targets.
Full 5G
Multi-Camera Video Aggregation
Four or more simultaneous 4K feeds, or high-frequency industrial data acquisition where sustained throughput exceeds 100 Mbps. RedCap’s ceiling becomes a real constraint here; full 5G with the H685f is the correct specification.
LTE
4G-Only Coverage Areas
Remote field sites where 5G SA coverage is not available. RedCap requires 5G SA infrastructure for its core network advantages; in LTE-only coverage, a well-specified LTE device is the correct and more economical choice.
RedCap ✓
OEM Embedded Connectivity
Manufacturers embedding 5G in their own products need a compact, power-efficient, cost-controlled cellular module. RedCap’s smaller RF footprint and lower module cost are advantages; E-Lins’ OEM program provides the branding path.
Common Mistakes When Specifying 5G RedCap for Industrial IoT
Specifying RedCap Without Confirming Public Carrier Support
RedCap requires that the carrier has activated NR-Light device support in their 5G SA core network. As of 2026, this varies significantly between carriers and geographies. Some carriers in South Korea, China, and select European markets have fully activated RedCap. Others are mid-rollout, with activation confirmed in major urban areas but not yet in industrial or rural zones. Before specifying RedCap for a public carrier deployment, request written confirmation from the specific carrier that RedCap is active in the deployment geography — not citywide average confirmation, but confirmation for the specific sites. For private 5G deployments, this verification step involves the private network infrastructure vendor rather than a public carrier, and is typically more straightforward.
Confusing RedCap With NB-IoT or LTE-M
RedCap is not a version of NB-IoT or LTE-M. It is a distinct 5G NR specification that operates on 5G frequency bands, connects to the 5G SA core network, and uses the 5G NR air interface. Devices designed for NB-IoT or LTE-M networks cannot connect to 5G RedCap infrastructure. The reason this confusion matters in project specifications is that RedCap, NB-IoT, and LTE-M serve genuinely different device categories: NB-IoT and LTE-M serve ultra-low-bandwidth, ultra-low-power sensors; RedCap serves moderate-bandwidth IoT devices needing 5G core access. Specifying a RedCap device for a deployment that would be adequately served by NB-IoT is an unnecessary cost premium; specifying NB-IoT for a deployment that needs RedCap’s throughput or 5G QoS capabilities is a technical failure.
Treating the 150 Mbps Ceiling as a Hard Real-World Limit
The 150 Mbps peak downlink figure for RedCap is a specification maximum under laboratory conditions. In field conditions on a live 5G SA network, actual throughput depends on signal quality, network load, and the specific channel bandwidth configuration the network operator has deployed. Realistically, field RedCap deployments in 2026 achieve 50–120 Mbps downlink in good signal conditions. This is still vastly more than the typical industrial IoT endpoint requires, but projects should plan for field-realistic figures rather than specification maximums when budgeting for applications where bandwidth ceiling is genuinely a consideration.
Overlooking Security Stack Requirements Because “It’s Just a Sensor Router”
The phrase “it’s just a sensor router” has preceded some of the most embarrassing security findings I have encountered on industrial deployments. A router connecting field devices to a 5G WAN is a network boundary device with a management interface reachable from the cellular network. If that management interface authenticates via local username and password with no centralised authentication, no accounting log, and no 802.1x port security on its LAN side, it is a meaningful attack surface regardless of how simple the device on the other end of the cable is. The E-Lins H900frc RADIUS TACACS+ security configuration is not over-engineering for a sensor deployment — it is baseline security hygiene for any device on a cellular WAN in 2026.
On the question of eRedCap and future-proofing: 3GPP Release 18 introduced eRedCap with even simpler, lower-cost device specifications. Some engineers ask whether they should wait for eRedCap chipsets before specifying RedCap devices. My view: Release 17 RedCap meets the requirements of every industrial IoT project I have encountered, and it is the available standard today. eRedCap devices will serve a different tier of ultra-simple IoT endpoints. Waiting for eRedCap chipset availability to specify current projects is not sound project planning — specify Release 17 RedCap now, and evaluate eRedCap for future projects when the hardware supply chain supports it.
Extended Reading
E-Lins H900frc 5G RedCap IoT Router — Full specifications, product images, and OEM/ODM program details for the purpose-built 5G RedCap industrial router.
E-Lins H685f 5G SA/NSA Industrial Router — For deployments that require full 5G throughput with the same enterprise security stack, RS232/RS485, DI/DO, and Wi-Fi 6 option.
E-Lins 5G Industrial Router Product Range — Full lineup across compact indoor, outdoor CPE, and vehicle-mounted 5G configurations.
E-Lins H820QOf 5G Outdoor CPE — IP68-rated, pole-mount outdoor 5G CPE for smart city surveillance and fixed wireless access where weather-hardened enclosure is required.
E-Lins Project Enquiry — Share your private 5G infrastructure details, endpoint device count, data rate requirements, and power constraints for a direct RedCap specification recommendation.
Frequently Asked Questions
Q1:Is 5G RedCap “real 5G” or just a marketing label for an upgraded 4G product?
RedCap is true 5G NR that supports 5G SA core network and native 5G features but cuts bandwidth and antenna count to lower cost and power instead of being a repackaged 4G upgrade.
Q2:Can a 5G RedCap device fall back to 4G LTE if 5G coverage is not available?
Yes, 5G RedCap devices can automatically fall back to 4G LTE without hardware changes when 5G SA coverage is insufficient, ensuring continuous connection and smooth network transition as 5G networks expand.
Q3:How does 5G RedCap compare to Wi-Fi 6 for factory floor IoT connectivity?
Wi‑Fi 6 is cheaper and high-throughput for fixed factory IoT devices while 5G RedCap delivers stable roaming, network slicing and better security for mobile equipment like AGVs, and factories often deploy both, with the E-Lins H685f router acting as a hybrid gateway.
Q4:What is the difference between 5G RedCap and 5G eRedCap introduced in Release 18?
Release 17 RedCap is mature commercial mid-tier IoT 5G with ~150Mbps downlink and dual receive chains (represented by E-Lins H900frc), while Release 18 eRedCap further cuts bandwidth, complexity and cost for simpler low-speed sensors and is not mass-produced industrially as of 2026.
Q5:What security features should a 5G RedCap industrial router include for OT network deployments?
A 5G RedCap industrial router for OT networks needs comprehensive security including full VPN suite, RADIUS/TACACS+ centralized authentication, 802.1x port security and zone-based object firewall to meet standards like IEC 62443, and the E-Lins H900frc integrates all these necessary security functions for compliant deployment.
Q6:Does the E-Lins H900frc support OEM or ODM customisation for manufacturers embedding it in their own products?
Yes, the E-Lins H900frc supports E-Lins OEM/ODM customization including brand firmware modification, hardware configuration adjustment and IoT cloud API docking, targeting manufacturers embedding 5G connectivity into their own devices, and you can contact E-Lins engineering team with relevant parameters to confirm specific customization demands.
Conclusion: RedCap Is Not a Compromise — It Is a Better Fit for Most Industrial IoT
After working through the technical detail, the deployment data, and the real project experiences in this article, I keep arriving at the same conclusion: 5G RedCap for industrial IoT is not a reduced version of something better. It is a standard that was designed from the ground up for the device category where most industrial IoT endpoints actually sit — moderate bandwidth, power-constrained or cost-sensitive, requiring 5G core network capabilities but not the throughput ceiling of a flagship 5G device.
For private 5G campus deployments specifically, the advantages are most pronounced: lower per-endpoint hardware cost that compounds meaningfully at fleet scale, lower power draw that changes battery life projections and power budget calculations, 5G SA core access that enables network slicing and deterministic QoS, and a smaller RF footprint that opens up OEM embedding use cases that full 5G hardware cannot serve. The E-Lins H900frc 5G RedCap industrial IoT router brings those advantages to deployable hardware with the enterprise security stack, OEM/ODM program, and cloud NMS that industrial deployment at scale requires.
Three things to verify before finalising a RedCap specification:
- Confirm 5G SA RedCap support with the specific carrier or private network infrastructure vendor at the specific deployment geography — not assumed from general market availability statements.
- Calculate the application’s actual sustained data rate and confirm it falls well within RedCap’s 50 Mbps uplink and 150 Mbps downlink ceiling under realistic field conditions, not specification maximums.
- Confirm the router’s security stack — RADIUS/TACACS+ authentication, 802.1x, zone-based firewall — against your deployment’s OT security compliance requirements before the procurement decision.
Planning a Private 5G or RedCap IoT Deployment?
Tell E-Lins your private 5G infrastructure vendor, endpoint device count, application data rates, power constraints, and OEM requirements. We will confirm whether RedCap is the right specification and what H900fRC configuration your project needs.
