Resource coherency among resources cached in a peer to peer environment

• US 20020062336A1
• Filed: 09/13/2001
• Published: 05/23/2002
• Est. Priority Date: 11/22/2000
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Bjorner, Nikolaj S., Teodosiu, Dan, Breunig, Markus M.
• Application Number:
  US09/952,367
• Publication Number:
  US 20020062336A1
• Time in Patent Office: Days
• US Class Current: 709/201
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 61/4552 Lookup mechanisms between a plurality of directories; Synchronisation of directories, e.g. metadirectories
• CPC Class Codes: H04L 67/104 Peer-to-peer [P2P] networks
• CPC Class Codes: H04L 67/1063 Discovery through centralising entities
• CPC Class Codes: H04L 67/1072 Discovery involving ranked list compilation of candidate peers
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 67/5682 Policies or rules for updating, deleting or replacing the stored data
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A resource tracking service tracks locations of peer resources among peer devices in a networking environment. As a peer resource is cached and made available at multiple peer devices, the locator service also tracks state information for each copy of the resources and, in various embodiments, maintains coherency among the copies as the resource is modified and/or deleted.

Claims

1. A method comprising:

receiving a status indication at a resource naming service (RNS) server, said status indication being received through a networking environment, and said status indication indicating that a peer platform has available a peer resource; and

updating a record cached by the RNS server, said record to indicate locations in the networking environment where the peer resource is expected to be available, said RNS server to service requests for the peer resource with one or more locations from the record.

2. The method of claim 1 wherein the status indication comprises a publication notice, said publication notice being proactively sent to the RNS server upon one of creation, modification, and deletion of the peer resource.

3. The method of claim 1 wherein the status indication comprises a publication acknowledgement, said publication acknowledgement being sent to the RNS server in response to a status request initiated by the RNS server.

4. The method of claim 1 wherein the status indication is received from one of a master publisher of the peer resource homed at the RNS server, a caching publisher of the peer resource homed at the RNS server, and a remote RNS server at which the master publisher of the peer resource is homed.

5. The method of claim 1 wherein updating the record comprises:

creating an initial record corresponding to a first status indication received corresponding to the peer resource.

6. The method of claim 1 wherein updating the record comprises:

adding a network address corresponding to the peer platform to a list of network addresses cached by the RNS server for the peer resource, wherein said RNS server services the requests for the peer resource with one or more networking addresses from the list.

7. The method of claim 1 wherein the locations in the networking environment where the peer resource is expected to be available comprise a location of a master resource and a plurality of locations of cached copies of the master resource in the networking environment, and wherein updating the record comprises:

maintaining coherency among the master resource and the plurality of cached copies.

8. The method of claim 7 wherein maintaining coherency comprises:

comparing a version number for the peer resource from the status indication to a version number for the peer resource from the record;

flushing the record of any previously recorded locations for the peer resource if the version number from the status indication indicates a newer version than the version number from the record; and

recording a location of the peer platform from the status indication.

9. The method of claim 7 wherein maintaining coherency further comprises:

comparing a version number for the peer resource from the status indication to a version number for the peer resource from the record;

disregarding the status indication if the version number from the status indication indicates an older version than the version number from the record;

sending back an indication to the peer that sent the status indication to notify it that it is caching an obsolete version, if the version number from the status indication indicates an older version than the version number from the record.

10. The method of claim 1 further comprising:

flushing the record after a particular period of time.

11. The method of claim 10 wherein flushing the record comprises:

flushing locations corresponding to resource publishers homed at remote RNS servers.

12. The method of claim 8 wherein the version number is generated based on a current time when a new version is created.

13. The method of claim 8 wherein the version number is uniquely generated when a new version is created.

14. The method of claim 1 wherein the status indication is sent to the RNS server upon modification and/or deletion of the peer resource if the RNS server has previously cached the record for the peer resource.

16. The method of claim 15 further comprising:

flushing the copy of the peer resource from the second peer device after at least one of a particular period of time or exceeding a specified space quota for the cached resources; and

notifying the RNS server that the copy of the peer resource is no longer available at the second peer device.

17. The method of claim 15 wherein publishing the peer resource further comprises notifying the RNS server of a version of the copy of the peer resource.

18. The method of claim 17 further comprising:

periodically notifying the RNS server that the copy of the peer resource is available at the second peer device and notifying the RNS server of the version of the copy of the peer resource.

19. The method of claim 17 wherein the RNS server is to discontinue tracking the copy of the peer resource on the second peer device when a version number for the peer resource no longer matches the version number for the copy of the peer resource.

20. The method of claim 17 further comprising:

receiving an instruction from the RNS server to flush the copy of the peer resource when a version number for the peer resource no longer matches the version number for the copy of the peer resource; and

flushing the copy of the peer resource.

21. The method of claim 15 wherein conducting the peer-to-peer access comprises:

requesting and receiving a response from a particular peer device at a network location selected from a list of network locations for the peer resource provided by the RNS server, said response comprising a version number for a copy of the peer resource available at the particular peer device;

comparing the version number for the copy of the peer device available at the particular peer device to a current version number for the peer resource provided by the RNS server; and

repeating the requesting, receiving, and comparing until the version numbers match.

15. A method comprising:

conducting a peer-to-peer access of a peer resource available at a first peer device;

caching a copy of the peer resource at a second peer device;

publishing the peer resource at the second peer device by notifying a resource naming service (RNS) server to which the second peer device is assigned that the copy of the peer resource is available at the second peer device, said RNS server to serve subsequent requests for the peer resource with a network location of the second peer device to enable access to the copy of the peer resource.

22. A method comprising:

publishing a master copy of a peer resource at a master peer device, said master copy being available to serve requests within a peer-to-peer realm, said requests first being directed to the master peer device by a resource locator service;

servicing a plurality of requests from a plurality of caching peer devices with the master copy of the peer resource, particular ones of the plurality of caching peer devices to publish a cached copy of the peer resource and service additional requests with the cached copy of the peer resource, said peer resource to be cached by a plurality of generations of caching peer devices to make the peer resource available at many different locations within the peer-to-peer realm, said resource locator service to track locations of the peer resource within the realm and service requests for the peer resource with one or more of the locations.

23. The method of claim 22 further comprising:

proactively notifying the locator service of a modification to the master copy of the peer resource, said resource locator service to flush its records of locations of out-dated cached copies of the peer resource.

24. The method of claim 23 wherein proactively notifying the locator service comprises:

proactively notifying the locator service if the locator service has previously cached a record corresponding to the peer resource at the master peer device

25. The method of claim 22 further comprising:

receiving a status request for the master copy of the peer resource from the resource locator service, said resource locator service to issue the status request before servicing a new request for the peer resource; and

responding to the status request with a current version number of the master copy, said resource locator service to service the new request only with locations for the peer resource, if any, having a same version number.

27. The machine readable medium of claim 26 wherein the status indication comprises a publication notice, said publication notice being proactively sent to the RNS server upon one of creation, modification, and deletion of the peer resource.

28. The machine readable medium of claim 26 wherein the status indication comprises a publication acknowledgement, said publication acknowledgement being sent to the RNS server in response to a status request initiated by the RNS server.

29. The machine readable medium of claim 26 wherein the status indication is received from one of a master publisher of the peer resource homed at the RNS server, a caching publisher of the peer resource homed at the RNS server, and a remote RNS server at which the master publisher of the peer resource is homed.

30. The machine readable medium of claim 26 wherein updating the record comprises:

creating an initial record corresponding to a first status indication received corresponding to the peer resource.

31. The machine readable medium of claim 26 wherein updating the record comprises:

adding a network address corresponding to the peer platform to a list of network addresses cached by the RNS server for the peer resource, wherein said RNS server services the requests for the peer resource with one or more networking addresses from the list.

32. The machine readable medium of claim 26 wherein the locations in the networking environment where the peer resource is expected to be available comprise a location of a master resource and a plurality of locations of cached copies of the master resource in the networking environment, and wherein updating the record comprises:

maintaining coherency among the master resource and the plurality of cached copies.

33. The machine readable medium of claim 32 wherein maintaining coherency comprises:

comparing a version number for the peer resource from the status indication to a version number for the peer resource from the record;

flushing the record of any previously recorded locations for the peer resource if the version number from the status indication indicates a newer version than the version number from the record; and

recording a location of the peer platform from the status indication.

34. The machine readable medium of claim 32 wherein maintaining coherency further comprises:

comparing a version number for the peer resource from the status indication to a version number for the peer resource from the record;

disregarding the status indication if the version number from the status indication indicates an older version than the version number from the record.

35. The machine readable medium of claim 26, the method further comprising:

flushing the record after a particular period of time.

36. The machine readable medium of claim 35 wherein flushing the record comprises:

flushing locations corresponding to resource publishers homed at remote RNS servers.

37. The machine readable medium of claim 33 wherein the version number is generated based on a current time when a new version is created.

38. The machine readable medium of claim 33 wherein the version number is sequentially generated when a new version is created.

39. The machine readable medium of claim 26 wherein the status indication is sent to the RNS server upon modification and/or deletion of the peer resource if the RNS server has previously cached the record for the peer resource.

26. A machine readable medium having stored thereon machine executable instructions to implement a method comprising:

receiving a status indication at a resource naming service (RNS) server, said status indication being received through a networking environment, and said status indication indicating that a peer platform has available a peer resource; and

updating a record cached by the RNS server, said record to indicate locations in the networking environment where the peer resource is expected to be available, said RNS server to service requests for the peer resource with one or more locations from the record.

40. A machine readable medium having stored thereon machine executable instructions to implement a method comprising:

conducting a peer-to-peer access of a peer resource available at a first peer device;

caching a copy of the peer resource at a second peer device;

publishing the peer resource at the second peer device by notifying a resource naming service (RNS) server to which the second peer device is assigned that the copy of the peer resource is available at the second peer device, said RNS server to serve subsequent requests for the peer resource with a network location of the second peer device to enable access to the copy of the peer resource.

41. The machine readable medium of claim 40, the method further comprising:

flushing the copy of the peer resource from the second peer device after at least one of a particular period of time or exceeding a specified space quota for the cached resources; and

notifying the RNS server that the copy of the peer resource is no longer available at the second peer device.

42. The machine readable medium of claim 40 wherein publishing the peer resource further comprises notifying the RNS server of a version of the copy of the peer resource.

43. The machine readable medium of claim 42, the method further comprising:

periodically notifying the RNS server that the copy of the peer resource is available at the second peer device and notifying the RNS server of the version of the copy of the peer resource.

44. The machine readable medium of claim 42 wherein the RNS server is to discontinue tracking the copy of the peer resource on the second peer device when a version number for the peer resource no longer matches the version number for the copy of the peer resource.

45. The machine readable medium of claim 42, the method further comprising:

receiving an instruction from the RNS server to flush the copy of the peer resource when a version number for the peer resource no longer matches the version number for the copy of the peer resource; and

flushing the copy of the peer resource.

46. The machine readable medium of claim 40 wherein conducting the peer-to-peer access comprises:

requesting and receiving a response from a particular peer device at a network location selected from a list of network locations for the peer resource provided by the RNS server, said response comprising a version number for a copy of the peer resource available at the particular peer device;

comparing the version number for the copy of the peer device available at the particular peer device to a current version number for the peer resource provided by the RNS server; and

repeating the requesting, receiving, and comparing until the version numbers match.

48. The machine readable medium of claim 47, the method further comprising:

proactively notifying the locator service of a modification to the master copy of the peer resource, said resource locator service to flush its records of locations of outdated cached copies of the peer resource.

49. The machine readable medium of claim 48 wherein proactively notifying the locator service comprises:

proactively notifying the locator service if the locator service has previously cached a record corresponding to the peer resource at the master peer device

50. The machine readable medium of claim 47, the method further comprising:

receiving a status request for the master copy of the peer resource from the resource locator service, said resource locator service to issue the status request before servicing a new request for the peer resource; and

responding to the status request with a current version number of the master copy, said resource locator service to service the new request only with locations for the peer resource, if any, having a same version number.

47. A machine readable medium having stored thereon machine executable instruction to implement a method comprising:

publishing a master copy of a peer resource at a master peer device, said master copy being available to serve requests within a peer-to-peer realm, said requests first being directed to the master peer device by a resource locator service;

servicing a plurality of requests from a plurality of caching peer devices with the master copy of the peer resource, particular ones of the plurality of caching peer devices to publish a cached copy of the peer resource and service additional requests with the cached copy of the peer resource, said peer resource to be cached by a plurality of generations of caching peer devices to make the peer resource available at many different locations within the peer-to-peer realm, said resource locator service to track locations of the peer resource within the realm and service requests for the peer resource with one or more of the locations.

51. An apparatus comprising:

a resource naming service (RNS) server to receive a status indication, said status indication being received through a networking environment, and said status indication indicating that a peer platform has available a peer resource; and

a cache coupled to said RNS server, said RNS server to update a record in the cache, said record to indicate locations in the networking environment where the peer resource is expected to be available, said RNS server to service requests for the peer resource with one or more locations from the record.

52. An apparatus comprising:

a first peer device to conduct a peer-to-peer access of a peer resource available at a second peer device;

a cache coupled to the first peer device, said first peer device to cache a copy of the peer resource in the cache; and

said first peer device to publish the peer resource by notifying a resource naming service (RNS) server to which the first peer device is assigned that the copy of the peer resource is available at the first peer device, said RNS server to serve subsequent requests for the peer resource with a network location of the first peer device to enable access to the copy of the peer resource.

53. An apparatus comprising:

a master peer device to publish a master copy of a peer resource, said master copy being available to serve requests within a peer-to-peer realm, said requests first being directed to the master peer device by a resource locator service;

said master peer device to service a plurality of requests from a plurality of caching peer devices with the master copy of the peer resource, particular ones of the plurality of caching peer devices to publish a cached copy of the peer resource and service additional requests with the cached copy of the peer resource, said peer resource to be cached by a plurality of generations of caching peer devices to make the peer resource available at many different locations within the peer-to-peer realm, said resource locator service to track locations of the peer resource within the realm and service requests for the peer resource with one or more of the locations.