WO2020233351A1 - Blockchain-oriented data management method, apparatus and device, and storage medium - Google Patents

Abstract

Disclosed are a blockchain-oriented data management method, apparatus and device, and a storage medium. The method comprises: receiving a second update request sent by a user, wherein each update request comprises a first state and a second state of to-be-updated data (S101); obtaining to-be-updated data from a preset relational database according to the first state and searching data corresponding to the to-be-updated data from a preset blockchain, wherein the to-be-updated data which is obtained from the relational database is considered as first data, and the data corresponding to the to-be-updated data which is searched from the blockchain is considered as second data (S102); comparing the first data with the second data to determine whether the first data is consistent with the second data (S103); if the first data is not consistent with the second data, determining whether the first data meets a preset data compensation condition according to the first state and the second state (S104); and if the first data meets a preset data compensation condition, performing data compensation on the first data according to the second state (S105). The method can effectively ensure the orderly implementation of business on the chain and improve the abnormal business processing capability.

Description

Block chain-oriented data management method, device, equipment and storage medium

This application claims the priority of the Chinese patent application filed with the Chinese Patent Office on May 22, 2019, the application number is 201910428728.7, and the invention title is "Blockchain-oriented data management methods, devices, equipment and storage media". All of them The content is incorporated in this application by reference.

Technical field

This application relates to the field of blockchain technology, and in particular, to a blockchain-oriented data management method, device, equipment and storage medium.

Background technique

The blockchain can be understood as a distributed ledger. In the application scenario where the blockchain stores data, specifically, the data of the data structure composed of key-value pairs is stored on the blockchain. Among them, the key is the key and the value is the value. Since the data stored in this structure cannot be queried according to very complex conditions, currently, relational databases are usually used to store the conditions for querying the data stored on the chain. Therefore, both on the blockchain and a relational database There is a corresponding piece of data, that is, the data needs to be saved in a relational database when the data is on the chain. This situation is likely to cause inconsistent data between the two parties when updating the data in the blockchain and the relational database. problem. The inventor realizes that in the existing solutions for updating the state of the data in the blockchain and the relational database, the state of the data in the relational database is usually updated first, and then the corresponding data and its state are written The chain is used to update the data on the chain to ensure that the state of the data on the chain is updated accordingly when the state of the data is successfully updated in the relational database. However, there may be a state of the data on the chain that is successfully updated but not returned or The failure to return causes the state of the updated data in the relational database to be rolled back, which leads to the problem of inconsistency between the data in the relational database and the corresponding data on the chain, which can easily cause the data on the chain to become garbage Data, and remain permanently on the chain.

Summary of the invention

The embodiments of the application provide a blockchain-oriented data management method, device, equipment, and storage medium, which can effectively solve the problem of inconsistency between the data of the relational database and the corresponding data on the chain, and avoid the problem of data and Undesirable consequences caused by inconsistent data on the chain.

In the first aspect, an embodiment of the present application provides a blockchain-oriented data management method, which includes: receiving a second update request sent by a user, wherein each update request includes the first state and the first state of the data to be updated. Two states, wherein the first state and the second state are the data states of the data to be updated, and the data state is the state attribute value of the data to be updated; according to the first state, a preset relationship The data to be updated is obtained from the database and the data corresponding to the data to be updated is searched from a preset blockchain, wherein the data to be updated obtained in the relational database is used as the first data, and the block The data corresponding to the data to be updated found on the chain is used as the second data; the first data and the second data are compared to determine whether the first data is consistent with the second data; if the first data is consistent with the second data; If one data is inconsistent with the second data, it is determined whether the first data meets the preset data compensation condition according to the first state and the second state; and if the first data meets the preset data compensation condition, according to the The second state performs data compensation on the first data.

In a second aspect, an embodiment of the present application also provides a blockchain-oriented data management device, which includes: a first receiving unit, configured to receive a second update request sent by a user, wherein each update request includes a waiting Update the first state and the second state of the data, wherein the first state and the second state are the data state of the data to be updated, and the data state is the state attribute value of the data to be updated; first acquisition Unit for obtaining data to be updated from a preset relational database according to the first state and searching for data corresponding to the data to be updated from a preset blockchain, wherein the relational database is The acquired data to be updated is used as the first data, and the data corresponding to the data to be updated found on the blockchain is used as the second data; the first judgment unit is used to compare the first data with the first data Two data to determine whether the first data and the second data are consistent; a second determining unit, for determining whether the first data and the second data are inconsistent, based on the first state and the second state Whether the first data meets a preset data compensation condition; and the first compensation unit is configured to perform data compensation on the first data according to the second state if the first data meets the preset data compensation condition.

In the third aspect, the embodiments of the present application also provide a computer device. The computer device includes a memory, a processor, and a computer program stored on the memory and running on the processor. When the processor executes the program, Implementing a blockchain-oriented data management method includes: receiving a second update request sent by a user, wherein each update request includes a first state and a second state of the data to be updated, wherein the first state And the second state is the data state of the data to be updated, and the data state is the state attribute value of the data to be updated; according to the first state, the data to be updated is obtained from a preset relational database and the data It is assumed that the data corresponding to the data to be updated is searched on the blockchain, wherein the data to be updated obtained in the relational database is used as the first data, and the data searched on the blockchain is corresponding to the data to be updated The data of is used as the second data; the first data is compared with the second data to determine whether the first data is consistent with the second data; if the first data is inconsistent with the second data, According to the first state and the second state, it is determined whether the first data meets the preset data compensation condition; and if the first data meets the preset data compensation condition, the first data is processed according to the second state Perform data compensation.

In a fourth aspect, the embodiments of the present application also provide a computer-readable storage medium with a computer program stored on the computer-readable storage medium, and when the computer program is executed by a processor, a blockchain-oriented data management The method includes: receiving a second update request sent by a user, wherein each update request includes a first state and a second state of the data to be updated, wherein the first state and the second state are the data to be updated The data state is the state attribute value of the data to be updated; the data to be updated is obtained from a preset relational database according to the first state, and the data to be updated is searched on the preset blockchain. Update the data corresponding to the data, wherein the data to be updated obtained in the relational database is used as the first data, and the data corresponding to the data to be updated found on the blockchain is used as the second data; The first data and the second data to determine whether the first data is consistent with the second data; if the first data is inconsistent with the second data, according to the first state and the second state Determine whether the first data meets a preset data compensation condition; and if the first data meets the preset data compensation condition, perform data compensation on the first data according to the second state.

The embodiments of the present application provide a blockchain-oriented data management method, device, equipment, and storage medium. The embodiments of the present application can effectively solve the problem of inconsistency between the data stored in a relational database and the corresponding data on the chain, and avoid the problem that the data on the chain cannot be updated due to the inconsistency between the data of the relational database and the corresponding data on the chain. This embodiment of the application receives an update request sent by a user, and determines whether data compensation is needed for the data in the relational database according to the update request. If it is determined that data compensation is required for the data in the relational database, it will automatically The data is compensated, and the data repair compensation can be realized automatically without user involvement. The embodiments of the present application can effectively ensure the orderly progress of on-chain transactions and can improve the processing capability of abnormal transactions.

Description of the drawings

FIG. 1 is a schematic flowchart of a blockchain-oriented data management method provided by the first embodiment of the application;

2 is a schematic flowchart of a blockchain-oriented data management method provided by the first embodiment of this application;

FIG. 3 is a schematic flowchart of a blockchain-oriented data management method provided by the second embodiment of this application;

4 is a schematic flowchart of a blockchain-oriented data management method provided by the third embodiment of this application;

FIG. 5 is a schematic block diagram of a blockchain-oriented data management device provided by the first embodiment of this application;

6 is a schematic block diagram of a second judgment unit of a blockchain-oriented data management device provided by the first embodiment of this application;

FIG. 7 is a schematic block diagram of a block chain-oriented data management device provided by the second embodiment of this application;

FIG. 8 is a schematic block diagram of a block chain-oriented data management device provided by the third embodiment of this application; and

FIG. 9 is a schematic block diagram of a computer device provided by an embodiment of the application.

Detailed ways

Please refer to FIG. 1, which is a schematic flowchart of a blockchain-oriented data management method provided by the first embodiment of this application. The blockchain-oriented data management method can be run in a terminal device that provides data on-chain functions. Specifically, the blockchain-oriented data management method is applied to a user-end system of a terminal device to prevent relational The data in the database is inconsistent with the corresponding data on the blockchain. Among them, the terminal device may be an electronic device such as a smart phone, a tablet computer, or a notebook computer configured with a preset blockchain; or an independent server or a server cluster composed of multiple servers; the terminal device may also be configured without a preset blockchain. Set a blockchain, but it can interact with other terminal devices that configure the preset blockchain. The method may include steps S101 to S105.

S101. Receive a second update request sent by a user, where each update request includes a first state and a second state of the data to be updated, wherein the first state and the second state are data of the data to be updated State, the data state is the state attribute value of the data to be updated.

Specifically, each update request is specifically a data upload request. The preset client terminal includes a preset personal client terminal, a preset enterprise terminal, and a preset bank terminal. In an embodiment, the receiving the second update request sent by the user may be receiving the second update request sent by the preset enterprise end; or may be receiving the second update request sent by the preset bank end; or It can be to receive the second update request sent by the preset personal client. Wherein, each update request includes a first state and a second state of the data to be updated, wherein the first state and the second state are the data state of the data to be updated, and the data state is the data to be updated The status attribute value of the data to be updated includes multiple attribute values, and the status attribute value is one of the multiple attribute values included therein.

In an embodiment, for example, in this embodiment, the data to be updated is service data, and the service data is data generated by each preset service in the service system of the preset user end. Wherein, the preset client terminal includes a preset personal client terminal, a preset enterprise terminal, and a preset bank terminal, and the preset business includes insurance business, loan business, and financial and wealth management business. Then the business data may specifically For example, insurance data, loan data, and financial management data. Wherein, each piece of business data generated corresponding to each preset service includes multiple attribute values, where the multiple attribute values can be used as query conditions for querying the business data. Specifically, since the data on the blockchain is stored in a data structure of key-value pairs, it is impossible to find the data on the chain according to very complicated query conditions. Among them, the key is the key and the value is the value. Therefore, a preset relational database can be used to store a piece of data on the blockchain correspondingly, that is, the data can be correspondingly stored in the relational database while the data is on the chain, so as to save the relational database The multiple attribute values corresponding to a piece of data saved in the data are used as query conditions for searching data on the blockchain. Wherein, a piece of data correspondingly saved in the relational database includes the key value key and data content value; the data content value includes multiple attribute values. If the data is loan data, the multiple attribute values may be, for example, the loan company, loan amount, loan date, repayment date, repayment amount, loan type, and loan status.

Wherein, the first state and the second state are the data states of the data to be updated, the data state is the state attribute value of the data to be updated, and the first state and the second state are used to indicate the data to be updated The data state before the update and the updated data state of the data, specifically, the first state is the data state before the data to be updated is updated, and the second state is the data state after the data to be updated is updated. Specifically, if the data to be updated is not updated, the current data state of the data to be updated is the data state of the data to be updated before the update; if the data to be updated has been updated, the data to be updated The current data status of is the data status of the data to be updated after the update, therefore, the current data status of the data to be updated will change with the progress of the preset service. For example, if the preset business is a loan business, the corresponding business data generated is loan data, and the data status of the loan data is the loan status. Specifically, when the user applies for a loan business on the business system of the preset enterprise side A piece of loan data LOAN will be generated correspondingly. The loan data LOAN includes the key value of the loan data and the data content value, where the data content value includes the loan company, loan amount, loan date, repayment date, and repayment amount. Multiple attribute values such as loan type and loan status. Among them, the loan data LOAN can be found by using multiple attribute values of the loan data. For example, the loan data generated on xx month and xx day can be queried. If the loan time of the loan data LOAN is also xx month xx day, the Loan data will be searched out. In addition, since the loan status of the loan data LOAN is the data status of the loan data, the loan status of the loan data LOAN will change with the progress of the loan business, that is, the loan status of the loan data LOAN specifically includes the first status And the second state, the loan state of the loan data LOAN will be updated from the first state to the second state as the loan business progresses. For example, when an enterprise applies for a loan business on the enterprise side, the current data status of the corresponding piece of loan data is in application by default, that is, the first state of the loan status of the loan data is in application; if the bank is in the bank After seeing this piece of loan data LOAN, you can decide whether to approve the loan business application; if the bank agrees to the loan business application, the loan status of the loan data LOAN will be updated from the application to the approved application, where the The first state of the loan status is the application, and the second state is the application approved; if the application for the loan business is disapproved, the loan status of the loan data LOAN will be updated from the application to the application disapproved, where the loan The first status of the status is the application, and the second status is the application disapproved; if the company enters the stage of preparing for repayment after the loan is completed, the loan status of the loan data LOAN will be updated from loaned to paid, part The status of repayment or overdue payment. During this process, the loan status of the loan data LOAN will change with the progress of the loan business, that is, the loan status of the loan data LOAN will be updated from the first status to The second state. The first state is the data state before the update of the data to be updated, and the first state may specifically include application in progress, application cancellation, application approval, application disapproval, loan released, paid, partial repayment, and overdue The state of payment, etc.; the second state is the data state after the update of the data to be updated, and the second state may specifically include application in progress, application cancellation, application approval, application disapproval, loan disbursed, repayment, and partial repayment , Overdue payment and other status.

S102. Acquire data to be updated from a preset relational database according to the first state and search for data corresponding to the data to be updated from a preset blockchain, wherein the data obtained from the relational database The data to be updated is used as the first data, and the data corresponding to the data to be updated found on the blockchain is used as the second data.

Specifically, in an embodiment, the obtaining data to be updated from a preset relational database according to the first state and searching for data corresponding to the data to be updated from a preset blockchain includes the following sub Steps S102a to S102b, wherein, the step S102a: obtain the to-be-updated data from a preset relational database according to the first state of the to-be-updated data, wherein the to-be-updated data obtained in the relational database is Data as the first data; and step S102b: search for data corresponding to the first data from a preset blockchain according to the first data, wherein the data searched on the blockchain is compared with the first data The data corresponding to one data serves as the second data.

Specifically, it can be known from step S101 that a piece of data correspondingly stored in the relational database includes the key value and the data content value; the data content value includes multiple attribute values. For example, in one embodiment, if the data is loan data, the multiple attribute values may be, for example, the loan company, loan amount, loan date, repayment date, repayment amount, loan type, and loan status. Specifically, in step S102a, if the data to be updated is loan data, the first state of the loan data is the loan state of the loan data, and the first state of the data to be updated starts from a preset relationship Obtaining the data to be updated in the type database specifically refers to obtaining data whose current loan state is the first state from a preset relational database according to the first state, and the acquired data is the data to be updated. For example, if the first status is application, all loan data whose current loan status is application is obtained from a preset relational database. The step S102b searching for data corresponding to the first data from a preset blockchain according to the first data includes: searching from a preset blockchain according to the key value of the first data and Data with the same key value key of the first data, wherein the data corresponding to the first data found on the blockchain is used as the second data. Specifically, a piece of data stored in the block chain corresponding to the relational database also includes the key value of the data and the data content value; the data content value includes multiple attribute values. For example, in one embodiment, if the data is loan data, the multiple attribute values may be, for example, the loan company, loan amount, loan date, repayment date, repayment amount, loan type, and loan status. At this time, the loan status of the second data corresponding to the first data found on the blockchain is the current data status of the second data.

S103. Compare the first data with the second data to determine whether the first data is consistent with the second data.

Specifically, usually the first data and the second data are completely the same data. The difference is that the first data is stored in a preset relational database, and the second data is written into a preset area. Block chain. However, in the entire process of writing business data to the blockchain, it is necessary to interact with multiple systems through the HTTP protocol. The systems can be, for example, transaction systems and blockchain systems, that is, the client system needs to communicate with the transaction through the HTTP protocol. The system interacts with the blockchain system to achieve data on-chain. Therefore, there are many uncontrollable factors in the process of data on-chain. When business data on-chain timeout, return failure, or abnormal execution, it will Automatically roll back the updated data in the preset relational database. However, a failure to return or an abnormal situation does not mean that the business data has failed to be uploaded to the chain. If the business data is successfully uploaded to the chain, and the corresponding updated business data in the preset relational database is rolled back, the data on the chain is different from the data in the preset relational database. For example, when the preset enterprise side submits a business application , Correspondingly generate a piece of business data and save it in a preset relational database and write it on a preset blockchain. At this time, the current data status of the business data is in application, and when the preset bank has processed the After the business application, for example, to approve the business application, the current data status of the business data in the preset relational database is updated from the application to the approved application, and the updated business data is written into a preset area On the block chain, however, there may be that after the updated business data is successfully written into the chain, but the client system does not return success, the updated business data will be automatically rolled back to the update in the preset relational database The previous data status, at this time, the data status of the business data in the preset relational database is application, and the application is approved on the preset blockchain. Therefore, the first data and the second data are compared to determine whether the first data and the second data are the same.

Wherein, in one embodiment, after the step of comparing the first data with the second data to determine whether the first data is consistent with the second data, the step further includes if the first data is consistent with If the second data is consistent, the second update request sent by the user is executed; wherein, the second update request is a data upload request. Specifically, if the first data is consistent with the second data, it indicates that the first data is normal uplink data, and data compensation processing is not required for the first data.

S104: If the first data is inconsistent with the second data, determine whether the first data meets a preset data compensation condition according to the first state and the second state.

Specifically, in an embodiment, when the first data is inconsistent with the second data, the judging whether the first data meets a preset data compensation condition according to the first state and the second state includes Data compensation judgment method. The data compensation judgment method is shown in FIG. 2, that is, step S104 includes sub-steps S104a to S104d. Wherein, S104a, determining whether the first state of the first data can be transferred to the current data state of the second data according to a preset state transfer rule; S104b, if the first state of the first data can be transferred to all The current data state of the second data, and determine whether the second state of the first data is consistent with the current data state of the second data; S104c, if the second state of the first data is the same as the current data state of the second data If the data status is consistent, it is determined that the first data meets the preset data compensation condition; S104d, if the first status of the first data cannot be transferred to the current data status of the second data or the second data status of the first data The state is inconsistent with the current data state of the second data, and it is determined that the first data does not meet the preset data compensation condition.

Specifically, in the step S104a, the preset state transfer rules include a state transferable rule and a state non-transferable rule, wherein the state transferable rule is a preset state that can be updated from one state to another. State rules, the state non-circulation rule is a preset rule that cannot be transferred from one state to another state. For example, if a state is in application, the preset state can be transferred to another state. The status is canceled application, approved application, and disapproved application; the other status that cannot be transferred with it is loaned out, repaid, partial repayment, overdue payment; if one status is approved to apply, it can happen with the status The other status of the transfer is already loaned; the other status of the status that cannot be associated with the process is application, disapproval of application, repayment, partial repayment, and overdue payment; that is, a status can be transferred from the application status In order to agree to the application status, it cannot be transferred from the approved application status to the application status. Therefore, in the step S104a, if the first status of the first data is in application, the current data status of the second data is in application approval, and the data status is in application can be transferred to application approval, then It is determined that the first state of the first data satisfies the preset state transfer rule; if the first state of the first data is an application approved, the current data state of the second data is an application disapproved, wherein the data state is If the approval application cannot be transferred to the disapproval application, it is determined that the first state of the first data does not meet the preset state transfer rule.

In the step S104b, if the first state of the first data can be transferred to the current data state of the second data, the second state of the first data is determined according to the second state of the first data. Whether the status is consistent with the current data status of the second data; specifically, for example, if it can be known that the first status of the first data is in application according to the update request, and the second status is the approved application; it can be known from step S102 that the area The current data status of the second data corresponding to the first data found on the block chain is an approved application. Therefore, the second status of the first data is consistent with the current data status of the second data, and both are approved applications. If the second state of the first data is consistent with the current data state of the second data, it can be determined that the first data meets the preset data compensation condition, and the corresponding data compensation processing may be performed on the first data. Wherein, the first data is stored in the preset relational database, and the second data is stored in the preset blockchain.

Because the data status in the first data is different from the data status in the second data in the process of data uploading, for example, in the process of updating the data status of the data, when the current data status of the first data is updated from the application to agree When applying, write the updated first data as the second data into the blockchain. When the second data is successfully written into the chain, but due to the need to interact with multiple systems through the HTTP protocol, the system can For example, the transaction system and the blockchain system, that is, the client system needs to interact with the transaction system and the blockchain system through the HTTP protocol to achieve data on the chain. Therefore, there are many uncontrollable factors in the process of data on the chain. Therefore, it is easy to return abnormalities or timeout on the chain, which will cause the data state of the first data in the preset relational database to automatically roll back from the second state to the first state, that is, roll back from the agreed application state to Application status. At this time, the data status of the first data in the preset relational database is application, and the data status of the second data corresponding to the first data on the preset blockchain is application approval. When the client system receives the query condition that the data status is application, the first data that was rolled back will be retrieved by query, and then the first data needs to be updated to agree to the application and write again according to the update request sent by the user In the chain, but at this time, the data status of the second data corresponding to the first data on the chain is already in the state of agreeing to apply. Because the data on the chain is unique, the first data cannot be repeatedly written to the On the blockchain, the data on the chain will be abnormal, which may cause more adverse effects. At this time, it is only necessary to compensate the data state of the first data in the preset relational database, so that the first data is not queried. Therefore, it is necessary to determine whether the second state of the first data is consistent with the current data state of the second data. If the second state of the first data is consistent with the current data state of the second data, it indicates that the first data was rolled back in the process of updating the data state to the chain, and the corresponding second data has succeeded On the chain, at this time, only the data state of the first data in the preset relational database needs to be compensated, that is, the data state compensation of the first data in the preset relational database is a consent application to prevent The first data is repeatedly chained to solve the abnormality of the chaining transaction.

S105: If the first data meets a preset data compensation condition, perform data compensation on the first data according to the second state.

Specifically, if the second state of the first data is consistent with the current data state of the second data, that is, it is determined that the first data satisfies the preset data compensation condition, then the data of the first data is performed according to the update request. Compensation, wherein the performing data compensation on the first data according to the update request specifically includes: updating and compensating the data state of the first data from the first state to the second state according to the update request.

In the above embodiment, this solution first obtains the first data in a preset relational database according to the update request after receiving the update request submitted by the user, and then finds it on the chain according to the first data The second data corresponding to the first data is then judged whether the first data and the second data are consistent; if the first data is consistent with the second data, the second update request sent by the user is executed; if the first data is consistent If the data is inconsistent with the second data, then it is determined whether the first data meets the preset data compensation conditions, and if so, data compensation is performed on the first data, so as to ensure that the need for data is avoided when the update request is subsequently executed. The compensated first data interferes with the update request, that is, avoids interference with the normal uploading of other data to be updated, which can ensure the normal progress of the user's update request, wherein the update request is a data upload request. The embodiments of the present application can effectively solve the problem of inconsistency between the data stored in a relational database and the corresponding data on the chain, and avoid the problem that the data on the chain cannot be updated due to the inconsistency between the data of the relational database and the corresponding data on the chain. The embodiment of the application can automatically compensate the data to be updated that needs data compensation, and can automatically realize data repair compensation without user involvement. The embodiments of the present application can also effectively ensure the orderly progress of on-chain transactions and can improve the processing capability of the abnormal transaction of the client system.

Please refer to FIG. 3, which is a schematic flowchart of a blockchain-oriented data management method provided by the second embodiment of this application. Specifically, as shown in FIG. 3, the method may include steps S201-S207. The steps S201-S205 are similar to the steps S101-S105 in the foregoing embodiment, and will not be repeated here. The steps S206-S207 added in this embodiment will be described in detail below.

S206. If the first data is consistent with the second data, execute a second update request sent by the user; wherein, each update request is a data upload request.

Wherein, in one embodiment, it can be seen from step S203 that after the step of comparing the first data with the second data to determine whether the first data is consistent with the second data, the method further includes: The first data is consistent with the second data, and the second update request sent by the user is executed; wherein, the second update request is a data upload request.

Specifically, if the first data is consistent with the second data, it indicates that the first data is normal on-chain data, and there is no need to perform data compensation processing on the first data, and the data compensation may not be required. The data on the blockchain is to execute the second update request sent by the user, so as to ensure the normal progress of the second update request of the user. Specifically, the second update request sent by the executing user specifically includes sub-step S206a and sub-step S206b, wherein the sub-step S206a: updating the data to be updated in the relational database; and the sub-step S206b : Write the updated data to be updated on a preset blockchain by calling the update link; wherein the update link is an interface that the blockchain provides to the client to call.

S207: If the first data does not meet the preset data compensation condition, send an abnormal reminder to the user.

Specifically, it can be known from step S204 that judging whether the first data meets the preset data compensation condition according to the first state and the second state specifically includes: S204a: judging the first data of the first data according to the preset state circulation rule Whether a state can be transferred to the current data state of the second data; and S204b, if the first state of the first data can be transferred to the current data state of the second data, determine the first data state of the first data Whether the second state is consistent with the current data state of the second data; wherein, if the first state of the first data cannot be transferred to the current data state of the second data or the second state of the first data is If the current data state of the data is inconsistent, the first data is abnormal data, which is regarded as an unknown abnormality of the system operation, and data consistency cannot be achieved through automatic system compensation, and an abnormal reminder needs to be issued to the user.

Specifically, in an embodiment, when the first data does not meet the preset data compensation condition, the sending an abnormal reminder to the user includes sub-step S207a and sub-step S207b. Wherein, S207a, save the first data in a preset data table; S207b, send the data table to the user by email to send an abnormal reminder. Of course, in other embodiments, the data table may be sent to the user by means of instant messaging, text messages, or system alarms to send out abnormal reminders. Specifically, in an embodiment, the ID or serial number of the first data may be written into a preset database table, which is used to store all abnormal data and send email reminders to the relevant person in charge, So that the relevant person in charge can analyze and solve the data problem in time according to the email reminder.

In the above embodiment, this solution first obtains the first data in a preset relational database according to the update request after receiving the update request submitted by the user, and then finds it on the chain according to the first data The second data corresponding to the first data is then judged whether the first data is consistent with the second data; if the first data is consistent with the second data, the second update request sent by the user is executed; if the first data is consistent If the data is inconsistent with the second data, then it is determined whether the first data meets the preset data compensation conditions, and if so, data compensation is performed on the first data, so as to ensure that the need for data is avoided when the update request is subsequently executed. The compensated first data interferes with the update request, that is, avoids interference with the normal uploading of other data to be updated, which can ensure the normal progress of the user's update request, wherein the update request is a data upload request. If it is not satisfied, an abnormal reminder is sent to the user, which can prompt the user in time so that the user can quickly and easily find the abnormal data, and then perform manual repair in time.

Please refer to FIG. 4, which is a schematic flowchart of a blockchain-oriented data management method provided by the third embodiment of this application. Specifically, the method is applied to a preset user terminal, and the update request is the second update request. As shown in FIG. 4, the method may include steps S301-S310. Steps S301-S307 are similar to steps S201-S207 in the foregoing embodiment, and will not be repeated here. The steps S308 to S312 added in this embodiment will be described in detail below.

S308: If the first update request sent by the user is received, determine whether the data to be updated in the relational database meets a preset state transfer rule according to the first state and the second state of the first update request.

Specifically, the judging whether the data to be updated in the relational database meets the preset state transfer rule according to the first state and the second state of the first update request includes sub-step S308a, wherein the sub-step S308a : Judging whether the data to be updated in the relational database can be updated from the first state to the second state according to the first state and the second state of the first update request and the preset state flow rule; wherein, one update The request includes a first state and a second state of the data to be updated, wherein the first state and the second state are the data state of the data to be updated, and the data state is the state attribute value of the data to be updated; The first state is the data state before the data to be updated is updated, and the second state is the data state after the data to be updated is updated. The preset state transfer rule includes a state transferable rule and a state non-transferable rule, wherein the state transferable rule is a preset rule that can be transferred from one state to another state, and the state cannot be transferred rule It is a pre-set rule that cannot flow from one state to another. Specifically, for example, if the first status of the data to be updated is application and its second status is repaid, then the data to be updated in the relational database does not meet the preset state transfer rules; The first state of the updated data is the application, and the second state is the application approved, then the data to be updated in the relational database meets the preset state circulation rules.

S309: If the data to be updated in the relational database meets the preset state circulation rule, update the data to be updated.

Specifically, the updating the data to be updated specifically includes: updating the data status of the data to be updated in a preset relational database of the user end system. The updating the data state of the data to be updated in a preset relational database of the user-end system specifically includes: updating the data to be updated in a preset relational database of the user-end system from the first state to The second state.

S310. Write the updated data to be updated on a preset blockchain by calling the update link; wherein the update link is an interface that the blockchain provides to the client to call.

Specifically, the writing of the updated data to be updated on a preset blockchain by calling the update link port is achieved through remote access via HTTP protocol. Specifically, it is necessary to remotely access multiple systems through the HTTP protocol. For example, the client system may call the write link port of the transaction server through the HTTP protocol, where the HTTP protocol will return the HTTP return code purposefully, and The HTTP return code can be customized according to the needs of the user's actual application scenario. When the HTTP return code indicates a failure, the data saved in the relational database will be automatically rolled back.

S311. Receive an HTTP return code and determine whether an update exception occurs according to the HTTP return code.

Wherein, the HTTP return code includes multiple status codes, and the multiple status codes are used to indicate an error that occurs when the server processes the request. Therefore, the received HTTP return code can be used to determine whether it is an update abnormality. The update exception is an error condition that occurs when multiple systems in the process of data uploading are processing requests. That is, the multiple status codes are used to indicate errors that occur when multiple systems used in the data upload process process requests. These errors may be errors in the server itself, rather than errors in the request. The multiple status codes can be, for example, 500 (server internal error), 501 (not yet implemented), 502 (error gateway), 503 (service unavailable), 504 (gateway timeout), 505 (HTTP version is not supported), etc. . Among them, in one embodiment, the time required for the entire process of writing data to the chain can be set to 15 seconds in advance. If the entire process of writing data to the chain takes more than 15 seconds, it is determined that the data entry into the chain has timed out, that is, the If the data fails to enter the chain, an HTTP return code of 504 (gateway timeout) will be returned.

S312: If an abnormal update occurs, roll back the updated data to be updated in the relational database.

Specifically, when the HTTP return code indicates failure, the data stored in the relational database will be automatically rolled back.

Specifically, the above step S307-step S309 are necessary steps to execute the second update request sent by the user, that is, the second update request can be realized by executing the above step S307-step S309, that is, the data upload request is completed, Among them, when the user sends the first update request, the data to be updated does not exist in the preset relational database and on the preset blockchain, that is, there is no data in the preset relational database and the preset The problem of data inconsistency on the blockchain. However, after the first update request is executed, there may be a problem that the data in the preset relational database is inconsistent with the data on the preset blockchain. Therefore, it should be judged and identified. Data for data compensation, and compensation for data in the preset relational database that needs data compensation, thereby ensuring that when the update request is subsequently executed, the interference of the first data that needs data compensation on the update request is avoided , That is, to avoid interference with the normal uploading of other data to be updated, which can ensure the normal progress of the user's update request, where each update request is a data upload request.

Please refer to FIG. 5, which is a schematic block diagram of a blockchain-oriented data management device 100 provided by the first embodiment of the application. As shown in FIG. 5, the blockchain-oriented data management device 100 corresponds to the blockchain-oriented data management method shown in FIG. The blockchain-oriented data management device 100 includes a unit for executing the above-mentioned blockchain-oriented data management method. The blockchain-oriented data management device 100 can be configured in a terminal device that provides data on-chain functions, Specifically, the blockchain-oriented data management device 100 is applied in a client system of a terminal device to prevent data in a relational database from being inconsistent with corresponding data on the blockchain. Among them, the terminal device may be an electronic device such as a smart phone, a tablet computer, or a notebook computer configured with a preset blockchain; or an independent server or a server cluster composed of multiple servers; the terminal device may also be configured without a preset blockchain. Set a blockchain, but it can interact with other terminal devices that configure the preset blockchain. Specifically, referring to FIG. 5, the blockchain-oriented data management device 100 includes a first receiving unit 101, a first acquiring unit 102, a first determining unit 103, a second determining unit 104, and a first compensation unit 105.

The first receiving unit 101 is configured to receive a second update request sent by a user, where each update request includes a first state and a second state of the data to be updated, wherein the first state and the second state are The data state of the data to be updated, where the data state is the state attribute value of the data to be updated.

The first obtaining unit 102 is configured to obtain data to be updated from a preset relational database according to the first state and search for data corresponding to the data to be updated from a preset blockchain, wherein The data to be updated obtained in the relational database is used as the first data, and the data corresponding to the data to be updated found on the blockchain is used as the second data.

In an embodiment, the first obtaining unit 102 includes: a first obtaining subunit 102a and a second obtaining subunit 102b. Wherein, the first obtaining subunit 102a is configured to obtain the data to be updated from a preset relational database according to the first state of the data to be updated, wherein the data to be updated obtained from the relational database is Update data as first data; and the second acquiring subunit 102b is configured to search for data corresponding to the first data from a preset blockchain according to the first data, wherein the area is The data corresponding to the first data found on the block chain is used as the second data.

The first determining unit 103 is configured to compare the first data with the second data to determine whether the first data is consistent with the second data.

The second determining unit 104 is configured to determine whether the first data meets a preset data compensation condition according to the first state and the second state if the first data is inconsistent with the second data.

In an embodiment, as shown in FIG. 6, the second judgment unit 104 includes: a first judgment subunit 104a, a second judgment subunit 104b, a first judgment unit 104c, and a second judgment unit 104d. The first determining subunit 104a is configured to determine whether the first state of the first data can be transferred to the current data state of the second data according to a preset state transfer rule; the second determining subunit 102b, configured to determine whether the second state of the first data is consistent with the current data state of the second data if the first state of the first data can be transferred to the current data state of the second data; The first determining unit 104c is configured to determine that the first data meets a preset data compensation condition if the second state of the first data is consistent with the current data state of the second data; and the second determining unit 104d, configured to determine if the first state of the first data cannot be transferred to the current data state of the second data or the second state of the first data is inconsistent with the current data state of the second data The first data does not meet the preset data compensation condition.

The first compensation unit 105 is configured to perform data compensation on the first data according to the second state if the first data meets a preset data compensation condition.

It should be noted that those skilled in the art can clearly understand that the above-mentioned blockchain-oriented data management device 100 and the specific implementation process and effects of each unit can refer to the corresponding description in the foregoing method embodiment, for the purpose of description Convenient and concise, I won’t repeat it here.

Please refer to FIG. 7, which is a schematic block diagram of a block chain-oriented data management device 200 provided by the second embodiment of the application. As shown in FIG. 7, the block chain-oriented data management device 200 provided by the second embodiment of the present application adds a first execution unit 206 and a first reminder unit 207 on the basis of the above-mentioned embodiment. The device 200 includes a second receiving unit 201, a second acquiring unit 202, a third determining unit 203, a fourth determining unit 204, a second compensating unit 205, a first executing unit 206, and a first reminding unit 207. Among them, the second receiving unit 201, the second acquiring unit 202, the third determining unit 203, the fourth determining unit 204, and the second compensating unit 205 are the same as the first receiving unit 101, the first acquiring unit 102, The first judging unit 103, the second judging unit 104, and the first compensation unit 105 are similar, and since their application process and corresponding functions are similar to the corresponding units in the foregoing embodiment, they will not be repeated here.

The first execution unit 206 is configured to execute a second update request sent by the user if the first data is consistent with the second data; wherein, each update request is a data upload request.

Specifically, in an embodiment, the first execution unit 206 includes a first execution sub-unit 206a and a second execution sub-unit 206b. Wherein, the first execution sub-unit 206a is used to update the data to be updated in the relational database; and the second execution sub-unit 206b is used to write the updated data to be updated into a file by calling the update link port. On a preset blockchain; wherein, the update link port is an interface that the blockchain provides to the client to call.

The first reminder unit 207 is configured to send an abnormal reminder to the user if the first data does not meet the preset data compensation condition.

Specifically, in an embodiment, the first reminder unit 207 includes a first storage unit 207a and a first reminder subunit 207b. Wherein, the first storage unit 207a is used to store the first data in a preset data table; and the first reminder sub-unit 207b is used to send the data table to the user by email for sending Exception reminder. Of course, in other embodiments, the data table may be sent to the user by means of instant messaging, text messages, or system alarms to send out abnormal reminders.

It should be noted that those skilled in the art can clearly understand that for the specific implementation process and effects of the above-mentioned device 200 and each unit, reference may be made to the corresponding description in the foregoing method embodiment. For the convenience and brevity of the description, it is not here. Repeat it again.

Please refer to FIG. 8, which is a schematic block diagram of a blockchain-oriented data management device 300 provided by the third embodiment of the application. As shown in FIG. 8, a blockchain-oriented data management device 300 provided by the third embodiment of the present application adds a rule determination unit 308, an update unit 309, an update chain unit 310, and a return Code judgment unit 311 and rollback unit 312, that is, the device 300 includes a third receiving unit 301, a third acquisition unit 302, a fifth judgment unit 303, a sixth judgment unit 304, a third compensation unit 305, and a second execution unit 306, a second reminder unit 307, a rule determination unit 308, an update unit 308, an update chain unit 310, a return code determination unit 311, and a rollback unit 312. Among them, the third receiving unit 301, the third acquiring unit 302, the fifth determining unit 303, the sixth determining unit 304, the third compensating unit 305, the second executing unit 306, and the second reminding unit 307 are the same as those in the foregoing embodiment The second receiving unit 201, the second acquiring unit 202, the third judging unit 203, the fourth judging unit 204, the second compensation unit 205, the first executing unit 206, and the first reminding unit 207 are similar, due to their application process and corresponding functions It is similar to the corresponding units in the above-mentioned embodiment, and will not be repeated here.

The rule determination unit 308 is configured to, if the first update request sent by the user is received, determine whether the to-be-updated data in the relational database meets the predetermined requirements according to the first state and the second state of the first update request. Set state transfer rules. Wherein, the rule determination unit 308 is specifically configured to determine the relationship type according to the first state and second state of the first update request and a preset state transfer rule if the first update request sent by the user is received. Whether the data to be updated in the database can be updated from the first state to the second state.

The updating unit 309 is configured to update the data to be updated if the data to be updated in the relational database meets a preset state circulation rule.

The update chain unit 310 is used to write the updated data to be updated on a preset blockchain by calling an update link; wherein, the update link is provided by the blockchain for the client to call Interface.

The return code judgment unit 311 is configured to receive an HTTP return code and judge whether an update abnormality occurs according to the HTTP return code.

The rollback unit 312 is configured to roll back the updated data to be updated in the relational database if an abnormal update occurs.

It should be noted that those skilled in the art can clearly understand that for the specific implementation process and effects of the foregoing device 300 and each unit, reference may be made to the corresponding description in the foregoing method embodiment. For the convenience and brevity of the description, it is not here. Repeat it again.

The above-mentioned apparatus may be implemented in the form of a computer program, and the computer program may run on the computer device as shown in FIG. 9.

Please refer to FIG. 9, which is a schematic block diagram of a computer device according to an embodiment of the application. The computer device 600 may be a terminal or a server, where the terminal may be an electronic device supporting data on-chain transactions such as a smart phone, a tablet computer, a notebook computer, a desktop computer, and a personal digital assistant. The server is a server that supports data on-chain transactions, and the server may be an independent server or a server cluster composed of multiple servers.

Referring to FIG. 9, the computer device 600 includes a processor 602, a memory, and a network interface 605 connected through a system bus 601, where the memory may include a non-volatile storage medium 603 and an internal memory 604.

The non-volatile storage medium 603 can store an operating system 6031 and a computer program 6032. The computer program 6032 includes program instructions. When the program instructions are executed, the processor 602 can execute a blockchain-oriented data management method.

The processor 602 is used to provide calculation and control capabilities to support the operation of the entire computer device 600.

The internal memory 604 provides an environment for the operation of the computer program 6032 in the non-volatile storage medium 603. When the computer program 6032 is executed by the processor 602, the processor 602 can execute a blockchain-oriented data management method.

The network interface 605 is used for network communication with other devices. Those skilled in the art can understand that the structure shown in FIG. 9 is only a block diagram of part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device 600 to which the solution of the present application is applied. The specific computer device 600 may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

The processor 602 is configured to run a computer program 6032 stored in the memory to implement the following steps: receiving a second update request sent by the user, wherein each update request includes the first state of the data to be updated and the first state of the data to be updated. Two states, wherein the first state and the second state are the data states of the data to be updated, and the data state is the state attribute value of the data to be updated; according to the first state, a preset relationship The data to be updated is obtained from the database and the data corresponding to the data to be updated is searched from a preset blockchain, wherein the data to be updated obtained in the relational database is used as the first data, and the block The data corresponding to the data to be updated found on the chain is used as the second data; the first data and the second data are compared to determine whether the first data is consistent with the second data; if the first data is consistent with the second data; If one data is inconsistent with the second data, it is determined whether the first data meets the preset data compensation condition according to the first state and the second state; and if the first data meets the preset data compensation condition, according to the The second state performs data compensation on the first data.

In an embodiment, the blockchain-oriented data management method is applied to a preset user terminal, and the processor 602 further implements the following specifically before implementing the step of receiving the second update request sent by the user Step: if the first update request sent by the user is received, determine whether the data to be updated in the relational database meets the preset state transfer rule according to the first state and the second state of the first update request; if The data to be updated in the relational database meets the preset state circulation rules, and the data to be updated is updated; the updated data to be updated is written to a preset blockchain by calling the update link port; wherein, the The update link port is the interface that the blockchain provides to the client to call; receives the HTTP return code and judges whether an update exception occurs according to the HTTP return code; and if an update exception occurs, rolls back to the relational database The updated data to be updated.

In an embodiment, when the processor 602 implements the step of judging whether the data to be updated in the relational database meets a preset state transfer rule according to the first state and the second state of the first update request , The specific implementation is as follows: judging whether the data to be updated in the relational database can be updated from the first state to the second state according to the first state and the second state of the first update request and the preset state transfer rule .

In an embodiment, the processor 602 implements the process of obtaining the data to be updated from a preset relational database according to the first state and searching the data corresponding to the data to be updated from the preset blockchain. In the step, the following steps are specifically implemented: obtaining the data to be updated from a preset relational database according to the first state of the data to be updated, wherein the data to be updated obtained in the relational database is used as the first Data; and searching for data corresponding to the first data from a preset blockchain according to the first data, wherein the data corresponding to the first data searched on the blockchain is taken as the first Two data.

In one embodiment, when the processor 602 implements the step of judging whether the first data meets the preset data compensation condition based on the first state and the second state, the processor 602 specifically implements the following steps: The rule determines whether the first state of the first data can be transferred to the current data state of the second data; if the first state of the first data can be transferred to the current data state of the second data, it is determined Whether the second state of the first data is consistent with the current data state of the second data; if the second state of the first data is consistent with the current data state of the second data, it is determined that the first data meets the preset Data compensation conditions; and if the first state of the first data cannot be transferred to the current data state of the second data or the second state of the first data is inconsistent with the current data state of the second data, it is determined The first data does not meet the preset data compensation condition.

In one embodiment, after the processor 602 implements the step of judging whether the first data meets the preset data compensation condition according to the first state and the second state, the processor 602 specifically implements the following steps: One data does not meet the preset data compensation conditions, and an abnormal reminder is issued to the user.

In one embodiment, when the processor 602 implements the step of sending an abnormal reminder to the user, it specifically implements the following steps: save the first data in a preset data table; and pass the data table through The email is sent to the user to alert the user of the exception.

It should be understood that in this embodiment of the application, the processor 602 may be a central processing unit (Central Processing Unit, CPU), and the processor 602 may also be other general-purpose processors, digital signal processors (DSP), Application Specific Integrated Circuit (ASIC), Field-Programmable Gate Array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processor may be a microprocessor or the processor may also be any conventional processor.

Those of ordinary skill in the art can understand that all or part of the processes in the methods of the foregoing embodiments can be implemented by computer programs instructing relevant hardware. The computer program includes program instructions, and the computer program can be stored in a storage medium, which is a storage medium. The program instructions are executed by at least one processor in the computer system to implement the process steps of the foregoing method embodiments.

Therefore, this application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program, where the computer program includes program instructions. When the program instructions are executed by the processor, the processor executes the blockchain-oriented data management method as described above.

The computer-readable storage medium may be non-volatile or volatile. The storage medium may be a U disk, a mobile hard disk, a read-only memory (Read-Only Memory, ROM), a magnetic disk, or an optical disk, etc., which can store program codes.

A person of ordinary skill in the art may realize that the units and algorithm steps of the examples described in the embodiments disclosed herein can be implemented by electronic hardware, computer software, or a combination of the two, in order to clearly illustrate the hardware and software Interchangeability. In the above description, the composition and steps of each example have been generally described in terms of function. Whether these functions are executed by hardware or software depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.

In the several embodiments provided in this application, it should be understood that the disclosed system and method may be implemented in other ways. For example, the system embodiment described above is only illustrative. For example, the division of each unit is only a logical function division, and there may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be omitted or not implemented.

The steps in the method of the embodiment of the present application can be adjusted, merged, and deleted in order according to actual needs. The units in the system of the embodiment of the present application may be combined, divided, and deleted according to actual needs. In addition, the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.

If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a storage medium. Based on this understanding, the technical solution of this application is essentially or the part that contributes to the existing technology, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium It includes several instructions to make a computer device (which may be a personal computer, a terminal, or a network device, etc.) execute all or part of the steps of the method described in each embodiment of the present application.

Claims (20)

1. A blockchain-oriented data management method, including:

   Receiving a second update request sent by the user, where each update request includes a first state and a second state of the data to be updated, wherein the first state and the second state are the data states of the data to be updated, The data status is the status attribute value of the data to be updated;

   According to the first state, the data to be updated is obtained from a preset relational database and the data corresponding to the data to be updated is searched on the preset blockchain, wherein the data to be updated obtained in the relational database is Data as the first data, and the data corresponding to the data to be updated found on the blockchain as the second data;

   Comparing the first data with the second data to determine whether the first data is consistent with the second data;

   If the first data is inconsistent with the second data, judging whether the first data meets a preset data compensation condition according to the first state and the second state; and

   If the first data meets a preset data compensation condition, perform data compensation on the first data according to the second state.
2. The blockchain-oriented data management method according to claim 1, wherein the method is applied to a preset user terminal, and before the step of receiving the second update request sent by the user, the method further comprises:

   If the first update request sent by the user is received, judging whether the data to be updated in the relational database meets the preset state transfer rule according to the first state and the second state of the first update request;

   If the data to be updated in the relational database meets the preset state circulation rule, update the data to be updated;

   Write the updated data to be updated on a preset blockchain by calling the update link; wherein, the update link is an interface that the blockchain provides to the client to call;

   Receiving an HTTP return code and judging whether an update exception occurs according to the HTTP return code; and

   If an update exception occurs, roll back the updated data to be updated in the relational database.
3. The blockchain-oriented data management method according to claim 2, wherein said determining whether the data to be updated in the relational database meets a preset state according to the first state and the second state of the first update request Circulation rules, including:

   Determine whether the data to be updated in the relational database can be updated from the first state to the second state according to the first state and the second state of the first update request and a preset state circulation rule.
4. The blockchain-oriented data management method according to claim 1, wherein the data to be updated is obtained from a preset relational database according to the first state, and the data to be updated is searched from the preset blockchain. Data corresponding to the data, including:

   Acquiring the data to be updated from a preset relational database according to the first state of the data to be updated, wherein the data to be updated acquired in the relational database is used as the first data; and

   Searching for data corresponding to the first data from a preset blockchain according to the first data, wherein the data corresponding to the first data searched on the blockchain is used as the second data.
5. The blockchain-oriented data management method according to claim 1, wherein the judging whether the first data meets a preset data compensation condition according to the first state and the second state comprises:

   Judging whether the first state of the first data can be transferred to the current data state of the second data according to a preset state transfer rule;

   If the first state of the first data can be transferred to the current data state of the second data, determining whether the second state of the first data is consistent with the current data state of the second data;

   If the second state of the first data is consistent with the current data state of the second data, determining that the first data meets the preset data compensation condition; and

   If the first state of the first data cannot be transferred to the current data state of the second data or the second state of the first data is inconsistent with the current data state of the second data, it is determined that the first data is not Meet the preset data compensation conditions.
6. The blockchain-oriented data management method according to claim 1, after the step of judging whether the first data meets a preset data compensation condition according to the first state and the second state, further comprising:

   If the first data does not meet the preset data compensation condition, an abnormal reminder is issued to the user.
7. According to the blockchain-oriented data management method of claim 6, the sending an abnormal reminder to the user includes:

   Save the first data in a preset data table; and

   The data table is sent to the user by mail to send out an abnormal reminder.
8. A block chain-oriented data management device includes:

   The first receiving unit is configured to receive a second update request sent by a user, wherein each update request includes a first state and a second state of the data to be updated, wherein the first state and the second state are the The data state of the data to be updated, where the data state is the state attribute value of the data to be updated;

   The first obtaining unit is configured to obtain data to be updated from a preset relational database according to the first state and search for data corresponding to the data to be updated from a preset blockchain, wherein the relationship is The data to be updated obtained in the type database is used as the first data, and the data corresponding to the data to be updated found on the blockchain is used as the second data;

   A first judging unit, configured to compare the first data with the second data to judge whether the first data is consistent with the second data;

   A second judgment unit, configured to judge whether the first data meets a preset data compensation condition according to the first state and the second state if the first data is inconsistent with the second data; and

   The first compensation unit is configured to perform data compensation on the first data according to the second state if the first data meets a preset data compensation condition.
9. A computer device that includes a memory, a processor, and a computer program stored in the memory and capable of running on the processor. The processor implements a blockchain-oriented data management method when the processor executes the program ,include:

   Receiving a second update request sent by the user, where each update request includes a first state and a second state of the data to be updated, wherein the first state and the second state are the data states of the data to be updated, The data status is the status attribute value of the data to be updated;

   According to the first state, the data to be updated is obtained from a preset relational database and the data corresponding to the data to be updated is searched on the preset blockchain, wherein the data to be updated obtained in the relational database is Data as the first data, and the data corresponding to the data to be updated found on the blockchain as the second data;

   Comparing the first data with the second data to determine whether the first data is consistent with the second data;

   If the first data is inconsistent with the second data, judging whether the first data meets a preset data compensation condition according to the first state and the second state; and

   If the first data meets a preset data compensation condition, perform data compensation on the first data according to the second state.
10. The computer device according to claim 9, wherein the method is applied to a preset user terminal, and before the step of receiving the second update request sent by the user, the method further comprises:

    If the first update request sent by the user is received, judging whether the data to be updated in the relational database meets the preset state transfer rule according to the first state and the second state of the first update request;

    If the data to be updated in the relational database meets the preset state circulation rule, update the data to be updated;

    Write the updated data to be updated on a preset blockchain by calling the update link; wherein, the update link is an interface that the blockchain provides to the client to call;

    Receiving an HTTP return code and judging whether an update exception occurs according to the HTTP return code; and

    If an update exception occurs, roll back the updated data to be updated in the relational database.
11. The computer device according to claim 10, wherein the judging whether the data to be updated in the relational database meets a preset state transfer rule according to the first state and the second state of the first update request comprises:

    Determine whether the data to be updated in the relational database can be updated from the first state to the second state according to the first state and the second state of the first update request and a preset state circulation rule.
12. The computer device according to claim 9, wherein the obtaining data to be updated from a preset relational database according to the first state and searching for data corresponding to the data to be updated from a preset blockchain comprises :

    Acquiring the data to be updated from a preset relational database according to the first state of the data to be updated, wherein the data to be updated acquired in the relational database is used as the first data; and

    Searching for data corresponding to the first data from a preset blockchain according to the first data, wherein the data corresponding to the first data searched on the blockchain is used as the second data.
13. 9. The computer device according to claim 9, wherein the judging whether the first data meets a preset data compensation condition according to the first state and the second state comprises:

    Judging whether the first state of the first data can be transferred to the current data state of the second data according to a preset state transfer rule;

    If the first state of the first data can be transferred to the current data state of the second data, determining whether the second state of the first data is consistent with the current data state of the second data;

    If the second state of the first data is consistent with the current data state of the second data, determining that the first data meets the preset data compensation condition; and

    If the first state of the first data cannot be transferred to the current data state of the second data or the second state of the first data is inconsistent with the current data state of the second data, it is determined that the first data is not Meet the preset data compensation conditions.
14. 8. The computer device according to claim 9, after the step of judging whether the first data meets a preset data compensation condition according to the first state and the second state, further comprising:

    If the first data does not meet the preset data compensation condition, an abnormal reminder is issued to the user.
15. The computer device according to claim 13, wherein the sending an abnormal reminder to the user comprises:

    Save the first data in a preset data table; and

    The data table is sent to the user by mail to send out an abnormal reminder.
16. A computer-readable storage medium having a computer program stored on the computer-readable storage medium, and when the computer program is executed by a processor, realizes a blockchain-oriented data management method, including:

    Receiving a second update request sent by the user, where each update request includes a first state and a second state of the data to be updated, wherein the first state and the second state are the data states of the data to be updated, The data status is the status attribute value of the data to be updated;

    According to the first state, the data to be updated is obtained from a preset relational database and the data corresponding to the data to be updated is searched on the preset blockchain, wherein the data to be updated obtained in the relational database is Data as the first data, and the data corresponding to the data to be updated found on the blockchain as the second data;

    Comparing the first data with the second data to determine whether the first data is consistent with the second data;

    If the first data is inconsistent with the second data, judging whether the first data meets a preset data compensation condition according to the first state and the second state; and

    If the first data meets a preset data compensation condition, perform data compensation on the first data according to the second state.
17. The computer-readable storage medium according to claim 16, wherein the method is applied to a preset user terminal, and before the step of receiving the second update request sent by the user, the method further comprises:

    If the first update request sent by the user is received, judging whether the data to be updated in the relational database meets the preset state transfer rule according to the first state and the second state of the first update request;

    If the data to be updated in the relational database meets the preset state circulation rule, update the data to be updated;

    Write the updated data to be updated on a preset blockchain by calling the update link; wherein, the update link is an interface that the blockchain provides to the client to call;

    Receiving an HTTP return code and judging whether an update exception occurs according to the HTTP return code; and

    If an update exception occurs, roll back the updated data to be updated in the relational database.
18. 18. The computer-readable storage medium according to claim 17, wherein said determining whether the data to be updated in the relational database meets a preset state transfer rule according to the first state and the second state of the first update request, include:

    Determine whether the data to be updated in the relational database can be updated from the first state to the second state according to the first state and the second state of the first update request and a preset state circulation rule.
19. The computer-readable storage medium according to claim 16, wherein the data to be updated is obtained from a preset relational database according to the first state and the data corresponding to the data to be updated is searched from a preset blockchain Data, including:

    Acquiring the data to be updated from a preset relational database according to the first state of the data to be updated, wherein the data to be updated acquired in the relational database is used as the first data; and

    Searching for data corresponding to the first data from a preset blockchain according to the first data, wherein the data corresponding to the first data searched on the blockchain is used as the second data.
20. 15. The computer-readable storage medium according to claim 16, wherein the judging whether the first data meets a preset data compensation condition according to the first state and the second state comprises:

    Judging whether the first state of the first data can be transferred to the current data state of the second data according to a preset state transfer rule;

    If the first state of the first data can be transferred to the current data state of the second data, determining whether the second state of the first data is consistent with the current data state of the second data;

    If the second state of the first data is consistent with the current data state of the second data, determining that the first data meets the preset data compensation condition; and

    If the first state of the first data cannot be transferred to the current data state of the second data or the second state of the first data is inconsistent with the current data state of the second data, it is determined that the first data is not Meet the preset data compensation conditions.

Images