1 / 9

Pushing Web Pages into Personal Digital Assistants

Explore how context-driven services require pushing contents into PDAs, avoiding network overload & real-time constraints with a single push at the right moment. Learn about scenarios in malls & museums and a solution involving URL transfer to enhance user experience.

llinde
Download Presentation

Pushing Web Pages into Personal Digital Assistants

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. Pushing Web Pages into Personal Digital Assistants Enrique Costa Montenegro Departamento de Ingeniería Telemática ETSI Telecomunicación Universidad de Vigo, Spain kike@det.uvigo.es

  2. Introduction • Context-driven services  need to push contents into PDAs • Minimum client participation • Inefficiency of periodic reloads • Network overload • Real time constraints • Single push at the right moment

  3. Scenario I: Mall • Walking customers with wireless PDAs • Auxiliar Bluetooth/RFID/... location network • Different web pages associated to different positions • Goals: • Event notification: restaurants, cinemas, special offers... • Advertisements

  4. Scenario II: Museum • Walking visitors with wireless PDAs • Auxiliar Bluetooth/RFID/... location network • Different web pages associated to different museum halls • Additional features: • Alarm to suggest manual update • In-depth information links

  5. Our Solution

  6. Our Solution (II) • A) URL sent from server to PDA connection server at a given port • B) PDA connection server submits URL to browser • C) Browser asks for the URL • D) Web server sends Web page to PDA

  7. Conclusions • Need to push URLs into PDAs in some context-driven scenarios • HTTP reloads or Javascript approaches do not scale well • Connection server prototype developed (7 Kb binary) • Future upgrade: Java for individual frame upload

  8. Questions!!

  9. The End

More Related