Quick Answer: RedCap and eRedCap are the 5G device classes positioned as successors to LTE Cat-4 and LTE Cat-1 hardware, respectively. Neither operates as 5G until the private network runs 5G standalone (SA) with RedCap enabled, and a module helps only where it supports the network’s 5G band. At oil and gas field sites in 2026, the timing depends on those network conditions and on a thin catalog of industrial RedCap hardware, little of it rated for hazardous areas. The practical path is to write RedCap modules with LTE fallback into the next camera and gateway refresh, let eRedCap mature before touching RTUs, and leave LTE-M and NB-IoT sensors and WirelessHART instruments where they are.
When GSA tallied the 5G RedCap ecosystem in September 2026, it counted 9 chipsets, 34 modules and 46 pieces of customer premises equipment, but only 4 industrial devices. Somewhere in West Texas, an integrator is walking a well pad that has run on Citizens Broadband Radio Service (CBRS) private LTE for a few years, scoping a job that calls for industrial RedCap hardware.
The customer wants new cameras for AI-based leak detection, and the vendor proposal specifies 5G RedCap. The site supervisor raises a broader point: if the cameras go 5G, shouldn’t the remote terminal units (RTUs) and the WirelessHART gateways go with them?
The answer depends on three things no camera proposal can settle on its own. The pad’s core network is 4G. Its radios run LTE in Band 48. And nobody has asked yet what hazardous-area rating each camera location needs.
RedCap Is a Device Answer to a Network Question
Reduced Capability, or RedCap, arrived in 3GPP Release 17 as a lighter 5G device class. Enhanced RedCap, or eRedCap, followed in Release 18 and stripped the design down further. Between them, the two classes cover the range LTE Cat-1 to Cat-4 devices occupy today:
• Release 17 RedCap caps bandwidth at 20 MHz, drops carrier aggregation and dual connectivity, and allows single-antenna designs, according to a GSA article published on 3GPP’s site. The same article puts RedCap’s peak at up to 226 Mbps downlink and 120 Mbps uplink. Qualcomm’s Snapdragon X35 brief lists peaks of 220 Mbps downlink and 100 Mbps uplink, with the uplink running on a single transmit antenna, and presents the chip as a migration path from LTE Cat-4 and higher devices.
• Release 18 eRedCap caps the peak rate at 10 Mbps in both directions and adds an option to narrow the baseband bandwidth for data transmissions from 20 MHz to 5 MHz. Telit Cinterion, a module maker, presents it as the 5G successor to LTE Cat-1 and Cat-1bis at similar data rates.
Both classes need an SA core. Modules built on chipsets like the X35 also carry LTE Cat-4 as a fallback mode: a RedCap camera attached to a 4G Evolved Packet Core (EPC) works, but it works as an LTE camera.
Once SA is in place, the radio-side step can be small. Ericsson launched RedCap in 2023 as a software addition for 5G SA networks built on its equipment, with no new hardware required. Samsung said in 2024 that its RedCap feature would be commercially available that year for both traditional and virtualized RAN, after a field test on a Tier 1 US operator’s commercial network. In early 2025, Samsung and Hyundai Motor completed what Samsung called the industry’s first end-to-end RedCap trial on a private 5G network, using Samsung’s virtualized core and 4.7 GHz radios. Hyundai said it planned to extend RedCap private 5G to its newest electric vehicle plants. At MWC 2026, Eurofiber and Nokia announced that RedCap was being added to Eurofiber’s private 5G ecosystem in the Netherlands, where no mobile operator had yet launched it commercially. Boldyn has since connected environmental sensors in livestock pens over RedCap on a private 5G network in West Sussex. Private networks can move first, provided they already run 5G SA.
On an oil and gas site, the first thing to check is the core. Buying RedCap-capable devices doesn’t bring RedCap to the site, and the step in between is a network migration the customer may not have scheduled.
Not Everything on the Pad Runs on LTE
Before mapping anything to RedCap, list what the LTE network carries. On pads instrumented with WirelessHART, the process instruments never touch cellular at all. They report to a gateway, which Endress+Hauser’s documentation rates for up to 250 field devices, and the gateway passes their data over Ethernet or a serial link to a host such as the RTU or a cellular router. Cellular starts at that host and also carries the cameras and the crew’s handsets. The 450 MHz Alliance’s 2025 equipment report shows a similar range of device categories on the networks it covers, from LTE Cat-4 down to Cat-1, LTE-M and Narrowband IoT (NB-IoT).
Where the AI model runs sets the uplink requirement for the camera tier, and the two common arrangements pull in different directions:
• Central analytics needs a continuous stream. In January 2026, Teledyne FLIR described a liquefied natural gas (LNG) pressure-regulation site at South Korea’s Boryeong LNG Terminal, where a GF77a optical gas imaging (OGI) camera sends real-time video to an AI engine that detects leak plumes and triggers alarms. A single stream might fit within a 10 Mbps device class, but a video gateway carrying several such feeds needs RedCap-class uplink.
• Edge inference sends far less. When the model runs on the camera or a video gateway on site, only alarms and short clips go upstream, and eRedCap may be enough. Hu Jianguo, chief technical expert at the Changqing Oilfield run by China National Petroleum Corporation (CNPC), has described an architecture that runs inference at the edge, in three tiers: model training in the CNPC group cloud, regional management of inference, and real-time inference at edge wells and stations.
Mapped tier by tier, an LTE field site’s device fleet sorts like this.
| Device tier | Typical LTE category today | 5G successor | Status in 2026 |
| Cameras and video gateways | Cat-4 | RedCap | Modules shipping; few industrial products |
| RTUs and data collectors | Cat-1 or Cat-1bis | eRedCap | Not yet commercial |
| Meters and battery sensors | LTE-M or NB-IoT | No direct successor | Stay on LTE-M or NB-IoT |
| WirelessHART gateways and instruments | Not cellular | Not affected directly | Follow the RTU or router the gateway connects to |
| Handsets and push-to-talk | Full LTE | Full 5G | Outside RedCap’s scope |
Of the tiers RedCap and eRedCap are meant to replace, only cameras and video gateways have a successor on sale today, and that is where AI video analytics sits.
| Planning private wireless for oil and gas sites?PrivateLTEand5G covers private network deployments, device readiness and spectrum across oil and gas and other industrial sectors, written for the integrators and operators doing the work.Subscribe to PrivateLTEand5G |
The Device Catalog Is Thinner Than the Operator List
GSA’s September 2026 update counts 43 operators in 28 countries and territories investing in RedCap, and GSA expects the technology to dominate the mid-tier 5G IoT space for the next few years. The device list is narrower: customer premises equipment is the largest category so far, and industrial products remain in single digits.
For field sites, certification narrows the list further. Equipment in a Zone 1 or Class I, Division 1 location needs an explosion-protection (Ex) rating, and the Zone 1 certified 5G devices I found, such as Bartec’s SP9EX1 and Pepperl+Fuchs’s Smart-Ex 03, are full 5G smartphones. RedCap has reached the tier below that: Semtech lists Class I, Division 2, IECEx and ATEX hazardous-location certifications for the RX400. I could not find a RedCap camera with an Ex rating, so in classified areas, the workable pattern for now is an Ex-rated camera wired to a RedCap router mounted in a Division 2 or unclassified location.
The eRedCap timeline is not settled either, and GSA and Ericsson’s Mobility Report measure different milestones:
• GSA expects eRedCap chipsets and devices to become commercially available in early 2027.
• Ericsson’s June 2026 Mobility Report tracks a later milestone: it expects eRedCap’s full commercial potential in 2028 and beyond, after lab trials that start in 2026.
For an RTU fleet, the planning date falls somewhere in that range, and for any one network, it depends on when eRedCap modules list that network’s band.
China supplies the clearest evidence of scale, though the examples below stop short of RedCap at an oil field. China Unicom reported in 2025 that it had deployed 1,000 5G macro base stations across the onshore sites of Sinopec’s Shengli Oilfield, covering more than 11,000 production wells, with more than 8,000 5G devices in operation, but its release does not say which device classes those are. The RedCap example comes from a chemical plant. At Wanhua Chemical’s Fujian site, China Telecom and Huawei announced plans in 2023 for more than 3,000 RedCap cameras and 5,000 distributed control system (DCS) data collectors, integrated with AI and big data analysis. Outside China, Samsung has trialed RedCap on private 5G with Hyundai Motor for its car plants, but I found no public RedCap deployment at an oil and gas site.
| PRO TIP: Write Dual-Mode RedCap Into the Next Camera RFQWhen cameras or video gateways come up for replacement, write two requirements into the request for quotation (RFQ): RedCap in your network’s NR band, with LTE fallback in its LTE band. Where the camera sits in a classified area, put the RedCap radio in a separate router and ask for that router’s hazardous-location certificate for the exact zone or division where it will be mounted. The devices run on today’s LTE network and switch to RedCap once the network supports it, with no second hardware swap. Leave the RTUs on their current plan until eRedCap modules exist for your band. |
Let the Calendar Decide When to Swap
Holding the RTUs back doesn’t mean holding everything back. The device decision should follow events the customer can see coming, and three of them justify buying 5G-capable devices:
• A core migration is the strongest trigger. If the network is moving to 5G SA anyway, RedCap becomes a configuration and licensing question, and the camera and video gateway tier can move with it.
• A scheduled device refresh makes dual-mode hardware an easy call, since the truck is going out regardless.
• Band support changes the default. Once RedCap modules list n72 for a device type, a 450 MHz operator’s next purchases of that type should be RedCap with LTE fallback.
In heavy industry, networks stay in service a long time: SNS Telecom & IT reports that many of Australia’s private LTE networks in mining are being replaced by standalone 5G only after nearly ten years of service, a shift made possible by new area-wide licenses in mid-band spectrum. Chevron’s CBRS network at a New Mexico remediation site launched in late 2023 to serve a program scheduled to run through 2040. An oil and gas customer that built private LTE in the last few years may not touch its core for a long time, and RedCap-capable devices bought in the meantime are likely to spend most of their service lives running as LTE.
AI video is the pressure most likely to change that schedule. If leak-detection or safety analytics need more uplink per camera than Cat-4 hardware delivers, it makes sense to bring the SA migration forward, because shipping RedCap silicon roughly doubles Cat-4’s 50 Mbps peak uplink. RedCap buys nothing, though, for battery sensors on LTE-M or NB-IoT, for WirelessHART fields, or for sites with no plan to leave an LTE core. Those can stay where they are for the life of the current network.
Where Does This Leave You?
If you’re a systems integrator or vendor working on oil and gas sites, scope RedCap as a network decision before it becomes a device quote. Bring each customer a site-by-site check: whether the core is standalone or on a dated roadmap, whether a module exists for the network’s NR band, and what hazardous-area rating each mounting location needs. Done well, the check turns a hardware conversation into a network plan, and the integrator who leads it is well placed to own the refresh that follows. Vendors holding Ex-rated RedCap cameras or a credible n72 roadmap have something this market is short of, and the Executive Voice Program and Partner With Us are built to put that in front of the operators and integrators planning these migrations.
If you run IT or operational technology (OT) for an operator, sort your device fleet by tier before the next vendor meeting: cameras and video gateways, RTUs and data collectors, and battery sensors. Note which RTU or router each WirelessHART gateway connects to, since the gateway follows that host. Then put three questions to your network vendor: when does the core go standalone, which NR band will it run, and is RedCap already enabled on your cells or licensed separately? The answers tell you which tier can move and when, and a private wireless self-audit is a practical place to start the inventory. Pinning down all three may take more than one meeting, and with eRedCap not yet commercial, holding the RTU tier on LTE is a sound position for now.
FAQ
If our RedCap devices run in LTE fallback, are we paying for capability we don’t use?
In fallback, an X35-class module works as an LTE Cat-4 device, so for now you’re paying for an option: a later switch to RedCap without replacing the device. The trade makes sense for cameras, but a Cat-4 fallback radio is more than an RTU’s Cat-1 workload needs.
Should we skip RedCap and wait for eRedCap?
Only for part of the fleet. eRedCap’s 10 Mbps cap suits RTUs and data collectors, and a single camera stream may fit under it. A video gateway carrying several feeds to central analytics won’t, so holding cameras back for eRedCap risks putting them on a device class they’d outgrow.
Will eRedCap replace LTE-M and NB-IoT on battery-powered sensors?
LTE-M and NB-IoT were built for low data rates and deep in-building coverage, which u-blox notes the RedCap specification did not focus on. Release 18’s longer sleep cycles narrow the battery gap, but a sensor sending a few bytes a day gains little from a 10 Mbps radio.
Our network vendor says the 5G upgrade includes RedCap. What should we check?
Ask for interoperability results with your exact module on the vendor’s core, not a reference device. Then ask how the network will stop large numbers of RedCap devices from fragmenting uplink on cells shared with full 5G handsets. GSA says getting that right at high density takes careful network policy.
