25 KiB
Estimating the end-to-end energy consumption of IoT devices along with their impact on Cloud and telecommunication infrastructures
Introduction [2 col]
Related Work [1 col]
Use-Case [1 col]
Application Characteristic
The IoT part is composed of an Access Point (AP), connected to several sensors using WIFI. In the system, the IoT part is considered as the part where the system data are created. In fact, the data life cycle start when the sensors records their respective local temperature at a frequency $f$ and the local timestamp. Then, these data are transmitted through the network along with an arbitrary sensor id of 128 bits. Finally, the AP is in charge to transmit the data to the cloud using the network part.
The network part is considered as the medium that link the IoT part to the cloud. It is composed of several network switches and router and it is considered to be a wired network.
Cloud Infrastructure
System Model [2 col]
The system model is divided in two parts. First, the IoT and the Network part are models through simulations. Then, the Cloud part is model using real servers connected to watt-meters. In this way, it is possible to evaluate the end-to-end energy consumption of the system.
IoT Part
In the first place, the IoT part is composed of several sensors connected to an AP which forms a cell. It is model using the ns-3 network simulator. Thus, we setup between 5 and 15 sensors connected to the AP using WIFI 5GHz 802.11n. The node are placed randomly in a rectangle of 400m2 around the AP which correspond to a typical real use case. All the nodes of the cell are setup with the default WIFI energy model provided by ns-3. The different energy values used by the energy model are provided on Table \ref{tab:wifi-energy}. These energy were extracted from previous work\cite{halperin_demystifying_nodate,li_end–end_2018} on 802.11n. Note that we suppose that the energy source of the cell nodes are unlimited and thus every nodes can communicate until the end of all the simulations.
As a scenario, sensors send to the AP packets of 192 bits that include: \textbf{1)} A 128 bits sensors id \textbf{2)} A 32 bits integer representing the temperature \textbf{3)} An integer timestamp representing the temperature sensing time. The data are transmitted immediately at each sensing interval $I$ varied from 1s to 60s. Finally, the AP is in charge of relaying data to the cloud using the network part.
Network Part
The network part represents the network starting from the AP to the Cloud excluding the server. It is also model into ns-3. We consider the server to be 9 hops aways from the AP with a typical round-trip latency of 100ms from the AP to the server. Each node from the AP to the Cloud is assume to be network switches with static and dynamic network energy consumption. ECOFEN \cite{orgerie_ecofen:_2011} is used to model the energy consumption of the network part. ECOFEN is a ns-3 network energy module for ns-3 dedicated to wired network energy estimation. It is based on an energy-per-bit model including static consumption by assuming a linear relation between the amount of data sent to the network interface and the power consumption. The different energy values used to instanciate the ECOFEN energy model for the network part are shown in Table \ref{tab:net-energy} and come from previous work \cite{cornea_studying_2014-1}.
Cloud Part
Finally, to measure the energy consumption of the server, we used real server from the large-scale test-beds Grid5000 (G5K). In fact, G5K has a cluster called Nova composed of several nodes which are connected to watt-meters. In this way, we can benefit from real energy measurements. The server used in the experiment is composed of Intel Xeon E5-2620 processor with 64 GB of RAM and 600GB of disk space on a Linux based distribution. This server is configured to use KVM as virtualization mechanism. We deploy a classical Linux x86_64 disctribution on the Virtual Machines (VM) along with a MySQL database. We different amount of allocated memory for the VM namely 1024MB/2048MB/4096MB to highlight its effects on the server energy consumption.
The sensors requests are simulated using another server. This server is in charge to send hundred of requests to the VM in order to fill the database. Consequently, it is easy to vary the different requests characteristics namely: \textbf{1)} The number request, to virtually add/remove sensors \textbf{2)} The requests frequency.
Evaluation [3 col]
IoT/Network Consumption
Cloud Energy Consumption
Virtual Machine Size Impact
Application Accuracy
Refresh frequency etc…
End-To-End Consumption
Discussion [1 col]
Conclusion [1 col]
References [1 col]
\bibliographystyle{IEEEtran} \bibliography{references}