SWIM Technical Infrastructure (ATC-ATC and EAD Profiles)

Transcription

1 SWIM Technical Infrastructure (ATC-ATC and EAD Profiles) D. Di Crescenzo SELEX Consortium F. Pérez Alamillo Indra H. Souami Thales H. Milchrahm FREQUENTIS

2 ATC (MUAC) NM NOP ATC (Coflight) SWIM infrastructure SWIM Profiles One solution does not fit all ATC (itec) Airport Different types of SWIM usage / needs Map SWIM needs with potential set of supporting technologies & services options WS Clients (AOC,GA AIS, ) EAD SWIM Step1 profiles FO/IOP Profile NOP/B2B Profile EAD/B2B Profile Multi Technologies 7

3 SWIM Technical Infrastructure Segmentation (i.e. Profiles) One solution and certainly not one technology will suit all. Different stakeholders, based on their business needs, may not have the same requirements for SWIM. SWIM profiles are needed to classify different types of SWIM usage permitting and to map the SWIM requirements with the potential set of supporting technologies and services options. SWIM Profiles are also used to assemble SWIM middleware functionality into coherent right-sized solutions that meet the needs of the stakeholder systems. 8

4 Service needs driving Profile definition 9 Offered Infrastructure Required Infrastructure

5 APP D APP A APP C SWIM Node A SWIM Node C SWIM infrastructure SWIM Node B APP B SWIM Node Capabilities Messaging Security (opt) Recording Loc. Supervision (opt) High availability Interface management SWIM Core Capabilities Supervision Security Registry Max. use of Commercial Of-The The-Shelf (COTS) products 10

6 Governance Design Time Service Consumer implementation (3) Regulation Discovery (5) Service Discovery SWIM REGISTRY (1) Regulation Publication (2) Oversight (3) Regulation Discovery (4) Service Publication Service Provider implementation Run Time SWIM Infrastructure 11

7 Supervision as federated capability in the SWIM environment 3 levels initially foreseen (Local, Sub-Regional, Regional) Still subject to open discussions 12

8 ATC-ATC Profile Overview SWIM (Middleware) perspective Architecture & Technologies Capabilities Interfaces Others 13

9 Need to ensure a consistent view of the flight data between ATM systems. It is intended to satisfy current operational needs including the European Commission Regulation (No 1032/2006) relating to notification, coordination and transfer of flights between air traffic control units, as well as to provide the basis for future operational concepts. icog projects dealing with it Ground Industry, wide range of ANSPs and ECTRL on board. An EUROCAE standard as a result: ED-133 FLIGHT OBJECT INTEROPERABILITY SPECIFICATION 14

10 Sharing Flight Object (FO) information during the execution phase of the flight between ATC systems Each ATC system is both provider and consumer of services Technologies have to accommodate near real-time (e.g. requests for coordination to be served within 1 sec.) and criticality (i.e. Safety, Security, Availability, ) The initial work for ATC-ATC profile starts from: Standard defined at EUROCAE (ED FLIGHT OBJECT INTEROPERABILITY SPECIFICATION) Open standards available from the SOA or OMG world that provide interoperability COTS products 19

11 The definition is not looking for a unique fixed way to implement the ATC-ATC SWIM profile but setting the needed requirements for making them interoperable. Two prototypes are developed by using different open standard based COTS/OSSs whenever possible (solution needed to be vendor independent) in order to support the validation exercise The ATC-ATC SWIM profile provides a set of needed capabilities allows a better sharing and accuracy of Flight information. is not linked to application services (changes to App Services doesn t mean changing ATC-ATC SWIM profile. 20

12 ATC Backend System System A SWIM Technical Access Sublayer SWIM Tech. Added value Sublayer Security Supervision Interface Management High Availability Messaging Recording 21

13 Internal protocol(s) to expose/access services System A SWIM Technical Access Sublayer SWIM Tech. Added value Sublayer Security Supervision Interface Management High Availability Messaging Recording 22

14 Shared object (currently just Flight Object) System A SWIM Technical Access Sublayer SWIM Tech. Added value Sublayer Security Supervision Interface Management High Availability Messaging Recording 23

15 System A SWIM Technical Access Sublayer SWIM Tech. Added value Sublayer Security Supervision Digital Signatures, SSL Interface Management High Availability Not prototyped Messaging Recording SOAP over HTTP/HTTPS & DDS 24

16 System A SWIM Technical Access Sublayer SWIM Tech. Added value Sublayer Security Supervision Monitoring & Statistics Interface Management High Availability Not prototyped Messaging Recording ESB Basic Features 25

17 Run-time Container including Request/Reply Product: Servicemix ESB, JBoss ESB Technologies: ext: SOAP via HTTP/HTTPS, int: CXF (WS Framework), OSGI, JBI Data Distribution Service Product: OpenSplice DDS, RTI DDS Technologies: ext: OMG DDS int: OSGI, JBI Local supervision Product: RedHat RHQ Technologies: int: Database, Application Server Security Product: EjbCA Technologies: ext: X509 certificates 26

18 Open standards Web Services: WS-I basic profile V1.1 Data Distribution Service: DDS V1.2, DDS-I v2.1 Security Transport Layer Security: TLS V1.1 Mutual authentication using X509 certificates 27

19 Example of Services enabled, so far, by this profile modify_route This service allows a contributor to modify a given section of a route. set_coordination_and_transfer_data This service allows a contributor to update active coordination related information related to a coordination status modify_constraints This service allows a contributor to modify either the list of accepted constraints or list the of rejected constraints set_next_ssr This service allows a contributor to modify the SSR code it will allocate to the flight. set_star This service allows a contributor to change the STAR. 28

20 EAD Profile Overview EAD (European AIS Database) EAD Profile Requirements MEP: Publish / Subscribe and Request / Response EAD SWIM Node Implementation Specifics (WS-Notification) EAD Services 29

21 European Aeronautical Information System Database SDO (Static Data Operation) INO DU (International NOTAM Operation Data User) INO DP (International NOTAM Operation Data Provider) PAMS (Published AIP Management System) 30

22 EAD Profile Requirements Generic Publish/Subscribe used to distribute Digital NOTAMS Standardised Data Format AIXM 5.1 (XML) Information represented in accordance with the modelling of WP8 31

23 MEP: Publish / Subscribe: Interactions (Push & Pull) 32

24 EAD Logical Decomposition 33

25 EAD Interfaces SWIM Node = AIM B2B MEP Request / Response & MEP Publish / Subscribe 34

26 EAD SWIM Node 35

27 EAD SWIM Node 36

28 WS Notification Standards (WS-N) WS-Notification Web Services Base Notification 1.3 (WS-BaseNotification) OASIS Standard, 1 October 2006 WS-BrokeredNotification Web Services Brokered Notification 1.3 (WS-BrokeredNotification) OASIS Standard, 1 October 2006 WS-Topics Web Services Topics 1.3 (WS-Topics) OASIS Standard, 1 October 2006 Related Standards: WS-Resource WS-Addressing WS-Security WS-ReliableMessaging 37

29 EAD Services available at the Moment PAMS (Published AIP Management System) Document Family PAMS Search PAMS Download INO DU (International NOTAM Operation Data User) Single NOTAM Retrieval PIB Generation NOTAM Summary SDO (Static Data Operation) Download INO DP (International NOTAM Operation Data Provider) Maintain NOTAM 38

30 39