A blockchain-based data management method and related device

Abstract

The embodiment of the application discloses a kind of data management method based on blockchain and related equipment, wherein, blockchain is located in blockchain system, blockchain system includes multiple node devices, node device includes management node device and non-administration node device, the method is executed by management node device, the method includes: in response to the operation request sent by target node device, the operation authority of target node device is verified, target node device is any non-administration node device in blockchain system;If the operation authority of target node device is verified successfully, the data operation requested by operation request is executed on blockchain according to operation request;Management notification is generated according to data operation, and management notification is broadcasted in blockchain system.Using the embodiment of the application, data can be uniformly managed, so as to ensure the consistency of data.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, in particular to a data management method based on a block chain and related equipment. BACKGROUND

[0002] At present, there are many data management scenarios, such as enterprise user data (such as enterprise identification, legal representative, registered capital, business scope, etc.) management scenarios, Internet user data (such as user identification, user avatar, user credit, etc.) management scenarios, medical data (such as case information, prescription information, etc.) management scenarios, etc. In these data management scenarios, often involve multiple data management functional agencies. Taking the management scenario of enterprise user data as an example, the payment supervision agency, the third-party payment agency and the industry and commerce management agency will manage the enterprise user data. These functional agencies have their own management specifications and are scattered management, which is easy to cause data inconsistency. SUMMARY

[0003] The embodiments of the present application provide a data management method based on a block chain and related equipment, which can uniformly manage data, thereby ensuring the consistency of data.

[0004] In one aspect, the embodiments of the present application provide a data management method based on a block chain, the block chain is located in a block chain system, the block chain system includes a plurality of node devices, the node devices include management node devices and non-management node devices, the method is executed by the management node device, and the method includes:

[0005] In response to an operation request sent by a target node device, verifying the operation authority of the target node device, the target node device being any non-management node device in the block chain system;

[0006] If the operation authority of the target node device is verified successfully, performing a data operation requested by the operation request on the block chain according to the operation request;

[0007] Generating a management notification according to the data operation, and broadcasting the management notification in the block chain system.

[0008] In one aspect, the embodiments of the present application provide a data management device based on a block chain, the block chain is located in a block chain system, the block chain system includes a plurality of node devices, the node devices include management node devices and non-management node devices, the data management device is arranged in the management node device, and the data management device includes:

[0009] A verification unit, configured to verify the operation authority of a target node device in response to an operation request sent by the target node device, the target node device being any non-management node device in the block chain system;

[0010] The execution unit is configured to perform, if the operation permission of the target node device is verified successfully, a data operation requested by the operation request on the blockchain according to the operation request.

[0011] The broadcasting unit is configured to generate a management notification according to the data operation, and broadcast the management notification in the blockchain system.

[0012] In one aspect, the embodiment of the present application provides a data management device based on a blockchain, the blockchain is located in a blockchain system, the blockchain system comprises a plurality of node devices, the node devices comprise a management node device and a non-management node device, the data management device is the management node device, and the data management device comprises:

[0013] The memory is configured to store a computer program.

[0014] The processor is configured to invoke the computer program stored in the memory, and perform the data management method based on the blockchain.

[0015] In one aspect, the embodiment of the present application provides a computer readable storage medium, configured to store a computer program, the computer program is adapted to be invoked by a processor and perform the data management method based on the blockchain.

[0016] In the embodiment of the present application, the management node device can respond to the operation request sent by the target node device, and verify the operation permission of the target node device, if the management node device verifies the operation permission of the target node device successfully, the management node device can perform a data operation on the blockchain according to the operation request, and generate a management notification according to the data operation, and the management node device can broadcast the management notification in the blockchain system. The management node device performs the data operation on the blockchain in the blockchain system, so that the management node device can uniformly manage the data in the blockchain. The management node device broadcasts the management notification generated according to the data operation to each node device in the blockchain system, so that the consistency of the data in the blockchain can be ensured. BRIEF DESCRIPTION OF DRAWINGS

[0017] In order to more clearly illustrate the technical solutions of the embodiments of the present application or the prior art, the drawings needed in the embodiment description will be briefly introduced. Obviously, the drawings in the following description are some embodiments of the present application, and those skilled in the art can also obtain other drawings according to these drawings without creative labor.

[0018] Figure 1 is a basic architecture diagram of a blockchain provided by the embodiment of the present application;

[0019] Figure 2 is a structural schematic diagram of a blockchain provided by the embodiment of the present application;

[0020] Figure 3 is a schematic diagram of an architecture of a blockchain system provided by an embodiment of the present application;

[0021] Figure 4 is another schematic diagram of an architecture of a blockchain system provided by an embodiment of the present application;

[0022] Figure 5a is a schematic diagram of an exemplary data management scheme provided by an embodiment of the present application;

[0023] Figure 5b is another schematic diagram of an exemplary data management scheme provided by an embodiment of the present application;

[0024] Figure 5c is yet another schematic diagram of an exemplary data management scheme provided by an embodiment of the present application;

[0025] Figure 6 is a flowchart of a data management method based on a blockchain provided by an embodiment of the present application;

[0026] Figure 7 is a flowchart of an operation permission verification method provided by an embodiment of the present application;

[0027] Figure 8 is a structural schematic diagram of a data management apparatus provided by an embodiment of the present application;

[0028] Figure 9 is a structural schematic diagram of a data management device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0029] The technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, but not all the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the scope of protection of the present application.

[0030] The embodiments of the present application relate to a blockchain. The blockchain refers to a set of decentralized, distributed storage characteristic infrastructure, specifically a data structure composed of data blocks in a time sequence in a way similar to a linked list, capable of securely storing data with a chronological relationship that can be verified within the system, and ensuring data unalterable and unforgeable by means of cryptography.

[0031] Please refer to Figure 1 , Figure 1 is a basic infrastructure diagram of a blockchain provided by an embodiment of the present application; as Figure 1As shown, the infrastructure of the blockchain mainly includes 5 levels from bottom to top, i.e. 101-105. Among them:

[0032] (1) Information data and Merkle tree are located at the bottom layer 101. The information data here refers to the original data requested to be published to the blockchain system, but has not yet formed a block, which can be enterprise user data, transaction data, etc. These original data need to be further processed (such as verified by each node device in the blockchain system, hashed, etc.) before being written into the block. Merkle tree is an important part of blockchain technology. The blockchain does not directly save the plaintext original data, and the original data needs to be hashed and stored in the form of hash value. The Merkle tree is used to organize the hash values of multiple original data obtained by hash operation in a binary tree structure and save them in the block body.

[0033] (2) The block is located at level 102. The block is a data block, and the information data at the bottom layer 101 is written into the block at level 102 after further processing. Multiple blocks are connected in a chain structure, i.e. to form a blockchain. Please refer to Figure 2 , Figure 2 is a structural diagram of a blockchain provided by an embodiment of the present application; as Figure 2 shown, the blocks 201, 202 and 203 are connected in a chain structure. Among them, the block 202 is divided into a block header and a block body, the block header contains the digest value of the previous block 201, the digest value of the block 202 and the Merkle root of the block. The block body contains the complete data of the block 202 and is organized in the form of a Merkle tree.

[0034] (3) The protocol and mechanism followed by the blockchain are located at level 103. These protocols can include: P2P (Peer-to-Peer, peer-to-peer network) protocol; mechanisms can include but are not limited to: broadcast mechanism, consensus mechanism (including PoW (Proof Of Work, proof of work) mechanism, POS (Proof Of Stake, proof of stake) mechanism, etc. Core mechanism).

[0035] (4) The blockchain system is located at level 104. The blockchain system is composed of multiple node devices; node devices can include but are not limited to PC (Personal Computer, personal computer), server, smart phone, tablet computer, mobile computer, etc. Please refer to Figure 3 , Figure 3is a schematic diagram of an architecture of a blockchain system provided by an embodiment of the present application; seven node devices are taken as an example for illustration in the diagram, the node devices in the blockchain system are networked in a P2P manner, and the node devices communicate with each other according to a P2P protocol; each node device jointly complies with a broadcast mechanism and a consensus mechanism (including a PoW mechanism, a POS mechanism, and other core mechanisms), and jointly ensures the data on the blockchain to be tamper-proof and unforgeable, and meanwhile realizes the decentralization and trustlessness of the blockchain.

[0036] (5) The smart contract is located in the upper layer 105. The smart contract is a set of situational response type programmed rules and logic, and is a decentralized and information-shareable program code deployed on the blockchain. The parties signing the contract reach an agreement on the contract content, and deploy the smart contract in the blockchain, so that the contract can be automatically executed on behalf of each signing party without relying on any central institution.

[0037] In an embodiment of the present application, the node devices in the blockchain system can be divided into management node devices and non-management node devices. The blockchain is specifically stored in each node device of the blockchain system. The management node devices can uniformly manage the non-management node devices in the blockchain system, and the management here can include but is not limited to permission granting, permission verification, permission withdrawal, and issuing of management notifications.

[0038] In order to uniformly manage data and ensure the consistency of data, an embodiment of the present application introduces the blockchain into the scene of data management, and proposes a data management method based on the blockchain and related equipment.

[0039] Based on the above description, please refer to Figure 4 , Figure 4 is another schematic diagram of an architecture of a blockchain system provided by an embodiment of the present application. As shown in Figure 4 , the blockchain system includes a management node device 401 and a plurality of non-management node devices 402 connected to the management node device 401.

[0040] In the blockchain system composed of the management node device 401 and the plurality of non-management node devices 402, the management node device 401 can respond to an operation request sent by a target node device and verify the operation authority of the target node device, and if the verification is successful, it can be determined that the target node device has the operation authority. The operation request can be broadcasted by the target node device in the blockchain system, and each node device in the blockchain system can respond to the operation request sent by the target node device and verify the operation authority of the target node device when receiving the operation request. The operation request can be used to request to perform a data operation on the blockchain in the blockchain system, and the target node device can be any of the plurality of non-management node devices 402. The operation request can include but is not limited to a query operation request or a modification operation request. The query operation request can be used to request to perform a query operation on the data in the blockchain. The modification operation request can be used to request to perform a modification operation on the data in the blockchain. The modification operation can include any of the following: adding data operation, deleting existing data operation, and modifying existing data operation. The data in the blockchain can include but is not limited to at least one of the following: enterprise user data, Internet user data, and medical data.

[0041] In an implementation manner, the management node device 401 can verify the operation authority of the target node device in the following two ways: the first way is that the management node device 401 verifies the operation authority of the target node device by itself; the second way is that each node device in the blockchain system verifies the operation authority of the target node device together, and if more than 50% or 2 / 3 of the node devices verify the operation authority of the target node device successfully, the verification of the operation authority of the target node device is successful.

[0042] In an implementation, if the operation request broadcasted by the target node device into the blockchain system is a modification operation request, and the modification operation authority verification of the target node device succeeds, the target node device has the modification operation authority, the management node device 401 executes a modification operation on the data in the blockchain according to the modification content carried in the modification operation request. For example, assuming that the modification content carried in the modification operation request sent by the target node device indicates that the name of a certain enterprise user is modified from A to B, the management node device 401 modifies the name of the enterprise user from A to B in the blockchain after confirming that the target node device has the modification operation authority. The modification process can be to store the new name B of the enterprise user in a new block, and to overwrite the content in the existing old block with the content of the new block to achieve modification and update. In order to further ensure data security, the management node device 401 also verifies the modification content before executing the modification operation. The purpose of the verification is to confirm whether the modification content is trustworthy. If the verification succeeds, it means that the modification content is trustworthy, and the management node device 401 can update the data in the blockchain according to the modification content. If the verification fails, it means that the modification content is untrustworthy and there is a risk, and the management node device 401 can discard the modification operation request without processing. The verification method can be flexibly selected according to actual needs. For example, if the credit of the target node device is high and the management node device 401 highly trusts the target node device, it can directly confirm that the modification content is trustworthy and the verification succeeds. For another example, the nodes in the blockchain system can jointly verify the modification content. If more than 50% or 2 / 3 of the nodes approve the modification content, the verification succeeds. For another example, the modification content can be an encrypted stamp. The nodes in the blockchain system can jointly verify the encrypted stamp. If more than 50% or 2 / 3 of the nodes approve the encrypted stamp, the verification succeeds. The encrypted stamp can be obtained by encrypting the plaintext modification content with a predetermined key (such as the private key of the business system, the private key of the credit system, etc.) after the plaintext modification content is sent to the information system (such as the business system, the credit system, etc.) associated with the blockchain system. For another example, the management node device 401 can also send the modification content to the information system associated with the blockchain system, and actively verify the modification content by means of the associated information system.

[0043] In another implementation, if the operation request broadcasted by the target node device into the blockchain system is a query operation request, and the query operation authority verification of the target node device succeeds, the target node device has the query operation authority, the management node device 401 queries the data requested by the target node device from the blockchain, and returns the queried requested data to the target node device.

[0044] The management node device 401 can also generate a management notification according to the data operation performed by the management node device 401 on the data in the blockchain, and broadcast the management notification to each node device in the blockchain system. The management notification records the data operation performed by the management node device 401 on the data in the blockchain. The node device in the blockchain system can update the data stored in the node device according to the management notification. The node device in the blockchain system can also trace the operation of the data in the blockchain according to the management notification.

[0045] It can be understood that the blockchain system described in the embodiments of the present application is for more clearly illustrating the technical solutions of the embodiments of the present application, and does not constitute a limitation on the technical solutions provided by the embodiments of the present application. Those skilled in the art can know that, with the evolution of system architecture and the appearance of new business scenarios, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems.

[0046] Taking the management scenario of enterprise user data as an example, please refer to Figure 5a , Figure 5ais a schematic diagram of an exemplary data management scheme provided by the embodiments of the present application. The management node device is a node device used by the payment regulatory authority, the target node device is a node device used by the third-party payment institution A, and the non-management node device is a node device used by the third-party payment institution B and the third-party payment institution C. The third-party payment institution A broadcasts a modification operation request in the blockchain system, and the modification operation request is used to request to perform a modification operation on the enterprise user data in the blockchain according to the modification content carried in the modification operation request. When the payment regulatory authority, the third-party payment institution A, the third-party payment institution B and the third-party payment institution C receive the modification operation request sent by the third-party payment institution A, they all respond to the modification operation request sent by the third-party payment institution A. The payment regulatory authority, the third-party payment institution A, the third-party payment institution B and the third-party payment institution C all verify the modification operation authority of the third-party payment institution A successfully. The third-party payment institution A has the modification operation authority. The payment regulatory authority sends the modification content to the industrial and commercial system associated with the blockchain system for verification. After receiving the verification passed notification sent by the industrial and commercial system, the payment regulatory authority determines that the modification content is verified, and the payment regulatory authority updates the enterprise user data in the blockchain according to the modification content. The payment regulatory authority also generates a management notification according to the modification operation of the payment regulatory authority on the enterprise user data in the blockchain, and sends the management notification to the third-party payment institution A, the third-party payment institution B and the third-party payment institution C. The third-party payment institution A, the third-party payment institution B and the third-party payment institution C can update the enterprise user data stored in the local storage space according to the management notification. The third-party payment institution A, the third-party payment institution B and the third-party payment institution C can also trace the modification operation of the payment regulatory authority on the enterprise user data in the blockchain according to the management notification.

[0047] Taking the management scenario of enterprise user data as an example, please refer to Figure 5b , Figure 5bis a schematic diagram of another exemplary data management scheme provided by the embodiments of the present application. The management node device is a node device used by the payment regulatory authority, the target node device is a node device used by the third-party payment institution 2, and the non-management node device is a node device used by other third-party payment institutions. The third-party payment institution 2 broadcasts a modification operation request in the blockchain system, and the modification operation request is used to request to perform a modification operation on the enterprise user data in the blockchain according to the modification content carried in the modification operation request. The modification content is an encrypted stamp, which can be obtained by encrypting the plaintext modification content using the private key of the industrial and commercial system after the third-party payment institution 2 sends the plaintext modification content to the industrial and commercial system associated with the blockchain system and the industrial and commercial system verifies the plaintext modification content. When the payment regulatory authority and each third-party payment institution receives the modification operation request sent by the third-party payment institution 2, they all respond to the modification operation request sent by the third-party payment institution 2, and the payment regulatory authority and each third-party payment institution jointly verify the modification operation authority of the third-party payment institution 2. After verification, more than 50% of the institutions successfully verify the modification operation authority of the third-party payment institution 2, and the third-party payment institution 2 has the modification operation authority. Each institution in the blockchain system jointly verifies the encrypted stamp. Each institution first verifies the legality of the encrypted stamp. If the encrypted stamp is a legal stamp, each institution then decrypts the encrypted stamp using the public key of the industrial and commercial system. If the decryption is successful, each institution determines that the encrypted stamp passes the verification, and each institution sends a verification pass notification to the payment regulatory authority. The payment regulatory authority receives the verification pass notification returned by more than 50% of the institutions in the blockchain system, and determines that the encrypted stamp passes the verification. The payment regulatory authority decrypts the encrypted stamp using the public key of the industrial and commercial system to obtain the plaintext modification content, and updates the enterprise user data in the blockchain according to the plaintext modification content. The payment regulatory authority also generates a management notification according to the modification operation of the payment regulatory authority on the enterprise user data in the blockchain, and sends the management notification to each third-party payment institution. Each third-party payment institution can update the enterprise user data stored in the local storage space of each third-party payment institution according to the management notification. Each third-party payment institution can also trace the modification operation of the payment regulatory authority on the enterprise user data in the blockchain according to the management notification.

[0048] Taking the management of enterprise user data as an example, please refer to Figure 5c , Figure 5cis a schematic diagram of another exemplary data management scheme provided by the embodiments of the present application. The management node device is a node device used by the payment regulatory authority, the target node device is a node device used by the third-party payment institution A, and the non-management node device is a node device used by the third-party payment institution B and the third-party payment institution C. The third-party payment institution A broadcasts a query operation request in the blockchain system, and the query operation request is used to request to perform a query operation on enterprise user data in the blockchain. When the payment regulatory authority, the third-party payment institution A, the third-party payment institution B and the third-party payment institution C receive the query operation request sent by the third-party payment institution A, the payment regulatory authority, the third-party payment institution A, the third-party payment institution B and the third-party payment institution C all respond to the query operation request sent by the third-party payment institution A, the query operation authority of the third-party payment institution A is verified successfully by the payment regulatory authority, the third-party payment institution A, the third-party payment institution B and the third-party payment institution C, the third-party payment institution A has the query operation authority, the payment regulatory authority obtains the enterprise user data from the blockchain, and sends the obtained enterprise user data to the third-party payment institution A. The payment regulatory authority also generates a management notification according to the query operation of the payment regulatory authority on the enterprise user data in the blockchain, and sends the management notification to the third-party payment institution A, the third-party payment institution B and the third-party payment institution C. The third-party payment institution A, the third-party payment institution B and the third-party payment institution C can update the enterprise user data stored in the local storage space according to the management notification. The third-party payment institution A, the third-party payment institution B and the third-party payment institution C can also trace the query operation of the payment regulatory authority on the enterprise user data in the blockchain according to the management notification.

[0049] Based on Figure 4 the architecture schematic diagram of the blockchain system shown in FIG. 1, please refer to Figure 6 , Figure 6 is a flow schematic diagram of a data management method based on a blockchain provided by the embodiments of the present application. The method is executed by the management node device shown in FIG. 1, and the method comprises the following steps S601 to S605: Figure 4

[0050] Step S601: receiving an operation request sent by a target node device.

[0051] In an implementation mode, the target node device broadcasts the operation request in the blockchain system, and each node device of the blockchain system can receive the operation request, so the management node device can also receive the operation request sent by the target node device.

[0052] Step S602: responding to the operation request sent by the target node device, and verifying the operation authority of the target node device.

[0053] ​In an implementation, the management node device can respond to the operation request sent by the target node device and verify the operation authority of the target node device to determine whether the target node device has the operation authority. If the target node device has the operation authority, the management node device can perform the data operation requested by the operation request on the blockchain according to the operation request sent by the target node device. If the target node device does not have the operation authority, the management node device can send a verification failure notification to the target node device, and the management node device can also delete the operation request sent by the target node device from the storage space of the management node device. The execution process of the management node device responding to the operation request sent by the target node device and verifying the operation authority of the target node device can refer to the specific description of Figure 7

[0054] Step S603: If the operation authority verification of the target node device is successful, performing the data operation requested by the operation request on the blockchain according to the operation request.

[0055] In an implementation, if the operation authority verification of the target node device is successful, the target node device has the operation authority, and the management node device can perform the data operation requested by the operation request on the blockchain according to the operation request. The operation authority can include a query operation authority and a modification operation authority. The data operation can include a query operation on the target data and a modification operation on the target data. If the target node device has the query operation authority, the management node device can perform the query operation on the target data in the blockchain according to the query operation request. If the target node device has the modification operation authority, the management node device can perform the modification operation on the target data in the blockchain according to the modification operation request.

[0056] In an implementation, if the data operation is the query operation on the target data, the management node device can obtain the target data from the blockchain, and the management node device can send the target data to the target node device.

[0057] In an implementation, if the data operation is the modification operation on the target data, the operation request received by the management node device from the target node device can carry the modification content. The management node device can verify the modification content. If the verification is passed, the management node device updates the target data in the blockchain according to the modification content.

[0058] In an implementation, the verification method can include a first verification method, a second verification method, and a third verification method. If the credit of the target node device is high, the management node device can verify the modification content according to the first verification method. The verification method of the common verification of the modification content by each node device in the blockchain system is the second verification method. The verification method of the management node device sending the modification content to the information system associated with the blockchain system for verification is the third verification method.​

[0059] In an implementation manner, the verification manner can be the first verification manner. The management node device can obtain a credit evaluation level of the target node device. If the credit evaluation level of the target node device is higher than a second credit level threshold, the management node device can determine that the target node device is a node device highly recognized by the management node, and the management node device can determine that the modification content passes the verification. The credit evaluation level is information for judging the credit degree of the target node device. The higher the credit evaluation level is, the higher the credit degree of the node device is, and the higher the probability of being trusted is. Conversely, the lower the credit evaluation level is, the lower the credit degree of the node device is, and the lower the probability of being trusted is.

[0060] In an implementation manner, the verification manner can be the second verification manner. Each node device in the blockchain system can jointly verify the modification content. The specific process in which each node device in the blockchain system verifies the modification content can be that each node device in the blockchain system verifies the private key signature of the target node device in the modification content by using the public key of the target node device, and sends a verification result of passing the verification to the management node device if the verification of the private key signature of the target node device passes. After each node device in the blockchain system verifies the modification content, the management node device counts the verification results of the modification content by each node device in the blockchain system. If the number of verification results of passing the verification in the verification results is greater than a second number threshold, the management node device determines that the modification content passes the verification. If the number of verification results of passing the verification in the verification results is less than or equal to the second number threshold, the management node device determines that the modification content fails the verification.

[0061] In an implementation manner, the verification manner can be a second verification manner. The modified content can be a cryptographic stamp. The cryptographic stamp can be obtained by the information system associated with the blockchain system (for example, a business system, a credit investigation system, and the like) verifying the modified content in plaintext after the target node device sends the modified content in plaintext to the information system associated with the blockchain system, and encrypting the modified content in plaintext by using a predetermined key (for example, a private key of the business system, a private key of the credit investigation system, and the like) after the verification is passed. The specific process of the nodes in the blockchain system verifying the cryptographic stamp can be as follows: the nodes in the blockchain system check the legality of the cryptographic stamp, and if the legality is passed, the cryptographic stamp is decrypted by using a predetermined key (for example, a public key of the business system, a public key of the credit investigation system, and the like); if the decryption is successful, a verification result passed is obtained, and the verification result passed is sent to the management node device. The management node device counts the verification results of the cryptographic stamp of the nodes in the blockchain system; if the number of verification results passed in the verification results is greater than a second number threshold, the management node device determines that the cryptographic stamp is passed. If the number of verification results passed in the verification results is less than or equal to the second number threshold, the management node device determines that the cryptographic stamp is failed.

[0062] The second number threshold can be one-half, two-thirds, or four-fifths of the total number of nodes in the blockchain system, and the like.

[0063] In an implementation manner, the verification manner can be a third verification manner. The management node device can send the modified content to the information system associated with the blockchain system for verification. The specific execution process of the information system associated with the blockchain system verifying the modified content can be as follows: the information system associated with the blockchain system compares the modified content with the related data stored locally by the information system, and if the modified content is consistent with the related data stored locally by the information system, the information system associated with the blockchain system feeds back a verification passed notification to the management node device. If the management node device receives the verification passed notification fed back by the information system associated with the blockchain system, the management node device can determine that the modified content is passed. If the management node device does not receive the verification passed notification fed back by the information system associated with the blockchain system, or receives a verification failed notification fed back by the information system associated with the blockchain system, the management node device can determine that the modified content is failed.

[0064] Taking the management scenario of enterprise user data as an example, the payment regulatory authority receives a modification operation request from a third-party payment institution, the modification operation request being used to request the management node device to perform a modification operation on the business license of XX enterprise in the blockchain, and the modification operation request carrying modification content. If the payment regulatory authority determines that the third-party payment institution has the modification operation authority, the payment regulatory authority sends the modification content to the industrial and commercial system associated with the blockchain system for verification, the industrial and commercial system compares the business license of XX enterprise in the modification content with the business license of XX enterprise stored locally in the industrial and commercial system, and if the business license of XX enterprise in the modification content is consistent with the business license of XX enterprise stored locally in the industrial and commercial system, the industrial and commercial system feeds back a verification pass notification to the payment regulatory authority. If the payment regulatory authority receives the verification pass notification fed back by the industrial and commercial system, the management node device determines that the modification content passes verification.

[0065] In an implementation manner, the verification manner of the obtained target data is related to the type of the target data.

[0066] For example, in the management scenario of enterprise user data, if the target data is "contact information of XX enterprise", "communication address of XX enterprise" and the like, which are data of a lower confidentiality level, the verification manner obtained by the management node device can be the first verification manner. If the target data is "business license of XX enterprise", "fingerprint of the legal representative of XX enterprise" and the like, which are data of a higher confidentiality level, the verification manner obtained by the management node device can be the second verification manner or the third verification manner. In this way, the management node device can obtain the verification manner related to the type of the target data, the verification manner of the modification content is flexible and diverse, and the accuracy of the verification result can be improved.

[0067] Step S604: generating a management notification according to the data operation.

[0068] If the target node device has the operation authority, the management node device can perform a data operation on the blockchain according to the operation request, and the management node device can also generate a management notification according to the data operation. The management notification records the data operation performed by the management node device on the data in the blockchain.

[0069] In an implementation, the management notification can include a first management notification and a second management notification. The first management notification carries the operation content of the data operation, and the second management notification does not carry the operation content of the data operation. If the data operation is a query operation on the target data in the blockchain, the first management notification carries the operation content of the query operation on the target data in the blockchain; if the data operation is a modification operation on the target data in the blockchain, the first management notification carries the operation content of the modification operation on the target data in the blockchain. The operation content of the query operation can include the device identifier of the target node device, the operation time, the query content, the operation result, and the like. The operation content of the modification operation can include the device identifier of the target node device, the operation time, the modification content, the operation result, and the like.

[0070] Step S605: broadcast the management notification in the blockchain system.

[0071] The management node device can broadcast the management notification to each node device in the blockchain system.

[0072] In an implementation, the management node device can send the first management notification to a non-management node in the blockchain system that has an operation right. The management node device can send the second management notification to a non-management node device in the blockchain system that does not have an operation right. The non-management node device receiving the first management notification can update the target data stored locally by the non-management node device according to the operation content carried in the first management notification. The non-management node device receiving the second management notification can store the second management notification and trace the data operation performed by the management node device on the target data in the blockchain according to the management notification. Since the management notification is stored in each node device, all data operations on the blockchain can be traced based on the management notification, thereby realizing the post-management of the data operation; and the management node device can perform the pre-management before the data operation is performed by each node device, and the pre-post management can effectively improve the management strength of the management node device.

[0073] For example, in the management scenario of enterprise user data, the management node device is a node device used by a payment regulatory authority, the target node device is a node device used by a third-party payment institution A, and the non-management node device is a node device used by a third-party payment institution B. After receiving the modification operation request sent by the third-party payment institution A and determining that the third-party payment institution A has the modification operation authority, the payment regulatory authority can perform a modification operation on the contact information of an XX enterprise on the blockchain according to the modification operation request. The payment regulatory authority can also generate a management notification (a first management notification and a second management notification) according to the modification operation. The operation content carried in the first management notification can be "the third-party payment institution with a device identifier of XX requests to modify the contact information of the XX enterprise from A to B at XX time, and the modification is successful". If the third-party payment institution B has the operation authority, the payment regulatory authority can send the first management notification to the third-party payment institution B, and the third-party payment institution B can update the contact information of the XX enterprise stored locally according to the operation content carried in the first management notification. If the third-party payment institution B does not have the operation authority, the payment regulatory authority can send the second management notification to the third-party payment institution B, and the third-party payment institution B can store the second management notification and trace the modification operation performed by the payment regulatory authority on the target data in the blockchain according to the management notification.

[0074] For example, in the management scenario of enterprise user data, the payment regulatory authority receives a query operation request sent by the third-party payment institution A, and determines that the third-party payment institution A has the query operation authority. The payment regulatory authority can send the communication address of the XX enterprise on the blockchain to the third-party payment institution A according to the query operation request. The payment regulatory authority can also generate a management notification (a first management notification and a second management notification) according to the query operation. The operation content carried in the first management notification can be "the third-party payment institution with a device identifier of XX requests to query the communication address of the XX enterprise at XX time, and the query is successful". If the third-party payment institution B has the operation authority, the payment regulatory authority can send the first management notification to the third-party payment institution B, and the third-party payment institution B can determine whether to update the communication address of the XX enterprise stored locally according to the operation content carried in the first management notification. If the third-party payment institution B does not have the operation authority, the payment regulatory authority can send the second management notification to the third-party payment institution B, and the third-party payment institution B can store the second management notification and trace the query operation performed by the payment regulatory authority on the target data in the blockchain according to the management notification.

[0075] Through the embodiments of the present application, the management node device can respond to the operation request sent by the node device in the blockchain system, and can perform data operation on the data in the blockchain according to the operation request, so that the management node device can uniformly manage the data in the blockchain. In addition, the management node device can broadcast the management notification generated according to the data operation in the blockchain system, the node device with operation permission can update the data stored locally according to the management notification, and the node device without operation permission can store the management notification, thereby ensuring the consistency of the data. In addition, if the operation request sent by the target node device to the management node device is a query operation for requesting the data operation on the target data in the blockchain, the management node device returns the target data queried to the target node device. If the operation request sent by the target node device to the management node device is a modification operation for requesting the data operation on the target data in the blockchain, the management node device checks the modification content to ensure that the data updated in the blockchain is the data that passes the check.

[0076] Please refer to Figure 7 , Figure 7 is a flow diagram of an operation permission verification method provided by an embodiment of the present application. The method is executed by the management node device shown in Figure 4 , and the method comprises the following steps S701-S702:

[0077] Step S701: When receiving the operation request sent by the target node device, the management node device acquires the authorized device list corresponding to the operation type.

[0078] When receiving the operation request sent by the target node device, the management node device can acquire the authorized device list corresponding to the operation type. The authorized device list can be represented as Table 1 as follows:

[0079] Table 1: Operation type-authorized device list

[0080]

[0081] As shown in the above table, the authorized device list can include a plurality of authorized device identifiers, and each authorized device identifier corresponds to a node device granted the operation permission of the operation type by the management node device. Among them, the authorized device identifier can be the IP address of the node device.

[0082] In an implementation manner, if the operation type of the data operation is a query operation, the management node device can obtain an authorized device list corresponding to the query operation. The authorized device list corresponding to the query operation can include a plurality of authorized device identifiers, and each authorized device identifier corresponds to a node device that is granted a query operation right corresponding to the query operation by the management node device. If the operation type of the data operation is a modification operation, the management node device can obtain an authorized device list corresponding to the modification operation. The authorized device list corresponding to the modification operation can include a plurality of authorized device identifiers, and each authorized device identifier corresponds to a node device that is granted a modification operation right corresponding to the modification operation by the management node device.

[0083] In an implementation manner, the authorized device list can be configured in the following manner: the management node device can obtain a credit evaluation level of each non-management node device in the blockchain system; the management node device further obtains a first credit level threshold corresponding to the operation type of the data operation; and the management node device adds a device identifier of a non-management node device with a credit evaluation level higher than the first credit level threshold to the authorized device list corresponding to the operation type of the data operation. The first credit level threshold corresponding to the query operation and the first credit level threshold corresponding to the modification operation can be different. The credit evaluation level is information for judging the credit of the non-management node device. The higher the credit evaluation level, the higher the credit of the node device and the higher the probability of being trusted. Conversely, the lower the credit evaluation level, the lower the credit of the node device and the lower the probability of being trusted.

[0084] For example, in the management scenario of enterprise user data, the management node device is a node device used by a payment regulatory agency, the target node device is a node device used by a third-party payment agency A, and the non-management node device is a node device used by a third-party payment agency B. The first credit level threshold corresponding to the query operation is "A level", the first credit level threshold corresponding to the modification operation is "AAA level", and "AAA level" is higher than "A level". The credit evaluation level of the third-party payment agency A is "AAAA level", which is higher than "AAA level" and "A level". The management node device grants the third-party payment agency A the modification operation right corresponding to the modification operation and the query operation right corresponding to the query operation, and adds the device identifier of the third-party payment agency A to the authorized device list corresponding to the modification operation and the authorized device list corresponding to the query operation. The credit evaluation level of the third-party payment agency B is "AA level", which is lower than "AAA level" and higher than "A level". The management node device grants the third-party payment agency B the query operation right corresponding to the query operation, and adds the device identifier of the third-party payment agency B to the authorized device list corresponding to the query operation.

[0085] In an implementation, the management node device can also update the authorized device list, and the method for updating the authorized device list by the management node device can be: the management node device can detect changes in the credit evaluation level of each non-management node device in the blockchain system; and the management node device can update the authorized device list according to the changes in the credit evaluation level of each non-management node device in the blockchain system.

[0086] For example, if the credit evaluation level of the non-management node device A changes from being higher than the first credit level threshold to being lower than the first credit level threshold, the management node device can delete the device identifier of the non-management node device A from the authorized device list; and if the credit evaluation level of the non-management node device B changes from being lower than the first credit level threshold to being higher than the first credit level threshold, the management node device can add the device identifier of the non-management node device B to the authorized device list.

[0087] Step S702: If the device identifier of the target node device is an authorized device identifier in the authorized device list, the management node device determines that the target node device has the operation right.

[0088] In an implementation, if the device identifier of the target node device is an authorized device identifier in the authorized device list, the management node device can determine that the target node device has the operation right.

[0089] For example, if the device identifier of the target node device is an authorized device identifier in the authorized device list corresponding to the query operation, the management node device can determine that the target node device has the query operation right; and if the device identifier of the target node device is an authorized device identifier in the authorized device list corresponding to the modification operation, the management node device can determine that the target node device has the modification operation right.

[0090] In an implementation manner, the method for the management node device to verify the operation permission of the target node device can further include: when receiving the operation request sent by the target node device, the management device acquires an authorized device list corresponding to the operation type, and sends the authorized device list to each node device in the blockchain system, so that each node device in the blockchain system verifies the operation permission of the target node device according to the authorized device list. The method for each node device in the blockchain system to verify the operation permission of the target node device is the same as the method for the management node device to verify the operation permission of the target node device, and can refer to the description of the method for the management node device to verify the operation permission of the target node device. If the operation permission of the target node device is verified successfully by each node device in the blockchain system, each node device in the blockchain system sends a verification success notification to the management node device. If the management node device receives the verification success notification returned by more than a first number threshold of node devices, it is determined that the operation permission of the target node device is verified successfully. If the management node device receives the verification success notification returned by less than or equal to the first number threshold of node devices, it is determined that the operation permission of the target node device is verified unsuccessfully.

[0091] The second number threshold can be one half, two thirds, or four fifths of the total number of node devices in the blockchain system, and the like.

[0092] According to the embodiments of the present application, the management node device can uniformly manage the permissions of the node devices in the blockchain system, including permission granting, permission verification, and permission withdrawal.

[0093] Please refer to Figure 8 , Figure 8 is a structural schematic diagram of a data management apparatus provided by the embodiments of the present application. The data management apparatus 80 can be a computer program (including program code) running in the management node device 401, for example, an application software in the management node device 401. The data management apparatus can be used to execute the corresponding steps in the method shown in Figure 6 or Figure 7 . Please refer to Figure 8 , the data management apparatus includes the following units:

[0094] The verification unit 801 is configured to verify the operation permission of the target node device in response to the operation request sent by the target node device, the target node device being any non-management node device in the blockchain system.

[0095] The execution unit 802 is configured to perform the data operation requested by the operation request on the blockchain according to the operation request if the operation permission of the target node device is verified successfully.

[0096] ​The broadcast unit 803 is configured to generate a management notification according to a data operation, and broadcast the management notification in the blockchain system.

[0097] In an implementation manner, the operation request carries a device identifier of the target node device and an operation type of the data operation requested by the target node device; and the verification unit 801, in response to the operation request sent by the target node device, is specifically configured to:

[0098] When receiving the operation request sent by the target node device, the verification unit 801 acquires an authorized device list corresponding to the operation type, the authorized device list including a plurality of authorized device identifiers, each authorized device identifier corresponding to a node device being granted an operation right corresponding to the operation type.

[0099] If the device identifier of the target node device is an authorized device identifier in the authorized device list, it is determined that the target node device has the operation right.

[0100] In an implementation manner, the authorized device list is configured by the verification unit 801 through the following method:

[0101] Acquiring credit evaluation levels of each non-management node device in the blockchain system;

[0102] Acquiring a first credit level threshold corresponding to the operation type;

[0103] Adding a device identifier of a non-management node device with a credit evaluation level higher than the first credit level threshold to the authorized device list corresponding to the operation type.

[0104] In an implementation manner, the verification unit 801 is further configured to:

[0105] Detecting changes in credit evaluation levels of each non-management node device in the blockchain system;

[0106] Updating the authorized device list according to the changes in credit evaluation levels of each non-management node device in the blockchain system.

[0107] In an implementation manner, the operation request carries an operation type of a data operation requested by the target node device; and the verification unit 801, in response to the operation request sent by the target node device, is specifically configured to:

[0108] When receiving the operation request sent by the target node device, the verification unit 801 acquires an authorized device list corresponding to the operation type;

[0109] The authorized device list is sent to each node device in the blockchain system, so that each node device in the blockchain system verifies the operation permission of the target node device according to the authorized device list, and the authorized device list includes a plurality of authorized device identifiers, and each authorized device identifier corresponds to a node device that is granted an operation permission of a corresponding operation type;

[0110] If a verification success notification returned by a node device exceeding the first number threshold is received, it is determined that the operation permission verification of the target node device is successful.

[0111] In an implementation manner, the data operation is a modification operation on target data, and the operation request carries modification content of the target data; when the execution unit 802 performs the data operation on the blockchain according to the operation request, the execution unit 802 is specifically configured to:

[0112] verify the modification content;

[0113] If the verification is passed, the target data in the blockchain is updated according to the modification content.

[0114] In an implementation manner, when the execution unit 802 verifies the modification content, the execution unit 802 is specifically configured to:

[0115] obtain a credit evaluation level of the target node device;

[0116] If the credit evaluation level of the target node device is higher than a second credit level threshold, it is determined that the modification content verification is passed.

[0117] In an implementation manner, when the execution unit 802 verifies the modification content, the execution unit 802 is specifically configured to:

[0118] send the modification content to an associated information system for verification;

[0119] If a verification pass notification fed back by the associated information system is received, it is determined that the modification content verification is passed.

[0120] In an implementation manner, the operation request is obtained by broadcasting in the blockchain system by the target node device; when the execution unit 802 verifies the modification content, the execution unit 802 is specifically configured to:

[0121] statistically obtain a verification result of the modification content by each node device in the blockchain system;

[0122] If the number of verification results that pass the verification in the verification result is greater than a second number threshold, it is determined that the modification content verification is passed.

[0123] In an implementation manner, the modified content is an encrypted seal, the encrypted seal is obtained by encrypting the modified content in plaintext by a predetermined key after the target node device sends the modified content in plaintext to the associated information system, and the associated information system checks the modified content in plaintext and passes the check; the checking process of the encrypted seal by any node device in the blockchain system includes:

[0124] checking the legality of the encrypted seal;

[0125] if the legality passes, decrypting the encrypted seal by the predetermined key;

[0126] if the decryption succeeds, obtaining a check result passing the check.

[0127] In an implementation manner, the management notification includes a first management notification and a second management notification, the first management notification carries operation content of a data operation, and the second management notification does not carry the operation content of the data operation; when the broadcasting unit 803 broadcasts the management notification in the blockchain system, the broadcasting unit 803 is specifically configured to:

[0128] send the first management notification to a non-management node device in the blockchain system that has an operation permission;

[0129] send the second management notification to a non-management node device in the blockchain system that does not have the operation permission.

[0130] According to the embodiments of the present application, Figure 8 The units in the data management apparatus 80 shown in the embodiments of the present application can be combined into one or several other units respectively or all, or some of the units can be further split into a plurality of units with smaller functions to constitute, which can realize the same operation without affecting the realization of the technical effects of the embodiments of the present application. The units are divided based on logical functions, and in actual application, the functions of one unit can be realized by multiple units, or the functions of multiple units can be realized by one unit. In other embodiments of the present application, the data management apparatus 80 can also include other units, and in actual application, these functions can also be realized by other units and can be realized by multiple units in cooperation. According to the embodiments of the present application, the data management apparatus 80 can be constructed by running a computer program (including program codes) related to each step of the corresponding method shown in, for example, Figure 6 or Figure 7 the embodiments of the present application, on a general computing device including processing elements and storage elements such as a central processing unit (CPU), a random access memory (RAM), a read-only memory (ROM), and the like. Figure 8The data management apparatus shown in the method and the data management apparatus shown in the method, and the data management method based on the blockchain implemented by the embodiments of the application. The computer program can be recorded on, for example, a computer readable storage medium, and loaded into the above-mentioned computing device through the computer readable storage medium, and run therein.

[0131] In the embodiments of the application, the management node device can respond to the operation request sent by the target node device and verify the operation authority of the target node device. If the management node device verifies the operation authority of the target node device successfully, the management node device can execute data operation on the blockchain according to the operation request, and generate a management notification according to the data operation. The management node device can broadcast the management notification in the blockchain system. By executing data operation on the blockchain in the blockchain system by the management node device, the management node device can uniformly manage the data in the blockchain. Broadcasting the management notification generated according to the data operation to each node device in the blockchain system by the management node device can ensure the consistency of the data in the blockchain.

[0132] Please refer to Figure 9 , Figure 9 is a structural schematic diagram of a data management device 90 provided by the embodiments of the application. The data management device 90 at least includes a processor 901, an input device 903, an output device 902 and a computer readable storage medium 904. The processor 901, the input device 903, the output device 902 and the computer readable storage medium 904 can be connected through a bus or other means. The computer readable storage medium 904 can be stored in a memory, and is used to store a computer program. The computer program includes program instructions, and the processor 901 is used to execute the program instructions stored in the computer readable storage medium 904. The processor 901 (or CPU (Central Processing Unit, central processor)) is the computing core and control core of the data management device 90, and is suitable for implementing one or more instructions, and is specifically suitable for loading and executing one or more instructions to realize the corresponding method flow or corresponding function.

[0133] The embodiment of the present application further provides a computer readable storage medium (Memory), which is a memory device in the data management device 90, used for storing programs and data. It can be understood that the computer readable storage medium herein can include the built-in storage medium in the data management device 90, and of course can also include the extended storage medium supported by the data management device 90. The computer readable storage medium provides a storage space, which stores the operating system of the data management device 90. In addition, one or more instructions suitable for being loaded and executed by the processor 901 are also stored in the storage space, and the instructions can be one or more computer programs (including program codes). It should be noted that the computer readable storage medium herein can be a high-speed RAM memory, or a non-volatile memory such as at least one disk memory; optionally, it can also be at least one computer readable storage medium located away from the aforementioned processor 901.

[0134] In an implementation manner, the data management device 90 can be Figure 4 The computer readable storage medium 904 stores one or more first instructions; the one or more first instructions in the computer readable storage medium are loaded and executed by the processor 901 to implement the corresponding steps in the above-mentioned data management method embodiments; in a specific implementation, the one or more first instructions in the computer readable storage medium 904 are loaded and executed by the processor 901 to implement the following steps:

[0135] In response to the operation request sent by the target node device, verifying the operation permission of the target node device, the target node device being any non-management node device in the blockchain system;

[0136] If the operation permission of the target node device is verified successfully, performing the data operation requested by the operation request on the blockchain according to the operation request;

[0137] Generating a management notification according to the data operation, and broadcasting the management notification in the blockchain system.

[0138] In an implementation manner, the operation request carries the device identifier of the target node device and the operation type of the data operation requested by the target node device; when the one or more first instructions in the computer readable storage medium 904 are loaded and executed by the processor 901 to implement the step of verifying the operation permission of the target node device in response to the operation request sent by the target node device, the following steps are specifically implemented:

[0139] When receiving the operation request sent by the target node device, the authorized device list corresponding to the operation type is obtained, and the authorized device list includes a plurality of authorized device identifiers, and each authorized device identifier corresponds to a node device that is granted the operation permission corresponding to the operation type.

[0140] If the device identifier of the target node device is an authorized device identifier in the authorized device list, it is determined that the target node device has the operation permission.

[0141] In an implementation manner, the authorized device list is configured by the processor 901 through the following method:

[0142] Obtain the credit evaluation levels of each non-administration node device in the blockchain system.

[0143] Obtain the first credit level threshold corresponding to the operation type.

[0144] Add the device identifier of the non-administration node device with the credit evaluation level higher than the first credit level threshold to the authorized device list corresponding to the operation type.

[0145] In an implementation manner, the one or more first instructions in the computer readable storage medium 904 are loaded by the processor 901 and further perform the following steps:

[0146] Detect the change of the credit evaluation level of each non-administration node device in the blockchain system.

[0147] Update the authorized device list according to the change of the credit evaluation level of each non-administration node device in the blockchain system.

[0148] In an implementation manner, the operation request carries the operation type of the data operation requested by the target node device; when the one or more first instructions in the computer readable storage medium 904 are loaded and executed by the processor 901 to verify the operation permission of the target node device in response to the operation request sent by the target node device, the following steps are specifically performed:

[0149] When receiving the operation request sent by the target node device, the authorized device list corresponding to the operation type is obtained.

[0150] The authorized device list is sent to each node device in the blockchain system, so that each node device in the blockchain system verifies the operation permission of the target node device according to the authorized device list, and the authorized device list includes a plurality of authorized device identifiers, and each authorized device identifier corresponds to a node device that is granted the operation permission corresponding to the operation type.

[0151] If the verification success notification returned by more than the first number threshold of node devices is received, it is determined that the operation permission verification of the target node device is successful.

[0152] In an implementation manner, the data operation is a modification operation on the target data; the operation request carries a modification content of the target data; when the one or more first instructions in the computer readable storage medium 904 are loaded and executed by the processor 901 to perform the data operation on the blockchain according to the operation request, the following steps are specifically performed:

[0153] verifying the modification content;

[0154] If the verification passes, updating the target data in the blockchain according to the modification content.

[0155] In an implementation manner, when the one or more first instructions in the computer readable storage medium 904 are loaded and executed by the processor 901 to verify the modification content, the following steps are specifically performed:

[0156] obtaining a credit evaluation level of the target node device;

[0157] If the credit evaluation level of the target node device is higher than the second credit level threshold, it is determined that the modification content passes the verification.

[0158] In an implementation manner, when the one or more first instructions in the computer readable storage medium 904 are loaded and executed by the processor 901 to verify the modification content, the following steps are specifically performed:

[0159] sending the modification content to an associated information system for verification;

[0160] If a verification pass notification fed back by the associated information system is received, it is determined that the modification content passes the verification.

[0161] In an implementation manner, the operation request is obtained by broadcasting in the blockchain system by the target node device; when the one or more first instructions in the computer readable storage medium 904 are loaded and executed by the processor 901 to verify the modification content, the following steps are specifically performed:

[0162] counting verification results of the modification content by each node device in the blockchain system;

[0163] If the number of verification results that pass the verification in the verification results is greater than a second number threshold, it is determined that the modification content passes the verification.

[0164] In an implementation manner, the modification content is an encrypted stamp, the encrypted stamp is obtained by encrypting the modification content in plaintext by an associated information system after the target node device sends the modification content in plaintext to the associated information system and passes the verification by the associated information system; the verification process of the encrypted stamp by any node device in the blockchain system includes:

[0165] checking the legality of the encrypted seal;

[0166] if the legality is passed, the encrypted seal is decrypted using the agreed key;

[0167] if the decryption is successful, a check result is obtained, and the check is passed.

[0168] In an implementation manner, the management notification includes a first management notification and a second management notification, the first management notification carries operation content of a data operation, and the second management notification does not carry the operation content of the data operation. When the one or more first instructions in the computer readable storage medium 904 are loaded and executed by the processor 901, the following steps are specifically performed when the management notification is broadcast in the blockchain system:

[0169] sending the first management notification to a non-management node device in the blockchain system that has operation permission; and

[0170] sending the second management notification to a non-management node device in the blockchain system that does not have operation permission.

[0171] In the embodiments of the application, the management node device can respond to an operation request sent by a target node device and verify operation permission of the target node device. If the management node device successfully verifies the operation permission of the target node device, the management node device can perform a data operation on the blockchain according to the operation request and generate a management notification according to the data operation. The management node device can broadcast the management notification in the blockchain system. The management node device performs a data operation on the blockchain in the blockchain system, which can enable the management node device to uniformly manage data in the blockchain. The management node device broadcasts the management notification generated according to the data operation to each node device in the blockchain system, which can ensure consistency of data in the blockchain.

[0172] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be completed by a computer program instructing related hardware. The program can be stored in a computer readable storage medium. When the program is executed, the processes of the above-mentioned embodiments can be included. The storage medium can be a magnetic disc, an optical disc, a read-only memory (ROM) or a random access memory (RAM).

[0173] The above merely provides a specific implementation of the application, but the protection scope of the application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical range disclosed in the application, which should be covered in the protection scope of the application. Therefore, the protection scope of the application should be subject to the protection scope of the claims.

Claims

1. A blockchain-based data management method, characterized by, The blockchain is located in a blockchain system, the blockchain system comprises a plurality of node devices, the node devices comprise a management node device and a non-management node device, the method is executed by the management node device, and the method comprises: In response to an operation request sent by a target node device, verifying the operation authority of the target node device, the target node device being any non-management node device in the blockchain system; the operation request carries an operation type of a data operation requested by the target node device, the data operation being a modification operation on target data, and the operation request also carries modification content of the target data, the modification content being an encrypted stamp, the encrypted stamp being obtained by performing encryption on plaintext modification content by using an agreed key after the target node device sends the plaintext modification content to an associated information system and the associated information system performs verification on the plaintext modification content and passes the verification; If the operation authority verification of the target node device succeeds, a verification mode related to the type of the target data is obtained, the modification content is verified according to the obtained verification mode, the type of the target data refers to the confidentiality level of the target data, and if the verification passes, the target data in the blockchain is updated according to the modification content; the operation authority verification of the target node device succeeding indicates that the target node device has a modification operation authority; wherein verifying the modification content according to the obtained second verification mode comprises: counting verification results of the encrypted stamp by each node device in the blockchain system, and if the number of verification results that pass the verification in the verification results is greater than a second number threshold, it is determined that the encrypted stamp passes the verification; the verification process of the encrypted stamp by any node device in the blockchain system comprises: checking the legality of the encrypted stamp, if the legality passes, decrypting the encrypted stamp by using the agreed key, and if the decryption succeeds, a verification result that passes the verification is obtained; Generating a management notification according to the data operation, and broadcasting the management notification in the blockchain system.

2. The method of claim 1, wherein, The operation request also carries a device identifier of the target node device; The operation request sent by the target node device is received, an authorized device list corresponding to the operation type is obtained, the authorized device list comprises a plurality of authorized device identifiers, and each authorized device identifier corresponds to a node device that is granted an operation authority corresponding to the operation type; If the device identifier of the target node device is an authorized device identifier in the authorized device list, it is determined that the operation authority verification of the target node device succeeds. The authorized device list is obtained by the following method:

3. The method of claim 2, wherein, Obtaining a credit evaluation level of each non-management node device in the blockchain system; Obtaining a first credit level threshold corresponding to the operation type; ​ Add a device identifier of a non-administration node device with a credit evaluation level higher than the first credit level threshold to an authorized device list corresponding to the operation type.

4. The method of claim 3, wherein, The method further comprises: detecting changes in credit evaluation levels of each non-administration node device in the blockchain system; updating the authorized device list according to the changes in credit evaluation levels of each non-administration node device in the blockchain system.

5. The method of claim 1, wherein, The operation authority verification of the target node device in response to the operation request sent by the target node device comprises: When receiving the operation request sent by the target node device, obtaining the authorized device list corresponding to the operation type; sending the authorized device list to each node device in the blockchain system, so that each node device in the blockchain system verifies the operation authority of the target node device according to the authorized device list, and the authorized device list includes a plurality of authorized device identifiers, each authorized device identifier corresponds to a node device granted with the operation authority corresponding to the operation type; If a verification success notification returned by more than a first number threshold of node devices is received, it is determined that the operation authority verification of the target node device is successful.

6. The method of claim 1, wherein, According to the obtained first verification mode, the modification content is verified, comprising: obtaining the credit evaluation level of the target node device; If the credit evaluation level of the target node device is higher than a second credit level threshold, it is determined that the modification content verification is passed.

7. The method of claim 1, wherein, According to the obtained third verification mode, the modification content is verified, comprising: sending the modification content to the associated information system for verification; If a verification success notification fed back by the associated information system is received, it is determined that the modification content verification is passed.

8. The method of claim 1, wherein, The management notification includes a first management notification and a second management notification, and the first management notification carries the operation content of the data operation; The second management notification does not carry the operation content of the data operation; The broadcasting of the management notification in the blockchain system comprises: sending the first management notification to non-administration node devices with operation authority in the blockchain system; and, sending the second management notification to non-administration node devices without operation authority in the blockchain system. 9.A blockchain-based data management apparatus, characterized by, The blockchain is located in a blockchain system, the blockchain system includes a plurality of node devices, the node devices include administration node devices and non-administration node devices, the data management device is arranged in the administration node device, and the data management device comprises: The verification unit is configured to verify the operation permission of the target node device in response to an operation request sent by the target node device, the target node device being any non-administration node device in the blockchain system; the operation request carrying an operation type of a data operation requested by the target node device, the data operation being a modification operation on target data, and the operation request further carrying modification content of the target data, the modification content being an encrypted stamp, the encrypted stamp being obtained by performing verification on plaintext modification content by an associated information system after the target node device sends the plaintext modification content to the associated information system, and then performing encryption on the plaintext modification content by using a predetermined key after the verification is passed; The execution unit is configured to, if the operation permission of the target node device is verified successfully, acquire a verification mode related to the type of the target data, perform verification on the modification content according to the acquired verification mode, the type of the target data being a confidentiality level of the target data, and update the target data in the blockchain according to the modification content if the verification is passed; the operation permission of the target node device being verified successfully indicating that the target node device has a modification operation permission; wherein performing verification on the modification content according to the acquired second verification mode includes: counting verification results of the encrypted stamp by each node device in the blockchain system, and determining that the verification of the encrypted stamp is passed if the number of verification results passed in the verification results is greater than a second number threshold; and the verification process of the encrypted stamp by any node device in the blockchain system including: checking the legality of the encrypted stamp, and if the legality is passed, decrypting the encrypted stamp by using the predetermined key, and obtaining a verification result passed if the decryption is successful. The broadcast unit is configured to generate a management notification according to the data operation, and broadcast the management notification in the blockchain system. 10.A blockchain-based data management device, characterized by, The blockchain is located in a blockchain system, the blockchain system including a plurality of node devices, the node devices including administration node devices and non-administration node devices, the data management device being the administration node device, and the data management device including: a memory configured to store a computer program; a processor configured to invoke the computer program stored in the memory, and execute the blockchain-based data management method according to any one of claims 1 to 8.

11. A computer readable storage medium, characterized in that, The computer readable storage medium is configured to store a computer program, the computer program being adapted to be invoked by a processor and execute the blockchain-based data management method according to any one of claims 1 to 8.

12. A computer program product, characterised in that, The computer program product includes a computer program stored in a computer readable storage medium, and the computer program is executed to implement the blockchain-based data management method according to any one of claims 1 to 8.

Images