CN108810186B - Block chain node communication method and device and block chain node - Google Patents
Block chain node communication method and device and block chain node Download PDFInfo
- Publication number
- CN108810186B CN108810186B CN201810555793.1A CN201810555793A CN108810186B CN 108810186 B CN108810186 B CN 108810186B CN 201810555793 A CN201810555793 A CN 201810555793A CN 108810186 B CN108810186 B CN 108810186B
- Authority
- CN
- China
- Prior art keywords
- target node
- node
- address
- nat
- source
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000004891 communication Methods 0.000 title claims abstract description 48
- 238000000034 method Methods 0.000 title claims abstract description 43
- 238000013519 translation Methods 0.000 claims abstract description 14
- 238000004590 computer program Methods 0.000 claims description 11
- 230000004044 response Effects 0.000 claims description 11
- 230000003993 interaction Effects 0.000 claims description 4
- 238000011161 development Methods 0.000 abstract description 7
- 238000010586 diagram Methods 0.000 description 6
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000001737 promoting effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- 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
-
- 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/2557—Translation policies or rules
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
本发明实施例提供一种区块链节点通信方法、装置及区块链节点。该方法包括：主存储节点接收目标节点发送的请求信息；比较该请求信息的源IP地址和该目标节点在加入区块链网络时广播的IP地址是否相同；若该请求信息的源IP地址和该目标节点在加入区块链网络时广播的IP地址不同，则该主存储节点确定该目标节点位于网络地址转换NAT下，并确定该目标节点对应的NAT的公网IP地址，以及该目标节点在该NAT上映射的端口号；通过向该目标节点发送连接请求，确定该目标节点对应的NAT的类型信息；将该NAT的类型信息发送给该目标节点。本发明实施例使得没有公网IP地址的节点也可以成为从存储节点，促进了区块链业务的发展。
Embodiments of the present invention provide a block chain node communication method, device, and block chain node. The method includes: the main storage node receives the request information sent by the target node; compares whether the source IP address of the request information and the IP address broadcast by the target node when joining the blockchain network are the same; if the source IP address of the request information and The IP address broadcasted by the target node when it joins the blockchain network is different, then the main storage node determines that the target node is under the network address translation NAT, and determines the public IP address of the NAT corresponding to the target node, and the target node. The port number mapped on the NAT; the type information of the NAT corresponding to the target node is determined by sending a connection request to the target node; the type information of the NAT is sent to the target node. In the embodiment of the present invention, a node without a public network IP address can also become a slave storage node, which promotes the development of blockchain services.
Description
Technical Field
The embodiment of the invention relates to the technical field of communication, in particular to a block link point communication method and device and a block link node.
Background
In a blockchain network, a master storage node may store a complete blockchain ledger, a slave storage node may store a partial blockchain ledger, and the slave storage node may receive inquiry access of other nodes by providing inquiry services to the other nodes to obtain corresponding rewards.
In the prior art, in order to promote the block chain service, more nodes are required to become slave storage nodes, but the nodes are required to have public network IP addresses to become the slave storage nodes, but at present, many nodes do not have public network IP addresses, so that many nodes cannot become slave storage nodes, and the development of the block chain service is limited.
Disclosure of Invention
Embodiments of the present invention provide a method and an apparatus for block link point communication, and a block link node, so that a node without a public network IP address may also become a slave storage node, thereby promoting the development of a block link service.
In a first aspect, an embodiment of the present invention provides a block-node point communication method, including:
a master storage node receives request information sent by a target node, wherein the request information indicates that the target node requests to become a slave storage node, and the request information comprises identification information of the target node;
the main storage node compares whether the source IP address of the request information is the same as the IP address broadcast by the target node when the target node joins the block chain network;
if the source IP address of the request information is different from the IP address broadcast by the target node when the target node joins the block chain network, the main storage node determines that the target node is positioned under a Network Address Translation (NAT), and determines the public network IP address of the NAT corresponding to the target node and the port number mapped on the NAT by the target node;
the main storage node determines the type information of the NAT corresponding to the target node by sending a connection request to the target node;
and the main storage node sends the NAT type information to the target node.
In a second aspect, an embodiment of the present invention provides a block link point communication device, including:
a receiving module, configured to receive request information sent by a target node, where the request information indicates that the target node requests to become a slave storage node, and the request information includes identification information of the target node;
the comparison module is used for comparing whether the source IP address of the request information is the same as the IP address broadcasted by the target node when the target node joins the block chain network;
a first determining module, configured to determine that the target node is located under a network address translation NAT when a source IP address of the request information is different from an IP address broadcasted by the target node when the target node joins a block chain network, and determine a public network IP address of the NAT corresponding to the target node and a port number mapped by the target node on the NAT;
a second determining module, configured to determine, by sending a connection request to the target node, type information of an NAT corresponding to the target node;
and the sending module is used for sending the NAT type information to the target node.
In a third aspect, an embodiment of the present invention provides a block link point, including:
a memory;
a processor; and
a computer program;
wherein the computer program is stored in the memory and configured to be executed by the processor to implement the method of the first aspect.
In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium, on which a computer program is stored, the computer program being executed by a processor to implement the method of the first aspect.
According to the block chain node communication method, device and block chain node provided by the embodiment of the invention, request information sent by a target node is received through a main storage node, whether a source IP address of the request information is the same as an IP address broadcast by the target node when the target node joins a block chain network is compared, if the source IP address of the request information is different from the IP address broadcast by the target node when the target node joins the block chain network, the main storage node determines that the target node is positioned under a network address translation NAT, determines a public network IP address of the NAT corresponding to the target node and a port number mapped by the target node on the NAT, so that the target node can become a slave storage node, a node without the public network IP address can also become a slave storage node, and the development of block chain service is promoted.
Drawings
Fig. 1 is a schematic diagram of an application scenario provided in an embodiment of the present invention;
fig. 2 is a flowchart of a block link point communication method according to an embodiment of the present invention;
fig. 3 is a schematic diagram of a block chain network according to an embodiment of the present invention;
fig. 4 is a flowchart of a block-node communication method according to another embodiment of the present invention;
fig. 5 is a flowchart of a block-node communication method according to another embodiment of the present invention;
fig. 6 is a schematic structural diagram of a block link point communication device according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of a blockchain node according to an embodiment of the present invention.
With the foregoing drawings in mind, certain embodiments of the disclosure have been shown and described in more detail below. These drawings and written description are not intended to limit the scope of the disclosed concepts in any way, but rather to illustrate the concepts of the disclosure to those skilled in the art by reference to specific embodiments.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.
The block link point communication method provided by the invention can be applied to the communication system shown in fig. 1. As shown in fig. 1, the communication system includes: access network device 11, terminal device 12, and server 13. It should be noted that the communication System shown in fig. 1 may be applicable to different network formats, for example, may be applicable to Global System for Mobile communication (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time Division-Synchronous Code Division Multiple Access (TD-SCDMA), Long Term Evolution (Long Term Evolution, LTE), and future 5G network formats. Optionally, the communication system may be a system in a scenario of high-reliability and Low-Latency Communications (URLLC) transmission in a 5G communication system.
Therefore, optionally, the access Network device 11 may be a Base Station (BTS) and/or a Base Station Controller in GSM or CDMA, a Base Station (NodeB, NB) and/or a Radio Network Controller (RNC) in WCDMA, an evolved Node B (eNB or eNodeB) in LTE, or a relay Station or an access point, or a Base Station (gbb) in a future 5G Network, and the present invention is not limited thereto.
The terminal device 12 may be a wireless terminal or a wired terminal. A wireless terminal may refer to a device that provides voice and/or other traffic data connectivity to a user, a handheld device having wireless connection capability, or other processing device connected to a wireless modem. A wireless terminal, which may be a mobile terminal such as a mobile telephone (or "cellular" telephone) and a computer having a mobile terminal, for example, a portable, pocket, hand-held, computer-included, or vehicle-mounted mobile device, may communicate with one or more core Network devices via a Radio Access Network (RAN), and may exchange language and/or data with the RAN. For another example, the Wireless terminal may also be a Personal Communication Service (PCS) phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), and other devices. A wireless Terminal may also be referred to as a system, a Subscriber Unit (Subscriber Unit), a Subscriber Station (Subscriber Station), a Mobile Station (Mobile), a Remote Station (Remote Station), a Remote Terminal (Remote Terminal), an Access Terminal (Access Terminal), a User Terminal (User Terminal), a User Agent (User Agent), and a User Device or User Equipment (User Equipment), which are not limited herein. Optionally, the terminal device 12 may also be a smart watch, a tablet computer, or the like. In this embodiment, the terminal device 12 and the server 13 may be nodes in a blockchain network.
The invention provides a block link point communication method, which aims to solve the technical problems in the prior art.
The following describes the technical solutions of the present invention and how to solve the above technical problems with specific embodiments. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments. Embodiments of the present invention will be described below with reference to the accompanying drawings.
Fig. 2 is a flowchart of a block link point communication method according to an embodiment of the present invention. The embodiment of the invention provides a block chain node communication method aiming at the technical problems in the prior art, and the method comprises the following specific steps:
As shown in fig. 3, 31 denotes a master storage node in the blockchain network, 32 denotes a target node in the blockchain network, the target node 32 requests to become a slave storage node, and the target node 32 has its own public network IP address. Another target node is indicated at 33, the target node 33 requests to become a slave storage node, the target node 33 has no public Network IP Address, the target node 33 communicates with the blockchain Network via Network Address Translation (NAT), NAT is indicated at 34, and a querying node in the blockchain Network is indicated at 35. In this embodiment, the query node 35 is provided with a query service by a slave storage node. The method is only illustrative and does not limit the specific network architecture of the blockchain network. In addition, the query node 35 may be a node under the NAT or may not be a node under the NAT.
When the target node 32 or the target node 33 first joins the block chain network, it is necessary to obtain the created blocks from the nodes adjacent to the target node 32 or the target node 33, and optionally, all the nodes in the block chain network store the created blocks. In order to ensure that the target node 32 or the target node 33 acquires a real created block, the target node 32 or the target node 33 may send created block query requests to a plurality of neighboring nodes, for example, the target node 32 or the target node 33 sends created block query requests to the neighboring node B and the neighboring node C, after receiving the created block query requests, the neighboring node B and the neighboring node C send respective locally stored created blocks to the target node 32 or the target node 33, the target node 32 or the target node 33 compares whether the created blocks fed back by the neighboring node B and the neighboring node C are consistent, and if the created blocks fed back by the neighboring node B and the neighboring node C are consistent, the target node 32 or the target node 33 locally stores the created blocks; if the created blocks fed back by the adjacent node B and the adjacent node C are not consistent, the target node 32 or the target node 33 may further continue to send created block query requests to the adjacent node D and the adjacent node E, and receive created blocks fed back by the adjacent node D and the adjacent node E, respectively, and if the created blocks fed back by adjacent nodes exceeding a preset proportion among the adjacent node B, the adjacent node C, the adjacent node D, and the adjacent node E are consistent, the target node 32 or the target node 33 determines that the created blocks are real. Optionally, if the created blocks fed back by more than fifty percent of the neighboring nodes, such as the neighboring node C, the neighboring node D, and the neighboring node E, are consistent, the target node 32 or the target node 33 determines that the created block fed back by the neighboring node C is real, and the created block fed back by the neighboring node B is false.
When the target node 32 or the target node 33 acquires the real created block, the created block is stored locally, and the IP address of the main storage node is acquired from the created block, and optionally, the created block stores IP addresses of one or more main storage nodes, and the target node 32 or the target node 33 may send request information to the one or more main storage nodes according to the IP addresses of the one or more main storage nodes, for example, the created block stores the IP address of the main storage node 31, the target node 32 sends request information to the main storage node 31, the request information is used to indicate that the target node 32 intends to become a slave storage node, and includes identification information of the target node 32 and a terminal device number corresponding to the target node 32. Or/and the target node 33 sends request information to the master storage node 31, wherein the request information is used for indicating that the target node 33 wants to become a slave storage node, and the request information comprises identification information of the target node 33 and a terminal equipment number corresponding to the target node 33.
When the main storage node 31 receives the request information sent by the target node 32, the main storage node 31 obtains a source IP address, for example, TTT, of the request information, and searches a blockchain ledger locally stored in the main storage node 31 for an IP address, for example, UUU, broadcast by the target node 32 when joining the blockchain network, and further compares whether the source IP address, for example, TTT, of the request information is the same as the IP address, for example, UUU, broadcast by the target node 32 when joining the blockchain network.
Similarly, when the main storage node 31 receives the request message sent by the target node 33, the main storage node 31 obtains the source IP address, e.g., TTT, of the request message, and searches the blockchain ledger locally stored in the main storage node 31 for the IP address, e.g., UUU, broadcast by the target node 33 when joining the blockchain network, and further compares whether the source IP address, e.g., TTT, of the request message is the same as the IP address, e.g., UUU, broadcast by the target node 33 when joining the blockchain network.
As shown in fig. 3, the destination node 33 does not have its own public IP address, and therefore, the source IP address of the request message sent by the destination node 33 to the main storage node 31 may not be the own public IP address of the destination node 33, and the source IP address of the request message may be a public IP address allocated to the destination node 33 by an access point in a local area network corresponding to the destination node 33, and the source IP address of the request message may be different from the IP address broadcast by the destination node 33 when joining the blockchain network. Thus, when the primary storage node 31 compares the source IP address, e.g., TTT, of the request message sent by the target node 33 with the IP address, e.g., UUU, broadcast by the target node 33 when joining the blockchain network, the primary storage node 31 determines that the target node 33 is under NAT and that the target node 33 does not have its own public network IP address. The main storage node 31 further determines the public network IP address of the NAT corresponding to the destination node 33 and the port number mapped on the NAT by the destination node 33, specifically, the source IP address of the request information is the public network IP address of the NAT corresponding to the destination node 33, and the source port number of the request information is the port number mapped on the NAT by the destination node 33.
As shown in fig. 3, the destination node 32 has its own public network IP address, and therefore, the source IP address of the request message sent by the destination node 32 to the main storage node 31 is the own public network IP address of the destination node 32, and the source IP address of the request message is the same as the IP address broadcast by the destination node 32 when joining the blockchain network. Therefore, when the main storage node 31 compares the source IP address, e.g., TTT, of the request message sent by the target node 32 with the IP address, e.g., UUU, broadcast by the target node 32 when joining the blockchain network, and is the same, the main storage node 31 determines that the target node 32 is not under the NAT and the target node 32 has its own public network IP address, the source IP address of the request message sent by the target node 32 is the target node 32's own public network IP address, and the source port number of the request message sent by the target node 32 is the port number of the target node 32.
And step 204, the main storage node determines the type information of the NAT corresponding to the target node by sending a connection request to the target node.
When the main storage node 31 determines that the target node 33 is under the NAT and the target node 33 does not have its own public network IP address, the main storage node 31 further determines the type information of the NAT corresponding to the target node 33, where the type information of the NAT corresponding to the target node 33 includes an asymmetric type and a symmetric type.
And step 205, the master storage node sends the type information of the NAT to the target node.
When the main storage node 31 determines the type information of the NAT corresponding to the target node 33, the type information of the NAT corresponding to the target node 33 is sent to the target node 33.
In the embodiment of the invention, the main storage node receives the request information sent by the target node, compares whether the source IP address of the request information is the same as the IP address broadcast by the target node when the target node joins the block chain network, and if the source IP address of the request information is different from the IP address broadcast by the target node when the target node joins the block chain network, the main storage node determines that the target node is positioned under the NAT (network address translation), and determines the public network IP address of the NAT corresponding to the target node and the port number mapped by the target node on the NAT, so that the target node can become a slave storage node, the node without the public network IP address can also become a slave storage node, and the development of block chain service is promoted.
Fig. 4 is a flowchart of a block-node communication method according to another embodiment of the present invention. On the basis of the foregoing embodiment, the block link point communication method provided in this embodiment specifically includes the following steps:
The implementation manner of step 401 and step 201 is consistent with specific principles, and is not described herein again.
The implementation manner of step 402 and step 202 is consistent with specific principles, and will not be described herein.
The implementation manner of step 403 and step 203 is consistent with specific principles, and will not be described herein.
The master storage node 31 sends a connection request, which may specifically be a TCP connection request, to the target node 33 according to the source IP address, e.g. TTT, and the source port number, e.g. 4040, of the request information sent by the target node 33.
If the target node 33 receives the connection request sent by the main storage node 31 and sends a connection response to the main storage node 31, it indicates that the target node 33 is under the asymmetric NAT, i.e. the type information of the NAT corresponding to the target node 33 is asymmetric.
And step 406, the main storage node sends the type information of the NAT to the target node.
When the main storage node 31 determines the type information of the NAT corresponding to the target node 33, the type information of the NAT corresponding to the target node 33 is sent to the target node 33.
When the target node 33 receives that the type information of the NAT sent by the main storage node 31 is asymmetric, the target node 33 sends a first packet to the main storage node 31 according to the public network IP address of the NAT corresponding to the target node 33 at the current time and the port number of the target node 33 mapped on the NAT, where the source IP address of the first packet is the public network IP address of the NAT corresponding to the target node 33 at the current time, and the source port number of the first packet is the port number of the target node 33 mapped on the NAT at the current time. In addition, the first message further includes identification information of the target node 33 and a terminal device number corresponding to the target node 33, so that when the main storage node 31 receives the first message, the identity information of the target node 33 is identified according to the identification information of the target node 33. In addition, the target node 33 may also sign the first packet by using its own private key, that is, the target node 33 signs the identification information of the target node 33 and the terminal device number corresponding to the target node 33 by using its own private key, and sends the signed content to the main storage node 31, so that the main storage node 31 identifies the identity information of the target node 33 according to the signed content of the target node 33.
Optionally, the public network IP address of the NAT corresponding to the target node 33 and the port number mapped on the NAT by the target node 33 at different times may be different, that is, the public network IP address of the NAT corresponding to the target node 33 and the public network IP address of the NAT corresponding to the target node 33 at the current time may be different when the target node 33 sends the request information to the main storage node 31, and the port number mapped on the NAT by the target node 33 and the port number mapped on the NAT at the current time by the target node 33 when the target node 33 sends the request information to the main storage node 31 may be different.
After receiving the first packet sent by the destination node 33, the main storage node 31 extracts the source IP address and the source port number of the first packet, uses the source IP address and the source port number of the first packet as a new communication address of the destination node 33, and sends a second packet to the destination node 33 according to the source IP address and the source port number of the first packet.
And 409, receiving the heartbeat message periodically sent by the target node by the main storage node.
After receiving the second message sent by the main storage node 31, the target node 33 periodically sends a heartbeat message to the main storage node 31 according to the new communication address of the target node 33 in the second message, so as to keep the heartbeat channel between the target node 33 and the main storage node 31 open all the time.
And step 410, the main storage node updates the locally recorded public network IP address of the NAT corresponding to the target node and the port number mapped on the NAT by the target node according to the heartbeat message periodically sent by the target node.
The main storage node 31 updates the locally recorded public network IP address of the NAT corresponding to the target node 33 and the port number mapped on the NAT by the target node 33 according to the heartbeat packet periodically sent by the target node 33. In addition, the target node 33 may also broadcast the public network IP address of the NAT corresponding to the current time and the port number mapped on the NAT by the target node 33 at the current time to the blockchain network, so as to correct the IP address and the port number declared by the target node 33 at the historical time.
In the embodiment of the invention, the main storage node receives the request information sent by the target node, compares whether the source IP address of the request information is the same as the IP address broadcast by the target node when the target node joins the block chain network, and if the source IP address of the request information is different from the IP address broadcast by the target node when the target node joins the block chain network, the main storage node determines that the target node is positioned under the NAT (network address translation), and determines the public network IP address of the NAT corresponding to the target node and the port number mapped by the target node on the NAT, so that the target node can become a slave storage node, the node without the public network IP address can also become a slave storage node, and the development of block chain service is promoted.
Fig. 5 is a flowchart of a block-node communication method according to another embodiment of the present invention. On the basis of the foregoing embodiment, the block link point communication method provided in this embodiment specifically includes the following steps:
The implementation manner of step 501 and step 201 is consistent with specific principles, and is not described herein again.
The implementation manner of step 502 and step 202 is consistent with specific principles, and will not be described herein.
The implementation manner of step 503 and step 203 is consistent with specific principles, and is not described herein again.
The master storage node 31 sends a connection request, which may specifically be a TCP connection request, to the target node 33 according to the source IP address, e.g. TTT, and the source port number, e.g. 4040, of the request information sent by the target node 33.
After the main storage node 31 sends the connection request to the target node 33 according to the source IP address, e.g., TTT, and the source port number, e.g., 4040, of the request information sent by the target node 33, if the main storage node 31 does not receive the connection response sent by the target node 33 within the preset time, the main storage node 31 may send the connection request to the target node 33 again, and if the main storage node 31 still does not receive the connection response sent by the target node 33 within the preset time after sending the preset number of connection requests to the target node 33, it indicates that the target node 33 is under a symmetric NAT, that is, the type information of the NAT corresponding to the target node 33 is symmetric.
When the main storage node 31 determines the type information of the NAT corresponding to the target node 33, the type information of the NAT corresponding to the target node 33 is sent to the target node 33.
And step 507, the main storage node receives the query request sent by the query node.
For example, the master storage node 31 receives a query request sent by the query node 35.
The main storage node 31 sends the IP address and the port number of the querying node 35 to the target node 33, and optionally, the IP address of the querying node 35 is the source IP address of the querying request, and the port number of the querying node 35 is the source port number of the querying request. The target node 33 sends a heartbeat message to the query node 35 according to the IP address and the port number of the query node 35, and keeps a heartbeat channel between the target node 33 and the query node 35 open all the time, when the query node 35 needs to query information stored on the target node 33, the query node 35 can send a query request to the target node 33 through the heartbeat channel between the target node 33 and the query node 35, and the target node 33 can send a query result to the query node 35 through the heartbeat channel between the target node 33 and the query node 35.
In the embodiment of the invention, the main storage node receives the request information sent by the target node, compares whether the source IP address of the request information is the same as the IP address broadcast by the target node when the target node joins the block chain network, and if the source IP address of the request information is different from the IP address broadcast by the target node when the target node joins the block chain network, the main storage node determines that the target node is positioned under the NAT (network address translation), and determines the public network IP address of the NAT corresponding to the target node and the port number mapped by the target node on the NAT, so that the target node can become a slave storage node, the node without the public network IP address can also become a slave storage node, and the development of block chain service is promoted.
Fig. 6 is a schematic structural diagram of a block link point communication device according to an embodiment of the present invention. The block link point communicator may be the main storage node in the above embodiments. As shown in fig. 6, the block link point communication device 60 includes: a receiving module 61, a comparing module 62, a first determining module 63, a second determining module 64 and a sending module 65; the receiving module 61 is configured to receive request information sent by a target node, where the request information indicates that the target node requests to become a slave storage node, and the request information includes identification information of the target node; the comparing module 62 is configured to compare whether the source IP address of the request message is the same as the IP address broadcast by the target node when joining the blockchain network; the first determining module 63 is configured to determine that the target node is located under a network address translation NAT when a source IP address of the request information is different from an IP address broadcasted by the target node when the target node joins the block chain network, and determine a public network IP address of the NAT corresponding to the target node and a port number mapped by the target node on the NAT; the second determining module 64 is configured to determine the type information of the NAT corresponding to the target node by sending a connection request to the target node; the sending module 65 is configured to send the type information of the NAT to the target node.
Optionally, the sending module 65 is further configured to: sending a connection request to the target node according to the source IP address and the source port number of the request information; the second determining module 64 is specifically configured to: and when the receiving module receives the connection response sent by the target node, determining that the type information of the NAT corresponding to the target node is asymmetric.
Optionally, the receiving module 61 is further configured to: receiving a first message sent by the target node, wherein a source IP address of the first message is a public network IP address of an NAT corresponding to the target node at the current time, and a source port number of the first message is a port number mapped on the NAT by the target node at the current time; the sending module 65 is further configured to: sending a second message to the target node according to the source IP address and the source port number of the first message; the receiving module 61 is further configured to: receiving heartbeat messages periodically sent by the target node; the block-link point communication device 60 further includes: and the updating module 66, where the updating module 66 is configured to update the locally recorded public network IP address of the NAT corresponding to the target node and the port number mapped on the NAT by the target node according to the heartbeat packet periodically sent by the target node.
Optionally, the sending module 65 is further configured to: sending a connection request to the target node according to the source IP address and the source port number of the request information; the second determining module 64 is specifically configured to: and when the main storage node does not receive the connection response sent by the target node within the preset time, determining that the type information of the NAT corresponding to the target node is a symmetrical type.
Optionally, the receiving module 61 is further configured to: receiving a query request sent by a query node; the sending module 65 is further configured to: and sending the IP address and the port number of the query node to the target node so as to enable the target node and the query node to carry out information interaction.
The block link point communication apparatus of the embodiment shown in fig. 6 can be used to implement the technical solution of the above method embodiment, and the implementation principle and technical effect are similar, and are not described herein again.
Fig. 7 is a schematic structural diagram of a blockchain node according to an embodiment of the present invention. The block link point provided by the embodiment of the present invention may execute the processing procedure provided by the block link point communication method embodiment, as shown in fig. 7, the block link point 70 includes a memory 71, a processor 72, a computer program, and a communication interface 73; wherein a computer program is stored in the memory 71 and configured to be executed by the processor 72 for the block-link point communication method as described in the above embodiments.
The block link points of the embodiment shown in fig. 7 can be used to implement the technical solution of the above method embodiment, and the implementation principle and technical effect are similar, and are not described herein again.
In addition, the present embodiment also provides a computer-readable storage medium on which a computer program is stored, the computer program being executed by a processor to implement the block link point communication method described in the above embodiments.
In the embodiments provided in the present invention, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.
The integrated unit implemented in the form of a software functional unit may be stored in a computer readable storage medium. The software functional unit is stored in a storage medium and includes several instructions to enable a computer device (which may be a personal computer, a server, or a network device) or a processor (processor) to execute some steps of the methods according to the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
It is obvious to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional modules is merely used as an example, and in practical applications, the above function distribution may be performed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to perform all or part of the above described functions. For the specific working process of the device described above, reference may be made to the corresponding process in the foregoing method embodiment, which is not described herein again.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; while the invention has been described in detail and with reference to the foregoing embodiments, it will be understood by those skilled in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present invention.
Claims (12)
1. A block-node communication method, comprising:
a master storage node receives request information sent by a target node, wherein the request information indicates that the target node requests to become a slave storage node, and the request information comprises identification information of the target node; the main storage node and the target node are nodes in the same block chain network;
the main storage node compares whether the source IP address of the request information is the same as the IP address broadcast by the target node when the target node joins the block chain network;
if the source IP address of the request information is different from the IP address broadcast by the target node when the target node joins the block chain network, the main storage node determines that the target node is positioned under a Network Address Translation (NAT), determines the public network IP address of the NAT corresponding to the target node and the port number mapped by the target node on the NAT so as to enable the target node to become a slave storage node, the public network IP address of the NAT corresponding to the target node is the source IP address of the request information, and the port number mapped by the target node on the NAT is the source port number of the request information; the target node communicates with the main storage node through the NAT;
the main storage node determines the type information of the NAT corresponding to the target node by sending a connection request to the target node;
and the main storage node sends the NAT type information to the target node.
2. The method of claim 1, wherein the determining, by the master storage node sending a connection request to the target node, the type information of the NAT corresponding to the target node comprises:
the main storage node sends a connection request to the target node according to the source IP address and the source port number of the request information;
and if the main storage node receives the connection response sent by the target node, the main storage node determines that the type information of the NAT corresponding to the target node is asymmetric.
3. The method of claim 2, further comprising:
the main storage node receives a first message sent by the target node, wherein a source IP address of the first message is a public network IP address of an NAT corresponding to the target node at the current time, and a source port number of the first message is a port number mapped on the NAT by the target node at the current time;
the main storage node sends a second message to the target node according to the source IP address and the source port number of the first message;
the main storage node receives heartbeat messages periodically sent by the target node;
and the main storage node updates the locally recorded public network IP address of the NAT corresponding to the target node and the port number mapped on the NAT by the target node according to the heartbeat message periodically sent by the target node.
4. The method of claim 1, wherein the determining, by the master storage node sending a connection request to the target node, the type information of the NAT corresponding to the target node comprises:
the main storage node sends a connection request to the target node according to the source IP address and the source port number of the request information;
and if the main storage node does not receive the connection response sent by the target node within the preset time, the main storage node determines that the type information of the NAT corresponding to the target node is a symmetrical type.
5. The method of claim 4, further comprising:
the main storage node receives a query request sent by a query node;
and the main storage node sends the IP address and the port number of the query node to the target node so as to enable the target node and the query node to carry out information interaction.
6. A block-link point communication device, comprising:
a receiving module, configured to receive request information sent by a target node, where the request information indicates that the target node requests to become a slave storage node, and the request information includes identification information of the target node; the main storage node and the target node are nodes in the same block chain network;
the comparison module is used for comparing whether the source IP address of the request information is the same as the IP address broadcasted by the target node when the target node joins the block chain network;
a first determining module, configured to determine that the target node is located under a network address translation NAT when a source IP address of the request information is different from an IP address broadcasted by the target node when the target node joins a blockchain network, and determine a public network IP address of the NAT corresponding to the target node and a port number mapped by the target node on the NAT, so that the target node becomes a slave storage node, the public network IP address of the NAT corresponding to the target node is the source IP address of the request information, and the port number mapped by the target node on the NAT is a source port number of the request information; the target node communicates with the main storage node through the NAT;
a second determining module, configured to determine, by sending a connection request to the target node, type information of an NAT corresponding to the target node;
and the sending module is used for sending the NAT type information to the target node.
7. The block-link point communication device of claim 6, wherein the sending module is further configured to: sending a connection request to the target node according to the source IP address and the source port number of the request information;
the second determining module is specifically configured to: and when the receiving module receives the connection response sent by the target node, determining that the type information of the NAT corresponding to the target node is asymmetric.
8. The block-link point communication device of claim 7,
the receiving module is further configured to: receiving a first message sent by the target node, wherein a source IP address of the first message is a public network IP address of an NAT corresponding to the target node at the current time, and a source port number of the first message is a port number mapped on the NAT by the target node at the current time;
the sending module is further configured to: sending a second message to the target node according to the source IP address and the source port number of the first message;
the receiving module is further configured to: receiving heartbeat messages periodically sent by the target node;
the block link point communication device further comprises: and the updating module is used for updating the locally recorded public network IP address of the NAT corresponding to the target node and the port number mapped on the NAT by the target node according to the heartbeat message periodically sent by the target node.
9. The block-link point communication device of claim 6, wherein the sending module is further configured to: sending a connection request to the target node according to the source IP address and the source port number of the request information;
the second determining module is specifically configured to: and when the block link point communication device does not receive the connection response sent by the target node within the preset time, determining that the type information of the NAT corresponding to the target node is a symmetrical type.
10. The block-link point communication device of claim 9,
the receiving module is further configured to: receiving a query request sent by a query node;
the sending module is further configured to: and sending the IP address and the port number of the query node to the target node so as to enable the target node and the query node to carry out information interaction.
11. A block link point, comprising:
a memory;
a processor; and
a computer program;
wherein the computer program is stored in the memory and configured to be executed by the processor to implement the method of any one of claims 1-5.
12. A computer-readable storage medium, having stored thereon a computer program for execution by a processor to perform the method of any one of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810555793.1A CN108810186B (en) | 2018-05-31 | 2018-05-31 | Block chain node communication method and device and block chain node |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810555793.1A CN108810186B (en) | 2018-05-31 | 2018-05-31 | Block chain node communication method and device and block chain node |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108810186A CN108810186A (en) | 2018-11-13 |
| CN108810186B true CN108810186B (en) | 2021-05-18 |
Family
ID=64089930
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810555793.1A Active CN108810186B (en) | 2018-05-31 | 2018-05-31 | Block chain node communication method and device and block chain node |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108810186B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1697452A (en) * | 2005-06-17 | 2005-11-16 | 中兴通讯股份有限公司 | A security protection method for IP multimedia subsystem access based on IPSec traversal through NAT |
| CN101350825A (en) * | 2008-08-22 | 2009-01-21 | 中兴通讯股份有限公司 | Method and system for crossing network address conversion, stream media server, set-top box |
| CN104980528A (en) * | 2015-06-26 | 2015-10-14 | 广州华多网络科技有限公司 | Method, system and apparatus for realizing communication between nodes |
| CN106716421A (en) * | 2016-12-30 | 2017-05-24 | 深圳前海达闼云端智能科技有限公司 | Data query method, device and node apparatus |
| CN107911421A (en) * | 2017-10-30 | 2018-04-13 | 上海点融信息科技有限责任公司 | For configuring the method for internetwork communication, equipment and computer-readable storage medium in block chain |
-
2018
- 2018-05-31 CN CN201810555793.1A patent/CN108810186B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1697452A (en) * | 2005-06-17 | 2005-11-16 | 中兴通讯股份有限公司 | A security protection method for IP multimedia subsystem access based on IPSec traversal through NAT |
| CN101350825A (en) * | 2008-08-22 | 2009-01-21 | 中兴通讯股份有限公司 | Method and system for crossing network address conversion, stream media server, set-top box |
| CN104980528A (en) * | 2015-06-26 | 2015-10-14 | 广州华多网络科技有限公司 | Method, system and apparatus for realizing communication between nodes |
| CN106716421A (en) * | 2016-12-30 | 2017-05-24 | 深圳前海达闼云端智能科技有限公司 | Data query method, device and node apparatus |
| CN107911421A (en) * | 2017-10-30 | 2018-04-13 | 上海点融信息科技有限责任公司 | For configuring the method for internetwork communication, equipment and computer-readable storage medium in block chain |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108810186A (en) | 2018-11-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108712506B (en) | Block chain node communication method and device and block chain node | |
| EP3668134A1 (en) | Wireless communication method, network device, and terminal device | |
| CN109067724B (en) | Block chain data transaction method, device, equipment and storage medium | |
| CN109640274B (en) | Short message sending method and device based on block chain and computer readable storage medium | |
| CN108769142B (en) | Transaction information processing method and block generation node | |
| CN108810120B (en) | Block chain node communication method, device and block chain node | |
| CN109118360B (en) | Blockchain reconciliation method, device, equipment and storage medium | |
| CN108989043B (en) | Block processing method and device and block link points | |
| CN105165038B (en) | The method and apparatus of calling circulation for avoiding | |
| CN108777712B (en) | Block chain node communication method and device and block chain node | |
| CN108683727B (en) | Block processing method and master node | |
| CN108777710B (en) | Inter-node communication method and device of block chain and block chain node | |
| CN108848144B (en) | Method and device for accessing nodes in block chain and block chain link point | |
| CN108243631B (en) | A method and device for accessing a network | |
| CN108876611B (en) | Transaction information processing method and device and block link points | |
| CN109639715B (en) | Method, device and equipment for avoiding double-flower attack and computer readable storage medium | |
| CN108768733B (en) | Blockchain ledger processing method, device and blockchain node | |
| CN109087096B (en) | Blockchain reconciliation method, device, equipment and storage medium | |
| CN108898419B (en) | Reward information processing method, device and blockchain node | |
| CN108833513B (en) | Communication method and device between blockchain nodes, and blockchain node | |
| CN108769144A (en) | Storage processing method, transaction node, memory node and communication equipment | |
| CN108810186B (en) | Block chain node communication method and device and block chain node | |
| CN108712507B (en) | Block link point access method and device and block link point | |
| WO2017080303A1 (en) | Method and apparatus for processing circuit switched fallback (csfb) flow | |
| CN103053185B (en) | Network name processing method and mobility management network element equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |