From 00a9af2664abff1b74f9d34768e05b41e3e7d684 Mon Sep 17 00:00:00 2001 From: Refik Hadzialic Date: Wed, 29 Aug 2012 17:33:14 +0200 Subject: Results --- vorlagen/thesis/maindoc.pdf | Bin 17062906 -> 17080408 bytes vorlagen/thesis/src/bib/literatur.bib | 45 ++- vorlagen/thesis/src/img/googlemapsResults.pdf | Bin 2520684 -> 2520814 bytes vorlagen/thesis/src/img/googlemapsResults.svg | 453 ++++++++++++++------------ vorlagen/thesis/src/kapitel_x.tex | 234 +++++++++---- vorlagen/thesis/src/maindoc.lof | 2 +- vorlagen/thesis/src/maindoc.lot | 5 +- 7 files changed, 449 insertions(+), 290 deletions(-) diff --git a/vorlagen/thesis/maindoc.pdf b/vorlagen/thesis/maindoc.pdf index 2e94f6a..f15a741 100644 Binary files a/vorlagen/thesis/maindoc.pdf and b/vorlagen/thesis/maindoc.pdf differ diff --git a/vorlagen/thesis/src/bib/literatur.bib b/vorlagen/thesis/src/bib/literatur.bib index cc1b471..2300432 100644 --- a/vorlagen/thesis/src/bib/literatur.bib +++ b/vorlagen/thesis/src/bib/literatur.bib @@ -91,7 +91,7 @@ month = sep, organization = "Department of Defence, U.S. of America", publisher = "Pentagon", - title = "{GLOBAL POSITIONING SYSTEM STANDARD POSITIONING SERVICE PERFORMANCE STANDARD}", + title = "GLOBAL POSITIONING SYSTEM STANDARD POSITIONING SERVICE PERFORMANCE STANDARD", url = "http://www.gps.gov/technical/ps/2008-SPS-performance-standard.pdf", year = "2008" } @@ -109,7 +109,7 @@ @inproceedings{implSoftGPSRec, author = "Ma, Changlin and Lachapelle, Gerard and Cannon, M. Elizabeth", - booktitle = "{Proceedings of ION GNSS 2004 (Session A3), Long Beach, CA}", + booktitle = "Proceedings of ION GNSS 2004 (Session A3), Long Beach, CA", month = "sep.", title = "{Implementation of a Software GPS Receiver}", url = "http://plan.geomatics.ucalgary.ca/papers/04gnss_ion_cmaetal.pdf", @@ -719,4 +719,45 @@ ISSN={0018-9251},} note = "[Online; accessed 29-August-2012]", title = "{Detailed specifications for the Nokia N95}", year = "2006" +} + +@misc{gpsAntenna, + author = "u-blox AG", + howpublished = "\url{https://www.u-blox.com/images/downloads/Product_Docs/GPS_Antennas_ApplicationNote%28GPS-X-08014%29.pdf}", + note = "[Online; accessed 5-April-2012]", + title = "{GPS Antennas: RF Design Considerations for u-blox GPS Receivers}", + year = "2009" +} + +@inproceedings{agpsTests, + author = "P. Boulton and A. Read and G. MacGougan and R. Klukas and M. E. Cannon and G. Lachapelle", + booktitle = "Proceedings of the 15th International Technical Meeting of the Satellite Division of The Institute of Navigation (ION GPS 2002)", + month = "sep.", + title = "Proposed Models and Methodologies for Verification Testing of AGPS-Equipped Cellular Mobile Phones in the Laboratory", + url = "http://plan.geomatics.ucalgary.ca/papers/boulton_et_al_ion_gps2002.pdf", + year = "2002" +} + +@inproceedings{agpsTests1, + author = "S. Singh", + booktitle = "Proceedings of the 19th International Technical Meeting of the Satellite Division of The Institute of Navigation (ION GNSS 2006)", + month = "sep.", + title = "Evaluation of Assisted GPS (AGPS) Performance Using Simulator and Field Tests", + url = "http://plan.geomatics.ucalgary.ca/papers/SanjeetION2006Student.pdf", + year = "2006" +} + +@misc{predictMovements, + author = {S. MALM and L. OSBORNE}, + howpublished = {\url{http://www.dailymail.co.uk/sciencetech/article-2190531/Mobile-phone-companies-predict-future-movements-users-building-profile-lifestyle.html}}, + note = {[Online; accessed 29-August-2012]}, + title = {Mobile phone companies can predict future movements of users by building a profile of their lifestyle} +} + +@misc{gpsTest2, + author = "Spirent Communication", + howpublished = "\url{http://www.spirentfederal.com/gps/documents/Spirent_A-GPS_OTA_whitepaper.pdf}", + note = "[Online; accessed 20-August-2012]", + title = "A-GPS Over the Air Test Method: Business and Technology Implications", + year = "2009" } \ No newline at end of file diff --git a/vorlagen/thesis/src/img/googlemapsResults.pdf b/vorlagen/thesis/src/img/googlemapsResults.pdf index 45b7706..fb166a5 100644 Binary files a/vorlagen/thesis/src/img/googlemapsResults.pdf and b/vorlagen/thesis/src/img/googlemapsResults.pdf differ diff --git a/vorlagen/thesis/src/img/googlemapsResults.svg b/vorlagen/thesis/src/img/googlemapsResults.svg index 0586be0..9b43ded 100644 --- a/vorlagen/thesis/src/img/googlemapsResults.svg +++ b/vorlagen/thesis/src/img/googlemapsResults.svg @@ -19,7 +19,7 @@ sodipodi:docname="googlemapsResults.svg">image/svg+xml + id="g3346" + transform="scale(0.1,0.1)"> + Test room 2 + id="g7302">Test room 2 + Test room 1 + style="fill:none;stroke:#000000;stroke-width:3.20000004999999987;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;marker-start:url(#Arrow2Lstart-6)" + d="m 746.20847,424.74534 70.76271,60.1483" + id="path6922" + inkscape:connector-curvature="0" />Test room 1 + Test room 3 + style="fill:none;stroke:#000000;stroke-width:3.20000005;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;marker-start:url(#Arrow2Lstart-6)" + d="m 832.72376,337.89195 76.06992,37.15043" + id="path7900" + inkscape:connector-curvature="0" />Test room 3 + Test outside + style="fill:none;stroke:#000000;stroke-width:4;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;stroke-miterlimit:4;stroke-dasharray:none;marker-start:url(#Arrow2Lstart-6)" + d="m 997.31197,681.0911 90.66473,57.4947" + id="path8305" + inkscape:connector-curvature="0" + transform="matrix(0.8,0,0,-0.8,-90.898782,944.93439)" />Test outside + 2 + style="opacity:0.75000000000000000;fill:#903027;fill-opacity:1;fill-rule:nonzero;stroke:#ff6600;stroke-width:3.20000004999999987;stroke-linecap:square;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;stroke-dashoffset:0" + id="rect8565" + width="72.531784" + height="392.73306" + x="-211.18645" + y="-846.07587" + transform="matrix(0.80798481,-0.58920332,-0.58920332,-0.80798481,0,0)" />2 + 20 m + id="g9212">20 m + 1 + inkscape:connector-curvature="0" + id="path8578" + d="m 83.463501,64.691259 100.664099,0" + style="fill:none;stroke:#000000;stroke-width:3.20000005;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;marker-start:url(#StopL);marker-end:url(#StopL)" />1 + 2 + style="opacity:0.63374484;fill:#31cece;fill-opacity:1;fill-rule:nonzero;stroke:#ff6600;stroke-width:3.20000005;stroke-linecap:square;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;stroke-dashoffset:0" + id="rect9224" + width="28.305084" + height="47.764832" + x="396.6257" + y="698.58466" + transform="matrix(0.18309759,0.98309474,0.98309474,-0.18309759,0,0)" />2 + +O \ No newline at end of file diff --git a/vorlagen/thesis/src/kapitel_x.tex b/vorlagen/thesis/src/kapitel_x.tex index c4d2711..eb8bec9 100644 --- a/vorlagen/thesis/src/kapitel_x.tex +++ b/vorlagen/thesis/src/kapitel_x.tex @@ -2680,7 +2680,7 @@ configuration the power supply port is not used. The following port is for the e connection with 48 V DC power supply. This port is connected to a power supply that is supplied with the nanoBTS. It extends the ethernet connection with 48 V DC for the normal operation mode of the nanoBTS which is in the range between 38-50 V DC. -The power consumtion of the nanoBTS is 13 W. More details on how to interconnect the cables +The power consumption of the nanoBTS is 13 W. More details on how to interconnect the cables shall be given in section \ref{sec:hardwareConfig}. In the middle of the five port region, the mini USB port can be found. It is used by the manufacturer to write the firmware software to the nanoBTS. The last two ports are the TIB-IN and TIB-OUT port\footnote{TIB stands @@ -2825,9 +2825,9 @@ were obtained. Analysis of the results by the time required to perform a localization of a GSM user and the geographical dislocation error using Google maps are going to be discussed. Smart phones used for the test are going to be introduced and followed by the location -of the tests. After the results have been presented, +of the tests. After the results have been provided, a section with criticism demonstrates all the obstacles that may have appeared -while the tests have been performed and why some of the results may biased. The criticism +while the tests have been performed and why some of the results may be biased. The criticism section is a vital part of this thesis, aside from the given theoretical and mathematical perspective of how AGPS works and why lack of time synchronization inside GSM can be of critical value to correctly evaluate the results. It gives an additional @@ -2880,7 +2880,12 @@ first only an RRLP request without any assistance data was sent. The second test included an RRLP request with almanac, UTC model, ionospheric model and reference location data. The last test was an RRLP request with almanac, ephemeris, UTC model, ionospheric model and reference location data. The stated requests have been sent in an -reverse order, to observe if the smart phones can actually make an usage of the assistance data. +reverse order, to observe if the smart phones can actually make an usage of the assistance data. +The RRLP requests were manually sent from the telnet interface from OpenBSC after they have been +implemented by the author. Results delivered by the MS were stored in the database and the +following analysis is based on them and on the time out results which were not stored in the +database but notices by the author. + \begin{figure}[ht!] \centering \includegraphics[scale=0.38]{img/googlemapsResults.pdf} @@ -2909,6 +2914,28 @@ $G1$ may not know how to employ the ephemeris data because it is one of the firs market. Later on it can be seen other smart phones that are even older than the $G1$ can not employ any of the assistance data. +\begin{figure} + ~ %add desired spacing between images, e. g. ~, \quad, \qquad etc. + %(or a blank line to force the subfigure onto a new line) + \centering + \begin{subfigure}[b]{0.3\textwidth} + \centering + \includegraphics[width=\textwidth]{img/smartPhoneWindow.jpg} + \caption{Smart phones on the window.} + \label{fig:window} + \end{subfigure} + ~ %add desired spacing between images, e. g. ~, \quad, \qquad etc. + %(or a blank line to force the subfigure onto a new line) + \begin{subfigure}[b]{0.3\textwidth} + \centering + \includegraphics[width=\textwidth]{img/smartRoomTable.jpg} + \caption{Smart phones on the table.} + \label{fig:table} + \end{subfigure} + \caption{Test room 2 with the positions of the smart phones}\label{fig:animals} + \label{img:smartphonepositions} +\end{figure} + The second tests took place in Test room 2. Test room 2 is located in the basement of the computer pool, with the following coordinates: latitude 48\textdegree 0'13.12"N and longitude 7\textdegree 50'53.50"E. The fact tests took place in the basement adds @@ -2936,18 +2963,12 @@ The majority of the performed tests in this work were performed in this room. Smart phones have been tested on the table which is $3 m$ away from the windows and on the window itself, as shown in figure \ref{img:smartphonepositions}. These small changes in position of the smart phone did not make any difference -in the resulting estimated position. To find out if the delivered -results are taken from the cache or some other memory in the -smart phone, the same test have been performed in the basement hallway where no -windows exist just after the smart phones delivered successfully their position -in Test room 2. This test did not deliver any position but only time outs -or errors. This test provided and confirmed that the smart phones are always -performing a postion estimation at the moment when an RRLP request is sent -to the MS. The smart phones tested in Test room 2 were all the listed ones -in table \ref{tbl:smartphones}. One unanticipated finding was that -the ``newer generation'' smart phones did not deliver their -position in any case but rather requested more assistance data like $iPhone$ $4$, -$Galaxy$ $S2$ and $Galaxy$ $S3$. There are two possible explanations for this result. +in the resulting estimated position. The smart phones tested in Test +room 2 were all the listed ones in table \ref{tbl:smartphones}. One +unanticipated finding was that the ``newer generation'' smart phones did not +deliver their position in any case but rather requested more assistance data +like $iPhone$ $4$, $Galaxy$ $S2$ and $Galaxy$ $S3$. There are two possible +explanations for this result. This might be because the newer AGPS devices require more assistance data by relying on the network providers to have synchronized GSM systems or it is an security protection of the smart phone user. No information on the AGPS receiver @@ -2963,67 +2984,123 @@ the tests. At the time point when they were released by Nokia the firmware for t might not have been fully evolved and developed since both models are from the same company. +The third test took place in Test room 3, as shown in figure \ref{img:googlemapsResults} +by the yellow dot. The smart phones were placed on the windows. +In this room the smart phones tested did not deliver any positions but only errors about +missing assistance data and time outs. While no MS delivered its position, the room was +tested if a GPS position can be obtained with an external GPS receiver. +The test was successful and after 12 minutes the position was obtained but the signal +strength was weak according to the delivered GPS output. An implication emerging from +this finding may be related to the GPS receiver high sensitivity (-160 dBm $10^{−16}$ mW) +and an active patch antenna with a size of 2x2 cm \citep{ubxDatasheet}. +The GPS receivers employed in smart phones have to be small in size to fit into the device +and use a passive antenna because active antennas have an additional power consumption +\citep{gpsAntenna}. + +To determine if the delivered results are taken from the cache or some other memory in the +smart phone, the same test have been performed in the basement hallway where no +windows exist just after the smart phones delivered successfully their position +in Test room 2. This test did not deliver any position but only time outs +or errors containing information that no satellites are visible. +This test provided and confirmed that the smart phones are always performing a +postion estimation at the moment when an RRLP request is sent to the MS. + +The last test has been performed outside of the computer pool building. +This test was conducted to confirm the argument that precision of the estimated +position is related to the received GPS signal strength and number of visible satellites. +As it can be seen in figure \ref{img:googlemapsResults}, the tests were performed +at the blue dot and around it and the estimated positions were 1-5 m off of +the real position. The estimated positions are shown in a blue rectangle with an O +in the left corner of it. +\begin {table}[ht] +\caption{Smart phone RRLP test results} +\label{tbl:resultsByTest}\centering +%\rowcolor{2}{light-gray}{} +\scriptsize\fontfamily{iwona}\selectfont +\begin{tabular}{lllll} +\toprule +%$D$&&$P_u$&$\sigma_N$\\ +Cell phone model&RRLP(E)&RRLP(A)&RRLP&Type of error (or missing data)\\\toprule +$Defy$&No&No&No&No response (time out) \\\midrule +$iPhone$ $4$&No&No&No&Reference time, Navigation Model,\\ +&&&&Reference Location\\\midrule +$iPhone$ $3GS$&Yes&Yes&No&/\\\midrule +$G1$&No&Yes&Sometimes&/\\\midrule +$Galaxy$ $S2$&No&No&No&Acquisition Assistance\\\midrule +$Galaxy$ $S3$&No&No&No&Reference Location, Reference Time,\\ +&&&&Acquisition Assistance, Navigation Model\\\midrule +$Galaxy$ $Nexus$ $i9250$&No&No&No&Did not respond, only ACKs\\\midrule +$E71$&No&No&Yes&/\\\midrule +$N95$&No&No&Yes&/\\\midrule +$Desire$ $S$&Yes&No&No&/\\\midrule +$Blade$&No&No&Yes&/ +\\\bottomrule +\end {tabular} +\end {table} +In table \ref{tbl:resultsByTest} the list of all results is shown. The abbreviations +used in the table are explained in this paragraph. RRLP indicates the MS has delivered its +position only when an RRLP position request without any assistance data has been sent. +RRLP(E) indicates the MS has delivered its position only when an RRLP request contained +almanac, ephemeris, UTC model, ionospheric model and reference location data has been sent. +RRLP(A) indicated the MS has delivered its position only when an RRLP request contained +almanac, UTC model, ionospheric model and reference location data has been sent (the difference +from RRLP(E) is in the fact that no ephemeris data are included). If there is no error description +then the stated data were requested to be delivered to the MS. If the position was delivered the +position estimation by the smart phones took never longet than 3 minutes. The waiting time period +of 3 minutes for the result is not discouraging provided that the assistance data like +reference time (exact time, explained in section \ref{sec:rrlpassistance}) and +acquisition assistance data (phase and Doppler effect frequency required by the AGPS, +explained in section \ref{sec:rrlpassistance}) were not delivered to the MS. It is important +to mention the strange behaviour by $Galaxy$ $Nexus$ $i9250$, the MS responded only with +acknowledgements while the assistance data have been sent but after the reception it +immediatelly closed the SDCCH channel. The $Blade$ closed the SDCCH channel after 4 transmitted +assistance packets for the RRLP(E) test. The $Defy$ by Motorola did not produce any output at +all and behaved like a 2G cell phone without a GPS receiver. To eliminate any doubts and +suspicion if the SDCCH channel was properly working and not producing the time outs, +2G phones (Nokia 3310 and Siemens M50) have been used to perform tests. An SDCCH channel +has been initialized 10 times at different days with the 2G phones and left open for 10 +minutes. The 2G phones reported the signal strengths of the initialized channel according +to the defined standard. This provides a proof for the cases where the time out appeared, +it was not produced by the BTS but rather by the smart phone. One important remark related +to the tests ought to be mentioned. While the $iPhone$ $3GS$ and $G1$ provided the results in +the tests, sometimes it was the case they did not deliver the results the first time +the RRLP request was executed but an time out. Second time the same RRLP request was sent, +the smart phones delivered their positions. This unexpected behaviour raises a suspicion that +the smart phones do not behave according to the RRLP standard where it is well defined how much +time they have to perform the localization. However, the previous statement ought to be considered +with some uncertainty since it can not be proved without access to the firmware of the smart phones. +The combination of described findings in this chapter and in table \ref{tbl:resultsByTest} +provides some support for the premise that the RRLP standard is not yet a fully implemented +standard by all the manufacturers that claim AGPS functionality. Does it dependt on the AGPS chipset +or RRLP itself, remains an open question. -\begin{figure} - ~ %add desired spacing between images, e. g. ~, \quad, \qquad etc. - %(or a blank line to force the subfigure onto a new line) - \centering - \begin{subfigure}[b]{0.3\textwidth} - \centering - \includegraphics[width=\textwidth]{img/smartPhoneWindow.jpg} - \caption{Smart phones on the window.} - \label{fig:window} - \end{subfigure} - ~ %add desired spacing between images, e. g. ~, \quad, \qquad etc. - %(or a blank line to force the subfigure onto a new line) - \begin{subfigure}[b]{0.3\textwidth} - \centering - \includegraphics[width=\textwidth]{img/smartRoomTable.jpg} - \caption{Smart phones on the table.} - \label{fig:table} - \end{subfigure} - \caption{Test room 2 with the positions of the smart phones}\label{fig:animals} - \label{img:smartphonepositions} -\end{figure} - -Comparing the two results, it can be seen that - -Motorola Defy Nothing -Samsung Galaxy S2 H -Nokia E71 -Nokia N95 4810 error -iPhone 4 D,G,F -iPhone 3GS -Google phone G1 -HTC Desire S -ZTE Blade -Samsung Galaxy S3 -Samsung Galaxy Nexus i9250 - -\newpage \section{Criticism of performed tests} Perhaps the most serious weakness of the presented results is that the author had no access to the firmware of the MS while the tests have been performed. This would allow the author to see what type and how the assistance data are employed by the AGPS in the MS. If access could be gained, to the internal operation of the AGPS receiver, -all bias could be eliminated whether the AGPS receiver uses the transmitted -assistance data or it may be the case that they are from the memory in the -smart phones. The whole system represents a black box where an input is +all doubts and bias about the deduced hypotheses could be eliminated. +The whole system represents a black box where an input is delivered and an output is expected. Another drawback was the lack of -the hardware information inside the MS. This does not allow an exact -comparison between different cell phone models. - +hardware information about the hardware inside of the MS (AGPS receivers and +antennas). This does not allow an exact comparison between different +cell phone models and if they can acquire any GPS signal in weak signal +strength conditions. Difficulties arise in assessment and comparing the results in this -thesis with other relevant studies due to the lack of expensive -hardware equipment used in the studies. In addition, no research has -been found that surveyed the amount of time required to get a -position response from a MS where only almanac, ephemeris, UTC model, -ionospheric model and reference location data have been delivered to -the MS. +thesis with other relevant studies due to the lack of any research +studies compleyed using the equivalent hardware and type of +assistance data. In the relevant studies different +hardware test equipment is used while this thesis was carried +out without that test equipment \citep{agpsTests} \citep{agpsTests1} +\citep{gpsTest2}. +In addition, no research has been found that surveyed the amount of +time required to get a position response from a MS where only +almanac, ephemeris, UTC model, ionospheric model and reference +location data have been delivered to the MS. Another limitation of the evaluated results lies in the fact that it has only been applied to the stated cell phones and it could not be tested @@ -3033,18 +3110,37 @@ rather in serial manner in time. In other words a satellite visible at the moment while the first test is being performed may not be visible the second time when the test is executed. GPS signal strength is a vital measurement information, where the signal levels are lower than a -predefined acquisition sensitivity even assistance data can not always help. +predefined acquisition sensitivity even assistance data can not help. Antenna polarization and the position of the cell phone matter as well. Correctness of assistance data in almanac and ephemeris data can not be verified. The author had to rely and trust NASA and Trimble as sources although errors were confirmed by different studies in \citep{Stanford-Ephem-Errors} \citep{NASA-Ephem-Errors}. Errors can be confirmed by the author in -ephemeris data as well (URA values were out of range specified by the standard). +ephemeris data as well (URA values were out of range specified by the standard). +These errors were not continual but appeared occasionally and these errors +were inside of the assistance data provided by NASA. \section{Future work} - -Test if it can be tricked out by the software Dennis mentioned (protect my privacy)! +The system could be extended with a GPS device that delivers raw GPS data +instead of using the data provided by NASA and Trimble. Obtained data by the GPS +could be compared to the data provided by NASA or other GPS observation stations +and verified for errors. By having more redundant sources of same information, +mistakes in the output could be eliminated. More sources of redundant data could +indicate the correctness of assistance data. + +Another idea to extend this work would be to use an LMU and provide the +reference time and acquisition assistance data. This feature would enhance the +complete system. However, one ought to understand it would require great changes +in the OpenBSC source code and interoperability between the BTS and LMU. + +Additionally a position tracking system could be built. By adding a timer that will +execute an RRLP request every few minutes. The successfully estimated positions could +be connected into a path and displayed where the GSM user spends his time. Along the +described method, a machine learning algorithm could be developed to predict the +movement of GSM users \citep{predictMovements}. + +%Test if it can be tricked out by the software Dennis mentioned (protect my privacy)! \chapter{Summary} diff --git a/vorlagen/thesis/src/maindoc.lof b/vorlagen/thesis/src/maindoc.lof index 1af8fb9..b9038bd 100644 --- a/vorlagen/thesis/src/maindoc.lof +++ b/vorlagen/thesis/src/maindoc.lof @@ -43,5 +43,5 @@ \contentsline {figure}{\numberline {6.4}{\ignorespaces Cable connections, showing interconnection diagram\relax }}{73}{figure.caption.53} \addvspace {10\p@ } \contentsline {figure}{\numberline {7.1}{\ignorespaces Test rooms as well as the results delivered by the smart phones.\relax }}{77}{figure.caption.55} -\contentsline {figure}{\numberline {7.2}{\ignorespaces Test room 2 with the positions of the smart phones\relax }}{79}{figure.caption.56} +\contentsline {figure}{\numberline {7.2}{\ignorespaces Test room 2 with the positions of the smart phones\relax }}{78}{figure.caption.56} \addvspace {10\p@ } diff --git a/vorlagen/thesis/src/maindoc.lot b/vorlagen/thesis/src/maindoc.lot index 01a28a4..5ffc3d6 100644 --- a/vorlagen/thesis/src/maindoc.lot +++ b/vorlagen/thesis/src/maindoc.lot @@ -17,6 +17,7 @@ \contentsline {table}{\numberline {6.1}{\ignorespaces Indicator LED status on the nanoBTS\relax }}{74}{table.caption.51} \addvspace {10\p@ } \contentsline {table}{\numberline {7.1}{\ignorespaces Smart phone models used for testing in the thesis.\relax }}{76}{table.caption.54} +\contentsline {table}{\numberline {7.2}{\ignorespaces Smart phone RRLP test results\relax }}{80}{table.caption.57} \addvspace {10\p@ } -\contentsline {table}{\numberline {A.3.1}{\ignorespaces Example uncertainties (latitude and longitude) for various integer values of $K$\relax }}{91}{table.caption.62} -\contentsline {table}{\numberline {A.3.2}{\ignorespaces Example uncertainties (altitude) for various integer values of $K$\relax }}{92}{table.caption.63} +\contentsline {table}{\numberline {A.3.1}{\ignorespaces Example uncertainties (latitude and longitude) for various integer values of $K$\relax }}{95}{table.caption.63} +\contentsline {table}{\numberline {A.3.2}{\ignorespaces Example uncertainties (altitude) for various integer values of $K$\relax }}{96}{table.caption.64} -- cgit v1.2.3-55-g7522