Time & Location Sensitive Messaging Protocol for Automated Delivery

1. Time & Location Sensitive Messaging Protocol for Automated Delivery CSE 237A: Final Project Presentation Presented by Jennifer Chiang & Jeffrey Kuramoto

2. What are Time/Location Sensitive Messages? Message is received only when time or location sensitive conditions are met. Example: Send reminder in the morning: “Mom, Can I get a ride home from school?” / 2:00 pm • Message received at 2:00 pm, in time for Mom to get to school. Example: “Pick up eggs” / Ralph’s • Next time I go to Ralph’s, I get a reminder to buy eggs.

3. Outline Introduction • Location Based Services • Related Implementations • Project Goals Implementation • Challenges and Limitations • Client Server Modeling Results • Example Query • Conclusions • Future Work References

4. Outline Introduction • Location Based Services • Related Implementations • Project Goals Implementation • Challenges and Limitations • Client Server Modeling Results • Example Query • Conclusions • Future Work References

5. Motivation for LBS Relevance • Receive relevant information Reminders • Send information to arrive at designated times Mobility • Information available wherever you are

6. Requirements Requirements of an LBS: • Positioning (e.g. GPS) • Geographic Information Services (GIS) • Information Management Time/Location Sensitive Messaging is a Location Based Service (LBS): must satisfy requirements

7. Outline Introduction • Location Based Services • Related Implementations • Project Goals Implementation • Challenges and Limitations • Client Server Modeling Results • Example Query • Conclusions • Future Work References

8. Current State of the Art • Research on building context-aware systems with support of GPS technology • Cybreminder, Stick-e notes, ComMotion • ActiveCampus, by W. Griswold • Wearable computing research

9. Outline Introduction • Location Based Services • Related Implementations • Project Goals Implementation • Challenges and Limitations • Client Server Modeling Results • Example Query • Conclusions • Future Work References

10. Project Goal • Motivation: • Communication & organization • Mobile reminders & calendars • Advertising • Proposal: • Provide time & location sensitive messaging protocol • Automate message delivery • Trigger time & location reminders

11. Project Goal What makes us unique: • Sending context sensitive messages to other people • Using Google Local for GIS • Information on local businesses • Time and location sensitivity

12. Outline Introduction • Location Based Services • Related Implementations • Project Goals Implementation • Challenges and Limitations • Client Server Modeling Results • Example Query • Conclusions • Future Work References

13. Challenges • Precise measurement of location is difficult • Physical landmarks may block access • Optimal location may be further, but more accessible • Fortunately, location precision is not always required

14. Additional Limitations • User input • Input methods may be awkward • GPS range limitations • Location unavailable inside buildings • Dependencies on GIS • GIS must provide accurate information

15. Outline Introduction • Location Based Services • Related Implementations • Project Goals Implementation • Challenges and Limitations • Client Server Modeling Results • Example Query • Conclusions • Future Work References

16. Location Based Service Requirements Fulfilling Requirements: • Use GPS to determine location • Satisfies positioning requirement • Google Local for relevant information • Satisfies Geographic Information Services (GIS) requirement • Client and Server Programs process information • Satisfies information management requirement

17. High Level: Client-Server Model • Application • Send / receive time & location sensitive messages • Message • Holds recipient, message, and time or location • Central Server • Queue message until designated time or until location is reached • Send message alert to recipient • Information Server • Lookup keyword queries in Google Local • Return matching phone number & names • Pseudo-GPS location generator • Determine phone’s current location

18. Client-Server Model

19. Message Passing as a Petri Net

20. Client Message Packet Packet Types Local Query Message Time & Location Message

21. Design Choices • Server processes context • Client sends location at intervals • Server checks if message triggers Implication: If client loses connection to server, no messages will be delivered • Multiple Threads • Client has thread for: message listening, periodic location updates, input processing Implication: Performance penalty

22. Outline Introduction • Location Based Services • Related Implementations • Project Goals Implementation • Challenges and Limitations • Client Server Modeling Results • Example Query • Conclusions • Future Work References

23. Search for Pizza • Search for local pizza • Type: Local service query • Query: Look for pizza anywhere near current phone location. • Location: Latitude and longitude determined by GPS • Pseudo-GPS in this implementation • Return value: list of possible pizza parlors in vicinity. • User has option to send time sensitive message. • Example: Request delivery sent at next Friday 5:30pm.

24. Search for Pizza • Example of “pizza search” in the demo

25. Outline Introduction • Location Based Services • Related Implementations • Project Goals Implementation • Challenges and Limitations • Client Server Modeling Results • Example Query • Conclusions • Future Work References

26. Results • Design of time/location sensitive messaging protocol • Client-server model • Implementation of basic time/location sensitive messaging service • Pseudo-GPS for location • Google Local for GIS

27. Conclusions • Time/Location sensitive messaging is useful • Non-trivial implementations • Problems with non-accessible paths • Complex user input • More and more useful • Affordable GPS mobile devices available • Cheaper Internet on phones

28. Outline Introduction • Location Based Services • Related Implementations • Project Goals Implementation • Challenges and Limitations • Client Server Modeling Results • Example Query • Conclusions • Future Work References

29. Future Work • Development of optimal non-shortest path • Requires knowledge of city infrastructure • Higher GPS accuracy • Near-exact location • Location while in buildings • Simplified user input • Choosing between various parameters • Lots and lots of implementation • Able to use in everyday devices

30. Outline Introduction • Location Based Services • Related Implementations • Project Goals Implementation • Challenges and Limitations • Client Server Modeling Results • Example Query • Conclusions • Future Work References

31. Selected References • Smith, I., Consolvo, S., Hightower, J., Hughes, J.,Sohn, T., Abowd, G. Social Disclosure of Place: From Communication Practice. To Appear in Proc. Pervasive 2005 • Dey, A.K. and Abowd, G. D. CybreMinder: A Context-Aware System for SupportingReminders. In: 2nd Intl. Symposium on Handheld and Ubiquitous Computing. (2000) 172-186. • Dey, A.K, Salbert, D., Abowd, G.D. A Conceptual Framework and a Toolkit for Supportingthe Rapid Prototyping of Context-Aware Applications. Human-Computer Interaction,16. 2001. • Brown, P.J. The Stick-e Document: A Framework for Creating Context-Aware Applications.Electronic Publishing 8(2&3) 259-272 • Kaasinen, E. User Needs for Location-aware Mobile Services. Personal and UbiquitousComputing, 2003. 7(1), 70-79.