vittorio miori Ð dario russo rolando bianchi...

A solution for heterogeneous

domotic systems integration

La Habana, Cuba - 29 de noviembre al 3 de diciembre de 2010

Vittorio Miori – Dario Russo

Rolando Bianchi Bandinelli

La Habana 2/12/2010

2

Domotics Laboratory at I.S.T.I. (Institute of Science

and Information Technologies of the National Research

Council of Italy– Pisa)

The context



3

Summary

• The Domotics

• Problems

• The solution

• The details

• The future



4

What is domotics?

• New technologies for integrating all housedevices in one system in order to achievehome and buildings automation and smarthouses

• Advantages:• Comfort (Wellness)

• Security, intended as "safety" or as "security"

• Increased independence (for elderly and disabled people)

• Energy saving

• Entertainment

• Remote Control

• Access to external services

5

• A set of hardware/software technologies to build-up

working home networks and applications

• Using different communication standards (Ethernet,

FireWire, Bluetooth, Wi-Fi, dedicated buses, etc…)

• Promoted by different consortia and typically constitute

proprietary standards

• Konnex, EIB, BatiBUS, EHS, X10, CEBus, LonWorks,

HAVi, Jini, OSGi, UPnP

Domotic middlewares



6

• Because of lack of knowledge often the usersare still suspicious of real benefits derivingfrom domotic devices and installations

• Too many domotic middlewares and lack of auniversally recognized domotic standard

• Little interoperability between differentmiddlewares

• Too many standards drive up costs

Why the domotic doesn’t take off?



7

History repeating…

• ICT market situation in ‘70s/’80s

– Many proprietary network protocols… then

! Introduction of TCP/IP the standard

– Many database protocols … then

! Introduction of ODBC

– Video tape many proprietary … then

! Introduction of VHS

…………



8

• Building an infrastructure based onstandard technologies independent of alldomotic middlewares

• Developing a standard formalism to convoyinformation on this infrastructure, toguarantee the comprehension between alldomotic devices

A possible solution



9

• Based on a Service Oriented Architecture

(SOA) model, in which services coincide with

devices’ functionalities

• Using the emergent standard communication

paradigm in distributed SOA domain: Web

Services

• Using a univocal formalism: DomoML

(Domotic Markup Language)

DomoNet Framework



10

TCP/IP

Web Services

DomoML

DomoNet: protocol stack



11

• An XML standard grammar that aims tobecome the universal language in everydomotic context

• As generic as possible

• A sort of lingua franca between entitiesin the DomoNet infrastructure

DomoML



12

DomoML

• The grammar specifications have beendefined.

• An example of the grammar, in order to setup DomoNet prototype, has beenimplemented.

• The complete implementation should berealized after an agreement between themost important household applianceproducers.



13

DomoNET

JiniX10

UPnP

Konnex

LonHAVi

JiniManager

X10Manager

UPnPManager

HAViManager

LonManager

KNXManager

DomoNet

14

DomoNetDeviceWS_1

DeviceWS_2

DeviceWS_n

DomoNet: from up above



15

• It manages a specific device category

(Lighting, Heating, Safety, etc…)

• It has a standard service interface and useful

data structures

• It uses an addressing mechanism in order to

identify the devices in DomoNet

• It exposes the devices it manages, to all

domotic middlewares in a standard way

DeviceWS: Device Web

Service



16

• The software module working as an application

gateway between a domotic middleware and the

DomoNet framework

• Installed on a computer with interfaces towards both

the domotic middleware and DomoNet

• Translating the standard formalism DomoML in the

formalism of the middleware which is related to, and

vice versa

• Its implementation can be partially automated through

the use of XML-Schemas of DomoML

TechManager



17

• The prototype managed only Lighting devices

• It considered 3 domotic middlewares (Konnex, UPnP

and X10)

• It was composed by:

• three TechManagers developed on different

platforms (Java and .NET)

• a DeviceWS (LightsWS)

• a web interface and a mobile application at

DomoNet / DeviceWS-level

DomoNet: the first prototype



18

The evolution: a typical flat has been

simulated using several standards

The entrance

19

Mutimedia integrated in the system

KNX

KNX

KNX

KNX

KNX

KNX

KNX

UPnP

WMC

WiFi

20

Kitchen and bathroom

KNX

MyHome

KNX

KNX

MyHome

21

The bedroom

22

• Integration with other research projects of the Domotics

Laboratory (i.e. NICHE – http://niche.isti.cnr.it)

• Use of new Web Services standards (WSE 3.0)

• Development of more friendly interfaces for mobile

devices

• Integration with PUC (Personal Universal Controller)

research project(http://www.pebbles.hcii.cmu.edu/puc/ – Carnegie Mellon University)

Old projects where we have

used Domonet



23

• DAGON (Domotics and Automation Government and

Orchestration Network) - Project aimed to developand install domotic systems in the marine area

– Nextworks s.r.l.

– Wonder-sys

– Life Troni

– Promi

– ISTI-CNR “Laboratorio di domotica)

Current project where

Domonet is used



Thank you

More details

26

The generic TechManager retrieves DomoNET WebServices (DeviceWSs), through UDDI.

It can invoke the standard services that DeviceWSsexpose, to:

1) registrer itself to interesting DeviceWSs,

2) export to DomoNet the network configuration of its domoticmiddleware,

3) obtain the devices managed by each DeviceWS which it isregistered to,

4) update the entire domotic network topology, through thevirtualization of all the devices previously obtained.

The interaction model



27

Devices’ interaction

At runtime, each middleware has a set of real and

virtual devices.

Use of mapping structures both in TechManagers and

DeviceWSs.

The DomoNet framework intermediates the

interactions between devices belonging to different

middlewares.



28

Web

Interface

LightsWS

DomoNet: the prototype

Mobile

Interface

29

DomoML: an example

30

DomoML: an example (2)



31

Konnex components

! Bus Konnex/EIB (TP1)

! BCU (interface between PC and bus via RS232)

! Siemens actuator with 4 exits (4 leds)

! A/C Adapter

! ABB dimmer linked to a bulb

! Siemens 8 push-buttons with IR remote control

32

• S-Mode Konnex devices

• ETS2 software to configure the network

• Translation of ETS2 output into KNXManagerinput

Konnex configuration



33

Konnex/EIB

RS232

<…>………

</…>

KNXConfiguration.xml

Konnex configuration

ETS2KNXManager



34

• Developed in Java on Windows platform,

using NetBeans 4.1 IDE

• Uses Falcon libraries distibuted by Konnex/EIB

for bus interaction

• Uses JWSDP 1.5 and Apache Axis 1.2 for the

interaction with Web Services

• With a simple user interface

KNXManager



35

Bus KNX/EIB

KNXLightingTranslator

KNXLightingController

KNXDevice

…

. . .KNXHeatingController

KNXHeatingTranslator …

KNXDevice

KNXDeviceController

KNXServer KNXConfigurationParser<…>

…

</…>

KNXManager software architecture

36

UPnP components

• A UPnP control point

(Intel DeviceSpy)

• Some UPnP appliances

(Intel Light Bulb)



37

• TCP/IP network

• Plug And Play so no need forconfiguration

UPnP configuration



38

• Developed in C# on the Windows

platform with .NET Framework, using

Visual Studio .NET 2003 IDE

• Uses UPNP.dll library distibuted by

INTEL to control devices

• With a simple user interface

UPnPManager



39

KNXManager

UPnPManager

TechManagers: user

interfaces



40

X10

LightsWS

UPnP Konnex

Test scenario

41

• Possible solution to the interoperabilityproblem in domotic domains

• Development of a limited, but wide tested andworking prototype

• Demonstration of interoperability betweendistributed application on different platforms(Java e .NET), using the Web Servicesparadigm

Reached objectives



42

• New DeviceWSs or creation ofgeneral purpose web services?(Audio/Video, white goods, ecc…)

• New TechManagers

• Entities controlling automation atDomoNet level

Possible advances



43

• Integration with other research projects of the

Domotics Laboratory (i.e. NICHE – http://niche.isti.cnr.it)

• Use of new Web Services standards (WSE 3.0)

• Development of more friendly interfaces for

mobile devices

• Integration with PUC (Personal Universal

Controller) research project(http://www.pebbles.hcii.cmu.edu/puc/ – Carnegie Mellon University)

What else?



44

Please contact

• Vittorio Miori, I.S.T.I. - C.N.R., Pisa –

Italy

– Tel.: +39 050 315 3007

– E-mail: [email protected]



vittorio miori Ð dario russo rolando bianchi...

Documents