Skip to main content

LPWAN Decoded (Extract)

Page 1

#01

LPWAN Decoded

on

t s . P ra c

tic

a

b

y

El

IS

ed

up

at

po

Cre

rt

ve n .

Wireless & Communications

P ro

Electr

s

gh i s In

l.

ic

LoRaWAN, Sigfox, NB-IoT & LTE-M Compared

ek

tor

’s C o

n t e n t Te a

m

w

it h

A


LPWAN Decoded LoRaWAN, Sigfox, NB-IoT & LTE-M Compared A Technical Brief Compiled By Elektor’s Content Team


This is an Elektor publication. Elektor is the media brand of Elektor International Media BV. Elektor International Media BV Postbus 11 6114 ZG Susteren Netherlands Phone: +31 46 4389444 Website: www.elektor.com All Rights Reserved No part of this book may be reproduced in any material form, including photocopying, or storing in any medium by electronic means and whether or not transiently or incidentally to some other use of this publication, without the written permission of the copyright holder except in accordance with the provisions of the Copyright Designs and Patents Act 1988 or under the terms of a licence issued by the Copyright Licencing Agency Ltd., 90 Tottenham Court Road, London, England W1P 9HE. Applications for the copyright holder’s permission to reproduce any part of the publication should be addressed to the publishers. Declaration The author and publisher have made every effort to ensure the accuracy of the information contained in this book. They do not assume, or hereby disclaim, any liability to any party for any loss or damage caused by errors or omissions in this book, whether such errors or omissions result from negligence, accident, or any other cause. All product names, trademarks, and registered trademarks mentioned in this publication are the property of their respective owners and are acknowledged accordingly. Founded in 1961, Elektor has a long history of exploring and reporting on emerging technologies, including artificial intelligence. Today, Elektor employees use AI tools as part of their editorial, business, and engineering workflows. We encourage employees to experiment responsibly with AI, share learnings across teams, and contribute to the continuous improvement of our AI practices. AI may assist our teams with tasks such as engineering support, editing/writing/proofreading, news aggregation, translations, project planning, graphic/layout preparation, research, and more. AI tools help us work more efficiently and explore new ideas. However, AI is used only as a tool. We are not sharing personal information with AI. All Elektor content, projects, and publications are guided, reviewed, and validated by humans. We are guided by a simple principle: AI technology empowers people. It does not replace them. Human expertise, curiosity, and engineering creativity remain the foundation of Elektor. With an internal AI Control Group (comprising employees from various teams within Elektor) in place, we remain committed to accuracy, transparency, and the high editorial standards that have defined Elektor for decades. ISBN 978-3-89576-752-4 (Print) ISBN 978-3-89576-753-1 (eBook PDF) © Copyright 2026 Elektor International Media BV Website: www.elektor.com Editor: The Elektor Content Team Cover Design: Harmen Heida Technical Review: C. J. Abate, Saad Imtiaz Production: Patrick Wielders Elektor is the world’s leading source of essential technical information and electronics products for pro engineers, electronics designers, and the companies seeking to engage them. Each day, our international team develops and delivers high-quality content — via a variety of media channels (including magazines, video, digital media, and social media) in several languages — relating to electronics design and DIY electronics. Memberships: www.elektormagazine.com/membership Store: www.elektor.com Magazine: www.elektormagazine.com

4

Elektor


Content Foreword: Making LPWAN Practical for Engineers

7

Chapter 1: Why LPWAN Exists

8

1.1 — The Connectivity Gap in Early IoT 1.2 — LPWAN’s Design Philosophy 1.3 — Applications That Drive LPWAN Adoption 1.4 — Link Budget, Interference, and Efficiency 1.5 — The Evolving IoT Connectivity Landscape

8 9 10 11 12

Chapter 2: The Physics You Can’t Negotiate

13

2.1 — Noise Is Always There 2.2 — Free-Space Path Loss: Distance Always Costs 2.3 — Shannon’s Limit: The Hard Ceiling 2.4 — How LPWAN Achieves Long Range 2.5 — LoRa and Chirp Spread Spectrum 2.6 — Sigfox and Ultra-Narrowband Minimalism 2.7 — Licensed Spectrum: NB-IoT and LTE-M 2.8 — Engineering Reality: Physics Comes First

13 13 14 14 15 15 16 17

Chapter 3: LPWAN Architectures at a Glance

18

3.1 — Two Families, Two Philosophies 3.2 — Non-Cellular LPWAN Architectures 3.3 — Cellular LPWAN Architectures 3.4 — Why the Architectural Split Matters 3.5 — Engineering Takeaway for Elektor Readers

18 19 20 22 22

Chapter 4: LoRaWAN Deep Dive

23

4.1 — LoRa vs. LoRaWAN 4.2 — The Physical Layer: Chirp Spread Spectrum (CSS) 4.3 — What LoRaWAN Adds: Networking, Security, and Device Behavior 4.4 — LoRaWAN Device Classes 4.5 — Hardware Design: Modules vs. Discrete RF 4.6 — Network Ownership: LoRaWAN’s Defining Advantage 4.7 — Where LoRaWAN Shines

23 23 24 25 26 26 27

Chapter 5: Sigfox Deep Dive

28

5.1 — Sigfox Architecture: Operator Network First 5.2 — The Physical Layer: Ultra-Narrowband (UNB) 5.3 — Message Strategy: Redundancy Over Interaction

28 28 30


5.4 — Power Consumption and Device Simplicity 5.5 — Spectrum and Interference Environment 5.6 — Sigfox vs. LoRaWAN: A Useful Contrast 5.7 — Where Sigfox Stands Out 5.8 — The Core Limitation: Ecosystem Dependency

30 30 31 31 32

Chapter 6: NB-IoT Deep Dive

33

6.1 — Architectural Foundation: Cellular LPWAN by Design 6.2 — Spectrum and Deployment Modes 6.3 — Coverage Enhancement Through Repetition 6.4 — Power Consumption: Low, But Not “LoRa-Class” 6.5 — Data Rate, Latency, and Payload Flexibility 6.6 — Module and Hardware Considerations 6.7 — Where NB-IoT Excels 6.8 — Engineering Perspective: NB-IoT as Managed LPWAN

33 34 34 34 34 35 35 36

Chapter 7: LTE-M Deep Dive

37

7.1 — LTE-M in the 3GPP Cellular IoT Family 7.2 — Bandwidth and Throughput Advantages 7.3 — Mobility Support: LTE-M’s Key Differentiator 7.4 — Latency and Responsiveness 7.5 — Power Consumption: Higher Capability, Higher Peaks 7.6 — Voice and IoT Product-Class Features 7.7 — Hardware and Certification Implications 7.8 — Where LTE-M Shines

37 37 38 38 39 39 40 40

Chapter 8: LoRaWAN vs Sigfox vs NB-IoT vs LTE-M

42

8.1 — The Two Axes That Matter Most 8.2 — Range: The Link Budget Reality 8.3 — Battery Life and Power Profiles 8.4 — Latency, Downlink Capability, and Deployment 8.5 — Practical Selection Guidance

42 43 43 43 44

Chapter 9: Takeaways and the Future of LPWAN

46

Thank You

49

Become an Elektor Member Stay Connected

49 49


Foreword: Making LPWAN Practical for Engineers At Elektor, we are dedicated to assisting engineers, makers, and students on their journeys to design and sell real-world electronic solutions. For decades, long before the Internet of Things (IoT) became an everyday reality, our editors, engineers, and contributors have built a reputation on clarifying what matters and communicating complex electronics theory into decisions that work at the workbench. That tradition is the reason Elektor readers trust us. We don’t simply report on technology. We elucidate it. For much of my career, I have focused my work on translating complex engineering into compelling technical narratives. Today, in my role as Elektor’s Chief Communications and Content Officer, I see the same pattern repeat itself whenever a technology category matures: the number of options grows, the claims get louder, and the practical differences get harder to see. Low-Power Wide-Area Network (LPWAN) technology is exactly at that stage. LoRaWAN, Sigfox, NB-IoT, and LTE-M are no longer “emerging.” They are deployed and shipping inside real products. These technologies are shaping design constraints in ways that can either make your system elegant or doom it to failure. That is why we prepared this technical brief. In “LPWAN Decoded: LoRaWAN, Sigfox, NB-IoT & LTE-M Compared,” we focus on key topics such as link budget reality, power profiles, deployment models, certification friction, and lifecycle implications. If you will be selecting an LPWAN stack the way you would select a microcontroller — based on constraints, tradeoffs, and long-term maintainability — this document is meant to shorten your path to success. “LPWAN Decoded” is not a final, authoritative book about the subject. Rather, it is meant to be compact and immediately useful, bringing together the key explanations and helpful engineering tips. It curates insights from the Elektor engineering team, Elektor authors and contributors, and carefully vetted AI-assisted research (including Elektor GPT), alongside select online resources where they add clarity. We aim to help you move from confusing options to confident LPWAN decisions. The chapters that follow assume a simple premise that Elektor has returned to again and again since its founding in 1961: regardless of how the hardware changes, the fundamentals always matter. When you understand the essentials, the right choice tends to reveal itself.

C. J. Abate Chief Communications and Content Officer Elektor International Media


Chapter 1: Why LPWAN Exists In the early years of the Internet of Things (IoT), engineers confronted a persistent paradox: sensors, microcontrollers, and low-cost hardware were more capable and energy-efficient than ever, yet the connectivity technologies available at the time struggled to support real-world IoT deployments. Solutions like Wi-Fi, Bluetooth, and legacy cellular (2G/3G/4G) had been designed for a fundamentally different set of assumptions. They were intended for frequent, high-throughput communication over short to moderate distances, with ample power availability. When confronted with devices that needed to operate for years on coin-cell batteries, transmit only small packets of data, and often sit in remote locations, these traditional connectivity options proved inadequate. This problem laid the groundwork for Low-Power Wide-Area Networks (LPWAN), which is a family of wireless technologies designed to connect low-power IoT devices over long distances with minimal energy use. Elektor’s engineering team prepared this Technical Brief because LPWAN technology has matured into a practical — and sometimes confusing — set of choices that directly affect real designs: power budget, coverage expectations, deployment cost, regulatory constraints, module availability, and long-term maintainability. Engineers are now expected to select a connectivity stack as deliberately as they select a microcontroller or key components in a design. But how? We start by looking at the connectivity challenges of the early IoT. We then touch on how LPWAN works by giving up some speed to achieve better range and battery life.

1.1 — The Connectivity Gap in Early IoT Early IoT deployments ran into a simple problem. The wireless options were decent but not ideal for tiny, battery-powered devices, especially those which would have to connect occasionally from far away for years at a time. Older wireless tools worked great for what they were built to do. > Wi-Fi delivers high data rates suitable for broadband Internet access but requires relatively high power and dense infrastructure. > Bluetooth and ZigBee are optimized for short-range, low-power connectivity, often under 100 m, but they don’t have the range needed to cover a city or a wide rural area. > Cellular (2G/3G/4G/LTE) offers wide coverage but was originally designed for voice and broadband data with expensive, power-hungry radios. Moreover, sunsetting of 2G/3G networks left many machine-type communication (MTC) solutions stranded as service windows closed. [1]

8

Elektor


In the context of IoT, most devices do not need high throughput; they need connectivity that: > Consumes minimal energy, enabling battery lifetimes of years rather than months. > Supports long physical range, from urban spans of a few kilometers up to tens of kilometers in rural environments. > Handles low duty-cycle traffic, where devices send small bursts of data sporadically rather than sustained streams. > Scales to massive numbers of endpoints without prohibitive infrastructure cost. [2] Put plainly, the mainstream protocols weren’t built for this specific mix of constraints, especially the “years of battery life” requirement paired with wide-area reach. This is exactly the gap LPWAN technologies were created to fill. Learn More Elektor IoT & Sensors [3] Elektor Wireless & Communication [4]

1.2 — LPWAN’s Design Philosophy At its core, LPWAN flips the optimization priorities of conventional networks. Rather than striving for raw bitrate or low latency, LPWAN designs aim to minimize the energy consumed per bit transferred, trading data speed and throughput for deep energy savings and extended coverage. This shift enables devices to remain dormant most of the time, waking only to transmit brief messages when necessary. [5]

LPWAN Decoded: LoRaWAN, Sigfox, NB-IoT & LTE-M Compared

9


Key aspects of the LPWAN design philosophy include: > Low Power Consumption: Radios are engineered to operate in ultra-low-power modes and wake infrequently, allowing battery lifetimes measured in years on small cells. > Small, Infrequent Messages: Because LPWAN standards deliberately constrain payload sizes and limit duty cycles, energy usage is kept minimal, with networks optimized for sparse data transmission. > Tolerant Latency: Many IoT applications do not require real-time responsiveness. LPWAN protocols accept higher latencies in exchange for power savings. > Extended Range: Narrowband modulation techniques and sub-GHz frequency use result in high link budgets and long propagation distances. This is especially beneficial for sprawling or infrastructure-poor environments. Rather than being a “lesser” form of connectivity, LPWAN represents an adjustment to meet real requirements for billions of connected sensors that simply don’t need broadband. When engineers are connecting countless sensors that only need to send small amounts of data occasionally, broadband is unnecessary. LPWAN exists because the real challenge isn’t speed, but achieving reliable, long-range communication with minimal power and cost. Energy per bit optimization is a network design approach that focuses on using the least possible power to transmit each piece of data. It favors small, occasional messages over high-speed communication.

1.3 — Applications That Drive LPWAN Adoption LPWAN technologies aren’t designed for every IoT application. They exist for the scenarios many Elektor community members run into: projects where the “hard part” isn’t the sensor or the microcontroller, but getting a tiny device to report a few bytes reliably, over long distances, for years, without a wall plug nearby. If you’re building something that only needs to check in occasionally, LPWAN can be the difference. And in classic Elektor fashion, the value here isn’t theoretical. It shows up in practical applications where range, battery life, and low maintenance are essential. Where those attributes match the system requirements, LPWAN solutions excel. Consider some use cases: > Smart Metering: Transmitting periodic usage statistics from electric, gas, or water meters. LPWAN’s energy efficiency and long range make it ideal for remote or hard-toaccess units. [6] > Environmental Sensing: Agricultural soil moisture, remote weather stations, or flooding sensors — devices deployed over wide areas, powered by long-life batteries or energy harvesting. > Asset Tracking: Tracking location or status of goods, containers, and equipment spread across cities or national rail networks where power access is limited.

10

Elektor


> Infrastructure Monitoring: Bridges, pipelines, and industrial assets benefit from low-power radios communicating over long distances without extensive infrastructure. These aren’t fringe use cases. They’re foundational to the scaling of IoT across industry, agriculture, utilities, and smart cities. Duty cycle matters. Most LPWAN nodes send tiny bursts of data only occasionally. If that matches your application, LPWAN delivers the range and battery life you’re after without the cost and power draw of “always-on” connectivity.

1.4 — Link Budget, Interference, and Efficiency From the moment an RF link leaves an antenna, it encounters the physics of propagation loss, multipath fading, and interference. A thousand engineers can craft an elegant protocol stack, but if the link budget doesn’t support the intended range and power envelope, the design fails in practice. That’s why engineers keep coming back to the fundamentals: link budget, interference tolerance, and efficiency. If those three don’t work out, nothing else matters.

LPWAN technologies directly embrace these realities: > Link Budget Focus: By using narrowband or spread spectrum modulation in sub-GHz bands, LPWAN achieves significant link budget gains compared to ultra-wideband systems. This enhances coverage while reducing power.

LPWAN Decoded: LoRaWAN, Sigfox, NB-IoT & LTE-M Compared

11


> Spectrum Efficiency: Techniques like ultra-narrowband (UNB) employed by Sigfox squeeze transmissions into very narrow channels to reduce noise and energy consumption, enabling longer range with limited power. > Interference Resilience: Through careful modulation and channel access design, LPWAN standards can maintain connectivity even in environments crowded with Wi-Fi, Bluetooth, and cellular signals. In other words, LPWAN optimizes for the messy RF world. For Elektor community members, the practical takeaway is simple: if you want an IoT system that performs well outside the lab, you have to treat RF as a first-order design constraint, not a checkbox at the end. LPWAN is not magic: it’s disciplined engineering that aligns the physics, the protocol, and the power budget, so real deployments behave like your block diagram promised. Link budget is your back-of-the-envelope accounting of how much signal strength a wireless link can afford to lose and still deliver reliable communication over the intended range.

1.5 — The Evolving IoT Connectivity Landscape LPWAN’s rise mirrors a broader maturation in how engineers approach IoT connectivity: select the tool that matches the job. Rather than forcing low-data sensors onto networks designed for products like smartphones and applications such as video streaming, LPWAN gives engineers a purpose-built set of technologies that balance the following: > > > >

Power usage vs. battery lifetime Range vs. infrastructure cost Data rate vs. energy per bit Latency tolerance vs. transmission frequency

This approach contrasts sharply with early IoT connectivity solutions that attempted to adapt Wi-Fi or cellular technologies ill-suited to the task. LPWAN isn’t a compromise. It’s a recalibration around the real physical, economic, and operational requirements of IoT systems. As we transition into later chapters that cover specific LPWAN standards (LoRaWAN, Sigfox, NB-IoT, LTE-M), appreciating why LPWAN was created clarifies the tradeoffs each standard makes — and why those tradeoffs matter in system design. [1] Wikipedia, "LPWAN.": https://bit.ly/elektor-lpwan [2] Springer, "A systematic and comprehensive review on low power wide area network," 2025.: https://bit.ly/ elektor-springer-lpwan [3] Elektor IoT & Sensors: https://www.elektormagazine.com/iot-sensors [4] Elektor Wireless & Communication: https://www.elektormagazine.com/wireless-communication [5] R. Heredia, "LPWANs for IoT Connectivity," Zipit 2025.: http://www.zipitwireless.com/blog/lpwans-for-iotconnectivity [6] Pelion, "What is LP-WAN?": https://bit.ly/elektor-pelion-lpwan

12

Elektor


LPWAN Decoded: LoRaWAN, Sigfox, NB-IoT & LTE-M Compared The Internet of Things depends on a critical question. How do you connect devices that must operate for years on tiny batteries, often miles from the nearest power outlet? The Elektor Technical Brief titled LPWAN Decoded: LoRaWAN, Sigfox, NB-IoT & LTE-M Compared provides a practical guide to the technologies that have become the backbone of long-range, low-power IoT connectivity. Compiled by the Elektor Content Team, this concise technical brief examines the real engineering tradeoffs behind today’s leading Low-Power Wide-Area Network (LPWAN) technologies: LoRaWAN, Sigfox, NB-IoT, and LTE-M.

Wireless & Communications

By referencing a wide range of Elektor articles and other online content, this document explains why link budget, noise, bandwidth, and power consumption ultimately determine system performance. From there, it explores the architectures, strengths, limitations, and deployment realities of each major LPWAN technology, helping you understand not just how they work, but when and why to use them. Whether you’re designing smart meters, industrial sensors, agricultural monitoring systems, asset trackers, or connected infrastructure, this guide provides the insights needed to make informed connectivity decisions. Along the way, you’ll discover: > > > > > >

Why LPWAN technologies emerged and where they fit in the IoT landscape The RF fundamentals that drive range, reliability, and battery life Details about LoRaWAN, Sigfox, NB-IoT, and LTE-M Practical comparisons of power, coverage, latency, cost, and deployment models Guidance for selecting the right LPWAN technology for your application Emerging trends shaping the future of long-range IoT connectivity

Clear, accessible, and grounded in real engineering practice, this Technical Brief helps you move beyond specifications and marketing claims to understand what matters most. If you’re building connected products that need to survive in the field — not just in the lab — this is the LPWAN guide you’ll want at your side. Elektor helped launch the first wave of electronics makers in 1961. Since then, our global community has grown by hundreds of thousands of active members (comprising professional engineers, makers, and students) and more than 500 contributing experts. Every day, we inspire members to design and earn money with electronics.

Elektor International Media www.elektor.com www.elektormagazine.com Print version: €19.95 eBook version: €14.95


Turn static files into dynamic content formats.

Create a flipbook
LPWAN Decoded (Extract) by Elektor - Issuu