System and method for a blockchain based automated certifiable workflow process
US-2020028691-A1 · Jan 23, 2020 · US
US10958438B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10958438-B2 |
| Application number | US-202015931909-A |
| Country | US |
| Kind code | B2 |
| Filing date | May 14, 2020 |
| Priority date | Oct 31, 2018 |
| Publication date | Mar 23, 2021 |
| Grant date | Mar 23, 2021 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A method for blockchain-based data verification is provided. The method includes: obtaining target data submitted by a data submitter, wherein a first data digest of the target data is recorded in a blockchain; computing a second data digest of the target data; determining whether the second data digest matches the first data digest of the target data recorded in the blockchain; and determining that the target data submitted by the data submitter is valid in response to determining that the second data digest matches the first data digest of the target data recorded in the blockchain.
Opening claim text (preview).
What is claimed is: 1. A method, comprising: capturing, at a device, a data stream, wherein the data stream comprises a video stream or an audio stream; applying, at the device, a hash algorithm to each of a plurality of fragments of the data stream to respectively generate a plurality of hash values, each of the hash values corresponding to one of the plurality of fragments; obtaining, at the device, an acquisition timestamp of each of the fragments; recording description data of each of the fragments of the data stream; for each of the hash values, digitally signing as a whole, in a trusted execution environment (TEE) of the device, the hash value and the description data of the fragment corresponding to the hash value by using a private key stored in the TEE to generate a signature; generating, at the device, a plurality of blockchain transactions each comprising a respective one of the hash values and the description data of the fragment corresponding to the respective one of the hash values, the signature generated from digitally signing the hash value and the description data of the fragment corresponding to the hash value, and the acquisition timestamp of the fragment associated with the hash value of the blockchain transaction; and transmitting, by the device, the plurality of blockchain transactions to a blockchain network for consensus verification of the plurality of blockchain transactions and storage of the plurality of hash values and the description data of the fragments corresponding to the hash values, to a blockchain on the blockchain network. 2. The method of claim 1 , before digitally signing each of the hash values, further comprising: obtaining, at the device, identity information input by a user of the device; and determining, at the device, if a private key associated with the identity information is stored in the TEE. 3. The method of claim 2 , further comprising: in response to determining that there is no private key associated with the identity information: authenticating, at the device, the user based on the identity information; invoking, at the device, a key generating algorithm in the TEE to generate a private key associated with the user; and storing the private key, the identity information of the user, and an association relationship between the private key and the identity information of the user in the TEE. 4. The method of claim 1 , further comprising: obtaining, at the device, an acquisition location of each of the fragments, wherein each of the blockchain transactions further comprises the acquisition location of the fragment associated with the hash value of the blockchain transaction. 5. The method of claim 1 , further comprising: receiving, at the device, a notification message from a node on the blockchain network, the notification message identifying a location on the blockchain where a hash value associated with one of the transactions is stored. 6. The method of claim 1 , wherein the plurality of fragments are captured in a chronological order, wherein submitting the transactions to the blockchain network comprises: submitting the plurality of transactions to the blockchain network such that the plurality of hash values are stored on the blockchain in the chronological order. 7. The method of claim 1 , further comprising: storing in the TEE, at the device, device authentication information signed by a private key associated with a manufacturer of the device; obtaining, at the device, a public key corresponding to the private key associated with the manufacturer; and prior to digitally signing each of the hash values, verifying, at the device, based on the public key, a signature of the device authentication information to determine that the device is valid. 8. A device comprising: one or more processors and one or more non-transitory computer-readable mediums coupled to the one or more processors and configured with instructions executable by the one or more processors to cause the device to perform operations comprising: capturing a data stream, wherein the data stream comprises a video stream or an audio stream; applying a hash algorithm to each of a plurality of fragments of the data stream to respectively generate a plurality of hash values, each of the hash values corresponding to one of the plurality of fragments; and obtaining an acquisition timestamp of each of the fragments; recording description data of each of the fragments of the data stream; for each of the hash values, digitally signing as a whole, in a trusted execution environment (TEE) of the device, the hash value and the description data of the fragment corresponding to the hash value by using a private key stored in the TEE to generate a signature; generating a plurality of blockchain transactions each comprising a respective one of the hash values and the description data of the fragment corresponding to the respective one of the hash values, the signature generated from digitally signing the hash value and the description data of the fragments corresponding to the hash values, and the acquisition timestamp of the fragment associated with the hash value of the blockchain transaction; and transmitting the plurality of blockchain transactions to a blockchain network for consensus verification of the plurality of blockchain transactions and storage of the plurality of hash values and the description data of the fragment corresponding to the hash value, to a blockchain on the blockchain network. 9. The device of claim 8 , wherein the operations further comprise: before digitally signing each of the hash values: obtaining identity information input by a user of the device; and determining if a private key associated with the identity information is stored in the TEE. 10. The device of claim 9 , wherein the operations further comprise: in response to determining that there is no private key associated with the identity information: authenticating the user based on the identity information; invoking a key generating algorithm in the TEE to generate a private key associated with the user; and storing the private key, the identity information of the user, and an association relationship between the private key and the identity information of the user in the TEE. 11. The device of claim 8 , wherein the operations further comprise: obtaining an acquisition location of each of the fragments, wherein each of the blockchain transactions further comprises the acquisition location of the fragment associated with the hash value of the blockchain transaction. 12. The device of claim 8 , wherein the operations further comprise: receiving a notification message from a node on the blockchain network, the notification message identifying a location on the blockchain where a hash value associated with one of the transactions is stored. 13. The device of claim 8 , wherein the plurality of fragments are captured in a chronological order, wherein submitting the transactions to the blockchain network comprises: submitting the plurality of transactions to the blockchain network such that the plurality of hash values are stored on the blockchain in the chronological order. 14. The device of claim 8 , wherein the operations further comprise: storing in the TEE device authentication information signed by a private key associated with a manufacturer of the device; obtaining a public key corresponding to the private key associated with the manufacturer; and prior to digitally signing each of the hash values, verifying, based on the public key, a signature of the device authentication information to determine that the d
using hash chains, e.g. blockchains or hash trees · CPC title
for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS] · CPC title
Applying verification of the received information (cryptographic mechanisms or cryptographic arrangements for data integrity or data verification H04L9/32) · CPC title
Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor · CPC title
involving key management · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.