main.tex

   1 \documentclass[a4paper,11pt]{article}
   2 \usepackage[utf8]{inputenc}
   3 \usepackage[T1]{fontenc}
   4 \usepackage{ae}
   5 \usepackage{color}
   6 \usepackage{graphicx}
   7 \usepackage{wrapfig}
   8 \usepackage{hyperref}
   9
  10 \urlstyle{sf}
  11
  12 \newcommand{\pages}[1]{\marginpar{#1 pages}}
  13 \newcommand{\todo}[1][]{\textcolor{red}{TODO #1} \\}
  14 \newcommand{\term}[1]{\emph{#1}}
  15 \newcommand{\code}[1]{\textsf{#1}}
  16
  17 \title{Chatty Things -- Making the Internet of Things Readily Usable for the
  18 Masses with XMPP}
  19 \author{Roland Hieber}
  20 \date{Seminar Communications and Multimedia, TU~Braunschweig \\[1em] \today}
  21
  22 \begin{document}
  23 \maketitle
  24
  25 %% Introduction
  26 \section{Introduction}
  27 \todo
  28 \pages{0-1}
  29 short overview, not too long: what do we want, what are we
  30 going to do
  31
  32 basically: how do we talk to our smart home?
  33 \paragraph{Human-to-Machine Communication:} especiall in the Internet of Things,
  34         Chatty Things need to be accessible for the user and should be easy to talk
  35         to.
  36 \paragraph{Interoperability} integration into already existing
  37 infrastructure.
  38
  39 %% Prerequisites
  40 \section{Prerequisites}
  41 \todo
  42 overview to the techniques used in the paper by Klauk and Kirsche
  43
  44 \cite{klauck-kirsche-chattythings}
  45
  46 \input{sec-address-allocation.tex}
  47 \input{sec-dns-extensions.tex}
  48 \input{sec-xmpp.tex}
  49 \input{sec-chatty-things.tex}
  50
  51 \section{Related Approaches}
  52 \todo
  53 \pages{3}
  54 Middleware, Application protocol gateways:
  55 \begin{itemize}
  56         \item Constrained Application Protocol \cite{draft-ietf-core-coap-18}
  57         \begin{itemize}
  58                 \item machine-to-machine
  59                 \item everything-built-in
  60                 \item discovery over multicast, service discovery over /.well-known
  61                         entry-point
  62                 \item maps to HTTP => stateless => relies on application gateway
  63                 \item low protocol overhead and parsing complexity (binary messages)
  64                 \item only draft status
  65                 \item UDP with Ack and IDs instead of TCP... (limited state machine)
  66                 \item proxies
  67                 \item asynchronous messages
  68         \end{itemize}
  69         \item MQ Telemetry Transport \cite{mqtt}
  70         \begin{itemize}
  71                 \item TCP/IP
  72                 \item small overhead: 2 byte header + variable header length
  73                 \item publish-subscribe with topic names
  74                 \item binary protocol => application-level gateway
  75                 \item discovery?
  76         \end{itemize}
  77         \item Devices Profile for Web Services \cite{zeeb-moritz-ws4d}
  78         \begin{itemize}
  79                 \item TCP/IP -> HTTP -> SOAP -> Web Services. Overhead!
  80                 \item but very extendable and composable
  81                 \item discovery as a service
  82                 \item focused on multiple platforms, deeply embedded and servers
  83                 \item IPv6 partly experimental
  84                 \item ROM usage of uDPWS: 45 kByte
  85         \end{itemize}
  86
  87 \end{itemize}
  88
  89 \section{Discussion}
  90 \todo
  91 comparison of mentioned approaches
  92
  93 \pages{1-2}
  94
  95 \bibliographystyle{plain}
  96 \bibliography{biblio}
  97
  98 \end{document}
  99 % vim: set ft=tex et ts=2 sw=2 :