summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--notFinishedCode/Report/.test.tex.kate-swpbin841 -> 1827 bytes
-rw-r--r--notFinishedCode/Report/test.aux39
-rw-r--r--notFinishedCode/Report/test.log62
-rw-r--r--notFinishedCode/Report/test.pdfbin598443 -> 603598 bytes
-rw-r--r--notFinishedCode/Report/test.tex40
-rw-r--r--notFinishedCode/Report/test.tex.backup15
-rw-r--r--notFinishedCode/Report/test.tex~40
-rw-r--r--notFinishedCode/Report/test.toc25
8 files changed, 144 insertions, 77 deletions
diff --git a/notFinishedCode/Report/.test.tex.kate-swp b/notFinishedCode/Report/.test.tex.kate-swp
index bc13d34..67f696f 100644
--- a/notFinishedCode/Report/.test.tex.kate-swp
+++ b/notFinishedCode/Report/.test.tex.kate-swp
Binary files differ
diff --git a/notFinishedCode/Report/test.aux b/notFinishedCode/Report/test.aux
index 0d9c017..e4a2b13 100644
--- a/notFinishedCode/Report/test.aux
+++ b/notFinishedCode/Report/test.aux
@@ -4,32 +4,39 @@
\@writefile{lof}{\select@language{english}}
\@writefile{lot}{\select@language{english}}
\@writefile{toc}{\contentsline {section}{\numberline {1}Introduction and Motivation}{3}}
-\@writefile{toc}{\contentsline {section}{\numberline {2}Requests}{4}}
+\@writefile{toc}{\contentsline {section}{\numberline {2}Requirements}{4}}
\@writefile{toc}{\contentsline {section}{\numberline {3}Database design}{5}}
\@writefile{toc}{\contentsline {section}{\numberline {4}Software design}{6}}
-\@writefile{toc}{\contentsline {subsection}{\numberline {4.1}Usage}{6}}
+\@writefile{toc}{\contentsline {subsection}{\numberline {4.1}Database access}{6}}
+\@writefile{toc}{\contentsline {subsection}{\numberline {4.2}Controlling the cell phones}{6}}
+\@writefile{toc}{\contentsline {subsection}{\numberline {4.3}}{6}}
+\citation{beagleDataSheet}
\@writefile{toc}{\contentsline {section}{\numberline {5}Hardware design}{7}}
+\@writefile{toc}{\contentsline {subsection}{\numberline {5.1}BeagleBoard}{7}}
\@writefile{lof}{\contentsline {figure}{\numberline {1}{\ignorespaces }}{7}}
-\@writefile{toc}{\contentsline {section}{\numberline {6}Communication protocol}{8}}
-\@writefile{lof}{\contentsline {figure}{\numberline {2}{\ignorespaces }}{8}}
-\@writefile{lof}{\contentsline {figure}{\numberline {3}{\ignorespaces }}{8}}
-\@writefile{lof}{\contentsline {figure}{\numberline {4}{\ignorespaces }}{9}}
+\@writefile{toc}{\contentsline {subsection}{\numberline {5.2}Cell phones}{8}}
+\@writefile{toc}{\contentsline {subsection}{\numberline {5.3}Cables for the cell phones}{8}}
+\@writefile{toc}{\contentsline {section}{\numberline {6}Communication protocol}{9}}
+\@writefile{lof}{\contentsline {figure}{\numberline {2}{\ignorespaces }}{9}}
+\@writefile{lof}{\contentsline {figure}{\numberline {3}{\ignorespaces }}{9}}
+\@writefile{lof}{\contentsline {figure}{\numberline {4}{\ignorespaces }}{10}}
\citation{sshTunnel}
-\@writefile{toc}{\contentsline {section}{\numberline {7}Security and safety of the system}{10}}
-\@writefile{toc}{\contentsline {subsection}{\numberline {7.1}Encryption of the communication channels}{10}}
-\@writefile{lof}{\contentsline {figure}{\numberline {5}{\ignorespaces }}{10}}
+\@writefile{toc}{\contentsline {section}{\numberline {7}Security and safety of the system}{11}}
+\@writefile{toc}{\contentsline {subsection}{\numberline {7.1}Encryption of the communication channels}{11}}
+\@writefile{lof}{\contentsline {figure}{\numberline {5}{\ignorespaces }}{11}}
\citation{https}
-\@writefile{toc}{\contentsline {subsection}{\numberline {7.2}Security on the web site}{11}}
+\@writefile{toc}{\contentsline {subsection}{\numberline {7.2}Security on the web site}{12}}
\citation{https}
\citation{https}
-\@writefile{toc}{\contentsline {section}{\numberline {8}Web page}{15}}
-\@writefile{toc}{\contentsline {subsection}{\numberline {8.1}Communication between the web page and the test software}{15}}
-\@writefile{toc}{\contentsline {subsection}{\numberline {8.2}Results on the web page}{15}}
+\@writefile{toc}{\contentsline {section}{\numberline {8}Web page}{16}}
+\@writefile{toc}{\contentsline {subsection}{\numberline {8.1}Communication between the web page and the test software}{16}}
+\@writefile{toc}{\contentsline {subsection}{\numberline {8.2}Results on the web page}{16}}
\citation{pChart}
-\@writefile{lof}{\contentsline {figure}{\numberline {6}{\ignorespaces }}{16}}
-\@writefile{toc}{\contentsline {section}{\numberline {9}Conclusion}{17}}
+\@writefile{lof}{\contentsline {figure}{\numberline {6}{\ignorespaces }}{17}}
+\@writefile{toc}{\contentsline {section}{\numberline {9}Conclusion}{18}}
\bibcite{site1}{1}
\bibcite{sshTunnel}{2}
\bibcite{https}{3}
\bibcite{pChart}{4}
-\newlabel{LastPage}{{}{18}}
+\bibcite{beagleDataSheet}{5}
+\newlabel{LastPage}{{}{19}}
diff --git a/notFinishedCode/Report/test.log b/notFinishedCode/Report/test.log
index 214d813..46dc006 100644
--- a/notFinishedCode/Report/test.log
+++ b/notFinishedCode/Report/test.log
@@ -1,4 +1,4 @@
-This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/Debian) (format=pdflatex 2011.9.27) 9 OCT 2011 17:55
+This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/Debian) (format=pdflatex 2011.9.27) 9 OCT 2011 18:49
entering extended mode
%&-line parsing enabled.
**test.tex
@@ -281,19 +281,19 @@ LaTeX Font Info: External font `cmex10' loaded for size
(Font) <10.95> on input line 6.
Class scrartcl Info: You've told me to use the font selection of the element
(scrartcl) `sectioning' that is an alias of element `disposition'
-(scrartcl) on input line 7.
+(scrartcl) on input line 9.
Class scrartcl Info: You've told me to use the font selection of the element
(scrartcl) `sectioning' that is an alias of element `disposition'
-(scrartcl) on input line 8.
+(scrartcl) on input line 13.
Class scrartcl Info: You've told me to use the font selection of the element
(scrartcl) `sectioning' that is an alias of element `disposition'
-(scrartcl) on input line 9.
+(scrartcl) on input line 14.
Class scrartcl Info: You've told me to use the font selection of the element
(scrartcl) `sectioning' that is an alias of element `disposition'
-(scrartcl) on input line 12.
+(scrartcl) on input line 17.
Class scrartcl Info: You've told me to use the font selection of the element
(scrartcl) `sectioning' that is an alias of element `disposition'
-(scrartcl) on input line 15.
+(scrartcl) on input line 20.
)
\tf@toc=\write4
\openout4 = `test.toc'.
@@ -301,58 +301,58 @@ Class scrartcl Info: You've told me to use the font selection of the element
[2] [3]
[4] [5] [6] <bb.jpg, id=28, 521.95pt x 516.93124pt>
File: bb.jpg Graphic file (type jpg)
- <use bb.jpg> [7 <./bb.jpg>] <protocolCommunicationHandler.png, id=33, 2486.938
-23pt x 792.13588pt>
+ <use bb.jpg> [7 <./bb.jpg>] [8] <protocolCommunicationHandler.png, id=36, 2486
+.93823pt x 792.13588pt>
File: protocolCommunicationHandler.png Graphic file (type png)
<use protocolCommunicationHandler.png>
-<protocolCommunicationcControllerReceiver.png, id=34, 1808.16705pt x 766.62883p
+<protocolCommunicationcControllerReceiver.png, id=37, 1808.16705pt x 766.62883p
t>
File: protocolCommunicationcControllerReceiver.png Graphic file (type png)
<use protocolCommunicationcControllerReceiver.png>
-<protocolCommunicationcControllerCaller.png, id=35, 1808.16705pt x 766.62883pt>
+<protocolCommunicationcControllerCaller.png, id=38, 1808.16705pt x 766.62883pt>
File: protocolCommunicationcControllerCaller.png Graphic file (type png)
-<use protocolCommunicationcControllerCaller.png> [8 <./protocolCommunicationHan
+<use protocolCommunicationcControllerCaller.png> [9 <./protocolCommunicationHan
dler.png (PNG copy)> <./protocolCommunicationcControllerReceiver.png (PNG copy)
->] [9 <./protocolCommunicationcControllerCaller.png (PNG copy)>]
-<sshTunnel.png, id=42, 696.6025pt x 152.57pt>
+>] [10 <./protocolCommunicationcControllerCaller.png (PNG copy)>]
+<sshTunnel.png, id=45, 696.6025pt x 152.57pt>
File: sshTunnel.png Graphic file (type png)
- <use sshTunnel.png> [10
+ <use sshTunnel.png> [11
<./sshTunnel.png (PNG copy)>]
LaTeX Font Info: External font `cmex10' loaded for size
-(Font) <9> on input line 175.
+(Font) <9> on input line 194.
LaTeX Font Info: External font `cmex10' loaded for size
-(Font) <5> on input line 175.
- [11] [12]
-LaTeX Font Info: Try loading font information for OMS+cmr on input line 286.
+(Font) <5> on input line 194.
+ [12] [13]
+LaTeX Font Info: Try loading font information for OMS+cmr on input line 305.
(/usr/share/texmf-texlive/tex/latex/base/omscmr.fd
File: omscmr.fd 1999/05/25 v2.5h Standard LaTeX font definitions
)
LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <9> not available
-(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 286.
- [13] [14] [15]
+(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 305.
+ [14] [15] [16]
LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <12> not available
-(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 358.
+(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 377.
-<resultsImage.png, id=67, 702.625pt x 431.6125pt>
+<resultsImage.png, id=70, 702.625pt x 431.6125pt>
File: resultsImage.png Graphic file (type png)
<use resultsImage.png>
-[16 <./resultsImage.png (PNG copy)>] [17]
-LaTeX Font Info: Try loading font information for T1+cmtt on input line 383.
+[17 <./resultsImage.png (PNG copy)>] [18]
+LaTeX Font Info: Try loading font information for T1+cmtt on input line 402.
(/usr/share/texmf-texlive/tex/latex/base/t1cmtt.fd
File: t1cmtt.fd 1999/05/25 v2.5h Standard LaTeX font definitions
)
-AED: lastpage setting LastPage [18] (./test.aux) )
+AED: lastpage setting LastPage [19] (./test.aux) )
Here is how much of TeX's memory you used:
- 4884 strings out of 495061
- 67557 string characters out of 1182621
- 255255 words of memory out of 3000000
- 8001 multiletter control sequences out of 15000+50000
+ 4885 strings out of 495061
+ 67574 string characters out of 1182621
+ 255259 words of memory out of 3000000
+ 8002 multiletter control sequences out of 15000+50000
18484 words of font info for 43 fonts, out of 3000000 for 9000
28 hyphenation exceptions out of 8191
36i,10n,45p,751b,1285s stack positions out of 5000i,500n,10000p,200000b,50000s
@@ -369,9 +369,9 @@ ur/jknappen/ec/ecsx1440.600pk> </home/refik/.texmf-var/fonts/pk/ljfour/jknappen
0.600pk> </home/refik/.texmf-var/fonts/pk/ljfour/jknappen/ec/ecrm1728.600pk></u
sr/share/texmf-texlive/fonts/type1/public/amsfonts/cm/cmsy10.pfb></usr/share/te
xmf-texlive/fonts/type1/public/amsfonts/cm/cmsy9.pfb>
-Output written on test.pdf (18 pages, 598443 bytes).
+Output written on test.pdf (19 pages, 603598 bytes).
PDF statistics:
- 566 PDF objects out of 1000 (max. 8388607)
+ 578 PDF objects out of 1000 (max. 8388607)
0 named destinations out of 1000 (max. 500000)
36 words of extra memory for PDF output out of 10000 (max. 10000000)
diff --git a/notFinishedCode/Report/test.pdf b/notFinishedCode/Report/test.pdf
index 0d5459c..5056692 100644
--- a/notFinishedCode/Report/test.pdf
+++ b/notFinishedCode/Report/test.pdf
Binary files differ
diff --git a/notFinishedCode/Report/test.tex b/notFinishedCode/Report/test.tex
index d0e70d9..af12352 100644
--- a/notFinishedCode/Report/test.tex
+++ b/notFinishedCode/Report/test.tex
@@ -102,27 +102,46 @@ Prof. Dr. Gerhard Schneider\\ \vspace{1\baselineskip} Supervisors: \\ Konrad Mei
Before we had started working on our project, we had to analyze the overall network to come up with test cases that contain the highest information content. The next step in our procedure was to implement our ideas into a working piece of software.
Gradually we implemented a bit-by-bit of the final software. Every single step was accompanied by testing and validation procedures. At the end we connected all the ``black-boxes'' into one big piece of software. We have fulfilled our requests and goals and made a fully working and operable test software. Despite developing a working software, all the way along we thought about the simplicity of the usage of the software. In the following chapters we will describe in more detail our approach and how each subsystem works.
\newpage
-\section{Requests} % chapter 2
+\section{Requirements} % chapter 2
\newpage
\section{Database design}
+How we designed our database and why, explain in this section!
\newpage
\section{Software design} % section 2.1
-\subsection{Usage} % subsection 2.1.1
+\subsection{Database access} % subsection 2.1.1
+\subsection{Controlling the cell phones}
+Our first version of the developed program code for controlling the cell phones used predefined timed values
+to send commands instead of using a state controlled approach to confirm that every command was successfuly received and executed by the cell phone.
+It meant we had to make an enormous number of assumptions. In comparison to our second approach, to build a state controlled cell phone control class,
+our first approach was inferior and slower. The state controlled method connected two cell phones, on the same base station, up to 15 times faster than timed approach.
+\subsection{}
\newpage
\section{Hardware design}
In our team project we had the option to choose all the required hardware ourself beside the two BeagleBoards, which we were luckily supplied by Konrad and Dennis.
-Since one of the project goals was to reduce the costs as much as it was possible, we had tried to use some of the leftovers in our lab.
-
+Since one of the project goals was to reduce the costs as much as it was possible, we had tried to use some of the leftovers found in our lab.
+
+\subsection{BeagleBoard}
+``The BeagleBoard is an OMAP3530 platform designed specifically to address the Open
+Source Community. It has been equipped with a minimum set of features to allow the
+user to experience the power of the OMAP3530 and is not intended as a full development
+platform as many of the features and interfaces supplied by the OMAP3530 are not
+accessible from the BeagleBoard'' \cite{beagleDataSheet}.
\begin{figure}[ht!]
\centering
\includegraphics[width=130mm]{bb.jpg}
\caption[]{BeagleBoard, a linux-on-chip board where our controller software runs the GSM device }
\end{figure}
-\par Our first attempt was to control a Nokia cell phone 3310 with the supplied USB connection cable.
-Protocols used by old versions of Nokia phones as the 3310 use the F-Bus protocol. It was not easy to work with.
-After performing various experiments we found out that it was not possible to
-send commands for controlling the calls. In the meantime we found two Siemens phones, one M45 and S55.
-The first one, Siemens M45, had a cable supplied with it and it was not difficult to control it with AT commands.
+
+\subsection{Cell phones}
+Our first attempt was to control a Nokia cell phone 3310 with the supplied USB connection cable.
+The protocols used by old versions of Nokia cell phones, as the 3310, use the F-Bus protocol. It was not easy to work with.
+After performing various experiments we succeeded to send and to read SMS messages. Later on we found out that it was not possible to
+send commands for receiving and making the calls. In the meantime we found two Siemens phones, one M45 and S55.
+The first one, Siemens M45, had a cable supplied with it and it was not difficult to control it with the standard set of AT modem commands.
+At the start we did not have a cable supplied for the Siemens S55 phone. We controlled it over the Bluetooth port.
+
+\subsection{Cables for the cell phones}
+
\newpage
\section{Communication protocol}
@@ -391,6 +410,9 @@ Hypothesis}, preprint (2003), available at
\bibitem{pChart} \emph{pChart}, accessed on 15.08.2011, available at
\url{http://http://www.pchart.net/}.
+\bibitem{beagleDataSheet} \emph{BeagleBoard System Reference Manual}, accessed on 20.06.2011, available at
+\url{http://beagleboard.org/static/BBSRM_latest.pdf}.
+
%bibliography end
\end{thebibliography}
diff --git a/notFinishedCode/Report/test.tex.backup b/notFinishedCode/Report/test.tex.backup
index 9cc4e7c..2bf7a72 100644
--- a/notFinishedCode/Report/test.tex.backup
+++ b/notFinishedCode/Report/test.tex.backup
@@ -102,12 +102,19 @@ Prof. Dr. Gerhard Schneider\\ \vspace{1\baselineskip} Supervisors: \\ Konrad Mei
Before we had started working on our project, we had to analyze the overall network to come up with test cases that contain the highest information content. The next step in our procedure was to implement our ideas into a working piece of software.
Gradually we implemented a bit-by-bit of the final software. Every single step was accompanied by testing and validation procedures. At the end we connected all the ``black-boxes'' into one big piece of software. We have fulfilled our requests and goals and made a fully working and operable test software. Despite developing a working software, all the way along we thought about the simplicity of the usage of the software. In the following chapters we will describe in more detail our approach and how each subsystem works.
\newpage
-\section{Requests} % chapter 2
+\section{Requirements} % chapter 2
\newpage
\section{Database design}
+How we designed our database and why, explain in this section!
\newpage
\section{Software design} % section 2.1
-\subsection{Usage} % subsection 2.1.1
+\subsection{Database access} % subsection 2.1.1
+\subsection{Controlling the cell phones}
+Our first version of the developed program code for controlling the cell phones used predefined timed values
+to send commands instead of using a state controlled approach to confirm that every command was successfuly received and executed by the cell phone.
+It meant we had to make an enormous number of assumptions. In comparison to our second approach, to build a state controlled cell phone control class,
+our first approach was inferior and slower. The state controlled method connected two cell phones, on the same base station, up to 15 times faster than timed approach.
+\subsection{}
\newpage
\section{Hardware design}
In our team project we had the option to choose all the required hardware ourself beside the two BeagleBoards, which we were luckily supplied by Konrad and Dennis.
@@ -122,6 +129,10 @@ Since one of the project goals was to reduce the costs as much as it was possibl
Protocols used by old versions of Nokia phones as the 3310 use the F-Bus protocol. It was not easy to work with.
After performing various experiments we found out that it was not possible to
send commands for controlling the calls. In the meantime we found two Siemens phones, one M45 and S55.
+The first one, Siemens M45, had a cable supplied with it and it was not difficult to control it with AT commands.
+At the start we did not have a cable supplied with the Siemens S55 phone. We controlled it over the Bluetooth port.
+\subsection{Cables}
+
\newpage
\section{Communication protocol}
diff --git a/notFinishedCode/Report/test.tex~ b/notFinishedCode/Report/test.tex~
index 24fb21e..5719ec7 100644
--- a/notFinishedCode/Report/test.tex~
+++ b/notFinishedCode/Report/test.tex~
@@ -102,27 +102,46 @@ Prof. Dr. Gerhard Schneider\\ \vspace{1\baselineskip} Supervisors: \\ Konrad Mei
Before we had started working on our project, we had to analyze the overall network to come up with test cases that contain the highest information content. The next step in our procedure was to implement our ideas into a working piece of software.
Gradually we implemented a bit-by-bit of the final software. Every single step was accompanied by testing and validation procedures. At the end we connected all the ``black-boxes'' into one big piece of software. We have fulfilled our requests and goals and made a fully working and operable test software. Despite developing a working software, all the way along we thought about the simplicity of the usage of the software. In the following chapters we will describe in more detail our approach and how each subsystem works.
\newpage
-\section{Requests} % chapter 2
+\section{Requirements} % chapter 2
\newpage
\section{Database design}
+How we designed our database and why, explain in this section!
\newpage
\section{Software design} % section 2.1
-\subsection{Usage} % subsection 2.1.1
+\subsection{Database access} % subsection 2.1.1
+\subsection{Controlling the cell phones}
+Our first version of the developed program code for controlling the cell phones used predefined timed values
+to send commands instead of using a state controlled approach to confirm that every command was successfuly received and executed by the cell phone.
+It meant we had to make an enormous number of assumptions. In comparison to our second approach, to build a state controlled cell phone control class,
+our first approach was inferior and slower. The state controlled method connected two cell phones, on the same base station, up to 15 times faster than timed approach.
+\subsection{}
\newpage
\section{Hardware design}
In our team project we had the option to choose all the required hardware ourself beside the two BeagleBoards, which we were luckily supplied by Konrad and Dennis.
-Since one of the project goals was to reduce the costs as much as it was possible, we had tried to use some of the leftovers in our lab.
-
+Since one of the project goals was to reduce the costs as much as it was possible, we had tried to use some of the leftovers found in our lab.
+
+\subsection{BeagleBoard}
+``The BeagleBoard is an OMAP3530 platform designed specifically to address the Open
+Source Community. It has been equipped with a minimum set of features to allow the
+user to experience the power of the OMAP3530 and is not intended as a full development
+platform as many of the features and interfaces supplied by the OMAP3530 are not
+accessible from the BeagleBoard'' \cite{beagleDataSheet}.
\begin{figure}[ht!]
\centering
\includegraphics[width=130mm]{bb.jpg}
\caption[]{BeagleBoard, a linux-on-chip board where our controller software runs the GSM device }
\end{figure}
-\par Our first attempt was to control a Nokia cell phone 3310 with the supplied USB connection cable.
-Protocols used by old versions of Nokia phones as the 3310 use the F-Bus protocol. It was not easy to work with.
-After performing various experiments we found out that it was not possible to
-send commands for controlling the calls. In the meantime we found two Siemens phones, one M45 and S55.
-The first one, Siemens M45 had a cable and it was not so difficult to control it with the
+
+\subsection{Cell phones}
+Our first attempt was to control a Nokia cell phone 3310 with the supplied USB connection cable.
+The protocols used by old versions of Nokia cell phones, as the 3310, use the F-Bus protocol. It was not easy to work with.
+After performing various experiments we succeeded to send and to read SMS messages. Later on we found out that it was not possible to
+send commands for receiving and making the calls. In the meantime we found two Siemens phones, one M45 and S55.
+The first one, Siemens M45, had a cable supplied with it and it was not difficult to control it with the standard set of AT modem commands.
+At the start we did not have a cable supplied for the Siemens S55 phone. We controlled it over the Bluetooth port.
+
+\subsection{Cables for the cell phones}
+
\newpage
\section{Communication protocol}
@@ -391,6 +410,9 @@ Hypothesis}, preprint (2003), available at
\bibitem{pChart} \emph{pChart}, accessed on 15.08.2011, available at
\url{http://http://www.pchart.net/}.
+\bibitem{{beagleDataSheet} \emph{BeagleBoard System Reference Manual}, accessed on 20.06.2011, available at
+\url{http://beagleboard.org/static/BBSRM_latest.pdf}.
+
%bibliography end
\end{thebibliography}
diff --git a/notFinishedCode/Report/test.toc b/notFinishedCode/Report/test.toc
index 2f6da58..a6e62b0 100644
--- a/notFinishedCode/Report/test.toc
+++ b/notFinishedCode/Report/test.toc
@@ -1,15 +1,20 @@
\select@language {english}
\contentsline {section}{\numberline {1}Introduction and Motivation}{3}
-\contentsline {section}{\numberline {2}Requests}{4}
+\contentsline {section}{\numberline {2}Requirements}{4}
\contentsline {section}{\numberline {3}Database design}{5}
\contentsline {section}{\numberline {4}Software design}{6}
-\contentsline {subsection}{\numberline {4.1}Usage}{6}
+\contentsline {subsection}{\numberline {4.1}Database access}{6}
+\contentsline {subsection}{\numberline {4.2}Controlling the cell phones}{6}
+\contentsline {subsection}{\numberline {4.3}}{6}
\contentsline {section}{\numberline {5}Hardware design}{7}
-\contentsline {section}{\numberline {6}Communication protocol}{8}
-\contentsline {section}{\numberline {7}Security and safety of the system}{10}
-\contentsline {subsection}{\numberline {7.1}Encryption of the communication channels}{10}
-\contentsline {subsection}{\numberline {7.2}Security on the web site}{11}
-\contentsline {section}{\numberline {8}Web page}{15}
-\contentsline {subsection}{\numberline {8.1}Communication between the web page and the test software}{15}
-\contentsline {subsection}{\numberline {8.2}Results on the web page}{15}
-\contentsline {section}{\numberline {9}Conclusion}{17}
+\contentsline {subsection}{\numberline {5.1}BeagleBoard}{7}
+\contentsline {subsection}{\numberline {5.2}Cell phones}{8}
+\contentsline {subsection}{\numberline {5.3}Cables for the cell phones}{8}
+\contentsline {section}{\numberline {6}Communication protocol}{9}
+\contentsline {section}{\numberline {7}Security and safety of the system}{11}
+\contentsline {subsection}{\numberline {7.1}Encryption of the communication channels}{11}
+\contentsline {subsection}{\numberline {7.2}Security on the web site}{12}
+\contentsline {section}{\numberline {8}Web page}{16}
+\contentsline {subsection}{\numberline {8.1}Communication between the web page and the test software}{16}
+\contentsline {subsection}{\numberline {8.2}Results on the web page}{16}
+\contentsline {section}{\numberline {9}Conclusion}{18}