10  LPWAN Visual Reference Gallery

In 60 Seconds

This gallery provides visual reference diagrams for LPWAN technology selection, architecture comparison, and deployment planning. Use these visuals to quickly grasp LPWAN positioning (between short-range and cellular), compare LoRaWAN vs. Sigfox vs. NB-IoT trade-offs, and apply decision frameworks for choosing the right technology based on range, power, data rate, and cost requirements.

10.1 Introduction

This visual reference gallery provides quick access to key LPWAN diagrams and illustrations for learning and reference purposes. Visual representations make complex LPWAN technology trade-offs, network architectures, and selection criteria easier to understand at a glance. Whether you are studying for an exam, preparing a presentation, or making a deployment decision, these diagrams distill the essential relationships between LPWAN technologies into clear, memorable visuals.

Learning Objectives

• Analyze LPWAN positioning diagrams to explain how these networks fill the gap between short-range wireless and cellular technologies
• Compare LoRaWAN, Sigfox, and NB-IoT architectures by evaluating trade-offs across range, power, data rate, cost, and deployment model
• Apply visual decision frameworks to select the appropriate LPWAN technology for a given IoT deployment scenario
• Distinguish licensed from unlicensed LPWAN spectrum and justify the regulatory implications for duty cycle and QoS
• Calculate LPWAN device battery life estimates using duty-cycle power models and interpret the results to assess deployment feasibility

Key Concepts

• Visual Reference Gallery: A collection of diagrams, charts, and visualizations covering LPWAN concepts including technology comparison matrices, network architecture diagrams, and link budget illustrations.
• LPWAN Architecture Diagrams: Visual representations of LoRaWAN star-of-stars, NB-IoT cellular architecture, and Sigfox operator model network structures.
• Performance Comparison Charts: Graphical comparisons of LPWAN technologies across range, data rate, power consumption, and cost dimensions.

10.2 Minimum Viable Understanding

• LPWAN fills a specific gap: Between short-range (Wi-Fi/BLE, <100 m) and cellular (high power, high cost), LPWAN delivers 2–40+ km range at ultra-low power for small, infrequent data payloads.
• Three main families, three deployment models: LoRaWAN (private/community networks), Sigfox (operator subscription), and NB-IoT/LTE-M (cellular carrier infrastructure) each trade off differently on cost, coverage, data rate, and control.
• Selection is scenario-driven: No single LPWAN technology is best for all cases – the right choice depends on range requirements, data rate needs, power budget, QoS demands, and whether you need private network control.

Sensor Squad: The LPWAN Art Museum

Lila the LoRa Module had a wonderful idea. “Let’s build an art museum – but instead of paintings, we’ll hang diagrams that explain how LPWAN works! That way, anyone can walk in and understand in seconds!”

Sammy the Sensor painted the first picture: a big map showing how far different wireless signals can travel. “See? Wi-Fi can only reach across one room, but LPWAN can reach across the whole city!”

Max the Microcontroller drew a chart comparing the three LPWAN families. “LoRaWAN is like building your own treehouse – you control everything. Sigfox is like renting a room in a big hotel – someone else manages it. And NB-IoT uses the same towers as your phone!”

Bella the Battery added her favorite diagram: a flowchart that helps you pick the right technology. “Just answer a few questions – how far do you need to send data? How often? Do you need your own network? – and the flowchart tells you the best choice!”

The Sensor Squad Museum was a hit. Now everyone could look at the pictures and understand LPWAN technology without reading a whole textbook!

For Beginners: Why Visual References Matter for LPWAN

LPWAN technology selection involves balancing many factors simultaneously: range, power consumption, data rate, cost, deployment model, spectrum type, and QoS guarantees. Trying to hold all of these in your head at once is difficult.

Visual diagrams help because they:

• Show relationships at a glance – A comparison chart reveals trade-offs that take paragraphs to describe in text
• Support decision-making – Flowcharts guide you through the selection process step by step
• Aid memory retention – Studies show that combining text with visuals improves recall by 65%
• Enable quick reference – During meetings or design reviews, a single diagram can communicate what matters

How to use this gallery:

1. Studying – Review diagrams after reading the main LPWAN chapters to reinforce concepts
2. Presentations – Reference these visuals when explaining LPWAN to stakeholders
3. Decision-making – Use the flowcharts and comparison diagrams when selecting a technology
4. Quick lookup – Bookmark this page for fast access to LPWAN reference material

Visual Type	Best Used For
Positioning Diagram	Understanding where LPWAN fits among wireless technologies
Comparison Chart	Evaluating trade-offs between LoRaWAN, Sigfox, NB-IoT
Decision Flowchart	Selecting the right technology for a specific project
Architecture Diagram	Understanding network topology and data flow
Spectrum Map	Knowing which frequency bands each technology uses

10.3 Visual Reference Gallery

LPWAN Technology Diagrams

These visual references provide alternative perspectives on LPWAN concepts covered in this chapter.

LPWAN Technology Overview

Figure 10.1: LPWAN technology positioning showing how these networks fill the gap between short-range wireless and traditional cellular for battery-powered IoT applications.

LPWAN Technology Comparison

Figure 10.2: LPWAN technology comparison highlighting the trade-offs between LoRaWAN, Sigfox, and NB-IoT for different IoT deployment scenarios.

LPWAN Decision Flowchart

Figure 10.3: LPWAN technology selection flowchart helping engineers navigate the decision process based on coverage, data rate, deployment control, and cost requirements.

10.4 LPWAN Technology Positioning

The following diagram shows where LPWAN technologies sit relative to other wireless options, plotted by range and data rate. This is the most fundamental visualization for understanding the LPWAN value proposition.

10.5 LPWAN Network Architecture Comparison

Each LPWAN technology uses a different network architecture. Understanding these architectural differences is key to selecting the right technology and planning deployments.

Key architectural differences:

Aspect	LoRaWAN	Sigfox	NB-IoT
Topology	Star-of-stars	Star	Star (cellular)
Infrastructure	Private gateways	Operator base stations	Existing cell towers
Backhaul	Any IP connection	Sigfox-managed	Carrier core network
Control	Full owner control	Operator-managed	Carrier-managed

10.6 LPWAN Technology Selection Decision Tree

Use this decision flowchart when choosing an LPWAN technology for a new IoT project. Follow the questions from top to bottom to arrive at a recommended technology.

10.7 LPWAN Spectrum and Frequency Bands

Different LPWAN technologies operate in different frequency bands, which affects range, building penetration, and regulatory constraints.

Spectrum implications:

• Unlicensed bands (LoRaWAN, Sigfox): Free to use but subject to duty cycle limits and potential interference from other devices
• Licensed bands (NB-IoT, LTE-M): Guaranteed quality of service but requires carrier agreements and subscription fees

10.8 LPWAN Power Consumption Lifecycle

Understanding the power consumption profile of LPWAN devices is critical for battery life estimation. The following diagram shows the typical duty cycle of an LPWAN sensor node.

LPWAN device power consumption lifecycle

Common Pitfalls with LPWAN Visual References

Pitfall 1: Assuming diagrams show exact specifications. LPWAN parameters vary significantly by region, configuration, and vendor. A diagram showing “10 km range” reflects typical outdoor conditions – urban environments may achieve only 2-3 km.

Pitfall 2: Comparing technologies on a single axis. It is tempting to rank LPWAN technologies by one metric (e.g., range or data rate). Real-world selection requires considering cost, power, QoS, spectrum regulations, ecosystem maturity, and deployment model simultaneously.

Pitfall 3: Ignoring regional regulatory differences. Spectrum diagrams show general frequency bands, but duty cycle limits (1% in EU868 vs. frequency hopping in US915), maximum transmit power, and channel plans differ significantly between regions. Always check local regulations.

Pitfall 4: Confusing theoretical vs. practical link budgets. Architecture diagrams may suggest overlapping coverage, but real-world propagation depends on terrain, building materials, antenna placement, and interference. Always perform site surveys.

Pitfall 5: Over-simplifying the cost comparison. Cost diagrams typically show per-device or per-message costs. Total cost of ownership must include gateway infrastructure (LoRaWAN), subscription fees (Sigfox/NB-IoT), network management, and device certification.

10.9 Worked Example: Selecting LPWAN for a Smart City Parking System

Scenario: A city council wants to deploy 5,000 in-ground parking sensors across the downtown area (3 km x 3 km). Each sensor detects whether a space is occupied and reports status changes. The system must operate for 5+ years on battery, work reliably in urban environments, and integrate with a real-time mobile app for drivers.

10.9.1 Step 1: Define Requirements

Requirement	Value	Rationale
Number of devices	5,000	One per parking space
Coverage area	~9 km2 (3 x 3 km)	Downtown core
Message frequency	~10-20 per day per device	Status changes only
Payload size	4-8 bytes	Occupied/free + battery + temperature
Latency tolerance	< 30 seconds	Real-time enough for drivers
Battery life	> 5 years	Underground installation makes replacement expensive
Environment	Urban, in-ground	Metal manhole covers, interference

10.9.2 Step 2: Apply the Decision Flowchart

Following the decision tree above:

1. Data rate needed? – Very low (< 1 kbps effective) – proceed to QoS question
2. QoS guarantee required? – Not strictly (parking is not safety-critical, occasional missed updates are acceptable) – proceed to private network question
3. Private network preferred? – City wants long-term control and no recurring carrier fees – proceed to LoRaWAN path
4. Messages per day? – 10-20 per device fits well within LoRaWAN and Sigfox limits

10.9.3 Step 3: Evaluate Top Candidates

Criterion	LoRaWAN	Sigfox	NB-IoT
Coverage	4-6 gateways for 9 km2	Depends on operator coverage	Good if carrier has urban coverage
Cost model	Gateway CAPEX (~$1,500 each) + no recurring per-device	~$1/device/year subscription	~$2-5/device/year SIM cost
Battery	Excellent (Class A)	Excellent	Good (PSM/eDRX needed)
In-ground performance	Good at 868/915 MHz	Good at 868/915 MHz	Best (licensed band, higher power)
City control	Full control of infrastructure	Dependent on Sigfox operator	Dependent on carrier
5-year TCO (5,000 devices)	~$35,000	~$25,000	~$75,000

10.9.4 Step 4: Recommendation

LoRaWAN is the best fit for this scenario because:

• The city retains full infrastructure control with 4-6 gateways
• Zero recurring per-device fees result in the best long-term TCO
• Class A operation delivers excellent battery life for event-driven parking status
• Sub-GHz frequency provides reasonable in-ground penetration
• Open ecosystem with multiple sensor vendors (e.g., PNI PlacePod, Bosch PLS)

Risk mitigation: Deploy 2 pilot gateways and 50 sensors for 3 months to validate urban coverage before full rollout. Use redundant gateway coverage (each sensor should be reachable by at least 2 gateways).

Putting Numbers to It: Coverage Area and Gateway Density

For the smart parking deployment (5,000 sensors over 9 km²), let’s calculate how many LoRaWAN gateways are needed and the coverage overlap.

Single Gateway Coverage Area: \[ A_{\text{gateway}} = \pi r^2 \] Where \(r\) is the effective urban range. From link budget analysis: \(r_{\text{urban}} = 2\) km (conservative urban estimate with in-ground sensors).

\[ A_{\text{gateway}} = \pi (2)^2 = 12.57 \text{ km}^2 \]

Minimum Gateways Required (No Overlap): \[ N_{\text{min}} = \frac{A_{\text{total}}}{A_{\text{gateway}}} = \frac{9}{12.57} = 0.72 \approx 1 \text{ gateway (theoretical)} \]

In practice: Single gateway is NOT sufficient due to: - Urban shadowing: Buildings block line-of-sight - Underground sensors: Parking sensors buried under asphalt lose ~20 dB - Redundancy requirement: Each sensor should reach 2+ gateways

Gateway Density with 2× Coverage Redundancy: \[ N_{\text{redundant}} = 2 \times N_{\text{min}} = 2 \times 0.72 = 1.44 \approx 2 \text{ gateways (minimum)} \]

Practical deployment (hexagonal grid for uniform coverage): \[ d_{\text{gateway}} = \sqrt{\frac{2A_{\text{gateway}}}{\sqrt{3}}} = \sqrt{\frac{2 \times 12.57}{\sqrt{3}}} = 3.8 \text{ km spacing} \]

For a 3 km × 3 km downtown area, hexagonal layout gives: \[ N_{\text{hex}} = \text{ceil}\left(\frac{3}{3.8}\right) \times \text{ceil}\left(\frac{3}{3.8 \times \sqrt{3}/2}\right) = 1 \times 2 = 2 \text{ gateways} \]

Actual recommendation: 4-6 gateways to ensure: - 99%+ coverage (accounting for 20 dB in-ground loss) - Redundancy (each sensor reaches 2-3 gateways) - Future growth (additional parking zones)

Cost Impact: \[ \text{Gateway CAPEX} = 6 \times \$1,500 = \$9,000 \text{ (vs } \$3,000 \text{ for 2 gateways)} \] This is a worthwhile 3× increase for reliability in a 5,000-sensor mission-critical system.

10.10 Knowledge Checks

Test your understanding of LPWAN visual concepts and technology selection.

Common Mistake: Misreading Range Specifications in Diagrams

The Mistake: Looking at an LPWAN positioning diagram that shows “LoRaWAN: 15 km range” and assuming your urban sensors 5 km from a gateway will work reliably.

Why It’s Wrong: Range specifications in reference diagrams represent ideal conditions: - Line-of-sight (no buildings, trees, hills) - Rural/open terrain - Maximum allowed TX power (+16 dBm EIRP EU868, +30 dBm EIRP US915) - Best spreading factor (SF12 for LoRa) - No interference - Gateway at optimal height (rooftop/tower)

Urban Reality Check:

Specification	Diagram Claim	Urban Reality
LoRaWAN range	15 km	2-5 km (buildings attenuate)
NB-IoT range	10 km	3-7 km (cell tower density)
Sigfox range	40 km	5-10 km (interference)

Real Example: Barcelona smart city project: - Vendor promised: “LoRaWAN covers 10 km² per gateway” - Actual deployment: Needed 1 gateway per 3-4 km² (3× more) - Reason: Dense urban buildings (5-15 story), underground sensors, interference from Wi-Fi

How to Use Diagrams Correctly:

1. Apply urban degradation factor: Multiply diagram range by 0.3-0.5 for cities
2. Add redundancy: Plan for 2× coverage overlap (no single-point-of-failure)
3. Conduct site survey: Test actual range before full deployment
4. Check building penetration: Indoor sensors may need +10 to +20 dB link budget

Corrected Urban Interpretation:

• Diagram shows “15 km” → Assume 3-5 km effective urban range
• Diagram shows “40 km” (Sigfox rural) → Assume 10-15 km urban range
• Diagram shows “10+ year battery” → Assume 5-7 years with real-world duty cycles

10.11 LPWAN Battery Life Estimator

Use this interactive tool to estimate the battery life of an LPWAN sensor node based on its duty cycle (see the power lifecycle diagram above).

viewof bl_batt_mah = Inputs.range([200, 20000], {
  value: 2400, step: 100, label: "Battery capacity (mAh)"
})
viewof bl_sleep_ua = Inputs.range([1, 20], {
  value: 3, step: 0.5, label: "Sleep current (µA)"
})
viewof bl_tx_ma = Inputs.range([10, 200], {
  value: 50, step: 5, label: "TX current (mA)"
})
viewof bl_tx_ms = Inputs.range([10, 2000], {
  value: 100, step: 10, label: "TX duration (ms per message)"
})
viewof bl_msgs_day = Inputs.range([1, 1440], {
  value: 24, step: 1, label: "Messages per day"
})

{
  const sleepMah_day = (bl_sleep_ua / 1000) * 24;
  const txMah_day    = (bl_tx_ma * (bl_tx_ms / 1000) * bl_msgs_day) / 3600;
  const totalMah_day = sleepMah_day + txMah_day;
  const days         = bl_batt_mah / totalMah_day;
  const years        = days / 365;

  const txPct  = (txMah_day / totalMah_day * 100).toFixed(1);
  const slpPct = (sleepMah_day / totalMah_day * 100).toFixed(1);

  const color = years >= 5 ? "#16A085" : years >= 2 ? "#E67E22" : "#E74C3C";

  return htl.html`<div style="font-family:Arial,sans-serif;padding:14px;background:#f8f9fa;border-radius:6px;border-left:4px solid ${color}">
    <table style="width:100%;border-collapse:collapse;font-size:0.9em">
      <tr style="background:#2C3E50;color:#fff">
        <th style="padding:7px;text-align:left">Component</th>
        <th style="padding:7px;text-align:right">Daily Consumption</th>
        <th style="padding:7px;text-align:right">% of Total</th>
      </tr>
      <tr><td style="padding:6px">Sleep (${bl_sleep_ua} µA × 24 h)</td>
          <td style="padding:6px;text-align:right">${sleepMah_day.toFixed(4)} mAh</td>
          <td style="padding:6px;text-align:right">${slpPct}%</td></tr>
      <tr style="background:#f0f0f0">
          <td style="padding:6px">TX (${bl_tx_ma} mA × ${bl_tx_ms} ms × ${bl_msgs_day} msgs)</td>
          <td style="padding:6px;text-align:right">${txMah_day.toFixed(4)} mAh</td>
          <td style="padding:6px;text-align:right">${txPct}%</td></tr>
      <tr style="font-weight:bold">
          <td style="padding:6px">Total daily</td>
          <td style="padding:6px;text-align:right">${totalMah_day.toFixed(4)} mAh</td>
          <td style="padding:6px;text-align:right">100%</td></tr>
    </table>
    <p style="margin:10px 0 0;padding:8px;background:${color};color:#fff;border-radius:4px;text-align:center;font-weight:bold">
      Estimated battery life: <strong>${years.toFixed(1)} years</strong>
      (${Math.round(days).toLocaleString()} days) with ${bl_batt_mah.toLocaleString()} mAh battery
    </p>
  </div>`;
}

🏷️ Label the Diagram

💻 Code Challenge

10.12 Summary

This LPWAN visual reference gallery provides diagrams, decision aids, and worked examples covering the essential aspects of LPWAN technology:

• Technology positioning: LPWAN occupies the unique long-range, low-power, low-data-rate space between short-range wireless (Wi-Fi, BLE, Zigbee) and traditional cellular (4G/5G), enabling battery-powered IoT at scale
• Architecture comparison: LoRaWAN uses private gateways with star-of-stars topology, Sigfox uses operator-managed base stations, and NB-IoT/LTE-M leverages existing cellular infrastructure – each model has distinct cost, control, and QoS implications
• Spectrum and regulation: LoRaWAN and Sigfox operate in unlicensed ISM bands (868/915 MHz) with duty cycle constraints, while NB-IoT and LTE-M use licensed cellular bands with guaranteed QoS but carrier subscription costs
• Power lifecycle: LPWAN devices achieve multi-year battery life through aggressive duty cycling – sleeping at 1-5 uA for 99%+ of the time, with brief wake/sense/transmit/receive cycles
• Decision framework: Technology selection should follow a structured process evaluating data rate, QoS requirements, mobility needs, infrastructure control preferences, message volume, and total cost of ownership
• Selection is context-dependent: No single LPWAN technology wins in all scenarios – the worked example showed how a smart city parking deployment favored LoRaWAN for infrastructure control despite Sigfox having lower direct costs

10.13 Concept Relationships

How This Topic Connects

Builds on:

• LPWAN Introduction and Fundamentals - Core concepts visualised in these diagrams
• LPWAN Technology Comparison - Detailed comparison shown in visual form

Supports:

• LPWAN Selection Guide - Decision flowcharts guide technology choice
• LoRaWAN Architecture - Network topology diagrams explained

Visual Learning:

• Positioning diagrams show LPWAN’s unique long-range, low-power, low-data-rate niche
• Architecture comparisons reveal deployment model differences (private vs. operator vs. cellular)
• Decision trees systematize technology selection based on requirements

10.14 See Also

Additional Resources

Within This Module:

• LPWAN Cost Analysis - TCO calculations and break-even analysis
• LPWAN Fundamentals - Additional technical foundations

Visual Learning Tools:

• Knowledge Map - Interactive technology positioning
• Simulations Hub - LPWAN range calculator and duty cycle simulator

External Visual Resources:

• LoRa Alliance Infographics - Official visual guides
• GSMA IoT Visualizations - Cellular LPWAN deployment maps

10.15 What’s Next

Use this gallery as a visual anchor, then build deeper understanding with these chapters:

Chapter	Focus	Why Read It
LPWAN Introduction and Fundamentals	Core LPWAN concepts and characteristics	Explains the theory behind every diagram in this gallery — range, link budget, and duty cycle fundamentals
LPWAN Technology Comparison	Detailed head-to-head technology comparison	Goes beyond the visual summary to compare LoRaWAN, Sigfox, and NB-IoT with quantitative benchmarks
LoRaWAN Overview	LoRaWAN architecture, device classes, and deployment	Implement LoRaWAN networks using the star-of-stars topology shown in the architecture diagram
NB-IoT & LTE-M Fundamentals	Cellular LPWAN — NB-IoT and LTE-M protocols	Analyse the licensed-band spectrum characteristics and PSM/eDRX power modes introduced in this gallery
LPWAN Selection Guide	Structured decision framework for technology choice	Apply the decision flowchart methodology from this gallery to real project scenarios with worked guidance
Cellular IoT Applications	Real-world cellular IoT deployments	Evaluate how NB-IoT and LTE-M are deployed in smart city and industrial contexts beyond this gallery overview