paper-lowrate-iot/2019-Mascots.org

#+TITLE: Estimating the end-to-end energy consumption of IoT devices along with their impact on Cloud and telecommunication infrastructures

#+EXPORT_EXCLUDE_TAGS: noexport
#+STARTUP: hideblocks
#+OPTIONS: H:5 author:nil email:nil creator:nil timestamp:nil skip:nil toc:nil ^:nil
#+LATEX_CLASS: IEEEtran
#+LATEX_HEADER: \usepackage{hyperref}
#+LATEX_HEADER: \IEEEoverridecommandlockouts 
#+LATEX_HEADER: \author{\IEEEauthorblockN{1\textsuperscript{st} Anne-Cécile Orgerie}
#+LATEX_HEADER: \IEEEauthorblockA{\textit{Univ Rennes, Inria, CNRS, IRISA, Rennes, France} \\
#+LATEX_HEADER: Rennes, France \\
#+LATEX_HEADER: anne-cecile.orgerie@irisa.fr}
#+LATEX_HEADER: \and
#+LATEX_HEADER: \IEEEauthorblockN{2\textsuperscript{nd} Loic Guegan}
#+LATEX_HEADER: \IEEEauthorblockA{\textit{Univ Rennes, Inria, CNRS, IRISA, Rennes, France} \\
#+LATEX_HEADER: Rennes, France \\
#+LATEX_HEADER: loic.guegan@irisa.fr}
#+LATEX_HEADER: }



#+BEGIN_EXPORT latex
\begin{abstract}
Information and Communication Technology takes a growing part in the worldwide energy consumption. One of the root causes of this increase lies in the multiplication of connected devices. Each object of the Internet-of-Things often does not consume much energy by itself. Yet, their number and the infrastructures they require to properly work have leverage. In this paper, we combine simulations and real measurements to study the energy impact of IoT devices. In particular, we analyze the energy consumption of Cloud and telecommunication infrastructures induced by the utilization of connected devices, and we propose an end-to-end energy consumption model for these devices. 
\end{abstract}

\begin{IEEEkeywords}
component, formatting, style, styling, insert
\end{IEEEkeywords}
#+END_EXPORT


* Introduction
* Related Work
* Use-Case
** 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 respectives 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
  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 wattmeters. 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 20 sensors
   connected to the AP using WIFI 5GHz 802.11n. 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 come
   from the litterature and are provided on Table \ref{tab:wifi-energy}. Note that we suppose that the
   energy source of the cell nodes are unlimited and thus every nodes can communicate for all the
   simulation duration.
   
   #+BEGIN_EXPORT latex
   \begin{table}[]
     \centering
     \caption{Wifi Energy Settings}
     \label{tab:wifi-energy}
     \begin{tabular}{|l|l|l|}
       \hline
       & Value  & Reference(s) \\ \hline
       Supply Voltage & 3.3V   & TODO         \\ \hline
       Tx             & 0.38A  & TODO         \\ \hline
       Rx             & 0.313A & TODO         \\ \hline
       Idle           & 0.273A & TODO         \\ \hline
     \end{tabular}
   \end{table}  

   #+END_EXPORT


** Network Part

   
** Cloud Part
* Evaluation
** IoT/Network Consumption
** Cloud Energy Consumption
** Virtual Machine Size Impact
** Application Accuracy
   Refresh frequency etc...
** End-To-End Consumption
* Discussion
* Conclusion



* Emacs settings :noexport:
  # Local Variables:
  # eval:    (unless (boundp 'org-latex-classes) (setq org-latex-classes nil))
  # eval:    (add-to-list 'org-latex-classes
  #                       '("IEEEtran" "\\documentclass[conference]{IEEEtran}\n \[NO-DEFAULT-PACKAGES]\n \[EXTRA]\n"  ("\\section{%s}" . "\\section*{%s}") ("\\subsection{%s}" . "\\subsection*{%s}")                       ("\\subsubsection{%s}" . "\\subsubsection*{%s}")                       ("\\paragraph{%s}" . "\\paragraph*{%s}")                       ("\\subparagraph{%s}" . "\\subparagraph*{%s}")))
  # End: