WO2022001960A1 - 代理方法、设备及计算机可读存储介质 - Google Patents

代理方法、设备及计算机可读存储介质 Download PDF

Info

Publication number
WO2022001960A1
WO2022001960A1 PCT/CN2021/102766 CN2021102766W WO2022001960A1 WO 2022001960 A1 WO2022001960 A1 WO 2022001960A1 CN 2021102766 W CN2021102766 W CN 2021102766W WO 2022001960 A1 WO2022001960 A1 WO 2022001960A1
Authority
WO
WIPO (PCT)
Prior art keywords
private data
transaction
proxy
agent
data
Prior art date
Application number
PCT/CN2021/102766
Other languages
English (en)
French (fr)
Inventor
曾鸣
王德政
郭海生
屠要峰
张强
周治中
Original Assignee
中兴通讯股份有限公司
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 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to AU2021300461A priority Critical patent/AU2021300461A1/en
Priority to US18/003,393 priority patent/US20230247106A1/en
Priority to KR1020237002756A priority patent/KR20230027284A/ko
Priority to JP2022581656A priority patent/JP7488379B2/ja
Priority to EP21832546.2A priority patent/EP4174702A4/en
Publication of WO2022001960A1 publication Critical patent/WO2022001960A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
    • G06F21/6245—Protecting personal data, e.g. for financial or medical purposes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/602—Providing cryptographic facilities or services
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/64—Protecting data integrity, e.g. using checksums, certificates or signatures
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/64—Protecting data integrity, e.g. using checksums, certificates or signatures
    • G06F21/645—Protecting data integrity, e.g. using checksums, certificates or signatures using a third party
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/04—Payment circuits
    • G06Q20/06—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
    • G06Q20/065—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
    • G06Q20/3821—Electronic credentials
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
    • G06Q20/3825—Use of electronic signatures
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
    • G06Q20/3829—Payment protocols; Details thereof insuring higher security of transaction involving key management
    • 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/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
    • H04L63/0281—Proxies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1045—Proxies, e.g. for session initiation protocol [SIP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H04L65/4061—Push-to services, e.g. push-to-talk or push-to-video
    • 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/12—Transmitting and receiving encryption devices synchronised or initially set up in a particular manner
    • 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/50—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols using hash chains, e.g. blockchains or hash trees

Definitions

  • Embodiments of the present application provide a proxy method, device, and computer-readable storage medium.
  • an agent method provided by an embodiment of the present application which is used for a first agent, includes: acquiring transaction data of a user, where the transaction data includes a transaction request and private data; storing the private data locally, and Send the transaction request to the blockchain platform, so that the blockchain platform completes the transaction according to the transaction request; after completing the transaction, the private data is sent to the peer agent for transaction verification.
  • a proxy method provided by an embodiment of the present application is used for a second proxy, including: acquiring private data sent by a peer proxy, the private data being stored in the peer proxy, and used for retrieving data sent by the peer proxy The transaction is verified by sending a transaction request to the blockchain platform; the transaction verification is performed on the private data.
  • a computer-readable storage medium provided by an embodiment of the present application stores computer-executable instructions, where the computer-executable instructions are used to execute the first aspect embodiment or the second aspect embodiment. proxy method.
  • FIG. 1 is a schematic diagram of a system architecture platform provided by an embodiment of the present application.
  • FIG. 3 is a flowchart of a proxy method provided by another embodiment of the present application.
  • FIG. 6 is a flowchart of a proxy method provided by another embodiment of the present application.
  • FIG. 8 is a flow chart of the transaction process of Embodiment 1 of the present application.
  • FIG. 9 is a flowchart of a data acquisition process in Embodiment 1 of the present application.
  • This application provides a proxy method, proxy node, device and computer-readable storage medium proposed in this application.
  • the transaction data includes transaction request and private data, and then sending the transaction request to the blockchain platform,
  • the blockchain platform completes the transaction according to the transaction request, stores the private data locally, and sends the private data to the peer agent for transaction verification after the transaction is completed.
  • FIG. 1 is a schematic diagram of a system architecture platform 100 for executing a proxy method provided by an embodiment of the present application.
  • the system architecture platform 100 includes a business layer 120, a communication layer 150 and a storage layer 160, wherein the business layer 120 is used to submit a transaction request to the blockchain platform and notify the storage of private data; communication The layer 150 is used to establish a communication connection between the agent modules; the database is used to store the user's private data.
  • the business layer 120 is used to send the transaction request to the blockchain platform, and the blockchain platform completes the transaction according to the transaction request, and passes The storage layer 160 stores the private data locally.
  • the communication layer 150 is used to establish a communication connection with the peer agent, and the private data is sent to the peer agent for transaction verification, thereby completing the transaction.
  • the system architecture platform 100 can be understood as an agent module that executes the agent method, and the agent module is deployed on the accounting node of the blockchain platform, that is, both parties to the transaction are connected to the blockchain platform through the agent module to conduct transactions, thus utilizing the blockchain
  • the non-tampering characteristics of the technology ensure the credibility and traceability of the transaction.
  • the private data is only traded between the local agents of both parties to the transaction, and the private data is stored in the agent mode for local storage. It will be uploaded on the blockchain platform, and the private data is only completed between the agent modules of both parties of the transaction, which effectively solves the problem that the private data of the blockchain platform is easily leaked.
  • the transaction security is high, and the private data is effectively protected. function, and private data does not need to be on the chain, which can reduce the occupation of a large amount of storage space.
  • the proxy module is responsible for connecting the blockchain platform and the local database for users, helping users to safely complete private data transactions.
  • the proxy module includes an adaptation layer 110, a business layer 120, a model layer 130, an access layer 140, a communication layer 150 and a storage layer 160, wherein the adaptation layer 110 is used to adapt different blockchains through a unified interface of encapsulation
  • the difference in platform interface supports different alliance chains, public and private blockchain platforms such as Hyperledger Fabric, Fisco Bcos, and Ethereum.
  • the business layer 120 is mainly responsible for submitting transactions to the blockchain platform, and notifying the data management module to store and synchronize private data.
  • the model layer 130 is used for unified modeling of smart contracts, transactions, private data, and configurations to provide support for storage and transactions.
  • the access layer 140 is used to perform human-computer interaction with the transaction user through the Cli command line to complete the transaction agency and data synchronization functions.
  • the communication layer 150 uses the gossip protocol to communicate with the proxy modules of other nodes, and uses a message queue to buffer messages sent by other proxy modules.
  • the storage layer 160 is used to store the configuration information and private data of the agent module, wherein the configuration initialization information is used to configure the blockchain platform type, address, port, channel information, and access certificates that need to be connected; the private data is encrypted by the local database Storage, supports common databases such as couchDB and RocksDB.
  • a smart contract is a computer protocol designed to disseminate, verify or execute contracts in an information-based manner
  • blockchain can provide a decentralized and trusted environment, so smart contracts can be compatible with blockchain , that is, smart contracts can be implemented based on blockchain technology.
  • the proxy module can provide a unified interface through the adaptation layer 110, which can support different blockchain platforms, make the system architecture platform 100 suitable for cross-blockchain platforms, and can solve the problem of privacy leakage in most blockchain platforms. question of risk.
  • the system architecture platform 100 and the application scenarios described in the embodiments of the present application are for the purpose of illustrating the technical solutions of the embodiments of the present application more clearly, and do not constitute limitations on the technical solutions provided by the embodiments of the present application.
  • the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.
  • system architecture platform 100 shown in FIG. 1 does not constitute a limitation to the embodiments of the present application, and may include more or less components than those shown in the figure, or combine certain components, or different component layout.
  • the adaptation layer 110 the service layer 120 , the model layer 130 , the access layer 140 , the communication layer 150 and the storage layer 160 can cooperate to execute the proxy method.
  • FIG. 2 is a flowchart of a proxy method provided by an embodiment of the present application.
  • the proxy method includes but is not limited to step S100, step S200, and step S300.
  • Step S100 acquiring transaction data of the user, where the transaction data includes a transaction request and private data.
  • the transaction process is implemented based on blockchain technology. It can be understood that transaction data needs to be generated according to the user's transaction content before the transaction, and then the transaction data is sent online, where the transaction content can be understood as the two parties to the transaction. The transaction details agreed in the offline, the two parties of the transaction can exchange account numbers and public keys with each other to produce transaction data and encrypt and decrypt the transaction data.
  • step S200 the private data is stored locally, and a transaction request is sent to the blockchain platform, so that the blockchain platform completes the transaction according to the transaction request.
  • the local storage of private data can be understood as using the local proxy module to store the private data, specifically using the storage layer of the local proxy module to store the private data; at the same time, the transaction request is sent to the blockchain platform, It can be understood that only the transaction request is sent to the blockchain platform, and the private data does not need to be sent to the blockchain platform, that is, the private data will not be uploaded to the chain.
  • the blockchain platform will execute the corresponding transaction after receiving the transaction request.
  • the transaction request includes the data that can be used by the blockchain platform to complete the transaction.
  • the blockchain platform completes the transaction according to the transaction request on the premise that the two parties to the transaction can be identified.
  • the private data will not be sent to the blockchain platform. Therefore, It can effectively avoid the leakage of private data, which is beneficial to improve the security of transactions.
  • Step S300 after the transaction is completed, the private data is sent to the counterparty agent for transaction verification.
  • the private data is stored in the local agent module, and after the transaction is completed on the blockchain platform, the private data is sent to the peer agent, and the peer agent can be understood as the corresponding transaction counterparty.
  • Agent for example, the buyer is the data provider, the buyer's agent is the first agent, the seller is the data demander, and the seller's agent is the second agent.
  • the first agent sends a transaction request to the blockchain platform and stores the private data Locally, after the transaction is completed, the first agent sends private data to the second agent for transaction verification, where the second agent can be understood as the opposite-end agent of the first agent.
  • the private data will not be uploaded through the blockchain platform, and the private data will be directly traded between the agents, which effectively solves the problem that the private data of the blockchain platform is easily leaked.
  • the problem is that the transaction security is high, and it can effectively protect the private data; and the private data does not need to be on the chain, that is, the on-chain data is isolated from the private data, which can not only ensure the traceability of the transaction, but also solve the problem caused by the private data on the chain. It takes up a lot of storage space and has the problem of privacy leakage, which effectively solves the problem of poor data privacy protection across blockchain platforms.
  • step S100, step S200 and step S300 are the execution flow of the first agent, which belong to the execution steps on the data provider side in the transaction body, wherein the transaction verification step in step S300 is executed on the opposite end agent.
  • step S100 before acquiring the user's transaction data, the following steps are also included but not limited to:
  • Step S110 generating a digest according to the private data, encrypting the private data, and signing the encrypted private data;
  • Step S120 Generate a transaction request according to the digest and the signature.
  • a summary is generated according to the private data, and the summary may be understood as a content summary of the private data.
  • the provider of the transaction data uses its own private key to sign the private data, and the use of the signature can facilitate the verification of the identity of the data provider.
  • the locally stored private data is encrypted and signed data to ensure the security of the private data.
  • Generate a transaction request according to the digest and signature that is, the transaction request includes the digest and signature, but is not limited to only the digest and signature.
  • the transaction request can also include the accounts of both parties to the transaction, etc.
  • the local agent sends the transaction request including the digest and signature to the Blockchain platform, the blockchain platform initiates the transaction and completes the transaction accounting between the two agents through the smart contract.
  • the transaction accounting contains the summary of private data and the signature information, which ensures that the transaction can be traced and secured. higher.
  • step S300 after completing the transaction, the private data is sent to the counterparty agent for transaction verification, which further includes but is not limited to the following steps:
  • Step S310 Send a push request to the peer proxy
  • Step S320 Receive the response information sent by the peer agent according to the push request
  • Step S330 Send private data to the opposite-end proxy according to the response information, so that the opposite-end proxy performs transaction verification according to the private data.
  • the proxy module of the data provider initiates the push process of private data to the proxy module of the data demander.
  • the first agent acts as the sending side of private data and acts as an agent for the data provider;
  • the second agent acts as the receiving side of private data and acts as an agent for the data demander.
  • Step S311 the first agent establishes a Transport Layer Security (TLS) link to the second agent, and initiates a push request, so that the second agent returns an agree response according to the push request, and returns the requested random number;
  • TLS Transport Layer Security
  • Step S321 the first agent receives the response information of the second agent, and pushes the private data to the second agent, including the push flow and summary information;
  • Step S331 After completing the private data push, the first agent sends an end message to the second agent.
  • the parameters of the push request include the ID of the first agent, the channel number, the account number of the recipient, the transaction ID and the random number. If the private data to be pushed is large, it can be sent in sub-packages. In addition, after the push of the private data is completed, the second agent verifies the private data and stores it locally, thereby completing the sending of the private data.
  • the first agent sends private data to the second agent through the Gossip protocol.
  • the Gossip protocol is a widely used protocol in distributed systems and is mainly used to realize information exchange between distributed nodes or processes. Meet the requirements of low load, high reliability and scalability required by application layer multicast protocols.
  • the proxy method further includes but is not limited to the following steps:
  • Step S400 Receive a synchronization request from the peer agent, and return a summary list of private data according to the synchronization request, so that the peer agent compares with the private data stored by itself according to the summary list, and returns the request list when it is determined that the private data is missing;
  • Step S500 Send private data to the peer proxy according to the request list.
  • the synchronization request can be understood as the synchronization request of private data. Since there is data loss or failure in the sending process of private data, in order to ensure the consistency of private data in the proxy storage of both parties of the transaction and meet the requirements of transaction verification, After the private data is sent, the peer proxy will initiate a synchronization request.
  • Step S410 the first agent receives the synchronization request from the second agent
  • Step S420 The first agent returns the summary list of private data that meets the conditions and the requested random number according to the synchronization request, so that the second agent determines the missing private data after comparing it with the summary of the private data stored by itself, and makes the second agent sending a request list to the first agent;
  • Step S510 the first agent sequentially pushes private data to the second agent according to the request list
  • Step S520 After completing the push of all private data, the first agent sends a push end message to the second agent.
  • the information of the synchronization request includes the agent ID, the range filtering parameters of the synchronization data (for example, time, account number, transaction ID, etc.) and a random number (marking this request).
  • the second agent sends a synchronization request for private data to the first agent through the TLS link.
  • the second agent verifies the private data and stores it locally.
  • the synchronization process of private data is performed periodically by all agents, that is, in the embodiment, the first agent periodically receives synchronization requests from the second agent, thereby effectively solving the problem of loss of private data.
  • Step S600 when the storage time of the private data exceeds the preset storage time, delete the private data.
  • the private data is stored on the local proxy module, for example, the private data of the first proxy is stored on the proxy module of the first proxy, the private data of the second proxy is stored on the proxy module of the second proxy, and the proxy module Periodically clear the locally stored private data to ensure that the agent module has enough storage space.
  • the proxy method is an execution step on the side of the data demander in a transaction subject, and the subject executing the steps of the proxy method is the peer in step S300 of the embodiment. acting.
  • the proxy method includes but is not limited to the following steps:
  • Step S101 obtaining private data sent by the peer agent, the private data is stored in the peer agent, and used to verify the transaction performed by the peer agent by sending a transaction request to the blockchain platform;
  • Step S201 Perform transaction verification on the private data.
  • the peer proxy in this embodiment is the first proxy
  • the second proxy obtains the private data sent by the first proxy, And perform transaction verification on private data.
  • the process of sending private data from the first agent to the second agent reference may be made to the process of the embodiment shown in FIG. 2 , and details are not repeated here.
  • step S201 the transaction verification is performed on the private data, which further includes but is not limited to the following steps:
  • Step S211 Perform signature verification on the private data to confirm the user who provides the private data
  • Step S212 Decrypt the private data, and generate a comparison summary from the decrypted private data, so as to compare the comparison summary with the summary of the private data of the peer agent to confirm whether the private data is valid.
  • the second agent stores the received private data locally, and the data demander obtains the private data through the second agent, and uses the public key to perform signature verification on the private data to confirm the identity of the user who provided the private data. For example, if the verified signatures are consistent, it is confirmed that the data provider of the private data is the object of the transaction.
  • the second agent decrypts the private data with the private key, and generates a comparison summary of the decrypted private data, and the comparison summary can be compared with the summary of the private data sent by the first agent to determine the private data. Whether it has been tampered with, if the comparison summary is inconsistent with the sent summary, it can be considered that the private data has been tampered with, and the transaction process can be traced to ensure the security of data transactions.
  • the proxy method further includes but is not limited to the following steps:
  • Step S301 Send a synchronization request to the peer agent
  • Step S302 Receive a summary list of private data returned by the peer agent according to the synchronization request, and compare the summary list with the private data stored by itself;
  • the peer agent is the first agent
  • the second agent sends a synchronization request to the peer agent
  • the first agent returns a summary list of private data according to the synchronization request
  • the second agent returns a summary list of private data according to the summary list and the private data stored by itself. Compare to see if private data is missing.
  • the second agent determines the missing private data, it returns a request list to the first agent, and the first agent sends the private data according to the request list, thereby completing the synchronization operation of the private data.
  • the synchronization process of private data is performed by all agents periodically, and the second agent periodically requests synchronization to the first agent, thereby ensuring the consistency of the private data stored in the first agent and the second agent.
  • the deployment process includes the following steps:
  • Step S701 Deploy the agent program to the environment where the local blockchain node is located, place the certificate in the cert certificate directory, and place the smart contract to be installed in the corresponding language in the contracts directory;
  • Step S703 Modify the config/config.yaml configuration file to complete the relevant configuration of the locally connected blockchain platform;
  • Step S705 the deployment process ends.
  • the fabric platform includes the organization name, peer and orderer addresses, and certificate configuration.
  • the transaction process includes the following steps:
  • Step S708 the first agent uploads the encrypted private data to the local accounting node and stores it in the local database;
  • Step S709 The first agent pushes the private data to the second agent of the accounting node where the user B is located, and the second agent receives the private data and stores it in the local database to complete the private data transaction.
  • the transaction accounting includes summary information of private data to ensure that the transaction can be traced back, and the smart contract can automatically complete the deduction of user B's points and the increase of user A's points.
  • the data acquisition process includes the following steps:
  • Step S710 User B obtains private data from the second agent, and provides the transaction account number and transaction ID;
  • Step S711 the second agent confirms that the private data belongs to user B according to the transaction account number and transaction ID, and returns the address for obtaining the private data to user B;
  • Step S712 User B obtains the private data through the address, and uses the public key of User A to verify the signature of the private data, confirming that the data is the data provided by User A;
  • Step S713 User B decrypts the private data with the private key, and generates a comparison summary for the private data, and compares it with the summary provided by User A to confirm that the data has not been tampered with;
  • Step S714 End the private data acquisition process.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • the deployment process includes the following steps:
  • Step S803 Modify the config/config.yaml configuration file to complete the relevant configuration of the locally connected blockchain platform;
  • Step S804 Execute the proxy start command to start the proxy service program
  • Step S805 the deployment process ends.
  • the Fabric platform includes the organization name, peer, orderer address, encryption algorithm and certificate configuration.
  • the transaction process includes the following steps:
  • Step S806 User A submits a transaction through the first agent, including encrypted private data, digest, signature, transaction party B's affiliation organization and account number;
  • Step S807 The first agent initiates a transaction to the blockchain platform, and completes transaction accounting through a smart contract;
  • Step S808 the first agent uploads the encrypted data to the local blockchain accounting node and stores it in the local database
  • Step S809 The first agent pushes the private data to the second agent of the billing node where the user B is located, and the second agent receives the data and stores it in the local database to complete the private data transaction.
  • the transaction accounting includes summary information of private data to ensure that the transaction can be traced back, and the smart contract can automatically complete the deduction of user B's points and the increase of user A's points.
  • the data acquisition process includes the following steps:
  • Step S810 User B obtains private data from the second agent, and provides the transaction account number and transaction ID;
  • Step S811 the second agent confirms that the private data belongs to user B according to the transaction account number and transaction ID, and returns the address for obtaining the private data to user B;
  • Step S812 User B obtains the private data through the address, and uses the public key of User A to verify the signature of the private data, confirming that the data is the data provided by User A;
  • Step S813 User B decrypts the private data with the private key, generates a comparison summary for the private data, and compares it with the summary provided by User A to confirm that the data has not been tampered with;
  • Step S814 End the private data acquisition process.
  • an embodiment of the present application also provides a device, the device includes: a memory, a processor, and a computer program stored on the memory and executable on the processor.
  • the processor and memory may be connected by a bus or otherwise.
  • the memory can be used to store non-transitory software programs and non-transitory computer-executable programs.
  • the memory may include high-speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid state storage device.
  • the memory may include memory located remotely from the processor, which may be connected to the processor through a network. Examples of such networks include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.
  • the terminal in this embodiment may include the system architecture platform 100 in the embodiment shown in FIG. 1 , and the terminal in this embodiment and the system architecture platform 100 in the embodiment shown in FIG. 1 belong to the same Therefore, these embodiments have the same realization principle and technical effect, and will not be described in detail here.
  • the non-transitory software programs and instructions required to implement the proxy method of the above embodiment are stored in the memory, and when executed by the processor, the proxy method in the above embodiment is executed, for example, the method steps in FIG. 2 described above are executed S100 to S300, method steps S110 to S120 in FIG. 3, method steps S310 to S330 in FIG. 4, method steps S400 to S500 in FIG. 5, method steps S100 to S102 in FIG. Method steps S701 to S705 , method steps S706 to S709 in FIG. 8 , and method steps S710 to S714 in FIG. 9 .
  • an embodiment of the present application also provides a computer-readable storage medium, where the computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are executed by a processor or controller, for example, by the above-mentioned
  • the execution of a processor in the terminal embodiment can cause the above-mentioned processor to execute the proxy method in the above-mentioned embodiment, for example, to execute the above-described method steps S100 to S300 in FIG. 2 , method steps S110 to S120 in FIG. 3 , Method steps S310 to S330 in FIG. 4 , method steps S400 to S500 in FIG. 5 , method steps S100 to S102 in FIG. 6 , method steps S701 to S705 in FIG. 7 , method steps S706 in FIG. 8 Go to step S709, and step S710 to step S714 of the method in FIG. 9 .
  • the embodiments of the present application include: by acquiring the user's transaction data, the transaction data includes transaction requests and private data, and then sending the transaction request to the blockchain platform, the blockchain platform completes the transaction according to the transaction request, and locally stores the private data. , after the transaction is completed, the private data is sent to the peer agent for transaction verification.
  • the non-tamperable feature of blockchain technology is used to ensure the credibility and traceability of the transaction, and the private data is only between the local agents of both parties to the transaction.
  • Conduct transactions, and store private data locally that is, private data will not be uploaded through the blockchain platform, effectively solving the problem of easy leakage of private data on the blockchain platform, high transaction security, and effective for private data. Protection, suitable for cross-blockchain platforms, and private data does not need to be on the chain, which can reduce the occupation of a large amount of storage space.
  • Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cartridges, magnetic tape, magnetic disk storage or other magnetic storage devices, or may Any other medium used to store desired information and which can be accessed by a computer.
  • communication media typically embodies computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and can include any information delivery media, as is well known to those of ordinary skill in the art .

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Business, Economics & Management (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Accounting & Taxation (AREA)
  • General Health & Medical Sciences (AREA)
  • Bioethics (AREA)
  • Health & Medical Sciences (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Software Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Finance (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • Medical Informatics (AREA)
  • Databases & Information Systems (AREA)
  • Multimedia (AREA)
  • Computing Systems (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Hardware Redundancy (AREA)

Abstract

一种代理方法、设备及计算机可读存储介质，其中代理方法通过获取用户的交易数据，该交易数据包括交易请求和私有数据，然后向区块链平台发送交易请求，区块链平台根据交易请求完成交易，并将私有数据进行本地存储，在完成交易后将私有数据发送至对端代理进行交易核验。

Description

代理方法、设备及计算机可读存储介质
相关申请的交叉引用
本申请基于申请号为202010599762.3、申请日为2020年6月28日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本申请涉及计算机技术领域，特别涉及一种代理方法、设备及计算机可读存储介质。
背景技术
当今社会处于信息高速增长的时代，数据作为一个新的商品，其共享和交易成为当今技术和商业的一个新热点。传统的交易往往依赖第三方的交易中心来达成交易，而这些交易中心背后都有可信机构来监管和背书，所以整个交易过程繁琐，时间较长。由于数据与传统商品相比存在较大的差异，容易传播和复制，涉及个人和企业的隐私需要保密，所以对于数据交易的过程可追溯和数据的完整性、可靠性都有更高的要求，需要一种可信、不可篡改、可追溯的交易手段来保证数据交易的安全进行。
区块链是一种多方共享的分布式记账的数据库技术，其技术的核心是块状数据链式存储与智能合约，并且只能读取和写入，不能修改和删除。然而区块链是去中心的架构，所有的节点共同参与记账并共同维护账本，上链的数据是对所有用户公开的，这样的设计不利于数据隐私保护，如果直接把隐私数据上链会存在数据泄露的问题。目前大多数区块链平台仍未能对隐私数据进行有效保护，存在隐私泄露的风险，尤其是在跨区块链平台的技术领域，没有一个统一、有效的解决方法。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本申请实施例提出一种代理方法、设备及计算机可读存储介质。
第一方面，本申请实施例提供的一种代理方法，用于第一代理，包括：获取用户的交易数据，所述交易数据包括交易请求和私有数据；将所述私有数据进行本地存储，并向区块链平台发送所述交易请求，以使区块链平台根据所述交易请求完成交易；在完成交易后将所述私有数据发送至对端代理进行交易核验。
第二方面，本申请实施例提供的一种代理方法，用于第二代理，包括：获取对端代理发送的私有数据，所述私有数据保存于对端代理，且用于对由对端代理通过向区块链平台发送交易请求而进行的交易进行核验；对所述私有数据进行交易核验。
第三方面，本申请实施例提供的一种设备，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现如上述第一方面实施例或第二方面实施例所述的代理方法。
第四方面，本申请实施例提供的一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行如上述第一方面实施例或第二方面实施例所述的代理方法。
本申请的其它特征和优点将在随后的说明书中阐述，并且，部分地从说明书中变得显而易见，或者通过实施本申请而了解。本申请的目的和其他优点可通过在说明书、权利要 求书以及附图中所特别指出的结构来实现和获得。
附图说明
附图用来提供对本申请技术方案的进一步理解，并且构成说明书的一部分，与本申请的实施例一起用于解释本申请的技术方案，并不构成对本申请技术方案的限制。
图1是本申请一个实施例提供的系统架构平台的示意图；
图2是本申请一个实施例提供的代理方法的流程图；
图3是本申请另一实施例提供的代理方法的流程图；
图4是本申请另一实施例提供的代理方法的流程图；
图5是本申请另一实施例提供的代理方法的流程图；
图6是本申请另一实施例提供的代理方法的流程图；
图7是本申请实施例一的部署过程的流程图；
图8是本申请实施例一的交易过程的流程图；
图9是本申请实施例一的数据获取过程的流程图。
具体实施方式
为了使本申请的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本申请进行进一步详细说明。应当理解，此处所描述的具体实施例仅用以解释本申请，并不用于限定本申请。
需要说明的是，虽然在装置示意图中进行了功能模块划分，在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于装置中的模块划分，或流程图中的顺序执行所示出或描述的步骤。说明书、权利要求书或上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
区块链是一种多方共享的分布式记账的数据库技术，其技术的核心是块状数据链式存储与智能合约，并且只能读取和写入，不能修改和删除。区块链重点解决的是在不信任的网络中进行价值传递的问题。采用区块链技术进行数据交易，既可以保证交易的可信、可追溯，又可以减少第三方介入环节，提高交易效率。由于区块链是去中心的架构，所有的节点共同参与记账并共同维护账本，上链的数据是对所有用户公开的，这样的设计不利于数据隐私保护，如果直接把隐私数据上链会存在数据泄露的问题。
针对目前区块链平台仍未能对隐私数据进行有效保护，仍然存在隐私泄露的风险，尤其是在跨区块链平台的技术领域，没有一个统一、有效的解决方法。本申请提供了本申请提出一种代理方法、代理节点、设备及计算机可读存储介质，通过获取用户的交易数据，该交易数据包括交易请求和私有数据，然后向区块链平台发送交易请求，区块链平台根据交易请求完成交易，并将私有数据进行本地存储，在完成交易后将私有数据发送至对端代理进行交易核验，这样，利用区块链技术的不可篡改的特性，保证交易的可信、可追溯，同时私有数据只在交易双方的本地代理间进行交易，且私有数据进行本地存储，即私有数据不会通过区块链平台进行上链，有效解决区块链平台的私有数据容易泄露的问题，交易安全性高，对私有数据起到有效的保护作用，适用于跨区块链平台，且私有数据无需上链，从而可减少占用大量存储空间。
下面将结合附图对本申请的技术方案进行清楚、完整的描述，显然，以下所描述的实施例是本申请一部分实施例，并非全部实施例。
参见图1所示，图1是本申请一个实施例提供的用于执行代理方法的系统架构平台100 示意图。
在图1所示的实施例中，系统架构平台100包括业务层120、通讯层150和存储层160，其中，业务层120用于向区块链平台提交交易请求，并通知存储私有数据；通讯层150用于在代理模块之间建立通讯连接；数据库用于存储用户的私有数据。基于区块链平台交易时，通过获取用户的交易数据，该交易数据包括交易请求和私有数据，利用业务层120向区块链平台发送交易请求，区块链平台根据交易请求完成交易，并通过存储层160将私有数据进行本地存储，在完成交易后，利用通讯层150与对端代理建立通讯连接，并将私有数据发送至对端代理进行交易核验，从而完成交易。
该系统架构平台100可理解为执行代理方法的代理模块，该代理模块部署在区块链平台的记账节点上，即交易双方通过代理模块连接到区块链平台进行交易，这样利用区块链技术的不可篡改的特性，保证交易的可信、可追溯，同时私有数据只在交易双方的本地代理间进行交易，且将私有数据存储在代理模式上，进行本地存储，交易过程中私有数据不会通过区块链平台进行上链，私有数据只在交易双方的代理模块之间完成，有效解决区块链平台的私有数据容易泄露的问题，交易安全性高，对私有数据起到有效的保护作用，且私有数据无需上链，从而可减少占用大量存储空间。
如图1所示，以具体的代理模块结构为示例进行说明，代理模块负责为用户连接区块链平台和本地数据库，帮助用户安全完成私有数据的交易。
具体的，代理模块包括适配层110、业务层120、模型层130、接入层140、通讯层150和存储层160，其中，适配层110用于通过封装统一接口适配不同区块链平台接口的差异，支持Hyperledger Fabric、Fisco Bcos、以太坊等不同的联盟链、公私区块链平台。业务层120主要负责向区块链平台提交交易，并通知数据管理模块进行私有数据的存储和同步功能。模型层130用于针对智能合约、交易、私有数据、配置进行统一建模为存储和交易提供支撑。接入层140用于通过Cli命令行方式与交易用户进行人机交互完成交易代理和数据同步功能。通讯层150采用gossip协议与其他节点的代理模块通讯，并使用消息队列来缓存其它代理模块发送过来的消息。存储层160用于存放代理模块的配置信息和私有数据，其中配置初始化信息用于配置需要连接的区块链平台类型、地址、端口、通道信息以及访问采用的证书等；私有数据采用本地数据库加密存储，支持couchDB、RocksDB等常用数据库。
需要说明的是，在区块链平台上进行交易时，通过智能合约执行交易，该智能合约负责执行交易，记录交易并同时完成交易用户的积分账号转账操作。可理解到，智能合约是一种旨在以信息化方式传播、验证或执行合同的计算机协议，而区块链可以提供一个去中心化的可信环境，因此智能合约可与区块链相契合，即智能合约能够基于区块链技术来实现。另外，代理模块可通过适配层110提供统一接口，这样能够支持不同的区块链平台，使系统架构平台100适用于跨区块链平台，能够解决目前大多数区块链平台存在隐私泄露的风险的问题。
本申请实施例描述的系统架构平台100以及应用场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域技术人员可知，随着系统架构平台100的演变和新应用场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
本领域技术人员可以理解的是，图1中示出的系统架构平台100并不构成对本申请实 施例的限定，可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。
在图1所示的系统架构平台100中，适配层110、业务层120、模型层130、接入层140、通讯层150和存储层160可以配合执行代理方法。
基于上述系统架构平台100，下面提出本申请的代理方法的各个实施例。
参见图2所示，图2是本申请一个实施例提供的代理方法的流程图，该代理方法包括但不限于步骤S100、步骤S200和步骤S300。
步骤S100，获取用户的交易数据，交易数据包括交易请求和私有数据。
在一实施例中，交易过程是基于区块链技术而实现的，可理解到，交易前需要根据用户的交易内容生成交易数据，然后通过线上发送交易数据，其中交易内容可理解为交易双方线下约定的交易明细，交易双方可相互交换账号和公钥，以用于生产交易数据和对交易数据进行加解密。
交易双方通过代理模块连接到区块链平台进行交易，具体的，交易双方在区块链平台的记账节点上部署对应的代理模块，通过本地代理模块完成交易工作。实施例中，获取用户的交易数据的步骤通过代理模块执行，获取到的交易数据包括交易请求和私有数据，其中交易请求可包括交易双方账户、交易时间等，私有数据包括个人身份信息等隐私信息的数据。
步骤S200，将私有数据进行本地存储，并向区块链平台发送交易请求，以使区块链平台根据交易请求完成交易。
在一实施例中，将私有数据进行本地存储可理解为利用本地代理模块对私有数据进行存储，具体是利用本地代理模块的存储层存放私有数据；同时将交易请求向区块链平台进行发送，可理解到，仅将交易请求发送给区块链平台，无需将私有数据发给区块链平台，即私有数据不会上链。区块链平台接收到交易请求后会执行相应的交易。
需要说明的是，交易请求包括能够供区块链平台完成交易的数据，区块链平台根据交易请求在能够识别交易双方的前提下完成交易，私有数据并不会发送至区块链平台，因此能够有效避免私有数据的泄漏，有利于提高交易的安全性。
步骤S300，在完成交易后将私有数据发送至对端代理进行交易核验。
在一实施例中，在步骤S200中，将私有数据存储在本地代理模块中，在区块链平台上完成交易后将私有数据发送给对端代理，对端代理可理解为交易对方所对应的代理，例如，买方作为数据提供方，买方的代理为第一代理，卖方作为数据需求方，卖方的代理为第二代理，交易时第一代理向区块链平台发送交易请求并将私有数据存储在本地，待交易完成后，第一代理向第二代理发送私有数据进行交易核验，其中，第二代理可理解为第一代理的对端代理。
相对于传统的交易方法，本实施例的交易过程中私有数据并不会通过区块链平台进行上链，私有数据直接在代理之间进行交易，有效解决区块链平台的私有数据容易泄露的问题，交易安全性高，对私有数据起到有效的保护作用；且私有数据无需上链，即上链数据与私有数据隔离，既可以保证交易的可追溯，又解决了私有数据上链造成的占用大量存储空间以及存在隐私泄露的问题，有效解决跨区块链平台对数据隐私保护性差的问题。
实施例中，步骤S100、步骤S200和步骤S300为第一代理的执行流程，属于交易主体中数据提供方一侧的执行步骤，其中在步骤S300中的交易核验步骤在对端代理上执行。
参见图3，在一实施例中，步骤S100中，在获取用户的交易数据之前，还包括但不限于以下步骤：
步骤S110：根据私有数据生成摘要，并对私有数据进行加密，并对加密后的私有数据进行签名；
步骤S120：根据摘要和签名生成交易请求。
具体的，在获取交易数据之前，根据私有数据生成摘要，该摘要可理解为私有数据的内容概要。利用交易双方的公钥对私有数据进行加密，并利用私钥对加密后的私有数据进行签名，其中，公钥可理解为交易双方持有的公共的密钥，私钥可理解为交易双方各自持有的密钥，交易数据的提供方利用自己的私钥对私有数据进行签名，利用签名可便于核实数据提供方的身份。
可理解到，本地存储的私有数据为经过加密和签名的数据，保证私有数据的安全性。根据摘要和签名生成交易请求，即交易请求包括有摘要和签名，但不限于仅有摘要和签名，如交易请求还可包括交易双方账户等，本地代理将包括有摘要和签名的交易请求发送给区块链平台，区块链平台发起交易并通过智能合约完成两代理之间的交易记账，在交易记账中包含有私有数据的摘要和签名的信息，这样可确保交易可以追溯，安全性更高。
参见图4，在一实施例中，步骤S300中，在完成交易后将私有数据发送至对端代理进行交易核验，还包括但不限于以下步骤：
步骤S310：向对端代理发送推送请求；
步骤S320：接收对端代理根据推送请求发出的响应信息；
步骤S330：根据响应信息向对端代理发送私有数据，以使对端代理根据私有数据进行交易核验。
当本地代理模块通过区块链平台完成交易上链以后，由数据提供方的代理模块向数据需求方的代理模块发起私有数据的推送流程。
具体的，第一代理作为私有数据的发送侧，代理数据提供方；第二代理作为私有数据的接收侧，代理数据需求方，以此为示例进行说明，包括但不限于以下步骤：
步骤S311：第一代理向第二代理建立安全传输层协议(TLS)链接，并发起推送请求，以使第二代理根据推送请求返回同意响应，并返回请求随机数；
步骤S321：第一代理接收第二代理的响应信息，并向第二代理推送私有数据并包括推送流水、摘要信息；
步骤S331：完成私有数据推送后，第一代理向第二代理发送结束消息。
其中，推送请求的参数包括第一代理的ID、通道号、接收方的账号、交易ID和随机数。若推送的私有数据较大，可进行分包发送。另外，在私有数据推送完成，第二代理对私有数据进行校验并进行本地存储，从而完成私有数据的发送。
需要说明的是，第一代理通过Gossip协议向第二代理发送私有数据，Gossip协议是分布式系统中被广泛使用的协议，主要用于实现分布式节点或者进程之间的信息交换，Gossip协议同时满足应用层多播协议所要求的低负载，高可靠和可扩展性的要求。
参见图5，在一实施例中，代理方法还包括但不限于以下步骤：
步骤S400：接收对端代理的同步请求，并根据同步请求返回私有数据的摘要列表，以使对端代理根据摘要列表与自身存储的私有数据进行对比，并当确定缺失私有数据，返回请求列表；
步骤S500：根据请求列表向对端代理发送私有数据。
其中，同步请求可理解为私有数据的同步请求，由于在私有数据的发送过程中存在数据丢失或发送失败情况，因此为保证私有数据在交易双方的代理存储的一致性，满足交易核验的要求，在私有数据发送完成后，对端代理会发起同步请求。
具体的私有数据同步过程为：
步骤S410：第一代理接收到来自第二代理的同步请求；
步骤S420：第一代理根据同步请求返回满足条件的私有数据的摘要列表和请求随机数，以使第二代理通过与自身存储私有数据的摘要对比后，确定缺失的私有数据，并使第二代理向第一代理发送请求列表；
步骤S510：第一代理根据请求列表依次向第二代理推送私有数据；
步骤S520：完成所有私有数据推送后，第一代理向第二代理发送推送结束消息。
其中，同步请求的信息包括代理ID、同步数据的范围过滤参数(例如是时间、账号、交易ID等)和随机数(标注本次请求)。第二代理通过TLS链接向第一代理发送私有数据的同步请求。另外，在私有数据推送完成，第二代理对私有数据进行校验并进行本地存储。
需要说明的是，私有数据的同步流程是所有代理都会定期执行，即实施例中，第一代理定期接收第二代理的同步请求，从而有效解决私有数据丢失的问题。
在一实施例中，代理方法还包括但不限于以下步骤：
步骤S600：当私有数据的存储时间超过预设保存时间，删除私有数据。
可理解到，私有数据存储在本地的代理模块上，例如，第一代理的私有数据存储在第一代理的代理模块上，第二代理的私有数据存储在第二代理的代理模块上，代理模块定期对本地存储的私有数据进行清除，以保证代理模块具有足够的存储空间。
参见图6所示，本申请另一个实施例提供的代理方法，该代理方法为交易主体中数据需求方一侧的执行步骤，执行该代理方法步骤的主体是实施例的步骤S300中的对端代理。
具体的，该代理方法包括但不限于以下步骤：
步骤S101：获取对端代理发送的私有数据，私有数据保存于对端代理，且用于对由对端代理通过向区块链平台发送交易请求而进行的交易进行核验；
步骤S201：对私有数据进行交易核验。
以第一代理代理数据提供方，第二代理代理数据需求方为示例进行说明，可理解到，本实施例中的对端代理为第一代理，第二代理获取第一代理发送的私有数据，并对私有数据进行交易核验。第一代理向第二代理发送私有数据的流程可参考图2所示实施例的流程，此处不再赘述。
在一实施例中，步骤S201中，对私有数据进行交易核验，还包括但不限于以下步骤：
步骤S211：对私有数据进行签名验证，以确认提供私有数据的用户；
步骤S212：对私有数据进行解密，并将解密的私有数据生成对比摘要，以将对比摘要与对端代理的私有数据的摘要进行对比，确认私有数据是否有效。
具体的，第二代理将接收的私有数据存储在本地，数据需求方通过第二代理获取私有数据，并利用公钥对私有数据进行签名验证，确认提供该私有数据的用户身份。例如，若验证的签名一致，则确认该私有数据的数据提供方为交易的对象。
经过签名验证后，第二代理利用私钥对私有数据进行解密，并将经过解密的私有数据生成对比摘要，利用该对比摘要可与第一代理发送的私有数据的摘要进行对比，判断该私 有数据是否被篡改过，若对比摘要与发送的摘要不一致，则可认为私有数据被篡改，可追溯交易过程，从而保证数据交易的安全性。
在一实施例中，代理方法还包括但不限于以下步骤：
步骤S301：向对端代理发送同步请求；
步骤S302：接收对端代理根据同步请求返回私有数据的摘要列表，并根据摘要列表与自身存储的私有数据进行对比；
步骤S303：当确定缺失私有数据，向对端代理返回请求列表，以使对端代理根据请求列表发送私有数据。
本实施例中的对端代理为第一代理，第二代理向对端代理发送同步请求，第一代理根据该同步请求返回私有数据的摘要列表，第二代理根据摘要列表与自身存储的私有数据进行对比，确认私有数据是否存在缺失。第二代理确定缺失的私有数据时，向第一代理返回请求列表，第一代理根据该请求列表发送私有数据，从而完成私有数据的同步操作。其中，在同步流程中，第一代理向第二代理发送私有数据的步骤可参考上述实施例的步骤S410至步骤S520所示流程，此处不再赘述。
需要说明的是，私有数据的同步流程是所有代理都会定期执行，第二代理定期向第一代理的同步请求，从而保证第一代理与第二代理中存储的私有数据的一致性。
为了更加清楚的说明上述各个实施例中代理方法的具体步骤流程，以下通过两个实施例进行说明。
实施例一：
以Fabric平台隐私数据交易实施流程为示例，包括部署、交易和数据获取过程。
参见图7所示，部署过程包括以下步骤：
步骤S701：将代理程序部署到本地区块链节点所在环境上，并将证书放置在cert证书目录，且将需要安装的智能合约放置在contracts目录下对应的语种下；
步骤S702：修改config/config.yaml配置文件，设置对接区块链平台类型，替换本地存储DB地址、配置对端代理地址；
步骤S703：修改config/config.yaml配置文件，完成本地对接的区块链平台相关配置；
步骤S704：执行代理开始命令，启动代理服务程序；
步骤S705：部署过程结束。
其中，fabric平台包括组织名称、peer和orderer地址和证书配置。
参见图8所示，交易过程包括以下步骤：
步骤S706：用户A通过第一代理提交交易，包括加密的私有数据、摘要、签名、用户B归属组织和账号；
步骤S707：第一代理向区块链平台发起交易，通过智能合约完成交易记账；
步骤S708：第一代理把加密的私有数据上传到本地记账节点并存入本地数据库；
步骤S709：第一代理向用户B所在的记账节点的第二代理推送私有数据，第二代理接收私有数据并存入本地数据库，完成私有数据交易。
其中，交易记账包含了私有数据的摘要信息，确保交易可以追溯，同时智能合约能够自动完成用户B的积分扣除和用户A的积分增加操作。
参见图9所示，数据获取过程包括以下步骤：
步骤S710：用户B向第二代理获取私有数据，提供交易账号、交易ID；
步骤S711：第二代理根据交易账号和交易ID确认该私有数据属于用户B，并返回给用户B获取私有数据的地址；
步骤S712：用户B通过地址获取私有数据，并利用用户A的公钥对私有数据签名验证，确认该数据是用户A提供的数据；
步骤S713：用户B利用私钥对私有数据进行解密，同时对私有数据生成对比摘要，并与用户A提供的摘要进行比对，确认数据未被篡改；
步骤S714：结束私有数据获取过程。
实施例二：
以跨平台(Fabric-Fscio)隐私数据交易实施流程为示例，包括部署、交易和数据获取过程。
部署过程包括以下步骤：
步骤S801：将代理程序部署到本地区块链节点所在环境上，并将证书放置在cert证书目录，且将需要安装的智能合约放置在contracts目录下对应的语种下；
步骤S802：修改config/config.yaml配置文件，设置对接区块链平台类型，替换本地存储DB地址、配置对端代理地址；
步骤S803：修改config/config.yaml配置文件，完成本地对接的区块链平台相关配置；
步骤S804：执行代理开始命令，启动代理服务程序；
步骤S805：部署过程结束。
其中，Fabric平台包括组织名称、peer、orderer地址、加密算法和证书配置。
交易过程包括以下步骤：
步骤S806：用户A通过第一代理提交交易，包括加密的私有数据、摘要、签名、交易方B归属组织和账号；
步骤S807：第一代理向区块链平台发起交易，通过智能合约完成交易记账；
步骤S808：第一代理把加密数据上传到本地区块链记账节点并存入本地数据库；
步骤S809：第一代理向用户B所在的记账节点的第二代理推送私有数据，第二代理接收数据并存入本地数据库，完成私有数据交易。
其中，交易记账包含了私有数据的摘要信息，确保交易可以追溯，同时智能合约能够自动完成用户B的积分扣除和用户A的积分增加操作。
数据获取过程包括以下步骤：
步骤S810：用户B向第二代理获取私有数据，提供交易账号、交易ID；
步骤S811：第二代理根据交易账号和交易ID确认该私有数据属于用户B，并返回给用户B获取私有数据的地址；
步骤S812：用户B通过地址获取私有数据，并利用用户A的公钥对私有数据签名验证，确认该数据是用户A提供的数据；
步骤S813：用户B利用私钥对私有数据进行解密，同时对私有数据生成对比摘要，并与用户A提供的摘要进行比对，确认数据未被篡改；
步骤S814：结束私有数据获取过程。
另外，本申请的一个实施例还提供了一种设备，该设备包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序。处理器和存储器可以通过总线或者其他方式连接。
存储器作为一种非暂态计算机可读存储介质，可用于存储非暂态软件程序以及非暂态性计算机可执行程序。此外，存储器可以包括高速随机存取存储器，还可以包括非暂态存储器，例如至少一个磁盘存储器件、闪存器件、或其他非暂态固态存储器件。在一些实施方式中，存储器可包括相对于处理器远程设置的存储器，这些远程存储器可以通过网络连接至该处理器。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
需要说明的是，本实施例中的终端，可以包括有如图1所示实施例中的系统架构平台100，本实施例中的终端和如图1所示实施例中的系统架构平台100属于相同的发明构思，因此这些实施例具有相同的实现原理以及技术效果，此处不再详述。
实现上述实施例的代理方法所需的非暂态软件程序以及指令存储在存储器中，当被处理器执行时，执行上述实施例中的代理方法，例如，执行以上描述的图2中的方法步骤S100至S300、图3中的方法步骤S110至S120、图4中的方法步骤S310至S330、图5中的方法步骤S400至步骤S500、图6中的方法步骤S100至步骤S102、图7中的方法步骤S701至步骤S705、图8中的方法步骤S706至步骤S709、图9中的方法步骤S710至步骤S714。
以上所描述的装置实施例仅仅是示意性的，其中作为分离部件说明的单元可以是或者也可以不是物理上分开的，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。
此外，本申请的一个实施例还提供了一种计算机可读存储介质，该计算机可读存储介质存储有计算机可执行指令，该计算机可执行指令被一个处理器或控制器执行，例如，被上述终端实施例中的一个处理器执行，可使得上述处理器执行上述实施例中的代理方法，例如，执行以上描述的图2中的方法步骤S100至S300、图3中的方法步骤S110至S120、图4中的方法步骤S310至S330、图5中的方法步骤S400至步骤S500、图6中的方法步骤S100至步骤S102、图7中的方法步骤S701至步骤S705、图8中的方法步骤S706至步骤S709、图9中的方法步骤S710至步骤S714。
本申请实施例包括：通过获取用户的交易数据，该交易数据包括交易请求和私有数据，然后向区块链平台发送交易请求，区块链平台根据交易请求完成交易，并将私有数据进行本地存储，在完成交易后将私有数据发送至对端代理进行交易核验，这样，利用区块链技术的不可篡改的特性，保证交易的可信、可追溯，同时私有数据只在交易双方的本地代理间进行交易，且私有数据进行本地存储，即私有数据不会通过区块链平台进行上链，有效解决区块链平台的私有数据容易泄露的问题，交易安全性高，对私有数据起到有效的保护作用，适用于跨区块链平台，且私有数据无需上链，从而可减少占用大量存储空间。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、系统可以被实施为软件、固件、硬件及其适当的组合。某些物理组件或所有物理组件可以被实施为由处理器，如中央处理器、数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘 存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。
以上是对本申请的一些实施进行了具体说明，但本申请并不局限于上述实施方式，熟悉本领域的技术人员在不违背本申请范围的前提下还可作出种种的等同变形或替换，这些等同的变形或替换均包含在本申请权利要求所限定的范围内。

Claims (13)

  1. 一种代理方法，用于第一代理，包括：
    获取用户的交易数据，所述交易数据包括交易请求和私有数据；
    将所述私有数据进行本地存储，并向区块链平台发送所述交易请求，以使区块链平台根据所述交易请求完成交易；
    在完成交易后将所述私有数据发送至对端代理进行交易核验。
  2. 根据权利要求1所述的代理方法，其中，所述获取用户的交易数据前，还包括：
    根据所述私有数据生成摘要，并对所述私有数据进行加密，并对加密后的所述私有数据进行签名；
    根据所述摘要和所述签名生成所述交易请求。
  3. 根据权利要求1所述的代理方法，其中，所述在完成交易后将所述私有数据发送至对端代理进行交易核验，包括：
    向对端代理发送推送请求；
    接收对端代理根据所述推送请求发出的响应信息；
    根据所述响应信息向对端代理发送所述私有数据，以使对端代理根据所述私有数据进行交易核验。
  4. 根据权利要求3所述的代理方法，其中，所述根据所述响应信息向对端代理发送所述私有数据，包括：
    根据所述响应信息通过Gossip协议向对端代理发送所述私有数据。
  5. 根据权利要求1至4任一项所述的代理方法，其中，还包括:
    当所述私有数据的存储时间超过预设保存时间，删除所述私有数据。
  6. 根据权利要求1所述的代理方法，还包括：
    接收对端代理的同步请求，并根据所述同步请求返回所述私有数据的摘要列表，以使对端代理根据所述摘要列表与自身存储的所述私有数据进行对比，并当确定缺失私有数据，返回请求列表；
    根据所述请求列表向对端代理发送所述私有数据。
  7. 根据权利要求6所述的代理方法，其中，所述接收对端代理的同步请求，包括：
    定期执行接收对端代理的同步请求。
  8. 一种代理方法，用于第二代理，包括：
    获取对端代理发送的私有数据，所述私有数据保存于对端代理，且用于对由对端代理通过向区块链平台发送交易请求而进行的交易进行核验；
    对所述私有数据进行交易核验。
  9. 根据权利要求8所述的代理方法，其中，所述对所述私有数据进行交易核验，包括：
    对所述私有数据进行签名验证，以确认提供所述私有数据的用户；
    对所述私有数据进行解密，并将解密的所述私有数据生成对比摘要，以将所述对比摘要与对端代理的私有数据的摘要进行对比，确认所述私有数据是否有效。
  10. 根据权利要求8所述的代理方法，还包括：
    向对端代理发送同步请求；
    接收对端代理根据同步请求返回所述私有数据的摘要列表，并根据所述摘要列表与自 身存储的所述私有数据进行对比；
    当确定缺失私有数据，向对端代理返回请求列表，以使对端代理根据请求列表发送所述私有数据。
  11. 根据权利要求10所述的代理方法，其中，所述向对端代理发送同步请求，包括：
    定期执行向对端代理发送同步请求。
  12. 一种设备，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，其中，所述处理器执行所述计算机程序时实现如权利要求1至11中任意一项所述的代理方法。
  13. 一种计算机可读存储介质，存储有计算机可执行指令，其中，所述计算机可执行指令用于执行如权利要求1至11中任意一项所述的代理方法。
PCT/CN2021/102766 2020-06-28 2021-06-28 代理方法、设备及计算机可读存储介质 WO2022001960A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
AU2021300461A AU2021300461A1 (en) 2020-06-28 2021-06-28 Proxy method, device, and computer-readable storage medium
US18/003,393 US20230247106A1 (en) 2020-06-28 2021-06-28 Proxy method, device, and computer-readable storage medium
KR1020237002756A KR20230027284A (ko) 2020-06-28 2021-06-28 프록시 방법, 디바이스 및 컴퓨터 판독 가능한 저장 매체
JP2022581656A JP7488379B2 (ja) 2020-06-28 2021-06-28 プロキシ方法、装置及びコンピュータ可読記憶媒体
EP21832546.2A EP4174702A4 (en) 2020-06-28 2021-06-28 PROXY METHOD, APPARATUS AND COMPUTER READABLE STORAGE MEDIUM

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010599762.3 2020-06-28
CN202010599762.3A CN113849851A (zh) 2020-06-28 2020-06-28 代理方法、设备及计算机可读存储介质

Publications (1)

Publication Number Publication Date
WO2022001960A1 true WO2022001960A1 (zh) 2022-01-06

Family

ID=78972607

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/102766 WO2022001960A1 (zh) 2020-06-28 2021-06-28 代理方法、设备及计算机可读存储介质

Country Status (7)

Country Link
US (1) US20230247106A1 (zh)
EP (1) EP4174702A4 (zh)
JP (1) JP7488379B2 (zh)
KR (1) KR20230027284A (zh)
CN (1) CN113849851A (zh)
AU (1) AU2021300461A1 (zh)
WO (1) WO2022001960A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4344154A1 (en) * 2022-09-21 2024-03-27 Sandvine Corporation System and method for managing network traffic in a distributed environment

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108737374A (zh) * 2018-04-12 2018-11-02 三维通信股份有限公司 一种区块链中数据存储的隐私保护方法
CN109033426A (zh) * 2018-08-10 2018-12-18 杭州数澜科技有限公司 基于私有区块链网络的保存数据操作信息的方法及系统
CN109313753A (zh) * 2016-04-01 2019-02-05 摩根大通国家银行 用于在私有分布式账本中提供数据隐私的系统和方法
US20190349203A1 (en) * 2018-05-08 2019-11-14 Sap Se Mediated anonymity for permissioned, distributed-ledger networks
CN110502905A (zh) * 2019-07-10 2019-11-26 布比（北京）网络技术有限公司 一种隐私保护的分布式账本交易方法和系统
CN111294379A (zh) * 2018-12-10 2020-06-16 北京沃东天骏信息技术有限公司 区块链网络服务平台及其权限托管方法、存储介质

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100319061A1 (en) 2007-02-06 2010-12-16 Makoto Hatakeyama Personal information managing device, service providing device, program, personal information managing method, checking method and personal information checking system for falsification prevention of personal information and non repudiation of personal information circulation
JP6413792B2 (ja) 2015-01-22 2018-10-31 日本電気株式会社 ストレージシステム
EP3292484B1 (en) 2015-05-05 2021-07-07 Ping Identity Corporation Identity management service using a block chain
US10255342B2 (en) * 2017-04-12 2019-04-09 Vijay K. Madisetti Method and system for tuning blockchain scalability, decentralization, and security for fast and low-cost payment and transaction processing
GB201721021D0 (en) 2017-12-15 2018-01-31 Nchain Holdings Ltd Computer-implemented methods and systems
US10878429B2 (en) 2018-03-28 2020-12-29 Konstantinos Bakalis Systems and methods for using codes and images within a blockchain
CN113015989A (zh) 2018-06-08 2021-06-22 通信安全集团公司 区块链监督
US10853353B2 (en) * 2018-08-03 2020-12-01 American Express Travel Related Services Company, Inc. Blockchain-enabled datasets shared across different database systems
JP6566278B1 (ja) 2018-08-08 2019-08-28 株式会社ＤａｔａＳｉｇｎ パーソナルデータ管理システム
US11488158B2 (en) * 2018-09-05 2022-11-01 Atrium Separate Ip Holdings Number 4, Llc Blockchain architecture, system, method and device for automated cybersecurity and data privacy law compliance with proprietary off-chain storage mechanism
CN109377221B (zh) 2018-10-16 2021-09-03 杭州趣链科技有限公司 一种基于联盟区块链的隐私交易保护的方法
CN110059495B (zh) * 2018-12-14 2020-11-17 创新先进技术有限公司 数据共享方法、装置及系统、电子设备
US11106659B2 (en) 2019-04-28 2021-08-31 Advanced New Technologies Co., Ltd. Blockchain-based recording and querying operations

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109313753A (zh) * 2016-04-01 2019-02-05 摩根大通国家银行 用于在私有分布式账本中提供数据隐私的系统和方法
CN108737374A (zh) * 2018-04-12 2018-11-02 三维通信股份有限公司 一种区块链中数据存储的隐私保护方法
US20190349203A1 (en) * 2018-05-08 2019-11-14 Sap Se Mediated anonymity for permissioned, distributed-ledger networks
CN109033426A (zh) * 2018-08-10 2018-12-18 杭州数澜科技有限公司 基于私有区块链网络的保存数据操作信息的方法及系统
CN111294379A (zh) * 2018-12-10 2020-06-16 北京沃东天骏信息技术有限公司 区块链网络服务平台及其权限托管方法、存储介质
CN110502905A (zh) * 2019-07-10 2019-11-26 布比（北京）网络技术有限公司 一种隐私保护的分布式账本交易方法和系统

Non-Patent Citations (1)

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

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4344154A1 (en) * 2022-09-21 2024-03-27 Sandvine Corporation System and method for managing network traffic in a distributed environment

Also Published As

Publication number Publication date
US20230247106A1 (en) 2023-08-03
JP7488379B2 (ja) 2024-05-21
KR20230027284A (ko) 2023-02-27
AU2021300461A1 (en) 2023-03-09
EP4174702A1 (en) 2023-05-03
JP2023532356A (ja) 2023-07-27
CN113849851A (zh) 2021-12-28
EP4174702A4 (en) 2023-11-22

Similar Documents

Publication Publication Date Title
CN110912937B (zh) 一种基于区块链的数字存证平台和存证方法
KR102065315B1 (ko) 블록체인 기반 파일 보관 및 공유 시스템 및 방법
CN109829326B (zh) 基于区块链的跨域认证与公平审计去重云存储系统
CN112491847B (zh) 区块链一体机及其自动建链方法、装置
US9967334B2 (en) Computing device configuration and management using a secure decentralized transaction ledger
CN112686668B (zh) 联盟链跨链系统及方法
CN111541724B (zh) 区块链一体机及其节点自动加入方法、装置
CN111541552B (zh) 区块链一体机及其节点自动加入方法、装置
WO2023024742A1 (zh) 一种数据处理方法、装置、计算机设备及存储介质
CN109241754B (zh) 一种基于区块链的云文件重复数据删除方法
CN111740966B (zh) 一种基于区块链网络的数据处理方法及相关设备
US11582034B2 (en) Secure, decentralized, automated platform and multi-actors for object identity management through the use of a block chain technology
CN112804354B (zh) 跨链进行数据传输的方法、装置、计算机设备和存储介质
CN112702402A (zh) 基于区块链技术实现政务信息资源共享和交换的系统、方法、装置、处理器及其存储介质
CN111489256A (zh) 用于多链区块链系统中的跨链处理方法、设备及系统
CN108829539A (zh) 数据备份、数据恢复方法及设备
TW202007115A (zh) 基於跨鏈架構的身分識別管理系統及其方法
WO2020252611A1 (zh) 一种数据交互方法及相关设备
JP2023542681A (ja) ブロックチェーンの許可フレームワークへのデバイスアイデンティティの統合
US20210234675A1 (en) Secure, decentralized, automated platform and multi-actors for object identity management through the use of a block chain technology
CN114051031B (zh) 基于分布式身份的加密通讯方法、系统、设备及存储介质
WO2022001960A1 (zh) 代理方法、设备及计算机可读存储介质
CN114172730A (zh) 面向链上链下结合文件区块链的跨链方法及中间系统
CN110784318B (zh) 群密钥更新方法、装置、电子设备、存储介质及通信系统
CN111709053A (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: 21832546

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2022581656

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2021832546

Country of ref document: EP

Effective date: 20230124

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2021300461

Country of ref document: AU

Date of ref document: 20210628

Kind code of ref document: A