Presentation on theme: "ICAO ACP WG-N meeting Use of IP in ARTAS"— Presentation transcript:
1ICAO ACP WG-N meeting Use of IP in ARTAS 3rd July 2006European Organisation for the Safety of Air Navigation
2ARTASARTAS (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.
8ARTAS System presentation SNMP, NTPSNMP, NTPSensor inputSensor inputSensor inputUsersUsersAdjacent UnitAdjacent UnitA complete Artas system is composed of :10 stations,2 FDDI hubs,2 X terminals,4 external disks,2 tape drivers,Broadcast usersBroadcast users
9ARTAS System presentation (cont’d) Internal LAN(Dual Eth. HUBorDual FDDI Conc.)MMS nodeMMS nodeSRV nodeSNMP, NTPSNMP, NTPSRV nodeSensor inputSensor inputRBR nodeRBR nodeUsersUsersAdjacent UnitAdjacent UnitTRK nodeA complete Artas system is composed of :10 stations,2 FDDI hubs,2 X terminals,4 external disks,2 tape drivers,TRK nodeBroadcast usersREC nodeBroadcast usersREC node
10ARTAS System presentation (cont) System ManagerRecording(DISK)On-lineDynamic andStaticDatabasesTrackerServerRouter BridgePlots Local TracksSystem TracksAdjacent ARTAS UnitsSensorsUsers
11ARTAS 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 BridgeRADAR LAN ARADAR LAN BBROADCAST LANNTP LANSUPERVISION LANPoint-to-Point USER LAN
12Protocols used in ARTAS TCP: The RFC 793IP: RFC 761Multicast Host Extensions for IP multi-casting: RFC 1112UDP: RFC 768PDC (Private Data Channel)NTP: RFC 1305SNMP: RFC1157
13SENSOR INPUT ARTAS supports up two RADAR LANs. Preferred LAN Secondary LANFDDI (except with V7A1 Linux) and Ethernet LANs are supported.
14SENSOR INPUT Sensor information is a multicast message. There are two possible protocol stacks:ETHERNET or FDDIMAC/LLC1<not used>ASTERIXÌPUDPETHERNET or FDDIMAC/LLC1<not used>ASTERIXUDP/IP MAC/LLC1Only one protocol stack has to be used.
15SENSOR INPUT ASTERIX CAT used: 001 Plots-Local tracks 002 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 FDDIMAC/LLC1<not used>ASTERIXÌPUDPETHERNET or FDDIMAC/LLC1<not used>ASTERIX
16Normal USER connection Normal Users are connected through a POINT-TO-POINT connectionThe Private Data Channel ( PDC) protocol is on top of TCP layer.ARTASARTAS SYSTEM
17Normal USER connection ETHERNET or FDDIMAC/LLC1<not used>ASTERIXÌPTCPPDCARTAS
18Normal USER connection ASTERIX CAT used:FDPS032 MINIPLAN messages062 Track information065 Service related messages252 Service related messagesOther Normal users062 Track information065 Service related messages063 Sensor information252 Service related messages030 Track information030 Sensor informationARTASARTAS SYSTEM
19Adjacent Unit connection Adjacent units are connected through a POINT-TO-POINT connectionThe Private Data Channel ( PDC) protocol is on top of TCP layer.ARTAS UNIT BARTAS UNIT AWAN
20Adjacent Unit connection ARTAS UNIT BARTAS UNIT AWANETHERNET or FDDIMAC/LLC1<not used>ASTERIXÌPTCPPDCASTERIX CAT used:032 MINIPLAN messages062 Track information065 Service related messages252 Service related messages
21Broadcast Service ARTAS Tracks Multicast message Two protocol stacks UDP/IPMAC/LLC1ARTAS
22Broadcast Service MAC/LLC1 UDP/IP ARTAS ASTERIX ASTERIX ETHERNET or FDDIMAC/LLC1<not used>ASTERIXÌPUDPETHERNET or FDDIMAC/LLC1<not used>ASTERIXMAC/LLC1UDP/IPARTAS
23Broadcast Service ASTERIX CAT used: 062 Track information 065 Service related messages063 Sensor information252 Service related messages030 Track information031 Sensor informationARTAS
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.
26RADAR IDENTIFICATION SIC/SAC Alias of the SIC/SAC; Route preferred and Route secondaryPreferred LAN and Secondary LAN *4 Channels* The input coming from the secondary LAN is always received by ARTAS.
27RADAR IDENTIFICATION Channels definition Channel #1 = ( Preferred LAN, preferred route ); MULTICAST IP 1; PORT 1Channel #2 = ( Preferred LAN, secondary route ); MULTICAST IP 2; PORT 2Channel #3 = (Secondary LAN, preferred route ); MULTICAST IP 3; PORT 3Channel #4 = (Secondary LAN, secondary route); MULTICAST IP 4; PORT 4The 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.
28ARTAS non-Sensors Environment Unique IP PORT NUMBER for the output. At the moment the UDP ports must be in the range [5001,65535]