Easing the Mobility of Disabled People in Supermarket Using a Distributed Solution


Published on

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Hello, my name is … . I work as a researcher at the Mobility Research Lab, the research group behind the INTERNET unit of DeustoTech – Deusto Institute of Technology at the University of Deusto. Some of our main research areas are: Smart Environments Ambient Assisted Living (AAL) Contextual mobile solutions Future Internet: Internet of Services and Internet of Things So, I’m here to present you our research work, which title is… Let’s start with it.
  • Index presentation: First of all, our motivation for doing this... Then I’ll present you the problem we faced with... Proposed solution and challenges we encountered Then the final system architecture Conclusions and further work Acknowledgments And finally if you have any question, I’ll try to ask all of them
  • Well, as I’ve said before one of our research areas is the AAL. In these years we’ve learned that task which can be common for us can be tedious and very difficult for others
  • So, we focused our work on a very common and important task: shopping in a supermarket. This is a simple activity for us, but have you ever think about a man on a wheelchair? Or someone with temporary impairments? What about elderly? Those will be our target users, although there is no need to have a mobility problem to take advantage from our solution.
  • So, once the main problem is clear, how would we help these users to get a better UX?
  • Well, here is our proposal. We present a distributed system which is able to get the users’ shopping list from their devices and then mark their desired products on another device’s screen This sounds good but we need some infrastructure support, what do we need for that? - Android devices, two kind of devices. The user´s one with his shopping list and another one from the supermarket to display the products location. - We will need wireless communication, and some kind of coordination. Remember this word ‘cause it’s very important here.
  • When we formulated that definition we saw two main challenges: Distributed architectures are difficult to maintain and their functionality is particularly hard to guarantee Where has to be the collected data stored ? How should the system manage the information flow ? How should the system react to node crashes ? How should the system manage a node addition or removing ? Getting any info from a user device is a controversial practise User authentication and authorization
  • Ok, do you remember the previous word... Coordination?. For us, coordination + distributed platform + security means Triple Spaces. And what is TS? It is a coordination paradigm where nodes can share information in a decoupled way. In other words, it is a distributed shared semantic space between nodes which join it. This information is stored in triples, which are stored in graphs. Otsopack is our solution for TS. It’s open source, and you can download and test it in Google Code site.
  • Ver Introduction de: http://www.cepis.org/upgrade/media/GomezGoiri_1_20112.pdf TS offers 4 autonomies: Reference: nodes do not need to know each other Time: because of its asynchronous nature Location: because information providers and consumers are independent from where the data is stored Data Schema: it follows the RDF specification making it independent of nodes internal data schema
  • This diagram shows how the devices (nodes) share their information connecting to the spaces Remember this slide in order to understand the next one
  • Well, here there is how TS fits in our system. On the left side you can see the supermarket servers, which have all the information about the products and their locations. On the right side there are the customers with their personal devices. Both are able to perform the same operation over the space: write . There are 4 main operations in TS: - Query : which returns a new graph with the triples which match the given template - Write : which adds new knowledge to a space writing the given triples in a new RDF graph Read and Take : They return a whole RDF graph which can be selected by its identifying URI or by a template. With the Read, if one triple fits the template, the whole graph is returned. The Take operation just returns a graph if it contains at least a triple which matches the template. The Take also subtracts the returned graph from the space. So, users (from their devices) and servers perform writes operations, sharing their products and shopping lists. On the other hand, a customer with a device from a supermarket performs a read operation, obtaining customized triples with the location of his desired products.
  • So, as we have seen in the previous slide, there are two device applications. The first one, in the user’s device, which just lists his desired products. The second one, in the supermarket device, which will show a map with the products marked over it.
  • Here it is the ontology which represents the data. It represents information about the supermarket and the relations between the user shopping cart and the available products.
  • This work has been supported by the ACROSS project, where the scenarios we participate in deals with social robotics services in social scenarios
  • We’ve obtained a decoupled infrastructure which keeps user’s data safe Robot responsible of guiding customers Improve otsopack Alimerka and exhaustive evaluation of the scenario
  • Easing the Mobility of Disabled People in Supermarket Using a Distributed Solution

    1. 1. Aitor G ó mez-Goiri 1 , Eduardo Castillejo 1 , Pablo Ordu ñ a 1 , Xabier Laiseca 1 , Diego L ó pez-de-Ipi ñ a 1 and Sergio F í nez 2 1 DeustoTech - Deusto Institute of Technology, University of Deusto http://www.morelab.deusto.es 2 Treelogic http://www.treelogic.com
    2. 2. Index <ul><li>Motivation </li></ul><ul><li>Main Problem </li></ul><ul><li>Proposed Solution </li></ul><ul><li>Challenges </li></ul><ul><li>System Architecture </li></ul><ul><li>Acknowledgments </li></ul><ul><li>Conclusions and Future Work </li></ul><ul><li>Questions </li></ul>
    3. 3. Motivation (1 of 2) <ul><li>Unfortunately, impaired people have to deal with difficulties every day </li></ul><ul><li>What for us are daily and common tasks become huge challenges for handicapped people </li></ul><ul><li>Outside home people’s impairments become bigger </li></ul>
    4. 4. Motivation (2 of 2)
    5. 5. <ul><li>So, the problem is... </li></ul><ul><ul><li>Common tasks, such as shopping in a supermarket , can be tedious for impaired people </li></ul></ul><ul><li>We have focused our work on this activity </li></ul><ul><li>How can we help mobility impaired people to get a better user experience? </li></ul>Main Problem
    6. 6. Proposed Solution <ul><li>What do we propose? </li></ul><ul><ul><ul><li>A distributed system able to get the users’ shopping list from their devices and show the desired products over a supermarket map </li></ul></ul></ul><ul><li>What do we need? </li></ul><ul><ul><ul><li>Android devices </li></ul></ul></ul><ul><ul><ul><li>Wireless communication </li></ul></ul></ul><ul><ul><ul><li>... And some kind of coordination </li></ul></ul></ul>
    7. 7. Challenges (1 of 3) <ul><li>Distributed architectures </li></ul><ul><li>Three main challenges: </li></ul>Coordination Authentication and authorization
    8. 8. Challenges (2 of 3) <ul><li>And... Coordination actually means Triple Spaces (TS) - http://code.google.com/p/otsopack </li></ul><ul><ul><li>TS computing is a coordination paradigm based on tuplespace-based computing </li></ul></ul><ul><ul><li>It performs a tuplespace-based communication using RDF triples, in which the information unit has three dimensions: “subject – predicate - object” , to express this semantic data </li></ul></ul>
    9. 9. Challenges (3 of 4) <ul><li>Triple Spaces offers 4 autonomies </li></ul>Reference Time Data Schema Location
    10. 10. Challenges (3 of 3) <ul><li>Within TS several nodes connect to so named “spaces” to share information </li></ul>
    11. 11. System Architecture (1 of 3)
    12. 12. System Architecture (2 of 3) <ul><li>Developed system components: </li></ul><ul><ul><li>Shopping Cart mobile </li></ul></ul><ul><ul><li>application </li></ul></ul><ul><ul><li>Product Loader tablet </li></ul></ul><ul><ul><li>application </li></ul></ul>
    13. 13. System Architecture (3 of 3) <ul><ul><li>Supermarket servers </li></ul></ul><ul><ul><li>Triple Spaces </li></ul></ul><ul><ul><li>Ontology </li></ul></ul>
    14. 14. Acknowledgments <ul><li>This work has been supported by project grant TSI-020301-2009-27 (ACROSS), funded by the Spanish Ministerio de Industria, Turismo y Comercio </li></ul><ul><ul><li>http://www.acrosspse.com </li></ul></ul>
    15. 15. Conclusions and Future Work <ul><li>We’ve obtained a decoupled infrastructure which keeps all user data in a safe way </li></ul><ul><li>In the future, a robot will be responsible of guiding users among the supermarket by choosing the most efficient path </li></ul><ul><li>Keep working improving otsopack </li></ul><ul><li>An exhaustive evaluation of the final scenario is planned to be carried out with Spanish ALIMERKA supermarkets </li></ul>
    16. 16. Questions