This document discusses DiCEPE, a distributed complex event processing engine. It has a component architecture that allows a CEP editor to add, delete, and retrieve statements from DiCEPE. DiCEPE is connected to an event cloud to subscribe to and notify events. It has been tested successfully with CEPEditor. DiCEPE is also context aware and listener aware to statements and engine instances. A crisis use case is presented involving firemen, police, and sensors.

1. Distributed
Complex Event Processing
Fernand Paraiso, Lionel Seinturier,
Romain Rouvoy
INRIA Lille – Nord Europe
Project-team ADAM

2. Agenda
DiCEPE
Distributed aware
Crisis Use case
Question & Answer
DiCEPE: Distributed Complex Event Processing Engine

3. Component architecture : DiCEPE
lisAllStatements
(
(
getStatementById
CEP Editor addStatement
( DiCEPE
deleteStatement
(
subscribe
)
Event Cloud
)
notify
DiCEPE: Distributed Complex Event Processing Engine

4. DiCEPE-CEPEDITOR has been tested
successfully with CEPEditor
DiCEPE: Distributed Complex Event Processing Engine

5. DiCEPE -EC is under test with
EventCloud
DiCEPE: Distributed Complex Event Processing Engine

6. Distributed aware
Listener aware
Statements
Engine Instance
Context aware
Presentation of information and services

7. Crisis Use Case Entities
Firemen
Firemen are grouping by station
Police
Police are grouping by station
Sensors

8. Use Case sequence Diagram

9. Use case Architecture
DiCEPE: Distributed Complex Event Processing Engine

10. Use Case Simulation
What is Siafu ?
Why Siafu ?

11. Demonstration
Questions?
DiCEPE: Distributed Complex Event Processing Engine

12. Perspectives
&
Conclusion
Integration of EventType
Distributed aware.
Filter Operator
Finish Test with EventCloud
Finish Crisis USE CASE