SWIM-SUpported by Innovative Technologies Antonio Strano 14/04/2010 SWIM-SUIT Overview

2 Outline SWIM concept SWIM-SUIT project –Objectives –Design Principles / requirements –SWIM-SUIT Prototype Architecture overview –Testing & Validation

3 SWIM concept (simplified) 3 SWIM aims to establish a seamless interoperability among heterogeneous ATM stakeholders –Need for common data representation –Need for a coherent view on current ATM information (e.g. Flight Data, Aeronautical Data, Weather..) It may be seen as a common data/service bus on which systems having to interoperate are “connected”

4 SWIM-SUIT project objectives Analyse the (SESAR) SWIM concept defining (high level) requirements Identify the right technologies Design and Implement the first SWIM prototype Validate the SWIM prototype capabilities in order to demonstrate the feasibility of the SWIM concept Identify the lessons learned to support the SESAR activities 4

5 Design Principles / Requirements (1/2) Following SESAR definitions the prototype : –has been designed using a domain based approach (Flight, Surveillance, etc. – like a data model based systems integration) –has been implemented using a standard based approach Well known data and information models (e.g. ICOG2) Standard technologies (Web Services, EJB, DDS) –decouples external adapters/systems from internal knowledge about the SWIM implementation Accept overheads are due to the use of XML data modelling at the interface level Establish programming language independence 5

6 Design Principles / Requirements (2/2) Request/Reply –Supported by Web Services (basically a synchronous access) Publish/Subscribe –Supported by JMS/DDS (asynchronous access) 6

7 SWIM-SUIT prototype 7 ATM Virtual Information Pool AOC MXP AIRPORT Heathrow CDM ISPOC Prototype ATFCM (CFMU) ACC/APP ACC Flight Simulator FMS EAD USA SWIM The prototype (named “SWIM-BOX”) has been conceived as a sort of “Gateway/Mediator” across legacy applications

8 SWIM-SUIT Prototype architecture 1/3 The SWIM BOX acts as a mediator between different legacy systems The SWIM BOX acts as a mediator between different legacy systems The Adapter translates data/services among Legacy and SWIM-BOX The Adapter translates data/services among Legacy and SWIM-BOX 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)

9 SWIM-SUIT Prototype architecture 2/3

10 SWIM-SUIT Prototype architecture 3/3

11 SWIM Data Domains Following SESAR definitions, the prototype provides support (service/data exchanges) on a “data domain” base –Offers generic (but “standard”) services for their specific domain and offer some extra management service –Defines a “standard” data representation and translate it in a flexible format (XML in the prototype) –On a domain basis, manages the roles taking into account a subset of data –Provides 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) ICOG2 data & information standard (providing specific extensions) –SDD (Surveillance Data Domain) ASTERIX Category 62 data standard (binary & XML representations) –AID (Aeronautical Information Service Domain) Aeronautical Information Exchange Model (AIXM) 11

12 SWIM-BOX Core 12 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 (acts as much as possible as a transport layer) SWIM Data Domain Interfaces and Wire Interfaces follow established standards 12

13 SWIM-Box FDD-Adapter communications : consume service 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]) 13

14 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 14

15 Testing & Validation activities Unit Tests (no data domain components involved) –Automatic test suite for the SWIM-BOX core components Integration Tests (no Legacy Systems involved) –Semi-Automatic test suite for each SWIM-BOX data domain components (to test the data domain capabilities and to evaluate potential data domain components integration problems) –LAN & WAN Pseudo Operative Tests (Legacy Systems involved) –Suite of operative scenarios (e.g. management of the airport arrival sequence) to validate the prototype capabilities and to demonstrate the feasibility of the SWIM concept –WAN Performance Tests (no Legacy Systems involved) –Automatic test suite to evaluate the prototype behavior (e.g. average response time, data loss, throughput, etc.) building specific workloads (e.g. service invocation rate, data publication rate, number of published data, number of flight data, etc.) –LAN & WAN

16 Questions? 16

17 Subscribing 17 AdapterTo SwimBox SwimBox subscribe Legacy subscribe SwimBox AdapterTo SwimBox Legacy 13/04/ SWIM-SUIT Overview

18 Creating FOs – Node A 18 FDDAdapter Notification FOContributor createFO distributeFO notifyFOSummary addFlightObject notifyFOUpdate addFlightObject AdapterTo SwimBox SB Legacy SB FOManager addFlighObject 13/04/ SWIM-SUIT Overview

19 createFO distributeFO notifyFOSummary addFlightObject notifyFOUpdate addFlightObject FOContributorLegacy FDDAdapter Notification AdapterTo SwimBox SwimBox FOManager addFlighObject Creating FOs – Node B 13/04/ SWIM-SUIT Overview

20 Requesting services – Node B 20 requestFOService getFlightObject requestFOService send updateFO distributeFO notifyFOSummary notifyFOUpdate addFlightObject FOContributor SBLegacy AdapterTo SwimBox FDDAdapter Notification FOManagerFDDAdapter Adapter Messaging SB 13/04/2010 SWIM-SUIT Overview

21 Performing handover – Node A 21 requestFOhandover acceptHandover handoverFO getFlightObject addFlightObject removeFlightObject addFlightObject removeFlightObject Legacy AdapterTo SwimBox SB FDDAdapterFOContributorFOManager FOContributor 13/04/2010 SWIM-SUIT Overview

22 Unsubscribing unsubscribe AdapterTo SwimBox SwimBoxLegacySwimBoxLegacy AdapterTo SwimBox 13/04/2010 SWIM-SUIT Overview