What Is LoRaWAN
LoRaWAN is the leading low-power wide-area network (LPWAN) protocol for IoT devices that need to send small amounts of data over long distances on tiny amounts of power. Sensors running on coin-cell batteries can transmit to gateways many kilometers away for 5-10 years between battery changes. The tradeoffs that make this possible — very low bitrate, infrequent transmissions, asymmetric link, regulated duty cycle — define the application categories LoRaWAN is and isn't right for.
The four-piece architecture
| Component | Role |
|---|---|
| End device | The sensor or actuator. Transmits to nearby gateways. |
| Gateway | Receives device transmissions on LoRa radio; forwards via IP backhaul to network server. |
| Network server | Deduplicates packets received by multiple gateways, manages MAC layer, decrypts network header. |
| Application server | Receives decrypted application payload and handles business logic. |
Devices broadcast — they don't connect to a specific gateway. Whichever gateways happen to hear the transmission forward it to the network server. The network server deduplicates and picks the best copy.
The radio physics: LoRa modulation
LoRa uses chirp spread spectrum modulation in unlicensed sub-GHz bands (typically 868 MHz in Europe, 915 MHz in North America, 433 MHz in some regions). The technique trades data rate for sensitivity and range:
- Bandwidth: 125 or 250 kHz typically.
- Data rate: 0.3 kbps to ~50 kbps depending on spreading factor.
- Range: 2-5 km urban, 15+ km rural line-of-sight.
- Link budget: ~150 dB — comparable to deep-space communication relative to the small transmit power.
The "long range" name is justified — a single gateway can cover an entire small town in flat terrain.
The duty cycle constraint
Operating on unlicensed bands means following local duty-cycle regulations. In Europe, devices may transmit for at most 1% of the time on most bands (some sub-bands are 0.1%). A device that hits its duty-cycle limit must wait — often hours — before transmitting again.
This is the single biggest constraint shaping LoRaWAN application design. You cannot use it for chatty protocols, large file transfers, or real-time updates. You can use it for "transmit a few bytes every 10 minutes" style telemetry.
Device classes
Three classes balance power consumption against downlink latency:
| Class | Receive windows | Power | Downlink latency |
|---|---|---|---|
| A | Two short windows immediately after each uplink | Lowest (years on coin cell) | High — only when device just uplinked |
| B | Class A + additional scheduled windows synchronized via beacon | Moderate | Bounded; predictable |
| C | Continuous listening when not transmitting | Highest (mains-powered) | Immediate |
Class A is the default and the most common. Class B is useful for actuators that need infrequent commands at predictable times. Class C is for mains-powered devices that need real-time control.
Joining the network
Two activation modes:
- OTAA (Over-the-Air Activation) — device sends a join request with its DevEUI and AppEUI; network server responds with session keys. Keys are derived during the join and rotated when device rejoins. The secure and preferred method.
- ABP (Activation by Personalization) — device is pre-provisioned with static session keys. Simpler but less secure; keys don't rotate and the same keys are used forever.
The two-key encryption model
LoRaWAN encrypts in layers:
- NwkSKey (Network Session Key) — used for MAC-layer integrity (MIC). The network server can verify and route packets but not read payload.
- AppSKey (Application Session Key) — used for application payload encryption. Only the device and the application server have it. The network server never sees plaintext payload.
This separation enables the typical operational pattern: a public LoRaWAN operator (The Things Network, Helium, Senet, etc.) runs the network server, while you operate the application server with your own AppSKey. The operator forwards encrypted payloads to you.
What LoRaWAN is good for
- Environmental sensors — soil moisture, water level, temperature, air quality.
- Utility metering — water, gas, electricity meters reporting once per hour.
- Asset tracking — vehicles, shipping containers, livestock with GPS modules.
- Smart city infrastructure — parking sensors, smart waste bins, street lighting telemetry.
- Industrial monitoring — equipment vibration, pressure, status in remote facilities.
- Agriculture — crop monitoring, irrigation control, livestock tracking.
What LoRaWAN is not good for
- Streaming video, audio, or any continuous data.
- Real-time control of safety-critical systems (the downlink latency is too high for Class A).
- Firmware updates over the air (FUOTA exists but is slow and duty-cycle-constrained).
- Devices that need to send large payloads often.
- Indoor applications with thick walls and dense interference (sometimes works, sometimes doesn't).
LoRaWAN vs other LPWAN options
| Technology | Frequency | Coverage model | Tradeoffs |
|---|---|---|---|
| LoRaWAN | Unlicensed sub-GHz | Private or public networks | Open standard, low cost per device, long range |
| NB-IoT | Licensed cellular | Carrier-provided | Better indoor, higher cost per device, carrier dependency |
| LTE-M | Licensed cellular | Carrier-provided | Higher bandwidth, mobility support, voice possible |
| Sigfox | Unlicensed sub-GHz | Single operator (Sigfox network) | Tiny payloads, ultra-low power, single vendor |
Network ownership models
- Private network — you operate your own gateways and network server. Full control; capital and operational cost.
- Public network — you use a shared network (The Things Network, Helium, Senet, carrier-operated). Lower cost; rely on someone else's coverage.
- Hybrid — your private gateways supplement public coverage in specific locations.
Frequently Asked Questions
What is LoRaWAN?
A wide-area networking protocol for low-power IoT devices that operates on unlicensed sub-GHz radio bands. LoRaWAN uses LoRa (Long Range) modulation to achieve ranges of several kilometers in urban areas and tens of kilometers in line-of-sight conditions, while consuming so little power that battery life of 5-10 years is normal. It is designed for small, infrequent data transmissions — a few bytes every few minutes — not streaming.
What is the difference between LoRa and LoRaWAN?
LoRa is the physical layer — the radio modulation technique. LoRaWAN is the MAC layer protocol that runs on top of LoRa, defining how devices join networks, how messages are addressed, how encryption works, and how gateways relay data. You can use LoRa without LoRaWAN (for proprietary point-to-point links), but LoRaWAN is the standard for multi-device networks.
What are LoRaWAN device classes?
Three classes defining when the device listens for downlink messages. Class A devices only listen briefly after each uplink — lowest power, highest downlink latency. Class B devices schedule additional receive windows at regular intervals — moderate power, predictable downlink latency. Class C devices listen continuously when not transmitting — highest power, immediate downlink delivery. Class A is the default and covers most use cases.
How does LoRaWAN handle encryption?
Two layers of AES-128 encryption applied at the device. Network session key encrypts the MAC header for the network server; application session key encrypts the payload for the application server. The two are separated so the network operator can route packets without seeing application data, and the application sees nothing about radio-layer routing.
What is LoRaWAN best for?
Sensor telemetry that needs long battery life and infrequent updates over wide areas: smart agriculture (soil moisture, livestock tracking), utility metering (water, gas, electricity), asset tracking, environmental monitoring, smart city infrastructure (parking sensors, waste bin levels), and industrial equipment monitoring in remote locations. Not suitable for streaming, real-time control, or high-volume data.
Related Guides
More From This Section
All IoT Protocols Guides
MQTT, CoAP, Zigbee, Thread, Z-Wave, Matter, Modbus, and OPC UA.
Bluetooth Low Energy for IoT
How BLE works for IoT — advertising vs connections, GATT profile, pairing, BLE 5 features, BLE mesh for multi-device…
CoAP Protocol Deep Dive
How CoAP works — request/response over UDP, confirmable vs non-confirmable messages, observe, block-wise transfer, DTLS…
Run a Speed Test
Measure download, upload, ping, and jitter in your browser.