swim-suit final user forum. 24-25 june 2010 swim-suit final user forum, rome subscription first...

SWIM-SUITSWIM-SUIT

Final User ForumFinal User Forum

24-25 June 2010 SWIM-SUIT Final User Forum, Rome

SubscriptionSubscription

• First step: SubscriptionFirst step: Subscription– On FDD subscription a client provide its On FDD subscription a client provide its

own identifier (a unique “name”) and own identifier (a unique “name”) and (optionally) an Endpoint (and URL) where (optionally) an Endpoint (and URL) where it will be notified upon data arrival and/or it will be notified upon data arrival and/or service requests.service requests.

– Internally, the SWIM-BOX, stores the Internally, the SWIM-BOX, stores the subscription information in the subscription information in the “SharedDataStore” (a SB internal “SharedDataStore” (a SB internal component)component)•The SDS is synchronized across all SB The SDS is synchronized across all SB

instances. Therefore, every participant instances. Therefore, every participant will now know about this new will now know about this new subscription (The SDS, in FDD, acts like subscription (The SDS, in FDD, acts like a distributed registry). a distributed registry).

Legacy SystemCFMU

Legacy SystemLISATM

Legacy SystemCRISTAL MED

SubscriptionSubscription

1.Subscribe request

1.Subscribe request

2.Create Participant2.Create

Participant

The CFMUswim-box instance ...CFMU

DescriptionAdditional

InfoParticipant

3.Synchronize participants list

3.Synchronize participants list


Fligth Object CreationFligth Object Creation

• Second step: FO creationSecond step: FO creation– A client creates a new flight and publish it on the A client creates a new flight and publish it on the

SWIM Network via the SWIM-BOX. Upon creation, it SWIM Network via the SWIM-BOX. Upon creation, it has to provide (at least) FlightKey and Trajectory has to provide (at least) FlightKey and Trajectory clusters which are used by the SB to determine a clusters which are used by the SB to determine a unique (System Wide) FlightIdentifier and a list of unique (System Wide) FlightIdentifier and a list of auto-determined receivers (they are inserted in the auto-determined receivers (they are inserted in the so called “distribution list”).so called “distribution list”).

• Internally, the SB also stores a structure in the Internally, the SB also stores a structure in the SharedDataStore which indicates for each flight SharedDataStore which indicates for each flight who is the “Manager” and who are the “Users” or who is the “Manager” and who are the “Users” or the “Contributors”the “Contributors”

– If the Flight was not already existing, the SB returns If the Flight was not already existing, the SB returns the FlightIdentifier to the client and publishes the the FlightIdentifier to the client and publishes the Flight Object (i.e. A Flight Summary – auto Flight Object (i.e. A Flight Summary – auto generated - plus a set of clusters as provided by the generated - plus a set of clusters as provided by the client).client).

• Upon publication, the systems in the distribution Upon publication, the systems in the distribution list will receive the datalist will receive the data

Legacy SystemCFMU

Legacy SystemLISATM


Flight Object CreationFlight Object Creation

1.FO Creation

1.FO Creation

2.Validate information and identify USERs and CONTRIBUTORs using FlighKey

and Trajectory clusters

2.Validate information and identify USERs and CONTRIBUTORs using FlighKey

and Trajectory clusters

CFMU ...AZ100MANAGER USERs

Flight Identifier CRISTAL MED,

LISATM

CONTRIBUTORs

3.Share FO role mapping

3.Share FO role mapping

4.Synchronize FO roles mapping

4.Synchronize FO roles mapping

SWIM-SUITSWIM-SUIT



Flight Object UpdateFlight Object Update

• The Manager can update its own The Manager can update its own flights. This could be due to an update flights. This could be due to an update of its own information or following a of its own information or following a “contribution” from another system “contribution” from another system (playing the “Contributor” role).(playing the “Contributor” role).

• The Manager provides the updated The Manager provides the updated clusters to the SWIM-BOX which in turn clusters to the SWIM-BOX which in turn distribute them to the systems in the distribute them to the systems in the distribution list.distribution list.

• Updated data are received by each SB Updated data are received by each SB local instance and notified to the local local instance and notified to the local clientclient

Legacy SystemCFMU

Legacy SystemLISATM


Flight Object UpdateFlight Object Update

5.FO Update5.FO

Update

6.Internal flight update

and publication

6.Internal flight update

and publication

Flight summary

AZ100Flight

identifier LISATMManagerxx

EOBD/EOBT xxADEP

xxADES....

Flight object clusters

TRAJECTORYSSR

FlightKeyFlightPlan

..

7.Flight Object notification


8.Legacy notification8.Legacy

notification




notification

SWIM-SUITSWIM-SUIT



Flight Object HandoverFlight Object Handover

• The Manager asks to the SB to The Manager asks to the SB to perform an handover on a given FOperform an handover on a given FO

• The SB forwards this request to the The SB forwards this request to the first “Contributor” on the basis of first “Contributor” on the basis of aircraft trajectory.aircraft trajectory.

• Once the contributor accepts the Once the contributor accepts the request, the SB updates the roles request, the SB updates the roles (in a transaction) in the (in a transaction) in the SharedDataStore and publish SharedDataStore and publish clusters affected by this clusters affected by this modification.modification.

Legacy SystemCFMU

Legacy SystemLISATM


Flight Object HandoverFlight Object Handover

1.FO Handover

1.FO Handover

2.Discovery candidate next MANAGERusing available CONTRIBUTORs

and Trajectory information

2.Discovery candidate next MANAGERusing available CONTRIBUTORs

and Trajectory information

3.Forward the Handover requestto CRISTAL MED

SWIM-BOX instance

3.Forward the Handover requestto CRISTAL MED

SWIM-BOX instance

4.Require Handover approval

4.Require Handover approval

5.The legacy accept the request

5.The legacy accept the request

6.Update Flight roles mapping

6.Update Flight roles mapping

LISATM ...AZ100MANAGER USERs

Flight Identifier CRISTAL

MED,CFMU

CONTRIBUTORs

7.Update Flight summaryand Flight IOPINFORMATION cluster

7.Update Flight summaryand Flight IOPINFORMATION cluster

Flight summary Flight object clusters

AZ100Flight identifier CRISTAL

MEDManagerxx

EOBD/EOBT xxADEP

xxADES....

Flight IdentificationIOP Information




notification




notification

SWIM-SUITSWIM-SUIT


Story Board: Surveillance Story Board: Surveillance / HMI/ HMI


Data Format: Asterix Data Format: Asterix Cat062Cat062

• binary3e 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

HMI ComponentsHMI Components


SWIM HMIAdapter

SWIM HMIAdapter

SWIM HMIServer

SWIM HMIServer

BrowserClient(s)BrowserClient(s)

Based on GeoServerand uses

Google Maps

Handle subscriptions and receive data from SWIM SUIT

HMI subscribes to dataHMI subscribes to data


SWIM HMIAdapter

SWIM HMIAdapter

SWIM HMIServer

SWIM HMIServer

SWIMBox

(HMI)

SWIMBox

(HMI)

BrowserClient(s)BrowserClient(s)

Subscriptions defined in Config file:1)Activated on start-up2)De-activated on shut-down

Un-subscribe

Subscribe

Subscriptions define: areas of interest & mode (push/pull) & data format

HMI receives dataHMI receives data


SWIM HMI

Adapter

SWIM HMI

Adapter

SWIMBox

(HMI)

SWIMBox

(HMI)

SWIMBox

(ENAV)

SWIMBox

(ENAV)

SWIM ENAV

Adapter

SWIM ENAV

Adapter

MRTMRT

SWIM HMI

Server

SWIM HMI

Server

BrowserClient

BrowserClient

Communication Pattern: Publish/Subscribe

(Multicast)

swim-suit final user forum. 24-25 june 2010 swim-suit final user forum, rome subscription first...

Documents

data slide

new flight

flight summary

fdd subscription

subscription information

new subscription

trajectory clusters

cfmu swimbox instance