Peer name resolution protocol simple application program interface

• US 8,255,546 B2
• Filed: 09/30/2005
• Issued: 08/28/2012
• Est. Priority Date: 09/30/2005
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Horton, Noah, Thaler, David G., Lieuallen, Brian R., Parks, Upshur Warren III, Dewey, Jeremy L., Manion, Todd R., Senkeresty, Scott A.
• Primary Examiner(s): England, David
• Application Number:
  US11/241,393
• Publication Number:
  US 20070076630A1
• Time in Patent Office: 2,524 Days
• Field of Search: None
• US Class Current: 709/228
• CPC Class Codes: H04L 61/45 Network directories; Name-to-address mapping
• CPC Class Codes: H04L 67/104 Peer-to-peer [P2P] networks
• CPC Class Codes: H04L 67/1048 Departure or maintenance mechanisms
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services

Abstract

An application program interface (API) for sending and receiving endpoint registration data and peer-to-peer network cloud data has a registration call for adding endpoint data to a peer-to-peer network. The API may receive explicit data regarding address information or may be instructed to select and maintain suitable address information as the topology of the peer-to-peer network changes. Blocking and non-blocking calls are exposed for retrieving information peer-to-peer network endpoint data.

Claims

1. A computer-readable storage medium having computer-executable instructions for implementing a method of communicating data for a lifecycle support of participation in a peer-to-peer network, the method comprising:

processing a call that sends a notification message to one or more other nodes in a cloud regarding a change of a status of an endpoint in the peer-to-peer network;

processing a call for exchanging name registration data about at least one other endpoint in the peer-to-peer network; and

processing a call for reporting the name registration data about the at least one other endpoint in the peer-to-peer network or a null value;

the name registration data comprising;

a name of a cloud in which to register the name registration data and at least one of

a PeerPNRPAIILinkClouds or

a PeerPNRPGlobalCloud

request to register the name registration data in link local clouds or a global cloud respectively,

a data structure having at least one of a peer identifier,

a count of address/port pairs, an array of address/port pairs, and

a payload corresponding to the at least one other endpoint, and the null value comprising;

an indicator that no endpoint was found.

2. A computer-readable storage medium having computer-executable instructions of claim 1, processing the call for notifying the other nodes comprising:

receiving a call for distributing endpoint data having a plurality of call parameters comprising a peer_name; and

responding with a parameter comprising a registration handle associated with the endpoint.

3. A computer-readable storage medium having computer-executable instructions of claim 1, processing the call for notifying the other nodes comprising:

receiving a PeerPnrpRegister call having a plurality of call parameters comprising at least one of a peer_name, cloud data specifying one or more clouds, and one or more address/socket information pairs.

4. A computer-readable storage medium having computer-executable instructions of claim 1, processing the call for notifying the other nodes comprising:

receiving a call for changing registration data about an endpoint having a plurality of call parameters comprising at least one of a registration handle associated with the endpoint and an updated registration data, the updated registration data comprising at least one of cloud data specifying one or more clouds, and one or more address/socket information pairs.

5. A computer-readable storage medium having computer-executable instructions of claim 1, processing the call for notifying the other nodes comprising:

receiving a call for removing registration data associated with an endpoint having a call parameter comprising a registration handle associated with a peer name.

6. A computer-readable storage medium having computer-executable instructions of claim 1, processing the call for exchanging name registration data comprising:

receiving a request for gathering endpoint information in a blocking manner having a plurality of call parameters comprising at least one of a peer_name, a cloud name, and a maximum number of results to return; and

responding with endpoint information about zero or more instances of endpoints.

7. A computer-readable storage medium having computer-executable instructions of claim 1, processing the call for exchanging name registration data comprising:

receiving a request for gathering endpoint information in a non-blocking manner having a plurality of call parameters comprising at least one of a peer_name, a cloud name, and a maximum number of results to return.

8. A computer-readable storage medium having computer-executable instructions of claim 7, comprising returning a result by at least one of a callback and a signal having an event handle.

9. A computer-readable storage medium having computer-executable instructions of claim 1, processing the call for exchanging name registration data comprising:

receiving a request for halting an in-process resolve request having one or more call parameters comprising at least an event handle associated with the in-process resolve request.

10. A computer-readable storage medium having computer-executable instructions of claim 1, processing the call for reporting the name registration data comprising:

receiving a request for receiving data corresponding to results of a prior resolve request having at least a call parameter comprising an event handle associated with the prior resolve request, the event handle pointing to a data structure having information about zero or more other endpoints, the data structure having entries corresponding to zero or more peer identifiers of the zero or more other endpoints, a number of address/port pairs associated with the zero or more other endpoints, a byte count of the payload, and a payload of information for the zero or more other endpoints.

11. A method of communicating between a requesting process and a serving process supporting communication in a peer-to-peer network comprising:

processing a call for exchanging data between a first endpoint and at least one other entity in the peer-to-peer network, with the at least one other entity being at least one of a member of a cloud and another endpoint;

processing a call for reporting the data about the at least one other endpoint in the peer-to-peer network; and

processing a call for registering one or more addresses based at least in part on a PeerPNRPAutoAddresses request comprising picking one or more values for the addresses to register, registering the addresses with one or more new clouds, and updating concurrently with an address change on a local machine.

12. The method of claim 11, processing the call for exchanging data comprising:

issuing a PeerPnrpGetCloudInfo call to retrieve one or more cloud names;

receiving the PeerPnrpGetCloudInfo call; and

issuing a response comprising a number of cloud names returned and information corresponding to the respective returned cloud names.

13. The method of claim 11, processing the call for exchanging data comprising:

issuing a PeerPnrpResolve request comprising at least one of a peer_name, a cloud name, and a maximum number of results to return;

receiving the PeerPnrpResolve request and processing the request in a blocking manner; and

issuing a response comprising an event handle for signaling availability of results and for use in retrieving the results.

14. The method of claim 11, processing the call for exchanging data comprising:

issuing a PeerPnrpStartResolve request comprising at least one of a peer_name, a cloud name, and a maximum number of results to return;

receiving the PeerPnrpStartResolve request and processing the request in a non-blocking manner; and

issuing a response comprising an event handle for signaling availability of results and for use in retrieving the results.

15. The method of claim 11, processing the call for exchanging data comprising:

issuing a PeerPnrpRegister call to add endpoint data to at least one associated cloud, the PeerPnrpRegister call comprising a peer_name;

receiving the PeerPnrpRegister call and sending data about the first endpoint and the peer_name to zero or more other entities; and

issuing a response to the requesting process comprising a registration handle associated with the endpoint data.

16. The method of claim 15, comprising issuing, by the requesting process, a second PeerPnrpRegister call, comprising:

issuing the second PeerPnrpRegister call to add endpoint data to at least one associated cloud, the second PeerPnrpRegister call comprising a peer_name and at least one registration parameter, the registration parameter comprising at least one of a cloud name, a count of addresses to publish, an array of address/socket pairs, a port for an automatically selected address, a comment field, or a payload of information corresponding to a registration.

17. The method of claim 11, processing the call for exchanging data comprising:

issuing a PeerPnrpUpdateRegistration call to update endpoint data in at least a portion of the peer-to-peer network, the PeerPnrpUpdateRegistration call comprising a peer_name and updated endpoint data; and

receiving the PeerPnrpUpdateRegistration call and sending data comprising the peer_name and updated endpoint data to at least one surrounding entity.

18. A computer adapted for participation in a peer-to-peer network comprising:

a network communication device for exchanging data via a network;

a memory storing machine-readable instructions; and

a processor for executing the machine-readable instructions that when executed perform a method comprising;

performing at least one of a synchronous blocking resolve or an asynchronous non-blocking resolve based at least in part on a name to be resolved, a cloud name to perform the resolve, a specified number of results, a cancelling handle, and a maximum number of endpoints to return;

processing a call for registering a peer-to-peer network endpoint, the call having a peer name and a single attribute predefined value; and

selecting a valid address to register with the peer-to-peer network.

19. The computer of claim 18, the memory storing instructions for performing the method comprising:

automatically updating the valid address when a host machine address changes.

20. The computer of claim 18, the memory storing instructions for performing the method comprising:

automatically updating the valid address in a new cloud when the new cloud is discovered.