Middleware & Applications for Mobile Collaboration Prof. Markus Endler Laboratory for Advanced Collaboration (LAC) P

1. Middleware & Applications for Mobile Collaboration Prof. Markus Endler Laboratory for Advanced Collaboration (LAC) PUC-Rio www.lac.inf.puc-rio.br

2. State of the Art • Traditional groupware tools are not suited for wireless networks. • There exist some (few) collaboration tools for wireless networks but they: • don’t handle well intermittent connectivity and migration between networks • are dedicated tools, restricted to a single or few forms of interaction (usually messaging) • don’t consider the fact that the mobile user’s interaction needs depend on her current context.

3. Our Vision Stationary collaboration  Mobile collaboration The fact that users are mobile (change their location) opens a range of new and yet unexplored forms of collaboration.

4. Two Simple Examples Geo-messaging: • Synchronous: discover and establish connection with users at a certain place (e.g. conference room) • Asynchronous: attach a note to a place (e.g. at a bus stop, in vicinity of a machine) Task Force Coordination: • Knowing location and viewpoint of each group member of task force, a manager can remotely coordinate the actions (e.g. military, rescue action, firemen)

5. Context-awareness Context-awareness is a key feature of current and future collaboration tools for mobile users. Context information is needed for: • transparent adaptation, for reacting to changes in the devices’ execution environment (e.g. disconnections, drop in QoS, low energy, etc.) • Enabling an extended notion of collaboration-awareness (e.g. user is driving) • Allowing for new forms of interaction (e.g. co-location, geo-messaging)

6. Concrete Research Goals • Build a middleware infra-structure, with services for collecting, enabling application-level access and inference of context • Using this middleware, develop new collaboration tools & applications that are context-aware and adaptive

7. MoCA Appl. Server MObile Collaboration Architecture Appl. Proxy Client M subscribe notify Context info MOCA Services

8. Main Components of MoCA Core Services: • Monitor • Configuration Service • Context Information Service • Discovery Service • Indoor Location Inference Additional Services: • User Profile Matching • Proximity Service • ...

9. The Monitor • A daemon executing on the mobile device; • Periodically collects & sends to the Context Information Service (CIS) state information about the mobile devices, e.g.: • Strength of signal received from all Access Points (through scan); • CPU utilization, available memory and energy; • MAC Address, IP and currently used Access Point; • Quality of current connection; • In addition to the periodic sending, the Monitor also reports to the CIS any change of the current IP address or Access Point of the device (i.e. a migration)

10. Example of a MOCA service ALI: Approximate Location Inference (Indoor Positioning) • compares the RF signal strength obtained from several 802.11 Access Points • on a map, several reference points are marked (logical positions) • for each point, the signal pattern is measured (several directions and conditions), and this data is recorded in a database • Approximate position of the device is inferred through similarity analysis of the signal patterns (using a statistical method) • Main advantage: requires only 802.11 network

11. ALI: Example 0.5 0.85 XY 0.45 0.8 0.4 0.4 0.9 door1 door2 0.5 0.5 0.3 0.6 0.6 0.3 room1 0.9 room2 0.65 Access Point Reference Point 0.4 RF Signal Intensity Proxy is notified of “DeviceXY @door2”

12. Proxy Framework MOCA provides a white-box OO Framework for developing & customizing the Proxy to specific needs of the application. • Frozen-Spots • Handover Management; • Service Discovery; • Protocol Translation. • Hot-Spots • Context Management & Inference • Adaptation; • User Profile Management & Matching; • Stores user profiles and searches for other users with similar interests; • Caching & Session State Management: • Authentication; • Message Filtering;

13. Case Study First Case Study: A Wireless Chat (W-Chat) which disseminates the (wireless) connectivity status of the participants in a chat room;

14. Current Status • Monitor for WinXP, Linux & WinCE (iPAQs) which is independent of 802.11 chipset • Client and Server APIs for synchronous, synchronous and event-based communication • All core services (DS, CS, CIS) • Prototype Indoor Positioning Service • Proxy Framework • Other Applications

15. Research Labs Computer Science Department Almost all of the 26 faculty also do applied research in one of the following Labs of the Software Technology Institute (ITS): • LES (Software Engineering) – lucena@inf.puc-rio.br • TecGraf (Computer Graphics) – mgattass@inf.puc-rio.br • LAC (Mobility, Collaboration) – endler@inf.puc-rio.br • TecBD (Databases) – rubens@inf.puc-rio.br • Telemídia (Networks and Hypermidia) – lfgs@inf.puc-rio.br • LEARN (Neural Networks and Machine Learning) – milidiu@inf.puc-rio.br • SERG (HCI) – clarisse@inf.puc-rio.br • ICAD (Intelligent CAD) – bruno@inf.puc-rio.br • TecMF (Formal Methods) – hermann@inf.puc-rio.br • LabPar (Parallel Computing) – noemi@inf.puc-rio.br • TecWeb (Web Engineering) – dschwabe@inf.puc-rio.br

16. Q/A Contact: endler@inf.puc-rio.br www.inf.puc-rio.br/~endler