Vai al contenuto principale

Cellular IoT Connectivity: The Complete Guide to NB-IoT, LTE-M, RedCap and eSIM

Cellular IoT Connectivity: The Complete Guide to NB-IoT, LTE-M, RedCap and eSIM

Cellular IoT connectivity is the use of licensed mobile-network technology — rather than Wi-Fi or short-range radio — to connect Internet-of-Things devices such as sensors, meters, trackers, and machines. It ranges from ultra-low-power standards built for tiny battery devices (NB-IoT and LTE-M) through mid-tier 5G RedCap to full broadband cellular, all managed at scale with eSIM/eUICC. This guide explains the LPWA standards, where RedCap fits, the IoT eSIM standard SGP.32, and when to deploy a private cellular network — the building blocks of any serious enterprise IoT strategy.

TL;DR — key takeaways

  • NB-IoT = lowest power, deepest coverage, lowest data rate, static devices. LTE-M = higher data, mobility, voice.
  • Both are 3GPP LPWA standards from Release 13 (2016); they coexist on most operator networks.
  • RedCap (Release 17, 2022) is the 5G-native mid-tier between LPWA and full 5G.
  • SGP.32 (2023) is the IoT eSIM standard — eIM + IPA for fleet-scale remote provisioning.
  • Private cellular networks (LTE/5G, licensed or shared spectrum) serve factories, ports, and campuses where Wi-Fi falls short.

What is cellular IoT connectivity?

Cellular IoT connectivity uses licensed mobile-network technology to connect IoT devices, in contrast to Wi-Fi, Bluetooth, or unlicensed LPWAN like LoRa. It spans a spectrum of capability: low-power wide-area (LPWA) standards — NB-IoT and LTE-M — built for tiny, battery-powered devices that send small amounts of data; the mid-tier 5G RedCap class; and full broadband cellular for high-bandwidth devices like connected cameras and gateways. The advantages of going cellular are licensed-spectrum reliability, near-global reach through operator roaming, carrier-grade security, and managed connectivity at scale via eSIM/eUICC. Because IoT devices ride the same networks as phones, they inherit mature coverage, standards-based interoperability, and a deep ecosystem of certified modules and connectivity-management platforms — making cellular the default for wide-area, mobile, or mission-critical IoT.

NB-IoT vs LTE-M: choosing an LPWA standard

NB-IoT and LTE-M are the two principal 3GPP low-power wide-area standards, both introduced in Release 13 (2016). NB-IoT (Narrowband IoT) optimises for the lowest power consumption, the deepest indoor and underground signal penetration, and the lowest module cost, at very low data rates and with no native mobility or voice — it is ideal for static devices such as smart utility meters, parking and environmental sensors, and agricultural monitors that report occasionally and must run for years on a battery. LTE-M (also called Cat-M1) supports higher data rates, lower latency, full mobility with cell handover, and voice (VoLTE), suiting moving assets, wearables, alarm systems, and connected-health devices that need responsiveness. Most operators deploy both; the decision turns on whether the device moves, how much data it sends, and how aggressively it must conserve power.

How the cellular IoT tiers compare

Technology3GPP introData rateMobilityPowerBest for
NB-IoTRel-13 (2016)Very low (tens–hundreds kbps)Limited / noneLowestStatic meters, deep-indoor sensors
LTE-MRel-13 (2016)Low (up to ~1 Mbps)Full handover, voiceLowTrackers, wearables, alarms
RedCap (5G)Rel-17 (2022)Mid (tens of Mbps)FullMediumIndustrial sensors, wearables, surveillance
Full 5G NRRel-15+ (2018+)High (hundreds of Mbps+)FullHighestGateways, video, broadband devices

Where does RedCap fit in cellular IoT?

RedCap (Reduced Capability) is a 5G NR device class introduced in 3GPP Release 17 (2022) that fills the gap between low-power LPWA and full 5G broadband. It deliberately reduces the bandwidth, antenna count, and processing complexity of full 5G to lower device cost, power draw, and size, while still delivering far higher throughput and lower latency than NB-IoT or LTE-M. That makes RedCap the natural fit for the large middle band of IoT — industrial sensors, video surveillance, wearables, and connected industrial equipment — that needs more than a trickle sensor but less than a smartphone, and lets these devices live natively on a 5G standalone network instead of falling back to 4G LPWA. Release 18 extends the family with eRedCap (enhanced RedCap), a still lower-capability variant. As operators migrate to 5G standalone, RedCap becomes the strategic mid-tier IoT class.

IoT eSIM: SGP.32, eIM and the IPA

For IoT at scale, the embedded, reprogrammable SIM (eUICC) is essential because devices are frequently sealed, remote, or shipped worldwide, making a physical SIM swap impractical. GSMA SGP.32, published in 2023, is the IoT-specific remote SIM provisioning standard that replaces the older SGP.02 M2M architecture. It introduces the eIM (eSIM IoT Manager), a platform-side component that issues signed profile-management commands to a fleet, and the IPA (IoT Profile Assistant) on the device that executes them — removing both the consumer QR-scan flow and the legacy SM-SR push model, neither of which suited headless or intermittently connected devices. With SGP.32 an enterprise can manufacture a device once, ship it anywhere, assign the best local operator after deployment, and switch carriers over the air years later without a truck roll. For greenfield IoT in 2026, SGP.32 is the default where eUICC, operator, and platform support align.

When should an enterprise deploy a private cellular network?

A private cellular network is a dedicated 4G LTE or 5G network for one organisation’s site — a factory, port, mine, airport, or warehouse — built on licensed, shared (e.g. CBRS in the US), or local spectrum. It delivers carrier-grade coverage, capacity, and reliability under the enterprise’s own control, with deterministic performance, strong security and data sovereignty (traffic can stay on-premises), and the wide-area mobility that Wi-Fi struggles to maintain across large industrial spaces. Enterprises choose private networks for mission-critical automation, autonomous vehicles and robots, dense sensor and camera deployments, and any environment where Wi-Fi coverage or reliability is inadequate. 5G standalone with network slicing and edge computing makes private networks especially compelling for low-latency industrial control and Industry 4.0, where a guaranteed, isolated slice of capacity and on-site processing are prerequisites rather than nice-to-haves.

Building an enterprise IoT connectivity strategy

  • Match the radio to the device: NB-IoT for static low-data sensors, LTE-M for mobile/responsive assets, RedCap for mid-tier 5G, full 5G for broadband devices.
  • Standardise on eUICC + SGP.32 so you can provision once and switch operators over the air at fleet scale.
  • Plan for global roaming or multi-IMSI/eUICC profiles where devices cross borders.
  • Consider a private network for high-density, low-latency, or data-sovereign industrial sites.
  • Use a connectivity-management platform to monitor, control, and bill the fleet centrally.

Related on DROAM

Frequently asked questions

What is cellular IoT connectivity?

Cellular IoT connectivity is the use of licensed mobile-network technology to connect Internet-of-Things devices — sensors, meters, trackers, and machines — rather than Wi-Fi or short-range radio. It spans low-power wide-area (LPWA) standards built for tiny, battery-powered devices (NB-IoT and LTE-M, both 3GPP standards), mid-tier options like RedCap on 5G, and full broadband cellular for high-bandwidth devices. The appeal is licensed-spectrum reliability, near-global coverage through operator roaming, carrier-grade security, and managed connectivity at scale via eSIM/eUICC. Because it rides the same networks as phones, cellular IoT inherits operator coverage, standards-based interoperability, and a mature ecosystem of modules and platforms — making it the default choice for wide-area, mobile, or mission-critical IoT deployments.

What is the difference between NB-IoT and LTE-M?

NB-IoT and LTE-M are the two main 3GPP low-power wide-area cellular standards, both introduced in Release 13 (2016) and refined since. NB-IoT (Narrowband IoT) is optimised for the lowest power, deepest indoor/underground penetration, and lowest cost, at very low data rates and with no native mobility or voice — ideal for static sensors like smart meters, parking sensors, and environmental monitors. LTE-M (LTE-Machine, also called Cat-M1) supports higher data rates, lower latency, full mobility (handover between cells), and voice over LTE, making it suited to moving assets, wearables, and applications needing more responsiveness — asset trackers, alarm panels, and connected health devices. Many operators run both; the right choice depends on whether the device moves, how much data it sends, and how aggressively it must conserve battery.

What is RedCap and where does it fit?

RedCap (Reduced Capability) is a 5G NR device class introduced in 3GPP Release 17 (2022) that fills the gap between low-power LPWA (NB-IoT/LTE-M) and full 5G broadband. It strips down the complexity, bandwidth, and antenna requirements of full 5G to cut device cost, power, and size, while still offering meaningfully higher throughput and lower latency than NB-IoT/LTE-M — targeting mid-tier use cases such as industrial sensors, wearables, video surveillance, and connected industrial equipment. RedCap lets these mid-tier devices live natively on a 5G standalone network rather than relying on 4G LPWA. Release 18 adds eRedCap (enhanced RedCap) with even lower-capability variants. RedCap is significant because it gives operators a 5G-native answer for the large middle band of IoT devices that need more than a sensor but less than a smartphone.

What is SGP.32 and why does it matter for IoT eSIM?

GSMA SGP.32 is the IoT-specific eSIM (remote SIM provisioning) standard published in 2023, designed to replace the older SGP.02 M2M architecture. It introduces two new actors: the eIM (eSIM IoT Manager), a platform-side component that issues signed profile-management commands across a device fleet, and the IPA (IoT Profile Assistant), which runs on the device and executes those commands against its eUICC. SGP.32 removes the consumer-style QR-scan requirement and the legacy SM-SR push model, both of which were poorly suited to headless, intermittently connected, or NAT/firewalled IoT devices. This lets enterprises provision, switch, and manage operator profiles remotely at fleet scale — changing carriers over the air to optimise coverage or cost without touching the hardware. For greenfield IoT in 2026, SGP.32 is the strategic default where the eUICC vendor, operator, and platform support it.

What is a private cellular network and when should an enterprise use one?

A private cellular network is a dedicated 4G LTE or 5G network deployed for a single organisation’s site or campus — a factory, port, mine, airport, or warehouse — using either licensed, shared (e.g. CBRS in the US), or local/unlicensed spectrum. It gives the enterprise carrier-grade coverage, capacity, and reliability under its own control, with deterministic performance, strong security and data sovereignty (traffic can stay on-premises), and the mobility and range that Wi-Fi struggles to deliver across large industrial spaces. Enterprises choose private networks for mission-critical automation, AGV/robot control, high-density sensor deployments, and environments where Wi-Fi reliability or coverage is inadequate. 5G standalone with network slicing and edge computing makes private networks especially powerful for low-latency industrial control and Industry 4.0 use cases.

Why use eSIM/eUICC for IoT instead of a physical SIM?

For IoT at scale, the eUICC (embedded, reprogrammable SIM) solves problems a plastic SIM cannot. Devices are often sealed, deployed in inaccessible locations, or shipped worldwide, so swapping a physical SIM to change operator is impractical or impossible. An eUICC lets you provision and switch operator profiles remotely over the air — manufacture a device once, ship it anywhere, and assign the best local operator after deployment, or change carrier years later to chase better coverage or pricing without a truck roll. The embedded form factor is also more robust against vibration, temperature, and tampering than a removable card. Under the IoT standard SGP.32, the eIM/IPA architecture makes fleet-scale remote management practical, which is why eUICC plus SGP.32 is becoming the default connectivity approach for serious enterprise IoT deployments.