CN109101664B

CN109101664B - Data transmission method, device, equipment and medium for lightweight node

Info

Publication number: CN109101664B
Application number: CN201811087950.7A
Authority: CN
Inventors: 肖伟
Original assignee: Baidu Online Network Technology Beijing Co Ltd
Current assignee: Baidu Online Network Technology Beijing Co Ltd
Priority date: 2018-09-18
Filing date: 2018-09-18
Publication date: 2021-12-07
Anticipated expiration: 2038-09-18
Also published as: CN109101664A

Abstract

The embodiment of the invention discloses a data transmission method, a device, equipment and a medium for a lightweight node. The method is applied to the lightweight node and comprises the following steps: sending a lightweight data transmission request to at least one full node to request the full node to eliminate the transmission of lightweight node non-associated transaction data; receiving data which is sent by a whole node and comprises a block header and light-weight node association transaction data; received data is verified. According to the technical scheme, the data to be received by the lightweight node are screened in a mode of excluding the lightweight node non-associated transaction data, so that the data transmission quantity of the lightweight node is reduced, the data transmission mode is optimized, and the performance requirement on the lightweight node is lowered.

Description

Data transmission method, device, equipment and medium for lightweight node

Technical Field

The embodiment of the invention relates to a block chain data communication technology, in particular to a data transmission method, a device, equipment and a medium for a lightweight node.

Background

The blockchain is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, a consensus mechanism and an encryption algorithm. Each node in a blockchain network needs to store all the data of the blockchain, and such nodes may be referred to as full nodes.

With the advancement of blockchain technology and the demand of application scenarios, the concept of lightweight nodes gradually appears. Lightweight nodes differ from full nodes in that only partial blockchain data is stored, e.g., only block headers, and no blocks, thereby alleviating the requirements on node hardware devices.

However, based on the operation rule of the blockchain, higher requirements are still put on the performance of the lightweight node in various aspects, such as data computing capacity, data transmission capacity and the like, and the popularization and application of the lightweight node are limited.

Disclosure of Invention

The embodiment of the invention provides a data transmission method, a data transmission device, data transmission equipment and a data transmission medium for a lightweight node, which are used for optimizing a data transmission mode and reducing the performance requirement on the lightweight node.

In a first aspect, an embodiment of the present invention provides a data transmission method for a lightweight node, where the method is applied to the lightweight node, and the method includes:

sending a lightweight data transmission request to at least one full node to request the full node to exclude the transmission of the lightweight node non-associated transaction data;

receiving data sent by the whole node, wherein the data comprises: associating the transaction data with the block header and the lightweight node;

and verifying the received data.

In a second aspect, an embodiment of the present invention further provides a data transmission method for a lightweight node, which is applied to a full node, and the method includes:

receiving a lightweight data transmission request sent by a lightweight node;

determining a block to be transmitted according to the lightweight data transmission request;

extracting the lightweight node associated transaction data from the block;

and sending the block head of the block and the light-weight node association transaction data to the light-weight node.

In a third aspect, an embodiment of the present invention further provides a data transmission device for a lightweight node, where the data transmission device is configured at the lightweight node, and the data transmission device includes:

a request sending module, configured to send a lightweight data transmission request to at least one full node to request the full node to exclude transmission of non-associated transaction data of the lightweight node;

a data receiving module, configured to receive data sent by the whole node, where the data includes: associating the transaction data with the block header and the lightweight node;

and the data verification module is used for verifying the received data.

In a fourth aspect, an embodiment of the present invention further provides a data transmission device for a lightweight node, where the data transmission device is configured at a full node, and the device includes:

the request receiving module is used for receiving a lightweight data transmission request sent by a lightweight node;

the block determining module is used for determining a block to be transmitted according to the lightweight data transmission request;

the data extraction module is used for extracting the light-weight node associated transaction data from the block;

and the data sending module is used for sending the block head of the block and the light-weight node association transaction data to the light-weight node.

In a fifth aspect, an embodiment of the present invention further provides an electronic device, including:

one or more processors;

a memory for storing one or more programs;

when the one or more programs are executed by the one or more processors, the one or more processors implement the data transmission method of the lightweight node as provided in the embodiment of the first aspect.

In a sixth aspect, an embodiment of the present invention further provides an electronic device, including:

one or more processors;

a memory for storing one or more programs;

when the one or more programs are executed by the one or more processors, the one or more processors implement a data transmission method of a lightweight node as provided in an embodiment of the second aspect.

In a seventh aspect, an embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a processor, the method for data transmission of a lightweight node is implemented as provided in the embodiment of the first aspect.

In an eighth aspect, the embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the data transmission method for the lightweight node as provided in the embodiment of the second aspect.

The lightweight node sends a lightweight data transmission request to at least one full node to request the full node to eliminate the transmission of non-associated transaction data of the lightweight node; receiving data which is sent by a whole node and comprises a block header and light-weight node association transaction data; received data is verified. According to the technical scheme, the data to be received by the lightweight node are screened in a mode of excluding the lightweight node non-associated transaction data, so that the data transmission quantity of the lightweight node is reduced, the data transmission mode is optimized, and the performance requirement on the lightweight node is lowered.

Drawings

Fig. 1 is a flowchart of a data transmission method for a lightweight node according to a first embodiment of the present invention;

fig. 2 is a flowchart of a data transmission method for a lightweight node according to a second embodiment of the present invention;

fig. 3 is a flowchart of a data transmission method for a lightweight node according to a third embodiment of the present invention;

fig. 4 is a flowchart of a data transmission method for a lightweight node according to a fourth embodiment of the present invention;

fig. 5 is a structural diagram of a data transmission apparatus of a lightweight node according to a fifth embodiment of the present invention;

fig. 6 is a structural diagram of a data transmission apparatus of a lightweight node according to a sixth embodiment of the present invention;

fig. 7 is a schematic structural diagram of an electronic device according to a seventh embodiment of the present invention.

Detailed Description

The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.

Example one

Fig. 1 is a flowchart of a data transmission method for a lightweight node according to a first embodiment of the present invention. The embodiment of the invention is suitable for the condition that the full node transmits data to the lightweight node, and the method can be executed by a data transmission device of the lightweight node, wherein the device is realized by software and/or hardware and is specifically configured in electronic equipment carrying the lightweight node.

The data transmission method of the lightweight node shown in fig. 1 includes:

s110, sending a lightweight data transmission request to at least one full node to request the full node to eliminate the transmission of the lightweight node non-associated transaction data.

The lightweight node is different from all nodes in the block chain network, and does not completely store data of all block chains, so that when the block chain needs to be completed, or one or more newly added block data needs to be added, or historical block data needs to be inquired, a lightweight data transmission request is initiated. For example, a user to which a lightweight node belongs may be in an active state infrequently, where the active state refers to generating or processing a transaction request, and then the lightweight node may trigger a lightweight data transfer request when the user triggers entry into the active state. For example, the active state is entered when a lightweight user transacts based on a blockchain.

The lightweight data transfer request represents a transaction request to obtain transaction data associated with a lightweight node. Wherein the obtained associated transaction data may be at least one of: all transaction data associated with the lightweight node in the blockchain; specifying transaction data associated with the lightweight node in the block in the blockchain; specified transaction data queried by lightweight nodes in the blockchain. The designated block may be the current block or other blocks in the designated block chain. The associated transaction data may be understood as transaction data of the lightweight node or the login account of the lightweight node as a participant.

The whole node receiving the lightweight data transmission request may be any conventional node in the blockchain network, which has all data of the blockchain, or may be a trust node of the lightweight node. The trust node may be a node with higher public trust, a node with higher data processing capability, a node with higher link times with the lightweight node, and/or a node establishing a fixed link relationship with the lightweight node in the blockchain network.

Preferably, the lightweight node sends a lightweight data transmission request to one or two full nodes with higher public confidence of the established fixed link relation.

Optionally, the lightweight data transmission request includes an association rule of the transaction data, and is used to instruct the full node to determine the association transaction data and the non-association transaction data according to the association rule.

The association rule may include a data selection condition set by a user. The data selection condition may include: basic limiting conditions related to the identification of the lightweight node or the login account of the lightweight node; the method can also comprise the following steps: the time node of the generation of the transaction data, or the block height of the block in which the transaction data is located.

The association rule may further include a data transmission format of data required by the lightweight node. Optionally, the data transmission format may be preconfigured in the data communication protocol of the deployment data of the lightweight node.

Specifically, when a user executes an inquiry operation of associated transaction data with a lightweight node in an electronic device carrying the lightweight node, or the lightweight node learns that a new block in a block chain network is out of blocks, a corresponding lightweight data transmission request is generated; and sending the generated lightweight data transmission request to at least one full node in the blockchain network in which the lightweight node participates. Correspondingly, after the full node receives the lightweight data transmission request, all block data, designated block data or designated transaction data are acquired, and non-associated transaction data with the lightweight node are eliminated, so that associated transaction data of the lightweight node are acquired.

Wherein the lightweight node associated transaction data may comprise element roll-in transaction data and/or element roll-out transaction data relating to the lightweight node. The associated transaction data may further include a running result of the intelligent contract, and the like.

S120, receiving data sent by the whole nodes, wherein the data comprises: the block header and the lightweight node associate transaction data.

And the full node feeds back the block body containing the light-weight node associated transaction data and the corresponding block head to the light-weight node. The block body is obtained by deleting the non-associated transaction data on the basis of the original block body, and the block head is the original block head in the block chain. And correspondingly, the lightweight node receives data. And the block header comprises a transaction identifier of the lightweight node associated transaction data.

It can be understood that, in order to facilitate the verification of the received data by the lightweight node, the data sent by the full node may further include matching verification information such as a lightweight node identifier or a lightweight node login account.

S130, verifying the received data.

For example, the received data may be verified by verifying the validity, and/or correctness of the associated transaction data in the received tile.

The verification of the received data may be, for example, the verification of the matching of the received data with the currently used lightweight node or the login account of the lightweight node. Specifically, the matching verification process may be: and judging whether the lightweight node identifier contained in the received data is the same as the node identifier of the currently used lightweight node or judging whether the lightweight node login account contained in the received data is the same as the currently used login account.

The lightweight node sends a lightweight data transmission request to at least one full node to request the full node to eliminate the transmission of non-associated transaction data of the lightweight node; receiving data which is sent by a whole node and comprises a block header and light-weight node association transaction data; received data is verified. According to the technical scheme, the data to be received by the lightweight node is screened in a mode of excluding the lightweight node non-associated transaction data, so that the data transmission quantity of the lightweight node is reduced, the data transmission mode is optimized, and the performance requirement on the lightweight node is lowered.

On the basis of the technical solutions of the foregoing embodiments, further, after "verifying the received data", the method further includes: and storing the received data.

Specifically, the lightweight node establishes a corresponding relationship between the associated transaction data and the account in the lightweight node according to the received data, and stores the associated transaction data and the account. In order to reduce the requirement on the storage space of the lightweight node, the lightweight node is allowed to have no block data, so that the lightweight node can be discarded after the block data is acquired and correspondingly processed, and can also be fixedly stored locally to form lightweight block chain data. The corresponding processing of the tile data may be, for example, displaying for a user to view, etc. The number of the login accounts corresponding to the lightweight node may be one or more, and preferably, the associated transaction data is stored in correspondence with the account number in the lightweight node, so that the user of the account can conveniently inquire the login account, which is equivalent to a lightweight book. The embodiment of the invention realizes the management of the lightweight node on the received data by locally storing the received data.

Example two

Fig. 2 is a flowchart of a data transmission method for a lightweight node in the second embodiment of the present invention. The embodiment of the invention carries out subdivision optimization on the basis of the technical scheme of each embodiment.

Further, the operation of verifying the received data is refined into the operation of verifying at least one of the validity and validity of the block and the correctness of the associated transaction data according to the received data so as to perfect a data verification mechanism of the lightweight node.

The data transmission method of the lightweight node shown in fig. 2 includes:

s210, sending a lightweight data transmission request to at least one full node to request the full node to eliminate the transmission of the lightweight node non-associated transaction data.

S220, receiving data sent by the whole nodes, wherein the data comprises: the block header and the lightweight node associate transaction data.

S230, at least one item of validity, validity and correctness of the associated transaction data of the block is verified according to the received data.

The validity is used as a judgment basis for judging whether the block where the received data is located is generated by a correct node in the block chain network; the validity is used as a criterion for determining whether the block in which the received data is located is a correct and continuous block in the block chain.

For example, according to the received data, the validity of the block is verified by: acquiring a block identifier of a previous block according to a block header of a locally stored historical block; and if the received block header comprises the block identification of the previous block, the validity verification is passed. Wherein the history block is a block previous to the currently received block stored in the lightweight node.

Illustratively, according to the received data, verifying the validity of the block may be: and verifying the legality of the block according to the received data and a consensus mechanism adopted by a block chain. When the consensus mechanism adopted by the block link points is different, the way of determining the nodes generating the blocks is also different.

Specifically, when the block chain network adopts a POW (Proof of Work) consensus mechanism, a nonce value in a received block header is obtained, and a hash value is calculated according to the nonce value and other data in the block header; comparing the obtained hash value with the block identifier of the obtained block header; and if the comparison results are the same, the validity verification is passed. Wherein the other data in the block header comprises at least one of a previous block identifier, a timestamp, a transaction identifier array, and a root of the Merkel tree.

Specifically, when the block chain network adopts a POS (Proof of stock) consensus mechanism, the lightweight node obtains the block height or the block identifier of the received block; determining a corresponding generation node identifier for the block identifier according to a consensus mechanism in the lightweight node deployment data; searching whether the generation node identification in the received block header is matched with the determined generation node identification; and if the two are matched, the validity verification is passed. The block identifier in the block header includes a node identifier of the generated block, that is, a node public key. The consensus mechanism presets the block generation nodes in the block chain network and the block-out time period or block height of each block generation node.

Wherein obtaining the block height of the received block comprises: the block height of the historical block locally stored by the lightweight node is directly obtained, or the block height of the received block is determined according to a set algorithm based on data contained in the received block header.

Illustratively, according to the received data, verifying the correctness of the associated transaction data may be: verifying whether a transaction array is in the block header; if yes, determining a transaction identifier according to the associated transaction data calculation, and verifying whether the transaction identifier of the associated transaction data is in a transaction array; if yes, the correctness verification is passed. The transaction array is an array of transaction identifiers of the transaction data in the storage block after hash operation. It will be appreciated that the correctness validation fails when the received block header does not contain a transaction array or the transaction identification associated with the transaction data is not in the transaction array.

It should be noted that when the associated transaction data includes the operation result of the intelligent contract, the lightweight node needs to further verify the correctness of the operation result of the intelligent contract when verifying the correctness of the associated transaction data.

If the lightweight node is difficult to verify at least one of the validity, the validity and the correctness of the associated transaction data of the block due to a common identification mechanism or the calculation force of the lightweight node or the like, or the lightweight node is expected to further improve the verification reliability, optionally, the lightweight node can also send a verification consultation message to at least one full node according to a locally maintained full node list to request other full nodes to verify at least one of the validity, the validity and the correctness of the associated transaction data of the block, wherein the full node requesting consultation is different from the full node sending the lightweight data transmission request; and receiving the verification result fed back by other full nodes. Correspondingly, the lightweight node judges at least one of the legality and the validity of the received data and the correctness of the associated transaction data according to the verification result fed back by the full node. Wherein verifying the advisory message comprises: at least one of a validity verification message, and an associated transaction data correctness verification message.

Specifically, the verification of the validity of the block may be: and the lightweight node sends a validity verification message to at least one full node in a locally maintained full node list, wherein the validity verification message comprises a block header of a block to be verified. Correspondingly, the full node receives the validity verification message, searches the block identifier of the corresponding block stored locally based on the block identifier in the block header, and compares the block identifier with the block identifier of the block to be verified to obtain a comparison result; obtaining a block identifier of a previous block of a corresponding block stored locally and comparing the block identifier of the previous block contained in the block to be verified to obtain a comparison result; if the comparison results are the same, the validity verification is passed; otherwise, the validity verification is not passed; and feeding back a verification result of the validity verification to the lightweight node.

Specifically, the verifying the validity of the block may be: and the lightweight node sends a validity verification message to at least one full node in a locally maintained full node list, wherein the validity verification message comprises a block header of a block to be verified. Correspondingly, the all-node receives the validity verification message and compares the data contained in the block head of the block to be verified with the information in the corresponding block head in the local storage area block chain to verify the validity of the block; and feeding back a verification result of the validity verification to the lightweight node.

Specifically, the verifying the correctness of the associated transaction data may be: and the lightweight node sends an associated transaction data correctness verification message to at least one full node in a locally maintained full node list, wherein the associated transaction data correctness verification message comprises the data received by the lightweight node. Correspondingly, after receiving the correctness verification message, the whole node searches the associated transaction data in the corresponding block in the block chain according to the received data and compares the transaction data; if the comparison result is consistent, the correctness verification of the associated transaction data is passed; otherwise, the correctness verification is not passed; and feeding back a verification result of correctness verification to the lightweight node.

It can be understood that, in order to reduce the amount of data transmitted by the lightweight node, the received data may be directly signed to obtain a data signature identifier, and the data signature identifier is added to the verification consultation message and sent to at least one full node in the locally maintained full node list. The operation performed by the verification-performing full node is similar to that performed by the data-providing full node, and the required block is also queried for the lightweight node, and the block header and the associated transaction data are obtained. The data content provided by different overall nodes should be the same. And then signature calculation is carried out based on a set algorithm, comparison with a data signature identification provided by the lightweight node is carried out, and if the signature identification is consistent with the data signature identification provided by the lightweight node, verification is passed.

It should be noted that the lightweight node may verify the correctness of the block data locally, but it is difficult to verify the integrity. In particular, the associated transaction data typically includes element in transaction data and element out transaction data. For element roll-out transaction data, it is a transaction request initiated by the lightweight node side, so it can be determined from the native record whether all element roll-out transaction data is included. For element transfer-in transaction data, the lightweight node may not know and verify whether the full node provides all the transaction data for transferring elements to the local account. Therefore, the verification consultation message can be initiated, and consultation verification can be carried out on a plurality of full nodes. The integrity verification does not affect the correctness of the block data in the block chain, namely, the element transfer transaction data is stored in the block chain in the processing process, and the confirmation of all the nodes is obtained. Integrity verification may be optionally performed based on user requirements and/or network bandwidth, among other conditions.

The embodiment of the invention verifies the validity and validity of the block and/or the correctness of the associated transaction data according to the received data, provides different verification modes according to the calculation power condition of the lightweight node, and perfects the data verification mechanism of the lightweight node.

EXAMPLE III

Fig. 3 is a flowchart of a data transmission method for a lightweight node in a third embodiment of the present invention. The embodiment of the invention is applicable to the condition that all nodes transmit data to the lightweight node, and the method can be executed by a data transmission device of all nodes, wherein the data transmission device is realized by software and/or hardware and is specifically configured in electronic equipment carrying all nodes.

The full node may be any conventional node in the blockchain network, which has all data of the blockchain, or may be a trust node of the lightweight node. The trust node may be a node with higher public trust, a node with higher data processing capability, a node with higher number of links with the lightweight node, and/or a node establishing a fixed link relationship with the lightweight node in the blockchain network. Preferably, the full node according to the embodiment of the present invention is one or two full nodes with higher public confidence that a fixed link relationship has been established with the lightweight node.

A data transmission method of a lightweight node shown in fig. 3 includes:

and S310, receiving a lightweight data transmission request sent by a lightweight node.

Wherein the lightweight data transfer request represents a transaction request to obtain transaction data associated with a lightweight node. Wherein the obtained associated transaction data may be at least one of: all transaction data associated with the lightweight node in the blockchain; specifying transaction data associated with the lightweight node in the block in the blockchain; specified transaction data queried by lightweight nodes in the blockchain. The designated block may be the current block or other blocks in the designated block chain. The associated transaction data may be understood as transaction data of the lightweight node or the login account of the lightweight node as a participant.

When a user executes query operation of associated transaction data of the lightweight node in the electronic equipment bearing the lightweight node, or when the lightweight node knows that a new block in a block chain network is out of the block, a corresponding lightweight data transmission request is generated; and sending the generated lightweight data transmission request to at least one full node in the blockchain network in which the lightweight node participates. Accordingly, the full node receives the lightweight data transmission request.

S320, determining a block to be transmitted according to the lightweight data transmission request.

Optionally, the lightweight data transmission request includes an association rule of the transaction data. The full node acquires the association rule of the transaction data in the lightweight data transmission request; and extracting the lightweight node associated transaction data from the block according to the association rule of the transaction data.

The association rule comprises a data selection condition set by a user. The data selection condition may include: basic limiting conditions related to the identification of the lightweight node or the login account of the lightweight node; the method can also comprise the following steps: the time node of the generation of the transaction data, or the block height of the block in which the transaction data is located.

Specifically, the full node determines, according to the data selection condition, a block corresponding to the transaction data satisfying the data selection condition as a block to be transmitted.

Alternatively, the full node may also provide the associated transaction data to the lightweight node according to the lightweight node transmission requirement predefined by the local deployment data.

S330, extracting the light-weight node associated transaction data from the block.

Specifically, non-associated transaction data included in the block body of the block to be transmitted and the lightweight node is excluded, so that associated transaction data is obtained. The original block may be copied and then the non-associated transaction data may be deleted, or the block header and the required associated transaction data may be extracted from the original block, which is equivalent to deleting the lightweight node non-associated transaction data from the original block. The blockchain stored locally at all nodes does not change accordingly.

Wherein the lightweight node associated transaction data comprises element roll-in transaction data and/or element roll-out transaction data relating to the lightweight node. Wherein the associated transaction data may further include a running result of the intelligent contract.

S340, sending the transaction data associated with the block head and the lightweight node of the block to the lightweight node.

The association rule may further include a data transmission format of data required by the lightweight node. Optionally, the data transmission format may be configured in a data communication protocol of the deployment data of the lightweight node.

Specifically, the full node sends the block header of the block and the associated transaction data to the lightweight node according to the data transmission format of the data required by the lightweight node. It will be appreciated that when no associated transaction data is present in the block, the block header may be transferred directly to the lightweight node.

The method comprises the steps that a full node receives a lightweight data transmission request sent by a lightweight node; determining a block to be transmitted according to the lightweight data transmission request; extracting lightweight node associated transaction data from the block; and associating the block head of the block with the lightweight node to send transaction data to the lightweight node. According to the technical scheme, the data sent to the lightweight nodes are screened in a mode of excluding the lightweight node non-associated transaction data, so that the data transmission quantity of the lightweight nodes is reduced, the data transmission mode is optimized, and the performance requirement on the lightweight nodes is lowered.

Example four

Fig. 4 is a flowchart of a data transmission method for a lightweight node in the fourth embodiment of the present invention. The embodiment of the invention performs additional optimization on the basis of the technical scheme of each embodiment.

Further, the whole node can also be used for receiving verification consultation messages sent by other lightweight nodes; and verifying the verification requirement in the verification consultation message according to the data in the local block chain, and feeding back the verification result to respond to the verification consultation messages of other lightweight nodes and assist other lightweight nodes in data verification. Typically, the lightweight node is different from the full node requesting to provide the block data and the full node requesting to consult for verification. Each full node may provide services for transmitting data and consulting the verification to different lightweight nodes.

The data transmission method of the lightweight node shown in fig. 4 includes:

and S410, receiving a verification consultation message sent by the lightweight node.

Wherein verifying the advisory message comprises: at least one of a validity verification message, and an associated transaction data correctness verification message. The validity verification message and the validity verification message are used for verifying the validity or validity of the block to be verified. The validity is used as a judgment basis for judging whether the block where the received data is located is generated by a correct node in the block chain network; the validity is used as a criterion for determining whether the block in which the received data is located is a correctly connected block in the block chain.

And S420, verifying the verification requirement in the verification consultation message according to the data in the local block chain, and feeding back the verification result.

When the advisory message is verified as the validity advisory message, specifically: and the lightweight node sends a validity verification message to at least one full node in a locally maintained full node list, wherein the validity verification message comprises a block header of a block to be verified. Correspondingly, the all-node receives the validity verification message, searches the block identifier of the corresponding block stored locally based on the block identifier in the block header, and compares the block identifier with the block identifier of the block to be verified to obtain a comparison result; obtaining a block identifier of a previous block of a corresponding block stored locally and comparing the block identifier of the previous block contained in the block to be verified to obtain a comparison result; if the comparison results are the same, the validity verification is passed; otherwise, the validity verification is not passed; and feeding back a verification result of the validity verification to the lightweight node.

When the verification consultation message is a validity verification message, specifically: and the lightweight node sends a validity verification message to at least one full node in a locally maintained full node list, wherein the validity verification message comprises a block header of a block to be verified. Correspondingly, the all-node receives the validity verification message and compares the data contained in the block head of the block to be verified with the information in the corresponding block head in the local storage area block chain to verify the validity of the block; and feeding back a verification result of the validity verification to the lightweight node.

When the verification consultation message is the associated transaction data correctness verification message, specifically: and the lightweight node sends an associated transaction data correctness verification message to at least one full node in a locally maintained full node list, wherein the associated transaction data correctness verification message comprises the data received by the lightweight node. Correspondingly, after receiving the correctness verification message, the whole node searches the associated transaction data in the corresponding block in the block chain according to the received data and compares the transaction data; if the comparison result is consistent, the correctness verification of the associated transaction data is passed; otherwise, the correctness verification is not passed; and feeding back a verification result of correctness verification to the lightweight node.

It can be understood that, in order to reduce the amount of data transmitted by the lightweight node, the lightweight node may also directly sign the received data to obtain a data signature identifier, and add the data signature identifier to the verification consultation message and send the verification consultation message to at least one full node in the locally maintained full node list. The operation performed by the verification-performing full node is similar to that performed by the data-providing full node, and the required block is also queried for the lightweight node, and the block header and the associated transaction data are obtained. The data content provided by different overall nodes should be the same. And then signature calculation is carried out based on a set algorithm, comparison with a data signature identification provided by the lightweight node is carried out, and if the signature identification is consistent with the data signature identification provided by the lightweight node, verification is passed. And feeding back a verification result of correctness verification to the lightweight node.

The embodiment of the invention receives a verification consultation message sent by a lightweight node by a full node; according to the data in the local block chain, the auxiliary lightweight node verifies the validity and validity of the block received by the lightweight node and/or the correctness of the associated transaction data, meanwhile, a verification basis is provided for the integrity of the data received by the lightweight node, and a verification mechanism of the lightweight node is perfected.

EXAMPLE five

Fig. 5 is a structural diagram of a data transmission apparatus of a lightweight node in the fifth embodiment of the present invention. The embodiment of the invention can be suitable for the condition that the data is transmitted from the full node to the lightweight node, and the device is realized by software and/or hardware and is specifically configured in the electronic equipment carrying the lightweight node. The data transmission apparatus of the lightweight node shown in fig. 5 includes: a request sending module 510, a data receiving module 520, and a data verification module 530.

The request sending module 510 is configured to send a lightweight data transmission request to at least one full node, so as to request the full node to exclude transmission of non-associated transaction data of the lightweight node;

a data receiving module 520, configured to receive data sent by the whole node, where the data includes: associating the transaction data with the block header and the lightweight node;

a data verification module 530, configured to verify the received data.

The embodiment of the invention sends a lightweight data transmission request to at least one full node through a request sending module lightweight node to request the full node to eliminate the transmission of non-associated transaction data of the lightweight node; receiving data which is sent by a full node and comprises a block header and light-weight node associated transaction data through a data receiving module; and verifying the received data through a data verification module. According to the technical scheme, the data to be received by the lightweight node are screened in a mode of excluding the lightweight node non-associated transaction data, so that the data transmission quantity of the lightweight node is reduced, the data transmission mode is optimized, and the performance requirement on the lightweight node is lowered.

Further, the lightweight data transmission request includes an association rule of the transaction data, and is used to instruct the full node to determine association transaction data and non-association transaction data according to the association rule.

Further, the association rule of the transaction data is configured in the deployment data of the lightweight node.

Further, the lightweight node associated transaction data includes element roll-in transaction data and/or element roll-out transaction data relating to the lightweight node.

Further, the data verification module 530 is specifically configured to:

and verifying at least one of the validity and validity of the block and the correctness of the associated transaction data according to the received data.

Further, the data verification module 530 includes a secondary verification unit for:

sending a verification consultation message to at least one full node according to a locally maintained full node list so as to request other full nodes to verify at least one of the validity, validity and correctness of the associated transaction data of the block;

and receiving the verification result fed back by other full nodes.

Further, the data verification module 530 further includes a message adding unit, configured to sign the received data before the auxiliary verification unit sends the verification inquiry message to at least one full node according to the locally maintained full node list, and add the signed data to the verification inquiry message.

Further, the data verification module 530 includes a validity verification unit, specifically configured to:

acquiring a block identifier of a previous block according to a block header of a locally stored historical block;

and if the received block header comprises the block identification of the previous block, the validity verification is passed.

Further, the data verification module 530 includes a validity verification unit, which is specifically configured to:

and verifying the legality of the block according to the received data and a consensus mechanism adopted by a block chain.

Further, the data verification module 530 includes a correctness verification unit, specifically configured to:

verifying whether a transaction array is in the block header;

if yes, determining a transaction identifier according to the associated transaction data calculation, and verifying whether the transaction identifier of the associated transaction data is in a transaction array;

if yes, the correctness verification is passed.

Further, the apparatus further comprises a data storage module, configured to: and after the received data is verified, storing the received data.

Further, the data storage module is specifically configured to: and establishing a corresponding relation between the associated transaction data and the account in the lightweight node according to the received data, and storing the corresponding relation.

The data transmission device of the lightweight node provided by the embodiment of the invention can execute the data transmission method of the lightweight node provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of executing the data transmission method of the lightweight node.

EXAMPLE six

Fig. 6 is a structural diagram of a data transmission apparatus of a lightweight node according to a sixth embodiment of the present invention. The embodiment of the invention can be suitable for the condition that the whole node transmits data to the lightweight node, and the device is realized by software and/or hardware and is specifically configured in the electronic equipment carrying the whole node. The data transmission apparatus of the lightweight node shown in fig. 6 includes: a request receiving module 610, a block determining module 620, a data extracting module 630 and a data transmitting module 640.

The request receiving module 610 is configured to receive a lightweight data transmission request sent by a lightweight node;

a block determining module 620, configured to determine a block to be transmitted according to the lightweight data transmission request;

a data extraction module 630, configured to extract the lightweight node associated transaction data from the block;

a data sending module 640, configured to send the block header of the block and the transaction data associated with the lightweight node to the lightweight node.

The embodiment of the invention receives a lightweight data transmission request sent by a lightweight node through a request receiving module; determining a block to be transmitted according to the lightweight data transmission request through a block determination module; extracting lightweight node associated transaction data from the block through a data extraction module; and sending the block head of the block and the light-weight node association transaction data to the light-weight node through a data sending module. According to the technical scheme, the data sent to the lightweight nodes are screened in a mode of excluding the lightweight node non-associated transaction data, so that the data transmission quantity of the lightweight nodes is reduced, the data transmission mode is optimized, and the performance requirement on the lightweight nodes is lowered.

Further, the data extraction module 630 includes:

an association rule obtaining unit, configured to obtain an association rule of the transaction data in the lightweight data transmission request;

and the data extraction unit is used for extracting the light-weight node associated transaction data from the block according to the association rule of the transaction data.

Further, the apparatus further includes a verification feedback module, specifically including:

the verification consultation information receiving unit is used for receiving verification consultation information sent by other lightweight nodes;

and the verification result feedback unit is used for verifying the verification requirement in the verification consultation message according to the data in the local block chain and feeding back the verification result.

Further, the verification result feedback unit is specifically configured to:

obtaining a data signature from the verification advisory message;

acquiring a block to be verified from a local block chain, and acquiring block head and light-weight node associated transaction data from the block;

and performing signature calculation on the block head and the light-weight node associated transaction data, comparing whether the calculated signature is consistent with the acquired data signature, and if so, feeding back a passing verification result.

EXAMPLE seven

Fig. 7 is a schematic structural diagram of an electronic device according to a seventh embodiment of the present invention. FIG. 7 illustrates a block diagram of an exemplary electronic device 712 suitable for use in implementing embodiments of the present invention. The electronic device 712 shown in fig. 7 is only an example and should not bring any limitations to the function and the scope of use of the embodiments of the present invention.

As shown in fig. 7, electronic device 712 is embodied in the form of a general purpose computing device. Components of electronic device 712 may include, but are not limited to: one or more processors or processing units 716, a system memory 728, and a bus 718 that couples the various system components (including the system memory 728 and the processing unit 716).

Bus 718 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, such architectures include, but are not limited to, Industry Standard Architecture (ISA) bus, micro-channel architecture (MAC) bus, enhanced ISA bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus.

Electronic device 712 typically includes a variety of computer system readable media. Such media can be any available media that is accessible by electronic device 712 and includes both volatile and nonvolatile media, removable and non-removable media.

The system memory 728 may include computer system readable media in the form of volatile memory, such as Random Access Memory (RAM)730 and/or cache memory 732. The electronic device 712 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 734 may be used to read from and write to non-removable, nonvolatile magnetic media (not shown in FIG. 7, commonly referred to as a "hard drive"). Although not shown in FIG. 7, a magnetic disk drive for reading from and writing to a removable, nonvolatile magnetic disk (e.g., a "floppy disk") and an optical disk drive for reading from or writing to a removable, nonvolatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to the bus 718 by one or more data media interfaces. Memory 728 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.

Program/utility 740 having a set (at least one) of program modules 742 may be stored, for instance, in memory 728, such program modules 742 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which examples or some combination thereof may include an implementation of a network environment. Program modules 742 generally perform the functions and/or methodologies of embodiments of the invention as described herein.

The electronic device 712 may also communicate with one or more external devices 714 (e.g., keyboard, pointing device, display 724, etc.), with one or more devices that enable a user to interact with the electronic device 712, and/or with any devices (e.g., network card, modem, etc.) that enable the electronic device 712 to communicate with one or more other computing devices. Such communication may occur through input/output (I/O) interfaces 722. Also, the electronic device 712 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the internet) via the network adapter 720. As shown, the network adapter 720 communicates with the other modules of the electronic device 712 via the bus 718. It should be appreciated that although not shown, other hardware and/or software modules may be used in conjunction with the electronic device 712, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.

The processing unit 716 executes various functional applications and data processing by executing at least one program of a plurality of programs stored in the system memory 728, for example, to implement a data transmission method of a lightweight node provided by the embodiment of the present invention.

Example eight

The eighth embodiment of the present invention further provides an electronic device, and the structural diagram of the electronic device may also refer to fig. 7.

The embodiment of the invention is different from the seventh embodiment only in that: the processing unit 716 executes programs stored in the system memory 728 to execute various functional applications and data processing, for example, to implement another data transmission method of the lightweight node provided by the embodiment of the present invention.

Example nine

An embodiment ninth of the present invention provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements a data transmission method for a lightweight node provided in any embodiment of the present invention, where the method is applied to the lightweight node, and the method includes: sending a lightweight data transmission request to at least one full node to request the full node to exclude the transmission of the lightweight node non-associated transaction data; receiving data sent by the whole node, wherein the data comprises: associating the transaction data with the block header and the lightweight node; and verifying the received data.

The embodiment of the present invention further provides another computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements a data transmission method for a lightweight node provided in any embodiment of the present invention, where the method is applied to a full node, and the method includes: receiving a lightweight data transmission request sent by a lightweight node; determining a block to be transmitted according to the lightweight data transmission request; extracting the lightweight node associated transaction data from the block; and sending the block head of the block and the light-weight node association transaction data to the light-weight node.

Computer storage media for embodiments of the invention may employ any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).

It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A data transmission method of a lightweight node is applied to the lightweight node, and the method comprises the following steps:

verifying the received data;

wherein the verifying the received data comprises:

verifying whether a transaction array is in the block header; if yes, determining a transaction identifier according to the associated transaction data calculation, and verifying whether the transaction identifier of the associated transaction data is in the transaction array; if yes, the correctness verification is passed.

2. The method according to claim 1, wherein the lightweight data transmission request includes an association rule of the transaction data, and is used to instruct the full node to determine the association transaction data and the non-association transaction data according to the association rule.

3. The method of claim 2, wherein the association rule for the transaction data is configured in deployment data for the lightweight node.

4. The method according to claim 1, wherein associating transaction data with a lightweight node comprises transferring element in transaction data and/or transferring element out transaction data involving the lightweight node.

5. The method of claim 1, wherein validating the received data further comprises:

and verifying the legality and/or validity of the block according to the received data.

6. The method of claim 5, wherein verifying at least one of the validity, and correctness of the associated transaction data for the block based on the received data comprises:

and receiving the verification result fed back by other full nodes.

7. The method of claim 6, wherein before sending the validation consultation message to at least one full node according to a locally maintained full node list, further comprising:

and signing the received data, and adding the signed data into the verification consultation message.

8. The method of claim 5, wherein verifying the validity of the block based on the received data comprises:

9. The method of claim 5, wherein verifying the validity of the block based on the received data comprises:

10. The method of claim 1, wherein after verifying the received data, further comprising:

and storing the received data.

11. The method of claim 10, wherein storing the received data comprises:

and establishing a corresponding relation between the associated transaction data and the account in the lightweight node according to the received data, and storing the corresponding relation.

12. A data transmission method of a lightweight node is applied to a full node, and the method comprises the following steps:

receiving a lightweight data transmission request sent by a lightweight node;

extracting the lightweight node associated transaction data from the block;

sending the block head of the block and the transaction data associated with the lightweight node to the lightweight node so that the lightweight node verifies the received data based on the following modes:

13. The method of claim 12, wherein extracting the lightweight node associated transaction data from the block comprises:

acquiring an association rule of the transaction data in the lightweight data transmission request;

and extracting the lightweight node associated transaction data from the block according to the association rule of the transaction data.

14. The method according to claim 13, wherein associating transaction data with a lightweight node comprises transferring element in transaction data and/or transferring element out transaction data involving the lightweight node.

15. The method of claim 12, further comprising:

receiving verification consultation messages sent by other lightweight nodes;

and verifying the verification requirement in the verification consultation message according to the data in the local block chain, and feeding back the verification result.

16. The method of claim 15, wherein verifying the verification requirement in the verification consultation message according to data in a local blockchain, and feeding back the verification result comprises:

obtaining a data signature from the verification advisory message;

17. A data transmission apparatus for a lightweight node, the apparatus being configured for the lightweight node, the apparatus comprising:

the data verification module is used for verifying the received data;

the data verification module comprises a correctness verification unit and is specifically used for:

verifying whether a transaction array is in the block header;

if yes, determining a transaction identifier according to the associated transaction data calculation, and verifying whether the transaction identifier of the associated transaction data is in the transaction array;

if yes, the correctness verification is passed.

18. A data transmission apparatus for a lightweight node, configured to a full node, the apparatus comprising:

a data sending module, configured to send the block header of the block and the transaction data associated with the lightweight node to the lightweight node, so that the lightweight node verifies the received data based on the following manner:

19. An electronic device, comprising:

one or more processors;

a memory for storing one or more programs;

when executed by the one or more processors, cause the one or more processors to implement a method of data transmission for a lightweight node as recited in any of claims 1-11.

20. An electronic device, comprising:

one or more processors;

a memory for storing one or more programs;

when executed by the one or more processors, cause the one or more processors to implement a method of data transmission for a lightweight node as recited in any of claims 12-16.

21. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out a method of data transmission of a lightweight node according to any one of claims 1 to 11.

22. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out a method of data transmission of a lightweight node according to any one of claims 12 to 16.