NB-IoT vs. LTE-M: Measurement Data of the Energy Consumption of LPWAN Technologies

<strong>NB-IoT vs. LTE-M: Measurement Data of the Energy Consumption of LPWAN Technologies</strong> This dataset contains the raw energy measurements as well as R scripts to reproduce the energy consumption plot for the corresponding paper. Each .csv file contains a specific set of measurements and we provide a script to read, process and plot the contained data. <strong>Figure 3</strong> Mean energy consumption of the different phases for Authentication for NB-IoT and LTE-M. Due to the fact that the duration of <em>Idle Connected</em> in the measurement scripts was 30 seconds and 60 seconds for <em>Idle Not Connected</em>, the D-value and the mean power consumption are divided by 2. Data – energy_measurements_fig3.csv Code – fig3.R <strong>Figure 4</strong> Mean energy consumption of the different phases for Data Connection and Download for NB-IoT and LTE-M for 1KB of data in HTTP. The delay between the measurements for Figure 4 were all 30 seconds long, but the identified <em>Standby</em> and <em>Idle</em> phases have different lengths. Therefore, the <em>Idle</em> phase values for both access technologies have been normalized and calculated for 20 seconds each. Data – energy_measurements_fig4.csv Code – fig4.R <strong>Figure 5</strong> Mean energy consumption of the different phases for Data Connection and Download for HTTP and MQTT for 1KB of data in NB-IoT. In this scenario the delay between the measurements were different again. For <em>MQTT</em> the delay was 150 seconds and for <em>HTTP</em> 30 seconds. Therefore, the data during the <em>Idle</em> and <em>Standby</em> (only for <em>MQTT</em>) phase is normalized and calculated for 20 seconds and 10 seconds, respectively. During the <em>MQTT</em> <em>Idle</em> phase measurements, the device disconnects. This is not taken into account for the evaluation, which is why these energy values are discarded for this figure. Data – energy_measurements_fig5.csv Code – fig5.R <strong>Contact</strong> For questions or issues with this code, please contact Viktoria Vomhoff ([e-mail]) or any of the authors of the related publication.