summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRefik Hadzialic2012-08-03 18:39:32 +0200
committerRefik Hadzialic2012-08-03 18:39:32 +0200
commite1f098a49b17a82fc79ae9f51a425c8f6c0a0215 (patch)
tree3493057de237a0ef98a5c3fa6742d9d148f66335
parentAssistance (diff)
downloadmalign-e1f098a49b17a82fc79ae9f51a425c8f6c0a0215.tar.gz
malign-e1f098a49b17a82fc79ae9f51a425c8f6c0a0215.tar.xz
malign-e1f098a49b17a82fc79ae9f51a425c8f6c0a0215.zip
RRLP Response
-rw-r--r--vorlagen/thesis/maindoc.pdfbin6165273 -> 6198019 bytes
-rw-r--r--vorlagen/thesis/src/erklaerung.tex3
-rw-r--r--vorlagen/thesis/src/img/RRLPReqExplained.pdfbin28422 -> 29055 bytes
-rw-r--r--vorlagen/thesis/src/img/RRLPReqExplained.svg88
-rw-r--r--vorlagen/thesis/src/kapitel_x.tex290
-rw-r--r--vorlagen/thesis/src/maindoc.lof39
-rw-r--r--vorlagen/thesis/src/maindoc.lol15
-rw-r--r--vorlagen/thesis/src/maindoc.lot17
-rw-r--r--vorlagen/thesis/src/maindoc.tex2
9 files changed, 341 insertions, 113 deletions
diff --git a/vorlagen/thesis/maindoc.pdf b/vorlagen/thesis/maindoc.pdf
index 71feb3e..fa89ec6 100644
--- a/vorlagen/thesis/maindoc.pdf
+++ b/vorlagen/thesis/maindoc.pdf
Binary files differ
diff --git a/vorlagen/thesis/src/erklaerung.tex b/vorlagen/thesis/src/erklaerung.tex
index a3f158b..860857c 100644
--- a/vorlagen/thesis/src/erklaerung.tex
+++ b/vorlagen/thesis/src/erklaerung.tex
@@ -42,5 +42,4 @@ are intellectually seductive in some way and it kept me motivated and working du
periods.
\newpage
-\section*{
-Abstract} \ No newline at end of file
+\section*{Abstract} \ No newline at end of file
diff --git a/vorlagen/thesis/src/img/RRLPReqExplained.pdf b/vorlagen/thesis/src/img/RRLPReqExplained.pdf
index bbbd658..94877be 100644
--- a/vorlagen/thesis/src/img/RRLPReqExplained.pdf
+++ b/vorlagen/thesis/src/img/RRLPReqExplained.pdf
Binary files differ
diff --git a/vorlagen/thesis/src/img/RRLPReqExplained.svg b/vorlagen/thesis/src/img/RRLPReqExplained.svg
index b888015..4965e2d 100644
--- a/vorlagen/thesis/src/img/RRLPReqExplained.svg
+++ b/vorlagen/thesis/src/img/RRLPReqExplained.svg
@@ -138,7 +138,7 @@
inkscape:pageopacity="0.0"
inkscape:pageshadow="2"
inkscape:zoom="2.8"
- inkscape:cx="74.906758"
+ inkscape:cx="368.4111"
inkscape:cy="79.13056"
inkscape:document-units="mm"
inkscape:current-layer="layer1"
@@ -187,6 +187,46 @@
inkscape:groupmode="layer"
id="layer1"
transform="translate(97.475456,-310.06305)">
+ <path
+ style="fill:none;stroke:#989898;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1"
+ d="m 35.433068,422.11889 0,3.07797 60.6629,0 0,-3.43511"
+ id="path4071"
+ inkscape:connector-curvature="0" />
+ <path
+ style="fill:none;stroke:#989898;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1"
+ d="m 99.612694,421.65356 0,3.5433 59.026236,0 0,-3.5433"
+ id="path4073"
+ inkscape:connector-curvature="0" />
+ <path
+ style="fill:none;stroke:#989898;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1"
+ d="m 162.15565,421.65356 0,3.5433 58.10385,0 0,-3.43511"
+ id="path4075"
+ inkscape:connector-curvature="0" />
+ <path
+ style="fill:none;stroke:#989898;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1"
+ d="m 223.77622,422.11889 0,3.07797 58.93906,0 0,-3.5433"
+ id="path4077"
+ inkscape:connector-curvature="0" />
+ <path
+ style="fill:none;stroke:#989898;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1"
+ d="m 286.232,422.11889 0,3.07797 58.92857,0 0,-3.5433"
+ id="path4079"
+ inkscape:connector-curvature="0" />
+ <path
+ style="fill:none;stroke:#989898;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1"
+ d="m 348.67728,421.65356 0,3.5433 59.24148,0 0,-3.5433"
+ id="path4081"
+ inkscape:connector-curvature="0" />
+ <path
+ style="fill:none;stroke:#989898;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1"
+ d="m 411.43549,421.65356 0,3.5433 58.28663,0 0,-3.5433"
+ id="path4083"
+ inkscape:connector-curvature="0" />
+ <path
+ style="fill:none;stroke:#989898;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1"
+ d="m 473.23884,421.65356 0,3.67961 60.71428,0 0,-3.92857"
+ id="path4085"
+ inkscape:connector-curvature="0" />
<text
xml:space="preserve"
style="font-size:16px;font-style:normal;font-weight:normal;line-height:125%;letter-spacing:0px;word-spacing:0px;fill:#000000;fill-opacity:1;stroke:none;font-family:Sans"
@@ -547,5 +587,51 @@
id="tspan4173"
x="-63.045769"
y="408.5798">RRLP PDU:</tspan></text>
+ <text
+ xml:space="preserve"
+ style="font-size:16px;font-style:normal;font-weight:normal;line-height:125%;letter-spacing:0px;word-spacing:0px;fill:#989898;fill-opacity:1;stroke:none;font-family:Sans"
+ x="60.738834"
+ y="440.79865"
+ id="text4087"
+ sodipodi:linespacing="125%"><tspan
+ sodipodi:role="line"
+ id="tspan4089"
+ x="60.738834"
+ y="440.79865">4 0 </tspan></text>
+ <text
+ xml:space="preserve"
+ style="font-size:16px;font-style:normal;font-weight:normal;line-height:125%;letter-spacing:0px;word-spacing:0px;fill:#989898;fill-opacity:1;stroke:none;font-family:Sans"
+ x="186.81027"
+ y="440.79865"
+ id="text4091"
+ sodipodi:linespacing="125%"><tspan
+ sodipodi:role="line"
+ id="tspan4093"
+ x="186.81027"
+ y="440.79865">0 1</tspan></text>
+ <text
+ xml:space="preserve"
+ style="font-size:16px;font-style:normal;font-weight:normal;line-height:125%;letter-spacing:0px;word-spacing:0px;fill:#989898;fill-opacity:1;stroke:none;font-family:Sans"
+ x="311.09598"
+ y="440.79865"
+ id="text4095"
+ sodipodi:linespacing="125%"><tspan
+ sodipodi:role="line"
+ id="tspan4097"
+ x="311.09598"
+ y="440.79865"
+ style="fill:#989898;fill-opacity:1">7 8</tspan></text>
+ <text
+ xml:space="preserve"
+ style="font-size:16px;font-style:normal;font-weight:normal;line-height:125%;letter-spacing:0px;word-spacing:0px;fill:#000000;fill-opacity:1;stroke:none;font-family:Sans"
+ x="436.45312"
+ y="440.79865"
+ id="text4099"
+ sodipodi:linespacing="125%"><tspan
+ sodipodi:role="line"
+ id="tspan4101"
+ x="436.45312"
+ y="440.79865"
+ style="fill:#989898;fill-opacity:1">F 8</tspan></text>
</g>
</svg>
diff --git a/vorlagen/thesis/src/kapitel_x.tex b/vorlagen/thesis/src/kapitel_x.tex
index 7720ce2..01a72c8 100644
--- a/vorlagen/thesis/src/kapitel_x.tex
+++ b/vorlagen/thesis/src/kapitel_x.tex
@@ -81,7 +81,7 @@ BTS has a unique identifier code name and hence can be distinguished from other
\begin{figure}[ht!]
\centering
\includegraphics[scale=0.70]{img/CellID.pdf}
- \caption[]{Cell-ID position estimation technique where a mobile user can be connected to only one BTS.}
+ \caption{Cell-ID position estimation technique where a mobile user can be connected to only one BTS.}
\label{img:cellid}
\end{figure}
@@ -90,14 +90,14 @@ can be achieved than the known shape of signal reception \citep[Chapter 8]{04700
\textit{timing advance} (TA) value is known. The TA is the rough prediction of the \textit{round trip time} (RTT), time
required for a data packet to be received and acknowleded by the MS. Using this measure a rough circle can be made between
the BTS and the bordering points of the Cell-ID region since TA multiplied with speed of light produces the radius distance
-of the circle. To get the TA value a connection between the MS and the BTS has to exist or a silent call can be made
+of the circle. To obtain the TA value a connection between the MS and the BTS has to exist or a silent call can be made
where the GSM subscriber does not even notice that he/she is being called since there is no ringing
or any other sign that an idle connection is being performed on the MS \citep[Chapter 4]{3GPPTS03.71}.
If there are more antennas than one, then it can be even further specified where the MS is positioned.
This can be still inaccurate because of the multipath signal reflections.
In urban environments it is usually the case that there is no optical line of sight between the BTS and MS,
-so while the signal propagates from the BTS to the MS and vice versa it gets reflected from multiple buildings
-or other objects which adds extra time (extra range to the distance). The accuracy of this method is typically
+so while the signal propagates from the BTS to the MS and vice versa it may get reflected from multiple buildings
+or other objects which add extra propagation time (extra range to the distance). The accuracy of this method is typically
in a range of 200 m \citep{Zeimpekis}.
This method can be seen both as a handset and network based position
estimation technique, due to the fact that the user may run his/her own application on the cell phone or it can be applied by
@@ -113,7 +113,7 @@ are used to determine if the handover process should be triggered or not \citep{
\begin{figure}[ht!]
\centering
\includegraphics[scale=0.50]{img/RSS.pdf}
- \caption[]{Basic idea of the RSS estimation technique. One rectangle location is represented by two
+ \caption{Basic idea of the RSS estimation technique. One rectangle location is represented by two
RSS measurements for two BTS, blue is BTS1 and red is BTS2.}
\label{img:rssLoc}
\end{figure}
@@ -153,7 +153,7 @@ the absolute location of the BTS's. The basic idea can be seen in figure \ref{im
\begin{figure}[ht!]
\centering
\includegraphics[scale=1.20]{img/EOTD.pdf}
- \caption[]{Basic idea of the E-OTD positioning technique. Current time information
+ \caption{Basic idea of the E-OTD positioning technique. Current time information
are transmitted from 3 different BTS's at the same time.Then the MS observes the difference of time when
the information arrive and using trilateration technique calculates the relative position of
the MS.}
@@ -195,7 +195,7 @@ The power of received signals on a GPS receiver is in the range
of 100 attowatts\footnote{1 attowatt = $10^{-16} W$.
The reception quality depends on the receiver antenna and RF front-end part as well.}
when the GPS receiver is outdoors on open sky,
-the signal strength gets even smaller by a factor of 10-1000 if the user is
+the signal strength becomes even smaller by a factor of 10-1000 if the user is
between tall buildings or indoors \citep[Chapter 2]{diggelen2009a-gps}. All these given factors
affect the acquisition of GPS signals and make the correct reception of GPS signals unrealisable
and impractical.
@@ -219,7 +219,7 @@ In this section, two more techniques will be briefly described, angle of arrival
\begin{figure}[ht!]
\centering
\includegraphics[scale=1.20]{img/AOA.pdf}
- \caption[]{Basic idea of the Angle of Arrival positioning technique. The angle of the reception signal
+ \caption{Basic idea of the Angle of Arrival positioning technique. The angle of the reception signal
on the BTS antenna is measured. By knowing at least two angles on two BTS's, it is possible to
interpolate the intersection point where the MS is located.}
\label{img:aoadLoc}
@@ -237,7 +237,7 @@ position estimation techniques.
\begin{figure}[ht!]
\centering
\includegraphics[scale=0.50]{img/WiFiTag.pdf}
- \caption[]{Wireless Access Point tagging. The MS could be located anywhere where all three access points
+ \caption{Wireless Access Point tagging. The MS could be located anywhere where all three access points
are visible, this area has a wavy background and is between access points 1, 2 and 4.}
\label{img:WiFiTag}
\end{figure}
@@ -319,7 +319,7 @@ In the last part of this thesis, test results are reported and summary of the en
\begin{figure}[ht!]
\centering
\includegraphics[scale=0.38]{img/satelliteRanges.pdf}
- \caption[]{GPS Simple working principle, a) example in 3D space with spheres b) example in 2D space with circles.}
+ \caption{GPS Simple working principle, a) example in 3D space with spheres b) example in 2D space with circles.}
\label{img:GPSSimplePrinciple}
\end{figure}
In the new global economy age, GPS positioning has become of important value for various services
@@ -374,7 +374,7 @@ user's position.
\begin{figure}[ht!]
\centering
\includegraphics[scale=0.60]{img/NAV-Message.pdf}
- \caption[]{One frame of 1500 bits on L1 frequency carrier}
+ \caption{One frame of 1500 bits on L1 frequency carrier}
\label{img:gpsframe}
\end{figure}
Each subframe can be divided into three fields of data,
@@ -403,7 +403,7 @@ change in the transmitted 25 frames beside the system time stamp \citep{GPS-Guid
\begin{figure}[ht!]
\centering
\includegraphics[scale=0.50]{img/GPSSubframe.pdf}
- \caption[]{Subframes always start with telemetry and handover words}
+ \caption{Subframes always start with telemetry and handover words}
\label{img:gpssubframe}
\end{figure}
Fourth and fifth subframes include \textit{almanac data}, low-precision clock corrections,
@@ -443,7 +443,7 @@ of L1 will be discussed and analysed seperately in section \ref{sec:Carrierdemod
\begin{figure}[ht!]
\centering
\includegraphics[scale=0.50]{img/BPSKModulation.pdf}
- \caption[]{BPSK Modulation - First signal is the carrier wave,
+ \caption{BPSK Modulation - First signal is the carrier wave,
and it is multiplied (mixed) with the second signal, which are
the data to be transmitted. The resulting signal at the output
of the satellite antenna is the third one.}
@@ -479,7 +479,7 @@ $(1500 \, \mathrm{bits per frame}\, \cdot \, 25 \, \mathrm{frames}) / (50 \,\mat
\begin{figure}[ht!]
\centering
\includegraphics[scale=0.50]{img/GPS-Modulation.pdf}
- \caption[]{Modulation of the GPS signal L1}
+ \caption{Modulation of the GPS signal L1}
\label{img:gpsmod}
\end{figure}
@@ -654,14 +654,14 @@ such that $\Delta \varphi \approx 0$, a phase shift is shown in figure \ref{img:
\begin{figure}[ht!]
\centering
\includegraphics[scale=0.5]{img/Phase-Diff.pdf}
- \caption[]{Two equivalent carrier waves with the same frequency but different phase shift}
+ \caption{Two equivalent carrier waves with the same frequency but different phase shift}
\label{img:phaseShift}
\end{figure}
\begin{figure}[ht!]
\centering
\includegraphics[scale=0.5]{img/L1-Demodulation.pdf}
- \caption[]{Demodulation of the L1 GPS signal}
+ \caption{Demodulation of the L1 GPS signal}
\label{img:L1Demod}
\end{figure}
@@ -736,7 +736,7 @@ in figure \ref{img:multCAPhase}.
\begin{figure}[ht!]
\centering
\includegraphics[scale=0.5]{img/PRN-PhaseShiftAfterDemod.pdf}
- \caption[]{Effects of the low frequency term on the demodulated output
+ \caption{Effects of the low frequency term on the demodulated output
C/A wave on the GPS receiver (the explanations and figures are from top to bottom).
If the synthesized frequency is correct, $f_{1}=f_{2}$, the low
frequency term becomes a DC term and does not modify the output
@@ -769,7 +769,7 @@ section \ref{sec:Carrierdemod}.
\begin{figure}[ht!]
\centering
\includegraphics[scale=0.50]{img/PRN-ChipRate.pdf}
- \caption[]{Comparison between the original C/A code generated on the
+ \caption{Comparison between the original C/A code generated on the
GPS satellite with two synthesized PRN codes with a different phase shift on the receiver.}
\label{img:prnCodeCompare}
\end{figure}
@@ -812,7 +812,7 @@ $+5=(+1)\cdot(+1)+(-1)\cdot(-1)+(+1)\cdot(+1)+(+1)\cdot(+1)+(-1)\cdot(-1)$.
\begin{figure}[ht!]
\centering
\includegraphics[scale=0.50]{img/Correlation.pdf}
- \caption[]{Cross-correlation on three different signals}
+ \caption{Cross-correlation on three different signals}
\label{img:correlatingSignals}
\end{figure}
The same principle applies to the transmitted C/A and
@@ -898,7 +898,7 @@ unknown frequency to be in range of $10 \, \mathrm{kHz}-25 \, \mathrm{kHz}$.
\begin{figure}[ht!]
\centering
\includegraphics[scale=0.70]{img/2D-SearchSpaceInk.pdf}
- \caption[]{Segment of the frequency/code delay search space for a single GPS satellite}
+ \caption{Segment of the frequency/code delay search space for a single GPS satellite}
\label{img:prnSearchSpace3d}
\end{figure}
@@ -909,7 +909,7 @@ The frequency search bin (band) size is a function of the desired peak magnitude
due to the frequency mismatch and integration time period. Larger frequency
bands mean a smaller number of bins to search but
a greater correlation peak magnitude loss, i.e. with larger frequency bands
-it gets harder to identify the correlation peaks described in sections \ref{sec:gpsDataAndSignal} and \ref{sec:CAdemod}.
+it becomes harder to identify the correlation peaks described in sections \ref{sec:gpsDataAndSignal} and \ref{sec:CAdemod}.
The frequency search bin size can be
estimated using the frequency
mimsmatch loss \textit{sinc} function given in equation \eqref{eq:mistunigLoss} \citep{implSoftGPSRec},
@@ -959,7 +959,7 @@ in figure \ref{img:SearchSpace2d}.
\begin{figure}[ht!]
\centering
\includegraphics[scale=0.50]{img/2DSearchSpace.pdf}
- \caption[]{The total search space}
+ \caption{The total search space}
\label{img:SearchSpace2d}
\end{figure}
@@ -975,7 +975,7 @@ first time the GPS receiver is turned on. It is known under the name of cold sta
\begin{figure}[ht!]
\centering
\includegraphics[scale=0.50]{img/frequencySearch.pdf}
- \caption[]{Idea of the frequency searching algorithm}
+ \caption{Idea of the frequency searching algorithm}
\label{img:freqSearch}
\end{figure}
@@ -1010,7 +1010,7 @@ known location.
\begin{figure}[ht!]
\centering
\includegraphics[scale=0.50]{img/Localization.pdf}
- \caption[]{Basic distance estimation principle for one satellite}
+ \caption{Basic distance estimation principle for one satellite}
\label{img:SatLocalization}
\end{figure}
In figure \ref{img:SatLocalization}, an example concept can be seen, where $\vec{u}=(x_u,y_u,z_u)$ represents the unknown
@@ -1036,7 +1036,7 @@ geometric distance $r$ is computed, as given in equation \eqref{eq:rDist}.
\begin{figure}[ht!]
\centering
\includegraphics[scale=0.50]{img/TimingLoc.pdf}
- \caption[]{Estimating the distance by phase shift $\Delta t =t_2 - t_1 =\tau$}
+ \caption{Estimating the distance by phase shift $\Delta t =t_2 - t_1 =\tau$}
\label{img:TimingLoc}
\end{figure}
\begin{equation}
@@ -1146,7 +1146,7 @@ f(x) = \sum_{n=0}^{\infty}\frac{f^{(n)}(a)}{n!}(x-a)^n = f(a) + \frac{f'(a)}{1!}
\begin{figure}[ht!]
\centering
\includegraphics[scale=0.50]{img/TaylorSeries.pdf}
- \caption[]{Taylor series approximation for a point $a=0.5$ where $n$ is the Taylor polynomial degree.}
+ \caption{Taylor series approximation for a point $a=0.5$ where $n$ is the Taylor polynomial degree.}
\label{img:taylorSeries}
\end{figure}
Due to the four unknown terms, Taylor series for multivariables
@@ -1303,7 +1303,7 @@ approximate location, satellite health as well as clock corrections, ionospheric
\begin{figure}[ht!]
\centering
\includegraphics[scale=0.50]{img/A-GPS.pdf}
- \caption[]{Basic AGPS principle}
+ \caption{Basic AGPS principle}
\label{img:agpsPrinciple}
\end{figure}
@@ -1337,11 +1337,12 @@ Consequently, this feasible region will shrink until the location has been fully
\item Pseudoranges are calculated for each visible satellite $SV_i$.
\item Trilaterate the position out of the pseudoranges $\rho_i$.
\end{enumerate}
-Although the AGPS algorithms can be seen as a set of equations, with more unknowns terms known it is
-straightforward to solve the set of equations. However, with more of the unknown terms it takes more
-time to get (decode) them from the satellite messages. One should know various AGPS algorithms exist,
-some do not require the exact time component and navigation data to be present in the assistance data
-\citep{998892}.
+Although the AGPS algorithms can be seen as a set of equations with more unknown terms being known. It is
+straightforward to solve a set of equations when all the terms are known. However, without assistance information
+which provide additional information to the GPS receiver,
+it takes more time to obtain (decode) assistance data from the satellite message.
+Numerous AGPS algorithms exist, some do not require the exact time component and navigation data to
+be present in the assistance data \citep{998892}.
\section{Error estimation}
@@ -1358,7 +1359,7 @@ some do not require the exact time component and navigation data to be present i
\chapter{GSM}
\chapter{Radio Resource Location Protocol}
This chapter will focus on the Radio Resource Location Protocol (RRLP) and a description
-how it works inside of the GSM will be given. RRLP is a protocol from the family of Location Services (LCS)
+how it works inside of the GSM network will be given. RRLP is a protocol from the family of Location Services (LCS)
which were not part of the initial GSM standard. It is a widely used protocol in other cellular
networks like UMTS, it was later introduced to the GSM system as well \citep{3GPPTS03.71}. It was
developed by the request of government and rescue organizations to fulfill the wireless enhanced 911
@@ -1368,18 +1369,18 @@ within 100 m in 67\% of cases \citep{E911Accuracy}.
The standard supports three positioning mechanisms: E-OTD, UL-TDOA and AGPS \citep{3GPPTS03.71}.
The LCS process can be divided into two seperate stages, signal measurements and
position estimation from the derived data in the previous stage. In this chapter
-the description will be given how to make an RRLP request, how to send assistance
+the description will be given on how to make an RRLP request, how to send assistance
data and then more information will be given on its response.
\newpage
\section{RRLP Request}
In this section the RRLP protocol and its request will be reviewed in more detail.
RRLP represents the connection/protocol between the Serving Mobile Location Center (SMLC)
-and the standalone handset, in this case the MS, in GSM networks \citep[Chapter 5]{harper2010server-side}.
+and the standalone handset, in this case the MS \citep[Chapter 5]{harper2010server-side}.
The SMLC node contains the functionaly to support
location services for the GSM network \citep{3GPPTS03.71}. SMLCs primary function is to manage
the overall coordination and scheduling of resources required to perform the localization of the MS
-and it is located on the Base Station Controller (BSC).\citep{3GPPTS03.71}.
+and it is located on the Base Station Controller (BSC) \citep{3GPPTS03.71}.
SMLC controls the LMU's as well but since in this work no LMU were available this part
will be skipped as well as the description of E-OTD and UL-TDOA localization.
@@ -1392,42 +1393,44 @@ connected to the GSM network.}.
\begin{figure}[ht!]
\centering
\includegraphics[scale=0.50]{img/RRLPRequest.pdf}
- \caption[]{RRLP Request protocol. Assistance data can be sent before the request is made. If the assistance
+ \caption{RRLP Request protocol. Assistance data can be sent before the request is made. If the assistance
data are sent, their reception acknowledgement is sent as a response from the MS.}
\label{img:RRLPReqProt}
\end{figure}
-Data/packets sent inside of a protocol is called Protocol Data Unit (PDU) and on different
-layer levels they may take a different shape \citep{kozierok2005the} \citep{stevens1994tcp/ip}.
+Data sent inside of a protocol are called Protocol Data Unit (PDU). On different
+layer levels PDU's may take a different shape and size because of the encapsulation or splitting \citep{kozierok2005the} \citep{stevens1994tcp/ip}.
In RRLP, the PDU's sent from the SMLC ought to be not greater than 244 bytes\footnote{Bytes of 8 bits!},
although the standard defines that larger packets will be split in lower layers, in this work the
rule of 244 bytes has been obeyed and each PDU packet is not greater
than 211 bytes \citep{04.31V8.18.0}. In the RRLP standard terms, the messages are entitled
as \textit{components} and fields in the messages (components) are labelled as \textit{information elements} (IE) \citep{04.31V8.18.0}.
The SMLC may send only the request for the position of the MS or it may assist the MS with assistance data
-required to estimate the position (in case of a AGPS request, these data may be ephemeris, almanac or
-accurate timing data), as depicted in figure \ref{img:RRLPReqProt}. Once the MS gets the data delivered after some
-processing time it will respond to the SMLC with the position of the MS or with an error IE indicating what
-assistance data are missing \citep{04.31V8.18.0} \citep{49.031V8.1.0}. In the IE it is exactly indicated
-what type of data ought to be sent to the MS so that it can complete the RRLP request and respond its
+required to estimate the position (in case of an AGPS request, these data may be ephemeris, almanac,
+accurate timing data and similar data that help to estimate the position in a shorter period of time).
+The RRLP protocol is shown in figure \ref{img:RRLPReqProt}. Dashed lines represent optionally transmitted data
+like assistance data according to which an acknowledgement or error will be produced. Once the MS obtains the RRLP request,
+after a period of processing time it will respond to the SMLC with the position of the MS or with an error IE indicating what
+assistance data are missing or why it can not return the position \citep{04.31V8.18.0} \citep{49.031V8.1.0}. In the response component IE it is exactly indicated
+what type of data ought to be sent to the MS so it can complete the RRLP request and give back its
position. To save bandwidth space in the communication between the SMLC and MS, it can be proceeded in such a manner that
first the RRLP request is sent out for the position estimation and then if the MS requires some of the assistance data,
it will send a request for those data back to the SMLC and then the SMLC can send the required data and expect an
successful response from the MS. However, in this work the author had a different approach in that sense, that first
-he sent all the RRLP assistance data and then the RRLP position request. This way, sending all assistance data,
-was choosen over the other because in the OpenBSC it was not possible to access directly the response
-data without querying the database directly. Since this system is a real time system, waiting for the database
-to respond may have corrupted the state machine of the GSM network and this would led to the malfunction and
-eventually failure of the complete network!
+all the RRLP assistance data were sent and then the RRLP position request. This way, sending all assistance data,
+was choosen over the other idea of waiting for the MS response because in OpenBSC it was not possible to access
+directly the response data without querying the database directly. Since this system is a real time system,
+waiting for the database to respond may have corrupted the state machine of the GSM network and this would
+led to the malfunction and eventually failure of the complete network!
The structure of the RRLP messages (requests, assistance data and response) is well defined using
-Abstract Syntax Notation One (ASN.1) in the technical specifications 3GPP 04.31 V8.18.0
+Abstract Syntax Notation One (ASN.1) in the technical specifications 3GPP 04.31
and ETSI TS 144 031 \citep{49.031V8.1.0} \citep{ETSITS144031}. ASN.1 is a conventional notation
for denoting the abstract syntax of data used inside of protocols or data
structures \citep[Chapter 8]{sharp2008principles} \citep{ITU-TX.680}. In other words, using ASN.1 it is possible
to describe data in an indepedent representation of programming languages in which a protocol is implemented.
-In this section, only some of the used parts of the RRLP protocol
-inside of this thesis will be presented, more details can be found in the
+In this section, only some of the mostly important and used parts of the RRLP protocol
+inside of the thesis will be presented, more details can be found in the
technical specifications \citep{49.031V8.1.0} \citep{ETSITS144031}. Structure
of the RRLP message encoding for transmission can be seen in listing \ref{lst:RRLP}.
Further details on some of the unknown terms are given in listings
@@ -1439,7 +1442,12 @@ notation \citep{ITU-TX.691}.
\begin{lstlisting}[label=lst:RRLP,
caption={\textbf{Structure of the RRLP message in ASN.1}},
backgroundcolor=\color{light-gray},
-basicstyle={\scriptsize\ttfamily}]
+basicstyle={\scriptsize\ttfamily},
+escapechar=@,
+emph={},
+emphstyle=\color{crvena},
+emph={[2]},
+emphstyle={[2]\color{plava}}]
RRLP-Messages
-- { RRLP-messages }
@@ -1454,12 +1462,12 @@ FROM
;
PDU ::= SEQUENCE {
- referenceNumber INTEGER (0..7),
- component RRLP-Component
+ @\textcolor{red}{referenceNumber INTEGER (0..7),}@
+ @\textcolor{blue}{component RRLP-Component}@
}
RRLP-Component ::= CHOICE {
- msrPositionReq MsrPosition-Req,
+ @\textcolor{narandzasta}{msrPositionReq MsrPosition-Req,}@
msrPositionRsp MsrPosition-Rsp,
assistanceData AssistanceData,
assistanceDataAck NULL,
@@ -1492,12 +1500,13 @@ PER is intended for use in circumstances where
minimizing the size of the representation of values is the major concern
in the choice of encoding rules \citep{ITU-TX.691}. In other words, it compresses the data
in the PDU packets by limiting the bit field length to the minimal amount of
-bits required to define the minimal and maximal values defined in the standard.
+bits required to define the minimal and maximal variable values defined in the standard.
There are two variations of PER,
aligned and nonaligned \citep{ITU-TX.691}. In the RRLP protocol the nonaligned type of PER
is used. The major difference between aligned and nonaligned PER lies in the fact that some
data structures are aligned on octet boundaries in aligned PER, i.e.
-there are some wasted padding bits which are set to zero if not used.
+there are some wasted padding bits which are set to zero if not used according to the size of the
+packets.
Before proceeding with an example, summary for the used ASN.1 type
elements will be provided otherwise it is not possible to proceed with an example
@@ -1512,31 +1521,32 @@ component types'' \citep{ITU-TX.691}, i.e. only one element is selected from the
list and the elements of the list are defined according to their variable type.
Variables of type \textbf{ENUMERATED} are ``simple types whose values are given
distinct identifiers as part of the type notation'' \citep{ITU-TX.691}, these types
-are used to distinguish a choice by identifying it with an incremented number where the
-first element is of value zero. Veriables defined by \textbf{INTEGER} are of the ``simple
+are used to distinguish a choice by identifying it with an incremented number from the previous
+element where the
+first element is of value zero. Variables defined by \textbf{INTEGER} are of the ``simple
type with distinguished values which are the positive and negative whole numbers,
including zero (as a single value)'' \citep{ITU-TX.691}.
-At this point the meaning of RRLP data elements will be given. To construct an RRLP PDU sequence
-these fields need to be known: \textit{referenceNumber} and \textit{RRLP-Component}.
-\textbf{referenceNumber}
+At this point the meaning of RRLP data elements colored in red, blue and orange from listing \ref{lst:RRLP} will be given.
+To construct an RRLP PDU sequence (packet) these fields need to be known: \textit{referenceNumber}
+and \textit{RRLP-Component}. \textbf{referenceNumber}
specifies the reference number of the request and is used for the purpose of identifying
the response from the MS. It can take any value between 0 and 7, in
-PER enocoding this requires at least three bits representation since with three bits
+PER enocoding this requires at least a three bit representation since with three bits,
eight different values can be represented ($2^3=8$). \textbf{component} is of the type RRLP-Component,
-which is a list of type CHOICE. RRLP-Component is used for defining what type of information the
+which is a CHOICE list. RRLP-Component is used for defining what type of information the
packet will include (assistance data, request, response, error, etc.). For this particular example
-one chooses \textbf{msrPositionReq} that is of type MsrPosition-Req, with this the MS will know
-that its position is requested. MsrPosition-Req is of type SEQUENCE,
-consisting out of one mandatory and few optional IE. One choice will be only considered,
+one chooses \textbf{msrPositionReq} that is of type MsrPosition-Req (colored in orange in listing \ref{lst:RRLP}),
+with this information the MS will know that its position is requested. MsrPosition-Req is a SEQUENCE,
+consisting out of one mandatory and few optional IE elements. One choice will be only considered,
\textbf{PositionInstruct}, the rest is used later for the assistance data and what
type of information is included inside of the PDU message. \textbf{PositionInstruct} consists
of five elements but four are mandatory: \textit{methodType}, \textit{positionMethod},
\textit{measureResponseTime} and \textit{useMultipleSets}. These four elements are the most
-compact representation of an inquiry for the MS to know what kind of position measurement to
-do, how long (time duration) it is allowed to measure the position and what type of
-response to send back.
-
+compact representation of an inquiry for the MS to differentiate between all the possible
+position measurements it could perform, how long (time duration) it is allowed to measure
+the position and how many positions it should perform and return in its response.
+\newpage
\textbf{methodType} defines where the position estimation calculation ought to be executed,
will it take place solely on the MS (\textit{msBased}), solely on the server\footnote{With server
the BTS location is ment!} (\textit{msAssisted}),
@@ -1590,43 +1600,47 @@ UseMultipleSets ::= ENUMERATED {
oneSet (1) -- sending of multiple is not allowed
}
\end{lstlisting}
-
\begin{equation}
\label{eq:uncerAccuracy}
r=10((1.1)^{K}-1)
\end{equation}
\begin{equation}
\label{eq:responseTime}
-MeasureResponseTime=\frac{ln(N)}{ln(2)}
+MeasureResponseTimeBitValue=\frac{ln(N)}{ln(2)}
\end{equation}
\newpage
This uncertainty of the accuracy, is an integer
-number, that defines how certain the accuracy of the returned position is. It can be calculated
+number, that defines how certain the accuracy of the returned position ought to be. It can be calculated
using the equation \eqref{eq:uncerAccuracy}, where $K$ is the seven bit integer number
and $r$ is the accuracy uncertainty in meters \citep{3gppequations}. The next three parameters
-to be defined are the position estimation method (GPS, E-OTD or one of the two prefered by the MS),
+to be defined are the position estimation technique (GPS, E-OTD or one of the two prefered by the MS),
the position measurement time and how many measurements the MS ought to report back to SMLC.
Since in this thesis the author exploits the AGPS method, GPS is choosen for \textbf{PositionMethod}.
\textbf{MeasureResponseTime} is a three bit integer value that corresponds to the time the MS is allowed
-to take to send a respond back to SMLC. It can be calculated using the equation
+to perform the position estimation and to send a respose back to SMLC. Otherwise, if it takes longer the MS
+than the specified time period, it will disconnect the SDDCH channel without responding back.
+It can be calculated using the equation
given in \eqref{eq:responseTime}, where $N$ is the number of seconds the MS is allowed to perform the
position estimation.
After the ASN.1 parameters of an RRLP request have been understood, they can be
choosen and set according to the position measurement request which the network operator wants to perform.
-In the next step the RRLP request can be constructed and encoded using PER. This process can be seen as
-as a concatenation of binary digits. To construct the RRLP request query from the above
-given ASN.1 specifications is straightforward. A simple
-RRLP request in PER encoded form is shown in figure \ref{img:RRLPReqExplained}, more
-details can be seen in listing \ref{lst:RRLPReqPER}. After the concationation it can be converted to the
+In the next step the RRLP request can be constructed and encoded using PER. To construct the RRLP request
+query from the above given ASN.1 specifications is straightforward. The choosen values are only concatenated
+into a binary string. A simple
+RRLP request in PER encoded form is shown in figure \ref{img:RRLPReqExplained} and the previous conversion
+process might become more clear, different variables have been colored with distinguishable colors to its neighbor
+variables so that it is easy to recognize different variables. The five red zeros define what type of data
+will be included in the current RRLP packet. This becomes more understandable by looking at the listing \ref{lst:RRLPReqPER}.
+After the concationation it can be converted to the
desired notation system (binary, hexadecimal, etc.). In this particular example the RRLP request to be sent
-using the RRLP protocol in hexadecimal notation is: \textit{x400178F8}. This message is transmitted to the MS
+using the RRLP protocol in hexadecimal notation is: \textbf{400178F8}. This message is transmitted to the MS
via the opened SDDCH channel. However, before sending this request the assistance data can be sent. In the
folowing section \ref{sec:rrlpassistance} more details of how assistance data are sent will be presented.
\begin{figure}[ht!]
\centering
\includegraphics[scale=0.80]{img/RRLPReqExplained.pdf}
- \caption[]{An example RRLP request. Constructing a binary RRLP request in PER from ASN.1. Yellow zero bits
+ \caption{An example RRLP request. Constructing a binary RRLP request in PER from ASN.1. Yellow zero bits
are extension markers or spare bits. }
\label{img:RRLPReqExplained}
\end{figure}
@@ -1673,7 +1687,7 @@ If the assistance data are present, the response time ought to be shorter since
the AGPS receiver knows the orbital information of the satellites and the exact time
which allows the AGPS to find immediatelly the Doppler frequency and phase shift of
the visible GPS satellite. In the assistance data packets, same as in the request
-packet, one has to specify what type of information are included in the assistance data.
+packet, one has to specify what type of assistance information are included in the RRLP assistance packets.
In this thesis, as assistance data only the almanac, ephemeris, UTC model, ionospheric
model and reference location are transmitted to the MS. There are also other assistance
data like differential GPS corrections (DGPS), real time integrity, acquisition assistance
@@ -1701,8 +1715,8 @@ required for methods like E-OTD) \citep[Chapter 4]{harper2010server-side}. Acqui
data, as the name itself says provides the AGPS receiver directly with acquisition data. Acquisition data
are the Doppler frequencies and phase shift precalculated on the BTS for the MS. If this type of data is
provided to the AGPS receiver, it does not require to compute and search for the given data from the provided time
-on its on \citep[Chapter 4]{harper2010server-side}. This would speed up even more the process of getting a
-position and would help weak signals to be better detected.
+on its on \citep[Chapter 4]{harper2010server-side}. This would speed up the process of getting a
+position and would help weak signals to be detected which in return would minimize the reception errors.
More information on the assistance data transmitted within the RRLP protocol
in this work will be presented here. As listed above,
@@ -1710,13 +1724,13 @@ almanac, ephemeris, UTC model, ionospheric model and reference location are tran
location is the location of the BTS and provides the MS with an approximate location which can be used
for the position determination in equations given in section \ref{sec:distanceAndPosition}.
Furthermore, this limits the search space in time and frequency domain for satellites
-to lock on, since the AGPS receiver knows it can not expect to see satellites
+to lock on, since if the AGPS receiver has access to these data it can not expect to see satellites
which send signals on the opposite side of the Earth \citep[Chapter 4]{harper2010server-side}.
With the reference location, one sends also the altitude and uncertainty of the included location
data so that the AGPS receiver inside the MS can determine and limit the time and frequency search space even further.
The ionospheric model includes data for correcting errors introduced by the radio wave transmission through
-the inosphere \citep[Chapter 4]{harper2010server-side}. These data are not satellite dependent therefore they
-are not sent for each satellite seperately, but once and they are valid for
+the ionosphere \citep[Chapter 4]{harper2010server-side}. These data are not satellite dependent therefore they
+are not sent for each satellite seperately but once and they are valid for
all satellites \citep[Chapter 4]{harper2010server-side}. Navigation data in RRLP terminology are the ephemeris data.
The transmitted assistance data can be seen in the following tables \ref{tbl:utcModel}, \ref{tbl:navMessage},
\ref{tbl:almanacMessage} and \ref{tbl:ionoModel}, on the following pages \pageref{tbl:utcModel},
@@ -1725,7 +1739,7 @@ data are encoded will be given in the implementation chapter, chapter \ref{Imple
The packets are constructed in the same manner as RRLP requests with a slight difference of selecting
different RRLP components and including assistance data. In this particular example,
-only a packet with the reference location will be presented, a ``complete'' 211 bytes PDU packet constructed by authors
+only a packet with the reference location will be presented, a ``complete'' 211 bytes PDU packet constructed by author's
software would require at least four pages to be shown. Instead of RRLP request (\textit{msrPositionReq})
in \textbf{RRLP-Component} one has to choose assistance data (\textit{assistanceData}) (for the purpose
of better understanding in this listening different colors have been used,
@@ -1737,8 +1751,8 @@ specified in the RRLP standard for GPS assistance data, listing \ref{lst:GPSAssi
ionospheric model, UTC model, almanac, acquisition assistance and real time integrity (all colored blue in
listing \ref{lst:RRLPAssisPER}). The assistance data one
wants to include in the RRLP packet have to be selected previously.
-Selecting is straightforward and one only is required to be set
-the appropriate bit to one (1). Since in this example only the reference
+Selecting is straightforward and one only is required to set
+the appropriate bit to one (1=included in the packet, 0=not included in the packet). Since in this example only the reference
location is transmitted inside the RRLP PDU packet, the \textit{refLocation}
bit is set to one. Once the variables have been set, the assistance data
have to follow the given order as in listing \ref{lst:GPSAssisData}.
@@ -1779,19 +1793,19 @@ of the BTS between the major axis and North pole in degrees. These terms are dep
\ref{img:earthElipsoid} by showing the World Geodetic System 1984 (WGS84). The latitude,
longitude and altitude need to be encoded into a format recognized by the RRLP standard. This is
straightforward and can be proceeded using the equations shown in \eqref{eq:latLong}, where $\varphi$
-is the latitude and $\lambda$ is the longitude value.
+is the latitude and $\lambda$ is the longitude value in decimal degrees.
Longitude is encoded as second compliment binary number \citep{3gppequations}.
\begin{figure}[ht!]
\centering
\includegraphics[scale=0.5]{img/ElipsoidPoint.pdf}
- \caption[]{Reference location is a 14 octet stream built according to the given rule as
+ \caption{Reference location is a 14 octet stream built according to the given rule as
specified in the standard \citep{3gppequations} under section \textit{7.3.6}.}
\label{img:refLocStandard}
\end{figure}
\begin{figure}[ht!]
\centering
\includegraphics[scale=0.5]{img/EarthElipsoid.pdf}
- \caption[]{World Geodetic System 1984}
+ \caption{World Geodetic System 1984}
\label{img:earthElipsoid}
\end{figure}
The altitude is encoded as it is where one bit increments represent one meter incerements.
@@ -1816,9 +1830,13 @@ reference location. There are other reference location standards inside of the R
This way the RRLP protocol knows where the data end and where new data may start if they are included.
What type of reference location is include is defined by the first four bits of the reference location,
in this case it is $1001$, as it can be seen in figure \ref{img:refLocStandard}. This is an additional
-mechanism for error control, if the numbers do not fit when the transmitted binary data have been decoded
+mechanism for error control, if the numbers do not match when the transmitted binary data have been decoded
then the MS can return an error and ask for retransmission of the data. Information related to the reference
-location in the example listing \ref{lst:RRLPAssisPER} are colored in orange. In the next section more
+location in the example listing \ref{lst:RRLPAssisPER} are colored in orange. Once the assistance data
+have been transmitted to the MS, it will respond back with an acknowledgement or error depending if the
+data were correctly received and parsed by the MS. The acknowledgement will have the same reference number
+as the assistance packet. This can be seen as well in figure \ref{img:RRLPReqProt}.
+In the next section more
details will be given on the RRLP response from the MS.
\begin{equation}
\label{eq:latLong}
@@ -1909,7 +1927,7 @@ $a_{f2}$&Apparent clock correction\\\midrule
$a_{f1}$&Apparent clock correction\\\midrule
$a_{f0}$&Apparent clock correction\\\midrule
$C_{rs}$&Ampltitude of the sine harmonic correction term to the orbit radius (meters)\\\midrule
-$\Delta n$&Mean motion difference from computed value (semicircles/sec)\\\midrule
+$\Delta n$&Mean motion difference from computed value (semicircles/second)\\\midrule
$M_{0}$&Mean anomaly at reference time (semicircles)\\\midrule
$C_{uc}$&Ampltitude of the cosine harmonic correction term to the\\
&argument of latitude (radians)\\\midrule
@@ -1928,8 +1946,8 @@ $C_{is}$&Amplitude of the cosine harmonic correction term to the angle of inclin
$i_{0}$&Inclination angle at reference time (semicircles)\\\midrule
$C_{rc}$&Amplitude of the cosine harmonic correction term to the orbit radius (meters)\\\midrule
$\omega$&Argument of perigee (semicircles)\\\midrule
-OMEGAdot&Rate of right ascension (semicircles/sec)\\\midrule
-Idot&Rate of inclination angle (semicircles/sec)
+OMEGAdot&Rate of right ascension (semicircles/second)\\\midrule
+Idot&Rate of inclination angle (semicircles/second)
\\\bottomrule
\end {tabular}
\end {table}
@@ -1996,10 +2014,10 @@ backgroundcolor=\color{light-gray},
basicstyle=\scriptsize\ttfamily,
escapechar=@,
emph={gps-AssistData},
-emphstyle=\color{crvena},
+emphstyle=\color{red},
emph={[2]referenceTime,refLocation,dgpsCorrections,
navigationModel,ionosphericModel,utcModel,almanac,acquisAssist,realTimeIntegrity},
-emphstyle={[2]\color{plava}}]
+emphstyle={[2]\color{blue}}]
RRLP Message:
44 010..... referenceNumber = 2
component(RRLP-Component):
@@ -2048,8 +2066,60 @@ D9 1101....
\end{lstlisting}
\clearpage
\section{RRLP Response}
-
-
+In this section the RRLP response from the MS will be analysed. The RRLP response is
+constructed in the same manner as the RRLP request and assistance data by following
+ASN.1 rules precisely specified in the RRLP standard. RRLP response is produced by the MS itself.
+It may include the estimated position, data for estimating the position on the BTS (if MS assisted was
+choosen as the prefered method) or errors indicating that some of the
+previously mentioned assistance data are missing. Missing data and errors are
+specified inside of the RRLP response. The response data will be PER encoded and require
+to be decoded into the ASN.1 notation.
+
+\begin{lstlisting}[label=lst:RRLPRespError,
+caption={\textbf{Decoding an error RRLP response from Samsung Galaxy S3}},
+backgroundcolor=\color{light-gray},
+basicstyle=\scriptsize\ttfamily,
+escapechar=@,
+emph={gps-AssistData},
+emphstyle=\color{red},
+emph={[2]referenceTime,refLocation,dgpsCorrections,
+navigationModel,ionosphericModel,utcModel,almanac,acquisAssist,realTimeIntegrity},
+emphstyle={[2]\color{blue}}]
+ RRLP Message:
+42 010..... referenceNumber = 2
+ component(RRLP-Component):
+ ...0.... Extension of RRLP-Component = 0 :Absent
+ @\textbf{....001.}@ @\textbf{RRLP-Component}@ @\textbf{=}@ @\textbf{1}@ @\textbf{:msrPositionRsp}@
+ MsrPosition-Rsp:
+ .......0 Extension of MsrPosition-Rsp = 0 :Absent
+04 0....... multipleSets = 0 :Absent
+ .0...... referenceIdentity = 0 :Absent
+ ..0..... otd-MeasureInfo = 0 :Absent
+ ...0.... locationInfo = 0 :Absent
+ ....0... gps-MeasureInfo = 0 :Absent
+ .....1.. @\textcolor{red}{locationError = 1 :Present}@
+ ......0. extensionContainer = 0 :Absent
+ LocationError:
+ .......0 Extension of LocationError = 0 :Absent
+99 1....... additionalAssistanceData = 1 :Present
+ LocErrorReason:
+ .0...... Extension of LocErrorReason = 0 :Absent
+ ..0110.. @\textcolor{blue}{LocErrorReason = 6 :gpsAssDataMissing}@
+ AdditionalAssistanceData:
+ ......0. Extension of AdditionalAssistanceData = 0 :Absent
+ .......1 gpsAssistanceData = 1 :Present
+0B 0....... extensionContainer = 0 :Absent
+ GPSAssistanceData:
+ .000101. GPSAssistanceData length(octet) = 5 :5 + 1 = 6
+ .......1 @\textcolor{narandzasta}{GPSAssistanceData = E80000000000h}@
+D0 11010000
+00 00000000
+00 00000000
+00 00000000
+00 00000000
+00 0000000.
+ .......0 Spare Bits = 0b
+\end{lstlisting}
@@ -2110,7 +2180,7 @@ of 200 kHz \citep{nanoGSM2007brochure}. \todo{Add the Abis over IP protocol}
\begin{figure}[ht!]
\centering
\includegraphics[scale=0.50]{img/nanoBTS.jpg}
- \caption[]{nanoBTS with its plastic cover. Image courtesy of ip.access ltd}
+ \caption{nanoBTS with its plastic cover. Image courtesy of ip.access ltd}
\label{img:nanoBTSPlastic}
\end{figure}
@@ -2130,7 +2200,7 @@ port, TIB-IN and TIB-OUT. In the next paragraph a brief overview of each port wi
\begin{figure}[ht!]
\centering
\includegraphics[scale=0.15]{img/nanoBTSPorts.jpg}
- \caption[]{nanoBTS with two external antennas and five connection ports}
+ \caption{nanoBTS with two external antennas and five connection ports}
\label{img:nanoBTSPorts}
\end{figure}
@@ -2206,7 +2276,7 @@ the receiver which corresponds to the L1 civil frequencies and Coarse/Acquisitio
The GPS chipset consists of 50 channels,
each channel tracks the transmission from a single satellite \citep{understandGPS}.
It is important to note, the number of channels inside a GPS receiver interrelates
-with the amount of time required to get the first fix. Receiver tracking sensitivity is
+with the amount of time required to obtain the first fix. Receiver tracking sensitivity is
-160 dBm ($10^{-16}$ mW).
The GPS receiver communicates with the computer ovet the USB port.
Although the GPS receiver uses an USB interface, on the computer it emulates 2 UART ports,
@@ -2216,7 +2286,7 @@ which are serial communication interfaces.
\begin{figure}[ht!]
\centering
\includegraphics[scale=0.12]{img/gpsNavlock.jpg}
- \caption[]{Navilock NL-402U, opened up with the antenna and USB cable}
+ \caption{Navilock NL-402U, opened up with the antenna and USB cable}
\label{img:gpsNavilock}
\end{figure}
@@ -2235,7 +2305,7 @@ than 100 m \citep{installnanoBTS}.
\begin{figure}[ht!]
\centering
\includegraphics[scale=0.5]{img/hardwareConnection}
- \caption[]{Cable connections, showing interconnection diagram}
+ \caption{Cable connections, showing interconnection diagram}
\label{img:connectionDiagram}
\end{figure}
diff --git a/vorlagen/thesis/src/maindoc.lof b/vorlagen/thesis/src/maindoc.lof
new file mode 100644
index 0000000..bd1e075
--- /dev/null
+++ b/vorlagen/thesis/src/maindoc.lof
@@ -0,0 +1,39 @@
+\select@language {english}
+\addvspace {10\p@ }
+\contentsline {figure}{\numberline {1.1}{\ignorespaces Cell-ID position estimation technique where a mobile user can be connected to only one BTS.\relax }}{4}{figure.caption.7}
+\contentsline {figure}{\numberline {1.2}{\ignorespaces Basic idea of the RSS estimation technique. One rectangle location is represented by two RSS measurements for two BTS, blue is BTS1 and red is BTS2.\relax }}{5}{figure.caption.8}
+\contentsline {figure}{\numberline {1.3}{\ignorespaces Basic idea of the E-OTD positioning technique. Current time information are transmitted from 3 different BTS's at the same time.Then the MS observes the difference of time when the information arrive and using trilateration technique calculates the relative position of the MS.\relax }}{6}{figure.caption.9}
+\contentsline {figure}{\numberline {1.4}{\ignorespaces Basic idea of the Angle of Arrival positioning technique. The angle of the reception signal on the BTS antenna is measured. By knowing at least two angles on two BTS's, it is possible to interpolate the intersection point where the MS is located.\relax }}{8}{figure.caption.10}
+\contentsline {figure}{\numberline {1.5}{\ignorespaces Wireless Access Point tagging. The MS could be located anywhere where all three access points are visible, this area has a wavy background and is between access points 1, 2 and 4.\relax }}{9}{figure.caption.11}
+\addvspace {10\p@ }
+\contentsline {figure}{\numberline {2.1}{\ignorespaces GPS Simple working principle, a) example in 3D space with spheres b) example in 2D space with circles.\relax }}{13}{figure.caption.13}
+\contentsline {figure}{\numberline {2.2}{\ignorespaces One frame of 1500 bits on L1 frequency carrier\relax }}{15}{figure.caption.14}
+\contentsline {figure}{\numberline {2.3}{\ignorespaces Subframes always start with telemetry and handover words\relax }}{16}{figure.caption.15}
+\contentsline {figure}{\numberline {2.4}{\ignorespaces BPSK Modulation - First signal is the carrier wave, and it is multiplied (mixed) with the second signal, which are the data to be transmitted. The resulting signal at the output of the satellite antenna is the third one.\relax }}{17}{figure.caption.16}
+\contentsline {figure}{\numberline {2.5}{\ignorespaces Modulation of the GPS signal L1\relax }}{18}{figure.caption.17}
+\contentsline {figure}{\numberline {2.6}{\ignorespaces Two equivalent carrier waves with the same frequency but different phase shift\relax }}{21}{figure.caption.18}
+\contentsline {figure}{\numberline {2.7}{\ignorespaces Demodulation of the L1 GPS signal\relax }}{21}{figure.caption.19}
+\contentsline {figure}{\numberline {2.8}{\ignorespaces Effects of the low frequency term on the demodulated output C/A wave on the GPS receiver (the explanations and figures are from top to bottom). If the synthesized frequency is correct, $f_{1}=f_{2}$, the low frequency term becomes a DC term and does not modify the output $d_{C/A}$ wave (first figure). If the frequency matches but the phase not, in this case the phase is shifted for $\pi $, then $d_{C/A}$ is inverted (second figure). If the phase shifts with time, then the amplitude and phase of $d_{C/A}$ will vary as well (third figure).\relax }}{23}{figure.caption.20}
+\contentsline {figure}{\numberline {2.9}{\ignorespaces Comparison between the original C/A code generated on the GPS satellite with two synthesized PRN codes with a different phase shift on the receiver.\relax }}{24}{figure.caption.21}
+\contentsline {figure}{\numberline {2.10}{\ignorespaces Cross-correlation on three different signals\relax }}{25}{figure.caption.22}
+\contentsline {figure}{\numberline {2.11}{\ignorespaces Segment of the frequency/code delay search space for a single GPS satellite\relax }}{27}{figure.caption.23}
+\contentsline {figure}{\numberline {2.12}{\ignorespaces The total search space\relax }}{28}{figure.caption.24}
+\contentsline {figure}{\numberline {2.13}{\ignorespaces Idea of the frequency searching algorithm\relax }}{28}{figure.caption.25}
+\contentsline {figure}{\numberline {2.14}{\ignorespaces Basic distance estimation principle for one satellite\relax }}{29}{figure.caption.26}
+\contentsline {figure}{\numberline {2.15}{\ignorespaces Estimating the distance by phase shift $\Delta t =t_2 - t_1 =\tau $\relax }}{30}{figure.caption.27}
+\contentsline {figure}{\numberline {2.16}{\ignorespaces Taylor series approximation for a point $a=0.5$ where $n$ is the Taylor polynomial degree.\relax }}{32}{figure.caption.28}
+\contentsline {figure}{\numberline {2.17}{\ignorespaces Basic AGPS principle\relax }}{35}{figure.caption.29}
+\addvspace {10\p@ }
+\addvspace {10\p@ }
+\contentsline {figure}{\numberline {4.1}{\ignorespaces RRLP Request protocol. Assistance data can be sent before the request is made. If the assistance data are sent, their reception acknowledgement is sent as a response from the MS.\relax }}{40}{figure.caption.30}
+\contentsline {figure}{\numberline {4.2}{\ignorespaces An example RRLP request. Constructing a binary RRLP request in PER from ASN.1. Yellow zero bits are extension markers or spare bits. \relax }}{46}{figure.caption.31}
+\contentsline {figure}{\numberline {4.3}{\ignorespaces Reference location is a 14 octet stream built according to the given rule as specified in the standard \citep {3gppequations} under section \textit {7.3.6}.\relax }}{50}{figure.caption.32}
+\contentsline {figure}{\numberline {4.4}{\ignorespaces World Geodetic System 1984\relax }}{50}{figure.caption.33}
+\addvspace {10\p@ }
+\addvspace {10\p@ }
+\contentsline {figure}{\numberline {6.1}{\ignorespaces nanoBTS with its plastic cover. Image courtesy of ip.access ltd\relax }}{60}{figure.caption.40}
+\contentsline {figure}{\numberline {6.2}{\ignorespaces nanoBTS with two external antennas and five connection ports\relax }}{61}{figure.caption.42}
+\contentsline {figure}{\numberline {6.3}{\ignorespaces Navilock NL-402U, opened up with the antenna and USB cable\relax }}{63}{figure.caption.44}
+\contentsline {figure}{\numberline {6.4}{\ignorespaces Cable connections, showing interconnection diagram\relax }}{64}{figure.caption.45}
+\addvspace {10\p@ }
+\addvspace {10\p@ }
diff --git a/vorlagen/thesis/src/maindoc.lol b/vorlagen/thesis/src/maindoc.lol
new file mode 100644
index 0000000..f7bb90b
--- /dev/null
+++ b/vorlagen/thesis/src/maindoc.lol
@@ -0,0 +1,15 @@
+\addvspace {10\p@ }
+\addvspace {10\p@ }
+\addvspace {10\p@ }
+\addvspace {10\p@ }
+\contentsline {lstlisting}{\numberline {4.1}\textbf {Structure of the RRLP message in ASN.1}}{42}{lstlisting.4.1}
+\contentsline {lstlisting}{\numberline {4.2}\textbf {Structure of the RRLP request in ASN.1}}{42}{lstlisting.4.2}
+\contentsline {lstlisting}{\numberline {4.3}\textbf {Structure of the data types from RRLP request in ASN.1}}{44}{lstlisting.4.3}
+\contentsline {lstlisting}{\numberline {4.4}\textbf {Encoding an RRLP request from ASN.1 to PER}}{46}{lstlisting.4.4}
+\contentsline {lstlisting}{\numberline {4.5}\textbf {Structure of data types of GPS assistance data in ASN.1}}{49}{lstlisting.4.5}
+\contentsline {lstlisting}{\numberline {4.6}\textbf {Encoding reference location from ASN.1 to PER}}{54}{lstlisting.4.6}
+\addvspace {10\p@ }
+\addvspace {10\p@ }
+\addvspace {10\p@ }
+\addvspace {10\p@ }
+\contentsline {lstlisting}{[}{72}{lstlisting..-3}
diff --git a/vorlagen/thesis/src/maindoc.lot b/vorlagen/thesis/src/maindoc.lot
new file mode 100644
index 0000000..bb89d8a
--- /dev/null
+++ b/vorlagen/thesis/src/maindoc.lot
@@ -0,0 +1,17 @@
+\select@language {english}
+\addvspace {10\p@ }
+\contentsline {table}{\numberline {1.1}{\ignorespaces Overview of the localization techniques.\relax }}{10}{table.caption.12}
+\addvspace {10\p@ }
+\addvspace {10\p@ }
+\addvspace {10\p@ }
+\contentsline {table}{\numberline {4.1}{\ignorespaces GPS UTC Model content\relax }}{51}{table.caption.34}
+\contentsline {table}{\numberline {4.2}{\ignorespaces Navigation message (ephemeris) content\relax }}{52}{table.caption.35}
+\contentsline {table}{\numberline {4.3}{\ignorespaces Almanac message content\relax }}{53}{table.caption.36}
+\contentsline {table}{\numberline {4.4}{\ignorespaces GPS Ionosphere Model content\relax }}{53}{table.caption.37}
+\addvspace {10\p@ }
+\addvspace {10\p@ }
+\contentsline {table}{\numberline {6.1}{\ignorespaces Indicator LED status on the nanoBTS\relax }}{62}{table.caption.43}
+\addvspace {10\p@ }
+\addvspace {10\p@ }
+\contentsline {table}{\numberline {A.3.1}{\ignorespaces Example uncertainties (latitude and longitude) for various integer values of $K$\relax }}{77}{table.caption.51}
+\contentsline {table}{\numberline {A.3.2}{\ignorespaces Example uncertainties (altitude) for various integer values of $K$\relax }}{78}{table.caption.52}
diff --git a/vorlagen/thesis/src/maindoc.tex b/vorlagen/thesis/src/maindoc.tex
index 959ac15..d7b96f8 100644
--- a/vorlagen/thesis/src/maindoc.tex
+++ b/vorlagen/thesis/src/maindoc.tex
@@ -217,6 +217,8 @@ stepnumber=1, numbersep=5pt, numbers = none}
%%% .. %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\include{erklaerung}
\tableofcontents
+\listoftables
+\listoffigures
\cleardoublepage
\pagenumbering{arabic}