13 LPWAN Fundamentals: Introduction
13.1 Low-Power Wide-Area Networks (LPWAN)
In 60 seconds, understand LPWAN:
LPWAN (Low-Power Wide-Area Network) fills the gap between short-range technologies (Wi-Fi, Bluetooth) and expensive cellular networks for IoT applications that need:
- Long range: 2-40 km (vs. 100m for Wi-Fi)
- Long battery life: 5-15 years on a single battery
- Low cost: Cents per message (vs. $5-10/month cellular)
- Small data: Perfect for sensor readings (bytes, not megabytes)
The three main LPWAN technologies:
| Technology | Key Characteristic | Best For |
|---|---|---|
| LoRaWAN | Open standard, build your own network | Private deployments, agriculture, cities |
| Sigfox | Subscription service, ultra-low power | Simple monitoring, no infrastructure |
| NB-IoT/LTE-M | Cellular-based, global coverage | Mission-critical, mobility needed |
The fundamental trade-off: LPWAN sacrifices data rate (0.1-50 kbps) to achieve long range and low power. Perfect for sending “temperature = 23C” hourly, but cannot stream video.
Read on for the full picture, or jump to Real-World Examples to see LPWAN in action.
13.2 Introduction
Low-Power Wide-Area Network (LPWAN) technologies represent a class of wireless communication protocols specifically designed for IoT applications that require long-range connectivity with minimal power consumption. LPWAN fills the gap between short-range technologies (like Wi-Fi and Bluetooth) and traditional cellular networks, enabling battery-powered devices to communicate over distances of several kilometers while lasting years on a single battery.
By the end of this chapter, you will be able to:
- Explain the defining characteristics of LPWAN technologies and why they fill a unique gap in wireless connectivity
- Distinguish the key LPWAN protocols — LoRaWAN, Sigfox, and NB-IoT/LTE-M — by their architecture, spectrum use, and deployment model
- Compare LPWAN with Wi-Fi, Bluetooth, and cellular networks using quantitative parameters (range, data rate, cost)
- Evaluate LPWAN suitability for different IoT applications by applying a structured technology-selection framework
- Calculate link budget and duty cycle capacity to assess whether a deployment design is technically feasible
- Justify technology selection decisions using total cost of ownership analysis across deployment scales
13.3 Prerequisites
Before diving into this chapter, you should be familiar with:
- Networking Basics: Understanding fundamental networking concepts including protocols, topologies, and wireless communication provides essential background for LPWAN technologies
- Mobile Wireless Technologies Basics: Familiarity with cellular and wireless technologies provides useful comparison points for understanding LPWAN’s unique characteristics
- (Optional but helpful) Wireless Sensor Networks: Knowledge of WSN architectures, energy constraints, and deployment strategies helps contextualize LPWAN’s role in large‑scale sensor deployments
- LPWAN Introduction: An overview of Low-Power Wide-Area Network technologies, their place in the IoT connectivity landscape, and why they solve specific problems not addressed by Wi-Fi, Bluetooth, or cellular.
- IoT Connectivity Tiers: The layered view of IoT connectivity: short-range (BLE, Zigbee, Z-Wave), medium-range (Wi-Fi, Thread), long-range (LPWAN, cellular) — each addressing different power/range/data rate tradeoffs.
- Sub-GHz Band: Radio frequencies below 1 GHz (433 MHz, 868 MHz, 915 MHz); used by most LPWAN technologies for better range and building penetration than 2.4 GHz.
13.4 How LPWAN Complements Wi-Fi and Bluetooth
After learning about Wi-Fi Fundamentals and Standards and Bluetooth Fundamentals and Architecture, LPWAN is the third major wireless family to keep in mind. Wi-Fi and Bluetooth focus on short-range, higher data-rate links, while LPWAN trades speed for very long range and multi‑year battery life. As you read this chapter, compare each idea with what you already know from Wi-Fi and Bluetooth to build a connected mental model.
13.5 Sensor Squad: Super Long-Distance Walkie-Talkies!
Meet the Sensor Squad Characters!
- Sammy the Sensor - A curious temperature sensor who loves asking questions
- Lila the Light - A bright and cheerful light sensor who’s always positive
- Max the Motor - An energetic actuator who loves action and movement
- Bella the Button - A helpful input device who’s always ready to respond
Sammy says: “Hey friends! Today we’re learning about LPWAN - it’s like having super-powered walkie-talkies that can reach across a whole city!”
Lila asks: “But Sammy, why can’t we just use Wi-Fi like at home?”
Sammy explains: “Great question, Lila! Imagine you have sensors on a BIG farm - miles away from any house! Wi-Fi only works in one building, and Bluetooth only works in one room. We need something that can talk from REALLY far away!”
13.5.1 What Makes LPWAN Special?
| Regular Wireless | LPWAN |
|---|---|
| Works in one room or house | Works across a whole CITY! |
| Battery lasts days or weeks | Battery lasts for YEARS! |
| Can send lots of data | Sends tiny bits of data |
| Like a fire hose | Like a garden hose (slower but steady) |
13.5.2 The Sensor Squad Farm Adventure
Max shouts: “I love stories! Tell us one!”
Sammy tells the story:
Once upon a time, Farmer Jenny had 100 water sensors spread across a HUGE farm - 10 miles wide! The sensors needed to tell her when plants needed water.
“Let’s try Wi-Fi!” said Lila. But Wi-Fi only reached the barn - way too short!
“What about phone signals?” asked Max. But that cost $5 per sensor per month. With 100 sensors, that’s $500 every month! Too expensive!
“I know!” said Sammy. “Let’s use LPWAN!” Each sensor could whisper tiny messages that traveled 10 miles, using almost no battery power. The sensors worked for 10 YEARS on one tiny battery!
Farmer Jenny was so happy. Now she always knows when her crops need water!
13.5.3 How LPWAN Works (The Whisper Game)
Bella explains: “LPWAN is like playing the whisper game, but you can whisper REALLY far!”
- Sensor whispers: “I’m sensor #7. The soil is dry.”
- Message travels: Through the air for miles and miles…
- Tower listens: A special tower hears all the whispers
- Farmer gets message: “Time to water section 7!”
13.5.4 Where LPWAN Helps
| Place | What LPWAN Does |
|---|---|
| Big farms | Tells farmers when to water crops |
| Cities | Knows when trash cans are full |
| Parking lots | Shows which spots are empty |
| Rivers | Watches water levels to prevent floods |
13.5.5 Lila’s Fun Fact!
Lila says: “Did you know? LPWAN is like my marathon runner friend! While Wi-Fi runs FAST but gets tired quickly, LPWAN goes slowly but can run for YEARS without getting tired. We’re both useful for different jobs!”
13.5.6 Key Words for Kids
| Word | What It Means |
|---|---|
| LPWAN | Special wireless for super long distances |
| LoRa | One type of LPWAN (Lo = Long, Ra = Range) |
| Battery Life | How long a battery lasts before it needs replacing |
| Range | How far a signal can travel |
13.5.7 Try This at Home!
Max challenges you: “Count how many wireless devices are in your home! (Hint: phones, tablets, smart speakers, game controllers…) Now imagine if each one needed to talk from 10 miles away - that’s when you’d need LPWAN!”
13.6 🌱 Getting Started (For Beginners)
13.6.1 The Problem LPWAN Solves
Scenario: You want to monitor 10,000 water meters across a city. Each meter needs to send a small reading (a few bytes) once per day. What technology do you use?
| Technology | Why It Doesn’t Work |
|---|---|
| Wi-Fi | Range only ~100m; would need routers everywhere |
| Bluetooth | Range only ~50m; same problem |
| 4G/5G Cellular | Works, but ~$5-10/month per device = $50,000-100,000/month! |
| Zigbee | Short range, needs mesh network infrastructure |
The Gap: There was no technology for: - ✅ Long range (kilometers, not meters) - ✅ Low cost (cents per message, not dollars per month) - ✅ Low power (batteries lasting years, not weeks) - ✅ Small data (a few bytes per day, not video streaming)
LPWAN fills this gap!
13.6.2 Understanding LPWAN: A Simple Analogy
Analogy: Postcards vs. Phone Calls vs. Texting
| Communication | Technology | Speed | Cost | When to Use |
|---|---|---|---|---|
| Phone call | 4G Cellular | Very fast | Expensive | Long conversations, video |
| Text message | Wi-Fi/BLE | Fast | Medium | Short-range, instant messages |
| Postcard | LPWAN | Very slow | Very cheap | Simple messages, across distances |
LPWAN is like sending postcards:
- 📬 Cheap — Costs almost nothing per message
- 🏔️ Goes far — Works across entire cities, farms, or industrial sites
- ✍️ Short messages — Just a few words (bytes), not entire letters
- 🐢 Slow — Takes time, but that’s okay for sensor readings
13.6.3 The Three Main LPWAN Technologies
Think of these as three competing “postcard services” for IoT:
This chart shows how total cost of ownership evolves: LoRaWAN has high upfront (gateways) but low ongoing costs; Sigfox has moderate costs; NB-IoT subscriptions accumulate significantly over time.
The diagram above shows a side-by-side comparison of the three main LPWAN technologies.
13.6.4 Real-World LPWAN Examples
1. Smart Agriculture 🌾 - Soil moisture sensors across 1000-acre farms - No Wi-Fi, no cellular coverage needed - Battery lasts 5+ years - Sends data once per hour
2. Smart Cities 🏙️ - Parking sensors in every spot - Waste bins signaling when full - Street light monitoring - Water leak detection
3. Asset Tracking 📦 - Shipping container locations - Fleet vehicle monitoring - Equipment tracking in warehouses
4. Utilities 💧 - Smart water meters - Gas meters - Electricity meters - All reading remotely, no meter readers needed!
Question 1: A farmer wants to monitor soil moisture across a 500-acre farm with 200 sensors, each sending readings once per hour. Which LPWAN characteristic makes this feasible?
- High data rate for video streaming
- Long range and low power consumption
- Real-time response capability
- High bandwidth for large file transfers
b) Long range and low power consumption - LPWAN’s key advantage is enabling sensors to communicate over several kilometers while operating for years on a single battery, making large-scale agricultural deployments economically viable.
Question 2: A smart city deploys 50,000 parking sensors. Why would cellular connectivity be problematic for this use case?
- Cellular networks don’t work in cities
- The monthly subscription cost ($5-10/device) would be $250,000-500,000/month
- Cellular signals can’t detect parking occupancy
- Parking sensors need video streaming
b) The monthly subscription cost would be $250,000-500,000/month - At scale, traditional cellular’s per-device subscription model becomes prohibitively expensive. LPWAN technologies like LoRaWAN or Sigfox drastically reduce this cost.
13.6.5 Key Trade-offs: The LPWAN Triangle
You can’t have everything. LPWAN trades speed for range and battery life:
What this means:
- ✅ Perfect for sending “temperature = 23°C” once per hour
- ❌ Cannot stream video
- ❌ Cannot send large files
- ❌ Cannot support real-time interactive apps
13.6.6 LPWAN End-to-End Architecture
Before diving into the protocol stack, let’s visualize how LPWAN fits into a complete IoT system from sensor to cloud:
Figure: LPWAN End-to-End Architecture - sensors communicate over long distances via LPWAN to gateways/base stations, which forward data through network servers to cloud applications.
Key architectural components:
- End Devices: Battery-powered sensors with LPWAN radios (LoRa, Sigfox, or cellular modem)
- Gateways/Base Stations: Bridge between LPWAN and IP networks (LoRaWAN gateways are typically user-deployed; NB-IoT uses cellular infrastructure)
- Network Server: Manages device authentication, deduplication, and routing
- Application Server: Processes sensor data and provides APIs for dashboards and analytics
13.6.7 LPWAN Protocol Stack Architecture
Understanding where LPWAN fits in the networking stack helps clarify its role in IoT systems. The following diagram shows the typical LPWAN protocol stack compared to traditional IP networking:
Figure: LPWAN Protocol Stack - showing how different LPWAN technologies (LoRaWAN, Sigfox, NB-IoT) implement the physical and MAC layers while potentially sharing upper layer protocols.
Key observations from the stack:
- Physical Layer diversity: Each LPWAN technology uses different modulation (CSS for LoRa, UNB for Sigfox, OFDM for NB-IoT)
- MAC Layer differences: Protocol-specific addressing, duty cycling, and channel access mechanisms
- Network Layer flexibility: LoRaWAN and NB-IoT support IPv6; Sigfox uses proprietary networking
- Application Layer commonality: All can ultimately deliver sensor data to cloud platforms
Question 3: A company needs to track high-value shipping containers with GPS updates every 5 minutes during transport across multiple countries. Which LPWAN technology would be MOST suitable?
- LoRaWAN - because it’s open standard
- Sigfox - because it has the lowest power consumption
- NB-IoT/LTE-M - because it provides mobility support and global roaming
- Wi-Fi - because it has the highest data rate
c) NB-IoT/LTE-M - For mobile asset tracking across countries, cellular-based LPWAN (NB-IoT or especially LTE-M which supports handover) is ideal because it leverages existing cellular infrastructure for global coverage and supports mobility, unlike LoRaWAN or Sigfox which are optimized for stationary or slow-moving devices.
Question 4: An IoT engineer is designing a system where sensors need to send 100 KB images twice per day. Is LPWAN suitable for this application?
- Yes, LPWAN can handle any data size
- No, LPWAN is optimized for small payloads (typically < 250 bytes) and would struggle with 100 KB transmissions
- Yes, but only if using NB-IoT
- Yes, but only at night when network traffic is low
b) No, LPWAN is optimized for small payloads - LPWAN technologies are designed for transmitting small amounts of data (typically 12-250 bytes per message). Sending 100 KB would require hundreds of transmissions, consume excessive battery, and violate duty cycle regulations. For image transmission, consider Wi-Fi with edge processing to reduce data size, or cellular connectivity.
13.6.8 Common Pitfalls and Misconceptions
Pitfall 1: “LPWAN can replace Wi-Fi”
- Reality: LPWAN and Wi-Fi serve completely different purposes. Wi-Fi is for high-bandwidth local connectivity; LPWAN is for low-bandwidth wide-area sensor data. You cannot stream video or browse the web over LPWAN.
Pitfall 2: “All LPWAN technologies are the same”
- Reality: LoRaWAN, Sigfox, and NB-IoT have fundamentally different architectures, cost models, and use cases. Choosing the wrong one can result in 10x higher costs or deployment failures.
Pitfall 3: “LPWAN means no infrastructure needed”
- Reality: Only Sigfox and NB-IoT use operator-managed networks. LoRaWAN requires deploying your own gateways (or using a public network if available). Budget for infrastructure accordingly.
Pitfall 4: “Battery life is always 10+ years”
- Reality: Battery life depends heavily on transmission frequency, payload size, and environmental factors. Sending data every minute instead of every hour can reduce battery life from 10 years to 1 year.
Pitfall 5: “LPWAN is always the cheapest option”
- Reality: For small deployments (<100 devices) with existing cellular coverage, NB-IoT might be cheaper than deploying LoRaWAN infrastructure. Always calculate TCO for your specific scale.
13.6.9 Quick Check: LPWAN Fundamentals
13.6.10 Self-Check: Understanding the Basics
Before continuing, make sure you can answer:
- What gap does LPWAN fill? → Long-range, low-power, low-cost connectivity for small data transfers
- Why not just use 4G cellular for IoT sensors? → Too expensive for thousands of devices sending small amounts of data
- What is the main trade-off of LPWAN? → Very slow data rates in exchange for long range and low power
- Name the three main LPWAN technologies → LoRaWAN (open, build your own), Sigfox (proprietary network), NB-IoT (cellular-based)
The Gap (2008-2010): By 2010, IoT visionaries faced a fundamental connectivity problem. Wi-Fi offered only ~100m range and consumed too much power for battery-operated sensors. Cellular networks (2G/3G) provided coverage but cost $5-15 per device per month and drained batteries in days. Zigbee and 802.15.4 required complex mesh networks. The industry needed something new: 10+ km range, 10-year battery life, and connectivity costs under $1 per year.
Proprietary Pioneers (2009-2012):
Sigfox (France, 2009): Ludovic Le Moan and Christophe Fourtet invented Ultra-Narrowband (UNB) technology, transmitting at just 100 bps in the unlicensed 868 MHz band. By using extremely narrow 100 Hz channels, Sigfox achieved remarkable sensitivity (-142 dBm) enabling 40+ km range with minimal power. First commercial network launched in France in 2012.
LoRa (France, 2010): Cycleo developed Chirp Spread Spectrum (CSS) modulation, later acquired by Semtech in 2012. LoRa spreads signals across wide bandwidth, achieving -137 dBm sensitivity and interference resistance. The open LoRaWAN protocol (2015) enabled private network deployment.
Cellular Response (2015-2016): Threatened by proprietary LPWAN, cellular operators pushed 3GPP to standardize:
- NB-IoT (Release 13, 2016): Narrowband IoT operating in 180 kHz channels within licensed LTE spectrum. Peak downlink 26 kbps / uplink 62 kbps, optimized for stationary sensors.
- LTE-M (Release 13, 2016): Cat-M1 supporting 1 Mbps and mobility, ideal for asset tracking.
Both leverage existing cell tower infrastructure, offering global roaming and carrier-grade reliability.
Ecosystem Explosion (2017-2020):
| Year | Milestone |
|---|---|
| 2017 | LoRaWAN Alliance reaches 500 members; Sigfox covers 45 countries |
| 2018 | NB-IoT deployments exceed 100 networks worldwide |
| 2019 | LoRaWAN roaming specification published; Semtech ships 100M+ LoRa chips |
| 2020 | COVID accelerates smart building/healthcare IoT; 1.5B LPWAN connections projected by 2025 |
Convergence Era (2021-Present):
- Multi-protocol gateways: Single devices supporting LoRaWAN + NB-IoT + Wi-Fi
- Satellite integration: Lacuna Space, Swarm, and Amazon Sidewalk extend coverage to remote areas
- Amazon Sidewalk (2021): 900 MHz mesh network using Ring doorbells and Echo devices as gateways
- LoRa Edge: Combines LoRa with GPS/Wi-Fi scanning for ultra-low-power asset tracking
- Matter over Thread: Smart home standard leveraging 802.15.4 alongside LPWAN for IoT ecosystem integration
Key Metrics That Drove LPWAN Adoption:
| Metric | Wi-Fi (2010) | 3G Cellular (2010) | LPWAN Target | LPWAN Achieved (2020) |
|---|---|---|---|---|
| Range | 100m | 10 km | 10+ km | 15-40 km (rural) |
| Battery Life | Hours-days | Hours | 10 years | 10-15 years |
| Module Cost | $10 | $25+ | $5 | $2-5 |
| Connectivity/year | $0 (local) | $60-180 | $1 | $0-2 (LoRa), $12-60 (cellular) |
| Data Rate | 54 Mbps | 2 Mbps | 1-50 kbps | 0.1-50 kbps |
Why This Matters: LPWAN did not just fill a gap—it created an entirely new category of connectivity that enabled previously impossible IoT deployments. Smart agriculture across thousand-hectare farms, city-wide utility metering, and global asset tracking became economically viable only because LPWAN solved the range/power/cost equation that Wi-Fi and cellular could not. Understanding this history helps explain why multiple LPWAN technologies coexist: each emerged to solve slightly different variations of the same fundamental problem.
13.7 Worked Example: Urban Water Utility — LPWAN Technology Selection for 50,000 Smart Meters
Scenario: AquaCity Water serves a mid-sized European city (population 320,000, area 85 km2). They plan to replace manual meter reading with LPWAN-connected smart water meters across 50,000 residential and 2,400 commercial customers. The project must select between LoRaWAN, Sigfox, and NB-IoT based on coverage, cost, and operational requirements.
Requirements:
| Requirement | Value | Why |
|---|---|---|
| Coverage | 85 km2 urban + 15 km2 suburban fringe | Full city boundary |
| Meter locations | 60% in basements, 25% in meter pits, 15% outdoor | Deep indoor penetration needed |
| Reporting interval | Every 6 hours (residential), every 15 min (commercial) | Leak detection for commercial |
| Payload per reading | 12 bytes (meter ID + flow + timestamp + battery) | Minimal data |
| Battery life target | 10+ years (residential), 5+ years (commercial) | Avoid truck rolls |
| Downlink needed | Monthly config updates + on-demand reads | Billing cycle changes |
| Budget (connectivity) | < EUR 2.50/meter/year for residential | City council constraint |
Step 1 — Coverage analysis:
LoRaWAN (868 MHz, SF12, 125 kHz BW):
MCL = 157 dB (max coupling loss)
Gateway TX: 27 dBm EIRP (EU868 limit)
Link budget: 27 + 157 = device can be at -130 dBm
Urban range: 3-5 km per gateway (buildings, multipath)
Basement penetration loss: -22 dB (concrete + soil)
Effective range to basement meters: 1.5-2.5 km
Gateways needed: 85 km2 / (pi x 2^2) = ~7 gateways (plus 3 for fringe)
Total: 10 gateways
Sigfox (868 MHz, DBPSK, 100 Hz BW):
MCL = 162 dB (5 dB better than LoRaWAN due to ultra-narrow bandwidth)
Base station range: 5-8 km urban
Basement penetration: similar physics, but 5 dB margin helps
Effective range to basement: 2-4 km
Sigfox operator has 6 base stations in city (pre-existing)
Coverage claim: 95% outdoor, 82% deep indoor
NB-IoT (Band 20, 800 MHz):
MCL = 164 dB (best of three)
eNodeB range: 5-10 km urban with CE Mode B (2048 repetitions)
Basement penetration: -22 dB absorbed by MCL margin
Carrier has 14 macro cells covering city
Coverage claim: 98% outdoor, 91% deep indoorStep 2 — Cost comparison (5-year TCO for 52,400 meters):
| Cost Factor | LoRaWAN | Sigfox | NB-IoT |
|---|---|---|---|
| Module cost/meter | EUR 4.50 | EUR 3.80 | EUR 6.20 |
| Module total | EUR 235,800 | EUR 199,120 | EUR 324,880 |
| Connectivity/meter/year | EUR 0 (own network) | EUR 1.00 (subscription) | EUR 1.80 (carrier SIM) |
| Connectivity 5 years | EUR 0 | EUR 262,000 | EUR 471,600 |
| Infrastructure | 10 gateways x EUR 2,500 = EUR 25,000 | EUR 0 (operator) | EUR 0 (carrier) |
| Gateway hosting (5 yr) | 10 sites x EUR 600/yr x 5 = EUR 30,000 | EUR 0 | EUR 0 |
| Network server | EUR 12,000/yr x 5 = EUR 60,000 | Included | Included |
| 5-Year Total | EUR 350,800 | EUR 461,120 | EUR 796,480 |
| Per meter/year | EUR 1.34 | EUR 1.76 | EUR 3.04 |
Step 3 — Operational requirements comparison:
| Requirement | LoRaWAN | Sigfox | NB-IoT |
|---|---|---|---|
| Basement coverage (60%) | 10 gateways cover 94% | 82% (6 base stations) | 91% (14 eNodeBs) |
| 15-min commercial reads | Duty cycle limited: EU868 allows 36 s/hr TX per sub-band = OK at 12 bytes | Max 140 uplinks/day = 1 every 10.3 min = marginal | No duty cycle limit = OK |
| Downlink config updates | 1 downlink per uplink in Class A | Max 4 downlinks/day = insufficient for on-demand | Full bidirectional = OK |
| On-demand meter reads | Requires Class C (always listening, no battery saving) or Class B (beacon window) | Not supported (4 DL/day) | Supported via eDRX paging |
| Battery life (residential) | SF12, 6-hour cycle: 12+ years | Ultra-low TX power: 15+ years | PSM + T3412=6h: 10+ years |
| Battery life (commercial) | SF10, 15-min cycle: 4.2 years | 15-min uplinks = 96/day (within 140 limit): 8+ years | eDRX 15-min: 5.1 years |
Step 4 — Decision matrix:
| Factor | Weight | LoRaWAN Score | Sigfox Score | NB-IoT Score |
|---|---|---|---|---|
| 5-year cost | 30% | 9 (cheapest) | 7 | 4 |
| Basement coverage | 25% | 8 (94%) | 6 (82%) | 8 (91%) |
| Downlink capability | 20% | 6 (Class A limited) | 2 (4/day max) | 9 (full bidir) |
| Battery life (residential) | 15% | 9 (12+ yr) | 10 (15+ yr) | 8 (10+ yr) |
| Battery life (commercial) | 10% | 5 (4.2 yr) | 7 (8+ yr) | 6 (5.1 yr) |
| Weighted Total | 7.65 | 5.95 | 6.55 |
Decision: LoRaWAN selected as primary technology. However, the 82 commercial sites requiring 15-minute reads and on-demand billing reads will use NB-IoT (better downlink and no duty cycle limit). This hybrid approach costs:
50,000 residential meters on LoRaWAN: EUR 1.34/meter/year = EUR 67,000/year
2,400 commercial meters on NB-IoT: EUR 3.04/meter/year = EUR 7,296/year
Total: EUR 74,296/year = EUR 1.42/meter/year blended
vs all-NB-IoT: EUR 159,296/year (2.1x more expensive)
vs all-Sigfox: EUR 92,224/year (insufficient downlink for commercial)Key lessons:
- No single LPWAN technology wins on all axes. LoRaWAN dominates on cost for high-volume one-way reporting, but NB-IoT wins for bidirectional commercial meters. Sigfox’s 4-downlink-per-day limit disqualified it for on-demand reads.
- Basement coverage drives infrastructure cost. LoRaWAN needed 10 gateways (EUR 25,000) specifically because 60% of meters are in basements. Outdoor-only deployments would need only 4 gateways.
- Duty cycle regulations are a hard constraint in Europe. EU868 allows 36 seconds of TX per hour per sub-band. At SF12 (1.3 s per 12-byte uplink), that is 27 transmissions per hour — adequate for 15-minute intervals but leaving only 50% headroom for retransmissions.
:
13.8 What’s Next
Now that you can explain the LPWAN gap, compare the three dominant technologies, and calculate link budgets and duty cycle capacity, the following chapters build directly on these foundations.
| Chapter | Focus | Why Read It |
|---|---|---|
| LoRaWAN Overview | LoRa modulation, LoRaWAN network architecture, Class A/B/C devices, Adaptive Data Rate, and end-to-end security | Apply the technology-selection skills from this chapter to understand when and how LoRaWAN is configured and deployed at scale |
| Sigfox Fundamentals | Ultra-Narrowband (UNB) modulation, Sigfox’s global operator network model, 140-uplink/day limit, and SIGFOX backend API | Distinguish Sigfox’s operator-managed architecture from the private-network model of LoRaWAN and assess trade-offs for simple monitoring use cases |
| Cellular IoT Fundamentals | NB-IoT and LTE-M 3GPP specifications, PSM/eDRX power-saving modes, global roaming, and carrier integration | Evaluate when licensed-spectrum cellular IoT outperforms unlicensed LPWAN — especially for mobility, bidirectional communication, and mission-critical reliability |
| LPWAN Architectures | Gateway placement strategies, star-of-stars topology, redundancy, roaming between networks, and scaling to thousands of devices | Construct complete deployment designs by applying the link budget and capacity calculations introduced in this chapter |
| Application Protocols Overview | MQTT, CoAP, and HTTP/REST as the application layer used above LPWAN | Analyse how application-layer protocol choice affects battery life, server load, and data latency in LPWAN deployments |
| LPWAN Selection Tools | Decision tree and quantitative comparison matrix for LoRaWAN vs Sigfox vs NB-IoT | Select the optimal technology for any given IoT scenario using a structured framework rather than intuition alone |
13.8.1 Practice Activities
To solidify your understanding, try these activities:
Cost Calculator Exercise: Calculate the 5-year TCO for a 1,000-device deployment using each LPWAN technology. Consider device costs, connectivity fees, and infrastructure investment.
Use Case Mapping: Take a real-world IoT application (smart agriculture, fleet tracking, utility metering) and evaluate which LPWAN technology would be optimal and why.
Technology Comparison: Create a decision matrix for your organization comparing LoRaWAN, Sigfox, and NB-IoT across 10 criteria important to your use case.
This chapter provided the foundational understanding of LPWAN technologies. The subsequent chapters will build on these concepts with detailed technical specifications, implementation guides, and hands-on examples for each LPWAN technology.