LoRaWAN: When You Own the Network

LoRaWAN runs in the unlicensed sub-GHz ISM bands. Anyone can deploy a gateway, and the protocol is designed for years of battery life with reporting cadences from once-a-day to once-per-15-minutes. The economics work especially well when you own the deployment site.

LoRaWAN wins when:

• The assets stay on a campus, port, factory, or warehouse you control. Two to ten gateways cover the whole site for a one-time hardware cost
• You want the connectivity OPEX to be near zero — your gateways, your network server, your bill
• Reporting cadence is hourly or daily; sub-minute updates are a poor fit
• Battery target is 7-10 years on a coin or AA-equivalent cell

It struggles when assets travel across uncontrolled territory. Public LoRaWAN networks (The Things Network, Helium, Senet) help, but coverage outside dense urban areas is uneven, and your SLA is whoever volunteered the gateway.

NB-IoT: The Workhorse for Wide-Area Tracking

NB-IoT (3GPP Release 13+) is the radio that has won most large-scale wide-area asset deployments since 2022. It runs on existing operator spectrum, has 164 dB maximum coupling loss (the deepest indoor penetration of any cellular radio), and fits 7-10 year battery life with daily reporting comfortably.

NB-IoT wins when:

• Assets travel across multiple sites or geographies but always within an operator's coverage map
• Indoor penetration matters — basement-to-mezzanine reach in a warehouse, container interior, vehicle compartments
• Reporting cadence is 1-12 messages per day, message size 50-200 bytes
• You want a single SIM that works EU-wide via a connectivity provider's roaming agreements

It struggles when assets are in motion across cell boundaries continuously (no handover) or when reporting cadence climbs above 1 message per minute (battery and operator cost both suffer).

LTE-M: When Mobility Matters

LTE-M (Cat-M1) sits between NB-IoT and traditional LTE. It supports proper handover (so a tracker on a moving vehicle stays connected as it crosses cells), more bandwidth than NB-IoT, and voice if you ever need it. The trade-off is higher current draw and shorter battery life.

LTE-M wins when:

• The asset is in continuous motion across cell boundaries — fleet vehicles, container chassis on highways, mobile machinery
• Reporting cadence is every few minutes
• You need 100-1,000 byte messages and occasional firmware updates over the air
• 3-5 year battery life is acceptable, or the asset is rechargeable / vehicle-powered

It struggles when battery life needs to exceed 5 years or when message size is consistently small. NB-IoT is more efficient for those shapes.

5G NR-RedCap: The Future, Not Yet the Present

5G NR-RedCap (Reduced Capability, 3GPP Release 17, deployed from 2024 onwards) targets industrial IoT use cases that need more bandwidth than LTE-M but less than full 5G. It is the natural replacement for LTE-M as operators sunset 4G in the early 2030s.

5G NR-RedCap is the right choice when:

• Asset deployment will outlive 4G operator support (10+ year fleet)
• Use case includes high-bandwidth episodes — image upload from a tag, frequent firmware updates, live video diagnostics
• Asset is rechargeable or mains-powered (battery life is the worst of the four radios)

For most pure asset-tracking deployments today, LTE-M or NB-IoT is more cost-effective. 5G RedCap becomes the default in 2027-2028 as 4G sunset approaches.

Decision Tree We Use With Customers

1. Are all assets on one or two sites you control? → LoRaWAN
2. Are assets stationary or quasi-static across a wide geography, indoor-heavy, with a 7-10 year battery target? → NB-IoT
3. Are assets in continuous motion across cells, with 3-5 year battery acceptable? → LTE-M
4. Is the deployment a 10-year fleet that needs to ride the 4G sunset, with high-bandwidth episodes? → 5G NR-RedCap
5. Is the use case truly real-time and indoor with sub-second latency? → BLE 5.x via fixed gateway infrastructure, not a wide-area radio

Hybrid deployments are common: LoRaWAN inside the warehouse, NB-IoT on the in-transit leg, and BLE for tool tracking on the workshop floor. The platform should accept all three through a unified asset twin.

Operator Choice Matters Almost as Much as Radio Choice

NB-IoT and LTE-M coverage maps differ from operator to operator within the same country. A multi-IMSI / eSIM-based connectivity provider that switches between operator networks is usually worth the small premium. We have seen deployments fail because the customer locked into a single MNO and the in-transit leg passed through 200 km of that MNO's poor coverage.

How Opsio Helps

Opsio's iot asset delivery work begins with a connectivity site survey — drive-tests, signal heatmaps, and operator coverage validation against the actual asset routes. We pair this with the platform engineering for industrial iot services and the end-to-end iot services operating model that keeps the radio fleet healthy across its 5-10 year life.