WO2011082637A1

WO2011082637A1 - Peer to peer network and peer node restarting method

Info

Publication number: WO2011082637A1
Application number: PCT/CN2010/080322
Authority: WO
Inventors: 彭永林; 郝振武
Original assignee: 中兴通讯股份有限公司
Priority date: 2010-01-05
Filing date: 2010-12-27
Publication date: 2011-07-14
Also published as: CN102118421B; CN102118421A

Abstract

A peer to peer network and a peer node restarting method are disclosed by the present invention. The method includes: when a peer node in the peer to peer network is restarting, the peer node obtains configuration information from other peer nodes in the peer to peer network except the restarting peer node; the restarting peer node accomplishes the restarting procedure according to the obtained configuration information. By the present invention, the problem that the peer node fails to obtain configuration information when restarting is avoided, and the service performance is improved.

Description

TECHNICAL FIELD The present invention relates to the field of network and communication technologies, and in particular, to a peer-to-peer network and a method for restarting a peer node. BACKGROUND Peer-to-Peer (P2P) is a distributed network in which participants of a network share resources and services they have. In general, the sharing of resources and services includes: sharing and exchange of information, sharing of computing resources (for example, CPU), sharing of storage resources (for example, cache and disk space). Shared resources and services can be accessed by any peer (Peer) in the network. Each participant in a peer-to-peer network is both a resource and a service provider (server), as well as a resource and a client. Resource location and distribution (REsource LOcate And Discovery, RELOAD for short) is a kind of peer-to-peer network resource definition defined by the Peer To Peer Session Initiation Protocol (P2PSIP) working group. And discovery agreement. Specifically, several terms involved in the RELOAD network are defined as follows: Node ID: A unique identifier for each node in a peer-to-peer network; Configuration Server: Provides configuration information for the entire network, for example, certificate server address, boot node Addresses, algorithms used by the network, size limits of messages, and some other common configuration information. Boot node: A peer node with a public IP address that can be directly connected by a peer node and can provide a boot service for the joining of peer nodes; the address of the boot node is set in the configuration information of the configuration server; It is determined by the algorithm according to the relationship between two node IDs. When the ID of one node B is the latest successor node ID of the ID of another node A, node B is called the access node of node A. FIG. 1 is a schematic diagram of an existing RELOAD peer-to-peer network. As shown in FIG. 1, the RELOAD peer-to-peer network is composed of peer nodes (A, B, C, D), a configuration server, and the like. The configuration server provides configuration information for the entire network; the node D is a boot node, and the other nodes can join the peer network to provide the boot service. In a peer-to-peer network, due to the large number of nodes and large instability, the frequency of node restarts in the RELOAD peer-to-peer network is relatively high. For example, assuming that peer node A is to be restarted and joins the peer-to-peer network in Figure 1, node A first needs to obtain configuration information from the configuration server and store it locally, then test the local cached boot node D ( Since node A is restarted, the connectivity of the boot node is already cached locally and its own admission node ID is obtained. The specific implementation process of the process is as shown in FIG. 2, and mainly includes the following steps: Step 201: The peer node A is restarted; Step 202: The peer node A obtains configuration information from the configuration server by using HTTP GET mode; Step 4 gathers 203 : The configuration server returns an XML configuration file; Step 4: 204: Peer node A overwrites the local old configuration with the new configuration; Step 205: Peer node A selects node D from the locally cached boot node; Step 206: The node A sends a connectivity test request to the node D, and the request includes its own node ID. Step 207: The boot node D searches for the corresponding access node in the peer-to-peer network according to the node ID in the request, and then The node ID of the admission node is returned to node A; Step 208: Peer node A performs the remaining processes of joining the peer-to-peer network. As can be seen from the above process, each time the peer node restarts, the configuration file must be obtained from the configuration server. Generally, the number of nodes in the peer network is large, so When the frequency of restarting the node is high, each peer node needs to obtain the configuration file from the configuration server, which will impose a heavy burden on the configuration server. SUMMARY OF THE INVENTION A primary object of the present invention is to provide a peer-to-peer network and a method for restarting a peer node to at least solve the above problems. According to an aspect of the present invention, a method for restarting a peer node is provided, comprising: when a peer node of a peer-to-peer network restarts, other than the restarting peer node from the peer-to-peer network The configuration information is obtained on the other peer nodes; the restarted peer node completes the restart process according to the obtained configuration information. Preferably, the other peer nodes in the peer-to-peer network comprise: a boot node or an admission node of the restarted peer node. Further, the restarting peer node acquiring the configuration information from the boot node includes: the restarting peer node acquiring its cached boot node information; the restarting peer node selecting a boot node corresponding to the boot node information The restarting peer node sends a connectivity test request to the bootstrap node; after receiving the response message returned by the bootstrap node, the restarted peer node requests the boot node to obtain configuration information; the restarted pair The node receives the configuration information returned by the boot node. Further, the restarting peer node acquiring configuration information from the boot node includes: the restarting peer node acquiring its cached boot node information; the restarting peer node selecting a boot node corresponding to the boot node information; The restarting peer node sends a request message to the boot node, where the request message is used to request a connectivity test and request to obtain configuration information; the restarting peer node receives a response message returned by the boot node, where The response message carries configuration information. Further, when the configuration server of the peer-to-peer network updates its local configuration information, the method further includes: after updating the configuration information, the configuration server sends a notification message to all the guiding nodes in the peer-to-peer network, to notify that the configuration information has been updated; Each of the boot nodes that received the notification message requests updated configuration information from the configuration server; each of the boot nodes receives the updated configuration information returned by the configuration server, and updates the local configuration information using the received configuration information. Further, when the configuration server of the peer-to-peer network updates the local configuration information, the method further includes: after the configuration server updates the configuration information, sending the updated configuration information to each guiding node in the RELOAD peer-to-peer network; The boot node updates the local configuration information with the received configuration information. Further, the method further includes: the guiding node periodically acquiring configuration information from the configuration server of the peer-to-peer network according to a preset period, and updating the local configuration information by using the obtained configuration information. Further, the restarting peer node acquiring configuration information from the admission node includes: the restarting peer node acquiring its cached boot node information; the restarting peer node selecting a boot node corresponding to the boot node information The restarting peer node sends a connectivity test request to the bootstrap node; the restarted peer node receives a response message returned by the bootstrap node, The response message carries the node identifier of the access node of the restarted peer node; the restarted peer node is located at the node identifier of the admission node, and requests the admission node to obtain configuration information; The peer node receives the configuration information returned by the admission node. According to another aspect of the present invention, a peer-to-peer network is provided, comprising: a plurality of peer nodes, wherein: a plurality of peer nodes include: a restarted peer node and a peer node other than the restart Other peer nodes, wherein the restarting peer node is configured to obtain configuration information from the other peer nodes when restarting; other peer nodes are used to restart the peer node in the restart Provides configuration information for the restarted peer node. Preferably, the other peer nodes mentioned above include: a boot node or an access node of the restarted peer node. Further, the peer-to-peer network further includes: a configuration server, configured to send a notification to the guiding node when the local configuration information is tampered, so that the guiding node obtains the modified configuration information from the configuration server; or Send the modified configuration information to the boot node. With the present invention, when a peer node in the peer-to-peer network restarts, it does not acquire configuration information from the configuration server, but obtains configuration information from other peer nodes in the peer-to-peer network, and solves a large number of peer nodes. The problem of excessive configuration of the server caused by startup avoids the problem that the peer node fails to obtain configuration information when restarting, and improves service performance. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are set to illustrate,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, In the drawings: FIG. 1 is a schematic diagram of a RELOAD peer-to-peer network; FIG. 2 is a flowchart of a peer node restart in the prior art; FIG. 3 is a schematic diagram of a peer-to-peer network in an embodiment of the present invention; Figure 5 is a flowchart of a method for restarting a peer node according to an embodiment of the present invention; Figure 5 is a flowchart of Embodiment 1 of the present invention; Figure 7 is a flow chart of Embodiment 3 of the present invention; Figure 8 is a flow chart of Embodiment 4 of the present invention; Figure 9 is a flow chart of Embodiment 5 of the present invention; Figure 10 is a flow chart of Embodiment 6 of the present invention. BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, the present invention will be described in detail with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict. 3 is a schematic diagram of a peer-to-peer network in accordance with an embodiment of the present invention. As shown in FIG. 3, a peer-to-peer network according to an embodiment of the present invention includes a plurality of peer nodes and a configuration server, and is equivalent in the embodiment of the present invention. Among the plurality of peer nodes in the network, a peer node (in the embodiment of the present invention, in order to distinguish the peer node as a boot node), when restarting, no configuration information is obtained from the configuration server. The configuration information is obtained from other nodes in the peer-to-peer network. Therefore, in the embodiment of the present invention, the startup node is configured to acquire configuration information from other nodes of the peer-to-peer network when restarting; The node other than the startup node is configured to provide configuration information for the startup node when the startup node is restarted. With the peer-to-peer network of the embodiment of the present invention, when a peer node is restarted, configuration information may be obtained from other peer nodes in the peer-to-peer network, thereby reducing the burden on the configuration server, and because the peer node More data can also avoid the problem of failures only by obtaining configuration information from the configuration server, which in turn improves server performance. Preferably, the other peer nodes described above may be a boot node in the peer-to-peer network or an access node of the boot node. Specifically, when the startup node acquires the configuration information from the boot node, the startup node may select a boot node from the boot node corresponding to the cached boot node information, and send a connectivity test request to the boot node to test the boot node with the boot node. Connectivity, when the initiating node obtains configuration information from the boot node, the initiating node may first test connectivity with the boot node, and then obtain The configuration information may also be obtained by combining the two, that is, obtaining the configuration information from the boot node while performing the connectivity test. When the initiating node obtains configuration information from its admission node, when the initiating node performs connectivity testing with the instructing node, the instructing node returns the identification information (eg, node ID) of its admission node to the initiating node, and the initiating node according to the The identification information of the admission node acquires configuration information from its admission node. In addition, if the startup node obtains configuration information from the boot node, in order to make the configuration information in the boot node consistent with the configuration information on the configuration server, when the configuration information on the configuration server is modified, the configuration server may notify the boot node and then boot The node obtains the new configuration information from the configuration server. The configuration information can be directly sent to the boot node by the configuration server. Alternatively, the configuration information can be obtained from the configuration server by the boot node. Therefore, the configuration information of the boot node can be consistent with the configuration information on the configuration server. The method for restarting a peer node in the embodiment of the present invention is described below, and the method is implemented based on the peer-to-peer network described above. 4 is a flowchart of a method for restarting a peer node according to an embodiment of the present invention. As shown in FIG. 4, the method mainly includes the following steps (step S402 - step S404): Step S402, a peer node (for convenience) In the following description, the peer node is referred to as a boot node. When restarting, configuration information is obtained from other peer nodes other than the peer node in the current peer network; the other peer nodes mentioned above This includes but is not limited to: a bootstrap node of a peer-to-peer network or an approved access node of the peer node. Moreover, when the startup node obtains the configuration information from the boot node of the peer-to-peer network, in order to make the configuration information in the boot node consistent with the configuration information on the configuration server, when the configuration information on the configuration server is modified, the configuration server may notify The boot node, and then the boot node obtains new configuration information from the configuration server; the modified configuration information may be directly sent to the boot node by the configuration server; or the configuration information may be obtained from the configuration server by the boot node. Step S404, the process of starting the restart of the configuration information acquired by the node is completed. According to the method for restarting the peer node described above according to the embodiment of the present invention, the peer node may obtain configuration information from other peer nodes in the peer-to-peer network, thereby avoiding obtaining the configuration server. The configuration information is used to impose a heavier burden on the configuration server, and since the number of other peer nodes in the peer-to-peer network is relatively large, the single-point failure problem can be avoided and the service performance can be improved. The method for restarting the peer node provided by the embodiment of the present invention is described by using the RELOAD peer-to-peer network shown in FIG. 1 as an example. Embodiment 1 In this embodiment, the peer node A is restarted and added to the peer-to-peer network, and the peer node A locally caches the node information of the boot node (the peer node D in this embodiment). In this embodiment, peer node A is restarted as: Peer node A first tests connectivity with peer node D and obtains the node ID of the admission node; then obtains configuration information from peer node D and updates Local configuration. FIG. 5 is a flowchart of restarting the peer node A in the embodiment. As shown in FIG. 5, the peer node A restarting mainly includes the following steps: Step 501, the peer node A restarts; Step 502, The node A selects the peer node D from the boot node corresponding to the node information of the locally cached boot node; Step 503, the peer node A sends a connectivity test request to the boot node D, where the connectivity schedule request carries Node ID of the peer node A; Step 504, the boot node D searches for the corresponding admission node in the peer-to-peer network according to the node ID carried in the connectivity test request, and then returns the node ID of the admission node to Peer node A; Step 505, the peer node A requests the configuration information from the boot node D; Step 506, the boot node D returns the configuration information to the peer node A; Step 507, the peer node A uses the received configuration information to overwrite The local configuration information, that is, the local configuration is updated using the received configuration information; Step 508, the peer node A performs the remaining processes of joining the peer-to-peer network. Embodiment 2 In this embodiment, the peer node A is restarted and added to the peer-to-peer network, and the peer node A locally caches the node information of the boot node D. In this embodiment, the startup method of the peer node A is: peer-to-peer Node A sends a request to test connectivity with the bootstrap node D and obtains configuration information, and then bootstrap node D returns the node ID and configuration information of the access node of peer node A. FIG. 6 is a flowchart of restarting the peer node A in the embodiment. As shown in FIG. 6, the peer node A restarting mainly includes the following steps: Step 601, the peer node A is restarted; Step 602, The node A selects the node D from the boot node corresponding to the node information of the locally cached boot node; Step 603, the peer node A sends a connectivity test and a configuration request message to the boot node D, where the request message carries Node ID of the peer node A; Step 604, the node D searches for the node ID of the admission node corresponding to the node ID in the peer-to-peer network according to the node ID carried in the request message, and then the access node The node ID and the local configuration information are returned to the peer node A; Step 605, the peer node A overwrites the local configuration information with the received configuration information, that is, updates the local configuration; Step 606, the peer node A performs join peering The rest of the network. In the embodiment, in the embodiment, the peer node A is restarted and joins the peer-to-peer network, and the peer node A locally caches the node of the boot node D. In this embodiment, the peer node A startup method is: the peer node A first tests the connectivity with the bootstrap node D and obtains the node ID of its admission node (the peer node B in this embodiment); then obtains the configuration information from the admission node B and updates the local configuration. FIG. 7 is a flowchart of restarting the peer node A in the embodiment. As shown in FIG. 7, the peer node A restarting mainly includes the following steps: Step 4: 701, and the peer node A restarts; Step 702 The peer node A selects the peer node D from the boot node corresponding to the node information of the locally cached boot node; Step 703: The peer node A sends a connectivity test request to the guiding node D, where the connectivity test request carries the node ID of the peer node A. Step 704, the guiding node D is carried in the connectivity test request. Node ID, find the access node of the peer node A in the peer-to-peer network, and then return the node ID of the admission node B to the node A; Step 705, the node ID of the peer node A in the admission node B is accurate The ingress node B requests to obtain the configuration information; Step 706, the admission node B returns the local configuration information; Step 707, the peer node A uses the configuration information returned by the admission node B to overwrite the local configuration information, that is, update the local configuration; Peer node A performs the rest of the process of joining the peer-to-peer network. It should be noted that although the above embodiment is described by taking the configuration information of the peer node from the boot node or the admission node as an example, the present invention is not limited thereto. In the specific implementation process, the restarted peer node may also be removed. The boot node and other peer nodes other than the admission node obtain configuration information. For example, in the above embodiment, when the peer node A and the boot node D perform the connectivity test, the boot node D may return to the peer node A in addition to returning the node ID of the admission node B to the peer node A. The node ID of the node C, the peer node A can obtain the configuration information from the peer node C according to the node ID of the peer node C. In order to enable the joining node to obtain the latest configuration information, it is necessary to ensure that the boot node has the latest configuration, that is, the configuration of the boot node needs to be consistent with the configuration on the configuration server. In the following embodiments, a method of updating the configuration information of the bootstrap node in the embodiment of the present invention will be described. Embodiment 4 In this embodiment, after the configuration information is modified, the configuration server notifies the boot node D to update the configuration. FIG. 8 is a flowchart of the configuration of the configuration information of the boot node D in the embodiment. As shown in FIG. 8 , in the embodiment, the boot node D updates its configuration information mainly includes the following steps: Step 801: The configuration information on the configuration server is tampered with; Step 802: The configuration server extracts, from the configuration, the node identifiers of all the bootstrap nodes (in this embodiment, the peer node D) in the current peer-to-peer network; Step 803 The configuration server sends a configuration tamper notification to each boot node (node D in this embodiment); Step 804, the boot node D obtains the configuration from the configuration server through HTTP GET; Step 4 gathers 805, and the configuration server returns XML. The configuration file; Step 806, the boot node D overwrites the local configuration information by using the configuration information returned by the configuration server, and updates the local configuration. In this way, there is a new configuration on the boot node D, which provides the latest configuration information for the rejoining peer node. Embodiment 5 In this embodiment, the boot node D periodically acquires the latest configuration from the configuration server. In a specific application, the period in which the bootstrap node obtains the latest configuration information from the configuration server may be preset, and then, when each cycle arrives, the boot node is triggered to obtain the latest configuration information from the configuration server. In a specific implementation process, a timer may be set in the boot node to calculate a period, and the duration of the timer is a preset period duration. When the timer expires, the boot node obtains the latest configuration information from the configuration server. . FIG. 9 is a flowchart of the configuration information of the boot node in the embodiment. As shown in FIG. 9 , in the embodiment, the boot node D updates the configuration information, which mainly includes the following steps: Step 901 : Configure the server The configuration is falsified; Step 902, the timer of the configuration of the node D is triggered to be triggered; Step 903, the boot node D obtains the configuration from the configuration server by using HTTP GET; Step 904, the configuration server returns an XML configuration file to the boot node D; Step 905: The guiding node D overwrites the local configuration information by using the configuration information returned by the configuration server, and updates the local configuration. In this way, the latest configuration information is available on the boot node D, so that the latest configuration information can be provided for the rejoined peer node. In a specific application, if there are multiple boot nodes in the peer-to-peer network, when the configuration information of the configuration server is modified, the timers for obtaining the configuration of each boot node are triggered, and each boot node acquires a new one from the configuration server. Configuration information. It should be noted that, when the configuration node obtains the configuration information from the configuration server at the timing of the foregoing embodiment, the obtained configuration information is higher than the version of the locally saved configuration information. In an actual application, the boot node acquires the configuration from the configuration server at a timing. When the information is used, the configuration information of the configuration server may be the same as the configuration information of the boot node. In the specific implementation process, there may be two ways of processing. One is that when the configuration node obtains the configuration information from the configuration server, it does not determine whether the version of the configuration information of the configuration server is higher than the local one, but obtains the judgment after the acquisition. If the version of the obtained configuration information is higher than the local one, the local configuration information is updated with the obtained configuration information; otherwise, the local configuration information is not updated; another processing method is before the boot node obtains the configuration information from the configuration server. First, obtain the version information of the configuration information on the configuration server, and compare whether the configuration information on the configuration server is higher than the version of the local configuration information. If yes, obtain the configuration information from the configuration server. Otherwise, the configuration information is not obtained from the configuration server. Configuration information, waiting for the next timer to expire, then obtain version information from the configuration server for comparison. Embodiment 6 In this embodiment, after the configuration information in the configuration server is tampered with, the server is configured to actively send to each of the guiding nodes (in the present embodiment, the guiding node D) in the peer-to-peer network. The latest configuration information. 10 is a flowchart of the configuration information update of the boot node in the embodiment. As shown in FIG. 10, in the embodiment, the configuration information update of the boot node mainly includes the following steps: Step 4: 101, configured on the server The configuration is tampered with; Step 102, the configuration server takes out the node information of all the boot nodes (in this embodiment, the boot node D) from the configuration; Step 103, configures the server to each boot node (in this embodiment, the boot Node D) sends a configuration update request, where the configuration update request carries new configuration information; Step 104: After receiving the new configuration information, the guiding node D overwrites the local configuration information with the new configuration information, and updates the local configuration. In step 4, the guiding node D returns a configuration update response to the configuration server. In this way, the latest configuration information is available on the boot node D, so that the latest configuration information can be provided for the rejoined peer node. From the above description, it can be seen that in the embodiment of the present invention, when a peer node in the peer-to-peer network restarts, it does not acquire configuration information from the configuration server, but from other peers in the peer-to-peer network. The configuration information is obtained in the node, which solves the problem that the burden on the configuration server is too large when the peer node is restarted, thereby avoiding the problem that the peer node fails to obtain the configuration information when restarting, and improving the service performance. In addition, in the embodiment of the present invention, when the configuration information in the configuration server is changed, the configuration information of the boot node in the peer-to-peer network is updated by using the configuration information in the configuration server, so that the boot node can be a rejoined pair. The nodes provide the latest configuration information. Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. The steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps are fabricated as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software. The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the scope of the present invention are intended to be included within the scope of the present invention.

Claims

A method for restarting a peer node, characterized in that it comprises:

When a peer node in the peer-to-peer network restarts, obtain configuration information from other peer nodes other than the restarted peer node in the peer-to-peer network; the restarting peer node resides The obtained configuration information completes the process of restarting.

2. The method of claim 1, wherein the other peer nodes in the peer to peer network comprise: a bootstrap node or an admission node of the restarted peer node.

The method according to claim 2, wherein the restarting the peer node acquiring the configuration information from the guiding node comprises:

The restarting peer node acquires its cached boot node information; the restarted peer node selects a boot node corresponding to the boot node information;

The restarting peer node sends a connectivity test request to the boot node; after receiving the response message returned by the boot node, the restarted peer node requests the boot node to acquire the configuration information. ;

The restarted peer node receives the configuration information returned by the bootstrap node.

The method according to claim 2, wherein the restarting the peer node acquiring the configuration information from the boot node comprises:

The restarting peer node sends a request message to the bootstrap node, where the request message is used to request a connectivity test and request to obtain the configuration information; the restarted peer node receives the guide The response message returned by the node, where the response message carries the configuration information. The method according to claim 3 or 4, wherein, when the configuration server of the peer-to-peer network updates its local configuration information, the method further includes:

After updating the configuration information, the configuration server sends a notification message to all the guiding nodes in the peer-to-peer network to notify that the configuration information has been updated;

And each of the guiding nodes that received the notification message requests the updated configuration information from the configuration server;

Each of the boot nodes receives the updated configuration information returned by the configuration server, and updates the local configuration information using the received configuration information. The method according to claim 3 or 4, wherein, when the configuration server of the peer-to-peer network updates the local configuration information, the method further includes:

After the configuration server updates the configuration information, the configuration server sends the updated configuration information to each of the guiding nodes in the peer-to-peer network;

The respective bootstrap nodes update the local configuration information using the received configuration information. The method according to claim 3 or 4, wherein the method further comprises: the guiding node periodically acquiring configuration information from the configuration server of the RELOAD peer network according to a preset period, and using the configuration information. The obtained configuration information updates the local configuration information. The method according to claim 2, wherein the restarting the peer node acquiring the configuration information from the admission node comprises:

The restarting peer node sends a connectivity test request to the boot node; the restarting peer node receives a response message returned by the boot node, where the response message carries the restart The node identifier of the admission node of the peer node;

And the restarting peer node is located at the node identifier of the admission node, and requests the access node to acquire the configuration information; The restarted peer node receives the configuration information returned by the admission node.

9. A peer-to-peer network comprising a plurality of peer nodes, wherein the plurality of peer nodes comprise: a restarting peer node and other peers other than the restarted peer node Node, where,

The restarting peer node is configured to acquire configuration information from the other peer nodes when restarting;

The other peer node is configured to provide the configuration information for the restarted peer node when the restarted peer node is restarted.

10. The peer to peer network of claim 9, wherein the other peer nodes comprise: a boot node or an admission node of the restarted peer node.

11. The peer-to-peer network of claim 10, wherein the peer-to-peer network further comprises: a configuration server,

The configuration server is configured to send a notification to the guiding node when the local configuration information is modified, so that the guiding node obtains the modified configuration information from the configuration server; or

The configuration server is configured to send the modified configuration information to the boot node.