1 / 17

SWIM-SUIT Final User Forum

SWIM-SUIT Final User Forum. Subscription. First step: Subscription On FDD subscription a client provide its own identifier (a unique “name”) and (optionally) an Endpoint (and URL) where it will be notified upon data arrival and/or service requests.

gay
Download Presentation

SWIM-SUIT Final User Forum

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. SWIM-SUITFinal User Forum

  2. Subscription • First step: Subscription • On FDD subscription a client provide its own identifier (a unique “name”) and (optionally) an Endpoint (and URL) where it will be notified upon data arrival and/or service requests. • Internally, the SWIM-BOX, stores the subscription information in the “SharedDataStore” (a SB internal component) • The SDS is synchronized across all SB instances. Therefore, every participant will now know about this new subscription (The SDS, in FDD, acts like a distributed registry). SWIM-SUIT Final User Forum, Rome

  3. Flight Data Domain Flight Data Domain Flight Data Domain Publish Subscribe Service Publish Subscribe Service Publish Subscribe Service Shared Data Store Service Shared Data Store Service Shared Data Store Service Subscription Legacy System CFMU Legacy System LISATM Legacy System CRISTAL MED 1.Subscribe request 2.Create Participant 3.Synchronize participantslist Description Additional Info Participant The CFMUswim-box instance ... CFMU

  4. Fligth Object Creation • Second step: FO creation • A client creates a new flight and publish it on the SWIM Network via the SWIM-BOX. Upon creation, it has to provide (at least) FlightKey and Trajectory clusters which are used by the SB to determine a unique (System Wide) FlightIdentifier and a list of auto-determined receivers (they are inserted in the so called “distribution list”). • Internally, the SB also stores a structure in the SharedDataStore which indicates for each flight who is the “Manager” and who are the “Users” or the “Contributors” • If the Flight was not already existing, the SB returns the FlightIdentifier to the client and publishes the Flight Object (i.e. A Flight Summary – auto generated - plus a set of clusters as provided by the client). • Upon publication, the systems in the distribution list will receive the data SWIM-SUIT Final User Forum, Rome

  5. Flight Data Domain Flight Data Domain Flight Data Domain Publish Subscribe Service Publish Subscribe Service Publish Subscribe Service Shared Data Store Service Shared Data Store Service Shared Data Store Service Flight Object Creation Legacy System CFMU Legacy System LISATM Legacy System CRISTAL MED 1.FO Creation 2.Validate information and identifyUSERs and CONTRIBUTORsusingFlighKey and Trajectoryclusters 3.Share FO rolemapping 4.Synchronize FO rolesmapping MANAGER USERs CONTRIBUTORs Flight Identifier CFMU ... CRISTAL MED, LISATM AZ100

  6. SWIM-SUITFinal User Forum

  7. Flight Object Update • The Manager can update its own flights. This could be due to an update of its own information or following a “contribution” from another system (playing the “Contributor” role). • The Manager provides the updated clusters to the SWIM-BOX which in turn distribute them to the systems in the distribution list. • Updated data are received by each SB local instance and notified to the local client SWIM-SUIT Final User Forum, Rome

  8. Flight Data Domain Flight Data Domain Flight Data Domain Publish Subscribe Service Publish Subscribe Service Publish Subscribe Service Shared Data Store Service Shared Data Store Service Shared Data Store Service Flight Object Update Legacy System CFMU Legacy System LISATM Legacy System CRISTAL MED 8.Legacy notification 5.FO Update 8.Legacy notification 6.Internal flight update and publication 7.Flight Objectnotification 7.Flight Objectnotification Flight objectclusters Flight summary TRAJECTORY Flight identifier AZ100 Manager LISATM SSR EOBD/EOBT xx FlightKey ADEP xx FlightPlan ADES xx .. .. ..

  9. SWIM-SUITFinal User Forum

  10. Flight Object Handover • The Manager asks to the SB to perform an handover on a given FO • The SB forwards this request to the first “Contributor” on the basis of aircraft trajectory. • Once the contributor accepts the request, the SB updates the roles (in a transaction) in the SharedDataStore and publish clusters affected by this modification. SWIM-SUIT Final User Forum, Rome

  11. Flight Data Domain Flight Data Domain Flight Data Domain Publish Subscribe Service Publish Subscribe Service Publish Subscribe Service Shared Data Store Service Shared Data Store Service Shared Data Store Service Flight Object Handover Legacy System CFMU Legacy System LISATM Legacy System CRISTAL MED 1.FO Handover 9.Legacy notification 9.Legacy notification 4.Require Handoverapproval 5.The legacyaccept the request 7.Update Flight summary and Flight IOPINFORMATION cluster 2.Discovery candidate next MANAGER usingavailableCONTRIBUTORs and Trajectory information 3.Forward the Handoverrequest to CRISTAL MED SWIM-BOX instance 8.Flight Objectnotification 8.Flight Objectnotification 6.Update Flight rolesmapping Flight summary Flight objectclusters Flight Identification Flight identifier AZ100 MANAGER USERs CONTRIBUTORs Flight Identifier Manager CRISTAL MED IOP Information LISATM ... CRISTAL MED, CFMU AZ100 EOBD/EOBT xx ADEP xx ADES xx .. ..

  12. SWIM-SUITFinal User Forum

  13. Story Board: Surveillance / HMI 24-25 June 2010 SWIM-SUIT Final User Forum, Rome

  14. Data Format: Asterix Cat062 binary 3e 00 24 b9 4d 22 21 12 14 41 f5 ec 00 76 fc 69 00 22 e8 90 07 dc 04 97 00 04 10 41 00 4f 53 35 30 31 20 20 • XML <TrackEntry> <SAC>33</SAC> <SIC>18</SIC> <ServiceID>20</ServiceID> <TrackNumber>1175</TrackNumber> <Mode3A>3734</Mode3A> <TimeOfTrackInfo>2010-06-09T09:22:51.844Z</TimeOfTrackInfo> <TrackStatus>00</TrackStatus> <WGS84Latitude>41.83100759983063</WGS84Latitude> <WGS84Longitude>12.272500991821289</WGS84Longitude> <MeasuredFlightLevel>260.0</MeasuredFlightLevel> <Callsign>OS501</Callsign> </TrackEntry> 24-25 June 2010 SWIM-SUIT Final ser Forum, Rome

  15. HMI Components Handle subscriptions and receive data from SWIM SUIT Based on GeoServer and uses Google Maps SWIM HMI Adapter Browser Client(s) SWIM HMI Server 24-25 June 2010 SWIM-SUIT Final User Forum, Rome

  16. HMI subscribes to data Subscriptions define: areas of interest & mode (push/pull) & data format • Subscriptions defined in Config file: • Activated on start-up • De-activated on shut-down Browser Client(s) SWIM HMI Server SWIM Box (HMI) Subscribe SWIM HMI Adapter Un-subscribe 24-25 June 2010 SWIM-SUIT Final User Forum, Rome

  17. HMI receives data Communication Pattern: Publish/Subscribe (Multicast) MRT SWIM ENAV Adapter SWIM Box (ENAV) SWIM Box (HMI) SWIM HMI Adapter Browser Client SWIM HMI Server 24-25 June 2010 SWIM-SUIT Final User Forum, Rome

More Related