1. SWIM-SUIT prototype architecture Dario Di Crescenzo / SELEX Sistemi Integrati Georg Trausmuth / FREQUENTIS

2. SWIM-SUIT Prototype ATM Virtual Information Pool AVI POOL AOC MXP AIRPORT Heathrow CDM ISPOC Prototype ATFCM (CFMU) ACC/APP ACC Flight Simulator FMS EAD USA SWIM 09/12/2009 SWIM-SUIT User Forum, Rome 2/39

3. The overall picture (1/2) The SWIM BOX acts as a gateway among different sites The SWIM BOX acts as a gateway among different sites The Adapter translates data/services among Legacy and SWIM-BOX The Adapter translates data/services among Legacy and SWIM-BOX 3/39 SWIM-SUIT User Forum, Rome 09/12/2009

4. The overall picture (2/2) ATM System A ATM System B ATM System N SWIM- BOX A SWIM- BOX B SWIM- BOX N Data Exchange Adapter AAdapter BAdapter N Common Infrastructure Each Adapter in the picture might be further decomposed in different adapters dedicated to the served “Data Domains” (they will be detailed later) Each Adapter in the picture might be further decomposed in different adapters dedicated to the served “Data Domains” (they will be detailed later) 4/39 SWIM-SUIT User Forum, Rome 09/12/2009

5. SWIM Box revisited Base Components: middleware, shared data store, registry, security,.. Data Domain Components: FDD, SDD, AID,.. 5/39 SWIM-SUIT User Forum, Rome Data DomainsCore Services 09/12/2009

6. Interaction patterns Request/Reply –Supported by Web Services (basically a synchronous access) Publish/Subscribe –Supported by JMS/DDS (asynchronous access) The technology choice must be driven by the requirements (in turn driven by the operational concepts) on a domain basis –In SWIM-SUIT the chosen technologies (supporting both patterns) are fitting requirements on the considered domains – this might not be true for every domain 6/39 SWIM-SUIT User Forum, Rome Data DomainsCore Services 09/12/2009

7. 7/39 SWIM-BOX (logical) Application Server SWIM-BOX DDS / JMS Application Server FDD (logical) Web Services Core (logical) PubSubService Middleware RegistryService SDD (logical) Overall Structure AID (logical) SharedDataStoreService SecurityMediator RequestReplyService SWIM-SUIT User Forum, Rome Data DomainsCore Services 09/12/2009

8. Design Principles Standard based approach avoiding unnecessary domain specific functions. Decouple external adapters from internal knowledge about the SWIM implementation. Accept overheads incurred because of XML data modelling at the interface level. Establish programming language independence. 8/39 SWIM-SUIT User Forum, Rome Data DomainsCore Services 09/12/2009

9. 9/39 SWIM-BOX Core The SWIM-BOX Core has no knowledge of the data representation it manages It provides services for data delivery and QoS management (in different technologies for each pattern – pub/sub or req/reply) It is loosely impacted by changes in the data representation and by changes in the services exposed in the SWIM Data Domains (act as much as possible as a transport layer) SWIM Data Domain Interfaces and Wire Interfaces follow established standards SWIM-SUIT User Forum, Rome Data DomainsCore Services 09/12/2009

10. Some details on core services (1/2) Security Mediator –Provides encryption services –Provides access control –Authentication via Digital Certificates –Hidden to the clients Registry –Basis for “pure” SOA approach –Provides standard interface (currently subset of UDDI) –It is a “distributed” implementation (each SWIM-BOX has a local registry – all are synchronized) to avoid single point of failure and simplify client access (it does not have to care about physical location of the registry) 10/39 SWIM-SUIT User Forum, Rome Data DomainsCore Services 09/12/2009

11. Some details on core services (2/2) Publish/Subscribe Service –Provides an abstraction layer hiding data distribution technology to the clients –Allows data distribution with different technologies (currently JMS and DDS – one COTS already “integrated”, a second is foreseen) and QoS Shared Data Store –Provides a transparently distributed transactional and (optionally) persistent shared cache –Provides location transparency to the clients (object stored in the data store are automatically synchronized among data store instances) –Automatic discovery 11/39 SWIM-SUIT User Forum, Rome Data DomainsCore Services 09/12/2009

12. SWIM Data Domains Offer generic (but “standard”) services for their specific domain and offer some extra management service Define a “standard” data representation and translate it in a flexible format (XML in the prototype) On a domain basis, manage the roles taking into account a subset of data Provide facilities for consuming services exposed by the adapters\legacies through the SWIM-BOX For the prototype three Data Domains are implemented: –FDD (Flight Data Domain) –SDD (Surveillance Data Domain) –AID (Aeronautical Information Service Domain) 12/39 SWIM-SUIT User Forum, Rome FDD SDDAID Data DomainsCore Services 09/12/2009

13. Flight Data Domain (FDD) The FDD component of SWIM-SUIT enables data distribution of flight data (i.e. Flight Objects) while also taking in charge a subset of “application responsibilities” in order to simplify application tasks It embraces well defined models and collaborative approaches (i.e. FOIPS, ICOG2) while providing specific extensions 13/39 SWIM-SUIT User Forum, Rome SDDAIDFDD 09/12/2009

14. The Flight Object It can be seen as a single entity comprising different information related to a flight SWIM-SUIT User Forum, Rome FLIGHT IDENTIFICATION FLIGHT KEY DEPARTURE ARRIVAL SCRIPT TRAJECTORY …. Information are “clusterised” in self-consistent parts When having to share information to the interested parties, just clusters are distributed (they are therefore called “Distribution Clusters”) 14/39 SDDAIDFDD 09/12/2009

15. Flight Data Domain roles Manager –Collects the partial contribution from the Contributors to compute a coherent data D. –Distributes the coherent data D to the other stakeholders. Contributor –Sets the value to a subset of the information constituting the data D. –Passes the new value of a topic of D to the Manager for partial contribution. –Consumes the updates of D. User –Subscribes to a published data D or to a part thereof. –Consumes the updates of D. SWIM-SUIT User Forum, Rome 15/39 SDDAIDFDD 09/12/2009

16. FDD Payload Data Model Payload data is defined in separate XML Schema files Conforms to the Flight Object XML PSM (Platform Specific Model) 16/39 SWIM-SUIT User Forum, Rome SDDAIDFDD 09/12/2009

17. FDD Interaction patterns doSomething() > Publish updated info Some elaboration 17/39 SWIM-SUIT User Forum, Rome SDDAIDFDD 09/12/2009

18. FDD Component responsibilities It provides generic services to the Adapters on Flights (many derived from ICOG). Manages the Roles defined in the FDD collaboration (Manager, Contributor, User) Provides Flight Objects (as defined in ICOG) caching Provides filtering capabilities Manages the distribution list (the list of actual users of the Flight Object) Dispatches request/data to the right recipients Provides pull/push data access (asynchronous notification or synchronous request) 18/39 SWIM-SUIT User Forum, Rome SDDAIDFDD 09/12/2009

19. FDD Interface Definition Interface definition in Web Service Description Language (WSDL) Interface is language independent –can be used from any platform that supports SOAP web service calls –protocol stacks supported by Linux, Microsoft Windows, etc. Requires a well known interface on client side for data notification and interaction 19/39 SWIM-SUIT User Forum, Rome SDDAIDFDD 09/12/2009

20. SWIM-Box FDD-Adapter communications SOAP/HTTP(S) PubSub Shared DS Security JAX-WS FDD WS Interface SOAP/HTTP(S) PubSub Shared DS Security JAX-WS FDD WS Interface SOAP/HTTP(S) “VIRTUAL INTERFACE” (APP-ICD) Authentication Authorization Encryption (XML Encryption) Technology: Web Service (SOAP over HTTP[s]) Technology: Web Service (SOAP over HTTP[s]) Authentication Authorization Decryption When Invoking the interface “doSomething” the actual operation invoked is “requestFOService(‘doSomething’)” Technology (Req/Rep): Web Service (SOAP over HTTP[s])

21. SWIM-Box FDD-Adapter communications SOAP/HTTP(S) PubSub Shared DS Security JAX-WS FDD WS Interface PubSub Shared DS Security JAX-WS FDD WS Interface SOAP/HTTP(S) Encryption (XMLEncryption) Technology (Pub/Sub): JMS or DDS Technology (Req/Rep): Web Service (SOAP over HTTP[s]) Technology: Web Service (SOAP over HTTP[s]) Decryption

22. Surveillance Data Domain Services SDD 22/39 SWIM-SUIT User Forum, Rome FDDSDDAID 09/12/2009

23. Surveillance Data Domain (SDD) The SDD component of SWIM-SUIT enables data distribution of aircraft positions (surveillance data). A tracker system can selectively push information out to legitimate subscribers 23/39 SWIM-SUIT User Forum, Rome FDDAIDSDD 09/12/2009

24. Surveillance Data Domain (SDD) The SDD component of SWIM-SUIT enables data distribution of aircraft positions (surveillance data). A tracker system can selectively push information out to legitimate subscribers 24/39 SWIM-SUIT User Forum, Rome FDDAIDSDD Publish/Subscribe Wikipedia: Publish/subscribe (or pub/sub) is a messaging paradigm, where senders (publishers) post messages to specific topics without knowledge of what (if any) subscribers there may be, and subscribers express interest in one or more topics, and only receive messages that are of interest, without knowledge of what publishers there are. 09/12/2009

25. Surveillance Data Domain (SDD) The SDD component of SWIM-SUIT enables data distribution of aircraft positions (surveillance data). A tracker system can selectively push information out to legitimate subscribers 25/39 SWIM-SUIT User Forum, Rome FDDAIDSDD Push Subscriptions Subscribers receive messages asynchronously, i.e. as soon as a new message (to a subscribed topic) is received. For this aim they must implement a call-back function. Notify Middle- ware Subscriber 09/12/2009

26. Surveillance Data Domain (SDD) The SDD component of SWIM-SUIT enables data distribution of aircraft positions (surveillance data). A tracker system can selectively push information out to legitimate subscribers 26/39 SWIM-SUIT User Forum, Rome FDDAIDSDD Pull Subscriptions Subscribers receive messages synchronously, i.e. the subscriber regularly polls for new messages that are cached (until consumed). Middle- ware Subscriber Polling 09/12/2009

27. SDD Design Principles Encapsulate transport level publish/subscribe technology (e.g. DDS, JMS) and provide access via web services. 27/39 SWIM-SUIT User Forum, Rome FDDAIDSDD 09/12/2009

28. SDD Interface Definition Interface definition in Web Service Description Language (WSDL) Interface is language independent –can be used from any platform that supports SOAP web service calls –protocol stacks supported by Linux, Microsoft Windows, etc. –could also be built from scratch using primitive HTTP library 28/39 SWIM-SUIT User Forum, Rome FDDAIDSDD 09/12/2009

29. SDD in Relation to Standard Web Services Using W3C & OASIS Web Service Standard Operations to interface with SDD of SWIM-Box Relevant Standards –WS-Addressing –WS-Notification –WS-Topics 29/39 SWIM-SUIT User Forum, Rome FDDAIDSDD 09/12/2009

30. SDD Payload Data Model Payload data is defined in separate XML Schema files ASTERIX Category 62 XML data structure supporting either binary data or XML structure or both 30/39 SWIM-SUIT User Forum, Rome FDDAIDSDD 09/12/2009

31. Aeronautical Information Domain Services AID 31/39 SWIM-SUIT User Forum, Rome FDDSDDAID 09/12/2009

32. Aeronautical Information Domain (AID) The AID supports 3 different types of information retrieval services: Web Service „SDO Query“ Web Service „Reporting Management“ Basic Web Feature Service for retrieving geo-data All of the services implement the request/reply pattern. 32/39 SWIM-SUIT User Forum, Rome FDDSDDAID 09/12/2009

33. Aeronautical Information Domain (AID) The AID supports 3 different types of information retrieval services: Web Service „SDO Query“ Web Service „Reporting Management“ Basic Web Feature Service for retrieving geo-data All of the services implement the request/reply pattern. 33/39 SWIM-SUIT User Forum, Rome FDDSDDAID Web Service Web services provide a standard means of interoperating between different software applications, running on a variety of platforms and/or frameworks. Web services are characterized by their great interoperability and extensibility, as well as their machine-processable descriptions thanks to the use of XML. They can be combined in a loosely coupled way in order to achieve complex operations. 09/12/2009

34. EAD Web Services Partial mapping of ESI functions to web services accessible via SOAP SDO Data User: –The SDO Query Service is used to retrieve information from and EAD. –The Reporting Management Service is used to list available reports, query for report definitions and execute predefined reports. 34/39 SWIM-SUIT User Forum, Rome FDDSDDAID 09/12/2009

35. Web Feature Service Overview The OpenGIS Web Feature Service Interface Standard (WFS) defines an interface for specifying requests for retrieving geographic features across the Web using platform- independent calls. The WFS standard defines interfaces and operations for data access and manipulation on a set of geographic features. 35/39 SWIM-SUIT User Forum, Rome FDDSDDAID 09/12/2009

36. Proxy approach supported by SWIM-Box Request/Reply Dialog between client system and provider is transparently routed through the SWIM-SUIT environment and network Proxy components provide access end points on the local „SWIM-Box“ and hide details of message routing/forwarding. Virtual end-to-end connection to enforce security policies and location transparency 36/39 SWIM-SUIT User Forum, Rome FDDSDDAID 09/12/2009

37. SWIM-Box Proxies 37/39 SWIM-SUIT User Forum, Rome FDDSDDAID 09/12/2009

38. WFS Payload: GML The OpenGIS® Geography Markup Language Encoding Standard (GML) is an XML grammar for expressing geographical features. AID Payload is defined by flattened AIXM5 alike model that has been developed by Eurocontrol and also been used for other projects, e.g. X-Notam Trial. –Flattened AIXM5 (so-called AIXM-WFS) had to be developed based on requirements imposed by COTS viewers 38/39 SWIM-SUIT User Forum, Rome FDDSDDAID 09/12/2009

39. Summary FDD provides publish/subscribe on top of the SWIM-Box services, roles/ownership management, subscribers discovery, distribution list definition SDD supports publish/subscribe on top of the SWIM-Box services. AID provides transparent access to services accessible via the SWIM infrastructure. –Support of request/reply Security and access control is enforced between SWIM- Boxes. 39/39 SWIM-SUIT User Forum, Rome 09/12/2009

40. Questions and Feedback http://www.swim-suit.aero/swimsuit/