CN112417517B - Data standard management method based on block chain - Google Patents
Data standard management method based on block chain Download PDFInfo
- Publication number
- CN112417517B CN112417517B CN202011303107.5A CN202011303107A CN112417517B CN 112417517 B CN112417517 B CN 112417517B CN 202011303107 A CN202011303107 A CN 202011303107A CN 112417517 B CN112417517 B CN 112417517B
- Authority
- CN
- China
- Prior art keywords
- metadata
- organization
- blockchain
- modification
- chain
- 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
- 238000007726 management method Methods 0.000 title claims abstract description 25
- 230000008520 organization Effects 0.000 claims abstract description 64
- 238000000034 method Methods 0.000 claims abstract description 35
- 230000004048 modification Effects 0.000 claims description 54
- 238000012986 modification Methods 0.000 claims description 54
- 230000004044 response Effects 0.000 claims description 12
- 230000008859 change Effects 0.000 claims description 11
- 238000012795 verification Methods 0.000 claims description 9
- 238000010276 construction Methods 0.000 claims description 3
- 239000000463 material Substances 0.000 claims description 3
- 238000004806 packaging method and process Methods 0.000 claims description 3
- 230000000977 initiatory effect Effects 0.000 claims description 2
- 230000001960 triggered effect Effects 0.000 claims description 2
- 238000006243 chemical reaction Methods 0.000 abstract description 5
- 230000000694 effects Effects 0.000 abstract description 2
- 238000005516 engineering process Methods 0.000 abstract description 2
- 230000008569 process Effects 0.000 description 11
- 238000012423 maintenance Methods 0.000 description 10
- 238000010586 diagram Methods 0.000 description 7
- 239000004744 fabric Substances 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 238000013500 data storage Methods 0.000 description 2
- 239000003999 initiator Substances 0.000 description 2
- 238000012163 sequencing technique Methods 0.000 description 2
- 238000012550 audit Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000012508 change request Methods 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
- 238000009472 formulation Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000011835 investigation Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 239000000203 mixture Substances 0.000 description 1
- 238000010606 normalization Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
Classifications
-
- 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
-
- 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/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
- G06F21/6227—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database where protection concerns the structure of data, e.g. records, types, queries
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Accounting & Taxation (AREA)
- General Engineering & Computer Science (AREA)
- General Health & Medical Sciences (AREA)
- Bioethics (AREA)
- Finance (AREA)
- Health & Medical Sciences (AREA)
- Software Systems (AREA)
- Databases & Information Systems (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Marketing (AREA)
- Strategic Management (AREA)
- Technology Law (AREA)
- General Business, Economics & Management (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention relates to the technical field of data standard management and blockchain, and particularly discloses a blockchain-based data standard management method. The method comprises the following steps: A. when the data standard is created, the metadata information in the data standard is uploaded to the blockchain, the unique identification code of each piece of metadata information is obtained, and the data standard maker and the user do not need to perform centralized access on the data standard any more, so that the effect of decentralized data standard management is achieved. The step A specifically comprises the following steps: 1, converting original metadata into a target format; and 2, operating the metadata in the target format to obtain a character string and an encrypted character string corresponding to the metadata in each target format. The invention carries out data conversion and uplink on the metadata information through the blockchain technology, so that the metadata is traceable and can not be tampered, and therefore, the used organization can completely trust the data standard obtained from the central library.
Description
Technical Field
The invention relates to the technical field of data standard management and blockchain, and particularly discloses a blockchain-based data standard management method.
Background
As the informatization of industries progresses, a large amount of data is deposited in each system, and unified standards are required for the data to be applied, so that the requirement of data standard management is met.
The data standard refers to a normalization constraint that ensures consistency and accuracy of internal and external use and exchange of data. The specific form of the data standard is typically a set of one or more metadata, i.e. the metadata is the basic unit of the data standard. What is metadata is data used to describe data, such as description data of names, types, lengths, etc. of fields in a data table is referred to as metadata. What the standard metadata is in turn, standard metadata is metadata that is commonly formulated and approved by some organization or community. Data conversion is carried out as rules in the process of establishing a data warehouse; in the process of sharing and exchanging data among departments, the method is used for describing the format of the data and improves the sharing and exchanging efficiency.
Since metadata in data standards plays a critical role in the data governance process, extremely high uniformity, acceptance, and credibility must be required for metadata. The traditional data standard management is generally carried out by a designated department or organization (such as an IT department), and the data standard is formed by investigation, wherein the data standard comprises a data set and data subclasses, specifically metadata describing the data subclasses, metadata information is stored in a central library, and the maintenance and management of the data standard are completed by the designated department, namely a centralized data standard management mode and system. However, the use of the data standard is difficult for all parties to participate in the establishment, maintenance and upgrading of the data standard, the process is complex, and the responsibility is unclear. Often, after an organization spends a lot of effort specifying data standards, the data standards are quickly inapplicable with the change of the service, the progress of revising the data standards cannot keep pace with the change speed of the service, and finally the data standards are similar to the dummy. Second, large organizations or data standards in a cross-organization environment have reliability problems, but organizations in data standard management using a centralized schema cannot identify whether the metadata is trusted, only unconditional trust center libraries. There is a need for a distributed decentralized data standard management method and system that enables the trust of metadata in the data standard and the participation of the related organization in the data standard during the formulation and maintenance process.
Disclosure of Invention
The invention aims at solving the current situation that in the data center or data warehouse data standard management, each organization or business department using the data standard cannot identify whether metadata in the data standard is credible or not, and is difficult to participate in centralized data standard management maintenance, and the standard data management method based on the blockchain is provided by utilizing the characteristic that the blockchain data is not falsified and traceable, and comprises a metadata conversion method based on the blockchain, so that the creation and maintenance of the multiparty common participation data standard are realized.
In order to achieve the above object, the present invention provides the following technical solutions:
a data standard management method based on block chain includes the steps:
A. when metadata is created, uploading metadata information to a blockchain, and acquiring unique identification codes of each piece of metadata information;
B. when metadata in a data standard is called, verifying on a blockchain is carried out on the acquired metadata according to the unique identification code, and determining whether the acquired metadata is tampered or not;
the step A specifically comprises the following steps:
firstly, converting original metadata into a target format to obtain metadata in the target format;
secondly, operating the metadata in the target format to obtain a character string corresponding to the metadata in each target format;
thirdly, encrypting the character string to obtain an encrypted character string;
and fourthly, combining the character string, an encrypted character string corresponding to the character string, a table name, related description, a pre-change information source and a current metadata version into metadata information on a blockchain, wherein the encrypted character string corresponding to the character string is a unique identification code of the metadata information.
Further, the method further comprises the step B of carrying out verification on a blockchain on the acquired metadata according to the unique identification code when the metadata in the data standard are called, and determining whether the acquired metadata are tampered;
the method specifically comprises the following steps:
searching an encrypted character string in the metadata under the chain when acquiring the metadata under the chain;
and searching whether corresponding on-chain metadata exists on the blockchain through the encryption character string, if so, obtaining the metadata under the chain without tampering, and if not, obtaining the metadata under the chain without tampering.
Preferably, the steps further include: the method for maintaining the metadata in the block comprises the following steps: 1) Preparing data; 2) Achieving the consensus on the chain; 3) The data under the chain is synchronously changed.
Further, the preparation of data specifically includes the following steps:
finding an encrypted character string before metadata change which needs to be changed;
according to the method of the step A, the changed metadata information is converted into an on-chain data structure, and the changed metadata information is obtained;
the encryption string before modification is added to the "information source before modification" field in the metadata information after modification.
Preferably, the step of achieving the on-chain consensus comprises:
c1, constructing an organization channel, wherein the organization channel comprises a plurality of organization nodes, the organization nodes are in one-to-one correspondence with metadata organization in the usage data standard, and the metadata organization is permitted to initiate a metadata modification request in the organization channel;
c2, one organization node initiates a request for modifying metadata in the data standard, and constructs a modification proposal;
the endorsement node in the organization channel verifies the modification proposal according to the content of the modification proposal and the construction information of the organization channel, and when the verification is passed, a transaction result is generated;
c4, generating proposal response according to the transaction result and the signature of the endorsement node;
c5, judging whether the proposal response meets a preset endorsement strategy, and if so, packaging the modified proposal into blocks according to the time sequence;
c6, each organization node verifies the modification proposal in the block, and if the modification proposal in the block is unchanged, the transaction mark of the block is valid;
c7, when the transaction mark of the block is valid, modifying metadata on the chain.
Preferably, the organization channels and organization nodes meet the following conditions:
1) The corresponding organization of the metadata in the usage data standard of the organization node completes the registration and registration of the metadata standard organization, and obtains the encrypted material for confirming the identity;
2) The blockchain of the modified metadata sets an endorsement policy and defines a method for modifying the metadata;
3) The organization node initiating the request for modifying the metadata has the authority to initiate the modification of the metadata;
4) And under the condition that all organization nodes on the organization channel agree, the blockchain can be triggered to modify the metadata.
In a preferred embodiment, in step C3, the modification proposal is verified, and the verification content includes:
1) Whether the format of the proposal is complete is modified; 2) Whether the modification proposal is submitted for the first time; 3) Verifying whether the signature of the endorsement node is valid; 4) Whether the organization node constructing the modification proposal has the right to initiate the modification of the metadata.
Preferably, the transaction result includes a response value and a write set, the write set being a key value pair of the metadata to be modified.
Preferably, the pre-endorsement policy is that all nodes in the organization channel are endorsed.
Based on the same conception, the invention also provides a data standard management system based on the block chain, which comprises at least one processor and a memory in communication connection with the at least one processor; the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of the above.
Compared with the prior art, the invention has the beneficial effects that:
1. according to the invention, metadata information is subjected to data conversion and uplink through a blockchain technology, so that the metadata is traceable and can not be tampered, and therefore, the used organization can completely trust the standard metadata obtained from the central library;
2. the invention also introduces the chain code and the channel in the alliance chain into the metadata block chain, realizes the non-falsification and traceability of the data, and the multiparty joint participates in the creation and maintenance of the data standard.
Description of the drawings:
FIG. 1 is a flowchart of a block chain based data standard management method according to an embodiment 1 of the present invention;
FIG. 2 is a schematic diagram of an in-chain data storage mode of metadata information in the data standard in embodiment 1 of the present invention;
FIG. 3 is a json string schematic diagram of embodiment 1 of the present invention;
FIG. 4 is a diagram showing the structure of metadata information on a block in embodiment 1 of the present invention;
FIG. 5 is a schematic diagram of an under-link data storage manner of metadata information added to an MD5 encrypted string in embodiment 1 of the present invention;
FIG. 6 is a block diagram of metadata in embodiment 1 of the present invention;
FIG. 7 is a diagram showing the conversion of modified metadata information into an on-chain data structure in embodiment 1 of the present invention;
FIG. 8 is a diagram illustrating the process of the accounting node placing received data into blocks in accordance with embodiment 1 of the present invention;
FIG. 9 is a flowchart showing the steps for achieving consensus on Fabric chains in example 1 of the present invention.
Detailed Description
The present invention will be described in further detail with reference to test examples and specific embodiments. It should not be construed that the scope of the above subject matter of the present invention is limited to the following embodiments, and all techniques realized based on the present invention are within the scope of the present invention.
Example 1
In the scheme of the invention, the central library is not completely abandoned, and the modification of the block chain is only carried out on the basis of the prior art. Taking metadata information in table 1 as an example, when metadata in a data standard is created, the metadata information is uploaded to a blockchain, the metadata information is regarded as an asset in the blockchain, a unique mark is obtained after each piece of data is uploaded, and the obtained unique mark is stored in metadata corresponding to a central repository, as shown in table 2. Therefore, when using the metadata, someone can acquire the data on the blockchain by holding the unique identifier on the block for comparison, and the problem of credibility is solved because the characteristic data of the blockchain is not tamperable.
Table 1 metadata information example
| Numbering device | Data item name | Length of | Constraint | Reference number |
| GXXX020101 | WYHBH | 8 | O | |
| GXXX020102 | WYHMC | 60 | O | |
| GXXX020103 | WYHJC | 12 | O |
Table 2 metadata format examples with chunk identification
| Numbering device | Data item name | Length of | Constraint | Reference number | Unique identification on a block |
| GXXX020101 | WYHBH | 8 | O | 87f34b75650f4848b2891e7cce9dfaa2 | |
| GXXX020102 | WYHMC | 60 | O | 5d85355111f34f029d3fead832decd52 | |
| GXXX020103 | WYHJC | 12 | O | a4dec2c8521a469c85a75077a74f0b56 |
A flowchart of a blockchain-based data standard management method is shown in fig. 1, the method comprising the steps of:
when metadata is created, the metadata information is uploaded to a blockchain, and unique identification codes of each piece of metadata information are obtained.
Firstly, converting original metadata into json format to obtain the metadata in the json format;
secondly, performing operation on the meta-data in the json format to obtain json character strings corresponding to the meta-data in each json format;
thirdly, performing an md5 encryption algorithm on the json character string to obtain an md5 encrypted character string;
fourth, the json character string, the md5 encryption character string corresponding to the json character string, the table name, the related description, the information source before modification and the current metadata version are combined into metadata information on the blockchain, and the md5 encryption character string corresponding to the json character string is the unique identification code of the metadata information.
The method is changed. The metadata information is stored in the link data as shown in fig. 2. Each piece of data includes nine types of data, which are "table_code", "meta_code", "meta_name", "meta_cn_name", "meta_type", "meta_len", "meta_constraint", "meta_value_space", respectively.
The first step, by converting metadata of the committee table into json format;
secondly, obtaining json character strings corresponding to each piece of data by using a json.stringing (metaJson) function;
thirdly, performing an md5 encryption algorithm on the json string to obtain an md5 encrypted string, for example:
as shown in fig. 3, the json string is expressed by the function of Var md5 str=md 5 (metaJsonStr), and the corresponding md5 encrypted string is obtained as:
md5Str = F5B89BEC77BD75374AED6F13BFD8798D
fourth, the metadata json string (data) of the committee table and the encrypted string (tx_id) obtained by the corresponding MD5 encryption algorithm are added with the table name (table_name), the associated description (desc), which metadata information on the block is changed from (update_from), the current metadata version (version). Together, these information form metadata information (i.e., a transaction information in the block) on the block, the structure of which is shown in fig. 4. table_name is defined as the table name described by the metadata; desc is defined as a description of metadata; data is defined as detailed data of metadata, and is stored in a json character string mode; tx_id is a character string after encrypting the metadata MD5, and is also a unique identifier of the metadata on the block; update_from is metadata tx_id before update, which can be used to find metadata information address before update; version is Version information of current metadata.
Preferably, each time metadata information is newly added to the link, update_from is null, and each time metadata information on the link is changed, update_from stores metadata tx_id before metadata update.
As a preferred solution, after the newly added metadata is added to the blockchain through the first step to the fourth step, the metadata information shown in fig. 2 is added with a tx_id field, and the character string after encrypting the metadata MD5 is saved, that is, the unique identifier of the metadata on the block is saved, and the storage format is shown in fig. 5.
The structure of metadata in a block is shown in fig. 6, the metadata of the committee table is a piece of transaction data in the block, each time the metadata information is changed, new transaction data is formed in the block, a metadata change chain can be formed through update_from, and the metadata information on the chain can be accessed through tx_id by using a chain code under the chain. If the metadata of the TX02 is to be accessed, calling the chain code get method of fabric, and inputting tx_id=md-02 as a parameter, the metadata information in the TX02 can be queried out from the chain.
When the organization using the metadata needs to verify the acquired metadata, the specific method is as follows:
if the metadata information is not successfully obtained on the chain through tx_id, the metadata under the chain is tampered, if the metadata information is successfully obtained, the md5 encrypted character string of the metadata under the line is calculated according to the 1, 2 and 3 steps of metadata initialization in the previous block, and the metadata stored under the line is compared, if the metadata are not tampered, otherwise, the metadata information can be used safely.
As a preferred solution, the present invention further includes maintenance of metadata in the block, where the metadata maintenance is mainly divided into three steps:
1) Preparation of data
2) Achieving on-chain consensus
3) Under-link data synchronization modification
The length of the committee responsibility field (meta_len) in the metadata of the committee table is changed from 200 to 1000, and the modification maintenance process is as follows:
1) Preparation of data
a) Found the md5 string to change the metadata, i.e. tx_id, found here is:
the F5B89BEC77BD75374AED6F13BFD8798D, tx_id will be used in the update_from of the new on-chain metadata transaction information.
b) The modified metadata information is converted into an in-chain data structure according to the metadata uplink initialization process, as shown in fig. 7.
2) Achieving on-chain consensus
When the organization initiates the change of the metadata on the chain, the mechanism of the block on the chain inquires whether other endorsement organizations allow the modification, and only after meeting the conditions allowed in the endorsement policy, the data is broadcast to each billing node through the ordering node, and the billing node puts the received data into the block, and the process is shown in fig. 8.
The flow of the specific steps is shown in fig. 9, and the steps include:
c1, constructing an organization channel, wherein the organization channel comprises a plurality of organization nodes, the organization nodes are in one-to-one correspondence with the organization using the metadata in the data standard, and the organization is permitted to initiate a metadata modification request in the organization channel;
c2, one of the organization nodes initiates a request for modifying metadata and constructs a modification proposal;
the endorsement node in the organization channel verifies the modification proposal according to the content of the modification proposal and the construction information of the organization channel, and when the verification is passed, a transaction result is generated;
c4, generating proposal response according to the transaction result and the signature of the endorsement node;
c5, judging whether the proposal response meets a preset endorsement strategy, and if so, packaging the modified proposal into blocks according to the time sequence;
c6, each organization node verifies the modification proposal in the block, and if the modification proposal in the block is unchanged, the transaction mark of the block is valid;
c7, when the transaction mark of the block is valid, modifying metadata on the chain.
Taking fig. 8 as an example, the process of implementing on-chain audit and metadata change by the federation chain is specifically described as follows:
2.1, assumption conditions:
1) A channel MDChannel has been provided that operates normally with organizations org1, org2, org3, org4, org5, respectively, corresponding to nodes peerA, peerB, peerC, peerD, peerE, and 5 organizations have all been registered and completed using the organization's CA and taken up the encrypted material for use in validating the identity in the network.
2) The chain code MDC (MDCircuit code) for modifying the original data on the chain is installed on the peerA-peerE to finish initialization and is approved by the five organizations, the chain code MDC defines a method for modifying the metadata, and an endorsement strategy is also set by the chain code, wherein the strategy is that each time the metadata modification is signed by nodes of the five organizations.
3) Rights definition: org1 and org2 may initiate metadata change requests, org3, org4, org5 may only be viewed.
4) The request for modifying the metadata triggers the modification of the metadata by the chain code MDChiancode only if all 5 organizations agree.
2.2, organization org1 initiates a request to modify metadata
The organization org1 sends a metadata modification request. The request will reach peerA, peerB, peerC, peerD, peerE. Then, a modification proposal is constructed. The proposal is a request to invoke a chain code method with certain input parameters. The effect of the request is to modify the metadata on the chain code.
2.3 endorsement node verifies the signature and performs the transaction
The endorsement nodes verify (1) that the format of the proposal is complete, (2) that the proposal has not been submitted before (3) that the verification signature is valid (using MSP), (4) that the initiator (org 1 in this example) has the right to perform the operation on the channel (that is, each endorsement node ensures that the initiator meets the channel Writers policy). The endorsement node inputs the proposal as a parameter of the invoked chain code function. The chain code is then executed in accordance with the current state database, generating a transaction result including a response value, a write set (i.e., a key-value pair representing metadata to be updated). But the ledger is not updated. These values, along with the signature of the endorsing node, are returned to the SDK as a "proposal response," which the SDK parses for the application.
2.4 checking proposal response, broadcast to ordering service
The application verifies the signature of the endorsement node and compares these modified proposal responses to determine if they are identical, if the specified endorsement policy is met (i.e., the peerA-peerE all endorse). And after the condition is met, the modification proposal is given to the sequencing service, the sequencing service receives the proposal, and the proposal is sequenced according to time and packaged into blocks.
2.5, validating and submitting transactions
The packaged blocks of the ordering service are "sent" to all the Peer nodes on the channel. The modification proposal within the block is validated to ensure that the endorsement policy is satisfied and to ensure that there is no change in the ledger state of the variables in the reading set since the proposal generation in step 3 was performed. If there is no change, the transactions in the block will be marked as valid.
2.6 modifying metadata on a chain
Each Peer node appends a block to the chain of channels and for each active modification, the write set is committed to the current state database. The system will issue an event informing the client application that the metadata modification has been attached unalterably to the chain and will also inform the transaction verification that the result is valid.
In the above manner, the multiparty common maintenance management standard metadata is realized, and each time the metadata is modified, the modification process is recorded on the chain.
1) Under-link data synchronization modification
After the modification of the on-chain data is completed, the fabric sends a result message to the under-chain, if the modification is successful, the under-chain data is modified together, and the tx_id is changed into the tx_id of the latest version on the chain, for example, the tx_id is changed from
F5B89BEC77BD75374AED6F13BFD8798D
Instead of
B19542B9C3A8D9EAD40401787415A653。
The foregoing description is only of the preferred embodiments of the present invention and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention are included in the protection scope of the present invention.
Claims (8)
1. A blockchain-based data standard management method, comprising the steps of:
A. when metadata is created, uploading metadata information to a blockchain, and acquiring unique identification codes of each piece of metadata information;
B. when metadata in a data standard is called, verifying on a blockchain is carried out on the acquired metadata according to the unique identification code, and determining whether the acquired metadata is tampered or not;
the step A specifically comprises the following steps:
firstly, converting original metadata into a target format to obtain metadata in the target format;
secondly, operating the metadata of the target formats to obtain character strings corresponding to the metadata of each target format;
thirdly, encrypting the character string to obtain an encrypted character string;
fourth, the character string, the encryption character string corresponding to the character string, the table name, the related description, the information source before modification and the current metadata version are combined into metadata information on a blockchain, and the encryption character string corresponding to the character string is a unique identification code of the metadata information;
the step B specifically comprises the following steps:
searching an encrypted character string in the metadata under the chain when acquiring the metadata under the chain;
searching whether corresponding on-chain metadata exists on the blockchain through the encryption character string, if so, obtaining the metadata under the chain without tampering, and if not, obtaining the metadata under the chain with tampering;
further comprises: the method for maintaining the metadata in the block comprises the following steps: 1) Preparing data; 2) Achieving the consensus on the chain; 3) The data under the chain is synchronously changed.
2. The method for managing blockchain-based data standard of claim 1, wherein the preparing of the data specifically comprises the steps of:
finding an encrypted character string before metadata change which needs to be changed;
according to the method of the step A, the changed metadata information is converted into an on-chain data structure, and the obtained changed metadata information is obtained;
and adding the encryption character string before modification into a field of 'information source before modification' in the metadata information after modification.
3. The method of claim 2, wherein the step of achieving the link consensus comprises:
c1, constructing an organization channel, wherein the organization channel comprises a plurality of organization nodes, the organization nodes are in one-to-one correspondence with metadata organization in the usage data standard, and the metadata organization is permitted to initiate a metadata modification request in the organization channel;
c2, one organization node initiates a request for modifying metadata in the data standard, and constructs a modification proposal;
the endorsement node in the organization channel verifies the modification proposal according to the content of the modification proposal and the construction information of the organization channel, and when the verification is passed, a transaction result is generated;
c4, generating proposal response according to the transaction result and the signature of the endorsement node;
judging whether the proposal response meets a preset endorsement strategy or not, and if so, packaging the modified proposal into blocks according to a time sequence;
c6, each organization node verifies the modification proposal in the block, and if the modification proposal in the block is unchanged, the transaction label of the block is valid;
c7, when the transaction flag of the block is valid, modifying metadata on the chain.
4. A blockchain-based data standard management method as in claim 3 wherein the organization channel and the organization node satisfy the following conditions:
1) The organization node completes the registration and registration of the metadata standard organization and acquires the encrypted material for confirming the identity;
2) The blockchain of the modified metadata sets an endorsement policy and defines a method for modifying the metadata;
3) The organization node initiating the request for modifying the metadata has the authority to initiate the modification of the metadata;
4) And under the condition that all organization nodes on the organization channel agree, the blockchain can be triggered to modify the metadata.
5. The method for managing blockchain-based data standards as in claim 3, wherein in step C3, the verification of the modification proposal is performed, and the verification includes:
1) Whether the format of the modification proposal is complete; 2) Whether the modification proposal is submitted for the first time; 3) Verifying whether the signature of the endorsement node is valid; 4) Whether the organization node constructing the modification proposal has the authority to initiate modification metadata.
6. The blockchain-based data standard management method of claim 3, wherein the transaction result includes a response value and a write set, the write set being a key-value pair of metadata to be modified.
7. A blockchain-based data standard management method as in claim 3, wherein the pre-endorsement policy is that all nodes in the organization channel are endorsed.
8. A blockchain-based data standard management system comprising at least one processor, and a memory communicatively coupled to the at least one processor; the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011303107.5A CN112417517B (en) | 2020-11-19 | 2020-11-19 | Data standard management method based on block chain |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011303107.5A CN112417517B (en) | 2020-11-19 | 2020-11-19 | Data standard management method based on block chain |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112417517A CN112417517A (en) | 2021-02-26 |
| CN112417517B true CN112417517B (en) | 2023-11-28 |
Family
ID=74773123
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011303107.5A Active CN112417517B (en) | 2020-11-19 | 2020-11-19 | Data standard management method based on block chain |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112417517B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113469713A (en) * | 2021-07-21 | 2021-10-01 | 贵州大学 | Block chain-based food data anti-counterfeiting tracing method and system |
| CN113469712A (en) * | 2021-07-21 | 2021-10-01 | 贵州大学 | Food multi-source heterogeneous data integration method and system based on block chain technology |
| CN116596197A (en) * | 2023-07-18 | 2023-08-15 | 青岛博什兰物联技术有限公司 | Standard public service platform based on block chain technology |
| CN117271528B (en) * | 2023-11-16 | 2024-02-06 | 佳瑛科技有限公司 | Table key character storage method and system based on block chain technology |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017136879A1 (en) * | 2016-02-08 | 2017-08-17 | Moloney Lindsay | A system and method for document information authenticity verification |
| CN108664770A (en) * | 2018-05-22 | 2018-10-16 | 上海七印信息科技有限公司 | There are methods of proof for a kind of high confidence level based on block chain technology |
| CN110691078A (en) * | 2019-09-25 | 2020-01-14 | 东北大学 | Block chain-based data dynamic reliability verification method |
| CN110765205A (en) * | 2019-10-12 | 2020-02-07 | 中思博安科技（北京）有限公司 | Block chain based metadata management method, system and computer storage medium |
| CN111563130A (en) * | 2020-07-15 | 2020-08-21 | 成都无右区块链科技有限公司 | Data credible data management method and system based on block chain technology |
-
2020
- 2020-11-19 CN CN202011303107.5A patent/CN112417517B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017136879A1 (en) * | 2016-02-08 | 2017-08-17 | Moloney Lindsay | A system and method for document information authenticity verification |
| CN108664770A (en) * | 2018-05-22 | 2018-10-16 | 上海七印信息科技有限公司 | There are methods of proof for a kind of high confidence level based on block chain technology |
| CN110691078A (en) * | 2019-09-25 | 2020-01-14 | 东北大学 | Block chain-based data dynamic reliability verification method |
| CN110765205A (en) * | 2019-10-12 | 2020-02-07 | 中思博安科技（北京）有限公司 | Block chain based metadata management method, system and computer storage medium |
| CN111563130A (en) * | 2020-07-15 | 2020-08-21 | 成都无右区块链科技有限公司 | Data credible data management method and system based on block chain technology |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112417517A (en) | 2021-02-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112417517B (en) | Data standard management method based on block chain | |
| US11764950B2 (en) | System or method to implement right to be forgotten on metadata driven blockchain using shared secrets and consensus on read | |
| US11869012B2 (en) | Systems, devices, and methods for DLT-based data management platforms and data products | |
| US11360963B2 (en) | Tracking and verification of physical assets | |
| US10904009B2 (en) | Blockchain implementing delta storage | |
| US11201747B2 (en) | Federated data management between partner systems | |
| US12010213B2 (en) | Pruning entries in tamper-evident data stores | |
| CN112835612A (en) | Electronic document version management method and device based on block chain | |
| CN111429995B (en) | Vaccine tracing method and system based on alliance chain | |
| US11240003B2 (en) | Consent-based data management | |
| US11880383B2 (en) | Federated data management between partner systems | |
| US11379472B2 (en) | Schema-based pruning of blockchain data | |
| US11196564B2 (en) | Hierarchical distributed ledger | |
| US11455403B2 (en) | Privacy-preserving document sharing | |
| US20200389318A1 (en) | Metadata-based endorsement | |
| CN111340483A (en) | Data management method based on block chain and related equipment | |
| US11354425B2 (en) | Privacy-preserving document sharing | |
| CN114612115A (en) | Industrial product traceability information storage method, traceability method and device based on block chain | |
| US11811865B2 (en) | Blockchain declarative descriptor for cross-network communication | |
| US11379474B2 (en) | Computation of containment relationships | |
| CN116596551A (en) | Supply chain product tracing method based on block chain, storage medium and electronic equipment | |
| WO2022116753A1 (en) | Automated merge of dlt networks | |
| Cui et al. | Enabling Efficient, Verifiable, and Secure Conjunctive Keyword Search in Hybrid-Storage Blockchains | |
| Chen et al. | Ladder: A Blockchain Model of Low-Overhead Storage | |
| CN112016118A (en) | Anonymous database rating updates |
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 |