Method and system for dynamic distributed data caching

• US 7,188,145 B2
• Filed: 01/12/2001
• Issued: 03/06/2007
• Est. Priority Date: 01/12/2001
• Status: Expired due to Term

• Current Assignee: Parallel Networks, LLC (epicRealm Licensing LP)
• Original Assignee: epicRealm Licensing LLC (epicRealm Licensing LP)
• Inventors: Lowery, Keith A., Chin, Bryan S., Consolver, David A., DeMasters, Gregg A.
• Primary Examiner(s): Najjar, Saleh
• Assistant Examiner(s): WON, MICHAEL YOUNG
• Application Number:
  US09/759,406
• Publication Number:
  US 20020107934A1
• Time in Patent Office: 2,244 Days
• Field of Search: 709/213, 709/217, 709/201, 709/212, 709/203, 709/205, 709/215, 709/216, 709/248, 707/8, 707/10, 711/151
• US Class Current: 709/214
• CPC Class Codes: G06F 16/9537 Spatial or temporal dependent retrieval, e.g. spatiotemporal queries
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: H04L 43/16 Threshold monitoring
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/104 Peer-to-peer [P2P] networks
• CPC Class Codes: H04L 67/1046 Joining mechanisms
• CPC Class Codes: H04L 67/1048 Departure or maintenance mechanisms
• CPC Class Codes: H04L 67/1068 Discovery involving direct consultation or announcement among potential requesting and potential source peers
• CPC Class Codes: H04L 67/108 characterised by resources being split in blocks or fragments
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching

Abstract

A method and system for dynamic distributed data caching is presented. The method includes providing a cache community (402) comprising at least one peer (413). Each peer has an associated first content portion (511) indicating content to be cached by the respective peer. A client (404) may be allowed to join the cache community. A peer list (426) associated with the cache community is updated to include the client. The peer list indicates the peers in the cache community. A respective second content portion (511) is associated with each peer based on the addition of the client.

Claims

1. A method for dynamic distributed data caching comprising:

providing a cache community on a first side of a point of presence, the cache community comprising at least one peer, the cache community being associated with content obtained from a second side of the point of presence, the content being cached by the at least one peer;

allowing a client to join the cache community;

updating a peer list associated with the cache community to include the client, the peer list indicating the peers in the cache community;

associating the content with the client based on joinder of the client;

re-allocating the cache storage of the content among the peers in the cache community in response to allowing the client to join the community.

2. The method for dynamic distributed data caching according to claim 1 and further comprising:

receiving a join request from the client; and

determining whether to allow the client to join the cache community.

3. The method dynamic distributed data caching according to claim 2, wherein the join request comprises a CRMSG_REQUESTTOJOIN data message.

4. The method for dynamic distributed data caching according to claim 1, wherein allowing the client to join the cache community comprises:

generating an allow message;

associating the peer list with the allow message; and

communicating the allow message to the client.

5. The method for dynamic distributed data caching according to claim 4, wherein allowing the client to joint the cache community comprises:

generating an allow message comprising the peer list updated to include the client;

communicating the allow message to the client; and

communicating the allow message to at least one member associated with the cache community.

6. The method for dynamic distributed data caching according to claim 4, wherein the allow message comprises a CRMSG_UPDATEPEERLTST data message.

7. The method for dynamic distributed caching according to claim 4, wherein the peer list associated with the allow message comprises the updated peer list which includes the client.

8. The method for dynamic distributed data caching according to claim 1, wherein the point of presence is an ISP.

9. The method for dynamic distributed data caching according to claim 1, wherein a one of the peers comprises a member.

10. The method for dynamic distributed data caching according to claim 1, wherein a one of the peers comprises a master.

11. The method for dynamic distributed data caching according to claim 1, wherein associating the content with the client comprises:

allocating the content to peers in the peer list; and

updating an allocation table to indicate the content associated with the peers.

12. The method for dynamic distributed data caching according to claim 11, wherein the content is cached at more than one peer.

13. The method for dynamic distributed data caching according to claim 11, wherein the content includes a plurality of internet protocol domain names.

14. The method for dynamic distributed data caching according to claim 1 and further comprising removing the association between the content and the peers.

15. A system for dynamic distributed data caching comprising:

logic encoded on storage and operable to;

provide a cache community on a first side of a point of presence, the cache community comprising at least one peer, the cache community being associated with content obtained from a second side of the point of presence, the content being cached by the at least one peer;

allow a client to join the cache community;

update a peer list associated with the cache community to include the client, the peer list indicating the peers in the cache community;

associate the content with the client based on joinder of the client;

re-allocate the cache storage of the content among the peers in the cache community in response to allowing the client to join the community.

16. The system for dynamic distributed data caching according to claim 15, wherein the logic is further operable to:

receive a join request from the client; and

determine whether to allow the client to join the cache community.

17. The system for dynamic distributed data caching according to claim 16, wherein the join request comprises a CRMSG_REQUESTTOJOIN data message.

18. The system for dynamic distributed data caching according to claim 15, wherein the logic is further operable to:

generate an allow message;

associate the peer list with the allow message;

communicate the allow message to the client.

19. The system for dynamic distributed data caching according to claim 18, wherein the logic is further operable to:

generate an allow message comprising the peer list updated to include the client;

communicate the allow message to the client; and

communicate the allow message to at least one member associated with the cache community.

20. The system for dynamic distributed data caching according to claim 18, wherein the allow message comprises a CRMSG_UPDATEPEERLIST data message.

21. The system for dynamic distributed caching according to claim 18, wherein the peer list associated with the allow message comprises the updated peer list which includes the client.

22. The system for dynamic distributed data caching according to claim 15, wherein the point of presence is an ISP.

23. The system for dynamic distributed data caching according to claim 15, wherein a one of the peers comprises a member.

24. The system for dynamic distributed data caching according to claim 15, wherein a one of the peers comprises a master.

25. The system for dynamic distributed data caching according to claim 15, wherein the logic is further operable to:

allocate the content to peers in the peer list; and

update an allocation table to indicate the content associated with the peers.

26. The system for dynamic distributed data caching according to claim 25, wherein the content is cached at more than one peer.

27. The system for dynamic distributed data caching according to claim 25, wherein the content includes a plurality of internet protocol domain names.

28. The system for dynamic distributed data caching according to claim 15, wherein the logic is further operable to remove the association between the content and the peers.

29. A method for dynamic distributed data caching comprising:

communicating a community request to an administration module;

receiving a community list from the administration module in response to the community request, the community list including a list of communities;

selecting one of the communities to attempt to join;

generating a join request to attempt to join the selected one of the communities;

receiving an allow message associated with the selected one of the communities;

receiving a peer list associated with the selected one of the communities;

receiving content allocated for storage in caches of peers in the peer list for cache storage re-allocation in response to joining the selected one of the communities; and

providing content for cache storage re-allocation to peers in the peer list in response to joining the selected one of the communities.

30. The method for dynamic distributed data caching according to claim 29, wherein the community request comprises a CRMSG_WAKEUP data message.

31. The method for dynamic distributed data caching according to claim 29, wherein the join request comprises a CRMSG_REQUESTTOJOTN data message.

32. A system for dynamic distributed data caching comprising:

logic encoded on storage and operable to;

communicate a community request to an administration module;

receive a community list from the administration module in response to the community request, the community list including a list of communities;

select one of the communities to attempt to join;

generate a join request to attempt to join the selected one of the communities;

receive an allow message associated with the selected one of the communities;

receive a peer list associated with the selected one of the communities;

receive content allocated for storage in caches of peers in the peer list for cache storage re-allocation in response to joining the selected one of the communities; and

provide content for cache storage re-allocation to peers in the peer list in response to joining the selected one of the communities.

33. The system for dynamic distributed data caching according to claim 32, wherein the community request comprises a CRMSG_WAKEUP data message.

34. The system for dynamic distributed data caching according to claim 32, wherein the join request comprises a CRMSG_REQUESTTOJOTN data message.

35. A system for dynamic distributed data caching comprising:

means for providing a cache community on a first side of a point of presence, the cache community comprising at least one peer, the cache community being associated with content obtained from a second side of the point of presence, the content being cached by the at least one peer;

means for allowing a client to join the cache community;

means for updating a peer list associated with the cache community to include the client, the peer list indicating the peers in the cache community;

means for associating the content with the client based on joinder of the client;

means for re-allocating the cache storage of the content among the peers in the cache community in response to allowing the client to join the community.

36. A system for dynamic distributed data caching comprising:

means for communicating a community request to an administration module;

means for receiving a community list from the administration module in response to the community request, the community list including a list of communities;

means for selecting one of the communities to attempt to join;

means for generating a join request to attempt to join the selected one of the communities;

means for receiving an allow message associated with the selected one of the communities;

means for receiving a peer list associated with the selected one of the communities;

means for receiving content allocated for storage in caches of peers in the peer list for cache storage re-allocation in response to joining the selected one of the communities; and

means for providing content for cache storage re-allocation to peers in the peer list in response to joining the selected one of the communities.