27 LPWAN Assessment: Fundamentals

In 60 Seconds

LPWAN technologies are defined by three interdependent characteristics: low bandwidth (100 bps to 50 kbps), long range (2-40+ km), and low power (5-20 year battery life). This assessment tests whether you can apply these fundamentals to real scenarios, including recognizing when Sigfox’s 12-byte payload limit eliminates it as an option and understanding how recurring subscription costs dominate cellular IoT TCO at scale.

27.1 Introduction

This chapter tests your foundational understanding of LPWAN technologies through targeted assessment questions covering core characteristics, technology comparisons, and basic selection criteria.

Learning Objectives

Explain the three defining characteristics of LPWAN and justify why each constraint is deliberately chosen
Compare LoRaWAN and Sigfox payload limits, message quotas, and duty cycle rules to select the appropriate technology for a given scenario
Calculate the 5-year Total Cost of Ownership for private LoRaWAN versus cellular NB-IoT deployments at scale
Evaluate technology selection decisions by applying payload size, message frequency, and power constraints simultaneously
Distinguish between daily message quotas (hard limits) and duty cycle restrictions (time-based limits) and assess their impact on application design
Apply the link budget trade-off between data rate, range, and power to diagnose why a proposed LPWAN configuration will or will not meet requirements

For Beginners: LPWAN Assessment

This assessment tests your understanding of LPWAN (Low-Power Wide-Area Network) fundamentals. LPWANs are wireless networks designed to send small amounts of data over very long distances using very little power – perfect for sensors that need to run on a single battery for years.

Sensor Squad: LPWAN Quiz Time

“Pop quiz!” announced Max the Microcontroller. “Sammy, what’s the maximum data rate of a typical LoRaWAN device?”

Sammy the Sensor thought carefully. “Around 50 kilobits per second at best? No wait – it’s much lower. Maybe 5 to 50 kbps depending on settings. You’re definitely not streaming video over LoRaWAN!”

“Correct! And why is that actually a FEATURE?” asked Max. Bella the Battery answered: “Because low data rate means low power. Each transmission is tiny, so I barely wake up the radio. That’s how we get 10-year battery life – by sending just a few bytes at a time.”

Lila the LED added: “Here’s another quiz question – what’s a duty cycle? It’s the percentage of time you’re ALLOWED to transmit. In Europe, it’s often just 1% – meaning you can only transmit for 36 seconds per hour. This quiz will test whether you really understand these fundamentals or just memorized the buzzwords!”

27.2 LPWAN Core Characteristics Quiz

Test your understanding of the fundamental principles that define LPWAN technologies.

Question 1: LPWAN Characteristics

Which combination of characteristics best defines LPWAN technologies?

High bandwidth, short range, low power
Low bandwidth, long range, high power
Low bandwidth, long range, low power
High bandwidth, long range, low power

Click to reveal answer

Answer: C) Low bandwidth, long range, low power

Explanation:

LPWAN technologies are specifically designed with these three key characteristics:

Low bandwidth:

Data rates from 100 bps (Sigfox) to 50 kbps (LoRaWAN)
Small payload sizes (12-243 bytes typically)
Optimized for sensor data, not multimedia

Long range:

2-15 km in urban environments
15-40+ km in rural/open areas
Much longer than Wi-Fi (100m) or Bluetooth (10m)

Low power:

Battery life of 5-20 years typical
Infrequent transmissions
Simple modulation schemes
Deep sleep modes between transmissions

These characteristics are intentionally traded off: - To achieve long range with low power, bandwidth must be reduced - Sub-GHz frequencies provide better propagation than 2.4/5 GHz - Simple protocols minimize processing power requirements

Why other options are incorrect:

A: LPWAN deliberately uses low bandwidth, not high
B: LPWAN uses low power, not high (this describes cellular 4G/5G)
D: Cannot achieve both high bandwidth and long range with low power simultaneously (physics constraints)

This unique combination makes LPWAN ideal for IoT applications like smart metering, environmental monitoring, and asset tracking.

Inline Check: Duty Cycle Fundamentals

27.3 Technology Comparison Quiz

Understanding the differences between LPWAN technologies is critical for proper solution design.

Question 2: LoRaWAN vs Sigfox Selection

A company needs to deploy 10,000 environmental sensors across a city. Sensors report every 15 minutes (96 messages/day) with 50-byte payloads. Battery life must exceed 5 years. Should they choose LoRaWAN or Sigfox?

Sigfox because it has lower power consumption
LoRaWAN because Sigfox message limits are exceeded
Either technology works equally well
Neither technology is suitable for this application

Click to reveal answer

Answer: B) LoRaWAN because Sigfox message limits are exceeded

Explanation:

Let’s analyze the requirements against each technology’s capabilities:

Application Requirements:

96 messages per day
50-byte payload
5+ year battery life
10,000 devices

Sigfox Limitations:

Maximum 140 uplink messages per day - (96 < 140, this passes)
Maximum 12-byte payload - (need 50 bytes, FAILS)
10-20 year battery life - acceptable
Scales to thousands of devices - acceptable

LoRaWAN Capabilities:

No daily message limit (only duty cycle restrictions) - acceptable
Up to 243-byte payload - (50 bytes well within limits)
5-10 year battery life - acceptable (at this message frequency)
Scales to thousands of devices per gateway - acceptable

Critical failure point: Sigfox’s 12-byte payload limit is exceeded by the 50-byte requirement. Even if we could compress the data, the fundamental constraint makes Sigfox unsuitable.

Additional considerations:

96 messages/day with 50 bytes represents ~4.8 KB/day per sensor
This is well within LoRaWAN duty cycle limits (~1% in EU)
With adaptive data rate, LoRaWAN can optimize power consumption
Battery life will depend on spreading factor selection

Why other options are incorrect:

A: While Sigfox has excellent power consumption, the payload size constraint eliminates it
C: The technologies are NOT equivalent - Sigfox physically cannot support 50-byte payloads
D: Both the message frequency (96/day) and payload size (50 bytes) are well within LoRaWAN capabilities

Recommendation: Deploy LoRaWAN with SF7-SF9 spreading factors to balance range and power consumption, achieving the required 5+ year battery life while accommodating the 50-byte payload.

27.4 Basic Cost Analysis Quiz

Understanding cost factors is essential for LPWAN deployment planning.

Question 3: Cost Analysis

A water utility wants to deploy 50,000 smart water meters across a region. Each meter sends one reading per day (24 bytes). Compare the 5-year total cost of ownership between private LoRaWAN and NB-IoT. Assume: LoRaWAN gateway 1,500 EUR, sensor 15 EUR, coverage needs 30 gateways, network server 300 EUR/month. NB-IoT sensor 20 EUR, data plan 1.50 EUR/device/month.

What is the approximate 5-year TCO difference?

NB-IoT costs 4,400,000 EUR more
LoRaWAN costs 2,000,000 EUR more
Both cost approximately the same
NB-IoT costs 800,000 EUR more

Click to reveal answer

Answer: A) NB-IoT costs 4,400,000 EUR more

Explanation:

Let’s calculate the detailed 5-year Total Cost of Ownership (TCO) for each option:

Private LoRaWAN:

Initial costs (Year 1): - Gateways: 30 x 1,500 EUR = 45,000 EUR - Sensors: 50,000 x 15 EUR = 750,000 EUR - Installation labor: ~100,000 EUR (estimate) - Total initial: 895,000 EUR

Recurring costs (Years 1-5): - Network server: 300 EUR/month x 12 months x 5 years = 18,000 EUR - Maintenance: ~5,000 EUR/year x 5 years = 25,000 EUR - Total recurring: 43,000 EUR

Putting Numbers to It

Let’s calculate the 5-year TCO for private LoRaWAN vs NB-IoT at scale.

LoRaWAN (\(N = 50{,}000\) sensors): \[\text{TCO}_{\text{LoRa}} = \underbrace{30 \times 1{,}500}_{\text{gateways}} + \underbrace{50{,}000 \times 15}_{\text{sensors}} + \underbrace{300 \times 12 \times 5}_{\text{network server}} + \underbrace{100{,}000}_{\text{install}} + \underbrace{25{,}000}_{\text{maintenance}}\] \[= 45{,}000 + 750{,}000 + 18{,}000 + 100{,}000 + 25{,}000 = 938{,}000 \text{ EUR}\]

NB-IoT (\(N = 50{,}000\) sensors, \(S = 1.50\) EUR/month subscription): \[\text{TCO}_{\text{NB-IoT}} = \underbrace{50{,}000 \times 20}_{\text{sensors}} + \underbrace{100{,}000}_{\text{install}} + \underbrace{N \times S \times 12 \times 5}_{\text{subscriptions}}\] \[= 1{,}000{,}000 + 100{,}000 + (50{,}000 \times 1.50 \times 60) = 1{,}100{,}000 + 4{,}500{,}000 = 5{,}600{,}000 \text{ EUR}\]

Cost difference: \(5{,}600{,}000 - 938{,}000 = 4{,}662{,}000\) EUR (NB-IoT costs ~6× more)

Break-even: LoRaWAN is already cheaper by Year 1 (\(938{,}000 < 1{,}100{,}000\) initial NB-IoT cost alone). After deployment, recurring NB-IoT subscriptions (\(900{,}000\)/year) dominate versus LoRaWAN’s minimal \(8{,}600\)/year recurring cost.

LoRaWAN 5-year TCO: 938,000 EUR

NB-IoT (Cellular):

Initial costs (Year 1): - Sensors: 50,000 x 20 EUR = 1,000,000 EUR - Installation labor: ~100,000 EUR - Total initial: 1,100,000 EUR

Recurring costs (Years 1-5): - Data plan: 50,000 devices x 1.50 EUR/month x 12 months x 5 years = 4,500,000 EUR - Total recurring: 4,500,000 EUR

NB-IoT 5-year TCO: 5,600,000 EUR

Cost Difference: 5,600,000 EUR - 938,000 EUR = 4,662,000 EUR (approximately 4,400,000 EUR)

Key Insights:

Year 1 costs: NB-IoT (1,190,000 EUR) vs LoRaWAN (913,000 EUR)
- Similar initial investment
Year 2-5 costs: NB-IoT (900,000 EUR/year) vs LoRaWAN (8,600 EUR/year)
- Massive recurring cost difference
Break-even point: LoRaWAN infrastructure pays for itself in ~2 months of operation
10-year TCO difference: Would exceed 8 million EUR in favor of LoRaWAN

Factors favoring LoRaWAN for this application:

Large scale deployment (50,000 devices)
Low data frequency (once per day)
Long-term operation (5+ years)
Fixed locations (no mobility requirements)
Small payload size (24 bytes)

When NB-IoT might be preferred despite cost:

Need guaranteed QoS
Cannot deploy/maintain gateways
Require nationwide coverage
Need higher bandwidth occasionally
Mobile devices requiring handoff

Conclusion: For large-scale, long-term, low-data-rate sensor deployments, private LPWAN networks offer dramatic cost savings compared to cellular IoT solutions. The initial infrastructure investment is recovered quickly through elimination of per-device subscription fees.

27.5 TCO Calculator: LoRaWAN vs NB-IoT

Use this interactive calculator to explore how device count and subscription costs affect the break-even point between private LoRaWAN and cellular NB-IoT.

Show code

viewof num_devices = Inputs.range([1000, 100000], {value: 50000, step: 1000, label: "Device count"})
viewof sub_cost = Inputs.range([0.50, 5.00], {value: 1.50, step: 0.10, label: "NB-IoT fee (EUR/mo)"})
viewof years = Inputs.range([1, 10], {value: 5, step: 1, label: "Deployment years"})
viewof sensor_cost_lora = Inputs.range([10, 30], {value: 15, step: 1, label: "LoRaWAN sensor cost (EUR)"})
viewof sensor_cost_nbiot = Inputs.range([15, 40], {value: 20, step: 1, label: "NB-IoT sensor cost (EUR)"})

Show code

{
  const gateways = Math.max(10, Math.ceil(num_devices / 1500));
  const tco_lora = (gateways * 1500) + (num_devices * sensor_cost_lora) + (300 * 12 * years) + 100000 + (5000 * years);
  const tco_nbiot = (num_devices * sensor_cost_nbiot) + 100000 + (num_devices * sub_cost * 12 * years);
  const diff = tco_nbiot - tco_lora;
  const ratio = (tco_nbiot / tco_lora).toFixed(1);
  const cheaper = diff > 0 ? "LoRaWAN" : "NB-IoT";
  const saving = Math.abs(diff);

  return html`<div style="background: var(--bs-light, #f8f9fa); padding: 1rem; border-radius: 8px; border-left: 4px solid #16A085; margin-top: 0.5rem;">
    <p style="margin:0 0 0.5rem 0; color: #2C3E50;"><strong>TCO Comparison (${years}-year deployment, ${num_devices.toLocaleString()} devices)</strong></p>
    <table style="width:100%; border-collapse:collapse; font-size:0.9em;">
      <tr style="background:#2C3E50; color:white;"><th style="padding:6px 8px; text-align:left;">Technology</th><th style="padding:6px 8px; text-align:right;">Total TCO (EUR)</th><th style="padding:6px 8px; text-align:right;">Per device/year</th></tr>
      <tr style="background:#e8f5e9;"><td style="padding:5px 8px;"><strong>Private LoRaWAN</strong></td><td style="padding:5px 8px; text-align:right;"><strong>${tco_lora.toLocaleString()}</strong></td><td style="padding:5px 8px; text-align:right;">${(tco_lora / num_devices / years).toFixed(2)}</td></tr>
      <tr><td style="padding:5px 8px;"><strong>NB-IoT (cellular)</strong></td><td style="padding:5px 8px; text-align:right;"><strong>${tco_nbiot.toLocaleString()}</strong></td><td style="padding:5px 8px; text-align:right;">${(tco_nbiot / num_devices / years).toFixed(2)}</td></tr>
    </table>
    <p style="margin:0.75rem 0 0 0; color:#16A085;"><strong>${cheaper} saves EUR ${saving.toLocaleString()} (NB-IoT costs ${ratio}× more)</strong></p>
    <p style="margin:0.25rem 0 0 0; font-size:0.85em; color:#7F8C8D;">Assumes ${gateways} gateways at EUR 1,500 each. LoRaWAN recurring: network server + maintenance only.</p>
  </div>`;
}

27.6 Quick Knowledge Check

Self-Assessment

Before proceeding to advanced assessment topics, ensure you can answer:

What are the three defining characteristics of LPWAN?
What is Sigfox’s maximum payload size limitation?
Why do recurring costs dominate cellular IoT TCO?
When would you choose LoRaWAN over Sigfox?

Common Mistake: Assuming “140 messages per day” Means “Can Send Every 10 Minutes”

The Mistake: A developer calculates: “Sigfox allows 140 uplink messages per day. My parking sensor changes state every 10-15 minutes on average. 24 hours × 6 messages/hour = 144 messages… close enough, let’s use Sigfox!”

Why It Fails: The 140 message limit is a daily quota, not an average. Peak usage matters more than average. Consider a busy parking lot:

Typical weekday parking turnover:
8:00-9:00 AM (rush hour): 45 state changes (car arrives/leaves every 1.3 min)
9:00-12:00 PM (morning): 30 state changes (every 6 min)
12:00-1:00 PM (lunch): 25 state changes (every 2.4 min)
1:00-5:00 PM (afternoon): 35 state changes (every 6.8 min)
5:00-6:00 PM (rush hour): 40 state changes (every 1.5 min)
6:00 PM-8:00 AM (evening/night): 10 state changes (every 80 min)

Total: 185 messages/day on busy days
Peak hour: 45 messages in 60 minutes

The Problem:

Quota exceeded: 185 > 140 = 45 messages silently dropped
Uneven distribution: Can’t “save up” quota for peak hours
No buffering: Sigfox devices have no queue — excess messages are lost
Revenue impact: Lost parking availability data = missed parking fees

The Fix: Use LoRaWAN Class A with confirmed uplinks:

LoRaWAN approach:
- No daily message limit (only 1% duty cycle in EU868)
- At SF7, 100ms airtime per message
- 1% duty cycle allows 36 seconds/hour = 360 messages/hour
- Easily handles 45 messages/hour peak with 88% capacity headroom
- Cost: One gateway per parking lot ($500) vs Sigfox subscription ($1/sensor/year)
- For 100 sensors over 5 years: LoRaWAN = $2,000 total, Sigfox = $2,500 + message drops

Real-World Impact: A European city deployed Sigfox parking sensors and saw 30% data loss during peak hours. Revenue impact: €50,000/year in missed parking fees. They migrated to LoRaWAN and recovered full occupancy visibility.

Key Lessons:

Always model peak hour usage, not daily averages
Understand if quotas are soft limits (throttled) or hard limits (dropped)
Test with realistic traffic patterns, including holidays and events
Factor in failure modes: what happens when quota is exceeded?

27.7 Concept Relationships

This assessment tests fundamental LPWAN concepts that connect to broader IoT knowledge:

Core Trade-offs:

Physics Constraints: The link budget equation explains why LPWAN must sacrifice data rate for range. See LPWAN Fundamentals for the mathematical foundations.
Power Management: Multi-year battery life requires understanding sleep modes and transmission duty cycles. See Energy & Power Management.

Technology Selection:

Requirements Analysis: Payload size, message frequency, and coverage needs drive technology choice. See LPWAN Comparison for decision frameworks.
TCO Modeling: Understanding capital vs operational expenses across deployment timelines. See LPWAN Assessment: Selection for detailed cost analysis.

Deployment Considerations:

Network Models: Private (LoRaWAN), operator-managed (Sigfox), cellular (NB-IoT). See LPWAN Architectures for architectural patterns.
Scale Economics: How device count affects break-even points between technologies. See LPWAN Assessment: Selection for worked examples.

27.8 See Also

Continue Your Assessment:

LPWAN Assessment: Technology Selection - Advanced deployment scenarios
LPWAN Assessment: Regulatory Compliance - Duty cycle and scaling challenges
LPWAN Comprehensive Assessment - Full assessment index

Build Foundation:

LPWAN Fundamentals - Review core concepts
LPWAN Comparison - Technology comparison matrix
LoRaWAN Overview - Deep dive into LoRaWAN

Related Assessments:

Quizzes Hub - All protocol quizzes
Knowledge Checks - Concept relationships

Common Pitfalls

1. Using Free-Space Path Loss for Indoor Deployments

Free-space path loss models assume clear line-of-sight. Indoor deployments face wall attenuation (5-15 dB per wall), floor attenuation (20-30 dB), and furniture. Use indoor propagation models (COST-231 Multi-Wall) for indoor link budgets.

2. Not Including Connector and Cable Losses in Link Budget

Antenna connector losses (0.5-1 dB per connector) and coax cable losses (0.5-1 dB/m at 868 MHz) reduce effective radiated power. In link budgets, include all connector and cable losses between transmitter and antenna.

3. Assuming Worst-Case Coverage Without Site Survey

Conservative link budgets provide coverage estimates but real-world coverage requires physical testing. Verify theoretical link budgets with actual RSSI/SNR measurements at planned deployment sites.

Label the Diagram

💻 Code Challenge

Order the Steps

🔗 Match the Concepts

27.9 What’s Next

Chapter	Focus	Why Read It
LPWAN Assessment: Technology Selection	Advanced multi-constraint deployment scenarios	Apply payload, duty-cycle, and coverage constraints together in realistic case studies
LPWAN Assessment: Regulatory Compliance	Duty cycle, spectrum, and scaling challenges	Understand the legal and technical limits that govern how often devices may transmit
LPWAN Fundamentals	Core LPWAN principles and link budget mathematics	Review the physics behind range, data rate, and power trade-offs tested in this chapter
LoRaWAN Overview	LoRaWAN architecture, spreading factors, and ADR	Deep-dive into the technology selected in most exercises above
LPWAN Comparison	Side-by-side decision matrix for all LPWAN technologies	Use a structured framework to select between LoRaWAN, Sigfox, NB-IoT, and LTE-M
LPWAN Comprehensive Assessment	Full three-part assessment index	Access all fundamentals, selection, and regulatory assessment questions in one place