Universal naming scheme for peer-to-peer resources

• US 7,562,149 B2
• Filed: 02/25/2005
• Issued: 07/14/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): Vaughn, Jr.; William C
• Assistant Examiner(s): Bayard; Djenane M
• Application Number:
  US11/066,366
• Publication Number:
  US 20050195838A1
• Time in Patent Office: 1,600 Days
• Field of Search: 709/248, 709/217, 709/207, 709/228, 709/201, 709/206, 709/245, 709/218, 709/220, 709/223, 709/229, 717/170
• US Class Current: 709/229
• 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/1046 Joining mechanisms
• CPC Class Codes: H04L 67/1063 Discovery through centralising entities

Abstract

Peer devices register with a resource locator service so that the peer devices can be uniquely identified in a networking environment. An addressing scheme addresses a peer resource in the networking environment based on the unique identifier of a peer device that is a master publisher of the resource. Based on the addressing scheme, the resource locator service can track the location of the master publisher of the resource as well as additional locations of peer devices that have cached the resource and made it available. In various embodiments, the resource locator service can service requests for peer resources by providing a list of locations where the resource is expected to be available or, in the case of non-compatible requester, provide access to the resource itself.

Claims

1. A method comprising:

receiving a peer notification including a new version number at a resource naming service (RNS) server included in a peer-to-peer networking environment comprising peer devices, said peer notification being received from a peer platform included in the peer-to-peer networking environment through the peer-to-peer networking environment, the new version number corresponding to a new revision of a resource available via peer sharing in the peer-to-peer networking environment, where different version numbers of the resource correspond to different revisions of the resource, where the RNS server participates in a hierarchy of other RNS servers that cooperatively respond to resource lookup requests such that the RNS server forwards a resource lookup request to another RNS server if the RNS server is unable to answer with a peer location of the resource lookup request; and

updating a record stored at the RNS server based on the peer notification, the updating causing the record to include the new version number corresponding to the new revision of the resource, said updated record being used by the RNS server to service lookup requests for peer resources stored at a plurality of peer resources with network locations within the peer-to-peer networking environment of respective peer devices in the peer-to-peer networking environment.

2. The method of claim 1 wherein a network location within the peer-to-peer networking environment for a particular peer device is dynamically allocated, wherein the peer notification comprises a current network address for the particular peer device, and wherein updating the record comprises:

storing the current network address in a record entry corresponding to the particular peer device.

3. The method of claim 1 wherein the peer notification comprises a periodic ping to notify the RNS server that a peer device associated with the peer platform is currently available to serve peer resources stored at the associated peer device.

4. The method of claim 3 wherein the RNS server determines that the peer device is not currently available if the periodic ping is not received within a particular time interval after a previous peer notification from the peer platform.

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

storing an indication when the peer device is not currently available until a new peer notification is received indicating that the peer device is again available so that the RNS server will not service requests for resources stored on the peer device with a network location within the peer-to-peer networking environment for the peer device while the peer device is determined to be unavailable.

6. The method of claim 1 wherein the peer notification comprises a logout indicator to notify the RNS server that a peer device associated with the peer platform is no longer available to serve peer resources stored at the peer device.

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

storing an indication when the peer device is not currently available until a new peer notification is received indicating that the peer device is again available so that the RNS server will not service requests for resources stored on the peer device with a network location with the peer-to-peer networking environment for the peer device while the peer device is determined to be unavailable.

8. The method of claim 1 further comprising:

synchronizing a clock at the peer platform to a master clock to provide uniform version numbers for peer resources based on the master clock.

9. The method of claim 8 wherein the clock at the peer platform is synchronized at initial login and at periodic intervals thereafter.

10. A machine readable storage medium having stored thereon machine executable instructions that when executed by a processor and memory of a computing device implement a method, the method comprising:

receiving, via a network by the computing device a peer notification including a version number at a resource naming service (RNS) server included in a peer-to-peer networking environment comprising peer devices, the version number corresponding to a revision of a resource available via peer sharing in the peer-to-peer networking environment, the RNS server participating in a network of other RNS servers that receives from the peer devices resource lookup requests comprising resource names and that returns to the requesting peer devices indicia of one or more of the peer devices from which the named resources can be retrieved, where the RNS server forwards a resource lookup request to another RNS server if the RNS server is unable to answer the resource lookup request, said peer notification being received from a peer device included in the peer-to-peer networking environment through the peer-to-peer networking environment, the peer notification corresponding to an update by the peer device of the resource on the peer-to-peer networking environment; and

responsive to receiving the peer notification, updating, by the computing device, a record stored at the RNS server to include the version number in the peer notification, said record to enable the RNS server to service requests for the resource stored at a plurality of peer resources, the servicing comprising responding to the requests with network locations within the peer-to-peer networking environment of respective peer platforms determined to have a copy of the resource corresponding to the version number.

11. The machine readable storage medium of claim 10 wherein a network location within the peer-to-peer networking environment for a particular peer device is dynamically allocated by the computing device, wherein the peer notification comprises a current network address for the particular peer device, and wherein updating the record comprises:

storing at the computing device the current network address in a record entry corresponding to the particular peer device.

12. The machine readable storage medium of claim 10 wherein the peer notification comprises a periodic ping to notify the RNS server that a peer device associated with the peer platform is currently available to serve peer resources stored at the associated peer device.

13. The machine readable storage medium of claim 12 wherein the RNS server determines that the peer device is not currently available if the periodic ping is not received within a particular time interval after a previous peer notification from the peer platform.

14. The machine readable storage medium of claim 13 wherein updating the record comprises:

storing, by the computing device, an indication when the peer device is not currently available until a new peer notification is received indicating that the peer device is again available so that the RNS server will not service requests for resources stored on the peer device with a network location within the peer-to-peer networking environment for the peer device while the peer device is determined to be unavailable.

15. The machine readable storage medium of claim 10 wherein the peer notification comprises a logout indicator to notify the RNS server that a peer device associated with the peer platform is no longer available to serve peer resources stored at the peer device.

16. The machine readable storage medium of claim 15 wherein updating the record comprises:

storing at the computing device an indication when the peer device is not currently available until a new peer notification is received indicating that the peer device is again available so that the RNS server will not service requests for resources stored on the peer device with a network location peer-to-peer networking environment for the peer device while the peer device is determined to be unavailable.

17. The machine readable storage medium of claim 10, the method further comprising:

synchronizing a clock at the peer platform to a master clock to provide uniform version numbers for peer resources based on the master clock.

18. The machine readable storage medium of claim 17 wherein the clock at the peer platform is synchronized at initial login and at periodic intervals thereafter.

19. An apparatus comprising:

a resource naming service (RNS) server device comprising a processor and storage and included in a peer-to-peer networking environment to receive a peer notification including a new version number, said peer notification being received from a peer platform through the peer-to-peer networking environment, the peer notification having been initiated by a peer in the peer-to-peer networking environment when the peer updated the resource, the new version number corresponding to and identifying a new revision of the resource, where different version numbers of the resource correspond to different revisions of the resource, where the RNS server participates in a hierarchy of other RNS servers that cooperatively respond to resource lookup requests such that the RNS server forwards a resource lookup request to another RNS server if the RNS server is unable to answer with a peer location of the resource lookup request; and

a cache coupled to the RNS server device, said RNS server to update a record included in the cache based on the peer notification, said record to enable the RNS server to service requests for peer resources stored at a plurality of peer resources by responding with network locations within the peer-to-peer networking environment of respective peer devices in the peer-to-peer networking environment, wherein the RNS server responds to a request for the resource by identifying network locations that are storing a copy of the resource that corresponds to the version number.

20. A computer-implemented method performed by a resource name service (RNS) server, the method comprising:

participating in a hierarchy of other RNS servers that cooperatively store resource records that map resources to peers of a peer-to-peer network that are providing the resources and cooperatively respond to resource lookup requests such that the RNS server forwards a resource lookup request to another RNS server if the RNS server is unable to answer with a peer location of the resource lookup request, where a peer locates a resource by sending to an RNS server a request comprising a name of the resource and receiving in return, according to a corresponding resource record, indicia of one of the peers from which the resource is available;

receiving a notification from a first peer comprising a new version number of a first resource published by the first peer, the notification having been generated in response to the first peer updating the first resource, and updating at the RNS server a first resource record of the first resource to indicate the new version number, the first resource record mapping the first peer to the corresponding first resource, where different version numbers of the resource correspond to different revisions of the resource; and

when a resource lookup request for the first resource is received by the RNS server, the RNS server responds by querying the first peer for a current version number of the first resource and comparing the current version number to the version number of the first resource record to determine how to respond to the lookup request.