System and method for smart persistent cache

• US 20060069746A1
• Filed: 09/08/2004
• Published: 03/30/2006
• Est. Priority Date: 09/08/2004
• Status: Abandoned Application

• Current Assignee: Nokia Corporation
• Original Assignee: Nokia Corporation
• Inventors: Beaty, William D., Davis, Franklin A.
• Application Number:
  US10/936,777
• Publication Number:
  US 20060069746A1
• Time in Patent Office: Days
• US Class Current: 709/218
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching

Abstract

A system and method for smart, persistent cache management of received content within a terminal. Received content is tagged with cache directive allowing cache control to determine which of cache storage locations to use for storage of content. Cache control detects the number of instances that received content correlates to a newer version of purged content and provides the ability to re-classify cache persistence directive based upon the number of instances.

Claims

1. A network browsing system, comprising:

a network having Web pages addressable by Uniform Resource Locators (URLs);

a terminal coupled to the network to receive content associated with the Web pages, the terminal including;

a cache controller adapted to determine cache attributes of the received content; and

a cache memory coupled to the cache controller to store the content in a location indicated by the cache attributes.

2. The network browsing system according to claim 1, wherein the cache memory comprises:

a persistent cache memory adapted to store persistent content; and

a non-persistent cache memory adapted to store non-persistent content, wherein the cache controller determines which cache memory the content is to be stored by inspecting a cache persistence directive associated with the cache attributes.

3. The network browsing system according to claim 2, wherein the terminal further comprises:

a purge list adapted to maintain entries corresponding to URLs previously purged by the cache controller; and

a purge counter adapted to maintain a count indicating a number of instances that the purged content corresponds to an older version of the received content.

4. The network browsing system according to claim 1, wherein the terminal further comprises a display adapted to provide an indication of the cache attributes associated with the received content.

5. The network browsing system according to claim 4, wherein the display facilitates an override of the storage location determined by the cache controller.

6. The network browsing system according to claim 1, further comprising an origin server adapted to modify the cache attributes of the stored content.

7. A method for managing content received by a terminal from a network, comprising:

inspecting a priority directive associated with the received content;

allowing a modification to be made on the priority directive of the received content; and

storing the received content in a storage location indicative of the priority directive.

8. The method according to claim 7, wherein inspecting the priority directive comprises:

comparing the received content with content previously received; and

updating a storage location of the previously received content if the received content is associated with the previously received content.

9. The method according to claim 8, wherein allowing a modification to be made on the priority directive of the received content comprises allowing an alternative storage location to be selected if the storage location of the previously received content is different than the storage location indicated by the priority directive of the received content.

10. The method according to claim 9, wherein the alternative storage location is selected by modifying the priority directive to be indicative of the desired alternative storage location.

11. The method according to claim 10, wherein storing the received content comprises:

directing the received content to persistent storage if the priority directive indicates use of persistent storage; and

directing the received content to non-persistent storage if the priority directive indicates use of non-persistent storage.

12. The method according to claim 7, wherein allowing a modification to be made on the priority directive of the received content comprises:

displaying a plurality of lists, each list containing entries indicative of received content storage locations; and

modifying a priority directive associated with each entry.

13. The method according to claim 7, further comprising:

detecting stale content in non-persistent storage; and

purging the stale content.

14. The method according to claim 13, further comprising:

comparing the purged content to the received content; and

incrementing a purge count if the purged content is related to the received content.

15. The method according to claim 14, wherein the modification of the priority directive is allowed in response to determining that the incremented purge count exceeds a predetermined threshold.

16. An origin server coupled to a network to provide priority directives within requested content hosted by the origin server, the origin server comprising:

means for receiving a content request from a browsing terminal;

means for generating content in response to the content requests;

means for adding priority directives to header information associated with the requested content; and

means for sending a response to the browsing terminal containing the header information and the requested content, wherein the priority directives indicate a storage location to be used by the browsing terminal.

17. The server according to claim 16, further comprising means to modify age characteristics of requested content in the storage location of the browsing terminal.

18. A computer-readable medium having instructions stored thereon which are executable by an origin server by performing steps comprising:

receiving a content request from a browsing terminal;

generating content in response to the content request; and

adding priority directives to header information associated with the requested content.

19. The computer-readable medium according to claim 18, further comprising steps to modify age characteristics of requested content in the storage location of the browsing terminal.

20. A mobile terminal capable of being wirelessly coupled to a network to receive content hosted by a content provider within the network, the mobile terminal comprising:

a memory capable of storing at least one of a cache control module and a cache memory module;

a processor coupled to the memory and configured by the cache control module to direct the received content into portions of the cache memory module; and

a transceiver configured to facilitate the content exchange, wherein the cache control module is responsive to cache and priority directives supplied by the content provider in determining which portion of the cache memory module to use for storage.

21. The mobile terminal according to claim 20, wherein the cache memory module comprises:

a persistent storage location adapted to receive persistent content; and

a non-persistent storage location adapted to receive non-persistent content.

22. The mobile terminal according to claim 21, wherein the memory further comprises a purge list adapted to provide a history of content purged from the non-persistent storage location.

23. The mobile terminal according to claim 22, wherein the memory further comprises a purge counter adapted to provide a count indicative of the number of instances that the purged content corresponds to an aged version of the received content.

24. A computer-readable medium having instructions stored thereon which are executable by a mobile terminal for providing a smart persistent cache by performing steps comprising:

storing received content into one of a persistent cache storage location and a normal cache storage location in response to a priority directive associated with the received content;

conditionally purging content from the persistent cache storage location to provide storage for high priority received content, the high priority received content having a priority directive indicative of the persistent cache storage location; and

diverting the high priority received content to the normal cache storage location when purging content from the persistent cache storage location is not allowed.

25. The computer readable medium of claim 24, wherein conditionally purging content from the persistent cache storage location comprises purging content having a lower priority than the received content when the persistent cache storage location is full.

26. The computer readable medium of claim 25, wherein conditionally purging content from the persistent cache storage location further comprises purging least recently used content when there is no lower priority content contained within the persistent cache storage location relative to the received content.

27. The computer readable medium of claim 26, wherein the purged content is diverted to the normal cache storage location.

28. A method of determining a storage location for received content, comprising:

comparing the received content to previously purged content;

incrementing a purge count if the received content matches a Uniform Resource Locator (URL) of the previously purged content;

comparing the purge count to a predetermined threshold;

automatically assigning a priority directive and allowing storage of the received content into a persistent cache if the purge count exceeds the predetermined threshold; and

storing the received content into a normal cache if the purge count does not exceed the predetermined threshold.

29. A method of automatically determining a priority directive of received content, the method comprising:

.

detecting an absence of a priority directive within the received content;

comparing a Uniform Resource Locator (URL) associated with the received content to a previously stored service provider'"'"'s URL directory tree; and

assigning a priority directive to the received content in response to finding a match between the URL associated with the received content and the previously stored service provider'"'"'s URL directory tree, wherein the assigned priority directive is indicative of a position of the matched URL in the service provider'"'"'s URL directory tree.

30. A method of automatically determining a priority directive of received content, the method comprising:

comparing a Uniform Resource Locator (URL) associated with the received content to a list of frequently accessed URLs; and

assigning a priority directive to the received content in response to finding a match between the URL associated with the received content and the list of frequently accessed URLs, wherein the assigned priority directive is indicative of a frequency of use of the matched URL.