Browse Source

add layout info to intro

master
Sven Reissmann 7 years ago
parent
commit
967b0902dc
  1. 6
      1-introduction.tex
  2. 2
      3-environment.tex
  3. 2
      4-requirements.tex
  4. 2
      5-concept.tex
  5. 2
      6-implementation.tex

6
1-introduction.tex

@ -23,3 +23,9 @@ It also decreases the maintenance cost drastically, because updates can be trigg
\textit{OTA} updates enable administrators to apply automation methods on the update process allowing to roll out new releases and fixes in a controlled fashion.
As an example, updates can be done on test-devices first, followed by security-critical deployments and subordinate ones can be delayed to times when the device is not utilized.
Further, a feedback channel which provides information about the update status of a devices allows administrators to apply monitoring techniques ensuring all updates are installed and devices are in the desired state.
The remaining part of this paper is laid out as follows.
Section \ref{related} discusses related work.
Next, in Section \ref{env} we present the environment, our research is based on, while Section \ref{req} defines the requirements for the implementation of an OTA update mechanism in this environment.
A concept for the implementation is presented in Section \ref{concept} and a reference implementation can be found in Section \ref{implementation}.
Finally, a conclusion and future work can be found in Section \ref{conclusion}.

2
3-environment.tex

@ -1,4 +1,4 @@
\section{Environment}
\section{Environment}\label{env}
The research presented in this paper was mainly driven by \textit{Magrathea Laboratories e.V.} \cite{maglab}, the local hackerspace in Fulda, in cooperation with researchers at the department for computer science at Fulda University.
Requirements were clearly defined by Magrathea Laboratories' demands to provide local and remote control over various sensors and actors in the foundations rooms to visitors and members.

2
4-requirements.tex

@ -1,4 +1,4 @@
\section{Requirements}
\section{Requirements}\label{req}
\makeatletter
\renewcommand{\@IEEEsectpunct}{\,}% Modified from {:\ \,}
\makeatother

2
5-concept.tex

@ -1,4 +1,4 @@
\section{Concept for implementing OTA updates}
\section{Concept for implementing OTA updates}\label{concept}
To implement \textit{OTA} updates under the given requirements, we first define a topology that integrates our build infrastructure, firmware repository, and controller with the IoT WiFi network, which the devices are connected to.
For our reference implementation, we particularly chose lightweight and common software projects to allow for easy exchangeability of the individual components.
The base topology, as well as the specific components used is shown in Figure \ref{fig:topology}.

2
6-implementation.tex

@ -1,4 +1,4 @@
\section{Implementation}
\section{Implementation}\label{implementation}
Implementing \textit{OTA} updates under the given requirements involves multiple components, which interact closely.
The continuous integration system is in charge of building the firmware from source, calculating cryptographic signatures, and publishing the built binary images.

Loading…
Cancel
Save