5 LoRaWAN vs Other LPWAN Technologies
5.1 Learning Objectives
By the end of this chapter, you should be able to:
- Distinguish between LoRa (physical layer) and LoRaWAN (network protocol)
- Compare LoRaWAN with NB-IoT and Sigfox across technical and business dimensions
- Justify the appropriate LPWAN technology selection for different use cases
- Analyze the trade-offs between spectrum licensing, coverage models, and total cost of ownership
- Assess vendor lock-in risks and network ownership implications for long-term deployments
Key Concepts
- LPWAN Comparison Framework: Evaluation criteria for LPWAN technologies including coverage, power consumption, data rate, latency, cost, deployment model, and ecosystem maturity.
- NB-IoT: 3GPP-standardized cellular LPWAN using licensed spectrum; carrier-managed infrastructure, higher power than LoRaWAN, better indoor penetration, deterministic latency.
- Sigfox: Proprietary ultra-narrowband LPWAN with 12-byte maximum payload and 140 uplinks/day limit; network operated by Sigfox SA until 2022 restructuring.
- LoRaWAN Advantages: Open standard, private deployment option, flexible payload size, community networks (TTN), and no per-message fees in self-hosted deployments.
- LoRaWAN Disadvantages: ISM band interference risk, duty cycle limitations, no guaranteed QoS, and smaller payload size limits compared to cellular alternatives.
- Technology Selection: Use LoRaWAN for private deployments, low cost, large area, and moderate payload; NB-IoT for carrier-managed, guaranteed QoS, and urban indoor scenarios.
- Convergence Trends: Multi-protocol devices and platforms supporting both LoRaWAN and NB-IoT are becoming common for deployments requiring technology flexibility.
LoRaWAN is one of several LPWAN (Low-Power Wide-Area Network) technologies. Others include Sigfox and NB-IoT. Each has different strengths: LoRaWAN offers flexibility and open standards, Sigfox prioritizes simplicity, and NB-IoT uses existing cellular infrastructure. This chapter helps you understand when LoRaWAN is the best choice.
“There are three main LPWAN technologies, and each one has different strengths!” Sammy the Sensor explained. “LoRaWAN lets you build and own your own network. NB-IoT uses existing cell towers. And Sigfox is a managed service where someone else runs everything. Choosing the right one depends on your project’s needs!”
“LoRaWAN is like owning your own walkie-talkie system,” Lila the LED said. “You buy the gateways, set up the network, and control everything. It is great for farms, campuses, and factories where you want full control. But you have to manage the infrastructure yourself.”
Max the Microcontroller compared, “NB-IoT is like using a cell phone – the carrier already built the towers, and you just pay a monthly subscription. It works great when you need guaranteed coverage in deep basements or across an entire country. Sigfox is even simpler – like a postal service where you just drop off your tiny postcard and they handle delivery.”
“The cost comparison is interesting,” Bella the Battery noted. “LoRaWAN has higher upfront costs for gateways but no subscription fees. NB-IoT has per-device subscriptions but zero infrastructure cost. Sigfox is cheapest per device but limits you to 140 tiny messages per day. For a hundred sensors on a farm, LoRaWAN wins. For ten thousand sensors across a country, NB-IoT or Sigfox might be better!”
5.2 What is LoRaWAN?
LoRaWAN (Long Range Wide Area Network) is an open protocol and MAC layer specification built on top of LoRa modulation. It defines the network architecture, communication protocol, and security mechanisms.
| Aspect | LoRa | LoRaWAN |
|---|---|---|
| Type | Physical layer modulation | MAC layer protocol |
| Function | Radio modulation technique | Network protocol |
| Ownership | Proprietary (Semtech) | Open standard (LoRa Alliance) |
| Defines | How data is transmitted | Network architecture, security, device management |
| Usage | Can be used independently | Uses LoRa as physical layer |
Analogy: LoRa is like Wi-Fi’s radio technology, while LoRaWAN is like the complete Wi-Fi protocol stack (802.11).
5.3 Tradeoff: LoRaWAN vs NB-IoT
Decision context: When selecting LPWAN technology for a wide-area IoT deployment, LoRaWAN and NB-IoT are the two leading options with fundamentally different architectures.
| Factor | LoRaWAN | NB-IoT |
|---|---|---|
| Spectrum | Unlicensed ISM bands (free) | Licensed cellular bands (carrier fees) |
| Network Ownership | Private or public (your choice) | Carrier-operated only |
| Data Rate | 0.3-50 kbps | Up to 250 kbps |
| Latency | Seconds to minutes (Class A) | Milliseconds to seconds |
| Coverage | Deploy your own gateways | Depends on carrier infrastructure |
| QoS Guarantees | Best-effort (no SLA) | Carrier SLA available |
| Bidirectional | Limited (Class A/B/C trade-offs) | Full duplex, always-on |
| Roaming | Complex (network-specific) | Carrier roaming agreements |
| Battery Life | 10+ years (optimized for sleep) | 5-10 years (PSM/eDRX modes) |
| Payload Size | 51-222 bytes | Up to 1600 bytes |
Choose LoRaWAN when:
- You need a private network (data sovereignty, no carrier dependency)
- Deploying in rural/remote areas without cellular coverage
- Cost is critical (no per-device subscription fees)
- You can deploy and manage your own gateways
- Ultra-low power with infrequent uplinks is the priority
Choose NB-IoT when:
- You need guaranteed QoS with carrier SLA
- Bidirectional communication with low latency is required
- Deploying in urban areas with existing cellular coverage
- Larger payloads or higher data rates are needed
- Global roaming with carrier agreements is important
- You prefer managed connectivity without infrastructure ownership
Default recommendation: Use LoRaWAN for private deployments, rural coverage, and cost-sensitive applications. Choose NB-IoT when you need carrier-grade reliability, SLA guarantees, or seamless global roaming in urban environments.
5.4 LPWAN Technology Comparison: LoRaWAN vs Sigfox vs NB-IoT
Different LPWAN technologies excel in different scenarios. This comparison helps you select the best fit for your IoT deployment:
| Feature | LoRaWAN | Sigfox | NB-IoT |
|---|---|---|---|
| Modulation | Chirp Spread Spectrum (CSS) | Ultra-Narrow Band (UNB) | LTE-based (QPSK) |
| Frequency | ISM bands (unlicensed): 868 MHz (EU), 915 MHz (US) | ISM bands (unlicensed): 868/902 MHz | Licensed cellular spectrum (LTE bands) |
| Range | 2-15 km (urban), 40 km (rural) | 10-50 km (urban), 50+ km (rural) | 1-10 km (coverage depends on carrier) |
| Data Rate | 0.3-50 kbps (adaptive) | 100 bps uplink, 600 bps downlink | 250 kbps (peak, shared with LTE) |
| Payload Size | 51-222 bytes (SF-dependent) | 12 bytes uplink, 8 bytes downlink | Up to 1600 bytes |
| Messages/Day | Unlimited (1% duty cycle in EU) | 140 uplink, 4 downlink | Unlimited (carrier-dependent) |
| Bidirectional | Yes (all classes support downlink) | Limited (4 downlinks/day) | Yes (full duplex) |
| Battery Life | 5-10 years | 10-20 years (very low message rate) | 5-10 years (PSM/eDRX modes) |
| Network Ownership | Public (TTN) or Private | Public only (Sigfox operates) | Public (carrier-operated: Verizon, AT&T, Vodafone) |
| Infrastructure Cost | Low ($300-600/gateway) | None (subscription-based) | None (uses existing cellular) |
| Subscription Cost | Free (TTN) or $1-5/device/year (private) | $1-10/device/year | $5-15/device/year (carrier contract) |
| Deployment | DIY possible (private network) | Operator-only (no private networks) | Operator-only (requires SIM) |
| Localization | Limited (TDOA via multi-gateway, ~50-200m accuracy) | Yes (RSSI-based, ~1-10 km accuracy) | Yes (cell tower triangulation) |
| Standardization | Open (LoRa Alliance) | Proprietary (Sigfox SA) | Open (3GPP standard) |
| Interference Immunity | Excellent (CSS spreading) | Good (UNB filtering) | Excellent (LTE QoS) |
| Indoor Penetration | Good (sub-GHz, high sensitivity) | Excellent (very low bandwidth) | Good (LTE infrastructure) |
| Mobility Support | Limited (ADR assumes stationary) | Good (no ADR needed) | Excellent (handoff like cellular) |
| QoS Guarantees | No (best effort, unconfirmed) | No (fire-and-forget) | Yes (carrier SLA, confirmed delivery) |
5.5 Decision Matrix: Which Technology to Choose?
Requirements:
- 200 sensors across 500-acre farm
- 1 reading per hour (temperature, moisture)
- 10-year battery life
- Low deployment cost
- No cellular coverage in rural area
Recommended: LoRaWAN
- Private network (1-2 gateways = $600)
- Unlimited messages (no subscription fees)
- Adaptive data rate optimizes battery
- DIY installation and maintenance
- Sigfox: No coverage in rural area, 140 msg/day limit
- NB-IoT: No cellular coverage available
Requirements:
- 10,000 containers tracked globally
- 1 GPS update per day
- Must work in 50+ countries
- Minimal infrastructure management
- Mobile (containers constantly moving)
Recommended: Sigfox
- Global coverage (70+ countries)
- No infrastructure to manage
- Low data rate acceptable (1 msg/day)
- Excellent mobility support
- LoRaWAN: No global coverage, ADR issues with mobility
- NB-IoT: Roaming expensive, carrier contracts complex
Requirements:
- 100,000 meters across city
- 1 reading per day + firmware updates
- Utility must guarantee 99.9% uptime
- Budget for subscriptions exists
- Needs bidirectional (meter commands)
Recommended: NB-IoT
- Carrier SLA (99.9% uptime guarantee)
- Large payloads (firmware updates)
- Unlimited downlinks (remote commands)
- Existing cellular infrastructure
- LoRaWAN: No uptime guarantees, FUOTA very slow
- Sigfox: 4 downlinks/day insufficient for commands
Requirements:
- 500 sensors per building
- 1 reading per 5 minutes
- Private network (data security)
- Immediate response to commands (<5 sec)
- Unlimited budget for infrastructure
Recommended: LoRaWAN (Private Network)
- No data leaves building (security)
- No subscription fees (long-term cost)
- Class B/C for fast downlinks
- High message frequency (no carrier limits)
- Sigfox: Cannot deploy private network
- NB-IoT: Data routed through carrier
5.6 Quick Selection Flowchart
Key Insight: No single LPWAN technology dominates all use cases. Choose based on: - LoRaWAN -> Private networks, unlimited messages, DIY control - Sigfox -> Global reach, ultra-low power, minimal maintenance - NB-IoT -> QoS guarantees, existing cellular, high data rates
5.7 Worked Example: 5-Year TCO for a Smart Agriculture Deployment
Scenario: A cooperative farm deploys 500 soil moisture sensors across 2,000 acres. Each sensor sends 24 readings/day (hourly). No cellular coverage exists. Compare the 5-year Total Cost of Ownership for LoRaWAN, Sigfox, and NB-IoT.
Device hardware costs (per sensor):
LoRaWAN module (SX1276): $4.50/unit
Sigfox module (S2-LP): $3.80/unit
NB-IoT module (BC95-G): $8.20/unit
Common components (MCU, sensor, PCB, enclosure): $12.00/unitInfrastructure costs:
LoRaWAN:
Gateways needed: 3 (each covers ~5 km radius)
Gateway cost: 3 x $450 = $1,350
Backhaul (cellular modem): 3 x $15/month = $45/month
Network server: The Things Stack Community (free) or $50/month (private)
Total infrastructure: $1,350 + ($45 x 60 months) = $4,050
Sigfox:
No coverage in rural area = CANNOT DEPLOY
Nearest base station: 40 km away
Operator will not install new base station for 500 devices
Result: Sigfox eliminated from consideration
NB-IoT:
No cellular coverage = CANNOT DEPLOY without new tower
Carrier mini-tower installation: ~$50,000 (if available)
Per-device SIM subscription: $2/device/month
Result: NB-IoT cost-prohibitive for this scenario5-year TCO comparison (500 sensors):
| Cost Item | LoRaWAN | Sigfox | NB-IoT |
|---|---|---|---|
| Sensors (500 x module + common) | $8,250 | N/A | $10,100 |
| Infrastructure | $4,050 | N/A | $50,000+ |
| Subscriptions (60 months) | $0-$3,000 | N/A | $60,000 |
| Replacement batteries (Year 3) | $2,500 | N/A | $2,500 |
| 5-Year Total | $14,800-$17,800 | Not feasible | $122,600+ |
| Per sensor per year | $5.92-$7.12 | – | $49.04 |
Battery life verification (LoRaWAN at SF8, ADR-optimized):
Per transmission:
TX current: 120 mA x 103 ms (SF8) = 12.36 mAs
RX1 window: 15 mA x 1 s = 15 mAs
RX2 window: 15 mA x 1 s = 15 mAs (if RX1 misses)
Processing: 10 mA x 5 ms = 0.05 mAs
Per TX total: ~27.4 mAs
Daily energy: 24 transmissions x 27.4 mAs = 657.6 mAs
Sleep current: 1.5 uA x 86,400 s = 129.6 mAs
Daily total: 787.2 mAs = 0.219 mAh
Battery capacity (2x AA lithium): 6,000 mAh
Projected life: 6,000 / 0.219 = 27,397 days = 75 years (theoretical)
With 50% derating (cold, aging): ~37 years
Practical life: 5-10 years (limited by battery self-discharge)Real-World Reference: Semtech’s deployment with Digital Matter in Australian cattle ranching (2022) uses LoRaWAN for 800 sensors across 10,000 hectares with 4 gateways, achieving $6.20/sensor/year TCO and 7+ year battery life – closely matching this calculation.
Key Takeaway: For rural deployments without existing infrastructure, LoRaWAN’s ability to self-deploy gateways makes it the only viable LPWAN option. The 5-year TCO advantage over NB-IoT can exceed 7x when infrastructure must be built from scratch.
TCO crossover point calculation uses: \(C_{LoRa} = C_{Sigfox}\) where costs are \(C_{device} + C_{infra} + C_{subscription} \times years\)
For \(N\) devices over 5 years: \[N \times 15 + (3 \times 450) + 0 = N \times 8 + 0 + N \times 6 \times 5\]
Solving for \(N\): \[15N + 1,350 = 8N + 30N\] \[1,350 = 23N\] \[N = 59 \text{ devices}\]
At scale >59 devices, LoRaWAN becomes cheaper. For 2,000 devices: - LoRaWAN: \((2000 \times 15) + 4,050 = \$34,050\) - Sigfox: \((2000 \times 8) + (2000 \times 6 \times 5) = \$76,000\)
Sigfox wins at <59 devices; LoRaWAN wins at >59 devices due to fixed gateway cost amortization.
5.8 Videos
See LoRaWAN technology deployed in real-world scenarios—from smart agriculture monitoring to urban IoT applications. This video demonstrates the practical aspects of LoRaWAN network setup, device configuration, and data visualization.
5.9 Hybrid Deployment Case Study: Swiss Post Smart Logistics
Swiss Post’s logistics division (2021) deployed a multi-technology LPWAN system across 1,400 post offices and 3 sorting centers, demonstrating that most real-world deployments do not use a single LPWAN technology. Each technology was selected for the specific constraints of its sub-application.
Deployment breakdown:
| Application | Technology | Devices | Why this technology |
|---|---|---|---|
| Parcel tracking (urban) | NB-IoT | 12,000 trackers | Indoor coverage in concrete buildings; carrier SLA for delivery guarantees; bidirectional for status queries |
| Parcel tracking (rural/alpine) | LoRaWAN | 3,200 trackers | 8 km range in valleys; no NB-IoT coverage in 34% of Swiss rural areas; private gateways on post offices |
| Mail container fill level | Sigfox | 6,800 sensors | Lowest cost (EUR 1.20/device/year); 1 message every 2 hours sufficient; 22,000+ device scale favored cheapest per-unit option |
| Building HVAC monitoring | LoRaWAN | 4,500 sensors | No cellular subscription cost; sensors inside metal HVAC ducts need local gateway proximity; 15-minute reporting |
| Fleet vehicle tracking | LTE-M | 2,100 trackers | Handover between cells at highway speed; voice fallback for driver SOS; GPS-assisted positioning |
Why not a single technology?
Swiss Post initially considered standardizing on NB-IoT for all applications. The projected cost comparison:
All-NB-IoT approach:
28,600 devices x EUR 4.50/device/year (Swisscom NB-IoT plan) = EUR 128,700/year
Rural coverage gap: 34% of post offices need signal repeaters
Repeater cost: 476 x EUR 800 = EUR 380,800 one-time
5-year connectivity TCO: EUR 1,024,300
Hybrid approach (actual):
NB-IoT: 12,000 x EUR 4.50 = EUR 54,000/year
LoRaWAN: 7,700 devices, 42 private gateways x EUR 300 = EUR 12,600 one-time
+ EUR 0 ongoing (own infrastructure)
Sigfox: 6,800 x EUR 1.20 = EUR 8,160/year
LTE-M: 2,100 x EUR 6.00 = EUR 12,600/year
5-year connectivity TCO: EUR 386,400The hybrid approach saved EUR 637,900 over 5 years (62% less) while providing better coverage than any single-technology solution. The key was matching each sub-application to the technology whose strengths aligned with its specific constraints – not forcing all use cases into one “best” technology.
Operational insight: The biggest challenge was not the technology itself but the data integration layer. Each LPWAN technology delivers data through a different API format and protocol (LoRaWAN via MQTT from ChirpStack, NB-IoT via Swisscom’s SCEF API, Sigfox via HTTP callbacks, LTE-M via direct TCP). Swiss Post built a unified ingestion gateway that normalized all sources into a common data model, adding EUR 85,000 in development cost but eliminating the need for 4 separate dashboards.
5.10 Summary
This chapter compared LoRaWAN with other LPWAN technologies:
- LoRa vs LoRaWAN: LoRa is the physical layer; LoRaWAN is the complete network protocol
- LoRaWAN strengths: Private networks, unlimited messages, no subscription fees
- Sigfox strengths: Global coverage, ultra-simple, lowest power
- NB-IoT strengths: Carrier SLA, larger payloads, bidirectional communication
- Selection criteria: Private network needs, global coverage, QoS requirements, message frequency
5.11 Knowledge Check
5.12 How It Works: LPWAN Technology Selection Process
Choosing the right LPWAN technology is a systematic process, not a guessing game. Here’s how to approach it:
Step 1: Map Your Requirements (15 minutes) Document your application’s constraints: message size, frequency, deployment scale, budget, coverage area, and latency needs. For example: “500 soil sensors, 8-byte payload, 24 messages/day, $20/sensor budget, rural 5 km² farm, no cellular coverage.”
Step 2: Apply Elimination Criteria (5 minutes) Use hard constraints to eliminate technologies. If your payload is 50 bytes, Sigfox (12-byte limit) is out. If you need 200 messages/day, Sigfox (140/day) is out. If you need real-time alerts (<5 sec), cellular IoT is required.
Step 3: Calculate 5-Year TCO (15 minutes) For remaining options, calculate total cost of ownership: devices + infrastructure + subscriptions + maintenance over 5 years. Include battery replacement costs (Class C devices need frequent changes) and gateway backhaul fees (cellular modems in gateways).
Step 4: Verify Coverage (Critical!) For Sigfox and NB-IoT, check actual coverage maps - not theoretical. Deploy 5-10 pilot devices at actual installation locations for 30 days. Measure message success rate and RSSI. Accept only if >95% success rate with >10 dB margin.
Step 5: Consider Vendor Lock-In Risk (Strategic) Evaluate: Can you switch technologies later? Sigfox is single-operator dependency. NB-IoT requires carrier relationship. LoRaWAN offers most flexibility (open standard, multiple vendors, self-deployable).
Real-World Example: Smart parking company evaluated all three for 2,000 sensors. Requirements: 5-byte payload, 50 updates/day, 10-year battery life, city deployment with existing cellular coverage.
- Sigfox: Eliminated (50 updates/day exceeds 140 limit)
- NB-IoT: $40K devices + $240K subscriptions (5 years) = $280K
- LoRaWAN: $50K devices + $15K gateways = $65K ✓ Winner
Lesson: Don’t assume cellular is “easier” - run the numbers!
5.13 Incremental Learning Examples
Master LPWAN selection through these progressive scenarios:
Example 1: Single Environmental Sensor (Beginner) You need one temperature sensor in your backyard reporting to a Raspberry Pi 100m away. Which LPWAN? None! Use LoRa peer-to-peer (no network protocol overhead) or Bluetooth LE. LPWAN is for wide-area networks - overkill here.
Example 2: Farm with 50 Soil Sensors (Intermediate) Sensors spread across 500 acres (2 km²), 1 reading/hour, no cellular coverage.
Analysis: 24 messages/day fits Sigfox, but check coverage first. If Sigfox available → $3K deployment. If not → LoRaWAN with 1-2 gateways → $10K. Decision depends on coverage, not technology preference.
Example 3: City-Wide 10,000 Parking Sensors (Advanced) Urban deployment with excellent cellular coverage, 100-byte payloads (occupancy + car size + confidence score), 10 updates/hour.
Analysis: - Sigfox: Eliminated (12-byte payload, 240 updates/day exceeds limit) - LoRaWAN: Possible (100 bytes fits SF7-9), but need ~100 gateways (1 per 10-15 blocks) = $50K infrastructure - NB-IoT: Best fit - existing infrastructure, handles 100-byte payloads easily, $1.2M subscription (5 years) justified by revenue ($2/hour parking fees)
Lesson: At this scale with revenue, subscription costs are acceptable. LoRaWAN infrastructure becomes expensive.
Example 4: Global Asset Tracking (Expert) Track 5,000 shipping containers across 50 countries, 1 GPS update every 2 hours.
Analysis: Only NB-IoT or hybrid work. Sigfox has coverage gaps. LoRaWAN impossible (can’t deploy gateways in every port). Use NB-IoT with eSIM roaming OR Sigfox + NB-IoT hybrid (Sigfox primary, cellular fallback in no-coverage zones).
5.14 Concept Check
Test your understanding before moving forward:
## Try It Yourself
Apply LPWAN selection to your own scenario:
Exercise: Personal LPWAN Decision
Pick a real or hypothetical IoT deployment you’re interested in. Work through these steps:
Define Requirements:
- Application: ___________________
- Number of devices: ___________
- Payload size: ________ bytes
- Message frequency: ______/day
- Deployment area: ________ km²
- Budget per device: $________
- Battery or mains power? ________
Apply Elimination Rules:
- If payload > 12 bytes → Eliminate Sigfox
- If frequency > 140/day → Eliminate Sigfox
- If need real-time (<5 sec) → Require cellular
- If no existing coverage → Eliminate Sigfox/NB-IoT
Calculate 5-Year TCO:
Sigfox: ____ devices × $12 + ____ × $1/year × 5 = $____ LoRaWAN: ____ devices × $15 + ____ gateways × $500 = $____ NB-IoT: ____ devices × $20 + ____ × $12/year × 5 = $____Decision: _______________ because: ___________________________
What to Observe:
- Did one technology get eliminated immediately by hard constraints?
- At what scale does LoRaWAN become cheaper than Sigfox? (usually ~1,000-2,000 devices)
- Does your application need features (large payloads, frequent updates) that justify higher costs?
Example Answer (for reference): Application: Wine cellar monitoring; 50 devices; 6-byte payload; 24 messages/day; 2 km² vineyard; $30 budget; battery-powered.
Elimination: None eliminated. Sigfox fits (6 bytes < 12, 24/day < 140). LoRaWAN fits. NB-IoT fits.
TCO: - Sigfox: $600 + $250 = $850 - LoRaWAN: $750 + $500 = $1,250 - NB-IoT: $1,000 + $3,000 = $4,000
Decision: Sigfox (if coverage exists) - smallest deployment, lowest cost, simplest. Verify coverage with pilot first.
5.15 Concept Relationships
| Concept | Builds On | Enables | Common Confusion | Real-World Impact |
|---|---|---|---|---|
| Spectrum (Licensed vs Unlicensed) | Radio regulations, ISM bands | Cost model (subscriptions vs free), interference characteristics | Licensed doesn’t mean “better” - just different tradeoffs | NB-IoT $6-12/year fees; LoRaWAN/Sigfox $0-2/year because unlicensed |
| Network Ownership Model | Infrastructure deployment rights | Data sovereignty, coverage control, vendor lock-in | Ownership ≠ technical superiority - operational choice | LoRaWAN private network = full control but maintenance; Sigfox = zero control but zero maintenance |
| Message Frequency Limits | Duty cycle regulations, battery life constraints | Application design (polling vs event-driven) | 140/day isn’t arbitrary - physics + regulation driven | Sigfox hourly reporting = 24/day (safe); every 10 min = 144/day (exceeds limit) |
| Payload Size Constraints | Modulation bandwidth, time-on-air, battery impact | Data encoding strategies (binary vs text) | Larger payloads don’t always need more bandwidth - encoding matters | Sigfox 12 bytes forces binary; LoRaWAN 242 bytes allows JSON (but shouldn’t!) |
| 5-Year TCO Crossover Point | Device count, gateway cost amortization, subscription accumulation | Technology selection at different scales | Cheapest ≠ best - consider operational factors too | <1K devices: Sigfox wins; >10K: LoRaWAN wins; revenue-generating: NB-IoT justifiable |
5.16 See Also
Explore related chapters to deepen your LPWAN expertise:
- LoRaWAN Architecture - Star-of-stars topology, gateway roles, network server functions, device classes
- Sigfox Fundamentals - UNB modulation, operator model, 12-byte encoding strategies, coverage dependencies
- NB-IoT Overview - Cellular LPWAN alternative, licensed spectrum benefits, carrier SLA guarantees
- LPWAN Comparison Matrix - Side-by-side feature comparison, decision frameworks, cost calculations
- LoRaWAN Deployment Guide - Gateway planning, regional parameters, The Things Network setup
Common Pitfalls
LPWAN vendors publish impressive coverage and battery life claims measured under ideal conditions. Always evaluate technology against your specific application requirements: actual data rate, payload size, message frequency, latency tolerance, and deployment geography.
LoRaWAN has lower per-message cost for private deployments but higher upfront infrastructure investment. NB-IoT has no infrastructure cost but recurring cellular subscription fees. Calculate 5-year TCO including hardware, connectivity, maintenance, and personnel for accurate comparison.
Selecting LoRaWAN over NB-IoT doesn’t mean the choice is irreversible. Many hardware platforms now support multiple LPWAN protocols. Design firmware modularity and evaluate multi-protocol hardware to maintain flexibility as technology landscapes evolve.
LoRaWAN and NB-IoT have different ecosystem strengths by vertical market. Check vendor availability, integration libraries, community support, and reference implementations for your specific use case before committing to a technology choice.
5.17 What’s Next
| Direction | Chapter | Focus |
|---|---|---|
| Next chapter | LoRaWAN Network Architecture | Gateways, network servers, and device classes in depth |
| Deep dive | ADR Optimization | Adaptive Data Rate algorithms and duty cycle management |
| Practical | Common Pitfalls | Frequent LoRaWAN deployment mistakes and how to avoid them |
| Compare | Sigfox Fundamentals | Ultra-narrow band modulation and operator model details |
| Compare | NB-IoT Fundamentals | Licensed cellular LPWAN with carrier SLA guarantees |
| Broader view | LPWAN Comparison | Full decision framework across all LPWAN technologies |