1 ICAO ACP WG-N meeting Use of IP in ARTAS 3 rd July 2006 European Organisation for the Safety of...
-
Upload
mary-barker -
Category
Documents
-
view
213 -
download
0
Transcript of 1 ICAO ACP WG-N meeting Use of IP in ARTAS 3 rd July 2006 European Organisation for the Safety of...
1
ICAO ACP WG-N meeting Use of IP in ARTAS
3rd July 2006
European Organisation for the Safety of Air Navigation
2
ARTAS
ARTAS (ATM Radar Tracker and Server) is conceived as a distributed system composed of a number of identical sub-systems, each with their own domain of Operation, co-operating together.
Each sub-system, called an ARTAS Unit, will process all surveillance data reports - at present, these are classical radar reports and, in the future, Mode S and ADS reports as well - so as to form the best estimate of the current air traffic situation.
3
ARTAS – Current Environment
Surveillance - Current Environment
HD19189_1003
SecondarySurveillanceRadar (SSR)
Mode A/C
Voice Position Reports
Primary Radar
Air TrafficManagement
Requirements defined by EUROCONTROL Radar Standard
4
ARTAS Future environment
S u r v e i l l a n c e - F u t u r e E n v i r o n m e n t
H D 1 9 1 8 9 _ 1 0 0 4
S S R M o d e SA D S v i a o t h e r
D a t a L i n k
S a t e l l i t e A D S
A i r T r a f f i c
M a n a g e m e n t
5
ARTAS Technical Environment
Mode-SSub-network
ADSSub-network
SADS
Regional Wide Area Network
ATC users ARTAS
ATC Centre
MilitaryATC Centre
ATC CentreATC users ARTAS
Sensor dataAirSituation Picture
ATC Centre
Router
6
ARTAS Deployment1/2
OperationalAdministration # Centres Version H/W Status Operational #
1 SCHIPHOL V6B2 DS10 OPE 15/05/2003 1- SCHIPHOL V7A1 DS10 N/A Jan-062 MAASTRICHT V6B2 XP1000 OPE 11/02/2003 22 MAASTRICHT V7A0 DS15 OPE 02/11/2005 3
NAV 3 LISBON V6B2 DS10 OPE 15/01/2004 44 GENEVA V6B2 DS10 OPE 13/01/2004 55 ZURICH V6B2 DS10 OPE 10/02/2004 6
BELGOCONTROL
6 BRUSSELS V6B2 DS10 OPE 03/05/2004 7
7 SHANNON APP V6B2 XP1000 OPE 02/12/2003 87 SHANNON ACC V6B2 XP1000 OPE 26/02/2004 88 DUBLIN V6B2 XP1000 OPE 22/05/2004 9
ATSA 9 SOFIA V6B2 DS10 OPE 22/01/2005 10LPS 10 BRATISLAVA V6B2 DS10 OPE 01/06/2005 11GAF 11 NEUBURG V6B2 DS10 OPE 10/06/2005 12ANS CZECH 12 PRAGUE V7A0 DS10 OPE Sep-05 13CCL 13 ZAGREB V6B2 DS10 OPE 28/12/2005 14DSNA 14 ATHIS – MONS V7A0 DS10 OPE 09/05/2006 15NAVAIR 15 COPENHAGEN V6B2 DS10 OPE 12/07/2006 16
LVNL
UAC
SKYGUIDE
IAA
7
ARTAS Deployment2/2
Pre-operationalAdministration # Centres Version H/W Status OperationalRNLAF 1 NIEUW MILLIGEN V7A0 DS10 PIL --/06/2005
DSNA 2 CDG V7A0 DS10 PIL --/--/2007AUSTROCONTROL
3 VIENNA V7A0 DS15 PIL --/11/2005
CYPRUS 5 NICOSIA V7A1 DS15 PIL --/12/2006SLOVENIA 6 V7A1 LXG4 PIL --/--/2006GAF 7 V7A1 LXG4 PIL --/--/2006NAV 8 ST MARIA V6B2 DS10 PIL --/--/2005LFV 9 MALMOE V7A1 DS10 --/--/2007LFV 10 STOCKHOLM V7A1 DS10 --/--/2007DFS 11 LANGEN V7A1 LXG4 PILFYROM 12 SKOPJAROMANIA 13 BUCUREST
CRISTALAdministration # Centres Version H/W StatusAUSTROCONTROL
1 WIEN V7A1 DS10 PIL
LFV 2 ORLANDA V7A1 DS10 PILIAA 3 V7A1 DS10 PILNATS 4 LONDON? V7A1 DS15 PILNAV 5 LISBON V7A1 DS15 PILIAA 6 V7A1 DS15 PILAENA 7 MADRID V7A1 DS15 PILHCAA 8 ATHENS V7A1 DS15 PILLVNL 9 Schiphol V7A1 ? PILEEC 10 BRETIGNY V7A1 DS10 PIL
ARTAS System presentation
Sensor inputSensor input
Broadcast users
Users
Adjacent Unit
Sensor input
Users
Adjacent Unit
Broadcast users
SNM
P, NTP
SNM
P, N
TP
Internal LAN (Dual Eth. HUBorDual FDDI Conc.)
ARTAS System presentation (cont’d)
MMS node
SRV node
RBR node
TRK node
REC node
Sensor input
Broadcast users
MMS node
SRV node
RBR node
TRK node
REC node
Sensor input
Users
Adjacent Unit
Users
Adjacent Unit
Broadcast users
SNM
P, NTP
SNM
P, N
TP
11
Router Bridge
ARTAS System presentation (cont’d)
• The Router Bridge is the only OP CSCI interfacing with the external world.
• The RBR can use up to 6 LANs.
• Only the first 2 can be used for Sensor Input.
• Max 23 USER simultaneously ( 20 Ordinary Users and 3 Adjacent Units or 12 Adjacent Units and 11 Ordinary Users)
Point-to-Point USER LAN
SUPERVISION LAN
RADAR LAN B
RADAR LAN A
BROADCAST LAN
NTP LAN
12
Protocols used in ARTAS
TCP: The RFC 793 IP: RFC 761 Multicast Host Extensions for IP multi-casting: RFC 1112 UDP: RFC 768 PDC (Private Data Channel) NTP: RFC 1305 SNMP: RFC1157
13
SENSOR INPUT
ARTAS supports up two RADAR LANs.
Secondary LAN
Preferred LAN
FDDI (except with V7A1 Linux) and Ethernet LANs are supported.
14
SENSOR INPUT
Sensor information is a multicast message.
There are two possible protocol stacks:
Only one protocol stack has to be used.
ETHERNET or FDDI
MAC/LLC1
<not used>
ASTERIX
ÌP
UDP
<not used>
ETHERNET or FDDI
MAC/LLC1
<not used>
ASTERIX
<not used>
<not used>
<not used>
UDP/IP MAC/LLC1
15
SENSOR INPUT
001 Plots-Local tracks002 Radar Service Messages034 Radar Service Messages*048 Plots-Local tracks*021 ADS−B message**023 CSN/ATM ground station service message**241 RMCDE PROTOCOL
* Mode-S stations** ADS-B Ground stationsETHERNET or FDDI
MAC/LLC1
<not used>
ASTERIX
ÌP
UDP
<not used>
ETHERNET or FDDI
MAC/LLC1
<not used>
ASTERIX
<not used>
<not used>
<not used>
ASTERIX CAT used:
16
Normal USER connection
FPPS USERSUSERS
The Private Data Channel ( PDC) protocol is on top of TCP layer.
ARTAS SYSTEM
ARTAS
Normal Users are connected through a POINT-TO-POINT connection
17
Normal USER connection
FPPS USERS USERS
ARTAS
ETHERNET or FDDI
MAC/LLC1
<not used>
ASTERIX
ÌP
TCP
PDC
18
Normal USER connection
FPPS USERSUSERS
ARTAS SYSTEM
ARTAS
FDPS032 MINIPLAN messages062 Track information065 Service related messages252 Service related messages
Other Normal users062 Track information065 Service related messages063 Sensor information252 Service related messages030 Track information 030 Sensor information
ASTERIX CAT used:
19
Adjacent Unit connection
ARTAS UNIT A
ARTAS UNIT B
Adjacent units are connected through a POINT-TO-POINT connection
WAN
The Private Data Channel ( PDC) protocol is on top of TCP layer.
20
Adjacent Unit connection
ARTAS UNIT A
WAN
ARTAS UNIT B
ASTERIX CAT used:
ETHERNET or FDDI
MAC/LLC1
<not used>
ASTERIX
ÌP
TCP
PDC
032 MINIPLAN messages062 Track information065 Service related messages252 Service related messages
21
Broadcast Service
Working position
Working position
ARTAS
ARTAS Tracks
Multicast message
Two protocol stacks
MAC/LLC1UDP/IP
22
Broadcast Service
Working position
Working position
ARTAS
MAC/LLC1
UDP/IP
ETHERNET or FDDI
MAC/LLC1
<not used>
ASTERIX
ÌP
UDP
<not used>
ETHERNET or FDDI
MAC/LLC1
<not used>
ASTERIX
<not used>
<not used>
<not used>
23
Broadcast Service
Working position
Working position
ARTAS
ASTERIX CAT used:062 Track information065 Service related messages063 Sensor information
252 Service related messages030 Track information 031 Sensor information
24
“IPAX Compliance”: A destination port uniquely identifies the application in the receiving system that should process the incoming IP packets.
ARTAS Requirement: There shall be a default port number* (configurable by means of an MMS parameter) that is written initially to the fields “Port 1” to “Port 4”. For backwards compatibility an operator can choose to change this default port number according to his needs (in the range of [1024, 65535]).
Implementation: A sensor is not any longer identified by a PORT NUMBER and there is DEFAULT PORT NUMBER for ALL RADARS.
*The default port number would be the port number for ASTERIX in receiving systems.
‘IPAX COMPLIANCE’
28
ARTAS non-Sensors Environment
Unique IP PORT NUMBER for the output. At the moment the UDP ports must be in the range [5001,65535]
ARTAS SYSTEM
29
IPv6
ARTAS is only validate for IPV4.
IPV6