Skip to content
aleant edited this page Jul 1, 2014 · 2 revisions

The CUPUS middleware is a content-based publish/subscribe, i.e., it supports stateless Boolean subscriptions, and top-k subscriptions over sliding windows (top-k/w subscriptions) that are stateful. It is designed to enable pre-filtering of sensor data streams close to data sources, e.g., on mobile devices, such that only data of interest and value to various subscribers is pushed into the publish/subscribe cloud. Note that the filtering process is not guided locally on mobile devices, but from the cloud based on global data requirements. Moreover, the CUPUS cloud distributes push-based notifications from the cloud to largely distributed destinations, e.g., mobile devices, in near real-time

The CUPUS middleware consists of the Cloud Broker and external entities such as subscirbers, publishers or mobile brokers. The OpenIoT Cloud Broker, i.e., the CPSP engine, accepts all messages from subscriber, publisher or mobile broker entities, based on user or ICO inputs. After processing the message, the cloud broker if necessary sends a notification or subscription to the end user entity (a subscriber, publisher or mobile broker)

Clone this wiki locally