CN114301866A

CN114301866A - Alliance-link communication method, system, electronic device and readable storage medium

Info

Publication number: CN114301866A
Application number: CN202111603846.0A
Authority: CN
Inventors: 尚璇; 胡麦芳; 陶媛; 黄方蕾; 张珂杰
Original assignee: Hangzhou Qulian Technology Co Ltd
Current assignee: Hangzhou Qulian Technology Co Ltd
Priority date: 2021-12-24
Filing date: 2021-12-24
Publication date: 2022-04-08

Abstract

The application is applicable to the technical field of block chains, and provides a alliance chain communication method, a system, an electronic device and a readable storage medium. The method comprises the following steps: acquiring first address information, wherein the first address information comprises an address of a first node in at least one network domain, the first node is positioned in the first network domain, and the first address information at least comprises the address of the first node in the first network domain; sending the first address information to the second node through a first connection with the second node; the second node is located in a second network domain; and receiving second address information from the second node through the first connection, wherein the second address information comprises addresses of the second node under one or more network domains, and the second address information at least comprises the addresses of the second node under the second network domain. The method can meet the requirement that users in the alliance chain map internal and external websites of the nodes in a proxy mode to carry out internal and external network communication.

Description

Alliance-link communication method, system, electronic device and readable storage medium

Technical Field

The present application relates to the field of block chain technologies, and in particular, to a method, a system, an electronic device, and a readable storage medium for alliance chain communication.

Background

A federation blockchain, referred to as a federation chain for short, is one of the blockchains. The federation chain is only for members of a certain group and limited third parties, and a plurality of preselected nodes are internally designated as billers, and the generation of each block is jointly determined by all the preselected nodes.

The alliance chain needs to perform cross-domain communication in the application process. In the related art, the cross-domain communication of the alliance chain is mainly realized by a NAT (Network Address Translation) penetration technology. However, the NAT traversal technology has the problem of low security, and thus, organizations corresponding to some nodes in the federation chain want to communicate with the outside world in a proxy manner. Therefore, research on related technologies of communication in a federation chain using a proxy mode is necessary to meet the needs of users.

Disclosure of Invention

The application provides a alliance chain communication method, device and system, electronic equipment and a computer readable storage medium, which can meet the requirement that users in alliance chains communicate with the outside in an agent mode.

In a first aspect, an embodiment of the present application provides a federation chain communication method, including: acquiring first address information, wherein the first address information comprises an address of a first node in at least one network domain, the first node is positioned in the first network domain, and the first address information at least comprises the address of the first node in the first network domain; sending the first address information to the second node through a first connection with the second node; the second node is located in a second network domain; and receiving second address information from the second node through the first connection, wherein the second address information comprises addresses of the second node under one or more network domains, and the second address information at least comprises the addresses of the second node under the second network domain.

The execution subject of the federation chain communication method provided by the first aspect may be the first node, or a device in the first node, such as a chip or a processing circuit.

Optionally, the first address information may be a network domain address list, which corresponds to the first network domain address list in the specific implementation.

Optionally, the second address information may be a network domain address list, which corresponds to the second network domain address list in the specific implementation.

Optionally, in this embodiment of the present application, the address may be, but is not limited to, an Internet Protocol (IP) address.

In this embodiment, the address of the node under the network domain refers to an address of the node for the node in the network domain to communicate with, for example, the address of the first node under the first network domain refers to an address of the first node for the node in the first network domain to communicate with.

In one embodiment, the method further comprises: and sending first prompt information to the second node when the address of the second node under the first network domain is not included in the second address information, wherein the first prompt information is used for prompting the second node to print a first warning log, and the first warning log is used for representing that the address of the second node under the first network domain is not included in the second address information.

In one embodiment, the method further comprises: sending second prompt information to the second node under the condition that the second address information comprises the address of the second node under the first network domain and the address of the second node under the first network domain cannot be communicated; the second prompt message is used for prompting the second node to print a second warning log, and the second warning log is used for representing that the address of the second node under the first network domain is not communicable.

In one embodiment, the method further comprises: receiving a list modification instruction; and modifying the first address information according to the list modification instruction, and sending the list modification instruction to the neighbor node of the first node.

Optionally, the first node may send the list modification instruction to the neighbor nodes of the first node by one or more of broadcasting, multicasting or unicasting.

In one embodiment, the remote address list of the first node includes an address of the second node, and before receiving second address information from the second node over the first connection, the method further includes: and establishing a first connection with the second node according to the address of the second node.

In a second aspect, an embodiment of the present application provides a federation chain communication method, including: acquiring second address information, wherein the second address information comprises addresses of second nodes in one or more network domains, and the second nodes are positioned in the second network domain; the second address information at least comprises the address of the second node under the second network domain; sending the second address information to the first node through a first connection with the first node; the first node is located in a first network domain; receiving first address information from a first node, wherein the first address information comprises an address of the first node under at least one network domain, and the first address information at least comprises the address of the first node under the first network domain.

The second aspect provides that the execution subject of the federation chain communication method may be the second node, or a device in the second node, such as a chip or a processing circuit.

In one embodiment, before the connection initiator of the first connection is the first node and acquires the second address information, the method further includes: receiving an address of a second node from the first node; obtaining second address information, comprising: acquiring original second address information; and under the condition that the original second address information does not comprise the address of the second node in the first network domain, writing the address of the second node serving as the address of the second node in the first network domain into the original second address information to obtain second address information.

In one embodiment, the method further comprises: and sending third prompt information to the first node under the condition that the address of the first node under the second network domain is not included in the first address information, wherein the third prompt information is used for prompting the first node to print a third warning log, and the third warning log is used for representing that the address of the first node under the second network domain is not included in the first address information.

In one embodiment, the method further comprises: and sending fourth prompting information to the first node under the condition that the first address information comprises the address of the first node under the second network domain and the address of the first node under the second network domain is not communicable, wherein the fourth prompting information is used for prompting the first node to print a fourth warning log, and the fourth warning log is used for representing that the address of the first node under the second network domain is not communicable.

In one embodiment, the method further comprises: receiving a list modification instruction from a first node; modifying the first address information according to the list modification instruction and/or performing a modify join operation.

In one embodiment, the list modification instruction comprises a first modification instruction for instructing to add an address of the first node under the first target domain in the first address information; modifying the first address information according to the list modification instruction and/or performing a modify join operation, comprising: according to the first modification instruction, the address of the first node under the first target domain is added in the first address information.

In one embodiment, the second node is located in a second target domain, and the list modification instruction includes a second modification instruction for instructing to delete the address of the first node under the second target domain in the first address information; modifying the first address information according to the list modification instruction and/or performing a modify join operation, comprising: and according to the second modification instruction, disconnecting the first node.

In one embodiment, the second node is located in a third target domain, and the list modification instruction includes a third modification instruction, where the third modification instruction is used to indicate that the address of the first node in the first address information under the third target domain is updated to be a target address; modifying the first address information according to the list modification instruction and/or performing a modify join operation, comprising: and according to the third modification instruction, disconnecting the first node, and reestablishing the connection with the first node according to the target address.

In a third aspect, an embodiment of the present application provides a alliance-chain communication device, which may be a first node, and may also be a device (such as a chip or a processing circuit) applied in the first node, where the alliance-chain communication device includes:

the first obtaining module is used for obtaining first address information, the first address information comprises an address of a first node under at least one network domain, the first node is located in the first network domain, and the first address information at least comprises the address of the first node under the first network domain;

the first sending module is used for sending the first address information to the second node through the first connection between the first sending module and the second node; the second node is located in a second network domain;

the first receiving module is used for receiving second address information from the second node through the first connection, the second address information comprises addresses of the second node under one or more network domains, and the second address information at least comprises the addresses of the second node under the second network domain.

In a fourth aspect, the present disclosure provides a alliance-chain communication device, which may be a second node, or a device (such as a chip or a processing circuit) applied in the second node,

the second obtaining module is used for obtaining second address information, the second address information comprises addresses of second nodes in one or more network domains, and the second nodes are located in the second network domain; the second address information at least comprises the address of the second node under the second network domain;

the second sending module is used for sending the second address information to the first node through the first connection with the first node; the first node is located in a first network domain;

the second receiving module is configured to receive first address information from the first node, where the first address information includes an address of the first node in at least one network domain, and the first address information includes at least an address of the first node in the first network domain.

In a fifth aspect, an embodiment of the present application provides a alliance-link communication system, including: a first node for performing the method of any of the above first aspects and a second node for performing the method of any of the above second aspects.

In a sixth aspect, an embodiment of the present application provides a computer device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, the processor implementing the federation chain communication method of any one of the first aspects described above when executing the computer program or the federation chain communication method of any one of the second aspects described above.

In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, where a computer program is stored, and when executed by a processor, the computer program implements the federation chain communication method of any one of the above first aspects, or implements the federation chain communication method of any one of the above second aspects.

The alliance-link communication method, device, system, electronic device and computer readable storage medium provided by the application are provided, wherein the first address information comprises addresses of the first node under at least one network domain, and the second address information comprises addresses of the second node under one or more network domains. That is to say, the federation chain communication method, apparatus, system, electronic device, and computer-readable storage medium provided in the embodiments of the present application may use multiple addresses to communicate with different domains, and it is not necessary to specify that only one address is used by one node, so that networking of a federation chain is more flexible, and it can be satisfied that a user uses a proxy mode to map internal and external websites of a node in the federation chain to perform internal and external network communication, thereby improving user experience. In addition, the alliance chain communication method, the device, the system, the electronic equipment and the computer readable storage medium exchange the network domain address list, so that each node in the communication system can store the network domain address list of the node and each neighbor node of the node, and each node can acquire the address communicated with the neighbor node, thereby facilitating the nodes to realize node communication management, node self-discovery, path planning in a network forwarding process and the like in the subsequent communication process, further facilitating the realization of communication in an alliance chain by using an agent mode, meeting the requirements of users and further improving the user experience.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.

FIG. 1 is a network topology diagram of a federated chain communication system as provided by an embodiment of the present application;

FIG. 2 is a flowchart illustrating a method for federation chain communication according to an embodiment of the present application;

FIG. 3 is a flow diagram illustrating a method for federation chain communication as provided by another embodiment of the present application;

FIG. 4 is a flowchart illustrating a method for federation chain communication as provided by yet another embodiment of the present application;

FIG. 5 is a flowchart illustrating a method for federation chain communication as provided by yet another embodiment of the present application;

FIG. 6 is a diagram illustrating a process for dynamically modifying a network domain address list according to an embodiment of the present application;

FIG. 7 is a block diagram illustrating a federated link communications device according to an embodiment of the present application;

FIG. 8 is a block diagram of a federated chain communication device as provided in another embodiment of the present application;

fig. 9 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.

It is to be understood that the terms "first," "second," "third," "fourth," and the like (if any) in the embodiments of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order.

It is understood that the term "and/or" as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.

Before explaining the embodiments of the present application in detail, an application scenario of the embodiments of the present application will be described.

The method provided by the embodiment of the application can be applied to a alliance chain communication system, the application scenario of the alliance chain communication system includes but is not limited to commodity source tracing, public welfare charity, supply chain finance, e-government affairs, mutual insurance or internet of things, and the like, and the application is not limited in any way.

Fig. 1 is a network topology diagram of an exemplary alliance-link communication system (hereinafter, referred to as a communication system) according to an embodiment of the present disclosure. As shown in fig. 1, the communication system includes a plurality of network domains, and each network domain is provided with at least one block chain node (hereinafter, referred to as a node). Optionally, the node according to the embodiment of the present application corresponds to each enterprise in the federation chain system, and may be a server or a terminal.

The concepts and definitions referred to in the embodiments of the present application are as follows:

cross-domain communication: communication between nodes in different network domains. Such as node 1 and node 2 in fig. 1.

And (3) neighbor nodes: a node having a neighbor relation with a certain node is referred to as a neighbor node of the node. As in fig. 1, the neighbor nodes of node 1 include node 2, node 4, and node 5; the neighbor nodes of node 2 include node 1, node 3, and node 5.

The method comprises the following steps: the domain in which a certain node is located is called the local domain of the node.

Correlation domain: for a certain node, the network domain of the non-local domain where the neighbor nodes of the node exist is called the relevant domain of the node. As in fig. 1, the associated domain of node 1 comprises a second network domain, the associated domain of node 2 comprises a first network domain and a third network domain, and the associated domain of node 3 comprises a first network domain and a second network domain.

As shown in FIG. 1, a federation chain involves cross-domain communications during an application. In the related art, cross-domain communication is mainly realized through a NAT traversal technology. However, due to the particularity of the federation chain, some enterprises in the federation chain have higher requirements on network security, and therefore, the enterprises want to communicate with the outside (other network domains) in a proxy manner, that is, to map the internal and external network addresses of nodes in a proxy manner for intranet and extranet communication, so as to hide the internal IP address of the enterprise. Thus, it may happen that an organization has different IP addresses for connections to the organizations in different network domains, especially when using reverse proxies. That is, in a communication system, a node may have multiple IP addresses for communication with nodes in multiple network domains at the same time. For example, node 1 in fig. 1 has an IP address a for nodes in a first network domain to communicate with and an IP address B for nodes in a second network domain to communicate with.

At present, a plurality of alliance chains do not consider the situation that enterprises need to communicate in a proxy mode, so that research on communication among nodes in the alliance chains needs to be conducted according to the requirement of users so as to meet the requirement of the users. The embodiment of the application aims to research a method for alliance link communication in the scene, and particularly researches a processing process of an IP address of a node in a communication process.

The technical solution in the present application will be described in detail with reference to fig. 1. It should be noted that, in the present application, different technical features may be combined with each other without conflict.

Fig. 2 shows a schematic flow chart of a method of federation chain communication as provided herein. As shown in fig. 2, the federation chain communication method provided in this embodiment may include:

s101, a first connection is established between a node 1 and a node 2, wherein the node 1 is located in a first network domain, and the node 2 is located in a second network domain.

In the first connection, one of the node 1 and the node 2 is a node initiator node, and the other is a node receiver. An initiator node (or called a connection initiator) is a party sending a connection request in two nodes, and a receiver node (or called a connection receiver) is a party receiving and responding to the connection request in the two nodes. It should be noted that, during the connection process of two nodes, a node connection collision may occur, that is, two nodes simultaneously initiate a connection request to each other. When node connection collision occurs, according to a preset rule, one of the two nodes gives up the connection request and receives the connection request sent by the opposite node, so that connection is established. The initiator node in the embodiment of the application refers to one of the two nodes which initiates a connection request and successfully establishes a connection; correspondingly, the receiving node is a party of the two nodes which receives and responds to the connection request and successfully establishes the connection.

For convenience of description, in the following embodiments, the node 1 is taken as a node initiator, and the node 2 is taken as a node receiver.

Optionally, the node 1 may initiate a connection request to the node 2 according to an IP address (hereinafter, referred to as a second IP address) of the node 2 in a remote address (remote address) list of the node 1. The list of remote addresses for node 1 may be user configurable.

Specifically, the user may configure the proxy node of the node 2 to obtain a second IP address that can be connected to the node 1, and configure the second IP address in the remote address list of the node 1. After the user completes configuration and starts the node, the node 1 initiates connection to the node 2 according to the second IP address in the remote address list, so as to establish the first connection.

It should be noted that, according to different actual use requirements, the IP address related to the embodiment of the present application may be an IP address provided by a proxy (including a forward proxy and a reverse proxy) node, and may also be an IP address provided by a NAT gateway.

S102, the node 1 acquires a first network domain address list; the first network domain address list is used for characterizing the IP address of the node 1 under at least one network domain, and the first network domain address list at least comprises the IP address of the node 1 under the first network domain.

In the embodiment of the present application, an IP address of a node in a network domain refers to an IP address of the node for a node in the network domain to communicatively connect. For example, the IP address a of the node 1 under the first network domain refers to an IP address of the node 1 for the nodes in the first network domain to communicatively connect. In other words, the node in the first network domain is communicatively connected to the node 1 via the IP address a.

Specifically, the first network domain address list includes the IP address of the node 1 in the first network domain, that is, the first network domain address list includes the IP address of the node 1 in its own domain. In addition, the first network domain address list may further include IP addresses of the node 1 in other network domains, for example, an IP address of the node 1 in a domain related to the node 1 is included, so that each neighbor node in the domain related to the node 1 is connected to the node 1. Meanwhile, in the first network domain address list, each network domain corresponds to one IP address.

Referring to fig. 1, a node 1 is located in a first network domain, and the associated domain of the node 1 includes a second network domain. The first network domain address list includes the IP address of node 1 under the first network domain. In addition, the first network domain address list may further include an IP address of the node 1 in the second network domain. For example, the first network domain address list may be: { domain1:10.10.1.1:50011, domain2:117.10.11.1:50012 }. Where domain1 represents a first network domain and domain2 represents a second network domain. That is, node 1 provides the node 4 connection in the first network domain with an IP address of 10.10.1.1:50011, and node 1 provides the node 2 and node 5 connections in the second network domain with an IP address of 117.10.11.1: 50012.

S103, the node 1 sends the first network domain address list to the node 2 based on the first connection.

It will be appreciated that the node 1 may also store the first network domain address list in the memory of the node 1 at the same time as sending the first network domain address list.

S104, the node 2 receives and stores the first network domain address list.

S105, the node 2 acquires a second network domain address list; the second network domain address list is used for characterizing the IP address of the node 2 under at least one network domain, and the second network domain address list at least comprises the IP address of the node 2 under the second network domain.

Similar to the first network domain address list, the second network domain address list includes the IP address of the node 2 in the second network domain, i.e., the second network domain address list includes the IP address of the node 2 in its own domain. In addition, the second network domain address list may further include IP addresses of the node 2 in other network domains, for example, an IP address of the node 2 in a domain related to the node 2 is included, so that each neighbor node in the domain related to the node 2 is connected to the node 2. Meanwhile, in the second network domain address list, each network domain corresponds to one IP address.

Referring to fig. 1, a node 2 is located in a second network domain, and related domains of the node 2 include a first network domain and a third network domain. The second network domain address list includes the IP address of node 2 under the second network domain. In addition, the second network domain address list may further include an IP address of the node 2 under the first network domain and/or an IP address of the node 2 under the third network domain. For example, the second network domain address list may be: { domain1:117.11.10.2:50012, domain2:10.10.1.2:50012, domain3:117.11.10.3:50012 }. Where domain1 represents a first network domain, domain2 represents a second network domain, and domain3 represents a third network domain. That is, node 2 provides node 1 connection in the first network domain with an IP address of 117.11.10.2:50012, node 2 provides node 5 connection in the second network domain with an IP address of 10.10.1.2:50012, and node 2 provides node 3 connection in the third network domain with an IP address of 117.11.10.3: 50012.

S106, the node 2 sends the second network domain address list to the node 1 based on the first connection.

It will be appreciated that the node 2 may also store the second network domain address list in the memory of the node 2 at the same time as sending the second network domain address list.

S107, the node 1 receives and stores the second network domain address list.

Through the above procedure, node 1 exchanges network domain address lists with node 2. Thus, both node 1 and node 2 have a first network domain address list and a second network domain address list stored therein.

In the process, for each node, a plurality of IP addresses can be used for communicating with different domains, and one node does not need to be appointed to use only one IP address, so that the networking of the alliance chain is more flexible, the requirement that a user uses an agent mode to map internal and external websites of the node in the alliance chain for internal and external network communication can be met, and the user experience is improved.

The above is the process of exchanging the network domain address list by the node 1 and the node 2. It is understood that any two nodes in the communication system having a neighbor relation can exchange their respective network domain address lists through the above-described process. Therefore, each node in the communication system can store the network domain address lists of the node and each neighbor node of the node, so that each node can acquire the IP address communicated with the neighbor node, and thus, each node can conveniently realize node communication management (such as disconnection and reconnection between nodes) in the subsequent communication process, self-discovery of the node, path planning in the network forwarding process (or called network forwarding of data) and the like, and further, the purpose of mapping internal and external network addresses of the node by using an agent mode in a alliance chain to perform internal and external network communication is conveniently realized, the requirements of users are met, and the user experience is further improved.

Taking the application of the network domain address list to the forwarding network as an example, please continue to refer to fig. 1. If the node 1 needs to send data to the node 3, the node 1 may send the data to the node 4, and the node 4 forwards the data to the node 3; alternatively, node 1 may send the data to node 2, with node 2 forwarding the data to node 3. Taking the first forwarding method as an example, the node 1 may know the IP address of the node 4 in the first network domain (assumed to be IP4) according to the network domain address list of the node 4 stored by the node 1. In addition, the node 4 stores a network domain address list of the node 3, and the node 4 can acquire an IP address (assumed to be IP3) of the node 3 in the first network domain from the network domain address list of the node 3. Assume that the IP address of node 1 is IP 1. The node 4 sends the IP address of the node 3 in the first network domain to the node 1, and the node 1 plans a data forwarding path according to the IP address as follows: IP1 → IP4 → IP 3.

Therefore, each node in the communication system can store the network domain address lists of the respective node and the adjacent node by exchanging the network domain address lists, so that the forwarding network is realized when the internal and external network addresses of the nodes are mapped by using a proxy mode in a alliance chain to carry out internal and external network communication, and the user experience is improved.

It should be noted that, the above is only an example of a part of the network domain address list applied in the process of alliance-link network communication, in addition, the network domain address list may also have more and wider applications, and the application is not limited in this respect.

In one embodiment, when the node 1 is an initiator node in the first connection and the node 2 is a receiver node in the first connection, the IP address of the node 2 in the second network domain address list under the first network domain may also be obtained by dynamic write back. Specifically, the node 1 sends the first network domain address list to the node 2, and simultaneously sends the second IP address in the remote address list to the node 2. Based on this, referring to fig. 3, step S104, the node 2 acquires the second network domain address list, which specifically includes:

s1041, the node 2 obtains the original second network domain address list.

Optionally, the original second network domain address list may include the IP address of the node 2 under the first network domain. Optionally, the IP address of the node 2 in the first network domain may not be included in the original second network domain address list, possibly due to a reason that the user is not configured.

S1042, the node 2 judges whether the original second network domain address list comprises the IP address of the node 2 in the first network domain;

if yes, executing step S1043;

if not, executing step S1044;

and S1043, taking the original second network domain address list as a second network domain address list.

S1044, writing the second IP address serving as the IP address of the node 2 in the first network domain into an original second network domain address list to obtain a second network domain address list.

It is understood that since the node 1 establishes the connection with the node 2 through the second IP address, the second IP address is for the node 1 under the first network domain to connect to, and the second IP address can be used as the IP address of the node 2 under the first network domain.

For example, assume that the remote address list of node 1 configures the IP address (i.e., the second IP address) of node 2 as 117.11.10.2:50012, and the original second network domain address list of node 2 is: { domain2:10.10.1.2:50012 }. If the node 2 judges that the original second network domain address list does not include the IP address of the node 2 in the first network domain, the node 2 writes the second IP address into the original second network domain address list, and the final second network domain address list is obtained as follows: { domain1:117.11.10.2:50012, domain2:10.10.1.2:50012 }.

In this embodiment, for the receiver node, the network domain address list is obtained through dynamic write back. Therefore, for the network domain and the node which are missed to be configured by the user or newly added in the communication system, the network domain address list can be obtained without the need of the user to perform configuration, so that the configuration process of the user can be simplified, and the user experience is further improved.

In one embodiment, after the node 1 and the node 2 exchange the network domain address lists, the node 1 and the node 2 may check the network domain address lists of each other, respectively. Specifically, as shown in fig. 4, the method may further include:

s1081, the node 1 determines whether the second network domain address list includes an IP address of the node 2 in the first network domain;

if not, executing step S1082;

if yes, go to step S1084.

S1082, the node 1 sends, to the node 2, first prompt information based on the first connection, where the first prompt information is used to prompt the node 2 to print a first warning log (warninglog).

S1083, the node 2 receives the first prompt information, and prints a first warning log according to the first prompt information, where the first warning log is used to prompt the user that the second network domain address list does not include the IP address of the node 2 in the first network domain.

By generating the first warning log, the user can know that the IP address of the node 2 in the first network domain is not included in the second network domain address list, so that the user can configure the IP address or perform other operations as required. The realization mode increases the interaction between the node and the user, and is convenient for the user to know the condition of the network domain address list, thereby being convenient for the user to perfect the second network domain address list, further better realizing the subsequent communication and further improving the user experience.

S1084, the node 1 determines whether the IP address of the node 2 in the first network domain can communicate;

if yes, ending the process;

if not, go to step S1085.

Specifically, if the IP address of the node 2 in the first network domain exists in the second network domain address list, the node 1 may initiate a connection request to the IP address, and determine whether to implement communication with the node 2 through the IP address. If a response or feedback of the other party is received after the connection request is initiated, the node 1 determines that the IP address is communicable. Otherwise, node 1 determines that the IP address is not communicable.

S1085, the node 1 sends second prompt information to the node 2, and the second prompt information is used for prompting the node 2 to print a second warning log.

S1086, the node 2 receives the second prompt information, and prints a second warning log according to the second prompt information, where the second warning log is used to prompt that the IP address of the user node 2 in the first network domain is not communicable.

By generating the second warning log, the user can know that the IP address of the node 2 in the first network domain is not communicable, and there may be a configuration error or a connection problem, so that the user can modify or check the connection of the IP address as required. The realization mode increases the interaction between the node and the user, and ensures the correctness of the address list of the second network domain, thereby ensuring the accuracy and reliability of the alliance link communication and further improving the user experience.

Meanwhile, the node 2 may also check the first network domain list sent by the node 1, and the specific process is similar to the process in which the node 1 checks the second network domain address list, and includes:

node 2 determines whether the IP address of node 1 under the second network domain is included in the first network domain address list.

If the first network domain address list does not include the IP address of the node 1 in the second network domain, then: the node 2 sends third prompt information to the node 1 based on the first connection, wherein the third prompt information is used for prompting the node 1 to print a third warning log; and the node 2 receives the third prompt message and prints a third warning log according to the third prompt message, wherein the third warning log is used for prompting the user that the IP address of the node 1 in the second network domain is not included in the first network domain address list.

If the first network domain address list includes the IP address of the node 1 under the second network domain, the node 2 determines whether the IP address of the node 1 under the second network domain is communicable.

If the node 2 determines that the IP address of the node 1 in the second network domain can be communicated, the process is ended; if the node 2 determines that the IP address of the node 1 in the second network domain is not communicable, the node 2 sends fourth prompt information to the node 1, wherein the fourth prompt information is used for prompting the node 1 to print a fourth warning log; and the node 1 receives the fourth prompt message and prints a fourth warning log according to the fourth prompt message, wherein the fourth warning log is used for prompting the user that the IP address of the node 1 under the second network domain cannot communicate.

The specific process and beneficial effects of the node 2 checking the first network domain address list refer to the node 1 checking the second network domain address list, which is not described herein again.

In one embodiment, when a new mechanism (i.e. a node in a certain network domain) joins the communication system, or a mechanism leaves the communication system, or an IP address of a node in one or several network domains is configured incorrectly or is configured missing, or the like, the relevant node in the communication system may dynamically modify the network domain address list based on the modification instruction of the user, and update the connection status of the node in the network, i.e. manage the node communication. Specifically, please refer to fig. 5, which illustrates an example that the node 1 in the communication system receives the modification command. As shown in fig. 5, the federation chain communication method may further include:

s1091, receiving a list modification instruction input by a user by a node 1; the list modification instruction is to indicate a modification of the first network domain address list.

Optionally, the list modification instruction may include modification type and modification information. The modification type may be addition, update or deletion. The modification information may include a network domain name, an IP address, etc. to be modified.

The application scenario of the list modification instruction (which may be referred to as a first modification instruction) with the modification type of "new" may be, for example: based on the third warning log in the above embodiment, the user sends a list modification instruction to the node 1, the list modification instruction being used to instruct to add the IP address of the node 1 in the second network domain to the first network domain address list. Or, a node under a new network domain C is newly added to the communication system, and the node is a neighbor node of the node 1, then, the user sends a list modification instruction to the node 1, where the list modification instruction is used to instruct to add the IP address of the node 1 under the new network domain C to the first network domain address list.

The application scenario of the list modification instruction (which may be referred to as a third modification instruction) whose modification type is "update" may be, for example: based on the fourth warning log in the above embodiment, the user sends a list modification instruction to the node 1, where the list modification instruction is used to instruct to update the IP address of the node 1 in the first network domain address list under the second network domain to a new IP address.

The application scenario of the list modification instruction (which may be referred to as a second modification instruction) whose modification type is "delete" may be, for example: and each node under a certain network domain D is not connected with the node 1 any more, the user sends a list modification instruction to the node 1, and the list modification instruction is used for indicating to delete the IP address of the node 1 under the network domain D in the first network domain address list.

Alternatively, the modification type may be indicated by adding character information after the modification information, for example, "-I" indicates addition, "-U" indicates update, and "-D" indicates deletion. Of course, the modification type can also be expressed in other ways, such as: { update: { domain2:117.11.10.1:50011} } denotes that the IP address under the second network domain is updated to 117.11.10.1: 50011. The embodiment of the present application does not limit the modification type and the specific form of the list modification instruction.

S1092, the node 1 modifies the first network domain address list based on the list modification instruction, and broadcasts the modification instruction to the neighbor nodes of the node 1.

As described in the foregoing embodiment, the network domain address lists are exchanged between the node 1 and each neighboring node of the node 1, so that each node stores the network domain address lists of the node and each neighboring node of the node. After the node 1 modifies the first network domain address list stored in the node, it needs to further inform each neighboring node of the list modification instruction, so that the neighboring node synchronously updates the first network domain address list.

S1093, each neighbor node of the node 1 modifies the first network domain address list stored in the neighbor node based on the list modification instruction.

Illustratively, fig. 6 shows a schematic diagram of a process for dynamically modifying a network domain address list. Continuing with the example of the network topology of fig. 1 in fig. 6, the node 1 receives a list modification instruction of a user, modifies the first network domain address list, and further broadcasts the modification instruction to the neighboring nodes of the node 1: node 2, node 4 and node 5. Node 2, node 4 and node 5 modify the respective stored first network domain address lists.

Of course, in some embodiments, the node 1 may also broadcast the modified first network domain address list to each neighboring node of the node 1, so as to update the first network domain address list stored in each neighboring node.

In this embodiment, only the list modification instruction is broadcast to each neighbor node of the node 1, which can reduce the broadcast of redundant messages and reduce the network congestion, thereby improving the efficiency of network communication and ensuring the high efficiency of network communication.

S1093, if the list modification instruction is used to instruct to delete the IP address of the node 1 in the first network domain address list under the first target domain, the node located under the first target domain in the neighbor nodes of the node 1 is disconnected from the node 1.

That is, if the modification type in the list modification instruction is "delete" and the modification information is the IP address of the node 1 in the first target domain, each node in the first target domain disconnects from the node 1 after receiving the instruction broadcast by the node 1.

Referring to fig. 1, for example, the list modification instruction is used to instruct to delete "domain 2:117.10.11.1: 50012" in the first network domain address list, i.e., delete the IP address 117.10.11.1:50012 of the node 1 under the second network domain. Node 2 and node 5 under the second network domain receive the list modification instruction broadcast by node 1, delete the information from the respective saved first network domain address list, and both disconnect from node 1.

S1094, if the list modification instruction is used for indicating that the IP address of the node 1 in the first network domain address list under the second target domain is updated to be the target IP address, the node in the neighbor node of the node 1 under the second target domain is disconnected from the node 1, and the connection is reestablished with the node 1 according to the target IP address.

That is, if the modification type in the list modification instruction is "update" and the modification information is to modify the IP address of the node 1 in the second target domain into the target IP address, after receiving the list modification instruction broadcast by the node 1, each node in the second target domain disconnects the node 1, and reestablishes the connection with the node 1 by using the target IP address.

For example, the first network domain address list originally includes: { domain1:10.10.1.1:50011, domain2:117.10.11.1:50012}, list modification instruction { update: { domain2:117.11.10.1:50011} } for indicating that the IP address of the node 1 in the updated first network domain address list under the second network domain is 117.11.10.1: 50011. Then node 2 and node 5 under the second network domain receive the list modification instruction broadcast by node 1, update the information in the respectively saved first network domain address list, and both disconnect from node 1 and re-establish connection with node 1 using IP addresses 117.11.10.1:50011, respectively.

In this embodiment, in the case of receiving a list modification instruction input by a user, the node 1 modifies the first network domain address list thereof based on the list modification instruction. Meanwhile, the node 1 broadcasts the list modification instruction to each neighbor node of the node 1, so that each neighbor node of the node 1 updates the first network domain address list stored in the neighbor node, the first network domain address lists stored in each node in the communication system are all updated, the consistency of the network domain address lists in each node is ensured, the accuracy and the reliability of communication are ensured, and the user experience is further improved. On the other hand, the method provided by the embodiment can dynamically configure the IP address, modify the network domain address list and manage the node communication when the communication system runs, without restarting the node down, thereby simplifying the network communication process, ensuring the stability of the network, saving the user time and further improving the user experience. In addition, the above process of dynamically modifying the network domain address list is user-unaware, that is, the above process is transparent to the user, which further improves the user experience. In addition, each neighbor node of the node 1 updates the connection state with the node 1 according to the list updating instruction, so that the accuracy of node connection is ensured, the reliability of network communication is ensured, and the user experience is further improved.

It should be noted that, in the foregoing embodiment, the scenario that the federation link communication method is applied to mapping internal and external network addresses of nodes in a proxy manner for internal and external network communication is mostly taken as an example for description, however, besides, the method provided in this embodiment may also be applied to any situation that one node may have multiple IP addresses for communication of nodes in multiple network domains, which is not limited in this application.

It should be understood that, although the steps in the flowcharts of the above embodiments are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least a portion of the steps in the flowchart may include multiple sub-steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of performing the sub-steps or stages is not necessarily sequential, but may be performed alternately or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

Fig. 7 shows a block diagram of a federated communications apparatus provided in this embodiment of the present application, where the federated communications apparatus may be the first node (for example, the node 1 described above), and may also be an apparatus (such as a chip or a processing circuit) applied in the first node. As shown in fig. 7, the alliance-chain communication device provided in this embodiment may include:

a first obtaining module 701, configured to obtain first address information, where the first address information includes an address of a first node in at least one network domain, the first node is located in the first network domain, and the first address information at least includes the address of the first node in the first network domain;

a first sending module 702, configured to send the first address information to the second node through a first connection with the second node; the second node is located in a second network domain;

a first receiving module 703 is configured to receive, through the first connection, second address information from the second node, where the second address information includes addresses of the second node in one or more network domains, and the second address information at least includes an address of the second node in the second network domain.

In one embodiment, the first sending module 702 is further configured to send, to the second node, first prompting information in a case that the address of the second node under the first network domain is not included in the second address information, where the first prompting information is used to prompt the second node to print a first warning log, and the first warning log is used to represent that the address of the second node under the first network domain is not included in the second address information.

In one embodiment, the first sending module 702 is further configured to send a second hint information to the second node if the address of the second node under the first network domain is included in the second address information and the address of the second node under the first network domain is not communicable; the second prompt message is used for prompting the second node to print a second warning log, and the second warning log is used for representing that the address of the second node under the first network domain is not communicable.

In one embodiment, the first receiving module 703 is further configured to receive a list modification instruction; the alliance-link communication device further comprises a first modifying module 704, configured to modify the first address information according to the list modifying instruction, and send the list modifying instruction to a neighbor node of the first node.

In one embodiment, the remote address list of the first node includes the address of the second node, and the apparatus further includes a first connection establishing module 705 configured to establish the first connection with the second node according to the address of the second node.

The alliance-link communication device provided in this embodiment is configured to execute the steps of the node 1 in the alliance-link communication method provided in the embodiment of the method of the present application, and the technical principles and technical effects are similar to each other.

Fig. 8 shows a block diagram of a federated communications apparatus provided in this embodiment of the present application, where the federated communications apparatus may be a second node (for example, the node 2 described above), and may also be an apparatus (such as a chip or a processing circuit) applied in the second node. As shown in fig. 8, the alliance-chain communication device provided in this embodiment may include:

a second obtaining module 801, configured to obtain second address information, where the second address information includes addresses of second nodes in one or more network domains, and the second nodes are located in the second network domain; the second address information at least comprises the address of the second node under the second network domain;

a second sending module 802, configured to send the second address information to the first node through the first connection with the first node; the first node is located in a first network domain;

a second receiving module 803, configured to receive first address information from the first node, where the first address information includes an address of the first node in at least one network domain, and the first address information includes at least an address of the first node in the first network domain.

In one embodiment, the connection initiator of the first connection is a first node, and the second receiving module 803 is further configured to receive an address of a second node from the first node; the second obtaining module 801 is further configured to obtain original second address information; and under the condition that the original second address information does not comprise the address of the second node in the first network domain, writing the address of the second node serving as the address of the second node in the first network domain into the original second address information to obtain second address information.

In one embodiment, the second sending module 802 is further configured to send, to the first node, third prompting information in a case that the address of the first node under the second network domain is not included in the first address information, where the third prompting information is used to prompt the first node to print a third warning log, and the third warning log is used to represent that the address of the first node under the second network domain is not included in the first address information.

In one embodiment, the second sending module 802 is further configured to send, to the first node, fourth prompting information in a case that the first address information includes an address of the first node under the second network domain and the address of the first node under the second network domain is not communicable, where the fourth prompting information is used to prompt the first node to print a fourth warning log, and the fourth warning log is used to indicate that the address of the first node under the second network domain is not communicable.

In one embodiment, the second receiving module 803 is further configured to receive a list modification instruction from the first node; the alliance-link communication device further comprises a second modification module 804 configured to modify the first address information according to the list modification instruction and/or perform a modify connection operation.

In one embodiment, the list modification instruction comprises a first modification instruction for instructing to add an address of the first node under the first target domain in the first address information; the second modifying module 804 is specifically configured to add, according to the first modifying instruction, an address of the first node in the first target domain in the first address information.

In one embodiment, the second node is located in a second target domain, and the list modification instruction includes a second modification instruction for instructing to delete the address of the first node under the second target domain in the first address information; the second modification module 804 is specifically configured to disconnect the connection with the first node according to the second modification instruction.

In one embodiment, the second node is located in a third target domain, and the list modification instruction includes a third modification instruction, where the third modification instruction is used to indicate that the address of the first node in the first address information under the third target domain is updated to be a target address; the second modifying module 804 is specifically configured to disconnect the connection with the first node according to the third modifying instruction, and reestablish the connection with the first node according to the destination address.

The alliance-link communication device provided in this embodiment is configured to execute the steps of the node 2 in the alliance-link communication method provided in the embodiment of the method of the present application, and the technical principles and technical effects are similar to each other.

The embodiment of the application also provides a alliance-chain communication system, which comprises a first alliance-chain communication device and a second alliance-chain communication device, wherein the first alliance-chain communication device can be a first node, and the second alliance-chain communication device can be a second node. The first alliance-link communication device is configured to execute the step of the node 1 in the alliance-link communication method provided in the embodiment of the method of the present application, and the second alliance-link communication device is configured to execute the step of the node 2 in the alliance-link communication method provided in the embodiment of the method of the present application.

It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

Referring to fig. 9, an embodiment of the present application further provides an electronic device, where the electronic device may be a first alliance-link communication device in a first node in the above application embodiment, and may also be a second alliance-link communication device in a second node in the above application embodiment. The electronic device includes: a processor 901, a receiver 902, a transmitter 903, a memory 904, and a bus 905. The processor 901 includes one or more processing cores, and the processor 901 executes applications of various functions and information processing by running software programs and modules. The receiver 902 and the transmitter 903 may be implemented as one communication component, which may be a baseband chip. The memory 904 is coupled to the processor 901 via a bus 905. The memory 904 may be configured to store at least one program instruction, and the processor 901 is configured to execute the at least one program instruction to implement the technical solutions of the above embodiments. The implementation principle and technical effect are similar to those of the embodiments related to the method, and are not described herein again.

When the electronic device is turned on, the processor can read the software program in the memory, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be sent through the antenna, the processor performs baseband processing on the data to be sent, and then outputs baseband signals to a control circuit in the control circuit, and the control circuit performs radio frequency processing on the baseband signals and then sends the radio frequency signals to the outside through the antenna in the form of electromagnetic waves. When data is sent to the electronic equipment, the control circuit receives radio-frequency signals through the antenna, converts the radio-frequency signals into baseband signals and outputs the baseband signals to the processor, and the processor converts the baseband signals into the data and processes the data.

Those skilled in the art will appreciate that fig. 9 shows only one memory and processor for ease of illustration. In a practical electronic device, there may be multiple processors and memories. The memory may also be referred to as a storage medium or a storage device, and the like, which is not limited in this application.

As an alternative implementation manner, the processor may include a baseband processor and a central processing unit, the baseband processor is mainly used for processing communication data, and the central processing unit is mainly used for executing a software program and processing data of the software program. Those skilled in the art will appreciate that the baseband processor and the central processing unit may be integrated into a single processor, or may be separate processors, interconnected via bus, etc. Those skilled in the art will appreciate that an electronic device may include multiple baseband processors to accommodate different network formats, multiple central processors to enhance its processing capabilities, and various components of the electronic device may be connected by various buses. The baseband processor may also be expressed as a baseband processing circuit or a baseband processing chip. The central processing unit may also be expressed as a central processing circuit or a central processing chip. The function of processing the communication protocol and the communication data may be built in the processor, or may be stored in the memory in the form of a software program, and the processor executes the software program to realize the baseband processing function. The memory may be integrated within the processor or may be separate from the processor. The memory includes a Cache, which may store frequently accessed data/instructions.

In the embodiments of the present application, the processor may be a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the methods, steps, and logic blocks disclosed in the embodiments of the present application. A general purpose processor may be a microprocessor or any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in a processor.

In the embodiment of the present application, the memory may be a nonvolatile memory, such as a Hard Disk Drive (HDD) or a solid-state drive (SS), and may also be a volatile memory (volatile memory), for example, a random-access memory (RAM). The memory is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, not limited thereto.

The memory in the embodiments of the present application may also be circuitry or any other device capable of performing a storage function for storing program instructions and/or data. The methods provided by the embodiments of the present application may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, a network appliance, a user device, or other programmable apparatus. The computer instructions may be stored in, or transmitted from, a computer-readable storage medium to another computer-readable storage medium, for example, from one website, computer, server, or data center, over a wired (e.g., coaxial cable, fiber optics, Digital Subscriber Line (DSL), or wireless (e.g., infrared, wireless, microwave, etc.) network, the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device including one or more integrated servers, data centers, etc., the available medium may be magnetic medium (e.g., floppy disk, hard disk, magnetic tape), optical medium (e.g., digital video disc (digital video disc, DWD), or a semiconductor medium (e.g., SSD), etc.

Embodiments of the present application further provide a computer-readable storage medium, which stores a computer program, and when the computer program is executed by a processor, the computer program can implement the steps in any of the above method embodiments.

The above-mentioned embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present application and are intended to be included within the scope of the present application.

Claims

1. A method of federation chain communication, comprising:

acquiring first address information, wherein the first address information comprises an address of a first node in at least one network domain, the first node is located in the first network domain, and the first address information at least comprises the address of the first node in the first network domain;

sending the first address information to a second node through a first connection with the second node; the second node is located in a second network domain;

receiving second address information from the second node through the first connection, wherein the second address information comprises addresses of the second node under one or more network domains, and the second address information at least comprises the address of the second node under the second network domain.

2. The method of claim 1, further comprising:

and sending first prompt information to the second node when the address of the second node under the first network domain is not included in the second address information, wherein the first prompt information is used for prompting the second node to print a first warning log which is used for representing that the address of the second node under the first network domain is not included in the second address information.

3. The method of claim 2, further comprising:

sending second prompt information to the second node under the condition that the second address information comprises the address of the second node under the first network domain and the address of the second node under the first network domain is not communicable; the second prompt message is used for prompting the second node to print a second warning log, and the second warning log is used for representing that the address of the second node under the first network domain is not communicable.

4. The method of claim 1, further comprising:

receiving a list modification instruction;

and modifying the first address information according to the list modification instruction, and sending the list modification instruction to the neighbor node of the first node.

5. The method according to any of claims 1 to 4, wherein the remote address list of the first node includes the address of the second node, and wherein the method further comprises, prior to receiving second address information from the second node over the first connection:

and establishing the first connection with the second node according to the address of the second node.

6. A method of federation chain communication, comprising:

acquiring second address information, wherein the second address information comprises addresses of second nodes in one or more network domains, and the second nodes are positioned in the second network domain; the second address information at least comprises the address of the second node under the second network domain;

sending the second address information to a first node through a first connection with the first node; the first node is located in a first network domain;

receiving first address information from the first node, wherein the first address information comprises an address of the first node under at least one network domain, and the first address information at least comprises the address of the first node under the first network domain.

7. The method of claim 6, wherein a connection initiator of the first connection is the first node, and wherein before the obtaining the second address information, the method further comprises:

receiving an address of the second node from the first node;

the obtaining of the second address information includes:

acquiring original second address information;

and writing the address of the second node as the address of the second node in the first network domain into the original second address information to obtain the second address information under the condition that the original second address information does not include the address of the second node in the first network domain.

8. The method of claim 6, further comprising:

and sending third prompt information to the first node when the address of the first node under the second network domain is not included in the first address information, wherein the third prompt information is used for prompting the first node to print a third warning log, and the third warning log is used for representing that the address of the first node under the second network domain is not included in the first address information.

9. The method of claim 6, further comprising:

and sending fourth prompt information to the first node when the first address information comprises the address of the first node under the second network domain and the address of the first node under the second network domain is not communicable, wherein the fourth prompt information is used for prompting the first node to print a fourth warning log which is used for representing that the address of the first node under the second network domain is not communicable.

10. The method according to any one of claims 6 to 9, further comprising:

receiving a list modification instruction from the first node;

and modifying the first address information according to the list modification instruction, and/or executing a modification connection operation.

11. The method of claim 10,

the list modification instruction comprises a first modification instruction for instructing to add an address of the first node under a first target domain in the first address information; modifying the first address information according to the list modification instruction, and/or executing a modification connection operation, including: according to the first modification instruction, increasing the address of the first node under the first target domain in the first address information;

or the like, or, alternatively,

the second node is located in a second target domain, and the list modification instruction comprises a second modification instruction which is used for indicating to delete the address of the first node under the second target domain in the first address information; modifying the first address information according to the list modification instruction, and/or executing a modification connection operation, including: disconnecting the connection with the first node according to the second modification instruction;

or the like, or, alternatively,

the second node is located in a third target domain, the list modification instruction comprises a third modification instruction, and the third modification instruction is used for indicating that the address of the first node under the third target domain in the first address information is updated to be a target address; modifying the first address information according to the list modification instruction, and/or executing a modification connection operation, including: and disconnecting the connection with the first node according to the third modification instruction, and reestablishing the connection with the first node according to the target address.

12. A federated link communication system, comprising: a first node for performing the method of any of claims 1 to 5 and a second node for performing the method of any of claims 6 to 11.

13. An electronic device, comprising: memory, a processor and a computer program stored in the memory and executable on the processor, the processor implementing the method of any one of claims 1 to 5 when executing the computer program or implementing the method of any one of claims 6 to 11.

14. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program which, when executed by a processor, implements the method of any of claims 1 to 5, or implements the method of any of claims 6 to 11.