17  LPWAN Technology Selection

In 60 Seconds

LPWAN technology selection starts with three questions: Do you need private network control? (LoRaWAN.) Do you need carrier-grade reliability? (NB-IoT.) Is it an ultra-simple sensor with tiny payloads? (Sigfox.) The comprehensive comparison matrix covers range, data rate, battery life, cost, mobility, reliability, and firmware update capabilities across LoRaWAN, Sigfox, NB-IoT, and LTE-M.

17.1 Learning Objectives

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

• Select the appropriate LPWAN technology using structured decision trees for specific deployment scenarios
• Compare LoRaWAN, Sigfox, NB-IoT, and LTE-M across technical and business dimensions to justify technology choices
• Evaluate private vs public network trade-offs for LoRaWAN deployments at different scales
• Distinguish LPWAN technologies by use case based on data rate, mobility, reliability, and cost requirements
• Calculate total cost of ownership across deployment scenarios to support evidence-based technology decisions

For Beginners: LPWAN Technology Selection

Choosing between LoRaWAN, Sigfox, and NB-IoT depends on your specific needs. Do you need to send data from a remote farm (LoRaWAN)? Just tiny status messages from thousands of simple devices (Sigfox)? Or reliable connectivity using existing cell towers (NB-IoT)? This chapter helps you match technology to requirements.

Sensor Squad: Three Technologies, Three Strengths

“LoRaWAN, Sigfox, NB-IoT – they all sound the same to me!” groaned Sammy the Sensor.

Max the Microcontroller clarified: “LoRaWAN is the DIY option. You buy your own gateway, set up your own network, and control everything. Great for farms, campuses, and private networks. Range up to 15 km rural.”

“Sigfox is the phone plan option,” said Lila the LED. “You just buy a Sigfox-enabled sensor and it connects to Sigfox’s network automatically – like a mobile phone. But you’re limited to 140 messages per day of 12 bytes each. Ultra-simple, ultra-cheap per device.”

Bella the Battery compared: “NB-IoT uses existing cell towers, so coverage is best in cities. It handles more data than LoRaWAN or Sigfox and works great indoors. But it requires a SIM card and a data plan, so the per-device cost is higher.”

Max summarized: “Remote farm with your own gateway? LoRaWAN. Millions of simple sensors with no infrastructure? Sigfox. City deployment needing reliable indoor coverage? NB-IoT. Match the technology to the environment!”

17.2 LPWAN Technology Selection Decision Tree

~15 min | Intermediate | P09.C02.U03

Choosing the right LPWAN technology depends on your deployment model, coverage needs, and application requirements. Use this decision tree to guide your selection:

Figure 17.1: LPWAN technology selection decision tree by requirements

17.3 LPWAN Technology Comparison Matrix

Use this comprehensive comparison to evaluate LPWAN options for your use case:

Factor	LoRaWAN	Sigfox	NB-IoT	LTE-M
Range (Urban)	2-5 km	3-10 km	1-10 km	1-10 km
Range (Rural)	15 km	30-50 km	10-15 km	10-15 km
Data Rate	0.3-50 kbps	100 bps (UL) 26.6 bps (DL)	Up to 250 kbps	Up to 1 Mbps
Bandwidth	125-500 kHz	100 Hz (UNB)	180 kHz	1.4 MHz
Messages/Day	Unlimited	140 UL / 4 DL	Unlimited	Unlimited
Payload Size	243 bytes max	12 bytes (UL) 8 bytes (DL)	1600 bytes	1600 bytes
Latency	1-5 seconds	2-6 seconds	1-10 seconds	10-100 ms
Battery Life	5-15 years	10-20 years	5-10 years	5-10 years
Spectrum	Unlicensed ISM (868/915 MHz)	Unlicensed ISM (868/902 MHz)	Licensed LTE (800-2600 MHz)	Licensed LTE (700-2600 MHz)
Deployment	Private or public	Public operator	Carrier network	Carrier network
Coverage	DIY or operator	Limited (70 countries)	Global (100+ countries)	Global (100+ countries)
Device Cost	$3-10	$2-5	$10-30	$15-40
Gateway Cost	$200-1500 (buy once)	N/A (operator)	N/A (carrier)	N/A (carrier)
Subscription	$0-1/device/year (private = $0)	$1-2/device/year	$1-5/device/month	$2-10/device/month
10-Year Cost (1000 devices)	$15K (private) $25K (public)	$25K	$300K	$500K
Mobility	Poor (stationary)	Poor (stationary)	Good (limited handoff)	Excellent (full handoff)
Downlink	Yes (Class A/B/C)	Yes (4 msgs/day)	Yes (unlimited)	Yes (unlimited)
Reliability	85-95% (Class A) 97-99% (confirmed)	95-98% (3x repeat)	99.9% (TCP-like)	99.9% (TCP-like)
QoS	No	No	Yes (3GPP)	Yes (3GPP)
Security	AES-128	AES-128	LTE security	LTE security
Standardization	LoRa Alliance	Sigfox (proprietary)	3GPP standard	3GPP standard
Firmware Updates	Yes (FUOTA)	No (too limited)	Yes (TCP/UDP)	Yes (TCP/UDP)
Best For	Private networks Agriculture Smart buildings Fixed sensors	Ultra-low cost Infrequent updates Simple sensors Low volume	Mission-critical Smart cities Utilities Reliable delivery	Asset tracking Fleet management Mobile devices Voice support

Knowledge Check: Reading the Comparison Matrix

A smart parking sensor updates every 2 minutes (720 messages/day) and requires 99%+ delivery reliability. Which LPWAN technology should you select?

A) Sigfox — Sigfox enforces a hard limit of 140 uplink messages per day. A sensor sending 720 messages per day (every 2 minutes) would exceed this limit by 5x, causing most messages to be dropped. Additionally, Sigfox achieves reliability through triple-redundant transmission at the network level — it does not provide confirmed delivery in the NB-IoT/LTE-M sense.

B) LoRaWAN Class A — LoRaWAN Class A achieves 85-95% delivery reliability without confirmed uplinks. For 99%+ reliability you must enable confirmed messages (which does reach 97-99%), but duty-cycle regulations in Europe (~1% at 868 MHz) also constrain transmission frequency. At 720 messages/day you risk hitting duty-cycle limits with large spreading factors, making this a risky choice for guaranteed high-frequency reliable delivery.

C) NB-IoT — Correct. NB-IoT supports unlimited messages per day and provides 99.9% reliability backed by a 3GPP licensed-spectrum carrier SLA. It is the appropriate choice when both high message frequency and high delivery reliability are required.

D) LoRaWAN Class C — Partially correct but incomplete reasoning. LoRaWAN Class C enables continuous downlink listening and reduces latency, but it does not inherently raise delivery reliability above Class A for uplink messages. The limiting factor here is reliability and message volume, which NB-IoT addresses more completely through licensed spectrum and guaranteed QoS.

Tradeoff: LoRaWAN Private Network vs Cellular LPWAN (NB-IoT/LTE-M)

Option A (LoRaWAN Private): Zero recurring connectivity cost, full data sovereignty, 2-15 km range per gateway. Upfront: 5 gateways x $500 = $2,500 + $15,000 sensors. 10-year TCO for 1,000 devices: ~$17,500 ($1.75/device/year). Requires gateway deployment and backhaul.

Option B (Cellular LPWAN): No infrastructure deployment, global roaming, 99.9% carrier SLA reliability. 10-year TCO for 1,000 devices: $20,000 hardware + $300,000 subscriptions = $320,000 ($32/device/year). Licensed spectrum eliminates interference.

Decision Factors: Choose LoRaWAN Private for fixed-location deployments (agriculture, utilities, smart buildings) where you control the premises and want minimal recurring costs. Choose Cellular LPWAN for mobile assets (fleet tracking, logistics), mission-critical reliability requirements, or deployments spanning multiple countries/regions where gateway deployment is impractical.

Tradeoff: LoRa Spreading Factor SF7 vs SF12

Option A (SF7): Data rate 5.5 kbps, airtime 36 ms for 12-byte payload, range 2-3 km urban, battery: 500,000+ messages on 2xAA cells. Link budget: +137 dB. Best throughput.

Option B (SF12): Data rate 0.25 kbps, airtime 1,810 ms for 12-byte payload (50x longer), range 8-15 km, battery: 10,000 messages on same cells. Link budget: +157 dB (+20 dB gain). Maximum range.

Decision Factors: Choose SF7-SF9 for urban deployments with good gateway density, high-frequency reporting (>10 messages/hour), or when battery life is critical. Choose SF10-SF12 for rural deployments, deep indoor penetration, or when gateway infrastructure is sparse. Use ADR (Adaptive Data Rate) to automatically optimize: devices start at SF12 for reliability, network server adjusts downward as link quality permits.

17.4 Interactive Tool: LPWAN Technology Selector

Use this interactive tool to determine the best LPWAN technology for your IoT deployment. Answer the questions below based on your requirements, and the tool will recommend LoRaWAN, Sigfox, or NB-IoT/LTE-M.

LPWAN Technology Selector Tool

Academic Resource: Stanford IoT Course - Energy Harvesting Sources for LPWAN

Stanford energy harvesting comparison table showing power density for different sources

Source: Stanford University IoT Course - Energy harvesting enables battery-free LPWAN sensors. Note the 1000x difference between indoor (10 uW/cm2) and outdoor solar (10,000 uW/cm2), explaining why most solar-powered IoT is outdoor.

Protocol Energy Efficiency Comparison

Understanding energy efficiency is critical for battery-powered IoT deployments. Energy per bit varies dramatically across wireless protocols, creating a 100x difference between the most and least efficient options:

Protocol	Energy (nJ/bit)	Range	Data Rate	Best For
Wi-Fi	50-100	~100m	54+ Mbps	High bandwidth, power available
BLE	15-30	~10m	1-2 Mbps	Short range, frequent small packets
Zigbee	40-60	~100m	250 kbps	Mesh networks, moderate data
LoRa	1000-5000	10+ km	0.3-50 kbps	Long range, infrequent data
NB-IoT	500-1000	Cellular	250 kbps	Licensed spectrum, reliability
Sigfox	500-2000	10+ km	100 bps	Ultra-low data, long range

Key insights:

1. Long range costs more per bit - LoRa uses 50-100x more energy per bit than BLE
2. Total energy matters - Sending 1KB via LoRa may still be efficient if it avoids gateway infrastructure
3. Protocol overhead varies - Consider header sizes for small payloads
4. Sleep current dominates - A device sleeping 99% of the time may use more energy sleeping than transmitting!

Key Insight: Energy per bit is NOT the whole story. Total energy consumption depends on your data volume and range requirements.

Example Scenarios:

Scenario 1: Smart Water Meter (1 reading/day, 12 bytes)

Wi-Fi:     12 bytes x 8 bits x 75 nJ/bit = 7,200 nJ/msg -> Battery life: 1-2 years
LoRa SF12: 12 bytes x 8 bits x 1200 nJ/bit = 115,200 nJ/msg -> Battery life: 10+ years
Why LoRa wins: Despite 16x worse energy/bit, LoRa's longer range means no Wi-Fi routers needed

Scenario 2: Fitness Tracker (continuous data, 1 KB/hour)

BLE:      1000 bytes x 8 bits x 25 nJ/bit = 200,000 nJ/msg -> Battery life: days (rechargeable OK)
LoRa SF7: 1000 bytes x 8 bits x 1000 nJ/bit = 8,000,000 nJ/msg -> Battery life: weeks (not months!)
Why BLE wins: For continuous data, BLE's 40x better energy/bit matters more than LoRa's range

Decision Framework:

1. Low data volume (< 1 KB/day) + Long range needed -> Choose LoRa/NB-IoT
   • Total energy dominated by fixed overhead (radio warmup, sync)
   • Higher energy/bit acceptable for infrequent transmissions
   • Example: Soil moisture sensor sending 20 bytes/hour across 5 km farm
2. High data volume (> 1 MB/day) + Short range acceptable -> Choose Wi-Fi/BLE
   • Total energy dominated by data transmission
   • Lower energy/bit becomes critical
   • Example: Smartwatch syncing health data to phone every 5 minutes
3. Medium data (1-100 KB/day) + Medium range -> Choose Zigbee/NB-IoT
   • Balance between energy/bit and range
   • Example: Smart thermostat updating temperature every 15 minutes

Rule of Thumb: Choose based on total energy for your data volume and range, not just energy/bit. A 100x worse energy/bit protocol can still have 10x better battery life if you only send 1/1000th the data.

Pitfall: Assuming LPWAN Means “Always Low Power”

The Mistake: Believing that using LoRa or any LPWAN technology automatically guarantees multi-year battery life, then being surprised when batteries drain in weeks.

Why It Happens: LPWAN marketing emphasizes “10+ year battery life” without clarifying that this assumes proper power management: aggressive sleep modes, infrequent transmissions (1-4 per hour), and avoiding continuous sensing. Developers who poll sensors frequently or use Class C mode negate all power benefits.

The Fix: Calculate your actual power budget before deployment. A LoRa radio transmitting at SF12 consumes 120mA for 1.3 seconds per message. At 1 message per hour with proper sleep (1uA), you get 10 years. At 1 message per minute, you get 6 months. At continuous Class C listening (15mA), you get 2 weeks on 2xAA batteries.

Pitfall: Treating All LPWAN Technologies as Interchangeable

The Mistake: Selecting LPWAN technology based solely on range claims, then discovering fundamental protocol mismatches with application requirements (e.g., Sigfox’s 140 messages/day limit for a parking sensor that changes state 50 times daily).

Why It Happens: LPWAN technologies appear similar at a high level (long range, low power) but have vastly different design centers: LoRaWAN for flexibility and private networks, Sigfox for ultra-simple sensors with infrequent updates, NB-IoT for carrier-grade reliability and mobility.

The Fix: Match technology to your specific requirements: (1) Message frequency: Sigfox limits 140/day, LoRaWAN limited by duty cycle (~500-2000/day at SF10), NB-IoT unlimited. (2) Bidirectional needs: Sigfox allows only 4 downlinks/day, LoRaWAN and NB-IoT are symmetric. (3) Mobility: Only LTE-M and NB-IoT support handoff. (4) Coverage: NB-IoT requires carrier infrastructure, LoRaWAN can be self-deployed.

17.5 Cost Analysis Examples

Understanding total cost of ownership is critical for LPWAN selection:

Scenario 1: Smart Agriculture - 1,000 Soil Sensors (10 years)

Option	Hardware	Infrastructure	Subscription (10yr)	Total Cost
LoRaWAN (Private)	$10K	$7.5K (5 gateways)	$0	$17.5K
LoRaWAN (Public)	$10K	$0	$15K ($1.50/yr/device)	$25K
Sigfox	$5K	$0	$20K ($2/yr/device)	$25K
NB-IoT	$25K	$0	$300K ($30/yr/device)	$325K

Winner: LoRaWAN private (lowest cost for stationary, rural deployment)

Putting Numbers to It

Let’s calculate the per-device cost difference over 10 years:

LoRaWAN per-device TCO: \[\text{Cost per device} = \frac{\$10{,}000 + \$7{,}500 + \$0}{ 1{,}000} = \$17.50/\text{device over 10 years}\]

NB-IoT per-device TCO: \[\text{Cost per device} = \frac{\$25{,}000 + \$0 + \$300{,}000}{1{,}000} = \$325/\text{device over 10 years}\]

The ratio: \(325 ÷ 17.50 = 18.6×\) more expensive for NB-IoT. The break-even scale where LoRaWAN becomes cheaper: \[\frac{\text{Gateway cost}}{\text{Subscription savings per device}} = \frac{\$7{,}500}{\$30/\text{yr}} = 250 \text{ devices at 1 year}\]

At 1,000 devices, LoRaWAN saves $307,500 over 10 years—enough to pay for 15× the gateway infrastructure. This is why utilities with fixed meter locations universally choose private LoRaWAN over cellular.

Scenario 2: Fleet Tracking - 500 Trucks (5 years, global)

Option	Hardware	Infrastructure	Subscription (5yr)	Total Cost
LoRaWAN	$5K	$0	$0	$5K + No global coverage
Sigfox	$2.5K	$0	$5K	$7.5K + Limited coverage
NB-IoT	$15K	$0	$150K	$165K Best option
LTE-M	$20K	$0	$250K	$270K Fallback option

Winner: NB-IoT (only option with global mobility and reliable coverage)

Scenario 3: Smart City Parking - 10,000 Sensors (10 years)

Option	Hardware	Infrastructure	Subscription (10yr)	Total Cost	Reliability
LoRaWAN	$50K	$30K (20 gateways)	$0	$80K	85-95%
Sigfox	$30K	$0	$200K	$230K	95-98%
NB-IoT	$250K	$0	$3M	$3.25M	99.9%

Winner: Depends on reliability requirement - Best cost: LoRaWAN ($80K but 85-95% reliability) - Best reliability: NB-IoT ($3.25M but 99.9% reliability) - Compromise: Sigfox ($230K with 95-98% reliability)

Calculator: 10-Year Total Cost of Ownership Comparison

viewof numDevices = Inputs.range([100, 50000], {value: 1000, step: 100, label: "Number of Devices"})
viewof years = Inputs.range([1, 15], {value: 10, step: 1, label: "Deployment Years"})
viewof loraGateways = Inputs.range([1, 50], {value: 5, step: 1, label: "LoRaWAN Gateways (Private)"})

{
  // Cost constants
  const gatewayCost = 500;       // $ per gateway
  const loraDeviceCost = 8;      // $ per device
  const sigfoxDeviceCost = 3.5;  // $ per device
  const nbiotDeviceCost = 20;    // $ per device
  const ltemDeviceCost = 30;     // $ per device

  const loraSubPrivate = 0;      // $/device/year (private)
  const sigfoxSub = 2;           // $/device/year
  const nbiotSub = 30;           // $/device/year (approx $2.50/month)
  const ltemSub = 60;            // $/device/year (approx $5/month)

  const loraPrivateTCO = (loraDeviceCost * numDevices) + (loraGateways * gatewayCost) + (loraSubPrivate * numDevices * years);
  const sigfoxTCO = (sigfoxDeviceCost * numDevices) + (sigfoxSub * numDevices * years);
  const nbiotTCO = (nbiotDeviceCost * numDevices) + (nbiotSub * numDevices * years);
  const ltemTCO = (ltemDeviceCost * numDevices) + (ltemSub * numDevices * years);

  const fmt = v => v >= 1000000 ? `$${(v/1000000).toFixed(2)}M` : v >= 1000 ? `$${(v/1000).toFixed(1)}K` : `$${v}`;
  const perDevice = v => `$${(v/numDevices).toFixed(2)}/device`;

  const div = htl.html`<div style="background:#f8f9fa;border-left:4px solid #E67E22;padding:16px;border-radius:4px;font-family:Arial,sans-serif">
    <h4 style="color:#2C3E50;margin:0 0 12px">${years}-Year TCO for ${numDevices.toLocaleString()} Devices</h4>
    <table style="border-collapse:collapse;width:100%;font-size:0.9em">
      <thead><tr style="background:#2C3E50;color:white">
        <th style="padding:8px;text-align:left">Technology</th>
        <th style="padding:8px;text-align:right">Hardware</th>
        <th style="padding:8px;text-align:right">Subscriptions</th>
        <th style="padding:8px;text-align:right">Total TCO</th>
        <th style="padding:8px;text-align:right">Per Device</th>
      </tr></thead>
      <tbody>
        <tr style="background:white"><td style="padding:6px 8px;color:#16A085;font-weight:bold">LoRaWAN (Private)</td><td style="padding:6px 8px;text-align:right">${fmt(loraDeviceCost*numDevices + loraGateways*gatewayCost)}</td><td style="padding:6px 8px;text-align:right">$0</td><td style="padding:6px 8px;text-align:right;font-weight:bold;color:#16A085">${fmt(loraPrivateTCO)}</td><td style="padding:6px 8px;text-align:right">${perDevice(loraPrivateTCO)}</td></tr>
        <tr style="background:#f8f9fa"><td style="padding:6px 8px;color:#3498DB;font-weight:bold">Sigfox</td><td style="padding:6px 8px;text-align:right">${fmt(sigfoxDeviceCost*numDevices)}</td><td style="padding:6px 8px;text-align:right">${fmt(sigfoxSub*numDevices*years)}</td><td style="padding:6px 8px;text-align:right;font-weight:bold;color:#3498DB">${fmt(sigfoxTCO)}</td><td style="padding:6px 8px;text-align:right">${perDevice(sigfoxTCO)}</td></tr>
        <tr style="background:white"><td style="padding:6px 8px;color:#E67E22;font-weight:bold">NB-IoT</td><td style="padding:6px 8px;text-align:right">${fmt(nbiotDeviceCost*numDevices)}</td><td style="padding:6px 8px;text-align:right">${fmt(nbiotSub*numDevices*years)}</td><td style="padding:6px 8px;text-align:right;font-weight:bold;color:#E67E22">${fmt(nbiotTCO)}</td><td style="padding:6px 8px;text-align:right">${perDevice(nbiotTCO)}</td></tr>
        <tr style="background:#f8f9fa"><td style="padding:6px 8px;color:#7F8C8D;font-weight:bold">LTE-M</td><td style="padding:6px 8px;text-align:right">${fmt(ltemDeviceCost*numDevices)}</td><td style="padding:6px 8px;text-align:right">${fmt(ltemSub*numDevices*years)}</td><td style="padding:6px 8px;text-align:right;font-weight:bold;color:#7F8C8D">${fmt(ltemTCO)}</td><td style="padding:6px 8px;text-align:right">${perDevice(ltemTCO)}</td></tr>
      </tbody>
    </table>
    <p style="margin:8px 0 0;font-size:0.85em;color:#7F8C8D">Assumes: LoRaWAN gateway $500, device costs LoRa $8 / Sigfox $3.50 / NB-IoT $20 / LTE-M $30. Subscriptions: Sigfox $2/yr, NB-IoT $30/yr, LTE-M $60/yr. Adjust device count and years to compare scenarios.</p>
  </div>`;
  return div;
}

17.6 Selection Checklist

Use this checklist to narrow down your LPWAN choice:

LPWAN Selection Questions

1. Coverage Requirements

• Do you have good cellular (4G/5G) coverage? Consider NB-IoT/LTE-M
• Is deployment in rural/remote areas? Consider LoRaWAN
• Need global roaming? NB-IoT/LTE-M only option

2. Deployment Model

• Can you deploy/maintain gateways? LoRaWAN feasible
• Want zero infrastructure management? NB-IoT/LTE-M or Sigfox
• Need full network control/privacy? LoRaWAN private

3. Application Requirements

• Messages > 140/day? NB-IoT/LTE-M or LoRaWAN
• Payload > 12 bytes? Not Sigfox
• Reliability must be 99%+? NB-IoT/LTE-M
• Downlink commands required? Not Sigfox (4/day limit)

4. Device Characteristics

• Devices are mobile? LTE-M or NB-IoT
• Devices are stationary? Any LPWAN works
• Need firmware updates OTA? LoRaWAN or NB-IoT/LTE-M

5. Cost Constraints

• Minimize upfront cost? Sigfox (lowest device cost)
• Minimize operational cost? LoRaWAN private (no subscription)
• Budget allows $2-5/device/month? NB-IoT/LTE-M acceptable

6. Scale and Timeline

• < 100 devices? Any option (small scale)
• 100-10,000 devices? Consider private LoRaWAN ROI
• > 10,000 devices? Private LoRaWAN or negotiate carrier bulk pricing

7. Future-Proofing

• Need 5G migration path? NB-IoT/LTE-M (3GPP standards)
• Concerned about operator bankruptcy? LoRaWAN (own infrastructure)
• Want open standards? LoRaWAN (LoRa Alliance) or NB-IoT (3GPP)

17.7 Real-World Deployment Examples

LoRaWAN Success Stories:

• Agriculture: 100,000+ acre farm with 5,000 soil sensors, 20 gateways, $0 ongoing cost
• Smart Building: 500-sensor private network, complete data privacy, gateway on-premise
• Campus Tracking: University asset tracking with full network control

Sigfox Success Stories:

• Utility Meters: Water/gas meters with 1 reading/day, $1/year/meter
• Simple Sensors: Temperature/humidity monitoring, minimal data, ultra-low cost
• Geolocation: GPS tracking with Sigfox Atlas (< 140 msgs/day)

NB-IoT Success Stories:

• Smart Cities: Barcelona parking sensors, 99.9% reliability for payment systems
• Utilities: Smart meters with carrier SLA, regulatory compliance
• Industrial: Factory monitoring requiring guaranteed message delivery

LTE-M Success Stories:

• Fleet Management: Global shipping container tracking with roaming
• Medical Devices: Wearable monitors with voice fallback capability
• Asset Tracking: High-value equipment requiring real-time location

Decision Framework: When to Choose Each LPWAN Technology

Use this decision matrix for rapid technology selection based on your critical requirements:

Your Requirement	Choose This	Why	Don’t Choose
<100 devices, pilot project, <2 years	NB-IoT/LTE-M	Avoid gateway CAPEX, instant coverage, fail fast if concept doesn’t work	LoRaWAN (gateway ROI insufficient)
1,000-10,000+ devices, fixed location, 5+ years	LoRaWAN Private	TCO savings: $500k-$5M over cellular subscriptions	Cellular (subscription costs compound)
Global roaming, mobile assets	LTE-M or NB-IoT	Only options with handover and 190+ country coverage	LoRaWAN/Sigfox (no mobility, regional coverage)
Ultra-simple, <140 msg/day, ≤12 bytes	Sigfox	Lowest hardware cost ($2-5/device), ultra-long battery (15+ years)	Others (over-engineered for simple use case)
Mission-critical, 99.9%+ reliability	NB-IoT/LTE-M	Licensed spectrum, carrier SLA, guaranteed QoS	Unlicensed LPWAN (best-effort, interference risk)
Remote location, no cellular	LoRaWAN Private	Only option if you can install gateways	Cellular (no coverage), Sigfox (limited rural)
Firmware updates required	LoRaWAN or NB-IoT/LTE-M	Support FUOTA (firmware updates over-the-air)	Sigfox (payload too small, 12 bytes)
Data rate >50 kbps needed	LTE-M (up to 1 Mbps)	Only LPWAN with >100 kbps capability	LoRaWAN/Sigfox (max 50/0.1 kbps)
Need private network control, data sovereignty	LoRaWAN Private	You own all infrastructure and data	Sigfox/NB-IoT (operator-managed, data passes through third party)
Budget <$5/device for hardware	LoRaWAN or Sigfox	Module costs $2-5 at volume	NB-IoT/LTE-M ($10-30 module + SIM)

Selection shortcut rules:

• Default to LoRaWAN if scale >1000 devices and can deploy gateways
• Default to NB-IoT if cellular coverage exists and reliability matters more than cost
• Default to Sigfox if ultra-simple sensors, operator network exists in region
• Default to LTE-M if mobile assets or need >100 kbps data rate

17.8 Knowledge Checks

Interactive Quiz: Match LPWAN Technology to Characteristic

🧠 Knowledge Check

🏷️ Label the Diagram

💻 Code Challenge

📝 Order the Steps

17.9 Summary

This chapter covered LPWAN technology selection:

• Decision tree: Navigate from requirements to recommended technology
• Comparison matrix: Detailed specifications for LoRaWAN, Sigfox, NB-IoT, LTE-M
• Interactive selector: Tool to evaluate your specific use case
• Cost analysis: TCO examples for different deployment scenarios
• Selection checklist: Questions to narrow down your choice

17.10 What’s Next

Chapter	Focus	Why Read It
LPWAN Link Budget	Friis equation, path loss models, link margin calculation	Validate whether your chosen technology reaches target sensors before hardware purchase
LPWAN Pitfalls	Common deployment mistakes and how to avoid them	Diagnose the 10 most frequent LPWAN implementation errors, including duty-cycle violations and gateway placement failures
LoRaWAN Overview	LoRaWAN architecture, MAC layer, OTAA/ABP join procedures	Implement LoRaWAN from scratch with a thorough understanding of the protocol stack
NB-IoT Fundamentals	NB-IoT radio interface, PSM, eDRX power modes	Configure NB-IoT power-saving modes to achieve target battery life in cellular deployments
LPWAN Overview	LPWAN history, spectrum, and shared design principles	Assess the broader LPWAN landscape and understand why all four technologies share similar range/power tradeoffs

Related Chapters

LPWAN Fundamentals Series:

• LPWAN Overview - Introduction and basics
• LPWAN Link Budget - Range calculations
• LPWAN Pitfalls - Common mistakes to avoid

Specific Technologies:

• LoRaWAN Overview - LoRa technology deep dive
• NB-IoT Fundamentals - Cellular LPWAN