Datasets
Standard Dataset
Dataset for End-to-end Latency Measurements of Standalone and Concatenated LPWAN Architectures with LoRa and LTE-M Networks
- Citation Author(s):
- Submitted by:
- Mouhamed Abdulla
- Last updated:
- Mon, 07/12/2021 - 13:08
- DOI:
- 10.21227/zzax-g919
- Data Format:
- License:
2735 Views
0 ratings - Please login to submit your rating.
Abstract
Extensive experimental measurement campaigns of more than 30,000 data points of end-to-end latency measurements for the following network architecture schemes is available:
- Unlicensed IoT (standalone LoRa)
- Cellular IoT (standalone LTE-M)
- Concatenated IoT (LoRa interfaced with LTE-M)
Download Data.zip to access all relevant files for the open data measurements.
Related Paper:
A. Ramoutar, Z. Motamedi and M. Abdulla, "Latency of Concatenating Unlicensed LPWAN with Cellular IoT: An Experimental QoE Study," In Proc. of the 94th IEEE Vehicular Technology Conference (VTC2021-Fall), pp. 1-6, virtual conference, Sep. 27-30, 2021. (arXiv:2105.10852)
Instructions:
End-to-end Latencies for Standalone LoRa:
- Files: lora_dataset_qty10722.json OR lora_dataset_qty10722.csv
- Number of Data Points: 10,722 (all latency measurements are in milliseconds).
- Measurement Information: name=lora in Toronto, Ontario; start=2020-09-15T16:38:24.000+00:00; end=2020-09-15T19:39:09.311+00:00.
- Network Setup: Dataset of end-to-end latency for a native LoRa LPWAN system captured for a defined duration outdoors. TTGO LoRa32 node to TTGO LoRa32 Gateway to Unifi AC AP Lite radio over Cat5e ethernet to EdgeRouter ER-X. Uplink to the internet is to Rogers Telecommunications Network using CODA-4582 cable modem. Downlink to core infrastructure from internet is through Rogers Telecommunications Network using CODA-4582 cable modem. An EdgeRouter ER-X routes over Cat5e to a Broadcom NC373i NIC to HP Proliant DL380 G5. End-user client Samsung Galaxy S7 performs RESTful HTTP request over Rogers Telecommunications Mobile Network to core infrastructure, which responds across the same.
End-to-end Latencies for Standalone LTE-M:
- Files: ltem_dataset_qty10762.json OR ltem_dataset_qty10762.csv
- Number of Data Points: 10,762 (all latency measurements are in milliseconds).
- Measurement Information: name=ltem in Toronto, Ontario; start=2020-09-16T14:01:03.000+00:00; end=2020-09-16T16:14:44.089+00:00.
- Network Setup: Dataset of end-to-end latency for a native LTE-M LPWAN system captured for a defined duration outdoors. MKR1500 node to LTE-M base station with an uplink to Bell Canada's LTE-M IoT network edge, eventually reaching the internet through the carrier network. Downlink to core infrastructure from internet is through Rogers Telecommunications Network using CODA-4582 cable modem. An EdgeRouter ER-X routes over Cat5e to a Broadcom NC373i NIC to HP Proliant DL380 G5. End-user client Samsung Galaxy S7 performs RESTful HTTP request over Rogers Telecommunications Mobile Network to core infrastructure, which responds across the same.
End-to-end Latencies for Concatenated LoRa with LTE-M:
- Files: lora+ltem_dataset_qty10452.json OR lora+ltem_dataset_qty10452.csv
- Number of Data Points: 10,452 (all latency measurements are in milliseconds).
- Measurement Information: name=lora+ltem in Toronto, Ontario; start=2020-09-15T15:12:21.000+00:00; end=2020-09-15T16:01:24.956+00:00.
- Network Setup: Dataset of end-to-end latency for a native LTE-M LPWAN system captured for a defined duration outdoors. TTGO LoRa32 node to TTGO LoRa32 Gateway to MKR1500 backhaul node to LTE-M base station with an uplink to Bell Canada's LTE-M IoT network edge, eventually reaching the internet through the carrier network. Downlink to core infrastructure from internet is through Rogers Telecommunications Network using CODA-4582 cable modem. An EdgeRouter ER-X routes over Cat5e to a Broadcom NC373i NIC to HP Proliant DL380 G5. End-user client Samsung Galaxy S7 performs RESTful HTTP request over Rogers Telecommunications Mobile Network to core infrastructure, which responds across the same.
Latency for Core Service and User Equipment GUI Rendering:
- Files: core-service.json OR core-service.csv
- Files: user-equipment.json OR user-equipment.csv
- Units: All latency measurements are in milliseconds.
