mirror of
https://gitlab.com/manzerbredes/paper-lowrate-iot.git
synced 2025-04-19 04:09:43 +00:00
ajout app charac
This commit is contained in:
parent
bc41352093
commit
b2378fbbd9
1 changed files with 12 additions and 0 deletions
|
@ -260,6 +260,8 @@ application. While the derived model is more generic, we focus on a
|
||||||
given application to obtain a precise use-case with accurate power
|
given application to obtain a precise use-case with accurate power
|
||||||
consumption measurements.
|
consumption measurements.
|
||||||
|
|
||||||
|
\subsection{IoT device side}
|
||||||
|
|
||||||
The Google Nest Thermostat relies on five sensors: temperature,
|
The Google Nest Thermostat relies on five sensors: temperature,
|
||||||
humidity, near-field activity, far-field activity and ambient
|
humidity, near-field activity, far-field activity and ambient
|
||||||
light~\cite{Nest}. Periodical measurements, sent through wireless
|
light~\cite{Nest}. Periodical measurements, sent through wireless
|
||||||
|
@ -284,6 +286,8 @@ home. We consider low-bandwidth applications where devices produces
|
||||||
several network packets during each sensing period. The transmitting
|
several network packets during each sensing period. The transmitting
|
||||||
frequency can vary from one to several packet sent per minute~\cite{Cisco2019}.
|
frequency can vary from one to several packet sent per minute~\cite{Cisco2019}.
|
||||||
|
|
||||||
|
|
||||||
|
\subsection{Cloud server side}
|
||||||
We consider that the link between the AP and the Cloud is composed of
|
We consider that the link between the AP and the Cloud is composed of
|
||||||
several network switches and routers using Ethernet as shown in
|
several network switches and routers using Ethernet as shown in
|
||||||
Figure~\ref{fig:parts}. The number of routers on the path depends on the
|
Figure~\ref{fig:parts}. The number of routers on the path depends on the
|
||||||
|
@ -303,6 +307,14 @@ same time.
|
||||||
\label{fig:parts}
|
\label{fig:parts}
|
||||||
\end{figure}
|
\end{figure}
|
||||||
|
|
||||||
|
The Cloud part of the application gathers the data sent by the IoT
|
||||||
|
devices. These data are treated either on the fly (e.g. threshold
|
||||||
|
detection) or periodically, and action commands are sent back to the
|
||||||
|
device if required. For instance, if the user has set a targeted
|
||||||
|
temperature, the connected thermostat sends the measured
|
||||||
|
temperature regularly, and once the target is reached, the Cloud server detects
|
||||||
|
it, and sends back to the IoT device the command to pause the heater.
|
||||||
|
|
||||||
In the following, we describe the experimental setup, the results and
|
In the following, we describe the experimental setup, the results and
|
||||||
the derived end-to-end model. For all these steps, we decompose the overall
|
the derived end-to-end model. For all these steps, we decompose the overall
|
||||||
IoT architecture into three parts: the IoT device part, the networking
|
IoT architecture into three parts: the IoT device part, the networking
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue