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

Semantic Data Exchange in E-Navigation

1

• 5. März 2015

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

It‘s good to know where the others are … 2

3/11/2015 https://www.youtube.com/watch?v=y3WveEZykJ8&app=desktop

Overview

 Motivation by scenario  Our approach  Data exchange features  State of the art  Outlook

3

3/11/2015

Scenario 4

3/11/2015

Harbour

VTS Radar Range

Radar range

• f ship 1 (theoretical)

Actual radar range

• f ship 1

Ship 4 VTS Building

State of the art: Only human to human communication / voice over radio (if any) With COSINUS: Human cooperation enhanced by automated data exchange

Vessel Traffic Service (VTS)

Public domain, by Mats Koivisto

Electronic Chart and Display Information System (ECDIS)

Ship 3! Ship 4!

[1] [1] http://commons.wikimedia.org/wiki/File:Wheelhouse_of_Leao_Dos_Mares.jpg

COSINUS project overview 5

3/11/2015

ECDIS VTS

Cooperative ship control

Interactive visualization

• f safety-critical

information Interactive visualization

• f safety-critical

information Data integration Data integration

Synchronized, situation adapted visualization Data exchange and integration

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

6

3/11/2015

Coastal Semantic Stream Data Processor ECDIS ECDIS

VTS

Coastal Context Model

Messages

Approach: distributed data stream based architecture

7

Mobile Context Model 1 Mobile Context Model n

… Mobile Semantic Stream Data Processor Mobile Semantic Stream Data Processor

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)  Extensible for new requirements,

• perators, scheduling strategies,

…

 Adaptable even at runtime

8

Download and Information: http://odysseus.informatik.uni-oldenburg.de Apache 2.0 License

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 contents:  Sensed ships (tracks, routes) and other information of interest  Representation of context models of communication partners  To rate quality (e.g., completeness, accuracy)  Needs concept of range (what could a ship see)  Mobile context model contents:  Sensed ships (tracks, routes) and other information of interest  When entering the range of a VTS, the ship can send some

history of it‘s information

9

3/11/2015

Coastal Semantic Stream Processor

Coastal Context Model

Mobile Semantic Stream Processor

Mobile Context Model

Data exchange feature: semantic compression 10

3/11/2015

 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

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

11

3/11/2015

State of the art

 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

• rganizes route planning among different participants in

a specific area at sea

12

3/11/2015

 Related work in E-Navigation

Conclusion

 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!

13

3/11/2015

 Summary

Discussion

Questions are welcome!

14

3/11/2015