Version du 19 juin 2016 à 20:40

Summary

This article deals with Energy Consumption of Networked Embedded Systems.

Due to the increase of utilization of connected devices, we need to focus on the energy consumption of these connections. Indeed, the Internet of Things allows us to connect our devices to the traditional Internet but the problem is that the protocols we use to do so were made without taking care of energy-efficiency, so these protocols are sometimes not adapted to the software we use.

The first important thing explained by the authors is that of the energy consumption is caused by the radio transceiver.

Authors also explain that there is an energy measurement methodology and there are different categories of measurement and estimation methods according to the device you are using.

Authors then explain the relation between energy consumption and internet protocols like IP, TCP or MAC and then explain the methodology developed in the article. If you use low-power wireless devices, it is difficult to mesaure the energy consumption, so you can only estimate it. They try to explain step by step the process which is based on the use of two energy estimation techniques, by using this method, we want to quantify the differences between simulation-based and real world software-based methods.

In a first phase, authors describe the test Bed description with a MCU, a low power radio chip compliant with the IEEE 802.15.4 standard. There is also an IPv6/IPv4 border router used to connect IP sensor network to a computer. It uses a Serial Line IP (SLIP) to send and receive IP packets with the computer. Then, we need to measure the energy footprint of the Contiki's HTTP embedded web server, we initialize an HTTP request asking for a playload ranging from 1 to 1040 bytes from a HTTP web server.

Then we use a Test Bench to run multiple experiments using two Contiki network configurations. To quantify the motes energy consumption, we must run our tests using two different environments : in the first we deploy the test bed in a real environment, then we use the simulator included in the Contiki network which gives us an ideal experiment environment, avoiding interferences. To characterize and compute the energy consumption for every node on the route when processing a HTTP request, we use the Contiki's built-in energy profiler Powertrace. Every node triggers two Powertrace timestamps, one at the beginning of a request by detecting the TCP opening connection flag and in the second environment, at the end by detecting the TCP closing connection flag.

Main contribution

Applications