Copyright © 2013 Open Geospatial Consortium.
45 the client and sent those data sets in order of importance in the event of
concurrent arrival at the DMS.
Synchronization: In the aviation context, to increase situation awareness, the
flight management entity e.g. dispatch may have interest in being aware of the information that is requested and communicated to aircraft it is responsible for.
To tackle that challenge, the DMS offered the capability to dispatch units to subscribe to clients to receive copies or summaries of the information received by
the client.
6.2.9.3 Deployment
The DMS server and its functions has been implemented and is running on TriaGnoSys premises.
6.2.9.4 Interfaces
There are 3 endpoints for the DMS, one for each type of entity that can communicate with it.
Endpoint Available operations
URL
Aircraft Client getSessionOptions
createSession clientRequest
clientSubscribeRequest http:192.37.61.154:8080Services
DMServices
Event Service Notify
http:192.37.61.154:8080Services GroundDMServices
Dispatch Client getConsumerReference
subscribeToClient unsubscribeFromClient
http:192.37.61.154:8080Services DispatchServices
The different operations are described here:
Operation Description
getSessionOptions This operation was called by the client to obtain the list of
options available at the DMS for Data Management createSession
This operation was called by the client to define the activated module for its session with the DMS and the potential options
associated
clientRequest This operation was called by the client to send a request
feature request, unsubscribe request … through the DMS. clientSuscribeRequest
This operation was called by the client to create a subscription to an Event Service that will be managed by the DMS.
Notify This operation was called by the Event Service to send a
notification that will then be forwarded to the client
46
Copyright © 2013 Open Geospatial Consortium.
getConsumerReference This operation was called by the dispatch client to obtain the
consumer reference of a given client at the DMS in order to make subscription on behalf of this client.
subscribeToClient This operation was called by the dispatch client to subscribe to
a given client. The DMS was then be notified with any information that arrived at the DMS intended for this particular
client.
unsubscribeFromClient This operation was called by the dispatch client to unsubscribe
from a client.
6.2.9.5 Component functionality
Within the OWS-9, the following DMS functionalities have been implemented and tested:
DMS service discovery; which mainly concerns the process of finding and setting the processing options to be done at the DMS by the aircraft and dispatch client.
DMS basic pass-through; which handles the forwarding of requestresponse and notifications between aircraft client and OGC web services.
Reliable messaging. Data compression expansion.
Data filtering. Dispatch synchronization.
6.2.10 Harris Data Management Service 6.2.10.1 Overview
