WO2023115982A1 - 通信方法、系统、电子设备及可读存储介质 - Google Patents

通信方法、系统、电子设备及可读存储介质 Download PDF

Info

Publication number
WO2023115982A1
WO2023115982A1 PCT/CN2022/111762 CN2022111762W WO2023115982A1 WO 2023115982 A1 WO2023115982 A1 WO 2023115982A1 CN 2022111762 W CN2022111762 W CN 2022111762W WO 2023115982 A1 WO2023115982 A1 WO 2023115982A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
address
network domain
nodes
connection
Prior art date
Application number
PCT/CN2022/111762
Other languages
English (en)
French (fr)
Inventor
尚璇
胡麦芳
陶媛
黄方蕾
张珂杰
Original Assignee
杭州趣链科技有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 杭州趣链科技有限公司 filed Critical 杭州趣链科技有限公司
Priority to EP22789151.2A priority Critical patent/EP4228209A4/en
Publication of WO2023115982A1 publication Critical patent/WO2023115982A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
    • H04L63/0281—Proxies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/20—Network architectures or network communication protocols for network security for managing network security; network security policies in general
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/50—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols using hash chains, e.g. blockchains or hash trees
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H04L61/2503—Translation of Internet protocol [IP] addresses
    • H04L61/2514—Translation of Internet protocol [IP] addresses between local and global IP addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses

Definitions

  • the present application relates to the field of block chain technology, and in particular to a communication method, system, electronic equipment and readable storage medium.
  • alliance chain is a type of blockchain.
  • the alliance chain is only aimed at members of a specific group and limited third parties. It internally designates multiple pre-selected nodes as bookkeepers, and the generation of each block is jointly decided by all pre-selected nodes.
  • cross-domain communication is required.
  • the cross-domain communication of the alliance chain is mainly realized through NAT (Network Address Translation, Network Address Translation) penetration technology.
  • NAT penetration technology has problems such as low security. Therefore, organizations corresponding to some nodes in the alliance chain hope to communicate with the outside world through proxy.
  • node discovery is a very important technology.
  • the new node joins the network through known nodes, and the new node knows only limited network node information, more nodes can be learned through node discovery, so as to establish sufficient connections.
  • the present application provides a communication method, system, electronic equipment, and readable storage medium, which realize the self-discovery of nodes in the scenario of using proxy communication in the alliance chain, and meet the needs of users.
  • the embodiment of the present application provides a communication method, the method includes: receiving the first information from the first node through the first connection with the first node; the first connection includes a logical connection, and the first connection The initiator of the connection is the first node; the first information includes the address of the first node under the target network domain, the target network domain is the network domain where at least one other node is located, and at least one other node refers to the network domain to be joined by the first node Nodes in the network partition except the second node; the address of the first node under the target network domain is used for establishing a connection between the first node and at least one other node; and sending the first information to at least one other node.
  • the embodiment of the present application provides a communication method, the method includes: obtaining first information; the first information includes the address of the first node under the target network domain; the target network domain is the network domain where at least one other node is located , at least one other node refers to a node other than the second node in the network partition to be joined by the first node; the address of the first node under the target network domain is used for the first node to establish a connection with at least one other node;
  • the first connection between two nodes sends the first information to the second node; the first connection includes a logical connection, and the connection initiator of the first connection is the first node.
  • the embodiment of the present application provides a communication method, the method includes: the third node receives the address of the first node under the target network domain from the second node, and the target network domain is the network domain where at least one other node is located , at least one other node refers to a node other than the second node in the network partition to be joined by the first node, and at least one other node includes the third node; the third node is based on the address of the first node under the target network domain and the first The node establishes the connection. At least one other node and the second node belong to the same network partition, and the network partition is the network partition to be joined by the first node.
  • the embodiment of the present application provides a consortium chain communication device.
  • the consortium chain communication device may be a second node, or a device (such as a chip or a processing circuit) applied to the second node.
  • the device includes : a first receiving module, configured to receive the first information from the first node through the first connection with the first node; the first connection includes a logical connection, and the connection initiator of the first connection is the first node; the first The information includes the address of the first node under the target network domain, where the target network domain is the network domain where at least one other node is located, and the at least one other node refers to a node other than the second node in the network partition to be joined by the first node; The address of the first node under the target network domain is used for the first node to establish a connection with at least one other node; the first sending module is used for sending the first information to at least one other node.
  • the embodiment of the present application provides a consortium chain communication device.
  • the consortium chain communication device may be a first node, or a device (such as a chip or a processing circuit) applied to the first node.
  • the device includes : an acquisition module, configured to acquire first information; the first information includes the address of the first node under the target network domain; the target network domain is the network domain where at least one other node is located, and at least one other node refers to the first node to be Nodes in the joined network partition except the second node; the address of the first node under the target network domain is used for the first node to establish a connection with at least one other node; the second sending module is used for passing through the connection with the second node The first connection of the first connection sends the first information to the second node; the first connection includes a logical connection, and the connection initiator of the first connection is the first node.
  • the embodiment of the present application provides a consortium chain communication system, including: a first node and a second node, the second node is used to perform any one of the methods in the first aspect above, and the first node is used to The method of any one of the above-mentioned second aspects is performed.
  • the above alliance chain communication system may further include at least one other node. At least one other node belongs to the same network partition as the second node, and the network partition is the network partition to be joined by the first node.
  • the embodiment of the present application provides a computer device, including: a memory, a processor, and a computer program stored in the memory and operable on the processor.
  • the processor executes the computer program, any of the above-mentioned first aspects can be realized.
  • the embodiment of the present application provides a computer-readable storage medium, the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the communication method in any one of the above-mentioned first aspects is implemented, or the The communication method according to any one of the above-mentioned second aspects.
  • the second node receives the first information sent by the first node through the first connection with the first node, and sends the first information sent to other nodes.
  • the first information includes the address of the first node under the target network domain where at least one other node is located, so other nodes receive the address of the first node under the target network domain where at least one other node is located, and can use the address and the first
  • the node establishes the connection.
  • the first node actively sends the first information to the second node. That is to say, this embodiment realizes the self-discovery of nodes in the consortium chain using the proxy communication scenario through the node discovery technology in the form of PUSH.
  • the consortium chain itself has stricter authentication of nodes, so node discovery in the consortium chain through PUSH can avoid Eclipse attacks and Sybil attacks, etc., and has high security.
  • the second node when the second node sends the first information, it only sends the first information to nodes in the network partition to be joined (that is, other nodes), so that the first node only communicates with the to-be-joined
  • the node connection in the network partition realizes the partition isolation of node discovery, which not only satisfies the self-discovery of nodes in the scenario of multiple network partition communication in the alliance chain, but also the partition isolation of node discovery will not cause confusion in business execution, further satisfying User needs.
  • Figure 1 is a network topology diagram of a consortium chain communication system provided by an embodiment of the present application.
  • Fig. 2 is a network topology diagram of a consortium chain communication system provided by another embodiment of the present application.
  • FIG. 3 is a schematic flowchart of a communication method provided by an embodiment of the present application.
  • FIG. 4 is a schematic flowchart of a communication method provided by another embodiment of the present application.
  • FIG. 5 is a schematic flowchart of a communication method provided in another embodiment of the present application.
  • FIG. 6 is a schematic flowchart of a method for obtaining a network domain address list provided in another embodiment of the present application.
  • FIG. 7 is a schematic flowchart of a method for obtaining a network domain address list of node 2 provided by an embodiment of the present application
  • FIG. 8 is a schematic flowchart of a method for checking a network domain address list provided by an embodiment of the present application.
  • FIG. 9 is a schematic flowchart of a method for dynamically modifying a network domain address list provided by an embodiment of the present application.
  • FIG. 10 is a schematic diagram of the process of dynamically modifying the network domain address list provided by an embodiment of the present application.
  • Fig. 11 is a structural block diagram of a consortium chain communication device provided by an embodiment of the present application.
  • Fig. 12 is a structural block diagram of a consortium chain communication device provided by another embodiment of the present application.
  • Fig. 13 is a schematic structural diagram of an electronic device provided by an embodiment of the present application.
  • the method provided in the embodiment of this application can be applied to the alliance chain communication system.
  • the application scenarios of the alliance chain communication system include but are not limited to product traceability, public welfare charity, supply chain finance, e-government, mutual insurance or the Internet of Things, etc. Do not make any restrictions.
  • FIG. 1 is a network topology diagram of an example of a consortium chain communication system (hereinafter referred to as a communication system) provided by an embodiment of the present application.
  • the communication system includes multiple network domains, and at least one blockchain node (hereinafter referred to as a node) is set in each network domain.
  • the nodes involved in this embodiment of the present application correspond to various institutions in the consortium chain, which can be servers or terminals.
  • Cross-domain communication Communication between nodes in different network domains. For example, the communication between node 1 and node 2 in Fig. 1 .
  • Neighbor nodes The nodes that have a neighbor relationship with a certain node are called the neighbor nodes of the node. As shown in FIG. 1 , the neighbor nodes of node 1 include node 2 , node 3 , node 4 and node 5 ; the neighbor nodes of node 2 include node 1 , node 3 and node 5 .
  • the domain where a node is located is called the local domain of the node.
  • the non-local network domain of the neighbor nodes of the node is called the relevant domain of the node.
  • the related domains of node 1 include the second network domain and the third network domain
  • the related domains of node 2 include the first network domain and the third network domain
  • the related domains of node 3 include the first network domain and the second network domain. network domain.
  • Network partition In order to provide different services to organizations corresponding to nodes in the network, the network is divided into multiple areas, and each area is called a network partition. Each network partition can include one or more nodes. Nodes in the same network partition can communicate with each other, but nodes in different network partitions cannot. As shown in FIG. 1 , Node 1 , Node 2 , Node 3 and Node 4 belong to the first network partition, and Node 2 and Node 5 belong to the second network partition. Interconnected nodes in the first network partition can communicate, and interconnected nodes in the second network partition can communicate, but nodes in the first network partition and nodes in the second network partition cannot communicate directly. For example, node 1 and node 5 do not belong to the same network partition and cannot communicate directly.
  • FIG. 2 is a network topology diagram provided by another embodiment of the present application.
  • the network includes a total of 10 nodes from node 0 to node 9, including three network partitions: ns1, ns2 and global.
  • ns1 includes node 3, node 4, node 5, node 6, node 7, and node 9, and ns2 includes node 0 and node 8.
  • Global includes node 1, node 2, node 3 and node 4. Taking node4 as an example, node4 can communicate with node1, node2, node3, and node9, but cannot communicate with node8 and node0.
  • Physical connection A connection made using the physical properties of objects. Physical connections enable physical network communication between nodes. Physical connections are the basis for logical connections.
  • Logical connection established on the basis of physical connection. That is to say, if a logical connection is established between two nodes, a physical connection must be established. However, a physical connection is established between two nodes, not necessarily a logical connection.
  • nodes By establishing a logical connection, communication of service messages between nodes can be realized. If no logical connection is established, only a physical connection is established, and the two nodes can only send and receive connection-related messages and check-in messages, but cannot send and receive business messages. Even if one end node sends a business message by mistake, it will not be blocked Nodes receive, and only after establishing a logical connection on the basis of establishing a physical connection, can business messages be sent and received. The logical connection needs to verify the identity of the node. Once the node finds that the peer node is an illegal node, the node immediately disconnects the logical connection and the physical connection.
  • node 3 and node 4 belong to both the first network partition and the third network partition.
  • the application process of the consortium chain involves cross-domain communication.
  • cross-domain communication is mainly realized through NAT penetration technology.
  • some institutions in the alliance chain have higher requirements for network security. Therefore, these institutions hope to communicate with the outside (other network domains) through a proxy method, that is, through proxy mapping
  • the internal and external URLs of the nodes are used for internal and external network communication to hide the internal IP address of the organization.
  • an institution it is possible for an institution to use different IP addresses for connections to institutions in different network domains, especially when using a reverse proxy. That is to say, in a communication system, a node may simultaneously have multiple IP addresses for communication between nodes in multiple network domains. For example, in FIG. 1 , the IP address of node 1 for communication with nodes in the first network domain is A, and the IP address for communication with nodes in the second network domain is B.
  • consortium chains do not take into account the scenario that organizations need to use proxy communication, so it is necessary to study the communication between nodes in the consortium chain according to the needs of users, including research on the discovery technology of nodes in the consortium chain .
  • node discovery is a very important technology. Just imagine, if there is no node discovery technology, there are hundreds of nodes in a huge network. If a new node needs to join the network, the IP addresses of these hundreds of nodes must be configured. This will be very complicated and time consuming.
  • the node discovery technology can solve this problem. When a new node joins the network, it only needs to configure the IP addresses of a few nodes in the network. After the new node establishes a connection with these few nodes, it can discover other nodes in the network through node discovery and establish connections with other nodes.
  • the embodiment of the present application aims to study the method of node discovery and connection in the scenario where the alliance chain uses proxy communication and there may be multiple network partition communications, so as to meet the needs of users in actual use.
  • the embodiment of the present application aims to study the method of node discovery and connection in the scenario where the alliance chain uses proxy communication and there may be multiple network partition communications, so as to meet the needs of users in actual use.
  • Various needs are possible.
  • the communication method provided in this embodiment is used to realize the connection between the node 1 and the nodes that need to be connected in the network partition to be joined. That is to say, in this embodiment, taking node 1 as a new joining node as an example, the network partition that node 1 needs to join is called the network partition to be joined.
  • the network partition to be joined includes node 2 and at least one other node (that is, both node 2 and at least one other node belong to the network partition to be joined by node 1).
  • the communication method will be described by taking node 1 as a newly added node and the network partition to be joined as the first network partition as an example.
  • at least one other node may include node 3 and node 4 .
  • the network domains to which each node belongs are shown in Figure 1.
  • the communication method provided in this embodiment is used to realize the connection between node 1 and node 2, and node 4 among other nodes.
  • node 1 joins the first network partition as an example for illustration.
  • the method provided in this embodiment may be applied to a communication system including one or more network partitions.
  • node 1 needs to join all can be executed by referring to the process of the embodiment of the present application, and the embodiments of the present application will not repeat them one by one.
  • FIG. 3 shows a schematic flow chart of the communication method provided by the present application.
  • the method may include:
  • Node 1 and Node 2 establish a first connection; the first connection includes a logical connection; Node 1 is a connection initiator of the first connection, and Node 2 is a connection receiver of the first connection.
  • connection initiator (or called the initiator node), that is, the one of the two nodes that sends the connection request
  • the connection receiver or called the receiver node
  • a node connection collision may occur, that is, two nodes initiate a connection request to each other at the same time.
  • one of the two nodes will give up the connection request and receive the connection request sent by the peer node to establish a connection.
  • node 1 since node 2 runs in the network and does not know the IP address of node 1, in this case, node 1 must be the connection initiator, and there is no problem of connection collision.
  • node 1 may initiate a connection request to node 2 according to the IP address of node 2 in the remote address (remote address) list of node 1 (hereinafter referred to as the first IP address).
  • the first IP address may be obtained through user configuration.
  • the user may configure the proxy node of node 2 to obtain a first IP address that can be connected to node 1, and configure the first IP address in the remote address list of node 1.
  • node 1 initiates a connection to node 2 according to the first IP address in its remote address, and node 2 responds to the connection request, thereby establishing the first connection.
  • the IP address involved in the embodiment of the present application may be an IP address provided by a proxy (including a forward proxy and a reverse proxy) node, or an IP address provided by a NAT gateway.
  • a proxy including a forward proxy and a reverse proxy
  • IP address provided by a NAT gateway.
  • the application does not impose any limitation on this, and the following embodiments will not repeat the source of each IP address.
  • Node 1 obtains a first network domain address list; the first network domain address list is used to represent the IP address of node 1 under at least one network domain, wherein the first network domain address list includes node 1 in at least one other node The IP address under the network domain where it is located.
  • the IP address of a certain node in a certain network domain refers to the IP address of the node for communication connection of nodes in the network domain.
  • the IP address A of node 1 in the first network domain refers to the IP address of node 1 for communication connection with nodes in the first network domain.
  • the node in the first network domain communicates with node 1 through the IP address A.
  • the first network domain address list may include the IP address of node 1 in its local domain and related domains, and other nodes may be located in the local domain of node 1 or in related domains of node 1.
  • the first network domain address list includes at least the IP address of node 1 under the network domain of one other node.
  • Each IP address in the first network domain address list may be configured by the user.
  • the configuration process is similar to the configuration process of the remote address list of node 1 above, and will not be repeated here.
  • node 1 is located in a first network domain, and related domains of node 1 include a second network domain and a third network domain.
  • the first network domain address list may include the IP address of node 1 under the first network domain and the IP address under the second network domain.
  • the first network domain address list may be: ⁇ domain1:10.10.1.1:50011, domain2:117.10.11.1:50012, domain3:117.10.11.1:50013 ⁇ .
  • domain1 represents the first network domain
  • domain2 represents the second network domain
  • domain3 represents the third network domain.
  • the IP address provided by node 1 to connect to node 4 in the first network domain is 10.10.1.1:50011
  • the IP address provided by node 1 to connect to node 2 and node 5 in the second network domain is 117.10.11.1:50012
  • the IP address provided by node 1 to connect to node 3 in the third network domain is 117.10.11.1:50013.
  • the first network domain address list includes the IP addresses of the node 1 under the network domains where the other nodes 3 and 4 are located.
  • Node 1 sends the first network domain address list to node 2 based on the first connection.
  • node 1 when node 1 sends the first network domain address list, it may also store the first network domain address list in the memory of node 1 .
  • Node 2 receives the first network domain address list.
  • Node 2 broadcasts the first network domain address list to each node in the first network partition.
  • node 2 may use the Gossip protocol to broadcast to all nodes in the first network partition. It should be noted that here node 2, as the receiver of the first connection, broadcasts the address list of the first network domain to all nodes in the first network partition, not the neighbor nodes of node 2. Node 2 uses the Gossip protocol to periodically randomly select some nodes to transmit the address list of the first network domain, which can reduce redundant messages in the network.
  • the other nodes receive the first network domain address list, and obtain the IP address of node 1 under the network domain where the other nodes are located from the first network domain address list.
  • the following uses node 4 among the other nodes in FIG. 1 as an example for illustration, and the process of other nodes is the same as that of node 4, which will not be repeated here.
  • Node 4 receives the first network domain address list, and acquires the IP address of node 1 under the network domain where node 4 is located from the first network domain address list.
  • node 4 looks up the IP address of node 1 under the first network domain from the address list of the first network domain. If the IP address of node 1 under the first network domain is not included in the first network domain address list, node 4 discards the message (received first network domain address list); if yes, execute step S307.
  • the node 4 determines whether the IP address of the node 1 under the network domain where the node 4 is located is communicable.
  • node 4 may initiate a connection request to the IP address of node 1 under the network domain where node 4 is located, and determine whether communication with node 1 can be realized through the IP address. If a response or feedback from the other party is received after the connection request is initiated, node 1 determines that the IP address can communicate. Otherwise, node 1 determines that the IP address is not communicable. In this implementation, before the connection is established, the node 4 determines the communicability of the IP address, so as to reduce useless messages and communications and improve connection efficiency.
  • step S308 is executed.
  • the node 4 establishes a connection with the node 1 according to the IP address of the node 1 under the network domain where the node 4 is located.
  • node 1 can discover and connect to node 3 and node 4 . And in the above process, node 1 actively sends its first network domain address list to node 2, so the above node discovery process is a node discovery in the form of PUSH.
  • the above node discovery process is a node discovery in the form of PUSH.
  • the node discovery technology in the form of PUSH the self-discovery of nodes in the consortium chain using proxy mode communication scenarios is realized, which meets the needs of users; and the consortium chain itself has stricter authentication of nodes, so Node discovery is performed through PUSH, which can avoid Eclipse attacks and Sybil attacks, etc., and has high security.
  • the method provided in this embodiment can be applied to a network system including a single network partition, and can also be applied to a network system including multiple network partitions, so as to meet different needs of users and have strong applicability.
  • node 2 when node 2 broadcasts the first network domain address list, it only broadcasts the first network domain address list to nodes in the first network partition, so that node 1 only communicates with nodes in the first network partition It realizes the partition isolation of node discovery, which not only meets the self-discovery of nodes in the scenario of multiple network partition communication in the alliance chain, but also the partition isolation of node discovery will not cause confusion in business execution, and further meet user needs .
  • each node in the first network partition may be located in the same network domain, or may be located in different network domains. Therefore, the method provided in this embodiment can not only be applied to include only one network domain
  • the network system can also be applied to a network system including multiple network domains, that is, the method provided in this embodiment can realize node discovery and connection in cross-domain communication, and further meet the user's network establishment requirements in the cross-domain communication scenario , improve user experience.
  • the method further includes:
  • the node 4 writes the IP address of the node 1 under the network domain where the node 4 is located into the remote address list of the node 4.
  • node 4 after the connection is realized, node 4 further writes back the IP address of node 1 to the remote address list of node 4. In this way, node 4 can gradually improve its remote address list and realize the remote address list. Automatic write-back reduces the user's configuration of the remote address list and improves user experience.
  • the node while the node discovers the node in the PUSH manner, it can also further discover the node in the PULL manner.
  • the communication method provided in this embodiment includes:
  • Node 1 sends a first request message to node 2 based on the first connection.
  • the first request message is also referred to as a first node request message (peer request).
  • the first request message is used to instruct node 2 to generate the first response message.
  • the first response message is also referred to as a first node response message (peer response).
  • Node 2 receives the first request message.
  • Node 2 obtains at least one third network domain address list in response to the first request message; the third network domain address list is used to indicate that among the neighbor nodes of node 2, nodes located in the first network partition are in at least one network domain under the IP address.
  • the node 2 may pre-store the network domain address list of the node 2, and may also store the network domain address lists of each neighbor node of the node 2.
  • Node 2 selects the network domain address list of nodes located in the first network partition from the network domain address list of neighboring nodes to obtain the third network domain address list. The source of each network domain address list stored in the node 2 will be described in subsequent embodiments.
  • Node 2 searches for the target IP address from the address list of the third network domain; the target IP address refers to the IP address of the node under the first network domain, and the target IP address includes the IP of at least one other node under the first network domain address.
  • the node 2 searches each third network domain address list one by one, picks out the IP addresses existing in the first network domain in each network domain address list, and obtains the above-mentioned target IP address.
  • Node 2 generates a first response message according to the target IP address.
  • Node 2 returns the first response message to Node 1 based on the first connection.
  • Node 1 determines whether the IP addresses of other nodes (node 4 in FIG. 4 is taken as an example) in the first network domain in the first response message are communicable.
  • node 1 determines that the IP addresses of other nodes in the first network domain in the first response message are not communicable, node 1 discards the IP address; if node 1 determines that the IP address is communicable, then execute step S408.
  • Node 1 establishes a connection with other nodes according to the IP addresses of other nodes under the first network domain in the first response message.
  • node 1 after node 1 establishes a connection with node 2, node 1 sends a first request message to node 2, and node 2 responds to the first request message and generates a first response message.
  • the neighbor nodes of node 2 include node 1 , node 3 and node 5 . Since the connection between node 1 and node 2 has been established in step S301, the network domain address list of node 1 is a repeated message, which does not need to be sent. And node 5 does not belong to the first network partition, therefore, the network domain address list of node 5 cannot be sent.
  • node 1 uses the network domain address list of node 3 as the above-mentioned third network domain address list, searches for the IP address under the first network domain, and obtains the IP address of node 3 under the first network domain.
  • Node 2 uses the IP address of node 3 under the first network domain as the target IP address, generates a first response message according to the target IP, and sends the first response message to node 1 .
  • Node 1 establishes a connection with node 3 according to the IP address of node 3 under the first network domain in the first response message.
  • node 1 can discover and connect to node 3 .
  • node 1 obtains the IP address of node 3 by pulling it from node 2, and the above node discovery process is a node discovery in the form of PULL.
  • the node discovery technology in the form of PULL the self-discovery of nodes in the scenario of proxy communication in the alliance chain is realized, which meets the needs of users; and the identity verification of the alliance chain itself is relatively strict for nodes, so Node discovery is performed through PULL, which can avoid Eclipse attacks and Sybil attacks, etc., and has high security.
  • the first response message returned by node 2 to node 1 is obtained from the third network domain list, and the third network domain address list is the neighbor nodes of node 2 located in the first network partition
  • the network domain address list of the node so the message returned by node 2 to node 1 does not include the messages of other network partitions, which realizes the partition isolation of node discovery, and not only satisfies the self-discovery of nodes in the scenario of multiple network partition communication in the alliance chain , and the partition isolation discovered by nodes will not cause confusion in business execution, further meeting user needs.
  • the method provided in this embodiment adopts the PUSH method for node discovery and the PULL method for node discovery.
  • the two methods complement each other, and can discover more nodes faster and improve the efficiency of node connection.
  • the PULL method may be able to obtain the IP address. IP addresses of other nodes under the first network domain, and node 1 establishes a connection with this node.
  • node 1 belongs to a newly added network domain
  • node 2 does not store the IP address of any node under the newly added network domain, then node 2 cannot return a response message to node 1, and PUSH is used Mode node discovery can compensate for this.
  • the method before the above step S403, the method further includes:
  • Node 2 determines whether the target IP address is stored in a preset storage location (cache is used as an example below).
  • node 2 does not perform any operation.
  • the node executes the above step S403, and after step S404, the method further includes:
  • Node 2 saves the target IP address in the cache.
  • the node 2 clears the target IP address in the cache.
  • node 2 each time after obtaining the target IP address, node 2 saves the target IP address in the cache for a preset period of time. If node 2 receives the first request message sent by node 1 again within the preset time period, node 2 will not return the first response message to node 1 again. If node 2 receives the first request message sent by node 1 again after the preset period of time, node 2 returns the first request message to node 1 according to the above steps S403 to S405. In this way, redundant messages in the network can be reduced, and the first response message including the target IP address can be sent to node 1 again in the event of packet loss or other undeliverable conditions during the message sending process, ensuring message integrity. Best effort to deliver.
  • the preset duration may be determined according to the period for node 1 to send the first request message and specific conditions of the network environment. For example, if the network environment is good and packet loss rarely occurs, the preset duration can be set longer, which is much longer than the period for sending the first request message. If the network environment is poor and packet loss often occurs, the preset duration can be set shorter, which is slightly longer than the period for sending the first request message.
  • the method further includes:
  • Node 1 writes the IP address list of other nodes under the first network domain in the first response message into the remote address list of node 1.
  • the IP addresses of other nodes that Node 1 can further communicate with under the first network domain are written back to the remote address list of Node 1.
  • Node 1 can gradually improve its remote address list.
  • the address list realizes the automatic write-back of the remote address list, reduces the configuration of the remote address list by the user, and improves the user experience.
  • Fig. 5 is a schematic flowchart of a communication method in still another embodiment.
  • node 1 after node 1 joins the above-mentioned first network partition, it may further perform timing node discovery.
  • the method also includes:
  • Node 1 sends a second request message to K target neighbor nodes among the neighbor nodes of Node 1 according to a preset period.
  • K is an integer greater than or equal to 1.
  • node 1 may randomly select K neighbor nodes as target neighbor nodes.
  • the target neighbor node receives the second request message.
  • the target neighbor node acquires at least one fourth network domain address list in response to the second request message.
  • the fourth network domain address list is used to represent the IP addresses of the nodes located in the first network partition among the neighbor nodes of the target neighbor node under at least one network domain.
  • the target neighbor node searches for the target IP address from the fourth network domain address list; the target IP address refers to the IP address of the node under the first network domain, and the target IP address includes at least one other node under the first network domain IP address.
  • the target neighbor node generates a second response message according to the target IP address.
  • the target neighbor node returns the second response message to node 1.
  • Node 1 determines whether the IP addresses of other nodes in the first network domain in the second response message are communicable.
  • node 1 determines that the IP address of other nodes in the first network domain in the second response message is not communicable, node 1 discards the IP address; if node 1 determines that the IP address is communicable, then execute step S508.
  • Node 1 establishes connections with other nodes according to the IP addresses of other nodes (taking node 4 in FIG. 5 as an example) in the first network domain in the second response message.
  • the second request message and the second response message are similar to the first request message and the first response message in the above embodiment, and steps S502 to S508 are similar to the above steps S402 to S408, and will not be repeated here.
  • target neighbor node and node 1 may further perform the processes of steps S409 to S412 above, and the specific process will not be repeated here.
  • the node may not perform repeated operations, that is, only connect to unconnected nodes.
  • nodes After a node establishes connections with some nodes in the first network partition, the nodes are discovered again through timing node discovery, and connections are established with nodes that have not established connections.
  • Regular node discovery can discover nodes that were not discovered in the early stage due to message loss, temporary node downtime and other reasons, and realize the connection, making node discovery more comprehensive and network establishment more comprehensive and accurate.
  • nodes can exchange network domain address lists with each other when establishing a connection, and update the network domain address lists after joining the network.
  • the process of exchanging network domain address lists in the process of establishing a connection between node 2 and node 3 will be described as an example. Other nodes are similar to this and will not be described again.
  • FIG. 6 is a schematic flowchart of a process of obtaining a network domain address list provided by an embodiment of the present application. As shown in FIG. 6, the process includes:
  • Node 3 establishes a second connection with node 2, where node 3 is located in the third network domain, and node 2 is located in the second network domain.
  • the process of establishing the second connection between node 3 and node 2 is similar to the process of establishing the first connection between node 1 and node 2, and will not be repeated here.
  • node connection collision may occur during the connection process between node 3 and node 2.
  • a node connection collision occurs, according to preset rules, one of the two nodes will give up the connection request and receive the connection request sent by the peer node to establish a connection.
  • the connection initiator refers to the one of the two nodes that initiates the connection request and successfully establishes the connection;
  • the corresponding connection receiver refers to the two nodes that receive and respond to the connection request, And the party that successfully establishes the connection.
  • node 3 is the connection initiator of the second connection
  • node 2 is the connection receiver of the second node as an example for illustration.
  • node 3 obtains the network domain address list of node 3; the network domain address list of node 3 is used to represent the IP address of node 3 under at least one network domain, and the network domain address list of node 3 includes at least node 3 in the third The IP address under the network domain.
  • Node 3 sends the network domain address list of node 3 to node 2 based on the second connection.
  • the node 3 may also store the network domain address list of the node 3 in the memory of the node 3 while sending the network domain address list of the node 3 .
  • Node 2 receives and saves the network domain address list of node 3.
  • Node 2 obtains the network domain address list of node 2; the network domain address list of node 2 is used to represent the IP address of node 2 under at least one network domain, and the second network domain address list includes at least node 2 in the second network IP address under the domain.
  • Node 2 sends the network domain address list of node 2 to node 3 based on the second connection.
  • node 2 when node 2 sends the network domain address list of node 2, it may also store the network domain address list of node 2 in the memory of node 2.
  • Node 3 receives and saves the network domain address list of node 2.
  • node 3 and node 2 exchange the network domain address list.
  • both node 3 and node 2 store the network domain address list of node 3 and the network domain address list of node 2 .
  • the proxy method is used to map the internal and external URLs of the nodes to communicate with each other in the internal and external network, so as to improve the user experience.
  • the above is the process of node 3 and node 2 exchanging the network domain address list. It can be understood that any two nodes that have a neighbor relationship in the communication system can exchange their respective network domain address lists through the above process. In this way, each node in the communication system can save the network domain address list of the node and each neighbor node of the node, so that each node can know the IP address of the communication with the neighbor node, so as to facilitate the realization of the above node discovery process .
  • the IP address of node 2 under the third network domain in the network domain address list of node 2 can also be obtained through dynamic write-back. Specifically, while node 3 sends node 3's network domain address list to node 2, it also sends node 2's IP address (hereinafter referred to as the second IP address) in node 3's remote address list to node 2.
  • step S104 node 2 obtains the network domain address list of node 2, specifically including:
  • Node 2 obtains the original network domain address list of node 2.
  • the original network domain address list of node 2 may include the IP address of node 2 under the third network domain.
  • the IP address of node 2 under the third network domain may not be included in the original network domain address list of node 2 due to reasons such as no user configuration.
  • Node 2 judges whether the original network domain address list of node 2 includes the IP address of node 2 under the third network domain;
  • node 3 since node 3 has established a connection with node 2 through the second IP address, it means that the second IP address can be connected to node 3 under the third network domain, and the second IP address can be used as node 2 in the second IP address. IP addresses under the three network domains.
  • the original second network domain address list of node 2 is: ⁇ domain2:10.10.1.2: 50012 ⁇ .
  • Node 2 judges that the IP address of node 2 under the third network domain is not included in the original network domain address list of node 2, then node 2 writes the second IP address into the original network domain address list of node 2, and obtains the final node 2
  • the list of network domain addresses is: ⁇ domain2:10.10.1.2:50012, domain3:117.11.10.2:50012 ⁇ .
  • the receiver node its network domain address list is obtained through dynamic write-back.
  • the network domain address list can be obtained without further configuration by the user, thus simplifying the configuration process of the user and further improving user experience.
  • node 3 and node 2 may check each other's network domain address list respectively.
  • the method may also include:
  • Node 3 determines whether the IP address of node 2 under the third network domain is included in the network domain address list of node 2;
  • Node 3 sends first prompt information to node 2 based on the second connection, where the first prompt information is used to prompt node 2 to print a first warning log (warning log).
  • Node 2 receives the first prompt information, and prints the first warning log according to the first prompt information.
  • the first warning log is used to remind the user that the IP of node 2 under the third network domain is not included in the network domain address list of node 2 address.
  • the user can know that the IP address of the node 2 under the third network domain is not included in the network domain address list of the node 2, so that the user can configure the IP address or perform other operations as required.
  • This implementation method increases the interaction between the node and the user, which facilitates the user to know the network domain address list, thereby facilitating the user to improve the network domain address list of node 2, thereby better implementing subsequent communication, and further improving user experience.
  • Node 3 determines whether the IP address of node 2 under the third network domain is communicable
  • Node 3 sends second prompt information to node 2, where the second prompt information is used to prompt node 2 to print a second warning log.
  • Node 2 receives the second prompt information, and prints a second warning log according to the second prompt information.
  • the second warning log is used to remind the user that the IP address of node 2 under the third network domain cannot communicate.
  • the user can know that the IP address of node 2 under the third network domain cannot communicate, and there may be a configuration error or a connection problem, so that the user can modify the IP address or check the connection as needed.
  • This implementation method increases the interaction between nodes and users, ensures the correctness of the network domain address list of node 2, thereby ensuring the accuracy and reliability of alliance chain communication, and further improving user experience.
  • node 2 can also check the network domain list of node 3 sent by node 3.
  • the specific process is similar to the process of node 3 checking the network domain address list of node 2, including:
  • Node 2 determines whether the network domain address list of node 3 includes the IP address of node 3 under the second network domain.
  • node 2 sends a third prompt message to node 3 based on the second connection, and the third prompt message is used to prompt node 3 to print
  • the third warning log Node 2 receives the third prompt information, and prints the third warning log according to the third prompt information, and the third warning log is used to prompt the user that the network domain address list of node 3 does not include node 3 in the second network domain under the IP address.
  • node 2 determines whether the IP address of node 3 under the second network domain is communicable.
  • node 2 determines that the IP address of node 3 under the second network domain is communicable, the process ends; if node 2 determines that the IP address of node 3 under the second network domain is not communicable, then node 2 sends a fourth prompt to node 3 information, the fourth prompt information is used to prompt node 3 to print the fourth warning log; node 3 receives the fourth prompt information, and prints the fourth warning log according to the fourth prompt information, and the fourth warning log is used to prompt the user node 3 to print the fourth warning log in the second
  • the IP addresses under the network domain cannot communicate.
  • node 2 checking the network domain address list of node 3 please refer to node 3 checking the network domain address list of node 2, which will not be repeated here.
  • relevant nodes in the communication system can dynamically modify the network domain address list based on user modification instructions, and update the connection status of nodes in the network, that is, manage node communication.
  • the node 3 in the communication system receives the modification instruction as an example for illustration.
  • the consortium chain communication method may also include:
  • the node 3 receives a list modification instruction input by the user; the list modification instruction is used to instruct to modify the network domain address list of the node 3.
  • the modification type and modification information may be included in the list modification instruction.
  • the modification type can be add, update or delete.
  • the modification information may include the network domain name, IP address, etc. to be modified.
  • the application scenario of the list modification instruction whose modification type is "new" can be, for example, as follows: based on the third warning log in the above-mentioned embodiment, the user sends a list modification instruction to node 3, and the list modification instruction is used to indicate that node 3 The IP address of node 3 under the second network domain is added to the list of network domain addresses.
  • a node under the new network domain C is newly added to the communication system, and the node is a neighbor node of node 3, then the user sends a list modification command to node 3, and the list modification command is used to indicate the network domain address of node 3 The IP address of node 3 under the new network domain C is added to the list.
  • the application scenario of the list modification instruction whose modification type is "update” can be, for example, as follows: based on the fourth warning log in the above embodiment, the user sends a list modification instruction to node 3, and the list modification instruction is used to instruct to update the network domain of node 3
  • the IP address of node 3 under the second network domain in the address list is the new IP address.
  • the application scenario of the list modification command whose modification type is "delete” can be, for example, as follows: each node under a certain network domain D is no longer connected to node 3, then the user sends a list modification command to node 3, and the list modification command uses The IP address of node 3 under network domain D in the network domain address list indicating to delete node 3.
  • the modification type can be indicated by adding character information after the modification information, for example, "-I” means adding, “-U” means updating, and "-D” means deleting.
  • the modification type can also be expressed in other ways, for example: ⁇ update: ⁇ domain2:117.11.10.1:50011 ⁇ means to update the IP address under the second network domain to 117.11.10.1:50011.
  • the embodiment of the present application does not set any limitation on the modification type and the specific form of the list modification instruction.
  • Node 3 modifies the network domain address list of node 3 based on the list modification instruction, and broadcasts the modification instruction to neighbor nodes of node 3.
  • the node 3 and each neighbor node of the node 3 exchange the network domain address list, so that each node keeps the network domain address list of the node and each neighbor node of the node.
  • node 3 modifies the network domain address list of node 3 stored in its own node, it needs to further notify each neighbor node of the list modification instruction, so that the neighbor nodes update the network domain address list of node 3 synchronously.
  • Each neighbor node of the node 3 modifies the network domain address list of the node 3 stored respectively based on the list modification instruction.
  • FIG. 10 shows a schematic diagram of a process of dynamically modifying a network domain address list.
  • Node 3 receives the user's list modification instruction, and after modifying the network domain address list of node 3, further broadcasts the modification instruction to the neighbor nodes of node 3: node 2, node 4, ... node n.
  • Node 2 , node 4 , . . . node n modifies the network domain address list of node 3 stored respectively.
  • node 3 may also broadcast the modified network domain address list of node 3 to each neighbor node of node 3, so as to update the network domain address list of node 3 stored in each neighbor node .
  • only the list modification instruction is broadcast to each neighbor node of node 3, which can reduce the broadcast of redundant messages, reduce network congestion, etc., thereby improving the efficiency of network communication and ensuring the efficiency of network communication.
  • each node under the first target domain receives the command broadcast by node 3 , are disconnected from node 3.
  • the list modification instruction is used to instruct to delete “domain2:117.10.11.1:50012” in the network domain address list of node 3, that is, to delete the IP address 117.10.11.1:50012 of node 3 under the second network domain. Then the nodes under the second network domain (including node 2) receive the list modification instruction broadcast by node 3, delete the information from the network domain address list of node 3 respectively saved, and both of them disconnect from node 3. connect.
  • the list modification instruction is used to instruct to update the IP address of node 3 under the second target domain in the network domain address list of node 3 to be the target IP address, then among the neighbor nodes of node 3, the nodes under the second target domain are disconnected. Open a connection with node 3 and re-establish a connection with node 3 based on the destination IP address.
  • the modification type in the list modification instruction is "update”
  • the modification information is to modify the IP address of node 3 under the second target domain to the target IP address
  • each node under the second target domain receives After the list modification instruction broadcasted by node 3, the connection with node 3 is respectively disconnected, and the connection with node 3 is re-established by using the target IP address.
  • the network domain address list of node 3 is originally: ⁇ domain2:117.10.11.1:50012, domain3:10.10.1.1:50011 ⁇ , the list modification command is ⁇ update: ⁇ domain2:117.11.10.1:50011 ⁇ , use The IP address of node 3 under the second network domain in the network domain address list indicated to update node 3 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 3, update the information in the network domain address list of node 3 saved respectively, and both of them disconnect from node 3. Connect and re-establish a connection with node 3 respectively using the IP address 117.11.10.1:50011.
  • node 3 modifies the network domain address list of node 3 based on the list modification instruction.
  • node 3 broadcasts the list modification instruction to each neighbor node of node 3, so that each neighbor node of node 3 updates the network domain address list of node 3 saved respectively, so that the node 3 stored in each node in the communication system All network domain address lists have been updated to ensure the consistency of the network domain address lists in each node, thereby ensuring the accuracy and reliability of communication, and further making the accuracy of the network domain address lists obtained when nodes are discovered , to improve the accuracy of node discovery.
  • the method provided by this embodiment can dynamically configure the IP address, modify the network domain address list, and manage node communication when the communication system is running without restarting the node, thereby simplifying the network communication process and ensuring the network Stability, save user time, and further improve user experience.
  • the above process of dynamically modifying the network domain address list is imperceptible to the user, that is to say, the above process is transparent to the user, which further improves the user experience.
  • each neighbor node of node 3 updates the connection status with node 3 according to the list update command, thereby ensuring the accuracy of node connection, ensuring the reliability of network communication, and further improving user experience.
  • consortium chain communication method is used as an example to describe the scenario where the internal and external network addresses of nodes are mapped through the proxy method for internal and external network communication.
  • the method provided in this embodiment can also be It is applied to any situation that may cause a node to have multiple IP addresses for communication between nodes in multiple network domains, and this application does not limit this.
  • Fig. 11 shows a structural block diagram of a consortium chain communication device provided by an embodiment of the present application, and the consortium chain communication device may be a second node (namely node 2).
  • the consortium chain communication device provided in this embodiment may include:
  • the first receiving module 1101 is configured to receive the first information from the first node through the first connection with the first node; the first connection includes a logical connection, and the connection initiator of the first connection is the first node; the first The information includes the address of the first node under the target network domain, where the target network domain is the network domain where at least one other node is located, and the at least one other node refers to a node other than the second node in the network partition to be joined by the first node; The address of the first node under the target network domain is used for the first node to establish a connection with at least one other node;
  • the first sending module 1102 is configured to send first information to at least one other node.
  • the first node belongs to the first network domain
  • the first receiving module 1101 is further configured to receive a first request message from the first node; the first request message is used to request to provide at least one other node in the first network domain The address under the domain; the address of at least one other node under the first network domain is used for the first node to establish a connection with at least one other node; the first sending module 1102 is also used for responding to the first request message, through the first connection, Sending a first response message to the first node, where the first response message includes an address of at least one other node under the first network domain.
  • the first sending module 1102 is also used to obtain at least one second information; the second information includes the addresses of the nodes in the network partition to be joined among the neighbor nodes of the second node under one or more network domains ; Find the target address from each second information; the target address refers to the address of the node under the first network domain, and the target address includes the address of at least one other node under the first network domain.
  • the first sending module 1102 is specifically configured to search for the target address from each piece of second information when it is determined that the target address is not stored in the preset storage location.
  • the first sending module 1102 is further configured to save the target address in a preset storage location; after a preset time period, clear the target address in the preset storage location.
  • the consortium chain communication device provided in this embodiment is used to execute the steps of node 2 in the consortium chain communication method provided by the method embodiment of the present application.
  • the technical principle and technical effect are similar. For details, please refer to the method embodiment part, and will not repeat them here .
  • Fig. 12 shows a structural block diagram of a consortium chain communication device provided by an embodiment of the present application, and the consortium chain communication device may be a first node (namely node 1). As shown in Figure 12, the consortium chain communication device provided in this embodiment may include:
  • An acquisition module 1201 configured to acquire first information; the first information includes the address of the first node under the target network domain; the target network domain is the network domain where at least one other node is located, and at least one other node refers to the first node to be Nodes in the joined network partition except the second node; the address of the first node under the target network domain is used for the first node to establish a connection with at least one other node;
  • the second sending module 1202 is configured to send the first information to the second node through the first connection with the second node; the first connection includes a logical connection, and the connection initiator of the first connection is the first node.
  • the first node belongs to the first network domain
  • the second obtaining module 1201 is further configured to obtain the address of at least one other node under the first network domain
  • the device further includes a connection module 1203 configured to Addresses of other nodes under the first network domain to establish a connection with at least one other node.
  • the obtaining module 1201 is specifically configured to send a first request message to the target node, the first request message is used to request the target node to provide the address of at least one other node under the first network domain; the target node includes the second node and/or at least one target neighbor node among the neighbor nodes of the first node; receiving a first response message from the target node; the first response message includes an address of at least one other node under the first network domain.
  • connection module 1203 is specifically configured to communicate with at least one other node according to the address of at least one other node in the first network domain under the condition that the address of at least one other node in the first network domain is communicable. establish connection.
  • the acquiring module 1201 is further configured to determine a remote address list of the first node, where the remote address list of the first node includes addresses of at least one other node under the first network domain.
  • the remote address list of the first node further includes indication information for indicating whether the address of each other node under the first network domain is communicable.
  • the first node belongs to the first network domain
  • the remote address list of the first node includes the address of the second node
  • the connection module 1203 is further configured to establish the first node with the second node according to the address of the second node. connect.
  • the consortium chain communication device provided in this embodiment is used to execute the steps of node 1 in the consortium chain communication method provided by the method embodiment of the present application.
  • the technical principle and technical effect are similar. For details, please refer to the method embodiment part, and will not repeat them here .
  • the embodiment of the present application also provides a consortium chain communication system, the system includes a first consortium chain communication device and a second consortium chain communication device, the first consortium chain communication device may be a first node, and the second consortium chain communication device may be for the second node.
  • the first consortium chain communication device is used to execute the steps of node 1 in the communication method provided by the method embodiment of the present application
  • the second consortium chain communication device is used to perform the steps of node 2 in the communication method provided by the method embodiment of the present application
  • the embodiment of this application also provides an electronic device, which can be the first consortium chain communication device in the first node in the above application embodiment, or the second consortium chain communication device in the above application embodiment.
  • the electronic device includes: a processor 1301 , a receiver 1302 , a transmitter 1303 , a memory 1304 and a bus 1305 .
  • the processor 1301 includes one or more processing cores, and the processor 1301 executes applications of various functions and information processing by running software programs and modules.
  • the receiver 1302 and the transmitter 1303 can be implemented as a communication component, and the communication component can be a baseband chip.
  • the memory 1304 is connected to the processor 1301 through a bus 1305 .
  • the memory 1304 may be used to store at least one program instruction, and the processor 1301 may be used to execute the at least one program instruction, so as to implement the technical solutions of the foregoing embodiments. Its implementation principle and technical effect are similar to those of the related embodiments of the method above, and will not be repeated here.
  • 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.
  • the processor performs baseband processing on the data to be sent, and outputs the baseband signal to the control circuit in the control circuit. send.
  • the control circuit receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor, and the processor converts the baseband signal into data and processes the data.
  • FIG. 13 only shows a memory and a processor. In an actual electronic device, there may be multiple processors and memories.
  • a storage may also be called a storage medium or a storage device, etc., which is not limited in this embodiment of the present application.
  • 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 software programs and processing data of the software programs.
  • the baseband processor and the central processing unit may be integrated into one processor, or may be independent processors interconnected through technologies such as a bus.
  • an electronic device may include multiple baseband processors to adapt to different network standards, an electronic device may include multiple central processors to enhance its processing capability, and various components of the electronic device may be connected through 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 communication data can be built in the processor, or can 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 can be integrated in the processor, or it can be independent from the processor.
  • the memory includes a high-speed cache, which can store frequently accessed data/instructions.
  • 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 block diagrams 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 the methods disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor.
  • the memory may be a non-volatile memory, such as a hard disk (hard disk drive, HDD) or a solid-state drive (solid-state drive, SS), etc., or a volatile memory (volatile memory), such as Random-access memory (RAM).
  • a memory is, without limitation, 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.
  • the memory in the embodiment of the present application may also be a circuit or any other device capable of implementing a storage function, and is used for storing program instructions and/or data.
  • the methods provided in the various embodiments of the present application may be fully or partially implemented by software, hardware, firmware or any combination thereof. When implemented using software, it 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 the computer program instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application will be generated in whole or in part.
  • the computer may be a general purpose computer, a special purpose computer, a computer network, network equipment, user equipment or other programmable devices.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server or data center Transmission to another website site, computer, server, or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL) or wireless (such as infrared, wireless, microwave, etc.).
  • the readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes one or more available media integrated.
  • the available medium can be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape, etc.) ), optical media (for example, digital video disc (DWD), or semiconductor media (for example, SSD), etc.
  • the embodiment of the present application also provides a computer-readable storage medium, the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps in any of the foregoing method embodiments can be implemented.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请提供了一种通信方法、系统、电子设备及可读存储介质。该通信方法包括：通过与第一节点之间的第一连接接收来自第一节点的第一信息；第一连接的连接发起方为第一节点；第一信息中包括第一节点在目标网络域下的地址，目标网络域为至少一个其他节点所在的网络域，至少一个其他节点是指第一节点待加入的网络分区中除第二节点外的节点；第一节点在目标网络域下的地址用于第一节点与至少一个其他节点建立连接；向至少一个其他节点发送第一信息。该方法能够实现联盟链中使用代理方式通信场景下节点的自发现。

Description

通信方法、系统、电子设备及可读存储介质
本申请要求于2021年12月24日提交国家知识产权局、申请号为202111599322.9、申请名称为“通信方法、系统、电子设备及可读存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及区块链技术领域，尤其涉及一种通信方法、系统、电子设备及可读存储介质。
背景技术
联盟区块链，简称联盟链，是区块链中的一种。联盟链只针对某个特定群体的成员和有限的第三方，其内部指定多个预选节点为记账人，每个块的生成由所有的预选节点共同决定。联盟链在应用的过程中，需要进行跨域通信。相关技术中，联盟链的跨域通信主要通过NAT(Network Address Translation，网络地址转换)穿透技术实现。然而，NAT穿透技术存在安全性不高等问题，因而，联盟链中一些节点对应的机构希望通过代理方式与外界进行通信。
另外一方面，在区块链网络中，节点发现是一个很重要的技术。在一个新节点通过已知的节点加入到网络时，新节点所知的网络节点信息有限的情况下，通过节点发现能够获知更多的节点，从而建立起足够的连接。
基于以上两方面的情况，有必要针对联盟链中使用代理方式通信的场景下，基于节点发现的网络通信方法进行研究，以满足用户的需求。
发明内容
本申请提供一种通信方法、系统、电子设备及可读存储介质，实现了联盟链中使用代理方式通信场景下节点的自发现，满足了用户需求。
第一方面，本申请实施例提供了一种通信方法，该方法包括：通过与第一节点之间的第一连接接收来自第一节点的第一信息；第一连接包括逻辑连接，第一连接的连接发起方为第一节点；第一信息中包括第一节点在目标网络域下的地址，目标网络域为至少一个其他节点所在的网络域，至少一个其他节点是指第一节点待加入的网络分区中除第二节点外的节点；第一节点在目标网络域下的地址用于第一节点与至少一个其他节点建立连接；向至少一个其他节点发送第一信息。
第二方面，本申请实施例提供一种通信方法，方法包括：获取第一信息；第一信息中包括第一节点在目标网络域下的地址；目标网络域为至少一个其他节点所在的网络域，至少一个其他节点是指第一节点待加入的网络分区中除第二节点外的节点；第一节点在目标网络域下的地址用于第一节点与至少一个其他节点建立连接；通过与第二节点之间的第一连接，向第二节点发送第一信息；第一连接包括逻辑连接，第一连接的连接发起方为第一节点。
第三方面，本申请实施例提供一种通信方法，该方法包括：第三节点接收来自第二节点的第一节点在目标网络域下的地址，目标网络域为至少一个其他节点所在的网络域，至少一个其他节点是指第一节点待加入的网络分区中除第二节点外的节点，至少一个其他节点包括第三节点；第三节点根据第一节点在目标网络域下的地址与第一节点建立连接。至少一个其他节点和第二节点属于同一个网络分区，网络分区为第一节点待加入的网络分区。
第四方面，本申请实施例提供了一种联盟链通信装置，该联盟链通信装置可以为第二节点，也可以为应用于第二节点中的装置(比如芯片或者处理电路)，该装置包括：第一接收模块，用于通过与第一节点之间的第一连接接收来自第一节点的第一信息；第一连接包括逻辑连接，第一 连接的连接发起方为第一节点；第一信息中包括第一节点在目标网络域下的地址，目标网络域为至少一个其他节点所在的网络域，至少一个其他节点是指第一节点待加入的网络分区中除第二节点外的节点；第一节点在目标网络域下的地址用于第一节点与至少一个其他节点建立连接；第一发送模块，用于向至少一个其他节点发送第一信息。
第五方面，本申请实施例提供了一种联盟链通信装置，该联盟链通信装置可以为第一节点，也可以为应用于第一节点中的装置(比如芯片或者处理电路)，该装置包括：获取模块，用于获取第一信息；第一信息中包括第一节点在目标网络域下的地址；目标网络域为至少一个其他节点所在的网络域，至少一个其他节点是指第一节点待加入的网络分区中除第二节点外的节点；第一节点在目标网络域下的地址用于第一节点与至少一个其他节点建立连接；第二发送模块，用于通过与第二节点之间的第一连接，向第二节点发送第一信息；第一连接包括逻辑连接，第一连接的连接发起方为第一节点。
第六方面，本申请实施例提供了一种联盟链通信系统，包括：第一节点和第二节点，第二节点，用于执行上述第一方面中任一项的方法，第一节点用于执行上述第二方面中任一项的方法。
在本申请的一个可选的实施例中，上述联盟链通信系统还可以包括至少一个其他节点。至少一个其他节点与第二节点属于同一个网络分区，网络分区为第一节点待加入的网络分区。
第七方面，本申请实施例提供了一种计算机设备，包括：存储器、处理器以及存储在存储器中并可在处理器上运行的计算机程序，处理器执行计算机程序时实现上述第一方面中任一项的通信方法，或者实现上述第二方面中任一项的通信方法。
第八方面，本申请实施例提供了一种计算机可读存储介质，计算机可读存储介质存储有计算机程序，计算机程序被处理器执行时实现上述第一方面中任一项的通信方法，或者实现上述第二方面中任一项的通信方法。
本申请提供的通信方法、装置、系统、电子设备及计算机可读存储介质，第二节点通过与第一节点之间的第一连接，接收第一节点发送的第一信息，并将第一信息发送给其他节点。第一信息中包括第一节点在至少一个其他节点所在的目标网络域下的地址，因而其他节点接收到第一节点在至少一个其他节点所在的目标网络域下的地址能够根据该地址与第一节点建立连接。本实施例中，第一节点主动将第一信息发送至第二节点，也就是说，本实施例通过PUSH形式的节点发现技术，实现了联盟链中使用代理方式通信场景下节点的自发现，满足了用户需求。而且，联盟链本身对于节点的身份验证较为严格，因而在联盟链中通过PUSH的方式进行节点发现，能够避免Eclipse攻击和Sybil攻击等，安全性较高。另外，本实施例提供的方法，第二节点在发送第一信息时，仅将第一信息发送至待加入的网络分区中的节点(即其他节点)，从而使得第一节点仅与待加入的网络分区中的节点连接，实现了节点发现的分区隔离，不仅满足了联盟链中多个网络分区通信的场景下的节点自发现，且节点发现的分区隔离不会造成业务执行的混乱，进一步满足用户需求。
附图说明
为了更清楚地说明本申请实施例中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1是本申请一实施例提供的联盟链通信系统的网络拓扑图；
图2是本申请另一实施例提供的联盟链通信系统的网络拓扑图；
图3是本申请一实施例提供的通信方法的流程示意图；
图4是本申请另一实施例提供的通信方法的流程示意图；
图5是本申请又一实施例提供的通信方法的流程示意图；
图6是本申请又一实施例提供的网络域地址列表的获取方法的流程示意图；
图7是本申请一实施例提供的节点2的网络域地址列表的获取方法的流程示意图；
图8是本申请一实施例提供的检查网络域地址列表的方法的流程示意图；
图9是本申请一实施例提供的动态修改网络域地址列表的方法的流程示意图；
图10是本申请一实施例提供的动态修改网络域地址列表的过程示意图；
图11是本申请一实施例提供的联盟链通信装置的结构框图；
图12是本申请另一实施例提供的联盟链通信装置的结构框图；
图13是本申请一实施例提供的电子设备的结构示意图。
具体实施方式
为了使本申请的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本申请进行进一步详细说明。应当理解，此处所描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。
可以理解，本申请实施例中的术语“第一”、“第二”、“第三”、“第四”等(如果存在)是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
可以理解，本申请所使用的术语“和/或”是指相关联列出的项中的一个或多个的任何组合以及所有可能组合，并且包括这些组合。
在对本申请实施例进行详细地解释说明之前，先对本申请实施例的应用场景予以说明。
本申请实施例提供的方法可以应用于联盟链通信系统，联盟链通信系统的应用场景包括但不限于商品溯源、公益慈善、供应链金融、电子政务、互助保险或物联网等，本申请对此不做任何限定。
示例性的，图1为本申请实施例提供的一例联盟链通信系统(以下简称通信系统)的网络拓扑图。如图1所示，该通信系统包括多个网络域，每个网络域中设置有至少一个区块链节点(下文简称节点)。可选的，本申请实施例所涉及的节点对应联盟链中的各个机构，其可以为服务器也可以为终端。
本申请实施例中涉及的概念和定义如下：
跨域通信：不同网络域中的节点之间的通信。例如图1中的节点1与节点2的通信。
邻居节点：与某一节点存在邻居关系的节点称为该节点的邻居节点。如图1中，节点1的邻居节点包括节点2、节点3、节点4和节点5；节点2的邻居节点包括节点1、节点3和节点5。
本域：某一节点所在的域称为该节点的本域。
相关域：对于某一节点而言，存在该节点的邻居节点的非本域的网络域称为该节点的相关域。如图1中，节点1的相关域包括第二网络域和第三网络域，节点2的相关域包括第一网络域和第三网络域，节点3的相关域包括第一网络域和第二网络域。
网络分区：为了向网络中的节点对应的机构提供不同的服务，将网络划分为多个区，每个区称为一个网络分区。每个网络分区中可以包括一个或多个节点。同一网络分区中的节点可以相互通信，不同网络分区中的节点不能通信。如图1所示，节点1、节点2、节点3和节点4属于第一网络分区，节点2和节点5属于第二网络分区。第一网络分区中相互连接的节点可以通信，第二网络分区中相互连接的节点可以通信，但是第一网络分区中的节点和第二网络分区中的节点不能直接通信。例如，节点1与节点5不属于同一网络分区，不能直接通信。
示例性的，图2为本申请另一个实施例提供的网络拓扑图。如图2所示，该网络包括节点(node)0至node 9共10个节点，包括三个网络分区：ns1、ns2和global。ns1中包括node 3、node 4、node  5、node 6、node 7和node 9，ns2中包括node 0和node 8。global中包括node 1、node 2、node 3和node 4。以node4为例来说，node4可以与node1、node2、node3、node9通信，但是不可以与node8和node0通信。
物理连接：利用物体的物理特性实现的连接。物理连接能够实现节点与节点之间的物理网络通信。物理连接是逻辑连接的基础。
逻辑连接：建立于物理连接的基础上。也就是说，若两个节点之间建立了逻辑连接，则必然建立了物理连接。但是，两个节点之间建立了物理连接，未必建立逻辑连接。
通过建立逻辑连接，能够实现节点与节点之间的业务消息的通信。若未建立逻辑连接，仅建立物理连接，两个节点之间只能够收发建立连接的相关消息以及检活消息，不能够收发业务消息，即使一端节点错误发送了业务消息，也不会被对端节点接收，只有在建立物理连接的基础上进一步建立逻辑连接，才能收发业务消息。逻辑连接需要验证节点身份，一旦节点发现对端节点是不合法的节点，该节点立即断开逻辑连接和物理连接。
另外，在包括多个网络分区的网络拓扑中，两个节点之间有且只有一条物理连接，但是，逻辑连接可以有多条。例如，图2中，node 3和node 4既属于第一网络分区，又属于第三网络分区。node 3和node 4之间有且只有一条物理连接，但是，node 3和node 4之间可以包括两条逻辑连接L1和L2，其中，逻辑连接L1用于在第一网络分区中的通信，逻辑连接L2用于在第三网络分区中的通信。
如图1所示，联盟链在应用过程中，涉及到跨域通信。相关技术中，跨域通信主要通过NAT穿透技术实现。然而，由于联盟链的特殊性，联盟链中的一些机构对网络的安全性有更高的要求，因而，这些机构希望通过代理方式与外部(其他网络域)进行通信，即，通过代理方式映射节点内外网址进行内外网通信，以隐藏该机构的内部IP地址。这样，就可能出现一个机构给不同网络域中的机构连接用的IP地址不同的情况，尤其是在使用反向代理时。也就是说，通信系统中，一个节点会同时存在多个IP地址供多个网络域中的节点通信。例如，图1中节点1供第一网络域中的节点通信的IP地址为A，供第二网络域中的节点通信的IP地址为B。
目前，很多联盟链并没有考虑到机构需要使用代理方式通信的场景，因而有必要针对用户此需求对联盟链中节点之间的通信进行研究，其中，包括对于联盟链中节点的发现技术的研究。
在区块链网络中，节点发现是一个很重要的技术。试想，如果没有节点发现技术，在一个庞大的网络中，存在成百上千的节点，若一个新的节点需要加入该网络，则必须配置这成百上千节点的IP地址。这将非常复杂且非常耗时。而节点发现技术可以解决这个问题。新节点在加入网络时，只需要配置网络中的少数节点的IP地址，新节点与这少数节点建立连接后，通过节点发现即可发现网络中的其他节点，并与其他节点建立连接。
相关技术中，一些区块链项目虽然已经实现了节点发现功能，但是，这些节点发现技术都无法应用于联盟链中使用代理方式通信的场景下。
另外一方面，联盟链中，可能会存在多个网络分区，通信过程中存在跨网络分区的情况。如上所述，不同网络分区之间的业务消息是隔离的，这种应用场景对于节点发现的研究又是一种限制。
基于上述几方面的原因，本申请实施例旨在对于联盟链中使用代理方式通信，且可能存在多个网络分区通信的场景下节点发现及连接的方法进行研究，以满足用户在实际使用中的多种需求。
下面将结合图1，对本申请中的技术方案进行详细描述。需要说明，在不冲突的情况下，本申请中不同的技术特征之间可以相互结合。
本实施例提供的通信方法用于实现节点1与待加入的网络分区中需要连接的节点的连接。也就是说，本实施例中，以节点1为新加入节点为例，节点1需要加入的网络分区称为待加入的网 络分区。待加入的网络分区中包括节点2和至少一个其他节点(即，节点2和至少一个其他节点均属于节点1的待加入的网络分区)。
具体的，参见图1，以下实施例中，以节点1为新加入节点，待加入的网络分区为第一网络分区为例，对通信方法进行说明。如图1所示，至少一个其他节点可以包括节点3和节点4。各个节点所属的网络域如图1所示。本实施例提供的通信方法用于实现节点1与节点2，以及其他节点中的节点4的连接。
需要说明的是，本申请实施例中以节点1加入第一网络分区为例进行说明。但是，本实施例提供的方法可以应用于包括一个或多个网络分区的通信系统中。对于通信系统中其他的新加入节点，以及节点1需要加入的其他的网络域分区均参照本申请实施例过程执行即可，本申请实施例不再一一赘述。
示例性的，图3示出了本申请提供的通信方法的示意性流程图。如图3所示，该方法可以包括：
S301、节点1与节点2建立第一连接；第一连接包括逻辑连接；节点1为第一连接的连接发起方，节点2为第一连接的连接接收方。
连接发起方(或称为发起方节点)，即两个节点中发送连接请求的一方，连接接收方(或称为接收方节点)，即两个节点中接收并响应连接请求的一方。需要说明的是，两个节点在连接的过程中，可能出现节点连接碰撞的情况，即两个节点同时向对方发起连接请求。发生节点连接碰撞时，根据预设规则，两个节点中的其中一个节点将放弃连接请求，并接收对端节点发送的连接请求，从而建立连接。本实施例中，由于节点2运行在网络中，并不知道节点1的IP地址，所以在这种情况下，节点1必然是作为连接发起方，不存在连接碰撞的问题。
可选的，节点1可以根据节点1的远程地址(remote address)列表中节点2的IP地址(以下称第一IP地址)，向节点2发起连接请求。其中，第一IP地址可以通过用户配置得到。
具体的，用户可以对节点2的代理节点进行配置，以获取能够供节点1连接的第一IP地址，并将该第一IP地址配置于节点1的远程地址列表中。用户完成配置并启动节点后，节点1根据其远程地址中的第一IP地址向节点2发起连接，节点2响应连接请求，从而建立第一连接。
需要说明的是，根据实际使用需求的不同，本申请实施例涉及的IP地址可以为代理(包括正向代理和反向代理)节点提供的IP地址，也可以为NAT网关提供的IP地址，本申请对此不做任何限定，且下述实施例对于各个IP地址的来源不再赘述。
S302、节点1获取第一网络域地址列表；第一网络域地址列表用于表征节点1在至少一个网络域下的IP地址，其中，第一网络域地址列表中包括节点1在至少一个其他节点所在的网络域下的IP地址。
需要说明的是，本申请实施例中，某一节点在某一网络域下的IP地址是指该节点供该网络域中的节点通信连接的IP地址。例如，节点1在第一网络域下的IP地址A是指节点1供第一网络域中的节点通信连接的IP地址。换句话说，第一网络域中节点通过该IP地址A与节点1通信连接。
可选的，第一网络域地址列表中可以包括节点1在其本域和相关域下的IP地址，其他节点可能位于节点1的本域中，也可能位于节点1的相关域中。第一网络域地址列表中至少包括节点1在一个其他节点的网络域下的IP地址。第一网络域地址列表中的各个IP地址可以由用户配置得到。配置过程与上述节点1的远程地址列表的配置过程相似，在此不再赘述。
参照图1，节点1位于第一网络域，节点1的相关域包括第二网络域和第三网络域。第一网络域地址列表中可以包括节点1在第一网络域下的IP地址、第二网络域下的IP地址。例如，第一网络域地址列表可以为：{domain1:10.10.1.1:50011，domain2:117.10.11.1:50012， domain3:117.10.11.1:50013}。其中，domain1表示第一网络域，domain2表示第二网络域，domain3表示第三网络域。即，节点1提供给第一网络域中的节点4连接的IP地址为10.10.1.1:50011，节点1提供给第二网络域中的节点2和节点5连接的IP地址为117.10.11.1:50012，节点1提供给第三网络域中的节点3连接的IP地址为117.10.11.1:50013。也就是说，第一网络域地址列表中包括节点1在其他节点3和其他节点4所在的网络域下的IP地址。
S303、节点1基于第一连接，将第一网络域地址列表发送至节点2。
可以理解，节点1在发送第一网络域地址列表的同时，也可以将第一网络域地址列表存储于节点1的存储器中。
S304、节点2接收第一网络域地址列表。
S305、节点2将第一网络域地址列表广播至第一网络分区中的各个节点。
可选的，节点2可以使用Gossip协议广播至第一网络分区中所有节点。需要注意的是，这里节点2作为第一连接的接收方，将第一网络域地址列表广播，广播的对象是第一网络分区中的所有节点，而非节点2的邻居节点。节点2采用Gossip协议，周期性的随机选择一些节点传递第一网络域地址列表，这样能够减少网络中的冗余消息。
其他节点接收第一网络域地址列表，并从第一网络域地址列表中获取节点1在其他节点所在网络域下的IP地址。下面以图1中其他节点中的节点4为例进行说明，其他的其他节点与节点4过程相同，不再赘述。
S306、节点4接收第一网络域地址列表，并从第一网络域地址列表中获取节点1在节点4所在的网络域下的IP地址。
也就是说，节点4从第一网络域地址列表中查找节点1在第一网络域下的IP地址。若第一网络域地址列表中未包括节点1在第一网络域下的IP地址，则节点4丢弃该消息(接收到的第一网络域地址列表)；若包括，则执行步骤S307。
S307、节点4确定节点1在节点4所在的网络域下的IP地址是否可通信。
具体的，节点4可以向节点1在节点4所在的网络域下的IP地址发起连接请求，确定是否可以通过该IP地址实现与节点1的通信。若发起连接请求后接收到对方的响应或反馈，则节点1确定该IP地址可通信。否则，节点1确定该IP地址不可通信。该实现方式中，在建立连接之前，节点4确定IP地址的可通信性，以减少无用的消息和通信，提高连接效率。
若节点4确定该IP地址不可通信，则节点4丢弃该IP地址；若节点4确定该IP地址可通信，则执行步骤S308。
S308、节点4根据节点1在节点4所在的网络域下的IP地址，与节点1建立连接。
通过上述过程，节点1能够实现对节点3和节点4的发现和连接。且上述过程中，节点1主动将其第一网络域地址列表发送至节点2，因而上述节点发现过程为PUSH形式的节点发现。本实施例中，通过PUSH形式的节点发现技术，实现了联盟链中使用代理方式通信场景下节点的自发现，满足了用户需求；且联盟链本身对于节点的身份验证较为严格，因而在联盟链中通过PUSH的方式进行节点发现，能够避免Eclipse攻击和Sybil攻击等，安全性较高。而且，本实施例中提供的方法能够应用于包括单个网络分区的网络系统，也能够应用于包括多网络分区的网络系统，满足用户的不同需求，适用性强。另外，本实施例提供的方法，节点2在广播第一网络域地址列表时，仅将第一网络域地址列表广播至第一网络分区中的节点，从而使得节点1仅与第一网络分区中的其他节点连接，实现了节点发现的分区隔离，不仅满足了联盟链中多个网络分区通信的场景下的节点自发现，且节点发现的分区隔离不会造成业务执行的混乱，进一步满足用户需求。
除此之外，如上述实施例，第一网络分区中的各个节点可能位于同一网络域，也可能位于不同的网络域，因而，本实施例提供的方法，不仅可以应用于包括仅一个网络域的网络系统，也可 以应用于包括多个网络域的网络系统，即本实施例提供的方法可以实现跨域通信中的节点发现和连接，进一步满足了用户在跨域通信场景下的网络建立需求，提高用户体验。
在一个实施例中，上述步骤S308之后，所述方法还包括：
S309、节点4将节点1在节点4所在的网络域下的IP地址写入节点4的远程地址列表中。
该实现方式中，在实现连接之后，节点4进一步将节点1的IP地址回写至节点4的远程地址列表中，通过这种方式，节点4能够逐渐完善其远程地址列表，实现远程地址列表的自动回写，减少用户对于远程地址列表的配置，提高用户体验。
在一个实施例中，节点在采用PUSH方式进行节点发现的同时，还可以进一步采用PULL方式进行节点发现。具体的，参见图4，本实施例中提供的通信方法包括：
S401、节点1基于第一连接向节点2发送第一请求消息。
第一请求消息也称为第一节点请求消息(peer request)。第一请求消息用于指示节点2生成第一响应消息。第一响应消息也称为第一节点响应消息(peer response)。
S402、节点2接收第一请求消息。
S403、节点2响应于第一请求消息，获取至少一个第三网络域地址列表；第三网络域地址列表用于表征节点2的邻居节点中，位于第一网络分区中的节点在至少一个网络域下的IP地址。
节点2中可以预先存储有节点2的网络域地址列表，还可以存储有节点2的各个邻居节点的网络域地址列表。节点2从邻居节点的网络域地址列表中挑选出位于第一网络分区中的节点的网络域地址列表，得到第三网络域地址列表。关于节点2中存储的各个网络域地址列表的来源将在后续实施例进行说明。
S404、节点2从第三网络域地址列表中查找目标IP地址；目标IP地址是指节点在第一网络域下的IP地址，目标IP地址中包括至少一个其他节点在第一网络域下的IP地址。
具体的，节点2一一查找各个第三网络域地址列表，从中挑出每个网络域地址列表中存在于第一网络域下的IP地址，得到上述目标IP地址。
S405、节点2根据目标IP地址生成第一响应消息。
S406、节点2基于第一连接，将第一响应消息返回至节点1。
S407、节点1确定第一响应消息中其他节点(图4中以节点4为例)在第一网络域下的IP地址是否可通信。
该步骤的具体过程及有益效果与上述步骤S307类似，在此不再赘述。
若节点1确定第一响应消息中其他节点在第一网络域下的IP地址不可通信，则节点1丢弃该IP地址；若节点1确定该IP地址可通信，则执行步骤S408。
S408、节点1根据第一响应消息中其他节点在第一网络域下的IP地址，与其他节点建立连接。
例如，图1中，节点1与节点2建立连接后，节点1向节点2发送第一请求消息，节点2响应第一请求消息，生成第一响应消息。具体的，节点2的邻居节点包括节点1、节点3和节点5。由于步骤S301中，节点1与节点2已建立连接，因而节点1的网络域地址列表为重复消息，不必发送。且节点5不属于第一网络分区，因而，节点5的网络域地址列表也不可发送。所以，节点1将节点3的网络域地址列表作为上述第三网络域地址列表，从中查找在第一网络域下的IP地址，得到节点3在第一网络域下的IP地址。节点2将节点3在第一网络域下的IP地址作为目标IP地址，根据目标IP生成第一响应消息，并将第一响应消息发送至节点1。节点1根据第一响应消息中节点3在第一网络域下的IP地址，与节点3建立连接。
通过上述过程，节点1能够实现对节点3的发现和连接。且上述过程中，节点1通过向节点2拉取的方式获取节点3的IP地址，上述节点发现过程为PULL形式的节点发现。本实施例中，通过PULL形式的节点发现技术，实现了联盟链中使用代理方式通信场景下节点的自发现，满足 了用户需求；且联盟链本身对于节点的身份验证较为严格，因而在联盟链中通过PULL的方式进行节点发现，能够避免Eclipse攻击和Sybil攻击等，安全性较高。另外，本实施例提供的方法，节点2向节点1返回的第一响应消息是从第三网络域列表中查找得到，第三网络域地址列表为节点2的邻居节点中位于第一网络分区的节点的网络域地址列表，因而节点2返回给节点1的消息不包括其他网络分区的消息，实现了节点发现的分区隔离，不仅满足了联盟链中多个网络分区通信的场景下的节点自发现，且节点发现的分区隔离不会造成业务执行的混乱，进一步满足用户需求。
而且，本实施例提供的方法，在采取PUSH的方式进行节点发现的同时，采用了PULL方式进行节点发现，两种方式相辅相成，能够更快更多的发现节点，提高节点连接的效率。具体的，采用PUSH方式节点发现时可能存在第一网络域地址列表中未配置有些其他节点所在的网络域下的IP地址，或者配置的IP地址不可通信的情况，采用PULL方式可能能够获取到该其他节点在第一网络域下的IP地址，由节点1与该节点建立连接。采用PULL方式节点发现时，对于节点1属于一新增网络域的情况，节点2中未存储任何节点在该新增网络域下的IP地址，则节点2无法返回响应消息给节点1，采用PUSH方式节点发现能够对此进行弥补。
需要说明的是，无论是采用PUSH的方式，还是PULL的方式，或者PUSH和PULL方式结合进行节点发现和连接时，若发现某一可通信的IP地址已经连接，则节点可以不再进行重复操作，即仅对未连接的节点进行连接。
在一个实施例中，上述步骤S403之前，该方法还包括：
S409、节点2确定预设存储位置(下述均以缓存为例)是否存储有目标IP地址。
若缓存中存储有目标IP地址，则节点2不执行任何操作。
若缓存中未存储目标IP地址，则节点执行上述步骤S403，且在步骤S404之后，该方法还包括：
S410、节点2将目标IP地址保存至缓存中。
S411、预设时长之后，节点2清除缓存中的目标IP地址。
也就是说，每次获取到目标IP地址后，节点2将该目标IP地址保存在缓存中预设时长。若在这预设时长内节点2再次接收到节点1发送的第一请求消息，则节点2不再向节点1返回第一响应消息。若在预设时长之后节点2再次接收到节点1发送的第一请求消息，则节点2按照上述步骤S403至S405，向节点1返回第一请求消息。这样，既能够减少网络中冗余消息，又能够在消息发送过程中出现丢包或其他无法送达的情况下，再次将包括目标IP地址的第一响应消息发送至节点1，保证了消息的尽力交付。
可选的，预设时长可以根据节点1发送第一请求消息的周期，以及网络环境的具体情况确定。例如，若网络环境良好，丢包现象很少发生，则可以将预设时长设置的长一些，比发送第一请求消息的周期大较多。若网络环境较差，时常出现丢包现象，则可以将预设时长设置短一些，比发送第一请求消息的周期略大。
在一个实施例中，上述步骤S408之后，所述方法还包括：
S412、节点1将第一响应消息中其他节点在第一网络域下的IP地址列表写入节点1的远程地址列表中。
该实现方式中，在实现连接之后，节点1进一步可通信的其他节点在第一网络域下的IP地址回写至节点1的远程地址列表中，通过这种方式，节点1能够逐渐完善其远程地址列表，实现远程地址列表的自动回写，减少用户对于远程地址列表的配置，提高用户体验。
示例性的，图5为又一个实施例中通信方法的流程示意图。本实施例中，节点1在加入上述第一网络分区之后，还可以进一步进行定时节点发现。具体的，如图5所示，所述方法还包括：
S501、节点1按照预设周期向节点1的邻居节点中的K个目标邻居节点发送第二请求消息。
K为大于或等于1的整数。可选的，节点1可以随机选择K个邻居节点作为目标邻居节点。
S502、目标邻居节点接收第二请求消息。
S503、目标邻居节点响应于第二请求消息，获取至少一个第四网络域地址列表。
第四网络域地址列表用于表征目标邻居节点的邻居节点中，位于第一网络分区中的节点在至少一个网络域下的IP地址。
S504、目标邻居节点从第四网络域地址列表中查找目标IP地址；目标IP地址是指节点在第一网络域下的IP地址，目标IP地址中包括至少一个其他节点在第一网络域下的IP地址。
S505、目标邻居节点根据目标IP地址生成第二响应消息。
S506、目标邻居节点将第二响应消息返回至节点1。
S507、节点1确定第二响应消息中其他节点在第一网络域下的IP地址是否可通信。
若节点1确定第二响应消息中其他节点在第一网络域下的IP地址不可通信，则节点1丢弃该IP地址；若节点1确定该IP地址可通信，则执行步骤S508。
S508、节点1根据第二响应消息中其他节点(图5中以节点4为例)在第一网络域下的IP地址，与其他节点建立连接。
本实施例中，第二请求消息和第二响应消息与上述实施例中第一请求消息和第一响应消息类似，步骤S502至步骤S508与上述步骤S402至步骤S408类似，在此不再赘述。
另外，该实现方式中，目标邻居节点和节点1也可以进一步执行与上述步骤S409至S412的过程，具体过程不再赘述。
同时，同上述实施例，定时发现过程中，若发现的某一可通信的IP地址已经连接，则节点可以不再进行重复操作，即仅对未连接的节点进行连接。
该实现方式中，在节点与第一网络分区中部分节点建立连接后，通过定时节点发现，再次发现节点，并与未建立连接的节点建立连接。定时节点发现能够及时发现前期因为消息丢失、节点暂时宕机等原因未发现的节点，并实现连接，使得节点发现更加全面，网络建立更加全面和准确。
下面结合实施例，对待加入的网络分区中各个节点中存储的网络域地址列表的获取过程进行说明。可选的，节点可以在建立连接时相互交换网络域地址列表，并在加入网络后，对网络域地址列表进行更新。下面，以节点2和节点3建立连接过程交换网络域地址列表的过程为例进行说明，其他的节点与此类似，不再重复说明。
示例性的，图6为本申请一个实施例提供的网络域地址列表的获取过程的流程示意图，如图6所示，该过程包括：
S101、节点3与节点2建立第二连接，其中，节点3位于第三网络域，节点2位于第二网络域。
节点3和节点2建立第二连接的过程与节点1与节点2建立第一连接的过程类似，在此不再赘述。
需要说明的是，节点3和节点2在连接的过程中，可能出现节点连接碰撞的情况。发生节点连接碰撞时，根据预设规则，两个节点中的其中一个节点将放弃连接请求，并接收对端节点发送的连接请求，从而建立连接。本申请实施例中，有连接碰撞时，所述的连接发起方是指两个节点中发起连接请求并成功建立连接的一方；对应的连接接收方是指两个节点中接收并响应连接请求，并成功建立连接的一方。
为了便于说明，下述实施例中，以节点3为第二连接的连接发起方，节点2为第二节点的连接接收方为例进行说明。
S102、节点3获取节点3的网络域地址列表；节点3的网络域地址列表用于表征节点3在至 少一个网络域下的IP地址，节点3的网络域地址列表中至少包括节点3在第三网络域下的IP地址。
S103、节点3基于第二连接，将节点3的网络域地址列表发送至节点2。
可以理解，节点3在发送节点3的网络域地址列表的同时，也可以将节点3的网络域地址列表存储于节点3的存储器中。
S104、节点2接收并保存节点3的网络域地址列表。
S105、节点2获取节点2的网络域地址列表；节点2的网络域地址列表用于表征节点2在至少一个网络域下的IP地址，第二网络域地址列表中至少包括节点2在第二网络域下的IP地址。
S106、节点2基于第二连接，将节点2的网络域地址列表发送至节点3。
可以理解，节点2在发送节点2的网络域地址列表的同时，也可以将节点2的网络域地址列表存储于节点2的存储器中。
S107、节点3接收并保存节点2的网络域地址列表。
通过上述过程，节点3与节点2交换了网络域地址列表。这样，节点3和节点2中均保存有节点3的网络域地址列表和节点2的网络域地址列表。
上述过程对于每个节点来说，可以使用多个IP地址与不同域进行通信，而不必指定一个节点只能使用一个IP地址，这样使得联盟链的组网更加的灵活性，且能够满足用户在联盟链中使用代理方式映射节点内外网址进行内外网通信的需求，提高用户体验。
以上为节点3与节点2交换网络域地址列表的过程。可以理解，通信系统中存在邻居关系的任意两个节点均可以通过上述过程交换各自的网络域地址列表。如此以来，通信系统中每个节点均可以保存有本节点和本节点的各个邻居节点的网络域地址列表，从而每个节点均可以获知与邻居节点通信的IP地址，从而便于实现上述节点发现过程。
在一个实施例中，当节点3为第二连接中的连接发起方，节点2为第二连接中的连接接收方时，节点2的网络域地址列表中节点2在第三网络域下的IP地址也可以通过动态回写得到。具体的，节点3在向节点2发送节点3的网络域地址列表的同时，将节点3的远程地址列表中节点2的IP地址(以下称第二IP地址)也发送至节点2。
基于此，参见图7，步骤S104、节点2获取节点2的网络域地址列表，具体包括：
S1041、节点2获取节点2的原始网络域地址列表。
可选的，节点2的原始网络域地址列表中可以包括节点2在第三网络域下的IP地址。可选的，可能由于用户未配置等原因，节点2的原始网络域地址列表中也可以未包括节点2在第三网络域下的IP地址。
S1042、节点2判断节点2的原始网络域地址列表中是否包括节点2在第三网络域下的IP地址；
若包括，则执行步骤S1043；
若未包括，则执行步骤S1044。
S1043、将节点2的原始网络域地址列表作为节点2的网络域地址列表。
S1044、将第二IP地址作为节点2在第三网络域下的IP地址写入节点2的原始网络域地址列表，得到节点2的网络域地址列表。
可以理解，由于节点3通过第二IP地址与节点2建立了连接，那么说明第二IP地址是可以供第三网络域下的节点3连接的，则可以将第二IP地址作为节点2在第三网络域下的IP地址。
例如，假设节点3的远程地址列表中配置了节点2的IP地址(即第二IP地址)为117.11.10.2:50012，节点2的原始第二网络域地址列表为：{domain2:10.10.1.2:50012}。节点2判断节点2的原始网络域地址列表中未包括节点2在第三网络域下的IP地址，则节点2将第二IP 地址写入节点2的原始网络域地址列表，得到最终的节点2的网络域地址列表为：{domain2:10.10.1.2:50012，domain3:117.11.10.2:50012}。
本实施例中，对于接收方节点，通过动态回写获得其网络域地址列表。这样，对于用户漏配置，或者通信系统中新加入的网络域及节点，无需用户再进行配置，即可得到网络域地址列表，因而能够简化用户的配置过程，进一步提高用户体验。
在一个实施例中，节点3和节点2在交换了网络域地址列表后，节点3和节点2可以分别对对方的网络域地址列表进行检查。具体的，如图8所示，所述方法还可以包括：
S1081、节点3确定节点2的网络域地址列表中是否包括节点2在第三网络域下的IP地址；
若否，则执行步骤S1082；
若是，则执行步骤S1084。
S1082、节点3基于第二连接向节点2发送第一提示信息，第一提示信息用于提示节点2打印第一警告日志(warning log)。
S1083、节点2接收第一提示信息，并根据第一提示信息打印第一警告日志，第一警告日志用于提示用户节点2的网络域地址列表中未包括节点2在第三网络域下的IP地址。
通过生成第一警告日志使得用户能够获知节点2的网络域地址列表中未包括节点2在第三网络域下的IP地址，从而便于用户根据需要对该IP地址进行配置或者执行其他操作。该实现方式增加了节点与用户的交互，便于用户获知网络域地址列表的情况，从而便于用户对节点2的网络域地址列表进行完善，进而更好的实现后续的通信，进一步提高用户体验。
S1084、节点3确定节点2在第三网络域下的IP地址是否可通信；
若是，则结束流程；
若否，则执行步骤S1085。
S1085、节点3向节点2发送第二提示信息，第二提示信息用于提示节点2打印第二警告日志。
S1086、节点2接收第二提示信息，并根据第二提示信息打印第二警告日志，第二警告日志用于提示用户节点2在第三网络域下的IP地址不可通信。
通过生成第二警告日志使得用户能够获知节点2在第三网络域下的IP地址不可通信，可能存在配置错误或连接问题，从而便于用户根据需要对该IP地址进行修改或检查连接等操作。该实现方式增加了节点与用户的交互，保证了节点2的网络域地址列表的正确性，从而保证了联盟链通信的准确性和可靠性，进一步提高用户体验。
同时，节点2也可以对节点3发送的节点3的网络域列表进行检查，具体过程与节点3检查节点2的网络域地址列表的过程类似，包括：
节点2确定节点3的网络域地址列表中是否包括节点3在第二网络域下的IP地址。
若节点3的网络域地址列表中未包括节点3在第二网络域下的IP地址，则：节点2基于第二连接向节点3发送第三提示信息，第三提示信息用于提示节点3打印第三警告日志；节点2接收第三提示信息，并根据第三提示信息打印第三警告日志，第三警告日志用于提示用户节点3的网络域地址列表中未包括节点3在第二网络域下的IP地址。
若节点3的网络域地址列表中包括节点3在第二网络域下的IP地址，则节点2确定节点3在第二网络域下的IP地址是否可通信。
若节点2确定节点3在第二网络域下的IP地址可通信，则结束流程；若节点2确定节点3在第二网络域下的IP地址不可通信，则节点2向节点3发送第四提示信息，第四提示信息用于提示节点3打印第四警告日志；节点3接收第四提示信息，并根据第四提示信息打印第四警告日志，第四警告日志用于提示用户节点3在第二网络域下的IP地址不可通信。
节点2检查节点3的网络域地址列表的具体过程和有益效果等参见节点3检查节点2的网络 域地址列表，在此不再赘述。
在一个实施例中，当通信系统有新的机构(即某一网络域下的节点)加入，或者有机构从通信系统中离开，或者节点在某一个或某几个网络域下的IP地址配置错误，或者配置遗漏等情况发生时，通信系统中的相关节点可以基于用户的修改指令对网络域地址列表进行动态修改，并对网络中节点的连接状态进行更新，即对节点通信进行管理。具体的，请参见图9，以通信系统中的节点3接收到修改指令为例进行说明。如图9所示，该联盟链通信方法还可以包括：
S1091、节点3接收用户输入的列表修改指令；列表修改指令用于指示修改节点3的网络域地址列表。
可选的，列表修改指令中可以包括修改类型和修改信息等。修改类型可以为新增、更新或删除。修改信息可以包括待修改的网络域名称、IP地址等。
其中，修改类型为“新增”的列表修改指令的应用场景例如可以为：基于上述实施例中的第三警告日志，用户向节点3发送列表修改指令，该列表修改指令用于指示在节点3的网络域地址列表中增加节点3在第二网络域下的IP地址。或者，通信系统中新加入新的网络域C下的节点，该节点为节点3的邻居节点，则，用户向节点3发送列表修改指令，该列表修改指令用于指示在节点3的网络域地址列表中增加节点3在该新的网络域C下的IP地址。
修改类型为“更新”的列表修改指令的应用场景例如可以为：基于上述实施例中的第四警告日志，用户向节点3发送列表修改指令，该列表修改指令用于指示更新节点3的网络域地址列表中节点3在第二网络域下的IP地址为新的IP地址。
修改类型为“删除”的列表修改指令的应用场景例如可以为：某一网络域D下的各个节点均不再与节点3进行连接，则用户向节点3发送列表修改指令，该列表修改指令用于指示删除节点3的网络域地址列表中节点3在网络域D下的IP地址。
可选的，修改类型可以通过在修改信息后增加字符信息来表示，例如，“-I”表示新增，“-U”表示更新，“-D”表示删除。当然，修改类型也可以通过其他的方式表示，例如：{update：{domain2:117.11.10.1:50011}}表示更新第二网络域下的IP地址为117.11.10.1:50011。本申请实施例对于修改类型及列表修改指令的具体形式不做任何限定。
S1092、节点3基于列表修改指令，对节点3的网络域地址列表进行修改，并将修改指令广播至节点3的邻居节点。
如上述实施例所述，节点3和节点3的各个邻居节点通过交换网络域地址列表，从而使得每个节点均保存有本节点和本节点的各个邻居节点的网络域地址列表。节点3对本节点存储的节点3的网络域地址列表进行修改后，需要进一步将列表修改指令告知各个邻居节点，以使邻居节点同步更新节点3的网络域地址列表。
S1093、节点3的各个邻居节点基于列表修改指令修改各自存储的节点3的网络域地址列表。
示例性的，图10示出了动态修改网络域地址列表的过程示意图。节点3接收用户的列表修改指令，对节点3的网络域地址列表修改后，将修改指令进一步广播至节点3的邻居节点：节点2、节点4、……节点n。节点2、节点4、……节点n修改各自存储的节点3的网络域地址列表。
当然，在一些实施例中，节点3也可以将修改后的节点3的网络域地址列表广播至节点3的各个邻居节点，以实现对各个邻居节点中存储的节点3的网络域地址列表的更新。
本实施例中，仅将列表修改指令广播至节点3的各个邻居节点，这样能够减少冗余消息的广播，减少网络堵塞等情况，从而提高网络通信的效率，保证网络通信的高效性。
S1094、若列表修改指令用于指示删除节点3的网络域地址列表中节点3在第一目标域下的IP地址，则节点3的邻居节点中位于第一目标域下的节点断开与节点3的连接。
也就是说，若列表修改指令中的修改类型为“删除”，修改信息为节点3在第一目标域下的 IP地址，则该第一目标域下的各个节点接收到节点3广播的指令后，均断开与节点3的连接。
例如，列表修改指令用于指示删除节点3的网络域地址列表中的“domain2:117.10.11.1:50012”，也即删除节点3在第二网络域下的IP地址117.10.11.1:50012。则第二网络域下的节点(包括节点2)接收到节点3广播的该列表修改指令，从各自保存的节点3的网络域地址列表中删除该信息，且二者均断开与节点3的连接。
S1095、若列表修改指令用于指示更新节点3的网络域地址列表中节点3在第二目标域下的IP地址为目标IP地址，则节点3的邻居节点中位于第二目标域下的节点断开与节点3的连接，并根据目标IP地址与节点3重新建立连接。
也就是说，若列表修改指令中的修改类型为“更新”，修改信息为将节点3在第二目标域下的IP地址修改为目标IP地址，则该第二目标域下的各个节点接收到节点3广播的该列表修改指令后，分别断开与节点3的连接，并使用目标IP地址与节点3重新建立连接。
例如，节点3的网络域地址列表中原本为：{domain2:117.10.11.1:50012，domain3:10.10.1.1:50011}，列表修改指令为{update：{domain2:117.11.10.1:50011}}，用于指示更新节点3的网络域地址列表中的节点3在第二网络域下的IP地址为117.11.10.1:50011。则，第二网络域下的节点2和节点5接收到节点3广播的该列表修改指令，更新各自保存的节点3的网络域地址列表中的该信息，且二者均断开与节点3的连接，并使用IP地址117.11.10.1:50011分别与节点3重新建立连接。
本实施例中，在接收用户输入的列表修改指令的情况下，节点3基于该列表修改指令对其节点3的网络域地址列表进行了修改。同时，节点3将该列表修改指令广播至节点3的各个邻居节点，以使节点3的各个邻居节点更新各自保存的节点3的网络域地址列表，从而使得通信系统中各个节点中存储的节点3的网络域地址列表均得到了更新，保证了各个节点中该网络域地址列表的一致性，从而保证了通信的准确性和可靠性，进一步使得节点发现时获取的各个网络域地址列表的准确性，提高节点发现的准确性。另一方面，本实施例提供的方法能够在通信系统运行时动态的配置IP地址、修改网络域地址列表以及管理节点通信，而无需将节点宕机重启，从而能够简化网络通信的过程，保证网络的稳定性，节约用户时间，进一步提高用户体验。另外，上述动态修改网络域地址列表的过程用户是无感知的，也就是说，上述过程对于用户而言是透明的，这进一步提高了用户体验。而且，节点3的各个邻居节点根据列表更新指令对与节点3的连接状态进行更新，从而保证了节点连接的准确性，保证了网络通信的可靠性，进一步提高用户体验。
需要说明的是，上述实施例中多以联盟链通信方法应用于通过代理方式映射节点内外网址进行内外网通信的场景为例进行说明，然而，除此之外，本实施例提供的方法也可以应用于任何可能导致一个节点存在多个IP地址供多个网络域的节点通信的情况，本申请对此不做限定。
应该理解的是，虽然上述实施例的流程图中的各个步骤按照箭头的指示依次显示，但是这些步骤并不是必然按照箭头指示的顺序依次执行。除非本文中有明确的说明，这些步骤的执行并没有严格的顺序限制，这些步骤可以以其它的顺序执行。而且，流程图中的至少一部分步骤可以包括多个子步骤或者多个阶段，这些子步骤或者阶段并不必然是在同一时刻执行完成，而是可以在不同的时刻执行，这些子步骤或者阶段的执行顺序也不必然是依次进行，而是可以与其它步骤或者其它步骤的子步骤或者阶段的至少一部分轮流或者交替地执行。
图11示出了本申请实施例提供的联盟链通信装置的结构框图，该联盟链通信装置可以为第二节点(即节点2)。如图11所示，本实施例提供的联盟链通信装置，可以包括：
第一接收模块1101，用于通过与第一节点之间的第一连接接收来自第一节点的第一信息；第一连接包括逻辑连接，第一连接的连接发起方为第一节点；第一信息中包括第一节点在目标网络域下的地址，目标网络域为至少一个其他节点所在的网络域，至少一个其他节点是指第一节点待 加入的网络分区中除第二节点外的节点；第一节点在目标网络域下的地址用于第一节点与至少一个其他节点建立连接；
第一发送模块1102，用于向至少一个其他节点发送第一信息。
在一个实施例中，第一节点属于第一网络域，第一接收模块1101还用于接收来自第一节点的第一请求消息；第一请求消息用于请求提供至少一个其他节点在第一网络域下的地址；至少一个其他节点在第一网络域下的地址用于第一节点与至少一个其他节点建立连接；第一发送模块1102还用于响应于第一请求消息，通过第一连接，向第一节点发送第一响应消息，第一响应消息中包括至少一个其他节点在第一网络域下的地址。
在一个实施例中，第一发送模块1102还用于获取至少一个第二信息；第二信息包括第二节点的邻居节点中位于待加入的网络分区的节点在一个或多个网络域下的地址；从各个第二信息中查找目标地址；目标地址是指节点在第一网络域下的地址，目标地址中包括至少一个其他节点在第一网络域下的地址。
在一个实施例中，第一发送模块1102具体用于在确定预设存储位置未存储有目标地址的情况下，从各个第二信息中查找目标地址。
在一个实施例中，第一发送模块1102还用于将目标地址保存至预设存储位置；预设时长之后，清除预设存储位置的目标地址。
本实施例提供的联盟链通信装置，用于执行本申请方法实施例提供的联盟链通信方法中节点2的步骤，技术原理和技术效果相似，具体可参见方法实施例部分，此处不再赘述。
图12示出了本申请实施例提供的联盟链通信装置的结构框图，该联盟链通信装置可以为第一节点(即节点1)。如图12所示，本实施例提供的联盟链通信装置，可以包括：
获取模块1201，用于获取第一信息；第一信息中包括第一节点在目标网络域下的地址；目标网络域为至少一个其他节点所在的网络域，至少一个其他节点是指第一节点待加入的网络分区中除第二节点外的节点；第一节点在目标网络域下的地址用于第一节点与至少一个其他节点建立连接；
第二发送模块1202，用于通过与第二节点之间的第一连接，向第二节点发送第一信息；第一连接包括逻辑连接，第一连接的连接发起方为第一节点。
在一个实施例中，第一节点属于第一网络域，第二获取模块1201还用于获取至少一个其他节点在第一网络域下的地址；该装置还包括连接模块1203，用于根据至少一个其他节点在第一网络域下的地址，与至少一个其他节点建立连接。
在一个实施例中，获取模块1201具体用于向目标节点发送第一请求消息，第一请求消息用于请求目标节点提供至少一个其他节点在第一网络域下的地址；目标节点包括第二节点和/或第一节点的邻居节点中的至少一个目标邻居节点；接收来自目标节点的第一响应消息；第一响应消息中包括至少一个其他节点在第一网络域下的地址。
在一个实施例中，连接模块1203具体用于在至少一个其他节点在第一网络域下的地址可通信的情况下，根据至少一个其他节点在第一网络域下的地址，与至少一个其他节点建立连接。
在一个实施例中，获取模块1201还用于确定第一节点的远程地址列表，第一节点的远程地址列表中包括至少一个其他节点在第一网络域下的地址。
在一个实施例中，第一节点的远程地址列表中还包括用于指示每个其他节点在第一网络域下的地址是否可通信的指示信息。
在一个实施例中，第一节点属于第一网络域，第一节点的远程地址列表中包括第二节点的地址，连接模块1203还用于根据第二节点的地址，与第二节点建立第一连接。
本实施例提供的联盟链通信装置，用于执行本申请方法实施例提供的联盟链通信方法中节点 1的步骤，技术原理和技术效果相似，具体可参见方法实施例部分，此处不再赘述。
本申请实施例还提供了一种联盟链通信系统，该系统包括第一联盟链通信装置和第二联盟链通信装置，第一联盟链通信装置可以为第一节点，第二联盟链通信装置可以为第二节点。第一联盟链通信装置用于执行本申请方法实施例提供的通信方法中节点1的步骤，第二联盟链通信装置用于执行本申请方法实施例提供的通信方法中节点2的步骤，技术原理和技术效果相似，具体可参见方法实施例部分，此处不再赘述。
所属领域的技术人员可以清楚地了解到，为了描述的方便和简洁，仅以上述各功能单元、模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能单元、模块完成，即将所述装置的内部结构划分成不同的功能单元或模块，以完成以上描述的全部或者部分功能。实施例中的各功能单元、模块可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中，上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。另外，各功能单元、模块的具体名称也只是为了便于相互区分，并不用于限制本申请的保护范围。上述系统中单元、模块的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
参见图13，本申请实施例还提供了一种电子设备，该电子设备可以为上述申请实施例中的第一节点中的第一联盟链通信装置，也可以为上述申请实施例中的第二节点中的第二联盟链通信装置。该电子设备包括：处理器1301、接收器1302、发射器1303、存储器1304和总线1305。处理器1301包括一个或者多个处理核心，处理器1301通过运行软件程序以及模块，从而执行各种功能的应用以及信息处理。接收器1302和发射器1303可以实现为一个通信组件，该通信组件可以是一块基带芯片。存储器1304通过总线1305和处理器1301相连。存储器1304可用于存储至少一个程序指令，处理器1301用于执行至少一个程序指令，以实现上述实施例的技术方案。其实现原理和技术效果与上述方法相关实施例类似，此处不再赘述。
当电子设备开机后，处理器可以读取存储器中的软件程序，解释并执行软件程序的指令，处理软件程序的数据。当需要通过天线发送数据时，处理器对待发送的数据进行基带处理后，输出基带信号至控制电路中的控制电路，控制电路将基带信号进行射频处理后将射频信号通过天线以电磁波的形式向外发送。当有数据发送到电子设备时，控制电路通过天线接收到射频信号，将射频信号转换为基带信号，并将基带信号输出至处理器，处理器将基带信号转换为数据并对该数据进行处理。
本领域技术人员可以理解，为了便于说明，图13仅示出了一个存储器和处理器。在实际的电子设备中，可以存在多个处理器和存储器。存储器也可以称为存储介质或者存储设备等，本申请实施例对此不做限制。
作为一种可选的实现方式，处理器可以包括基带处理器和中央处理器，基带处理器主要用于对通信数据进行处理，中央处理器主要用于执行软件程序，处理软件程序的数据。本领域技术人员可以理解，基带处理器和中央处理器可以集成在一个处理器中，也可以是各自独立的处理器，通过总线等技术互联。本领域技术人员可以理解，电子设备可以包括多个基带处理器以适应不同的网络制式，电子设备可以包括多个中央处理器以增强其处理能力，电子设备的各个部件可以通过各种总线连接。该基带处理器也可以表述为基带处理电路或者基带处理芯片。该中央处理器也可以表述为中央处理电路或者中央处理芯片。对通信协议以及通信数据进行处理的功能可以内置在处理器中，也可以以软件程序的形式存储在存储器中，由处理器执行软件程序以实现基带处理功能。该存储器可以集成在处理器中，也可以独立在处理器之外。该存储器包括高速缓存Cache，可以存放频繁访问的数据/指令。
在本申请实施例中，处理器可以是通用处理器、数字信号处理器、专用集成电路、现场可编 程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件，可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。
在本申请实施例中，存储器可以是非易失性存储器，比如硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SS)等，还可以是易失性存储器(volatile memory)，例如随机存取存储器(random-access memory，RAM)。存储器是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，不限于此。
本申请实施例中的存储器还可以是电路或者其它任意能够实现存储功能的装置，用于存储程序指令和/或数据。本申请各实施例提供的方法中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、网络设备、用户设备或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL)或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机可以存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，数字视频光盘(digital video disc，DWD)、或者半导体介质(例如，SSD)等。
本申请实施例还提供了一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，所述计算机程序被处理器执行时可实现上述任意方法实施例中的步骤。
以上所述实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的精神和范围，均应包含在本申请的保护范围之内。

Claims (20)

  1. 一种通信方法，其特征在于，所述方法包括：
    通过与第一节点之间的第一连接接收来自所述第一节点的第一信息；所述第一连接包括逻辑连接，所述第一连接的连接发起方为所述第一节点；所述第一信息中包括所述第一节点在目标网络域下的地址，所述目标网络域为至少一个其他节点所在的网络域，至少一个所述其他节点是指所述第一节点待加入的网络分区中除第二节点外的节点；所述第一节点在所述目标网络域下的地址用于所述第一节点与至少一个所述其他节点建立连接；
    向至少一个所述其他节点发送所述第一信息。
  2. 根据权利要求1所述的方法，其特征在于，所述第一节点属于第一网络域，所述方法还包括：
    接收来自所述第一节点的第一请求消息；所述第一请求消息用于请求提供至少一个所述其他节点在所述第一网络域下的地址；至少一个所述其他节点在所述第一网络域下的地址用于所述第一节点与至少一个所述其他节点建立连接；
    响应于所述第一请求消息，通过所述第一连接，向所述第一节点发送第一响应消息，所述第一响应消息中包括至少一个所述其他节点在所述第一网络域下的地址。
  3. 根据权利要求2所述的方法，其特征在于，所述通过所述第一连接，向所述第一节点发送第一响应消息之前，所述方法还包括：
    获取至少一个第二信息；所述第二信息包括所述第二节点的邻居节点中位于所述待加入的网络分区的节点在一个或多个网络域下的地址；
    从各个所述第二信息中查找目标地址；所述目标地址是指节点在所述第一网络域下的地址，所述目标地址中包括至少一个所述其他节点在所述第一网络域下的地址。
  4. 根据权利要求3所述的方法，其特征在于，所述从各个所述第二信息中查找目标地址，包括：
    在确定预设存储位置未存储有所述目标地址的情况下，从各个所述第二信息中查找所述目标地址。
  5. 根据权利要求4所述的方法，其特征在于，所述在确定预设存储位置未存储有所述目标地址的情况下，从各个所述第二信息中查找所述目标地址之后，所述方法还包括：
    将所述目标地址保存至所述预设存储位置；
    预设时长之后，清除所述预设存储位置的所述目标地址。
  6. 根据权利要求1至5中任一项所述的方法，其特征在于，所述向至少一个所述其他节点发送所述第一信息，包括：
    采用Gossip协议向至少一个所述其他节点广播所述第一信息。
  7. 一种通信方法，其特征在于，所述方法包括：
    获取第一信息；所述第一信息中包括第一节点在目标网络域下的地址；所述目标网络域为至少一个其他节点所在的网络域，至少一个所述其他节点是指所述第一节点待加入的网络分区中除第二节点外的节点；所述第一节点在所述目标网络域下的地址用于所述第一节点与至少一个所述其他节点建立连接；
    通过与所述第二节点之间的第一连接，向所述第二节点发送所述第一信息；所述第一连接包括逻辑连接，所述第一连接的连接发起方为所述第一节点。
  8. 根据权利要求7所述的方法，其特征在于，所述第一节点属于第一网络域，所述方法还包括：
    获取至少一个所述其他节点在所述第一网络域下的地址；
    根据至少一个所述其他节点在所述第一网络域下的地址，与至少一个所述其他节点建立连接。
  9. 根据权利要求8所述的方法，其特征在于，所述获取至少一个所述其他节点在所述第一网络域下的地址，包括：
    向目标节点发送第一请求消息，所述第一请求消息用于请求所述目标节点提供至少一个所述其他节点在所述第一网络域下的地址；所述目标节点包括所述第二节点和/或所述第一节点的邻居节点中的至少一个目标邻居节点；
    接收来自所述目标节点的第一响应消息；所述第一响应消息中包括至少一个所述其他节点在所述第一网络域下的地址。
  10. 根据权利要求8所述的方法，其特征在于，所述根据至少一个所述其他节点在所述第一网络域下的地址，与至少一个所述其他节点建立连接，包括：
    在至少一个所述其他节点在所述第一网络域下的地址可通信的情况下，根据至少一个所述其他节点在所述第一网络域下的地址，与至少一个所述其他节点建立连接。
  11. 根据权利要求8所述的方法，其特征在于，所述获取至少一个所述其他节点在所述第一网络域下的地址之后，所述方法还包括：
    确定所述第一节点的远程地址列表，所述第一节点的远程地址列表中包括至少一个所述其他节点在所述第一网络域下的地址。
  12. 根据权利要求9所述的方法，其特征在于，所述第一节点的远程地址列表中还包括用于指示每个所述其他节点在所述第一网络域下的地址是否可通信的指示信息。
  13. 根据权利要求7至12中任一项所述的方法，其特征在于，所述第一节点属于第一网络域，所述第一节点的远程地址列表中包括所述第二节点的地址，所述通过与所述第二节点之间的第一连接，向所述第二节点发送所述第一信息之前，所述方法还包括：
    根据所述第二节点的地址，与所述第二节点建立所述第一连接。
  14. 根据权利要求7至12中任一项所述的方法，其特征在于，所述第一节点属于第一网络域，所述第二节点位于第二网络域；所述第一信息中包括所述第一节点在所述第一网络域下的地址；所述方法还包括：
    通过所述第一连接接收来自所述第二节点的第三信息；所述第三信息中至少包括所述第二节点在所述第二网络域下的地址。
  15. 根据权利要求7至12中任一项所述的方法，其特征在于，所述方法还包括：
    接收信息修改指令；
    根据所述信息修改指令，对所述第一信息进行修改，并将所述信息修改指令发送至所述第一节点的邻居节点。
  16. 一种联盟链通信装置，其特征在于，包括：
    第一接收模块，用于通过与第一节点之间的第一连接接收来自所述第一节点的第一信息；所述第一连接包括逻辑连接，所述第一连接的连接发起方为所述第一节点；所述第一信息中包括所述第一节点在目标网络域下的地址，所述目标网络域为至少一个其他节点所在的网络域，至少一个所述其他节点是指所述第一节点待加入的网络分区中除第二节点外的节点；所述第一节点在所述目标网络域下的地址用于所述第一节点与至少一个所述其他节点建立连接；
    第一发送模块，用于向至少一个所述其他节点发送所述第一信息。
  17. 一种联盟链通信装置，其特征在于，包括：
    获取模块，用于获取第一信息；所述第一信息中包括第一节点在目标网络域下的地址；所述目标网络域为至少一个其他节点所在的网络域，至少一个所述其他节点是指所述第一节点待加入 的网络分区中除第二节点外的节点；所述第一节点在所述目标网络域下的地址用于所述第一节点与至少一个所述其他节点建立连接；
    第二发送模块，用于通过与所述第二节点之间的第一连接，向所述第二节点发送所述第一信息；所述第一连接包括逻辑连接，所述第一连接的连接发起方为所述第一节点。
  18. 一种通信系统，其特征在于，包括：第一节点和第二节点，所述第二节点用于执行如权利要求1至6中任一项所述的方法，所述第一节点用于执行如权利要求7至15中任一项所述的方法。
  19. 一种电子设备，其特征在于，包括：存储器、处理器以及存储在所述存储器中并可在所述处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现如权利要求1至6任一项所述的方法，或者实现如权利要求7至15任一项所述的方法。
  20. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求1至6任一项所述的方法，或者实现如权利要求7至15任一项所述的方法。
PCT/CN2022/111762 2021-12-24 2022-08-11 通信方法、系统、电子设备及可读存储介质 WO2023115982A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP22789151.2A EP4228209A4 (en) 2021-12-24 2022-08-11 COMMUNICATION METHOD AND SYSTEM, ELECTRONIC DEVICE AND READABLE STORAGE MEDIUM

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111599322.9 2021-12-24
CN202111599322.9A CN113992434B (zh) 2021-12-24 2021-12-24 通信方法、系统、电子设备及可读存储介质

Publications (1)

Publication Number Publication Date
WO2023115982A1 true WO2023115982A1 (zh) 2023-06-29

Family

ID=79734305

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/111762 WO2023115982A1 (zh) 2021-12-24 2022-08-11 通信方法、系统、电子设备及可读存储介质

Country Status (3)

Country Link
EP (1) EP4228209A4 (zh)
CN (1) CN113992434B (zh)
WO (1) WO2023115982A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113992434B (zh) * 2021-12-24 2022-04-01 杭州趣链科技有限公司 通信方法、系统、电子设备及可读存储介质
CN115499409A (zh) * 2022-09-29 2022-12-20 阿里巴巴（中国）有限公司 Nat网关、服务器和网络系统

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1788480A (zh) * 2003-05-12 2006-06-14 西门子公司 在具有不同地址范围的网络中的网络单元之间进行数据交换的方法
US20180152277A1 (en) * 2016-11-30 2018-05-31 International Business Machines Corporation Multi-domain connection establishment in computer networking communications
CN110266763A (zh) * 2019-05-20 2019-09-20 深圳壹账通智能科技有限公司 跨网段互连的区块链网络实现方法、系统及存储介质
CN110891082A (zh) * 2019-10-24 2020-03-17 南京可信区块链与算法经济研究院有限公司 一种联盟链中p2p端口地址的连接方法、系统及存储介质
CN111598564A (zh) * 2019-02-20 2020-08-28 华为技术有限公司 区块链节点连接建立方法、装置及设备
CN113992434A (zh) * 2021-12-24 2022-01-28 杭州趣链科技有限公司 通信方法、系统、电子设备及可读存储介质

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8189577B2 (en) * 2007-06-15 2012-05-29 Silver Spring Networks, Inc. Network utilities in wireless mesh communications networks
US20200119926A1 (en) * 2017-07-07 2020-04-16 Pablo Javier BUKI Methods and systems for processing high volume, fast settlement blockchain transactions
US11468046B2 (en) * 2018-01-17 2022-10-11 Geeq Corporation Blockchain methods, nodes, systems and products
US10813032B2 (en) * 2018-11-14 2020-10-20 Landis+Gyr Innovations, Inc. Systems and methods for neighboring node discovery in a network
CN110445850A (zh) * 2019-07-24 2019-11-12 深圳壹账通智能科技有限公司 区块链节点访问方法及装置、存储介质、电子设备
CN110708383B (zh) * 2019-10-12 2022-06-07 深圳市迅雷网络技术有限公司 区块链节点的网络连接方法及相关设备
CN111224829B (zh) * 2020-01-17 2022-11-08 深圳市迅雷网络技术有限公司 外部节点接入区块链网络的方法及装置，区块链网络
CN112822242B (zh) * 2020-12-30 2023-03-24 杭州趣链科技有限公司 一种点对点网络及其节点通信方法和装置
CN112910660B (zh) * 2021-03-25 2023-02-24 中国工商银行股份有限公司 区块链系统的证书颁发方法、添加方法及交易处理方法

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1788480A (zh) * 2003-05-12 2006-06-14 西门子公司 在具有不同地址范围的网络中的网络单元之间进行数据交换的方法
US20180152277A1 (en) * 2016-11-30 2018-05-31 International Business Machines Corporation Multi-domain connection establishment in computer networking communications
CN111598564A (zh) * 2019-02-20 2020-08-28 华为技术有限公司 区块链节点连接建立方法、装置及设备
CN110266763A (zh) * 2019-05-20 2019-09-20 深圳壹账通智能科技有限公司 跨网段互连的区块链网络实现方法、系统及存储介质
CN110891082A (zh) * 2019-10-24 2020-03-17 南京可信区块链与算法经济研究院有限公司 一种联盟链中p2p端口地址的连接方法、系统及存储介质
CN113992434A (zh) * 2021-12-24 2022-01-28 杭州趣链科技有限公司 通信方法、系统、电子设备及可读存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4228209A4

Also Published As

Publication number Publication date
EP4228209A4 (en) 2024-04-24
EP4228209A1 (en) 2023-08-16
CN113992434B (zh) 2022-04-01
CN113992434A (zh) 2022-01-28

Similar Documents

Publication Publication Date Title
WO2023115982A1 (zh) 通信方法、系统、电子设备及可读存储介质
EP3651485B1 (en) Bluetooth cluster online upgrade method and apparatus
EP3070890A1 (en) Multicast flow overlay using registration over a reliable transport
KR100513282B1 (ko) 에드 혹 네트워크에서의 패스 엠티유를 이용하여 데이터를 송신하는 데이터 송신 노드 및 송신 방법
US20150312089A1 (en) Method of managing zigbee network in the internet of things
WO2021031648A1 (zh) Evpn和vpls共存双活的方法、设备及系统
WO2023005128A1 (zh) 节点加入方法、对讲机、系统及存储介质
CN110838935B (zh) 高可用sdn控制器集群方法、系统、存储介质及设备
TWI599201B (zh) 網路系統及建立資料連線的方法
WO2023272981A1 (zh) 窄带通信方法、对讲机、设备、存储介质及自组网系统
US20150229523A1 (en) Virtual extensible local area network (vxlan) system of automatically configuring multicasting tunnel for segment of virtual extensible local area network according to life cycle of end system and operating method thereof
US20160134510A1 (en) Topology structure discovery method and device
JP7483924B2 (ja) 接続ステータス検出方法、関連デバイス、コンピュータ記憶媒体、およびコンピュータプログラム
CN111711941A (zh) 数据传输方法以及相关设备、装置
JP7479427B2 (ja) トランスポートプロトコル上でのポイント・ツー・ポイント・データベース同期
WO2022062568A1 (zh) 一种交换机的配置方法及相关设备
US11343153B2 (en) BGP logical topology generation method, and device
WO2021104284A1 (zh) 关于数据传输的表项建立方法及相关设备
WO2020192727A1 (zh) 一种确定服务区域的方法、装置及系统
Dash et al. Flooding control in named data networking
CN114301866B (zh) 联盟链通信方法、系统、电子设备及可读存储介质
WO2018058385A1 (zh) 一种网络互通方法、网元及系统
US7433330B2 (en) Method and apparatus for sending IP multicast packets in a wireless communication system
CN115955431B (zh) 一种数据传输方法、装置及存储介质
CN113852572B (zh) 一种报文处理方法及装置

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 17921502

Country of ref document: US

ENP Entry into the national phase

Ref document number: 2022789151

Country of ref document: EP

Effective date: 20221024