29  5G Advanced and 6G for IoT

In 60 Seconds

5G-Advanced (Releases 17-18) introduces RedCap devices that bridge the gap between NB-IoT and full 5G NR, network slicing to run multiple virtual networks with different QoS on shared infrastructure, and URLLC for sub-1ms latency in mission-critical IoT. 6G (expected 2030+) will push further with integrated sensing, AI-native design, and sub-0.1ms latency.

Key Concepts
  • 5G NR (New Radio): The 5G air interface standard operating on sub-6 GHz and mmWave bands; uses OFDM with flexible numerology (15–240 kHz subcarrier spacing)
  • mmWave (millimeter wave): 5G spectrum bands above 24 GHz (24–100 GHz); provides multi-Gbps throughput but limited to <200 m range with no obstacle penetration
  • Massive MIMO: 5G antenna technology using 64–256 antenna elements at base stations to serve multiple devices simultaneously via spatial multiplexing (beamforming)
  • 6G Research: Next-generation communications research targeting 1 Tbps peak throughput, sub-100 µs latency, and native AI integration; standardization expected 2030+
  • AI-Native Network: 6G concept embedding ML inference directly in the radio access network for real-time channel prediction, resource allocation, and anomaly detection
  • Integrated Sensing and Communication (ISAC): 6G feature enabling base stations to simultaneously transmit data and perform radar-like sensing of the physical environment
  • Non-Terrestrial Networks (NTN): 5G/6G extension supporting satellite (LEO, MEO, GEO) and aerial (HAPS, UAV) communication nodes for global IoT coverage
  • RedCap (Reduced Capability): 3GPP Release 17 5G device category for IoT with reduced complexity: 1–2 Rx antennas, 20 MHz BW, targeting wearables and industrial sensors

30 5G Advanced: The Next Evolution in Cellular IoT

Learning Objectives

By the end of this section, you will be able to:

  • Explain 5G-Advanced (Release 17-18) features and their impact on IoT device design
  • Compare RedCap, NB-IoT, LTE-M, and full 5G NR across cost, latency, and throughput dimensions
  • Design network slicing architectures for diverse IoT requirements
  • Evaluate private 5G networks for enterprise IoT deployments
  • Differentiate URLLC capabilities from other 5G service classes for mission-critical applications
  • Assess 6G performance targets and their implications for IoT system planning (2030+)

30.1 Prerequisites

Before diving into this chapter, you should be familiar with:

Cellular IoT:

Comparisons:

Key Takeaway

In one sentence: 5G-Advanced introduces RedCap devices that bridge the cost-capability gap between NB-IoT ($5) and full 5G ($100), while network slicing enables dedicated virtual networks for different IoT requirements on shared infrastructure.

Remember this: Match device category to requirements: NB-IoT for 10+ year battery sensors, LTE-M for mobile tracking, RedCap for wearables and cameras, and URLLC slice for sub-millisecond industrial control.

“5G is the next big thing for IoT!” Sammy the Sensor exclaimed. “While NB-IoT and LTE-M are great for simple sensors, 5G opens up a whole new world. Imagine connecting not just thousands but millions of devices in a single square kilometer – that is what 5G’s mMTC mode can do!”

“RedCap is my favorite 5G feature,” Lila the LED said. “It stands for Reduced Capability, and it fills the gap between cheap NB-IoT modules and expensive full 5G modems. A RedCap device costs about fifteen to twenty-five dollars and can handle things like smartwatches with displays, security cameras streaming video, and industrial sensors that need more bandwidth than NB-IoT can provide.”

Max the Microcontroller added, “Network slicing is incredibly clever. One physical 5G network can be split into multiple virtual networks, each optimized for different needs. One slice handles factory robots that need instant response, another handles video cameras that need high bandwidth, and a third handles thousands of simple sensors. All on the same cell tower!”

“And looking even further ahead,” Bella the Battery said, “6G is expected around 2030 with even faster speeds and lower latency. But for now, 5G-Advanced already gives us amazing tools for IoT. The key is matching the right 5G technology to your application – not every sensor needs the full power of 5G!”

30.2 Chapter Overview

This topic is covered in three focused chapters:

30.2.1 5G Device Categories for IoT

Deep dive into selecting the right 5G device category:

  • NB-IoT, LTE-M, RedCap, Full 5G NR comparison
  • RedCap specifications and use cases (Release 17-18)
  • Cost-performance trade-offs ($3-5 to $50-100 per module)
  • Device category selection decision tree

30.2.2 5G Network Slicing for IoT

Understanding virtual networks on shared infrastructure:

  • Network slicing architecture (eMBB, URLLC, mMTC)
  • Private 5G deployment models (standalone, hybrid, carrier slice)
  • Spectrum options (CBRS, n78, mmWave)
  • Cost analysis: private vs carrier slicing

30.2.3 5G URLLC and 6G Vision

Mission-critical IoT and future technologies:

  • URLLC requirements (<1ms latency, 99.999% reliability)
  • Power saving features (PSM, eDRX for 10+ year battery)
  • 6G timeline and capabilities (2030+, 100x improvements)
  • LTE-M handover optimization for mobile fleet tracking

30.3 For Beginners: Understanding 5G Evolution

The 5G Evolution:

  • 5G (Release 15-16): The initial 5G we have today
  • 5G-Advanced (Release 17-18): Enhanced 5G, arriving 2024-2025
  • 6G (Release 21+): Next generation, expected 2030+

Why 5G-Advanced Matters for IoT:

  1. RedCap (Reduced Capability): New device class between full 5G and NB-IoT
    • Cheaper than full 5G (simpler chips)
    • More capable than NB-IoT (higher data rates)
    • Perfect for: Wearables, industrial sensors, cameras
  2. Better Positioning: Centimeter-level location accuracy
    • Critical for: Autonomous vehicles, drones, warehouses
  3. Improved Power Efficiency: Extended battery life
    • Important for: All battery-powered IoT
  4. Network Slicing: Virtual private networks within 5G
    • Use case: Dedicated capacity for critical IoT

Analogy: Think of it like airline tickets: - NB-IoT = Economy (cheap, basic, gets you there) - RedCap = Premium Economy (better comfort, reasonable price) - Full 5G = Business Class (all features, higher cost) - URLLC = Emergency lane (guaranteed priority, highest cost)

30.4 5G Evolution Timeline

3GPP release timeline from 2016 to 2030 showing IoT evolution: Release 13 (2016) introduced NB-IoT/LTE-M, Release 15-16 (2018-2020) brought 5G NR with eMBB and URLLC, Release 17-18 (2022-2024) is 5G-Advanced with RedCap and NTN, Release 21+ (2030) begins 6G era.
Figure 30.1: 3GPP release timeline showing 5G evolution from Release 13 to 6G

30.5 5G Device Categories Quick Reference

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

For detailed device category selection guidance, see 5G Device Categories for IoT.

30.6 Network Slice Types for IoT

Slice Type SLA Guarantee IoT Use Case
eMBB Throughput (100+ Mbps) Video surveillance, AR/VR
URLLC Latency (<1 ms), Reliability (99.999%) Factory automation, autonomous vehicles
mMTC Density (1M devices/km²) Smart meters, agriculture sensors
Custom Application-specific Private IoT networks

For network slicing architecture and private 5G deployment, see 5G Network Slicing for IoT.

30.7 Worked Example: Selecting the Right 5G Device Category for a Smart City Deployment

Scenario

A municipality is deploying connected infrastructure across a mid-size city (population 200,000). Three application types need cellular connectivity:

Application Count Data per Message Frequency Mobility Latency Need
Smart streetlights 8,000 50 bytes (status + energy) Every 15 min None Minutes OK
Traffic cameras 200 500 KB (JPEG snapshot) Every 30 sec None <2 sec
Connected buses 150 200 bytes (GPS + passenger) Every 5 sec 60 km/h <1 sec

Step 1: Match each application to a device category.

Streetlights – Low data, no mobility, long battery life not required (mains-powered), but cost at scale matters. 8,000 units at $3-5/modem (NB-IoT) = $24,000-40,000 vs $15-25/modem (RedCap) = $120,000-200,000. NB-IoT is the clear choice – 250 kbps is more than sufficient for 50-byte messages.

Traffic cameras – 500 KB every 30 seconds = ~133 kbps sustained throughput. NB-IoT’s 250 kbps is theoretically sufficient but leaves no headroom for bursts or retransmissions. LTE-M’s 1 Mbps is marginal for peak loads (e.g., sending 10 consecutive frames during incidents). RedCap at 150 Mbps handles this comfortably with headroom for firmware OTA and occasional video clips. At 200 units, cost difference is manageable: 200 x $20 (RedCap) = $4,000.

Connected buses – Mobility at 60 km/h rules out NB-IoT (no handover). LTE-M supports handover up to 160 km/h and 200-byte messages easily. At $5-10/modem x 150 = $750-1,500 – much cheaper than RedCap with no real benefit from higher bandwidth.

Step 2: Calculate 5-year connectivity costs.

Application Technology Modem Cost Data Plan 5-Year TCO
Streetlights NB-IoT $32,000 $1.50/mo x 8,000 x 60 = $720,000 $752,000
Cameras RedCap $4,000 $8/mo x 200 x 60 = $96,000 $100,000
Buses LTE-M $1,125 $5/mo x 150 x 60 = $45,000 $46,125
Total $37,125 $861,000 $898,125

Key Insight: Modem cost is only 4% of 5-year TCO – the data plan dominates. Choosing NB-IoT for streetlights saves $160,000 in modem costs AND provides the lowest data plan rates. The right device category per application type saves roughly 30% compared to using RedCap for everything.

The Total Cost of Ownership (TCO) for cellular IoT over \(N\) years is:

\[TCO = N_{devices} \times (C_{modem} + C_{data/month} \times 12 \times N)\]

Example: Compare NB-IoT vs RedCap for 8,000 smart streetlights over 5 years:

NB-IoT option: \[TCO_{NB-IoT} = 8000 \times (4 + 1.50 \times 12 \times 5) = 8000 \times (4 + 90) = 8000 \times 94 = \$752,000\]

RedCap option: \[TCO_{RedCap} = 8000 \times (20 + 3 \times 12 \times 5) = 8000 \times (20 + 180) = 8000 \times 200 = \$1,600,000\]

Choosing NB-IoT saves $848,000 (53% reduction) because: - Lower modem cost: \((20-4) \times 8000 = \$128,000\) saved - Lower data plan: \((3-1.50) \times 12 \times 5 \times 8000 = \$720,000\) saved

The data plan savings dwarf the modem savings (5.6×), proving that right-sizing device capability is critical for IoT economics at scale.

30.8 6G Performance Targets

Parameter 5G 6G Target Improvement
Peak Rate 20 Gbps 1 Tbps 50x
User Rate 100 Mbps 1 Gbps 10x
Latency 1 ms 100 μs 10x
Reliability 99.999% 99.99999% 100x
Density 1M/km² 10M/km² 10x
Energy Efficiency Baseline 100x better 100x

For URLLC details and 6G vision, see 5G URLLC and 6G Vision.

30.10 Summary

Key Takeaways
  1. 5G-Advanced (Release 17-18) introduces RedCap for mid-tier IoT devices

  2. RedCap fills the gap between NB-IoT ($5) and full 5G ($100) with ~$20 modems

  3. Network slicing enables custom virtual networks for different IoT requirements

  4. Private 5G offers dedicated capacity, low latency, and data sovereignty

  5. URLLC achieves 1ms latency and 99.999% reliability for critical IoT

  6. Power saving (PSM, eDRX) enables multi-year battery life for NB-IoT/LTE-M

  7. 6G (2030+) will bring sensing, AI-native networks, and 100x improvements

30.11 Knowledge Check

30.12 Concept Relationships

How This Connects

Builds on:

Extends to:

  • 5G Network Slicing uses the 5G-Advanced infrastructure to create isolated virtual networks for different IoT service classes
  • Private 5G Networks applies RedCap and network slicing concepts to enterprise-controlled deployments

Contrasts with:

  • LoRaWAN - Unlicensed LPWAN achieves similar battery life at 1/10th the per-device cost but lacks 5G’s mobility and latency guarantees
  • Wi-Fi 6E and 7 - Local high-throughput connectivity without wide-area coverage or operator SLAs

30.13 See Also

Related Resources

Technical Specifications:

Industry Applications:

Further Reading:

30.14 Try It Yourself

Hands-On Challenge

Task: Design a 5G connectivity strategy for a smart factory with three application types:

Requirements:

  • 200 quality inspection cameras (25 Mbps each, stationary)
  • 50 AGVs (automated guided vehicles) requiring <10 ms latency for collision avoidance
  • 10,000 environmental sensors (temperature, humidity, pressure) reporting every 5 minutes

Your Challenge:

  1. Choose the appropriate 5G device category for each application type (NB-IoT, LTE-M, RedCap, or full 5G NR)
  2. Calculate the total annual connectivity cost assuming:
    • NB-IoT: $3/month/device
    • LTE-M: $6/month/device
    • RedCap: $20/month/device
    • Full 5G NR: $50/month/device
  3. Justify why a single device category for all three applications would be suboptimal

Expected Outcome:

  • Cameras: RedCap (150 Mbps sufficient for 25 Mbps streams, $20/month = $48,000/year for 200 units)
  • AGVs: Full 5G NR with URLLC (<1 ms latency for safety-critical control, $50/month = $30,000/year for 50 units)
  • Sensors: NB-IoT (stationary, low data, $3/month = $360,000/year for 10,000 units)
  • Total: $438,000/year vs all-5G-NR: $50 × 10,250 × 12 = $6,150,000/year (93% savings)

Reflection Questions:

  • What happens to AGV safety if you choose RedCap (5-10 ms latency) instead of full 5G URLLC?
  • Why would using full 5G NR for sensors waste money despite working technically?
  • How does network slicing enable these three device types to coexist on shared infrastructure?

Common Pitfalls

6G is in early research phase (2026 timeframe) with no commercial deployments before 2030. Designing IoT systems today around 6G features (Tbps throughput, sub-100 µs latency, ISAC radar sensing) means planning for hypothetical capabilities. Current production IoT deployments should use 5G NR, LTE-M, or NB-IoT. Track 6G standardization via ITU-R IMT-2030 documents but do not include 6G dependencies in near-term system designs.

5G NR modems consume 3–5× more power than LTE-M modems during active transmission. Deploying 5G NR on battery-powered IoT sensors that transmit infrequently results in rapid battery drain from modem wake-up overhead alone. Use LTE-M or NB-IoT for battery-powered sensors; reserve 5G NR for mains-powered edge devices requiring high throughput (HD cameras, industrial robots, AR/VR headsets).

5G advertises 1 ms latency but this refers to the air interface latency — not end-to-end application latency. End-to-end latency from IoT device to cloud application includes: radio (1–10 ms) + RAN processing (2–5 ms) + core network (5–20 ms) + internet routing (10–50 ms) + server processing. For most IoT applications, end-to-end latency is 20–100 ms even on 5G. URLLC (<1 ms) requires edge computing co-located with the base station.

Private 5G networks require licensed spectrum; availability varies by country. In the US, CBRS (3.5 GHz) provides shared commercial spectrum for private networks. In Europe, dedicated local spectrum (3.8–4.2 GHz) is available in some countries. Deploying private 5G without verifying local spectrum licensing leads to interference with public networks and potential regulatory violations. Always check national regulator spectrum databases before designing private 5G deployments.

30.15 What’s Next

Chapter Focus Area
5G Device Categories for IoT NB-IoT, LTE-M, RedCap, and Full 5G NR selection criteria
5G Network Slicing for IoT Virtual networks, private 5G, and spectrum options
5G URLLC and 6G Vision Mission-critical IoT, power saving, and 6G timeline
Private 5G Networks Enterprise deployment models and ROI analysis