1 / 18

Outline

Outline. Introduction Scenario and objectives Methods and materials Results Conceptual model Logical model Physical model Discussion Conclusions. Improvement and expansion of mobile communications permit the design of helpful tools in all the aspects of each user’s life.

olinda
Télécharger la présentation

Outline

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 26-27 October 2006, Nice, France

  2. Outline • Introduction • Scenario and objectives • Methods and materials • Results • Conceptual model • Logical model • Physical model • Discussion • Conclusions 26-27 October 2006, Nice, France

  3. Improvement and expansion of mobile communications permit the design of helpful tools in all the aspects of each user’s life. Mobile devices are highly suitable for most of everyday situations: More process capability More modalities for user interface purposes More resources to be connected to their context of use Small, low cost and users carry them every time Important applications for these devices: Support for the independent living of people with disabilities Access to available AmI based services Adapted remote controllers of smart homes Introduction 26-27 October 2006, Nice, France

  4. Scenario and objectives • Scenario: • A user going into a smart environment would be notified about the availability of services, and given the possibility to interact with all the domotic services (open/close doors, turn on/off TV, turn on/off lights, events notification, etc.) through his mobile device. • Smart home with domotic devices controlled via web interface • Network connection wifi, bluetooth, LAN, …. • User with handheld device • Objectives: • To increase accessibility and usability in smart homes • To design a middleware architecture based on the concept of ambient intelligence • To provide seamless wireless connectivity through automatic procedures 26-27 October 2006, Nice, France

  5. Methods and materials (I) The description of our project has been made in agreement to IEEE standard 1471 and the concept of views, in order to define every aspects of the system, and the concept of viewpoints in order to capture common descriptive frameworks. • The architecture has been defined in three layers model that are the views: • conceptual model • logical model • physical model 26-27 October 2006, Nice, France

  6. Methods and materials (II) Requirements: • Hardware independence: the agent will be able to run on different kinds of devices (notebook, mobile phone, PDA, etc..). • Operating system independence: the agent will be compatible with multiple OS. • Lightweight software: the agents must have a little set of resources active for its computation. • Minimum added software: a minimal set of external libraries will be needed in order to develop the agent. • Seamless connectivity: the agent has not to ask for a direct interaction with the user during its execution. 26-27 October 2006, Nice, France

  7. Results: conceptual model (I) 26-27 October 2006, Nice, France

  8. Results: conceptual model (II) • Mobile device: • This component allows the interaction between user and smart home. We can differentiate three parts in its structure: a service client, a mobility management agent and dedicated agents. • Smart home: • Three main software modules are foreseen: the services that manage the devices of the smart home, the communication management agent and the wireless connection agents. 26-27 October 2006, Nice, France

  9. Results: logical model (I) 26-27 October 2006, Nice, France

  10. Results: logical model (II) The logical model is obtained fixing the network standards, protocols and the connection procedures for the different elements of the conceptual model. • The service client at the mobile device described in the conceptual model, corresponds with an HTTP client, in the logical model. • In the smart home, the Bluetooth agent Network Access Point (NAP) allows that one or more mobile devices can use the services. • In the mobile device, the Bluetooth agent Personal Area Network User (PANU) is the software that will manage the connection with the NAP side of the smart home. 26-27 October 2006, Nice, France

  11. Results: physical model (I) HP Ipaq 5500 Smart Home http client EIB bus/ OSGI /Java Technologies Smart Home web server Java agent connector Linux bridge JNI library for NAP Bluetooth services Java software JNI library for PANU Bluetooth services Bluetooth connection 26-27 October 2006, Nice, France

  12. Results: physical model (II) Hardware: • Mobile Device: HP Ipaq 5500 with the operating system Familiar V0.8. • Smart home: PC with fedora core 3 distribution as Linux bluetooth bridge, Windows XP PC with OSGI platform and EIB based technologies. Software: • Java SDK 1.3 • Java Native Interface • Linux scripts 26-27 October 2006, Nice, France

  13. Discussion (I) • The PDA has been able to connect automatically with the Linux Bridge through a Bluetooth connection, showing on the PDA display the web interface of the smart home without any user interaction. • Many problems have been found on the usability and the scalability of the software. • It has not been achieved total independence from hardware, software and operating systems used for both PDA and smart home. 26-27 October 2006, Nice, France

  14. Discussion (II) • Common problems: • Bluetooth protocol stack is still in development. • No Java distribution has implemented the PAN Bluetooth profile. • There is no standard library that is able to connect Bluetooth devices in a local area network through TCP/IP independently from the operating system used. 26-27 October 2006, Nice, France

  15. Discussion (III) • Different solutions have been investigated based on Windows and Linux operating systems. • Linux based solution • The Bluez module provides the Bluetooth PAN profile. • It is possible to manage Bluez commands with scripts. • There are some bugs in the Bluez implementation of Familiar (additional management when Bluez service crashes). • Windows based solution • Bluetooth protocol stack is not modifiable and cannot be manipulated with scripts. • It needs legacy and commercial solutions. • The only way for interacting with Bluetooth is by using the OS graphic interface. 26-27 October 2006, Nice, France

  16. Conclusions (I) It is proposed a middleware architecture for Ambient Intelligence environments that allows to join natural interaction with the user and automatic selection of communication technologies in an adaptive, non-intrusive and personalized way. 26-27 October 2006, Nice, France

  17. Conclusions (II) • Some problems have been detected in order to develop entirely the proposed scenario: • a little collection of devices fully implement the Bluetooth protocol stack • there are no standard Java libraries in order to implement scalable solutions with Bluetooth in LAN applications • for Windows-based systems, it is not possible to implement scalable solutions based on free and open source software • for Linux-based solutions, there are problems depending on the hardware used, some models of PDA still present several bugs 26-27 October 2006, Nice, France

  18. Thank you for your attention! 26-27 October 2006, Nice, France

More Related