Interoperation Modeling

849 views

Published on

Published in: Education, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
849
On SlideShare
0
From Embeds
0
Number of Embeds
10
Actions
Shares
0
Downloads
37
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Interoperation Modeling

  1. 1. Interoperation Modeling for Intelligent DomoticEnvironments <br />Dario Bonino, FulvioCorno<br />Politecnicodi Torino – e-Lite group<br />
  2. 2. Outline<br />Motivations<br />Device Modeling<br />Interconnection & Interoperation<br />Integration in DOG <br />Conclusions<br />19/11/2009<br />2<br />Interoperation Modeling for IDE, Dario Bonino - AmI&apos;09<br />
  3. 3. Motivations<br />Poor interoperation between domotic plants<br />No real standard support<br />KNX should be a European standard, but<br />Not free / open<br />Several manufacturers providing their own solutions<br />Network level bridges<br />Address only 2-way connections<br />Proprietary solution mostly master-slave<br />Research solutions<br />Mainly service based <br />Often require excessive duplication/replication<br />No Formal definition of Interoperation<br />Not tested/deployed on real domotic plants<br />19/11/2009<br />3<br />Interoperation Modeling for IDE, Dario Bonino - AmI&apos;09<br />
  4. 4. Intelligent Domotic Environment<br />19/11/2009<br />4<br />Interoperation Modeling for IDE, Dario Bonino - AmI&apos;09<br />
  5. 5. Domotic Environment Modeling<br />DogOnt [ISWC08]<br />Ontology-based formal modeling of domotic environments (OWL)<br />Technology independent device modeling<br />Formally represents interoperation semantics through relations [AMI09]<br />Supports automatic generation <br /> of interoperation rules [TCE09]<br />5<br />
  6. 6. Goal<br />19/11/2009<br />Interoperation Modeling for IDE, Dario Bonino - AmI&apos;09<br />6<br />Provide system designers with high-level, declarative view of interoperation strategies<br />To formally describe intercommunication between devices<br />OWL representation of device connections<br />Allow semantic query and reasoning<br />Modeling detail sufficient to support automatic generation of interoperation rules<br />Independence from network-specific issues<br />
  7. 7. DogOnt – Device Model<br />19/11/2009<br />7<br />Interoperation Modeling for IDE, Dario Bonino - AmI&apos;09<br />
  8. 8. Device Interconnection<br />8<br />has Functionality<br />has Functionality<br />Dimmer Lamp<br />Dimmer Lamp<br />has Functionality<br />has Functionality<br />LightRegulation Functionality<br />LightRegulation Functionality<br />OnOff Functionality<br />OnOff Functionality<br />has Command<br />has Command<br />controlledObject<br />has Command<br />has Command<br />Set Command<br />Set Command<br />Off Command<br />Off Command<br />Set(50%)<br />OnOff Switch<br />Off<br />generatesCommand<br />generatesCommand<br />has Functionality<br />On<br />OnNotification<br />Off<br />OffNotification<br />OnOffNotification<br />Functionality<br />has Notification<br />has Notification<br />
  9. 9. Interoperation<br />Whenever <br />Devices are not connected to the same network<br />Devices are not “speaking” the same protocol<br />Implemented through<br />Automatic Rule Generation<br />DOG<br />Domotic OSGi Gateway<br />19/11/2009<br />9<br />Interoperation Modeling for IDE, Dario Bonino - AmI&apos;09<br />
  10. 10. Automatic Rule Generation<br />SELECT DISTINCT ?x ?y ?v ?cv WHERE<br />{<br />?x a Controllable . ?y a Controllable .<br />?x controlledObject ?y . ?x hasFunctionality ?f.<br />?f hasNotification ?n . ?n notificationValue ?v.<br />?n generatesCommand ?c . ?d hasFunctionality ?f2.<br />?f2 dogont:hasCommand ?c . ?c rdf:type ?class .<br />?class rdfs:subClassOf DiscreteCommand .<br />?class rdfs:subClassOf [rdf:type owl:Restriction; owl:onProperty realCommandName; owl:hasValue ?cv]<br />}<br />rule “interoperation_rule_x”<br />when<br />rulesCore:DogRulesBundle()<br />dev:Device( id==rulesCore:get(?x))<br />cmd:StateCommand(state==rulesCore:get(?v))<br />status:DeviceStatus( status==cmd, device==dev)<br />message: DogMessage(dType==DEVICE_STATUS, data== status)<br />then<br />Device newDev = new Device(rulesCore:get(?y))<br />DeviceStatus newStatus = newDeviceStatus(newDev,<br /> new StateCommand(rulesCore.get(?cv),DISCRETE))<br />DogMessagemyCmd = new DogMessage(CMD,newGregorianCalendar(), message.getDataType(), newStatus)<br />rulesCore.takeActions(myCmd)<br />OWL Matching (SPARQL)<br />Generated Rules (DROOLs)<br />19/11/2009<br />10<br />Interoperation Modeling for IDE, Dario Bonino - AmI&apos;09<br />
  11. 11. Integration in DOG<br />DOG<br />19/11/2009<br />11<br />Interoperation Modeling for IDE, Dario Bonino - AmI&apos;09<br />
  12. 12. Experimental Setup<br />Real world benchmark <br />2 demo cases equipped with <br />MyOpen<br />KNX<br />Associations between all<br />control (buttons/switches)<br />and controllable (lamps)<br />58 automatically generated rules<br />Time required ~ 50 ms<br />Negligible runtime latency<br />19/11/2009<br />12<br />Interoperation Modeling for IDE, Dario Bonino - AmI&apos;09<br />
  13. 13. Conclusions<br />We designed an<br />ontology-based solution for device-to-device interoperation<br />Explicitly modeling interconnections supports<br />Higher-level design of automation scenarios<br />Automatic generation of rules<br />More advanced features<br />E.g. Dynamic composition of device functions<br />DOG integration<br />Allows ready exploitation of designed solutions<br />Download at http://domoticdog.sourceforge.net<br />19/11/2009<br />13<br />Interoperation Modeling for IDE, Dario Bonino - AmI&apos;09<br />
  14. 14. Dario Bonino<br />dario.bonino@polito.it<br />http://domoticdog.sourceforge.net<br />Questions?<br />19/11/2009<br />14<br />Interoperation Modeling for IDE, Dario Bonino - AmI&apos;09<br />

×