Differences

This shows you the differences between two versions of the page.

--- sensorweaver [2014-12-17 15:12] – luigi.fortunati
+++ sensorweaver [2017-09-26 07:08] (current) – michele
@@ Line 11: / Line 11: @@
 ===== Middleware =====
-Wireless Sensor networks are often etherogenous in terms of communication technologies and protocols and cover a limited spatial area. Applications that use sensor data needs are often run remotely and require a secure communication channel in order to access it over the Internet.
+Wireless Sensor networks are often heterogeneous in terms of communication technologies and protocols and cover a limited spatial area. Applications that use sensor data needs are often run remotely and require a secure communication channel in order to access it over the Internet.
-SensorWeaver Middleware tries to address the aforementioned issues by offering a practical and secure solution which enables secure communication between sensor nodes and applications that use sensor data.
+SensorWeaver Middleware tries to address the aforementioned issues by offering simple abstractions and API to clients and a distributed platform for secure communication between sensor nodes and applications that use context data.
 {{ ::componentdiagram.jpg|Sample deployment diagram depicting a scenario with ZigBee devices integration}}
-The functionalities offered by the Middleware to other software components covers different areas:
+The functionalities offered by the Middleware are based on the simple //datafeed// and //service// abstractions. A //datafeed// generally identifies an entity that produces data and can be characterized with a set of properties and a message content definition.
-  * Datasource publishing and sensor data dissemination
+There are two areas of functionalities concerning the datafeeds, one for data publishers and one for data consumers:
-    * Announce the presence of a new sensor by providing a description in terms of sensor properties and message format
+  * Datafeed publishing and sensor data dissemination
-    * Announce unavailability of a sensor
+    * Announce the presence of a new datafeed by providing a description in terms of sensor properties and message format
-    * Publish sensor data for a published sensor, using the defined message format
+    * Announce unavailability of a datafeed
-  * Sensor discovery and data listening
+    * Publish data for a published datafeed, using the defined message format
-    * Discover sensors matching a set of properties
+  * Datafeed discovery and data listening
-    * Listening for data produced by a sensor
+    * Discover datafeeds matching a set of properties
+    * Listening for data produced by a datafeed
-Sensors can also be virtual, in the sense that any data source can be represented as a data feed on the middleware, enabling sensor data fusion scenarios.
+Regarding the services, the following functionalities for both the publishers and the consumers are provided:
+  * Service publishing
+    * Announce the presence of a new service by providing a description of the properties, request message format and response message format
+    * Announce unavailability of a service
+    * Reply to a service invocation from a client
+  * Service discovery and invocation
+    * Discover services matching a set of properties
+    * Invoking a service and receiving a response
+Any data source can be represented as a //data feed// on the middleware, enabling a sensor data fusion scenario.
 The deployment diagram depicts a scenario where ZigBee devices are integrated with the Middleware.
@@ Line 46: / Line 56: @@
   *[[sensorweaver:developer-guide|SensorWeaver Developer Guide]]
   *[[sensorweaver:admin-guide|SensorWeaver Administrator Guide]]
+  *[[sensorweaver:sensor-feeds|SensorWeaver The Sensor Feeds]]