21 5G Device Categories for IoT
Overview: Right-Size the Modem
Cellular IoT device selection is a fit problem, not a race to the newest radio. The useful question is what the installed device must prove: payload size, movement, latency tolerance, coverage depth, power source, expected lifetime, operator support, and the maintenance path after deployment.
NB-IoT and LTE-M cover many low-power wide-area jobs. RedCap fills a mid-tier 5G NR role for devices that need more throughput than LTE-M but do not need a full smartphone-class modem. Full 5G NR belongs where broadband throughput, private-network engineering, or validated low-latency service is part of the requirement.
For example, a basement water meter that wakes twice per day to send a few counters should not inherit the cost, antenna burden, and power draw of a broadband modem. A trailer tracker that reports while moving may need LTE-M handover and more responsive downlink. A mains-powered inspection camera in a warehouse may justify a RedCap review if moderate video and 5G lifecycle support matter. A robot-control claim, however, is not solved by the label "5G"; it needs measured latency, reliability, coverage, and fallback evidence across the whole service path. The category choice should therefore be recorded as a requirement-to-evidence decision, not as a marketing generation.
A good first pass can be blunt: if the device cannot explain why it needs the next larger category, keep the smaller one in the candidate set and spend the saved complexity on antenna, pilot, and lifecycle evidence.
Start with the smallest category that satisfies the service contract. Over-specifying the modem usually adds power, certification, antenna, tariff, and lifecycle burden without improving the installed system.
First-Pass Category Fit
NB-IoT
Best first candidate for fixed or mostly fixed devices that send compact telemetry, sleep for long periods, and can tolerate patient downlink behavior where the operator supports the service.
LTE-M
Best first candidate when a low-rate device needs practical mobility, handover, richer diagnostics, firmware updates, or more responsive interaction than an NB-IoT-only design can support.
RedCap
A reduced-capability 5G NR option for mid-tier devices such as wearables, cameras, industrial sensors, and gateways where 5G support is useful but full NR complexity is unnecessary.
Full 5G NR
Use for high-throughput devices or carefully engineered low-latency systems where the network, core, QoS, edge placement, and operational evidence are part of the design.
Practitioner: Make a Device-Category Record
A category decision should be written down as an evidence record. The record does not need to be long, but it must connect the application to measurable requirements and deployment constraints. If a pilot later fails, the team can see which assumption broke: coverage, mobility, firmware traffic, antenna performance, operator support, power budget, or latency.
A useful record is specific enough to reject attractive but wrong choices. Instead of writing "cellular sensor," write "fixed valve monitor, 120-byte alarm plus daily health packet, five-year battery target, indoor meter room, no voice, annual firmware update window, two-country operator footprint, and installation antenna limit." That sentence already points the review toward coverage, power, update, and roaming evidence before anyone orders modules.
Selection Workflow
Under the Hood: Capability Labels Are Not Guarantees
The radio category is only one layer of the service. RedCap reduces 5G NR device complexity by limiting parts of the full-NR feature set, but it still depends on deployed network support, module certification, firmware behavior, antenna design, and the traffic model. Full 5G NR can carry demanding workloads, but low-latency or high-reliability claims require an engineered path through the radio, transport, core, edge application, and operations process.
The same caution applies to network slicing and URLLC language. A slice label, a private-network label, or a 5G modem label does not prove deterministic behavior by itself. The evidence is measured end-to-end: latency distribution, packet loss, handover behavior, congestion response, fallback policy, power state transitions, and recovery after faults.
That means the category review must preserve the test conditions. A RedCap camera that works beside a lab cell may fail the real deployment if uplink congestion, indoor attenuation, SIM policy, firmware retry behavior, or cloud ingest limits are different. A full-NR gateway may meet throughput but still miss an alarm objective if the edge application queues events behind bulk video. The under-the-hood question is therefore not "which category is newest"; it is whether every boundary between modem, network, core, application, and operations has evidence for the promised service. A good test plan names those boundaries separately so a pass in one layer cannot hide a failure in another.
Do not write a requirement as "use 5G." Write it as a measurable service: payload size, maximum latency, availability target, coverage footprint, mobility behavior, power budget, update window, and support lifetime.
Boundary Checks
Coverage Boundary
Confirm the target operator supports the chosen category in the actual sites, bands, roaming profile, and deployment countries.
Module Boundary
Check certification, antenna constraints, firmware update path, host interface, SIM/eSIM handling, and diagnostics before committing hardware.
Service Boundary
Measure latency, throughput, sleep/wake behavior, handover, retransmission, and congestion response with realistic payloads.
Lifecycle Boundary
Plan operator sunsets, tariff changes, module substitutions, regulatory variants, and hardware refresh for long-lived fleets.
Phoebe’s Why
Every device category in this chapter has a conducted-power ceiling set by 3GPP and the regulator, so once a category is chosen, transmit power is nearly fixed. Range still has one more lever: the antenna. An isotropic radiator spreads power over the whole sphere; a directional antenna reshapes that same power into a narrower cone, trading coverage angle for reach in the direction it favors. EIRP – power times gain – is what the far end actually receives, and it is the fair way to compare a low-power NB-IoT sensor against a directional RedCap or 5G NR gateway without confusing “bigger category” with “stronger signal.”
The Derivation
Isotropic power density at distance \(d\):
\[S_{iso} = \frac{P_t}{4\pi d^2}\]
Gain redistributes the same power into solid angle \(\Omega\):
\[G = \frac{4\pi}{\Omega} \qquad S = \frac{P_t G}{4\pi d^2}\]
Effective isotropic radiated power:
\[\mathrm{EIRP}_{dBm} = P_{t,dBm} + G_{dBi}\]
At fixed receiver sensitivity, path loss \(\propto 1/d^2\) makes range scale with the square root of EIRP:
\[\frac{d_2}{d_1} = \sqrt{\frac{\mathrm{EIRP}_2}{\mathrm{EIRP}_1}}\]
Worked Numbers: NB-IoT Sensor vs. Directional RedCap Gateway
- NB-IoT sensor: catalog-typical 3GPP UE Power Class 3, \(P_t=23\) dBm \(=10^{2.3}=200\) mW, small omni chip antenna \(G\approx0\) dBi (isotropic-equivalent, catalog-typical for a compact module). EIRP \(=23\) dBm \(=200\) mW.
- RedCap gateway with a directional panel antenna: \(P_t=20\) dBm \(=100\) mW (lower conducted power), \(G=8\) dBi \(=10^{0.8}=6.31\times\) (catalog-typical panel antenna). EIRP \(=20+8=28\) dBm \(=631\) mW.
- EIRP ratio: \(631/200=3.16\times\) (\(=5.00\) dB, matching \((20+8)-(23+0)\)), so range ratio \(=\sqrt{3.16}=1.78\times\) for the directional gateway.
- Coverage angle: the panel’s solid angle is \(1/6.31=15.8\%\) of the sphere the omni sensor covers – the gateway must be aimed, while the sensor does not need to be. Fewer dBm from the modem, more dBi from the antenna, same or better range, at the cost of coverage angle rather than battery.
21.1 Start With the Story
5G device categories are labels for very different device promises. A tiny sensor, mobile tracker, industrial controller, and video gateway should not be judged by the same throughput or latency story.
Start simple: choose the category by payload, power, mobility, cost, and reachability before comparing feature lists.
21.2 Summary
5G-era cellular IoT is a spectrum of device categories. NB-IoT and LTE-M remain strong choices for low-power wide-area devices. RedCap adds a mid-tier 5G NR option for richer IoT devices. Full 5G NR is reserved for high-throughput or engineered low-latency systems where the whole service path is validated.
21.3 Key Takeaway
Choose the lowest-complexity cellular category that satisfies the evidence record: workload, mobility, coverage, power, operator support, module readiness, lifecycle risk, and measured service behavior.