ACS Ontology for Ambient Home Care
•
0 likes•354 views
The document discusses the development of an ontology for ambient care systems (ACS-Ont). It provides an introduction to ambient care systems and their architecture, which involves collecting data from various sensors on users and in their homes. It outlines requirements for an ACS data model such as handling uncertainty and quality of context. An overview of the general ACS-Ont ontology is given, which takes a modular approach and reuses existing ontologies. While still under development, ACS-Ont provides a semantic framework and integration of ambient assisted living domains. Future work involves further developing subontologies and addressing issues like uncertainty management.
Recommended
Recommended
More Related Content
More from Josué Freelance
More from Josué Freelance (20)
Recently uploaded
Recently uploaded (20)
ACS Ontology for Ambient Home Care
- 1. Grupo de Procesado de Datos y Simulación ETSI de Telecomunicación Universidad Politécnica de Madrid Data modeling for Ambient Home Care Systems DCAI 2010 Ana M. Bernardos, M. del Socorro Bernardos, Josué Iglesias, José R. Casar {abernardos, josue, jramon}@grpss.ssr.upm.es, sbernardos@fi.upm.es
- 2. contents introduction to Ambient Care Systems ACS architecture overview data model requirements general ACS-Ont overview discussions and future work Ambient Care System Ontology – DCAI2010 abernardos@grpss.ssr.upm.es
- 3. contents introduction to Ambient Care Systems ACS architecture overview data model requirements general ACS-Ont overview discussions and future work Ambient Care System Ontology – DCAI2010 abernardos@grpss.ssr.upm.es
- 4. ACS intoduction 1950 2000 2030 Ambient Care System Ontology – DCAI2010 abernardos@grpss.ssr.upm.es
- 5. ACS intoduction 1950 2000 2030 ACS (Ambient Care Systems) Ambient Care System Ontology – DCAI2010 abernardos@grpss.ssr.upm.es
- 6. ACS intoduction 1950 2000 2030 ACS (Ambient Care Systems) elder care network improvement Ambient Care System Ontology – DCAI2010 abernardos@grpss.ssr.upm.es
- 7. ACS intoduction 1950 2000 2030 ACS (Ambient Care Systems) elder care network emergency situations improvement detection and handling Ambient Care System Ontology – DCAI2010 abernardos@grpss.ssr.upm.es
- 8. ACS intoduction 1950 2000 2030 ACS (Ambient Care Systems) elder care network emergency situations activities of daily living improvement detection and handling support Ambient Care System Ontology – DCAI2010 abernardos@grpss.ssr.upm.es
- 9. ACS intoduction Ambient Care System Ontology – DCAI2010 abernardos@grpss.ssr.upm.es
- 10. ACS intoduction heterogeneous context sources (mobile phones, biometric sensors, infrastructure devices, etc.) + static data aggregation (profile information, personal calendars, electronic health records, etc.) + new user’s context information inference Ambient Care System Ontology – DCAI2010 abernardos@grpss.ssr.upm.es
- 11. ACS intoduction heterogeneous context sources (mobile phones, biometric sensors, infrastructure devices, etc.) + static data aggregation (profile information, personal calendars, electronic health records, etc.) + new user’s context information inference context image Ambient Care System Ontology – DCAI2010 abernardos@grpss.ssr.upm.es
- 12. ACS intoduction heterogeneous context sources (mobile phones, biometric sensors, infrastructure devices, etc.) + static data aggregation (profile information, personal calendars, electronic health records, etc.) + new user’s context information inference content management decision making events/actions triggering context image Ambient Care System Ontology – DCAI2010 abernardos@grpss.ssr.upm.es
- 13. ACS intoduction heterogeneous context sources (mobile phones, biometric sensors, infrastructure devices, etc.) + static data aggregation (profile information, personal calendars, electronic health records, etc.) + new user’s context information inference ... provider + external context ... ... consumer content management decision making events/actions triggering context image Ambient Care System Ontology – DCAI2010 abernardos@grpss.ssr.upm.es
- 14. ACS intoduction heterogeneous context sources (mobile phones, biometric sensors, infrastructure devices, etc.) + static data aggregation (profile information, personal calendars, electronic health records, etc.) + new user’s context information inference ... provider + external context ... ... consumer content management • great diversity of data decision making events/actions triggering context sources static data new inferred data 3rd parties (...) • highly sharable context image Ambient Care System Ontology – DCAI2010 abernardos@grpss.ssr.upm.es
- 15. contents introduction to Ambient Care Systems ACS architecture overview data model requirements general ACS-Ont overview discussions and future work Ambient Care System Ontology – DCAI2010 abernardos@grpss.ssr.upm.es
- 16. ACS architecture different assistive services different scenarios user’s real-time needs Ambient Care System Ontology – DCAI2010 abernardos@grpss.ssr.upm.es
- 17. ACS architecture different assistive services personal network different scenarios user’s wearable sensors (mobile device embedded) user’s real-time needs embedded GPS sensor WiFi, Bluetooth, ZigBee, etc. embedded RFID reader health monitoring sensors (...) Ambient Care System Ontology – DCAI2010 abernardos@grpss.ssr.upm.es
- 18. ACS architecture different assistive services personal network different scenarios user’s wearable sensors (mobile device embedded) user’s real-time needs embedded GPS sensor WiFi, Bluetooth, ZigBee, etc. embedded RFID reader health monitoring sensors (...) home network home infrastructure sensors / actuators WiFi, Bluetooth, ZigBee, etc. beacons RFID-tagged objects home gateway (...) Ambient Care System Ontology – DCAI2010 abernardos@grpss.ssr.upm.es
- 19. ACS architecture different assistive services personal network different scenarios user’s wearable sensors (mobile device embedded) user’s real-time needs embedded GPS sensor WiFi, Bluetooth, ZigBee, etc. embedded RFID reader health monitoring sensors (...) home network home infrastructure sensors / actuators WiFi, Bluetooth, ZigBee, etc. beacons RFID-tagged objects home gateway (...) core care network personal/home network – 3 parties bridge rd security & authentication external context data providers external care networks (...) Ambient Care System Ontology – DCAI2010 abernardos@grpss.ssr.upm.es
- 20. ACS architecture different assistive services personal network different scenarios user’s wearable sensors (mobile device embedded) user’s real-time needs embedded GPS sensor WiFi, Bluetooth, ZigBee, etc. embedded RFID reader health monitoring sensors (...) home network home infrastructure sensors / actuators WiFi, Bluetooth, ZigBee, etc. beacons RFID-tagged objects home gateway (...) core care network personal/home network – 3 parties bridge rd security & authentication external context data providers external care networks (...) Ambient Care System Ontology – DCAI2010 abernardos@grpss.ssr.upm.es
- 21. ACS architecture personal network user’s wearable sensors (mobile device embedded) context-aware emergency embedded GPS sensor activity logging notifications/reminders detection WiFi, Bluetooth, ZigBee, etc. embedded RFID reader health monitoring sensors (...) home network home infrastructure sensors / actuators WiFi, Bluetooth, ZigBee, etc. beacons RFID-tagged objects home gateway (...) core care network personal/home network – 3 parties bridge rd security & authentication external context data providers external care networks (...) Ambient Care System Ontology – DCAI2010 abernardos@grpss.ssr.upm.es
- 22. contents introduction to Ambient Care Systems ACS architecture overview data model requirements general ACS-Ont overview discussions and future work Ambient Care System Ontology – DCAI2010 abernardos@grpss.ssr.upm.es
- 23. model requirements Ambient Care System Ontology – DCAI2010 abernardos@grpss.ssr.upm.es
- 24. model requirements model requirements • consistency checking • information acquisition and data fusion (at different levels) • uncertainty and QoC handling (probabilistic approach) • scalable (general service support) • security support Ambient Care System Ontology – DCAI2010 abernardos@grpss.ssr.upm.es
- 25. model requirements model requirements • consistency checking • information acquisition and data fusion (at different levels) • uncertainty and QoC handling (probabilistic approach) • scalable (general service support) • security support • distribution • validation ontologies • formalization • ambiguity control • completeness • (...) Ambient Care System Ontology – DCAI2010 abernardos@grpss.ssr.upm.es
- 26. model requirements model requirements • consistency checking • information acquisition and data fusion (at different levels) • uncertainty and QoC handling (probabilistic approach) • scalable (general service support) • security support ACS-Ont • distribution • validation ontologies • formalization • ambiguity control • completeness • (...) Ambient Care System Ontology – DCAI2010 abernardos@grpss.ssr.upm.es
- 27. contents introduction to Ambient Care Systems ACS architecture overview data model requirements general ACS-Ont overview discussions and future work Ambient Care System Ontology – DCAI2010 abernardos@grpss.ssr.upm.es
- 28. general ACS-Ont ontology Ambient Care System Ontology – DCAI2010 abernardos@grpss.ssr.upm.es
- 29. general ACS-Ont ontology • user state context global image Ambient Care System Ontology – DCAI2010 abernardos@grpss.ssr.upm.es
- 30. general ACS-Ont ontology • user state context global image • device sensor Ambient Care System Ontology – DCAI2010 abernardos@grpss.ssr.upm.es
- 31. general ACS-Ont ontology • modular design general ontology subontologies Ambient Care System Ontology – DCAI2010 abernardos@grpss.ssr.upm.es
- 32. general ACS-Ont ontology • modular design general ontology subontologies Ambient Care System Ontology – DCAI2010 abernardos@grpss.ssr.upm.es
- 33. general ACS-Ont ontology • ontologies reuse Ambient Care System Ontology – DCAI2010 abernardos@grpss.ssr.upm.es
- 34. general ACS-Ont ontology • ontologies FOAF reuse Friend-Of-A-Friend RDF Calendar Geo-OWL Delivery OWL-Time Context Ontology Ambient Care System Ontology – DCAI2010 abernardos@grpss.ssr.upm.es
- 35. general ACS-Ont ontology • ontologies FOAF reuse Friend-Of-A-Friend SOUPA ConOn CoDAMoS X.73 RDF Calendar Geo-OWL Delivery OWL-Time Context Ontology Ambient Care System Ontology – DCAI2010 abernardos@grpss.ssr.upm.es
- 36. general ACS-Ont ontology • ontologies FOAF reuse Friend-Of-A-Friend SOUPA OpenEHR ConOn SNOMED CoDAMoS REI Policy X.73 RDF Calendar Geo-OWL Delivery OWL-Time Context Ontology Ambient Care System Ontology – DCAI2010 abernardos@grpss.ssr.upm.es
- 37. contents introduction to Ambient Care Systems ACS architecture overview data model requirements general ACS-Ont overview discussions and future work Ambient Care System Ontology – DCAI2010 abernardos@grpss.ssr.upm.es
- 38. discussion and future work • ACS-Ont is still in a development stage – subontologies identified but not already developed – more external model need to be integrated • ACS-Ont: – step forward in structuring general AAL domains – semantic frame – semantic integration guaranteed (standart language + well-known ontologies) future work we are already working on: ontology enrichment (adding rules, constraints, constants, etc.) specific problems extension integration (i.e. modeling activities of daily living to support behavioral analysis) tests uncertainty and Quality of Context management Ambient Care System Ontology – DCAI2010 abernardos@grpss.ssr.upm.es
- 39. any question? Ambient Care System Ontology – DCAI2010 abernardos@grpss.ssr.upm.es
Editor's Notes
- Hello, welcome everybody. My name’s Josué, I work for the GPDS group in UPM, there in Madrid and I’m going to talk about the data model we have designed in order support Ambient Home Care Systems.
- First of all, I will introduce Ambient Care System Showing later our particular perspective to these kind of systems and extracting some requirements for the data model Then, I will present the characteristics of our initial design (that we have called ACS-Ont) finishing with some discussions and future works.
- The population pyramid in developed countries is suffering an expansion in the number of elderly and mature citizens, having longer life expectancy but more chronic diseases too. This situation is a challenge for nowadays societies that are recently trying to use the technology in order to support social care systems. So Ambient Care Systems (ACS from now on) appears as the technology used in order to promote elder’s independent life, trying to guarantee a high quality of services while reducing costs. ACS may offer services ... ... to enhance elder’s care network (connecting the user with relatives, friends and health assistants) ... to detect and handle emergency situations (for instance, fall detections) and ... to help users in developing their everyday activities (supporting medication intakes reminders, for example)
- Technologically, ACS are based on the acquisition of information coming from heterogeneous context sources this dynamic information is integrated with static data (user’s profile information, personal calendars, ...) finally, having into account all this data, new user’s context information can be further inferred All these information (dynamic, static and inferred) conforms what we call the user’s “context image”. So ACS offer their services ( content management decision making and events triggering ) depending on this user’s “context image”. ACS must also act as a channel to 3rd parties entities, both, as providers or consumers (of services and context). It can be seen that ACS deal with a great diversity of data (...) and that this data needs to be shared between different entities.
- Data model requirements have been extracted from the particular architecture and service offering that I introduce next. We have shaped this ACS architecture taking into account that a wide range of services may be offered in different scenarios (mainly indoor and outdoor ones) and taking also into account final users’ real-time needs. This ACS architecture will be working on: a Personal Network that includes all the devices that a user may wear (is mainly composed by a mobile device with sensors attached,) (but it can also incluse other kind of devices, as health monitors, for instance) a Home Network that mainly includes home infrastructure sensors and actuators. Home Network sensors communicate with Personal Network by means of its ad hoc networking capabilities. It has also a Home Gateway connected to the Core Care Network. and a Core Care Network that will act as a kind of bridge between the personal and home networks and external entities (also supporting security and authentication mechanism) On top of this architecture, the ACS will build its own basic services, such as: context-aware reminders (medication intakes) (medical appointments notification) emergency situation detection or (relying on biomedical and environmental information checking) activity logging (that is, an offline contextual pattern analysis).
- So the main requirements extracting from this particular ACS architecture are: that the model needs to be able to dynamically check consistency when including new concepts it needs to be able to deal with information retrieval and data fusion at different levels of abstraction must support probabilistic inference mechanisms (dealing with uncertainty and QoC) it must be scalable enough (at least in order to support a wide variety of services) and finally, the model must support authentication and security. A well-known trend in context modeling is to use ontologies to model context data, mainly due to their versatility in terms of: (...) So here we proposed to an application-oriented ontology to cover the representation and semantic needs of ACS.
- So the model has this look at the moment. It has been modeled concepts related to the user (with a particular State and a general Context associated that conforms their GloblalImage I talk about before) and their personal device (with some sensors attached) We have followed a modular approach, so this view just represents what we called “general ontology”. Some of these concepts (as Object, Sensor or Event) are going to be further developed in other ontologies we call “subontologies”. We have also try to take advantage of ontology reuse. We have directly reuse some well-known ontologies in our model, directly using the same concepts and relations. Other well-known ontologies (as ...) have been also used, but indirecty, just as reference models. Finally, other ones have been identified to be integrated in future extensions of the model.
- Well, now to finish, it has to be said that ACS ontology is still an open design: as I’ve already said, we need to develop some subontologies and some external models need to be integrated too. But anyway, it is a step forward to structuring general AAL domains (Ambient Assisted Living) being a semantic frame that guarantees semantic integration as it’s going to be developed using standard languages and it reuses well-known ontologies We’re already working on: refining this ACS ontology (adding restrictions to the modeled concepts) extending the ontology to cope specific problems (as modeling ...) adding uncertainty and QoC support Finally we plan to test its viavility integrating this ACS ontology in a real context system.