Data management method and apparatus for blockchain system, medium, and electronic device

Patent metadata

Field	Value
Publication number	US-11968294-B2
Application number	US-202117148258-A
Country	US
Kind code	B2
Filing date	Jan 13, 2021
Priority date	Dec 7, 2018
Publication date	Apr 23, 2024
Grant date	Apr 23, 2024

Abstract

This application provide a data management method for a blockchain system, a medium, and an electronic device. The system includes an accounting node sub-network and a service node sub-network. The method includes: adding, after an accounting node generates a first data block, first key information used for verifying a block header of a second data block generated after the first data block to a block header of the first data block; generating a signature corresponding to the first data block, and adding the signature corresponding to the first data block to the block header of the first data block; and releasing the block header of the first data block to the service node sub-network, to cause a service node to verify the signature included in the block header of the first data block, and obtaining the first key information after a successful verification to verify the block header of the second data block.

First claim

What is claimed is:

1. A data management method for a blockchain system, the blockchain system comprising an accounting node sub-network and a service node sub-network, the accounting node sub-network comprising an accounting node, and the service node sub-network comprising a service node; and the data management method comprising:
adding, after the accounting node in the accounting node sub-network generates a first data block, first key information used for verifying a block header of a second data block generated after the first data block to a block header of the first data block, wherein:
in a case that the first key information is different from key information used for verifying the block header of the first data block, the first key information is added into a designated field in the block header of the first data block to instruct the service node to verify the block header of the second data block through the first key information, and
in a case that the first key information is the same as the key information used for verifying the block header of the first data block, the designated field is set to null to instruct the service node to verify the block header of the second data block through the first key information;

generating a signature corresponding to the first key information of the first data block, and adding the signature corresponding to the first key information of the first data block to the block header of the first data block; and
releasing the block header of the first data block to the service node sub-network, wherein the service node in the service node sub-network is configured to verify the signature comprised in the block header of the first data block, and to obtain the first key information after a successful verification to verify the block header of the second data block.

2. The data management method for a blockchain system according to claim 1 , wherein before the adding first key information used for verifying a block header of a second data block generated after the first data block to a block header of the first data block, the data management method further comprises:
obtaining a certificate corresponding to the second data block from a certificate authority, and using the obtained certificate as the first key information; and/or
obtaining a public key and a private key corresponding to the second data block from the certificate authority, and using the obtained public key as the first key information.

3. The data management method for a blockchain system according to claim 1 , wherein the generating a signature corresponding to the first data block comprises:
obtaining a signature key corresponding to the first data block; and
implementing a signature algorithm on data comprised in the first data block by using the signature key corresponding to the first data block, to generate the signature corresponding to the first data block.

4. The data management method for a blockchain system according to claim 1 , wherein after the releasing the block header of the first data block to the service node sub-network, the data management method further comprises:
generating, in a case that the accounting node in the accounting node sub-network generates the second data block, a signature corresponding to the second data block through a signature key corresponding to the first key information and the second data block; and
adding the signature corresponding to the second data block to the block header of the second data block, and releasing the block header of the second data block to the service node sub-network.

5. The data management method for a blockchain system according to claim 1 , further comprising:
obtaining, in a case that an obtaining request of a target service node in the service node sub-network for transaction data comprised in a designated data block is received, permission information of the target service node; and
returning, according to the permission information of the target service node, transaction data that the target service node is permitted to obtain and that is comprised in the designated data block to the target service node.

6. An electronic device for implementing a data management method for a blockchain system, the blockchain system comprising an accounting node sub-network and a service node sub-network, the accounting node sub-network comprising an accounting node, and the service node sub-network comprising a service node, the electronic device comprising:
a non-transitory memory having one or more instructions stored thereon; and
at least one hardware-based processor operatively coupled to the non-transitory memory, and configured to execute the one or more instructions to perform a plurality of operations including:
adding, after the accounting node in the accounting node sub-network generates a first data block, first key information used for verifying a block header of a second data block generated after the first data block to a block header of the first data block, wherein:
in a case that the first key information is different from key information used for verifying the block header of the first data block, the first key information is added into a designated field in the block header of the first data block to instruct the service node to verify the block header of the second data block through the first key information, and
in a case that the first key information is the same as the key information used for verifying the block header of the first data block, the designated field is set to null to instruct the service node to verify the block header of the second data block through the first key information;

generating a signature corresponding to the first key information of the first data block, and adding the signature corresponding to the first key information of the first data block to the block header of the first data block; and
releasing the block header of the first data block to the service node sub-network, wherein the service node in the service node sub-network is configured to verify the signature comprised in the block header of the first data block, and to obtain the first key information after a successful verification to verify the block header of the second data block.

7. The electronic device according to claim 6 , wherein before the adding first key information used for verifying a block header of a second data block generated after the first data block to a block header of the first data block, the plurality of operations further comprise:
obtaining a certificate corresponding to the second data block from a certificate authority, and using the obtained certificate as the first key information; and/or
obtaining a public key and a private key corresponding to the second data block from the certificate authority, and using the obtained public key as the first key information.

8. The electronic device according to claim 6 , wherein the generating a signature corresponding to the first data block comprises:
obtaining a signature key corresponding to the first data block; and
implementing a signature algorithm on data comprised in the first data block by using the signature key corresponding to the first data block, to generate the signature corresponding to the first data block.

9. The electronic device according to claim 6 , wherein after the releasing the block header of the first data block to the service node sub-network, the plurality of operations further comprise:
generating, in a case that the accounting node in the accounting node sub-network generates the second data block, a signature corresponding to the second data block through a signature key corresponding to the first key information and the second data

Assignees

• Tencent Tech Shenzhen Co Ltd

Inventors

• Li Maocai
• Wang Zongyou
• Kong Li
• Zhou Kaiban
• Lan Hu
• Shi Yifang
• Yang Changqing
• Zhang Jinsong
• Ding Yong
• Zhu Gengliang
• Liu Qucheng
• Chen Qiuping

Classifications

• H04L9/083 Primary

  involving central third party, e.g. key distribution center [KDC] or trusted third party [TTP] · CPC title

• H04L9/0825

  using asymmetric-key encryption or public key infrastructure [PKI], e.g. key signature or public key certificates · CPC title

• H04L9/50

  using hash chains, e.g. blockchains or hash trees · CPC title

• H04L63/08 Primary

  for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32) · CPC title

• H04L9/3239 Primary

  involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD · CPC title