LoRaWAN Traffic Analysis Dataset

This dataset was created by a LoRaWAN sniffer and contains packets, which are thoroughly analyzed in the paper Exploring LoRaWAN Traffic: In-Depth Analysis of IoT Network Communications. Data from the LoRaWAN sniffer was collected in four cities: Liege (Belgium), Graz (Austria), Vienna (Austria), and Brno (Czechia).

Gateway ID: b827ebafac000001

• Uplink reception (end-device => gateway)
• Only packets containing CRC, inverted IQ
• RX0: 867.1 MHz, 867.3 MHz, 867.5 MHz, 867.7 MHz, 867.9 MHz - BW 125 kHz and all SF
• RX1: 868.1 MHz, 868.3 MHz, 868.5 MHz - BW 125 kHz and all SF

Gateway ID: b827ebafac000002

• Downlink reception (gateway => end-device)
• Includes packets without CRC, non-inverted IQ
• RX0: 867.1 MHz, 867.3 MHz, 867.5 MHz, 867.7 MHz, 867.9 MHz - BW 125 kHz and all SF
• RX1: 868.1 MHz, 868.3 MHz, 868.5 MHz - BW 125 kHz and all SF

Gateway ID: b827ebafac000003

• Downlink reception (gateway => end-device) and Class-B beacon on 869.525 MHz
• Includes packets without CRC, non-inverted IQ
• RX0: 869.525 MHz - BW 125 kHz and all SF, BW 125 kHz and SF9 with implicit header, CR 4/5 and length 17 B

To open the pcap files, you need Wireshark with current support for LoRaTap and LoRaWAN protocols. This support will be available in the official 4.1.0 release. A working version for Windows is accessible in the automated build system.

The source data is available in the log.zip file, which contains the complete dataset obtained by the sniffer. A set of conversion tools for log processing is available on Github. The converted logs, available in Wireshark format, are stored in pcap.zip. For the LoRaWAN decoder, you can use the attached root and session keys. The processed outputs are stored in csv.zip, and graphical statistics are available in png.zip.

This data represents a unique, geographically identifiable selection from the full log, cleaned of any errors. The records from Brno include communication between the gateway and a node with known keys.

Test file :: 00_Test

• short test file for parser verification
• comparison of LoRaTap version 0 and version 1 formats

Brno, Czech Republic :: 01_Brno

• 49.22685N, 16.57536E, ASL 306m
• lines 150873 to 529796
• time 1.8.2022 15:04:28 to 17.8.2022 13:05:32
• preliminary experiment
• experimental device
  • Device EUI: 70b3d5cee0000042
  • Application key: d494d49a7b4053302bdcf96f1defa65a
  • Device address: 00d85395
  • Network session key: c417540b8b2afad8930c82fcf7ea54bb
  • Application session key: 421fea9bedd2cc497f63303edf5adf8e

Liege, Belgium :: 02_Liege :: evaluated in the paper

• 50.66445N, 5.59276E, ASL 151m
• lines 636205 to 886868
• time 25.8.2022 10:12:24 to 12.9.2022 06:20:48

Brno, Czech Republic :: 03_Brno_join

• 49.22685N, 16.57536E, ASL 306m
• lines 947787 to 979382
• time 30.9.2022 15:21:27 to 4.10.2022 10:46:31
• record contains OTAA activation (Join Request / Join Accept)
• experimental device:
  • Device EUI: 70b3d5cee0000042
  • Application key: d494d49a7b4053302bdcf96f1defa65a
  • Device address: 01e65ddc
  • Network session key: e2898779a03de59e2317b149abf00238
  • Application session key: 59ca1ac91922887093bc7b236bd1b07f

Graz, Austria :: 04_Graz :: evaluated in the paper

• 47.07049N, 15.44506E, ASL 364m
• lines 1015139 to 1178855
• time 26.10.2022 06:21:07 to 29.11.2022 10:03:00

Vienna, Austria :: 05_Wien :: evaluated in the paper

• 48.19666N, 16.37101E, ASL 204m
• lines 1179308 to 3657105
• time 1.12.2022 10:42:19 to 4.1.2023 14:00:05
• contains a total of 14 short restarts (under 90 seconds)

Brno, Czech Republic :: 07_Brno :: evaluated in the paper

• 49.22685N, 16.57536E, ASL 306m
• lines 4969648 to 6919392
• time 16.2.2023 8:53:43 to 30.3.2023 9:00:11