interoperation modeling

INTEROPERATION MODELING FOR INTELLIGENT DOMOTICENVIRONMENTS

Dario Bonino, Fulvio Corno

Politecnico di Torino – e-Lite group

Interoperation Modeling for IDE, Dario Bonino - AmI'09

2

Outline

Motivations Device Modeling Interconnection & Interoperation Integration in DOG Conclusions

19/11/2009


3

Motivations

Poor interoperation between domotic plants No real standard support

KNX should be a European standard, but Not free / open Several manufacturers providing their own solutions

Network level bridges Address only 2-way connections Proprietary solution mostly master-slave

Research solutions Mainly service based Often require excessive duplication/replication No Formal definition of Interoperation Not tested/deployed on real domotic plants

19/11/2009


4

Intelligent Domotic Environment

19/11/2009

5

Domotic Environment Modeling DogOnt [ISWC08] Ontology-based formal modeling of

domotic environments (OWL) Technology independent device modeling Formally represents interoperation

semantics through relations [AMI09] Supports automatic generation

of interoperation rules [TCE09]


6

Goal

19/11/2009

Provide system designers with high-level, declarative view of interoperation strategies

To formally describe intercommunication between devices OWL representation of device connections Allow semantic query and reasoning Modeling detail sufficient to support

automatic generation of interoperation rules

Independence from network-specific issues


7

DogOnt – Device Model

19/11/2009

8

Device Interconnection

Dimmer Lamp

LightRegulation

Functionality

OnOff Functionalit

y

Set Command Off

Command

has Functionalityhas Functionality

has Command has Command

OnOff Switch

OnOffNotification

Functionality

OnNotification

OffNotification

has Functionality

has Notificationhas Notification

controlledObject

generatesCommandgeneratesCommand

Set(50%)

On

Off

Off

Dimmer Lamp

LightRegulation

Functionality

OnOff Functionalit

y

Set Command Off

Command

has Functionalityhas Functionality

has Command has Command


9

Interoperation

Whenever Devices are not connected to the same

network Devices are not “speaking” the same

protocol Implemented through

Automatic Rule Generation DOG

Domotic OSGi Gateway

19/11/2009


Automatic Rule Generation

SELECT DISTINCT ?x ?y ?v ?cv WHERE

{

?x a Controllable . ?y a Controllable .

?x controlledObject ?y . ?x hasFunctionality ?f.

?f hasNotification ?n . ?n notificationValue ?v.

?n generatesCommand ?c . ?d hasFunctionality ?f2.

?f2 dogont:hasCommand ?c . ?c rdf:type ?class .

?class rdfs:subClassOf DiscreteCommand .

?class rdfs:subClassOf [rdf:type owl:Restriction; owl:onProperty realCommandName; owl:hasValue ?cv]

}

rule “interoperation_rule_x”

whenrulesCore:DogRulesBundle()dev:Device( id==rulesCore:get(?x))cmd:StateCommand(state==rulesCore:g

et(?v))status:DeviceStatus( status==cmd,

device==dev)message:

DogMessage(dType==DEVICE_STATUS, data== status)

thenDevice newDev = new

Device(rulesCore:get(?y))DeviceStatus newStatus =

newDeviceStatus(newDev, new StateCommand(rulesCore.get(?

cv),DISCRETE))DogMessage myCmd = new

DogMessage(CMD,new GregorianCalendar(), message.getDataType(), newStatus)

rulesCore.takeActions(myCmd)

OWL Matching (SPARQL)Generated Rules (DROOLs)

19/11/2009

10


Integration in DOG

DOG

19/11/2009

11


12

Experimental Setup

Real world benchmark 2 demo cases equipped with

MyOpen KNX

Associations between all control (buttons/switches) and controllable (lamps)

58 automatically generated rules Time required ~ 50 ms Negligible runtime latency

19/11/2009


13

Conclusions

We designed an ontology-based solution for device-to-device

interoperation Explicitly modeling interconnections supports

Higher-level design of automation scenarios Automatic generation of rules

More advanced features E.g. Dynamic composition of device functions

DOG integration Allows ready exploitation of designed solutions Download at http://domoticdog.sourceforge.net

19/11/2009


Dario [email protected]

http://domoticdog.sourceforge.net

Questions?

19/11/2009

14

interoperation modeling

Education

netquest modeling

rule interoperation

device id

interoperation semantics

motivationspoor interoperation

x hasfunctionality

type owl

class rdfs