DOI: 10.5281/zenodo.8090619
title: LoRaWAN Traffic Analysis Dataset

description: This dataset was created by a LoRaWAN sniffer and contains packets, which are thoroughly analyzed in the paper <em>Exploring LoRaWAN Traffic: In-Depth Analysis of IoT Network Communications</em>. Data from the LoRaWAN sniffer was collected in four cities: Liege (Belgium), Graz (Austria), Vienna (Austria), and Brno (Czechia). Gateway ID: <code>b827ebafac000001</code> Uplink reception (end-device =&gt; 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: <code>b827ebafac000002</code> Downlink reception (gateway =&gt; 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: <code>b827ebafac000003</code> Downlink reception (gateway =&gt; 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 <code>pcap</code> 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 <code>log.zip</code> 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 <code>pcap.zip</code>. For the LoRaWAN decoder, you can use the attached root and session keys. The processed outputs are stored in <code>csv.zip</code>, and graphical statistics are available in <code>png.zip</code>. 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 :: <code>00_Test</code> short test file for parser verification comparison of LoRaTap version 0 and version 1 formats Brno, Czech Republic :: <code>01_Brno</code> 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: <code>70b3d5cee0000042</code> Application key: <code>d494d49a7b4053302bdcf96f1defa65a</code> Device address: <code>00d85395</code> Network session key: <code>c417540b8b2afad8930c82fcf7ea54bb</code> Application session key: <code>421fea9bedd2cc497f63303edf5adf8e</code> Liege, Belgium :: <code>02_Liege</code> :: <strong>evaluated in the paper</strong> 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 :: <code>03_Brno_join</code> 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: <code>70b3d5cee0000042</code> Application key: <code>d494d49a7b4053302bdcf96f1defa65a</code> Device address: <code>01e65ddc</code> Network session key: <code>e2898779a03de59e2317b149abf00238</code> Application session key: <code>59ca1ac91922887093bc7b236bd1b07f</code> Graz, Austria :: <code>04_Graz</code> :: <strong>evaluated in the paper</strong> 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 :: <code>05_Wien</code> :: <strong>evaluated in the paper</strong> 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 :: <code>07_Brno</code> :: <strong>evaluated in the paper</strong> 49.22685N, 16.57536E, ASL 306m lines 4969648 to 6919392 time 16.2.2023 8:53:43 to 30.3.2023 9:00:11