Semantic Web for AAL

826 views

Published on

Robust solutions for ambient assisted living are numerous, yet predominantly specific in their scope of usability. This presentation describes the contribution of the service oriented architecture combined with semantic web technologies in order to build more versatile solutions — a step towards adaptable context-aware engines and simplified deployments. Our design and deployment work in hindsight, we highlight some requirements for semantic web tools that would help with real-life deployment of semantically driven assistive technologies. We also describe our current service platform developed as an integrated solution for AAL.
-- A research work from IPAL Lab, Singapore.

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

  • Be the first to like this

No Downloads
Views
Total views
826
On SlideShare
0
From Embeds
0
Number of Embeds
121
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • \n
  • \n
  • AAL: set of ubiquitous technologies embedded in living space to provide pervasive access to context-aware assistive services. EX: enhance aging in place by helping elderly people with their ADL.\n[#]\nmap nh\n
  • AAL: set of ubiquitous technologies embedded in living space to provide pervasive access to context-aware assistive services. EX: enhance aging in place by helping elderly people with their ADL.\n[#]\nmap nh\n
  • AAL: set of ubiquitous technologies embedded in living space to provide pervasive access to context-aware assistive services. EX: enhance aging in place by helping elderly people with their ADL.\n[#]\nmap nh\n
  • introduce term entities\nbig idea = modularity, flexibility to go towards deployability without loosing customizability\n[#1] > SOA [#2] > PNP\n?!? whose device? where is the light?\n[#3] > semantic = common language/understanding to describe entities/environ > interoperable > semantic P&P (role1)\n > reasoning (role2)\nimperative = application specific, robust, short design phase\ndeclarative = reusable code by splitting application logic and underlying models, better maintenance \n
  • introduce term entities\nbig idea = modularity, flexibility to go towards deployability without loosing customizability\n[#1] > SOA [#2] > PNP\n?!? whose device? where is the light?\n[#3] > semantic = common language/understanding to describe entities/environ > interoperable > semantic P&P (role1)\n > reasoning (role2)\nimperative = application specific, robust, short design phase\ndeclarative = reusable code by splitting application logic and underlying models, better maintenance \n
  • introduce term entities\nbig idea = modularity, flexibility to go towards deployability without loosing customizability\n[#1] > SOA [#2] > PNP\n?!? whose device? where is the light?\n[#3] > semantic = common language/understanding to describe entities/environ > interoperable > semantic P&P (role1)\n > reasoning (role2)\nimperative = application specific, robust, short design phase\ndeclarative = reusable code by splitting application logic and underlying models, better maintenance \n
  • introduce term entities\nbig idea = modularity, flexibility to go towards deployability without loosing customizability\n[#1] > SOA [#2] > PNP\n?!? whose device? where is the light?\n[#3] > semantic = common language/understanding to describe entities/environ > interoperable > semantic P&P (role1)\n > reasoning (role2)\nimperative = application specific, robust, short design phase\ndeclarative = reusable code by splitting application logic and underlying models, better maintenance \n
  • introduce term entities\nbig idea = modularity, flexibility to go towards deployability without loosing customizability\n[#1] > SOA [#2] > PNP\n?!? whose device? where is the light?\n[#3] > semantic = common language/understanding to describe entities/environ > interoperable > semantic P&P (role1)\n > reasoning (role2)\nimperative = application specific, robust, short design phase\ndeclarative = reusable code by splitting application logic and underlying models, better maintenance \n
  • introduce term entities\nbig idea = modularity, flexibility to go towards deployability without loosing customizability\n[#1] > SOA [#2] > PNP\n?!? whose device? where is the light?\n[#3] > semantic = common language/understanding to describe entities/environ > interoperable > semantic P&P (role1)\n > reasoning (role2)\nimperative = application specific, robust, short design phase\ndeclarative = reusable code by splitting application logic and underlying models, better maintenance \n
  • introduce term entities\nbig idea = modularity, flexibility to go towards deployability without loosing customizability\n[#1] > SOA [#2] > PNP\n?!? whose device? where is the light?\n[#3] > semantic = common language/understanding to describe entities/environ > interoperable > semantic P&P (role1)\n > reasoning (role2)\nimperative = application specific, robust, short design phase\ndeclarative = reusable code by splitting application logic and underlying models, better maintenance \n
  • introduce term entities\nbig idea = modularity, flexibility to go towards deployability without loosing customizability\n[#1] > SOA [#2] > PNP\n?!? whose device? where is the light?\n[#3] > semantic = common language/understanding to describe entities/environ > interoperable > semantic P&P (role1)\n > reasoning (role2)\nimperative = application specific, robust, short design phase\ndeclarative = reusable code by splitting application logic and underlying models, better maintenance \n
  • introduce term entities\nbig idea = modularity, flexibility to go towards deployability without loosing customizability\n[#1] > SOA [#2] > PNP\n?!? whose device? where is the light?\n[#3] > semantic = common language/understanding to describe entities/environ > interoperable > semantic P&P (role1)\n > reasoning (role2)\nimperative = application specific, robust, short design phase\ndeclarative = reusable code by splitting application logic and underlying models, better maintenance \n
  • introduce term entities\nbig idea = modularity, flexibility to go towards deployability without loosing customizability\n[#1] > SOA [#2] > PNP\n?!? whose device? where is the light?\n[#3] > semantic = common language/understanding to describe entities/environ > interoperable > semantic P&P (role1)\n > reasoning (role2)\nimperative = application specific, robust, short design phase\ndeclarative = reusable code by splitting application logic and underlying models, better maintenance \n
  • introduce term entities\nbig idea = modularity, flexibility to go towards deployability without loosing customizability\n[#1] > SOA [#2] > PNP\n?!? whose device? where is the light?\n[#3] > semantic = common language/understanding to describe entities/environ > interoperable > semantic P&P (role1)\n > reasoning (role2)\nimperative = application specific, robust, short design phase\ndeclarative = reusable code by splitting application logic and underlying models, better maintenance \n
  • introduce term entities\nbig idea = modularity, flexibility to go towards deployability without loosing customizability\n[#1] > SOA [#2] > PNP\n?!? whose device? where is the light?\n[#3] > semantic = common language/understanding to describe entities/environ > interoperable > semantic P&P (role1)\n > reasoning (role2)\nimperative = application specific, robust, short design phase\ndeclarative = reusable code by splitting application logic and underlying models, better maintenance \n
  • WANTED: graph repr. > delete auto nodes branching downwards\n[#] > monotonicity\nsolutions: 1. higher complexity = tried and not enthusiastic\n2. no live state is good > explain\n
  • WANTED: graph repr. > delete auto nodes branching downwards\n[#] > monotonicity\nsolutions: 1. higher complexity = tried and not enthusiastic\n2. no live state is good > explain\n
  • WANTED: graph repr. > delete auto nodes branching downwards\n[#] > monotonicity\nsolutions: 1. higher complexity = tried and not enthusiastic\n2. no live state is good > explain\n
  • WANTED: graph repr. > delete auto nodes branching downwards\n[#] > monotonicity\nsolutions: 1. higher complexity = tried and not enthusiastic\n2. no live state is good > explain\n
  • WANTED: graph repr. > delete auto nodes branching downwards\n[#] > monotonicity\nsolutions: 1. higher complexity = tried and not enthusiastic\n2. no live state is good > explain\n
  • WANTED: graph repr. > delete auto nodes branching downwards\n[#] > monotonicity\nsolutions: 1. higher complexity = tried and not enthusiastic\n2. no live state is good > explain\n
  • WANTED: graph repr. > delete auto nodes branching downwards\n[#] > monotonicity\nsolutions: 1. higher complexity = tried and not enthusiastic\n2. no live state is good > explain\n
  • dynamic data contrary of web data for which SW is designed\n[#]\nexplosion of number of triples\ninterconnection of events + linked data philosophy > keep one big ontology\n
  • dynamic data contrary of web data for which SW is designed\n[#]\nexplosion of number of triples\ninterconnection of events + linked data philosophy > keep one big ontology\n
  • make it short!\n
  • make it short!\n
  • \n
  • \n
  • \n
  • \n
  • SOA > bundles\nplug’n’play: WSMS + auto-generation of bundle then DPWS advertise & discovery (web service techno for device connection)\n> add semantics (& same on device side)\nreasoning: euler as bundle, continuous inference, ontology in files updated\n> go through files then 1 to 6\n
  • SOA > bundles\nplug’n’play: WSMS + auto-generation of bundle then DPWS advertise & discovery (web service techno for device connection)\n> add semantics (& same on device side)\nreasoning: euler as bundle, continuous inference, ontology in files updated\n> go through files then 1 to 6\n
  • SOA > bundles\nplug’n’play: WSMS + auto-generation of bundle then DPWS advertise & discovery (web service techno for device connection)\n> add semantics (& same on device side)\nreasoning: euler as bundle, continuous inference, ontology in files updated\n> go through files then 1 to 6\n
  • SOA > bundles\nplug’n’play: WSMS + auto-generation of bundle then DPWS advertise & discovery (web service techno for device connection)\n> add semantics (& same on device side)\nreasoning: euler as bundle, continuous inference, ontology in files updated\n> go through files then 1 to 6\n
  • SOA > bundles\nplug’n’play: WSMS + auto-generation of bundle then DPWS advertise & discovery (web service techno for device connection)\n> add semantics (& same on device side)\nreasoning: euler as bundle, continuous inference, ontology in files updated\n> go through files then 1 to 6\n
  • SOA > bundles\nplug’n’play: WSMS + auto-generation of bundle then DPWS advertise & discovery (web service techno for device connection)\n> add semantics (& same on device side)\nreasoning: euler as bundle, continuous inference, ontology in files updated\n> go through files then 1 to 6\n
  • \n
  • 2 main aspects\nPB now: 1. environment pre-described (user specs, space organization,etc.)\n2. sensors must be configured in the lab, we want to buy on the way\n> conf. tool, extend P&P, already basic behavior done, add semantic\n[#]\nLimitations: contrary to device selection well parametrized, services described at low level: what deviance do they solve\n> parametrize this, rules on parameters\n> hard: non-deterministic, infinite possibilities, heterogeneity of actions...\n
  • 2 main aspects\nPB now: 1. environment pre-described (user specs, space organization,etc.)\n2. sensors must be configured in the lab, we want to buy on the way\n> conf. tool, extend P&P, already basic behavior done, add semantic\n[#]\nLimitations: contrary to device selection well parametrized, services described at low level: what deviance do they solve\n> parametrize this, rules on parameters\n> hard: non-deterministic, infinite possibilities, heterogeneity of actions...\n
  • \n
  • \n
  • Semantic Web for AAL

    1. 1. SEMANTIC WEB FOR AAL Design & Deployment - Lessons Learned Thibaut Tiberghien January, 18th 2012 www.ipal.cnrs.fr
    2. 2. CONTENTS‣ Some background‣ Our take on AAL: 2 thesis - 2 approaches - 1 convergence point‣ Semantic web for AAL - Requirements on technology - Technology selection‣ Our service platform, an integrated solution‣ Next? Smart space composer 2
    3. 3. SOME BACKGROUND 3
    4. 4. SOME BACKGROUND‣ Ambient Assisted Living (AAL) 3
    5. 5. SOME BACKGROUND‣ Ambient Assisted Living (AAL)‣ AMUPADH deployment in Peacehaven nursing home iPhone/Android for nurse (3G) IPTV (Wi-Fi) Shower Bed Cupboard Nursing console (Wi-Fi) Shake sensor Passive infrared Speaker (Bluetooth) RFID bracelet on resident Pressure sensor Tiny debian machine ZigBee gateway RFID reader Wi-Fi router over ZigBee 3
    6. 6. OUR TAKE ON THIS! 4
    7. 7. OUR TAKE ON THIS! End-user Services Reasoning Engine (Context Awareness) Sensors Devices Actuators 4
    8. 8. OUR TAKE ON THIS!‣ Service oriented architecture (SOA) - dynamic class loading End-user Services - publish & subscribe Reasoning Engine (Context Awareness) OSGi container Sensors Devices Actuators 4
    9. 9. OUR TAKE ON THIS!‣ Service oriented architecture (SOA) - dynamic class loading End-user SOA software representation Services of plug&play agents - publish & subscribe Reasoning Engine‣ SOA based plug’n’play (Context Awareness) OSGi container - loose coupling (mechanical) plug & play Sensors Devices Actuators 4
    10. 10. OUR TAKE ON THIS!‣ Service oriented architecture (SOA) - dynamic class loading End-user SOA software representation Services of plug&play agents - publish & subscribe Reasoning Engine‣ SOA based plug’n’play (Context Awareness) OSGi container - loose coupling (mechanical) plug & play‣ Semantics Sensors Devices Actuators - loose coupling (semantic) - semantic reasoning, description logic (declarative) 4
    11. 11. SEMANTIC WEB FOR AAL Requirements gathering 5
    12. 12. SEMANTIC WEB FOR AAL Requirements gathering‣ Retractability of information - contextual information is dynamic & temporal - ease to retract information: asserted & inferred 5
    13. 13. SEMANTIC WEB FOR AAL Requirements gathering‣ Retractability of information - contextual information is dynamic & temporal - ease to retract information: asserted & inferred - opposition to RDF monotonicity assumption - Solutions: - higher complexity in reasoner’s language - no live state reasoner 5
    14. 14. SEMANTIC WEB FOR AAL Requirements gathering 6
    15. 15. SEMANTIC WEB FOR AAL Requirements gathering‣ Processing efficiency - real-time constraints - highly dynamic data - embedded devices 6
    16. 16. SEMANTIC WEB FOR AAL Requirements gathering‣ Processing efficiency - real-time constraints - highly dynamic data - embedded devices‣ Scalability - size of monitored space? room, building, smart city... - keep linked data - beware of the reasoner’s complexity 6
    17. 17. SEMANTIC WEB FOR AAL The appropriate reasoner Jena Pellet RacerPro EulerOWL-DL entailment incomplete ✓ ✓ ✓ Rule format own SWRL own, powerful N3++ Retractability ✓ ~ ✓ ✓ Ease of use average (manual) easy complex easy 100 783ms 442ms ~ 503ms 4msSpeed 1,000 29,330ms 28,836ms ~ 44,166ms 40ms 10,000 out of memory 436ms Scalability ✕ ~ ✕ ✓ Size (download) 22.3Mb 24.3Mb 60.3Mb 12.9Mb Licensing free, open-source free, open-source $, closed-source free, open-source 7
    18. 18. SEMANTIC WEB FOR AAL The appropriate reasoner Jena Pellet RacerPro EulerOWL-DL entailment incomplete ✓ ✓ ✓ Rule format own SWRL own, powerful N3++ Retractability ✓ ~ ✓ ✓ Ease of use average (manual) easy complex easy 100 783ms 442ms ~ 503ms 4msSpeed 1,000 29,330ms 28,836ms ~ 44,166ms 40ms 10,000 out of memory 436ms Scalability ✕ ~ ✕ ✓ Size (download) 22.3Mb 24.3Mb 60.3Mb 12.9Mb Licensing free, open-source free, open-source $, closed-source free, open-source 7
    19. 19. SEMANTIC WEB FOR AAL The appropriate reasoner Jena Pellet RacerPro EulerOWL-DL entailment incomplete ✓ ✓ ✓ Rule format own SWRL own, powerful N3++ Retractability ✓ ~ ✓ ✓ Ease of use average (manual) easy complex easy 100 783ms 442ms ~ 503ms 4msSpeed 1,000 29,330ms 28,836ms ~ 44,166ms 40ms 10,000 out of memory 436ms Scalability ✕ ~ ✕ ✓ ☻ Size (download) 22.3Mb 24.3Mb 60.3Mb 12.9Mb Licensing free, open-source free, open-source $, closed-source free, open-source 7
    20. 20. UBISMART SERVICE PLATFORM Architecture‣ Semantic representation of entities in environment 8
    21. 21. UBISMART SERVICE PLATFORM Architecture‣ Semantic representation of entities in environment Context Producer Sensor Knowledge Base [KB] Service Module based on Euler Delivery UI Parser User Interface Plasticity Context Module Acquisition Stream Module Interaction Handler Context Synthetiser Context Understanding Context ss Module Awarene Service Selection Module Service Service Service Service ment Service Manage Context Consumer 8
    22. 22. UBISMART SERVICE PLATFORM Architecture‣ Semantic representation of entities in environment Context Producer Sensor Knowledge Base [KB] Service Module based on Euler Delivery UI Parser User Interface Plasticity Context Module Acquisition Stream Module Interaction Handler Context Synthetiser Context Understanding Context ss Module Awarene Service Selection Module Service Service Service Service ment Service Manage Context Consumer 8
    23. 23. UBISMART SERVICE PLATFORM Architecture‣ Semantic representation of entities in environment Context Producer Sensor Knowledge Base [KB] Service Module based on Euler Delivery UI Parser User Interface Plasticity Context Module Acquisition Stream Module Interaction Handler Context Synthetiser Context Understanding Context ss Module Awarene Service Selection Module Service Service Service Service ment Service Manage Context Consumer 8
    24. 24. UBISMART SERVICE PLATFORM Architecture‣ Semantic representation of entities in environment Context Producer Sensor Knowledge Base [KB] Service Module based on Euler Delivery UI Parser User Interface Plasticity Context Module Acquisition Stream Module Interaction Handler Context Synthetiser Context Understanding Context ss Module Awarene Service Selection Module Service Service Service Service ment Service Manage Context Consumer 8
    25. 25. UBISMART SERVICE PLATFORMSemantic web: plug’n’play & reasoning 9
    26. 26. UBISMART SERVICE PLATFORM Semantic web: plug’n’play & reasoning Sensors Devices ZigBee Wi-Fi/3G/BTHomeControlService Euler (API) DeviceManager ServiceControl ReminderService WSMS Apache Felix container 9
    27. 27. UBISMART SERVICE PLATFORM Semantic web: plug’n’play & reasoningbundle auto-generation Sensors Devices ZigBee Wi-Fi/3G/BT HomeControlService Euler (API) DeviceManager ServiceControl ReminderService WSMS ors ns Se Apache Felix container 9
    28. 28. UBISMART SERVICE PLATFORM Semantic web: plug’n’play & reasoningbundle auto-generation Sensors Devices ZigBee DPWS Wi-Fi/3G/BT EnvironmentDiscovery HomeControlService Euler (API) DeviceManager ServiceControl ReminderService WSMS ors ns Se Apache Felix container 9
    29. 29. UBISMART SERVICE PLATFORM Semantic web: plug’n’play & reasoningbundle auto-generation Sensors Devices ZigBee DPWS Wi-Fi/3G/BT EnvironmentDiscovery HomeControlService Euler (API) DeviceManager ServiceControl ReminderService WSMS ors es ns vic Se De Apache Felix container 9
    30. 30. UBISMART SERVICE PLATFORM Semantic web: plug’n’play & reasoningbundle auto-generation Sensors Devices ZigBee DPWS Wi-Fi/3G/BT EnvironmentDiscovery HomeControlService Euler (API) DeviceManager ServiceControl ReminderService WSMS rules.n3 & query.n3 ors es ns vic environment.n3 Se De skeleton.n3 input.n3 Apache Felix container 9
    31. 31. UBISMART SERVICE PLATFORM Semantic web: plug’n’play & reasoning bundle auto-generation1. profiles of users, devices, sensors2. context information, devices status3. selected service and device4. start/stop service on a device5. services status Sensors Devices6. service instantiation on device ZigBee DPWS Wi-Fi/3G/BT EnvironmentDiscovery HomeControlService Euler (API) DeviceManager ServiceControl ReminderService WSMS rules.n3 & query.n3 ors es ns vic environment.n3 Se De 3 skeleton.n3 1 input.n3 5 2 6 4 Apache Felix container 9
    32. 32. UBISMART SERVICE PLATFORM Semantic inference[KB skeleton] toPeople/aboutPeople usedByPeople Service People name hasModel generateService model name repeat snoozeTime hasContext id onDevice Context hasModel timeSent Device name stage model name hasAckService SuperUser User hasSolvingContext busy stageForAlert Reminder Notification inLocation hasSuperUser Activity ackHandled Deviance escalateTo acknowledgement Location solved Legend Class data property object property subClassOf 10
    33. 33. UBISMART SERVICE PLATFORM Semantic inference[KB skeleton] toPeople/aboutPeople usedByPeople Service People name hasModel generateService model name repeat snoozeTime hasContext id onDevice Context hasModel timeSent Device name stage model name hasAckService SuperUser User hasSolvingContext busy stageForAlert Reminder Notification inLocation hasSuperUser Activity ackHandled Deviance escalateTo acknowledgement Location solved Legend Class data property service s, people p, location l, device d, activity a object property (s toP eople p) ^ (p hasContext l) ^ (d inLocation l) ) (s onDevice d) subClassOf (p hasContext a) ^ (a handsOn true) ^ (d handheld true) ) (d f itted f alse) 10
    34. 34. PERSPECTIVE WORKSmart space composer 11
    35. 35. PERSPECTIVE WORK Smart space composer‣ Tackle heterogeneity of deployment environments - configuration tool - describe environment - attach semantics to off-the-shelve hardware 11
    36. 36. PERSPECTIVE WORK Smart space composer‣ Tackle heterogeneity of deployment environments - configuration tool - describe environment - attach semantics to off-the-shelve hardware‣ Push forward the level of reasoning - bind sensors, context, services through parameters - parameters matching rules - difficulty due to contextual data characteristics 11
    37. 37. PERSPECTIVE WORK ThemesContext Understanding + context approximation y Service Selection int Se ellin + service composition Mo rta de xt g rvi Mo nte ce d llin ce Un Co g Device SSC Modelling User Interface Plasticity multi-modality & polymorphism Smart Space Composer 12
    38. 38. QUESTIONS...Thibaut Tiberghien Ph.D. student (2nd year) thibaut.tiberghien@ipal.cnrs.fr Image & Pervasive Access Lab International joint research unit - UMI CNRS 2955 www.ipal.cnrs.fr

    ×