## 7 Network Performance Analysis: NB-IoT vs. LoRaWAN
### Throughput
#### 7.2.1 Battery Life  
The energy consumption of IoT devices is use case-dependent and is mainly influenced by several protocol-specific factors such as hardware synchronisation, the OFDM modulation scheme, network coverage levels, high message repetitions, software, and application capabilities [24]. The energy consumption target of NB-IoT devices according to the 3 GPP release 13 standard is 10 years when operated between 20 dBm and 23 dBm. This requirement includes devices that are battery powered, non-rechargeable and used in the most difficult terrains. The power consumption analysis is one way of computing the battery life of IoT modules. The comparison of power consumption analysis of Fipy module in NB-IoT and LoRa networks is based on the USB power meter. It is important to note that the timing resolution of the power meter is a critical requirement and may affect the following results presented in Table 5. As Fipy is a release 13 standard, its radio components remain turned off once registered to the NB-IoT network except when there is scheduled data transmission. At this point, the UE is in an idle state, and the channel is monitored for any handover procedure using paging signals. The eDRX included in the higher 3 GPP standardisation is to allow UEs to stay in a sleep state for up to T413 (413.3 days) to save more energy. For every packet's transmission, bursts of power consumption are observed in the CPU and NB-IoT power transmission measurements in Figure 14.  
Since the Fipy was not battery powered and to keep the tests' duration to a reasonable period, the evaluation of battery life was limited to the RRC connection procedure and data transmission. With an average of 3 mAh needed to reconnect the NB-IoT module to the network, an uplink message consumed an average of 1.8 mAh for 44 bytes of data at 3.3 vs. the regulated output voltage. For instance, this deviates by a high margin from the 100 mAh measured for uplink messages in LoRaWAN. As concluded in [30], based on ideal conditions, the 10-year lifetime in NB-IoT can be met if 24 h data transmission intervals are implemented and lowering the time scale to 2 h becomes unrealistic at 146 dB MCL. The mode of operation does not impact the uplink transmission, a major determinant of  
Figure 14: NB-IoT CPU receive and transmission channels’ power consumption. \begin{table}
\begin{tabular}{c c c} \hline \hline
**Features** & **NB-IoT** & **LoRaWAN** \\ \hline Joining network & 3 mAh & 1 mAh \\ Uplink message (44 bytes) & 1.8 mAh & 100 mAh \\ UE class & Cat NBI & A \\ Data rate (20 bytes) & 0.6–4 bps & \\ Frequency & 28 MHz & EU868 MHz \\ \hline \hline \end{tabular}
\end{table} 
Table 5: NB-IoT vs. LoRaWAN average power consumption, latency, and throughput. power consumption reduction. In release 14, where a power class of 14 dBm enables the use of smaller cell batteries in new NB-IoT deployment, more efficient power consumption is expected. This improvement over release 13 helps reduce the power amplifier (PA) drain current which negatively affects the UL coverage and the maximum coupling loss (MCL) to 155 dB. An example is that of the Fipy NB-IoT module, a release 13 device that supports 20 and 23 dBm power classes. As shown in Figure 14, without transmissions, the \(-20.4\) dB and \(-2.72\) dB full scale is the maximum power, \(-35.5\) dB and \(-17.7\) dB root mean square (RMS) full-scale value, and 8.40% and 2.72% CPU power for the transmit and receive channels, respectively. During transmissions, an average of \(-5.68\) dB and \(-2.99\) dB full scale was the maximum power, \(-31.4\) dB and \(-17.1\) dB RMS was the full-scale value, 6.32% and 1.85% was the CPU power for the transmit and receive channels, respectively. This shows that the NB-IoT consumed more power than LoRaWAN due to its complicated communication procedure, irrespective of the PSM and eDRX power saving modes. A greater part of the energy was drawn during the synchronisation, joining, and connected state of the UE.