CN111080287B

CN111080287B - Service data processing method, related equipment and system

Info

Publication number: CN111080287B
Application number: CN201811215247.XA
Authority: CN
Inventors: 朱晓琪; 易旭昆
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2018-10-18
Filing date: 2018-10-18
Publication date: 2023-06-16
Anticipated expiration: 2038-10-18
Also published as: CN111080287A

Abstract

The application discloses a service data processing method, related equipment and a system. The assigned management node in the block chain system maintains the sub-chain consensus process, all nodes in the block chain system are not required to participate in the sub-chain consensus process, the consumption of computing resources caused by generation of block consumption by all nodes in the block chain system is avoided, and the utilization rate of the computing resources of the block chain system is improved. In addition, a plurality of sub-chains can be formed on the block chain, different sub-chains correspond to different services, and the types of service data recorded by different sub-chains can also be different, so that the capability of recording various different types of service data in the block chain system is realized.

Description

Service data processing method, related equipment and system

Technical Field

The present invention relates to the field of communications, and in particular, to a method, related device, and system for processing service data.

Background

The blockchain technology integrates novel application modes of computer technologies such as distributed data storage, point-to-point transmission, consensus mechanism, encryption algorithm and the like, and is originally born in a bottom technology architecture of bit coin, and the application of the blockchain technology is more and more widely applied.

Current blockchain technology can be categorized from the participant perspective into public chains, federated chains, and private chains, which are implemented primarily within individuals or companies, with no significant benefit over the centralized model. The federation chain is defined by a plurality of preselected nodes within a community as accounting nodes, the generation of each block is determined by the preselected nodes in common, and other nodes can participate in the transaction but do not go through the accounting process. A public chain means that any individual or group participates in the consensus process.

In a blockchain system of a public chain, each node stores a same local account book, the local account books are stored in a blockchain mode, and each node forms a distributed database system. The block chain comprises blocks, the first block is called an originating block, the originating block does not comprise the digest value of the father block, and other blocks except the originating block comprise the digest value of the last block, so that a chain structure is formed. The block comprises a block header and a block body, wherein a plurality of transaction data and abstract values obtained by the transaction data are kept in the block header, and a merkel (Merkle) root abstract value is generated in the form of a Merkletree. The common information of the block is included in the block header: parent block digest value, timestamp, version number, difficulty value, merkle root, random number.

Under a common chain architecture, a consensus needs to be generated within all nodes. All nodes participating in consensus are concentrated on the tail blocks of the blockchain to contend for accounting rights, and bifurcation-confirmation nodes-bifurcation elimination can be continuously generated in the consensus process. Only the node that finally obtains the accounting right can obtain the benefit, so that many nodes consume much calculation power, but cannot obtain the benefit. How to reduce the number of nodes involved in achieving consensus on one business data and reduce the waste of computing resources in the whole blockchain ecology is a technical problem to be solved.

Disclosure of Invention

The technical problem to be solved in the application is to provide a method, a device and a system for processing service data so as to reduce the waste of computing resources of nodes in a block chain system.

In a first aspect, the present application provides a method for processing service data, where the processing method is applied to a first management node in a blockchain system, where the blockchain system includes a first management node set and a second management node set, where the first management node set includes a first management node and a second management node, the second management node set includes a third management node and a fourth management node, the first management node set is used to process service data of a first service, i.e., the first management node set participates in a consensus process for service data of the first service, and the second management node set is used to manage a first blockchain, i.e., the second management node set participates in a consensus process for a block on the first blockchain. The processing method comprises the following steps: the first management node receives first service data from the terminal device, the first service data is generated by the first service, the first management node generates a first block according to the first service data, the first block comprises a service identifier of the first service data and a digest value of the second block, the digest value represents a value obtained by using a hash algorithm, and the digest value can be called a hash value or an MD5 (message digest algorithm, a fifth version of a message digest algorithm) value. The second block is a tail block in the first blockchain, which is the last block in the first blockchain, and the tail block is the latest block in the first blockchain. The first management node broadcasts a first block in the block chain system, the first set of management nodes participate in the consensus of the first block, the first management node determines that the management node agrees with the first block, and the first management node links the first block to the second block to form a first sub-chain of the first block chain, namely the first block is the first block in the first sub-chain. The first management node sends the billing information of the first block to the second set of management nodes, the first management node receives a third block from a third management node, the third management node is a billing node in the second set of management nodes, the third block is generated by the third management node according to the billing information of the first block, the billing information of the first block comprises the abstract value of the second block and the service identifier of the first service, and the first management node links the third block to the second block.

By implementing the embodiment of the invention, the first set of management nodes is used for maintaining the consensus process of the sub-chain, all nodes in the block chain system are not required to participate in the consensus process of the sub-chain, the consumption of computing resources caused by generation of block consumption by other nodes outside the set of management nodes is avoided, and the utilization rate of the computing resources of the block chain system is improved. In addition, a plurality of sub-chains can be formed on the first block chain, different sub-chains correspond to different services, and the types of the business data recorded by different sub-chains can also be different, so that the capability of recording various different types of business data in the block chain system is realized.

In one possible design, before the linking the first blockchain to the second blockchain to form the first subchain, the method further includes: the first management node receives a fourth block from the second management node, wherein the fourth block is generated by the second management node according to the first service data; determining that the first set of management nodes does not agree on the fourth block, the first management node discarding the fourth block.

In one possible design, after the linking the third block to the second block, the method further comprises:

A first management node receives second service data of the first service from the terminal equipment; the first management node generates a fifth block according to the second service data; wherein the fifth block includes a service identifier of the first service and a digest value of the first block; the first management node sends the fifth block to other nodes except the first management node in the first set of management nodes and the second set of management nodes;

determining that the first set of management nodes agree on the fifth block, adding the fifth block into the first sub-chain;

sending billing information for the fifth block to the second set of management nodes; wherein, the billing information of the fifth block includes the digest value of the first block and the service identifier of the first service;

the first management node receives a sixth block from the third management node; wherein the sixth block is generated by the third management node according to billing information of the fifth block;

the sixth block is linked to the third block.

In one possible design, before the receiving the third block from the third management node, the method further includes:

Receiving a verification request from a third management node; the verification request carries billing information of the first block;

verifying whether the received billing information of the first block and the billing information of the first block stored in the first sub-chain are identical;

and sending a verification result to the third management node.

receiving a fifth block from a second management node, wherein the fifth block is generated by the second management node according to second service data of the first service, and comprises a summary value of the first block and a service identifier of the first service;

determining that the first set of management nodes agree on the fifth block, linking the fifth block to the first block;

receiving a sixth block from the third management node, the sixth block generated by the third management node from accounting information of a fifth block;

the sixth block is linked to the third block.

In one possible design, the method further comprises:

Generating a seventh block according to the second service data;

transmitting the seventh block to other management nodes in the first set of management nodes except the first management node and the second set of management nodes;

determining that the first set of management nodes does not agree on the seventh block, discarding the seventh block.

In one possible design, the blocks in the first sub-chain include a branching weight for the first traffic, and the revenue for billing on the first sub-chain is related to the branching weight.

In one possible design, the blocks in the first sub-chain further include a total number of intra-block records and a time stamp, and the revenue of accounting on the first sub-chain is further related to the total number of intra-block records and the time stamp.

In a second aspect, the present application provides a method for processing service data, where the method is applied to a second management node in a blockchain system, where the blockchain system includes a first set of management nodes and a second set of management nodes, the first set of management nodes includes a first management node and a second management node, the second set of management nodes includes a third management node and a fourth management node, the first set of management nodes is used for processing service data of a first service, and the second set of management nodes is used for managing the first blockchain;

The processing method comprises the following steps:

receiving a first block from a first management node; the first block is generated by the first management node according to first service data of the first service, the first block comprises a summary value of the second block and a service identifier of the first service, the second block is a tail block in the first block chain, and the tail block is the last block in the first block chain and is also the latest block in the first block chain; the digest value represents a value obtained by using a hash algorithm, and the digest value can be called a hash value or an MD5 value;

determining that the first set of management nodes agree on the first block, linking the first block to the second block to form a first sub-chain of the first block chain;

receiving a third block from the third management node, wherein the third block is generated by the third management node according to the billing information of the first block, and the billing information of the first block comprises the abstract value of the second block and the service identifier of the first service;

the third block is linked to the second block.

In one possible design, the method further comprises:

receiving the first service data from the terminal equipment;

generating a fourth block according to the first service data;

sending the fourth block to other management nodes except the first management node in the first set of management nodes and the second set of management nodes;

determining that the first set of management nodes does not agree on the fourth block, discarding the fourth block;

receiving second service data of the first service from a terminal device;

generating a seventh block according to the second service data;

transmitting the seventh block to other management nodes except the second management node in the first set of management nodes;

determining that the first set of management nodes does not agree on the seventh block, discarding the seventh block;

receiving a fifth block from the first management node, wherein the fifth block is generated by the first management node according to the second service data;

Determining that the first set of management nodes agree on a fifth block, linking the fifth block to the first block;

receiving a sixth block from the third management node; the sixth block is generated by the third management node according to the billing information of the fifth block;

the sixth block is linked to the third block.

receiving second service data of the first service from the terminal equipment;

generating a fifth block according to the second service data; the fifth block comprises the digest value of the first block and the identification of the first service;

transmitting the fifth block to other management nodes except the second management node in the first set of management nodes;

sending billing information for the fifth block to the second set of management nodes;

receiving a sixth block from the third management node, the sixth block generated by the third management node from billing information for the fifth block;

The sixth block is linked to the third block.

In one possible design, the method further comprises:

receiving a seventh block from the first management node; the seventh block is generated by the first management node according to the second service data;

In a third aspect, the present application provides a method for processing service data, where the processing method is applied to a third management node in a blockchain system, where the blockchain system includes a first set of management nodes and a second set of management nodes, the first management node and the second management node belong to the first set of management nodes, the third management node belongs to the second set of management nodes, the first set of management nodes is used for processing service data of a first service, and the second management set is used for maintaining a consensus of the first blockchain;

the processing method comprises the following steps:

receiving a first block from the first management node, wherein the first block is generated by the first management node according to first data of the first service, the first block comprises a digest value of a second block and a service identifier of the first service, the second block is a tail block in a first block chain, and the tail block is the last block in the first block chain, is also the latest block in the first block chain, or is a block without a subsequent block in the first block chain;

Determining that the first set of management nodes agree on the first block, linking the first block to a second block to form a first sub-chain of the first block chain;

receiving billing information from a first block of the first management node; wherein the billing information of the first block includes a service identifier of the first service and a digest value of the second block; the digest value represents a value obtained by using a hash algorithm, and the digest value can be called a hash value or an MD5 value;

when the billing information of the first block is verified to be correct on the first set of management nodes, generating a third block according to the billing information of the first block, and linking the third block to the second block;

and sending the third block to other nodes except the third management node in the second set of management nodes and the first set of management nodes.

In one possible design, the method further comprises:

receiving a fourth block from the second management node; the fourth block is generated by the second management node according to the first service data;

determining that the first set of management nodes does not agree on the fourth block, discarding the fourth block.

In one possible design, after the sending the third block to the other nodes in the second set of management nodes than the third management node and the first set of management nodes, the method further includes:

receiving a fifth block from the first management node; the fifth block is generated by the first management node according to second service data of the first service;

receiving billing information for the fifth block from the first management node;

when the billing information of the fifth block is verified to be correct on the first management node set, generating a sixth block according to the billing information of the fifth block;

linking the sixth block to the third block;

In one possible design, the method further comprises:

receiving a seventh block from a second management node, the seventh block being generated by the second management node according to the second service data;

In one possible design, the verifying billing information for the fifth block on the first set of management nodes includes:

sending a verification request to a first set of management nodes; the verification request carries billing information of the fifth block, and is used for verifying whether the billing information of the fifth block stored by each management node in the first set of management nodes is the same as the billing information of the fifth block carried in the verification request or not, and sending a verification result to the third management node;

and determining whether the billing information of the fifth block is correct according to the verification result sent by each management node in the management node first set.

receiving a fifth block from the second management node; the fifth block is generated by the second management node according to second service data of the first service;

Determining that a first set of management nodes agree on the fifth block, linking the fifth block to the first block;

receiving billing information from a fifth block of the second management node; the billing information of the fifth block comprises the abstract value of the first block and the service identifier of the first service;

when the billing information of the fifth block is verified to be correct on the first set of management nodes, a sixth block is generated according to the billing information of the fifth block;

transmitting the sixth block to other management nodes except the second management node in the second set of management nodes

A sixth block is linked over the third block.

In one possible design, the method further comprises:

receiving a seventh block sent by the first management node, wherein the seventh block is generated by the first management node according to the second service data;

In a fourth aspect, the present application provides a method for processing service data, where the method is applied to a fourth management node in a blockchain system, where the blockchain system includes a first set of management nodes and a second set of management nodes, the first set of management nodes includes a first management node and a second management node, the second set of management nodes includes a third management node and a fourth management node, the first set of management nodes is used for processing service data of a first service, and the second set of management nodes is used for managing a first backbone;

The processing method comprises the following steps:

receiving a first block from a first management node; the first block is generated by a first management node according to first service data of a first service, the first block comprises a summary value of a second block and a service identifier of the first service, the second block is a chain tail block in a first block chain, and the chain tail block is the last block in the first block chain and is also the latest block in the first block chain; the digest value represents a value obtained by using a hash algorithm, and the digest value can be called a hash value or an MD5 value;

determining that the first set of management nodes agree on the first block, linking the first block to the second block;

receiving a third block from a third management node; wherein the third block is generated by the third management node according to the accounting information of the first block, and the accounting information of the first block includes the digest value of the second block and the service identifier of the first service;

the third block is linked to the second block.

In one possible design, the method further comprises:

Determining that the first set of management nodes does not agree on the third block, discarding the fourth block.

the sixth block is linked to the third block.

In one possible design, the method further comprises:

receiving a seventh block from the second management node; the seventh block is generated by the second management node according to the second service data;

determining that the first set of management nodes does not agree on the fifth block, discarding the seventh block.

the sixth block is linked to the third block.

In one possible design, the method further comprises:

In one possible design, the blocks in the first sub-chain include branching weights for the first traffic, and the revenue for billing on the first sub-chain is related to the branching weights.

In a fifth aspect, the present application provides a method for processing service data, where the processing method is applied to a terminal device, and a blockchain system includes a first set of management nodes and a second set of management nodes, where the first set of management nodes includes a first management node, the second set of management nodes includes a third management node, the first set of management nodes is used for managing a first sub-chain, and the second set of management nodes is used for managing a first blockchain;

the processing method comprises the following steps:

sending a query request to the first management node; the query request carries a service identifier, and is used for requesting to query a first block in the first sub-chain indicated by the service identifier; the first block comprises the abstract value and the service identifier of the second block;

receiving a first block sent by the first management node;

sending a verification request to the third management node; the verification request carries the service identifier, the digest value of the second block included in the first block and the height of the first block in the first sub-chain, and is used for requesting to query a second block corresponding to the first block in the first block chain, verifying whether the digest value of the second block recorded in the second block and the digest value of the second block included in the sub-chain block are the same, and sending a verification result to the terminal equipment; the digest value represents a value obtained by using a hash algorithm, and the digest value can be called a hash value or an MD5 value;

Receiving a verification result from the third management node;

and determining whether the first block is correct according to the verification result.

In a sixth aspect, the present application provides a blockchain system including a first set of management nodes, a second set of management nodes, and a third set of management nodes; the second set of management nodes comprises a third management node and a fourth management node, the first set of management nodes is used for processing the service data of the first service, the second set of management nodes is used for managing the first block chain, and the third set of management nodes is used for processing the service data of the second service;

the third management node is configured to receive a first block from an accounting node in the first set of management nodes, where the first block is generated by the accounting node in the first set of management nodes according to first service data of the first service, the first block includes a summary value of a second block and a service identifier of the first service, and the second block is a tail block in the first block chain; determining that the first set of management nodes agree on the first block, linking the first block to a second block to form a first sub-chain of the first block chain; receiving billing information from a first block of billing nodes in the first set of management nodes, the billing information for the first block including a service identification of the first service and a digest value of the second block; when the billing information of the first block is verified to be correct on the first set of management nodes, generating a third block according to the billing information of the first block, and linking the third block to the second block; broadcasting the third block to the blockchain system;

The fourth management node for receiving a first block from accounting nodes in the first set of management nodes; determining that the first set of management nodes agree on the first block, linking the first block to the second block to form a first sub-chain of the first block chain; receiving a third block from the third management node; the third block is linked to the second block.

The third management node is further configured to receive a fourth block from accounting nodes in the third set of management nodes; the fourth block is generated by an accounting node in the third set of management nodes according to the first service data of the second service; determining that the third set of management nodes agree on the fourth block, linking the fourth block to the third block to form a second sub-chain of the first block chain; receiving accounting information of a fourth block from accounting nodes in the third set of management nodes, wherein the accounting information of the fourth block comprises a service identifier of the second service and a digest value of the fourth block; when the billing information of the fourth block is verified to be correct on the third set of management nodes, generating a fifth block according to the billing information of the fourth block, and linking the fifth block to the third block; broadcasting the fifth block to the blockchain system;

The fourth management node further configured to receive the fourth block from accounting nodes in the third set of management nodes; determining that the third set of management nodes agree on the fourth block, linking the fourth block to the third block to form a second sub-chain of the first block chain; the fifth block from the third management node is received and linked to the third block.

In a seventh aspect, the present application provides an apparatus, which may implement the method for processing service data in the first to fifth aspects. The means may be, for example, a chip (e.g. a baseband chip, or a communication chip, etc.) or a management node or terminal device. The above method may be implemented by software, hardware, or by hardware executing corresponding software.

In one possible implementation, the apparatus includes a processor and a memory in its structure; the processor is configured to support the apparatus to perform corresponding functions in the communication method described above. The memory is used to couple with the processor, which holds the necessary programs (instructions) and/or data for the device. Optionally, the apparatus may further comprise a communication interface for supporting communication between the apparatus and other network elements.

In another possible implementation manner, the apparatus may include unit modules that perform corresponding actions in the above method.

In yet another possible implementation, the system includes a processor and a transceiver, the processor being coupled to the transceiver, the processor being configured to execute a computer program or instructions to control the transceiver to receive and transmit information; the processor is also adapted to implement the above-described method when the processor executes the computer program or instructions. The transceiver device may be a transceiver, a transceiver circuit, or an input/output interface. When the device is a chip, the transceiver is a transceiver circuit or an input/output interface.

When the device is a chip, the transmitting unit may be an output unit, such as an output circuit or a communication interface; the receiving unit may be an input unit such as an input circuit or a communication interface. When the apparatus is a network device, the transmitting unit may be a transmitter or a transmitter; the receiving unit may be a receiver or a receiver.

A further aspect of the present application provides a computer storage medium comprising instructions which, when run on a computer, cause the computer to perform the method according to any one of the various possible implementations of the first to fifth aspects.

A further aspect of the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method according to any of the various possible implementations of the first to fifth aspects.

Drawings

In order to more clearly describe the embodiments of the present invention or the technical solutions in the background art, the following description will describe the drawings that are required to be used in the embodiments of the present invention or the background art.

FIG. 1 is a block chain system architecture diagram according to an embodiment of the present invention;

FIG. 2 is a schematic diagram of a local ledger in a blockchain system according to an embodiment of the present invention;

FIG. 3 is a schematic diagram of a local ledger in a blockchain system according to an embodiment of the present invention;

FIG. 4 is a schematic diagram of a block on a sub-chain according to an embodiment of the present invention;

fig. 5 is a flow chart of a method for processing service data according to an embodiment of the present invention;

Fig. 6 is another flow chart of a method for processing service data according to an embodiment of the present invention;

fig. 7 is another flow chart of a method for processing service data according to an embodiment of the present invention;

fig. 8 is a flow chart of a method for processing service data according to an embodiment of the present invention;

fig. 9 to 11 are schematic diagrams of a method for processing service data according to an embodiment of the present invention;

FIG. 12 is a schematic view of an apparatus according to an embodiment of the present invention;

fig. 13 is another schematic structural view of an apparatus according to an embodiment of the present invention.

Detailed Description

Embodiments of the present invention will be described in detail below with reference to the drawings attached to the specification.

Fig. 1 is a schematic structural diagram of a blockchain system provided in the present application, where the blockchain system includes a first set of management nodes and a second set of management nodes, and the number of management nodes in the first set of management nodes and the second set of management nodes is plural. The first set of management nodes includes a first management node and a second management node, and the second set of management nodes includes a third management node and a fourth management node. Any two nodes in the block chain system can be interconnected and intercommunicated. The first set of management nodes is for processing the traffic data of the first traffic, i.e. the first set of management nodes maintains a consensus of the traffic data of the first traffic. The second set of management nodes is for maintaining a consensus of the first blockchain that does not record traffic data for the traffic. It should be noted that the number and connection relationship of the devices in the block chain system in fig. 1, the number of blocks in the local ledger, and the connection relationship between blocks are only illustrative, and the present invention is not limited thereto.

Wherein each node in the blockchain system stores an identical local ledger, for example: the first to fourth management nodes in fig. 1 each store one and the same local ledger. The local account book comprises a first blockchain and one or more sub-chains, each sub-chain is associated with one service, and different sub-chains are associated with different services, namely, each sub-chain records service data generated by the service, wherein the service data can be transaction data or service detail information, and the invention is not limited. For example: the number of first blockchain linked subchains in fig. 1 is 1 and the number of linked subchains in fig. 2 and 3 is 2. Where the number of subchains linked by the first blockchain is multiple, each subchain may be linked to a different block in the first blockchain, or multiple subchains may be linked to the same subchain in the first blockchain, as shown in fig. 2, the first subchain being linked to block 10 in the first blockchain and the second subchain being linked to block 11 in the first blockchain; as shown in FIG. 3, both the first and second sub-chains are linked to a block 11 of the first blockchain. It will be appreciated that the position of the link of the sub-chain in the first blockchain is determined by the time of the traffic data first generated by the traffic corresponding to the sub-chain.

Wherein each service manages a set of management nodes, and the management nodes in the management set participate in competition of the accounting rights of the service data and obtain a certain benefit, for example: as shown in fig. 1, the first sub-chain manages a first set of management nodes, where the management nodes in the first set of management nodes participate in competition for accounting rights for service data generated by the first service, and obtain a certain benefit when successfully competing for the accounting rights for the service data. The management nodes in the management sets corresponding to different sub-chains may overlap, that is, the same management node may exist in two management node sets, and one management node may participate in competition of accounting rights of service data of more than two services at the same time.

Wherein no traffic may be published at a certain time, then neither is the first blockchain linked to any of the sub-chains.

Wherein the first blockchain is also referred to as a backbone, the first blockchain and the backbone are used interchangeably in the following description, both of which express the same meaning. It should be noted that, in the embodiment of the present invention, the operations related to the block by the node (for example, operations of adding the block, deleting the block, etc.) all represent the operations related to the block in the local ledger by the node. The sub-chain is used to record service data generated by the associated service, and the first blockchain is used to record billing information for the blocks in the sub-chain.

As shown in fig. 4, the blocks in the sub-chain include a block header and a block header, the block header includes one or more of a parent digest value, a service identifier, a height, a random number, a Merkle root hash value, and a total number of records in a block, the parent block digest value represents a digest value of a parent block, and for a first block in the sub-chain, the parent block digest value of the first block may be a digest value of a parent block in the first block chain, or may be a Merkle root hash value of a parent block in the first block chain, as shown in fig. 2, the first block 20 in the first sub-chain, the parent block of the block 20 is the block 10 in the first block chain, and the parent block digest value of the block 20 may be a digest value of the block 10, or may be a Merkle root hash value of the block 10. The service identification represents the identity of the service associated with the sub-chain in which the block is located, and different sub-chains have different service identifications; the time stamp represents the time of recording each service data; height represents the position in the block sub-chain, for example: the height of the first block in the sub-chain is 1, and the height of the second block is 2; the total number of records in a block represents the number of service data recorded in the block, the Merkle root hash value is generated according to the service data recorded in the block, and the generation process of the Merkle root hash value can refer to the prior art and is not repeated here. In one possible implementation, the block header also includes branching weights that are used to represent weights of the sub-chains, which can be used to adjust the revenue of billing on the sub-chains.

The blocks in the first blockchain may have the same structure as the blocks in the sub-chain, in this case, since the first blockchain is not associated with any service and no service data is recorded, for the blocks in the first blockchain, the branch identifier in the block header may take a preset special value, for example: the traffic flag is 0 indicating that the block is located in the first blockchain.

Referring to fig. 5, an interaction schematic diagram of a method for processing service data according to an embodiment of the present invention is shown, where in the embodiment of the present invention, based on the network architecture of fig. 1, the method includes:

s501, the terminal equipment sends first service data to a first management node, and the first management node receives the first service data from the terminal equipment.

Specifically, the first service data is generated by the terminal device when the first service is operated, the terminal device sends the first service data to the block chain system, and each management node in the block system receives the first service data. The number of data entries included in the first service data may be one or more, and the present invention is not limited. In one possible implementation, the first business data is transaction data, and the first business data is transaction data generated for the first time by the first business. In another possible implementation manner, the first service data is service detail information of the first service, for example: the service detail information comprises a service identifier, a branch weight or other attributes of the first service; the service detail information may be generated by the terminal device when the terminal device issues the first service, or may be generated by other devices.

S502, the terminal equipment sends first service data to the second management node, and the second management node receives the first service data from the terminal equipment.

S503, the first management node generates a first block according to the first service data.

Specifically, the block body of the first block stores first service data, and the block header of the first block includes a service identifier of the first service and a parent block digest value, where the service identifier represents the service identifier of the first service. Before generating the first block, the first management node determines that a chain tail block on a first blockchain in the local ledger is a second block, a father block of the first block is the second block, and the father block digest value of the first block is the digest value of the second block.

In one possible implementation, for the second management node, the method further includes: the second management node receives first service data from the terminal equipment, the first service data is also generated by the first service, the second management node generates a fourth block according to the first service data, the second management node sends the fourth block to other management nodes in the blockchain system except for the second management node, the first set of the management nodes is requested to execute a consensus mechanism on the fourth block, the first set of the management nodes does not agree on the fourth block, and the second management node discards the fourth block.

In one possible implementation, the first block further includes a branching weight of the first service, and the benefit of billing the service data of the first service is related to the branching weight. Further, the first block further includes a total number of records in the block and a time stamp, and the benefit of billing the service data of the first service is further related to the total number of records in the block and the time stamp.

Specifically, under the traditional public chain, all nodes contend for the accounting rights of the same information, each node continuously generates block bifurcation to form consensus, and bifurcation is eliminated, so that a lot of computing resources are wasted. In the blockchain system of the embodiment of the invention, the management node can freely adjust the sub-chain of the accounting, and the distribution of the management node on the sub-chain is dynamically adjusted by adjusting the income on the sub-chain. For example: the higher the participation degree and the higher the provided income of the business with great branch weight, thereby attracting more management nodes to participate in accounting on the corresponding sub-chains, improving the difficulty of data falsification and forming the dynamic and reasonable adjustment of the distribution of computing resources.

The return of management node successfully accounting on the sub-chain is Rn (w, TPS) _n ) The parameters include: a branch weight w and a TPS of a service, wherein n represents an nth block on a sub-chain, and the greater the branch weight is, the higher the billing income is; the larger the TPS, the higher the billing benefit. The branching weights are generated when the service is released. TPS (Transaction Per Second) is the number of transactions per second, which can be calculated by the time stamp T in the block header and the total number m of records in the block on the sub-chain, and the calculation formula is TPS _n ＝m _n /(T _n -T _n-1 ). The management node records Rn (w, TPSn) obtained as described above in the block header of the generated block.

S504, the first management node broadcasts the first block.

Specifically, the first management node sends the first block to each node except the first management node in the blockchain system, and the second management node, the third management node and the fourth management node all belong to the blockchain system, so that the second management node, the third management node and the fourth management node all receive the first block of the first management node.

S505, the first set of management nodes agree on a first block.

Specifically, the first set of management nodes belongs to a blockchain system, and the first set of management nodes executes a consensus process for the first block, where the consensus process for the first block may utilize a common chain consensus algorithm commonly used at present, for example: proof of work (POW), proof of equity (POS), proof of trust (delegated proof of stake, DOS), or practical bayer fault tolerance (practical Byzantine fault tolerance, PBFT).

It should be noted that, other management nodes except the first management node in the first set of management nodes may also generate respective blocks according to the first service data, and broadcast the respective blocks to the first set of management nodes to execute the consensus process, but the first set of management nodes only agrees with the block generated by the only one management node.

S506, linking the first block to the second block.

Specifically, each management node in the blockchain links a first blockchain to a second blockchain, and for a first management node, a second management node, a third management node, and a fourth management node belonging to the blockchain system, the first management node links the first blockchain to a second blockchain in a local ledger of the first management node, the second management node links the first blockchain to a second blockchain in a local ledger of the second management node, the third management node links the first blockchain to a second blockchain in a local ledger of the third management node, and the fourth management node links the first blockchain to a second blockchain in a local ledger of the fourth management node to enable synchronous updating of the respective local ledgers in the blockchain system. The first block is linked to the second block to form a first sub-chain, and the first block is the first block of the first sub-chain. All the service data of the first service are recorded in the first sub-chain, i.e. the blocks generated according to the service data of the first service are added in the first sub-chain.

If other nodes in the blockchain system receive the fourth block from the second management node, discarding the fourth block which does not pass through the consensus, and discarding the fourth block by the first management node, the third management node and the fourth management node.

S507, the first management node sends the billing information of the first block to the third management node, and the third management node receives the billing information of the first block from the first management node.

Specifically, the first management node obtains billing information of the first block, the billing information of the first block includes a parent block digest value of the first block and a service identifier of the first service, the first management node sends the billing information of the first block to the second set of management nodes, the third management node belongs to the second set of management nodes, and the third node receives the billing information of the first block from the first management node.

S508, the first management node sends the billing information of the first block to the fourth management node, and the fourth management node receives the billing information of the first block from the first management node.

Specifically, the fourth management node belongs to the second set of management nodes, and the fourth management node receives billing information from the first block of the first management node.

S509, the third management node sends a verification request to the first management node, and the first management node receives the verification request from the third management node.

Specifically, the third management node sends a verification request to the first set of management nodes, where the verification request is used to verify whether the billing information of the first block received in S510 is correct, where the verification request may carry the billing information of the first block and the height of the first block, and the first management node and the second management node belonging to the first set of management nodes may receive the verification request from the third management node.

S510, the third management node sends a verification request to the second management node, and the second management node receives the verification request from the third management node.

S511, the second management node sends the verification result to the third management node, and the third management node receives the verification result from the second management node.

Specifically, the second management node determines a corresponding second block in the first block chain according to the height of the first block, acquires billing information of the first block in the second block, compares whether the billing information of the first block stored in the first block is consistent with the billing information of the first block in the verification request, and then sends a verification result to the third management node.

S512, the first management node sends the verification result to the third management node, and the third management node receives the verification result from the first management node.

S513, the third management node generates a third block according to the billing information of the first block.

Specifically, the third management node receives the verification results sent by each management node in the first set of management nodes, and when the verification results of all management nodes in the first set of management nodes are yes, the third management node determines that the billing information of the first block is correct.

Wherein the first blockchain may be a federation chain and the third management node is a current billing node. The second set of management nodes except the third management node do not generate blocks based on accounting information for the first block.

S514, the third management node broadcasts the third block.

Specifically, the third management node sends the third block to other management nodes except the third management node in the blockchain system, and the first management node, the second management node and the fourth management node belong to the blockchain system, and all of the first management node, the second management node and the fourth management node receive the third block from the third management node.

S515, adding the third block to the first blockchain.

Specifically, each management node in the blockchain system adds a third blockchain to the first blockchain of the local ledger, and links the third blockchain to the tail blockin the first blockchain, for example: the current tail block in the first blockchain is the second block, and the third block is linked to the second block.

In one possible implementation, when the first management node generates the fifth block according to the second service data of the first service, the fifth block that is agreed needs to be added to the first sub-chain, and the sixth block that is generated according to the accounting information of the fifth block is added to the first sub-chain, based on the network architecture of fig. 1, the specific process may refer to the steps shown in fig. 6:

S601, the terminal equipment sends second service data to the first management node, and the first management node receives the second service data from the terminal equipment.

Specifically, the second service data is generated by the terminal device when the first service is operated, the terminal device sends the second service data to the block chain system, and each management node in the block system receives the second service data. The number of data entries included in the second service data may be one or more, and the present invention is not limited. The second service data is transaction data, the second service data is generated after the first service data, and the sending time of the first service data is adjacent to the sending time of the second service data.

S602, the terminal equipment sends second service data to a second management node, and the second management node receives the second service data from the terminal equipment.

S603, the first management node generates a fifth block according to the second service data.

Specifically, the second service data is stored in the block body of the fifth block, and the block header of the fifth block includes a service identifier of the first service and a father block digest value, where the service identifier represents the service identifier of the first service, and the father block digest value is the digest value of the father block of the fifth block. Before generating the fifth block, the first management node determines a chain tail block (assumed to be the first block) on the first sub-chain in the local ledger, a parent block of the fifth block is the first block, and a parent block digest value of the fifth block is a digest value of the first block.

In one possible implementation, for the second management node, the method further includes: the second management node receives second service data from the terminal equipment, the second service data is also generated by the first service, the second management node generates a seventh block according to the second service data, the second management node sends the seventh block to other management nodes except for the second management node in the blockchain system, the first set of management nodes is requested to execute a consensus mechanism on the seventh five blocks, the seventh block is not agreed on by the first set of management nodes, and the seventh block is discarded by the second management node and other management nodes (the first management node, the third management node and the fourth management node) in the blockchain system.

In a possible implementation manner, the fifth block further includes a branching weight of the first service, and the benefit of billing the service data of the first service is related to the branching weight. Further, the fifth block further includes a total number of records in the block and a time stamp, and the benefit of billing the service data of the first service is further related to the total number of records in the block and the time stamp.

Specifically, under the traditional public chain, all nodes contend for the accounting rights of the same information, each node continuously generates block bifurcation to form consensus, and bifurcation is eliminated, so that a lot of computing resources are wasted. In the blockchain system of the embodiment of the invention, the management node can freely adjust the sub-chain of the accounting, and the distribution of the management node on the sub-chain is dynamically adjusted by adjusting the income on the sub-chain. For example: the higher the participation degree and the higher the provided income of the business with the branch weight, thereby attracting more management nodes to participate in accounting on the corresponding sub-chains, improving the difficulty of data falsification and forming the dynamic and reasonable adjustment of the distribution of the computing resources. .

The return of management node successfully accounting on the sub-chain is Rn (w, TPS) _n ) The parameters include: a branch weight w and a TPS of a service, wherein n represents an nth block on a sub-chain, and the greater the branch weight is, the higher the billing income is; the larger the TPS, the higher the billing benefit. The branching weights are generated when the service is released. TPS (Transaction Per Second) is the number of transactions per second, which can be calculated by the time stamp T in the block header and the total number m of records in the block on the sub-chain, and the calculation formula is TPS _n ＝m _n /(T _n -T _n-1 ). The management node records the obtained benefits Rn (w, TPSn) in the block header of the generated block.

S604, the first management node broadcasts a fifth block.

Specifically, the first management node sends the fifth block to each node except the first management node in the blockchain system, and the second management node, the third management node and the fourth management node all belong to the blockchain system, so that the second management node, the third management node and the fourth management node all receive the fifth block of the first management node.

S605, the first set of management nodes agree on the fifth block.

Specifically, the first set of management nodes belongs to a blockchain system, and the first set of management nodes executes a consensus process for a fifth block, where the consensus process for the fifth block may utilize a common chain consensus algorithm commonly used at present, for example: POW algorithm, POS algorithm, DOS algorithm, or PBFT algorithm.

The fifth block to achieve consensus may also be generated by a second management node in the first node of the management node, and the specific process may refer to the process of generating the fifth block by the first management node, which is not described herein.

S606, linking the fifth block to the first block.

Specifically, the first block is a tail block in the first sub-chain, each management node in the blockchain links the fifth block to the first block, for the first management node, the second management node, the third management node and the fourth management node belonging to the blockchain system, the first management node links the fifth block to the first block in the local ledger of the first management node, the second management node links the fifth block to the first block in the local ledger of the second management node, the third management node links the fifth block to the first block in the local ledger of the third management node, and the fourth management node links the fifth block to the first block in the local ledger of the fourth management node, so as to realize synchronous updating of the respective local ledgers in the blockchain system.

In one possible implementation, if the second service data is sent after the first service data, but the sending time of the first service data and the sending time of the second service data are not adjacent, the first management node needs to link the fifth block with consensus to the latest block in the first sub-chain.

S607, the first management node sends the accounting information of the fifth block to the third management node, and the third management node receives the accounting information of the fifth block from the first management node.

Specifically, the first management node obtains accounting information of a fifth block, the accounting information of the fifth block includes a father block abstract value of the fifth block and a service identifier of the first service, the first management node sends the accounting information of the fifth block to the second set of management nodes, the third management node belongs to the second set of management nodes, and the third node receives the accounting information of the fifth block from the first management node. The parent digest value of the fifth block is the digest value of the first block, which represents the value obtained by hashing the first block.

S608, the first management node sends the billing information of the fifth block to the fourth management node, and the fourth management node receives the billing information of the fifth block from the first management node.

Specifically, the fourth management node belongs to the second set of management nodes, and the fourth management node receives billing information from the fifth block of the first management node.

S609, the third management node sends a verification request to the first management node, and the first management node receives the verification request from the third management node.

Specifically, the third management node sends a verification request to the first set of management nodes, where the verification request is used to verify whether the accounting information of the fifth block received in S608 is correct, where the verification request may carry the accounting information of the fifth block and the height of the fifth block, and the first management node and the second management node belonging to the first set of management nodes receive the verification request from the third management node.

S610, the third management node sends a verification request to the second management node, and the second management node receives the verification request from the third management node.

S611, the second management node sends the verification result to the third management node, and the third management node receives the verification result from the second management node.

Specifically, the second management node determines a corresponding fifth block in the first blockchain according to the height of the fifth block, obtains accounting information of the fifth block in the fifth block, compares whether the accounting information of the fifth block stored in the fifth block is consistent with the accounting information of the fifth block in the verification request, and then sends a verification result to the third management node.

S612, the first management node sends the verification result to the third management node, and the third management node receives the verification result from the first management node.

And S613, the third management node generates a sixth block according to the billing information of the fifth block.

Specifically, the third management node receives the verification results sent by each management node in the first set of management nodes, and when the verification results of all management nodes in the first set of management nodes are yes, the third management node determines that the billing information of the fifth block is correct.

Wherein the fifth blockchain may be a federation chain and the third management node is a current billing node. The second set of management nodes except the third management node do not generate blocks according to the accounting information of the fifth block.

The current accounting node in the second set of management nodes may also be a fourth management node, and the process of generating the sixth block by the fourth management node may refer to the description of the third management node, which is not described herein.

S614, the third management node broadcasts the sixth block.

Specifically, the third management node sends the sixth block to other management nodes except the third management node in the blockchain system, and the first management node, the second management node and the fourth management node belong to the blockchain system, and all of the first management node, the second management node and the fourth management node receive the sixth block from the third management node.

S615 adds the sixth block to the first blockchain.

Specifically, each management node in the blockchain system adds a sixth blockchain to the first blockchain of the local ledger, and links the sixth blockchain to the tail blockin the first blockchain, for example: the current tail block in the first blockchain is the third block, and the sixth block is linked to the third block.

In another possible implementation, when the second management node generates the fifth block according to the second service data of the first service, the fifth block that achieves consensus needs to be added to the first sub-chain, and the sixth block generated according to the accounting information of the fifth block needs to be added to the first sub-chain, based on the network architecture of fig. 1, the specific process may refer to the steps shown in fig. 7:

s701, the terminal equipment sends second service data to the first management node, and the first management node receives the second service data from the terminal equipment.

S702, the terminal equipment sends second service data to a second management node, and the second management node receives the second service data from the terminal equipment.

S703, the second management node generates a fifth block according to the second service data.

S704, the second management node broadcasts the fifth block.

S705, the first set of management nodes agree on the fifth block.

The first management node generates a seventh block according to the second service data, the first management node broadcasts the seventh block in the blockchain system, the first management node determines that the first set of management nodes does not agree on the seventh block, and the first management node and other management nodes in the blockchain system which receive the seventh block discard the seventh block.

S706, linking the fifth block to the first block.

S707, the second management node sends the accounting information of the fifth block to the third management node, and the third management node receives the accounting information of the fifth block sent by the second management node.

S708, the second management node sends the billing information of the fifth block to the fourth management node, and the fourth management node receives the billing information of the fifth block from the second management node.

S709, the third management node sends a verification request to the second management node, and the second management node receives the verification request from the third management node.

S710, the third management node sends a verification request to the first management node, and the first management node receives the verification request from the third management node.

S711, the second management node sends the verification result to the third management node, and the third management node receives the verification result from the second management node.

S712, the first management node sends the verification result to the third management node, and the third management node receives the verification result from the first management node.

S713, the third management node generates a sixth block according to the billing information of the fifth block.

S714, the third management node broadcasts the sixth block to the blockchain system.

S715, adding the sixth block to the first blockchain.

The specific processes of S701 to S715 are different from those of S601 to S615 in fig. 6 only in that part of the execution subjects are not different, and the specific process of each step in fig. 7 may be shown in fig. 6, which is not repeated here.

Referring to fig. 8, a flow chart of a method for processing service data according to an embodiment of the present invention is provided, where in an embodiment of the present invention, based on the network architecture of fig. 1, the method includes:

s801, a terminal sends a query request to a first management node, and the first management node receives the query request from terminal equipment.

Specifically, the query request carries a service identifier and a height, the first management node determines a corresponding first sub-chain according to the service identifier, then determines a corresponding first block in the first sub-chain according to the height, the first block comprises a summary value of the second block and the service identifier, and the service identifier indicates the first sub-chain.

S802, the first management node sends the first block to the terminal equipment, and the terminal equipment receives the first block from the first management node.

S803, the terminal equipment sends a verification request to a third management node, and the third management node receives the verification request from the terminal equipment.

Specifically, the verification request carries the service identifier and the height of the first block in the first sub-chain.

S804, the third management node queries a second block corresponding to the first block in the first block chain.

Specifically, the third management node searches a second block corresponding to the first block in the first block chain according to the service identifier and the height of the first block in the sub-chain, and the second block stores billing information of the first block, wherein the billing information of the first block comprises the service identifier and a father abstract value.

S805, the third management node verifies whether the father digest value carried in the father digest value verification request recorded in the second block is the same.

S806, the third management node sends the verification result to the terminal equipment, and the terminal equipment receives the verification result from the third management node.

Specifically, if the authentication result is the same, the third management node sends the authentication result that passes the authentication to the terminal device, otherwise, sends the authentication result that does not pass the authentication.

S807, the terminal equipment verifies the first block according to the verification result.

Specifically, when receiving a verification result that passes the verification, the terminal device determines that the queried first block is correct; and the terminal equipment determines that the queried first block is wrong when receiving a verification result that the verification is not passed. The terminal device may also receive the second block from the third management node, compare whether the father digest value recorded in the second block is the same as the father digest value of the queried first block, and verify whether the queried first block is correct according to the comparison result.

By implementing the embodiment of the invention, the terminal equipment queries the service data on the sub-chain corresponding to the service, so that the service data is prevented from being queried on the whole block chain, and the retrieval efficiency of the service data is improved.

Referring to fig. 9 to 11, a process of an embodiment of the present invention is described below with reference to a specific embodiment, where the blockchain system of fig. 9 includes a management node set 1, a management node set 2, a management node set 3, and a management node set 4, the number of the management node set 1, the management node set 2, the management node set 3, and the management node set 4 is a plurality, and any two nodes in the blockchain system have capability of interconnection and interworking. Each node in the blockchain system stores an identical local ledger, the local ledger includes a main chain, a sub-chain 1, a sub-chain 2 and a sub-chain 3, the main chain includes a block 10, a block 11, a block 12 and a block 13, the sub-chain 1 includes a block 20, a block 21 and a block, the sub-chain 2 includes a block 30 and a block 31, and the sub-chain 3 includes a block 40, a block 41 and a block 42. The first block in subchain 1 is block 20, block 20 is linked to block 10, the first block in subchain 2 is block 30, block 30 is linked to block 11, the first block in subchain 3 is block 40, and block 40 is also linked to block 11. The sub-chain is used for recording business data of vehicle purchasing service, the sub-chain 2 is used for recording business data of bank loan, and the sub-chain 3 is used for recording business data of credit investigation business.

The vehicle purchase service is associated with the management node set 2, namely, each management node in the management node set 2 competes for the accounting right of the service data generated by the vehicle purchase service, and the management node with successful accounting obtains corresponding benefits. The bank loan management node set 3, namely, each node in the management node set 3 competes for the accounting right of the business data generated by the bank loan business, and the management node with successful accounting obtains corresponding benefits. And the credit investigation business management node set 4, namely the management nodes in the management node set 4 compete for the accounting rights of business data generated by credit investigation business, and the management nodes with successful accounting obtain corresponding benefits.

The accounting benefits of the sub-chain 1, the sub-chain 2 and the sub-chain 3 can be adjusted through branch weights, and different branch weights correspond to different benefits.

The process of purchasing vehicles in 4S stores by the user A through the form of loans is described in detail, and the process relates to three businesses of credit investigation business, bank loan and vehicle purchasing service.

a. Inquiring the credit record, the user A applies for loan to the bank, the bank inquires the credit record of the user A, and particularly inquires the credit record of the user A on the sub-chain 3, and the inquiring process comprises the following steps:

1. The bank terminal sends a query request to the management node 40 in the management node set 4, the query request is used for querying credit information of the user a, the query request carries a service identifier of the credit service and an identifier of the user a, and the management node 40 receives the query request and returns a block 42 comprising the credit information of the user a to the bank terminal.

2. The bank terminal receives the block 42 from the management node 40, and obtains the parent block digest value and the service identification of the block 42.

3. The bank terminal sends a verification request to the management node 10 of the management node set 1, the verification request carries the service identification of the credit investigation service, the height of the block 42 in the sub-chain 3 and the father block digest value of the block 42, the management node 10 queries the block 12 managed by the block 42 in the main chain according to the information, obtains the accounting information of the block 42 in the block 12, compares whether the father block digest value in the accounting information of the block 42 recorded in the block 12 is the same as the father block digest value in the verification request, and returns a verification result to the management bank terminal.

4. The bank terminal receives the verification result from the management node 40, and when the verification result is that the verification is passed, it indicates that the block 42 from the management node 40 is correct.

(b) As shown in fig. 10, the bank determines the process of issuing a loan to the user a according to the credit record of the user a queried in the sub-chain 3:

1. the banking terminal transmits the loan records to the management node set 3, and each management node in the management node set 3 receives the loan records from the banking terminal.

2. Each management node in the management node set 3 calculates the current transaction total number, the time stamp and the branch weight, obtains accounting benefits, broadcasts the block generated according to the loan records, and each management node in the management node set 3 contends for the accounting rights to the loan records.

3. The management node 30 in the management node set 3 generates a block 32 from the loan records, and the management node set 3 agrees with the block 32, i.e., the management node 30 competes for accounting rights to the loan records.

4. Nodes in the blocksystem link the blocks 32 to the blocks 31 in the sub-chain 2, respectively, while discarding the blocks generated by other nodes from the loan record.

5. The management node 30 transmits billing information of the block 32 to the management node set 1, and the billing information of the block 32 includes a parent block digest value of the block 31 and a service identification of the bank loan.

6. The main chain adopts a alliance chain mode to carry out accounting, the current accounting node in the management node set 1 is the management node 10, the management node 10 generates a block 14 according to the accounting information of the block 32, links the block 14 to a chain tail block (block 13) on the main chain, then broadcasts the block 14 to other nodes in the blockchain system, the other nodes in the blockchain system receive the block 14 from the management node 10, and links the block 14 to the blocks 13 of the local account books respectively so as to realize the synchronization of the local account books among the nodes in the blockchain system.

(c) As shown in fig. 11, 4S shop purchase process: the 4S store terminal queries the loan record of the user a on the sub-chain 2, determines whether the loan record of the user a is correct, and the querying process can refer to the process of querying the credit record of the user a, which is not described herein.

After the 4S point terminal determines that the loan record of the user a is correct, a vehicle-selling record is generated, the vehicle-selling record is requested to be recorded on the sub-chain 1,

the recording process comprises the following steps:

1. the 4S store terminal transmits the sales records to the management node set 2, and each management node in the management node set 2 receives the sales records from the 4S store terminal.

2. Each management node in the management node set 2 calculates the total number of current transactions, the time stamp and the branch weight, obtains accounting benefits, broadcasts the block generated according to the loan records, and each management node in the management node set 2 contends for the accounting rights to the loan records.

3. The management nodes 20 in the management node set 2 generate the block 22 from the loan records, and the management node set 2 agrees with the block 22, i.e., the management nodes 20 compete for the accounting rights to the loan records.

4. Nodes in the blocksystem link the block22 to the block21 in the sub-chain 1, respectively, while discarding the blocks generated by other nodes from the loan record.

5. Management node 20 sends accounting information for block 22 to management node set 1, the accounting information for block 22 including the parent block digest value for block 31 and the business identification for the vehicle purchase service.

6. The main chain adopts a alliance chain mode to carry out accounting, the current accounting node in the management node set 1 is the management node 10, the management node 10 generates a block 15 according to accounting information of a block 22, links the block 15 to a chain tail block (block 14) on the main chain, then broadcasts the block 15 to other nodes in the blockchain system, the other nodes in the blockchain system receive the block 15 from the management node 10, and links the block 15 to the blocks 14 of the local account books respectively so as to realize the synchronization of the local account books among the nodes in the blockchain system.

Having described the method of the embodiment of the present invention in detail, a schematic structural diagram of the apparatus of the embodiment of the present invention is provided below, and hereinafter referred to as apparatus 12, apparatus 12 includes a processing unit 1201 and a transceiver unit 1202,

embodiment one: the apparatus 12 is configured to perform the function of the first management node in the embodiments of fig. 5 to 7, and the specific principle of the apparatus 12 may refer to the description of the first management node and will not be repeated herein. .

The block chain system comprises a first set of management nodes and a second set of management nodes, wherein the first set of management nodes comprises the first management node and the second management node, and the second set of management nodes comprises a third management node and a fourth management node; the first set of management nodes is used for processing service data of a first service, and the second set of management nodes is used for managing a first block chain;

a transceiver unit 1202, configured to receive first service data of the first service.

And the processing unit 1201 is configured to generate a first block according to the first service data, where the first block includes a service identifier of the first service and a digest value of a second block, and the second block is a tail block in the first blockchain.

The transceiver 1202 is further configured to send the first block to a management node other than the first management node in the first set of management nodes and the second set of management nodes.

The processing unit 1201 is further configured to determine that the first set of management nodes agree on the first block, and link the first block to the second block to form a first sub-chain of the first block chain.

The transceiver 1202 is further configured to send accounting information of the first block to the second set of management nodes, where the accounting information of the first block includes a digest value of the second block and a service identifier of the first service.

The transceiver unit 1202 is further configured to receive a third block from the third management node, where the third block is generated by the third management node according to the accounting information of the first block.

The processing unit 1201 is further configured to link the third block to the second block.

In a possible implementation manner, the transceiver unit 1202 is further configured to receive a fourth block from the second management node, where the fourth block is generated by the second management node according to the first service data;

the processing unit 1201 is further configured to determine that the first set of management nodes does not agree on the fourth block, and discard the fourth block.

In a possible implementation manner, the transceiver unit 1202 is further configured to receive second service data of the first service.

A processing unit 1201, configured to generate a fifth block according to the second service data; wherein the fifth block includes a service identifier of the first service and a digest value of the first block.

The transceiver 1202 is further configured to send the fifth block to other nodes in the first set of management nodes except the first management node and the second set of management nodes.

The processing unit 1201 is further configured to determine that the first set of management nodes agree on the fifth block, and add the fifth block to the first sub-chain.

A transceiver unit 1202 further configured to send accounting information of the fifth block to the second set of management nodes; wherein the billing information of the fifth block includes a digest value of the first block and a service identifier of the first service.

A transceiver 1202, configured to receive a sixth block from the third management node; wherein the sixth block is generated by the third management node from the accounting information of the fifth block.

The processing unit 1201 is further configured to link the sixth block to the third block.

In a possible implementation manner, the transceiver unit 1202 is further configured to receive a verification request from the third management node; the authentication request carries billing information for the first block.

A processing unit 1201, configured to verify whether the received billing information of the first block and the billing information of the first block stored in the first sub-chain are the same;

The transceiver 1202 is further configured to send a verification result to the third management node.

In a possible implementation manner, the transceiver unit 1202 is further configured to receive a fifth block from the second management node, where the fifth block is generated by the second management node according to the second service data of the first service, and the fifth block includes a digest value of the first block and a service identifier of the first service.

The processing unit 1201 is further configured to determine that the first set of management nodes agree on the fifth block, and link the fifth block to the first block.

The transceiver unit 1202 is further configured to receive a sixth block from the third management node, where the sixth block is generated by the third management node according to the accounting information of the fifth block.

In a possible implementation manner, the processing unit 1201 is further configured to generate a seventh block according to the second service data;

the transceiver 1202 is further configured to send the seventh block to other management nodes in the first set of management nodes except the first management node and the second set of management nodes;

The processing unit 1201 is further configured to determine that the first set of management nodes does not agree on the seventh block, and discard the seventh block.

In one possible implementation, the blocks in the first sub-chain include a branching weight for the first traffic, and the revenue for billing on the first sub-chain is related to the branching weight.

In one possible implementation, the blocks in the first sub-chain further comprise a total number of intra-block records and a time stamp, and the revenue of accounting on the first sub-chain is further related to the total number of intra-block records and the time stamp.

Embodiment two: the apparatus 12 is configured to perform the functions of the second management node in fig. 5 to 7, and the specific principle of the apparatus 12 may refer to the description of the second management node, which is not repeated herein.

The system comprises a first set of management nodes and a second set of management nodes, wherein the first set of management nodes comprises a first management node and a second management node, the second set of management nodes comprises a third management node and a fourth management node, the first set of management nodes is used for processing service data of a first service, and the second set of management nodes is used for managing the first block chain;

A transceiver unit 1202 for receiving a first block from a first management node; the first block is generated by the first management node according to first service data of the first service, the first block comprises a summary value of the second block and a service identifier of the first service, and the second block is a chain tail block in the first block chain.

A processing unit 1201 is configured to determine that the first set of management nodes agree on the first block and link the first block to the second block to form a first sub-chain of the first block chain.

The transceiver 1201 is further configured to receive a third block from the third management node, where the third block is generated by the third management node according to the accounting information of the first block, and the accounting information of the first block includes the digest value of the second block and the service identifier of the first service.

In a possible design, the transceiver unit 1202 is further configured to receive the first service data from the terminal device;

The processing unit 1201 is further configured to generate a fourth block according to the first service data;

the transceiver 1202 is further configured to send the fourth block to other management nodes in the first set of management nodes except the first management node and the second set of management nodes;

a processing unit 1201, configured to determine that the first set of management nodes does not agree on the fourth block, and discard the fourth block;

in a possible design, the transceiver unit 1202 is further configured to receive second service data of the first service from a terminal device.

The processing unit 1201 is further configured to generate a seventh block according to the second service data.

The transceiver 1202 is further configured to send the seventh block to other management nodes in the first set of management nodes except the second management node and the second set of management nodes.

The transceiver 1202 is further configured to receive a fifth block from the first management node, where the fifth block is generated by the first management node according to the second service data.

The processing unit 1201 is further configured to determine that the first set of management nodes agree on a fifth block, and link the fifth block to the first block.

A transceiver 1202, configured to receive a sixth block from the third management node; the sixth block is generated by the third management node according to the billing information of the fifth block;

In a possible implementation manner, the transceiver unit 1202 is further configured to receive second service data from the first service;

a processing unit 1201, configured to generate a fifth block according to the second service data; the fifth block comprises the digest value of the first block and the identification of the first service;

the transceiver 1202 is further configured to send the fifth block to other management nodes except the second management node in the first set of management nodes and the second set of management nodes;

a processing unit 1201, further configured to determine that the first set of management nodes agree on the fifth block, and link the fifth block to the first block;

a transceiver unit 1202 further configured to send accounting information of the fifth block to the second set of management nodes;

A transceiver 1202 further configured to receive a sixth block from the third management node, where the sixth block is generated by the third management node according to the billing information of the fifth block;

In a possible implementation manner, the transceiver unit 1202 is further configured to receive a seventh block from the first management node; the seventh block is generated by the first management node according to the second service data;

In the third embodiment, the apparatus 12 is configured to perform the function of the third management node in fig. 5 to 7, and the specific principle of the apparatus 12 may refer to the description of the third management node, which is not repeated herein. .

The system comprises a first set of management nodes and a second set of management nodes, wherein the first management nodes and the second management nodes belong to the first set of management nodes, the third management nodes belong to the second set of management nodes, the first set of management nodes is used for processing service data of a first service, and the second management set is used for maintaining consensus of the first block chain;

The transceiver 1202 is configured to receive a first block from the first management node, where the first block is generated by the first management node according to first data of the first service, the first block includes a digest value of a second block and a service identifier of the first service, and the second block is a tail block in the first block chain.

A processing unit 1201 is configured to determine that the first set of management nodes agree on the first block and link the first block to a second block to form a first sub-chain of the first block chain.

A transceiver unit 1202 further configured to receive billing information from a first block of the first management node; wherein the billing information of the first block includes a service identifier of the first service and a digest value of the second block;

the processing unit 1201 is further configured to determine that the accounting information of the first block is verified to be correct on the first set of management nodes, generate a third block according to the accounting information of the first block, and link the third block to the second block;

the transceiver 1202 is further configured to send the third block to other nodes in the second set of management nodes except the third management node and the first set of management nodes.

In a possible implementation manner, the transceiver unit 1202 is further configured to receive a fourth block from the second management node; the fourth block is generated by the second management node according to the first service data;

In a possible implementation manner, the transceiver unit 1202 is further configured to receive a fifth block from the first management node; the fifth block is generated by the first management node according to second service data of the first service;

a transceiver unit 1202 further configured to receive billing information from the fifth block of the first management node;

the processing unit 1201 is further configured to determine that the accounting information of the fifth block is correct on the first management node set, and generate a sixth block according to the accounting information of the fifth block;

a transceiving unit 1202 for linking the sixth block to the third block;

In a possible implementation manner, the transceiver unit 1202 is further configured to receive a seventh block from the second management node, where the seventh block is generated by the second management node according to the second service data;

In one possible implementation, the verifying, by the processing unit 1201, the billing information of the fifth block on the first set of management nodes includes:

instructing the transceiver unit to send a verification request to a first set of management nodes; the verification request carries billing information of the fifth block, and is used for verifying whether the billing information of the fifth block stored by each management node in the first set of management nodes is the same as the billing information of the fifth block carried in the verification request or not, and sending a verification result to the third management node;

In a possible implementation manner, the transceiver unit 1202 is further configured to receive a fifth block from the second management node; the fifth block is generated by the second management node according to second service data of the first service;

a processing unit 1201, further configured to determine that a first set of management nodes agree on the fifth block, and link the fifth block to the first block;

a transceiver unit 1202 further configured to receive billing information from a fifth block of the second management node; the billing information of the fifth block comprises the abstract value of the first block and the service identifier of the first service;

the processing unit 1201 is further configured to determine that the accounting information of the fifth block is verified to be correct on the first set of management nodes, and generate a sixth block according to the accounting information of the fifth block;

a transceiver 1202 configured to send the sixth block to other management nodes in the second set of management nodes except the second management node and the second set of management nodes

The processing unit 1201 is further configured to link a sixth block to the third block.

In a possible implementation manner, the transceiver unit 1202 is further configured to receive a seventh block sent from the first management node, where the seventh block is generated by the first management node according to the second service data;

Embodiment four: the device 12 is configured to perform the function of the fourth management node in fig. 5 to 7, and the specific principle of the device 12 may refer to the description of the fourth management node, which is not repeated herein.

The block chain system comprises a first set of management nodes and a second set of management nodes, wherein the first set of management nodes comprises a first management node and a second management node, the second set of management nodes comprises a third management node and a fourth management node, the first set of management nodes is used for processing service data of a first service, and the second set of management nodes is used for managing a first main chain;

a transceiver unit 1202 for receiving a first block from a first management node; the first block is generated by a first management node according to first service data of a first service, the first block comprises a summary value of a second block and a service identifier of the first service, and the second block is a chain tail block in the first block chain;

A processing unit 1201 configured to determine that the first set of management nodes agree on the first block, and link the first block to the second block to form a first sub-chain of the first block chain;

a transceiver 1202, configured to receive a third block from the third management node; wherein the third block is generated by the third management node according to the accounting information of the first block, and the accounting information of the first block includes the digest value of the second block and the service identifier of the first service;

In a possible implementation manner, the transceiving unit 1202 is configured to receive a fourth block from the second management node; the fourth block is generated by the second management node according to the first service data;

a processing unit 1201 is configured to determine that the first set of management nodes does not agree on the third block, and discard the fourth block.

In a possible implementation manner, the transceiver unit 1202 is configured to receive a fifth block from the first management node; the fifth block is generated by the first management node according to second service data of the first service;

A processing unit 1201 configured to determine that the first set of management nodes agree on the fifth block, and link the fifth block to the first block;

a transceiver 1202 configured to receive a sixth block from the third management node; the sixth block is generated by the third management node according to the billing information of the fifth block;

a processing unit 1201 is configured to link the sixth block to the third block.

In a possible implementation manner, the transceiver unit 1202 is configured to receive a seventh block from the second management node; the seventh block is generated by the second management node according to the second service data;

the processing unit 1201 is further configured to determine that the first set of management nodes does not agree on the fifth block, and discard the seventh block.

Fifth embodiment: the apparatus 12 is configured to perform the functions of the terminal device in fig. 8, and the specific principle of the apparatus 12 may refer to the description of the terminal device in fig. 8, which is not repeated herein.

The block chain system comprises a first set of management nodes and a second set of management nodes, wherein the first set of management nodes comprises a first management node, the second set of management nodes comprises a third management node, the first set of management nodes is used for managing a first sub-chain, and the second set of management nodes is used for managing a first block chain;

A transceiver unit 1202, configured to send a query request to the first management node; the query request carries a service identifier, and is used for requesting to query a first block in the first sub-chain indicated by the service identifier, wherein the first block comprises a summary value of a second block and the service identifier;

the transceiver 1202 is further configured to receive a first block sent by the first management node;

a transceiver 1202, configured to send a verification request to the third management node; the verification request carries the service identifier, the digest value of the second block included in the first block and the height of the first block in the first sub-chain, and is used for requesting to query a second block corresponding to the first block in the first block chain, verifying whether the digest value of the second block recorded in the second block and the digest value of the second block included in the sub-chain block are the same, and sending a verification result to the terminal equipment;

a transceiver 1202, configured to receive a verification result from the third management node;

a processing unit 1201 is configured to determine whether the first block is correct according to the verification result.

The above embodiment of the apparatus only lists the logic functions between the modules, and the specific execution process and the beneficial effects refer to the corresponding method embodiments.

The device 12 may be a terminal device or a management node, or may be a field-programmable gate array (FPGA) for implementing related functions, an application-specific integrated chip, a system on chip (SoC), a central processor (central processor unit, CPU), a network processor (network processor, NP), a digital signal processing circuit, a microcontroller (micro controller unit, MCU), a programmable controller (programmable logic device, PLD) or other integrated chips.

Fig. 13 is a schematic structural diagram of an apparatus provided in an embodiment of the present invention, hereinafter referred to as apparatus 13, where the apparatus 13 may be integrated in the foregoing management node or terminal device, as shown in fig. 13, and the apparatus includes: memory 1302, processor 1301, transceiver 1303.

The memory 1302 may be a separate physical unit and may be connected to the processor 1301 and the transceiver 1303 by a bus. The memory 1302, processor 1301, transceiver 1303 may also be integrated together, implemented by hardware, etc.

The memory 1302 is used for storing a program implementing the above method embodiment, or each module of the apparatus embodiment, and the processor 1201 calls the program to perform the operations of the above method embodiment.

Alternatively, when part or all of the processing methods of service data in the above embodiments are implemented by software, the apparatus may include only the processor. The memory for storing the program is located outside the device and the processor is connected to the memory via a circuit/wire for reading and executing the program stored in the memory.

The processor may be a central processor (central processing unit, CPU), a network processor (network processor, NP) or a combination of CPU and NP.

The processor may further comprise a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (programmable logic device, PLD), or a combination thereof. The PLD may be a complex programmable logic device (complex programmable logic device, CPLD), a field-programmable gate array (field-programmable gate array, FPGA), general-purpose array logic (generic array logic, GAL), or any combination thereof.

The memory may include volatile memory (RAM), such as random-access memory (RAM); the memory may also include a nonvolatile memory (non-volatile memory), such as a flash memory (flash memory), a hard disk (HDD) or a Solid State Drive (SSD); the memory may also comprise a combination of the above types of memories.

In the above embodiments, the transmitting module or the transmitter performs the steps of transmitting the above embodiments of the method, the receiving module or the receiver performs the steps of receiving the above embodiments of the method, and other steps are performed by other modules or processors. The transmitting module and the receiving module may constitute a transceiver module, and the receiver and the transmitter may constitute a transceiver.

The embodiment of the application also provides a computer storage medium storing a computer program for executing the processing method of the service data provided by the embodiment.

The present application also provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method for processing service data provided in the above embodiments.

It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

Claims

1. The processing method of the service data is characterized in that the processing method is applied to a first management node in a blockchain system, the blockchain system comprises a first management node set and a second management node set, the first management node set comprises the first management node and the second management node, and the second management node set comprises a third management node and a fourth management node; the first set of management nodes is used for processing service data of a first service, and the second set of management nodes is used for managing a first block chain;

The processing method comprises the following steps:

receiving first service data of the first service;

generating a first block according to the first service data, wherein the first block comprises a service identifier of the first service and a digest value of a second block, and the second block is a chain tail block in the first block chain;

sending the first block to a management node other than the first management node in the first set of management nodes and the second set of management nodes;

transmitting accounting information of the first block to the second set of management nodes, wherein the accounting information of the first block comprises a summary value of the second block and a service identifier of the first service;

receiving a third block from the third management node, the third block generated by the third management node from billing information for the first block;

the third block is linked to the second block.

2. The method of claim 1, wherein before the linking the first blockchain to the second blockchain to form a first sub-chain of the first blockchain, further comprising:

Receiving a fourth block from the second management node, wherein the fourth block is generated by the second management node according to the first service data;

3. The method of claim 1 or 2, wherein after the linking the third block to the second block, further comprising:

receiving second service data of the first service;

generating a fifth block according to the second service data; wherein the fifth block includes a service identifier of the first service and a digest value of the first block;

transmitting a fifth block to other nodes except the first management node in the first set of management nodes and the second set of management nodes;

the sixth block is linked to the third block.

4. A method according to any one of claims 1 to 3, wherein prior to receiving a third block from the third management node, further comprising:

and sending a verification result to the third management node.

5. The method of claim 1 or 2, wherein after the linking the third block to the second block, further comprising:

the sixth block is linked to the third block.

6. The method as recited in claim 5, further comprising:

generating a seventh block according to the second service data;

7. The method of any of claims 1 to 6, wherein the blocks in the first sub-chain comprise branching weights for the first traffic, and wherein the revenue for accounting on the first sub-chain is related to the branching weights.

8. The method of claim 7, wherein the blocks in the first sub-chain further comprise a total number of records in a block and a time stamp, and wherein the revenue of accounting on the first sub-chain is further related to the total number of records in a block and the time stamp.

9. The processing method of the service data is characterized in that the processing method is applied to a second management node in a blockchain system, the blockchain system comprises a first management node set and a second management node set, the first management node set comprises a first management node and a second management node, the second management node set comprises a third management node and a fourth management node, the first management node set is used for processing the service data of the first service, and the second management node set is used for managing the first blockchain;

the processing method comprises the following steps:

receiving a first block from a first management node; the first block is generated by the first management node according to first service data of the first service, the first block comprises a summary value of a second block and a service identifier of the first service, and the second block is a chain tail block in the first block chain;

The third block is linked to the second block.

10. The method as recited in claim 9, further comprising:

receiving the first service data from a terminal device;

generating a fourth block according to the first service data;

11. The method of claim 9 or 10, wherein after the linking the third block to the second block, further comprising:

receiving second service data of the first service from a terminal device;

generating a seventh block according to the second service data;

the sixth block is linked to the third block.

12. The method of claim 9 or 10, wherein after the linking the third block to the second block, further comprising:

receiving second service data from the first service;

The sixth block is linked to the third block.

13. The method as recited in claim 12, further comprising:

14. The processing method of the service data is characterized in that the processing method is applied to a third management node in a blockchain system, the blockchain system comprises a first management node set and a second management node set, the first management node and the second management node belong to the first management node set, the third management node belongs to the second management node set, the first management node set is used for processing the service data of a first service, and the second management node set is used for maintaining consensus of a first blockchain;

the processing method comprises the following steps:

receiving a first block from the first management node, wherein the first block is generated by the first management node according to first data of the first service, the first block comprises a summary value of a second block and a service identifier of the first service, and the second block is a chain tail block in a first block chain;

receiving billing information from a first block of the first management node; wherein the billing information of the first block includes a service identifier of the first service and a digest value of the second block;

15. The method as recited in claim 14, further comprising:

16. The method according to claim 14 or 15, wherein after the sending the third block to the other nodes than the third management node in the second set of management nodes and the first set of management nodes, further comprises:

linking the sixth block to the third block;

17. The method as recited in claim 16, further comprising:

18. The method according to claim 16 or 17, wherein said verifying billing information for the fifth block on the management node first set comprises:

19. The method according to claim 14 or 15, wherein after the sending the third block to the other nodes than the third management node in the second set of management nodes and the first set of management nodes, further comprises:

When the fact that the billing information of the fifth block is correct is confirmed on the first set of the management nodes, a sixth block is generated according to the billing information of the fifth block;

A sixth block is linked over the third block.

20. The method as recited in claim 19, further comprising:

21. The processing method is applied to a fourth management node in a blockchain system, wherein the blockchain system comprises a first management node set and a second management node set, the first management node set comprises a first management node and a second management node, the second management node set comprises a third management node and a fourth management node, the first management node set is used for processing the business data of a first business, and the second management node set is used for managing a first main chain;

The processing method comprises the following steps:

receiving a first block from a first management node; the first block is generated by a first management node according to first service data of a first service, the first block comprises a summary value of a second block and a service identifier of the first service, and the second block is a chain tail block in the first block chain;

receiving a third block from the third management node; wherein the third block is generated by the third management node according to the accounting information of the first block, and the accounting information of the first block includes the digest value of the second block and the service identifier of the first service;

the third block is linked to the second block.

22. The method as recited in claim 21, further comprising:

23. The method of claim 21 or 22, wherein after the linking the third block to the second block, further comprising:

the sixth block is linked to the third block.

24. The method as recited in claim 23, further comprising:

25. The method of claim 21 or 22, wherein after the linking the third block to the second block, further comprising:

the sixth block is linked to the third block.

26. The method as recited in claim 25, further comprising:

27. The processing method of the service data is characterized in that the processing method is applied to terminal equipment, a block chain system comprises a first set of management nodes and a second set of management nodes, the first set of management nodes comprises a first management node, the second set of management nodes comprises a third management node, the first set of management nodes is used for managing a first sub-chain, and the second set of management nodes is used for managing a first block chain;

The processing method comprises the following steps:

sending a query request to the first management node; the query request carries a service identifier, and is used for requesting to query a first block in the first sub-chain indicated by the service identifier, wherein the first block comprises a summary value of a second block and the service identifier;

receiving a first block sent by the first management node;

sending a verification request to the third management node; the verification request carries the service identifier, the digest value of the second block included in the first block and the height of the first block in the first sub-chain, and is used for requesting to query a second block corresponding to the first block in the first block chain, verifying whether the digest value of the second block recorded in the second block and the digest value of the second block included in the sub-chain block are the same, and sending a verification result to the terminal equipment;

receiving a verification result from the third management node;

28. The management node is characterized in that the management node is a first management node, the blockchain system comprises a first set of management nodes and a second set of management nodes, the first set of management nodes comprises the first management node and the second management node, and the second set of management nodes comprises a third management node and a fourth management node; the first set of management nodes is used for processing service data of a first service, and the second set of management nodes is used for managing a first block chain;

The first management node includes:

the receiving and transmitting unit is used for receiving first service data of the first service;

the processing unit is used for generating a first block according to the first service data, wherein the first block comprises a service identifier of the first service and a digest value of a second block, and the second block is a chain tail block in the first block chain;

the transceiver unit is further configured to send the first block to a management node other than the first management node in the first set of management nodes and the second set of management nodes;

the processing unit is further configured to determine that the first set of management nodes agree on the first block, and link the first block to the second block to form a first sub-chain of the first block chain;

the transceiver unit is further configured to send accounting information of the first block to the second set of management nodes, where the accounting information of the first block includes a digest value of the second block and a service identifier of the first service;

the transceiver unit is further configured to receive a third block from the third management node, where the third block is generated by the third management node according to the accounting information of the first block;

The processing unit is further configured to link the third block to the second block.

29. The management node of claim 28, wherein,

the transceiver unit is further configured to receive a fourth block from the second management node, where the fourth block is generated by the second management node according to the first service data;

the processing unit is further configured to determine that the first set of management nodes does not agree on the fourth block, and discard the fourth block.

30. The management node according to claim 28 or 29, characterized in that,

the receiving and transmitting unit is further used for receiving second service data of the first service;

the processing unit is further configured to generate a fifth block according to the second service data; wherein the fifth block includes a service identifier of the first service and a digest value of the first block;

the receiving and transmitting unit is further configured to send a fifth block to other nodes in the first set of management nodes except the first management node and the second set of management nodes;

the processing unit is further configured to determine that the first set of management nodes agrees with the fifth block, and add the fifth block to the first sub-chain;

The transceiver unit is further configured to send accounting information of the fifth block to the second set of management nodes; wherein, the billing information of the fifth block includes the digest value of the first block and the service identifier of the first service;

the receiving and transmitting unit is further configured to receive a sixth block from the third management node; wherein the sixth block is generated by the third management node according to billing information of the fifth block;

the processing unit is further configured to link the sixth block to the third block.

31. The management node according to any of the claims 28 to 30, characterized in that,

the receiving and transmitting unit is further used for receiving a verification request from the third management node; the verification request carries billing information of the first block;

the processing unit is further configured to verify whether the received accounting information of the first block and the accounting information of the first block stored in the first sub-chain are the same;

the receiving and transmitting unit is further configured to send a verification result to the third management node.

32. The management node according to claim 28 or 29, characterized in that,

The transceiver unit is further configured to receive a fifth block from a second management node, where the fifth block is generated by the second management node according to second service data of the first service, and the fifth block includes a digest value of the first block and a service identifier of the first service;

the processing unit is further configured to determine that the first set of management nodes agree on the fifth block, and link the fifth block to the first block;

the transceiver unit is further configured to receive a sixth block from the third management node, where the sixth block is generated by the third management node according to the accounting information of the fifth block;

33. The management node of claim 32, wherein,

the processing unit is further configured to generate a seventh block according to the second service data;

the transceiver unit is further configured to send the seventh block to other management nodes in the first set of management nodes except the first management node and the second set of management nodes;

the processing unit is further configured to determine that the first set of management nodes does not agree on the seventh block, and discard the seventh block.

34. The management node according to any of the claims 28 to 33, wherein the blocks in the first sub-chain comprise a branching weight of the first traffic, and wherein the revenue of billing on the first sub-chain is related to the branching weight.

35. The management node of claim 34, wherein the blocks in the first sub-chain further comprise a total number of records in a block and a time stamp, and wherein the revenue for accounting on the first sub-chain is further related to the total number of records in a block and the time stamp.

36. The management node is characterized by comprising a second management node, a first set of block chain system package management nodes and a second set of management nodes, wherein the first set of management nodes comprises a first management node and a second management node, the second set of management nodes comprises a third management node and a fourth management node, the first set of management nodes is used for processing service data of a first service, and the second set of management nodes is used for managing a first block chain;

the second management node includes:

the receiving and transmitting unit is used for receiving the first block from the first management node; the first block is generated by the first management node according to first service data of the first service, the first block comprises a summary value of a second block and a service identifier of the first service, and the second block is a chain tail block in the first block chain;

A processing unit for determining that the first set of management nodes agree on the first block, linking the first block to the second block to form a first sub-chain of the first block chain;

the transceiver unit is further configured to receive a third block from the third management node, where the third block is generated by the third management node according to billing information of the first block, and the billing information of the first block includes a digest value of the second block and a service identifier of the first service;

37. The management node of claim 36, wherein,

the receiving and transmitting unit is further configured to receive the first service data from the terminal device;

the processing unit is further configured to generate a fourth block according to the first service data;

the transceiver unit is further configured to send the fourth block to other management nodes in the first set of management nodes except the first management node and the second set of management nodes;

38. The management node according to claim 36 or 37, characterized in that,

the receiving and transmitting unit is further used for receiving second service data of the first service from the terminal equipment;

the transceiver unit is further configured to send the seventh block to other management nodes except the second management node in the first set of management nodes and the second set of management nodes;

the processing unit is further configured to determine that the first set of management nodes does not agree on the seventh block, and discard the seventh block;

the transceiver unit is further configured to receive a fifth block from the first management node, where the fifth block is generated by the first management node according to the second service data;

the processing unit is further configured to determine that the first set of management nodes agree on a fifth block, and link the fifth block to the first block;

the receiving and transmitting unit is further configured to receive a sixth block from the third management node; the sixth block is generated by the third management node according to the billing information of the fifth block;

The sixth block is linked to the third block.

39. The management node according to claim 36 or 37, characterized in that,

the receiving and transmitting unit is further used for receiving second service data from the first service;

the processing unit is further configured to generate a fifth block according to the second service data; the fifth block comprises the digest value of the first block and the identification of the first service;

the transceiver unit is further configured to send the fifth block to other management nodes except the second management node in the first set of management nodes and the second set of management nodes;

the transceiver unit is further configured to send accounting information of the fifth block to the second set of management nodes;

40. The management node of claim 38, wherein,

the receiving and transmitting unit is further configured to receive a seventh block from the first management node; the seventh block is generated by the first management node according to the second service data;

41. The management node is characterized by comprising a third management node, wherein the block chain system comprises a first management node set and a second management node set, the first management node and the second management node belong to the first management node set, the third management node belongs to the second management node set, the first management node set is used for processing service data of a first service, and the second management node set is used for maintaining consensus of a first block chain;

the third management node includes:

the receiving and transmitting unit is used for receiving a first block from the first management node, the first block is generated by the first management node according to first data of the first service, the first block comprises a summary value of a second block and a service identifier of the first service, and the second block is a chain tail block in the first block chain;

A processing unit for determining that the first set of management nodes agree on the first block, linking the first block to a second block to form a first sub-chain of the first block chain;

the receiving and transmitting unit is further configured to receive accounting information from a first block of the first management node; wherein the billing information of the first block includes a service identifier of the first service and a digest value of the second block;

the processing unit is further configured to determine that billing information of the first block is verified to be correct on the first set of management nodes, generate a third block according to the billing information of the first block, and link the third block to the second block;

the transceiver unit is further configured to send the third block to other nodes in the second set of management nodes except the third management node and the first set of management nodes.

42. The management node of claim 41, wherein,

the receiving and transmitting unit is further used for receiving a fourth block from the second management node; the fourth block is generated by the second management node according to the first service data;

43. The management node of claim 41 or 42, wherein,

the receiving and transmitting unit is further configured to receive a fifth block from the first management node; the fifth block is generated by the first management node according to second service data of the first service;

the receiving and transmitting unit is further configured to receive billing information of the fifth block from the first management node;

the processing unit is further configured to determine that the accounting information of the fifth block is verified to be correct on the first management node set, and generate a sixth block according to the accounting information of the fifth block;

the transceiving unit is further used for linking the sixth block to the third block;

44. The management node of claim 43, wherein,

the transceiver unit is further configured to receive a seventh block from a second management node, where the seventh block is generated by the second management node according to the second service data;

45. The management node of claim 43 or 44, wherein the processing unit verifying billing information for the fifth zone on the management node first set comprises:

46. The management node of claim 41 or 42, wherein,

the receiving and transmitting unit is further configured to receive a fifth block from the second management node; the fifth block is generated by the second management node according to second service data of the first service;

the processing unit is further configured to determine that a first set of management nodes agree on the fifth block, and link the fifth block to the first block;

the receiving and transmitting unit is further configured to receive billing information from a fifth block of the second management node; the billing information of the fifth block comprises the abstract value of the first block and the service identifier of the first service;

the processing unit is further configured to determine that the accounting information of the fifth block is verified to be correct on the first set of management nodes, and generate a sixth block according to the accounting information of the fifth block;

the transceiver unit is further configured to send the sixth block to other management nodes in the second set of management nodes except the second management node and the second set of management nodes

The processing unit is further configured to link a sixth block to the third block.

47. The management node of claim 46, wherein,

the transceiver unit is further configured to receive a seventh block sent from the first management node, where the seventh block is generated by the first management node according to the second service data;

48. The management node is characterized in that the management node is a fourth management node, the blockchain system comprises a first management node set and a second management node set, the first management node set comprises a first management node and a second management node, the second management node set comprises a third management node and a fourth management node, the first management node set is used for processing service data of a first service, and the second management node set is used for managing a first main chain;

the fourth management node comprises:

the receiving and transmitting unit is used for receiving the first block from the first management node; the first block is generated by a first management node according to first service data of a first service, the first block comprises a summary value of a second block and a service identifier of the first service, and the second block is a chain tail block in the first block chain;

the receiving and transmitting unit is further configured to receive a third block from the third management node; wherein the third block is generated by the third management node according to the accounting information of the first block, and the accounting information of the first block includes the digest value of the second block and the service identifier of the first service;

49. The management node of claim 48, wherein,

the receiving and transmitting unit is used for receiving a fourth block from the second management node; the fourth block is generated by the second management node according to the first service data;

and the processing unit is used for determining that the first set of management nodes does not agree on the third block and discarding the fourth block.

50. The management node of claim 48 or 49, wherein,

the receiving and transmitting unit is used for receiving a fifth block from the first management node; the fifth block is generated by the first management node according to second service data of the first service;

The processing unit is configured to determine that the first set of management nodes agree on the fifth block, and link the fifth block to the first block;

the receiving and transmitting unit is configured to receive a sixth block from the third management node; the sixth block is generated by the third management node according to the billing information of the fifth block;

the processing unit is configured to link the sixth block to the third block.

51. The management node of claim 50, wherein,

the receiving and transmitting unit is used for receiving a seventh block from the second management node; the seventh block is generated by the second management node according to the second service data;

the processing unit is further configured to determine that the first set of management nodes does not agree on the fifth block, and discard the seventh block.

52. The management node of claim 48 or 49, wherein,

53. The management node of claim 52, wherein,

54. The terminal equipment is characterized in that the blockchain system comprises a first set of management nodes and a second set of management nodes, wherein the first set of management nodes comprises a first management node, the second set of management nodes comprises a third management node, the first set of management nodes is used for managing a first sub-chain, and the second set of management nodes is used for managing a first blockchain;

The terminal device includes:

the receiving and transmitting unit is used for sending a query request to the first management node; the query request carries a service identifier, and is used for requesting to query a first block in the first sub-chain indicated by the service identifier, wherein the first block comprises a summary value of a second block and the service identifier;

the receiving and transmitting unit is further configured to receive a first block sent by the first management node;

the receiving and transmitting unit is further configured to send a verification request to the third management node; the verification request carries the service identifier, the digest value of the second block included in the first block and the height of the first block in the first sub-chain, and is used for requesting to query a second block corresponding to the first block in the first block chain, verifying whether the digest value of the second block recorded in the second block and the digest value of the second block included in the sub-chain block are the same, and sending a verification result to the terminal equipment;

the receiving and transmitting unit is further used for receiving a verification result from the third management node;

And the processing unit is used for determining whether the first block is correct or not according to the verification result.

55. A blockchain system, wherein the blockchain system includes a first set of management nodes, a second set of management nodes, and a third set of management nodes; the second set of management nodes comprises a third management node and a fourth management node, the first set of management nodes is used for processing the service data of the first service, the second set of management nodes is used for managing the first block chain, and the third set of management nodes is used for processing the service data of the second service;

The fourth management node for receiving a first block from accounting nodes in the first set of management nodes; determining that the first set of management nodes agree on the first block, linking the first block to the second block to form a first sub-chain of the first block chain; receiving a third block from the third management node; linking the third block to the second block;