From: Roland Hieber Date: Mon, 23 Dec 2013 20:12:49 +0000 (+0100) Subject: introduction, connecting sections X-Git-Tag: final~2 X-Git-Url: https://git.rohieb.name/skm-ma-ws1314.git/commitdiff_plain/f505ad57144ab8d61bf5ba1eb4a967fbe73cb3b7 introduction, connecting sections --- diff --git a/main.tex b/main.tex index d6257cc..d187088 100644 --- a/main.tex +++ b/main.tex @@ -27,35 +27,16 @@ Masses with XMPP} \begin{document} \maketitle -%% Introduction -\section{Introduction} -\todo{asdf} -\pages{0-1} -short overview, not too long: what do we want, what are we going to do? - -how do we talk to our smart home? - -what are the challenges? (interoperability, H2M interface, self-configuration, -information filtering to prevent information overflow) - -In a distributed context like the Internet of Things, devices need to be ready -to use out of the box. Users often do not want to set up configurations for each -device they use, and when using several of those devices, it is often not -reasonable having to configure every single one. - - -%\paragraph{Human-to-Machine Communication:} especiall in the Internet of Things, - %Chatty Things need to be accessible for the user and should be easy to talk - %to. -%\paragraph{Interoperability} integration into already existing -%infrastructure. +\input{sec-intro.tex} %% Prerequisites -\section{Prerequisites} -\todo -overview to the techniques used in the paper by Klauk and Kirsche +\section{Prerequisites}\label{sec:prereq} -\cite{klauck-kirsche-chattythings} +In order to build a distributed, failure-tolerant network for our Chatty Things, +we will first look at some techniques which can be used to eliminate centralized +infrastructure. Most of these techniques are standardized by the IETF and widely +used in existing networks. Finally, we will look at XMPP as the basic +communication protocol used in Chatty Things. \input{sec-address-allocation.tex} \input{sec-dns-extensions.tex} diff --git a/sec-chatty-things.tex b/sec-chatty-things.tex index 25b1426..13407c0 100644 --- a/sec-chatty-things.tex +++ b/sec-chatty-things.tex @@ -1,4 +1,4 @@ -\section{System Architecture of ``Chatty Things''} +\section{System Architecture of ``Chatty Things''}\label{sec:arch} After the underlying techniques have been explained, we can now have a look at the system architecture which Klauck and diff --git a/sec-discussion.tex b/sec-discussion.tex index 3133b6e..e488f80 100644 --- a/sec-discussion.tex +++ b/sec-discussion.tex @@ -1,4 +1,4 @@ -\section{Discussion} +\section{Discussion}\label{sec:discussion} %\todo \pages{3} @@ -83,9 +83,10 @@ decrease message throughput and increase power consumption on embedded systems. \subsection{Related Approaches} -This section gives a short overview of related protocols for the Internet of -Things and shows their advantages and disadvantages, which are summarized in -Table~\ref{tab:comparison}. +Chatty Things is not the only approach to implement communication in embedded +networks. This section gives a short overview of related protocols for the +Internet of Things and shows their advantages and disadvantages, which are +summarized in Table~\ref{tab:comparison}. \begin{table} \small\centering diff --git a/sec-intro.tex b/sec-intro.tex new file mode 100644 index 0000000..6a385d9 --- /dev/null +++ b/sec-intro.tex @@ -0,0 +1,27 @@ +%% Introduction +\section{Introduction} +\todo{asdf} +\pages{0-1} + +Following the vision of the ``Internet of Things'', the amount of wireless +devices is steadily increasing, which not only improves our standard of living +in an age where information is expected to be available at one's fingertips, but +also poses challenges. New devices need to be integrated into existing network +setups, but when considering sensor nodes with very limited input capabilities, +manual configuration can be a cumbersome process -- such devices must be readily +usable out of the box, and should interoperate with existing infrastructure. +Moreover, users need to communicate with their devices, they need to know which +devices exist and use the information they collect, while too much or +unstructured information leads to information overflow, effectively discouraging +the user from using the network. + +This paper gives an overview of the ``Chatty Things'' approach as presented by +Klauck and Kirsche~\cite{klauck-kirsche-chattythings}, which proposes solutions +for information filtering, auto-configuration of devices and service discovery, +while using standard chat clients for human-to-machine communication. +Section~\ref{sec:prereq} shortly introduces the used techniques, +Section~\ref{sec:arch} describes the proposed system architecture for Chatty +Things, and Section~\ref{sec:discussion} discusses possible future enhancements +and compares Chatty Things to similar approaches. + +% vim: set ft=tex et ts=2 sw=2 :