Project Proposal

April 2014
Student to complete this section

H.M
.
Simulator For Multilateration System
Accuracy Analysis.
TSIMBA

Mr. 11038421
Study leader:
Prof. B.T Maharaj

Class group: English

Revision number:

Type of project: Design

Degree programme enrolled for: Electronic

Engineering

Student declaration:
I understand what plagiarism is and that I have to complete
my project on my own.

____________ ___
Student signature

_____________
Date

Declaration by language editor (proofreader)

I have been allowed adequate time to read this document carefully and to make corrections where necessary (date
received indicated below).
To the best of my knowledge, correct formatting, spelling and grammar are used throughout the document.

_______________________________
(language editor)

____________
Date

Declaration and recommendation by study leader

1. Have you (the study leader) been allowed adequate time to read and comment on the Project
Proposal?

Yes

No

Correct:

Yes

No

Complete:

Yes

No

Clear:

Yes

No

Unambiguous:

Yes

No

3. Recommendation: Do you recommend that the Project Proposal be approved?

Yes

No

________________________________
Prof. B.T. Maharaj (Study leader)

___________
Date

2. Is the Project Proposal a correct, complete, clear and unambiguous

description of what is required of the student?

This section to be used by the Project lecturer

Content /20
Subtract for editing
errors /10
Final mark /20

Attended lectures:

Yes

No

Language editing adequate:

Yes

No

Approved? (If "No", a revision

must be submitted):

Yes

No

Prof. J.J. Hanekom

Short Form Project Proposal

April 2014
Student details

H.M
.
Simulator For Multilateration System
Accuracy Analysis.
TSIMBA

Mr. 11038421
Study leader:
Prof. B.T. Maharaj

1. Motivation (why this project?)

What problem does this project solve and what is the concept?

The Multilateration system used at airports is susceptible to various factors that affect its
accuracy. The aim is to develop a simulator that will allow for the incorporation of all these
factors and the analysis their effects on the system.
What will be the main engineering challenges, and what restrictions would you need to overcome?

The main challenges will be (i) to account for all factors that come into play (ii) to develop
a comprehensive system and (iii) verify the correctness of the simulator.
2. Objectives (what will be the tasks?)
My tasks. What will be my main tasks? (What software will I develop? What hardware will I develop? Which
experiments will I perform?)

Theoretical background must be understood. A Graphical User Interface will be developed

in JAVA. Hardware will be designed to simulate some of the factors that affect the
accuracy. Experiments and necessary simulations will be made to test the simulation.
My product's tasks.
Design part of the project: what are the most import tasks of the system that I will design?

The simulator with a GUI that will take different factors one at a time or all at once.

Investigative part of the project: what is the one most important research question in my project?

The effect of the various factors on the accuracy with an emphasis on the effect of
inaccuracies in Time Difference of Arrival.
3. Specifications (how well should my system perform its tasks?)
What is the single most important target specification that my system is intended to meet?

The system must be able to output the position of the aircraft in simulated conditions
within at 25m in cases where no factors are considered.
4. Deliverables
List of deliverables that I will design and implement myself

The JAVA code for the simulator design and implementation of factors for
simulation.
DSP board based hardware to simulate the TDOA inaccuracy.

1. PROBLEM STATEMENT
This project aims to further develop the Multilateration (MLAT) system used to locate aircraft
that are at or within the vicinity of an airport. Work done on this system indicates that MLAT is
highly sensitive to inaccuracies in measurements and to other factors [1]. This sensitively results
in the current system incorrectly locating aircraft potentially leading to disastrous effects. There is
a need to better understand the factors that cause these inaccuracies so as to help reduce their
effects. Thus through the use of a simulator this project aims to determine the various effects that
are produced by these inaccuracies.
Currently most airports rely on the traditional method of primary and secondary surveillance
radar (SSR) [2]. These traditional methods have problems such as high power requirements, high
maintenance costs and blind spots. A solution to this problem is supplementing with MLAT
systems. MLAT is a modern approach to air traffic control which is backward compatible to SSR
and forward compatible to another emerging technology, Automatic Dependent SurveillanceBroadcast (ADS-B) [3]. MLAT systems make use of multiple stations which are placed
strategically on the airport surface. Using one of these stations (therefore the reference station),
the systems asks (interrogates) an oncoming aircraft for its information. The aircrafts
transponder will reply to this interrogation with its identity and this reply will be detected by all
the ground stations at different times due to the different distances between them and the aircraft.
The system makes use of the time difference of arrival (TDOA) between the same transponder
reply being received at the various stations on the ground to locate the interrogated transponder.
MLAT systems can be categorized into two methods namely, central and distributed systems.
Central system is whereby the transponder reply are time stamped by the main computer situated
somewhere away from the receivers and distributed time is whereby replies are time stamped by
the receivers themselves. It can be seen that the system is highly dependent on correctly
determining these TDOAs. These TDOAs can be affected by factors such as, among other, the
shortening of the fibre cable that connects a receiver to the central computer. Algorithms already
exist that solve for the position of a transponder namely the Friedlander [4], Bucher [5] and the
Gillette-Silverman [6] to name a few. These algorithms are highly sensitive to TDOA
inaccuracies; a 0.045s error in the TDOA estimation can produce a median error of 40m [1].
This project will extend on the work already done by C. Panayi [1]. This work comprises the
JAVA1 and Matlab2 coding of the MLAT algorithms. The simulator will use this code as the base
for the MLAT system to determine the exact effects of these factors on the MLAT output.
A technical challenge will be identifying all the factors and their sources that come into play in
the MLAT system such as TDOA and receiver location inaccuracies caused by fibre link delays,
phase shifts and inaccurate beacon positioning. Often the actual receiver location might be off by
a short distance from the measured location. A further challenge is the designing of a
comprehensive simulator that will correctly predict the outcome of the MLAT system. The
simulator must be able to simulate for one or all the factors at a time.
One limitation for the project is the obtaining of error free real data. This data is needed in order
to verify the functioning of the simulator. Another limitation is the effect of built up areas near
the transponder or the receiver. A multipath model for these effects will have to be assumed for
the simulator[7].
1 JAVA coding language is a product Oracle Cooperation. http://www.java.com
2 Matlab is a mathematical software simulation tool developed by MathWorks, Inc. http://www.mathworks.com/products/matlab
2

2. USER REQUIREMENT STATEMENT

The user requirement is to develop a simulator by using MLAT code and algorithms to determine
aircraft position and height. The simulator must in-cooperate a GUI for the input and display of
information. The secondary requirement is to then, through the use of the simulator, investigate
the effect on the system accuracy due to various imporatant factors.
2.1 Design part of the project
Task breakdown
Literature Study.
Analyze existing code.
Develop simulator code in platform.
Investigate appropriate hardware to realize receiver inaccuracies.
Port existing code to simulator platform.
Build GUI for simulator.
Generate random test data.
Run simulations to verify correctness.
Include factors that affect the system in the simulations.
Record results.
Mission requirements of the product

Simulation must be achieved using all the MLAT algorithms stated above.
Determine and analyze the effect of multiple factors on the accuracy of the MLAT system.
Simulate for both central and distributed time systems.
The simulator must be capable of determining the effects of a single factor at a time and
also of multiple factors at a time.
The system must quantitatively determine and display the error resulting from the factors.
The system should be able to take in some factors externally.

2.2 Investigative part of the project

Research Questions
The following research questions are to be addressed.

What algorithms exist and what approaches are used to solve MLAT problems?
Which factors affect the accuracy of the MLAT system?
Is the accuracy of system meaningfully affected by a certain factors?
Do all the algorithms respond the same way to a similar factor?
Can some factors be accounted for to mitigate their effect on the system?

3. FUNCTIONAL ANALYSIS
This section aims to give further insight into the functions of the system block. The functional diagram of
the entire system is shown in figure 1 below.
FU1
FU2
System Input
GUI input of factors for Capture
analysis of external data from hardware for simulation
Timestamps, Receiver locations, Transponder replies

Parameters
FU4

FU3

Display on GUI Calculations using MLAT algorithms to locate aircraft

Figure 1: Functional Diagram with brief description of each unit

The MLAT algorithms used in FU3 will be obtained from previous work done on this project by
C.Panayi in 2013[1].
The inputs to the system are the timestamps, receiver locations and transponder replies generated
for simulation. For the timestamp input, these will be from pre-determined static transponders so
as to provide a base for determining any changes in accuracy. The receiver locations input will be
for the simulation of any effects due to the positioning of the receivers. FU1 is comprised of the
GUI which will be the main input method for the user to change any simulation parameters. This
unit will provide default and changeable options to user to use in the simulation. Examples of
options are receiver location offset, synchronization of receivers (distributed systems), etc. FU2
will be used to supplement the main input method by providing inaccuracies for the system. This
is so, because some inaccuracies are inherent in the system and the hardware will provide a kind
of permanent default setting. This will be implemented on a DSP board. FU3 will consist of the
actual calculations done to determine the position of the aircraft. The algorithms will take into
account all the parameters and factors set by the user to give the simulated position of the
transponder. Finally FU4 is the unit that will display the location of the aircraft on map and also
show the region of error that might arise in a non-ideal situation. This functional unit will also
display on the map the output positions of the various MLAT algorithms to allow for an in-situ
comparison among them. FU4 will be built from first principles and will be implemented in Java.
FU2.1

FU2.2

FU2.3

Hardware for TDOA inaccuracy input

Code for manipulating the TDOA inaccuracy
Output of the Data to simulator FU3

Figure 2: Block diagram of the functioning of the hardware.

Figure 2 shows the purpose and the function diagram of FU2. A combination of hardware such as
sensors, switches, knobs and a DSP board will be the used to represent some factors for input to
the system in FU2.1. As the TDOA inaccuracies will not be a constant between all the receivers
FU2.2 will provide the necessary processing to produce the required TDOAs. FU2.3 will simply
send the processed data to the simulator.
4

4. SYSTEM SPECIFICATIONS
The following table gives the system specifications, a brief motivation as to why the specification
is necessary and how the specification will be confirmed.
4.1 MISSION-CRITICAL SYSTEM SPECIFICATIONS
SPECIFICATION (IN
MEASURABLE TERMS)

ORIGIN OR MOTIVATION
OF THIS SPECIFICATION

The simulator must return

the position of the aircraft
within at most 25m both
horizontally and vertically.
For simulations in which no
factors were considered.
The hardware must be able
to
vary
the
TDOA
inaccuracy from 0 to 10s.

The value was obtained The input to the simulator

from
Martone
and will be generated data from
Tucker[8]
a known position. The
simulator output will then
be compared with the
known location.
Given that an inaccuracy of The output of the hardware
0.06s produces a median timing will be tested using
error of 40m [1], it is an oscilloscope.
unnecessary to simulate
anything above 10s as the
value will already be wildly
incorrect
The receiver stations are The signal power and the
only able to achieve no bit added noise power will be
errors for an SNR above measured separately to
27dB. Thus situations in determine the SNR.
which the SNR is lower
than this will need to be
analyzed.
The standard transponder The generated reply pulse
reply is 8s. Changes in this width will be measured
width sometimes results in using an oscilloscope.
false and missed detections.
Hence the effect of different
values of these will need to
be simulated.
Transponder replies can The signal will be measured
sometimes
experience before the shift is applied
phase shifts. These will and compared to the same
affect the detection of signal after the shift has
replies by the receiver or by been applied.
the central computer.

The hardware input must be

able to vary the signal to
noise
ratio
of
the
transponder replies from
zero to at least 35dB.
The simulator must be able
to vary the transponder
reply width up to 1s.

The system must have

adjustable phase from zero
to 90 degrees.

HOW WILL YOU CONFIRM

THAT YOUR SYSTEM
COMPLIES WITH THIS
SPECIFICATION?

Table 1: The table describes in detail the mission-critical specifications.

4.2 FUNCTIONAL UNIT SPECIFICATIONS

Table 2 below gives the specifications for the four functional units in the system.
SPECIFICATION

ORIGIN OR MOTIVATION

FU1. The options should have default

values or conditions.
FU2.1 The input from the hardware button
press function will consider the
combination of all the buttons rather than
as a one button check. Must fall within
10% of the intended value.
FU3. All 3 MLAT algorithms mentioned in
section one and their variations coded in
[1] should be used in the simulator.

This is to prevent the simulator from

crashing upon a null or invalid input.
For a successful simulation the hardware
must be able to accurately deliver the
effects of the factors that it represents. The
range is in line with standard tolerance
values for hardware components.
This allows for comparison of the effects of
the factors on the different algorithms in
order to determine which is more
susceptible to which error.
FU4. The GUI should be a map thats A map would provide easy to read
shows the calculated position of the aircraft information.
together with the altitude.
Table 2: Specifications of the functional units with motivation

5. DELIVERABLES
5.1 Technical deliverables
Table 3 describes the technical deliverable and how they will be implemented.
DELIVERABLE

DSP board.
DSP code for manipulating
TDOAs.
Algorithm for simulator
with
input
variables
accessible to user.
GUI code that displays the
position of the aircraft
together with the error.
A user manual describing
the operation of the
simulator.

DESIGNED AND
IMPLEMENTED BY
STUDENT

OFF-THE-SHELF

X
X
X
X
X

Table 3: The table indicates how the deliverable will be implemented.

5.2 Demonstration at the examination

The following procedure will be used for the demonstration at the examination.
1. The demonstration will begin by displaying snippets of the input data (timestamps and
transponder replies) generated for simulation.
2. The GUI of the simulator will be opened and the timestamps or transponder replies feed
into the system.
3. The hardware will then be used to input the required TDOA inaccuracy.
4. The ability to manipulate factors that affect the MLAT system will then be shown.
5. A simulation will then be done to show the functioning of the simulator using ideal data
with the different factors in play.
6. Lastly a plot of the error against the different TDOA inaccuracies will be displayed.

6. REFERENCES
[1] C. Panayi, Transponder Position Monitoring using Multilateration, University of Pretoria,
Pretoria, Final Year Project 2011.
[2] M. C. Stevens, Secondary Surveillance Radar, Artech House, 1998.
[3] ERA Corporation. (2008, March) Multilateration & ADS-B Executive Reference Guide.
Document.
[4] B. Friedlander, A Passive Localization Algorithm and Its Accuracy Analysis, IEEE Journal
of Oceanic Engineering, vol. 12, no. 1, pp. 234-245, January 1987.
[5] R. Bucher, A synthesizable low power VHDL model of the exact solution of three
dimensional hyperbolic positioning systems, Proceedings of international Conference on
Modeling and Simulation of Microsystems, pp. 225-228, 2002.
[6] M. Gillette and H. Silverman, "A linear closed-form algorithm for source localization from
time-difference of arrival", IEEE Signal Process. Lett., vol. 15, pp.1 -4 2008
[7] M. Stevens, Multipath and interference effects in secondary surveillance radar systems,
Communications, Radar and Signal Processing, IEE Proceedings F, vol. 128, no. 1, pp. 43-53,
Feb 1981
[8] P.J. Martone and G.E. Tucker, Candidate requirements for Multilateration and ADS-B
systems to serve as alternatives to secondary radar, in Digital Avionics Systems, 2001. DASC.
20th Conference, 2001,pp. 7C2/1-7C2/12.
[9] ICAO Asia and Pacific Office, Multilateration (MLAT) Concept of use, International Civil
Aviation Organization, 2007.