Extending Mobile Devices with Spatially Arranged Gateways to Pervasive Services.


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
  • ~ 20 slides for 20 minutes (+ 5 min for questions).
  • Extending Mobile Devices with Spatially Arranged Gateways to Pervasive Services.

    1. 1. RelateGateways Extending Mobile Devices with Spatially Arranged Gateways to Pervasive Services. Dominique Guinard
    2. 2. Agenda <ul><li>Introduction. </li></ul><ul><li>End-to-End Service Discovery Model. </li></ul><ul><li>Spatial Discovery. </li></ul><ul><li>Network and Service Discovery. </li></ul><ul><li>Interoperability. </li></ul><ul><li>Conclusion and Questions. </li></ul>
    3. 3. Introduction <ul><li>Mobile users can benefit from access to pervasive services. </li></ul><ul><li>Network discovery technologies facilitate spontaneous connections. </li></ul><ul><li>However, these approaches are not user centric: </li></ul><ul><ul><li>Difficult for users to identify services; </li></ul></ul><ul><ul><li>Lack of simple and natural interaction techniques: </li></ul></ul><ul><ul><li>Lack of spontaneity in interaction… </li></ul></ul>Introduction
    4. 4. Aim <ul><li>Using the mobile device to: </li></ul><ul><ul><li>Identify services available in the user’s immediate environment. </li></ul></ul><ul><ul><li>Consume the services in a natural and seamless manner. </li></ul></ul><ul><li>Need to: </li></ul><ul><ul><li>Include users in the discovery process. </li></ul></ul><ul><ul><li>Address identification, discovery and invocation. </li></ul></ul>Introduction
    5. 5. End-to-End Service Discovery Model E2E Model
    6. 6. Layer 1: Spatial Discovery
    7. 7. Gateways <ul><li>Widgets as access points to the services: </li></ul><ul><ul><li>Gateways. </li></ul></ul><ul><li>Visual discovery of services: </li></ul><ul><ul><li>Mapping the user’s view of his environment on the mobile desktop. </li></ul></ul>Spatial Discovery
    8. 8. Spatial Information <ul><li>Mobile user interface (UI) as a “ compass ”: </li></ul><ul><ul><li>Helps users to identify services available in the immediate environment. </li></ul></ul>Spatial Discovery
    9. 9. Implementation <ul><li>Small Java Swing windows representing the service providers. </li></ul><ul><li>At the screen periphery. </li></ul><ul><li>Two interaction modes: </li></ul><ul><ul><li>Drag-and-Drop. </li></ul></ul><ul><ul><li>Click. </li></ul></ul>Spatial Discovery
    10. 10. Spatial Context <ul><li>Spatial context currently delivered to the mobile client by a Wizard of Oz interface. </li></ul><ul><li>Relate: </li></ul><ul><ul><li>EU-founded project. </li></ul></ul><ul><ul><li>Ad-hoc sensor network. </li></ul></ul><ul><ul><li>Providing relative positioning. </li></ul></ul><ul><li>Working on adapting Relate to deliver real-time positioning data to the compass UI. </li></ul>Spatial Discovery
    11. 11. Layer 2: Network & Service Discovery
    12. 12. Extending Relate Network Discovery
    13. 13. Layer 3: Invocation and Interoperability Interoperability
    14. 14. Service Architecture <ul><li>A service is composed of: </li></ul><ul><ul><li>A ServiceProvider, enclosing the service logic. </li></ul></ul><ul><ul><li>A ServiceRequester containing enough information to invoke the service. </li></ul></ul><ul><li>2 types of services: </li></ul><ul><ul><li>Push service (can be invoked using a Universal Requester). </li></ul></ul><ul><ul><li>Pull-and-push service. </li></ul></ul>Interoperability
    15. 15. Runtime Mobile Code <ul><li>The semantics of Pull-and-Push Services is unknown to the mobile client before discovery. </li></ul><ul><li>Packets of Mobile Code containing ServiceRequesters are downloaded and dynamically loaded on the mobile device. </li></ul>Interoperability
    16. 16. Settings <ul><li>Test run in Lancaster, formative User Study in Munich. </li></ul><ul><li>Total of 20 users. </li></ul><ul><li>3 services in a large office. </li></ul><ul><li>2 devices to interact with the services: </li></ul><ul><ul><li>OQO Handheld. </li></ul></ul><ul><ul><li>Paceblade TabletPC. </li></ul></ul>Evaluation
    17. 17. Evaluation Results <ul><li>Most cited benefits: </li></ul><ul><ul><li>No installation, no configuration: saves time. </li></ul></ul><ul><ul><li>Ease of interaction with the services: drag and drop. </li></ul></ul><ul><ul><li>Dynamic spatial arrangement of the gateways: making the UI more natural, especially useful in unknown places. </li></ul></ul><ul><li>Suggested a number of UI improvements: </li></ul><ul><ul><li>Single interaction zone. </li></ul></ul><ul><ul><li>Fish-eye. </li></ul></ul><ul><li>Suggested a number of services to implement. </li></ul>Evaluation
    18. 18. Summary and Critics <ul><li>The compass UI (Spatial Discovery Layer) helps users to: </li></ul><ul><ul><li>Identify co-located services. </li></ul></ul><ul><ul><li>Interact with pervasive services in a simple and uniform way. </li></ul></ul><ul><li>The Service Architecture enables: </li></ul><ul><ul><li>The dynamic discovery of previously unknown services. </li></ul></ul><ul><ul><li>The rapid prototyping of pervasive services. </li></ul></ul>Conclusion
    19. 19. Open Questions <ul><li>Scalability of the application: </li></ul><ul><ul><li>In terms of user interface. </li></ul></ul><ul><ul><li>In terms of Service Architecture. </li></ul></ul><ul><li>User study is formative: </li></ul><ul><ul><li>Need for a comparative study as well. </li></ul></ul><ul><ul><li>Need to evaluate the framework and its use for the prototyping of mobile spatial applications. </li></ul></ul><ul><li>Security concerns: </li></ul><ul><ul><li>Spontaneity is nice but in leaves a number of doors open for attackers. </li></ul></ul><ul><ul><li>Suggestions ? </li></ul></ul>Conclusion
    20. 20. Questions ? <ul><li>Contributors: Sara Streng, Hans Gellersen, Matthew Oppenheim, Carl Fischer. </li></ul><ul><li>Project’s homepage: http://ubicomp.lancs.ac.uk/relategateways </li></ul><ul><li>Contact: dguinard@guinard.org </li></ul>Conclusion