summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRefik Hadzialic2012-08-01 16:46:05 +0200
committerRefik Hadzialic2012-08-01 16:46:05 +0200
commit37ba20265a1476d7e205cba77c7fc85d89506c11 (patch)
tree7d95022ab37dcb9d89e8b2d5ba545348357886f5
parentAssistance data (diff)
downloadmalign-37ba20265a1476d7e205cba77c7fc85d89506c11.tar.gz
malign-37ba20265a1476d7e205cba77c7fc85d89506c11.tar.xz
malign-37ba20265a1476d7e205cba77c7fc85d89506c11.zip
Assistance data finished
-rw-r--r--vorlagen/thesis/maindoc.pdfbin6144285 -> 6165226 bytes
-rw-r--r--vorlagen/thesis/src/bib/literatur.bib10
-rw-r--r--vorlagen/thesis/src/kapitel_x.tex337
-rw-r--r--vorlagen/thesis/src/maindoc.tex4
4 files changed, 201 insertions, 150 deletions
diff --git a/vorlagen/thesis/maindoc.pdf b/vorlagen/thesis/maindoc.pdf
index cd791e0..b50cc16 100644
--- a/vorlagen/thesis/maindoc.pdf
+++ b/vorlagen/thesis/maindoc.pdf
Binary files differ
diff --git a/vorlagen/thesis/src/bib/literatur.bib b/vorlagen/thesis/src/bib/literatur.bib
index e3eda4e..1e3cc7a 100644
--- a/vorlagen/thesis/src/bib/literatur.bib
+++ b/vorlagen/thesis/src/bib/literatur.bib
@@ -635,4 +635,12 @@ number={2},
pages={795 -808},
keywords={100 km;Global Positioning System;dual frequency user;integrity;reference station;wide area differential GPS;Global Positioning System;error analysis;error correction;performance evaluation;wide area networks;},
doi={10.1109/7.489522},
-ISSN={0018-9251},} \ No newline at end of file
+ISSN={0018-9251},}
+
+@misc{ubxGPSDict,
+ author = "u-blox AG",
+ howpublished = "\url{http://www.u-blox.com/images/stories/the_gps_dictionary.pdf}",
+ note = "[Online; accessed 1-August-2012]",
+ title = "{The GPS Dictionary}",
+ year = "2010"
+} \ No newline at end of file
diff --git a/vorlagen/thesis/src/kapitel_x.tex b/vorlagen/thesis/src/kapitel_x.tex
index ff245df..351a0bb 100644
--- a/vorlagen/thesis/src/kapitel_x.tex
+++ b/vorlagen/thesis/src/kapitel_x.tex
@@ -256,6 +256,7 @@ table \ref{tbl:overviewLoc}.
\caption{Overview of the localization techniques.}
\label{tbl:overviewLoc}\centering
%\rowcolor{2}{light-gray}{}
+\fontfamily{iwona}\selectfont
\begin{tabular}{clccc}
\toprule
%$D$&&$P_u$&$\sigma_N$\\
@@ -1370,7 +1371,7 @@ 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
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)
@@ -1430,7 +1431,11 @@ inside of this 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
-\ref{lst:RRLPReq} and \ref{lst:RRLPReqData}.
+\ref{lst:RRLPReq} and \ref{lst:RRLPReqData}. An example how to build an RRLP request packet will be given,
+then it will be encoded using Packed Encoding Rules (PER). PER is one of the telecommunication
+standards used for encoding and decoding messages inside of protocols specified in the ASN.1
+notation \citep{ITU-TX.691}.
+\newpage
\begin{lstlisting}[label=lst:RRLP,
caption={\textbf{Structure of the RRLP message in ASN.1}},
backgroundcolor=\color{light-gray},
@@ -1465,10 +1470,6 @@ RRLP-Component ::= CHOICE {
}
END
\end{lstlisting}
-An example how to build an RRLP request packet will be given,
-then it will be encoded using Packed Encoding Rules (PER). PER is one of the telecommunication
-standards used for encoding and decoding messages inside of protocols specified in the ASN.1
-notation \citep{ITU-TX.691}.
\begin{lstlisting}[label=lst:RRLPReq,
caption={\textbf{Structure of the RRLP request in ASN.1}},
backgroundcolor=\color{light-gray},
@@ -1514,8 +1515,35 @@ distinct identifiers as part of the type notation'' \citep{ITU-TX.691}, these ty
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
type with distinguished values which are the positive and negative whole numbers,
-including zero (as a single value)'' \citep{ITU-TX.691}.
-\newpage
+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}
+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
+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
+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,
+\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.
+
+\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}),
+or one is prefered over the other depending if the MS can execute the prefered one
+(\textit{msBasedPref} or \textit{msAssistedPref}). The uncertainty of the accuracy
+of the estimated position is only optional if the choosen method is \textit{msAssisted},
+otherwise it must be included in the message.
\begin{lstlisting}[label=lst:RRLPReqData,
caption={\textbf{Structure of the data types from RRLP request in ASN.1}},
backgroundcolor=\color{light-gray},
@@ -1563,33 +1591,6 @@ UseMultipleSets ::= ENUMERATED {
}
\end{lstlisting}
-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}
-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
-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
-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,
-\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.
-
-\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}),
-or one is prefered over the other depending if the MS can execute the prefered one
-(\textit{msBasedPref} or \textit{msAssistedPref}). The uncertainty of the accuracy
-of the estimated position is only optional if the choosen method is \textit{msAssisted},
-otherwise it must be included in the message.
\begin{equation}
\label{eq:uncerAccuracy}
r=10((1.1)^{K}-1)
@@ -1598,6 +1599,7 @@ r=10((1.1)^{K}-1)
\label{eq:responseTime}
MeasureResponseTime=\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
using the equation \eqref{eq:uncerAccuracy}, where $K$ is the seven bit integer number
@@ -1663,8 +1665,8 @@ F8 1.......
\end{lstlisting}
-
-\subsection{RRLP Assistance data}
+\newpage
+\section{RRLP Assistance data}
\label{sec:rrlpassistance}
Assistance data are of the most important value when it comes to RRLP response time.
If the assistance data are present, the response time ought to be shorter since
@@ -1715,7 +1717,11 @@ data so that the AGPS receiver inside the MS can determine and limit the time an
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
-all satellites \citep[Chapter 4]{harper2010server-side}. Navigation data in RRLP terminology are the ephemeris data.
+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:ionoModel},
+\ref{tbl:navMessage} and \ref{tbl:almanacMessage} on the following pages \pageref{tbl:utcModel},
+\pageref{tbl:ionoModel}, \pageref{tbl:navMessage} and \pageref{tbl:almanacMessage}. How other
+data are encoded will be given in the implementation chapter, chapter \ref{Implementation}.
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,
@@ -1728,7 +1734,7 @@ needs to specify what type of assistance the packet includes, in this case it is
data (\textit{gps-AssistData}, colored red in listing \ref{lst:RRLPAssisPER}). GPS assistance data were described in the
two previous paragraphs and therefore will be omitted here. They will be only listed in the order as
specified in the RRLP standard for GPS assistance data, listing \ref{lst:GPSAssisData}: reference time, reference location, DGPS corrections, navigation model,
-ionospheric model, UTC model, almanac, acquisition assistance and real time integrity (colored blue in
+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
@@ -1742,6 +1748,7 @@ in the RRLP assistance PDU packet. The reference location has to be converted
into an ellipsoid point with altitude and uncertainty ellipsoid as described
in the standard \citep{3gppequations} under section \textit{7.3.6}, as shown
in figure \ref{img:refLocStandard}.
+
\begin{lstlisting}[label=lst:GPSAssisData,
caption={\textbf{Structure of data types of GPS assistance data in ASN.1}},
backgroundcolor=\color{light-gray},
@@ -1761,6 +1768,7 @@ ControlHeader ::= SEQUENCE {
realTimeIntegrity SeqOf-BadSatelliteSet OPTIONAL
}
\end{lstlisting}
+
The reference location consists of longitude, latitude, altitude, uncertainty semi-major,
uncertainty semi-minor, orientation of major axis, uncertainty of altitude and confidence
level. \textbf{S} is sign of the latitude, it is set to one if it is North and zero if
@@ -1786,6 +1794,31 @@ Longitude is encoded as second compliment binary number \citep{3gppequations}.
\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.
+The uncertainties for latitude, longitude and altitude are encoded using the equation
+given in \eqref{eq:uncerAltitudeStand}, where $r$ is the uncertainty in meters for
+latitude and longitude, and $h$ is the uncertainty in meters for altitude of the BTS.
+Both values, $U_L$ and $U_A$, are 7 bit numbers in the range between 0 and 127.
+Orientation of major axis is not used in this work so it was set to zero.
+Confidence describes the level by which the sent BTS reference position is
+known to be correct. The confidence is a 7 bit number but ought to take values
+between 0 and 100 since it represents the percentage. In this work it was set
+to zero, i.e. no information is available about the confidence for our reference
+location. It did not change the output behaviour from the MS.
+
+If the reference location is included in the RRLP assistance packet, it is
+important to specify the octet length of the reference location. The length of the reference
+location of an ellipsoid point with altitude and uncertainty ellipsoid is of length 14 octets,
+as it can be seen in figure \ref{img:refLocStandard} (amount of rows), it is written as 13 octets
+in the RRLP PDU packet.
+It is always specified as one number less since at least one octet has to be included in the
+reference location. There are other reference location standards inside of the RRLP protocol.
+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
+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.
\begin{equation}
\label{eq:latLong}
\begin{array}{l}
@@ -1806,32 +1839,6 @@ Longitude is encoded as second compliment binary number \citep{3gppequations}.
\end{split}
\end{array}
\end{equation}
-The altitude is encoded as it is where one bit increments represent one meter incerements.
-The uncertainties for latitude, longitude and altitude are encoded using the equation
-given in \eqref{eq:uncerAltitudeStand}, where $r$ is the uncertainty in meters for
-latitude and longitude, and $h$ is the uncertainty in meters for altitude of the BTS.
-Both values, $U_L$ and $U_A$, are 7 bit numbers in the range between 0 and 127.
-Orientation of major axis is not used in this work so it was set to zero.
-
-If the reference location is included in the RRLP assistance packet, it is
-important to specify the octet length of the reference location. The length of the reference
-location of an ellipsoid point with altitude and uncertainty ellipsoid is of length 14 octets,
-as it can be seen in figure \ref{img:refLocStandard} (amount of rows), it is written as 13 octets
-in the RRLP PDU packet.
-It is always specified as one number less since at least one octet has to be included in the
-reference location. There are other reference location standards inside of the RRLP protocol.
-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
-then the MS can return an error and ask for retransmission of the data.
-
-
-
-The assistance data RRLP packet is
-constructed by concatenating the bits required to descibre a variable.
-
-
\begin{equation}
\label{eq:uncerAltitudeStand}
@@ -1853,13 +1860,92 @@ constructed by concatenating the bits required to descibre a variable.
\end{split}
\end{array}
\end{equation}
-In the following tables
-NAPISI STA JE NAVIGATION MODEL (EPHEMERIS)
-\begin {table}[tp!]
-\caption{Navigation message content.}
+
+\begin {table}[hb]
+\caption{GPS UTC Model content}
+\label{tbl:utcModel}\centering
+%\rowcolor{2}{light-gray}{}
+\scriptsize\fontfamily{iwona}\selectfont
+\begin{tabular}{clccc}
+\toprule
+%$D$&&$P_u$&$\sigma_N$\\
+Field (IE) & Description\\\toprule
+$A_{1}$&Drift coefficient of GPS time scale relative\\
+&to UTC time scale\\\midrule
+$A_{0}$&Bias coefficient of GPS time scale relative\\
+&to UTC time scale\\\midrule
+$t_{ot}$&Time data reference time of week\\\midrule
+$\Delta t_{LS}$&Current or past leap second count\\\midrule
+$WN_{0}$&Time data reference week number\\\midrule
+$WN_{LSF}$&Leap second reference week number\\\midrule
+$DN$&Leap second reference day number\\\midrule
+$\Delta t_{LSF}$&Current of future leap second count
+\\\bottomrule
+\end {tabular}
+\end {table}
+\newpage
+\begin{lstlisting}[label=lst:RRLPAssisPER,
+caption={\textbf{Encoding reference location from ASN.1 to PER}},
+backgroundcolor=\color{light-gray},
+basicstyle=\scriptsize\ttfamily,
+escapechar=@,
+emph={gps-AssistData},
+emphstyle=\color{crvena},
+emph={[2]referenceTime,refLocation,dgpsCorrections,
+navigationModel,ionosphericModel,utcModel,almanac,acquisAssist,realTimeIntegrity},
+emphstyle={[2]\color{plava}}]
+ RRLP Message:
+44 010..... referenceNumber = 2
+ component(RRLP-Component):
+ ...0.... Extension of RRLP-Component = 0 :Absent
+ @\textbf{....010.}@ @\textbf{RRLP-Component}@ @\textbf{=}@ @\textbf{2}@ @\textbf{:assistanceData}@
+ AssistanceData:
+ .......0 Extension of AssistanceData = 0 :Absent
+11 0....... referenceAssistData = 0 :Absent
+ .0...... msrAssistData = 0 :Absent
+ ..0..... systemInfoAssistData = 0 :Absent
+ ...1.... @\textcolor{red}{gps-AssistData}@ = 1 :Present
+ ....0... moreAssDataToBeSent = 0 :Absent
+ .....0.. extensionContainer = 0 :Absent
+ GPS-AssistData:
+ ControlHeader:
+ ......0. referenceTime = 0 :Absent
+ .......1 refLocation = 1 :Present
+00 0....... dgpsCorrections = 0 :Absent
+ .0...... navigationModel = 0 :Absent
+ ..0..... ionosphericModel = 0 :Absent
+ ...0.... utcModel = 0 :Absent
+ ....0... almanac = 0 :Absent
+ .....0.. acquisAssist = 0 :Absent
+ ......0. realTimeIntegrity = 0 :Absent
+ RefLocation:
+ threeDLocation(Ext-GeographicalInformation):
+ .......0 @\textcolor{narandzasta}{Ext-GeographicalInformation length(octet)}@ = 13 :13 + 1 = 14
+D9 1101....
+ ....1001 @\textcolor{narandzasta}{Ext-GeographicalInformation}@ = 904445940594B200000707000700h
+04 00000100
+44 01000100
+59 01011001
+40 01000000
+59 01011001
+4B 01001011
+20 00100000
+00 00000000
+00 00000000
+70 01110000
+70 01110000
+00 00000000
+70 01110000
+00 0000....
+
+ ....0000 Spare Bits = 0000b
+\end{lstlisting}
+
+\begin {table}[ht!]
+\caption{Navigation message (ephemeris) content}
\label{tbl:navMessage}\centering
%\rowcolor{2}{light-gray}{}
-\scriptsize
+\scriptsize\fontfamily{iwona}\selectfont
\begin{tabular}{clccc}
\toprule
%$D$&&$P_u$&$\sigma_N$\\
@@ -1892,7 +1978,7 @@ Fit Interval Flag&\\\midrule
AODO&Age of data offset\\\midrule
$C_{ic}$&Amplitude of the cosine harmonic correction term to the angle of inclination\\
&(radians)\\\midrule
-OMEGA$_0$&Longitude of ascending node of orbit plane at weekly epoch (semicircles)\\\midrule
+$\Omega_0$&Longitude of ascending node of orbit plane at weekly epoch (semicircles)\\\midrule
$C_{is}$&Amplitude of the cosine harmonic correction term to the angle of inclination\\
&(radians)\\\midrule
$i_{0}$&Inclination angle at reference time (semicircles)\\\midrule
@@ -1904,32 +1990,45 @@ Idot&Rate of inclination angle (semicircles/sec)
\end {tabular}
\end {table}
-\begin {table}[tp!]
-\caption{GPS Ionosphere Model}
-\label{tbl:ionoModel}\centering
+\begin {table}[hb]
+\caption{Almanac message content}
+\label{tbl:almanacMessage}\centering
%\rowcolor{2}{light-gray}{}
-\scriptsize
+\scriptsize\fontfamily{iwona}\selectfont
\begin{tabular}{clccc}
\toprule
%$D$&&$P_u$&$\sigma_N$\\
Field (IE) & Description\\\toprule
-$\alpha_{0}$&Coefficient 0 of vertical delay\\\midrule
-$\alpha_{1}$&Coefficient 1 of vertical delay\\\midrule
-$\alpha_{2}$&Coefficient 2 of vertical delay\\\midrule
-$\alpha_{3}$&Coefficient 3 of vertical delay\\\midrule
-$\beta_{0}$&Coefficient 0 of period of the model\\\midrule
-$\beta_{1}$&Coefficient 1 of period of the model\\\midrule
-$\beta_{2}$&Coefficient 2 of period of the model\\\midrule
-$\beta_{3}$&Coefficient 3 of period of the model
+SatelliteID&This is the satellite ID that is in the range of 0 to 63. PRN=SatelliteID + 1\\\midrule
+SV Health&Satellite health (e.q. 000 means the satellite is fully operational)\\\midrule
+$e$&``Eccentricity shows the amount of the orbit deviation from circular (orbit).\\
+&It is the distance between the foci divided by the length of the semi-major axis'' \citep{ubxGPSDict}\\\midrule
+TOA&Time of applicability, reference time for orbit and clock parameters (seconds).\\
+&``The number of seconds in the orbit when the almanac data were generated'' \citep{ubxGPSDict}\\\midrule
+OI&Orbital inclination (radians). The angle to which the SV orbit meets\\
+&the equator \citep{ubxGPSDict}\\\midrule
+RORA&Rate or right ascension (radians/second). ``Rate of change of the angle of right ascension\\
+&as defined in the Right Ascension mnemonic'' \citep{ubxGPSDict}\\\midrule
+$A^{1/2}$& Square root of semi-major axis (meters$^{1/2}$). `` This is defined as the measurement\\
+&from the center of the orbit to either the point of apogee or the point of perigee'' \citep{ubxGPSDict}\\\midrule
+$\Omega_0$& Right Ascension at Week (radians). Longitude of ascending node of orbit plane at\\
+&weekly epoch\\\midrule
+$\omega$&Argument of perigee (semicircles). ``An angular measurement along the orbital path\\
+&measured from the ascending node to the point of perigee, measured in the direction of\\
+&the SV's motion'' \citep{ubxGPSDict}\\\midrule
+$M_0$&Mean anomaly (radians)\\\midrule
+$a_{f0}$&Satellite clock bias (seconds). Satellite clock error at reference time\\\midrule
+$a_{f1}$&Satellite clock drift (seconds per second). Satellite clock error rate\\\midrule
+Week&Week number since the last reset (i.e. since year 1980 modulo 1024 weeks)
\\\bottomrule
\end {tabular}
\end {table}
-\begin {table}[tp!]
-\caption{Navigation message content.}
+\begin {table}[hb]
+\caption{GPS Ionosphere Model content}
\label{tbl:ionoModel}\centering
%\rowcolor{2}{light-gray}{}
-\scriptsize
+\scriptsize\fontfamily{iwona}\selectfont
\begin{tabular}{clccc}
\toprule
%$D$&&$P_u$&$\sigma_N$\\
@@ -1947,66 +2046,7 @@ $\beta_{3}$&Coefficient 3 of period of the model
\end {table}
-\newpage
-\begin{lstlisting}[label=lst:RRLPAssisPER,
-caption={\textbf{Encoding reference location from ASN.1 to PER}},
-backgroundcolor=\color{light-gray},
-basicstyle=\scriptsize\ttfamily,
-escapechar=@,
-emph={gps-AssistData},
-emphstyle=\color{crvena},
-emph={[2]referenceTime,refLocation,dgpsCorrections,
-navigationModel,ionosphericModel,utcModel,almanac,acquisAssist,realTimeIntegrity},
-emphstyle={[2]\color{plava}}]
- RRLP Message:
-44 010..... referenceNumber = 2
- component(RRLP-Component):
- ...0.... Extension of RRLP-Component = 0 :Absent
- @\textbf{....010.}@ @\textbf{RRLP-Component}@ @\textbf{=}@ @\textbf{2}@ @\textbf{:assistanceData}@
- AssistanceData:
- .......0 Extension of AssistanceData = 0 :Absent
-11 0....... referenceAssistData = 0 :Absent
- .0...... msrAssistData = 0 :Absent
- ..0..... systemInfoAssistData = 0 :Absent
- ...1.... @\textcolor{red}{gps-AssistData}@ = 1 :Present
- ....0... moreAssDataToBeSent = 0 :Absent
- .....0.. extensionContainer = 0 :Absent
- GPS-AssistData:
- ControlHeader:
- ......0. referenceTime = 0 :Absent
- .......1 refLocation = 1 :Present
-00 0....... dgpsCorrections = 0 :Absent
- .0...... navigationModel = 0 :Absent
- ..0..... ionosphericModel = 0 :Absent
- ...0.... utcModel = 0 :Absent
- ....0... almanac = 0 :Absent
- .....0.. acquisAssist = 0 :Absent
- ......0. realTimeIntegrity = 0 :Absent
- RefLocation:
- threeDLocation(Ext-GeographicalInformation):
- .......0 @\textcolor{narandzasta}{Ext-GeographicalInformation length(octet)}@ = 13 :13 + 1 = 14
-D9 1101....
- ....1001 @\textcolor{narandzasta}{Ext-GeographicalInformation}@ = 904445940594B200000707000700h
-04 00000100
-44 01000100
-59 01011001
-40 01000000
-59 01011001
-4B 01001011
-20 00100000
-00 00000000
-00 00000000
-70 01110000
-70 01110000
-00 00000000
-70 01110000
-00 0000....
-
- ....0000 Spare Bits = 0000b
-\end{lstlisting}
-
-
-
+\clearpage
\section{RRLP Response}
@@ -2022,7 +2062,8 @@ D9 1101....
-\chapter{Software}
+\chapter{Implementation}
+\label{Implementation}
-from rinex conversion\\
explain rinex form \\
@@ -2198,8 +2239,6 @@ than 100 m \citep{installnanoBTS}.
\label{img:connectionDiagram}
\end{figure}
-\chapter{Implementation}
-
\chapter{Testing}
Test if it can be tricked out by the software Dennis mentioned (protect my privacy)!
diff --git a/vorlagen/thesis/src/maindoc.tex b/vorlagen/thesis/src/maindoc.tex
index 872f3e6..959ac15 100644
--- a/vorlagen/thesis/src/maindoc.tex
+++ b/vorlagen/thesis/src/maindoc.tex
@@ -33,9 +33,13 @@
%\usepackage{marvosym}
%Mathematische und andere Symbole
+%\usepackage{iwona}
+%\usepackage{fontspec}
+
\usepackage{amsmath,mathrsfs,amssymb}
\usepackage[scaled=.92]{helvet}
\usepackage{courier}
+%\usepackage[T1]{fontenc}
% I added this, REFIK
\usepackage{color}