Presentation on theme: "1 ICAO ACP WG-N meeting Use of IP in ARTAS 3 rd July 2006 European Organisation for the Safety of Air Navigation."— Presentation transcript:
1 ICAO ACP WG-N meeting Use of IP in ARTAS 3 rd 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
6 ARTAS Deployment 1/2
7 ARTAS Deployment 2/2
ARTAS System presentation Sensor input Broadcast users Users Adjacent Unit Sensor input Users Adjacent Unit Broadcast users SNMP, NTP
Internal LAN (Dual Eth. HUB or Dual FDDI Conc.) ARTAS System presentation (contd) 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 SNMP, NTP
10 Recording SensorsUsers (DISK) TrackerServer On-line Router Bridge System Manager Plots - Local Tracks System Tracks Dynamic and Static Databases Adjacent ARTAS Units ARTAS System presentation (cont)
11 Router Bridge ARTAS System presentation (contd) 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 ASTERIX ÌP UDP ETHERNET or FDDI MAC/LLC1 ASTERIX UDP/IP MAC/LLC1
15 SENSOR INPUT 001 Plots-Local tracks 002 Radar Service Messages 034 Radar Service Messages* 048 Plots-Local tracks* 021 ADSB message** 023 CSN/ATM ground station service message** 241 RMCDE PROTOCOL * Mode-S stations ** ADS-B Ground stations ETHERNET or FDDI MAC/LLC1 ASTERIX ÌP UDP ETHERNET or FDDI MAC/LLC1 ASTERIX ASTERIX CAT used:
16 Normal USER connection 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 ARTAS ETHERNET or FDDI MAC/LLC1 ASTERIX ÌP TCP PDC
18 Normal USER connection ARTAS SYSTEM ARTAS 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 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 ASTERIX ÌP TCP PDC 032 MINIPLAN messages 062 Track information 065 Service related messages 252 Service related messages
21 Broadcast Service ARTAS ARTAS Tracks Multicast message Two protocol stacks MAC/LLC1 UDP/IP
22 Broadcast Service ARTAS MAC/LLC1 UDP/IP ETHERNET or FDDI MAC/LLC1 ASTERIX ÌP UDP ETHERNET or FDDI MAC/LLC1 ASTERIX
23 Broadcast Service ARTAS ASTERIX CAT used: 062 Track information 065 Service related messages 063 Sensor information 252 Service related messages 030 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
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]