Browse Prior Art Database

Method for Pushing Permanent Content to Device Cache When It Is Pulled From a Content Server

IP.com Disclosure Number: IPCOM000131865D
Publication Date: 2005-Nov-21
Document File: 1 page(s) / 39K

Publishing Venue

The IP.com Prior Art Database

Abstract

On occasion, a mobile device user’s requests (using a mobile browswer) from content servers may be delayed. Sometimes, it takes time to deliver the content over-the-ar (OTA) wirelessly to the device. In most instances, the time content (e.g. home page, images, ring-tones) doesn’t change for long periods, and user has to unnecessarily make the same request until it is changed. A proposed solution is to push such content onto the device cache. In the future, when the user makes a request of the same content, the device can load the content from the cache. This method will reduce the OTA network traffic and increases the user experience on the subsequent visit because it loads the content from the device cache. When there are changes at the server, the content can be further pushed to the device. When the user requests content and it is not found on the device’s cache, the content is pulled from a content server. The content server logs this pull request and the content server uses its internal mechanism to push of the same content with expirey date to the device that requested it. On the next request to this content from the same device, the content will be retrieved from the device’s cache.

This text was extracted from a Microsoft Word document.
This is the abbreviated version, containing approximately 100% of the total text.

PUSH AND PULL CONTENT

Method for Pushing Permanent Content to Device Cache When It Is Pulled From a Content Server

Disclosed Anonymously

On occasion, a mobile device user’s requests (using a mobile browswer) from content servers may be delayed. Sometimes, it takes time to deliver the content over-the-ar (OTA) wirelessly to the device. In most instances, the time content (e.g. home page, images, ring-tones) doesn’t change for long periods, and user has to unnecessarily make the same request until it is changed.

A proposed solution is to push such content onto the device cache. In the future, when the user makes a request of the same content, the device can load the content from the cache. This method will reduce the OTA network traffic and increases the user experience on the subsequent visit because it loads the content from the device cache. When there are changes at the server, the content can be further pushed to the device.

When the user requests content and it is not found on the device’s cache, the content is pulled from a content server. The content server logs this pull request and the content server uses its internal mechanism to push of the same content with expirey date to the device that requested it. On the next request to this content from the same device, the content will be retrieved from the device’s cache.