Semantic Data Exchange in E-Navigation Mazen Salous, - PowerPoint PPT Presentation

1 Semantic Data Exchange in E-Navigation Mazen Salous, mazen.salous@offis.de Andre Bolles, andre.bolles@offis.de Daniela Nicklas, daniela.nicklas@uni-bamberg.de Henning Mextorf, henning_mextorf@raykiel.com 5. März 2015

It‘s good to know where the others are … 2 https://www.youtube.com/watch?v=y3WveEZykJ8&app=desktop 3/11/2015

3 Overview  Motivation by scenario  Our approach  Data exchange features  State of the art  Outlook 3/11/2015

4 Scenario [1] Ship 4 State of the art: Only human to human Actual communication / voice over radio radar range (if any) Radar range of ship 1 of ship 1 (theoretical) With COSINUS: Electronic Chart and Display Human cooperation enhanced by Information System (ECDIS) automated data exchange Ship 4! Ship 3! VTS Radar Range VTS Building Harbour Public domain, by Mats Koivisto Vessel Traffic Service (VTS) [1] http://commons.wikimedia.org/wiki/File:Wheelhouse_of_Leao_Dos_Mares.jpg 3/11/2015

5 COSINUS project overview Cooperative ship control Synchronized, situation adapted visualization Interactive visualization Interactive visualization of safety-critical of safety-critical information information Data exchange ECDIS VTS Data Data and integration integration integration 3/11/2015

6 Challenges for ship to shore data exchange  A dynamic, distributed system  Ships enter and leave the VTS range  Overlapping observations (  redundancy)  Integration with existing systems  Realize data exchange with operational navigational systems  Different formats (syntax), same (or similar) semantics  IVEF : (Inter VTS Exchange Format)  NMEA: (National Marine Electronics Association)  Data quality  Poor resolution of long range radars 3/11/2015

7 Approach: distributed data stream based architecture Mobile Context Model 1 Coastal Context Mobile Model Semantic ECDIS Stream Coastal Data Semantic Processor VTS Stream Data Processor … Mobile Semantic Stream ECDIS Data Processor Mobile Context Model n Messages

8 Data stream management by Odysseus  Flexible Open Source Data Stream Management Framework  Has sophisticated access framework  Easy integration of data models and formats  Context store: stream listeners, stream patterns storage  Framework architecture (OSGi) Download and Information:  Extensible for new requirements, http://odysseus.informatik.uni-oldenburg.de operators, scheduling strategies, …  Adaptable even at runtime Apache 2.0 License

9 Context models  Store a mid-term memory / history of a semantic processor  e.g., one hour sliding time-window (can be specified)  Built up by interpreting the passed-through messages Coastal Context Model  Coastal Context model contents: Coastal  Sensed ships (tracks, routes) and other information of interest Semantic Stream  Representation of context models of communication partners Processor  To rate quality (e.g., completeness, accuracy)  Needs concept of range (what could a ship see)  Mobile context model contents: Mobile Semantic  Sensed ships (tracks, routes) and other information of interest Stream Processor  When entering the range of a VTS, the ship can send some history of it‘s information Mobile Context Model 3/11/2015

10 Data exchange feature: semantic compression  Define the relevant data  Overlapping observations  Not all data needs to be exchanged  Exchange only if there are  Missed observerations  Low quality data  Reduce amount of exchanged messages based on content 3/11/2015

11 Data exchange feature: consistency  Ship1: Position1 for A at time t  Ship2: Position2!=Position1 for A at the same time t (or within given intervals)  Inconsistent messages can be detected by cooperation between coastal and mobile semantic stream pocessors  Potential reactions:  Annotate messages by inconsistency measurement  Based on the real tracking history of A and taking the planned route, speed direction into account, our system can decide the more accurate position 3/11/2015

12 State of the art  Related work in E-Navigation  Without data exchange and integration:  BaSSy (Baltic Sea Safety) and EfficenSea projects:  Focused on analyzing AIS information and radar images and contributed to risk identification algorithms for VTS systems regardless the data exchange and integration between ECDIS and VTS systems  Using data exchange and integration:  ACCSEAS:  prototypes demonstrate the functionality of route exchange  Monalisa I + II:  route exchange using a central administrative entity that organizes route planning among different participants in a specific area at sea 3/11/2015

13 Conclusion  Summary  Our system increases the maritime traffic safety by  Defining the semantics continuously: the relevant data for each navigation system to be exchanged  Exchanging the missed relevant data  Automatically anotation of data qualities: e.g. completeness, consistency  Enabling cooperative integrated traffic control on ship and shore sides  Enabling continuous awareness for the e-navigation situation  Approach:  Distributed data stream management system (Odysseus)  Know where the others are! 3/11/2015

14 Discussion Questions are welcome! 3/11/2015