From aee4fc0a3d65eed243daff51220f200442963a7f Mon Sep 17 00:00:00 2001
From: Refik Hadzialic
Date: Sat, 28 Jul 2012 18:28:27 +0200
Subject: assistance data

---
 vorlagen/thesis/src/kapitel_x.tex | 165 +++++++++++++++++++++++++++++---------
 1 file changed, 127 insertions(+), 38 deletions(-)

(limited to 'vorlagen/thesis/src/kapitel_x.tex')

diff --git a/vorlagen/thesis/src/kapitel_x.tex b/vorlagen/thesis/src/kapitel_x.tex
index 09f954f..d6eb19d 100644
--- a/vorlagen/thesis/src/kapitel_x.tex
+++ b/vorlagen/thesis/src/kapitel_x.tex
@@ -1087,7 +1087,7 @@ where $i=1,2,...,n$ such that $n\geq4$ and $\vec{s_i}=(x_i,y_i,z_i)$ is the sate
 \end{equation}
 Undoubtedly, the given equation in \eqref{eq:rhoSatsNew} is a nonlinear 
 equation\footnote{Nonlinear
-equations, also known as polynomial equations, are equations that cannot satisfy both
+equations, also known as polynomial equations, are equations that can not satisfy both
 of the linearity properties:
 additivity $f(x+y)=f(x)+f(y)$ and homogeneity $f(\alpha x) = \alpha f(x)$, $\alpha \in \mathbb{R}$ \citep{nonlinear}.}.
 It is not straightforward to find explicit solutions of nonlinear equations, it is more difficult than
@@ -1383,7 +1383,7 @@ SMLC controls the LMU's as well but since in this work no LMU were available thi
 will be skipped as well as the description of E-OTD and UL-TDOA localization. 
 
 Before an attempt is made, of requesting the SMLC to initialize an RRLP request, an SDDCH connection 
-channel has to be initialized to the MS, this connection cannot be seen by the MS user\footnote{However,
+channel has to be initialized to the MS, this connection can not be seen by the MS user\footnote{However,
 it is possible to take into consideration that something is going on the cell phone if the MSs battery
 is drained faster because an active RF connection drains the battery faster than a passive MS
 connected to the GSM network.}.
@@ -1398,9 +1398,10 @@ connected to the GSM network.}.
 
 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}. 
-In RRLP, the PDU's sent from the SMLC ought to be not greater than 242 bytes\footnote{Bytes of 8 bits!},
+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 \citep{04.31V8.18.0}. In the RRLP standard terms, the messages are entitled
+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 
@@ -1486,6 +1487,35 @@ MsrPosition-Req ::= SEQUENCE {
   rel98-MsrPosition-Req-extension Rel98-MsrPosition-Req-Extension OPTIONAL
 }
 \end{lstlisting}
+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. 
+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. 
+
+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
+RRLP request. A type of \textbf{SEQUENCE} is used to 
+reference a ``fixed, ordered list of types (some of which may be declared to be
+optional); each value of the sequence type is an ordered list of values,
+one from each component type'' \citep{ITU-TX.691} where the 
+IE (fields) of \textbf{OPTIONAL} type do not need to be included and are not mandatory.
+Variables defined by \textbf{CHOICE} are used to reference ``a list of distinct types; 
+each value of the choice type is derived from the value of one of the
+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 
+type with distinguished values which are the positive and negative whole numbers,
+including zero (as a single value)'' \citep{ITU-TX.691}.
+\newpage
 \begin{lstlisting}[label=lst:RRLPReqData,
 caption={\textbf{Structure of the data types from RRLP request in ASN.1}},
 backgroundcolor=\color{light-gray},
@@ -1532,34 +1562,6 @@ UseMultipleSets ::= ENUMERATED {
   oneSet (1) -- sending of multiple is not allowed
 }
 \end{lstlisting}
-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. 
-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. 
-
-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
-RRLP request. A type of \textbf{SEQUENCE} is used to 
-reference a ``fixed, ordered list of types (some of which may be declared to be
-optional); each value of the sequence type is an ordered list of values,
-one from each component type'' \citep{ITU-TX.691} where the 
-IE (fields) of \textbf{OPTIONAL} type do not need to be included and are not mandatory.
-Variables defined by \textbf{CHOICE} are used to reference ``a list of distinct types; 
-each value of the choice type is derived from the value of one of the
-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 
-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}.
@@ -1671,9 +1673,9 @@ which allows the AGPS to find immediatelly the Doppler frequency and phase shift
 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.
 In this thesis, as assistance data only the almanac, ephemeris, UTC model, ionospheric
-model and reference location is transmitted to the MS. There are also other assistance
-data like differential GPS corrections (DGPS), real time integrity and reference time
-but none of these were available to the author, so they were avoided. The reasons for
+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
+and reference time but none of these were available to the author, so they were avoided. The reasons for
 this decision were explained earlier as cost and complexity issues.
 
 DGPS corrections give additional accuracy to the GPS measurement reports between $1-3$ m \citep{489522} and they 
@@ -1693,15 +1695,102 @@ HOW starting words of the transmitted GPS packets from the satellites
 (refer to section \ref{sec:gpsDataAndSignal}). Reference time data can include the relationship
 between the GSM network and GPS time, as well as the GSM frame number to help the MS to 
 synchronize with the BTS (earlier this was described as time synchronized GSM networks which is
-required for methods like E-OTD)\citep[Chapter 4]{harper2010server-side}. 
-
-More information on assistance data transmitted inside the RRLP protocol will be presented now.
+required for methods like E-OTD) \citep[Chapter 4]{harper2010server-side}. Acquisition assistance
+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. 
+
+More information on the assistance data transmitted in this work will be presented here. As listed above, 
+almanac, ephemeris, UTC model, ionospheric model and reference location are transmitted to the MS. Reference
+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 
+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. 
+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 only sent once and are valid for all satellites \citep[Chapter 4]{harper2010server-side}.
+
+
+NAPISI STA JE NAVIGATION MODEL (EPHEMERIS)
 
 \newpage
+\begin{lstlisting}[label=lst:RRLPReqPER,
+caption={\textbf{Encoding an RRLP request from ASN.1 to PER}},
+backgroundcolor=\color{light-gray},
+basicstyle=\scriptsize\ttfamily]
+             RRLP Message:
+44 010.....   referenceNumber = 2
+              component(RRLP-Component):
+   ...0....    Extension of RRLP-Component = 0 :Absent
+   ....010.     RRLP-Component = 2 :assistanceData
+                 AssistanceData:
+   .......0       Extension of AssistanceData = 0 :Absent
+11 0.......       referenceAssistData = 0 :Absent
+   .0......       msrAssistData = 0 :Absent
+   ..0.....       systemInfoAssistData = 0 :Absent
+   ...1....       gps-AssistData = 1 :Present
+   ....0...       moreAssDataToBeSent = 0 :Absent
+   .....0..       extensionContainer = 0 :Absent
+                  GPS-AssistData:
+                   ControlHeader:
+   ......0.         referenceTime = 0 :Absent
+   .......1         refLocation = 1 :Present
+30 0.......         dgpsCorrections = 0 :Absent
+   .0......         navigationModel = 0 :Absent
+   ..0.....         ionosphericModel = 1 :Present
+   ...1....         utcModel = 1 :Present
+   ....0...         almanac = 0 :Absent
+   .....0..         acquisAssist = 0 :Absent
+   ......0.         realTimeIntegrity = 0 :Absent
+                    RefLocation:
+                     threeDLocation(Ext-GeographicalInformation):
+   .......0           Ext-GeographicalInformation length(octet) = 13 :13 + 1 = 14
+D9 1101....
+   ....1001           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}
 \section{RRLP Response}
 
+
+
+
+
+
+
+
+
+
+
+
+
+
 \chapter{Software}
 
+-from rinex conversion\\
+explain rinex form \\
+explain a bit ephemeris data and almanac \\
+data and conversion \\
+
 Author's test system operated on the ARFCN 877 channel. ARFCN (Absolute Radio
 Frequency Channel Number) defines the uplink and downlink channel frequency insdide 
 the GSM network \citep{Richard2011Master}. ARFCN 877 corresponds to the uplink frequency
-- 
cgit v1.2.3-55-g7522

