summaryrefslogtreecommitdiffstats
path: root/vorlagen
diff options
context:
space:
mode:
Diffstat (limited to 'vorlagen')
-rw-r--r--vorlagen/thesis/maindoc.pdfbin6028076 -> 6039969 bytes
-rw-r--r--vorlagen/thesis/src/kapitel_A.tex7
-rw-r--r--vorlagen/thesis/src/kapitel_x.tex94
3 files changed, 91 insertions, 10 deletions
diff --git a/vorlagen/thesis/maindoc.pdf b/vorlagen/thesis/maindoc.pdf
index 0a6e0a1..e1a118c 100644
--- a/vorlagen/thesis/maindoc.pdf
+++ b/vorlagen/thesis/maindoc.pdf
Binary files differ
diff --git a/vorlagen/thesis/src/kapitel_A.tex b/vorlagen/thesis/src/kapitel_A.tex
index 828182e..ff0352b 100644
--- a/vorlagen/thesis/src/kapitel_A.tex
+++ b/vorlagen/thesis/src/kapitel_A.tex
@@ -271,11 +271,8 @@ settings =
\todo{CHECK IF THIS IS CORRECT}
-The target user, one wants to locate, has to be inside of a geometric estimated shape.
-This shape can be described using an
-ellipsoid point with altitude and uncertainty ellipsoid. \todo{CHECK IF THIS IS CORRECT}
-The uncertainty of
-the latitude and longitude correctness can be described
+\label{accuracyUncertainty}
+The uncertainty of the latitude and longitude correctness can be described
using equation \eqref{eq:unclatlong} \citep{3gppequations}. The uncertainty of
$r$ is expressed in meters, it defines how accurate is the specified location
of the BTS. In the configuration file, $K$ is set to 7, which corresponds to
diff --git a/vorlagen/thesis/src/kapitel_x.tex b/vorlagen/thesis/src/kapitel_x.tex
index 343581d..c8492e5 100644
--- a/vorlagen/thesis/src/kapitel_x.tex
+++ b/vorlagen/thesis/src/kapitel_x.tex
@@ -1538,17 +1538,17 @@ in the choice of encoding rules \citep{ITU-TX.691}. In other words, it compresse
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 aligned type 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, i.e. there are some wasted padding bits which
-are set to zero if not used.
+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 elements inside
+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
@@ -1561,7 +1561,91 @@ first element is of value zero. Veriables defined by \textbf{INTEGER} are of the
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. The IE
+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 will be ignored. \textbf{PositionInstruct} consists
+of five elements but four are mandatory: \textit{methodType}, \textit{positionMethod},
+\textit{measureResponseTime} and \textit{useMultipleSets}. These five 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)
+\end{equation}
+\begin{equation}
+\label{eq:responseTime}
+MeasureResponseTime=\frac{ln(N)}{ln(2)}
+\end{equation}
+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
+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),
+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
+given in \eqref{eq:responseTime}, where $N$ is the number of seconds the MS is allowed to perform the
+position estimation.
+
+After the parameters have been choosen according to the selected test, the network operator wants to perform,
+the RRLP request can be constructed. \ref{lst:RRLPReqPER}
+\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:
+40 010..... referenceNumber = 2
+ component:
+ ...0.... Extension of RRLP-Component = 0 :Absent
+ ....000. RRLP-Component = 0 :msrPositionReq
+ MsrPosition-Req:
+ .......0 Extension of MsrPosition-Req = 0 :Absent
+01 0....... referenceAssistData = 0 :Absent
+ .0...... msrAssistData = 0 :Absent
+ ..0..... systemInfoAssistData = 0 :Absent
+ ...0.... gps-AssistData = 0 :Absent
+ ....0... extensionContainer = 0 :Absent
+ PositionInstruct:
+ .....0.. environmentCharacter = 0 :Absent
+ MethodType:
+ ......01 MethodType = 1 :msBased
+ Accuracy:
+78 0111100. Accuracy = 60
+ PositionMethod:
+ .......0 PositionMethod = 1 :gps
+F8 1.......
+ MeasureResponseTime:
+ .111.... MeasureResponseTime = 7
+ UseMultipleSets:
+ ....1... UseMultipleSets = 1 :oneSet
+ .....000 Spare Bits = 000b
+\end{lstlisting}
+
+
+To make an RRLP request,
+one has to construct the query from the above given ASN.1 specifications. The simplest
+possible request
\subsection{RRLP Assistance data}