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

4. ARTAS Future environment

5. ARTAS Technical Environment
Mode-S
Sub-network
ADS S
Regional Wide Area Network
ATC users
ARTAS
ATC Centre
Military
Sensor data
Air
Situation Picture
Router

6. ARTAS Deployment 1/2

7. ARTAS Deployment 2/2

8. ARTAS System presentation
SNMP, NTP
SNMP, NTP
Sensor input
Sensor input
Sensor input
Users
Users
Adjacent Unit
Adjacent Unit
A complete Artas system is composed of :
10 stations,
2 FDDI hubs,
2 X terminals,
4 external disks,
2 tape drivers,
Broadcast users
Broadcast users

9. ARTAS System presentation (cont’d)
Internal LAN
(Dual Eth. HUB or
Dual FDDI Conc.)
MMS node
MMS node
SRV node
SNMP, NTP
SNMP, NTP
SRV node
Sensor input
Sensor input
RBR node
RBR node
Users
Users
Adjacent Unit
Adjacent Unit
TRK node
A complete Artas system is composed of :
10 stations,
2 FDDI hubs,
2 X terminals,
4 external disks,
2 tape drivers,
TRK node
Broadcast users
REC node
Broadcast users
REC node

10. ARTAS System presentation (cont)
System Manager
Recording
(DISK)
On-line
Dynamic and
Static
Databases
Tracker
Server
Router Bridge
Plots Local Tracks
System Tracks
Adjacent ARTAS Units
Sensors
Users

11. 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)
Router Bridge
RADAR LAN A
RADAR LAN B
BROADCAST LAN
NTP LAN
SUPERVISION LAN
Point-to-Point USER 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. Preferred LAN
Secondary 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:
ETHERNET or FDDI
MAC/LLC1
<not used>
ASTERIX ÌP
UDP
ETHERNET or FDDI
MAC/LLC1
<not used>
ASTERIX
UDP/IP MAC/LLC1
Only one protocol stack has to be used.

15. SENSOR INPUT ASTERIX CAT used: 001 Plots-Local tracks
002 Radar Service Messages
034 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 stations
ETHERNET or FDDI
MAC/LLC1
<not used>
ASTERIX ÌP
UDP
ETHERNET or FDDI
MAC/LLC1
<not used>
ASTERIX

16. Normal USER connection
Normal Users are connected through a POINT-TO-POINT connection
The Private Data Channel ( PDC) protocol is on top of TCP layer.
ARTAS
ARTAS SYSTEM

17. Normal USER connection
ETHERNET or FDDI
MAC/LLC1
<not used>
ASTERIX ÌP
TCP
PDC
ARTAS

18. Normal USER connection
ASTERIX CAT used:
FDPS
032 MINIPLAN messages
062 Track information
065 Service related messages
252 Service related messages
Other Normal users
062 Track information
065 Service related messages
063 Sensor information
252 Service related messages
030 Track information
030 Sensor information
ARTAS
ARTAS SYSTEM

19. Adjacent Unit connection
Adjacent units are connected through a POINT-TO-POINT connection
The Private Data Channel ( PDC) protocol is on top of TCP layer.
ARTAS UNIT B
ARTAS UNIT A
WAN

20. Adjacent Unit connection
ARTAS UNIT B
ARTAS UNIT A
WAN
ETHERNET or FDDI
MAC/LLC1
<not used>
ASTERIX ÌP
TCP
PDC
ASTERIX CAT used:
032 MINIPLAN messages
062 Track information
065 Service related messages
252 Service related messages

21. Broadcast Service ARTAS Tracks Multicast message Two protocol stacks
UDP/IP
MAC/LLC1
ARTAS

22. Broadcast Service MAC/LLC1 UDP/IP ARTAS ASTERIX ASTERIX
ETHERNET or FDDI
MAC/LLC1
<not used>
ASTERIX ÌP
UDP
ETHERNET or FDDI
MAC/LLC1
<not used>
ASTERIX
MAC/LLC1
UDP/IP
ARTAS

23. Broadcast Service ASTERIX CAT used: 062 Track information
065 Service related messages
063 Sensor information
252 Service related messages
030 Track information
031 Sensor information
ARTAS

24. ‘IPAX COMPLIANCE’
“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.

25. RADAR DEFINITION

26. RADAR IDENTIFICATION SIC/SAC
Alias of the SIC/SAC; Route preferred and Route secondary
Preferred LAN and Secondary LAN *
4 Channels
* The input coming from the secondary LAN is always received by ARTAS.

27. RADAR IDENTIFICATION Channels definition
Channel #1 = ( Preferred LAN, preferred route ); MULTICAST IP 1; PORT 1
Channel #2 = ( Preferred LAN, secondary route ); MULTICAST IP 2; PORT 2
Channel #3 = (Secondary LAN, preferred route ); MULTICAST IP 3; PORT 3
Channel #4 = (Secondary LAN, secondary route); MULTICAST IP 4; PORT 4
The list order defines the priority amongst the four channels.
In ARTAS there is a mechanism that will always select the highest priority channel amongst those available.

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]

29. IPv6
ARTAS is only validate for IPV4.