WO2012075853A1 - Peer-to-peer communication method, apparatus, and system - Google Patents

Abstract

Disclosed are a peer-to-peer (P2P) communication method, apparatus, and system for improving the speed of downloading and uploading files for the client. The method of a embodiment of the present invention comprises: determining whether the number of TCP connections between the client and servers reaches a first preset threshold according to status information of connection to servers obtained by the client; if not, selecting at least one server not in TCP connection with the client to establish a TCP connection, and publishing shared file information to the servers in TCP connection with the client. The embodiment of the present invention can effectively improve the speed of downloading and uploading files for the client.

Description

 Method, device and system for peer-to-peer communication. The present application claims priority to Chinese patent application filed on December 8, 2010, the Chinese Patent Office, Application No. 201010579035.7, entitled "A Peer-to-Peer Communication Method, Apparatus and System" The entire contents of which are incorporated herein by reference. Technical field

 The present invention relates to the field of communications technologies, and in particular, to a point-to-point communication method, apparatus, and system. Scenery technology

 Peer-to-peer (P2P), also known as peer-to-peer networking technology, relies on the computing power and bandwidth of participants in the network, rather than concentrating on a small number of servers. Clients of resources and servers that provide shared resources. All clients can provide resources, including bandwidth, storage space and computing power. Such networks can be used for a variety of purposes. Various file sharing software has been widely used. Use, including open source free P2P file sharing software such as eMule and eDonkey. In these file sharing software, the client can establish a Transmission Control Protocol (TCP) connection and a user datagram protocol (UDP, User Datagram) with the server. Protocol) Messages communicate interactively. TCP is a connection-oriented (connection-oriented), reliable, byte-stream-based transport layer communication protocol. UDP is a connectionless transport layer protocol that provides transaction-oriented simple unreliable information transfer services.

 When the node as the client obtains the required shared file, the following two processes need to be performed: First, the node list that owns the shared file is obtained from the server, and it can also be understood that the node list of the shared file can be provided; Then, according to the acquired node The list downloads the shared file from the node in the node list. After the client downloads the shared file, the shared file can also be provided to the node that needs the shared file as the node that owns the shared file. In practical applications, because a shared file is large, a file is usually divided into multiple file segments for download.

In P2P technology, when a client downloads a shared file, it can provide a node of the shared file. The more nodes in the list, the faster the download speed.

 To implement the shared file fragment to other nodes, the node first publishes the shared file information in the server. The shared file information includes the address of the node, the identifier of the shared file that the node can provide, and so on.

 In the prior art, when providing the shared file information, the client needs to issue the shared file information to the server through the TCP connection, but the client only establishes a TCP connection with one server for communication, and communicates with other servers through UDP message interaction. Therefore, when publishing shared file information, the client only issues shared file information to one server through TCP, but does not publish shared file information to other servers.

 In the above prior art, since the node issues shared file information only to a server that establishes a TCP connection with itself when providing the shared file fragment, this will result in the acquisition of the shared file information of the node, and then according to the node. Sharing file information, there are fewer clients downloading the shared file fragment from the node, which in turn affects the download speed of all clients downloading the shared file. Summary of the invention

 The embodiment of the invention provides a peer-to-peer communication method, device and system, which can improve the speed at which a client downloads a file and uploads a file.

 The peer-to-peer communication method provided by the embodiment of the present invention includes: acquiring connection state information with each server; determining, according to the connection state information, whether the number of connections between the client and the each server for the transmission control protocol TCP connection reaches the first pre- Setting a threshold value; if the first preset threshold is not reached, selecting at least one server that does not establish a TCP connection with the client according to the connection state information, and establishing a TCP connection with the selected server; The shared file information is issued to a server that has established a TCP connection with the client.

The peer-to-peer communication device provided by the embodiment of the present invention includes: an obtaining unit, configured to acquire connection state information with each server; and a determining unit, configured to determine, according to the connection state information, a transmission control protocol between the client and each server Whether the number of connections of the TCP connection reaches the first preset threshold; establishing a connection unit, if the first preset threshold is not reached, according to the connection The connection status information selects at least one server that does not establish a TCP connection with itself and establishes a TCP connection with the selected server. The publishing unit is configured to issue shared file information to a server that establishes a TCP connection with the client.

 The peer-to-peer communication system provided by the embodiment of the present invention includes: a server and the foregoing client. As can be seen from the above technical solutions, the embodiment of the present invention has the following advantages: The client first obtains connection state information with each server, and judges and performs with each server according to the connection state information.

Whether the number of connections of the TCP connection reaches the first preset threshold. If not, select at least one server that does not establish a TCP connection with itself according to the status connection information, and establish a TCP connection with the selected server, and then The server that establishes the TCP connection itself issues the shared file information. Because the client can perform a TCP connection with multiple servers in the technical solution, the client that downloads the shared file is added, so that the download speed of all the clients that download the shared file can be improved. Provide the upload speed of the shared file client. DRAWINGS

 In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the description of the prior art will be briefly described below. Obviously, the drawings in the following description are only It is a certain embodiment of the present invention, and other drawings can be obtained from those skilled in the art without any inventive labor.

 1 is a schematic diagram of an embodiment of a point-to-point communication method according to an embodiment of the present invention;

 2a is a schematic diagram of another embodiment of a point-to-point communication method according to an embodiment of the present invention; FIG. 2b is a schematic diagram of another embodiment of a point-to-point communication method according to an embodiment of the present invention;

 4 is a schematic diagram of a point-to-point communication method for optimizing a network connection according to an embodiment of the present invention; FIG. 5 is a schematic diagram of another embodiment of a point-to-point communication method according to an embodiment of the present invention; FIG. Schematic diagram of an embodiment;

FIG. 7 is a schematic diagram of an embodiment of a point-to-point communication system according to an embodiment of the present invention. detailed description

 The technical solutions of the embodiments of the present invention are further described below with reference to the accompanying drawings and specific embodiments. It is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

 In a P2P environment, a node only stores a partial fragment file of a shared file. In the process of acquiring the entire shared file, the node provides the other node with the fragment file of the shared file owned by the other node, and also from other nodes. Get other clip files that have not yet been obtained. For example, the file filel has a total of 10 fragment files, which are denoted as filel_p0~filel_p9. Among them, the A node has filel_p0~filel_p4, and the A node publishes the shared file information on the server. Based on the shared file information posted by the node A on the server, the node B knows that the node A has the file filel, and learns that the node A has filel_p0~filel_p4 through message interaction with the node A, and then the node B downloads the filel_p0 of filel from the node A. Filel_p4. The A node can learn from the message interaction that the B node owns filel_p5~filel_p9, so that the A node can obtain filel_p5~filel_p9 directly from the B node.

 Therefore, in a P2P environment, the more nodes including the B node learn the shared file information of the A node, which not only speeds up the downloading of shared files by other nodes, but also speeds up the download of the A node to the entire shared file. speed.

 The embodiment of the present invention provides a peer-to-peer communication method, device, and system. The client can perform a TCP connection with multiple servers, and increase the number of clients that download the shared file, so as to improve the download speed of all clients that download the shared file. The point-to-point communication method, device and system provided by the embodiments of the present invention are described in detail below.

 In the embodiment of the present invention, the point-to-point communication protocol uses the eMule protocol as an example, and can also be applied to other point-to-point protocols, such as the eDonkey protocol, the Ares protocol, and the BT protocol.

 Referring to FIG. 1, an embodiment of a peer-to-peer communication method according to an embodiment of the present invention includes:

 101. Obtain connection state information with each server.

In the embodiment of the present invention, a server connection pool module is added to the client, including obtaining a single The unit, the judging unit, the establishing unit, the issuing unit, the control unit and the sending unit are responsible for the connection with each server, including the TCP connection and the UDP session, and are responsible for publishing the shared file information to the server, when other modules of the client are downloading the file. When you need to query the list of nodes that can provide shared files, you must use the server connection pool module to schedule when to decide whether to issue TCP query messages or UDP query messages.

 First, the client obtains connection state information of each server that has a connection relationship with the client, and the connection state information includes a case where each server performs a TCP connection and a UDP session with the client.

 It should be noted that, in this embodiment, a node that provides a shared file and a downloaded shared file is referred to as a client, and a server that establishes a TCP connection with the client and can provide a node list query function is referred to as a primary server.

 102. Determine whether the number of connections between the client and each server for the transmission control protocol connection reaches a first preset threshold.

 In the embodiment of the present invention, according to the obtained connection state information, the client can determine whether the number of connections (the number of connections with the primary server) for which the server performs TCP connection with each server reaches the first preset threshold, because the client is When the shared file information is published, the shared file information is only released to the primary server through TCP, and is not released to other servers. Therefore, the number of servers that the client makes a TCP connection with the server directly affects the scope of the client to publish the shared file information.

 It should be noted that the first preset threshold is set by the system. For example, the first preset threshold may be set in the range of 300 to 500. If the first preset threshold is set too large, the established threshold is established. The number of TCP connections is too large and the system resources are occupied. If the first preset threshold is set too small, the number of established TCP connections is too small to affect the transmission speed of the shared file. The first preset threshold can be based on actual conditions. The application process is set, which is not limited here.

 If the client determines that the number of connections for which the TCP connection is made with each server reaches the first preset threshold, the result is not reached, and then step 103 is performed.

 103. Select, according to the connection status information, at least one server that does not establish a transmission control protocol connection with the client and establish a transmission control protocol connection with the server;

If the client determines that the number of connections between the server and each server is not up to the first When the threshold is set, the status of the connection information with each server is queried, and a server that does not establish a TCP connection with itself is selected according to the status of the connection information and a TCP connection is established therewith.

 It should be noted that the client can select one and not established according to the status of the connection information.

TCP connection server, and establish a TCP connection with it, and then select the next TCP connection with the server that does not establish a TCP connection, until the number of connections with the server TCP connection reaches the first preset threshold, the client can also simultaneously The method of establishing a TCP connection with multiple servers to make the number of connections of the server to the TCP connection reaches the first preset threshold, and the manner of establishing the connection is not limited herein.

 It should be further noted that the specific way of selecting a TCP connection may be to select a server to respond to the speed of the response, such as preferentially selecting a server with a fast response to establish a TCP connection, or In other ways, for example, a server that does not establish a TCP connection with the client is randomly selected to establish a TCP connection. The specific selection method is related to the actual application process, which is not limited herein. The response speed of the above server can be detected by using UDP packets as probe messages.

 In addition, after receiving the probe message, the server may return the server information, and the client may also select according to the server information returned by the server. For example, the number of users of the server included in the server information, the client according to the number of users of the server is at least In order, a server with a large number of users is preferentially established to establish a TCP connection.

 104. Publish shared file information to a server that establishes a transmission control protocol connection with the client. In the embodiment of the present invention, after the client establishes a TCP connection with the server, the client may issue shared file information to the server that establishes a TCP connection with the client, where the shared file information includes the address of the client, the name of the shared file owned, Information such as size, release time, etc. Other clients can find all the nodes that save the shared file by querying the node list. The more nodes are found, the faster the client downloads the shared file, and the client issues the share to the primary server. The specific process of the file information will be described in detail in the subsequent embodiments.

In the embodiment of the present invention, the client first obtains connection state information with each server, and then determines, according to the connection state information, whether the number of connections for performing TCP connection with each server reaches the first preset. Threshold value, if not, select at least one server that does not establish a TCP connection with itself according to the status connection information, establish a TCP connection with the selected server, and then issue shared file information to all servers that establish a TCP connection with itself. Since the client can make a TCP connection with more servers, so that more other clients have the opportunity to know that the client can provide shared files, and increase the number of potential clients that download the shared file, thereby improving the download of the shared file. The download speed of all clients, and since the shared file information can be issued to multiple servers establishing TCP connections, any client with its main server can get the node address in the query of the first node list, increase The number of nodes, which in turn increases the download speed of all clients that download the shared file.

 For ease of understanding, the peer-to-peer communication method in the embodiment of the present invention is described below with reference to another embodiment. Referring to FIG. 2a, another embodiment of the peer-to-peer communication method in the embodiment of the present invention includes:

 201. Obtain connection state information with each server.

 For the content of the step 201 in the embodiment of the present invention, refer to the related description of the step 101 in the foregoing embodiment of the present invention, and details are not described herein again.

 202. Determine whether the number of connections between the client and each server for the transmission control protocol connection reaches a first preset threshold.

 If the client determines that the number of connections between the server and the server does not reach the first preset threshold, step 203 is performed, if the client determines that the number of connections between the server and each server reaches the first preset threshold. For the value, go to step 204.

 For the specific judgment process, refer to the related description in the embodiment shown in Figure 1 above, and details are not described herein again.

 203. Select at least one server that does not establish a transmission control protocol connection with the client according to the connection state information, and establish a transmission control protocol connection with the server;

In the embodiment of the present invention, if the client determines that the number of connections between the server and the server for the TCP connection does not reach the first preset threshold, the status of the connection information with each server is selected according to the state of the connection information. Establish a TCP with a server that does not have a TCP connection with itself For the specific process of establishing a TCP connection, refer to the related description in the embodiment shown in FIG. 1 , and details are not described herein again.

 When the number of connections of the TCP connection established by the client and the server reaches the first threshold, step 204 is performed.

 It should be noted that the specific setting of the first preset threshold is related to the actual application process, and is not limited herein.

 It should be further noted that the specific manner of selecting a server that does not establish a TCP connection with itself is related to the actual application process, and is not limited herein.

 204. Publish shared file information to all servers that have a transmission control protocol connection with the client;

 In the embodiment of the present invention, the client issues shared file information to all the primary servers that have established a TCP connection with itself.

 Specifically, the client obtains the shared file information stored on the primary server. If the client does not obtain the shared file information on a primary server, it may determine that there is no shared file on the primary server, if such a primary server exists. , the client issues shared file information to the primary server that has not published the shared file.

 In another case, the client records the shared file information that has been published to each primary server. If it is determined according to the record that a shared server does not include the shared file information to be published, the client issues the location to the primary server. The shared file information to be published.

 For example, the shared file information previously issued by the client to the primary server includes only the information of the file B, the identifier of the file C, the release time, and the like. When the client determines that the shared file information of the file A has not been released to the primary server according to the record, the client The terminal issues the shared file information of file A to the primary server.

 Further, the client sends a User Datagram Protocol UDP message to all servers except the TCP connection, and requests to establish a UDP session with the server. In addition to communicating with the primary server, the client can also communicate with other servers through the UDP message session mode. , but does not publish shared file information to servers other than the primary server.

It should be noted that the client issues shared file information to all the primary servers, which can be After the release, the shared file information can be released at a certain interval. The specific release mode is related to the actual application process, and is not limited herein.

 205. Query a node list.

 First, the client obtains the node number information of the shared file in the locally downloaded node list, and determines whether the number of nodes is smaller than the second preset threshold according to the quantity information. If not, the server selects the query message of the query node.

 Specifically, in order to prevent being blocked by the server, the client preferentially sends a query message to the primary server that has not queried the node list within a certain period of time. If there is no primary server that meets the requirements, the client sends a UDP to the server that does not establish a TCP connection. Query the message and query the node list of the files on other servers that do not have a TCP connection established.

 It should be noted that the first time can be set by the internal program of the system, and is generally set to be more than 1 minute. The main reason is to prevent the query message from being sent too frequently, which may be considered as malicious sending information, and the client that sends the query message is used by the system. Shielding can be set according to the actual situation, so that the client will not send the query message to the main server because the setting time is too long, and the client will not be blocked by the system because the setting time is too short. limited.

 It should be further explained that each time the query message of the node list is sent, the next query message may be sent after waiting for the feedback result of the queried server, and the query message may be simultaneously sent to multiple servers at the same time, and wait until the queried server The feedback result is executed in the next step, and the specific query situation is related to the actual application process, which is not limited herein.

 206. Determine whether the number of nodes sharing the file in the locally downloaded node list exceeds a second preset threshold;

 In the embodiment of the present invention, the client determines, according to the information displayed in the locally downloaded node list, whether the number of nodes of the shared file recorded in the locally downloaded node list exceeds a second preset threshold. 207.

It should be noted that the second preset threshold is set by the system. For example, the second threshold setting may be set in a range of 200 to several thousand, and may or may not be equal to the first preset threshold. The number of nodes affects the speed at which the shared file is downloaded, so the specific setting of the second preset threshold is set. It is related to the download speed to be shared by the actual application, which is not limited here.

 207. Stop the number of nodes that query the shared file.

 According to the number of nodes of the shared file in the local download node list, when the number of nodes sharing the file exceeds the second preset threshold, the client does not send the information of the query node list to each server, and stops querying the node of the shared file. The quantity, when it is determined in step 206 that the number of nodes of the shared file recorded in the locally downloaded node list is lower than the second preset threshold, the information of the query node list is sent to each server, and the number of nodes for querying the shared file is started.

 In the embodiment of the present invention, the client obtains the number of nodes of the shared file in the locally downloaded node list, and determines whether the number of nodes is smaller than the second preset threshold. If it is smaller, the client preferentially selects no query for a certain period of time. The primary server of the node list performs the query. Since the client and the primary server are in TCP mode communication, the reliability is high, and the correctness of the transmitted data can be ensured. The request information of the node list and the response information of the server are not lost. Therefore, the client can be effectively prevented from losing the opportunity to obtain a large number of nodes, thereby affecting the download speed of all clients downloading the shared file and the download speed of the shared file downloaded by the client. If there is no primary server that meets the requirements, the client sends a UDP query message to the server that does not establish a TCP connection, and queries the node list of the file on the other server that does not establish a TCP connection, which can effectively increase the chance of querying other nodes, and improve the client. Download the download speed of the shared file. Further, the client determines, according to the number of nodes of the shared file in the locally downloaded node list, whether the number of nodes having the shared file recorded in the locally downloaded node list exceeds a second preset threshold, and if so, indicates the number of nodes. Sufficiently, there is no need to send a query request to the server to query the node list to increase the number of nodes as the download source, and the client no longer queries the server for the node list.

 FIG. 2b is a flowchart of a peer-to-peer communication method in a scenario in which a client only has a partial file segment in a shared file to be downloaded, and needs to download other file segments from other nodes to obtain a complete shared file to be downloaded. The client performs the following steps 211 to 217, where the steps 211 to 214 are basically similar to the steps 201 to 204 in FIG. 2a, and are only briefly described herein: Step 211: The client acquires connection state information with each server;

Step 212, the client determines whether the number of connections with each server for TCP connection reaches the first a preset threshold; if the first preset threshold is reached, step 214 is performed, otherwise step 213 is performed; step 213, if the number of connections between the client and each server for TCP connection does not reach the first preset threshold a value, according to the connection status information, selecting at least one server that does not establish a TCP connection with the client and establishing a TCP connection with the server;

 Step 214: The client issues shared file information to a server that establishes a TCP connection with the client; the client owns a part of the file segment in the shared file;

 Step 215: Determine, according to the locally saved node list of the file segment of the shared file to be downloaded, whether the number of nodes in the node list of the shared file that has the shared file to be downloaded is smaller than the second preset threshold. Proceed to step 216; if greater than the second preset threshold, proceed to step 219;

 The locally saved node list of the file segment having the shared file to be downloaded is generated according to the shared file information of other nodes stored locally;

 Step 216: Send a query message for querying the node list to the server, where the node list includes a node that has a shared file to be downloaded, where the query message includes the identifier of the shared file to be downloaded;

 Optionally, a partial server may be selected to send a query message, and a selection policy when selecting a server is as described in step 205.

 Step 217: Receive a query result returned by the server, that is, return a node list of the node that has the shared file to be downloaded, and merge the returned node list with the previously locally saved node list to update the locally saved node list, and return to step 215. ;

 In step 218, the node that owns the shared file to be downloaded is obtained from the locally saved node list, and the remaining fragment files of the shared file to be downloaded are downloaded from the obtained node, thereby obtaining the entire shared file to be downloaded.

In the embodiment provided in FIG. 2a and FIG. 2b, the client can issue shared file information to a larger number of primary servers through the first four steps, thereby increasing the chances of other clients from More primary servers are aware of the client's opportunity to share file information. On the one hand, on the one hand, the download speed is increased by increasing the number of clients that download the shared file; On the one hand, since other clients download the file fragments of the shared file from the client and interact with each other's file fragments, the client can download other file fragments from other clients as soon as possible, shortening the client. The time it takes to download to the full shared file.

 In the worst case, the client that publishes the shared file information does not obtain the remaining file fragments from other clients during the process of downloading the shared file fragments from the client, and may go through steps 215 to 218. Speed up the process of getting the rest of the file fragments from other clients. For the network diagram in the prior art, refer to FIG. 3. For the network diagram optimized by the embodiment of the present invention, refer to FIG. 4, where 301 and 401 are eMule network servers, 302 and 402 are eMule network clients, 303 and 403 is a node in the eMule network. The solid line in the connection between the eMule network server, the eMule network client, and the nodes in the eMule network indicates the connection of the TCP connection mode, and the dotted line indicates the connection of other connection methods.

 For ease of understanding, the workflow of the client is described in detail in a specific application scenario. Referring to FIG. 5, another embodiment of the peer-to-peer communication method according to the embodiment of the present invention includes:

 501. Obtain connection status information.

 For the content of the step 501 in the embodiment, refer to the related description of the step 101 in the foregoing embodiment of the present invention, and details are not described herein again.

 It should be noted that, the first server may be a server that establishes a TCP connection with the client, and the second server may be a server that does not establish a TCP connection with the client. It may be understood that, in actual applications, the server may also be Other types of devices, if applied to the Ares protocol, the client establishes a connection with the super node. If the BT protocol is applied, the client establishes a connection with the tracker server, and the specific device is related to the actual application process, which is not limited herein.

 502. Determine whether the number of connections between the client and each server for the transmission control protocol connection reaches a first preset threshold.

 Based on the obtained connection status information, the client can determine whether the number of connections between the TCP connection and each server reaches the first preset threshold.

503. If not, select a server that does not establish a transmission control protocol connection with the client and It establishes a transmission control protocol connection;

 If the number of connections that the client determines to make a TCP connection with each server does not reach the first preset threshold, the server is selected to establish a TCP connection with the server that has not established a TCP connection with itself, and the number of established TCP connections reaches the first pre-establishment. When the threshold is set, the shared file information is published to the primary server.

 504. If yes, select a server that establishes a transmission control protocol connection with the client to issue shared file information.

 If the client determines that the number of connections between the TCP connection and the server is up to the first preset threshold according to the obtained connection status information, the client issues the shared file information to the primary server, and other clients can query the shared file by querying the shared file. Information finds all servers that store shared file information. The more servers you find, the faster the client downloads the shared file.

 For the specific process of publishing the shared file information in the embodiment of the present invention, refer to the description related to step 204 in the embodiment of FIG. 2, and details are not described herein again.

 505. Query a node list.

 First, the client obtains the number of nodes of the shared file in the locally downloaded node list, and determines whether the number of nodes is smaller than the second preset threshold according to the number of nodes. If the query is too frequent, the client has a query message. It may be blocked by the system as maliciously sent information. Therefore, the client prefers to send a query message to the primary server that has not queried the node list within a certain period of time. If there is no primary server that meets the requirements, the client does not establish a TCP connection. The server sends a UDP query message to query the list of nodes that have shared files on other servers that do not have a TCP connection established.

 For the specific process of querying the node list in the embodiment of the present invention, refer to the description related to step 205 in the foregoing embodiment of FIG. 2, and details are not described herein again.

 506. Determine whether the number of nodes in the locally downloaded node list that have the shared file to be downloaded exceeds a second preset threshold, and if so, stop querying the number of nodes sharing the file.

In the embodiment of the present invention, the client determines whether the number of nodes having the shared file to be downloaded exceeds the second preset threshold according to the number of nodes in the locally downloaded node list that have the shared file to be downloaded. More, no need to establish a TCP connection with the server to increase the section If the number of nodes of the shared file is less than the second preset threshold, the number of nodes of the shared file is not queried. Then, the information of the query node list is sent to each server, and the list of nodes having the shared file to be downloaded is started to be queried.

 It should be noted that the second preset threshold may or may not be equal to the first preset threshold. Because the number of nodes affects the speed of downloading the shared file, the specific setting of the second preset threshold is It is related to the download speed to be shared by the actual application, which is not limited here.

 The following describes a point-to-point communication device in the embodiment of the present invention. Referring to FIG. 6, an embodiment of the point-to-point communication device in the embodiment of the present invention includes:

 The obtaining unit 601 is configured to obtain connection state information with each server.

 The determining unit 602 is configured to determine, according to the connection state information, whether the number of connections between the client and each server for the transmission control protocol TCP connection reaches a first preset threshold;

 Establishing a connection unit 603, configured to: if the first preset threshold is not reached, select at least one server that does not establish a TCP connection with the client according to the connection status information, and establish a TCP connection with the selected server;

 The issuing unit 604 is configured to issue shared file information to a server that establishes a TCP connection with the client.

 Optionally, the issuing unit 604 is further configured to: if the determining result of the determining unit 602 is that the first preset threshold is reached, issue the shared file information to all servers that establish a TCP connection with the client.

 Optionally, in order to further shorten the time for the client to download to the entire shared file, the obtaining unit 601 is further configured to obtain a locally saved node list of the node that has the shared file to be downloaded;

 The determining unit 602 is further configured to determine whether the number of nodes in the node list is less than a second preset threshold;

The sending unit 605 is configured to: when the determination result of the determining unit 602 is less than the second preset threshold, send a TCP query message to the server that establishes the TCP connection, to all but the establishment of the TCP. The server sends a UDP query message, where the query message is used to query a node list that has a shared file to be downloaded;

 Specifically, when the determining unit 602 determines that the number of nodes having the shared file in the locally saved node list is less than the second preset threshold, sending the TCP to the server establishing the TCP connection according to the connection state information with the server. Query messages, send UDP query messages to all servers except TCP.

 The control unit 606 is configured to merge the node list returned by the server with the locally saved node list to update the locally saved node list, and if the determining unit 602 determines that the number of nodes in the updated locally saved node list exceeds the second preset Threshold, the number of nodes that stop querying the shared file.

 For ease of understanding, the following describes the relationship between the units in the point-to-point communication device in the embodiment of the present invention in a specific application scenario:

 In this embodiment, the obtaining unit 601 first acquires connection state information with each server, and the connection state information includes a case where each server performs a TCP connection and a UDP session with the client.

 It should be noted that the server that establishes a TCP connection with the client may be referred to as a primary server. The determining unit 602 determines whether the number of connections between the TCP connection and the server is up to the first preset threshold according to the connection status information. For the specific determination process, refer to the description in the embodiment shown in FIG. 1 above. Let me repeat.

 It should be noted that the specific setting of the first preset threshold is related to the actual application process, and may be arbitrarily set according to the expected speed of the shared file required by the client, which is not limited herein.

 If the determining unit 602 determines that the number of connections between the client and each server for TCP connection does not reach the first preset threshold, the establishing connection unit 603 selects at least one server that does not establish a TCP connection with itself and establishes a TCP connection with it, and when establishing When the number of TCP connections reaches the first preset threshold, the issuing unit 604 issues the shared file information to all the main servers, and if the determining unit 602 determines that the number of connections between the client and each server for the TCP connection reaches the first preset gate The limit value is also issued by the issuing unit 604 to all the main servers to share the file information.

In this embodiment, the specific process of establishing a TCP connection and the specificity of publishing the shared file information For details, refer to the descriptions of steps 204 to 205 in the embodiment of FIG. 2, and details are not described herein again.

 It is to be noted that the publishing unit 604 advertises the shared file information to all the main servers, which may be advertised at the same time, and the shared file information may be advertised at a certain time interval. The specific publishing method is related to the actual application process, and is not limited herein.

 Further, the sending unit 605 sends a UDP message to all servers except the established TCP connection, and requests to establish a UDP message session with the server for subsequent communication with the server that establishes the UDP message session.

 When the node list is queried, the obtaining unit 601 first obtains the node number information of the shared file to be downloaded in the locally saved node list, and according to the node quantity information, the determining unit 602 determines whether the number of nodes is less than the second preset threshold. If not, the establishing connection unit 603 preferentially sends a query message to the primary server that has not queried the node list within a certain period of time, and the query message is used to query the node list that has the shared file to be downloaded, if there is no primary server that meets the requirements, The sending unit 605 sends a UDP query message to the server that does not establish a TCP connection, and queries the node list of files on other servers that do not establish a TCP connection.

 It should be noted that the certain time can be set by the internal program of the system, generally set to more than 1 minute, mainly to prevent the query message from being sent too frequently, which may be considered as malicious sending information, and the client sending the query message is blocked by the system. Therefore, the certain time can be specifically set according to the actual situation, and the setup unit 603 does not send the query message to the primary server due to the set time, and the client is not blocked by the system because the set time is too short. The specific time is not limited here.

 Further, each time the sending unit 605 issues a query list of the node list for querying the node list that has the shared file to be downloaded, the query message may be sent after the query result of the queryed server, and then the next query message may be sent. The server sends the query message at the same time, and waits for the feedback result of the queried server to execute the next step. The specific query is related to the actual application process, which is not limited herein.

In this embodiment, the determining unit 602 is configured according to the shared text in the obtained locally downloaded node list. The number of nodes of the device determines whether the number of nodes sharing the file exceeds the second preset threshold. If it exceeds, it indicates that the number of nodes is sufficient, and there is no need to establish a TCP connection with the server to add a node, and the control unit 606 no longer The server sends a query message of the query node list, and stops querying the number of nodes of the shared file. When the number of nodes of the shared file recorded in the locally downloaded node list is lower than the second preset threshold, the server sends a query node to each server. The list of query messages, the number of nodes that started querying shared files.

 It should be noted that the specific setting of the second preset threshold is related to the actual application process, and is not limited herein.

 In the implementation of the present invention, the obtaining unit 601 first obtains connection state information with each server, and according to the connection state information, the determining unit 602 determines whether the number of connections for performing TCP connection with each server reaches a first preset threshold. The shared file information is issued by the issuing unit 604 to all the primary servers. If not, the establishing connection unit 603 selects at least one server that does not establish a TCP connection with itself according to the state connection information, and establishes a TCP connection with the selected server, and the issuing unit The 604 issues the shared file information to all the main servers. Since the client can make a TCP connection with more servers, the client that downloads the shared file is added, so that the download speed of all the clients that download the shared file can be improved, and since The server that establishes the TCP connection publishes the shared file information, so that any client with its main server can obtain the node address in the query of the first node list, increase the number of nodes, and thereby improve all the users who download the shared file. Download speed of clients. Further, the determining unit 602 determines, according to the node number information of the shared file in the locally downloaded node list acquired by the obtaining unit 601, whether the number of nodes of a shared file exceeds a second preset threshold, and if so, indicates the number of nodes. Sufficiently, the sending unit 605 does not need to send a query message again.

 The following describes a point-to-point communication system in the embodiment of the present invention. Referring to FIG. 7, an embodiment of the point-to-point communication system in the embodiment of the present invention includes:

 Client 701 and server 702;

The client 701 is configured to obtain connection state information with each server, and determine, according to the connection state information, whether the number of connections between the server and the server for the transmission control protocol TCP connection is A first preset threshold is reached. If the first preset threshold is not reached, at least one server that does not establish a TCP connection with the server is selected according to the connection status information, and a TCP connection is established with the selected server. The server that established the TCP connection publishes the shared file information.

 For the specific implementation process of the client 701, refer to the description of related parts in the foregoing embodiment shown in FIG. 2, and details are not described herein again.

 The server 702 is a high-performance computer in a network environment. It receives service requests submitted by other computers (clients) on the network, and provides corresponding services. It is a computer that manages resources and provides services for users. The specific working process of the server is Common sense, no more details here.

 A person skilled in the art can understand that all or part of the steps of implementing the above embodiments can be completed by a program to instruct related hardware, and the program can be stored in a computer readable storage medium, the above mentioned storage. The medium can be a read only memory, a magnetic disk or a compact disk or the like.

 The method, the device and the system for the peer-to-peer communication provided by the present invention are described in detail above. For those skilled in the art, according to the idea of the embodiment of the present invention, the specific implementation manner and the application range may be changed. In the above, the contents of this specification are not to be construed as limiting the invention.

Claims

Rights request  A point-to-point communication method, comprising:  Obtain connection status information with each server;  Determining, according to the connection status information, a transmission control protocol between the client and each server Whether the number of connections of the TCP connection reaches the first preset threshold;  If the first preset threshold is not reached, selecting at least one server that does not establish a TCP connection with the client according to the connection status information, and establishing a TCP connection with the selected server;  The shared file information is issued to a server that has established a TCP connection with the client.  2. The method according to claim 1, wherein the selecting at least one server that does not establish a TCP connection with the client is specifically:  After the client sends a probe message, the server responds with a fast-to-slow response, and the server is selected to establish a TCP connection.  The method according to claim 1, wherein the selecting at least one server that does not establish a TCP connection with the client is specifically:  After receiving the probe message sent by the client, the number of users of the server returned by the server; according to the number of users of the server, the server is selected to establish a TCP connection in at least an order. 4. The method according to claim 1, wherein if the first preset threshold is reached, the shared file information is issued to all servers that have established a TCP connection with the client.  The method according to any one of claims 1 to 4, wherein the method further comprises:  A User Datagram Protocol UDP message is sent to all servers except the established TCP connection, which is used to establish a UDP session with all servers except the established TCP connection. The method according to any one of claims 1 to 4, wherein the method further comprises: Obtaining a locally saved list of nodes having shared files to be downloaded;  Determining, according to the number of nodes, whether the number of nodes in the node list is less than a second preset threshold;  If it is smaller, the query message is sent to each server, and the query message is used to query the list of nodes that have the shared file to be downloaded.  The method according to claim 6, wherein after the sending the query message, the method further includes:  Combining the node list returned by the server with the locally saved node list, thereby updating the locally saved node list, and determining whether the number of nodes in the updated locally saved node list exceeds the second preset threshold. If exceeded, The client stops sending query messages.  8. The method according to claim 6, wherein the sending, by the client, the query message to each server comprises:  Based on the connection status information with each server, a TCP inquiry message is sent to the server establishing the TCP connection, and a UDP inquiry message is sent to all servers except the established TCP connection.  The method according to claim 6, wherein the sending the query message to each server is specifically: selecting to send a query message to a primary server that has not queried the node list within a predetermined time, if there is no predetermined time If the primary server has not queried the node list, it sends a UDP query message to the server that does not establish a TCP connection, and queries the node list of the node that has the shared file on the server that does not establish a TCP connection.  10. A point-to-point communication device, comprising:  An obtaining unit, configured to acquire connection state information with each server;  a determining unit, configured to determine, according to the connection state information, whether the number of connections between the client and the server for the transmission control protocol TCP connection reaches a first preset threshold;  Establishing a connection unit, configured to: if the first preset threshold is not reached, select at least one server that does not establish a TCP connection with itself according to the connection status information, and establish a TCP connection with the selected server; a publishing unit, configured to publish a shared file to a server that establishes a TCP connection with the client Information.  11. Apparatus according to claim 10 wherein:  The issuing unit is further configured to: if the judgment result of the determining unit is that the first preset threshold is reached, issue the shared file information to all servers that establish a TCP connection with the client.  The device according to claim 10 or 11, wherein the device further comprises: the obtaining unit, configured to acquire a locally saved node list of nodes having a shared file to be downloaded;  The determining unit is further configured to determine whether the number of nodes in the node list is less than a second preset threshold;  And a sending unit, configured to send a query message to each server when the determining result of the determining unit is less than the second preset threshold.  13. Apparatus according to claim 12 wherein:  The sending unit is specifically configured to send a TCP query message to the server establishing the TCP connection according to the connection state information with each server, and send a UDP query message to all servers except the established TCP connection.  14. A point-to-point communication system, comprising:  A server and an apparatus according to any one of claims 10 to 13.