Data quality lifecycle management method and processor based on blockchain

Abstract

The present application relates to the field of blockchain technology, and specifically to a data quality lifecycle management method, processor, storage medium and computer program product based on blockchain. The method includes: the smart contract management center obtains the account data of the business account and the node data of the process node where the transaction occurs; when the smart contract management center determines that the account data complies with the preset account rules and the node data complies with the preset business rules, the smart contract management center sends a qualified inspection notification to the process node; the process node synchronizes the node data to the accounting node according to the qualified inspection notification; the accounting node generates a new transaction record according to the node data, and synchronizes the transaction record to other nodes of the blockchain; based on the transaction record initiated by the business account, a transaction record tree with the business account as the initial point is generated to manage the lifecycle data of the business account. The above scheme realizes the full process supervision of the full life cycle of business object data.

Description

Technical Field

[0001] The present application relates to the field of blockchain technology, and specifically to a blockchain-based data quality lifecycle management method, processor, storage medium, and computer program product. Background Art

[0002] The digital economy is the direction of future development and a new driving force and new opportunity for economic growth. As an important focus of the development of the digital economy, the necessity and urgency of enterprise digital transformation have been increasingly highlighted and have been implemented and promoted in more and more enterprises.

[0003] Big data projects have a characteristic, that is, they are all centered on data. Data will serve as the cornerstone for generating business value and achieving business goals, so the quality of data becomes an extremely important factor in such projects. At present, because data quality factors are not considered at the beginning of the project, they are not discovered until the end of the project implementation, resulting in the risk of project failure caused by data quality problems. Summary of the invention

[0004] The purpose of the embodiments of the present application is to provide a blockchain-based data quality lifecycle management method, processor, storage medium and computer program product for managing data quality based on a blockchain platform.

[0005] In order to achieve the above purpose, an embodiment of the present invention provides a data quality lifecycle management method based on blockchain, the method comprising:

[0006] The smart contract management center obtains the account data of the business account and the node data of the process node where the transaction occurs;

[0007] When the smart contract management center determines that the account data complies with the preset account rules and the node data complies with the preset business rules, the smart contract management center sends a qualified inspection notice to the process node;

[0008] The process node synchronizes the node data to the accounting node according to the inspection pass notification;

[0009] The accounting node generates new transaction records based on the node data and synchronizes the transaction records to other nodes in the blockchain;

[0010] A transaction record tree with the business account as the starting point is generated based on the transaction records initiated by the business account to manage the life cycle data of the business account.

[0011] In one embodiment of the present application, the node data includes the hash value of the current process node where the transaction occurs, and the hash value of the current node is determined based on the first hash value of the previous process node of the current process node and the second hash value corresponding to the data reported by the current process node when the transaction occurs.

[0012] In one embodiment of the present application, when the previous process node is a process node corresponding to the first transaction of a business account, the first hash value is a hash value determined based on the account data.

[0013] In one embodiment of the present application, when the number of business process nodes supported by the node data exceeds a preset threshold, the process node corresponding to the node data is determined to be a forked transaction node; wherein the hash value of the forked transaction node is determined based on the node hash value of the forked transaction node and a second hash value, and the second hash value is determined based on the data reported by the current process node when a forked transaction occurs, or is determined based on data generated after processing the reported data.

[0014] In one embodiment of the present application, the business system obtains identification information of the account to be created and sends the identification information to the accounting node; the accounting node creates a corresponding business account according to the identification information and synchronizes the data associated with the business account to the synchronization node.

[0015] In one embodiment of the present application, the accounting node generates a new transaction record based on the node data, including: when the node data is the process node corresponding to the first transaction of the business account, the transaction record corresponding to the node data is determined as the initial transaction record; when the node data is not the process node corresponding to the first transaction of the business account, the transaction record of the node data is determined according to the order of occurrence of the node data.

[0016] In one embodiment of the present application, the method also includes: after generating a transaction record tree with the business account as the initial point based on the transaction records initiated by the business account, classifying the business accounts; determining the business accounts included in each classification and the transaction record tree corresponding to each business account based on the classification results.

[0017] A second aspect of the present application provides a processor configured to execute any one of the above-mentioned blockchain-based data quality lifecycle management methods.

[0018] The third aspect of the present application provides a machine-readable storage medium having instructions stored thereon, which, when executed by a processor, configures the processor to execute any of the above-mentioned blockchain-based data quality lifecycle management methods.

[0019] The fourth aspect of the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the blockchain-based data quality lifecycle management method according to any of the above items.

[0020] Through the above technical solution, based on the blockchain platform, the consent management of business rules and the automatic execution of rules are realized through smart contracts. The transaction record tree method is used to realize the full process record of data assets in different versions of data and data products managed in each business node, and the full process supervision of the entire life cycle of business object data collection, updating, processing and maintenance is realized, thereby ensuring the quality of data.

[0021] Other features and advantages of the embodiments of the present invention will be described in detail in the subsequent detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The accompanying drawings are used to provide a further understanding of the embodiments of the present invention and constitute a part of the specification. Together with the following specific implementations, they are used to explain the embodiments of the present invention, but do not constitute a limitation on the embodiments of the present invention. In the accompanying drawings:

[0023] Figure 1 The flowchart of the data quality lifecycle management method based on blockchain according to an embodiment of the present application is schematically shown;

[0024] Figure 2 A schematic diagram of a transaction record tree in a data quality lifecycle management method based on blockchain according to an embodiment of the present application is schematically shown;

[0025] Figure 3 A schematic diagram showing the principle diagram of generating transaction records of various transaction types in a data quality lifecycle management method based on blockchain according to an embodiment of the present application;

[0026] Figure 4 An example diagram of a data quality lifecycle management method based on blockchain according to an embodiment of the present application is schematically shown;

[0027] Figure 5 Another example diagram of a data quality lifecycle management method based on blockchain according to an embodiment of the present application is schematically shown;

[0028] Figure 6 The internal structure diagram of a computer device according to an embodiment of the present application is schematically shown. DETAILED DESCRIPTION

[0029] The specific implementation of the present application is described in detail below in conjunction with the accompanying drawings. It should be understood that the specific implementation described here is only used to illustrate and explain the present application, and is not used to limit the present application.

[0030] It should be noted that if the embodiments of the present application involve directional indications (such as up, down, left, right, front, back...), the directional indications are only used to explain the relative position relationship, movement status, etc. between the components under a certain specific posture (as shown in the accompanying drawings). If the specific posture changes, the directional indication will also change accordingly.

[0031] In addition, if there are descriptions involving "first", "second", etc. in the embodiments of the present application, the descriptions of "first", "second", etc. are only used for descriptive purposes and cannot be understood as indicating or suggesting their relative importance or implicitly indicating the number of technical features indicated. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In addition, the technical solutions between the various embodiments can be combined with each other, but they must be based on the ability of ordinary technicians in the field to implement them. When the combination of technical solutions is contradictory or cannot be implemented, it should be deemed that such combination of technical solutions does not exist and is not within the scope of protection required by this application.

[0032] like Figure 1 As shown, a schematic diagram of the process of the data quality lifecycle management method based on blockchain according to an embodiment of the present application is shown. Figure 1 As shown, in one embodiment of the present application, a data quality lifecycle management method based on blockchain is provided, including the following steps:

[0033] Step 101, the smart contract management center obtains the account data of the business account and the node data of the process node where the transaction occurs;

[0034] Step 102, when the smart contract management center determines that the account data complies with the preset account rules and the node data complies with the preset business rules, the smart contract management center sends a qualified inspection notification to the process node;

[0035] Step 103, the process node synchronizes the node data to the accounting node according to the inspection pass notification;

[0036] Step 104: the accounting node generates a new transaction record based on the node data and synchronizes the transaction record to other nodes of the blockchain;

[0037] Step 105 , generating a transaction record tree with the business account as the initial point according to the transaction records initiated by the business account, so as to manage the life cycle data of the business account.

[0038] The blockchain platform may include a smart contract management center, which may set preset account rules, which are rules set for the creation of business accounts to control the quality of account data. The smart contract management center may also set preset business rules, which are data quality control rules set for node data generated in each process node in the business account that can generate transactions.

[0039] The Smart Contract Management Center can obtain the account data of the business account and the node data generated by the process node when the business account has a transaction. When the Smart Contract Management Center determines that the obtained account data complies with the preset account rules set by the Smart Contract Management Center, and the obtained node data complies with the preset business rules set by the Smart Contract Management Center, the Smart Contract Management Center can send a qualified inspection notification to the process node where the business object generates the transaction.

[0040] The blockchain platform may also include accounting nodes and other nodes. After receiving the inspection pass notification sent by the smart contract center, the process node can synchronize the node data generated by the process node to the accounting node according to the inspection pass notification. The accounting node can generate new transaction records based on the node data, and synchronize the generated new transaction records to other nodes included in the blockchain according to the management principles of the blockchain, where the other nodes can be synchronization nodes.

[0041] The processor can generate a transaction record tree with the business account as the starting point based on the transaction records initiated by the business account to manage the life cycle data of the business account. Figure 2 The transaction record tree shown in the figure takes the business object, that is, the business account, as the initial point. The transaction node formed by the data attributes generated by the business account initialization is named transaction record 1. Each time an attribute data is added or modified in the subsequent process node, a transaction is generated. The transaction record node is incremented by 1, and the subsequent transactions are analogous. When data processing is performed based on the data of a transaction node (such as transaction record 1) of the business account, the transaction node corresponding to the generated new data asset undergoes transaction fork processing. Figure 2 As shown, the transaction data generated by data processing based on transaction record 1 is named transaction record 1.1. The transaction data generated by data processing based on transaction record 1.2 is named transaction record 1.2.1. The normal transaction records of the business account and the forked transaction records generated by each node constitute a transaction record tree with the business account as the starting point. The transaction tree is continuously maintained throughout the life cycle of the business object, thereby forming a tracking of data operations and maintenance throughout the life cycle of the business object.

[0042] In one implementation, the node data includes the hash value of the current process node where the transaction occurs, and the hash value of the current node is determined based on the first hash value of the previous process node of the current process node and the second hash value corresponding to the data reported by the current process node when the transaction occurs.

[0043] The processor can determine the first hash value of the previous process node of the current process node where the transaction occurs, and obtain the data reported by the current process node when the transaction occurs. The processor can perform a hash operation on the reported data to determine the second hash value. The node data of the process node can include the current node hash value of the current process node where the transaction occurs, and the current node hash value is a value obtained by performing a hash operation on the first hash value and the second hash value.

[0044] In one embodiment, when the previous process node is a process node corresponding to the first transaction of the business account, the first hash value is a hash value determined according to the account data.

[0045] When the previous process node is a process node corresponding to creating a business account and performing a first transaction, the processor can obtain account data of the business account and determine the first hash value through the account data.

[0046] In one embodiment, when the number of business process nodes supported by the node data exceeds a preset threshold, the process node corresponding to the node data is determined to be a forked transaction node; wherein the hash value of the forked transaction node is determined based on the node hash value of the forked transaction node and a second hash value, and the second hash value is determined based on the data reported by the current process node when a forked transaction occurs, or is determined based on data generated after processing the reported data.

[0047] When the number of business process nodes supported by the node data exceeds a preset threshold, the processor can generate a new node based on the process node, and determine that the process node corresponding to the node data is a forked transaction node. The hash value of the forked transaction node is a hash value obtained by hashing the hash value of the forked transaction node and the second hash value. Among them, the second hash value is determined based on the data reported by the current process node when a forked transaction occurs or based on the data generated after the reported data is processed. The processor can perform a hash operation on the data reported when a forked transaction occurs or the data generated after the reported data is processed to obtain a second hash value.

[0048] In one embodiment, Figure 3As shown, a schematic diagram of the generation principle of transaction records of various transaction types in the data quality lifecycle management method based on blockchain is shown. Process node 1 is the process node corresponding to the first transaction of the business account. At this time, the processor can determine the account hash value based on the account data, and the processor can perform a hash operation based on the data reported by process node 1 to obtain the hash value of the newly added data of node 1 corresponding to the data reported by process node 1. The processor can obtain the hash value of the first transaction record based on the account hash value and the hash value of the newly added data of node 1.

[0049] Process node 2 is a normal transaction that is not the first time, such as Figure 3 As shown, the normal transaction corresponding to process node 2 is the second transaction record. The processor can perform a hash operation on the data reported by process node 2 to obtain the hash value of the newly added data of node 2 corresponding to the data reported by process node 2. The processor can obtain the hash value of the second transaction record corresponding to process node 2 based on the hash value of the first transaction record and the hash value of the newly added data of node 2. Similarly, Figure 3 As shown, the journey transaction corresponding to process node 3 is the third transaction record. The processor can perform a hash operation on the data reported by process node 3 to obtain the hash value of the newly added data of node 3 corresponding to the data reported by process node 3. The processor can obtain the hash value of the third transaction record corresponding to process node 3 based on the hash value of the second transaction record corresponding to process node 2 and the hash value of the newly added data of node 3.

[0050] When the number of business process nodes supported by the node data exceeds a preset threshold, the processor can determine a forked transaction node, and the processor can set the preset threshold to 2. When the node data supports two or more business process nodes, a forked transaction node can be generated based on the transaction node. Figure 3 As shown, the transaction node corresponding to process node 2 generates an additional transaction node, and the additional transaction node is a forked transaction node corresponding to process node 4. The processor can perform a hash operation on the data generated by the data processing of process node 4 to obtain the hash value of the newly added data of node 4 corresponding to the data processing of process node 4. The processor can obtain the hash value of the forked transaction record corresponding to process node 4 based on the hash value of the second transaction record corresponding to process node 2 and the hash value of the newly added data of node 4.

[0051] In one embodiment, the business system obtains identification information of the account to be created and sends the identification information to the accounting node; the accounting node creates a corresponding business account according to the identification information and synchronizes data associated with the business account to the synchronization node.

[0052] The business system can obtain the identification information of the account to be created and send the identification information of the account to be created to the accounting node. The accounting node can create a corresponding business account based on the identification information and synchronize the data associated with the business account to the synchronization node.

[0053] In one embodiment, the accounting node generates a new transaction record based on the node data, including: when the node data is the process node corresponding to the first transaction of the business account, the transaction record corresponding to the node data is determined as the initial transaction record; when the node data is not the process node corresponding to the first transaction of the business account, the transaction record of the node data is determined according to the order of occurrence of the node data.

[0054] The blockchain platform may include an accounting node, and the accounting node may generate a new transaction record based on the node data. When the node data is the node data of the process node corresponding to the first transaction of the business account, the processor may determine the transaction record corresponding to the node data as the initial transaction record. When the node data is not the node data of the process node corresponding to the first transaction of the business account, the processor may determine the transaction record of the node data based on the order in which the node data occurs.

[0055] In one embodiment, after generating a transaction record tree with the business account as the initial point based on the transaction records initiated by the business account, the business account is classified; the business accounts included in each classification and the transaction record tree corresponding to each business account are determined based on the classification results.

[0056] After the processor generates a transaction tree with the business account as the initial point based on the transaction records initiated by the business account, the processor can classify the business account and determine the business accounts included in each classification and the transaction record tree corresponding to each business account based on the classification results. For example, based on the transaction record tree with the business account as the core, the business account is classified. Assuming that the business account is classified into business fields and subject fields, the processor can determine the business accounts included in different fields and the transaction record tree corresponding to each business account.

[0057] In one embodiment, a processor is provided, configured to execute any one of the above-mentioned blockchain-based data quality lifecycle management methods.

[0058] The present application scheme is a data quality lifecycle management method based on blockchain. The blockchain platform may include a smart contract management center, an accounting node, and a synchronization node. The business system may obtain the identification information of the account to be created, and send the identification information of the account to be created to the accounting node. The accounting node may create a corresponding business account based on the identification information, and synchronize the data associated with the business account to the synchronization node.

[0059] The Smart Contract Management Center can set preset account rules, which are rules set for the creation of business accounts to control the quality of account data. The Smart Contract Management Center can also set preset business rules, which are data quality control rules set for node data generated in each process node in the business account that can generate transactions.

[0060] The Smart Contract Management Center can obtain the account data of the business account and the node data generated by the process node when the business account has a transaction. When the Smart Contract Management Center determines that the acquired account data complies with the preset account rules set by the Smart Contract Management Center, and the acquired node data complies with the preset business rules set by the Smart Contract Management Center, the Smart Contract Management Center can send a qualified inspection notice to the process node where the business object generates the transaction. After receiving the qualified inspection notice sent by the Smart Contract Center, the process node can synchronize the node data generated by the process node to the accounting node according to the qualified inspection notice.

[0061] The accounting node can generate a new transaction record based on the node data. When the node data is the node data of the process node corresponding to the first transaction of the business account, the processor can determine the transaction record corresponding to the node data as the initial transaction record. In the case where the node data is not the node data of the process node corresponding to the first transaction of the business account, the processor can determine the transaction record of the node data according to the order of occurrence of the node data. The accounting node can generate a new transaction record based on the node data, and synchronize the generated new transaction record to other nodes included in the blockchain platform according to the management principles of the blockchain, where the other nodes can be synchronization nodes.

[0062] Specifically, for example Figure 4 As shown, the blockchain platform includes a smart contract management center, accounting nodes and synchronization nodes. The business system can obtain a business account based on the hash value of the business object's business information. When a business object undergoes a transaction, a new process node can be generated. The smart contract management center can set business rules. The business rules are data quality control rules set for the node data generated in each process node in the business account that can generate transactions. The smart contract management center can send a qualified inspection notice to the process node where the business object generates a transaction. After receiving the qualified inspection notice sent by the smart contract center, the process node can synchronize the node data generated by the process node to the accounting node according to the qualified inspection notice. As shown Figure 4In the process node 1 and process node 2, the accounting node can establish a transaction record based on the node data generated by the process node. The transaction record 1 corresponds to process node 1, and the transaction record 2 corresponds to process node 2. Transaction record 1 can be obtained based on the hash value of the business account and the node data of process node 1, that is, the hash value of the data reported by process node 1 at this node. Transaction record 2 can be obtained based on the hash value of transaction record 1 and the node data of process node 2, that is, the hash value of the data reported by process node 2 at this node. After the accounting node generates a transaction record based on the node data, it can synchronize the generated transaction record to the synchronization node of the blockchain platform according to the management principles of the blockchain.

[0063] The transaction record consists of the previous node hash value, the newly added data hash value, and the current node hash value. The transaction records are connected through the node hash values ​​to form a transaction record chain with the business object as the starting point, that is, the previous node hash value of each transaction record is the current node hash value of the previous transaction record. For example, Figure 5 As shown, the business object is taken as the starting point, where the business object is the business account. The first transaction record can be obtained through the data of the business account, that is, the "upper node hash value" in transaction record 1. Then, the newly added data hash value of transaction record 1 is obtained after hashing the data reported in transaction record 1. The upper node hash value in transaction record 1 (that is, the hash value obtained through the business account data) and the newly added data hash value of transaction record 1 are hashed to obtain the current node hash value of transaction record 1. Transaction record 1 is the previous node of transaction record 2, so the "current node hash value" in transaction record 1 is the "upper node hash value" in transaction record 2. Then, the hash value of the newly added data in transaction record 2 is obtained by hashing the data reported in transaction record 2. The upper node hash value in transaction record 2 (that is, the "current node hash value" in transaction record 1) and the newly added data hash value of transaction record 2 are hashed to obtain the current node hash value of transaction record 2.

[0064] The accounting node can generate a new transaction record based on the node data. When the account conducts the first transaction, the processor can obtain the account data of the business account, determine the first hash value through the account data, and obtain the data reported by the process node corresponding to the first transaction when the transaction occurs, perform a hash operation on the reported data, and thus obtain the second hash value, which is the hash value of the newly added data. The first hash value and the second hash value are combined to perform a hash operation to obtain the hash value of the first transaction. When the account conducts a normal transaction, the processor can obtain the hash value of the previous process node of the current process node where the transaction occurs, and determine the hash value of the previous process node as the first hash value, perform a hash operation on the data reported this time to determine the hash value of the newly added data, and determine the hash value of the newly added data as the second hash value. The hash value of this transaction is obtained by performing a hash operation based on the first hash value and the second hash value. When the number of business process nodes supported by the node data exceeds the preset threshold, the processor can generate a new node based on the process node, and determine the process node corresponding to the node data as a forked transaction node. The processor can use the hash value of the node where the forked transaction occurs as the first hash value, perform a hash operation on the data reported when the forked transaction occurs or the data generated after the reported data is processed, and obtain the newly added data hash value as the second hash value. The hash value of the current forked transaction is obtained by performing a hash operation on the first hash value and the second hash value.

[0065] like Figure 3 As shown, a schematic diagram of the generation principle of transaction records of various transaction types in the data quality lifecycle management method based on blockchain is shown. Process node 1 is the process node corresponding to the first transaction of the business account. At this time, the processor can determine the account hash value based on the account data, and the processor can perform a hash operation based on the data reported by process node 1 to obtain the hash value of the newly added data of node 1 corresponding to the data reported by process node 1. The processor can obtain the hash value of the first transaction record based on the account hash value and the hash value of the newly added data of node 1.

[0066] Process node 2 is a normal transaction that is not the first time, such as Figure 3 As shown, the normal transaction corresponding to process node 2 is the second transaction record. The processor can perform a hash operation on the data reported by process node 2 to obtain the hash value of the newly added data of node 2 corresponding to the data reported by process node 2. The processor can obtain the hash value of the second transaction record corresponding to process node 2 based on the hash value of the first transaction record and the hash value of the newly added data of node 2. Similarly, Figure 3As shown, the journey transaction corresponding to process node 3 is the third transaction record. The processor can perform a hash operation on the data reported by process node 3 to obtain the hash value of the newly added data of node 3 corresponding to the data reported by process node 3. The processor can obtain the hash value of the third transaction record corresponding to process node 3 based on the hash value of the second transaction record corresponding to process node 2 and the hash value of the newly added data of node 3.

[0067] When the number of business process nodes supported by the node data exceeds a preset threshold, the processor can determine a forked transaction node, and the processor can set the preset threshold to 2. When the node data supports two or more business process nodes, a forked transaction node can be generated based on the transaction node. Figure 3 As shown, the transaction node corresponding to process node 2 generates an additional transaction node, and the additional transaction node is a forked transaction node corresponding to process node 4. The processor can perform a hash operation on the data generated by the data processing of process node 4 to obtain the hash value of the newly added data of node 4 corresponding to the data processing of process node 4. The processor can obtain the hash value of the forked transaction record corresponding to process node 4 based on the hash value of the second transaction record corresponding to process node 2 and the hash value of the newly added data of node 4.

[0068] The processor can generate a transaction record tree with the business account as the starting point based on the transaction records initiated by the business account to manage the life cycle data of the business account, for example Figure 2 As shown in the figure, the business object, that is, the business account, is used as the initial point. The transaction node formed by the data attributes generated by the business account initialization is named transaction record 1. Each time an attribute data is added or modified in the subsequent process node, a transaction is generated. The transaction record node is incremented by 1, and the subsequent transactions are analogous. When data processing is performed based on the data of a transaction node (such as transaction record 1) of the business account, the transaction node corresponding to the generated new data asset undergoes transaction fork processing. Figure 2 As shown, the transaction data generated by data processing based on transaction record 1 is named transaction record 1.1. The transaction data generated by data processing based on transaction record 1.2 is named transaction record 1.2.1. The normal transaction records of the business account and the forked transaction records generated by each node constitute a transaction record tree with the business account as the starting point. The transaction tree is continuously maintained throughout the life cycle of the business object, thereby forming a tracking of data operations and maintenance throughout the life cycle of the business object.

[0069] After the processor generates a transaction tree with the business account as the initial point based on the transaction records initiated by the business account, it can classify the business accounts and determine the business accounts included in each classification and the transaction record tree corresponding to each business account based on the classification results.

[0070] Through the above technical solutions, this application is based on the blockchain platform, and realizes the unified management of business rules and the automatic execution of rules through smart contracts, thereby realizing the digitization of rules; the transaction record tree is used to realize the full process record of data assets in different versions of data and data products in each business node, and realize the full process supervision of the collection, update, processing and maintenance of business object data throughout the life cycle. Through blockchain technology, the quality of business object data is managed throughout the life cycle, and the process of business object data quality control is digitized, and data quality control is also realized by blockchain. Each business system runs independently without the need for chaining, thereby minimizing the consumption of hardware resources caused by multiple redundant backups of system resources brought about by chaining. At the same time, based on the blockchain platform, data assets can be traced and tamper-proof.

[0071] In one embodiment, a machine-readable storage medium is provided, on which instructions are stored, and when the instructions are executed by a processor, the processor is configured to execute any one of the above-mentioned blockchain-based data quality lifecycle management methods.

[0072] In one embodiment, a computer program product is provided, including a computer program, which, when executed by a processor, implements any of the above-mentioned blockchain-based data quality lifecycle management methods.

[0073] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.

[0074] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Figure 6 As shown. The computer device includes a processor A01, a network interface A02, a memory (not shown in the figure) and a database (not shown in the figure) connected via a system bus. Among them, the processor A01 of the computer device is used to provide computing and control capabilities. The memory of the computer device includes an internal memory A03 and a non-volatile storage medium A04. The non-volatile storage medium A04 stores an operating system B01, a computer program B02 and a database (not shown in the figure). The internal memory A03 provides an environment for the operation of the operating system B01 and the computer program B02 in the non-volatile storage medium A04. The database of the computer device is used to store relevant data of the business account, as well as the relevant data generated. The network interface A02 of the computer device is used to communicate with an external terminal through a network connection. When the computer program B02 is executed by the processor A01, a data quality lifecycle management method based on blockchain is implemented.

[0075] Figure 1 FIG. 1 is a flowchart of a data quality lifecycle management method based on blockchain in one embodiment. It should be understood that although Figure 1 The steps in the flowchart are shown in sequence as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified in this document, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. Moreover, Figure 1 At least part of the steps may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be executed in turn or alternately with other steps or at least part of the sub-steps or stages of other steps.

[0076] An embodiment of the present invention provides a device, comprising a processor, a memory, and a program stored in the memory and executable on the processor, wherein the processor implements the following steps when executing the program: a smart contract management center obtains account data of a business account and node data of a process node where a transaction occurs; when the smart contract management center determines that the account data complies with preset account rules and the node data complies with preset business rules, the smart contract management center sends a qualified inspection notification to the process node; the process node synchronizes the node data to the accounting node according to the qualified inspection notification; the accounting node generates a new transaction record according to the node data, and synchronizes the transaction record to other nodes of the blockchain; a transaction record tree with the business account as the initial point is generated according to the transaction record initiated by the business account to manage the life cycle data of the business account.

[0077] In one embodiment, the node data includes the hash value of the current process node where the transaction occurs, and the hash value of the current node is determined based on the first hash value of the previous process node of the current process node and the second hash value corresponding to the data reported by the current process node when the transaction occurs.

[0078] In one embodiment, when the previous process node is a process node corresponding to the first transaction of the business account, the first hash value is a hash value determined according to the account data.

[0079] In one embodiment, when the number of business process nodes supported by the node data exceeds a preset threshold, the process node corresponding to the node data is determined to be a forked transaction node; wherein the hash value of the forked transaction node is determined based on the node hash value of the forked transaction node and a second hash value, and the second hash value is determined based on the data reported by the current process node when a forked transaction occurs, or is determined based on data generated after processing the reported data.

[0080] In one embodiment, the business system obtains identification information of the account to be created and sends the identification information to the accounting node; the accounting node creates a corresponding business account according to the identification information and synchronizes data associated with the business account to the synchronization node.

[0081] In one embodiment, the accounting node generates a new transaction record based on the node data, including: when the node data is the process node corresponding to the first transaction of the business account, the transaction record corresponding to the node data is determined as the initial transaction record; when the node data is not the process node corresponding to the first transaction of the business account, the transaction record of the node data is determined according to the order of occurrence of the node data.

[0082] In one embodiment, the method further includes: after generating a transaction record tree with the business account as the initial point based on the transaction records initiated by the business account, classifying the business account; and determining the business accounts included in each classification and the transaction record tree corresponding to each business account based on the classification results.

[0083] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0084] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0085] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0086] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0087] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0088] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0089] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0090] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0091] The above are only embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included within the scope of the claims of the present application.

Claims

1. A data quality lifecycle management method based on blockchain, characterized in that: The method comprises: The smart contract management center obtains the account data of the business account and the node data of the process node where the transaction occurs, wherein the node data includes the hash value of the current process node where the transaction occurs, and the hash value of the current node is determined according to the first hash value of the previous process node of the current process node and the second hash value corresponding to the data reported by the current process node when the transaction occurs; when the number of business process nodes supported by the node data exceeds a preset threshold, the process node corresponding to the node data is determined to be a forked transaction node; wherein the hash value of the forked transaction node is determined according to the hash value of the current node and the second hash value of the forked transaction node, and the second hash value is determined according to the data reported by the current process node when the forked transaction occurs, or is determined according to data generated after processing the reported data; When the smart contract management center determines that the account data complies with the preset account rules and the node data complies with the preset business rules, the smart contract management center sends a qualified inspection notification to the process node; The process node synchronizes the node data to the accounting node according to the inspection pass notification; The accounting node generates a new transaction record according to the node data, and synchronizes the transaction record to other nodes of the blockchain; A transaction record tree with the business account as the initial point is generated according to the transaction records initiated by the business account, so as to manage the life cycle data of the business account.

2. The method according to claim 1, characterized in that When the previous process node is a process node corresponding to the first transaction performed by the business account, the first hash value is a hash value determined according to the account data.

3. The method according to claim 1, characterized in that The method further comprises: The business system obtains the identification information of the account to be created, and sends the identification information to the accounting node; The accounting node creates a corresponding business account according to the identification information, and synchronizes the data associated with the business account to the synchronization node.

4. The method according to claim 1, characterized in that The accounting node generates a new transaction record according to the node data, including: In the case where the node data is a process node corresponding to the first transaction performed by the business account, determining the transaction record corresponding to the node data as an initial transaction record; In the case that the node data is not the process node corresponding to the first transaction performed by the business account, the transaction record of the node data is determined according to the occurrence sequence of the node data.

5. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: After generating a transaction record tree with the business account as the initial point according to the transaction records initiated by the business account, classifying the business account; The business accounts included in each category and the transaction record tree corresponding to each business account are determined based on the classification results.

6. A processor, characterized in that: The method is configured to execute the blockchain-based data quality lifecycle management method according to any one of claims 1 to 5.

7. A machine-readable storage medium having instructions stored thereon, characterized in that: When the instruction is executed by a processor, the processor is configured to perform the blockchain-based data quality lifecycle management method according to any one of claims 1 to 5.

8. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the blockchain-based data quality lifecycle management method is implemented according to any one of claims 1 to 5.

Images