34  Sigfox Fundamentals

34.1 Learning Objectives

After completing this chapter series, you should be able to:

  • Differentiate the Sigfox network architecture from self-deployed LPWANs and classify Ultra-Narrow Band (UNB) modulation trade-offs
  • Calculate whether a given IoT application fits within the 140-message daily uplink budget and 12-byte payload constraint
  • Apply worked deployment examples to estimate costs and justify technology selection for fleet tracking and environmental monitoring scenarios
  • Evaluate Sigfox strengths and limitations relative to LoRaWAN and cellular LPWAN alternatives using quantitative decision frameworks

Key Concepts

  • Sigfox Technology Overview: Ultra-narrowband LPWAN technology providing long-range IoT connectivity with unique constraints and trade-offs compared to LoRaWAN and NB-IoT.
  • Learning Path: Structured progression through Sigfox concepts from fundamentals (UNB modulation, protocol basics) through deployment and advanced topics.
  • Sigfox Ecosystem Status: Following Unabiz acquisition of Sigfox network assets in 2022, the technology continues operating with transition considerations for new deployments.
  • Key Differentiators: Sigfox’s managed network eliminates infrastructure investment; ultra-narrow bandwidth achieves exceptional range; severe payload and duty cycle constraints require careful application design.
  • Module Structure: Course materials covering Sigfox fundamentals, technology details, deployment, device management, message flow, and comparative analysis with alternatives.
  • Prerequisites: Understanding of basic wireless communication principles, IoT sensor concepts, and familiarity with LPWAN technology category.
  • Practical Skills: Hands-on objectives including device registration, payload encoding, backend configuration, and coverage assessment for real Sigfox deployments.

Sigfox is an IoT network designed for extreme simplicity – devices send up to 140 tiny messages per day, using very little power, over distances of up to 50 kilometers. Think of it as a telegram service for sensors: short messages, long range, low cost. This section introduces the fundamentals of Sigfox technology and its place in the IoT ecosystem.

“Sigfox is the simplest LPWAN technology you will ever meet!” said Max the Microcontroller. “While LoRaWAN gives you lots of configuration options, Sigfox says: here are 12 bytes and 140 messages per day. Make it work. That radical simplicity is both its greatest strength and its biggest limitation.”

Sammy the Sensor was curious. “Only 12 bytes? What can I send in 12 bytes?” Max showed some examples. “A temperature reading takes 2 bytes. A battery level takes 1 byte. A GPS coordinate takes 8 bytes. You can fit a surprising amount of useful data if you encode it efficiently in binary instead of text.”

“The network is managed by Sigfox operators – you do not build your own infrastructure,” explained Lila the LED. “That means no gateways to buy, no network servers to maintain. Just activate your device and start sending. Coverage already exists in over 70 countries.”

Bella the Battery loved the power efficiency. “Sigfox devices use Ultra-Narrow Band modulation at just 100 Hz bandwidth. That narrow signal needs very little power to transmit, so I can last 10 to 15 years on a single battery. The trade-off is speed – each message takes about 2 seconds to transmit, and you cannot stream data. But for sensors that report once an hour, it is perfect.”

In 60 Seconds

Sigfox is a proprietary, operator-managed LPWAN using Ultra-Narrow Band modulation that sends 12-byte payloads up to 140 times/day over 30-50 km range. This module covers introduction and best practices, UNB technology deep dive, worked deployment examples, and a comprehensive assessment.

34.2 About This Module

This comprehensive guide to Sigfox, a proprietary LPWAN technology, is organized into four focused chapters covering everything from basic concepts to advanced technical details and practical applications.

Learning Path

This module is structured progressively:

  1. Introduction → Core concepts and best practices
  2. Technology → Technical deep dive
  3. Worked Examples → Practical calculations
  4. Assessment → Test your knowledge

34.3 Module Contents

34.3.1 1. Sigfox Introduction and Best Practices

⏱️ ~15 min | ⭐⭐ Intermediate | 📋 P09.C10.U01a

What you’ll learn:

  • Sigfox’s ultra-narrow band (UNB) technology fundamentals
  • Operator-managed network model vs self-deployed alternatives
  • 12-byte payload constraints and efficient data encoding
  • Barcelona waste management case study (95% cost reduction)
  • Common deployment mistakes and how to avoid them

Key topics:

  • Getting started guide for beginners
  • Sigfox vs LoRaWAN comparison
  • Real-world scenarios and limitations
  • 7 costly mistakes to avoid
  • Payload encoding best practices

Perfect for: Understanding when Sigfox is the right choice, learning deployment best practices, and avoiding common pitfalls.

34.3.2 2. Sigfox Technology Deep Dive

⏱️ ~12 min | ⭐⭐⭐ Advanced | 📋 P09.C10.U01b

What you’ll learn:

  • Ultra-narrow band (UNB) modulation details
  • Three-tier network architecture
  • RSSI-based geolocation (Atlas)
  • Link budget calculations
  • Technology comparison frameworks

Key topics:

  • UNB vs CSS vs OFDM modulation
  • Sigfox radio parameters (DBPSK uplink, GFSK downlink)
  • Spatial diversity and redundant reception
  • Decision frameworks for LPWAN selection
  • Cost crossover analysis

Perfect for: Engineers needing technical specifications, understanding RF characteristics, and making informed technology selections.

34.3.3 3. Sigfox Worked Examples

⏱️ ~10 min | ⭐⭐ Intermediate | 📋 P09.C10.U01c

What you’ll learn:

  • Message budget planning for asset tracking
  • Total Cost of Ownership (TCO) calculations
  • Link budget analysis for rural deployments
  • Duty cycle and regulatory compliance

Practical scenarios:

  1. Asset Tracking: 1,000 shipping containers, 30-day ocean transit, 92% cost savings vs cellular
  2. Smart Parking: 5,000 sensors, Sigfox vs LoRaWAN TCO, crossover at 9,100 sensors
  3. Agricultural Monitoring: 30 km range, link budget with 13 dB margin
  4. EU868 Compliance: 1% duty cycle allowing 43 messages/hour

Perfect for: System designers, project planners, and anyone making deployment calculations.

34.3.4 4. Sigfox Knowledge Assessment

⏱️ ~15 min | ⭐⭐ Intermediate | 📋 P09.C10.U01d

What you’ll test:

  • Sigfox fundamentals and constraints
  • Technology characteristics and trade-offs
  • Real-world application scenarios
  • Cost and deployment decisions

Assessment format:

  • Quiz 1: Sigfox Fundamentals (25 questions)
  • Quiz 2: Sigfox Characteristics (12 questions)
  • Knowledge checks throughout chapters
  • Visual reference gallery

Perfect for: Testing your understanding, preparing for interviews, and validating your Sigfox expertise.

34.4 Prerequisites

Before starting this module, you should be familiar with:

34.5 Quick Start Guide

New to Sigfox? Start here:

  1. Introduction - Getting Started: Beginner-friendly overview with simple analogies
  2. Introduction - Real-World Example: Barcelona case study with concrete numbers
  3. Technology - UNB Modulation: How Sigfox achieves long range
  4. Worked Examples: Practice with real calculations

Experienced? Jump to:

Scenario: A city wants to deploy 10,000 smart parking sensors over 10 years. Compare Sigfox vs LoRaWAN total cost of ownership.

Requirements:

  • 10,000 parking sensors reporting occupancy every 5 minutes
  • Message size: 8 bytes (sensor ID, status, battery, timestamp)
  • Messages per day: (60/5) × 24 = 288 messages/day per sensor
  • Coverage: 50 km² urban area

PROBLEM: Sigfox limit is 140 messages/day, but parking needs 288/day.

Solution 1: Sigfox with Reduced Frequency

Compromise: Report every 11 minutes instead (131 msgs/day, within 140 limit)

10-Year TCO (Sigfox):

Hardware:
- Sigfox modules: 10,000 × $12 = $120,000

Subscription (annual):
- Year 1-3: 10,000 × $6/year = $60,000
- Year 4-6: 10,000 × $7/year = $70,000 (inflation)
- Year 7-10: 10,000 × $8/year = $80,000
- Total subscription: ($60k×3) + ($70k×3) + ($80k×4) = $710,000

Battery replacement:
- Battery life: 3 years (144 msgs/day load)
- Replacements needed: 2 cycles over 10 years
- Cost: 10,000 × $5 × 2 = $100,000
- Labor: 10,000 × $15 × 2 = $300,000

Infrastructure:
- None (operator network)

Operations:
- Monitoring: $20,000/year × 10 = $200,000

TOTAL 10-YEAR: $1,430,000
Per sensor per year: $14.30

Solution 2: LoRaWAN Private Network

10-Year TCO (LoRaWAN):

Hardware:
- LoRaWAN modules: 10,000 × $15 = $150,000

Gateways:
- Coverage: 50 km² / 2 km² per gateway = 25 gateways
- Cost: 25 × $1,200 = $30,000
- Redundancy (20%): 5 × $1,200 = $6,000
- Total gateways: $36,000

Gateway Backhaul (cellular):
- 30 gateways × $40/month × 120 months = $144,000

Network Server:
- Self-hosted server: $10,000 initial
- Hosting: $500/month × 120 months = $60,000
- Maintenance: $5,000/year × 10 = $50,000
- Total: $120,000

Battery replacement:
- Battery life: 5 years (no downlinks, SF8 average)
- Replacements: 1 cycle
- Cost: 10,000 × $5 = $50,000
- Labor: 10,000 × $15 = $150,000

Operations:
- Network management: $30,000/year × 10 = $300,000
- Gateway maintenance: $2,000/year × 10 = $20,000

TOTAL 10-YEAR: $970,000
Per sensor per year: $9.70

Solution 3: Hybrid (Sigfox + LoRaWAN)

Use both networks for redundancy and flexibility:

10-Year TCO (Hybrid):

Dual-mode devices: 10,000 × $20 = $200,000
LoRaWAN infrastructure: $350,000 (as above)
Sigfox subscription (backup): $355,000 (half of full deployment)
Batteries: $150,000 (longer life with adaptive switching)
Operations: $250,000

TOTAL 10-YEAR: $1,305,000
Per sensor per year: $13.05

Cost Comparison Summary:

Approach 10-Year Total Per Sensor/Year Message Freq Reliability
Sigfox Only $1,430,000 $14.30 11 min (131/day) Medium (95%)
LoRaWAN Only $970,000 $9.70 5 min (288/day) High (99%)
Hybrid $1,305,000 $13.05 5 min Very High (99.9%)

Break-Even Analysis:

LoRaWAN has higher upfront cost but lower opex:

LoRaWAN advantage: $1,430k - $970k = $460,000 over 10 years

Upfront difference: $186,000 (LoRa infra) - $120,000 (Sigfox devices) = $66,000
Payback period: $66k / ($460k/10 years) = 1.4 years

LoRaWAN becomes cheaper after 17 months!

Scaling Factor:

What if the city wants 50,000 sensors?

Sigfox: $1,430k × 5 = $7,150,000 - Scales linearly (subscription per device)

LoRaWAN: $970k base + additional devices - Gateways: Already sufficient (maybe add 10 more = $12k) - Devices: 40,000 × $15 = $600,000 - Batteries: 40,000 × $5 × 1 = $200,000 - Network server: Same (scales to 100k devices) - Total additional: $812,000 - 50k total: $1,782,000

Cost per sensor at scale:

  • Sigfox: $7,150k / 50k = $143/sensor over 10 years
  • LoRaWAN: $1,782k / 50k = $36/sensor over 10 years

LoRaWAN saves $5.37 million at 50,000 sensor scale!

Cost scaling reveals the crossover point for technology selection. Sigfox cost grows linearly with device count: \(C_{\text{Sigfox}}(N) = N \times (\$12 + \$8/\text{yr} \times 10\,\text{yr}) = N \times \$92\). LoRaWAN has fixed infrastructure plus per-device costs: \(C_{\text{LoRaWAN}}(N) = \$350k + N \times \$20\). Worked example: Solving \(92N = 350k + 20N\) gives crossover at \(N \approx 4861\) devices. Above 5000 sensors, LoRaWAN’s infrastructure amortizes for major savings.

Decision Recommendations:

Choose Sigfox when:

  • <5,000 sensors (simplicity wins)
  • Can tolerate 10-minute updates
  • No IT team to manage infrastructure
  • Pilot/prototype phase (fastest deployment)

Choose LoRaWAN when:

  • 10,000 sensors (cost savings dominate)

  • Need 5-minute or faster updates
  • Have IT capability
  • Want independence from operator

Choose Hybrid when:

  • Mission-critical application (parking for paid zones)
  • Want redundancy against single network failure
  • Can afford 35% cost premium for 99.9% reliability

Key Insights:

  1. Scale matters: Sigfox is cheaper below ~8,000 devices; LoRaWAN cheaper above that
  2. Opex compounds: Sigfox’s $6-8/year per device adds up over 10 years
  3. Frequency constraint costs money: Reducing updates from 5min to 10min may lose parking revenue
  4. Infrastructure amortizes: LoRaWAN’s gateway cost is one-time, spreads across all devices
  5. Battery life impacts TCO: LoRaWAN’s longer battery life (5 years vs 3) saves $100k in this scenario

34.6 Key Takeaways

After completing this module, you will be able to:

  1. When to Use Sigfox:
    • Small infrequent messages (<12 bytes, <140/day)
    • Existing operator coverage
    • Cost-sensitive deployments (<10,000 devices)
    • No infrastructure management capability
  2. Sigfox Limitations:
    • 12-byte uplink / 8-byte downlink payloads
    • 140 uplink / 4 downlink messages per day
    • Operator-dependent coverage (cannot deploy own base stations)
    • 30-90 second typical latency
  3. Technology Comparison:
    • Sigfox: Cheapest for <10K devices, operator-managed
    • LoRaWAN: Best for >10K devices, user-deployable
    • NB-IoT: Premium option for mobility and high data rates
  4. Best Practices:
    • Always verify coverage before mass deployment
    • Use integer encoding (not floats) for payloads
    • Design for uplink-only operation
    • Pilot test in actual deployment environment

Common Pitfalls

Students who start with Sigfox deployment hands-on without first understanding the 12-byte payload and 140-message constraints encounter repeated design failures. Build solid understanding of constraints before attempting implementation.

Sigfox technology evaluations that don’t acknowledge the 2022 Unabiz acquisition provide incomplete risk assessment. Always include current network stability and operator commitment in technology selection decisions.

Sigfox and LoRaWAN have different strengths and appropriate use cases. Frame technology selection as “which technology best fits these specific requirements” rather than one technology being universally superior.

Understanding Sigfox modulation theory without hands-on lab experience makes concepts abstract and easily forgotten. Connect theory to practice: why does 100 Hz bandwidth achieve high sensitivity? (Narrower filter admits less noise.) How does this manifest in lab measurements?

34.7 What’s Next

After completing this module, continue with these related topics:

Chapter Focus Area
LoRaWAN Architecture Compare Sigfox with user-deployable LPWAN alternative
NB-IoT Fundamentals Cellular LPWAN option for higher data rates and mobility
Network Planning General IoT network design methodology and deployment strategies
LPWAN Fundamentals Foundation concepts underlying all LPWAN technologies
Study Recommendation

Estimated time: 52 minutes (15 + 12 + 10 + 15)

Suggested approach:

  1. Read Introduction chapter (focus on scenarios and mistakes)
  2. Skim Technology chapter (bookmark for reference)
  3. Work through Examples (practice calculations)
  4. Take Assessment quizzes (test retention)

For exams: Focus on message limits (140/4), payload sizes (12/8 bytes), cost crossover points, and technology comparisons.