DEBS 2011 - accepted papers and tutorials

DEBS 2O11 -  here are the list of accepted papers and tutorials.
The registration site is now open:  

Papers accepted to the Research Track

1	Qiong Zou, Bugra Gedik and Kun Wang.	SpamWatcher: A Streaming Social Network Analytic on the IBM Wire-speed Processor
2	Nihal Dindar, Peter M. Fischer, Merve Soner and Nesime Tatbul.	Efficiently Correlating Complex Events over Live and Archived Data Streams
3	Richard Hull, Elio Damaggio, Riccardo De Masellis, Fabiana Fournier, Manmohan Gupta, Fenno Heath Iii, Stacy Hobson, Mark Linehan, Sridhar Maradugu, Anil Nigam, Piyawadee Sukaviriya and Roman Vaculin.	Business Entities with Guard-Stage-Milestone Lifecycles: Managing Entity Interactions with Conditions and Events
4	Jonas Buys, Vincenzo De Florio and Chris Blondia.	Towards context-aware adaptive fault tolerance in SOA applications
5	Jatinder Singh, David Eyers and Jean Bacon.	Disclosure control in multi-domain publish/subscribe systems
6	Ella Rabinovich, Opher Etzion and Avigdor Gal	Pattern Rewriting Framework for Event Processing Optimization
7	Yagil Engel and Opher Etzion.	Towards Proactive Event-Driven Computing
8	Amer Farroukh, Mohammad Sadoghi and Hans-Arno Jacobsen.	Towards Vulnerability-Based Intrusion Detection with Event Processing
9	Gianpaolo Cugola and Alessandro Margara.	High Performance Content-Based Matching Using GPUs
10	Rohit Wagle, Henrique Andrade, Kirsten Hildrum, Chitra Venkatramani and Michael Spicer.	Distributed Middleware Reliability and Fault Tolerance Support in System S
11	Michael Olson, Annie Liu, Matthew Faulkner and K. Mani Chandy.	Rapid Detection of Rare Geospatial Events: Earthquake Warning Applications
12	Vana Kalogeraki, Adam Dou, Dimitrios Gunopulos, Taneli Mielikinen and Ville Tuulos.	Scheduling for Real-Time Mobile MapReduce Systems
13	Sangjeong Lee, Youngki Lee, Byoungjip Kim, K. Selçuk Candan, Yunseok Rhee and Junehwa Song	. High-Performance Composite Event Monitoring System Supporting Large Numbers of Queries and Sources
14	Siddarth Ganesan, Young Yoon and Hans-Arno Jacobsen.	Take Five: The Management Infrastructure for Distributed Event-Driven Workflows
15	Bibudh Lahiri, Srikanta Tirthapura and Jaideep Chandrashekar	Space-efficient Tracking of Persistent Items in a Massive Data Stream
16	Amirhossein Malekpour, Antonio Carzaniga, Fernando Pedone and Giovanni Toffetti Carughi.	End-to-End Reliability for Best-Effort Content-Based  Publish/Subscribe Networks
17	Eberhard Grummt.	Fine-grained Parallel XML Filtering for Content-based Publish/Subscribe Systems
18	Szabolcs Rozsnyai, Aleksander Slominski and Geetika Lakshmanan.	Discovering Event Correlation Rules for Semi-Structured Business Processes
19	Mark Linehan, Sylvain Dehors, Ella Rabinovich and Fabiana Fournier	Controlled English Language for Production and Event Processing Rules
20	Gabriela Jacques Da Silva, Bugra Gedik, Henrique Andrade, Kun-Lung Wu and Ravishankar K. Iyer.	Fault Injection-based Assessment of Partial Fault Tolerance in Stream Processing Applications
21	Xinxin Wang, K.Selcuk Candan and Junehwa Song	Complex Pattern Ranking (CPR): Evaluating Top-k Pattern Queries Over Event Streams
22	K R Jayaram and Patrick Eugster.	Program Analysis for Event-based Distributed Systems
23	Ming Li and Murali Mani.	Complex Event Pattern Detection over Streams with Interval-Based Temporal Semantics

Papers accepted to the industry track

1	Jimi Wen, Guyuan Lin, David Wu, Today Sung, Minsiong Liang and Gary Tsai.	A Complex Event Processing Architecture For Energy and Operation Management
2	Florian Kerschbaum.	Securely Disseminating RFID Events
3	Pekka Kaarela, Mika Varjola and Lucas Noldus.	PRONTO – Support for real-time decision making
4	Ashish Kulkarni.	ARCADE - ABSTRACTION AND REALIZATION OF COMPLEX EVENT SCENARIOS USING DYNAMIC RULE CREATION
5	Alexandre Alves.	A General Extension System for Event Processing Languages
6	Ruediger Klein, Jingquan Xie and Andrij Usov	Complex Events and Actions to Control Cyber-Physical Systems
7	Naomi Seyfer, Richard Tibbetts and Nathaniel Mishkin.	Capture Fields: Modularity in a Stream-Relational Event Processing Language
8	Hannes Obweger, Josef Schiefer, Martin Suntinger, Peter Kepplinger and Szabolcs Rozsnyai.	User-Oriented Rule Management for Event-Based Applications
9	Pål Evensen and Hein Meling.	A Paradigm Comparison for Collecting TV Channel Statistics from High-volume Channel Zap Events
10	Nenad Stojanovic, Dejan Milenovic, Yongchun Xu, Ljiljana Stojanovic and Darko Anicic.	An intelligent event-driven approach for efficient energy consumption in commercial buildings: smart office use case

Accepted tutorials

1	Gianpaolo Cugola and Alessandro Margara	Processing Flows of Information: From Data Stream to Complex Event Processing
2	Opher Etzion and Ella Rabinovich	Non Functional properties of event processing
3	Chathura Herath	Programming abstraction for Event processing in e?sciences – Dilemma of managing high data event rates with high resource consuming computations
4	Nenad Stojanovic, Pedro Bizzaro and Mani Chandy	Event Processing Grand Challenges
5	Scott De Deugd and Dave Locke	Open Messaging in the Real World
6	Paul Vincent, Adrian Paschke,  Catherine Moxey and Alexandre Alves	Architectural and Functional Design Patterns for Event Processing

On Intelligent Event Processing - AAAI symposium

This is a picture of the beautiful Stanford University, I am happy to inform today that the 2009 spring symposia of AAAI has accepted our proposal to hold a symposium about "Intelligent Event Processing" that I am organizing together with two young and energetic colleagues - Nenad Stojanovic and Adrian Paschke. This will be an attempt to get the AI community involved in event processing, and help realize the vision of "intelligent event processing". How can AI help event processing: there are several ways, and all of them are reflected in the symposium description, here are the important ones in my opinion:

Event Processing Modeling - using AI techniques: advanced logics, semantic

nets etc..

Event Pattern Discovery/mining

Event Prediction

Reasoning with uncertain events

Event-based reasoning under real-time constraints

The list of topics on the site contqins some additional topics as well. As one of our missions taken (within the EPTS) is to help accelerate the advancement of the event processing area, and using intelligent techniques may help some types of applications (again -- getting back to the elephant metaphor of my past postings - just a leg, not all applications !), the dialogue with the AI community and some projects already launched is a step in that direction. We'll post "call for papers" on the epts site, soon.

EPTS plans for 2008

This picture has been taken in the EPTS meeting in Orlando in September 2007, the meeting itself has been described by Paul Vincent in his blog : first day, second and third day.

As written before the EPTS is a consortium (under construction) intended to promote the understanding and incubate standards in the event processing area. Getting into 2008 - here is the work plan that has been recently approved by the steering committee:

Quarter 1: Launch - as expected when some of the players are big companies, the formalization process take some time, but it will hopefully converge soon. After getting approval of the steering committee - the idea is to invite vendors, customers, academic people and other individuals to join the list of founding members. The launch will also include - introduction of EPTS website (a prototype already exists - thanks to Brian Connell from WestGlobal and Serge Mankovskii from CA) which will support the work of work groups and other EPTS related information (leaving news, blog pointers, general discussion forum for David Luckham's site ). In the launch opportunity we'll also sign and seal the first version of the consensus glossary edited by David Luckham and Roy Schulte, with many contributions provided so far (a draft of this glossary is available)

Quarter 2: "State of the practice" white paper based on a collection of use cases. This is a workgroup launched in the last meeting, with a diversified team of volunteers. The first phase carried out by Tao Lin from SAP, Dieter Gawlick from Oracle and Pedro Bizzaro from University of Coimbra in Portugal to define a template to describe and compare use cases, where the use cases are those presented in the three EPTS meetings, in the Dagstuhl seminar on event processing and maybe open for others. After the glossary, this will be the next community effort in order to understand the state of the practice (there has also been some work last year on "reference architecture" lead by Tim Bass that we'll return to after completing the use cases survey).

Quarter 3: In this quarter we'll hold the fourth EPTS meeting (place and time are not determined yet), participate in the DEBS conference, which we support of becoming the research "flagship" of the event processing community. We'll also launch a portal of teaching material on event processing for the next school year.

Quarter 4: Our first contribution to standard -- we'll launch in early year a workgroup to provide the EPTS input for the OMG RFP on meta-modelling.

Many people are contributing their time and energy for these community activities, and I am looking forward to the momentum that will be created after the EPTS formal launch... stay tuned, or even better - join. Instructions about joining -- soon.

Event Processing - a footnote to databases ?

More in the spirit of the VLDB conference I've attended last week, there is a conception in the database community that event processing is really part of database technology, and that the functionality of event processing can be obtained using regular databases by inserting the events into the database, and asking "continuous queries" in the database. According to this outlook, the only reason that customers want to have engines outside the database engine is when some performance properties - typically - throughput and latency cannot be satisfied by database engines, but this can be handled by some tricks - like in-memory databases.


This reminds me that in the first conference I have ever organized: NGITS 1993 (we did not have conference webpages at those days) there was a discussion about the relations between Artificial Intelligence and Databases that followed the keynote address of John Mylopoulos, whom I always considered as one of the most visionary people I've ever met, John said something like this "the difference between AI and database discipline is that AI is a scientific discipline and database is an engineering discipline, which deals of efficiency issues", he, of course, made the database people who were present, quite angry, however, now that I am looking from the outside (at that time I have looked from the inside) on the way that database people think, I realize that he was, as usual, right.


While, high performance is one of the reasons that customers turn to COTS in this area, this is only the secondary reason, the main reason is that event processing software is being used is the level of abstraction they provide, and consequently the improvement in ROI. It seems also that the main competition between different products will be more in the ROI (ease of use) front, then in the performance front.


Event processing is different in the required functionality from database processing, the fact that database processing processes a state ("snapshot"), and event processing processes a set of transitions ("event cloud") impose different thinking, and hence different abstractions. Trying to introduce event pattern detection as extension to database processing (as we have seen in the EPTS meeting, the proposal being prepared now) have several attributes - simplicity is not part of them, and thus it totally misses the point of "ease of use", only to satisfy the assertion that event processing should be done within database processing. While these are nice academic attempts, and probably researchers will be able to write a lot of papers about the pattern extensions to SQL, I don't believe that they will catch in reality.


However - databases do have several roles in event processing, here are a few of them:

(1). Databases will be used to store events that should be used for retrospective processing. These database require to support temporal (or even spatio-temporal) characteristics; the database products don't provide yet good support of this area, and this deserves a separate blog.

(2). Databases (or in-memory databases) Will be used to store intermediate states for recoverability.

(3). Databases will be used to enrich events for processing (mainly reference data, but sometimes transaction data).
(4). Data warehouses will be used for embedded analytics.

I think that the database community should concentrate in enhancing database technology to support these functions in event processing -- e.g. temporal database support - both in abstraction level and efficiency in implementation, instead of insist on extend SQL in unnatural way.

I still need to discuss in more depth several topics like: temporal databases, retrospective processing, and alternative approach for SQL patterns, but will leave it for later.

VLDB - and computer science 2.0

Hello from Vienna. Today the VLDB conference started with an interesting talk of Werner Vogels the CTO of Amazon, whose blog is entitled: AllThingsDistributed, and the framework they have built (and that other retailers use), he referred to Amazon as a technology company that happens to do retail. I think that there many touch points of event processing technology with the Amazon model, but did not find him to talk about it. I am Amazon customer for years, somewhere in the late nineties I remember ordering a bunch of books from Amazon, and not receiving them in the designated time, I have sent an Email to Amazon asking about it, the answer amazed me: we don't know what happened, we are sending the order again. A day later I received the original shipment, and sent another Email to Amazon - I got the original shipment, you may stop the substitute one, the answer I got was even more amazing: We cannot trace an order once it was issued, keep the books with our compliments". It seems that now they know how to track their order.

Other two keynote speakers have been Mike Stonebraker and Michael Brodie, two old-timers, who have been around for a while. Stonebraker gave some variation about his repeating message: "One size fits all: A concept whose time has come and gone" which talk about the elephants (Oracle, Microsoft, IBM) DBMS product as an obsolete concept, and shows that for various types of functionality (including "stream processing", of course), a specialized engine is better than a monolithic one, and in fact, the monolithic engines excel at nothing and should be eliminated. The idea that one size does not fit all is probably true, in databases (and also in event processing), one thing to note (and this follows also Mike's talk in EDAPS yesterday), he looks on everything in a single criterion -- speed (latency ?), I think that reality is a little bit more complex.

Mike Brodie started with a nice video with music that was getting louder showing facts about quantities -- size of various databases, internet webpages, use of search engines etc -- and trend (the time everything is duplicated is getting shorter and shorter), he also talked briefly about SOA, and about the need to take a new approach that is application-based, semantics-based, and create Computer Science 2.0 -- however I did not understand what new science is required, and in response to a question he answered --- I presented the problems, leaving the solutions to you. I am not sure that I have understood the problem (except for engineering issues), but let's wait to see if computer science 2.0 will arrive (I think that the term 2.0 is starting to be over-hyped, there were some attempts at SOA 2.0 as combination of SOA and EDA, but I am not sure it caught as a buzzword). Anyway -- whatever Computer Science 2.0 is -- event processing should be one of its fundementals. More later.

EDAPS-07 and event processing research community

Hello from Vienna again. Today the event processing meetings festival, that started in the EPTS meeting exactly a week ago, continued (and ended) in Vienna with the EDAPS workshop adjecent to the VLDB conference. The EDAPS workshop was chaired by Ling Liu and myself. Unlike the previous meetings, EDAPS is a scientific workshop, where the accepted papers were selected by a program committee. This has been the second time we are doing this workshop, and it was attened by around 20 people with interesting papers. One of the issues we have discussed in the closing session is the creation of a unified research conference, this year there have been three such conferences: DEBS 2007, DEPSA 2007 and EDAPS, besides that other conferences like RULE-ML 2007 has some track on "reaction rules", while database conferences have tracks on "streams". Indeed, event processing has many roots - verification/simulation, active databases, stream management, pub/sub, distributed computing, rules, programming languages, sensor networks and maybe I forgot something, but the challange is to try and devise a community of researchers whose primary discipline will be event processing. A first step is to try and devise one annual conference that will unify all forces. We have proposed the DEBS steering committee to open up and make DEBS such a conference, as the "flagship" of the event processing community, and decided in 2008 not to hold EDAPS instance, to give a chance to DEBS to build a strong conference. Alex Buchmann who will chair the program committee of DEBS 2008 in Rome will work to extend the program committee and we'll help him recruit industry/vendors participation. In my opinion, a research community associated with event processing is important for the existance of event processing as an area and discipline.

One last comments about EDAPS - we have invited Mike Stonebraker to be keynote speaker, Mike is certainly a great speaker, however, he has chosen to wear his vendor hat, and provided sales pitch, with some assertions and generalizations that I wonder if Mike Stonebraker the distinguished scientist would have accepted for publication... well. Tomorrow, the VLDB conference - more later.