sensorweaver
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
sensorweaver [2014-12-17 15:01] – [SensorWeaver] luigi.fortunati | sensorweaver [2017-09-26 07:08] (current) – michele | ||
---|---|---|---|
Line 11: | Line 11: | ||
===== Middleware ===== | ===== Middleware ===== | ||
- | Wireless Sensor networks are often etherogenous | + | Wireless Sensor networks are often heterogeneous |
- | SensorWeaver Middleware tries to address the aforementioned issues by offering | + | SensorWeaver Middleware tries to address the aforementioned issues by offering |
{{ :: | {{ :: | ||
- | The functionalities offered by the Middleware | + | The functionalities offered by the Middleware |
- | * Datasource | + | 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 | + | * Datafeed |
- | * Announce unavailability of a sensor | + | * Announce the presence of a new datafeed |
- | * Publish | + | * Announce unavailability of a datafeed |
- | * Sensor | + | * Publish data for a published |
- | * Discover | + | * Datafeed |
- | * Listening for data produced by a sensor | + | * Discover |
+ | * 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 | + | 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 | ||
The deployment diagram depicts a scenario where ZigBee devices are integrated with the Middleware. | The deployment diagram depicts a scenario where ZigBee devices are integrated with the Middleware. | ||
Line 42: | Line 52: | ||
* Offers a simple model for the description/ | * Offers a simple model for the description/ | ||
* Strives for simplicity of integration | * Strives for simplicity of integration | ||
- | ==== Developer Guide ==== | ||
- | == Project and development environment setup == | ||
- | * IDE setup and repositories | ||
- | * Project setup | ||
- | * OSGi container of choice: Karaf | ||
- | == Getting an instance of the Middleware service == | ||
- | * OSGI Registry | ||
- | * Blueprint | ||
- | == API and usage == | ||
- | * Publishing sensor data | ||
- | * Getting sensor data | ||
- | == Integration testing == | ||
- | * Pax-Exam | ||
- | * Karaf | ||
- | == Links == | ||
- | * OSGi specs and compendium | ||
- | * Blueprint Aries | ||
- | * MQTT Protocol | ||
- | |||
- | ==== Administrator Guide ==== | ||
- | |||
- | |||
- | |||
+ | Links to guides: | ||
+ | *[[sensorweaver: | ||
+ | *[[sensorweaver: | ||
+ | *[[sensorweaver: |
sensorweaver.1418828477.txt.gz · Last modified: 2014-12-17 15:01 by luigi.fortunati