Technical information exchange at the interface to the property and the elements of the customer's facilities located there
Part 6-3: SPINE; Text in English
Class/Status:
Draft,
valid
Released: 2025 -10 Published:
2025-09 -12
VDE Art. No.: 1801055
End of objection deadline:
2025-11-12
Note: You can pre-order this document (delivery subject to availability). Valid from 2025-10-01.
SPINE (Smart Premises Interoperable Neutral-message Exchange) defines a neutral layer which helps connecting different communications technologies to build a smart home / smart grid system. As SPINE only defines messages and procedures on application level (ISO-OSI layer 7), 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 – that is also created by the EEBus Initiative e.V. – or Thread). For each communications technology a mapping is needed, but for some this mapping is very simple (this is esp. the case for SHIP). 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. However, SPINE follows a modular concept that helps incorporating other technologies as much as possible. This finally leads to the possibility to create SPINE-based applications on one hand and then connect them to one or more technology mapping components on the other hand.
This Document is related to the following Topics (in bold):
We use cookies on our website. Some are necessary, while others help us to improve website performance
and are used to provide personalized advertising.
For more information, please see our
data protection policy.
Individual Cookie Settings
Necessary Cookies
cookie_consent (Validity: 1 year)
PHPSESSID (Temporary, is removed when the browser is closed)
Optional Cookies
_gcl_au (Validity: 90 days)
_uetvid (validity: 30 days) - Stores a unique visitor ID for tracking user interactions.
_uetsid (validity: 30 minutes) - Saves a session ID for tracking the current visitor session.