Semantic Event Processing in ENVISION Alejandro Llaves, Patrick Maué, Henry Michels, & Marcell Roth Institute for Geoinformatics University of Muenster.

Post on 28-Mar-2015

218 Views

Category:

Documents

0 Downloads

Preview:

Click to see full reader

Transcript

Semantic Event Processing in ENVISION

Alejandro Llaves, Patrick Maué, Henry Michels, & Marcell Roth

Institute for GeoinformaticsUniversity of Muenster

10/04/23 2

Overview

Intro Semantic Sensor Web & Event Processing Approach

– Semantic Annotations for Sensor Data Services

– A Layered Event Ontology Model

– Semantic Event Processing – Architecture Overview

Example of Use: Flood Monitoring in the Danube Conclusion

10/04/23 3

Intro

Integration of geospatial information across different communities Inferring occurrences (events) from time-series of observations

Motivation Lack of standardized methods to process and represent environmental

information describing change causes semantic interoperability problems

10/04/23 4

Semantic Sensor Web & Event Processing

Sensor Web

Why Event Processing?

Semantic Event Processing

„Use of semantic event models and rules to enhance the results of Event Processing.“ [Teymourian & Paschke, 2009]

10/04/23 5

Enablement (SWE)Semantic

Approach (1/3)

Semantic Annotations for Sensor Data Services: Extending Semantic annotations in OGC standards [Maué et al., 2009]

10/04/23 6

Approach (2/3)

A Layered Event Ontology Model

10/04/23 7

The Event-Observation ontology (W3C’s SSN ontology extension)

Domain micro-ontologies

Example:

Approach (3/3)

Semantic Event Processing – Architecture Overview

10/04/23 8

Example of Use: Flood Monitoring in the Danube

A flood monitoring ontology - http://purl.org/ifgi/water/flood Semantic annotation of a water level SOS

10/04/23 9

Example of Use: Flood Monitoring in the Danube

A flood monitoring ontology - http://purl.org/ifgi/water/flood Semantic annotation of a water level SOS Description of relevant situations: HighWaterLevel events

– Water level must be maintained below 69,59 metres at Iron Gates I.

– Water level must be maintained below 41,00 metres at Iron Gates II.

10/04/23 10

SELECT *FROM WaterLevel.win:length(1)WHERE (sensor.id == 'IronGatesI') and(value >= 6959)

HighWaterLevel

SELECT *FROM WaterLevel.win:length(1)WHERE (sensor.id == 'IronGatesII') and(value >= 4100)

HighWaterLevel

Example of Use: Flood Monitoring in the Danube

A flood monitoring ontology - http://purl.org/ifgi/water/flood Semantic annotation of a water level SOS Description of relevant situations: HighWaterLevel events Event Subscription interface allows users subscribing to specific

situations to receive notifications– Video demo at http://www.envision-project.eu/resources/

10/04/23 11

Conclusion

Summary– Applying Semantic Event Processing to time-series of sensor data

– The layered ontology model presented eases maintenance tasks and enables modularity

– Loosely coupled event-driven service oriented architecture

Contribution– Semantic Event Processing methodology that allows near real-time

analysing and integrating different views for the same event type

Current status and open issues– Upgrading EPS to pull heterogeneous sensor data

– A event pattern editor is under development

– SNB will be extended to work on additional use cases

– Ontologies http://www.envision-project.eu/resources/ontologies/

10/04/23 12

Thanks!

http://www.envision-project.eu/

alejandro.llaves@uni-muenster.de

10/04/23 13

top related