SPINE (Smart Premises Interoperable Neutral-message Exchange) defines a neutral layer which helps connecting different technologies to build a smart home/smart grid system. As SPINE only defines messages and procedures on application level, it is completely independent from the used transport protocol. Any technology that supports the bi-directional exchange of arbitrary data can be used more or less directly (e.g. SHIP (SmartHome IP) which is also created by the EEBus).
For other communications technologies a mapping is needed. Within this mapping, the possible data points are mapped as well as some protocol definitions. The capabilities of the existing technologies are very diverse, so each SPINE-to-technology mapping is different and (possibly) not all SPINE functions are supported.
Our EEBus SPINE module covers use cases concerning every kind of control and monitoring of smart appliances like:
White Goods
HVAC systems
Adjacent devices like batteries, e-cars, etc. (in contrast to rather small devices like temperature sensors, switches, etc.)
with a focus on the sectors of smart energy, smart home and building, connected devices, E-Mobility.
Domains like AAL (ambient assisted living), home entertainment, etc. are currently not in the focus, although some use cases from these domains can be realised with the already existing data model. The SPINE data model evolves continuously. Hence, further domains will be added in the future.
Feature Set
The EEBus SPINE module provides the following functionalities:
Support for all datatypes defined in EEBus SPINE specification, v1.1.0 beta1. This is not an official release, there may be changes when version is officially released!
Implementation of EEBus SPINE device exporter that allows easy extension of the local SPINE device (OSGi framework as SPINE device) with new entities, features and functions as well as virtual SPINE devices registered as OSGi services.
Support for Destination List function on the local SPINE device. All virtual SPINE devices are visible to the external devices in the SPINE network through this functionality.
Support for bindings and subscriptions to the features on the local SPINE device as well as the virtual SPINE devices, bindings and subscriptions are persisted upon OSGi framework restarts.
Implementation of DeviceClassification and DeviceDiagnosis features on the local SPINE device as separate bundles.These implementations are based on the defined EEBus SPINE device exporter.
Defined protocol-specific HDM Device Class API for a subset of the EEBus SPINE standard class features and functions. These are mainly the feature and functions involved in the EEBus E-Mobility uses cases – DeviceDiagnosis, DeviceConfiguration, DeviceIdentification, Measurements, LoadControlLimits, ElectricalConnections, TimeSeries, IncentiveTable, Bill.
Implemented the protocol-specific HDM Device Class API for the EEBus SPINE standard class features and functions as a separate DCO provider bundle for the HDM SPINE Adapter.
Compliant Devices - the EEBus SPINE module provides support for all EEBus SPINE Standard-compliant devices, with a subset of features as described in the feature set above.
Tested Devices - a number of production devices is fully tested with the latest release of the Bosch IoT Gateway software stack.
For a most up-to-date list of actual tested and compliant devices, visit Supported Devices.
Known Issues and Limitations
The EEBus SPINE module supports the EEBus v1.1.0 specification. The module will be subject to change once new versions of the specification are released. Backwards compatibility is not guaranteed.
Module Dependencies
The SPINE module depends on:
mDNS module;
Websockets module;
SHIP module;
Externals module.
Third Party
The following are the third party bundles used by SPINE module:
javax.jmdns.jar;
xml-apis.jar;
javax.annotation.jar;
javax.activation.jar;
javax.xml.bind.jar;
jackson-annotations.jar;
jackson-core.jar;
jackson-databind.jar;
jackson-module-jaxb-annotations.jar.
Licensing Information
Check the SPINE section in the Third-Party Licenses.
