OpenGIS
®
Engineering Report OGC 12-163
1
OGC
®
OWS-9 Data Transmission Management
1 Introduction
1.1 Scope
This document is the results of the investigations and discussions undertaken in OWS-9 concerning the Data Management Service Entity.
This document establishes the structure of the Data Management Service DMS, defines its position in the OGC architecture, specifies its role within its architecture, together
with its limits and, as much as possible, its interfaces with other OGC entities e.g. Web Feature Service.
The baseline for those definitions can be found in the System Rules Model provided at the end of the document.
The general motivation of this document is to provide guidelines for the specification of a broker entity, which main objectives consist of optimizing resources utilization and
improving the quality of service delivery.
To achieve that purpose, this document defines 6 modules that constitute the DMS functionalities: Efficient Communication, Efficient Data Exchange, Prioritization,
Filtering, Validation and Provenance. Each of these modules is described in this document in terms of scope, investigation results and recommended approach.
This document is not a set of requirements that need to be fulfilled by a DMS implementation. It only provides the result of investigations for general transmission
optimization with a strong focus on the aviation domain. However for each module, the implementation choices made by the development team are described and justified.
2
1.2 Document contributor contact points
All questions regarding this document should be directed to the editor or the contributors:
Name Organization
Charles Chen Harris Corporation
Thibault Dacla Atmosphere gbmh
Eriza Fazli TriGnoSys
Stuart Wilson Harris Corporation
1.3 Revision history
Date Release
Editor Primary clauses
modified Description
1.4 Future work
Some points identified for future DMS work: - The use of SOAP and the intention to make the DMS as transparent as possible to
the different clients and web services eventually create an issue on the client implementation. If the OWSs already use SOAP, DMS insertion requires that the
client’s original SOAP envelope to be enclosed in another SOAP envelope to communicate with the DMS. This is rather tricky to do and requires modification
of the middleware that the client typically uses to intercept the original SOAP envelope.
more feedback from all stakeholders including client to devise which protocol solution to be used; use different transport than HTTP or SOAP
- Cleaner definition of DMS interfaces; right now {request, subscribe request, notify, {dispatch}}. Some messages are not captured, e.g. if the client wants to get
a WSDL or schema files from the web service. - Proper definition of the middle entity that operates between clients and the DMS
to make the inclusion of the DMS truly seamless to clients. - Provision of additional operations at the DMS, such as destroy session.
- Support of binary content e.g. image formats - Further investigation of AMQP as a potential alternative to HTTP for web
services over IP - Definition of the need scope and responsibility for the addition of filtering options
provided to the client. Tradeoff to be made between bandwidth efficiency and schema compliance.
- Address the issue of client mobility change of IP address - Similarly, address the use case of DMS handovers
3
1.5 Forward
Kategori