24  LPWAN Technology Selection

In 60 Seconds

This comprehensive LPWAN comparison covers four technologies across key parameters: LoRaWAN (0.3-50 kbps, 243-byte payloads, private network option), Sigfox (100 bps, 12-byte limit, 140 messages/day), NB-IoT (up to 159 kbps UL / 127 kbps DL, deep indoor coverage, carrier SLA), and LTE-M (1 Mbps, vehicular mobility, voice support). Use the decision frameworks and market analysis here to select the right technology for your deployment.

24.1 Introduction

This chapter provides a comprehensive comparison of LPWAN technologies including LoRaWAN, Sigfox, NB-IoT, and LTE-M. You’ll learn how to select the right technology for your IoT application based on technical requirements, cost constraints, and deployment models.

Learning Objectives

• Compare LoRaWAN, Sigfox, NB-IoT, and LTE-M across key technical parameters including data rate, range, and power consumption
• Analyze LPWAN market landscape and regional adoption patterns to identify dominant technologies by geography
• Apply decision frameworks to select the appropriate LPWAN technology for a given IoT deployment scenario
• Evaluate trade-offs between private and operator-managed deployment models based on total cost of ownership
• Calculate break-even points and 10-year TCO when comparing gateway-based and subscription-based LPWAN options
• Distinguish the defining constraints of each technology (Sigfox payload limits, LoRaWAN duty cycles, NB-IoT mobility restrictions, LTE-M power budget)

Key Concepts

• Technology Comparison Matrix: A structured table comparing LoRaWAN, NB-IoT, Sigfox, and LTE-M across key dimensions: frequency, range, data rate, battery life, message limits, and deployment model.
• Downlink Comparison: LoRaWAN Class A: two short receive windows per uplink; NB-IoT: always available downlink; Sigfox: 4 downlink messages/day maximum — downlink capability varies significantly.
• Regulatory Framework Comparison: LoRaWAN/Sigfox: unlicensed ISM bands with duty cycle limits; NB-IoT/LTE-M: licensed spectrum with no duty cycle limits but carrier dependency.

24.2 For Beginners: LPWAN Technology Selection

With multiple LPWAN options available, selecting the right one requires understanding each technology’s trade-offs. This chapter provides comparison frameworks and decision tools to help you evaluate LoRaWAN, Sigfox, NB-IoT, and emerging alternatives based on your specific IoT deployment requirements.

Sensor Squad: The LPWAN Olympics

“If LPWAN technologies were Olympic athletes, which would win which events?” asked Lila the LED playfully.

Max the Microcontroller played along: “Range event: Sigfox wins the gold medal – it can reach 50 km in ideal conditions! LoRaWAN gets silver at 15 km, and NB-IoT gets bronze, limited by cell tower placement.”

“Battery endurance: All three are marathon runners,” said Bella the Battery, “but Sigfox has a slight edge because its uplink-only design is the simplest. LoRaWAN Class A is a close second. NB-IoT uses slightly more power due to cellular synchronization overhead.”

Sammy the Sensor assigned the data event: “Data throughput: NB-IoT dominates with hundreds of kilobytes per day. LoRaWAN handles a few kilobytes. Sigfox is limited to 1,680 bytes per day (140 messages of 12 bytes). And the emerging technologies like mioty and DASH7 are the rising stars – watch out for them in the next LPWAN Olympics!”

24.3 LPWAN Technology Comparison

⏱️ ~15 min | ⭐⭐ Intermediate | 📋 P09.C01.U03

This section provides a comprehensive comparison of LPWAN technologies to help you select the right solution for your application.

24.3.1 LPWAN Market Landscape

The LPWAN market has grown rapidly, with distinct adoption patterns across technologies:

Figure 24.1: LPWAN market share by technology in 2024

Key Market Statistics (2024):

Metric	Value	Growth
Total LPWAN Connections	~2.5 billion devices globally	+25% YoY
LPWAN Market Size	~$15 billion annually	Projected $65B by 2030
LoRaWAN Networks	200+ national networks in 180+ countries	+40% gateways YoY
NB-IoT Coverage	100+ countries, 180+ operators	Dominant in China (~70% of global NB-IoT)
Sigfox Coverage	~70 countries	Restructured after 2022 bankruptcy

Regional Adoption Patterns:

• Asia-Pacific: NB-IoT dominates (China’s massive rollout with 1B+ connections)
• Europe: LoRaWAN leads in private deployments; NB-IoT growing in utilities
• North America: LTE-M strongest; LoRaWAN popular for enterprise/agriculture
• Latin America/Africa: Sigfox historically strong; LoRaWAN expanding

Market Insight: The “Co-opetition” Trend

Rather than winner-take-all, the market is trending toward multi-technology deployments: - 60% of large enterprises plan to use 2+ LPWAN technologies by 2026 - LoRaWAN for private campus networks and dense deployments - NB-IoT/LTE-M for mobile assets and carrier-grade coverage - Chip vendors (Nordic, Qualcomm) now offer multi-protocol modules

24.3.2 Technology Architecture Comparison

Side-by-side comparison of three LPWAN architectures. LoRaWAN shows end devices connecting to user-deployed or public gateways, which connect via IP to network servers and application servers. Sigfox shows devices connecting to operator-only base stations through managed cloud to application APIs. NB-IoT shows devices connecting to carrier eNodeB base stations through EPC/5GC core network to application platforms.

Figure 24.2: LPWAN architecture comparison showing deployment models: LoRaWAN (private/public gateways), Sigfox (operator-only infrastructure), and NB-IoT (cellular carrier deployment)

24.3.3 Comprehensive Technology Comparison Table

The following table provides a detailed comparison across all critical parameters:

Parameter	LoRaWAN	Sigfox	NB-IoT	LTE-M
Network & Deployment
Deployment Model	Public/Private	Operator Only	Carrier Only	Carrier Only
Spectrum	Unlicensed ISM	Unlicensed ISM	Licensed LTE	Licensed LTE
Standard	LoRa Alliance	Proprietary	3GPP Release 13+	3GPP Release 13+
Global Coverage	Depends on deployment	~70 countries	~100 countries	~90 countries
Technical Specifications
Frequency Bands	868 MHz (EU) 915 MHz (US)	868 MHz (EU) 902 MHz (US)	LTE Bands (700-2100 MHz)	LTE Bands (700-2100 MHz)
Modulation	CSS (LoRa)	DBPSK/GFSK	OFDMA/SC-FDMA	OFDMA/SC-FDMA
Data Rate (UL)	0.3-50 kbps	100 bps	Up to 159 kbps (Rel.14)	Up to 1 Mbps
Data Rate (DL)	0.3-50 kbps	600 bps	Up to 127 kbps (Rel.14)	Up to 1 Mbps
Max Payload	243 bytes	12 bytes (UL) 8 bytes (DL)	1600 bytes	1600 bytes
Range & Coverage
Urban Range	2-5 km	3-10 km	1-10 km	1-10 km
Rural Range	5-15 km	10-40 km	10-35 km	10-35 km
Indoor Penetration	Good (20 dB)	Excellent (25+ dB)	Excellent (20+ dB)	Excellent (20+ dB)
Power & Battery
TX Power	14 dBm (25 mW)	14-27 dBm	23 dBm (200 mW)	23 dBm (200 mW)
RX Current	10-15 mA	10-12 mA	40-60 mA	40-80 mA
Sleep Current	1-5 μA	1-3 μA	3-5 μA	5-15 μA
Battery Life	5-10 years	10-20 years	5-10 years	3-7 years
PSM Support	Native sleep (Class A)	No	Yes (3GPP PSM)	Yes (3GPP PSM)
eDRX Support	No	No	Yes	Yes
Communication
Topology	Star-of-Stars	Star	Star	Star
Bi-directional	Yes (All Classes)	Limited (4 DL/day)	Yes (Full)	Yes (Full)
Acknowledgements	Optional (Confirmed)	No (Unconfirmed)	Yes (RLC/MAC)	Yes (RLC/MAC)
Latency	1-2 seconds	2-10 seconds	1.6-10 seconds	10-15 ms
QoS Guarantee	No	No	Yes (Bearer QoS)	Yes (Bearer QoS)
Capacity & Limits
Messages/Day	Unlimited*	140 UL / 4 DL	Unlimited	Unlimited
Devices/Gateway	~10,000	N/A (Operator)	~50,000/cell	~50,000/cell
Adaptive Data Rate	Yes (ADR)	No	No	No
Handover/Mobility	No	No	Limited	Full (50+ km/h)
Cost (Typical)
Module Cost	$8-15	$5-10	$10-20	$15-25
Gateway Cost	$500-2000/GW	N/A	N/A	N/A
Subscription/Year	$1-5/device (or free private)	$1-10/device	$2-12/device	$3-15/device
Infrastructure	DIY or Cloud	Operator	Operator	Operator
Best Use Cases
Ideal Applications	Smart agriculture Smart buildings Private IoT networks Asset tracking (local)	Simple sensors Utility meters Environmental monitoring Low-frequency alarms	Smart meters Street lighting Fixed asset tracking Parking sensors	Fleet tracking Wearables Mobile sensors Voice-enabled IoT
Limitations
Key Constraints	Duty cycle (1%) Coverage gaps No mobility support	12-byte payload 140 msg/day limit No guaranteed delivery	Higher power Carrier dependency Module cost	Highest power Higher cost Carrier dependency

* Subject to regional duty cycle regulations (e.g., 1% in EU)

Table Notes

• Data rates are peak theoretical values. LoRaWAN depends on spreading factor (SF7 = 50 kbps, SF12 = 0.3 kbps). NB-IoT figures are 3GPP Release 14 peaks (Release 13 baseline: ~26 kbps DL / ~62 kbps UL). Actual rates depend on coverage conditions and network load
• Battery life estimates assume 1-2 messages/day; actual lifetime varies with message frequency, payload size, and environmental conditions
• Costs are approximate 2025 values and vary by region, volume, and service provider
• Coverage figures assume good conditions; urban environments and interference reduce effective range

Putting Numbers to It

How do LoRaWAN’s duty cycle limits compare to Sigfox’s message limits for a real application? Consider a flood sensor that sends a 30-byte alert every 5 minutes during a flood event (lasting 6 hours).

Sigfox regulatory limit:

• Maximum 140 uplink messages per day
• Flood event requires: \(\frac{6 \text{ hours} \times 60 \text{ min}}{5 \text{ min/msg}} = 72 \text{ messages}\) ✅ (within limit)
• Daily allowance remaining: \(140 - 72 = 68\) messages

LoRaWAN duty cycle (EU 868 MHz):

• 1% duty cycle = \(0.01 \times 3600 \text{ sec/hour} = 36 \text{ sec/hour}\) on-air time
• Time-on-air (30 bytes at SF7): ~56 ms per message
• Messages per hour: \(\frac{36 \text{ sec}}{0.056 \text{ sec}} \approx 643 \text{ msg/hour}\) ✅
• 6-hour flood event: \(72 \text{ messages} \times 0.056 \text{ sec} = 4.0 \text{ sec}\) (11% of 36 sec/hour allowance)

TX power difference:

• LoRaWAN: 14 dBm = 25 mW = \(25 \text{ mW} \times 0.056 \text{ sec} = 1.4 \text{ mWs per message}\)
• Sigfox: 14-27 dBm (up to 500 mW for extended range) = \(500 \text{ mW} \times 6 \text{ sec} = 3,000 \text{ mWs}\)

Key insight: Sigfox uses ~2,100x more energy per message due to longer transmission time (6 sec vs 56 ms), but its 140 msg/day limit is the real constraint for high-frequency applications. LoRaWAN’s duty cycle allows 643x more messages while using 2,100x less energy per message.

24.3.4 LPWAN Coverage vs Power Trade-offs (Variant View)

This radar chart provides an alternative visualization of LPWAN technology trade-offs across five critical dimensions:

Figure 24.3: LPWAN technology comparison showing trade-off profiles across range, battery life, data rate, reliability, and cost efficiency. Each technology excels in different dimensions: Sigfox maximizes range and battery life, LTE-M leads in data rate and reliability, LoRaWAN balances flexibility and cost, NB-IoT offers carrier-grade reliability with moderate power.

24.3.5 LPWAN Technology Selection Flowchart

Use this decision tree to select the most appropriate LPWAN technology for your application:

Flowchart for selecting LPWAN technology. Starts with coverage model decision (nationwide vs regional). Branches through private network preference, payload size (>12 bytes), message frequency (>140/day), mobility, data rate, and battery priority to recommend LoRaWAN (private/flexible), Sigfox (simple/long battery), NB-IoT (fixed assets/reliable), or LTE-M (mobile/higher speed).

Figure 24.4: Decision flowchart for LPWAN technology selection based on coverage model, payload size, message frequency, mobility, and battery requirements

Using the Decision Flowchart

How to use this flowchart:

1. Start with your primary requirement (coverage area)
2. Follow the decision path based on your application’s constraints
3. Review the recommended technology and its key benefits
4. Validate the choice against all your requirements

Common Decision Paths:

• Smart Agriculture → Private Coverage → Large Payload → High Frequency → LoRaWAN
• Simple Sensors → Private Coverage → Small Payload → Low Frequency → Long Battery → Sigfox (if available)
• Asset Tracking → Global Coverage → Mobile → Medium Data Rate → LTE-M
• Smart Meters → Global Coverage → Fixed → Low Power → NB-IoT

Multiple Technologies:

Some applications may benefit from using multiple LPWAN technologies: - Hybrid deployments: LoRaWAN for dense urban areas + NB-IoT for remote locations - Failover: Primary technology with cellular backup for critical messages - Cost optimization: Sigfox for bulk of devices + LoRaWAN for high-frequency nodes

24.3.6 LPWAN Use Case Decision Matrix (Variant View)

This matrix visualization provides an alternative perspective by mapping specific IoT use cases to optimal LPWAN technologies based on message requirements and cost constraints:

Figure 24.5: LPWAN use case decision matrix mapping common IoT applications to optimal technology choices. Each use case shows key requirements (payload, frequency, constraints) and rates technologies as optimal (checkmark), acceptable (circle), or unsuitable (X).

24.3.7 Quick Selection Guide

For rapid technology selection, use these rules of thumb:

Technology Selection Rules

Choose LoRaWAN when:

• ✅ You need private network control
• ✅ Payload > 12 bytes OR messages > 140/day
• ✅ Regional/local deployment is sufficient
• ✅ Want flexibility and no vendor lock-in
• ✅ Have technical team to manage infrastructure

Choose Sigfox when:

• ✅ Ultra-simple, low-cost deployment needed
• ✅ Payload ≤ 12 bytes AND messages ≤ 140/day
• ✅ Maximum battery life (10-20 years) required
• ✅ Sigfox coverage exists in deployment region
• ✅ Minimal bidirectional communication needed

Choose NB-IoT when:

• ✅ Need global carrier-grade reliability
• ✅ Fixed or slow-moving devices
• ✅ Require guaranteed message delivery (QoS)
• ✅ Battery life 5-10 years is acceptable
• ✅ Can afford carrier subscription costs

Choose LTE-M when:

• ✅ Devices are mobile (vehicles, wearables)
• ✅ Need voice capability or high data rates (>100 kbps)
• ✅ Low latency required (<100 ms)
• ✅ Can tolerate higher power consumption
• ✅ Cellular coverage is reliable in operating region

Quick Check: Technology Selection Rules

24.4 Worked Example: Hybrid LPWAN Deployment for a Utility Company

Worked Example: Dual-Technology Smart Water Network

Scenario: A water utility manages infrastructure across both a dense urban core (450,000 residential meters) and a rural distribution network (12 pump stations spread over 80 km of pipeline with pressure and flow sensors). The utility needs a single IoT platform covering both environments.

Given:

• Urban meters: 450,000 units, basement-mounted, reading every 6 hours, 32-byte payload
• Rural stations: 12 pump houses with 8 sensors each (96 sensors total), 64-byte payload every 5 minutes
• Requirement: 99.9% message delivery for pump alarms; best-effort for meter readings
• Budget: 10-year TCO must not exceed $18M

Step 1: Match technology to environment

Requirement	Urban Meters	Rural Stations
Coverage	Deep indoor (basements)	5-15 km open terrain
Payload	32 bytes	64 bytes
Frequency	4/day	288/day
Reliability	Best-effort OK	99.9% required
Infrastructure	Cellular towers exist	No cell coverage
Best fit	NB-IoT	LoRaWAN

Step 2: Calculate urban TCO (NB-IoT)

• Module cost: 450,000 x $12 = $5,400,000
• Installation: 450,000 x $8 (self-install clip) = $3,600,000
• Subscription: 450,000 x $1.20/year x 10 years = $5,400,000
• Total urban: $14,400,000

Step 3: Calculate rural TCO (LoRaWAN)

Putting Numbers to It

How many gateways do we need for 80 km of pipeline with 12 pump stations?

Gateway placement calculation:

• Pipeline length: 80 km (linear infrastructure)
• LoRaWAN rural range: 5-15 km typical
• With line-of-sight: assume 10 km effective range per gateway
• Coverage overlap required: 20% (for redundancy)
• Effective range per gateway: \(10 \text{ km} \times (1 - 0.20) = 8 \text{ km}\)
• Gateways needed: \(\frac{80 \text{ km}}{8 \text{ km/gateway}} = 10 \text{ gateways}\)

Reality check with pump station locations:

• 12 pump stations spread over 80 km = average spacing of 6.7 km
• Co-locate gateways at pump stations (infrastructure already exists: power, shelter, maintenance access)
• Coverage redundancy: Each sensor typically sees 2-3 gateways
• Gateway count reduced from theoretical 10 to practical 8 by optimizing placement at existing infrastructure

Why 8 is sufficient:

• Sensors at each pump station: \(12 \times 8 = 96\) sensors (all devices)
• Each gateway covers \(\pi r^2 = \pi (10 \text{ km})^2 \approx 314 \text{ km}^2\)
• Pipeline corridor width: ~200 m = 0.2 km
• Actual coverage needed: \(80 \text{ km} \times 0.2 \text{ km} = 16 \text{ km}^2\) << 314 km²
• Result: Massive coverage redundancy - every point sees 3-4 gateways

• Sensors: 96 x $25 = $2,400
• Gateways (8 for coverage): 8 x $1,200 = $9,600
• Solar+battery per gateway: 8 x $600 = $4,800
• Network server: $200/month x 120 months = $24,000
• Installation: 8 sites x $2,000 = $16,000
• Total rural: $56,800

Step 4: Combined TCO

• NB-IoT urban: $14,400,000
• LoRaWAN rural: $56,800
• Platform integration: $150,000
• Total: $14,606,800 (under $18M budget)

Why not a single technology?

• LoRaWAN for 450,000 urban meters would require ~900 gateways at $1.08M plus installation, BUT basement penetration is unreliable without extremely dense gateway placement. NB-IoT’s licensed spectrum provides guaranteed indoor coverage.
• NB-IoT for rural stations is impossible – no cell towers within 20 km of 5 pump houses. LoRaWAN’s private gateway model solves this.

Key Insight: Multi-technology deployments are not a compromise – they are often the optimal architecture. The utility saves approximately $3M compared to forcing NB-IoT everywhere (satellite backhaul costs for rural) while achieving better reliability than forcing LoRaWAN everywhere (basement coverage gaps). The integration cost ($150,000) is less than 1% of total TCO.

Common Pitfalls

1. Using Vendor-Provided Comparison Data Without Checking Conditions

Technology comparison data from vendor materials uses favorable test conditions. Compare technologies using data from independent third-party studies and real deployment reports.

2. Focusing Only on Radio Comparison, Ignoring Ecosystem

Radio performance is one dimension of technology selection. Ecosystem factors — available modules, network operators, cloud platform integration, developer tools — often matter more for product success.

Label the Diagram

💻 Code Challenge

Order the Steps

Match the Concepts

24.5 Summary

This chapter provided a comprehensive comparison of LPWAN technologies to guide your technology selection.

What LPWAN does best — bridge the gap between short-range wireless (Wi-Fi, Bluetooth, Zigbee) and cellular for infrequent small messages, battery-powered devices, and wide-area coverage at low cost. LPWAN is not suitable for high-bandwidth (video/audio), real-time critical, or continuous-streaming applications.

Technology landscape (2024):

• LoRaWAN (35% share) — most flexible, public or private networks, strong ecosystem; ideal for agriculture, smart buildings, private IoT
• Sigfox (5% share) — simplest operator service, very low power; constrained by 12-byte payload and 140 msg/day limit
• NB-IoT (42% share) — carrier-grade reliability, excellent deep indoor coverage; best for fixed utilities and smart meters
• LTE-M (15% share) — highest data rate LPWAN, full mobility and voice; best for wearables and fleet tracking

Key selection insights:

• No single “best” LPWAN — requirements drive the choice
• Multi-technology deployments are becoming common (60% of enterprises by 2026)
• Private LoRaWAN excels at scale (10,000+ devices); cellular wins for mobility and reliability
• Always calculate full TCO over the device lifetime (typically 5-10 years)

24.6 LPWAN Technology Fit Checker

Enter your application requirements to see which LPWAN technologies can support them.

viewof fit_payload = Inputs.range([1, 500], {
  value: 45, step: 1, label: "Required payload (bytes)"
})
viewof fit_msgs_day = Inputs.range([1, 2000], {
  value: 96, step: 1, label: "Required messages per day"
})
viewof fit_mobile = Inputs.select(["Fixed", "Slow mobile (<5 km/h)", "Vehicular (>50 km/h)"], {
  value: "Fixed", label: "Mobility requirement"
})
viewof fit_years = Inputs.range([1, 15], {
  value: 5, step: 1, label: "Required battery life (years)"
})

{
  const checks = {
    LoRaWAN: {
      payload: fit_payload <= 243,
      msgs: true, // duty-cycle limited, ~1440/day at SF7
      mobile: fit_mobile !== "Vehicular (>50 km/h)",
      battery: fit_years <= 10,
      color: "#3498DB"
    },
    Sigfox: {
      payload: fit_payload <= 12,
      msgs: fit_msgs_day <= 140,
      mobile: fit_mobile === "Fixed",
      battery: fit_years <= 20,
      color: "#E67E22"
    },
    "NB-IoT": {
      payload: fit_payload <= 1600,
      msgs: true,
      mobile: fit_mobile !== "Vehicular (>50 km/h)",
      battery: fit_years <= 10,
      color: "#16A085"
    },
    "LTE-M": {
      payload: fit_payload <= 1600,
      msgs: true,
      mobile: true,
      battery: fit_years <= 7,
      color: "#9B59B6"
    }
  };

  const rows = Object.entries(checks).map(([tech, c]) => {
    const allPass = c.payload && c.msgs && c.mobile && c.battery;
    return html`<tr style="background:${allPass ? '#e8f8f5' : '#fef9f9'}">
      <td style="padding:6px;color:${c.color};font-weight:bold">${tech}</td>
      ${[c.payload, c.msgs, c.mobile, c.battery].map(
        ok => html`<td style="padding:6px;text-align:center;color:${ok ? '#16A085' : '#E74C3C'};font-weight:bold">${ok ? '✓' : '✗'}</td>`
      )}
      <td style="padding:6px;text-align:center;font-weight:bold;color:${allPass ? '#16A085' : '#E74C3C'}">${allPass ? 'Suitable' : 'Cannot meet'}</td>
    </tr>`;
  });

  return html`<div style="font-family:Arial,sans-serif;padding:14px;background:#f8f9fa;border-radius:6px;border-left:4px solid #2C3E50">
    <table style="width:100%;border-collapse:collapse;font-size:0.9em">
      <tr style="background:#2C3E50;color:#fff">
        <th style="padding:7px;text-align:left">Technology</th>
        <th style="padding:7px;text-align:center">Payload (${fit_payload}B)</th>
        <th style="padding:7px;text-align:center">Msgs/day (${fit_msgs_day})</th>
        <th style="padding:7px;text-align:center">Mobility</th>
        <th style="padding:7px;text-align:center">Battery (${fit_years}yr)</th>
        <th style="padding:7px;text-align:center">Verdict</th>
      </tr>
      ${rows}
    </table>
    <p style="margin:8px 0 0;font-size:0.8em;color:#7F8C8D">
      Note: LoRaWAN msgs/day are duty-cycle limited (~1440/day at SF7, EU868). NB-IoT/LTE-M have no hard message limit.
    </p>
  </div>`;
}

24.7 Knowledge Check

Quiz: LPWAN Technology Comparison

24.8 Concept Relationships

How This Topic Connects

Builds on:

• LPWAN Introduction - Core concepts before detailed comparison
• Wireless Sensor Networks - WSN challenges that LPWAN addresses

Enables:

• Technology Selection - Apply comparison to choose optimal technology
• Cost Analysis - Calculate TCO for selected technology

Market Context:

• NB-IoT dominates Asia-Pacific (42% global share, especially China)
• LoRaWAN leads private deployments in Europe and North America (35% share)
• LTE-M strongest in North America (15% share)
• Multi-technology deployments becoming common (60% of enterprises by 2026)

24.9 See Also

Additional Resources

Within This Module:

• LPWAN Worked Example - 5-year TCO for 50,000 smart meters
• Architecture Comparison Diagrams - Visual network topologies

Market Analysis:

• LPWAN Market Statistics - 2024 adoption and growth patterns
• GSMA Mobile IoT Deployment Map - Global cellular LPWAN coverage

Technology Standards:

• LoRa Alliance - LoRaWAN specifications
• 3GPP NB-IoT/LTE-M - Cellular LPWAN standards

24.10 What’s Next

What to read next after LPWAN Technology Comparison

Chapter	Focus	Why Read It
LPWAN Technology Selection Guide	Structured decision frameworks and scoring rubrics for LPWAN selection	Apply the comparison knowledge from this chapter to make a justified technology recommendation
LPWAN Cost Analysis	Full TCO modelling: capex, opex, and break-even calculations	Go deeper on the financial analysis introduced in the Worked Example here
LoRaWAN Overview	LoRaWAN architecture, spreading factors, and network server configuration	LoRaWAN leads private deployments (35% market share) — understand the technology you will most likely configure
NB-IoT Fundamentals	NB-IoT radio interface, PSM, eDRX, and carrier deployment	NB-IoT dominates with 42% global share — essential for utility and smart-city deployments
LTE-M and Cellular IoT	LTE-M mobility, VoLTE, and fleet tracking use cases	Understand the highest-performance LPWAN tier for mobile and wearable applications
LPWAN Comprehensive Assessment	Advanced scenario-based quizzes and further reading recommendations	Test your ability to select, justify, and configure LPWAN technologies across complex real-world scenarios