Commit 860d97f4 authored by Peter Waher's avatar Peter Waher

Concentrators

parent fd055fc8
Concentrator
==================
This document outlines the XML representation of interacting with concentrators and their underlying nodes, as defined by the IEEE XMPP IoT Working Group.
A concentrator "concentrates" a set of underlying physical or virtual devices, called *nodes*, into one unit using one XMPP address (network identity).
The XML representation is modelled using an annotated XML Schema:
| Sensor Data ||
| ------------|----------------------------------------------|
| Namespace: | urn:ieee:iot:concentrator:1.0 |
| Schema: | [Concentrator.xsd](Schemas/Concentrator.xsd) |
Motivation and design goal
----------------------------
The method of decision support described here, is designed with the following goals in mind:
* It should be possible to interact with a node, just as with any other device on the network.
* The design should support small/simple concentrators, such as PLCs or devices with a small number of embedded devices.
* The design should support protocol bridging, allowing devices communicating using one protocol to be bridged to XMPP by a bridge working as a concentrator.
* The design should support complex concentrators interfacing huge networks or back-end systems with huge sets of physical or logical devices, as if they
were connected to the XMPP network via a concentrator.
* It should be possible to manage a concentrator that chooses to allow this, allowing administrators to manage nodes and their lifecycles.
* A concentrator is free to implement a security architecture providing access to nodes to authorized clients only.
* It should be possible to discover available nodes in a concentrator, given sufficient privileges.
Extended addressing
-------------------------
Since all nodes behind a concentrator reside behind the same XMPP address, an additional addressing mechanism is required. For all interfaces relating to
IoT Harmonization, wether it be related to sensor data, control operations, decision support or provisioning, the following set of attributes are available
to address nodes in a concentrator. If the request does not include these attributes, it is assumed the receiver is not a concentrator.
| Attribute | Type | Description |
|:-----------|:--------------|:-------------------|
| `id` | `xs:string` | Node identity. |
| `src` | `xs:string` | Source identity. |
| `pt` | `xs:string` | Partition. |
Each node in a concentrator is at least identified by its *node identity*, provided in the `id` attribute. A concentrator might choose to group nodes
with similar properties in data/node *sources*. If so, the *source identity* is provided using the `src` attribute. Large concentrators might need to
sub-divide sources in *partitions*. If so, the partition is identified using the `pt` attribute. If an attribute is not provided, it is assumed to have
the value of the empty string. The quadruple (JID, `id`, `src`, `pt`) should always be unique.
...@@ -43,7 +43,7 @@ Data Protection and Privacy ...@@ -43,7 +43,7 @@ Data Protection and Privacy
Administration Administration
------------------- -------------------
* Concentrators * [Concentrators](Concentrator.md)
* Discovery * Discovery
* [Clock Synchronization](ClockSynchronization.md) * [Clock Synchronization](ClockSynchronization.md)
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment