Locator and tracking service for peer to peer resources

• US 7,594,030 B2
• Filed: 09/13/2001
• Issued: 09/22/2009
• Est. Priority Date: 11/22/2000
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Bjorner, Nikolaj S., Teodosiu, Dan, Breunig, Markus M.
• Primary Examiner(s): Follansbee; John
• Assistant Examiner(s): Patel; Dhairya A
• Application Number:
  US09/952,652
• Publication Number:
  US 20020062375A1
• Time in Patent Office: 2,931 Days
• Field of Search: 709/201, 709/203, 709/204, 709/205, 709/206, 709/207
• US Class Current: 709/245
• 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/1072 Discovery involving ranked list compilation of candidate peers
• CPC Class Codes: H04L 67/1093 Some peer nodes performing special functions
• 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 naming service (RNS) server receives peer resource requests from peer platforms through a networking environment. The RNS server, possibly in cooperation with other RNS servers and peer registrars generates a response to the request to enable the peer platforms to access the requested peer resources. In one embodiment, a response includes a list of locations of peer devices in the networking environment where a resource is expected to be available. A requesting device can then choose to access the resource from one or more of the listed peer locations.

Claims

1. A method performed by a resource naming system (RNS) server providing resource naming service in a peer-to-peer networking environment having different groups of peers assigned to different RNS servers, the method comprising:

receiving a peer resource request at the RNS server, said peer resource request having been sent by a peer platform through the peer-to-peer networking environment that the peer platform is participating in, the peer resource request comprising a peer resource identifier identifying a peer resource available on the peer-to-peer networking environment,

tracking peers in the peer-to-peer networking environment that are assigned to the RNS server to determine whether those peers are connected to the peer-to-peer networking environment and in accordance with the tracking storing respective statuses of respective peers, a status indicating whether its corresponding peer is connected to the peer-to-peer networking environment;

generating a peer resource response based on the peer resource identifier and the statuses of the peers assigned to the RNS server, where indicia of a peer assigned to the RNS server is included in the peer resource response based on whether the peer resource identified in the peer resource request is available from the peers and based on whether the status of the peer indicates that the peer is connected to the peer-to-peer networking environment; and

returning the peer resource response to the peer platform through the peer-to-peer networking environment, said peer resource response to enable the peer platform to access the peer resource within the peer-to-peer networking environment.

2. The method of claim 1 wherein the peer resource identifier comprises at least one of a realm name for a peer-to-peer realm including the RNS server and a path name for the peer resource.

3. The method of claim 2 wherein the peer resource identifier includes both the realm name and the path name, the peer resource identifier being persistent and/or unique within the peer-to-peer networking environment.

4. The method of claim 1 wherein the peer-to-peer networking environment comprises a local area network, a wide area network, a private internet, and/or a public Internet.

5. The method of claim 1 wherein the peer resource response comprises an indication of a current version of the peer resource.

6. The method of claim 1 wherein generating the peer resource response comprises:

determining that resource status information regarding the peer resource is currently cached within the RNS server; and

generating the peer resource response based on the cached resource status information.

7. The method of claim 6 wherein the resource status information corresponds to a peer resource assigned either to the RNS server receiving the peer resource request or to a remote RNS server.

8. The method of claim 1 wherein generating the peer resource response comprises:

determining that a master publisher peer of the peer resource is assigned to the RNS server based on the peer resource request;

requesting and receiving resource status information corresponding to the peer resource from the master publisher peer of the peer resource; and

generating the peer resource response based on the resource status information corresponding to the peer resource.

9. The method of claim 8 wherein the RNS server has stored a list of the peers assigned to the RNS server, and wherein determining that the master publisher is homed at the RNS server comprises comparing the master publisher name to the list of peers assigned to the RNS server.

10. The method of claim 8 further comprising:

caching the resource status information within the RNS server.

11. The method of claim 8 wherein the resource status information comprises a version number for the master resource, and wherein generating the peer resource response based on the resource status information comprises:

comparing the version number from the resource status information to a version number for resource status information cached within the RNS server;

generating the peer resource response based on the resource status information cached within the RNS server if the version numbers match; and

generating the peer resource response based on the resource status information from the master publisher if the version numbers do not match.

12. The method of claim 1 wherein generating the peer resource response comprises:

determining that master publisher status information corresponding to the peer resource is currently cached within the RNS server based on the peer resource request, said master publisher status information indicating an assigned RNS server for the master publisher of the peer resource;

identifying a path name for the peer resource from the peer resource request;

requesting and receiving resource status information corresponding to the peer resource from the assigned RNS server based on the master publisher status information and the path name; and

generating the peer resource response based on the resource status information.

13. The method of claim 12 further comprising:

caching the resource status information within the RNS server.

14. The method of claim 1 wherein generating the peer resource response comprises:

identifying a master publisher name from the peer resource identifier;

requesting and receiving master publisher status information corresponding to the master publisher name from a master publisher registrar, said master publisher status information indicating a home RNS server for the master publisher of the peer resource corresponding to the master publisher name;

identifying a path name for the peer resource from the peer resource request;

requesting and receiving resource status information corresponding to the peer resource from the home RNS server based on the master publisher status information and the path name; and

generating the peer resource response based on the resource status information.

15. The method of claim 14 further comprising:

caching the master publisher status information and/or the resource status information within the RNS server.

16. The method of claim 1 wherein generating the peer resource response comprises:

selecting a set of network addresses from a plurality of network addresses where the peer resource is expected to be available in the peer-to-peer networking environment, said plurality of network addresses being cached in the RNS server, and where the indicia of the peer assigned to the RNS server comprises one of the network addresses; and

including the set of network addresses in the peer resource response, said peer platform to select from among the set of network addresses to access the peer resource.

17. The method of claim 16 wherein the set of network addresses is selected from the plurality of network addresses in response to successive peer resource requests in a fashion that distributes access loads across said plurality of network addresses.

18. The method of claim 17 wherein selecting the set of network addresses from the plurality of network addresses in response to successive peer resource requests comprises:

comparing a network address for the peer platform to each of the plurality of network addresses, said network address for the peer platform being part of the peer resource request, and a degree of relatedness between any two network addresses suggesting a related degree of topological closeness within the peer-to-peer networking environment; and

selecting network addresses from among the plurality of network addresses that have a highest degree of relatedness to the network address for the peer platform.

19. The method of claim 1, wherein the RNS server comprises a local RNS server, and the peer resource request comprises a first peer resource request, the method further comprising:

receiving a status request at the local RNS server, said status request corresponding to a local peer resource, and said status request being received from a remote RNS server through the peer-to-peer networking environment;

generating a status response for the local peer resource; and

returning the status response to the remote RNS server through the peer-to-peer networking environment, said status response to enable the remote RNS server to service a peer resource request for the local peer resource.

20. The method of claim 19 wherein said status response comprises at least one of a current version for the local peer resource and zero or more network addresses for the local peer resource.

22. The method of claim 19 wherein a master publisher of the local peer resource is homed at the local RNS server.

23. The method of claim 19 further comprising:

caching the status response within the remote RNS server, said remote RNS server to service subsequent peer resource quests for the local peer resource based on the cached status response.

24. The method of claim 23 further comprising:

flushing the status response from the remote RNS server after a particular period of time.

21. The method of 19 wherein the status request comprises a realm name for a peer-to-peer realm including the RNS server, a unique master publisher name corresponding to a master publisher of the local peer resource, and/or a pathname for the local peer resource within the master publisher.

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

receiving a peer resource request at a resource naming service (RNS) server, said peer resource request being received from a peer platform through a peer-to-peer networking environment, the peer resource request comprising a peer resource identifier identifying a peer resource;

determining and storing statuses of peers in the peer-to-peer networking environment that are assigned to the RNS server, the statuses indicating whether respective peers are available on the peer-to-peer networking environment;

generating a peer resource response based on the peer resource identifier and the determined statuses of the peers, where addresses or identifiers of peers are assigned to the RNS server are selected to be included in the peer resource response based on their having the peer resource and based on their previously stored statuses indicating whether they are available on the peer-to-peer networking environment; and

returning the peer resource response to the peer platform through the peer-to-peer networking environment, said peer resource response to enable the peer platform to access the peer resource within the peer-to-peer networking environment.

26. The machine readable storage medium of claim 25 wherein the peer resource identifier comprises a realm name for a peer-to-peer realm including the RNS server and/or a path name for the peer resource.

27. The machine readable storage medium of claim 26 wherein the peer resource identifier includes both the realm name and the path name, the peer resource identifier being persistent and/or unique within the networking environment.

28. The machine readable storage medium of claim 25 wherein the peer-to-peer networking environment comprises a local area network, a wide area network, a private internet, and the public Internet.

29. The machine readable storage medium of claim 25 wherein the peer resource response comprises an indication of a current version of the peer resource and/or a list of zero or more locations of peers within the peer-to-peer networking environment where the peer resource is expected to be available.

30. The machine readable storage medium of claim 25 wherein generating the peer resource response comprises:

determining that resource status information regarding the peer resource is currently cached within the RNS server; and

generating the peer resource response based on the cached resource status information.

31. The machine readable storage medium of claim 30 wherein the resource status information corresponds to a peer resource assigned either to the RNS server receiving the peer resource request or to a remote RNS server.

32. The machine readable storage medium of claim 25 wherein generating the peer resource response comprises:

determining that a master publisher of the peer resource is homed at the RNS server based on the peer resource request;

requesting and receiving resource status information corresponding to the peer resource from the master publisher of the peer resource; and

generating the peer resource response based on the resource status information corresponding to the peer resource.

33. The machine readable storage medium of claim 32 wherein the RNS server has stored a list of the peers assigned to the RNS server, and wherein determining that the master publisher is homed to the RNS server comprises comparing the master publisher name from the peer resource identifier to the list of peers assigned to the RNS server.

34. The machine readable storage medium of claim 32 the method further comprising:

caching the resource status information within the RNS server.

35. The machine readable storage medium of claim 32 wherein the resource status information comprises a version number for the master resource, and wherein generating the peer resource response based on the resource status information comprises:

comparing the version number from the resource status information to a version number for resource status information cached within the RNS server;

generating the peer resource response based on the resource status information cached within the RNS server if the version numbers match; and

generating the peer resource response based on the resource status information from the master publisher if the version numbers do not match.

36. The machine readable storage medium of claim 25 wherein generating the peer resource response comprises:

determining that master publisher status information corresponding to the peer resource is currently cached within the RNS server based on the peer resource request, said master publisher status information indicating an assigned RNS server for a master publisher of the peer resource;

identifying a pathname for the peer resource from the peer resource request;

requesting and receiving resource status information corresponding to the peer resource from the assigned RNS server based on the master publisher status information and the path name; and

generating the peer resource response based on the resource status information.

37. The machine readable storage medium of claim 36, the method further comprising:

caching the resource status information within the RNS server.

38. The machine readable storage medium of claim 25 wherein generating the peer resource response comprises:

identifying a master publisher name from the peer resource identifier;

requesting and receiving master publisher status information corresponding to the master publisher name from a master publisher registrar, said master publisher status information indicating a home RNS for a master publisher of the peer resource corresponding to the master publisher name;

identifying a path name for the peer resource from the peer resource request;

requesting and receiving resource status information corresponding to the peer resource from the home RNS server based on the master publisher status information and the path name; and

generating the peer resource response based on the resource status information.

39. The machine readable storage medium of claim 38, the method further comprising:

caching the master publisher status information and/or the resource status information within the RNS server.

40. The machine readable storage medium of claim 25 wherein generating the peer resource response comprises:

selecting a set of network addresses from a plurality of network addresses where the peer resource is expected to be available in the peer-to-peer networking environment, said plurality of network addresses being cached in the RNS server; and

including the set of network addresses in the peer resource response, said peer platform to select from among the set of network addresses to access the peer resource.

41. The machine readable storage medium of claim 40 wherein the set of network addresses is selected from the plurality of network addresses in response to successive peer resource requests in a fashion that distributes access loads across said plurality of network addresses.

42. The machine readable storage medium of claim 41 wherein selecting the set of network addresses from the plurality of network addresses in response to successive peer resource requests comprises:

comparing a network address for the peer platform to each of the plurality of network addresses, said network address for the peer platform being part of the peer resource request, and a degree of relatedness between any two network addresses suggesting a related degree of topological closeness within the peer-to-peer networking environment; and

selecting network addresses from among the plurality of network addresses that have a highest degree of relatedness to the network address for the peer platform.

43. The machine readable storage medium of claim 25, wherein the RNS server comprises a local RNS server, and the peer resource request comprises a first peer resource request, the method further comprising:

receiving a status request at the local RNS server, said status request corresponding to a local peer resource, and said status request being received from a remote RNS server through the peer-to-peer networking environment;

generating a status response for the local peer resource; and

returning the status response to the remote RNS server through the peer-to-peer networking environment, said status response to enable the remote RNS server to service a peer resource request for the local peer resource.

44. The machine readable storage medium of claim 43 wherein said status response comprises a current version for the local peer resource and/or zero or more network addresses for the local peer resource.

45. The machine readable storage medium of claim 43 wherein the status request comprises a unique master publisher name corresponding to a master publisher of the local peer resource and/or a path name for the local peer resource within the master publisher.

46. The machine readable storage medium of claim 43 wherein a master publisher of the local peer resource is homed at the local RNS server.

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

caching the status response within the remote RNS server, said remote RNS server to service subsequent peer resource quests for the local peer resource based on the cached status response.

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

flushing the status response from the remote RNS server after a particular period of time.

49. An apparatus comprising:

a resource naming service (RNS) server to receive a peer resource request, said peer resource request being received from a peer platform through a peer-to-peer networking environment, the peer resource request comprising a peer resource identifier identifying a peer resource available on the peer-to-peer networking environment;

said RNS server to determine statuses of peers in the peer-to-peer networking environment that are assigned the RNS server as a home RNS server, the statuses indicating whether respective peers are connected to the peer-to-peer network, where as peers connect or disconnect to the peer-to-peer network their status changes accordingly;

said RNS server to generate a peer resource response based on the peer resource request by identifying peers assigned to the RNS server that have cached or published the peer resource and that have statuses that indicate they are connected to the peer-to-peer network; and

said RNS server to return the peer resource response to the peer platform through the peer-to-peer networking environment, said peer resource response to enable the peer platform to access the peer resource within the peer-to-peer networking environment.