Knowledge/Interfaces explained/LoRa and LoRaWAN

Interfaces explainedLoRaWAN

What is LoRaWAN? LoRa and LoRaWAN for meters explained

LoRaWAN is a radio network for small amounts of data over long distances. Meters send their values at fixed intervals to a gateway; no cable to the meter is needed. LoRa is the radio technique underneath, LoRaWAN the network protocol on top.

Key facts

  • LoRa is a radio modulation with chirp spread spectrum: plenty of range, little data rate.
  • LoRaWAN is the network protocol of the LoRa Alliance, with gateways, network server and encryption.
  • In Europe LoRaWAN transmits licence-free in the 863–870 MHz band, with limited airtime (duty cycle).
  • Devices join the network via OTAA with DevEUI, JoinEUI and AppKey.
  • Suitable for quarter-hourly or hourly values, not for values every second.

On this page

What is the difference between LoRa and LoRaWAN?

LoRa is the radio technique: a modulation that spreads a narrow signal so widely that it is still detected even below the noise. That gains range and costs data rate. LoRaWAN is the network protocol on top. It governs how devices join, how the data is encrypted and how it gets from the gateway to the network server. More in the article LoRa or LoRaWAN?.

How is a LoRaWAN network structured?

  1. End device: the meter or sensor. It sends its data by radio without being assigned to a particular gateway.
  2. Gateway: receives all LoRa packets within range and forwards them over Ethernet or mobile network to the network server.
  3. Network server: checks the packets, removes those received twice and manages devices and keys. Examples are The Things Network and ChirpStack.
  4. Application server: decrypts the payload and passes it on to your system via MQTT, HTTP or an API.

The payload is encrypted twice with AES-128: once for the network and once end to end for the application. The gateway does not see the content.

How does a device join: OTAA or ABP?

With OTAA (over-the-air activation), the device sends a join request with DevEUI and JoinEUI. The network server checks it with the AppKey and assigns new session keys. With ABP (activation by personalization), the session keys are stored permanently in the device. OTAA is more secure and the usual route.

What do classes A, B and C mean?

ClassReceptionPower consumptionTypical use
Atwo short receive windows after each transmissionvery lowbattery-powered sensors, water meters
Badditional receive windows on a schedulelowdevices that receive commands at fixed times
Creception open almost continuouslyhighermains-powered devices such as power meters

What range does LoRaWAN have?

Outdoors several kilometres are usual, in the countryside with a clear line of sight considerably more. Inside buildings the range is shorter: concrete ceilings, metal doors and meter cabinets attenuate the signal strongly, and basements are often the most difficult. A gateway in the building or an external antenna on the meter usually solves this.

How far a packet gets also depends on the spreading factor, SF7 to SF12. A higher spreading factor reaches further but takes longer to transmit and so uses more of the limited airtime. With ADR (adaptive data rate), the network server chooses for each device the lowest spreading factor that still arrives reliably.

Why does LoRaWAN not deliver values every second?

In the EU868 band a device may transmit at most 1 % of the time in most sub-bands. At a high spreading factor a single packet can take over a second, and the pause afterwards is correspondingly long. For meters this is no drawback: one value every 15 minutes is enough for billing and load profiles.

A LoRaWAN packet is also only a few dozen bytes in size and binary-coded. To turn the bytes into meter readings, the network or application server needs a decoder for the device in question. How this works is shown in the article Decoding the LoRa payload.

LoRaWAN with EMU devices

The EMU Professional II power meter with LoRa works to LoRaWAN 1.0.3 in class C, joins via OTAA by default and sends import and export per tariff every 15 minutes. It is available with an internal antenna or additionally with an SMA connector for an external antenna.

For The Things Network there is a device template, and we provide the decoder on GitHub. The guide is at EMU Professional II LoRa in The Things Network. If you do not want to run a network server of your own, you can receive the values directly in Joulio-Web with its integrated network server.

Frequently asked questions


Is LoRa the same as LoRaWAN?

No. LoRa is the radio technique, LoRaWAN the network protocol with gateways, network server and encryption that builds on LoRa.

Do I need a gateway of my own?

Not necessarily. Where a public network such as The Things Network or an operator’s network has coverage, that is enough. For meters in the basement, or when availability has to be guaranteed, a gateway of your own in the building is usually the better choice.

Is LoRaWAN encrypted?

Yes. The payload is encrypted with AES-128, separately for the network and for the application. Gateway and network operator do not see the readings.

How often can a LoRaWAN meter transmit?

That is limited by the duty cycle and the spreading factor. Intervals of 15 minutes to an hour are usual. The EMU Professional II transmits every 15 minutes by default.

What is the difference between LoRaWAN and Wireless M-Bus?

Both transmit at 868 MHz but are not compatible. Wireless M-Bus is intended for reading meters over short distances, for example via collectors in the building. LoRaWAN is a network with gateways and network server that bridges greater distances and delivers the data directly into the target system.

Read more


SEITEPower meter with LoRaEMU Professional II with LoRaWAN SEITEThe Things NetworkIntegrating the EMU Professional II LoRa SEITELoRa or LoRaWAN?The two terms clearly separated SEITEInterfaces explainedAll five interfaces compared

Reading meters by radio?


Send us the number of meters, their location in the building and the target system. We will tell you whether LoRaWAN fits and what it takes.

Phone
+41 (0)41 545 03 00

Technical support
helpdesk [at] emuag.ch
Support form →