EEBus SPINE Datatypes

The EEBus SPINE Datatypes are:

• Auto-generated Java classes from EEBus SPINE XML Schemas;
• Used by EEBus SPINE transport implementations, EEBus SPINE protocol driver and EEBus SPINE DCO providers.

EEBus SPINE Transport Layer

The EEBus SPINE Transport Layer provides:

• Abstraction for underlaying transport for EEBus SPINE datagrams.
• Different implementations – SHIP (default), AllJoyn, etc.

SHIP (Smart Home IP)

• See SHIP Technical Documentation

EEBus SPINE Protocol Layer

EEBus SPINE Protocol Driver

The EEBus SPINE Protocol driver is independent of the underlaying transport. It uses EEBus SPINE datatypes and provides:

• Listing of the available EEBus SPINE devices.
• Detailed information of a certain EEBus SPINE device.
• Sending command requests towards the EEBus SPINE devices.
• Receiving replies and notifications from the EEBus SPINE devices.

EEBus SPINE Device Exporter

• Provides an API for exporting EEBus SPINE devices which are implemented as OSGi services.
• Allows to implement a bridge between any other home protocol and EEBus SPINE, e.g. ZigBee-to-EEBus SPINE.
• Independent of the EEBus SPINE transport.

EEBus SPINE HDM Adapter Layer

This layer consists of:

• EEBus SPINE HDM Adapter Core, which provides:
  • Integration of the EEBus SPINE devices with the Home Device Manager so that EEBus SPINE devices can be managed trough the abstraction layer of HDM.
  • Pluggable model for DCO Providers so that third parties can support new EEBus SPINE features and new device classes.

• EEBus SPINE Standart Classes DCO Provider

• EEBus Spine Smart Energy DCO Provider
  • DCO provider implementation for EEBus SPINE Smart Energy Management Power Sequences and white goods appliances.

• Other DCO providers are implemented as separate bundles and can be plugged within the EEBus SPINE HDM Adapter.