WO2024045552A1 - 一种数据处理方法及相关设备 - Google Patents

一种数据处理方法及相关设备 Download PDF

Info

Publication number
WO2024045552A1
WO2024045552A1 PCT/CN2023/081446 CN2023081446W WO2024045552A1 WO 2024045552 A1 WO2024045552 A1 WO 2024045552A1 CN 2023081446 W CN2023081446 W CN 2023081446W WO 2024045552 A1 WO2024045552 A1 WO 2024045552A1
Authority
WO
WIPO (PCT)
Prior art keywords
transaction
data management
management device
blockchain
target data
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2023/081446
Other languages
English (en)
French (fr)
Inventor
张子怡
曲强
杜明晓
俞岳
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Cloud Computing Technologies Co Ltd
Original Assignee
Huawei Cloud Computing Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Cloud Computing Technologies Co Ltd filed Critical Huawei Cloud Computing Technologies Co Ltd
Priority to EP23858594.7A priority Critical patent/EP4560974A4/en
Publication of WO2024045552A1 publication Critical patent/WO2024045552A1/zh
Priority to US19/067,606 priority patent/US20250202724A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
    • H04L63/0442—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/50—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols using hash chains, e.g. blockchains or hash trees
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/006—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols involving public key infrastructure [PKI] trust models
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/06—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols the encryption apparatus using shift registers or memories for block-wise or stream coding, e.g. DES systems or RC4; Hash functions; Pseudorandom sequence generators
    • H04L9/0618—Block ciphers, i.e. encrypting groups of characters of a plain text message using fixed encryption transformation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/30—Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy
    • H04L9/3066—Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy involving algebraic varieties, e.g. elliptic or hyper-elliptic curves
    • H04L9/3073—Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy involving algebraic varieties, e.g. elliptic or hyper-elliptic curves involving pairings, e.g. identity based encryption [IBE], bilinear mappings or bilinear pairings, e.g. Weil or Tate pairing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3236—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions
    • H04L9/3239—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3247—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving digital signatures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3263—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3263—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements
    • H04L9/3265—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements using certificate chains, trees or paths; Hierarchical trust model
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols

Definitions

  • This application relates to the field of blockchain technology, and in particular to a data processing method, a distributed data management system, a data management device, a computing equipment cluster, a computer-readable storage medium, and a computer program product.
  • Blockchain technology uses block chain data structures to verify and store data, uses distributed node consensus algorithms to generate and update data, uses cryptography to ensure the security of data transmission and access, and uses automated A decentralized architecture and computing paradigm that uses smart contracts composed of script codes to program and manipulate data.
  • Each participant in the blockchain holds the same ledger, and for each participant, their information is publicly visible to other participants. As the application of blockchain becomes more widespread, more organizations can share data on a main chain as participants.
  • This application provides a data processing method that specifies transaction participants in the transaction request and relies on the blockchain to implement private transactions such as privacy writing or privacy query without the need to write additional chain code or update the chain code each time , which realizes the chain code and business code that need to be developed to upload user-shielded private data to the chain, reduces the complexity of operations, and improves the scope of application and ease of use of the blockchain network.
  • This method also does not require the private key to be transferred offline, avoiding the risk of privacy leakage caused by the leakage of the private key.
  • This application also provides a distributed data management system, a data management device, a computing device cluster, a computer-readable storage medium and a computer program product corresponding to the above method.
  • this application provides a data processing method.
  • This method is applied to a distributed data management system, which includes multiple data management devices.
  • the first data management device among the multiple data management devices corresponds to the first blockchain node of the blockchain network.
  • the second data management device among the plurality of data management devices corresponds to the second blockchain node of the blockchain network.
  • the target data management device among the multiple data management devices receives a transaction request from the blockchain client.
  • the transaction request includes the identification of the transaction participant, and then the target data management device enters the transaction request into the blockchain network according to the transaction request.
  • Output (input output, IO) transaction information ciphertext which is obtained by encrypting the transaction information plaintext using a key invisible to another participant other than the transaction participant, and then the target data management device sends the transaction information to the blockchain
  • the client returns the transaction results.
  • This method specifies the transaction participants in the transaction request, and relies on the blockchain to implement private transactions such as privacy writing or privacy query. There is no need to write additional chain code or update the chain code every time, thus enabling users to shield private data from being uploaded to the chain.
  • the chain code and business code that need to be developed reduce the complexity of operations and improve the scope of application and ease of use of the blockchain network.
  • This method also does not require the private key to be transferred offline, avoiding the risk of privacy leakage caused by the leakage of the private key.
  • this method provides a set of adapted distributed data management systems (also called distributed privacy protection engines) for decentralized systems such as blockchain networks to complete the need for decentralized privacy protection capabilities and solve the problem.
  • the centralized system cannot meet the needs of distributed management, and will also cause the risk of managers doing evil in centralized management.
  • the distributed data management system relies on the performance of the blockchain system to efficiently utilize the performance of the current chain by encrypting transaction information.
  • the blockchain nodes of the blockchain network include blockchain ledgers, and the blockchain ledgers are distributed public ledgers.
  • the target data management device can transaction information ciphertext in the blockchain ledger IO according to the transaction request.
  • the operation of the target data management device in the blockchain ledger IO transaction information ciphertext can be recorded in the blockchain for subsequent traceability and data security.
  • the target data management device mounts local storage, and the local storage includes the private ledger of the blockchain network.
  • the private ledger is maintained by the target data management device.
  • the target data management device can transaction information ciphertext in the private ledger IO of the blockchain network according to the transaction request.
  • the ciphertext of IO transaction information in the private ledger does not require consensus among the various blockchain nodes of the blockchain network. It is more efficient and can meet the needs of Transaction requirements.
  • the transaction request is a storage request
  • the transaction request includes the plain text of the transaction information.
  • the target data management device can encrypt the transaction according to the chain key of the transaction initiator in the private transaction group among the transaction participants. Information plaintext, obtain the first transaction information ciphertext, and store the first transaction information ciphertext to the blockchain ledger.
  • the target data management device encrypts the plain text of the transaction information based on the public key or symmetric key of the transaction initiator among the transaction participants, obtains the second cipher text of the transaction information, and stores the second cipher text of the transaction information in the private ledger.
  • This method encrypts the transaction information ciphertext separately and then stores it in the blockchain ledger and private ledger.
  • the private ledger data is lost or tampered with, it can also be restored based on the blockchain ledger, further improving the reliability of data storage. .
  • the transaction request is a query request.
  • the target data management device can also read the ciphertext of the transaction information from the private ledger or the blockchain ledger according to the transaction request. Then the target data management device can read the ciphertext of the transaction information. Decrypt and obtain the clear text of the transaction information.
  • the transaction results may include the above-mentioned transaction information in plain text.
  • the ciphertext of the transaction information is invisible to non-transaction participants.
  • the target data management device obtains the ciphertext of the transaction information and decrypts it, and then carries it in the transaction result and returns it to the blockchain client, realizing privacy. Inquire.
  • the target data management device can also obtain the transaction initiator among the transaction participants in the private transaction group through blockchain network negotiation before the blockchain network IOs the ciphertext of the transaction information according to the transaction request.
  • a chain key that is not visible to another party other than the party involved in the transaction includes the chain key.
  • transaction participants in the private transaction group can use the above-mentioned chain key to implement encrypted sessions, and other participants in the blockchain network (such as the alliance chain) cannot decrypt it, ensuring transaction security.
  • the target data management device also supports updating the chain key. Specifically, when the key update condition is triggered, the target data management device may update the chain key through a double ratchet algorithm. In this way, you can prevent Prevent replay attacks and further improve security.
  • the key update condition includes that the number of transactions based on the chain key reaches a preset number.
  • the target data management device may also receive a public-private key pair issued by the certificate issuing node for the transaction initiator among the transaction participants before the blockchain network IO transaction information ciphertext according to the transaction request. Keys that are not visible to parties other than those involved in the transaction include the public key in a public-private key pair.
  • Transaction participants in a private transaction group can disclose their public keys within the group.
  • the public key is not visible to other participants in the blockchain network. Participants in the blockchain network other than the transaction participants Ciphertext encrypted using the above public key cannot be decrypted, thus enabling private transactions and ensuring privacy security.
  • the target data management device mounts local storage, and the local storage includes the private ledger of the blockchain network.
  • the target data management device can obtain the first meta-information of the data stored in the private ledger from the private ledger, and obtain the second meta-information of the data stored in the private ledger from the blockchain ledger of the blockchain network. Then the target data management device performs a fault check based on the first meta-information and the second meta-information, and obtains the fault check result.
  • the target data management device scans the meta-information in the local private ledger and the blockchain ledger and compares the meta-information to determine whether the local storage is faulty or whether the data in the locally stored private ledger has been deleted or tampering, thereby realizing efficient fault inspection, quickly locating the fault point, and meeting business needs.
  • the target data management device when the fault check result indicates that the data stored in the private ledger has been tampered with, deleted, or there is a storage failure mounted by the target data management device, the target data management device can also use the blockchain ledger to Perform crash recovery.
  • the target data management device can perform fault recovery based on the blockchain ledger storage data to maintain data consistency when the data stored in the private ledger is tampered with, deleted, or a storage failure mounted on the target data management device occurs.
  • the target data management device can provide a storage interface or a query interface.
  • the blockchain client can call the storage interface to generate a storage request, or call the query interface to generate a query request.
  • This method provides a unified interface for private data storage (upload, on-chain) or query (download), eliminating the need to separately develop chain code and business code for private data on-chain and query, reducing operational complexity and improving the efficiency of the blockchain system. Scope of application and ease of use.
  • the transaction request is a query request
  • the target data management device reads the transaction information ciphertext from the private ledger according to the transaction request, decrypts the transaction information ciphertext, and obtains the transaction information plaintext.
  • the hash value of the plain text of the transaction information is compared with the hash value of the plain text of the transaction information stored in the blockchain network. If they are consistent, the plain text of the transaction information is carried in the transaction result.
  • the target data management device supports verification of the private data queried from the private ledger and the data on the chain, thereby ensuring that the private data is not tampered with.
  • the target data management device when a transaction participant exits the private transaction group, the target data management device does not need to update the chain key.
  • the target data management device can reuse the chain key in the privacy transaction group formed by the remaining transaction participants. Conduct private transactions within the group. On the one hand, it ensures the security of private transactions, and on the other hand, there is no need to update the chain key, which reduces the operational complexity.
  • this application provides a distributed data management system.
  • the distributed data management system includes multiple Data management device, the first data management device among the plurality of data management devices corresponds to the first blockchain node of the blockchain network, and the second data management device among the plurality of data management devices corresponds to the blockchain network the second blockchain node;
  • the target data management device among the plurality of data management devices is used to receive a transaction request from the blockchain client, where the transaction request includes the identification of the transaction participant;
  • the target data management device is also configured to input and output IO transaction information ciphertext in the blockchain network according to the transaction request, and the transaction information ciphertext adopts another participating party other than the transaction participant.
  • the plain text of the transaction information is encrypted with a key invisible to the party, and the transaction result is returned to the blockchain client.
  • the blockchain nodes of the blockchain network include blockchain ledgers
  • the target data management device is specifically used for:
  • the transaction information ciphertext is entered in the blockchain ledger IO.
  • the target data management device mounts local storage, and the local storage includes the private ledger of the blockchain network;
  • the target data management device is specifically used for:
  • the transaction information ciphertext is in the private ledger IO.
  • the transaction request is a storage request, and the transaction request includes plain text of transaction information
  • the target data management device is specifically used for:
  • the plain text of the transaction information is encrypted, the first transaction information cipher text is obtained, and the first transaction information cipher text is stored in the blockchain ledger.
  • the plain text of the transaction information is encrypted according to the public key or symmetric key of the transaction initiator among the transaction participants, a second cipher text of the transaction information is obtained, and the second cipher text of the transaction information is stored in the private ledger.
  • the transaction request is a query request
  • the target data management device is specifically used for:
  • the method also includes:
  • the target data management device decrypts the ciphertext of the transaction information and obtains the plaintext of the transaction information
  • the transaction result includes the plain text of the transaction information.
  • the target data management device is also used to:
  • the chain secret of the transaction initiator in the privacy transaction group among the transaction participants is obtained through negotiation on the blockchain network. key;
  • Keys that are not visible to another party other than the party to the transaction include the chain key.
  • the target data management device is also used to:
  • the chain key is updated through a double ratchet algorithm.
  • the key update conditions include:
  • the number of transactions based on the chain key reaches a preset number.
  • the target data management device is also used to:
  • the blockchain network before the blockchain network inputs and outputs the IO transaction information ciphertext, receive the public and private key pair issued by the certificate issuing node for the transaction initiator among the transaction participants;
  • Keys that are not visible to another party other than the transaction party include the public key in the public-private key pair.
  • the target data management device mounts local storage, and the local storage includes the private ledger of the blockchain network;
  • the target data management device is also used for:
  • the target data management device is also used to:
  • fault recovery is performed based on the blockchain ledger.
  • the present application provides a data management device.
  • the data management device corresponds to the blockchain node of the blockchain network, and the data management device includes:
  • a communication module used to receive a transaction request from a blockchain client, where the transaction request includes the identification of the transaction participant;
  • a management module configured to input and output IO transaction information ciphertext in the blockchain network according to the transaction request.
  • the transaction information ciphertext adopts a ciphertext that is invisible to another participant other than the transaction participant.
  • the key is obtained by encrypting the plain text of the transaction information;
  • the communication module is also used to return transaction results to the blockchain client.
  • the blockchain nodes of the blockchain network include blockchain ledgers
  • the management module is specifically used for:
  • the transaction information ciphertext is entered in the blockchain ledger IO.
  • the data management device mounts local storage, and the local storage includes the private ledger of the blockchain network;
  • the management module is specifically used for:
  • the transaction information ciphertext is in the private ledger IO.
  • the transaction request is a storage request, and the transaction request includes plain text of transaction information
  • the management module is specifically used for:
  • the plain text of the transaction information is encrypted, the first transaction information cipher text is obtained, and the first transaction information cipher text is stored in the blockchain ledger.
  • the plain text of the transaction information is encrypted according to the public key or symmetric key of the transaction initiator among the transaction participants, a second cipher text of the transaction information is obtained, and the second cipher text of the transaction information is stored in the private ledger.
  • the transaction request is a query request
  • the management module is specifically used for:
  • the management module is also used to:
  • the transaction result includes the plain text of the transaction information.
  • the management module is also used to:
  • the chain secret of the transaction initiator in the privacy transaction group among the transaction participants is obtained through negotiation on the blockchain network. key;
  • Keys that are not visible to another party other than the party to the transaction include the chain key.
  • the management module is also used to:
  • the chain key is updated through a double ratchet algorithm.
  • the key update conditions include:
  • the number of transactions based on the chain key reaches a preset number.
  • the communication module is also used to:
  • Keys that are not visible to another party other than the transaction party include the public key in the public-private key pair.
  • the data management device mounts local storage, and the local storage includes the private ledger of the blockchain network;
  • the communication module is also used for:
  • the device also includes:
  • a fault checking module configured to perform fault checking according to the first meta-information and the second meta-information, and obtain a fault checking result.
  • the device further includes:
  • a fault recovery module configured to perform fault recovery based on the blockchain ledger when the fault check result indicates that the data stored in the private ledger has been tampered with, deleted, or a storage failure mounted on the data management device.
  • this application provides a computing device cluster.
  • the cluster of computing devices includes at least one computing device including at least one processor and at least one memory.
  • the at least one processor and the at least one memory communicate with each other.
  • the at least one processor is configured to execute instructions stored in the at least one memory, so that the computing device or a cluster of computing devices executes the data processing method as described in the first aspect or any implementation of the first aspect.
  • the present application provides a computer-readable storage medium in which instructions are stored, and the instructions instruct a computing device or a cluster of computing devices to execute the first aspect or any one of the first aspects. Implement the data processing method described in the method.
  • the present application provides a computer program product containing instructions that, when run on a computing device or a cluster of computing devices, causes the computing device or a cluster of computing devices to execute the first aspect or any one of the first aspects. Implement the data processing method described in the method.
  • Figure 1 is a schematic architectural diagram of a distributed data management system provided by an embodiment of the present application.
  • Figure 2 is a schematic architectural diagram of a distributed data management system provided by an embodiment of the present application.
  • Figure 3 is a schematic architectural diagram of a distributed data management system in a multi-scenario alliance provided by an embodiment of the present application
  • Figure 4 is a flow chart of a data processing method provided by an embodiment of the present application.
  • Figure 5 is a schematic diagram of a key chain provided by an embodiment of the present application.
  • Figure 6 is a schematic diagram of an application scenario of a data processing method provided by an embodiment of the present application.
  • Figure 7 is a schematic flow chart of the initialization of a distributed data management system provided by an embodiment of the present application.
  • Figure 8 is a schematic flow chart of group creation provided by an embodiment of the present application.
  • Figure 9 is a schematic flowchart of a privacy transaction initiation provided by an embodiment of the present application.
  • Figure 10 is a schematic flowchart of a private transaction synchronization provided by an embodiment of the present application.
  • Figure 11 is a schematic flow chart of a private transaction query provided by an embodiment of the present application.
  • Figure 12 is a schematic structural diagram of a distributed data management system provided by an embodiment of the present application.
  • Figure 13 is a schematic structural diagram of a computing device provided by an embodiment of the present application.
  • Figure 14 is a schematic structural diagram of a computing device cluster provided by an embodiment of the present application.
  • Figure 15 is a schematic structural diagram of a computing device cluster provided by an embodiment of the present application.
  • Figure 16 is a schematic structural diagram of a computing device cluster provided by an embodiment of the present application.
  • first and second in the embodiments of this application are only used for descriptive purposes and cannot be understood as indicating or implying relative importance or implicitly indicating the number of indicated technical features. Therefore, features defined as “first” and “second” may explicitly or implicitly include one or more of these features.
  • Blockchain network which can also be referred to as blockchain for short, refers to a peer-to-peer (P2P) network built based on blockchain technology.
  • a blockchain network includes multiple blockchain nodes, each of which is a peer node.
  • multiple blockchain nodes jointly maintain a continuously growing blockchain ledger constructed of ordered data blocks.
  • Each blockchain node stores a copy of the above-mentioned blockchain ledger and maintains consistency between copies. Therefore, the blockchain ledger is a public ledger of the blockchain network.
  • E2EE end-to-end encryption
  • End-to-end encryption is a communication system where only the users participating in the communication can read the information. It prevents potential eavesdroppers, including but not limited to telecommunications providers, Internet service providers and providers of the communication system, from obtaining the clear text of communications between the two parties. Such systems are designed to prevent potential surveillance or tampering attempts.
  • the blockchain network includes Participant A, Participant B, Participant C, and Participant D.
  • Participant A, Participant B, and Participant C conduct transactions.
  • Participant A conducts transactions with Participant B and Participant C.
  • Party C shares data
  • Party A can encrypt the data end-to-end to share the data. Share it with Participant B and Participant C, and keep it confidential to Participant D.
  • the industry usually uses zero-knowledge proof to protect the privacy of transaction information.
  • a bill scenario is used as an example.
  • the blockchain client can generate zero-knowledge proof information, and then initiate on-chain verification, and the blockchain node will perform the validity verification of the zero-knowledge proof information. If the verification is passed, the blockchain node conducts private transactions with the pre-established privacy ticket pool.
  • the privacy note pool is used to store privacy notes to be traded.
  • the above solution requires changing the smart contract and upgrading the chain code when the transaction participants change. For example, when participant A and participant B conduct private transactions, the chain code needs to be upgraded to specify participant A and participant B to conduct private transactions. This greatly reduces the performance of the blockchain network and affects transaction efficiency, thereby affecting transaction efficiency. Affects the availability of the blockchain network.
  • the distributed management system includes multiple data management devices. Each data management device is part of a distributed data management system. Among them, the distributed data management system is essentially a distributed storage engine, which is mainly used to protect the privacy of transaction information and other data. Therefore, the distributed data management system can also be called a distributed privacy protection engine and a distributed data management system.
  • the data management device in is part of the above-mentioned distributed privacy protection engine.
  • the first data management device among the plurality of data management devices corresponds to the first blockchain node of the blockchain network
  • the second data management device among the plurality of data management devices corresponds to the second blockchain node of the blockchain network. .
  • the target data management device among the multiple data management devices receives a transaction request from the blockchain client.
  • the transaction request includes the identification of the transaction participant, and then the target data management device enters the transaction request into the blockchain network according to the transaction request.
  • Output (input output, IO) transaction information ciphertext which is obtained by encrypting the transaction information plaintext using a key invisible to another participant other than the transaction participant, and then the target data management device sends the transaction information to the blockchain
  • the client returns the transaction results.
  • This method specifies the transaction participants in the transaction request, and relies on the blockchain to implement private transactions such as privacy writing or privacy query. There is no need to write additional chain code or update the chain code every time, thus enabling users to shield private data from being uploaded to the chain.
  • the chain code and business code that need to be developed reduce the complexity of operations and improve the scope of application and ease of use of the blockchain network.
  • This method also does not require the private key to be transferred offline, avoiding the risk of privacy leakage caused by the leakage of the private key.
  • This method provides a set of adapted distributed data management systems (also called distributed privacy protection engines) for decentralized systems such as blockchain networks to complete the need for decentralized privacy protection capabilities and solve the problem of centralization.
  • the system cannot meet the needs of distributed management, and it will also cause the risk of managers doing evil in centralized management.
  • the distributed data management system relies on the performance of the blockchain system to efficiently utilize the performance of the current chain by encrypting transaction information.
  • the distributed data management system 100 includes multiple data management devices 10, and each of the multiple data management devices 10 corresponds to a blockchain network 200.
  • a blockchain node of 20 For example, the first data management device corresponds to the first blockchain node, and the second data management device corresponds to the second blockchain node.
  • each data management device 10 can also mount the local storage 30 .
  • the data management device 10 in the embodiment of the present application supports the management and adaptation of different storage media.
  • the data management device 10 can mount different storage media. Same storage media, including but not limited to mechanical hard disk drive (HDD) or solid state drive (SDD).
  • the blockchain node 20 includes the blockchain ledger of the blockchain network 200 (belonging to the public ledger), and the local storage 30 includes the private ledger of the blockchain network 200 .
  • the data management device 10 can also interface with the blockchain client 40 .
  • Blockchain participants such as cloud tenants and off-cloud users can initiate transactions through the blockchain client 40 .
  • blockchain participants can share private data with designated participants through the blockchain client, or query private data.
  • the target data management device among the plurality of data management devices 10 can receive a transaction request from the blockchain client 40.
  • the transaction request includes the identifier (identifier, ID) of the transaction participant.
  • the transaction participant includes When participant A (for example, organization A) and participant B (for example, organization B), the transaction request may include the identification of organization A and the identification of organization B.
  • the target data management device transacts the information ciphertext in the blockchain network 20010 according to the transaction request.
  • the transaction request when the transaction request is a storage request, it can be to store the transaction information ciphertext in the blockchain ledger and private ledger of the blockchain network 200; when the transaction request is a query request, it can be to query the private ledger of the blockchain network 200.
  • Transaction information ciphertext when the transaction information ciphertext is not found in the private ledger, the transaction information ciphertext can also be queried from the blockchain ledger.
  • the ciphertext of the transaction information may be obtained by encrypting the plaintext of the transaction information using a key invisible to another participant other than the transaction participant (such as organization C).
  • the ciphertext of transaction information stored in the public ledger and the ciphertext of transaction information stored in the private ledger can be encrypted using different keys.
  • the transaction information ciphertext stored in the public ledger which may also be called the first transaction information ciphertext, may be encrypted based on the chain key of the transaction initiator in the private transaction group negotiated by the blockchain network 200 .
  • the transaction information ciphertext stored in the private ledger also called the second transaction information ciphertext, can be encrypted using the public key pair of the public-private key pair issued by the certificate authority (CA) node for the transaction initiator among the transaction participants. get.
  • CA certificate authority
  • the target data management device returns the transaction result to the blockchain client 40.
  • the transaction results can be different.
  • the transaction request is a storage request (also called a data upload request or a data upload request)
  • the transaction result can be a transaction success notification, which is used to indicate the success of the storage.
  • the transaction request is a query request (which may also be called a data download request)
  • the transaction result may include the plain text of the queried transaction information.
  • the plain text of the transaction information can be obtained by decrypting the cipher text of the transaction information by the target data management device.
  • the client side may also include a blockchain software development toolkit (SDK).
  • SDK blockchain software development toolkit
  • the blockchain SDK is used to receive transaction requests, such as storage requests for private data, query requests for querying private data, and the load is processed on the client side to obtain private data, group and identity verification calculations, and submit privacy
  • the data is sent to the distributed data management system 100 side for further interaction with the blockchain node 200 .
  • the data management device 10 of the distributed data management system 100 may include an end-to-end encryption component, thereby encrypting the plain text of the transaction information.
  • the end-to-end encryption component includes the optimization of the signal algorithm and the rectification of blockchain integration. It completes the entire process of key negotiation (such as chain key negotiation) based on the blockchain network 200, replacing the centralized system or centralized node distribution. Key, use its capabilities to create highly secure group transaction capabilities.
  • the data management device 10 may also include a group manager.
  • the group manager is used to calculate relevant group information for each organization (also referred to as a participant or member) corresponding to the data management device 10 .
  • the group manager checks the privacy Easy group, create private transaction group, delete private transaction group.
  • the group manager can also trigger the generation and saving of keys.
  • the group manager can trigger the generation and saving of one or more of chain keys, temporary public-private key pairs, and symmetric keys.
  • the data management device 10 may also include private ledger management.
  • Private ledger management can support local storage of private data of different participants and build the ability to quickly query private data. At the same time, this module can also support the ability to reconstruct local data from the blockchain ledger when data is lost.
  • the data management device 10 may also include computational checks. Computational verification is used to provide support for identity verification, group comparison, comparison of locally stored information and on-chain stored information, etc.
  • End-to-end encryption components private ledger management, group manager, calculation verification and other modules can be combined to build a highly available distributed data management system 100 based on the blockchain network 200.
  • the data management device 10 shown in Figure 1 may be a software device, and the software device may be deployed on other computing devices independent of the blockchain node.
  • the data management device shown in FIG. 1 may also be a hardware device.
  • the hardware device may be a computing device with a privacy protection function that is independent of the blockchain node 20 .
  • each data management device 10 of the distributed data management system 100 can also be deployed on the blockchain node 20, that is, the block chain node 20.
  • the chain node 20 includes a blockchain kernel and a data management device 10 .
  • the data management device 10 may be a middleware or component, and the middleware or component may be integrated into the blockchain node 20 .
  • the distributed data management system 100 of the embodiment of this application is aimed at the blockchain.
  • user data is open to all participants on the chain, but some users want to define privacy by specifying transaction participants.
  • Transaction or private information a system designed to integrate blockchain and end-to-end encryption.
  • the system provides distributed privacy protection components (such as the above-mentioned data management device 10) to support key management and privacy data storage for different users, thereby achieving organizational-level user privacy protection, and is also based on embedded group management capabilities. Improve the convenience of uploading and querying user privacy protection data.
  • the distributed data management system 100 can be applied to finance, energy, government affairs, aviation, agriculture, people's livelihood, logistics and other industries.
  • the distributed data management system 100 can be applied to scenarios such as commodity procurement and sales, non-fungible token (NFT) transactions, and other scenarios.
  • NFT non-fungible token
  • the distributed data management system 100 can be used as a distributed storage bottom layer to support the metaverse or web3.0.
  • public cloud refers to the cloud services provided by cloud service providers to users through the public Internet (Internet). Users can access the cloud through the Internet and enjoy various services, including but not limited to computing, storage, network, etc.
  • Private cloud is a cloud computing method built by the enterprise itself to provide services within the enterprise. Private cloud is an enterprise Built for stand-alone use, it can be deployed in an enterprise's data center or uniformly deployed in a cloud service provider's computer room.
  • Hybrid cloud is a cloud computing usage that combines private cloud and public cloud.
  • Edge nodes are relative to cloud computing data centers and refer to network nodes with fewer intermediate links between them and the final access users. The edge node can be a computer room or a physical device. Compared with directly accessing the origin site, users have better response capabilities and connection speeds when accessing the edge node.
  • the distributed data management system 100 can also be deployed in different environments in a distributed manner.
  • multiple data management devices 10 of the distributed data management system 100 can be deployed in public clouds, hybrid clouds, and edge nodes respectively, thereby providing multi-scenario alliances.
  • Data management services For example, trading goods on an e-commerce platform involves the following five organizations: farmers, shippers, wholesalers, distributors, and retailers.
  • the data management devices 10 corresponding to these organizations can be deployed in a distributed manner in a hybrid environment formed by public clouds, private clouds and edge nodes.
  • farmers transfer goods to distributors abroad when they sell goods abroad, shippers move goods between parties, wholesalers purchase goods from distributors, retailers purchase goods from shippers and wholesalers, and distribution Traders may wish to conduct private transactions with farmers and shippers so that wholesalers and retailers keep the terms of the transactions confidential and thereby avoid exposing the markups charged by distributors.
  • the distributor may also want to set up a separate privacy deal with the wholesaler because it charges the wholesaler a lower price than the retailer.
  • wholesalers may also wish to establish private transactions with retailers and shippers.
  • the embodiment of the present application Based on the distributed data management system 100 provided by the embodiment of the present application, the embodiment of the present application also provides a corresponding data processing method.
  • the method includes:
  • S402 The target data management device receives the transaction request sent by the blockchain client.
  • the transaction request is a storage request
  • S404 to S410 are executed
  • the transaction request is a query request
  • S412 to S418 are executed.
  • the target data management device may be any data management device 10 in the distributed data management system 100, for example, it may be the above-mentioned first data management device or the second data management device.
  • a transaction request can be a storage request.
  • a storage request is used to store data, for example, to the blockchain network 200 .
  • a transaction request can also be a query request. Used in query requests to query data, such as obtaining data from the blockchain network 200.
  • the transaction request can include the identification of the transaction participants to indicate that the data is shared among the transaction participants and kept confidential from non-transaction participants (such as another participant in the blockchain network other than the transaction participant). .
  • the storage request is used to request that the transaction information plaintext and other data be end-to-end encrypted before being uploaded to the chain.
  • the transaction request is a query request, it is used to request that the transaction information ciphertext be decrypted to obtain the transaction information plaintext. Return later.
  • the participants can be organizations in the blockchain network.
  • the identification of the transaction participants can be one or more of the organization name and organization code.
  • the transaction request can include the organization names of Organization A and Organization B, thereby specifying the privacy transaction between Organization A and Organization B.
  • the user When you want to initiate a privacy transaction between Organization B and Organization C, the transaction request can include the organization names of Organization B and Organization C, thereby specifying the privacy transaction between Organization B and Organization C.
  • the transaction request when the transaction request is a storage request, the transaction request can also carry the plain text of the transaction information.
  • the transaction letter The information plaintext may specifically be data that needs to be shared.
  • the target data management device encrypts the plain text of the transaction information based on the chain key of the transaction initiator in the private transaction group among the transaction participants, and obtains the first cipher text of the transaction information.
  • the participant can be in one or more private transaction groups, and the target data management device can determine the private transaction group corresponding to this transaction based on the identification of the transaction participant in the transaction request. For example, when the transaction request includes the organization names of organization A and organization B, the target data management device may determine the private transaction group to be the group formed by organization A and organization B, which is recorded as group (organization A, organization B). The same organization can have different chain keys in different private transaction groups.
  • the target data management device can obtain the chain key of the transaction initiator in the private transaction group among the transaction participants based on the private transaction group for this transaction. Key, such as the chain key of organization A in group (organization A, organization B), and then use the chain key to encrypt, thereby obtaining the first transaction information ciphertext.
  • KDF chain refers to the KDF key of the key derivation function (KDF) chain.
  • KDF chain is the abbreviation of KDF key chain.
  • KDF is defined as a cryptographic function that inputs a secret and random KDF key (KDF key) and some other input data, and returns the output data. Under the premise that the key is unknown, the output data is indistinguishable from random numbers (that is, KDF meets the requirements of pseudo-random function (PRF) in cryptography). If the key is not secret and random, the KDF output should still serve as a secure cryptographic hash of the KDF key and input data.
  • a KDF chain includes the output keys of multiple KDFs.
  • FIG. 5 shows a KDF chain that processes three input keys (KDF keys) and generates three output keys.
  • the target data management device can encrypt the transaction information using a double ratchet algorithm based on the chain key, thereby obtaining the first transaction information ciphertext, and then carrying it in the message to send it to the data management device 10 corresponding to the designated transaction participant. .
  • the KDF keys saved by both parties will be used for three chains: root chain, sending chain and receiving chain (one party's The sending chain corresponds to the receiving chain of the other party and vice versa).
  • Organization A and Organization B exchange messages (the messages can carry the ciphertext of the first transaction information), they also exchange new Diffie-Hellman public keys, and the key output by Diffie-Hellman will serve as the root chain. input of.
  • the key output by the root chain will be used as the KDF key for the sending chain and receiving chain. This is called the Diffie-Hellman ratchet.
  • the output key will be used to encrypt and decrypt messages. This is called symmetric-key ratchet.
  • Each message sent or received can be encrypted using a unique message key.
  • the message key is the output key of the sending KDF chain and the receiving KDF chain. Since the KDF input of the sending KDF chain and the receiving KDF chain is a constant, these two chains are not recoverable after being compromised.
  • the sending and receiving chains ensure that each message is encrypted with a unique key that can be deleted after encryption or decryption.
  • the process of calculating the next chain key and message key from a given chain key is called a ratchet step of the symmetric-key ratchet.
  • the double ratchet algorithm combines the symmetric key ratchet with DH A ratchet is composed together and uses the latter to update the chain key based on the Diffie-Hellman output.
  • the communicating parties each generate a DH key pair (Diffie-Hellman public key and private key) as the current ratchet key pair. Every message sent from either party will carry a message header containing the sender's current Ratchet public key.
  • the local end When receiving the new ratchet public key sent from the remote end, the local end will perform a DH ratchet step (DH ratchet step) to generate a new ratchet key pair to replace the current key pair of the local end.
  • the communicating parties alternately update the ratchet key pair, forming a "ping-pong" behavior pattern.
  • An eavesdropper who intercepts only one of the parties may obtain the value of the current ratchet private key, but this ratchet private key will eventually be replaced by the undisclosed ratchet private key.
  • the Diffie-Hellman computation between the ratchet key pair will define a new DH output unknown to the attacker.
  • the target data management device can also use the private key in the public-private key pair generated by the CA node to sign, so that the opposite end can perform signature verification and thereby determine the identity of the local end.
  • the CA node can derive a temporary public and private key pair, and the target data management device can use the temporary private key and combine it with the signature algorithm to sign the first transaction information ciphertext in the message.
  • the target data management device can construct a key value (KV) based on the group and the group message, and then upload the group message to the link in the form of a key value.
  • KV key value
  • the target data management device stores the first transaction information ciphertext in the blockchain ledger.
  • the target data management device can send the first transaction information ciphertext to the corresponding blockchain node 20 , and the blockchain node 20 stores the first transaction information ciphertext in based on the smart contract of the blockchain network 200 .
  • Blockchain ledger the blockchain nodes 20 can perform consensus based on the consensus algorithm defined by the smart contract, and after reaching a consensus, each blockchain node 20 stores the first transaction information ciphertext in the area maintained by each by adding blocks. Blockchain ledger.
  • the target data management device encrypts the plain text of the transaction information based on the public key or symmetric key of the transaction initiator among the transaction participants, and obtains the second cipher text of the transaction information.
  • the target data management device can use the public key or symmetric key of the transaction initiator to encrypt the plain text of the transaction information through an encryption algorithm, thereby obtaining the second cipher text of the transaction information.
  • the target data management device uses a public key, it can encrypt by an asymmetric encryption algorithm; when the target data management device uses a symmetric key, it can encrypt by a symmetric encryption algorithm.
  • the data management device 10 corresponding to other transaction participants in the private transaction group can use the public key or symmetric key of the transaction participant to encrypt the plain text of the transaction information through an encryption algorithm, thereby obtaining the second transaction Information cipher text.
  • the target data management device stores the second transaction information ciphertext in the private ledger.
  • the target data management device stores the second transaction information ciphertext calculated by the target data management device to the private account book in the local storage mounted on the target data management device.
  • the data management device 10 corresponding to other transaction participants in the private transaction group can store the second transaction information ciphertext calculated by the data management device 10 to the private ledger in the local storage mounted on the data management device 10 .
  • the second transaction information ciphertext stored in different private ledgers can be encrypted using the keys (public keys or symmetric keys) of the corresponding transaction participants. Therefore, the second transaction information ciphertext stored in different private ledgers can be different. .
  • the above-mentioned S404 to S410 are an implementation manner in which the target data management device stores the transaction information ciphertext in the blockchain network 200 according to the storage request. In other possible implementation manners of the embodiment of the present application, it can also be implemented Store transaction information ciphertext in other ways.
  • the target data management device may not mount local storage.
  • the local target data management device may not execute the above-mentioned S408 and S410.
  • S412 The target data management device queries the second transaction information ciphertext from the private ledger. If the query is successful, S414 can be executed. If the query fails, S416 and S418 can be executed.
  • the target data management device may first query the second transaction information ciphertext from the locally stored private ledger to improve query efficiency and query performance. Considering that the second transaction information cipher text in the locally stored private ledger may be tampered with or deleted, or the locally stored storage medium fails, the query may fail. Based on this, the target data management device may perform S414 for decryption when the query is successful. , when the query fails, execute S416 and S418 to obtain and decrypt the first transaction information ciphertext.
  • the target data management device decrypts the second transaction information ciphertext and obtains the transaction information plaintext.
  • the target data management device when the target data management device uses the public key to encrypt the plain text of the transaction information to obtain the second cipher text of the transaction information, it can use the private key to decrypt the second cipher text of the transaction information to restore the plain text of the transaction information.
  • the target data management device uses the symmetric key to encrypt the plain text of the transaction information to obtain the second cipher text of the transaction information, the target data management device can use the symmetric key to decrypt the second cipher text of the transaction information to restore the plain text of the transaction information.
  • S416 The target data management device queries the first transaction information ciphertext from the blockchain account book.
  • the target data management device may query the first transaction information ciphertext from the blockchain account book based on the smart contract of the blockchain network 200 . Due to the non-tampering characteristics of the blockchain, the target data management device can query the first transaction information ciphertext from the blockchain ledger maintained by each blockchain node 20 .
  • the target data management device decrypts the first transaction information ciphertext and obtains the transaction information plaintext.
  • the first transaction information ciphertext is usually based on the chain key and encrypted using the double ratchet algorithm. Based on this, the target data management device can decrypt the first transaction information ciphertext through a double ratchet algorithm in combination with the chain key, thereby obtaining the transaction information plaintext.
  • the target data management device can directly query the first transaction information ciphertext from the blockchain ledger according to the query request, and then decrypt the first transaction information ciphertext to obtain the transaction information plaintext.
  • the above-mentioned S404 to S418 are an implementation method for the target data management device in the embodiment of the present application to obtain the ciphertext of the transaction information in the blockchain network 200IO according to the transaction request.
  • the data processing method in the embodiment of the present application can also be executed by executing other steps to achieve.
  • S420 The target data management device returns the transaction result to the blockchain client.
  • the transaction results are different for different transaction requests.
  • the transaction result can be a transaction success notification, which is used to indicate the success of the storage.
  • the transaction result may also include the plain text of the queried transaction information.
  • the plain text of the transaction information can be obtained by decrypting the cipher text of the transaction information by the target data management device.
  • the target data management device can also obtain the first meta-information of the data stored in the private ledger from the private ledger, and obtain the first metadata of the data stored in the private ledger from the blockchain ledger of the blockchain network.
  • Secondary information of data stored in private ledgers refers to the meta-information of the data stored in the private ledger itself, such as one or more of the creator, creation time, size, and hash value of the data.
  • the second meta-information refers to the data stored on the chain.
  • the meta information of the data in the private ledger such as one or more of the creator, creation time, size, and hash value of the data.
  • the second meta information can be that when the data is stored in the private ledger, its meta information is stored on the chain. .
  • the target data management device may perform a fault check based on the first meta-information and the second meta-information, and obtain a fault check result. Specifically, the target data management device can compare the first meta-information and the second meta-information. If the first meta-information and the second meta-information do not match, it indicates that a failure has occurred, for example, the data stored in the private account book has been tampered with, deleted, or the data has been deleted. In the event of a storage failure mounted by the target data management device, the target management device may write the fault check result into the blockchain network 200 .
  • the target data management device can also perform fault recovery based on the blockchain ledger. Specifically, the target data management device can decrypt the first transaction information ciphertext in the blockchain ledger to obtain the transaction information plaintext, then encrypt the transaction information plaintext to obtain the second transaction information ciphertext, and convert the second transaction information ciphertext into Stored in a private ledger for failure recovery.
  • the embodiment of the present application provides a data processing method.
  • this method for blockchains in consortium chain scenarios or open consortium chain scenarios, user data is open to all participants on the chain, but some participants wish to define private transactions or private information by specifying different participants.
  • This method introduces a distributed data management system 100 to support the management of keys and the storage of private data for different participants to achieve organizational-level privacy protection.
  • the embedded group management capabilities it improves the efficiency of uploading and querying user privacy data. Convenience.
  • the blockchain network includes blockchain node A corresponding to organization A, blockchain node B corresponding to organization B, blockchain node C and organization D corresponding to organization C.
  • the corresponding blockchain node D is bound to data management device A
  • blockchain node B is bound to data management device B
  • blockchain node C is bound to data management device C
  • blockchain node D is not bound to data.
  • Management device therefore, blockchain node A, blockchain node B, and blockchain node C have private transaction capabilities
  • blockchain node D is an ordinary blockchain node and does not have private transaction capabilities.
  • the data management device bound to the blockchain node can create a private transaction group.
  • data management device A can create the following privacy transaction groups: group (organization A, organization B), group (organization A, organization C), group (organization B, organization C) and group (organization A, organization B, organization C). It should be noted that as the organization in the blockchain network expands or shrinks, the data management device can also dynamically update the private transaction group.
  • the data management device can also create the following private transaction group: group (organization A, organization D), group (organization A, organization B, organization D), group (organization A, organization D) C, organization D), group (organization B, organization C, organization D), group (organization C, organization D) and group (organization A, organization B, organization C), organization D.
  • Data management device A, data management device B, and data management device C can negotiate the chain key based on the blockchain network and synchronize the chain key in the group.
  • organization A initiates a transaction, for example, organization A sends a transaction request for storing data to data management device A through the blockchain client, and the transaction request includes the identification of organization A and the identification of organization B
  • data management device A can The chain key of organization A in group (organization A, organization B) encrypts the plain text of the transaction information, obtains the first cipher text of the transaction information, and then stores the first cipher text of the transaction information on the chain.
  • data management device A can also use the public key or symmetric key of organization A to encrypt the plain text of the transaction information, obtain the second cipher text of the transaction information, and then store the second cipher text of the transaction information locally, specifically in a private ledger. .
  • This stage may include the following steps:
  • Step 1 The target data management device of the distributed data management system periodically accesses the blockchain node to obtain the group list, group status, and on-chain event notifications.
  • Step 2 The target data management device periodically accesses the private ledger in local storage to obtain the group list and group status.
  • Step 3 The target data management device compares the group list and group status obtained from the blockchain node with the group list and group status obtained from the local ledger. If they are consistent, return to step 1 and step 2. If they are inconsistent, go to step 4.
  • Step 4 The target data management device identifies the reason for the inconsistency. If the reason is that the group has not been created or the creation of other data management devices has timed out, the on-chain status is changed.
  • Step 5 The target data management device triggers group creation.
  • Step 6 The target data management device performs on-chain event notification.
  • the target data management device when it triggers group creation, it can generate an on-chain event notification, which is used to notify other data management devices that the current target data management device is responsible for creating the target group.
  • the target data management device can execute based on the on-chain event notification. The action of creating a target group.
  • the data management system of the distributed data management system can interact with the blockchain network at startup and access the blockchain nodes to obtain the group list, group status and current organization-related events stored in the current chain. and other information, while loading the group list and group status in the locally stored private ledger, and calculating the group differences through comparison. If the chain and local groups are consistent, the initialization is completed. If they are inconsistent, identify the cause of the current inconsistency to see if it is other reasons. The data management device times out when creating a group. Based on different reasons, the creation task is preempted and updated to the chain, and the group creation process is triggered at the same time. Then return to step 1 and step 2 to continue checking the group.
  • this stage may include the following steps:
  • Step 1 After startup, each data management device of the distributed data management system queries the organizational information on the chain and synchronizes it. Group information.
  • Step 2 Data management device A creates a group list based on the organization information, compares the local and on-chain group lists, creates the missing group group (organization A, organization B, organization C), and updates the on-chain status, creation time, creation By.
  • Step 3 Data management device B and data management device C compare and check the local group and the group on the chain, determine that the group (organization A, organization B, organization C) creation task is executed by data management device A, and start monitoring the task. , and prepare the key for it.
  • Step 4 The CA node issues the temporary public and private key pairs used by data management device A, data management device B, and data management device C in group (organization A, organization B, organization C) respectively.
  • Data management device A, data management device B , the data management device C generates chain keys in groups (organization A, organization B, organization C) respectively.
  • Step 5 Data management device A uploads the temporary public key of data management device A to the chain, updates the transaction on the chain and notifies organization B.
  • Organization C uploads its temporary public key.
  • Step 6 Data management devices B and C monitor the transactions on the chain, upload their respective temporary public keys, and update the transaction status.
  • Step 7 Data management device A, data management device B and data management device C respectively use the public keys of other designated transaction participants to encrypt their respective chain keys, sign with the private keys, and then upload the ciphertext of the chain keys to the chain. .
  • Step 8 Data management device A, data management device B and data management device C respectively use the public keys of other designated transaction participants to verify the signature, and after passing the verification, use their respective private keys to decrypt to obtain the other designated transaction participants. The chain key is then encrypted and saved.
  • Figure 8 is an example of creating a group (organization A, organization B, organization C) and synchronizing the chain key.
  • group can be created in a similar manner and the chain key can be synchronized within the group.
  • Step 1 The blockchain client sends a transaction request to the target data management device.
  • the transaction request includes the identifiers of organization A, organization B, and organization C, for example, the organization names of organization A, organization B, and organization C.
  • Step 2 The target data management device verifies the signature carried in the transaction request and whether the organization specified in the transaction request exists. If the verification passes, step 3 is performed. If not, the transaction request is rejected.
  • the transaction initiated from the blockchain client includes the scope of the specified group and the content of the transaction.
  • the data management device first checks its signature. If it is an illegal request, it will return directly. If it is a legal request, it will verify whether the organization of the private transaction is If it exists, it will be returned if it does not exist.
  • Step 3 The target data management device queries the chain for the group status of the group to which the organization specified in the transaction request belongs. If the group status is normal, perform steps 4 and 5 to synchronize private transactions. If the group status is that the group does not exist, the group is in the process of key change, or the group is being created, group creation or processing is triggered.
  • the transaction request is returned to the blockchain client to wait for the group creation to end and initiate the group creation process.
  • Step 4 The target data management device encrypts the plain text of the transaction information and uploads it to the chain.
  • Step 5 The target data management device encrypts and stores the transaction information in plain text in the private ledger.
  • Step 6 The target data management device counts the number of private transactions. When the number of private transactions reaches the preset number, perform step 7.
  • the preset number can be set based on experience value, for example, the preset number can be set to 10.
  • Step 7 The target data management device triggers key update.
  • Figure 10 illustrates an example of privacy transactions between Organization A and Organization B, which specifically includes the following steps:
  • Step 1 Organization A sends a transaction request to data management device A through the blockchain client.
  • Step 2 Data management device A can use the double ratchet algorithm to generate a message key based on the chain key of organization A in the group, use the message key to encrypt the plain text of the transaction information, sign it with the private key, and then upload it to the chain with the group message .
  • Step 3 Data management device B monitors the new message sent by data management device A in the group, uses the chain key of organization A in the group to generate a message key, and uses the message key to decrypt the ciphertext of the transaction information to obtain the plaintext of the transaction information. .
  • Step 4 Data management device C monitors the ciphertext generated on the chain, but cannot decrypt it.
  • Step 5 When the number of private transactions between data management device A and data management device B reaches the preset number, key update is triggered to generate a new chain key and public-private key pair.
  • Step 6 Data management device A uploads the new temporary public key used in the group to the chain, and updates the on-chain transaction to notify other organizations in the group to upload the new public key.
  • Step 7 Data management device B monitors on-chain transactions, uploads its new temporary public key used in the group, and updates on-chain transactions.
  • Step 8 Data management device A obtains the new temporary public key used by organization B in the group, uses the temporary public key to encrypt the chain key, uses the private key to sign, and then uploads the ciphertext to the chain.
  • Step 9 Data management device B obtains the new temporary public key used by organization A in the group, uses the temporary public key to encrypt the chain key, uses the private key to sign, and then uploads the ciphertext to the chain.
  • Step 10 Data management device A and data management device B use the peer's public key to verify the signature. After passing the verification, they use their own private keys to decrypt to obtain the peer's chain key in the group.
  • the data management device can transmit private data based on the blockchain and regularly update the group secret key through the end-to-end encrypted double ratchet algorithm to achieve forward security capabilities for group transactions.
  • the data management device may also update keys for private transactions based on the number of key update rotations specified in the configuration. For example, the number of key update rotations can be specified as a minimum of once to achieve the effect of one-time padding. If the number of key update rotations is reached, group members will generate temporary public and private keys and new chain keys, and then based on the negotiation in the previous process The process is synchronized to other members of the group.
  • Step 1 The blockchain client sends a transaction request to the target data management device.
  • Step 2 The target data management device verifies the signature in the transaction request. If the verification passes, step 3 is performed. If the verification fails, the transaction request is rejected.
  • Step 3 The target data management device queries the ciphertext of transaction information from the locally stored private ledger.
  • the data management device supports private transaction query capabilities through the blockchain client. Since the data management device can host all temporary keys used for transaction encryption and are invisible to the user, transactions can be queried based on the data management device. After the user initiates a private transaction query, the data management device can verify whether the signature of the transaction request is a legal request. If it is not legal, it will be returned directly. If it is legal, the result will be queried from the locally stored private ledger and returned to the customer. At the same time, in order to ensure that the transaction has not been tampered with, the target data management device can compare the hash on the chain and the hash of the private ledger. If it does not exist in the private ledger, the ciphertext of the transaction information can be obtained from the blockchain ledger on the chain.
  • the embodiment of the present application also provides a distributed data management system 100 as described above.
  • the distributed data management system 100 is introduced below with reference to the accompanying drawings.
  • the distributed data management system 100 includes multiple data management devices 10 .
  • the first data management device among the plurality of data management devices 10 corresponds to the first blockchain node of the blockchain network
  • the second data management device among the plurality of data management devices 10 corresponds to the second blockchain of the blockchain network. node.
  • the target data management device among the plurality of data management devices 10 is configured to receive a transaction request from the blockchain client, where the transaction request includes the identification of the transaction participant;
  • the target data management device is also configured to input and output IO transaction information ciphertext in the blockchain network according to the transaction request, and the transaction information ciphertext adopts another participating party other than the transaction participant.
  • the plain text of the transaction information is encrypted with a key invisible to the party, and the transaction result is returned to the blockchain client.
  • the blockchain nodes of the blockchain network include blockchain ledgers
  • the target data management device is specifically used for:
  • the transaction information ciphertext is entered in the blockchain ledger IO.
  • the target data management device mounts local storage, and the local storage includes the private ledger of the blockchain network;
  • the target data management device is specifically used for:
  • the transaction information ciphertext is in the private ledger IO.
  • the transaction request is a storage request, and the transaction request includes plain text of transaction information
  • the target data management device is specifically used for:
  • the plain text of the transaction information is encrypted, the first transaction information cipher text is obtained, and the first transaction information cipher text is stored in the blockchain ledger.
  • the plain text of the transaction information is encrypted according to the public key or symmetric key of the transaction initiator among the transaction participants, a second cipher text of the transaction information is obtained, and the second cipher text of the transaction information is stored in the private ledger.
  • the transaction request is a query request
  • the target data management device is specifically used for:
  • the method also includes:
  • the target data management device decrypts the ciphertext of the transaction information and obtains the plaintext of the transaction information
  • the transaction result includes the plain text of the transaction information.
  • the target data management device is also used to:
  • the chain secret of the transaction initiator in the privacy transaction group among the transaction participants is obtained through negotiation on the blockchain network. key;
  • Keys that are not visible to another party other than the party to the transaction include the chain key.
  • the target data management device is also used to:
  • the chain key is updated through a double ratchet algorithm.
  • the key update conditions include:
  • the number of transactions based on the chain key reaches a preset number.
  • the target data management device is also used to:
  • the blockchain network before the blockchain network inputs and outputs the IO transaction information ciphertext, receive the public and private key pair issued by the certificate issuing node for the transaction initiator among the transaction participants;
  • Keys that are not visible to another party other than the transaction party include the public key in the public-private key pair.
  • the target data management device mounts local storage, and the local storage includes the private ledger of the blockchain network;
  • the target data management device is also used for:
  • the target data management device is also used to:
  • fault recovery is performed based on the blockchain ledger.
  • the target data management device may be any one of the plurality of data management devices 10 , for example, it may be the above-mentioned first data management device or the second data management device.
  • the structure of the data management device is introduced below. As shown in Figure 12, the data management device 10 includes:
  • the communication module 102 is used to receive a transaction request from the blockchain client, where the transaction request includes the identification of the transaction participant;
  • the management module 104 is configured to input and output IO transaction information ciphertext in the blockchain network according to the transaction request.
  • the transaction information ciphertext is invisible to another participant other than the transaction participant.
  • the key is obtained by encrypting the plain text of the transaction information;
  • the communication module 102 is also used to return transaction results to the blockchain client.
  • management module 104 is used to implement the group manager, end-to-end encryption component, private ledger management or calculation verification functions shown in Figure 1 or Figure 2 or Figure 3 .
  • the above-mentioned communication module 102 and management module 104 can be implemented by hardware modules or software modules.
  • the communication module 102 and the management module 104 may be application programs or application program modules running on a computing device or a cluster of computing devices.
  • the communication module 102 can be implemented by a transceiver module such as a network interface card or a transceiver.
  • the management module 104 may be a device implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD).
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • the above-mentioned PLD can be implemented by a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), a general array logic (GAL), or any combination thereof.
  • CPLD complex programmable logical device
  • FPGA field-programmable gate array
  • GAL general array logic
  • the blockchain nodes of the blockchain network include blockchain ledgers
  • the management module 104 is specifically used to:
  • the transaction information ciphertext is entered in the blockchain ledger IO.
  • the data management device mounts local storage, and the local storage includes the private ledger of the blockchain network;
  • the management module 104 is specifically used to:
  • the transaction information ciphertext is in the private ledger IO.
  • the transaction request is a storage request, and the transaction request includes plain text of transaction information
  • the management module 104 is specifically used to:
  • the plain text of the transaction information is encrypted, the first transaction information cipher text is obtained, and the first transaction information cipher text is stored in the blockchain ledger.
  • the plain text of the transaction information is encrypted according to the public key or symmetric key of the transaction initiator among the transaction participants, a second cipher text of the transaction information is obtained, and the second cipher text of the transaction information is stored in the private ledger.
  • the transaction request is a query request
  • the management module 104 is specifically used to:
  • the management module 104 is also used to:
  • the transaction result includes the plain text of the transaction information.
  • the management module 104 is also used to:
  • the chain secret of the transaction initiator in the privacy transaction group among the transaction participants is obtained through negotiation on the blockchain network. key;
  • Keys that are not visible to another party other than the party to the transaction include the chain key.
  • the management module 104 is also used to:
  • the chain key is updated through a double ratchet algorithm.
  • the key update conditions include:
  • the number of transactions based on the chain key reaches a preset number.
  • the communication module 102 is also used to:
  • Keys that are not visible to another party other than the transaction party include the public key in the public-private key pair.
  • the data management device 10 mounts local storage, and the local storage includes the private ledger of the blockchain network;
  • the communication module 102 is also used to:
  • the device 10 also includes:
  • the fault checking module 106 is used to perform fault checking according to the first meta-information and the second meta-information, and obtain Fault check results.
  • the above-mentioned fault checking module 106 can be implemented by a hardware module or a software module.
  • the fault checking module 106 may be an application or application module running on a computing device or cluster of computing devices.
  • the fault checking module 106 may be a device implemented using an application specific integrated circuit (ASIC), or a programmable logic device (PLD), or the like.
  • ASIC application specific integrated circuit
  • PLD programmable logic device
  • the above-mentioned PLD can be implemented by a complex program logic device CPLD, a field programmable gate array FPGA, a general array logic GAL, or any combination thereof.
  • the device 10 further includes:
  • the fault recovery module 108 is configured to perform fault recovery based on the blockchain ledger when the fault check result indicates that the data stored in the private ledger has been tampered with, deleted, or a storage failure mounted on the data management device.
  • the above-mentioned fault recovery module 108 can be implemented by a hardware module or a software module.
  • the fault recovery module 108 may be an application or application module running on a computing device or cluster of computing devices.
  • the fault recovery module 108 may be a device implemented using an application specific integrated circuit (ASIC), or a programmable logic device (PLD), or the like.
  • ASIC application specific integrated circuit
  • PLD programmable logic device
  • the above-mentioned PLD can be implemented by a complex program logic device CPLD, a field programmable gate array FPGA, a general array logic GAL, or any combination thereof.
  • computing device 1300 includes: bus 1302, processor 1304, memory 1306, and communication interface 1308.
  • the processor 1304, the memory 1306 and the communication interface 1308 communicate through a bus 1302.
  • the computing device 1300 may be a computing device in a central cloud, such as a central server, or a computing device in an edge cloud, such as an edge server.
  • the computing device 1300 may also be a lightweight device, such as a smartphone, a smart wearable device, and other terminal devices. It should be understood that this application does not limit the number of processors and memories in the computing device 1300.
  • the bus 1302 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc.
  • PCI peripheral component interconnect
  • EISA extended industry standard architecture
  • the bus can be divided into address bus, data bus, control bus, etc. For ease of presentation, only one line is used in Figure 13, but it does not mean that there is only one bus or one type of bus.
  • Bus 1302 may include a path that carries information between various components of computing device 1300 (eg, memory 1306, processor 1304, communications interface 1308).
  • the processor 1304 may include a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP) or a digital signal processor (DSP). any one or more of them.
  • CPU central processing unit
  • GPU graphics processing unit
  • MP microprocessor
  • DSP digital signal processor
  • Memory 1306 may include volatile memory, such as random access memory (RAM).
  • the processor 1304 may also include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD) or solid state drive (SSD). drive, SSD).
  • ROM read-only memory
  • HDD hard disk drive
  • SSD solid state drive
  • the memory 1306 stores executable program code, and the processor 1304 executes the executable program code to implement the foregoing data processing method.
  • the memory 1306 stores instructions for the distributed data management system 100 or the data management device 10 to execute the data processing method.
  • the communication interface 1308 uses transceiver modules such as, but not limited to, network interface cards and transceivers to implement communication between the computing device 1300 and other devices or communication networks.
  • An embodiment of the present application also provides a computing device cluster.
  • the computing device cluster includes at least one computing device 1300 .
  • the computing device 1300 may be a server, such as a central server or an edge server.
  • computing device 1300 may also be a terminal device.
  • the computing device cluster includes at least one computing device 1300. Instructions for performing the data processing method of the same distributed data management system 100 may be stored in the memory 1306 of one or more computing devices 1300 in the cluster of computing devices.
  • one or more computing devices 1300 in the computing device cluster may also be used to execute part of the instructions of the distributed data management system 100 for executing the data processing method.
  • a combination of one or more computing devices 1300 may collectively execute instructions of the distributed data management system 100 for performing the data processing method.
  • the memory 1306 in different computing devices 1300 in the computing device cluster can store different instructions for executing part of the functions of the distributed data management system 100 .
  • Figure 15 shows a possible implementation.
  • two computing devices 1300A and 1300B are connected through a communication interface 1308.
  • the memory in the computing device 1300A stores instructions for executing the functions of the communication module 102 and the management module 104 .
  • Instructions for the functions of the fault detection module 106 and the fault recovery module 108 are stored on memory in the computing device 1300B.
  • the memories 1306 of the computing devices 1300A and 1300B jointly store instructions for the distributed data management system 100 to perform the data processing method.
  • connection method between the computing device clusters shown in Figure 15 can be considered that the data processing method provided by this application needs to scan the distributed ledger maintained by the blockchain node in the blockchain network when performing fault check. When the fault is restored, , need to read the fault information stored in the blockchain node. Therefore, it is considered that the functions implemented by the communication module 102 and the management module 104 are executed by the computing device 1300A, and the functions implemented by the fault checking module 106 and the fault recovery module 108 are executed by the computing device 1300B.
  • computing device 1300A shown in FIG. 15 may also be performed by multiple computing devices 1300.
  • the functions of computing device 1300B may also be performed by multiple computing devices 1300.
  • one or more computing devices in a cluster of computing devices may be connected through a network.
  • the network may be a wide area network or a local area network, etc.
  • Figure 16 shows a possible implementation. As shown in Figure 16, two computing devices 1300C and 1300D are connected through a network. Specifically, the connection to the network is made through a communication interface in each computing device.
  • instructions for executing the functions of the communication module 102 and the management module 104 are stored in the memory 1306 of the computing device 1300C.
  • instructions for performing the functions of the fault checking module 106 and the fault recovery module 108 are stored in the memory 1306 in the computing device 1300D.
  • connection method between the computing device clusters shown in Figure 16 can be considering that the data processing method provided by this application needs to scan the distributed ledger maintained by the blockchain node in the blockchain network, or read the storage in the blockchain node. Therefore, it is considered that the functions implemented by the communication module 102 and the management module 104 are executed by the computing device 1300C, and the functions implemented by the fault checking module 106 and the fault recovery module 108 are executed by the computing device 1300D. It should be understood that the functions of computing device 1300C shown in FIG. 16 may also be performed by multiple computing devices 1300. Likewise, the functions of computing device 1300D may also be performed by multiple computing devices 1300.
  • An embodiment of the present application also provides a computer-readable storage medium.
  • the computer-readable storage medium may be any available medium that a computing device can store or a data storage device such as a data center that contains one or more available media. Prepare.
  • the available media may be magnetic media (eg, floppy disk, hard disk, tape), optical media (eg, DVD), or semiconductor media (eg, solid state drive), etc.
  • the computer-readable storage medium includes instructions that instruct the computing device to perform the above-mentioned data processing method applied to the distributed data management system 100.
  • An embodiment of the present application also provides a computer program product containing instructions.
  • the computer program product may be a software or program product containing instructions capable of running on a computing device or cluster of computing devices or stored in any available medium.
  • the computer program product is run on at least one computing device (computing device or computing device cluster), at least one computing device is caused to execute the above data processing method.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computing Systems (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Physics & Mathematics (AREA)
  • Mathematical Physics (AREA)
  • Pure & Applied Mathematics (AREA)
  • Mathematical Optimization (AREA)
  • Mathematical Analysis (AREA)
  • General Physics & Mathematics (AREA)
  • Algebra (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

本申请提供了一种数据处理方法，应用于分布式数据管理系统，该系统包括多个数据管理装置，每个数据管理装置对应区块链网络的一个区块链节点，该方法包括：多个数据管理装置中的目标数据管理装置接收来自区块链客户端的交易请求，交易请求中包括交易参与方的标识，目标数据管理装置根据交易请求，在区块链网络输入输出IO基于对交易参与方之外的另一参与方不可见的密钥对交易信息明文加密所得的交易信息密文，然后向区块链客户端返回交易结果。该方法通过在交易请求中指定交易参与方，并依托区块链实现隐私写入或隐私查询等隐私交易，实现了对用户屏蔽隐私数据上链需要开发的链代码、业务代码，提升了区块链网络的适用范围和易用性。

Description

一种数据处理方法及相关设备
本申请要求于2022年08月31日提交中国国家知识产权局、申请号为202211063836.7、发明名称为“一种数据处理方法及相关设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及区块链技术领域，尤其涉及一种数据处理方法、分布式数据管理系统、数据管理装置、计算设备集群、计算机可读存储介质、计算机程序产品。
背景技术
区块链(block chain)技术是利用块链式数据结构来验证和存储数据，利用分布式节点共识算法来生成和更新数据，利用密码学的方式保证数据传输和访问的安全，以及利用由自动化脚本代码组成的智能合约来编程和操作数据的一种去中心化架构与计算范式。
区块链的每个参与方都持有相同的账本，对于每个参与方而言，他们的信息对其他参与方都是公开可见的。随着区块链的应用越加广泛，更多的组织可以作为参与方在一条主链上共享数据。
然而，不同参与方之间可以存在一些独特的交易诉求，具体是交易参与方之间的交易信息对链上的非交易参与方不公开。如果在交易参与方之间额外构建一条区块链需要耗费大量的资源，如何在开放的区块链网络中实现交易参与方之间交易的隐私保护成为研究热点。
发明内容
本申请提供了一种数据处理方法，该方法通过在交易请求中指定交易参与方，并依托区块链实现隐私写入或隐私查询等隐私交易，无需额外编写链代码，或者每次更新链代码，实现了对用户屏蔽隐私数据上链需要开发的链代码、业务代码，降低了操作复杂性，提升了区块链网络的适用范围和易用性。该方法也不需要线下传递私钥，避免了私钥泄露导致的隐私泄露风险。本申请还提供了上述方法对应的分布式数据管理系统、数据管理装置、计算设备集群、计算机可读存储介质以及计算机程序产品。
第一方面，本申请提供一种数据处理方法。该方法应用于分布式数据管理系统，所述分布式数据管理系统包括多个数据管理装置，所述多个数据管理装置中的第一数据管理装置对应区块链网络的第一区块链节点，所述多个数据管理装置中的第二数据管理装置对应区块链网络的第二区块链节点。
具体地，多个数据管理装置中的目标数据管理装置接收来自区块链客户端的交易请求，该交易请求中包括交易参与方的标识，然后目标数据管理装置根据交易请求，在区块链网络输入输出(input output，IO)交易信息密文，该交易信息密文采用对交易参与方之外的另一参与方不可见的密钥对交易信息明文加密得到，接着目标数据管理装置向区块链客户端返回交易结果。
该方法通过在交易请求中指定交易参与方，并依托区块链实现隐私写入或隐私查询等隐私交易，无需额外编写链代码，或者每次更新链代码，实现了对用户屏蔽隐私数据上链需要开发的链代码、业务代码，降低了操作复杂性，提升了区块链网络的适用范围和易用性。该方法也不需要线下传递私钥，避免了私钥泄露导致的隐私泄露风险。
并且，该方法为区块链网络这种去中心化系统提供一套适配的分布式数据管理系统(也称作分布式隐私保护引擎)完成去中心化的实现隐私保护能力的需求，解决了中心化的系统无法满足分布式管理需求，又会造成集中管理中出现的管理者作恶风险的问题。此外，分布式数据管理系统依托于区块链体系的性能以加密交易信息方式高效利用当前链的性能。
在一些可能的实现方式中，区块链网络的区块链节点中包括区块链账本，区块链账本为分布式的公有账本。目标数据管理装置可以根据交易请求，在区块链账本IO交易信息密文。
如此，目标数据管理装置在区块链账本IO交易信息密文的操作可以记录在区块链，以便后续追溯，保障数据安全。
在一些可能的实现方式中，目标数据管理装置挂载本地存储，本地存储中包括区块链网络的私有账本。私有账本由目标数据管理装置维护。具体地，目标数据管理装置可以根据交易请求，在区块链网络的私有账本IO交易信息密文。
相较于在区块链网络的区块链账本IO交易信息密文，在私有账本IO交易信息密文，无需区块链网络的各个区块链节点达成共识，具有更高的效率，能够满足交易需求。
在一些可能的实现方式中，交易请求为存储请求，交易请求包括交易信息明文，相应地，目标数据管理装置可以根据交易参与方中交易发起方在隐私交易群组中的链密钥，加密交易信息明文，获得第一交易信息密文，存储该第一交易信息密文至区块链账本。目标数据管理装置根据交易参与方中交易发起方的公钥或对称密钥加密交易信息明文，获得第二交易信息密文，存储第二交易信息密文至私有账本。
该方法通过将交易信息密文分别加密，然后存储至区块链账本、私有账本，当私有账本数据丢失或被篡改时，还可以基于区块链账本进行恢复，进一步提升了数据存储的可靠性。
在一些可能的实现方式中，交易请求为查询请求，目标数据管理装置还可以根据交易请求，从私有账本或区块链账本读取交易信息密文，然后目标数据管理装置可以对交易信息密文进行解密，获得所述交易信息明文。交易结果可以包括上述交易信息明文。
在该方法中，该交易信息密文对非交易参与方不可见，目标数据管理装置获取到上述交易信息密文后进行解密，然后携带在交易结果中返回至区块链客户端，实现了隐私查询。
在一些可能的实现方式中，目标数据管理装置还可以根据交易请求，在区块链网络IO交易信息密文之前，通过区块链网络协商得到交易参与方中交易发起方在隐私交易群组中的链密钥，对交易参与方之外的另一参与方不可见的密钥包括所述链密钥。
如此，隐私交易群组中的交易参与方可以利用上述链密钥实现加密会话，区块链网络(如联盟链)中除交易参与方之外的其他参与方无法解密，保障了交易安全。
在一些可能的实现方式中，目标数据管理装置还支持更新链密钥。具体地，当密钥更新条件被触发时，目标数据管理装置可以通过双棘轮算法更新所述链密钥。如此，可以防 止重放攻击，进一步提升安全性。
在一些可能的实现方式中，密钥更新条件包括基于所述链密钥的交易次数达到预设数量。通过设置链密钥对应的最大交易次数，可以避免攻击者获取到链密钥持续使用该链密钥进行加密会话，缩小攻击范围。
在一些可能的实现方式中，目标数据管理装置根据交易请求，在区块链网络IO交易信息密文之前，还可以接收证书签发节点为交易参与方中交易发起方签发的公私钥对。对交易参与方之外的另一参与方不可见的密钥包括公私钥对中的公钥。
隐私交易群组中的交易参与方可以在群组内公开各自的公钥，该公钥对区块链网络的另一参与方不可见，区块链网络中除交易参与方之外的参与方无法解密采用上述公钥进行加密的密文，由此可以实现隐私交易，保障隐私安全。
在一些可能的实现方式中，目标数据管理装置挂载本地存储，本地存储中包括所述区块链网络的私有账本。目标数据管理装置可以从私有账本获取私有账本中存储数据的第一元信息，以及从区块链网络的区块链账本中获取私有账本中存储数据的第二元信息。然后目标数据管理装置根据第一元信息和第二元信息进行故障检查，获得故障检查结果。
该方法中，目标数据管理装置通过扫描本地的私有账本以及区块链账本中的元信息，并对元信息进行比对，从而确定本地存储是否故障或者本地存储的私有账本中数据是否被删除或篡改，由此实现了高效的故障检查，能够快速定位故障点，满足了业务需求。
在一些可能的实现方式中，当所述故障检查结果表征所述私有账本中存储数据被篡改、删除或者所述目标数据管理装置挂载的存储故障，目标数据管理装置还可以根据区块链账本进行故障恢复。
该方法中，目标数据管理装置可以在私有账本中存储数据被篡改、删除或者目标数据管理装置挂载的存储故障时，基于区块链账本存储数据进行故障恢复，保持数据一致性。
在一些可能的实现方式中，目标数据管理装置可以提供存储接口或查询接口，相应地，区块链客户端可以调用存储接口生成存储请求，或者是调用查询接口生成查询请求。该方法通过提供隐私数据存储(上传、上链)或查询(下载)的统一接口，无需针对隐私数据上链、查询单独开发链代码、业务代码，降低了操作复杂度，提升区块链系统的适用范围和易用性。
在一些可能的实现方式中，交易请求为查询请求，目标数据管理装置根据交易请求，从私有账本读取交易信息密文，对交易信息密文进行解密，获得交易信息明文。将交易信息明文的哈希值与区块链网络存储的该笔交易的交易信息明文的哈希值比较，若一致，则将该交易信息明文携带在交易结果中。
在该方法中，目标数据管理装置支持将从私有账本中查询的隐私数据和链上数据进行校验，从而保障隐私数据无篡改。
在一些可能的实现方式中，隐私交易群组存在交易参与方退出时，目标数据管理装置无需更新链密钥，目标数据管理装置可以复用链密钥，在剩余交易参与方形成的隐私交易群组内进行隐私交易。一方面保障隐私交易安全，另一方面无需更新链密钥，降低了操作复杂度。
第二方面，本申请提供一种分布式数据管理系统。所述分布式数据管理系统包括多个 数据管理装置，所述多个数据管理装置中的第一数据管理装置对应区块链网络的第一区块链节点，所述多个数据管理装置中的第二数据管理装置对应区块链网络的第二区块链节点；
所述多个数据管理装置中的目标数据管理装置，用于接收来自区块链客户端的交易请求，所述交易请求中包括交易参与方的标识；
所述目标数据管理装置，还用于根据所述交易请求，在所述区块链网络输入输出IO交易信息密文，所述交易信息密文采用对所述交易参与方之外的另一参与方不可见的密钥对交易信息明文加密得到，向所述区块链客户端返回交易结果。
在一些可能的实现方式中，所述区块链网络的区块链节点中包括区块链账本；
所述目标数据管理装置具体用于：
根据所述交易请求，在所述区块链账本IO交易信息密文。
在一些可能的实现方式中，所述目标数据管理装置挂载本地存储，所述本地存储中包括所述区块链网络的私有账本；
所述目标数据管理装置具体用于：
根据所述交易请求，在所述私有账本IO交易信息密文。
在一些可能的实现方式中，所述交易请求为存储请求，所述交易请求包括交易信息明文；
所述目标数据管理装置具体用于：
根据所述交易参与方中交易发起方在隐私交易群组中的链密钥，加密交易信息明文，获得第一交易信息密文，存储所述第一交易信息密文至所述区块链账本；
根据所述交易参与方中交易发起方的公钥或对称密钥加密交易信息明文，获得第二交易信息密文，存储所述第二交易信息密文至所述私有账本。
在一些可能的实现方式中，所述交易请求为查询请求；
所述目标数据管理装置具体用于：
根据所述交易请求，从所述私有账本或所述区块链账本读取所述交易信息密文；
所述方法还包括：
所述目标数据管理装置对所述交易信息密文进行解密，获得所述交易信息明文；
所述交易结果包括所述交易信息明文。
在一些可能的实现方式中，所述目标数据管理装置还用于：
在根据所述交易请求，在所述区块链网络输入输出IO交易信息密文之前，通过所述区块链网络协商得到所述交易参与方中交易发起方在隐私交易群组中的链密钥；
对所述交易参与方之外的另一参与方不可见的密钥包括所述链密钥。
在一些可能的实现方式中，所述目标数据管理装置还用于：
当密钥更新条件被触发时，通过双棘轮算法更新所述链密钥。
在一些可能的实现方式中，所述密钥更新条件包括：
基于所述链密钥的交易次数达到预设数量。
在一些可能的实现方式中，所述目标数据管理装置还用于：
在根据所述交易请求，在所述区块链网络输入输出IO交易信息密文之前，接收证书签发节点为所述交易参与方中交易发起方签发的公私钥对；
对所述交易参与方之外的另一参与方不可见的密钥包括所述公私钥对中的公钥。
在一些可能的实现方式中，所述目标数据管理装置挂载本地存储，所述本地存储中包括所述区块链网络的私有账本；
所述目标数据管理装置还用于：
从所述私有账本获取所述私有账本中存储数据的第一元信息，以及从所述区块链网络的区块链账本中获取所述私有账本中存储数据的第二元信息；
根据所述第一元信息和所述第二元信息进行故障检查，获得故障检查结果。
在一些可能的实现方式中，所述目标数据管理装置还用于：
当所述故障检查结果表征所述私有账本中存储数据被篡改、删除或者所述目标数据管理装置挂载的存储故障，根据所述区块链账本进行故障恢复。
第三方面，本申请提供一种数据管理装置。所述数据管理装置对应区块链网络的区块链节点，所述数据管理装置包括：
通信模块，用于接收来自区块链客户端的交易请求，所述交易请求中包括交易参与方的标识；
管理模块，用于根据所述交易请求，在所述区块链网络输入输出IO交易信息密文，所述交易信息密文采用对所述交易参与方之外的另一参与方不可见的密钥对交易信息明文加密得到；
所述通信模块，还用于向所述区块链客户端返回交易结果。
在一些可能的实现方式中，所述区块链网络的区块链节点中包括区块链账本；
所述管理模块具体用于：
根据所述交易请求，在所述区块链账本IO交易信息密文。
在一些可能的实现方式中，所述数据管理装置挂载本地存储，所述本地存储中包括所述区块链网络的私有账本；
所述管理模块具体用于：
根据所述交易请求，在所述私有账本IO交易信息密文。
在一些可能的实现方式中，所述交易请求为存储请求，所述交易请求包括交易信息明文；
所述管理模块具体用于：
根据所述交易参与方中交易发起方在隐私交易群组中的链密钥，加密交易信息明文，获得第一交易信息密文，存储所述第一交易信息密文至所述区块链账本；
根据所述交易参与方中交易发起方的公钥或对称密钥加密交易信息明文，获得第二交易信息密文，存储所述第二交易信息密文至所述私有账本。
在一些可能的实现方式中，所述交易请求为查询请求；
所述管理模块具体用于：
根据所述交易请求，从所述私有账本或所述区块链账本读取所述交易信息密文；
所述管理模块还用于：
对所述交易信息密文进行解密，获得所述交易信息明文；
所述交易结果包括所述交易信息明文。
在一些可能的实现方式中，所述管理模块还用于：
在根据所述交易请求，在所述区块链网络输入输出IO交易信息密文之前，通过所述区块链网络协商得到所述交易参与方中交易发起方在隐私交易群组中的链密钥；
对所述交易参与方之外的另一参与方不可见的密钥包括所述链密钥。
在一些可能的实现方式中，所述管理模块还用于：
当密钥更新条件被触发时，通过双棘轮算法更新所述链密钥。
在一些可能的实现方式中，所述密钥更新条件包括：
基于所述链密钥的交易次数达到预设数量。
在一些可能的实现方式中，所述通信模块还用于：
接收证书签发节点为所述交易参与方中交易发起方签发的公私钥对；
对所述交易参与方之外的另一参与方不可见的密钥包括所述公私钥对中的公钥。
在一些可能的实现方式中，所述数据管理装置挂载本地存储，所述本地存储中包括所述区块链网络的私有账本；
所述通信模块还用于：
从所述私有账本获取所述私有账本中存储数据的第一元信息，以及从所述区块链网络的区块链账本中获取所述私有账本中存储数据的第二元信息；
所述装置还包括：
故障检查模块，用于根据所述第一元信息和所述第二元信息进行故障检查，获得故障检查结果。
在一些可能的实现方式中，所述装置还包括：
故障恢复模块，用于当所述故障检查结果表征所述私有账本中存储数据被篡改、删除或者所述数据管理装置挂载的存储故障，根据所述区块链账本进行故障恢复。
第四方面，本申请提供一种计算设备集群。所述计算设备集群包括至少一台计算设备，所述至少一台计算设备包括至少一个处理器和至少一个存储器。所述至少一个处理器、所述至少一个存储器进行相互的通信。所述至少一个处理器用于执行所述至少一个存储器中存储的指令，以使得计算设备或计算设备集群执行如第一方面或第一方面的任一种实现方式所述的数据处理方法。
第五方面，本申请提供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，所述指令指示计算设备或计算设备集群执行上述第一方面或第一方面的任一种实现方式所述的数据处理方法。
第六方面，本申请提供了一种包含指令的计算机程序产品，当其在计算设备或计算设备集群上运行时，使得计算设备或计算设备集群执行上述第一方面或第一方面的任一种实现方式所述的数据处理方法。
本申请在上述各方面提供的实现方式的基础上，还可以进行进一步组合以提供更多实现方式。
附图说明
为了更清楚地说明本申请实施例的技术方法，下面将对实施例中所需使用的附图作以 简单地介绍。
图1为本申请实施例提供的一种分布式数据管理系统的架构示意图；
图2为本申请实施例提供的一种分布式数据管理系统的架构示意图；
图3为本申请实施例提供的一种多场景联盟中分布式数据管理系统的架构示意图；
图4为本申请实施例提供的一种数据处理方法的流程图；
图5为本申请实施例提供的一种密钥链的示意图；
图6为本申请实施例提供的一种数据处理方法的应用场景示意图；
图7为本申请实施例提供的一种分布式数据管理系统初始化的流程示意图；
图8为本申请实施例提供的一种群组创建的流程示意图；
图9为本申请实施例提供的一种隐私交易发起的流程示意图；
图10为本申请实施例提供的一种隐私交易同步的流程示意图；
图11为本申请实施例提供的一种隐私交易查询的流程示意图；
图12为本申请实施例提供的一种分布式数据管理系统的结构示意图；
图13为本申请实施例提供的一种计算设备的结构示意图；
图14为本申请实施例提供的一种计算设备集群的结构示意图；
图15为本申请实施例提供的一种计算设备集群的结构示意图；
图16为本申请实施例提供的一种计算设备集群的结构示意图。
具体实施方式
本申请实施例中的术语“第一”、“第二”仅用于描述目的，而不能理解为指示或暗示相对重要性或者隐含指明所指示的技术特征的数量。由此，限定有“第一”、“第二”的特征可以明示或者隐含地包括一个或者更多个该特征。
首先对本申请实施例中所涉及到的一些技术术语进行介绍。
区块链网络，也可以简称为区块链，是指基于区块链技术构建的对等(peer to peer，P2P)网络。区块链网络包括多个区块链节点，每个区块链节点为对等节点。在区块链网络中，多个区块链节点共同维护一个持续增长，由有序数据块所构建的区块链账本。每个区块链节点存储上述区块链账本的副本，并保持副本之间的一致性，因此，区块链账本为区块链网络的公有账本。
区块链网络的参与方之间不同参与方之间可以存在一些独特的交易诉求，具体为交易参与方之间的交易信息对链上的非交易参与方不公开。考虑到重新构建一条区块链的成本比较昂贵，可以通过对交易信息进行端到端加密(end-to-end encryption，E2EE)，以满足上述交易诉求，实现交易的隐私保护。
端到端加密是一种只有参与通信的用户可以读取信息的通信系统。它可以防止潜在的窃听者，包括但不限于电信供应商、互联网服务供应商以及该通讯系统的提供者，获取双方通信的明文。此类系统被设计为可以防止潜在的监视或篡改企图。
为了便于理解，本申请提供了具体示例进行说明。在该示例中，区块链网络包括参与方A、参与方B、参与方C、参与方D，参与方A、参与方B、参与方C进行交易，例如参与方A向参与方B、参与方C共享数据时，参与方A可以对数据进行端到端加密，以共 享给参与方B、参与方C，并对参与方D保密。
目前，业界通常采用零知识证明对交易信息进行隐私保护。为了便于理解，以票据场景示例说明。区块链客户端可以生成零知识证明信息，然后发起上链验证，由区块链节点执行对零知识证明信息的有效性验证。如果验证通过，则区块链节点与预先建立的隐私票据池进行隐私交易。其中，隐私票据池用于存储待交易隐私票据。
然而，上述方案需要交易参与方发生变更时，变更智能合约，进行链码升级。例如，参与方A和参与方B进行隐私交易时，需要升级链码，以指定参与方A、参与方B进行隐私交易，如此，大幅降低了区块链网络的性能，影响了交易效率，进而影响了区块链网络的可用性。
有鉴于此，本申请实施例提供了一种数据处理方法。该方法可以应用于分布式数据管理系统。分布式管理系统包括多个数据管理装置。每个数据管理装置为分布式数据管理系统的一部分。其中，分布式数据管理系统实质是一种分布式存储引擎，主要用于对交易信息等数据进行隐私保护，因此，分布式数据管理系统也可以称作分布式隐私保护引擎，分布式数据管理系统中的数据管理装置为上述分布式隐私保护引擎的一部分。多个数据管理装置中的第一数据管理装置对应区块链网络的第一区块链节点，多个数据管理装置中的第二数据管理装置对应区块链网络中的第二区块链节点。
具体地，多个数据管理装置中的目标数据管理装置接收来自区块链客户端的交易请求，该交易请求中包括交易参与方的标识，然后目标数据管理装置根据交易请求，在区块链网络输入输出(input output，IO)交易信息密文，该交易信息密文采用对交易参与方之外的另一参与方不可见的密钥对交易信息明文加密得到，接着目标数据管理装置向区块链客户端返回交易结果。
该方法通过在交易请求中指定交易参与方，并依托区块链实现隐私写入或隐私查询等隐私交易，无需额外编写链代码，或者每次更新链代码，实现了对用户屏蔽隐私数据上链需要开发的链代码、业务代码，降低了操作复杂性，提升了区块链网络的适用范围和易用性。该方法也不需要线下传递私钥，避免了私钥泄露导致的隐私泄露风险。
该方法为区块链网络这种去中心化系统提供一套适配的分布式数据管理系统(也称作分布式隐私保护引擎)完成去中心化的实现隐私保护能力的需求，解决了中心化的系统无法满足分布式管理需求，又会造成集中管理中出现的管理者作恶风险的问题。此外，分布式数据管理系统依托于区块链体系的性能以加密交易信息方式高效利用当前链的性能。
为了使得本申请的技术方案更加清楚、易于理解，下面结合附图对本申请实施例的系统架构进行介绍。
参见图1所示的分布式数据管理系统的架构示意图，分布式数据管理系统100包括多个数据管理装置10，多个数据管理装置10中的每个数据管理装置10分别对应区块链网络200的一个区块链节点20。例如，第一数据管理装置对应第一区块链节点，第二数据管理装置对应第二区块链节点。
进一步地，每个数据管理装置10还可以挂载本地存储30。需要说明，本申请实施例的数据管理装置10支持对不同存储介质的纳管和适配，例如数据管理装置10可以挂载不 同存储介质，包括但不限于机械硬盘(hard disk drive，HDD)或者固态硬盘(solid state drive，SDD)。其中，区块链节点20中包括区块链网络200的区块链账本(属于公有账本)，本地存储30包括区块链网络200的私有账本。
在图1的示例中，数据管理装置10还可以对接区块链客户端40。区块链的参与方如云上租户、云下用户可以通过区块链客户端40发起交易。例如，区块链的参与方可以通过区块链客户端向指定的参与方共享隐私数据，或者查询隐私数据。
具体实现时，多个数据管理装置10中的目标数据管理装置可以接收来自区块链客户端40的交易请求，该交易请求中包括交易参与方的标识(identifier，ID)，例如交易参与方包括参与方A(例如是组织A)、参与方B(例如是组织B)时，交易请求中可以包括组织A的标识和组织B的标识。
然后目标数据管理装置根据该交易请求，在区块链网络200IO交易信息密文。其中，交易请求为存储请求时，可以是在区块链网络200的区块链账本和私有账本存储交易信息密文；交易请求为查询请求时，可以是在区块链网络200的私有账本查询交易信息密文，当私有账本中未查找到交易信息密文时，还可以从区块链账本查询交易信息密文。其中，交易信息密文可以是采用对交易参与方之外的另一参与方(如组织C)不可见的密钥对交易信息明文加密得到。
在一些可能的实现方式中，存储至公有账本的交易信息密文以及存储至私有账本的交易信息密文可以采用不同密钥加密得到。例如，存储至公有账本的交易信息密文，也可以称作第一交易信息密文，可以是基于区块链网络200协商得到的交易发起方在隐私交易群组中的链密钥加密得到。存储至私有账本的交易信息密文，也称作第二交易信息密文，可以是采用证书签发(certificate authority，CA)节点为交易参与方中交易发起方签发的公私钥对中的公钥加密得到。
接着目标数据管理装置向区块链客户端40返回交易结果。针对不同交易请求，交易结果可以是不同的。例如，交易请求为存储请求(也可以称作数据上链请求、数据上传请求)时，交易结果可以是交易成功通知，用于表征存储成功。又例如，交易请求为查询请求(也可以称作数据下载请求)时，交易结果可以包括查询到的交易信息明文。该交易信息明文可以由目标数据管理装置对交易信息密文进行解密得到。
需要说明的是，客户侧除了区块链客户端40外，还可以包括区块链软件开发套件(software development toolkit，SDK)。其中，区块链SDK用于接收交易请求，如用于隐私数据的存储请求、用于查询隐私数据的查询请求，负载在客户侧处理隐私数据的获取、群组、身份的验证计算、提交隐私数据至分布式数据管理系统100侧，与区块链节点200进行进一步交互。
分布式数据管理系统100的数据管理装置10可以包括端到端加密组件，从而实现对交易信息明文进行加密。端到端加密组件包括对于signal算法的优化以及区块链集成的整改，基于区块链网络200完成密钥协商(如链密钥协商)的全过程，取代了中心化系统或中心化节点分发密钥，使用其能力打造高安全的群组交易能力。
数据管理装置10还可以包括群组管理器。群组管理器用于为每个数据管理装置10对应的组织(也可以称作参与方、成员)计算相关群组信息。例如，群组管理器检查隐私交 易群组、创建隐私交易群组、删除隐私交易群组。进一步地，群组管理器还可以触发生成和保存密钥。例如，群组管理器可以触发生成和保存链密钥、临时的公私钥对、对称密钥中的一种或多种。
进一步地，数据管理装置10还可以包括私有账本管理。私有账本管理可以支持对不同参与方的隐私数据进行本地存储，构建隐私数据快速查询能力。同时该模块也可以支持数据丢失时从区块链账本重建本地数据能力。数据管理装置10还可以包括计算校验。计算校验用于为身份验证、群组比较、本地存储信息及链上存储信息比较等提供支持。
端到端加密组件、私有账本管理、群组管理器、计算校验等模块，组合在一起可以依托区块链网络200构建起高可用的分布式数据管理系统100。
在该方案中，所有与隐私数据(被标识为隐私的交易信息)的交互均需通过数据管理装置10(分布式隐私保护引擎的一部分)，并由该数据管理装置10记录交互历史，基于链分享公钥和加密密钥，提升数据的安全性、可访问性与操作可追溯性。而且通过集成端到端加密技术到分布式隐私保护引擎中，支持通过区块链协商端到端加密所需要的公钥和加密密钥，优化其算法流程，依托区块链实现其具备的前向安全(forward secrecy，FS)和后向安全(backward secrecy，BS)能力。前向安全能够保护过去进行的通信不受密码或密钥在未来暴露的威胁。后向安全能够保护未来进行的通信不受密码或密钥在当前暴露的威胁。
需要说明的是，图1所示的数据管理装置10可以是软件装置，该软件装置可以部署在独立于区块链节点的其他计算设备上。图1所示的数据管理装置也可以是硬件装置，例如该硬件装置可以为独立于区块链节点20的、具有隐私保护功能的计算设备。
在一些可能的实现方式中，参见图2所示的分布式数据管理系统100的架构示意图，分布式数据管理系统100的各个数据管理装置10也可以部署在区块链节点20，也即区块链节点20中包括区块链内核和数据管理装置10。其中，数据管理装置10可以是中间件或组件，该中间件或组件可以集成到区块链节点20中。
本申请实施例的分布式数据管理系统100是针对区块链在联盟链场景或是开放联盟链场景下，用户数据针对所有链上参与方开放的，但是部分用户希望通过指定交易参与方定义隐私交易或者隐私信息，所设计的一种融合区块链和端到端加密的系统。该系统通过提供分布式的隐私保护组件(如上述数据管理装置10)，以支持对不同用户进行密钥管理及隐私数据的存储，实现组织级别用户隐私保护，同时基于内嵌式群组管理能力提升用户隐私保护数据上链及查询的便捷性。
分布式数据管理系统100可以应用于金融、能源、政务、航空、农业、民生、物流等行业。例如，分布式数据管理系统100可以应用于商品采购与售卖、非同质化代币(Non-fungible token，NFT)交易等场景。而且，该分布式数据管理系统100可以作为分布式存储底层，支持元宇宙或web3.0。
分布式数据管理系统100应用于上述场景中时，支持部署在私有云、公有云、混合云或边缘节点中。其中，公有云是指云服务提供商通过公共互联网(Internet)为用户提供的云服务，用户可以通过Internet访问云并享受各类服务，包括并不限于计算、存储、网络等。私有云是企业自己建设的为企业内部提供服务的一种云计算使用方式，私有云为一个企业 单独使用而构建，可部署在企业的数据中心中，也可统一部署在云服务提供商的机房。混合云是将私有云和公有云结合的一种云计算使用方式。边缘节点是相对于云计算数据中心的，指与最终接入的用户之间具有较少中间环节的网络节点。边缘节点可以是某个机房或者某个物理设备，相对于直接访问源站而言，用户访问边缘节点时有更好的响应能力和连接速度。
在一些可能的实现方式中，分布式数据管理系统100也可以分布式地部署在不同环境中。参见图3所示的分布式数据管理系统100的架构示意图，分布式数据管理系统100的多个数据管理装置10可以分别部署在公有云、混合云、边缘节点中，从而实现为多场景联盟提供数据管理服务。例如，在一个电商平台上交易商品涉及以下五个组织：农民、托运人、批发商、分销商、零售商。这些组织对应的数据管理装置10可以分布式地部署在公有云、私有云和边缘节点形成的混合环境中。其中，农民在国外售卖商品时，将商品转移到国外的分销商，托运人在各方之间移动商品，批发商从分销商处采购商品，零售商从托运人和批发商那里购买商品，分销商可能希望与农民、托运人进行隐私交易，以使批发商和零售商对交易条款保密，由此避免暴露分销商收取的加价。分销商可能还希望与批发商建立单独的隐私交易，因为它向批发商收取的价格低于零售商。类似地，批发商可能还希望与零售商和发货人建立隐私交易。
基于本申请实施例提供的分布式数据管理系统100，本申请实施例还提供了相应的数据处理方法。
为了使得本申请的技术方案更加清楚、易于理解，下面结合附图对本申请实施例的数据处理方法进行介绍。
参见图4所示的数据处理方法的流程图，该方法包括：
S402：目标数据管理装置接收区块链客户端发送的交易请求。交易请求为存储请求时，执行S404至S410；交易请求为查询请求时，执行S412至S418。
目标数据管理装置可以是分布式数据管理系统100中的任意一个数据管理装置10，例如可以是上述第一数据管理装置，或第二数据管理装置。
交易请求可以是存储请求。存储请求用于存储数据，例如将数据存储至区块链网络200。交易请求也可以是查询请求。查询请求中用于查询数据，例如从区块链网络200获取数据。其中，交易请求中可以包括交易参与方的标识，以指示在交易参与方之间共享数据，而对非交易参与方(如区块链网络中除交易参与方之外的另一参与方)保密。基于此，交易请求为存储请求时，存储请求用于请求将交易信息明文等数据进行端到端加密后上链，交易请求为查询请求时，用于请求将交易信息密文解密获得交易信息明文后返回。
其中，参与方可以是区块链网络的组织，基于此，交易参与方的标识可以是组织名称、组织代码中的一种或多种。例如，用户想要在组织A、组织B之间发起隐私交易时，交易请求中可以包括组织A、组织B的组织名称，从而指定在组织A、组织B之间进行隐私交易，又例如，用户想要在组织B、组织C之间发起隐私交易时，交易请求中可以包括组织B和组织C的组织名称，从而指定在组织B、组织C之间进行隐私交易。
其中，交易请求为存储请求时，交易请求中还可以携带交易信息明文。其中，交易信 息明文具体可以是需要共享的数据。
S404：目标数据管理装置根据交易参与方中交易发起方在隐私交易群组中的链密钥，加密交易信息明文，获得第一交易信息密文。
对于区块链网络中的参与方，该参与方可以在一个或多个隐私交易群组，目标数据管理装置可以根据交易请求中交易参与方的标识，确定本次交易对应的隐私交易群组。例如，交易请求中包括组织A、组织B的组织名称时，目标数据管理装置可以确定隐私交易群组为组织A、组织B形成的群组，记作group(组织A，组织B)。同一组织在不同隐私交易群组可以具有不同的链密钥，目标数据管理装置可以根据本次交易对于的隐私交易群组，获取交易参与方中交易发起方在该隐私交易群组中的链密钥，如组织A在group(组织A，组织B)中的链密钥，然后利用该链密钥进行加密，从而获得第一交易信息密文。
链密钥(chain key)是指密钥派生函数(Key derivation function，KDF)链的KDF密钥。KDF链为KDF密钥链的简称。KDF定义为这样一个密码学函数：输入一个秘密且随机的KDF密钥(KDF key)及其它一些输入数据，并返回输出数据。在密钥未知的前提下，输出的数据与随机数不可区分(也就是说，KDF满足密码学中伪随机函数(pseudo random function，PRF)的要求)。若密钥不是秘密且随机的，则KDF输出应仍然能作为KDF密钥和输入数据的安全的密码学哈希。KDF链包括多个KDF的输出密钥。其中，一个KDF输出的一部分作为输出密钥(Output key)，而另一部分将取代KDF密钥，作为另一个KDF的输入密钥。图5示出了一个处理三个输入密钥(KDF key)并生成三个输出密钥的KDF链。
目标数据管理装置可以根据链密钥，采用双棘轮算法对交易信息进行加密，从而获得第一交易信息密文，然后携带在消息中，以发送至指定的交易参与方所对应的数据管理装置10。
具体地，在组织A和组织B的双棘轮会话中，双方保存的KDF密钥将用于三条链：根链(root chain)、发送链(sending chain)及接收链(receiving chain)(一方的发送链对应另一方的接收链，反之亦然)。
组织A和组织B交换消息(消息中可以携带第一交易信息密文)的同时，也交换新的迪菲-赫尔曼公钥，而迪菲-赫尔曼输出的密钥将作为根链的输入。根链输出的密钥将作为发送链和接收链的KDF密钥。这称为迪菲-赫尔曼棘轮(Diffie-Hellman ratchet)。每发送和接收一条消息，发送链和接收链都将向前推进。相应地，输出密钥将用于加密和解密消息。这称为对称密钥棘轮(symmetric-key ratchet)。
每条发送或接收的消息(携带第一交易密文的消息)可以使用一个唯一的消息密钥(message key)加密。消息密钥是发送KDF链和接收KDF链的输出密钥。由于发送KDF链和接收KDF链的KDF输入是常数，所以这两条链不具备被攻破后的可恢复性。发送链和接收链确保每条消息使用唯一的密钥加密，而此密钥在加密或解密后可以删除。由一个给定的链密钥计算下一个链密钥和消息密钥的过程，称为对称密钥棘轮(symmetric-key ratchet)的一次棘轮步进(ratchet step)。
如果中间攻击者窃取了其中一方的发送链密钥和接收链密钥，那么他可以计算此后所有的消息密钥，并解密对应的消息。为了避免这种情况，双棘轮算法将对称密钥棘轮与DH 棘轮组成在一起，使用后者基于迪菲-赫尔曼的输出更新链密钥。
为了实现DH棘轮，通信双方各自生成一个DH密钥对(迪菲-赫尔曼公钥和私钥)作为当前的棘轮密钥对(ratchet key pair)。从任意一方发出的每一条消息都将携带一个消息头，其中包含发送者当前的棘轮公钥。当接收到远端发送过来的新的棘轮公钥时，本端将实施一次DH棘轮步进(DH ratchet step)，生成一个新的棘轮密钥对以取代本端当前的密钥对。
通信双方交替地更新棘轮密钥对，使之形成一个「乒乓」行为模式。仅截获了其中一方的窃听者可能得到当前棘轮私钥的值，但此棘轮私钥将最终被未泄露的棘轮私钥取代。那时，棘轮密钥对之间的迪菲-赫尔曼计算将定义一个对攻击者未知的新的DH输出。
需要说明的是，目标数据管理装置还可以利用CA节点生成的公私钥对中的私钥进行签名，以便于对端可以进行签名验证，从而确定本端的身份。为了保障安全性，CA节点可以派生临时的公私钥对，目标数据管理装置可以利用临时的私钥，结合签名算法对消息中的第一交易信息密文进行签名。此外，为了提高上链效率，目标数据管理装置可以根据群组以及群组消息构建键值(key value，KV)，然后将群组消息以键值形式上链。
S406：目标数据管理装置存储第一交易信息密文至区块链账本。
具体地，目标数据管理装置可以将第一交易信息密文发送至对应的区块链节点20，由区块链节点20基于区块链网络200的智能合约将该第一交易信息密文存储至区块链账本。其中，区块链节点20可以基于智能合约定义的共识算法进行共识，并在达成共识后，由各个区块链节点20以添加区块的方式将第一交易信息密文存储至各自维护的区块链账本。
S408：目标数据管理装置根据交易参与方中交易发起方的公钥或对称密钥，加密交易信息明文，获得第二交易信息密文。
当目标数据管理装置还挂载本地存储，目标数据管理装置可以利用交易发起方的公钥或对称密钥，通过加密算法对交易信息明文进行加密，从而获得第二交易信息密文。其中，目标数据管理装置利用公钥时，可以通过非对称加密算法进行加密，目标数据管理装置利用对称密钥时，可以通过对称加密算法进行加密。
需要说明的是，该隐私交易群组中其他交易参与方对应的数据管理装置10可以利用该交易参与方的公钥或对称密钥，通过加密算法对交易信息明文进行加密，从而获得第二交易信息密文。
S410：目标数据管理装置存储第二交易信息密文至私有账本。
目标数据管理装置存储该目标数据管理装置计算得到的第二交易信息密文至该目标数据管理装置挂载的本地存储中的私有账本。该隐私交易群组中其他交易参与方对应的数据管理装置10可以存储该数据管理装置10计算得到的第二交易信息密文至该数据管理装置10挂载的本地存储中的私有账本。
不同私有账本存储的第二交易信息密文可以采用各自对应的交易参与方的密钥(公钥或对称密钥)加密得到，因此，不同私有账本存储的第二交易信息密文可以是不同的。
需要说明的是，上述S404至S410为目标数据管理装置根据存储请求，在区块链网络200中存储交易信息密文的一种实现方式，在本申请实施例其他可能的实现方式中，也可以通过其他方式存储交易信息密文。例如，目标数据管理装置也可以不挂载本地存储，相 应地目标数据管理装置可以不执行上述S408、S410。
S412：目标数据管理装置从私有账本查询第二交易信息密文。若查询成功，则可以执行S414。若查询失败，则可以执行S416、S418。
目标数据管理装置挂载本地存储时，目标数据管理装置可以优先从本地存储的私有账本查询第二交易信息密文，以提高查询效率和查询性能。考虑到本地存储的私有账本中第二交易信息密文可能被篡改、删除，或者本地存储的存储介质故障，可以导致查询失败，基于此，目标数据管理装置可以在查询成功时，执行S414进行解密，在查询失败时，执行S416、S418进行第一交易信息密文的获取和解密。
S414：目标数据管理装置解密第二交易信息密文，获得交易信息明文。
具体地，目标数据管理装置采用公钥加密交易信息明文获得第二交易信息密文时，可以利用私钥对第二交易信息密文进行解密，以恢复交易信息明文。目标数据管理装置采用对称密钥加密交易信息明文获得第二交易信息密文时，可以利用对称密钥对第二交易信息密文进行解密，以恢复交易信息明文。
S416：目标数据管理装置从区块链账本查询第一交易信息密文。
目标数据管理装置可以基于区块链网络200的智能合约，从区块链账本查询第一交易信息密文。由于区块链的不可篡改特性，目标数据管理装置可以从各区块链节点20维护的区块链账本查询到上述第一交易信息密文。
S418：目标数据管理装置解密第一交易信息密文，获得交易信息明文。
第一交易信息密文通常是基于链密钥，采用双棘轮算法加密得到。基于此，目标数据管理装置可以结合链密钥，通过双棘轮算法对第一交易信息密文解密，从而获得交易信息明文。
需要说明的是，上述S412、S414为本申请实施例的可选步骤，执行本申请实施例的数据处理方法也可以不执行上述步骤。例如，目标数据管理装置可以根据查询请求，直接从区块链账本查询第一交易信息密文，然后解密该第一交易信息密文，获得交易信息明文。
上述S404至S418为本申请实施例中目标数据管理装置根据所述交易请求，在区块链网络200IO交易信息密文的一种实现方式，执行本申请实施例的数据处理方法也可以通过执行其他步骤实现。
S420：目标数据管理装置向所述区块链客户端返回交易结果。
针对不同交易请求，交易结果有所不同。例如，交易请求为存储请求时，交易结果可以是交易成功通知，用于表征存储成功。又例如，交易请求为查询请求时，交易结果还可以包括查询到的交易信息明文。该交易信息明文可以由目标数据管理装置对交易信息密文进行解密得到。
在一些可能的实现方式中，目标数据管理装置还可以从所述私有账本获取所述私有账本中存储数据的第一元信息，以及从所述区块链网络的区块链账本中获取所述私有账本中存储数据的第二元信息。其中，第一元信息是指私有账本自身存储的数据的元信息，如数据的创建者、创建时间、大小、哈希值中的一种或多种，第二元信息是指链上存储的私有账本中数据的元信息，如数据的创建者、创建时间、大小、哈希值中的一种或多种，第二元信息可以是数据存储至私有账本时，将其元信息上链存储。
目标数据管理装置可以根据所述第一元信息和所述第二元信息进行故障检查，获得故障检查结果。具体地，目标数据管理装置可以比较第一元信息、第二元信息，若第一元信息和第二元信息不匹配，则表明发生故障，例如是私有账本中存储数据被篡改、删除或者所述目标数据管理装置挂载的存储故障，目标管理装置可以写入向区块链网络200中写入故障检查结果。
进一步地，当故障检查结果表征私有账本中存储数据被篡改、删除或者所述目标数据管理装置挂载的存储故障，目标数据管理装置还可以根据所述区块链账本进行故障恢复。具体地，目标数据管理装置可以根据区块链账本中的第一交易信息密文，解密得到交易信息明文，然后加密交易信息明文获得第二交易信息密文，并将该第二交易信息密文存储至私有账本，从而进行故障恢复。
基于上述内容描述，本申请实施例提供了一种数据处理方法。在该方法中，针对区块链在联盟链场景或是开放联盟链场景下，用户数据是针对所有链上参与方开放的，但是部分参与方希望通过指定不同参与方定义隐私交易或者隐私信息，从而设计了一种融合区块链和端到端加密的方法。该方法引入分布式数据管理系统100以支持对不同参与方进行密钥的管理及隐私数据的存储，实现组织级别隐私保护，同时基于内嵌式群组管理能力提升用户隐私数据上链及查询的便捷性。
同时对前后向安全等问题提出了相应的隐私保护算法，基于区块链的传播进行密钥协商，基于端到端加密双棘轮算法提高安全性。用户的操作和加密信息都基于区块链账本记录，因而可以实现全程可追溯。同时在本地账本对当前组织的交易信息明文进行加密存储，本地私有账本丢失后，可以从区块链账本中进行逐条交易解析恢复数据，保证数据一致和可靠性，整体提高其可用性。
为了使得本申请的技术方案更加清楚、易于理解，下面结合一具体场景对本申请实施例的方法进行说明。
参见图6所示的数据处理方法的流程示意图，区块链网络包括组织A对应的区块链节点A、组织B对应的区块链节点B、组织C对应的区块链节点C和组织D对应的区块链节点D。其中，区块链节点A绑定有数据管理装置A，区块链节点B绑定有数据管理装置B，区块链节点C绑定有数据管理装置C，区块链节点D未绑定数据管理装置，因此，区块链节点A、区块链节点B、区块链节点C具有隐私交易能力，而区块链节点D为普通区块链节点，不具有隐私交易能力。
具体实现时，区块链节点绑定的数据管理装置可以创建隐私交易群组。例如，数据管理装置A可以创建如下隐私交易群组：group(组织A，组织B)，group(组织A，组织C)，group(组织B，组织C)以及group(组织A，组织B，组织C)。需要说明的是，随着区块链网络中组织扩容或缩容，数据管理装置还可以动态更新隐私交易群组。例如，组织D加入区块链网络，数据管理装置还可以再创建如下隐私交易群组：group(组织A，组织D)，group(组织A，组织B，组织D)，group(组织A，组织C，组织D)，group(组织B，组织C，组织D)，group(组织C，组织D)以及group(组织A，组织B，组织C)，组织D。
用户通过发送隐私保护交易到区块链隐私保护引擎侧，隐私保护引擎记录隐私交易信 息到本地私有账本，而加密信息会被记录到区块链节点的各个账本中。图3支持不同类型的部署，只有再部署了隐私保护引擎的组织支持发起隐私保护交易，其它节点无法支持此种功能。
数据管理装置A、数据管理装置B、数据管理装置C可以基于区块链网络协商链密钥，并在群组中同步链密钥。当组织A发起交易，如组织A通过区块链客户端向数据管理装置A发送用于存储数据的交易请求，该交易请求中包括组织A的标识、组织B的标识时，数据管理装置A可以组织A在group(组织A，组织B)中的链密钥，加密交易信息明文，获得第一交易信息密文，然后将第一交易信息密文上链存储。进一步地，数据管理装置A还可以利用组织A的公钥或对称密钥加密交易信息明文，获得第二交易信息密文，然后将第二交易信息密文进行本地存储，具体是存储至私有账本。
下面将从数据处理的各个阶段对本申请实施例的方法进行详细介绍。
首先，参见图7所示的分布式数据管理系统初始化的流程示意图，该阶段可以包括如下步骤：
步骤1：分布式数据管理系统的目标数据管理装置周期性地访问区块链节点，获取群组列表、群组状态以及链上事件通知。
步骤2：目标数据管理装置周期性地访问本地存储中的私有账本，获取群组列表、群组状态。
步骤3：目标数据管理装置比较区块链节点中获取的群组列表、群组状态以及本地账本中获取的群组列表、群组状态。若一致，则返回步骤1、步骤2，若不一致，则执行步骤4。
步骤4：目标数据管理装置识别不一致原因，当原因为存在未创建群组或者其他数据管理装置创建超时，则更改链上状态。
步骤5：目标数据管理装置触发群组创建。
步骤6：目标数据管理装置执行链上事件通知。
具体地，目标数据管理装置触发群组创建时可以生成链上事件通知，用于向其他数据管理装置通知当前目标数据管理装置负责创建目标群组，目标数据管理装置可以基于该链上事件通知执行创建目标群组的操作。
在该阶段，分布式数据管理系统的数据管理系统给可以在启动时与区块链网络进行交互，访问区块链节点获取当前链中所存储的群组列表，群组状态及当前组织相关事件等信息，同时加载本地存储的私有账本中群组列表及群组状态，通过比较计算群组差异，如果链上和本地群组一致即完成初始化，如果不一致就识别当前不一致原因，看是否是其它数据管理装置创建群组超时，基于不同原因将创建任务抢占并更新到链上，同时触发群组创建流程。然后返回步骤1、步骤2继续检查群组。
需要说明的是，上述创建群组的过程也可以在进行隐私交易时按需创建，无需在初始化阶段创建全量的隐私交易群组。
然后，参见图8所示的群组创建的流程示意图，该阶段可以包括如下步骤：
步骤1：分布式数据管理系统的各数据管理装置在启动后查询链上组织信息，并同步 群组信息。
步骤2：数据管理装置A基于组织信息创建群组列表，对比本地及链上群组列表，创建缺失群组group(组织A，组织B，组织C)，并更新链上状态、创建时间、创建者。
步骤3：数据管理装置B、数据管理装置C对比检查本地群组及链上群组，确定group(组织A，组织B，组织C)创建任务由数据管理装置A执行，启动对该任务的监听，并为其准备密钥。
步骤4：CA节点分别签发数据管理装置A、数据管理装置B、数据管理装置C在group(组织A，组织B，组织C)中使用的临时公私钥对，数据管理装置A、数据管理装置B、数据管理装置C分别生成在group(组织A，组织B，组织C)中的链密钥。
步骤5：数据管理装置A将数据管理装置A的临时公钥上链，更新链上事务通知组织B、组织C上传其临时公钥。
步骤6：数据管理装置B、C监听链上事务，上传各自的临时公钥，并更新事务状态。
步骤7：数据管理装置A、数据管理装置B和数据管理装置C分别采用其他指定的交易参与方的公钥加密各自的链密钥，并用私钥签名，然后将链密钥的密文上链。
步骤8：数据管理装置A、数据管理装置B和数据管理装置C分别采用其他指定的交易参与方的公钥验证签名，并在验证通过后，利用各自的私钥解密得到其他指定的交易参与方的链密钥，然后将该链密钥加密保存。
图8是以创建group(组织A，组织B，组织C)，并同步链密钥进行示例说明。当缺失的隐私交易群组是其他群组也可以采用类似方式创建群组，并在群组内同步链密钥。
接着，参见图9所示的隐私交易发起的流程示意图，该阶段包括如下步骤：
步骤1：区块链客户端向目标数据管理装置发送交易请求。
交易请求中包括组织A、组织B、组织C的标识，例如是组织A、组织B、组织C的组织名称。
步骤2：目标数据管理装置验证交易请求中携带的签名，以及交易请求指定的组织是否存在。若验证通过，则执行步骤3，若否，则拒绝交易请求。
从区块链客户端发起的交易中包括指定群组的范围及交易的内容，数据管理装置首先检查其签名，如果是非法请求就直接返回，如果是合法请求在校验其隐私交易的组织是否存在，不存在也返回。
步骤3：目标数据管理装置从链上查询交易请求指定组织所归属群组的群组状态。若群组状态为正常，执行步骤4、步骤5进行隐私交易同步，若群组状态为群组不存在、群组处于密钥变更或群组正在创建，触发群组创建或者处理。
群组不存在，或者处于密钥变更过程，或者正在创建，则返回交易请求至区块链客户端让其等待群组创建结束，并发起群组创建流程。
步骤4：目标数据管理装置将交易信息明文加密上链。
步骤5：目标数据管理装置将交易信息明文加密存储至私有账本。
步骤6：目标数据管理装置对隐私交易数量进行计数。当隐私交易数量达到预设数量，执行步骤7。
其中，预设数量可以根据经验值设置，例如预设数量可以设置为10。
步骤7:目标数据管理装置触发密钥更新。
其中，隐私交易同步的详细流程可以参见图10，图10以组织A和组织B之间进行隐私交易示例说明，具体包括如下步骤：
步骤1：组织A通过区块链客户端向数据管理装置A发送交易请求。
步骤2:数据管理装置A可以基于组织A在群组中的链密钥使用双棘轮算法生成消息密钥，利用消息密钥加密交易信息明文，并以私钥签名，然后以群组消息上链。
步骤3：数据管理装置B监听到群组中新消息由数据管理装置A发送，利用组织A在群组中的链密钥生成消息密钥，利用消息密钥解密交易信息密文获得交易信息明文。
步骤4：数据管理装置C监听到链上产生密文，但无法解密。
步骤5：数据管理装置A、数据管理装置B之间的隐私交易数量达到预设数量，触发密钥更新，以生成新的链密钥和公私钥对。
步骤6:数据管理装置A将其在群组中使用的、新的临时公钥上链，并更新链上事务通知群组中其他组织上传新的公钥。
步骤7:数据管理装置B监听链上事务，将其在群组中使用的、新的临时公钥上链，并更新链上事务。
步骤8:数据管理装置A获取组织B在群组中使用的、新的临时公钥，利用该临时公钥加密链密钥，并使用私钥签名，然后将密文上链。
步骤9：数据管理装置B获取组织A在群组中使用的、新的临时公钥，利用该临时公钥加密链密钥，并使用私钥签名，然后将密文上链。
步骤10:数据管理装置A、数据管理装置B使用对端的公钥验证签名，验证通过后，使用自身的私钥解密得到群组中对端的链密钥。
在该实施例中，数据管理装置可以基于区块链传递隐私数据，通过端到端加密的双棘轮算法，定期更新群组秘钥，达成群组交易前向安全能力。数据管理装置还可以基于配置中指定的密钥更新轮换次数来更新隐私交易的密钥。例如，密钥更新轮换次数可以最小指定为一次，达到一次一密的效果，如果达成更新密钥更新轮换次数后，群组成员生成临时公私钥和新的链密钥，再基于之前流程中协商过程同步给群组其他成员知晓。
接着，参见图11所示的隐私交易查询的流程示意图，该阶段包括如下步骤：
步骤1：区块链客户端发送交易请求至目标数据管理装置。
步骤2:目标数据管理装置校验交易请求中的签名。验证通过，则执行步骤3，验证不通过，则拒绝交易请求。
步骤3：目标数据管理装置从本地存储的私有账本查询交易信息密文。
在该实施例中，数据管理装置通过区块链客户端支持隐私交易查询能力。由于数据管理装置可以托管全部的临时密钥，密钥用于交易加密且对用户不可见，所以交易可以基于数据管理装置查询。用户发起隐私交易查询后，数据管理装置可以验证交易请求的签名是否为合法请求，不合法就直接返回，合法则从本地存储的私有账本中查询出结果返回客户。 同时为了保证交易没有经过篡改，目标数据管理装置可以对比链上的哈希以及私有账本的哈希。如果私有账本中不存在，则可以从链上的区块链账本获取交易信息密文。
基于本申请实施例提供的数据处理方法，本申请实施例还提供了一种如前述的分布式数据管理系统100。下面结合附图对分布式数据管理系统100进行介绍。
参见图12所示的分布式数据管理系统100的结构示意图，分布式数据管理系统100包括多个数据管理装置10。多个数据管理装置10中的第一数据管理装置对应区块链网络的第一区块链节点，多个数据管理装置10中的第二数据管理装置对应区块链网络的第二区块链节点。
所述多个数据管理装置10中的目标数据管理装置，用于接收来自区块链客户端的交易请求，所述交易请求中包括交易参与方的标识；
所述目标数据管理装置，还用于根据所述交易请求，在所述区块链网络输入输出IO交易信息密文，所述交易信息密文采用对所述交易参与方之外的另一参与方不可见的密钥对交易信息明文加密得到，向所述区块链客户端返回交易结果。
在一些可能的实现方式中，所述区块链网络的区块链节点中包括区块链账本；
所述目标数据管理装置具体用于：
根据所述交易请求，在所述区块链账本IO交易信息密文。
在一些可能的实现方式中，所述目标数据管理装置挂载本地存储，所述本地存储中包括所述区块链网络的私有账本；
所述目标数据管理装置具体用于：
根据所述交易请求，在所述私有账本IO交易信息密文。
在一些可能的实现方式中，所述交易请求为存储请求，所述交易请求包括交易信息明文；
所述目标数据管理装置具体用于：
根据所述交易参与方中交易发起方在隐私交易群组中的链密钥，加密交易信息明文，获得第一交易信息密文，存储所述第一交易信息密文至所述区块链账本；
根据所述交易参与方中交易发起方的公钥或对称密钥加密交易信息明文，获得第二交易信息密文，存储所述第二交易信息密文至所述私有账本。
在一些可能的实现方式中，所述交易请求为查询请求；
所述目标数据管理装置具体用于：
根据所述交易请求，从所述私有账本或所述区块链账本读取所述交易信息密文；
所述方法还包括：
所述目标数据管理装置对所述交易信息密文进行解密，获得所述交易信息明文；
所述交易结果包括所述交易信息明文。
在一些可能的实现方式中，所述目标数据管理装置还用于：
在根据所述交易请求，在所述区块链网络输入输出IO交易信息密文之前，通过所述区块链网络协商得到所述交易参与方中交易发起方在隐私交易群组中的链密钥；
对所述交易参与方之外的另一参与方不可见的密钥包括所述链密钥。
在一些可能的实现方式中，所述目标数据管理装置还用于：
当密钥更新条件被触发时，通过双棘轮算法更新所述链密钥。
在一些可能的实现方式中，所述密钥更新条件包括：
基于所述链密钥的交易次数达到预设数量。
在一些可能的实现方式中，所述目标数据管理装置还用于：
在根据所述交易请求，在所述区块链网络输入输出IO交易信息密文之前，接收证书签发节点为所述交易参与方中交易发起方签发的公私钥对；
对所述交易参与方之外的另一参与方不可见的密钥包括所述公私钥对中的公钥。
在一些可能的实现方式中，所述目标数据管理装置挂载本地存储，所述本地存储中包括所述区块链网络的私有账本；
所述目标数据管理装置还用于：
从所述私有账本获取所述私有账本中存储数据的第一元信息，以及从所述区块链网络的区块链账本中获取所述私有账本中存储数据的第二元信息；
根据所述第一元信息和所述第二元信息进行故障检查，获得故障检查结果。
在一些可能的实现方式中，所述目标数据管理装置还用于：
当所述故障检查结果表征所述私有账本中存储数据被篡改、删除或者所述目标数据管理装置挂载的存储故障，根据所述区块链账本进行故障恢复。
其中，目标数据管理装置可以为多个数据管理装置10中的任意一个装置，例如可以是上述第一数据管理装置，或者是第二数据管理装置。下面对数据管理装置的结构进行介绍。如图12所示，数据管理装置10包括：
通信模块102，用于接收来自区块链客户端的交易请求，所述交易请求中包括交易参与方的标识；
管理模块104，用于根据所述交易请求，在所述区块链网络输入输出IO交易信息密文，所述交易信息密文采用对所述交易参与方之外的另一参与方不可见的密钥对交易信息明文加密得到；
所述通信模块102，还用于向所述区块链客户端返回交易结果。
需要说明的是，管理模块104用于实现图1或图2、图3所示的群组管理器、端到端加密组件、私有账本管理或计算校验功能。
上述通信模块102、管理模块104可以通过硬件模块实现或通过软件模块实现。
当通过软件实现时，通信模块102、管理模块104可以是运行在计算设备或计算设备集群上的应用程序或者应用程序模块。
当通过硬件实现时，通信模块102可以通过网络接口卡、收发器一类的收发模块实现。管理模块104可以是利用专用集成电路(application-specific integrated circuit，ASIC)实现、或可编程逻辑器件(programmable logic device，PLD)实现的设备等。其中，上述PLD可以是复杂程序逻辑器件(complex programmable logical device，CPLD)、现场可编程门阵列(field-programmable gate array，FPGA)、通用阵列逻辑(generic array logic，GAL)或其任意组合实现。
在一些可能的实现方式中，所述区块链网络的区块链节点中包括区块链账本；
所述管理模块104具体用于：
根据所述交易请求，在所述区块链账本IO交易信息密文。
在一些可能的实现方式中，所述数据管理装置挂载本地存储，所述本地存储中包括所述区块链网络的私有账本；
所述管理模块104具体用于：
根据所述交易请求，在所述私有账本IO交易信息密文。
在一些可能的实现方式中，所述交易请求为存储请求，所述交易请求包括交易信息明文；
所述管理模块104具体用于：
根据所述交易参与方中交易发起方在隐私交易群组中的链密钥，加密交易信息明文，获得第一交易信息密文，存储所述第一交易信息密文至所述区块链账本；
根据所述交易参与方中交易发起方的公钥或对称密钥加密交易信息明文，获得第二交易信息密文，存储所述第二交易信息密文至所述私有账本。
在一些可能的实现方式中，所述交易请求为查询请求；
所述管理模块104具体用于：
根据所述交易请求，从所述私有账本或所述区块链账本读取所述交易信息密文；
所述管理模块104还用于：
对所述交易信息密文进行解密，获得所述交易信息明文；
所述交易结果包括所述交易信息明文。
在一些可能的实现方式中，所述管理模块104还用于：
在根据所述交易请求，在所述区块链网络输入输出IO交易信息密文之前，通过所述区块链网络协商得到所述交易参与方中交易发起方在隐私交易群组中的链密钥；
对所述交易参与方之外的另一参与方不可见的密钥包括所述链密钥。
在一些可能的实现方式中，所述管理模块104还用于：
当密钥更新条件被触发时，通过双棘轮算法更新所述链密钥。
在一些可能的实现方式中，所述密钥更新条件包括：
基于所述链密钥的交易次数达到预设数量。
在一些可能的实现方式中，所述通信模块102还用于：
接收证书签发节点为所述交易参与方中交易发起方签发的公私钥对；
对所述交易参与方之外的另一参与方不可见的密钥包括所述公私钥对中的公钥。
在一些可能的实现方式中，所述数据管理装置10挂载本地存储，所述本地存储中包括所述区块链网络的私有账本；
所述通信模块102还用于：
从所述私有账本获取所述私有账本中存储数据的第一元信息，以及从所述区块链网络的区块链账本中获取所述私有账本中存储数据的第二元信息；
所述装置10还包括：
故障检查模块106，用于根据所述第一元信息和所述第二元信息进行故障检查，获得 故障检查结果。
上述故障检查模块106可以通过硬件模块实现或通过软件模块实现。
当通过软件实现时，故障检查模块106可以是运行在计算设备或计算设备集群上的应用程序或者应用程序模块。
当通过硬件实现时，故障检查模块106可以是利用专用集成电路ASIC实现、或可编程逻辑器件PLD实现的设备等。其中，上述PLD可以是复杂程序逻辑器件CPLD、现场可编程门阵列FPGA、通用阵列逻辑GAL或其任意组合实现。
在一些可能的实现方式中，所述装置10还包括：
故障恢复模块108，用于当所述故障检查结果表征所述私有账本中存储数据被篡改、删除或者所述数据管理装置挂载的存储故障，根据所述区块链账本进行故障恢复。类似地，上述故障恢复模块108可以通过硬件模块实现或通过软件模块实现。
当通过软件实现时，故障恢复模块108可以是运行在计算设备或计算设备集群上的应用程序或者应用程序模块。
当通过硬件实现时，故障恢复模块108可以是利用专用集成电路ASIC实现、或可编程逻辑器件PLD实现的设备等。其中，上述PLD可以是复杂程序逻辑器件CPLD、现场可编程门阵列FPGA、通用阵列逻辑GAL或其任意组合实现。
本申请还提供一种计算设备1300。如图13所示，计算设备1300包括：总线1302、处理器1304、存储器1306和通信接口1308。处理器1304、存储器1306和通信接口1308之间通过总线1302通信。计算设备1300可以是中心云中的计算设备，如中心服务器，或者是边缘云中的计算设备，如边缘服务器。计算设备1300也可以是轻量级设备，如智能手机、智能穿戴设备等终端设备。应理解，本申请不限定计算设备1300中的处理器、存储器的个数。
总线1302可以是外设部件互连标准(peripheral component interconnect，PCI)总线或扩展工业标准结构(extended industry standard architecture，EISA)总线等。总线可以分为地址总线、数据总线、控制总线等。为便于表示，图13中仅用一条线表示，但并不表示仅有一根总线或一种类型的总线。总线1302可包括在计算设备1300各个部件(例如，存储器1306、处理器1304、通信接口1308)之间传送信息的通路。
处理器1304可以包括中央处理器(central processing unit，CPU)、图形处理器(graphics processing unit，GPU)、微处理器(micro processor，MP)或者数字信号处理器(digital signal processor，DSP)等处理器中的任意一种或多种。
存储器1306可以包括易失性存储器(volatile memory)，例如随机存取存储器(random access memory，RAM)。处理器1304还可以包括非易失性存储器(non-volatile memory)，例如只读存储器(read-only memory，ROM)，快闪存储器，机械硬盘(hard disk drive，HDD)或固态硬盘(solid state drive，SSD)。存储器1306中存储有可执行的程序代码，处理器1304执行该可执行的程序代码以实现前述数据处理方法。具体的，存储器1306上存有分布式数据管理系统100或数据管理装置10用于执行数据处理方法的指令。
通信接口1308使用例如但不限于网络接口卡、收发器一类的收发模块，来实现计算设备1300与其他设备或通信网络之间的通信。
本申请实施例还提供了一种计算设备集群。该计算设备集群包括至少一台计算设备1300。该计算设备1300可以是服务器，例如是中心服务器、边缘服务器。在一些实施例中，计算设备1300也可以是终端设备。
如图14所示，所述计算设备集群包括至少一个计算设备1300。计算设备集群中的一个或多个计算设备1300中的存储器1306中可以存有相同的分布式数据管理系统100用于执行数据处理方法的指令。
在一些可能的实现方式中，该计算设备集群中的一个或多个计算设备1300也可以用于执行分布式数据管理系统100用于执行数据处理方法的部分指令。换言之，一个或多个计算设备1300的组合可以共同执行分布式数据管理系统100用于执行数据处理方法的指令。
需要说明的是，计算设备集群中的不同的计算设备1300中的存储器1306可以存储不同的指令，用于执行分布式数据管理系统100的部分功能。
图15示出了一种可能的实现方式。如图15所示，两个计算设备1300A和1300B通过通信接口1308实现连接。计算设备1300A中的存储器上存有用于执行通信模块102、管理模块104的功能的指令。计算设备1300B中的存储器上存有用于故障检测模块106和故障恢复模块108的功能的指令。换言之，计算设备1300A和1300B的存储器1306共同存储了分布式数据管理系统100用于执行数据处理方法的指令。
图15所示的计算设备集群之间的连接方式可以是考虑到本申请提供的数据处理方法在进行故障检查时需要扫描区块链网络中区块链节点维护的分布式账本，在故障恢复时，需要读取区块链节点中存储的故障信息。因此，考虑将通信模块102、管理模块104实现的功能交由计算设备1300A执行，故障检查模块106和故障恢复模块108实现的功能由计算设备1300B执行。
应理解，图15中示出的计算设备1300A的功能也可以由多个计算设备1300完成。同样，计算设备1300B的功能也可以由多个计算设备1300完成。
在一些可能的实现方式中，计算设备集群中的一个或多个计算设备可以通过网络连接。其中，所述网络可以是广域网或局域网等等。图16示出了一种可能的实现方式。如图16所示，两个计算设备1300C和1300D之间通过网络进行连接。具体地，通过各个计算设备中的通信接口与所述网络进行连接。在这一类可能的实现方式中，计算设备1300C中的存储器1306中存有执行通信模块102、管理模块104的功能的指令。同时，计算设备1300D中的存储器1306中存有执行故障检查模块106和故障恢复模块108的功能的指令。
图16所示的计算设备集群之间的连接方式可以是考虑到本申请提供的数据处理方法需要扫描区块链网络中区块链节点维护的分布式账本，或者读取区块链节点中存储的故障信息，因此考虑将通信模块102、管理模块104实现的功能交由计算设备1300C执行，故障检查模块106和故障恢复模块108实现的功能由计算设备1300D执行。应理解，图16中示出的计算设备1300C的功能也可以由多个计算设备1300完成。同样，计算设备1300D的功能也可以由多个计算设备1300完成。
本申请实施例还提供了一种计算机可读存储介质。所述计算机可读存储介质可以是计算设备能够存储的任何可用介质或者是包含一个或多个可用介质的数据中心等数据存储设 备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘)等。该计算机可读存储介质包括指令，所述指令指示计算设备执行上述应用于分布式数据管理系统100的数据处理方法。
本申请实施例还提供了一种包含指令的计算机程序产品。所述计算机程序产品可以是包含指令的，能够运行在计算设备或计算设备集群上或被储存在任何可用介质中的软件或程序产品。当所述计算机程序产品在至少一个计算设备(计算设备或计算设备集群)上运行时，使得至少一个计算设备执行上述数据处理方法。
最后应说明的是：以上实施例仅用以说明本发明的技术方案，而非对其限制；尽管参照前述实施例对本发明进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本发明各实施例技术方案的保护范围。

Claims (26)

  1. 一种数据处理方法，其特征在于，应用于分布式数据管理系统，所述分布式数据管理系统包括多个数据管理装置，所述多个数据管理装置中的第一数据管理装置对应区块链网络的第一区块链节点，所述多个数据管理装置中的第二数据管理装置对应区块链网络的第二区块链节点；
    所述多个数据管理装置中的目标数据管理装置接收来自区块链客户端的交易请求，所述交易请求中包括交易参与方的标识；
    所述目标数据管理装置根据所述交易请求，在所述区块链网络输入输出IO交易信息密文，所述交易信息密文采用对所述交易参与方之外的另一参与方不可见的密钥对交易信息明文加密得到；
    所述目标数据管理装置向所述区块链客户端返回交易结果。
  2. 根据权利要求1所述的方法，其特征在于，所述区块链网络的区块链节点中包括区块链账本；
    所述目标数据管理装置根据所述交易请求，在所述区块链网络输入输出IO交易信息密文，包括：
    所述目标数据管理装置根据所述交易请求，在所述区块链账本IO交易信息密文。
  3. 根据权利要求1所述的方法，其特征在于，所述目标数据管理装置挂载本地存储，所述本地存储中包括所述区块链网络的私有账本；
    所述目标数据管理装置根据所述交易请求，在所述区块链网络输入输出IO交易信息密文，包括：
    所述目标数据管理装置根据所述交易请求，在所述私有账本IO交易信息密文。
  4. 根据权利要求3所述的方法，其特征在于，所述交易请求为存储请求，所述交易请求包括交易信息明文；
    所述目标数据管理装置根据所述交易请求，在所述区块链网络输入输出IO交易信息密文，包括：
    所述目标数据管理装置根据所述交易参与方中交易发起方在隐私交易群组中的链密钥，加密交易信息明文，获得第一交易信息密文，存储所述第一交易信息密文至所述区块链账本；
    所述目标数据管理装置根据所述交易参与方中交易发起方的公钥或对称密钥加密交易信息明文，获得第二交易信息密文，存储所述第二交易信息密文至所述私有账本。
  5. 根据权利要求3所述的方法，其特征在于，所述交易请求为查询请求；
    所述目标数据管理装置根据所述交易请求，在所述区块链网络输入输出IO交易信息密文，包括：
    所述目标数据管理装置根据所述交易请求，从所述私有账本或所述区块链账本读取所述交易信息密文；
    所述方法还包括：
    所述目标数据管理装置对所述交易信息密文进行解密，获得所述交易信息明文；
    所述交易结果包括所述交易信息明文。
  6. 根据权利要求1至5任一项所述的方法，其特征在于，所述目标数据管理装置根据所述交易请求，在所述区块链网络输入输出IO交易信息密文之前，所述方法还包括：
    通过所述区块链网络协商得到所述交易参与方中交易发起方在隐私交易群组中的链密钥；
    对所述交易参与方之外的另一参与方不可见的密钥包括所述链密钥。
  7. 根据权利要求6所述的方法，其特征在于，所述方法还包括：
    当密钥更新条件被触发时，通过双棘轮算法更新所述链密钥。
  8. 根据权利要求7所述的方法，其特征在于，所述密钥更新条件包括：
    基于所述链密钥的交易次数达到预设数量。
  9. 根据权利要求1至5任一项所述的方法，其特征在于，所述目标数据管理装置根据所述交易请求，在所述区块链网络输入输出IO交易信息密文之前，所述方法还包括：
    接收证书签发节点为所述交易参与方中交易发起方签发的公私钥对；
    对所述交易参与方之外的另一参与方不可见的密钥包括所述公私钥对中的公钥。
  10. 根据权利要求1至9任一项所述的方法，其特征在于，所述目标数据管理装置挂载本地存储，所述本地存储中包括所述区块链网络的私有账本；
    所述方法还包括：
    所述目标数据管理装置从所述私有账本获取所述私有账本中存储数据的第一元信息，以及从所述区块链网络的区块链账本中获取所述私有账本中存储数据的第二元信息；
    根据所述第一元信息和所述第二元信息进行故障检查，获得故障检查结果。
  11. 根据权利要求10所述的方法，其特征在于，所述方法还包括：
    当所述故障检查结果表征所述私有账本中存储数据被篡改、删除或者所述目标数据管理装置挂载的存储故障，所述目标数据管理装置根据所述区块链账本进行故障恢复。
  12. 一种分布式数据管理系统，其特征在于，所述分布式数据管理系统包括多个数据管理装置，所述多个数据管理装置中的第一数据管理装置对应区块链网络的第一区块链节点，所述多个数据管理装置中的第二数据管理装置对应区块链网络的第二区块链节点；
    所述多个数据管理装置中的目标数据管理装置，用于接收来自区块链客户端的交易请求，所述交易请求中包括交易参与方的标识；
    所述目标数据管理装置，还用于根据所述交易请求，在所述区块链网络输入输出IO交易信息密文，所述交易信息密文采用对所述交易参与方之外的另一参与方不可见的密钥对交易信息明文加密得到，向所述区块链客户端返回交易结果。
  13. 根据权利要求12所述的系统，其特征在于，所述区块链网络的区块链节点中包括区块链账本；
    所述目标数据管理装置具体用于：
    根据所述交易请求，在所述区块链账本IO交易信息密文。
  14. 根据权利要求12所述的系统，其特征在于，所述目标数据管理装置挂载本地存储，所述本地存储中包括所述区块链网络的私有账本；
    所述目标数据管理装置具体用于：
    根据所述交易请求，在所述私有账本IO交易信息密文。
  15. 根据权利要求14所述的系统，其特征在于，所述交易请求为存储请求，所述交易请求包括交易信息明文；
    所述目标数据管理装置具体用于：
    根据所述交易参与方中交易发起方在隐私交易群组中的链密钥，加密交易信息明文，获得第一交易信息密文，存储所述第一交易信息密文至所述区块链账本；
    根据所述交易参与方中交易发起方的公钥或对称密钥加密交易信息明文，获得第二交易信息密文，存储所述第二交易信息密文至所述私有账本。
  16. 根据权利要求14所述的系统，其特征在于，所述交易请求为查询请求；
    所述目标数据管理装置具体用于：
    根据所述交易请求，从所述私有账本或所述区块链账本读取所述交易信息密文；
    所述方法还包括：
    所述目标数据管理装置对所述交易信息密文进行解密，获得所述交易信息明文；
    所述交易结果包括所述交易信息明文。
  17. 根据权利要求11至16任一项所述的系统，其特征在于，所述目标数据管理装置还用于：
    在根据所述交易请求，在所述区块链网络输入输出IO交易信息密文之前，通过所述区块链网络协商得到所述交易参与方中交易发起方在隐私交易群组中的链密钥；
    对所述交易参与方之外的另一参与方不可见的密钥包括所述链密钥。
  18. 根据权利要求17所述的系统，其特征在于，所述目标数据管理装置还用于：
    当密钥更新条件被触发时，通过双棘轮算法更新所述链密钥。
  19. 根据权利要求18所述的系统，其特征在于，所述密钥更新条件包括：
    基于所述链密钥的交易次数达到预设数量。
  20. 根据权利要求11至16任一项所述的系统，其特征在于，所述目标数据管理装置还用于：
    在根据所述交易请求，在所述区块链网络输入输出IO交易信息密文之前，接收证书签发节点为所述交易参与方中交易发起方签发的公私钥对；
    对所述交易参与方之外的另一参与方不可见的密钥包括所述公私钥对中的公钥。
  21. 根据权利要求11至20任一项所述的系统，其特征在于，所述目标数据管理装置挂载本地存储，所述本地存储中包括所述区块链网络的私有账本；
    所述目标数据管理装置还用于：
    从所述私有账本获取所述私有账本中存储数据的第一元信息，以及从所述区块链网络的区块链账本中获取所述私有账本中存储数据的第二元信息；
    根据所述第一元信息和所述第二元信息进行故障检查，获得故障检查结果。
  22. 根据权利要求21所述的系统，其特征在于，所述目标数据管理装置还用于：
    当所述故障检查结果表征所述私有账本中存储数据被篡改、删除或者所述目标数据管理装置挂载的存储故障，根据所述区块链账本进行故障恢复。
  23. 一种数据管理装置，其特征在于，所述数据管理装置对应区块链网络的区块链节点，所述数据管理装置包括：
    通信模块，用于接收来自区块链客户端的交易请求，所述交易请求中包括交易参与方的标识；
    管理模块，用于根据所述交易请求，在所述区块链网络输入输出IO交易信息密文，所述交易信息密文采用对所述交易参与方之外的另一参与方不可见的密钥对交易信息明文加密得到；
    所述通信模块，还用于向所述区块链客户端返回交易结果。
  24. 一种计算设备集群，其特征在于，所述计算设备集群包括至少一台计算设备，所述至少一台计算设备包括至少一个处理器和至少一个存储器，所述至少一个存储器中存储有计算机可读指令；所述至少一个处理器执行所述计算机可读指令，以使得所述计算设备集群执行如权利要求1至11中任一项所述的方法。
  25. 一种计算机可读存储介质，其特征在于，包括计算机可读指令；所述计算机可读指令用于实现权利要求1至11任一项所述的方法。
  26. 一种计算机程序产品，其特征在于，包括计算机可读指令；所述计算机可读指令用于实现权利要求1至11任一项所述的方法。
PCT/CN2023/081446 2022-08-31 2023-03-14 一种数据处理方法及相关设备 Ceased WO2024045552A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP23858594.7A EP4560974A4 (en) 2022-08-31 2023-03-14 DATA PROCESSING AND ASSOCIATED DEVICES
US19/067,606 US20250202724A1 (en) 2022-08-31 2025-02-28 Data processing method and related device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211063836.7A CN117675216A (zh) 2022-08-31 2022-08-31 一种数据处理方法及相关设备
CN202211063836.7 2022-08-31

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US19/067,606 Continuation US20250202724A1 (en) 2022-08-31 2025-02-28 Data processing method and related device

Publications (1)

Publication Number Publication Date
WO2024045552A1 true WO2024045552A1 (zh) 2024-03-07

Family

ID=90072073

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/081446 Ceased WO2024045552A1 (zh) 2022-08-31 2023-03-14 一种数据处理方法及相关设备

Country Status (4)

Country Link
US (1) US20250202724A1 (zh)
EP (1) EP4560974A4 (zh)
CN (1) CN117675216A (zh)
WO (1) WO2024045552A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN118631588A (zh) * 2024-08-09 2024-09-10 北京三友卓越科技有限公司 一种数字地球空间的访问控制方法、设备及介质

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN118094639B (zh) * 2024-04-28 2024-07-02 北京中关村科金技术有限公司 基于人工智能的企业大数据挖掘方法及系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109493020A (zh) * 2018-11-08 2019-03-19 众安信息技术服务有限公司 基于区块链的安全交易方法和装置
CN110033266A (zh) * 2019-02-19 2019-07-19 阿里巴巴集团控股有限公司 区块链中实现隐私保护的方法、节点和存储介质
CN110335043A (zh) * 2019-07-03 2019-10-15 中国银行股份有限公司 一种基于区块链系统的交易隐私保护方法、设备以及系统
CN110827034A (zh) * 2019-10-31 2020-02-21 支付宝(杭州)信息技术有限公司 用于发起区块链交易的方法及装置
US20200259665A1 (en) * 2017-11-15 2020-08-13 Tencent Technology (Shenzhen) Company Limited Transaction data processing method, computing device, and storage medium

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112883015A (zh) * 2021-04-23 2021-06-01 北京中科金财科技股份有限公司 区块链数据管理方法、设备及存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200259665A1 (en) * 2017-11-15 2020-08-13 Tencent Technology (Shenzhen) Company Limited Transaction data processing method, computing device, and storage medium
CN109493020A (zh) * 2018-11-08 2019-03-19 众安信息技术服务有限公司 基于区块链的安全交易方法和装置
CN110033266A (zh) * 2019-02-19 2019-07-19 阿里巴巴集团控股有限公司 区块链中实现隐私保护的方法、节点和存储介质
CN110335043A (zh) * 2019-07-03 2019-10-15 中国银行股份有限公司 一种基于区块链系统的交易隐私保护方法、设备以及系统
CN110827034A (zh) * 2019-10-31 2020-02-21 支付宝(杭州)信息技术有限公司 用于发起区块链交易的方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4560974A4

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN118631588A (zh) * 2024-08-09 2024-09-10 北京三友卓越科技有限公司 一种数字地球空间的访问控制方法、设备及介质

Also Published As

Publication number Publication date
EP4560974A4 (en) 2025-11-12
EP4560974A1 (en) 2025-05-28
US20250202724A1 (en) 2025-06-19
CN117675216A (zh) 2024-03-08

Similar Documents

Publication Publication Date Title
US11356285B2 (en) Distributed key management for trusted execution environments
TWI725655B (zh) 用於在可信執行環境中執行子邏輯代碼的程式執行和資料證明的方法、設備和系統
US20220166634A1 (en) Method and apparatus for generating blockchain transaction
AU2019204725B2 (en) Retrieving access data for blockchain networks using highly available trusted execution environments
US11893577B2 (en) Cryptographic key storage system and method
CN111541724B (zh) 区块链一体机及其节点自动加入方法、装置
US11514446B2 (en) Method and apparatus for starting smart contract, electronic device, and storage medium
EP3619668B1 (en) Performing parallel execution of transactions in a distributed ledger system
WO2022193985A1 (zh) 一种数据处理方法、装置、设备及存储介质
CN112751673B (zh) 一种基于端边云协同的可监管数据隐私共享方法
WO2023024742A1 (zh) 一种数据处理方法、装置、计算机设备及存储介质
JP2020528224A (ja) 信頼できる実行環境におけるスマート契約動作のセキュアな実行
CA3058013A1 (en) Managing sensitive data elements in a blockchain network
CN115412568A (zh) 分布式数据传输方法、装置及系统
WO2022193984A1 (zh) 跨链进行数据传输的方法、装置、计算机设备、存储介质和计算机程序产品
US20250202724A1 (en) Data processing method and related device
CN111212139A (zh) 对信任节点信息进行更新的方法及装置
CN111541552A (zh) 区块链一体机及其节点自动加入方法、装置
CN113259130B (zh) 一种交易数据处理方法、装置、设备以及介质
CN111241593A (zh) 用于区块链节点的数据同步方法及装置
CN111211876B (zh) 发送针对数据请求的应答消息的方法及装置、区块链系统
CN111162970B (zh) 在区块链系统中测试去中心化应用服务器的方法及装置
WO2021172589A1 (ja) 情報処理システム、及びプログラム
CN115914243B (zh) 一种信息处理方法及装置、存储介质
HK40029934A (zh) 在区块链系统中测试去中心化应用服务器的方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23858594

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2023858594

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2023858594

Country of ref document: EP

Effective date: 20250220

NENP Non-entry into the national phase

Ref country code: DE

WWP Wipo information: published in national office

Ref document number: 2023858594

Country of ref document: EP