NB-IoT vs LPWAN: choosing the right technology
NB-IoT vs LPWAN: choosing the right technology
Choosing the right low-power wide-area network is one of the highest-leverage decisions in an IoT project. It shapes battery life, coverage, payload capacity, security model and total cost of ownership for years. This guide compares the four main LPWAN options: NB-IoT, LTE-M, LoRaWAN and Sigfox, and gives a clear decision framework for picking among them.
The LPWAN landscape
LPWAN technologies divide along two axes: licensed cellular versus unlicensed sub-GHz, and standardized global protocols versus proprietary or alliance-driven ones. The four options below cover the great majority of LPWAN deployments today:
- NB-IoT (3GPP): licensed cellular, narrowband, optimized for low-rate, deep-indoor, massive-density use cases.
- LTE-M / Cat-M1 (3GPP): licensed cellular, broader bandwidth than NB-IoT, supports voice and mobility, higher data rates.
- LoRaWAN (LoRa Alliance): unlicensed sub-GHz, public or private gateways, popular for private and campus deployments.
- Sigfox (Sigfox / UnaBiz): unlicensed sub-GHz, operator-managed, ultra-narrowband, very small payloads.
Side-by-side comparison
| NB-IoT | LTE-M | LoRaWAN | Sigfox |
|---|---|---|---|---|
| Standardisation | 3GPP global | 3GPP global | LoRa Alliance | Proprietary (UnaBiz) |
| Spectrum | Licensed cellular | Licensed cellular | Unlicensed sub-GHz ISM | Unlicensed sub-GHz ISM |
| Typical peak data rate | ~127 kbps DL / ~159 kbps UL (NB2) | ~588 kbps DL (HD-FDD) / ~1 Mbps UL (FD-FDD) | 0.3 to 50 kbps | 100 bps UL (EU) / 600 bps DL |
| Typical payload | ~1,600 B per message | Variable, larger | Up to ~242 B (region-dependent) | 12 B UL / 8 B DL |
| Bidirectional | Yes (asymmetric) | Yes, full duplex | Yes (Class A/B/C) | Limited |
| Mobility | Limited (handover not native) | Full mobility | Limited | Limited |
| Voice support | No | Yes (VoLTE) | No | No |
| Battery life | 10+ years (PSM/eDRX | 5 to 10+ years | 10+ years (Class A) | 10+ years |
| Network model | Public cellular | Public cellular | Public, private or hybrid | Operator-only |
| Security | Cellular grade, SIM-authenticated | Cellular grade, SIM-authenticated | AES-128, key-management dependent | Lightweight, vendor-managed |
| Best fit | Static, low-rate, deep-indoor | Mobile, voice, higher rate | Private campus, small fleets | Ultralow payload alerts |
Maximum frame size, confirmed on the ST87M01
This payload figure matches the ST87M01 in practice: reception is limited to one IP frame at a time, so 1,600 bytes. If there is more data to receive, the modem signals that more is waiting.
NB-IoT vs Sigfox
Sigfox occupies a narrow niche of ultralow-payload, alert-style applications. The decision is usually clear:
- Choose NB-IoT when: you need any meaningful payload size, useful downlink, or operator-grade SLAs.
- Choose Sigfox when: your application genuinely fits within 12 bytes per message, your target country has Sigfox coverage, and the operator's commercial terms suit your TCO model.
NB-IoT vs LTE-M
This is the most subtle comparison, because both are 3GPP cellular standards and they share much of the same network and certification ecosystem.
- Choose NB-IoT when: the device is largely static (meters, sensors, fixed assets); deep-indoor coverage matters; payloads are small and infrequent; battery life and module cost are paramount.
- Choose LTE-M when: the device moves significantly during a session (handover required); voice or higher data rates are needed; the application benefits from full duplex operation.
Many product portfolios include both, with NB-IoT for static use cases (smart meters, smart-city sensors) and LTE-M for mobile and voice-capable use cases. ST's NB-IoT portfolio focuses specifically on the static, low-rate, deep-indoor profile where NB-IoT is the unambiguous best fit.
A decision framework in five questions
- Is the device static or mobile?: Mobile devices with frequent handover lean LTE-M. Static or slow-moving devices favor NB-IoT or LoRaWAN.
- What is the payload profile?: Tens of bytes per message: any LPWAN works. Hundreds of bytes or kilobytes: NB-IoT or LTE-M.
- Where does the device live?: Deep-indoor, basement, equipment-room: NB-IoT. Outdoor and surface-level: any LPWAN.
- Public network or private gateway?: Public scale, no infrastructure: cellular (NB-IoT or LTE-M). Private campus you control: LoRaWAN is a strong option.
- Regulated or critical-infrastructure deployment?: Cellular standards (NB-IoT, LTE-M) align most cleanly with regulated SLAs, RED-DA cybersecurity requirements and operator-grade quality of service.
Where the ST87M01 fits
Where the ST87M01 fits
The ST87M01 is engineered specifically for the NB-IoT design point: static or slow-moving devices, small payloads, deep-indoor coverage, multi-year battery life on a single small cell. It does not attempt to be an LTE-M module or a multi-mode cellular platform; it does the NB-IoT job well, in the smallest footprint on the market, with the longevity and supply-chain assurance industrial and utility buyers now require.
Take the next step
See NB-IoT in your application
- Asset tracking and smart labels with NB-IoT: applied to logistics and tracking, including positioning.
Evaluate the technology
- Smart cities whitepaper: system-level NB-IoT architecture and TCO analysis.
- ST87M01 product page: datasheet, certifications, ordering.