30 5G Device Categories for IoT
- eMBB (Enhanced Mobile Broadband): 5G use case for high-throughput applications (4K/8K video, AR/VR); targets >1 Gbps peak, 100 Mbps user rate
- URLLC (Ultra-Reliable Low-Latency Communications): 5G use case for mission-critical IoT; targets <1 ms latency and 99.9999% reliability for industrial automation
- mMTC (Massive Machine-Type Communications): 5G use case targeting >1 million devices/km² for dense IoT sensor deployments; relies on NB-IoT and LTE-M
- 5G NR Device Category Spectrum: eMBB devices (smartphones, CPE) → URLLC devices (industrial robots, medical) → RedCap (wearables, cameras) → NB-IoT/LTE-M (sensors, meters)
- RedCap UE: 3GPP Release 17 reduced-capability 5G device category with 20 MHz bandwidth, 1–2 Rx antennas, and optional half-duplex FDD; targets $5–20 module cost
- 5G IoT Module: Commercial cellular module integrating 5G NR modem, power management, and RF front-end; examples include Quectel RG500Q, Sierra Wireless EM9191
- Power Class 3 (PC3): 5G device power class with maximum 23 dBm TX power; standard for most IoT devices; PC3 limits peak power to extend battery life and reduce SAR
- Network Slicing: 5G capability to partition a single physical network into multiple isolated logical networks (slices), each with guaranteed QoS parameters for different device categories
31 5G Device Categories: From NB-IoT to Full 5G NR
By the end of this chapter, you will be able to:
- Compare NB-IoT, LTE-M, RedCap, and full 5G NR device categories across data rate, latency, power, and cost
- Explain RedCap (Reduced Capability 5G) architecture simplifications and their impact on module cost and battery life
- Apply the device category selection decision tree to match IoT application requirements to the optimal 5G technology
- Calculate cost-performance trade-offs and total cost of ownership across cellular IoT technologies
31.1 Prerequisites
Before diving into this chapter, you should be familiar with:
- Cellular IoT Fundamentals: Basic cellular IoT concepts
- NB-IoT Fundamentals: Narrowband IoT technology
- 5G Advanced Overview: Introduction to 5G evolution
5G Deep Dives:
- 5G Advanced Overview - Evolution timeline
- 5G Network Slicing - Virtual networks for IoT
- 5G URLLC and Future - Critical IoT and 6G
Cellular IoT:
- Cellular IoT Fundamentals - Basic concepts
- NB-IoT Fundamentals - Narrowband IoT
- Cellular IoT Applications - Use cases
In one sentence: 5G offers a spectrum of device categories from NB-IoT ($3-5 modules) for ultra-low-power sensors to full 5G NR ($50-100) for high-performance applications, with RedCap ($15-25) filling the crucial mid-tier gap for wearables and industrial cameras.
Remember this: Match device category to requirements: NB-IoT for 10+ year battery sensors, LTE-M for mobile tracking with voice, RedCap for wearables and HD video, and full 5G NR for maximum performance.
31.2 For Beginners: Understanding 5G Device Categories
The Problem: Not all IoT devices need the same capabilities. A smart meter sending daily readings doesn’t need the same modem as an autonomous vehicle requiring real-time control.
The Solution: 3GPP defines different device categories, each optimized for specific use cases:
| Category | Think of it as… | Best for |
|---|---|---|
| NB-IoT | A postcard | Simple messages, very long battery |
| LTE-M | A text message | Mobile devices, voice calls |
| RedCap | An email with attachments | HD video, industrial sensors |
| Full 5G | Video call + screen share | Everything, maximum performance |
Why This Matters:
- Cost: NB-IoT module costs $3-5, full 5G costs $50-100
- Battery: NB-IoT lasts 10+ years, full 5G lasts days
- Capability: Choose the minimum needed to save money and power
Analogy: Think of it like airline tickets: - NB-IoT = Economy (cheap, basic, gets you there) - LTE-M = Premium Economy (better comfort, reasonable price) - RedCap = Business Class (good features, higher cost) - Full 5G = First Class (all features, highest cost)
“Not every IoT device needs the same 5G power!” Sammy the Sensor said. “I am a simple temperature sensor – NB-IoT at three dollars is perfect for me. But a security camera streaming video needs RedCap, and an autonomous car needs full 5G. It is all about matching the technology to the job!”
“Think of it like choosing a vehicle,” Lila the LED suggested. “NB-IoT is a bicycle – simple, cheap, gets the job done for short trips. LTE-M is a scooter – faster, more capable, still affordable. RedCap is a car – comfortable with good features. And full 5G is a sports car – top performance for when you need everything!”
Max the Microcontroller explained, “The cost differences are huge. An NB-IoT module costs about three to five dollars, but a full 5G modem costs fifty to one hundred dollars. If you are deploying ten thousand sensors, that cost difference adds up fast. Always choose the minimum capability that meets your requirements.”
“Battery life is the other big difference,” Bella the Battery noted. “NB-IoT can last ten-plus years on a coin cell. LTE-M lasts several years. RedCap might last months to a year. And full 5G lasts days at best. So if your device is in a hard-to-reach place where you cannot change batteries, NB-IoT or LTE-M is the way to go!”
The deployment cost savings from choosing the right device category:
\[\Delta C = N \times (C_{over-spec} - C_{min-spec})\]
where \(N\) is the number of devices, \(C_{over-spec}\) is the cost of an unnecessarily capable modem, and \(C_{min-spec}\) is the minimum-capability modem that meets requirements.
Example: Deploying 10,000 smart meters that only need to report 100 bytes once per hour:
**Over-specified (Full 5G NR at \(75/modem):**\)\(C_{5G} = 10,000 \times 75 = \$750,000\)$
**Right-sized (NB-IoT at \(4/modem):**\)\(C_{NB-IoT} = 10,000 \times 4 = \$40,000\)$
Savings: \[\Delta C = 10,000 \times (75 - 4) = \$710,000\]
This is a 95% cost reduction (18.75× cheaper) with zero functional impact – NB-IoT’s 250 kbps is 25,000× more bandwidth than needed for 100 bytes/hour. The same logic applies to data plans: over-specified connectivity wastes recurring costs every month for the device’s lifetime.
31.3 5G IoT Device Spectrum
The 5G ecosystem provides a complete spectrum of device capabilities, allowing designers to match technology to requirements:
31.4 Device Category Comparison Matrix
31.4.1 Technical Specifications
| Feature | NB-IoT | LTE-M | RedCap | Full 5G NR |
|---|---|---|---|---|
| Peak DL | 250 kbps | 1 Mbps | 150 Mbps | 10+ Gbps |
| Peak UL | 250 kbps | 1 Mbps | 50 Mbps | 1+ Gbps |
| Latency | 1-10 s | 10-15 ms | 5-10 ms | <1 ms (URLLC) |
| Bandwidth | 200 kHz | 1.4 MHz | 20 MHz | 100+ MHz |
| Modem Cost | $3-5 | $5-10 | $15-25 | $50-100 |
| Battery | 10+ years | 5-10 years | 1-5 years | Days-weeks |
| Use Case | Sensors, meters | Asset tracking | Wearables, cameras | Phones, FWA |
31.4.2 Power Consumption Comparison
31.4.3 When to Choose Each Category
| Category | Choose When… | Avoid When… |
|---|---|---|
| NB-IoT | Battery must last 10+ years; Data < 250 kbps; Latency >1s OK | Need mobility; Need real-time response |
| LTE-M | Need handover/mobility; Voice support required; Moderate latency OK | Need video streaming; Ultra-low latency required |
| RedCap | HD video required; $50+ module cost too high; 5G-native preferred | Battery must last >5 years; Data < 1 Mbps sufficient |
| Full 5G | Maximum performance needed; URLLC required; Cost is secondary | Battery-powered; Simple sensor application |
31.5 RedCap (Reduced Capability 5G)
31.5.1 What is RedCap?
RedCap (3GPP Release 17) creates a new device category between full 5G and LTE-M:
Design Goals:
- 5G native (no LTE fallback needed)
- Reduced complexity (lower modem cost)
- Reasonable data rates (HD video possible)
- Better battery life than full 5G
31.5.2 RedCap Specifications by Release
| Parameter | Full 5G NR | RedCap (R17) | eRedCap (R18) |
|---|---|---|---|
| Max Bandwidth | 100-400 MHz | 20 MHz (FR1) | 5 MHz (FR1) |
| MIMO Layers | 4-8 | 1-2 | 1 |
| Antennas | 2-4 Rx | 1 Rx | 1 Rx |
| DL Data Rate | 10+ Gbps | 150 Mbps | 10 Mbps |
| Target Cost | $50-100 | $15-25 | $8-15 |
31.5.3 RedCap Architecture Simplifications
RedCap reduces modem complexity through:
- Reduced Bandwidth: 20 MHz vs 100+ MHz
- Simpler RF frontend
- Lower ADC/DAC requirements
- Reduced baseband processing
- Single Receive Antenna: 1 Rx vs 2-4 Rx
- Smaller device form factor
- Lower power consumption
- Reduced cost
- Fewer MIMO Layers: 1-2 vs 4-8
- Simpler signal processing
- Lower computational requirements
31.5.4 RedCap Use Cases
31.5.5 RedCap vs LTE-M: When to Choose Which?
| Factor | Choose RedCap | Choose LTE-M |
|---|---|---|
| Data Rate | Need 1-150 Mbps | <1 Mbps sufficient |
| Future-proofing | 5G network required | LTE network acceptable |
| Battery | 1-5 years OK | 5-10 years needed |
| Voice | VoNR if needed | VoLTE native |
| Cost | $15-25 acceptable | Need <$10 module |
| Availability | 2024+ deployment | Already deployed |
31.6 Understanding Check
Scenario: You’re designing connectivity for three different IoT products: 1. A smart electricity meter that reports hourly readings for 15 years 2. A delivery drone requiring real-time control 3. A security camera streaming 4K video
Questions:
- Which device category would you choose for each?
- What are the cost implications of each choice?
- How would battery/power constraints affect your decision?
1. Device Category Selection: | Device | Category | Reasoning | |——–|———-|———–| | Smart meter | NB-IoT | 15-year battery, hourly readings (very low data), cost-sensitive | | Delivery drone | Full 5G NR + URLLC | Real-time control requires <10ms latency, 99.999% reliability | | 4K camera | RedCap | 25 Mbps streaming, cost-effective vs full 5G |
2. Cost Implications: | Device | Module Cost | Volume (10K units) | Total | |——–|————-|——————-|——-| | Smart meters | $4 | 10,000 | $40,000 | | Drones | $75 | 100 | $7,500 | | Cameras | $20 | 1,000 | $20,000 |
3. Power Constraints:
- Meter: Battery-powered, must last 15 years → NB-IoT’s PSM essential
- Drone: Battery-powered but charged after each flight → power less critical than latency
- Camera: Mains-powered → power not a constraint, can use RedCap’s higher power consumption
31.7 Worked Example: Device Category Selection for Smart Factory
Scenario: A manufacturing plant needs connectivity for three IoT use cases: - 500 quality inspection cameras (25 Mbps each) - 100 AGVs requiring real-time control (<10 ms latency) - 10,000 environmental sensors (5-year battery life)
Given:
- Cameras: 500 units, 4K video at 25 Mbps
- AGVs: 100 units, safety-critical control
- Sensors: 10,000 units, temperature/humidity readings every 5 minutes
Steps:
- Match cameras to device category:
- Data rate: 25 Mbps per camera
- NB-IoT: 250 kbps (100x insufficient)
- LTE-M: 1 Mbps (25x insufficient)
- RedCap: 150 Mbps (6x headroom, $15-25/module)
- Full 5G NR: 10+ Gbps (overkill at $50-100/module)
- Selection: RedCap
- Match AGVs to device category:
- Latency: <10 ms (safety-critical)
- Reliability: 99.999% required
- Only Full 5G NR with URLLC meets requirements
- Selection: Full 5G NR with URLLC
- Match sensors to device category:
- Data rate: ~100 bytes every 5 minutes = 3 bps average
- Battery: 5+ years required
- NB-IoT: 10+ year battery with PSM
- Selection: NB-IoT
Result: | Device | Category | Unit Cost | Quantity | Total | |——–|———-|———–|———-|——-| | Cameras | RedCap | $20 | 500 | $10,000 | | AGVs | Full 5G NR | $75 | 100 | $7,500 | | Sensors | NB-IoT | $4 | 10,000 | $40,000 | | Total | | | 10,600 | $57,500 |
Key Insight: Using the appropriate device category for each use case saves significant cost compared to using full 5G NR for everything ($50 x 10,600 = $530,000 vs $57,500).
31.8 5G IoT Device Category Selection Decision Tree
This decision framework guides the selection of the optimal 5G device category:
31.9 Technology Migration Timeline: Planning for Multi-Generation Coexistence
One of the hardest practical decisions in cellular IoT is not choosing the best technology today – it is planning for the transition between generations. Devices deployed in 2025 will still be operating in 2035, by which time the cellular landscape will have shifted significantly.
Expected network sunset timeline:
| Technology | Peak deployment | Expected sunset | Replacement path |
|---|---|---|---|
| 2G (GSM) | 2005 | 2025–2028 (ongoing) | NB-IoT or LTE-M |
| 3G (UMTS) | 2012 | 2025–2027 (mostly done) | LTE-M or NB-IoT |
| 4G LTE (full) | 2020 | 2035–2040 | 5G NR |
| NB-IoT (R13+) | 2025 | Not before 2035 (3GPP guaranteed) | RedCap or NR-Light |
| LTE-M (R13+) | 2024 | Not before 2035 (3GPP guaranteed) | RedCap or NR-Light |
| RedCap (R17) | 2026–2028 | Not before 2040 | NR evolution |
Why this matters for device selection:
A smart meter deployed in 2025 with a 15-year operational lifetime must survive until 2040. Choosing a technology nearing sunset risks stranded assets – devices that lose connectivity when the network shuts down.
Case study: AT&T 3G sunset impact on fleet tracking (February 2022)
When AT&T shut down its 3G network on February 22, 2022, approximately 10 million IoT devices lost connectivity overnight. Fleet management provider CalAmp reported that 12% of its 3.2 million active trackers (384,000 devices) used 3G-only modems. The company spent USD 28 million on emergency device replacements – USD 73 per device for hardware plus USD 45 per truck roll for installation.
Companies that had deployed dual-mode (3G/4G) or software-defined radio modems experienced zero disruption because the modem automatically fell back to 4G LTE. The lesson: paying USD 8–15 more per module for multi-mode capability avoids the USD 118 per-device replacement cost when a network sunsets.
Migration-safe device selection (2025 guidance):
| Use case | Recommended module | Why |
|---|---|---|
| 15-year meter/sensor | NB-IoT + LTE-M dual-mode | Both guaranteed through 2035; future firmware update to RedCap via FOTA |
| 5-year tracker | LTE-M (Cat-M1) | Full LTE compatibility ensures longevity; handover for mobility |
| 3-year wearable | RedCap (if available) or LTE-M | RedCap offers mid-tier performance; LTE-M as fallback |
| New industrial deployment | 5G NR (if infrastructure exists) | Longest runway; avoid starting on legacy |
Key insight: The safest strategy for long-lived IoT devices is dual-mode NB-IoT/LTE-M with FOTA (firmware-over-the-air) capability. This provides two independent fallback paths and the option to upgrade to RedCap via software when RedCap networks reach sufficient coverage (expected 2027–2029).
31.10 Summary
Four device categories span the 5G IoT spectrum: NB-IoT, LTE-M, RedCap, Full 5G NR
NB-IoT ($3-5): Best for ultra-low-power sensors needing 10+ year battery life
LTE-M ($5-10): Best for mobile tracking with handover and optional voice
RedCap ($15-25): New mid-tier category for wearables, cameras, and industrial sensors
Full 5G NR ($50-100): Maximum performance for URLLC and high-bandwidth applications
Match category to requirements: Using NB-IoT instead of full 5G can reduce costs by 95%
31.11 Concept Relationships
31.12 See Also
31.13 Try It Yourself
Common Pitfalls
Selecting a 5G eMBB module (designed for continuous high-throughput use) for a temperature sensor that reports every 15 minutes results in standby current of 10–50 mA — draining a 2000 mAh battery in 2–8 days. For IoT sensors, use LTE-M (PSM + eDRX, ~3 µA sleep) or NB-IoT (~1.5 µA sleep). Reserve 5G eMBB for video streaming, AR/VR, and always-on edge devices.
5G URLLC (<1 ms latency, 99.9999% reliability) requires specific network configurations: dedicated network slices, edge computing co-located at base stations, and URLLC-capable UEs. Standard 5G SA/NSA deployments do not provide URLLC guarantees. Industrial applications requiring URLLC must negotiate dedicated slice agreements with operators and verify base station edge computing proximity.
5G NR (especially mmWave) has significantly less coverage than LTE. In 2025, 5G covers ~50% of the US population but a much smaller fraction of geographic area. IoT devices in rural, underground, or remote locations may lack 5G coverage for years. Design systems with multi-RAT fallback (5G → LTE → NB-IoT/LTE-M) to ensure connectivity in areas without 5G coverage.
Developers often default to NB-IoT/LTE-M for all IoT use cases, missing 3GPP Release 17 RedCap which targets mid-range IoT: wearables needing >1 Mbps, industrial sensors with video capability, and smart city cameras. RedCap bridges the gap between NB-IoT (narrowband, low data rate) and eMBB (high power, expensive), offering ~10 Mbps with $10–20 module cost. Evaluate RedCap before defaulting to eMBB modules for mid-tier IoT.
31.14 What’s Next
| Chapter | Focus Area |
|---|---|
| 5G Network Slicing for IoT | Virtual networks, eMBB/URLLC/mMTC slices, and private 5G deployment |
| 5G URLLC and 6G Vision | Mission-critical IoT, power saving features, and 6G timeline |
| Private 5G Networks | Enterprise deployment models, spectrum options, and ROI analysis |
| Cellular IoT Applications | Real-world cellular IoT deployments across industry verticals |