Difference between revisions of "Tech pages/SensorNetworks"
(3 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
This has moved to [[Tech_pages/IoT_systems]] | |||
== Overview == | == Overview == | ||
* Abstract interface description, describing available sensor resources (readable/writable values, data types, meta information, etc.) | |||
* Request/response mechanism for readout. | |||
* Request/response mechanism for output. | |||
* Spontaneous reporting of momentary values based on subscription rules, hysteresis levels, and/or other logic. | |||
* Node topology information (if sensor part of larger whole, like a concentrator, for instance). | |||
* Abstract metering data description, including: | |||
o Timestamps | |||
o Description | |||
o Units (if numerical) | |||
o Precision (if numerical) | |||
o Statuses (sequence of flags: error, QoS, tampering, etc.) | |||
o Data types (numerical, Boolean, string, date & time, enum, time span) | |||
o Value Types (momentary values, historical values, status values, informative values, etc.) | |||
o Localization information | |||
Line 53: | Line 90: | ||
devices, and other devices intermittently available on the network. | devices, and other devices intermittently available on the network. | ||
== | == Interoperability Specification == | ||
In all networks that combines information from different systems over business and technology borders the crucial thing is to get interoperability. | In all networks that combines information from different systems over business and technology borders the crucial thing is to get interoperability. And there is no other way to do this than creating specifications that adds the "common good practices" to make things speak the same language. The interoperability spec will be a moving target with constant elaboration to enable true interoperability between systems | ||
* xep-0000-SN-Interoperability | * xep-0000-SN-Interoperability |
Latest revision as of 10:30, 13 June 2013
This has moved to Tech_pages/IoT_systems
Overview
- Abstract interface description, describing available sensor resources (readable/writable values, data types, meta information, etc.)
- Request/response mechanism for readout.
- Request/response mechanism for output.
- Spontaneous reporting of momentary values based on subscription rules, hysteresis levels, and/or other logic.
- Node topology information (if sensor part of larger whole, like a concentrator, for instance).
- Abstract metering data description, including:
o Timestamps o Description o Units (if numerical) o Precision (if numerical) o Statuses (sequence of flags: error, QoS, tampering, etc.) o Data types (numerical, Boolean, string, date & time, enum, time span) o Value Types (momentary values, historical values, status values, informative values, etc.) o Localization information
Base Specifications
To create this interoperable sensor network usage of XMPP a set of xep extensions has been created. The core is 4 xeps that together describes more or less any sensor actuator network.
Provides the underlying architecture, basic operations and data structures for sensor data communication over XMPP networks. It includes a hardware abstraction model, removing any technical detail implemented in underlying technologies. This XEP is used by all other sensor network XEPs.
Defines how to control actuators and other devices in sensor networks.
Defines how to handle architectures containing concentrators or servers handling multiple sensors.
This specification. Defines how provisioning, the management of access privileges, etc., can be efficiently and easily implemented.
Enhancing Specifications
To
- xep-0000-SN-Discovery
Defines the peculiars of sensor discovery in sensor networks. Apart from discovering sensors by JID, it also defines how to discover sensors based on location, etc.
- xep-0000-SN-Events
Defines how sensors send events, how event subscription, hysteresis levels, etc., are configured.
- xep-0000-SN-Multicast
Defines how sensor data can be multicast in efficient ways.
- xep-0000-SN-PubSub
Defines how efficient publication of sensor data can be made in sensor networks.
- xep-0000-SN-BatteryPoweredSensors
Defines how to handle the peculiars related to battery powered devices, and other devices intermittently available on the network.
Interoperability Specification
In all networks that combines information from different systems over business and technology borders the crucial thing is to get interoperability. And there is no other way to do this than creating specifications that adds the "common good practices" to make things speak the same language. The interoperability spec will be a moving target with constant elaboration to enable true interoperability between systems
- xep-0000-SN-Interoperability
Defines guidelines for how to achieve interoperability in sensor networks, publishing interoperability interfaces for different types of devices.
Supporting Specifications
- XEP-0000-ColorParameter
Defines extensions for how color parameters can be handled, based on Data Forms [1]
- XEP-0000-DynamicForms
Defines extensions for how dynamic forms can be created, based on Data Forms [2], Data Forms Validation [3], Publishing Stream Initiation Requests [4] and Data Forms Layout [5].
Defines how to EXI can be used in XMPP to achieve efficient compression of data. Albeit not a sensor network specific XEP, this XEP should be considered in all sensor network implementations where memory and packet size is an issue.
Implementations
Servers
Clients
Libraries
Discussion Venues
Main author
Email: peter.waher@clayster.com JabberID: peter.waher@jabber.org URI: http://se.linkedin.com/pub/peter-waher/1a/71b/a29/
Co working and Managed by
Email: joachim.lindborg@sust.se URI: http://se.linkedin.com/in/joachimlindborg/