CN112182009B - Block chain data updating method and device and readable storage medium - Google Patents
Block chain data updating method and device and readable storage medium Download PDFInfo
- Publication number
- CN112182009B CN112182009B CN202011167416.4A CN202011167416A CN112182009B CN 112182009 B CN112182009 B CN 112182009B CN 202011167416 A CN202011167416 A CN 202011167416A CN 112182009 B CN112182009 B CN 112182009B
- Authority
- CN
- China
- Prior art keywords
- data
- record
- updated
- validity
- uplink
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 57
- 238000012545 processing Methods 0.000 claims description 35
- 238000004590 computer program Methods 0.000 claims description 3
- 238000012795 verification Methods 0.000 abstract description 75
- 230000008569 process Effects 0.000 description 13
- 238000010586 diagram Methods 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 238000004891 communication Methods 0.000 description 3
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000013524 data verification Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000008014 freezing Effects 0.000 description 1
- 238000007710 freezing Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000010200 validation analysis Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/602—Providing cryptographic facilities or services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/64—Protecting data integrity, e.g. using checksums, certificates or signatures
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Databases & Information Systems (AREA)
- General Health & Medical Sciences (AREA)
- Computer Hardware Design (AREA)
- Software Systems (AREA)
- Health & Medical Sciences (AREA)
- Bioethics (AREA)
- Data Mining & Analysis (AREA)
- Computing Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application provides a data updating method and device of a blockchain and a readable storage medium. A method of data update for a blockchain, comprising: receiving an acquisition request of data to be updated; the acquisition request comprises identity information of a user; acquiring the data to be updated from a blockchain according to the identity information of the user; acquiring unique Identity (ID) data of the data to be updated; the unique identity ID data comprises an application data type to which the data to be updated belongs, a hash value of a first record of the data to be updated on the block chain and a hash value of a previous record of the data to be updated on the block chain; verifying whether the data to be updated is unique data or not according to the unique identity ID data; and feeding back the data to be updated when the data to be updated is determined to be the unique data. The method is used for realizing the uniqueness verification of the data, the verification of the validity and the track tracking of the data.
Description
Technical Field
The present application relates to the field of blockchain technologies, and in particular, to a method and an apparatus for updating blockchain data, and a readable storage medium.
Background
In a blockchain application system, some public data is usually uplinked, and in the life cycle of the application system, the public data needs to be updated along with the time, and the characteristics of the blockchain system determine that the uplinked data cannot be updated, so that the original uplinked data needs to be downloaded locally first, and then the updated data corresponding to the original uplinked data is used as new data to be uplinked again. When a user obtains public data through the block chain application system, the system obtains the data updated by the user on the chain last time according to the user information.
In the prior art, data to be updated on a chain is obtained through a Hash (Hash) address of the data on the chain. However, through the hash address, only the corresponding data can be obtained, but the unique identity of the data on the chain cannot be verified, and whether the data conflicts with other data on the chain cannot be determined; nor is it possible to determine whether the data on the chain is the last updated data.
Disclosure of Invention
An object of the embodiments of the present application is to provide a method and apparatus for updating data of a blockchain, and a readable storage medium, so as to implement unique verification of data on the blockchain.
In a first aspect, an embodiment of the present application provides a method for updating data of a blockchain, including: receiving an acquisition request of data to be updated; the acquisition request comprises identity information of a user; acquiring the data to be updated from a blockchain according to the identity information of the user; acquiring unique Identity (ID) data of the data to be updated; the unique identity ID data comprises an application data type to which the data to be updated belongs, a hash value of a first record of the data to be updated on the block chain and a hash value of a previous record of the data to be updated on the block chain; verifying whether the data to be updated is unique data or not according to the unique identity ID data; and feeding back the data to be updated when the data to be updated is determined to be the unique data.
In the embodiment of the application, compared with the prior art, when acquiring the data on the chain, firstly acquiring the data to be updated according to the identity information of the user, and then acquiring the unique identity ID (Identity document, identity identification) data of the data to be updated, wherein the data comprises an application data type to which the data to be updated belongs, a hash value of a first record of the data to be updated on the block chain and a hash value of a previous record of the data to be updated on the block chain; the application data category to which the data belongs can determine the category to which the data belongs, and the data in the blockchain can be distinguished through the data category, so that whether the category to which the data belongs is a unique category or not can be determined; the hash value of the first record and the previous record of the data on the blockchain can be used for determining the historical record data corresponding to the data to be updated, for example: finding a previous record through the hash value of the previous record of the data to be updated, and tracking the previous record in sequence according to the hash value of the previous record in the unique identity ID data of the previous record, so as to realize the determination of the history record data (whether the data is the latest updated data or not, and play the role of the identification of the current record and the history record). The data can be verified based on the unique identity ID data, and whether the data is the latest updated data or not can be determined, so that the data can be updated effectively and accurately.
As a possible implementation manner, after the data to be updated is fed back when the data to be updated is determined to be unique data, the method further includes: acquiring data to be uplink; the data to be uplink is data obtained after updating the data to be updated; generating unique Identity (ID) data of the data to be uplink; and carrying out uplink processing on the data to be uplink according to the unique Identity (ID) data of the data to be uplink.
In the embodiment of the application, after the data to be updated is fed back, the user performs data uplink based on the data to be updated, and generates unique Identity (ID) data for the data when the data is uplink, so that the data can be subjected to data uniqueness verification when the data is acquired or applied later, and the current record and the history record can be identified.
As a possible implementation manner, before the uplink processing is performed on the data to be uplink according to the unique ID data of the data to be uplink, the method further includes: acquiring first validity data of the data to be uplink; the first validity data is signature data of an uploading user of the data to be uplink; signing the unique Identity (ID) data of the data to be uplink to obtain second validity data; correspondingly, the uplink processing of the data to be uplink according to the unique identity ID data of the data to be uplink includes: and carrying out uplink processing on the data to be uplink according to the unique Identity (ID) data of the data to be uplink, the first validity data and the second validity data.
In the implementation of the method, when the data are uplink, the validity data of the uplink data are generated through the signature data, and then the uplink is performed based on the validity data and the unique identity ID data, so that when the data are acquired subsequently, the uniqueness of the data can be verified, the validity of the data can be verified based on the validity data, and the safety and the reliability of the data on the link are ensured.
As a possible implementation manner, before signing the unique ID data of the data to be uplink to obtain second validity data, the method further includes: acquiring attribute information of the data to be uplink; the attribute information comprises a record number and generation time of the data to be uplink; correspondingly, the signing the unique identity ID data of the data to be uplink to obtain second validity data includes: and signing the unique Identity (ID) data of the data to be uplink and the attribute information to obtain the second validity data.
In the embodiment of the application, when signing the on-chain data to generate the second validity data, the unique identity ID data and the attribute information can be signed, so that further validity guarantee of the on-chain data is achieved, and safety and reliability of the on-chain data are realized.
As a possible implementation manner, before verifying whether the data to be updated is unique data according to the unique ID data, the method further includes: acquiring validity data of the data to be updated; the validity data comprises signature data of an uploading user of the data to be updated, and signature data obtained by signing the unique identity ID data and attribute information of the data to be updated by an upper link point; the attribute information comprises a record number and generation time of the data to be updated; verifying whether the data to be updated is valid data or not according to the validity data; correspondingly, the verifying whether the data to be updated is unique data according to the unique identity ID data includes: and when the data to be updated is determined to be effective data, verifying whether the data to be updated is unique data according to the unique identity ID data.
In the embodiment of the application, as the data is uplink, the uplink can be performed based on the validity data; when acquiring the data on the chain, the validity data is used for verifying the validity of the acquired data on the chain, and after the verification is passed, the uniqueness verification is carried out, so that the safety, the reliability and the credibility of the acquired data on the chain are fully ensured.
As a possible implementation manner, the verifying whether the data to be updated is valid data according to the validity data includes: acquiring a signature certificate of the uploading user, and verifying whether the signature data of the uploading user is valid according to the signature certificate of the uploading user and the validity data when the signature certificate of the uploading user is valid; acquiring a signature certificate of the uplink node, and verifying whether the signature data of the uplink node is valid or not according to the signature certificate of the uplink node and the validity data when the signature certificate of the uplink node is determined to be valid; and when the signature data of the uploading user and the signature data of the uplink node are determined to be valid, determining the data to be updated as valid data.
In the embodiment of the application, when validity verification is performed based on the validity data, the signature certificate of the uploading user and the signature certificate of the upper link point are verified first, when the validity of the signature certificate is determined, the validity verification is performed on the signature data based on the verification certificates respectively, and when the validity data (signature data) of the data to be updated passes the verification, the data to be updated is the valid data, so that the validity verification of the data to be updated is realized.
As a possible implementation manner, the verifying whether the data to be updated is unique data according to the unique ID data includes: acquiring the first record and the validity data of the first record according to the hash value of the first record, wherein the validity data of the first record comprises: signature data obtained by signing the unique identity ID data and attribute information of the first record by the signature data of the uploading user of the first record and the upper link point; verifying whether the first record is valid according to the validity data of the first record; when the first record is determined to be valid, acquiring validity data corresponding to the previous record and the previous record according to the hash value of the previous record, wherein the validity data corresponding to the previous record comprises: signature data obtained by signing the unique identity ID data and attribute information of the previous record by the signature data of the uploading user of the previous record and the upper link point; verifying whether the previous record is valid according to the validity data of the previous record; when the fact that the previous record is valid is confirmed, whether the record number plus 1 in the attribute information of the previous record is equal to the record number of the data to be updated or not is verified; and when the record number added with 1 in the attribute information of the previous record is determined to be equal to the record number of the data to be updated, determining the data to be updated as unique data.
In the embodiment of the application, when the uniqueness verification is performed on the data on the chain, the validity verification is performed on the historical record data of the data on the chain, when the historical record data of the data on the chain is determined to be the valid data, whether the current data is the latest updated data is verified based on the historical record data, if so, the current data is the unique data and the latest updated data is indicated. When the uniqueness verification is carried out, the validity verification is also required to be carried out on the utilized historical record data, and the reliability of the uniqueness verification result is ensured.
As a possible implementation manner, the method further includes: receiving an acquisition request of historical record data; determining a target data chain corresponding to the historical record data according to the identity information of the user; when the historical record data on the target data chain is determined to be effective data and unique data, acquiring the historical record data; when the hash value of the first record on the target data chain in the unique identity ID data in the currently acquired historical record data is equal to the hash value of the currently acquired historical record data, completing the acquisition of all the historical record data on the target data chain; and feeding back all history data acquired from the target data chain.
In the embodiment of the application, besides performing uniqueness verification on the currently acquired on-chain data based on the historical record data, the historical record data can be acquired, and when the data is acquired, whether the historical record data on the chain are acquired is judged through the hash value of the first record in the unique identity ID data of each data, so that the acquisition of all the historical record data on one data chain can be realized, and the tracking of the data track is realized.
In a second aspect, an embodiment of the present application provides a data updating apparatus of a blockchain, including functional modules for implementing the method described in the first aspect and any one possible implementation manner of the first aspect.
In a third aspect, embodiments of the present application provide a readable storage medium having stored thereon a computer program which, when executed by a computer, performs a method as described in the first aspect and any one of the possible implementations of the first aspect.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments of the present application will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and should not be considered as limiting the scope, and other related drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a block chain application architecture diagram of a block chain application system according to an embodiment of the present disclosure; FIG. 2 is a flowchart of a method for updating data of a blockchain provided in an embodiment of the present application;
FIG. 3 is a flowchart of an application example of a data update method for a blockchain provided in an embodiment of the present application;
FIG. 4 is a functional block diagram of a block chain data update apparatus according to an embodiment of the present application.
Icon: 11-blockchain application; 12-user side; 300-data updating means of the blockchain; 301-a receiving module; 302, an acquisition module; 303-a processing module.
Detailed Description
The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.
For the sake of easy understanding, please refer to fig. 1, which is a schematic diagram of a block chain application mode provided in the embodiment of the present application, in fig. 1, the block chain application system 11 and the client 12 interact, where the block chain application system 11 includes one or more block chain nodes, typically a plurality of block chain nodes; the blockchain node may be understood as a blockchain server that maintains or manages data on the blockchain, including the uplink of the data, the acquisition of the data, the storage of related data of the blockchain data, and so on. The user terminal 12 can be understood as a terminal where a user is located, and can be electronic devices such as a computer, a mobile phone, a tablet computer and the like; the user may initiate a request for acquiring the data on the link through the user side 12, and generate the data to be linked through the user side 12, generate the data related to the data to be linked, and so on. A blockchain may be understood as a data chain for storing data, as a form of data storage, similar to databases in other application systems.
By way of example, in connection with the blockchain application 11, the client 12, and the blockchain, assuming that the user needs to update the data, the complete application flow may include: the user initiates an acquisition request of data to be updated through the user terminal 12, the user terminal 12 sends the acquisition request to the blockchain application system 11, and the blockchain application system 11 acquires corresponding data from a chain and returns the corresponding data to the user terminal 12; this process can be understood as the acquisition process of the data on the chain. The user generates data to be uplink (which can be understood as update data corresponding to the data to be updated) on the user side 12 based on the data returned to the user side 12, then the user side 12 sends the data to be uplink to the blockchain application system 11, and the blockchain application system 11 performs uplink processing on the data; this process can be understood as a data-chaining process. In the application flow, the basic and necessary flow is introduced, and the technical scheme of the embodiment of the application is improved based on the application flow, so that the application of the block chain data with higher reliability, higher safety and higher reliability is realized.
Further, the technical solution provided in the embodiment of the present application is applied to the blockchain application system 11, and may be understood as a server in the blockchain system.
Based on the above application scenario, referring next to fig. 2, a flowchart of a data updating method of a blockchain provided in an embodiment of the present application is provided, where the method is applied to a blockchain application system 11, and the method includes:
step 201: and receiving an acquisition request of the data to be updated. The acquisition request includes identity information of the user.
Step 202: and acquiring the data to be updated from the blockchain according to the identity information of the user.
Step 203: and acquiring unique Identity (ID) data of the data to be updated. The unique identity ID data comprises an application data category to which the data to be updated belongs, a hash value of a first record of the data to be updated on the blockchain, and a hash value of a previous record of the data to be updated on the blockchain.
Step 204: and verifying whether the data to be updated is unique data according to the unique identity ID data.
Step 205: and feeding back the data to be updated when the data to be updated is determined to be the unique data.
It will be appreciated that steps 201-205 correspond to the process of acquiring data on a chain, which may be directed to the acquisition of not only data to be updated, but also any data on a blockchain. That is, steps 201-205 may also be applicable in conventional data acquisition application scenarios.
Compared with the prior art, when acquiring the data on the chain, firstly acquiring the data to be updated according to the identity information of the user, and then acquiring the unique identity ID (Identity document, identity identification) data of the data to be updated, wherein the type of the data can be determined according to the application data type of the data, and the data in the block chain can be distinguished according to the data type, so that whether the type of the data is the unique type can be determined; the history record corresponding to the data to be updated can be determined by the hash value of the first record and the previous record of the data on the blockchain, for example: finding a previous record through the hash value of the previous record of the data to be updated, and tracking the previous record in sequence according to the hash value of the previous record in the unique identity ID data of the previous record, so as to realize the determination of the history record data (whether the data is the latest updated data or not, and play the role of the identification of the current record and the history record). The data can be verified based on the unique identity ID data, and whether the data is the latest updated data or not can be determined, so that the data can be updated effectively and accurately.
Next, the technical solutions provided in the embodiments of the present application will be described in detail in connection with steps 201 to 205.
In step 201, for the data to be updated, assuming that there are 3 records on the blockchain for the same class of data, the 1 st record is the data uploaded to the blockchain for the first time, the 2 nd record is the data recorded by downloading the 1 st record locally, then the data of the uplink is updated, the 3 rd record is the data recorded by downloading the 2 nd record locally, then the data of the uplink is updated; the data to be updated is the data recorded at the 3 rd time. That is, the data to be updated is the data that was updated last in the specified data category. In addition, the acquisition request is an acquisition request sent by the user through the user terminal 12.
The identity information of the user can be key information for representing the identity of the user, based on the identity information, a hash address of the user can be obtained, the hash address of the user is used for representing the hash address of the position where the data uploaded by the user is stored, and the position where the data requested by the user is stored can be located through the hash address.
In step 202, a hash address of the user is determined according to the identity information of the user, corresponding data is obtained on the blockchain based on the hash address, and then the blockchain returns the corresponding data.
After the blockchain returns the data to be updated, the blockchain application 11 performs step 203 to obtain the unique ID data of the data to be updated, where the unique ID data may be stored in the blockchain application 11 or may be stored on the blockchain. The application data category to which the data to be updated belongs is identified by the application data category because the data on the blockchain is divided according to the data category. The hash value of the first record of the data to be updated on the blockchain, which can be understood as the hash value of the 1 st record data, is assumed to be 3 times in total for the same class of data on the blockchain, referring to the previous example; similarly, the hash value of the previous record of the data to be updated on the blockchain can be understood as the hash value of the data recorded at the 2 nd time. These two hash values may be used to identify the current record and the history. For the identification function of the history record, since the first record and the previous record are recorded in the unique identity of the data recorded each time, the previous record can be searched along the data record chain by a reverse pushing mode until the first record is found, and therefore all the history records can be identified only by the first record and the previous record. The manner of acquiring the history is described in detail in the following embodiments.
After the unique ID data is obtained in step 203, step 204 is executed to verify whether the data to be updated is unique data according to the unique ID data, and in the verification, as an optional implementation manner, the verification process includes: acquiring a first record according to the hash value of the first record, and verifying whether the first record is valid (namely verifying whether the first record is valid data or not, and the same applies to the first record); when the first record is determined to be valid, acquiring the first two records according to hash values of the first two records, and verifying whether the first record is valid or not; when the former record is determined to be effective, acquiring attribute information of the former record, wherein the attribute information comprises a record number of the former record; acquiring attribute information of data to be updated, judging whether the record number +1 of the previous record is equal to the record number of the data to be updated, and if so, successfully verifying uniqueness; in each verification and judgment process, if any verification and judgment result is no, the uniqueness verification fails. The attribute information may be stored in the blockchain application 11, or may be stored on the blockchain together with the data itself, and have a correspondence relationship with the unique ID data of the data. In addition, regarding the verification of whether the verification is valid or not, that is, the verification of validity, a safe and reliable verification manner is provided in the embodiment of the present application, and is described in the subsequent implementation.
In step 204, if it is determined that the data to be updated is not unique data, i.e. the unique verification fails, the subsequent processing step is not performed, and the result of the verification failure is fed back to the ue 12, and the ue 12 feeds back to the user again. If it is determined that the data to be updated is unique data, i.e. the uniqueness verification is successful, step 205 is performed to feed back the data to be updated, and the feedback is also performed through the ue 12.
In the embodiment of the present application, in addition to verifying the uniqueness of the data to be updated, the validity of the data to be updated (that is, whether the data is valid or not, for example, tampered, and invalid data) may be verified. For the verification sequence of validity verification and uniqueness verification, in general, validity verification is performed first, then uniqueness verification is performed, that is, the data is guaranteed to be valid first, and then the uniqueness of the data is determined. In practical application, the sequence may be changed according to the application scenario, for example, the uniqueness verification is performed first and then the validity verification is performed, which is not limited in the embodiment of the present application. Next, an embodiment of validity verification will be described.
As an alternative embodiment, prior to step 204, the method further comprises: acquiring validity data of data to be updated; the validity data comprises signature data of an uploading user of the data to be updated, unique identity ID data and attribute information of the data to be updated of an upper link point, and signature data obtained by signing the unique identity ID data and the attribute information of the data to be updated; the attribute information comprises a record number and generation time of data to be updated; and verifying whether the data to be updated is valid data or not according to the validity data. Correspondingly, step 205 comprises: and when the data to be updated is determined to be the valid data, verifying whether the data to be updated is the unique data according to the unique identity ID data.
The validity data of the data to be updated can be stored in the blockchain application system 11 or can be stored on the blockchain, and the data to be updated can be flexibly selected according to the actual application scene. The validity data includes two signature data, one is the signature data of an uploading user of the data to be updated, and the uploading user can be the user side 12 where the user currently requesting the data to be updated is located; the other is signature data obtained by signing the unique ID data and attribute information of the data to be updated by the upper link point, and for the upper link point, as mentioned in the foregoing embodiment, one blockchain application system 11 includes a plurality of blockchain nodes, so that the node of the data to be updated in the uplink may be the node currently performing data processing or may be other nodes.
As an alternative embodiment, verifying whether the data to be updated is valid data according to the validity data includes: acquiring a signature certificate of an uploading user, and verifying whether the signature data of the uploading user is valid according to the signature certificate of the uploading user and the validity data when the signature certificate of the uploading user is valid; acquiring a signature certificate of the uplink link point, and verifying whether the signature data of the uplink node is valid or not according to the signature certificate of the uplink node and the validity data when the signature certificate of the uplink link point is determined to be valid; and when the signature data of the uploading user and the signature data of the uplink node are valid, determining that the data to be updated is valid data.
In such an embodiment, whether the signed certificate of the uploader or the signed certificate of the uplink node, its validity verification may include three aspects, (1) digital certificate validity period verification; (2) root certificate verification; (3) CRL (Certificate Revocation List ) verification. Wherein, the certificate validity period verification means that the using time of the certificate is required to be within the starting time and the ending time; the validity period of the certificate is easily obtained by parsing the certificate. Root certificate verification, a common certificate generally consists of three parts: user information, user public key, and CA (Certificate Authority ) signature. The root certificate is a certificate signed by the CA center itself (i.e., the certificate is signed by the CA public key); root certificate verification is: the issuer signature of the certificate is verified with the root certificate public key. There must first be a root certificate and the root certificate must be in a trusted certificate list (i.e., trust domain). The CRL is a certificate revocation list signed by the CA for certificate freezing and revocation. In general, the certificate has a CRL address, which can be accessed by adopting different network protocol modes, can be obtained by resolving, and then the CRL is downloaded for verification. And the certificate has the effective date of the CRL and the date of the next update, so the CRL is automatically updated, and delay exists. In the prior art, a technology of online inquiring the certificate status exists, so that the certificate status can be inquired through a corresponding channel in real time.
After verifying the signature certificate of the uploader or the uplink node, if the signature certificate is determined to be valid, the validity of the signature data can be verified by using the validity data. It can be understood that when the upper link point or the uploading person signs, the corresponding data is signed by the private key of the upper link point or the uploading person, and the generated signature result is the signature data, so that the public key corresponding to the private key (namely the public key in the signature certificate) can be utilized to decrypt the signature during verification, whether the data obtained by decrypting the public key is consistent with the data obtained by calculating the hash value or not is verified, and if so, the verification is passed; if not, the verification is not passed. The specific authentication process is described with reference to the related art of asymmetric encryption, which is well known to those skilled in the art and will not be described in detail herein.
In connection with the description of the validity verification in this section, reference is made to the description of the embodiment of the uniqueness verification in the foregoing embodiment, where it is described that, in performing the uniqueness verification, the validity of the first record and the previous record needs to be verified, where the validity verification may be implemented in the manner of the validity verification described herein, and therefore, in the validity data of the first record, there is included: signature data of an uploading user of the first record, signature data obtained by signing the unique identity ID data and attribute information of the first record by the upper link point; further, when validity verification is performed on the first record, whether the first record is valid or not is verified according to the validity data of the first record. And in the validity data of the previous record, including: signature data obtained by signing unique ID data and attribute information of the previous record by the link uploading point; and verifying whether the previous record is valid according to the validity data of the previous record when the second record is validated.
In the embodiment of the application, the data is subjected to double signature during uplink, and further, during validity verification, the validity, the reliability and the safety of the data on the blockchain are guaranteed through double signature verification.
The embodiment of validity verification is only an optional verification mode, and in practical application, other validity verification modes can be selected according to different application scenarios, for example: the verification manner of the single signature is not limited in the embodiment of the present application.
As an alternative embodiment, after step 205, the method includes: acquiring data to be uplink; the data to be uplink is the data obtained after the data to be updated are updated; generating unique Identity (ID) data of the data to be uplink; and carrying out uplink processing on the data to be uplink according to the unique identity ID data of the data to be uplink.
In this process, the data to be uplink may also be data for a certain data class, i.e. the first uplink data: the data uplink may be a process performed after step 205, and is applicable to such an application scenario that the data to be uplink is obtained from the data to be updated. The method and the device can also be a single data uplink process, so that the data uplink implementation mode provided by the embodiment of the application can also be applied to other data uplink application scenes.
In combination with the description of the unique ID data in the foregoing embodiment, when generating the unique ID data of the data to be uplink, it is required to determine: the application data category to which the data to be uplink belongs is the same as the application category to which the data to be uplink belongs if the application data category belongs to the application scene for data updating; if in other application scenarios, it may be defined by the blockchain application 11. The hash value of the first record of the data to be uplinked on the blockchain is also defined by the blockchain application system 11, and in the case that the data to be updated passes the uniqueness verification (or passes the validity verification), the hash value of the first record in the unique ID data of the data to be uplinked is the same as the hash value of the first record in the data to be updated. The hash value of the previous record of the data to be uplinked on the blockchain is also defined by the blockchain application system 11, and in the case that the data to be updated passes the uniqueness verification (or passes the validity verification), the hash value of the previous record in the unique ID data of the data to be uplinked and the hash value of the data to be updated are both the hash value of the data to be updated.
In the embodiment of the application, after the data to be updated is fed back, the user performs data uplink based on the data to be updated, and generates unique Identity (ID) data for the data when the data is uplink, so that the data can be subjected to data uniqueness verification when the data is acquired or applied later, and the current record and the history record can be identified.
In the embodiment of the application, in order to facilitate the subsequent verification of the validity of the data, a corresponding double-signature uplink mode may also be adopted when the data is uplink. Thus, as an alternative embodiment, before the uplink processing is performed on the data to be uplink according to the unique ID data of the data to be uplink, the method further includes: acquiring first validity data of data to be uplink; the first validity data is signature data of an uploading user of the data to be uplink; signing the unique Identity (ID) data of the data to be uplinked to obtain second validity data; correspondingly, the uplink processing is carried out on the data to be uplink according to the unique identity ID data of the data to be uplink, which comprises the following steps: and carrying out uplink processing on the data to be uplink according to the unique identity ID data, the first validity data and the second validity data of the data to be uplink.
In this embodiment, the uploader is a user terminal 12 uploading data to be uplink, after the user terminal 12 obtains the data to be uplink input by the user, the user terminal signs the data to be uplink by using a private key, and the signature result is the first validity data. Similarly, the blockchain application system 11 signs the generated unique ID data with a private key, and the obtained signature result is the second validity data.
In this embodiment of the present application, when the second validity data is obtained, the attribute information may be signed in addition to signing the unique ID data, and further the obtained second validity data may further include a signature result of the attribute information. Thus, as an alternative embodiment, before signing the unique identity ID data to be used for the uplink data, the method further comprises, before obtaining the second validity data: acquiring attribute information of data to be uplink; the attribute information comprises a record number and generation time of data to be uplink; correspondingly, signing the unique Identity (ID) data of the data to be uplinked to obtain second validity data, wherein the signing comprises the following steps: and signing the unique Identity (ID) data and the attribute information of the data to be uplinked to obtain second validity data.
In the embodiment of the application, when signing the on-chain data to generate the second validity data, the unique identity ID data and the attribute information can be signed, so that further validity guarantee of the on-chain data is achieved, and safety and reliability of the on-chain data are realized.
It will be appreciated that the end effect of the validity data of the on-chain data is to validate the on-chain data, and thus the more signature results are included in the validity data, the more reliable and reliable the end validation result. Therefore, in practical application, the validity data items contained in the validity data can be flexibly selected according to the application scene, so as to improve the reliability of validity verification.
Further, whether the uplink processing of the data to be uplink is performed based on the unique ID data or the uplink processing is performed based on the unique ID data, the first validity data and the second validity data, on the one hand, the data to be uplink is submitted to the blockchain, the blockchain automatically performs the data uplink, and the process of the data uplink of the blockchain is a technology well known to those skilled in the art, and will not be described in detail herein. On the other hand, the unique ID data, the first validity data, and the second validity data may be stored in the blockchain application 11 (in a distributed storage manner, that is, each blockchain node is stored), or may be stored in the blockchain. If stored in the blockchain, the storage may be performed by a specified unique identity ID data chain or a validity data chain. After the blockchain performs data uplink, the blockchain application 11 feeds back the uplink result to the client 12.
With reference to fig. 3, an optional complete implementation flow diagram of the technical solution of the embodiment of the present application in practical application is shown, where the complete implementation flow includes: the user side 12 starts the on-link data update flow, and on-link data update starts; the user side 12 requests to acquire data; blockchain application 11: acquiring a hash address of a user according to user key information (identity information); and acquiring the data on the chain of the user according to the hash address request. The blockchain returns the on-chain data specifying the hash address. Blockchain application 11: the validity verification of the data to be updated is firstly performed, then the uniqueness verification of the data to be updated is performed, and after both verification passes, the data is returned to the user side 12. The user side 12 generates data to be uplink based on data input by a user for updating the returned data to be updated; signing the data to be uplink to generate first validity data; the first validity data and the data to be uplinked are submitted to the blockchain application 11. Blockchain application 11: firstly, generating unique Identity (ID) data and generating attribute information; signing the unique identity ID data and the attribute information to generate second validity data; and submitting the data to be uplinked to the blockchain. The blockchain performs data uplink, the blockchain application system 11 returns the uplink result to the client 12, and the whole process is finished.
In the embodiment of the application, track tracking of data change can also be realized based on the data structure form of the data on the chain, and as an optional implementation manner, the method further comprises: receiving an acquisition request of historical record data; determining a target data chain corresponding to the history record data according to the identity information of the user; when the historical record data on the target data chain is determined to be effective data and unique data, acquiring the historical record data; when the hash value of the first record on the target data chain in the unique identity ID data in the currently acquired historical record data is equal to the hash value of the currently acquired historical record data, completing the acquisition of all the historical record data on the target data chain; all history data obtained from the target data chain is fed back.
In this embodiment, the identity information of the user is the same as that described in the previous examples. When determining the target data chain corresponding to the historical record data, the data updated last time on the target data chain can be determined first, and then data tracking is sequentially carried out along the hash value of the previous record recorded in the unique identity ID data of the last updated data. And when the data record is obtained each time, the validity and the uniqueness of the current data are required to be verified, and when the validity verification and the uniqueness verification are passed, the current data are obtained, and the record information in the unique Identity (ID) data of the current data is utilized to continue data tracking. And, after the current data is acquired, it is also necessary to verify whether the acquisition of all the histories has been completed. The verification method is that the hash value of the first record in the unique Identity (ID) data of the current data is used, and it can be understood that if the hash value of the current data is the same as the hash value of the first record, the current data is the first record, and it can be determined that all the data records on the target data chain have been traced. The implementation of validity verification and uniqueness verification is the same as that described in the foregoing examples, and the description thereof will not be repeated here.
In the embodiment of the application, besides performing uniqueness verification on the currently acquired on-chain data based on the historical record data, the historical record data can be acquired, and when the data is acquired, whether the historical record data on the chain are acquired is judged through the hash value of the first record in the unique identity ID data of each data, so that the acquisition of all the historical record data on one data chain can be realized, and the tracking of the data track is realized.
Based on the same inventive concept, referring to fig. 4, in an embodiment of the present application, a data updating apparatus 300 for a blockchain is further provided, including: a receiving module 301, an acquiring module 302 and a processing module 303.
The receiving module 301 is configured to receive an acquisition request of data to be updated; the acquisition request comprises identity information of a user; the acquiring module 302 is configured to acquire the data to be updated from a blockchain according to the identity information of the user; acquiring unique Identity (ID) data of the data to be updated; the unique identity ID data comprises an application data type to which the data to be updated belongs, a hash value of a first record of the data to be updated on the block chain and a hash value of a previous record of the data to be updated on the block chain; the processing module 303 is configured to verify whether the data to be updated is unique data according to the unique ID data; and feeding back the data to be updated when the data to be updated is determined to be the unique data.
Optionally, the acquiring module 302 is further configured to acquire data to be uplink; the data to be uplink is data obtained after updating the data to be updated; the processing module 303 is further configured to generate unique ID data of the data to be uplink; and carrying out uplink processing on the data to be uplink according to the unique Identity (ID) data of the data to be uplink.
Optionally, the acquiring module 302 is further configured to acquire first validity data of the data to be uplink; the first validity data is signature data of an uploading user of the data to be uplink; the processing module 303 is further configured to sign the unique ID data of the data to be uplink to obtain second validity data; the processing module 303 is specifically configured to: and carrying out uplink processing on the data to be uplink according to the unique Identity (ID) data of the data to be uplink, the first validity data and the second validity data.
Optionally, the acquiring module 302 is further configured to acquire attribute information of the data to be uplink; the attribute information comprises a record number and generation time of the data to be uplink; and the processing module 303 is specifically configured to sign the unique ID data of the data to be uplink and the attribute information, so as to obtain the second validity data.
Optionally, the acquiring module 302 is further configured to acquire validity data of the data to be updated; the validity data comprises signature data of an uploading user of the data to be updated, and signature data obtained by signing the unique identity ID data and attribute information of the data to be updated by an upper link point; the attribute information comprises a record number and generation time of the data to be updated; verifying whether the data to be updated is valid data or not according to the validity data; the processing module 303 is specifically configured to verify whether the data to be updated is unique data according to the unique ID data when the data to be updated is determined to be valid data.
Optionally, the acquiring module 302 is specifically configured to acquire the signature certificate of the uploader, and when determining that the signature certificate of the uploader is valid, the processing module 303 is specifically configured to verify whether the signature data of the uploader is valid according to the signature certificate of the uploader and the validity data; the obtaining module 302 is specifically further configured to obtain a signature certificate of the uplink node, and the processing module 303 is specifically further configured to, when determining that the signature certificate of the uplink node is valid, verify whether the signature data of the uplink node is valid according to the signature certificate of the uplink node and the validity data; and when the signature data of the uploading user and the signature data of the uplink node are determined to be valid, determining the data to be updated as valid data.
Optionally, the obtaining module 302 is specifically further configured to obtain the first record and validity data of the first record according to the hash value of the first record, where the validity data of the first record includes: signature data obtained by signing the unique identity ID data and attribute information of the first record by the signature data of the uploading user of the first record and the upper link point; the processing module 303 is specifically further configured to: verifying whether the first record is valid according to the validity data of the first record; the obtaining module 302 is specifically further configured to obtain, when it is determined that the first record is valid, validity data corresponding to the previous record and the previous record according to the hash value of the previous record, where the validity data corresponding to the previous record includes: signature data obtained by signing the unique identity ID data and attribute information of the previous record by the signature data of the uploading user of the previous record and the upper link point; the processing module 303 is specifically further configured to verify whether the previous record is valid according to the validity data of the previous record; when the fact that the previous record is valid is confirmed, whether the record number plus 1 in the attribute information of the previous record is equal to the record number of the data to be updated or not is verified; and when the record number added with 1 in the attribute information of the previous record is determined to be equal to the record number of the data to be updated, determining the data to be updated as unique data.
Optionally, the receiving module 301 is further configured to receive an acquisition request of the history data; the processing module 303 is further configured to determine a target data chain corresponding to the history data according to the identity information of the user; the obtaining module 302 is further configured to obtain the history data when it is determined that the history data on the target data chain is valid data and unique data; the processing module 303 is further configured to complete the acquisition of all the history data on the target data chain when it is determined that the hash value of the first record on the target data chain in the unique ID data in the currently acquired history data is equal to the hash value of the currently acquired history data; and feeding back all history data acquired from the target data chain.
The embodiments and specific examples of the data updating method of the blockchain in the foregoing embodiments are equally applicable to the apparatus of fig. 4, and those skilled in the art will clearly know the implementation method of the data updating apparatus 300 of the blockchain in fig. 4 through the foregoing detailed description of the data updating method of the blockchain, so they will not be described in detail herein for brevity of description.
Based on the same inventive concept, the embodiments of the present application also provide a readable storage medium having stored thereon a computer program that, when executed by a computer, performs the data update method of the blockchain of any of the embodiments described above.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. The above-described apparatus embodiments are merely illustrative, for example, the division of the units is merely a logical function division, and there may be other manners of division in actual implementation, and for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be through some communication interface, device or unit indirect coupling or communication connection, which may be in electrical, mechanical or other form.
Further, the units described as separate units may or may not be physically separate, and units displayed as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
Furthermore, functional modules in various embodiments of the present application may be integrated together to form a single portion, or each module may exist alone, or two or more modules may be integrated to form a single portion.
In this document, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions.
The foregoing is merely exemplary embodiments of the present application and is not intended to limit the scope of the present application, and various modifications and variations may be suggested to one skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principles of the present application should be included in the protection scope of the present application.
Claims (8)
1. A method of updating data of a blockchain, comprising:
receiving an acquisition request of data to be updated; the acquisition request comprises identity information of a user;
acquiring the data to be updated from a blockchain according to the identity information of the user;
acquiring unique Identity (ID) data of the data to be updated; the unique identity ID data comprises an application data type to which the data to be updated belongs, a hash value of a first record of the data to be updated on the block chain and a hash value of a previous record of the data to be updated on the block chain;
Acquiring validity data of the data to be updated; the validity data comprises signature data of an uploading user of the data to be updated, and signature data obtained by signing the unique identity ID data and attribute information of the data to be updated by an upper link point; the attribute information comprises a record number and generation time of the data to be updated;
verifying whether the data to be updated is valid data or not according to the validity data;
when the data to be updated is determined to be the validity data, verifying whether the data to be updated is the unique data according to the unique identity ID data comprises the following steps:
acquiring the first record and the validity data of the first record according to the hash value of the first record, wherein the validity data of the first record comprises: signature data obtained by signing the unique identity ID data and attribute information of the first record by the signature data of the uploading user of the first record and the upper link point;
verifying whether the first record is valid according to the validity data of the first record;
when the first record is determined to be valid, acquiring validity data corresponding to the previous record and the previous record according to the hash value of the previous record, wherein the validity data corresponding to the previous record comprises: signature data obtained by signing the unique identity ID data and attribute information of the previous record by the signature data of the uploading user of the previous record and the upper link point;
Verifying whether the previous record is valid according to the validity data of the previous record;
when the fact that the previous record is valid is confirmed, whether the record number plus 1 in the attribute information of the previous record is equal to the record number of the data to be updated or not is verified;
when the record number in the attribute information of the previous record is added with 1 to be equal to the record number of the data to be updated, determining the data to be updated as unique data;
and feeding back the data to be updated when the data to be updated is determined to be the unique data.
2. The method according to claim 1, wherein upon the feedback of the data to be updated when the data to be updated is determined to be unique data, the method further comprises:
acquiring data to be uplink; the data to be uplink is data obtained after updating the data to be updated;
generating unique Identity (ID) data of the data to be uplink;
and carrying out uplink processing on the data to be uplink according to the unique Identity (ID) data of the data to be uplink.
3. The method of claim 2, wherein prior to said processing said data to be uplinked according to said unique identity ID data of said data to be uplinked, said method further comprises:
Acquiring first validity data of the data to be uplink; the first validity data is signature data of an uploading user of the data to be uplink;
signing the unique Identity (ID) data of the data to be uplink to obtain second validity data;
correspondingly, the uplink processing of the data to be uplink according to the unique identity ID data of the data to be uplink includes:
and carrying out uplink processing on the data to be uplink according to the unique Identity (ID) data of the data to be uplink, the first validity data and the second validity data.
4. A method according to claim 3, wherein prior to signing the unique identity ID data of the data to be uplink, the method further comprises:
acquiring attribute information of the data to be uplink; the attribute information comprises a record number and generation time of the data to be uplink;
correspondingly, the signing the unique identity ID data of the data to be uplink to obtain second validity data includes:
and signing the unique Identity (ID) data of the data to be uplink and the attribute information to obtain the second validity data.
5. The method of claim 1, wherein verifying whether the data to be updated is valid data based on the validity data comprises:
acquiring a signature certificate of the uploading user, and verifying whether signature data of the uploading user are valid according to the signature certificate of the uploading user when the signature certificate of the uploading user is valid;
acquiring a signature certificate of the uplink node, and verifying whether signature data of the uplink node is valid according to the signature certificate of the uplink node when the signature certificate of the uplink node is valid;
and when the signature data of the uploading user and the signature data of the uplink node are determined to be valid, determining the data to be updated as valid data.
6. The method according to claim 1, wherein the method further comprises:
receiving an acquisition request of historical record data;
determining a target data chain corresponding to the historical record data according to the identity information of the user;
when the historical record data on the target data chain is determined to be effective data and unique data, acquiring the historical record data;
when the hash value of the first record on the target data chain in the unique identity ID data in the currently acquired historical record data is equal to the hash value of the currently acquired historical record data, completing the acquisition of all the historical record data on the target data chain;
And feeding back all history data acquired from the target data chain.
7. A data updating apparatus of a blockchain, comprising:
the receiving module is used for receiving an acquisition request of data to be updated; the acquisition request comprises identity information of a user;
the acquisition module is used for acquiring the data to be updated from the blockchain according to the identity information of the user;
the acquisition module is also used for acquiring the unique identity ID data of the data to be updated; the unique identity ID data comprises an application data type to which the data to be updated belongs, a hash value of a first record of the data to be updated on the block chain and a hash value of a previous record of the data to be updated on the block chain; the acquisition module is also used for acquiring the validity data of the data to be updated; the validity data comprises signature data of an uploading user of the data to be updated, and signature data obtained by signing the unique identity ID data and attribute information of the data to be updated by an upper link point; the attribute information comprises a record number and generation time of the data to be updated;
the processing module is used for verifying whether the data to be updated is valid data or not according to the validity data; when the data to be updated is determined to be the validity data, verifying whether the data to be updated is the unique data according to the unique identity ID data; when the data to be updated is determined to be unique data, the data to be updated is fed back, and the processing module is specifically configured to obtain the first record and validity data of the first record according to the hash value of the first record, where the validity data of the first record includes: signature data obtained by signing the unique identity ID data and attribute information of the first record by the signature data of the uploading user of the first record and the upper link point; verifying whether the first record is valid according to the validity data of the first record; when the first record is determined to be valid, acquiring validity data corresponding to the previous record and the previous record according to the hash value of the previous record, wherein the validity data corresponding to the previous record comprises: signature data obtained by signing the unique identity ID data and attribute information of the previous record by the signature data of the uploading user of the previous record and the upper link point; verifying whether the previous record is valid according to the validity data of the previous record; when the fact that the previous record is valid is confirmed, whether the record number plus 1 in the attribute information of the previous record is equal to the record number of the data to be updated or not is verified; and when the record number added with 1 in the attribute information of the previous record is determined to be equal to the record number of the data to be updated, determining the data to be updated as unique data.
8. A readable storage medium, characterized in that it has stored thereon a computer program which, when executed by a computer, performs the method according to any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011167416.4A CN112182009B (en) | 2020-10-27 | 2020-10-27 | Block chain data updating method and device and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011167416.4A CN112182009B (en) | 2020-10-27 | 2020-10-27 | Block chain data updating method and device and readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112182009A CN112182009A (en) | 2021-01-05 |
| CN112182009B true CN112182009B (en) | 2024-03-12 |
Family
ID=73922262
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011167416.4A Active CN112182009B (en) | 2020-10-27 | 2020-10-27 | Block chain data updating method and device and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112182009B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112637369B (en) * | 2021-03-10 | 2021-06-08 | 中航信移动科技有限公司 | Information interaction confirmation system based on block chain |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN207504911U (en) * | 2017-11-17 | 2018-06-15 | 北京亿生生网络科技有限公司 | A kind of data deposit system based on block chain technology |
| CN111198895A (en) * | 2020-02-18 | 2020-05-26 | 夏南南 | Block chain updating method |
| CN111783149A (en) * | 2020-06-30 | 2020-10-16 | 北京海益同展信息科技有限公司 | Data processing method, system, processing equipment and authentication equipment based on block chain |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| SG11201903533QA (en) * | 2018-11-30 | 2019-05-30 | Alibaba Group Holding Ltd | Blockchain smart contract updates using decentralized decision |
-
2020
- 2020-10-27 CN CN202011167416.4A patent/CN112182009B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN207504911U (en) * | 2017-11-17 | 2018-06-15 | 北京亿生生网络科技有限公司 | A kind of data deposit system based on block chain technology |
| CN111198895A (en) * | 2020-02-18 | 2020-05-26 | 夏南南 | Block chain updating method |
| CN111783149A (en) * | 2020-06-30 | 2020-10-16 | 北京海益同展信息科技有限公司 | Data processing method, system, processing equipment and authentication equipment based on block chain |
Non-Patent Citations (2)
| Title |
|---|
| Renovating blockchain with distributed databases:An open source system;M Muzammal,Q Qu,B Nasrulin;Future Generation Computer Systems;第90卷;105-117 * |
| 基于区块链技术的图书馆科学数据仓储模型研究;姚敏;;图书馆学刊(06);94-97 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112182009A (en) | 2021-01-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11349674B2 (en) | Digital certificate management method and apparatus, computer device, and storage medium | |
| AU2022204148B2 (en) | Methods and apparatus for providing blockchain participant identity binding | |
| JP7109569B2 (en) | Digital certificate verification method and its device, computer equipment and computer program | |
| CN107396360B (en) | Block verification method and device | |
| CN108681965B (en) | Block chain network transaction processing method and device for offline node | |
| EP3454238B1 (en) | Registration and authorization method, device and system | |
| US20210209373A1 (en) | Media authentication using distributed ledger | |
| US20080040808A1 (en) | Document management apparatus, computer readable medium, method for managing document, and computer data signal | |
| EP3966997B1 (en) | Methods and devices for public key management using a blockchain | |
| WO2021105816A1 (en) | Methods and devices for automated digital certificate verification | |
| CN112448946B (en) | Log auditing method and device based on block chain | |
| US20220067036A1 (en) | Systems and methods for a federated directory service | |
| CN112311779B (en) | Data access control method and device applied to block chain system | |
| WO2023093500A1 (en) | Access verification method and apparatus | |
| CN114978635A (en) | Cross-domain authentication method and device, and user registration method and device | |
| CN113129008B (en) | Data processing method, device, computer readable medium and electronic equipment | |
| CN112182009B (en) | Block chain data updating method and device and readable storage medium | |
| US20230146229A1 (en) | Entity, gateway device, information processing device, information processing system, and information processing method | |
| CN116975901A (en) | Identity verification method, device, equipment, medium and product based on block chain | |
| CN111212037B (en) | Advertisement data processing method and device | |
| JP2003134109A (en) | System for verifying validity of public key certificate | |
| CN111083122A (en) | Block chain-based electronic evidence processing method and system and storage medium | |
| CN116405265A (en) | Communication method and device for service end and user end of DID system | |
| CN114844700A (en) | Identity authentication method, system, equipment and storage medium based on trusted storage in distributed environment | |
| CN116012009A (en) | Block chain-based transaction verification method, device, electronic equipment and readable medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |