Architecture guide
What is LoRaWAN? A Practical Guide for Buildings, Utilities and Industry
LoRa, LoRaWAN, gateways, network servers and device classes explained, with a clear view of where LoRaWAN fits and where it does not.
By Faraz, Co-Founder, CTO & Head of R&D, MatrixAI · · Updated · 15 min read
LoRa and LoRaWAN are not the same thing
LoRa is the radio modulation — a chirp spread-spectrum technique that allows small amounts of data to travel long distances with very little power. LoRaWAN is the network protocol built on top of LoRa. It defines how devices join a network, how messages are secured, how gateways forward traffic and how the network server manages devices.
In practice, when people talk about a LoRaWAN deployment, they mean the whole system: battery-powered sensors, gateways, a network server and the applications that use the data.
The four building blocks of a LoRaWAN network
- End devices — sensors, meters, converters and actuators that send small messages (uplinks) and can receive commands (downlinks).
- Gateways — radio receivers that forward every message they hear to the network server over Ethernet, 4G or other IP backhaul.
- Network server — the brain of the network (for example ChirpStack). It de-duplicates messages, manages security keys, adapts data rates and schedules downlinks.
- Application layer — decoders, IoT platforms, BMS, CAFM, SCADA or analytics tools that turn payloads into decisions.
Why LoRaWAN suits buildings and infrastructure
- Long range: one gateway can cover a building, a campus or several kilometres outdoors depending on the environment.
- Low power: many battery-powered devices run for years on a single battery with typical reporting intervals.
- Deep indoor penetration: sub-GHz radio reaches risers, basements and plant rooms better than Wi-Fi or Bluetooth.
- Private networks: organisations can own their network end-to-end, with no per-device SIM fees.
- Open ecosystem: hundreds of vendors produce interoperable LoRaWAN devices.
Device classes A, B and C
Class A devices are the most power-efficient: they only listen for downlinks briefly after sending an uplink. They suit sensors and meters. Class B devices open scheduled receive windows, and Class C devices listen continuously, making them suitable for mains-powered actuators such as relays, valves and streetlight controllers that must respond quickly.
Spreading factors, data rates and airtime
LoRa trades speed for range using the spreading factor (SF). In the EU868 plan, devices use SF7 to SF12 on 125 kHz channels. Each step up roughly doubles the time a message spends on air, and improves receiver sensitivity so the signal can travel further or through more walls.
The practical effect is large. A small 12-byte meter reading takes around 50 ms to send at SF7, but well over a second at SF12. Long airtime drains batteries faster, uses more of the shared radio channel and eats into duty-cycle limits.
- DR5 (SF7, 125 kHz): about 5.5 kbit/s, up to 222 bytes per message — devices close to a gateway
- DR3 (SF9, 125 kHz): about 1.8 kbit/s, up to 115 bytes — mid-range
- DR0 (SF12, 125 kHz): about 250 bit/s, up to 51 bytes — the edge of coverage or deep indoors
This is why gateway placement matters so much: every device that can be moved from SF12 to SF7 by a better-placed gateway uses a fraction of the airtime and battery.
Adaptive data rate (ADR)
With ADR enabled, the network server watches the signal quality of each device's recent uplinks and tells static devices to use the fastest data rate and lowest transmit power that still reach a gateway reliably. On a well-designed network most fixed meters and sensors settle at fast data rates, which saves battery and capacity.
ADR suits fixed devices. For moving assets the radio conditions change too quickly for ADR to follow, so those devices usually use a fixed, more robust data rate.
Duty cycle: the EU868 rule that shapes every design
In the EU868 plan, most channels sit in sub-bands limited to a 1% duty cycle: a transmitter may be on air for at most 36 seconds per hour in that sub-band. The limit applies to gateways as well as devices, so every downlink — acknowledgements, join-accepts, ADR commands and application commands — uses part of the gateway's budget.
Designs that rely on confirmed uplinks or frequent downlinks can exhaust a gateway's budget and cause whole groups of devices to drop out for tens of minutes. We cover diagnosis and fixes in our article on LoRaWAN data gaps caused by gateway duty-cycle exhaustion.
Range in practice
Vendor range figures assume open line of sight. Real deployments depend on antenna height, construction and noise. As a planning guide:
- Inside a reinforced-concrete building: one gateway typically covers several floors; basements and meter rooms often need their own coverage
- Dense urban outdoor: around 1–3 km from a rooftop gateway
- Suburban, rural or open industrial sites: 5–15 km is possible with good antenna height and line of sight
An RF survey with a test device at the actual meter and sensor positions is the only reliable way to size the number of gateways.
Battery life
Battery life is set by how often a device transmits, its spreading factor, the payload size, how many downlinks it receives and its sleep current. A meter reporting every 15 minutes at SF7 can last many years; the same device stuck at SF12 with confirmed uplinks may last a fraction of that. Good network design, not just battery size, decides maintenance cycles.
Security
- AES-128 encryption with two separate keys: the network session key protects the network layer and the application session key encrypts the payload end-to-end to the application server.
- Over-the-air activation (OTAA) is preferred over activation by personalisation (ABP), because session keys are freshly derived at each join.
- Root keys must be stored and distributed securely, and gateways and the network server hardened like any other internet-facing system.
Public or private network servers
The network server can be a public operator's, a managed cloud service or your own. Popular options include ChirpStack (open source), The Things Stack, Actility ThingPark and Kerlink's Wanesy. Running a private network server gives you full control of devices, keys and data, with no per-device fees; a managed service reduces the operations you need to run yourself.
What LoRaWAN is not designed for
LoRaWAN carries small payloads at low data rates. It is not suitable for video, audio, high-frequency waveforms or fast closed-loop control. A good architecture uses LoRaWAN for monitoring, alarms and supervisory control, and keeps high-bandwidth or safety-critical functions on wired or other networks.
Frequency plan in the UAE
Deployments in the UAE commonly use the EU868 frequency plan, subject to local regulatory requirements. Device and gateway selection should always confirm the correct regional plan and type approval before procurement.
Getting started
The fastest route to a reliable network is a short requirements and RF/site assessment, followed by a pilot on a representative area. MatrixAI designs the architecture, selects devices and gateways, configures the network server and integrates data into your existing systems.
Frequently asked questions
What is the difference between LoRa and LoRaWAN?
LoRa is the long-range radio modulation used by the devices. LoRaWAN is the network protocol on top of it, defining how devices join, how messages are secured and how gateways and the network server manage traffic.
How far can LoRaWAN reach?
Indoors, one gateway commonly covers a building or several floors; outdoors, ranges of several kilometres are possible with good gateway placement. Actual range depends on construction, antenna height and interference, which is why we recommend an RF assessment.
What frequency does LoRaWAN use in the UAE?
Deployments in the UAE commonly use the EU868 frequency plan (863–870 MHz). Devices and gateways should be confirmed for the regional plan and local type approval before procurement.
How long do LoRaWAN batteries last?
From months to more than ten years, depending on reporting interval, spreading factor, payload size and downlinks. Fixed meters on a well-designed network commonly reach multi-year battery life.
Is LoRaWAN secure?
LoRaWAN uses AES-128 encryption with separate network and application session keys. Security also depends on key management, gateway hardening and the security of the integration layer.