1 / 25

ICAO ACP WG-N meeting Use of IP in ARTAS

ICAO ACP WG-N meeting Use of IP in ARTAS. 3 rd July 2006. European Organisation for the Safety of Air Navigation. ARTAS.

skule
Download Presentation

ICAO ACP WG-N meeting Use of IP in ARTAS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  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 ATC users ARTAS ATC Centre ATC Centre Mode-S ADS Sub-network Sub-network ADS S Regional Wide Area Network Router Air Sensor data Military Situation Picture ATC Centre ATC users ARTAS ATC Centre

  6. ARTAS Deployment1/2

  7. ARTAS Deployment2/2

  8. ARTAS System presentation SNMP, NTP SNMP, NTP Sensor input Sensor input Sensor input Users Users Adjacent Unit Adjacent Unit Broadcast users Broadcast users

  9. ARTASSystem presentation (cont’d) Internal LAN (Dual Eth. HUB or Dual FDDI Conc.) MMSnode MMSnode SNMP, NTP SRVnode SNMP, NTP SRVnode Sensor input Sensor input RBRnode RBRnode Users Users Adjacent Unit Adjacent Unit TRKnode TRKnode Broadcast users RECnode Broadcast users RECnode

  10. 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

  11. 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

  12. SENSOR INPUT ARTAS supports up two RADAR LANs. Preferred LAN Secondary LAN FDDI (except with V7A1 Linux) and Ethernet LANs are supported.

  13. SENSOR INPUT ASTERIX ASTERIX <not used> <not used> <not used> <not used> UDP <not used> <not used> ÌP MAC/LLC1 MAC/LLC1 ETHERNET or FDDI ETHERNET or FDDI Sensor information is a multicast message. There are two possible protocol stacks: UDP/IP MAC/LLC1 Only one protocol stack has to be used.

  14. SENSOR INPUT ASTERIX ASTERIX <not used> <not used> <not used> <not used> <not used> UDP <not used> ÌP MAC/LLC1 MAC/LLC1 ETHERNET or FDDI ETHERNET or FDDI 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

  15. 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

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

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

  18. 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

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

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

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

  22. 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

  23. ‘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.

  24. ARTAS non-Sensors Environment • Unique IP PORT NUMBER for the output. At the moment the UDP ports must be in the range [5001,65535]

  25. IPv6 • ARTAS is only validate for IPV4.

More Related