summaryrefslogtreecommitdiff
path: root/2019-Mascots.tex
diff options
context:
space:
mode:
authorLoic Guegan <manzerberdes@gmx.com>2019-05-04 10:34:16 +0200
committerLoic Guegan <manzerberdes@gmx.com>2019-05-04 10:34:16 +0200
commitb0f66eab21ca546c794ad0432f990d44ca7fc9a9 (patch)
tree8c9f58a6f66587e0bd6dd6d7e13368a1fc2a9463 /2019-Mascots.tex
parentf6d01996eb72fc71681efd4aacd8d8cb903be753 (diff)
parent94bc6b9bd43f2a88eb100ec9c0838739a10d771b (diff)
add git ignore
Diffstat (limited to '2019-Mascots.tex')
-rw-r--r--2019-Mascots.tex84
1 files changed, 0 insertions, 84 deletions
diff --git a/2019-Mascots.tex b/2019-Mascots.tex
deleted file mode 100644
index 80d8f8b..0000000
--- a/2019-Mascots.tex
+++ /dev/null
@@ -1,84 +0,0 @@
-% Intended LaTeX compiler: pdflatex
-\documentclass[conference]{IEEEtran}
- \usepackage{hyperref}
-\IEEEoverridecommandlockouts
-\author{\IEEEauthorblockN{1\textsuperscript{st} Anne-Cécile Orgerie}
-\IEEEauthorblockA{\textit{Univ Rennes, Inria, CNRS, IRISA, Rennes, France} \\
-Rennes, France \\
-anne-cecile.orgerie@irisa.fr}
-\and
-\IEEEauthorblockN{2\textsuperscript{nd} Loic Guegan}
-\IEEEauthorblockA{\textit{Univ Rennes, Inria, CNRS, IRISA, Rennes, France} \\
-Rennes, France \\
-loic.guegan@irisa.fr}
-}
-\date{\today}
-\title{A Large-Scale Wired Network Energy Model for Flow-Level Simulations}
-\hypersetup{
- pdfauthor={},
- pdftitle={A Large-Scale Wired Network Energy Model for Flow-Level Simulations},
- pdfkeywords={},
- pdfsubject={},
- pdfcreator={Emacs 26.2 (Org mode 9.1.9)},
- pdflang={English}}
-\begin{document}
-
-\maketitle
-\begin{abstract}
-This document is a model and instructions for \LaTeX.
-This and the IEEEtran.cls file define the components of your paper [title, text, heads, etc.]. *CRITICAL: Do Not Use Symbols, Special Characters, Footnotes,
-or Math in Paper Title or Abstract.
-\end{abstract}
-
-\begin{IEEEkeywords}
-component, formatting, style, styling, insert
-\end{IEEEkeywords}
-
-
-\section{Introduction}
-\label{sec:org9428352}
-\section{Related Work}
-\label{sec:orga22ca2a}
-\section{Use-Case}
-\label{sec:org3241664}
-\subsection{Application Characteristic}
-\label{sec:org8ebb00c}
-\subsection{Cloud Infrastructure}
-\label{sec:org17d08e8}
-\section{System Model}
-\label{sec:org2051e46}
-\subsection{IoT Part}
-\label{sec:org9fc7024}
-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.
-
-\subsection{Network Part}
-\label{sec:orgb1e4614}
-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 mostly considered as wired network.
-
-
-\subsection{Cloud Part}
-\label{sec:org4dad506}
-\section{Evaluation}
-\label{sec:org373c2b1}
-\subsection{IoT/Network Consumption}
-\label{sec:org993439d}
-\subsection{Cloud Energy Consumption}
-\label{sec:org7ae8276}
-\subsection{Virtual Machine Size Impact}
-\label{sec:orgde03152}
-\subsection{Application Accuracy}
-\label{sec:org79ddac3}
-Refresh frequency etc\ldots{}
-\subsection{End-To-End Consumption}
-\label{sec:org275997a}
-\section{Discussion}
-\label{sec:org25eaadf}
-\section{Conclusion}
-\label{sec:orgff11457}
-\end{document}