LoRaWAN vs NB-IoT vs LTE-M for Industrial IoT: 2026 Decision Guide
Last Updated: November 13, 2026
A pressure transmitter in a basement pump room and a tracker on a rail wagon can carry the same battery and the same twelve-byte payload, yet the right radio for each is different. Choosing between LoRaWAN vs NB-IoT vs LTE-M is the connectivity decision that decides whether a sealed sensor fleet lasts ten years or strands you with dead nodes, a carrier that switched off its network, or a duty-cycle wall you never modelled.
The decision got harder in 2026. AT&T has already decommissioned its US NB-IoT network and steers customers to LTE-M and 5G RedCap. European 2G and 3G shutdowns continue to push legacy telemetry onto LPWAN. LoRaWAN passed 125 million deployed end devices. Meanwhile most comparison tables still score the three on a single “range” column that hides the mechanism.
This guide compares them by mechanism: link budget, power-saving state machines, regional regulation, mobility and lifecycle risk. You leave with a decision table, an illustrative battery model you can rerun, and a list of failure modes.
What this covers: link budget and coverage, PSM and eDRX versus LoRaWAN Class A, payload and duty cycle, latency and mobility, cost structure, network sunsets and the RedCap roadmap, a decision matrix, a worked battery example, failure modes, a checklist and FAQ.
Context and Background
Low-power wide-area networks (LPWAN) exist for one corner of the design space: a few bytes, sent rarely, over kilometres, from a device that must run for years on a primary cell. Wi-Fi, Bluetooth and broadband cellular optimise for throughput and assume mains power or frequent charging. LPWAN radios invert that trade. They accept kilobit-class rates and long latencies in return for link budgets above 150 dB and sleep currents in the low microamps.
Three technologies dominate industrial LPWAN in 2026. LoRaWAN is a medium access control (MAC) and network specification stewarded by the LoRa Alliance. It runs over Semtech’s LoRa chirp spread spectrum (CSS) physical layer, and since Regional Parameters RP002-1.0.3 also over long-range frequency hopping spread spectrum (LR-FHSS). It uses unlicensed sub-GHz industrial, scientific and medical (ISM) bands. You can own the entire network, from gateway to network server, or buy from a public operator. The LoRa Alliance reported more than 125 million LoRaWAN end devices deployed globally in December 2025, with smart metering the largest single segment.
NB-IoT (Narrowband IoT, device category Cat-NB1 in 3GPP Release 13 and Cat-NB2 from Release 14) and LTE-M (LTE for Machine-Type Communication, Cat-M1 in Release 13, Cat-M2 from Release 14) are 3GPP standards operated by mobile network operators on licensed spectrum. NB-IoT occupies a single 180 kHz carrier and targets deep coverage for stationary devices. LTE-M uses a 1.4 MHz narrowband inside an LTE carrier and adds connected-mode mobility, higher throughput and optional VoLTE. Both were accepted into IMT-2020 as the massive machine-type communication (mMTC) component of 5G, so “5G IoT” in a carrier brochure often means one of these two.
In any LoRaWAN vs NB-IoT vs LTE-M evaluation, the single most important difference is ownership. LoRaWAN is infrastructure you build or choose; NB-IoT and LTE-M are services you rent, device by device, from an operator whose roadmap you do not control. That split drives capex versus opex, who holds the security keys, and, as the 2025 AT&T NB-IoT shutdown proved, who decides when your network ends. If you are new to the LoRaWAN side, our walkthrough of a self-hosted ChirpStack LoRaWAN network server with ADR, multicast and FUOTA shows what “owning the network” means in practice.
How the Three Radios Actually Differ: Mechanisms, Not Datasheets
LoRaWAN vs NB-IoT vs LTE-M comes down to four mechanisms. LoRaWAN buys range with spreading factor and pays in airtime under duty-cycle rules. NB-IoT buys depth with repetitions and pays in energy per message. LTE-M trades a few decibels of coverage for mobility, lower latency and firmware-scale throughput. Ownership and lifecycle risk sit on top of all three.

Figure 1: LoRaWAN’s private star of gateways and network server versus the operator-run path shared by NB-IoT and LTE-M.
Figure 1 shows the structural reason behind every later trade-off. A LoRaWAN end device broadcasts to whichever gateways hear it. Gateways forward packets to a network server that deduplicates, manages adaptive data rate and routes to a join server and application server. NB-IoT and LTE-M devices instead attach to a single serving cell, authenticate with a SIM or eSIM profile against the operator core, and reach your application through a packet gateway or a non-IP data delivery path. One model is uplink-by-broadcast with keys you hold; the other is a managed session with an operator in the middle.
Link budget: three different ways to buy decibels
A link budget is the total path loss a radio link tolerates, roughly transmit power minus receiver sensitivity. The three technologies reach similar numbers through different mechanisms, and each mechanism has a cost.
LoRa uses chirp spread spectrum. Each step up in spreading factor (SF7 to SF12) doubles symbol duration and gains about 2.5 dB of sensitivity. A common transceiver such as the Semtech SX1276 lists about -137 dBm sensitivity at SF12 and 125 kHz bandwidth. With the +14 dBm effective radiated power typical in the EU868 band, that yields a link budget around 151 dB. In US915, higher permitted transmit power lifts the budget a few dB further. The price of SF12 is airtime: a 25-byte physical payload takes about 61.7 ms at SF7 but about 1.48 s at SF12, a factor of 24.
NB-IoT reaches its headline 164 dB maximum coupling loss (MCL) through coverage enhancement (CE) levels. Deutsche Telekom’s NB-IoT network documentation describes a base MCL of 144 dB rising to 164 dB, with CE Level 2 using up to 128 repetitions. Repetition is coherent energy accumulation: send the same block many times, and the receiver combines them. Every repetition is more transmit time at up to 23 dBm, so a device in CE2 can spend one to two orders of magnitude more energy per message than the same device in CE0.
LTE-M targets about 156 dB MCL using CE mode B, also built on repetitions, but over a wider 1.4 MHz channel. That is roughly 8 dB less than NB-IoT on paper. In practice, 8 dB is the difference between reaching a meter cabinet in a basement and not reaching it. For street-level, rooftop or vehicle-mounted assets, LTE-M coverage is usually sufficient, and its wider channel shortens airtime per message.
The practical lesson is that the worst-placed device sets your maintenance schedule. A fleet average tells you little; the tail of devices running at SF12 or CE2 determines battery replacements. Our deeper post on LoRaWAN adaptive data rate, spreading factor and airtime capacity planning quantifies how ADR moves devices off SF12 when the link allows.
Power: a Class A receive window versus a cellular state machine
The second mechanism is how each radio sleeps and wakes. This determines battery life more than any other parameter, and it is where the technologies differ most.
A LoRaWAN Class A device has no network registration to maintain. It wakes, transmits, opens two short receive windows (RX1 one second after uplink by default, RX2 one second later), then sleeps at a few microamps. There is no attach, no paging, no keep-alive. The network cannot reach the device except in those windows. Class B adds scheduled ping slots synchronised to gateway beacons, and Class C keeps the receiver open continuously for mains-powered actuators.
Cellular devices must stay registered with the network, and the 3GPP power-saving features exist to make that cheap. Power Saving Mode (PSM) lets the device negotiate a periodic tracking area update timer (T3412 extended, up to about 413 days in the 3GPP encoding) and an active timer (T3324). After T3324 expires, the device is unreachable but stays registered, so it can wake and send without a full re-attach. Extended Discontinuous Reception (eDRX) stretches paging cycles so the device listens briefly at long intervals: up to 10,485.76 s (about 2.9 hours) for NB-IoT and 2,621.44 s (about 43.7 minutes) for LTE-M. Operators choose what values they actually grant, and Telekom, for instance, documents a T3412 range of 1 to 310 hours on its network.
The overlooked feature is Release Assistance Indication (RAI). Without it, a cellular device that has finished sending lingers in RRC connected mode until the network’s inactivity timer releases it, typically 20 to 30 seconds per Telekom’s documentation. With RAI, the device tells the network it expects no further data and is released immediately. On a fleet sending small payloads, RAI support on both module and network can halve energy per message. We cover the full state machine in cellular IoT power saving with PSM, eDRX and RAI.
Payload, duty cycle and regulation
The third mechanism is how much you may send and how often. Cellular LPWAN is limited by the operator’s tariff and your energy budget. LoRaWAN is limited by physics and by law.
LoRaWAN maximum application payloads depend on region and data rate. In EU868 the slowest data rate (DR0, SF12) allows 51 bytes and the fastest LoRa rates allow 222 bytes. In US915, the 400 ms dwell-time limit on uplinks restricts DR0 (SF10 on 125 kHz) to 11 bytes. These figures come from the LoRa Alliance Regional Parameters, the RP002 document series; the current published revision is RP002-1.0.4, released in September 2023, and you should confirm which revision your network server and device stack implement.
Duty cycle is the EU-specific constraint. Under ETSI EN 300 220 rules as encoded in the regional parameters, most EU868 sub-bands limit each device to 1% transmit time, with some sub-bands at 0.1% and one at 10%. At 1%, a device may transmit 36 s per hour. Public networks add fair-use policies on top; The Things Network, for example, allows 30 s of uplink airtime per device per day and 10 downlinks. The gateway is also bound by duty cycle, which makes downlinks and confirmed uplinks a scarce shared resource.
NB-IoT Cat-NB1 peaks in the tens of kbit/s, and Cat-NB2 raises that to roughly 100 to 160 kbit/s depending on direction and configuration. LTE-M Cat-M1 peaks around 1 Mbit/s, with real half-duplex throughput a few hundred kbit/s. None of the cellular options has a regulatory airtime ceiling, which is why firmware updates are routine on LTE-M and painful on LoRaWAN.
Latency and mobility
The fourth mechanism is how quickly a message moves and whether the device can move while sending it. LoRaWAN Class A uplink latency is mostly airtime, from tens of milliseconds to a second or two. Downlink latency is unbounded, because the server must wait for the next uplink. Mobility works only in the broadcast sense: a moving device is heard by whichever gateway is nearby, but ADR misbehaves when link conditions change quickly, so trackers usually run fixed data rates.
NB-IoT was designed for latency under 10 seconds for an exception report, and real numbers range from about 1.5 s in good coverage to well over 10 s in CE2. Release 13 NB-IoT has no connected-mode handover; a moving device reselects cells in idle mode, and a session in progress can drop. LTE-M supports connected-mode handover like normal LTE, latencies in the 50 to 200 ms range in good coverage, and VoLTE on supporting networks. That makes it the default for asset tracking, alarm panels and anything that moves across cells.
Decision Matrix, Battery Math and the Network Roadmap
The mechanisms above become a decision when you put numbers against a specific device class. This section gives the decision table, a decision flow, an illustrative battery model, the cost structure, and the lifecycle risk that most comparisons skip.
The decision table
The table uses published standards values where they exist. Where a value depends on operator configuration or deployment, it says so rather than inventing a figure.
| Criterion | LoRaWAN | NB-IoT | LTE-M |
|---|---|---|---|
| Spectrum | Unlicensed sub-GHz ISM, e.g. EU868, US915, AS923, IN865 | Licensed LTE bands, operator-run | Licensed LTE bands, operator-run |
| Link budget / MCL | About 151 dB at SF12 in EU868; more in US915 | Up to 164 dB with CE Level 2 | About 156 dB with CE mode B |
| Deep-indoor reach | Good; gateway placement fixable by you | Best of the three | Moderate |
| Peak data rate | About 0.25 to 11 kbit/s LoRa in EU868; about 12.5 kbit/s uplink at SF8 on US915 500 kHz | Tens of kbit/s on Cat-NB1; roughly 100 to 160 kbit/s on Cat-NB2 | About 1 Mbit/s Cat-M1 peak; a few hundred kbit/s typical |
| Max payload | 11 to 222 bytes, region and data-rate dependent | IP or non-IP packets, operator MTU-limited | IP packets, MTU-limited |
| Airtime limit | Regulatory duty cycle in EU; dwell time in US; fair-use on public networks | None regulatory; tariff-limited | None regulatory; tariff-limited |
| Power saving | Class A sleep; no registration overhead | PSM, eDRX up to about 2.9 h, RAI | PSM, eDRX up to about 43.7 min, RAI |
| Uplink latency | Tens of ms to about 2 s airtime | About 1.5 s to 10 s or more | About 50 to 200 ms typical |
| Downlink | Only after an uplink in Class A; gateway duty-cycle bound | Paging via eDRX or after PSM wake | Paging via eDRX or after PSM wake |
| Mobility | Broadcast reception only; no handover | Idle-mode reselection only in Rel-13 | Full connected-mode handover |
| Voice | No | No | VoLTE on supporting networks |
| FUOTA | Possible with multicast and fragmentation; slow | Feasible for small images | Routine |
| Cost model | Gateway capex plus network server; no per-device fee on private networks | Module plus recurring data plan | Module plus recurring data plan, slightly higher module cost |
| Lifecycle risk | You control it; regional parameter revisions | Operator-dependent; AT&T US shut down NB-IoT in 2025 | Operator-dependent; strongest carrier support in North America |
Read the table row by row against your device class rather than looking for a winner. A water meter in a basement cares about the MCL, power and lifecycle rows. A trailer tracker cares about mobility, latency and roaming. A tank-level sensor on a private refinery site cares about cost model and control.

Figure 2: A selection flow that routes device classes by mobility, coverage depth, site ownership, data volume and carrier support.
Figure 2 encodes the order in which constraints usually bite. Mobility goes first, because it rules out options outright: a device that moves across cells mid-session needs LTE-M. Firmware and data volume go next, since a 400 kB image over LoRaWAN takes hours of airtime under duty cycle. Then comes site control: if you own the site and can place gateways, LoRaWAN avoids per-device fees. Finally coverage depth and carrier support decide between the cellular pair. If NB-IoT is not commercially supported by an operator in every target country, it is not an option regardless of its MCL.
Worked battery example (illustrative)
The following model is illustrative. It uses round-number assumptions rather than measured values from a specific module, and real results vary with module, firmware, network configuration and temperature. Its purpose is to show which terms dominate, not to predict your fleet.
Assumptions: a 3.6 V AA lithium thionyl chloride cell rated 2.6 Ah, with 2,080 mAh treated as usable after derating. Each message carries a 12-byte application payload. LoRaWAN costs about 3.3 mA·s per message at SF7 (61.7 ms at 40 mA transmit plus receive windows and MCU time) and about 62.5 mA·s at SF12. Sleep current is 2 µA. NB-IoT and LTE-M use 3 µA PSM floor current, about 100 mA·s per message for NB-IoT in CE0 with RAI, 250 mA·s without RAI, about 1,800 mA·s in CE2, and about 60 mA·s for LTE-M in good coverage with RAI.
| Scenario (illustrative) | Reporting | Charge per day | Capacity-limited life |
|---|---|---|---|
| LoRaWAN, SF7 | Every 15 min | 0.14 mAh | About 42 years; cell shelf life dominates |
| LoRaWAN, SF12 | Every 15 min | 1.7 mAh | About 3.3 years |
| NB-IoT, CE0, RAI | Every 15 min | 2.7 mAh | About 2.1 years |
| NB-IoT, CE0, no RAI | Every 15 min | 6.7 mAh | About 0.8 years |
| NB-IoT, CE0, RAI, batched | Hourly, 4 readings | 0.74 mAh | About 7.7 years |
| NB-IoT, CE2, batched | Hourly, 4 readings | 12 mAh | About 0.5 years |
| LTE-M, good coverage, RAI | Every 15 min | 1.7 mAh | About 3.4 years |
| LTE-M, good coverage, RAI, batched | Hourly | 0.47 mAh | About 12 years; cell shelf life dominates |
Three conclusions survive any reasonable change to the assumptions. First, message count matters more than technology choice for cellular: batching four readings into one hourly report moves NB-IoT from about two years to about eight. Second, the coverage tail is brutal. The same NB-IoT node in CE2 lasts a fifteenth as long as in CE0, which is why coverage surveys at the actual mounting point matter. Third, LoRaWAN at SF7 is effectively bounded by cell self-discharge and passivation, not energy, while LoRaWAN at SF12 behaves much like cellular. Even at SF12, 96 messages a day use about 142 s of airtime, inside the EU 1% duty cycle but nearly five times the TTN fair-use allowance.
A further caveat is peak current. A bobbin-type lithium thionyl chloride cell delivers low continuous current well, but a cellular module transmitting at 23 dBm can draw several hundred milliamps in bursts. Without a hybrid layer capacitor or supercapacitor buffer, voltage sags under those pulses and the module browns out long before rated capacity is consumed. LoRa transmit peaks of around 40 mA are much gentler.

Figure 3: Per-message energy sequence for a LoRaWAN Class A uplink versus a cellular PSM wake with and without Release Assistance Indication.
Figure 3 explains the gap. The LoRaWAN device transmits and listens twice, then sleeps. The cellular device wakes from PSM, performs random access, establishes an RRC connection, sends, and then either releases immediately with RAI or waits out the inactivity timer. The radio bursts are short; the overhead around them is what drains batteries.
Cost structure
Cost comparisons that stop at module price mislead. Module prices for all three have converged into the low tens of dollars at volume, and they differ by less than the lifetime connectivity bill. The dominant terms differ by technology.
For LoRaWAN on a private network, the dominant terms are gateways, backhaul, the network server, and the people who run them. Industrial gateways cost a few hundred to a couple of thousand dollars each, and a single plant site often needs only a handful. The marginal cost of the ten-thousandth sensor on that site is close to zero. For public LoRaWAN operators, a per-device subscription replaces the capex.
For NB-IoT and LTE-M, the dominant term is the recurring data plan, multiplied by device count and service years. IoT plans priced per device per month or per megabyte pool look small individually and large over ten years. Roaming adds another layer, since NB-IoT roaming agreements remain thinner than LTE-M ones. The GSMA’s mobile IoT deployment map is the practical starting point for checking where each is commercially live. The crossover point depends on site density: dense single-site fleets favour LoRaWAN, while devices scattered across a country favour cellular, because building gateway coverage everywhere costs more than renting it.
Network sunsets and the 3GPP roadmap
Connectivity is the layer you cannot easily swap once sealed devices are in the field, so lifecycle risk deserves its own analysis. Three moves define the 2026 landscape.
First, 2G and 3G shutdowns continue. Most US 3G networks closed in 2022, and many European operators have closed 3G and scheduled 2G. Deutsche Telekom has said it will shut down 2G in Germany in 2028, and operator trackers list 2G dates running to 2030 in Spain. Legacy GSM telemetry such as alarm diallers and older smart meters must migrate, and LTE-M and NB-IoT are the usual destinations because they share LTE infrastructure that will outlive 2G.
Second, NB-IoT support is uneven. In November 2024, AT&T stopped selling NB-IoT plans and announced it would decommission the network, as early as Q1 2025, migrating customers to LTE-M, according to RCR Wireless. In July 2025, AT&T launched nationwide 5G RedCap, positioned partly as a successor for mid-tier IoT. NB-IoT remains strong in China and much of Europe, but a device designed only for NB-IoT now carries regional risk. Multi-mode LTE-M plus NB-IoT modules, which cost little more, are the default hedge.
Third, 5G RedCap and eRedCap fill the space above LPWAN, not inside it. RedCap (3GPP Release 17) cuts NR device complexity to up to 20 MHz bandwidth in FR1 and one or two receive antennas, with peak rates in the low hundreds of Mbit/s. Enhanced RedCap (eRedCap, Release 18) narrows the baseband data channel to 5 MHz with a single antenna and peak rates around 10 Mbit/s. That makes eRedCap a natural successor to LTE Cat-1 and Cat-1 bis, and over time a candidate for the upper end of LTE-M use cases. It does not replace NB-IoT or LTE-M for deep-coverage, decade-long battery devices today. 3GPP continues to enhance LTE-M and NB-IoT, including non-terrestrial network (NTN) support from Release 17, and both are expected to run on LTE spectrum for many years. Our analyses of 5G RedCap for industrial IoT and Release 20 5G-Advanced cover that roadmap.

Figure 4: Where legacy 2G and 3G telemetry migrates, and how LTE-M, NB-IoT, RedCap, eRedCap and LoRaWAN divide the capability range.
Figure 4 shows why “future-proof” is the wrong question. Every option has a lifecycle; the useful question is who controls it and how much warning you get. With LoRaWAN on a private network, you control it. With cellular, you depend on the operator’s spectrum refarming and business case, so contracts should include notice periods and the hardware should support at least two technologies.
Trade-offs, Gotchas, and What Goes Wrong
The LoRaWAN vs NB-IoT vs LTE-M failure modes below come from how the mechanisms interact with real sites. Most of them surface twelve to thirty-six months into a rollout, after the devices are sealed and the procurement decision feels settled.
The SF12 trap on LoRaWAN. Devices that join at SF12 because of a poor first link often stay there if ADR is disabled or the network server is misconfigured. They consume 24 times the airtime of SF7 devices, drain batteries like cellular nodes, and push the gateway towards collisions. ALOHA-style random access means collision probability rises with total airtime, so a few hundred SF12 devices can degrade a gateway serving thousands. Monitor the SF distribution, not just packet delivery ratio.
Downlink starvation. Under EU duty cycle, a gateway that sends many downlinks, such as join accepts, confirmed-uplink acknowledgements and MAC commands, burns its own 1% or 10% budget and stops answering. Confirmed uplinks across a large fleet are the usual cause. Use unconfirmed uplinks with application-level sequence checks wherever loss is tolerable.
Regional parameter mismatch. A device certified for EU868 shipped to India needs IN865, and one shipped to Japan needs AS923 with listen-before-talk. Mismatched channel plans, data-rate tables or dwell-time settings produce devices that join in the lab and fail in the field. Pin the regional parameter revision and MAC version in your device specification and verify that the network server supports both.
Coverage maps that lie about indoor depth. Operator maps show outdoor coverage. A meter cabinet behind concrete may sit 20 dB deeper, which can push NB-IoT into CE2 and LTE-M out of coverage entirely. Survey at the mounting position with the actual antenna and enclosure. Log reported CE level or RSRP and SINR during commissioning so you can find the tail later.
PSM values the network ignores. A device can request a 24-hour T3412 and a two-second T3324, but the network decides what to grant. Firmware that assumes the requested values, rather than reading the granted ones, either wakes too often or misses downlinks. Read the network-assigned timers after every attach and log them.
Synchronised wake storms. Thousands of cellular devices with identical firmware may report on the hour, after a power cut, or after a network outage. They hit the same cell simultaneously, fail random access, retry, and drain batteries. Add jitter to schedules and exponential backoff with randomness to retries. The same applies to LoRaWAN rejoins after a network server restart.
Battery chemistry mismatch. Lithium thionyl chloride cells passivate during long storage and then deliver poor peak current at first use. Cellular modules pulling several hundred milliamps can trigger brownout resets in a loop. Use a hybrid capacitor or supercapacitor buffer, and test at the coldest rated temperature, where internal resistance rises.
Single-technology lock-in. A product designed only for NB-IoT in the US had to be replaced or redesigned after AT&T’s shutdown. A product designed only for 2G faces the same in Europe by 2028 to 2030. Choose dual-mode LTE-M plus NB-IoT modules for cellular, and keep a firmware path to switch networks remotely, including eSIM profile management under GSMA SGP.32 where your supply chain supports it.
FUOTA optimism on LoRaWAN. Firmware update over the air works on LoRaWAN through multicast and fragmentation, but a 200 kB image at low data rates takes hours and consumes much of the gateway’s duty-cycle budget. Plan delta updates, schedule campaigns, and size flash for a dual-bank image. Our LoRaWAN FUOTA guide walks through the mechanics.
Practical Recommendations
Settle LoRaWAN vs NB-IoT vs LTE-M per device class, not from a technology preference. Most industrial programmes need more than one radio, and forcing a single choice across every device class is how expensive mistakes happen. A practical split is LoRaWAN for dense, fixed sensors on sites you control; NB-IoT for deep-indoor fixed assets where a local operator offers solid support; and LTE-M for anything mobile, anything that needs fast downlinks, and anything that needs regular firmware updates.
Second, model energy per message at your worst mounting position, not your average. Run the illustrative battery model above with your module’s measured currents and your operator’s granted timers. If the tail devices land in CE2 or SF12, fix placement, antennas or reporting frequency before volume production.
Third, treat lifecycle as a contract term. For cellular, ask operators for written support commitments and notice periods for each technology in each country. For LoRaWAN, decide whether you will run your own network server or rely on a public operator, and plan the operations staffing either way. Edge buffering also helps: an MQTT store-and-forward edge gateway keeps data intact through backhaul outages on private LoRaWAN sites.
Checklist before you commit:
- Classify devices by mobility, payload, report rate, downlink need and firmware size.
- Survey coverage at real mounting points and log SF, CE level, RSRP and SINR.
- Confirm NB-IoT and LTE-M commercial support and roaming in every target country.
- Pin LoRaWAN MAC version and regional parameter revision per region.
- Model battery life with measured currents, granted PSM and eDRX values, and RAI.
- Specify a capacitor buffer for cellular peak current and test at low temperature.
- Prefer dual-mode LTE-M plus NB-IoT modules and remote profile management.
- Add jitter and randomised backoff to every reporting and retry schedule.
- Put technology sunset notice periods into connectivity contracts.
Frequently Asked Questions
Which has the longest range: LoRaWAN, NB-IoT or LTE-M?
It depends on what “range” means. In open terrain, a LoRaWAN gateway on a mast can reach devices many kilometres away because its link budget at SF12 is around 151 dB in EU868, and you choose where gateways go. For deep-indoor penetration from existing towers, NB-IoT leads with up to 164 dB maximum coupling loss using coverage enhancement. LTE-M sits around 156 dB. In practice, coverage is set by gateway or tower placement, building losses and the coverage tail, so a site survey beats any headline number.
Is NB-IoT being shut down?
Not globally. AT&T stopped selling NB-IoT and announced its US network would be decommissioned as early as the first quarter of 2025, moving customers to LTE-M and later offering 5G RedCap. Many operators in Europe and China continue to run NB-IoT, and 3GPP still maintains the standard. The lesson is regional risk: check commercial support in each target country, prefer dual-mode LTE-M and NB-IoT modules, and ask operators for written notice periods. NB-IoT is not obsolete, but it is no longer a safe single-technology bet everywhere.
Does 5G RedCap replace LTE-M?
Not for most low-power use cases today. RedCap (Release 17) targets mid-tier devices such as wearables, video sensors and industrial gateways, with peak rates in the hundreds of Mbit/s. eRedCap (Release 18) narrows that to about 10 Mbit/s on a 5 MHz data channel and is positioned as a successor to LTE Cat-1 and Cat-1 bis. LTE-M remains cheaper, lower power and better in coverage for small-payload, battery-powered devices. Over a longer horizon, as LTE spectrum is refarmed, eRedCap may absorb the upper end of LTE-M use cases.
How long does a battery last on NB-IoT or LTE-M?
Multi-year life is achievable, but message count, coverage level and power-saving configuration dominate. In our illustrative model with a 2.6 Ah AA cell, NB-IoT reporting every 15 minutes in good coverage lasted about two years, while hourly batched reports lasted nearly eight. The same device in CE2 coverage lasted months. Enabling PSM, eDRX where needed and especially Release Assistance Indication matters as much as the technology choice. Always validate with measured currents on your module and the timers your operator actually grants.
What is the LoRaWAN duty cycle limit in Europe?
In the EU868 band, regional rules limit each transmitter’s share of time on air per sub-band, commonly 1%, with some sub-bands at 0.1% and one at 10% at higher power. At 1%, a device may transmit 36 seconds per hour. Gateways are bound by the same rules, which limits downlinks. Public networks often add fair-use policies; The Things Network allows 30 seconds of uplink airtime per device per day and 10 downlinks. Other regions use different constraints, such as the 400 ms dwell time in US915.
Can I use LoRaWAN and cellular together?
Yes, and many industrial fleets do. A common pattern uses LoRaWAN for dense fixed sensors on a site, with gateways backhauled over fibre, Ethernet or LTE. Mobile assets and remote single sensors use LTE-M or NB-IoT. Both feed the same MQTT broker or unified namespace, so applications do not care which radio carried a reading. Some devices also combine radios, using LoRaWAN on site and LTE-M as a fallback, though that adds cost, certification work and firmware complexity.
Further Reading
- Cellular IoT power saving with PSM, eDRX and RAI on LTE-M and NB-IoT
- LoRaWAN adaptive data rate, spreading factor and duty-cycle capacity planning
- ChirpStack LoRaWAN network server architecture for self-hosted networks
- 5G RedCap for industrial IoT: Release 17 and 18 architecture
- Satellite IoT: NB-NTN vs LoRa satellite direct-to-device selection
- Wi-Fi HaLow vs LoRaWAN vs LTE-M long-range IoT selection guide
- LoRa Alliance RP002-1.0.4 Regional Parameters
- AT&T 5G RedCap launch for mid-tier IoT, RCR Wireless
By Riju — about

Pingback: Ambient IoT: 3GPP Rel-19 vs Rel-20 (2026)
Pingback: CoAP Protocol Deep Dive: Constrained Application Protocol for Low-Power IoT in 2026 - IoT Digital Twin PLM
Pingback: Satellite IoT: NB-IoT NTN vs LoRa Satellite vs Direct-to-Dev
Pingback: IoT Telemetry Compression: Zstandard vs LZ4 vs Snappy vs Gor