WO2021017636A1 - Procédé d'obtention d'actif numérique authentifié - Google Patents

Procédé d'obtention d'actif numérique authentifié Download PDF

Info

Publication number
WO2021017636A1
WO2021017636A1 PCT/CN2020/094362 CN2020094362W WO2021017636A1 WO 2021017636 A1 WO2021017636 A1 WO 2021017636A1 CN 2020094362 W CN2020094362 W CN 2020094362W WO 2021017636 A1 WO2021017636 A1 WO 2021017636A1
Authority
WO
WIPO (PCT)
Prior art keywords
digital asset
hash value
entity
client
registration platform
Prior art date
Application number
PCT/CN2020/094362
Other languages
English (en)
Chinese (zh)
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 南京瑞祥信息技术有限公司
Publication of WO2021017636A1 publication Critical patent/WO2021017636A1/fr

Links

Images

Classifications

    • 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
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
    • 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/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
    • 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
    • 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
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • 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/02—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
    • 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/3827—Use of message hashing
    • 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/389—Keeping log of transactions for guaranteeing non-repudiation of a 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
    • G06Q30/00—Commerce
    • G06Q30/018—Certifying business or products
    • 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
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G06Q30/0601—Electronic shopping [e-shopping]
    • G06Q30/0609—Buyer or seller confidence or verification
    • 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
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/10—Services
    • G06Q50/18—Legal services
    • 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
    • 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
    • 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
    • G06Q2220/00—Business processing using cryptography
    • G06Q2220/10—Usage protection of distributed data files
    • G06Q2220/18—Licensing
    • 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

  • the embodiments of the application relate to the technical field of digital assets, and in particular to a method for obtaining certified digital assets.
  • the digital asset certification platform also known as the right confirmation platform, is mainly aimed at confirming the rights of a large number of intellectual works or achievements for copyright registration. Its functions are mainly embodied in two aspects: first, to confirm the rights of the registered copyrights, trademarks or patents that have obtained patent certificates; second, to confirm the rights of a large number of unregistered intellectual works or achievements. For intellectual works or achievements that have been confirmed by the digital asset certification platform, they need to be managed by the corresponding platform (digital asset registration platform) in the way of registration.
  • the digital asset registration platform is not only used to store the confirmed digital asset data, It also provides data interfaces for other business systems, enabling other systems to use the data on the digital asset registration platform to complete corresponding data processing operations.
  • the digital asset registration platform 2 and various types of terminals 1 form a point-to-point connection through the Internet.
  • Two parties any buyer or seller who conduct digital asset transactions can use different terminals 1, and establish connections through client 11 (for example, as a seller) and client 12 (for example, as a buyer) installed on the terminal side to complete digital asset transactions.
  • client 11 for example, as a seller
  • client 12 for example, as a buyer
  • the transaction process of digital assets usually includes multiple links. For example, the two parties involved in the transaction must go through the digital asset entity and negotiation to ensure the smooth completion of the transaction. Before the inspection, the buyer must first obtain the real digital assets.
  • the process of obtaining the digital assets is: the buyer's client obtains the physical assets according to the information given by the seller, and further obtains all the information including the bibliographic items, and passes The entity part of the digital asset obtains the content of the specific digital asset, so as to continue the inspection link.
  • the buyer client 12 can obtain the entity through the seller client 11, that is, the entity is directly provided by the seller client, or the seller encrypts the entity and then provides the encrypted entity and public key together.
  • the problem with this approach is that the buyer client 12 cannot determine whether the acquired entity is the real entity corresponding to the certified digital asset; in addition, the buyer client 12 can also obtain the entity from the third-party server 3 that stores the digital asset entity. Server 3 may be attacked and data may be tampered with, and the authenticity of the digital asset entity cannot be guaranteed. Therefore, how to obtain a certified digital asset entity with a high degree of authenticity is an urgent problem to be solved by the current digital asset registration platform.
  • This application provides a method for obtaining certified digital assets to solve the problem of how to increase the feasibility of digital asset entities.
  • this application provides a method for obtaining certified digital assets, and the method includes:
  • the first client sends digital asset data to be confirmed to the second client; wherein the digital asset data to be confirmed is a data packet including an authentication code and a digital asset entity;
  • the second client sends the acquired digital asset data to be confirmed to the digital asset registration platform
  • the digital asset registration platform uses a digital signature algorithm to calculate the hash value A of the digital asset entity, and extracts the hash value B stored in the authentication summary corresponding to the authentication code in the digital asset registration platform, and compares the hash values A and hash value B;
  • the digital asset registration platform feeds back the comparison result to the second client;
  • the second client determines whether to obtain a real digital asset entity according to the comparison result.
  • this application provides a method for obtaining certified digital assets, the method including:
  • the first client sends the digital asset data to be confirmed to the digital asset registration platform; wherein the digital asset data to be confirmed is a data packet including an authentication code, a digital asset entity, and information about the second client;
  • the digital asset registration platform uses a digital signature algorithm to calculate the hash value A of the digital asset entity, and extracts the hash value B stored in the authentication summary corresponding to the authentication code in the digital asset registration platform, and compares the hash values A and hash value B;
  • the digital asset registration platform feeds back the comparison result and the digital asset entity to the second client;
  • the second client determines whether to obtain a real digital asset entity according to the comparison result.
  • this application provides a method for obtaining certified digital assets, the method including:
  • the first client sends digital asset data to be confirmed to the second client; wherein the digital asset data to be confirmed is a data packet including an authentication code and a digital asset entity;
  • the second client sends the acquired digital asset data to be confirmed to the digital asset registration platform
  • the digital asset registration platform sends a request to a third-party server to request the digital asset entity corresponding to the authentication code and the corresponding hash value A;
  • the third-party server obtains the digital asset entity stored by itself according to the request, uses the digital signature algorithm to calculate the hash value A of the digital asset entity; and sends the hash value A of the digital asset entity to the digital asset registration platform;
  • the digital asset registration platform uses a digital signature algorithm to calculate the hash value B of the digital asset entity obtained through the second client, and compares the hash value A and the hash value B;
  • the digital asset registration platform feeds back the comparison result to the second client;
  • the second client determines whether to obtain a real digital asset entity according to the comparison result.
  • this application provides a method for obtaining certified digital assets, the method including:
  • the first client sends digital asset data to be confirmed to the second client; wherein the digital asset data to be confirmed is a data packet including an authentication code and a digital asset entity;
  • the second client sends the acquired digital asset data to be confirmed to the digital asset registration platform
  • the digital asset registration platform sends a request to the public chain node or sub-chain node of the blockchain network to request the digital asset entity corresponding to the authentication code and the corresponding hash value A;
  • the public chain node or sub-chain node of the blockchain network obtains the digital asset entity stored in the blockchain network according to the request, and uses the digital signature algorithm to calculate the hash value A of the digital asset entity; and, the hash value of the digital asset entity The value A is sent to the digital asset registration platform;
  • the digital asset registration platform uses a digital signature algorithm to calculate the hash value B of the digital asset entity obtained through the second client, and compares the hash value A and the hash value B;
  • the digital asset registration platform feeds back the comparison result to the second client;
  • the second client determines whether to obtain a real digital asset entity according to the comparison result.
  • this application provides a method for obtaining certified digital assets, the method including:
  • the first client sends an authentication code to the second client
  • the second client sends the obtained authentication code to the digital asset registration platform
  • the digital asset registration platform sends a request to a third-party server to request the digital asset entity corresponding to the authentication code and the corresponding hash value A;
  • the third-party server obtains the digital asset entity stored by itself according to the request, uses the digital signature algorithm to calculate the hash value A of the digital asset entity; and sends the digital asset entity and the hash value A of the digital asset entity to the digital asset registration platform;
  • the digital asset registration platform extracts the hash value B stored in the authentication summary corresponding to the authentication code in the digital asset registration platform, and compares the hash value A and the hash value B;
  • the digital asset registration platform feeds back the comparison result and the digital asset entity to the second client;
  • the second client determines whether to obtain a real digital asset entity according to the comparison result.
  • this application provides a method for obtaining certified digital assets, the method including:
  • the first client sends an authentication code to the second client
  • the second client sends the obtained authentication code to the digital asset registration platform
  • the digital asset registration platform sends a request to the public chain node or sub-chain node of the blockchain network to request the digital asset entity corresponding to the authentication code and the corresponding hash value A;
  • the public chain node or child chain node of the blockchain network obtains the digital asset entity stored in the blockchain network according to the request, and uses the digital signature algorithm to calculate the hash value A of the digital asset entity; and, the digital asset entity and the digital asset The hash value A of the entity is sent to the digital asset registration platform;
  • the digital asset registration platform extracts the hash value B stored in the authentication summary corresponding to the authentication code in the digital asset registration platform, and compares the hash value A and the hash value B;
  • the digital asset registration platform feeds back the comparison result and the digital asset entity to the second client;
  • the second client determines whether to obtain a real digital asset entity according to the comparison result.
  • this application provides a method for obtaining certified digital assets, the method including:
  • the first client sends the authentication code and the second client information to the digital asset registration platform
  • the digital asset registration platform sends a request to a third-party server to request the digital asset entity corresponding to the authentication code and the corresponding hash value A;
  • the third-party server obtains the digital asset entity stored by itself according to the request, uses the digital signature algorithm to calculate the hash value A of the digital asset entity; and sends the digital asset entity and the hash value A of the digital asset entity to the digital asset registration platform;
  • the digital asset registration platform extracts the hash value B stored in the authentication summary corresponding to the authentication code in the digital asset registration platform, and compares the hash value A and the hash value B;
  • the digital asset registration platform feeds back the comparison result and the digital asset entity to the second client;
  • the second client determines whether to obtain a real digital asset entity according to the comparison result.
  • this application provides a method for obtaining certified digital assets, the method including:
  • the first client sends the authentication code and the second client information to the digital asset registration platform
  • the digital asset registration platform sends a request to the public chain node or sub-chain node of the blockchain network to request the digital asset entity corresponding to the authentication code and the corresponding hash value A;
  • the public chain node or child chain node of the blockchain network obtains the digital asset entity stored in the blockchain network according to the request, and uses the digital signature algorithm to calculate the hash value A of the digital asset entity; and, the digital asset entity and the digital asset The hash value A of the entity is sent to the digital asset registration platform;
  • the digital asset registration platform extracts the hash value B stored in the authentication summary corresponding to the authentication code in the digital asset registration platform, and compares the hash value A and the hash value B;
  • the digital asset registration platform feeds back the comparison result and the digital asset entity to the second client;
  • the second client determines whether to obtain a real digital asset entity according to the comparison result.
  • this application provides a method for obtaining certified digital assets, the method including:
  • the first client sends the authentication code and the second client information to the digital asset registration platform
  • the digital asset registration platform extracts the hash value B stored in the authentication abstract corresponding to the authentication code in the digital asset registration platform;
  • the digital asset registration platform sends the extracted hash value B to a third-party server
  • the third-party server obtains the digital asset entity stored by itself, uses the digital signature algorithm to calculate the hash value A of the digital asset entity, and compares the hash value A and the hash value B;
  • the third-party server feeds back the comparison result and the digital asset entity to the second client;
  • the second client determines whether to obtain a real digital asset entity according to the comparison result.
  • this application provides a method for obtaining certified digital assets, the method including:
  • the first client sends the authentication code and the second client information to the digital asset registration platform
  • the digital asset registration platform extracts the hash value B stored in the authentication abstract corresponding to the authentication code in the digital asset registration platform;
  • the digital asset registration platform sends the extracted hash value B to the public chain node or the child chain node of the blockchain network;
  • the public chain node or sub-chain node of the blockchain network obtains the digital asset entity stored in the blockchain network, uses a digital signature algorithm to calculate the hash value A of the digital asset entity, and compares the hash value A and the hash value B;
  • the public chain node or sub-chain node of the blockchain network feeds back the comparison result and the digital asset entity to the second client;
  • the second client determines whether to obtain a real digital asset entity according to the comparison result.
  • This application provides a method for obtaining certified digital assets.
  • the buyer or seller of the transaction sends the authentication code of the digital asset data to be confirmed or the digital asset entity to the digital asset registration platform, and the digital asset registration platform uses the obtained data to calculate the hash value of the digital asset entity, and Compare the hash value in the authentication summary corresponding to the authentication code in the platform, obtain the comparison result and give feedback to the buyer's client, so that the buyer can determine whether it has obtained a real digital asset entity, and when it is determined to obtain a real digital asset
  • the source of the digital asset entity can be a seller's client, a third-party server, or a public chain node or sub-chain node of the blockchain network, etc.
  • the method and system provided in this application can ensure that the buyer obtains a certified digital asset entity with a high degree of authenticity, which improves the credibility of both parties in the transaction, and at the same time has a higher processing efficiency.
  • Figure 1 is an application scenario diagram of the digital asset registration platform
  • Figure 2 is a flowchart of the first embodiment of the method for obtaining certified digital assets provided by this application;
  • FIG. 3 is a flowchart of the second embodiment of the method for obtaining certified digital assets provided by this application;
  • Figure 4 is a flowchart of the third and fifth embodiments of the method for obtaining certified digital assets provided by this application;
  • Figure 5 is a flowchart of the fourth and sixth embodiments of the method for obtaining certified digital assets provided by this application;
  • FIG. 6 is a flowchart of a seventh embodiment of the method for obtaining certified digital assets provided by this application.
  • FIG. 7 is a flowchart of the eighth embodiment of the method for obtaining certified digital assets provided by this application.
  • FIG. 8 is a flowchart of a ninth embodiment of the method for obtaining certified digital assets provided by this application.
  • Fig. 9 is a flowchart of a tenth embodiment of a method for obtaining a certified digital asset provided by this application.
  • the embodiments of this application are applied in the scenario described in FIG. 1.
  • the first client 11 generally refers to any seller who conducts digital asset transactions
  • the second client 12 generally refers to any buyer who conducts digital asset transactions.
  • the correspondence between buyers and sellers is not limited to a one-to-one relationship, that is, multiple first clients (multiple sellers) may send digital asset data to the same second client (buyer), or it may be A first client (seller) sends different parts of digital asset data to multiple different second clients (multiple buyers).
  • the digital asset data to be confirmed sent between the clients can be the sum data packet of the authentication code and the digital asset entity, or only the authentication code, where the digital asset data packet is an encrypted data packet .
  • the method also includes the process of the client to package the data and parse the data packet, and the specific process is not limited in this embodiment.
  • the digital signature algorithm used in all embodiments of this application is the same as the algorithm used in authentication.
  • the scenario described in FIG. 1 may also include other entities, such as a blockchain network.
  • the first client After negotiation before the transaction, the first client sends digital asset data to be confirmed to the second client; wherein, the digital asset data to be confirmed is a data packet including an authentication code and a digital asset entity; in this implementation
  • the data packet can be an encrypted ciphertext data packet plus a public key.
  • the public key needs to be sent at the same time as the data packet, so as to decrypt the data packet with the public key. In this step, the authenticity of the certified digital asset has not been confirmed.
  • the second client sends the acquired digital asset data to be confirmed to the digital asset registration platform
  • the second client after the second client receives the digital asset data to be confirmed sent by the first client, if it needs to check the authenticity of the data in the data packet, it can perform operations on the received data packet (for example, Analysis), extract the authentication code or entity part, and then send the authentication code and entity part to the digital asset registration platform; if there is no need to view the data temporarily, it can directly forward the data packet to the digital asset registration platform, and the platform will The data packet performs further operations (such as parsing and subsequent calculation, etc.); at the same time, since the second client temporarily saves the content of the data packet (physical part) at this time, if the subsequent authentication result is a real entity, it can be determined to be saved The data package is real data, and the user can immediately obtain the real physical part directly from the second client.
  • operations on the received data packet for example, Analysis
  • extract the authentication code or entity part if there is no need to view the data temporarily, it can directly forward the data packet to the digital asset registration platform, and the platform will The data packet performs further operations (
  • the digital asset registration platform uses a digital signature algorithm to calculate the hash value A of the digital asset entity, and extracts the hash value B stored in the authentication abstract corresponding to the authentication code in the digital asset registration platform, and compares it. Hope value A and hash value B;
  • step S103 the digital signature algorithm is used to calculate the hash value A of the authentication code or the entity part in the data packet, and then the digital asset registration platform queries the corresponding authentication summary stored in the platform according to the received authentication code , And extract the hash value B stored in the authentication digest, compare the hash value A and the hash value B, specifically to compare whether the two are exactly the same or have a preset specific relationship, for example, if the hash value A If it is exactly the same as the hash value B, the comparison result obtained is that the authentication is successful, and the entity part corresponding to the authentication code is true and valid. Otherwise, if the authentication fails, the entity part corresponding to the authentication code is false.
  • the authentication summary maintained by the digital asset registration platform is the original data generated during the digital asset authentication process and has authenticity. Therefore, through the comparison operation in this step, the authenticity of the digital asset entity can be known.
  • the comparison result can be a piece of feedback information to notify the second client that the digital asset data to be confirmed received is true or false; in addition, the comparison result can also contain other content, for example, The certification documents attached to the digital asset registration platform-such as an electronic certification certificate, which records the certification time, the comparison result of the hash value A/B, etc.
  • S105 The second client terminal determines whether to obtain a real digital asset entity according to the comparison result.
  • the second client When the second client receives the comparison result, if the comparison result shows the real digital asset entity, the real digital asset entity can be parsed, encrypted, saved, and downloaded on the second client; if the comparison result is If the digital asset entity is displayed as a fake, the second client can delete or return the data packet containing the fake digital asset entity to the first client, and feedback the confirmation failure information to the first client, thereby terminating the transaction To continue.
  • the calculation of the hash value can be based on the digital asset entity, or can be based on the data packet or digital asset that includes the digital asset entity, depending on the system settings. Therefore, one of them will be used as an example in the following examples.
  • the second client needs to first obtain the digital asset data to be confirmed from the first client, and then transfer the data to the digital asset registration platform for processing.
  • the first client can also use the The confirmed digital asset data is directly sent to the digital asset registration platform, so that the second client can obtain the real certified digital asset.
  • Fig. 3 is a flowchart of a second embodiment of the method for obtaining a certified digital asset provided by this application.
  • the first client sends the digital asset data to be confirmed to the digital asset registration platform; wherein the digital asset data to be confirmed is a data packet including the authentication code, the digital asset entity, and the second client information; in this implementation
  • the data packet can be in the form of an encrypted ciphertext data packet + public key.
  • the second client information refers to information including the identity and network address of the second client (buyer), so that the verification result of the data asset entity by the digital asset registration platform is fed back to the second client.
  • the digital asset registration platform uses a digital signature algorithm to calculate the hash value A of the digital asset entity sent by the first client, and extracts the hash value A stored in the authentication abstract corresponding to the authentication code in the digital asset registration platform. Hope value B, compare hash value A and hash value B;
  • step S202 the digital signature algorithm is first used to calculate the hash value A of the digital asset entity part in the data packet, and then the digital asset registration platform queries the corresponding authentication summary stored in the platform according to the received authentication code. And extract the hash value B stored in the authentication digest, compare the hash value A and the hash value B, specifically to compare whether the two are exactly the same or have a preset specific relationship, for example, if the hash value A If it is exactly the same as the hash value B, the comparison result obtained is that the confirmation is successful and the entity part corresponding to the authentication code is true and valid. Otherwise, if the confirmation fails, the entity part corresponding to the authentication code is false.
  • S203 The digital asset registration platform feeds back the comparison result and the digital asset entity to the second client;
  • the comparison result can also contain other content, for example, the confirmation document attached by the digital asset registration platform-such as an electronic certification certificate, which records Authentication time, hash value A/B comparison result, etc.
  • step S203 is an embodiment for confirming success. If the confirmation is unsuccessful, there is another embodiment.
  • step S203 can be replaced with:
  • the digital asset registration platform feeds back the comparison result to the second client; at this time, it only needs to feed back the result that the digital asset entity corresponding to the authentication code is not a real entity to the second client, prompting for other operations without feedback The obtained digital asset entity.
  • the second client When the second client receives the comparison result, if the comparison result shows the real digital asset entity, the real digital asset entity can be parsed, encrypted, saved, and downloaded on the second client; if the comparison result is If the digital asset entity is displayed as a fake, the second client can feed back the confirmation failure information to the first client, thereby terminating the transaction.
  • the first embodiment uses the digital asset registration platform to complete the hash value calculation and comparison process.
  • the digital asset registration platform and the third-party server can send requests For obtaining the calculated hash value, refer to FIG. 4, which is a flowchart of the third and fifth embodiments of the method for obtaining a certified digital asset provided by this application.
  • the first client sends digital asset data to be confirmed to the second client; where the digital asset data to be confirmed is a data packet including an authentication code and a digital asset entity; in this embodiment, the data packet may be It is an encrypted ciphertext data packet + public key.
  • the first client sends the data packet to the second client, if you want the second client to view the data contained in the data packet, you need to send The public key is sent along with the data packet.
  • S302 The second client sends the acquired digital asset data to be confirmed to the digital asset registration platform
  • the second client after the second client receives the digital asset data to be confirmed sent by the first client, if it needs to check the authenticity of the data in the data packet, it can perform operations on the received data packet (for example, Analysis), extract the authentication code or entity part, and then send the authentication code and entity part to the digital asset registration platform; if there is no need to view the data temporarily, it can directly forward the data packet to the digital asset registration platform, and the platform will The data packet performs further operations (such as parsing and subsequent calculation, etc.); at the same time, since the second client temporarily saves the content of the data packet (physical part) at this time, if the subsequent authentication result is a real entity, it can be determined to be saved The data package is real data, and the user can immediately obtain the real physical part directly from the second client.
  • operations on the received data packet for example, Analysis
  • extract the authentication code or entity part if there is no need to view the data temporarily, it can directly forward the data packet to the digital asset registration platform, and the platform will The data packet performs further operations (
  • the digital asset registration platform sends a request to a third-party server to request the digital asset entity corresponding to the authentication code and the corresponding hash value A;
  • the third-party server obtains the digital asset entity stored by itself according to the request, and calculates the hash value A of the digital asset entity by using a digital signature algorithm;
  • the third-party server sends the hash value A of the digital asset entity to the digital asset registration platform;
  • the digital asset registration platform sends a request based on the authentication code.
  • the third-party server finds the digital asset entity corresponding to the authentication code in the request according to the request, and uses the digital signature algorithm to calculate the hash value A of the digital asset entity.
  • the hash value A is sent to the digital asset registration platform;
  • the digital asset registration platform uses a digital signature algorithm to calculate the hash value B of the digital asset entity obtained through the second client, and compares the hash value A and the hash value B;
  • the digital asset registration platform calculates the hash value B according to the received digital asset entity, and compares the hash value A and the hash value B, specifically to compare whether the two are exactly the same or have a preset specific relationship, for example If the hash value A and the hash value B are exactly the same, the comparison result is that the confirmation is successful and the entity part corresponding to the authentication code is true and valid. Otherwise, the confirmation fails and the entity part corresponding to the authentication code is false.
  • the comparison result can be a piece of feedback information to inform the second client that the digital asset data to be confirmed is true or false; in addition, the comparison result can also contain other content, for example, the digital asset
  • the second client When the second client receives the comparison result, if the comparison result shows the real digital asset entity, the real digital asset entity can be parsed, encrypted, saved, and downloaded on the second client; if the comparison result is If the digital asset entity is displayed as a fake, the second client can delete or return the data packet containing the fake digital asset entity to the first client, and feedback the confirmation failure information to the first client, thereby terminating the transaction To continue.
  • the digital asset entity in the system that executes the method, can be obtained through a third-party server, and can also be obtained by establishing a connection between the digital asset registration platform and the public chain node or sub-chain node of the blockchain network.
  • the public chain node or the sub-chain node can play the same function as the third-party server. See FIG. 5, which is a flowchart of the fourth and sixth embodiments of the method for obtaining certified digital assets provided by this application.
  • the first client sends digital asset data to be confirmed to the second client; wherein the digital asset data to be confirmed is a data packet including an authentication code and a digital asset entity;
  • S402 The second client sends the acquired digital asset data to be confirmed to the digital asset registration platform;
  • the digital asset registration platform sends a request to the public chain node or sub-chain node of the blockchain network to request the digital asset entity corresponding to the authentication code and the corresponding hash value A;
  • the public chain node or sub-chain node of the blockchain network obtains the digital asset entity stored in the blockchain network according to the request, and calculates the hash value A of the digital asset entity by using a digital signature algorithm;
  • S405 The public chain node or sub-chain node of the blockchain network sends the hash value A of the digital asset entity to the digital asset registration platform;
  • the digital asset registration platform uses a digital signature algorithm to calculate the hash value B of the digital asset entity obtained through the second client, and compares the hash value A and the hash value B;
  • Fig. 4 is a flowchart of the third and fifth embodiments of the method for obtaining a certified digital asset provided by this application.
  • S501 The first client sends an authentication code to the second client;
  • S502 The second client sends the obtained authentication code to the digital asset registration platform
  • the digital asset registration platform sends a request to a third-party server to request the digital asset entity corresponding to the authentication code and the corresponding hash value A;
  • the third-party server obtains the digital asset entity stored by itself according to the request, and calculates the hash value A of the digital asset entity by using a digital signature algorithm;
  • the third-party server sends the digital asset entity and the hash value A of the digital asset entity to the digital asset registration platform;
  • the digital asset registration platform extracts the hash value B stored in the authentication summary corresponding to the authentication code in the digital asset registration platform, and compares the hash value A and the hash value B;
  • step S507 is an embodiment for confirming success. If the confirmation is unsuccessful, there is another embodiment. In this case, step S507 can be replaced with:
  • the digital asset registration platform feeds back the comparison result to the second client; at this time, it only needs to feed back the result that the digital asset entity corresponding to the authentication code is not a real entity to the second client, prompting for other operations without feedback The obtained digital asset entity.
  • S601 The first client sends an authentication code to the second client;
  • S602 The second client sends the obtained authentication code to the digital asset registration platform
  • the digital asset registration platform sends a request to the public chain node or sub-chain node of the blockchain network to request the digital asset entity corresponding to the authentication code and the corresponding hash value A;
  • the public chain node or sub-chain node of the blockchain network obtains the digital asset entity stored in the blockchain network according to the request, and calculates the hash value A of the digital asset entity by using a digital signature algorithm;
  • S605 The public chain node or sub-chain node of the blockchain network sends the digital asset entity and the hash value A of the digital asset entity to the digital asset registration platform;
  • the digital asset registration platform extracts the hash value B stored in the authentication summary corresponding to the authentication code in the digital asset registration platform, and compares the hash value A and the hash value B;
  • step S607 is an embodiment for confirming success. If the confirmation is unsuccessful, there is another embodiment. In this case, step S607 can be replaced with:
  • the digital asset registration platform feeds back the comparison result to the second client; at this time, it only needs to feed back the result that the digital asset entity corresponding to the authentication code is not a real entity to the second client, prompting for other operations without feedback The obtained digital asset entity.
  • the difference from the fifth embodiment is that the digital asset data to be confirmed in the first client can be directly sent to the digital asset registration platform. See Figure 6, which is the seventh implementation of the method for obtaining certified digital assets provided by this application. Example flowchart.
  • S701 The first client sends the authentication code and the second client information to the digital asset registration platform;
  • the digital asset registration platform sends a request to a third-party server to request the digital asset entity corresponding to the authentication code and the corresponding hash value A;
  • the third-party server obtains the digital asset entity stored by itself according to the request, and calculates the hash value A of the digital asset entity by using a digital signature algorithm;
  • S704 Send the digital asset entity and the hash value A of the digital asset entity to the digital asset registration platform;
  • the digital asset registration platform extracts the hash value B stored in the authentication summary corresponding to the authentication code in the digital asset registration platform, and compares the hash value A and the hash value B;
  • S706 The digital asset registration platform feeds back the comparison result and the digital asset entity to the second client;
  • step S706 is an embodiment for confirming success. If the confirmation is unsuccessful, there is another embodiment. In this case, step S706 can be replaced with:
  • the digital asset registration platform feeds back the comparison result to the second client; at this time, it only needs to feed back the result that the digital asset entity corresponding to the authentication code is not a real entity to the second client, prompting for other operations without feedback The obtained digital asset entity.
  • Fig. 7 is a flowchart of the eighth embodiment of the method for obtaining a certified digital asset provided by this application.
  • S801 The first client sends the authentication code and the second client information to the digital asset registration platform;
  • the digital asset registration platform sends a request to the public chain node or sub-chain node of the blockchain network to request the digital asset entity corresponding to the authentication code and the corresponding hash value A;
  • the public chain node or sub-chain node of the blockchain network obtains the digital asset entity stored in the blockchain network according to the request, and calculates the hash value A of the digital asset entity by using a digital signature algorithm;
  • S804 Send the digital asset entity and the hash value A of the digital asset entity to the digital asset registration platform;
  • the digital asset registration platform extracts the hash value B stored in the authentication summary corresponding to the authentication code in the digital asset registration platform, and compares the hash value A and the hash value B;
  • step S806 is an embodiment for confirming success. If the confirmation is unsuccessful, there is another embodiment. At this time, step S806 can be replaced with:
  • the digital asset registration platform feeds back the comparison result to the second client; at this time, it only needs to feed back the result that the digital asset entity corresponding to the authentication code is not a real entity to the second client, prompting for other operations without feedback The obtained digital asset entity.
  • Embodiment 5 The difference from Embodiment 5 is that the process of comparing hash values can be undertaken by a third-party server, and when the third-party server obtains the comparison result, the comparison result and the digital asset entity can be directly fed back to the second client. This reduces the amount of calculation on the digital asset registration platform and increases the processing efficiency of the system.
  • FIG. 8 which is a flowchart of a ninth embodiment of a method for obtaining a certified digital asset provided by this application.
  • the first client sends the authentication code and the second client information to the digital asset registration platform;
  • the digital asset registration platform extracts the hash value B stored in the authentication abstract corresponding to the authentication code in the digital asset registration platform;
  • the digital asset registration platform sends the extracted hash value B to a third-party server;
  • the third-party server obtains the digital asset entity stored by itself, uses a digital signature algorithm to calculate the hash value A of the digital asset entity, and compares the hash value A with the hash value B;
  • S905 The third-party server feeds back the comparison result and the digital asset entity to the second client;
  • step S905 is an embodiment for confirming success. If the confirmation is unsuccessful, there is another embodiment. In this case, step S905 can be replaced with:
  • the digital asset registration platform feeds back the comparison result to the second client; at this time, it only needs to feed back the result that the digital asset entity corresponding to the authentication code is not a real entity to the second client, prompting for other operations without feedback The obtained digital asset entity.
  • the first client sends the authentication code and the second client information to the digital asset registration platform;
  • the digital asset registration platform extracts the hash value B stored in the authentication abstract corresponding to the authentication code in the digital asset registration platform;
  • the digital asset registration platform sends the extracted hash value B to the public chain node or child chain node of the blockchain network;
  • the public chain node or sub-chain node of the blockchain network obtains the digital asset entity stored in the blockchain network, uses a digital signature algorithm to calculate the hash value A of the digital asset entity, and compares the hash value A and the hash value B;
  • S1005 The public chain node or sub-chain node of the blockchain network feeds back the comparison result and the digital asset entity to the second client;
  • step S1005 is an embodiment for confirming success. If the confirmation is not successful, there is another embodiment. At this time, step S1005 can be replaced with:
  • the digital asset registration platform feeds back the comparison result to the second client; at this time, it only needs to feed back the result that the digital asset entity corresponding to the authentication code is not a real entity to the second client, prompting for other operations without feedback The obtained digital asset entity.
  • This application provides a method for obtaining certified digital assets.
  • the buyer or seller of the transaction sends the authentication code of the digital asset data to be confirmed or the digital asset entity to the digital asset registration platform, and the digital asset registration platform uses the obtained data to calculate the hash value of the digital asset entity, and Compare the hash value in the authentication summary corresponding to the authentication code in the platform, obtain the comparison result and give feedback to the buyer's client, so that the buyer can determine whether it has obtained a real digital asset entity, and when it is determined to obtain a real digital asset
  • the source of the digital asset entity can be a seller's client, a third-party server, or a public chain node or sub-chain node of the blockchain network, etc.
  • the method and system provided in this application can ensure that the buyer obtains a certified digital asset entity with a high degree of authenticity, which improves the credibility of both parties in the transaction, and at the same time has a higher processing efficiency.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • Accounting & Taxation (AREA)
  • General Business, Economics & Management (AREA)
  • Finance (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Software Systems (AREA)
  • Human Resources & Organizations (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Development Economics (AREA)
  • Tourism & Hospitality (AREA)
  • Technology Law (AREA)
  • Computer Hardware Design (AREA)
  • General Engineering & Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Operations Research (AREA)
  • Multimedia (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Data Mining & Analysis (AREA)
  • Bioethics (AREA)
  • Primary Health Care (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Storage Device Security (AREA)

Abstract

L'invention concerne un procédé d'obtention d'actif numérique authentifié. Dans une application réelle, un acheteur ou un vendeur envoie, dans le cadre d'une transaction, un code d'authentification ou une entité d'actif numérique de données d'actifs numériques à confirmer à une plate-forme d'enregistrement d'actifs numériques, et ladite plate-forme utilise les données obtenues pour calculer une valeur de hachage de l'entité d'actif numérique, compare ladite valeur à une valeur de hachage contenue dans un résumé d'authentification correspondant au code d'authentification sur la plateforme, et obtient un résultat de comparaison qu'elle renvoie au client de l'acheteur, ce qui permet à l'acheteur de déterminer s'il a obtenu une entité d'actif numérique réel. De plus, lorsqu'il est déterminé qu'une entité d'actif numérique réel est obtenue, la source de l'entité d'actif numérique peut être le client du vendeur, un serveur tiers, un noeud de chaîne publique ou un noeud de sous-chaîne d'un réseau de chaîne de blocs, ou analogue. Le procédé selon l'invention permet à l'acheteur de s'assurer qu'il obtient une entité d'actif numérique présentant un degré élevé d'authenticité, ce qui améliore la crédibilité des deux parties à la transaction, tout en conférant une efficacité de traitement supérieure.
PCT/CN2020/094362 2019-07-26 2020-06-04 Procédé d'obtention d'actif numérique authentifié WO2021017636A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910684851.5A CN112308711A (zh) 2019-07-26 2019-07-26 一种获得认证数字资产的方法
CN201910684851.5 2019-07-26

Publications (1)

Publication Number Publication Date
WO2021017636A1 true WO2021017636A1 (fr) 2021-02-04

Family

ID=74198348

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/094362 WO2021017636A1 (fr) 2019-07-26 2020-06-04 Procédé d'obtention d'actif numérique authentifié

Country Status (3)

Country Link
CN (1) CN112308711A (fr)
FR (1) FR3099257A1 (fr)
WO (1) WO2021017636A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113239052A (zh) * 2021-07-13 2021-08-10 广东卓启云链科技有限公司 一种联盟链分组方法、装置、设备和介质
CN116051278A (zh) * 2022-12-01 2023-05-02 北京中科深智科技有限公司 一种基于区块链数字人捏造和鉴权使用与交易的方法

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107395358A (zh) * 2017-06-30 2017-11-24 上海策赢网络科技有限公司 信息请求及提供方法和装置、存储介质和设备
CN107395574A (zh) * 2017-06-30 2017-11-24 上海策赢网络科技有限公司 信息标识、信息请求及提供方法和装置、存储介质和设备
CN107871063A (zh) * 2017-11-16 2018-04-03 王磊 防篡改的录音录像数字签名方法、装置及存储介质
US20180219685A1 (en) * 2017-01-30 2018-08-02 Factom Validating Documents via Blockchain
CN109101577A (zh) * 2018-07-19 2018-12-28 清华大学 一种数据流通方法、装置及系统

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10795977B2 (en) * 2017-08-24 2020-10-06 Oracle International Corporation Digital asset traceability and assurance using a distributed ledger

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180219685A1 (en) * 2017-01-30 2018-08-02 Factom Validating Documents via Blockchain
CN107395358A (zh) * 2017-06-30 2017-11-24 上海策赢网络科技有限公司 信息请求及提供方法和装置、存储介质和设备
CN107395574A (zh) * 2017-06-30 2017-11-24 上海策赢网络科技有限公司 信息标识、信息请求及提供方法和装置、存储介质和设备
CN107871063A (zh) * 2017-11-16 2018-04-03 王磊 防篡改的录音录像数字签名方法、装置及存储介质
CN109101577A (zh) * 2018-07-19 2018-12-28 清华大学 一种数据流通方法、装置及系统

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113239052A (zh) * 2021-07-13 2021-08-10 广东卓启云链科技有限公司 一种联盟链分组方法、装置、设备和介质
CN116051278A (zh) * 2022-12-01 2023-05-02 北京中科深智科技有限公司 一种基于区块链数字人捏造和鉴权使用与交易的方法

Also Published As

Publication number Publication date
CN112308711A (zh) 2021-02-02
FR3099257A1 (fr) 2021-01-29

Similar Documents

Publication Publication Date Title
CN109845220B (zh) 用于提供区块链参与者身份绑定的方法和装置
JP7228977B2 (ja) 情報処理装置及び認可システムと検証方法
US7051204B2 (en) Methods and system for providing a public key fingerprint list in a PK system
KR100734737B1 (ko) 조건부 전자 서명의 생성 방법, 조건부 전자 서명의 검증 방법, 데이터 처리 장치 및 컴퓨터 판독 가능 기록 매체
TW202040391A (zh) 在區塊鏈網路上實施轉移之電腦實施系統及方法
CN111144881A (zh) 对资产转移数据的选择性访问
WO2015072203A1 (fr) Système de distribution d'informations
CN111125781B (zh) 一种文件签名方法、装置和文件签名验证方法、装置
CN108769010B (zh) 节点受邀注册的方法和装置
JP2018093434A (ja) トランザクション管理方法、トランザクション管理プログラム及びトランザクション管理装置
CN107528877B (zh) 基于区块链结构的安全性电子文件处理系统及方法
WO2021017636A1 (fr) Procédé d'obtention d'actif numérique authentifié
KR101253683B1 (ko) 연쇄 해시에 의한 전자서명 시스템 및 방법
JP2023532211A (ja) ブロックチェーン上の合意
TW202231018A (zh) 識別阻斷服務攻擊之技術
WO2021017637A1 (fr) Procédé de vérification de l'authenticité de ressources numériques authentifiées
WO2023035477A1 (fr) Procédé basé sur une chaîne de blocs destiné à la validation de documents
CN113746916B (zh) 基于区块链的第三方服务提供方法、系统及相关节点
KR102190236B1 (ko) 블록체인을 이용한 전자문서의 소유권 이전 및 검증 방법, 그리고 시스템
CN111552950B (zh) 一种软件授权方法、装置及计算机可读存储介质
CN115982247B (zh) 基于区块链的账户信息查询方法和装置、设备和介质
CN115136560A (zh) 分层网络
GB2598301A (en) Alert account
CN115412378B (zh) 隐私数据及金融隐私数据相关服务的可信认证方法及装置
EP4388440A1 (fr) Coordination de transfert de données pair à pair à l'aide d'une chaîne de blocs

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: 20846828

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20846828

Country of ref document: EP

Kind code of ref document: A1