1 / 17

Context-Triggered Messaging and Information Sharing

Explore new forms of communication and information sharing facilitated by context-triggered messaging. Study the required context reasoning and conduct field tests in a prototype environment.

schumacherk
Télécharger la présentation

Context-Triggered Messaging and Information Sharing

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. Keep Me Informed: P2P Context Triggered Messaging and Information Sharing Martti Mäntylä HIIT/ARU

  2. Time t1, Place X Time t1, Place A Time dimension Place dimension Place B, time t+Δ Place A, time t Time t2>t1, Place X ± Δ Time t2>t1, Place B There is Room for New Forms of Communication Online communication: Voice, SMS, MMS, IM, rich call, streaming Context-triggered communication Location communication

  3. A Little Story - 1 • The school day of Anne, a third grader at elementary school, is usually ending at 3 PM on Tuesdays. After school, she usually goes to afternoon club at the church for a couple of hours before her mom gets home. • Today, however, the last two classes are cancelled, because the teacher turns ill after the third class (at 11 AM). • What to do? Anne cannot wait alone for two hours. • Fortunately, she and the other members of her family carry a LifeMgr device, supporting context-triggered P2P communication!

  4. A Little Story - 2 • Let's assume the cancellation message is posted in school's WWW pages at 11:10. • Anne's LifeMgr (its adaptive IR subsystem) is set up to monitor these pages for information relevant to her (ordinarily, homework assignments etc.). At 11:11, the LifeMgr notes the cancellation notification and retrieves the relevant data from the WWW system. • The retrieved information matches a template stored in Anne's LifeMgr. The template causes the information to be displayed to Anne at 11:45 (when Anne's present class ends) and also sends immediately a message to Anne's parents as to the fact that Anne's school day will end exceptionally at 1 PM.

  5. A Little Story - 3 • The message is passed to the family's shared context server that maintains a representation of the present context of Anne's parents. • Anne's mother is in an important business meeting for the whole afternoon, but Anne's father happens to be free from noon until 2 AM. Therefore, the context server decides to pass the message to Anne's father. • The actual delivery of the message takes is delayed until 11:55, when Anne's father ends his lecture at the university.

  6. A Little Story - 4 • Anne's father receives the message at 11:56. He studies the shared family calendar, and observes that his mother (Anne's granny) is not busy for the afternoon. He decides to pick Anne from the school and bring her to be babysitted by his mother for the afternoon. • He calls her about this at 12:03, and she agrees (she likes Anne a lot). • As a side effect of the call (executed in a context set up by the message from Anne's LifeMgr) the family calendar is automatically updated with relevant information of Anne's whereabouts (at 12:08).

  7. A Little Story - 5 • Anne's mother is just having a quick lunch before her important management board meeting. Her LifeMgr beeps so she peeks into it. • She notes that Anne's schedule has been altered, and clicks at the entry to see why. She sees the original messages (Anne's message at 11.11 and her husband's message at 12:03 (or a summary of it in text form)) and is relieved to see that the crisis has been managed.

  8. A Little Story - 6 • Anne, too is having a lunch when her LifeMgr beeps for an important message at 12:09. She becomes very happy to see that her daddy will bring her to granny's for the afternoon. (She had not been nervous of the situation because she had already seen at 11:57 that her father had been alerted of the schedule change.) • Anne's father picks her up from the school at 1.05 PM. When he prepares to leave to his mother's, his LifeMgr reminds him to buy some lemonade and biscuits from a nearby shop; Anne is likely to want a snack at her granny's.

  9. What Is Going On? • Relevant information for life management is extracted "automatically" from various (heterogeneous) information sources. • In addition to on-line messages, the system facilitates "delayed" messages (delivered at an appropriate time on the basis of the context of the recipient) or "contextually addressed" messages (delivered to one of several candidate recipients as determined by their current context/availability). • Only a few explicit messages are send; mostly messages/information sharing is triggered "automatically" so that a shared awareness of the situation at hand is maintained.

  10. The Project • Main goal: study the context models and context reasoning facilities required to support scenarios such as Anne’s story • Investigate and identify novel forms of (small) group communication and information sharing that are made possible or enhanced by contexts • Study real users and groups to understand context reasoning required to facilitate everyday life communication and information sharing • Perform field tests in a prototype environment

  11. Prototype System • Baseline: Munoz et al., IEEE Computer, Sept. 2003:

  12. Prototype System • Instant messaging: Jabber • IM protocol: Jabber’s XMPP (http://www.jabber.org/protocol/) • Context server: looks like an IM client to XMPP • But investigate if a P2P structure can be created enabling all user agents to perform context reasoning • Information synchronization: PDIS • Ignore (initially) external information retrieval

  13. The Focus • Context reasoning: • How to manage novel forms of messaging on the basis of information of the current context of the sender and the recipient(s) of a message? • How to control novel types of information sharing (synchronization) through context information? • How to use context to decide what information should be shown to users, and when? • How to implement the above through user-definable “policies”, scripts, agent rules, whatever? • Not so much in focus: • How to adapt an interface to current user context?

  14. Further Research Issues • How should context information be conveyed to the users (while causing minimal disturbance)? • What are the privacy and trust issues arising? How can they be handled? • E.g., context triggering should not expose context information that should be kept private

  15. Project Form • Two years, 10 person-years total • Budget 380 k€/a • Company funding 20%, ~19 k€/a if 4 companies join the project • Human resources: • HIIT UERG, DE • Close co-operation with CONTEXT, PDIS, Fuego Core • HUT INIT

  16. Work Packages • First year: • WP1 User Studies • WP2 Experimental System Design and Preliminary Implementation • WP3 Context Reasoning • Second year: • WP4 External Information Retrieval and Adaptation • WP5 Interaction Design • WP6 Final System Implementation • WP7 Field Testing • WP8 Wrap-Up and Final Deliverable Generation

  17. Deliverables • The demonstration system • Released in Open Source? • Novel communication concepts and solutions • Restricted to companies in the project • Examples of context reasoning “rules” • Restricted to companies in the project • Insight, ideas, publications, demonstrations, presentations, … • Open or closed

More Related