US8255546B2 - Peer name resolution protocol simple application program interface - Google Patents
Peer name resolution protocol simple application program interface Download PDFInfo
- Publication number
- US8255546B2 US8255546B2 US11/241,393 US24139305A US8255546B2 US 8255546 B2 US8255546 B2 US 8255546B2 US 24139305 A US24139305 A US 24139305A US 8255546 B2 US8255546 B2 US 8255546B2
- Authority
- US
- United States
- Prior art keywords
- call
- peer
- data
- name
- endpoint
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related, expires
Links
- 230000000903 blocking effect Effects 0.000 claims abstract description 18
- 238000000034 method Methods 0.000 claims description 41
- 238000012545 processing Methods 0.000 claims description 26
- 238000004891 communication Methods 0.000 claims description 16
- 230000008569 process Effects 0.000 claims description 12
- 230000008859 change Effects 0.000 claims description 5
- 230000001360 synchronised effect Effects 0.000 claims description 4
- 230000004044 response Effects 0.000 claims 4
- 230000011664 signaling Effects 0.000 claims 2
- 238000005516 engineering process Methods 0.000 description 7
- 230000006855 networking Effects 0.000 description 7
- 230000003287 optical effect Effects 0.000 description 5
- 239000008186 active pharmaceutical agent Substances 0.000 description 4
- 238000010586 diagram Methods 0.000 description 4
- 230000002093 peripheral effect Effects 0.000 description 4
- 238000011161 development Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 230000005055 memory storage Effects 0.000 description 2
- 239000007787 solid Substances 0.000 description 2
- 230000007723 transport mechanism Effects 0.000 description 2
- 239000011800 void material Substances 0.000 description 2
- CDFKCKUONRRKJD-UHFFFAOYSA-N 1-(3-chlorophenoxy)-3-[2-[[3-(3-chlorophenoxy)-2-hydroxypropyl]amino]ethylamino]propan-2-ol;methanesulfonic acid Chemical compound CS(O)(=O)=O.CS(O)(=O)=O.C=1C=CC(Cl)=CC=1OCC(O)CNCCNCC(O)COC1=CC=CC(Cl)=C1 CDFKCKUONRRKJD-UHFFFAOYSA-N 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 230000000644 propagated effect Effects 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/104—Peer-to-peer [P2P] networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/104—Peer-to-peer [P2P] networks
- H04L67/1044—Group management mechanisms
- H04L67/1048—Departure or maintenance mechanisms
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
Definitions
- Peer-to-peer networking offers users many opportunities for collaboration and sharing by connecting computers associated by geography or network characteristics. The chance to offer and discover services, files, data, and programmatic offerings increases flexibility and utilization of computing resources.
- a peer-to-peer network may include similar groupings of computers in clusters known as clouds. Clouds may be identified by their scope or by other attributes such as a department it is associated with. Multiple clouds may exist within a given company or organizational entity. Offerings available on the peer-to-peer network are known as endpoints. Endpoints may be computers, files, or programs. However, endpoints may also include services that are available at more than one physical location on the peer-to-peer network, that is, a service may have multiple Internet Protocol addresses and/or IP ports.
- PNRP peer Name Resolution Protocol
- API application program interface
- Winsock Namespace Provider API The GetAddrInfo API is relatively simple but does not make available all the functionality of PNRP.
- the NamespaceProvider API supports all the features of PNRP but has been found cumbersome and difficult to use by some developers. Beyond the coding challenges, the prior art APIs increased the difficulty of debugging systems incorporating PNRP. The adoption of PNRP and subsequently, the robust features available through PNRP for peer-to-peer networking, has been hampered by the difficulty of using the APIs currently available.
- the Simple PNRP API exposes all the functions available in PNRP while simplifying the programming and management overhead associated with building and maintaining peer-to-peer networks.
- the discovery calls may be blocking or non-blocking.
- the use of these simplified calls is expected to increase the utilization of PNRP by streamlining both the development and use of PNRP for peer-to-peer networks.
- the Simple PNRP APIs greatly eases the developer's burden for coding PNRP interfaces and simplifies the debugging process during development and testing.
- the Simple PNRP APIs are expected to significantly advance the adoption of PNRP and, through that, the adoption of peer-to-peer networking in an increasing number of consumer, commercial, and business applications.
- FIG. 1 is a simplified and representative block diagram of a computer network
- FIG. 2 is a block diagram of a computer that may be connected to the network of FIG. 1 ;
- FIG. 3 is a simplified and representative block diagram of a peer-to-peer network
- FIG. 4 is a simplified and representative block diagram of a peer-to-peer network.
- FIGS. 1 and 2 provide a structural basis for the network and computational platforms related to the instant disclosure.
- FIG. 1 illustrates a network 10 .
- the network 10 may be the Internet, a virtual private network (VPN), or any other network that allows one or more computers, communication devices, databases, etc., to be communicatively connected to each other.
- the network 10 may be connected to a personal computer 12 , and a computer terminal 14 via an Ethernet 16 and a router 18 , and a landline 20 .
- the Ethernet 16 may be a subnet of a larger Internet Protocol network.
- Other networked resources such as projectors or printers (not depicted), may also be supported via the Ethernet 16 or another data network.
- the network 10 may be wirelessly connected to a laptop computer 22 and a personal data assistant 24 via a wireless communication station 26 and a wireless link 28 .
- a server 30 may be connected to the network 10 using a communication link 32 and a mainframe 34 may be connected to the network 10 using another communication link 36 .
- the network 10 may be useful for supporting peer-to-peer network traffic.
- FIG. 2 illustrates a computing device in the form of a computer 110 .
- Components of the computer 110 may include, but are not limited to a processing unit 120 , a system memory 130 , and a system bus 121 that couples various system components including the system memory to the processing unit 120 .
- the system bus 121 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures.
- bus architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus also known as Mezzanine bus.
- ISA Industry Standard Architecture
- MCA Micro Channel Architecture
- EISA Enhanced ISA
- VESA Video Electronics Standards Association
- PCI Peripheral Component Interconnect
- Computer 110 typically includes a variety of computer readable media.
- Computer readable media can be any available media that can be accessed by computer 110 and includes both volatile and nonvolatile media, removable and non-removable media.
- Computer readable media may comprise computer storage media and communication media.
- Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data.
- Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, FLASH memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by computer 110 .
- Communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media.
- modulated data signal means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal.
- communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, radio frequency, infrared and other wireless media. Combinations of any of the above should also be included within the scope of computer readable media.
- the system memory 130 includes computer storage media in the form of volatile and/or nonvolatile memory such as read only memory (ROM) 131 and random access memory (RAM) 132 .
- ROM read only memory
- RAM random access memory
- BIOS basic input/output system
- RAM 132 typically contains data and/or program modules that are immediately accessible to and/or presently being operated on by processing unit 120 .
- FIG. 2 illustrates operating system 134 , application programs 135 , other program modules 136 , and program data 137 .
- the computer 110 may also include other removable/non-removable, volatile/nonvolatile computer storage media.
- FIG. 2 illustrates a hard disk drive 141 that reads from or writes to non-removable, nonvolatile magnetic media, a magnetic disk drive 151 that reads from or writes to a removable, nonvolatile magnetic disk 152 , and an optical disk drive 155 that reads from or writes to a removable, nonvolatile optical disk 156 such as a CD ROM or other optical media.
- removable/non-removable, volatile/nonvolatile computer storage media that can be used in the exemplary operating environment include, but are not limited to, magnetic tape cassettes, flash memory cards, digital versatile disks, digital video tape, solid state RAM, solid state ROM, and the like.
- the hard disk drive 141 is typically connected to the system bus 121 through a non-removable memory interface such as interface 140
- magnetic disk drive 151 and optical disk drive 155 are typically connected to the system bus 121 by a removable memory interface, such as interface 150 .
- hard disk drive 141 is illustrated as storing operating system 144 , application programs 145 , other program modules 146 , and program data 147 . Note that these components can either be the same as or different from operating system 134 , application programs 135 , other program modules 136 , and program data 137 . Operating system 144 , application programs 145 , other program modules 146 , and program data 147 are given different numbers here to illustrate that, at a minimum, they are different copies.
- a user may enter commands and information into the computer 20 through input devices such as a keyboard 162 and cursor control device 161 , commonly referred to as a mouse, trackball, or touch pad.
- a camera 163 such as web camera (webcam), may capture and input pictures of an environment associated with the computer 110 , such as providing pictures of users. The webcam 163 may capture pictures on demand, for example, when instructed by a user, or may take pictures periodically under the control of the computer 110 .
- Other input devices may include a microphone, joystick, game pad, satellite dish, scanner, or the like.
- a monitor 191 or other type of display device is also connected to the system bus 121 via an interface, such as a graphics controller 190 .
- computers may also include other peripheral output devices such as speakers 197 and printer 196 , which may be connected through an output peripheral interface 195 .
- the computer 110 may operate in a networked environment using logical connections to one or more remote computers, such as a remote computer 180 .
- the remote computer 180 may be a personal computer, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to the computer 110 , although only a memory storage device 181 has been illustrated in FIG. 2 .
- the logical connections depicted in FIG. 2 include a local area network (LAN) 171 and a wide area network (WAN) 173 , but may also include other networks.
- LAN local area network
- WAN wide area network
- Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets and the Internet.
- the computer 110 When used in a LAN networking environment, the computer 110 is connected to the LAN 171 through a network interface or adapter 170 .
- the computer 110 When used in a WAN networking environment, the computer 110 typically includes a modem 172 or other means for establishing communications over the WAN 173 , such as the Internet.
- the modem 172 which may be internal or external, may be connected to the system bus 121 via the input interface 160 , or other appropriate mechanism.
- program modules depicted relative to the computer 110 may be stored in the remote memory storage device.
- FIG. 2 illustrates remote application programs 185 as residing on memory device 181 .
- the communications connections 170 172 allow the device to communicate with other devices.
- the communications connections 170 172 are an example of communication media.
- the communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media.
- a “modulated data signal” may be a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal.
- communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.
- Computer readable media may include both storage media and communication media.
- FIG. 3 depicts an exemplary peer-to-peer network, that may be similar to or coupled to the network 10 of FIG. 1 .
- a peer-to-peer network 200 may have individual clouds 202 204 206 coupled by networks 208 210 212 .
- the networks may be wired or wireless and may support Internet protocol version 6 (IPv6).
- Cloud 202 may have computers 214 216 .
- Each computer may support multiple endpoints, for example, computer 216 is shown supporting endpoint 1 218 and endpoint 2 220 .
- Cloud 204 is shown having computers 222 and 224 .
- Computer 224 is shown supporting three endpoints 226 228 and 230 .
- Cloud 206 is shown having computers 232 and 234 .
- the computers of cloud 206 are not shown supporting any endpoints.
- each computer and its associated endpoints are shown within their respective clouds 202 204 206 , indicating perhaps organization by network topology.
- Each of the endpoints 218 220 226 228 230 may be processes, files, IP addresses, and the like. Each endpoint must be explicitly registered in order to be discovered on the peer-to-peer network 200 , within their respective clouds. For example, when one endpoint 218 wishes to register in cloud 202 it may use the PeerPNRPRegister call documented below. The PeerPNRPRegister call may be restricted to its own link-local cloud 202 . Similarly, an endpoint in cloud 204 , for example, endpoint 230 , may register locally in cloud 204 The PeerPNRPUpdateRegistration call may be used when data about the endpoint has changed, for example, an IP address.
- PeerPNRPUnregister call When an endpoint wishes to remove itself from the peer-to-peer network a PeerPNRPUnregister call may be issued.
- the methods by which peer-to-peer network registration information is propagated through a peer-to-peer network are known and well documented and are not discussed further here.
- FIG. 4 represents a more complex embodiment of peer-to-peer networking.
- the peer-to-peer network 300 has clouds 302 , 304 and 306 .
- the clouds may be coupled by respective network connections 308 , 310 , and 312 .
- Computer 314 in cloud 302 may have one or more endpoints (not depicted).
- Computer 316 is outside any cloud but has endpoint 1 322 in cloud 302 and endpoint 2 324 in cloud 304 .
- the computer 316 configured in this manner may be attached to different points in a topologically organized network and may be able to publish different endpoints in different networks.
- Computer 318 is shown in cloud 306 while computer 320 is shown configured in both clouds 304 and 306 .
- the computer 320 may be a logical member of both clouds 304 and 306 . It may publish the endpoint 326 in both clouds simultaneously.
- a handle may be returned for use in future calls regarding a particular endpoint having that handle.
- Any call that returns endpoint data may return a null set, in other words, no data. This may be the case when the name registration data for a cloud or endpoint cannot be matched to an existing entity. In this case, the return with no data is significant and useful.
- PeerPnrpRegister This method is used to register a PNRP endpoint. The infrastructure will pick addresses in all clouds to register, and watch for address change events, re-registering as necessary.
- pcwzPeerName to register pRegInfo
- NULL will register all addresses in all clouds. See Notes. phRegistration Handle for the registration allowing for updates and unregistration.
- peer_pnrp_register_info_tag ⁇ PWSTR pwzCloudName; ULONG cAddresses; SOCKADDR **ppAddresses; WORD wPort; PWSTR pwzComment; ULONG cbPayload; PBYTE pbPayload; ⁇ PEER_PNRP_REGISTER_INFO, *PPEER_PNRP_REGISTER_INFO;
- the PEER_PNRP_REGISTER_INFO provides additional information on how registrations should be performed.
- the simple mode for the API is passing null for this argument.
- Complex settings are accessed by actually using the structure.
- pcwzCloudName Name of the cloud in which to register the peername, typically retrieved via PeerPnrpGetCloudInfo. Also understands the following special values: * NULL: the peername will be registered in all clouds. * PEER_PNRP_ALL_LINK_CLOUDS: the peername will be registered in all link local clouds * PEER_PNRP_GLOBAL_CLOUD: the peername will only be registered in the global cloud. cAddresses Count of the number of addresses to be published. Max is 4. The value may be 0, only if a payload is specified. cAddress may also be the special value PEER_PNRP_AUTO_ADDDRESSES, which will cause the infrastructure to automatically choose good addresses for each specified cloud.
- ppAddresses Array of address/socket information that will be published with the name.
- cbPayload The byte count of the payload.
- pbPayload The payload information for the registration. Required if cAddress equals 0.
- the pRegInfo in the call to PeerPnrpRegister may be NULL. This is equivalent to passing a PEER_PNRP_REGISTER_INFO with following values:
- PeerPnrpUpdateRegistration This method is used to update a registration of a PNRP endpoint.
- the updated registration info Not all things about a registration may be changed. Specifically, the cloudname may not be changed, and cAddresses can not change between auto-selected addresses and specified addresses.
- the updated registration data may include data specifying one or more clouds and data about one or more address/socket information pairs, although for a given pair, the address or socket information may be null.
- PeerPnrpUnregister This method removes a PNRP endpoint registration
- a participant in the peer-to-peer network 200 may wish to gather information about resources available on the peer-to-peer network, for example, other endpoints.
- the Simple PNRP API supports several calls for determining information about clouds and other endpoints. Cloud information may be returned by issuing a PeerPnrpGetCloud info call, as documented below.
- PeerPnrpGetCloudInfo This method will retrieve all cloud names.
- pcNumClouds The number of cloud names pointed to by ppwzCloudNames ppCloudInfo The cloud information. This param must be freed via PeerFreeData.
- peer_pnrp_cloud_info_tag ⁇ WCHAR wzCloudName[MAX_CLOUD_NAME]; DWORD dwScope; DWORD dwScopeId; ⁇ PEER_PNRP_CLOUD_INFO, *PPEER_PNRP_CLOUD_INFO;
- the first initiates processes associated with retrieving endpoints from peernames and associated data in a synchronous (blocking) manner and returns results when the resolve process is completed.
- a second option resolves endpoints in a two step process.
- the first step initiates the data gathering in an asynchronous (non-blocking) manner. In most cases, this asynchronous method may offer more utility by allowing other activities, including other peer-to-peer network activities to take place in parallel.
- the second step involves retrieving the specific endpoint data accumulated during the non-blocking resolve step.
- PeerPnrpResolve This method performs a synchronous (blocking) resolve.
- pcwzPeerName The name to be resolved.
- pcwzCloudName The cloudname to perform the resolve. If NULL, resolves will be performed in all clouds. If PEER_PNRP_ALL_LINK_CLOUDS, resolves in all link local clouds. If PEER_PNRP_GLOBAL_CLOUD, resolve will only take place in the global cloud pcEndpoints On input, specifies the desired number of results. On output, specifies the actual number pointed to by ppEndpointInfo. Max is 500. ppEndPointInfo Returns an array of the resultant PNRP_ENDPOINT_INFO information. Must be freed by a call to PeerFreeData. For non-blocking functionality, use PeerPnrpStartResolve. To use a specific timeout, use the asynchronous version. If CloudName is null and the resolve is conducted in all clouds, then resolves will be issued in each cloud simultaneously. The method will return as soon as it has received enough results from any combination of clouds.
- the asynchronous (non-blocking) call and the related calls for stopping the resolve process and retrieving results when available are documented below.
- PeerPnrpStartResolve This method performs an asynchronous (non-blocking) resolve. This is the recommended way of performing resolves, especially if multiple endpoints are desired.
- pcwzPeerName The name to be resolved.
- pcwzCloudName The cloud name to perform the resolve. If NULL, resolves will be performed in all clouds.
- cMaxEndpoints The maximum number of endpoints to return to the caller hEvent An event handle to signal when new resolves are ready for consumption by calling PeerPnrpGetEndpoint phResolve Handle which can be used to cancel the resolve via PeerPnrpStopResolve As results are found, the hEvent gets signaled. The application may then call PeerPnrpGetEndpoint to retrieve the resolved Endpoint(s). In another embodiment, results may be returned via a callback to the requesting process.
- PeerPnrpStopResolve This method will cancel an in-progress resolve from a call to PeerPnrpStartResolve.
- PeerPnrpGetEndpoint This method is used to retrieve endpoints from a previous call to PeerPnrpStartResolve.
- PEER_E_PENDING The api was called before a resolve was ready PEER_E_NO_MORE No more endpoints are available, this resolve is complete. This method is part of the asynchronous resolve PnrpAPIs that also include PeerPnrpStartResolve and PeerPnrpStopResolve.
- PeerPnrpEndpointInfo The main data structure used to contain a PNRP Endpoint.
- peer_pnrp_endpoint_info_tag ⁇ PWSTR pwzPeerId; ULONG cAddresses; PSOCKADDR * ppAddresses; ULONG cbPayload; PVOID pPayload; ⁇ PEER_PNRP_ENDPOINT_INFO, *PPEER_PNRP_ENDPOINT_INFO; Elements
- pwzPeerId The complete Peer ID of the Endpoint.
- cAddresses Number of address/port pairs associated with the Endpoint.
- pAddresses Array of address/port information that will be published with the name cbPayload
- cbPayload The byte count of the payload pPayload The payload information for the registration.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Mathematical Physics (AREA)
- Theoretical Computer Science (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Computer And Data Communications (AREA)
- Information Transfer Between Computers (AREA)
Abstract
Description
HRESULT WINAPI PeerPnrpRegister( |
IN | PCWSTR | pcwzPeerName, |
IN | PPEER_PNRP_REGISTRATION_INFO | pRegistrationInfo, |
OUT | PHANDLE | phRegistration |
); | ||
Arguments
pcwzPeerName | Name to register |
pRegInfo | Optional information about the registration. NULL will |
register all addresses in all clouds. See Notes. | |
phRegistration | Handle for the registration allowing for updates and |
unregistration. | |
typedef struct peer_pnrp_register_info_tag { |
PWSTR | pwzCloudName; | |
ULONG | cAddresses; | |
SOCKADDR | **ppAddresses; | |
WORD | wPort; | |
PWSTR | pwzComment; | |
ULONG | cbPayload; | |
PBYTE | pbPayload; |
} PEER_PNRP_REGISTER_INFO, | ||
*PPEER_PNRP_REGISTER_INFO; | ||
pcwzCloudName | Name of the cloud in which to register the peername, typically retrieved via PeerPnrpGetCloudInfo. |
Also understands the following special values: | |
* NULL: the peername will be registered in all clouds. | |
* PEER_PNRP_ALL_LINK_CLOUDS: the peername will be registered in all link local clouds | |
* PEER_PNRP_GLOBAL_CLOUD: the peername will only be registered in the global cloud. | |
cAddresses | Count of the number of addresses to be published. Max is 4. The value may be 0, only if a payload is |
specified. cAddress may also be the special value PEER_PNRP_AUTO_ADDDRESSES, which will | |
cause the infrastructure to automatically choose good addresses for each specified cloud. | |
ppAddresses | Array of address/socket information that will be published with the name. |
wPort | Only used when cAddress equals PEER_PNRP_AUTO_ADDRESSES. Specifies which port to |
publish with the address chosen by our api. See further notes below. | |
pcwzComment | Comment field string for inclusion in CPA. |
cbPayload | The byte count of the payload. |
pbPayload | The payload information for the registration. Required if cAddress equals 0. |
The pRegInfo in the call to PeerPnrpRegister may be NULL. This is equivalent to passing a PEER_PNRP_REGISTER_INFO with following values:
pwzCloudName | NULL (All clouds) | ||
cAddresses | PEER_PNRP_AUTO_ADDRESSES | ||
ppAddresses | NULL | ||
wPort | 0 | ||
pwzComment | NULL | ||
cbPayload | 0 | ||
pbPayload | NULL | ||
HRESULT WINAPI PeerPnrpUpdateRegistration( | ||
IN HANDLE hRegistration, | ||
IN PPEER_PNRP_REGISTRATION_INFO pRegistrationInfo); | ||
Arguments
hRegistration | Handle to the registration from PeerPnrpRegister | ||
pRegInfo | the updated registration info | ||
Not all things about a registration may be changed. Specifically, the cloudname may not be changed, and cAddresses can not change between auto-selected addresses and specified addresses. The updated registration data may include data specifying one or more clouds and data about one or more address/socket information pairs, although for a given pair, the address or socket information may be null.
VOID WINAPI PeerPnrpUnregister( | ||
IN HANDLE hRegistration | ||
); | ||
Arguments:
phRegistration | Handle to the registration from PeerPnrpRegister |
HRESULT WINAPI PeerPnrpGetCloudInfo( | ||
ULONG *pcNumClouds, | ||
PPEER_PNRP_CLOUD_INFO *ppCloudInfo | ||
); | ||
Arguments
pcNumClouds | The number of cloud names pointed to by |
ppwzCloudNames | |
ppCloudInfo | The cloud information. This param must be freed via |
PeerFreeData. | |
typedef struct peer_pnrp_cloud_info_tag |
{ |
WCHAR | wzCloudName[MAX_CLOUD_NAME]; |
DWORD | dwScope; |
DWORD | dwScopeId; |
} PEER_PNRP_CLOUD_INFO, *PPEER_PNRP_CLOUD_INFO; |
HRESULT WINAPI PeerPnrpResolve( |
IN PCWSTR | pcwzPeerName, | |
IN PCWSTR | pcwzCloudName OPTIONAL, | |
IN OUT ULONG | *pcEndpoints, |
OUT PPEER_PNRP_ENDPOINT_INFO *ppEndPointInfo | ||
); | ||
Arguments
pcwzPeerName | The name to be resolved. |
pcwzCloudName | The cloudname to perform the resolve. If NULL, |
resolves will be performed in all clouds. If | |
PEER_PNRP_ALL_LINK_CLOUDS, | |
resolves in all link local clouds. If | |
PEER_PNRP_GLOBAL_CLOUD, | |
resolve will only take place in the global cloud | |
pcEndpoints | On input, specifies the desired number of results. |
On output, specifies the actual number pointed to by | |
ppEndpointInfo. Max is 500. | |
ppEndPointInfo | Returns an array of the resultant |
PNRP_ENDPOINT_INFO | |
information. Must be freed by a call to PeerFreeData. | |
For non-blocking functionality, use PeerPnrpStartResolve. To use a specific timeout, use the asynchronous version.
If CloudName is null and the resolve is conducted in all clouds, then resolves will be issued in each cloud simultaneously. The method will return as soon as it has received enough results from any combination of clouds.
HRESULT WINAPI PeerPnrpStartResolve( |
IN | PCWSTR | pcwzPeerName, | ||
IN | PCWSTR | pcwzCloudName, | ||
IN | ULONG | cMaxEndpoints, | ||
IN | HANDLE | hEvent, | ||
OUT | PHANDLE | phResolve, | ||
); | ||||
Arguments
pcwzPeerName | The name to be resolved. |
pcwzCloudName | The cloud name to perform the resolve. If NULL, |
resolves will be performed in all clouds. | |
cMaxEndpoints | The maximum number of endpoints to return to the |
caller | |
hEvent | An event handle to signal when new resolves are ready |
for consumption by calling PeerPnrpGetEndpoint | |
phResolve | Handle which can be used to cancel the resolve |
via PeerPnrpStopResolve | |
As results are found, the hEvent gets signaled. The application may then call PeerPnrpGetEndpoint to retrieve the resolved Endpoint(s). In another embodiment, results may be returned via a callback to the requesting process.
VOID WINAPI PeerPnrpStopResolve( | ||
IN HANDLE hResolve | ||
); | ||
Arguments
hResolve | The resolve handle from PeerPnrpStartResolve | ||
HRESULT WINAPI PeerPnrpGetEndpoint( |
IN | HANDLE hResolve, | ||
OUT | PPEER_PNRP_ENDPOINT_INFO *pEndpoint | ||
); | |||
Arguments
hResolve | The resolve handle from PeerPnrpStartResolve | ||
pEndpoint | A single Endpoint which was resolvedas a | ||
PeerPnrpEndpointInfo struct | |||
Errors
PEER_E_PENDING | The api was called before a resolve was ready |
PEER_E_NO_MORE | No more endpoints are available, |
this resolve is complete. | |
This method is part of the asynchronous resolve PnrpAPIs that also include PeerPnrpStartResolve and PeerPnrpStopResolve.
typedef struct peer_pnrp_endpoint_info_tag { |
PWSTR | pwzPeerId; | |
ULONG | cAddresses; |
PSOCKADDR | * | ppAddresses; |
ULONG | cbPayload; | |
PVOID | pPayload; |
} PEER_PNRP_ENDPOINT_INFO, | ||
*PPEER_PNRP_ENDPOINT_INFO; | ||
Elements
pwzPeerId | The complete Peer ID of the Endpoint. |
cAddresses | Number of address/port pairs associated with the Endpoint. |
pAddresses | Array of address/port information that will be |
published with the name | |
cbPayload | The byte count of the payload |
pPayload | The payload information for the registration. |
Claims (20)
Priority Applications (11)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/241,393 US8255546B2 (en) | 2005-09-30 | 2005-09-30 | Peer name resolution protocol simple application program interface |
PCT/US2006/038627 WO2007041580A1 (en) | 2005-09-30 | 2006-10-02 | Peer name resolution protocol simple application program interface |
CA002623861A CA2623861A1 (en) | 2005-09-30 | 2006-10-02 | Peer name resolution protocol simple application program interface |
CNA2006800363494A CN101278274A (en) | 2005-09-30 | 2006-10-02 | Peer name resolution protocol simple application program interface |
BRPI0616488-9A BRPI0616488A2 (en) | 2005-09-30 | 2006-10-02 | Simple Point Name Resolution Protocol Application Programming Interface |
EP06816114A EP1934788A1 (en) | 2005-09-30 | 2006-10-02 | Peer name resolution protocol simple application program interface |
AU2006299461A AU2006299461A1 (en) | 2005-09-30 | 2006-10-02 | Peer name resolution protocol simple application program interface |
KR1020087007110A KR20080063282A (en) | 2005-09-30 | 2006-10-02 | Peer name resolution protocol simple application program interface |
JP2008533777A JP2009510638A (en) | 2005-09-30 | 2006-10-02 | Simple application program interface for peer name resolution protocol |
RU2008112155/09A RU2008112155A (en) | 2005-09-30 | 2006-10-02 | SINGLE-PEOPLE PROTOCOL OF RESOLUTION OF NAMES OF SIMPLE INTERFACE OF APPLICATION PROGRAM |
NO20081331A NO20081331L (en) | 2005-09-30 | 2008-03-13 | Simple user programs Interface for the resolution protocol for names of peer-to-peer computers |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/241,393 US8255546B2 (en) | 2005-09-30 | 2005-09-30 | Peer name resolution protocol simple application program interface |
Publications (2)
Publication Number | Publication Date |
---|---|
US20070076630A1 US20070076630A1 (en) | 2007-04-05 |
US8255546B2 true US8255546B2 (en) | 2012-08-28 |
Family
ID=37901820
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/241,393 Expired - Fee Related US8255546B2 (en) | 2005-09-30 | 2005-09-30 | Peer name resolution protocol simple application program interface |
Country Status (11)
Country | Link |
---|---|
US (1) | US8255546B2 (en) |
EP (1) | EP1934788A1 (en) |
JP (1) | JP2009510638A (en) |
KR (1) | KR20080063282A (en) |
CN (1) | CN101278274A (en) |
AU (1) | AU2006299461A1 (en) |
BR (1) | BRPI0616488A2 (en) |
CA (1) | CA2623861A1 (en) |
NO (1) | NO20081331L (en) |
RU (1) | RU2008112155A (en) |
WO (1) | WO2007041580A1 (en) |
Families Citing this family (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8255546B2 (en) * | 2005-09-30 | 2012-08-28 | Microsoft Corporation | Peer name resolution protocol simple application program interface |
US20090282155A1 (en) * | 2008-05-09 | 2009-11-12 | Mavenir Systems, Inc. | Providing peer-to-peer media |
US8532108B2 (en) * | 2009-09-30 | 2013-09-10 | Alcatel Lucent | Layer 2 seamless site extension of enterprises in cloud computing |
US8924569B2 (en) * | 2009-12-17 | 2014-12-30 | Intel Corporation | Cloud federation as a service |
US9106675B2 (en) * | 2010-06-17 | 2015-08-11 | International Business Machines Corporation | Intelligent network storage planning within a clustered computing environment |
US9356964B2 (en) * | 2012-11-02 | 2016-05-31 | Aruba Networks, Inc. | Application based policy enforcement |
EP3226493B1 (en) | 2015-12-21 | 2020-03-25 | Huawei Technologies Co., Ltd. | Method, device, and system for discovering the relationship of applied topology |
CN108616572A (en) * | 2018-03-29 | 2018-10-02 | 阿里巴巴集团控股有限公司 | Communication means, device and equipment |
Citations (55)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5586264A (en) * | 1994-09-08 | 1996-12-17 | Ibm Corporation | Video optimized media streamer with cache management |
US5987376A (en) * | 1997-07-16 | 1999-11-16 | Microsoft Corporation | System and method for the distribution and synchronization of data and state information between clients in a distributed processing system |
US6205481B1 (en) * | 1998-03-17 | 2001-03-20 | Infolibria, Inc. | Protocol for distributing fresh content among networked cache servers |
US6252884B1 (en) | 1998-03-20 | 2001-06-26 | Ncr Corporation | Dynamic configuration of wireless networks |
US6269099B1 (en) * | 1998-07-01 | 2001-07-31 | 3Com Corporation | Protocol and method for peer network device discovery |
US20020027569A1 (en) | 2000-08-22 | 2002-03-07 | Microsoft Corporation | Generic user control point tool for universal plug and play (UPnP) devices |
US20020075900A1 (en) * | 2000-12-18 | 2002-06-20 | Klaus Turina | Signaling transport protocol extensions for load balancing and server pool support |
US20020112058A1 (en) | 2000-12-01 | 2002-08-15 | Microsoft Corporation | Peer networking host framework and hosting API |
US20020143989A1 (en) * | 2001-04-02 | 2002-10-03 | Microsoft Corporation | Peer-to-peer name resolution protocol (PNRP) and multilevel cache for use therewith |
US20020156875A1 (en) * | 2001-04-24 | 2002-10-24 | Kuldipsingh Pabla | Peer group name server |
US20030041141A1 (en) * | 2001-01-22 | 2003-02-27 | Abdelaziz Mohamed M. | Peer-to-peer presence detection |
US20030055892A1 (en) * | 2001-09-19 | 2003-03-20 | Microsoft Corporation | Peer-to-peer group management and method for maintaining peer-to-peer graphs |
US20030056094A1 (en) * | 2001-09-19 | 2003-03-20 | Microsoft Corporation | Peer-to-peer name resolution protocol (PNRP) security infrastructure and method |
US20030056093A1 (en) * | 2001-09-19 | 2003-03-20 | Microsoft Corporation | Peer-to-peer name resolution protocol (PNRP) group security infrastructure and method |
US20030097425A1 (en) | 2001-11-20 | 2003-05-22 | Microsoft Corporaton | Distributed device discovery framework for a network |
US20030117433A1 (en) | 2001-11-09 | 2003-06-26 | Microsoft Corporation | Tunable information presentation appliance using an extensible markup language |
US20030158839A1 (en) * | 2001-05-04 | 2003-08-21 | Yaroslav Faybishenko | System and method for determining relevancy of query responses in a distributed network search mechanism |
US20030188010A1 (en) | 2002-03-27 | 2003-10-02 | Imran Raza | Peer to peer mixed media messaging |
US20030196060A1 (en) * | 2002-04-15 | 2003-10-16 | Microsoft Corporation | Multi-level cache architecture and cache management method for peer-to-peer name resolution protocol |
US6636854B2 (en) * | 2000-12-07 | 2003-10-21 | International Business Machines Corporation | Method and system for augmenting web-indexed search engine results with peer-to-peer search results |
US20030204742A1 (en) * | 2002-04-29 | 2003-10-30 | Microsoft Corporation | Peer-to-peer name resolution protocol (PNRP) security infrastructure and method |
US20030204626A1 (en) * | 2002-04-24 | 2003-10-30 | Microsoft Corporation | Method and apparatus for efficiently matching responses to requests previously passed by a network node |
US20030217140A1 (en) * | 2002-03-27 | 2003-11-20 | International Business Machines Corporation | Persisting node reputations in transient communities |
US6674459B2 (en) * | 2001-10-24 | 2004-01-06 | Microsoft Corporation | Network conference recording system and method including post-conference processing |
US6725281B1 (en) | 1999-06-11 | 2004-04-20 | Microsoft Corporation | Synchronization of controlled device state using state table and eventing in data-driven remote device control model |
US6748420B1 (en) * | 1999-11-23 | 2004-06-08 | Cisco Technology, Inc. | Methods and apparatus for providing shared access to an application |
US20040111469A1 (en) | 2002-12-04 | 2004-06-10 | Microsoft Corporation | Peer-to peer graphing interfaces and methods |
US20040111515A1 (en) | 2002-12-04 | 2004-06-10 | Microsoft Corporation | Peer-to-peer identity management interfaces and methods |
US20040148333A1 (en) | 2003-01-27 | 2004-07-29 | Microsoft Corporation | Peer-to-peer grouping interfaces and methods |
US20040148611A1 (en) * | 2003-01-27 | 2004-07-29 | Microsoft Corporation | Peer-to-peer networking framework application programming interfaces |
US20040162871A1 (en) * | 2003-02-13 | 2004-08-19 | Pabla Kuldipsingh A. | Infrastructure for accessing a peer-to-peer network environment |
US20040181487A1 (en) * | 2003-03-10 | 2004-09-16 | Microsoft Corporation | Digital media clearing house platform |
US20040190549A1 (en) | 2003-03-27 | 2004-09-30 | Christian Huitema | Allowing IPv4 clients to communicate over an IPv6 network when behind a network address translator with reduced server workload |
US6801974B1 (en) | 2001-01-26 | 2004-10-05 | Dell Products L.P. | Method of filtering events in a combinational computing device |
US20040213220A1 (en) * | 2000-12-28 | 2004-10-28 | Davis Arlin R. | Method and device for LAN emulation over infiniband fabrics |
US20040236863A1 (en) * | 2003-05-23 | 2004-11-25 | Microsoft Corporation | Systems and methods for peer-to-peer collaboration to enhance multimedia streaming |
US20040249907A1 (en) | 2003-06-06 | 2004-12-09 | Microsoft Corporation | Automatic discovery and configuration of external network devices |
US20040255029A1 (en) | 2003-06-16 | 2004-12-16 | Microsoft Corporation | Discovery and control protocol for intelligent displays |
US20040260800A1 (en) | 1999-06-11 | 2004-12-23 | Microsoft Corporation | Dynamic self-configuration for ad hoc peer networking |
US20050004916A1 (en) * | 2003-06-13 | 2005-01-06 | Microsoft Corporation | Peer-to-peer name resolution wire protocol and message format data structure for use therein |
US20050074018A1 (en) | 1999-06-11 | 2005-04-07 | Microsoft Corporation | XML-based template language for devices and services |
US20050091529A1 (en) | 2003-10-23 | 2005-04-28 | Microsoft Corporation | Peer-to-peer identity management managed interfaces and methods |
US20050108371A1 (en) | 2003-10-23 | 2005-05-19 | Microsoft Corporation | Managed peer name resolution protocol (PNRP) interfaces for peer to peer networking |
US6898200B1 (en) * | 1999-10-29 | 2005-05-24 | Nortel Networks Limited | Method for improving signaling efficiency and performing service load balancing in a connection oriented network |
US20050157659A1 (en) * | 2003-10-30 | 2005-07-21 | Microsoft Corporation | Peer-to-peer cloud-split detection and repair methods |
US20050177715A1 (en) | 2004-02-09 | 2005-08-11 | Microsoft Corporation | Method and system for managing identities in a peer-to-peer networking environment |
US20050216556A1 (en) * | 2004-03-26 | 2005-09-29 | Microsoft Corporation | Real-time collaboration and communication in a peer-to-peer networking infrastructure |
US20060077911A1 (en) * | 2000-05-17 | 2006-04-13 | Shmuel Shaffer | Call optimization in ad-hoc conference calls |
US20060193265A1 (en) * | 2005-02-25 | 2006-08-31 | Microsoft Corporation | Peer-to-peer name resolution protocol with lightweight traffic |
US7185194B2 (en) * | 2000-05-17 | 2007-02-27 | Fujitsu Limited | System and method for distributed group management |
US20070076630A1 (en) * | 2005-09-30 | 2007-04-05 | Microsoft Corporation | Peer name resolution protocol simple application program interface |
US7277946B2 (en) * | 2002-06-28 | 2007-10-02 | Microsoft Corporation | Distributed session listing and content discovery |
US7817647B2 (en) * | 2005-04-22 | 2010-10-19 | Microsoft Corporation | Flower-petal resolutions for PNRP |
US7826396B2 (en) * | 2005-03-07 | 2010-11-02 | Miller John L | System and method for implementing PNRP locality |
US7848332B2 (en) * | 2004-11-15 | 2010-12-07 | Cisco Technology, Inc. | Method and apparatus for classifying a network protocol and aligning a network protocol header relative to cache line boundary |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
ATE469522T1 (en) * | 2000-10-18 | 2010-06-15 | Ericsson Telefon Ab L M | SEAMLESS TRANSFER OF MOBILE IP |
-
2005
- 2005-09-30 US US11/241,393 patent/US8255546B2/en not_active Expired - Fee Related
-
2006
- 2006-10-02 AU AU2006299461A patent/AU2006299461A1/en not_active Abandoned
- 2006-10-02 CA CA002623861A patent/CA2623861A1/en not_active Abandoned
- 2006-10-02 KR KR1020087007110A patent/KR20080063282A/en not_active Application Discontinuation
- 2006-10-02 EP EP06816114A patent/EP1934788A1/en not_active Withdrawn
- 2006-10-02 JP JP2008533777A patent/JP2009510638A/en not_active Withdrawn
- 2006-10-02 CN CNA2006800363494A patent/CN101278274A/en active Pending
- 2006-10-02 BR BRPI0616488-9A patent/BRPI0616488A2/en not_active Application Discontinuation
- 2006-10-02 WO PCT/US2006/038627 patent/WO2007041580A1/en active Application Filing
- 2006-10-02 RU RU2008112155/09A patent/RU2008112155A/en not_active Application Discontinuation
-
2008
- 2008-03-13 NO NO20081331A patent/NO20081331L/en not_active Application Discontinuation
Patent Citations (66)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5586264A (en) * | 1994-09-08 | 1996-12-17 | Ibm Corporation | Video optimized media streamer with cache management |
US5987376A (en) * | 1997-07-16 | 1999-11-16 | Microsoft Corporation | System and method for the distribution and synchronization of data and state information between clients in a distributed processing system |
US6205481B1 (en) * | 1998-03-17 | 2001-03-20 | Infolibria, Inc. | Protocol for distributing fresh content among networked cache servers |
US6252884B1 (en) | 1998-03-20 | 2001-06-26 | Ncr Corporation | Dynamic configuration of wireless networks |
US6269099B1 (en) * | 1998-07-01 | 2001-07-31 | 3Com Corporation | Protocol and method for peer network device discovery |
US20050022210A1 (en) | 1999-06-11 | 2005-01-27 | Microsoft Corporation | Synchronization of controlled device state using state table and eventing in data-driven remote device control model |
US6725281B1 (en) | 1999-06-11 | 2004-04-20 | Microsoft Corporation | Synchronization of controlled device state using state table and eventing in data-driven remote device control model |
US20040260800A1 (en) | 1999-06-11 | 2004-12-23 | Microsoft Corporation | Dynamic self-configuration for ad hoc peer networking |
US20050097503A1 (en) | 1999-06-11 | 2005-05-05 | Microsoft Corporation | XML-based template language for devices and services |
US20050074018A1 (en) | 1999-06-11 | 2005-04-07 | Microsoft Corporation | XML-based template language for devices and services |
US6779004B1 (en) | 1999-06-11 | 2004-08-17 | Microsoft Corporation | Auto-configuring of peripheral on host/peripheral computing platform with peer networking-to-host/peripheral adapter for peer networking connectivity |
US6892230B1 (en) | 1999-06-11 | 2005-05-10 | Microsoft Corporation | Dynamic self-configuration for ad hoc peer networking using mark-up language formated description messages |
US6898200B1 (en) * | 1999-10-29 | 2005-05-24 | Nortel Networks Limited | Method for improving signaling efficiency and performing service load balancing in a connection oriented network |
US6748420B1 (en) * | 1999-11-23 | 2004-06-08 | Cisco Technology, Inc. | Methods and apparatus for providing shared access to an application |
US20060077911A1 (en) * | 2000-05-17 | 2006-04-13 | Shmuel Shaffer | Call optimization in ad-hoc conference calls |
US7185194B2 (en) * | 2000-05-17 | 2007-02-27 | Fujitsu Limited | System and method for distributed group management |
US20020027569A1 (en) | 2000-08-22 | 2002-03-07 | Microsoft Corporation | Generic user control point tool for universal plug and play (UPnP) devices |
US20020112058A1 (en) | 2000-12-01 | 2002-08-15 | Microsoft Corporation | Peer networking host framework and hosting API |
US6636854B2 (en) * | 2000-12-07 | 2003-10-21 | International Business Machines Corporation | Method and system for augmenting web-indexed search engine results with peer-to-peer search results |
US20020075900A1 (en) * | 2000-12-18 | 2002-06-20 | Klaus Turina | Signaling transport protocol extensions for load balancing and server pool support |
US20040213220A1 (en) * | 2000-12-28 | 2004-10-28 | Davis Arlin R. | Method and device for LAN emulation over infiniband fabrics |
US20030041141A1 (en) * | 2001-01-22 | 2003-02-27 | Abdelaziz Mohamed M. | Peer-to-peer presence detection |
US6801974B1 (en) | 2001-01-26 | 2004-10-05 | Dell Products L.P. | Method of filtering events in a combinational computing device |
US7065587B2 (en) * | 2001-04-02 | 2006-06-20 | Microsoft Corporation | Peer-to-peer name resolution protocol (PNRP) and multilevel cache for use therewith |
US20020143989A1 (en) * | 2001-04-02 | 2002-10-03 | Microsoft Corporation | Peer-to-peer name resolution protocol (PNRP) and multilevel cache for use therewith |
US20020156875A1 (en) * | 2001-04-24 | 2002-10-24 | Kuldipsingh Pabla | Peer group name server |
US20030158839A1 (en) * | 2001-05-04 | 2003-08-21 | Yaroslav Faybishenko | System and method for determining relevancy of query responses in a distributed network search mechanism |
US20030056094A1 (en) * | 2001-09-19 | 2003-03-20 | Microsoft Corporation | Peer-to-peer name resolution protocol (PNRP) security infrastructure and method |
US20030055892A1 (en) * | 2001-09-19 | 2003-03-20 | Microsoft Corporation | Peer-to-peer group management and method for maintaining peer-to-peer graphs |
US20030056093A1 (en) * | 2001-09-19 | 2003-03-20 | Microsoft Corporation | Peer-to-peer name resolution protocol (PNRP) group security infrastructure and method |
US6674459B2 (en) * | 2001-10-24 | 2004-01-06 | Microsoft Corporation | Network conference recording system and method including post-conference processing |
US20030117433A1 (en) | 2001-11-09 | 2003-06-26 | Microsoft Corporation | Tunable information presentation appliance using an extensible markup language |
US20030097425A1 (en) | 2001-11-20 | 2003-05-22 | Microsoft Corporaton | Distributed device discovery framework for a network |
US20030188010A1 (en) | 2002-03-27 | 2003-10-02 | Imran Raza | Peer to peer mixed media messaging |
US20030217140A1 (en) * | 2002-03-27 | 2003-11-20 | International Business Machines Corporation | Persisting node reputations in transient communities |
US20030196060A1 (en) * | 2002-04-15 | 2003-10-16 | Microsoft Corporation | Multi-level cache architecture and cache management method for peer-to-peer name resolution protocol |
US20030204626A1 (en) * | 2002-04-24 | 2003-10-30 | Microsoft Corporation | Method and apparatus for efficiently matching responses to requests previously passed by a network node |
US7251694B2 (en) * | 2002-04-29 | 2007-07-31 | Microsoft Corporation | Peer-to peer name resolution protocol (PNRP) security infrastructure and method |
US20030204742A1 (en) * | 2002-04-29 | 2003-10-30 | Microsoft Corporation | Peer-to-peer name resolution protocol (PNRP) security infrastructure and method |
US7418479B2 (en) * | 2002-04-29 | 2008-08-26 | Microsoft Corporation | Peer-to-peer name resolution protocol (PNRP) security infrastructure and method |
US7051102B2 (en) * | 2002-04-29 | 2006-05-23 | Microsoft Corporation | Peer-to-peer name resolution protocol (PNRP) security infrastructure and method |
US7277946B2 (en) * | 2002-06-28 | 2007-10-02 | Microsoft Corporation | Distributed session listing and content discovery |
US20040111469A1 (en) | 2002-12-04 | 2004-06-10 | Microsoft Corporation | Peer-to peer graphing interfaces and methods |
US20040111515A1 (en) | 2002-12-04 | 2004-06-10 | Microsoft Corporation | Peer-to-peer identity management interfaces and methods |
US20040148333A1 (en) | 2003-01-27 | 2004-07-29 | Microsoft Corporation | Peer-to-peer grouping interfaces and methods |
US20040148611A1 (en) * | 2003-01-27 | 2004-07-29 | Microsoft Corporation | Peer-to-peer networking framework application programming interfaces |
US7774495B2 (en) * | 2003-02-13 | 2010-08-10 | Oracle America, Inc, | Infrastructure for accessing a peer-to-peer network environment |
US20040162871A1 (en) * | 2003-02-13 | 2004-08-19 | Pabla Kuldipsingh A. | Infrastructure for accessing a peer-to-peer network environment |
US20040181487A1 (en) * | 2003-03-10 | 2004-09-16 | Microsoft Corporation | Digital media clearing house platform |
US20040190549A1 (en) | 2003-03-27 | 2004-09-30 | Christian Huitema | Allowing IPv4 clients to communicate over an IPv6 network when behind a network address translator with reduced server workload |
US20040236863A1 (en) * | 2003-05-23 | 2004-11-25 | Microsoft Corporation | Systems and methods for peer-to-peer collaboration to enhance multimedia streaming |
US20040249907A1 (en) | 2003-06-06 | 2004-12-09 | Microsoft Corporation | Automatic discovery and configuration of external network devices |
US20050004916A1 (en) * | 2003-06-13 | 2005-01-06 | Microsoft Corporation | Peer-to-peer name resolution wire protocol and message format data structure for use therein |
US7533184B2 (en) * | 2003-06-13 | 2009-05-12 | Microsoft Corporation | Peer-to-peer name resolution wire protocol and message format data structure for use therein |
US20040255029A1 (en) | 2003-06-16 | 2004-12-16 | Microsoft Corporation | Discovery and control protocol for intelligent displays |
US20050091529A1 (en) | 2003-10-23 | 2005-04-28 | Microsoft Corporation | Peer-to-peer identity management managed interfaces and methods |
US20050108371A1 (en) | 2003-10-23 | 2005-05-19 | Microsoft Corporation | Managed peer name resolution protocol (PNRP) interfaces for peer to peer networking |
US7336623B2 (en) * | 2003-10-30 | 2008-02-26 | Microsoft Corporation | Peer-to-peer cloud-split detection and repair methods |
US20050157659A1 (en) * | 2003-10-30 | 2005-07-21 | Microsoft Corporation | Peer-to-peer cloud-split detection and repair methods |
US20050177715A1 (en) | 2004-02-09 | 2005-08-11 | Microsoft Corporation | Method and system for managing identities in a peer-to-peer networking environment |
US20050216556A1 (en) * | 2004-03-26 | 2005-09-29 | Microsoft Corporation | Real-time collaboration and communication in a peer-to-peer networking infrastructure |
US7848332B2 (en) * | 2004-11-15 | 2010-12-07 | Cisco Technology, Inc. | Method and apparatus for classifying a network protocol and aligning a network protocol header relative to cache line boundary |
US20060193265A1 (en) * | 2005-02-25 | 2006-08-31 | Microsoft Corporation | Peer-to-peer name resolution protocol with lightweight traffic |
US7826396B2 (en) * | 2005-03-07 | 2010-11-02 | Miller John L | System and method for implementing PNRP locality |
US7817647B2 (en) * | 2005-04-22 | 2010-10-19 | Microsoft Corporation | Flower-petal resolutions for PNRP |
US20070076630A1 (en) * | 2005-09-30 | 2007-04-05 | Microsoft Corporation | Peer name resolution protocol simple application program interface |
Non-Patent Citations (12)
Title |
---|
"Peer-to-Peer Infrastructure: Creating a Group Chat Application", Microsoft, Copyright 2004, reprinted from the Internet at: http://msdn.microsoft.com/library/en-us/p2psdk/p2p/creating-a-group-chat-application.asp on Apr. 5, 2005. |
"Peer-to-Peer Infrastructure: Grouping API Functions", Microsoft, Copyright 2004, reprinted from the Internet at: http://msdn.microsoft.com/library/en-us/p2psdk/p2p/grouping-api-functions.asp?frame=true on Jul. 13, 2005. |
"Peer-to-Peer Infrastructure: Identity manager Functions", Microsoft, Copyright 2004, reprinted from the Internet at: http://msdn.microsoft.com/library/en-us/p2psdk/p2p/identity-manager-functions.asp?frame on Apr. 5, 2005. |
"Peer-to-Peer Infrastructure: PeerGroupEnumMembers", Microsoft, Copyright 2004, reprinted from the Internet at: http://msdn.microsoft.com/library/en-us/p2psdk/p2p/Peergroupenummembers.asp?frame on Apr. 5, 2005. |
"Teredo Overview," Microsoft Corporation, website, 30 pages available at http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/teredo.mspx, © 2003 Microsoft Corporation. |
D. Box, "Code Name Indigo: A Guide to Developing and Running Connected Systems With Indigo," dated Jan. 2004, MSDN Magazine, 11 pages. |
D. Chappell, "Introducing Indigo: An Early Look," (Longhorn Technical Articles) dated Feb. 2005, Microsoft.com Library, 18 pages. |
Int. Preliminary Report on Patentability cited in PCT Application No. PCT/US2006/038627 dated Apr. 10, 2008. |
International Search Report for PCT/US2006/038627 mailed Feb. 15, 2007. |
New Zealand Examination Report cited in related application No. 566833 dated Oct. 19, 2009. |
The Cable Guy, "Windows Peer-to-Peer Networking: The Cable Guy-Nov. 2003," updated Aug. 5, 2004, Microsoft TechNet, 7 pages. |
Written Opinion for PCT/US2006/038627 mailed Feb. 15, 2007. |
Also Published As
Publication number | Publication date |
---|---|
US20070076630A1 (en) | 2007-04-05 |
RU2008112155A (en) | 2009-10-10 |
CA2623861A1 (en) | 2007-04-12 |
BRPI0616488A2 (en) | 2011-06-21 |
EP1934788A1 (en) | 2008-06-25 |
WO2007041580A1 (en) | 2007-04-12 |
NO20081331L (en) | 2008-06-27 |
CN101278274A (en) | 2008-10-01 |
AU2006299461A1 (en) | 2007-04-12 |
JP2009510638A (en) | 2009-03-12 |
KR20080063282A (en) | 2008-07-03 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN109618005B (en) | Method for calling server and proxy server | |
US8255546B2 (en) | Peer name resolution protocol simple application program interface | |
KR102046700B1 (en) | Message bus service directory | |
JP7097525B2 (en) | Internet of Things Resources Subscription Methods, Devices, and Systems | |
US20080225860A1 (en) | Distributed routing table interface | |
CN105993161B (en) | Element, method, system and computer readable storage device for resolving an address | |
CN107172214B (en) | Service node discovery method and device with load balancing function | |
AU2019430421B2 (en) | Entities for providing an external service to a network | |
US11638134B2 (en) | Methods, systems, and computer readable media for resource cleanup in communications networks | |
CN111615128A (en) | Multi-access edge computing method, platform and system | |
CN111510330B (en) | Interface management device, method and storage medium | |
US11057242B2 (en) | Address system | |
US20080101252A1 (en) | Providing ad-hoc interoperability among network nodes | |
WO2020169175A1 (en) | Entities for providing an external service to a network | |
US8107472B1 (en) | Network single entry point for subscriber management | |
US8041671B2 (en) | Method and system for providing a homogeneous view of a distributed common information model (CIM) within a heterogeneous virtual system environment | |
US11546405B2 (en) | Methods for exposing mainframe data as a web service and devices thereof | |
WO2024169469A1 (en) | Connection establishment method and apparatus | |
US11709725B1 (en) | Methods, systems, and computer readable media for health checking involving common application programming interface framework | |
CN117176612B (en) | Network quality detection method, device and computer readable storage medium | |
CN116866413A (en) | Education account number and basic data linkage processing method and system | |
JP2024523990A (en) | Hardware Accelerator Service Aggregation | |
US20080313646A1 (en) | Storage-device discovery protocol | |
CN117857642A (en) | Data access processing method, device and equipment | |
Cha et al. | Design of the OpenAPI Adaptor for Realizing the Convergence among Home Networks |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: MICROSOFT CORPORATION, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:HORTON, NOAH;THALER, DAVID G.;LIEUALLEN, BRIAN R.;AND OTHERS;SIGNING DATES FROM 20051005 TO 20051006;REEL/FRAME:018301/0942 Owner name: MICROSOFT CORPORATION, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:HORTON, NOAH;THALER, DAVID G.;LIEUALLEN, BRIAN R.;AND OTHERS;REEL/FRAME:018301/0942;SIGNING DATES FROM 20051005 TO 20051006 |
|
ZAAA | Notice of allowance and fees due |
Free format text: ORIGINAL CODE: NOA |
|
ZAAB | Notice of allowance mailed |
Free format text: ORIGINAL CODE: MN/=. |
|
ZAAA | Notice of allowance and fees due |
Free format text: ORIGINAL CODE: NOA |
|
ZAAB | Notice of allowance mailed |
Free format text: ORIGINAL CODE: MN/=. |
|
ZAAA | Notice of allowance and fees due |
Free format text: ORIGINAL CODE: NOA |
|
ZAAB | Notice of allowance mailed |
Free format text: ORIGINAL CODE: MN/=. |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034543/0001 Effective date: 20141014 |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 8 |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
LAPS | Lapse for failure to pay maintenance fees |
Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |