Copyright © 2013 Open Geospatial Consortium.
49
6.2.10.4.4 Data Provenance Module
The Data Provenance Module is a client-configurable Module Feature designed to track changes to message provenance by the Filtering Module prior to client transmission.
Whenever the Filtering Module removes content from a message, the aircraft client was be informed by the Provenance Module of the alteration. The Provenance module
generated metadata that describes the alterations made by the Filtering Module to the content of a message. The generatation of this metadata by the Provenance Module,
followed ISO Standard 1911519135 and was inserted into SOAP message headers before transmission to the client.
6.2.10.4.5 Dispatch Module
The Dispatch Module is a feature that allows a ground based client such as an airline dispatcher to subscribe to and receive copies of the messages sent to an aircraft client.
This enabled the dispatcher client to track the information that has been received by the aircraft client. The Dispatch Module provided the dispatch client with the aircraft clients
consumer reference endpoint. The dispatch client used this endpoint to subscribe an aircraft client to a Web Feature Service or Event Service data product if it determined the
aircraft client would benefit from the additional information.
6.2.10.5 Challenges
The key challenge in the development of the Data Management Service DMS was creating a solution that can fully communicate with both the North American and
European System Wide Information Management SWIM environments. Although the overarching system concepts for SWIM are the same in both North American and
Europe, the actual SWIM implementations currently employ different technical standards for their communication interfaces. During the development of DMS for OWS-9, the
web service technical standard was used as the communication protocol between aircraft, DMS, and ground services. The use of web service as a communication protocol works
well as connection to European SWIM ground services. Future OGC activity should focus on the integration of Message-Oriented Middleware MOM, which is the
communication protocol primarily used by North American SWIM ground services. The extent of the technical gap between what was created in OWS-9 and what needs to be
developed for integration of FAA SWIM ground services was documented by OWS-9 in the SWIM Compliance Assessment document. The creation of a solution that bridges the
gap between North American and European SWIM messaging protocol is a strong candidate for future OGC work.
50
Copyright © 2013 Open Geospatial Consortium.
6.2.10.6 Accomplishments
Several key accomplishments were achieved within OWS-9 Data Transmission Management during the development of the Data Management Service by Harris
Corporation:
Creation of an operational Data Management Service that was accessible by clients and provided reliable and efficient management of communications
between aircraft and services located on the ground. Submission of an engineering report that provided technical details describing
how the DMS standard was implemented, as well as feedback and comments that described lessons learn and recommendations for future improvements.
Collaboration with other developers of the Data Management Service and aircraft clients Atmosphere, TriaGnoSys, and Luciad to develop a common interface for
the connection of aircraft clients into the DMS for global interoperability. Feedback provided to OWS-9 stakeholders to increase understanding of the DMS
requirement while providing feedback for the shaping of future DMS requirements.
Designing the DMS as an interoperable system by providing SWIM Web Services Connectivity in the OGC architecture.
6.2.11 ATM-TGS Aviation Client
In order to demonstrate the functionalities of the DMS, a client was developed to test the different operations at the DMS and to demonstrate its usefulness and efficiency.
6.2.11.1 Functionalities
The client developed in OWS-9 had the capacity to communicate with the following entities:
Web Feature Service. Event Services.
Data Management Service. The client was divided in 2 parts; the client display application and the client DMS
module CDMS. The application part was in charge of the direct interaction with the human client. It
encompassed a moving map and an interface for information queries. All display was in the client application
Kategori