CN111193597A - Transmission method, device, equipment and system capable of verifying statement - Google Patents
Transmission method, device, equipment and system capable of verifying statement Download PDFInfo
- Publication number
- CN111193597A CN111193597A CN202010277167.8A CN202010277167A CN111193597A CN 111193597 A CN111193597 A CN 111193597A CN 202010277167 A CN202010277167 A CN 202010277167A CN 111193597 A CN111193597 A CN 111193597A
- Authority
- CN
- China
- Prior art keywords
- verifiable
- account
- verifiable statement
- statement
- digital identity
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- 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
Abstract
The embodiment of the specification discloses a transmission method, a device, equipment and a system of verifiable claims. The scheme comprises the following steps: obtaining a request for transmission of a verifiable claim; and sending the verifiable statement of the transmission requested by the request to a corresponding target block chain system according to the information contained in the request.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method, an apparatus, a device, and a system for transmitting a verifiable statement.
Background
Initially, digital identity authentication was centralized. The essence of a centralized identity system is that a central centralized authority holds identity data. The authentication, authorization, etc. processes performed around the data are all determined by a centralized authority. The digital identity is not controlled by the user himself. On the other hand, different centralized websites have a set of identity systems, so that a user needs to register an account again at each website. The identity systems (and the data corresponding to the accounts) of different websites are not intercommunicated.
In summary, the main problems of centralized identity include at least the following two problems, namely that the user cannot really own the identity of the user and the identities cannot be intercommunicated.
In order to solve the above problems, a technical concept of distributed Digital Identity (DID) is proposed.
Distributed digital identity, as the name implies, is a kind of digitized identity credential implemented based on a distributed system. Distributed digital identity technology is typically implemented based on a blockchain system. The basic elements forming the distributed digital identity at least comprise a distributed digital identity and a distributed digital identity document.
The distributed digital identity document does not include content related to the personal real information of the user (such as the real name, address, mobile phone number and the like of the user). Therefore, when the distributed digital authentication is adopted for authentication, a Verifiable statement (VC) is also needed.
The verifiable statement here is understood to be a digital certificate issued by an authority with relevant qualifications based on a request of a user. A distributed digital identity may have a corresponding plurality of verifiable claims. For example, a verifiable claim attesting to the distributed digital identity being in position at a company, a verifiable claim attesting to the academic story of the distributed digital identity being doctor's graduation, a verifiable claim attesting to the distributed digital identity being a proprietor of a cell, and so forth. It can be seen that there is little upper limit to the number of verifiable claims that a distributed digital identity can correspond to. Therefore, management of verifiable claims is becoming an urgent issue to be solved.
Disclosure of Invention
In view of this, the embodiments of the present application provide a method for transmitting a verifiable statement, which can record a usage process of the verifiable statement.
In order to solve the above technical problem, the embodiments of the present specification are implemented as follows:
an embodiment of the present specification provides a method for transmitting a verifiable statement, including:
obtaining a request to transmit a verifiable claim; the request comprises at least a first identification of the verifiable statement and a second identification of a target blockchain system;
obtaining a verifiable statement corresponding to the first identification;
sending the verifiable claims to the target blockchain system;
the authenticatable claimant account has usage rights of the first data repository and the authenticatable claimant account has usage rights of a second data repository.
An apparatus for transmitting a verifiable statement provided by an embodiment of this specification includes:
a transmission request acquisition module for acquiring a request for transmitting the verifiable statement; the request comprises at least a first identification of the verifiable statement and a second identification of a target blockchain system;
the verifiable statement acquisition module is used for acquiring the verifiable statement corresponding to the first identifier;
a verifiable assertion sending module for sending the verifiable assertion to the target blockchain system;
the authenticatable claimant account has usage rights of the first data repository and the authenticatable claimant account has usage rights of a second data repository.
An embodiment of this specification provides a transmission device capable of verifying a statement, including:
at least one processor; and the number of the first and second groups,
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores instructions executable by the at least one processor to enable the at least one processor to:
obtaining a request to transmit a verifiable claim; the request comprises at least a first identification of the verifiable statement and a second identification of a target blockchain system;
obtaining a verifiable statement corresponding to the first identification;
sending the verifiable claims to the target blockchain system;
the authenticatable claimant account has usage rights of the first data repository and the authenticatable claimant account has usage rights of a second data repository.
An embodiment of this specification provides a system for transmitting verifiable claims, including:
a first data warehouse, a second data warehouse, and at least one target blockchain system;
the first data repository to obtain a request to transmit a verifiable claim; the request comprises at least a first identification of the verifiable statement and a second identification of a target blockchain system; obtaining a verifiable statement corresponding to the first identification; sending the verifiable claims to the target blockchain system;
the second data repository to obtain the verifiable claims from the target blockchain system;
the authenticatable claimant account has usage rights of the first data repository and the authenticatable claimant account has usage rights of the second data repository.
The embodiment of the specification adopts at least one technical scheme which can achieve the following beneficial effects:
the verifiable statement is sent from the holding device to the verifying device through the block chain, so that the transmission process of the verifiable statement is recorded by the block chain system and can be traced. And because the data on the blockchain is not easy to be tampered, the record of the transmission or use process of the verifiable statement also has high credibility.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
FIG. 1 is a diagram illustrating an application context of a transmission method of a verifiable claim in an embodiment of the present specification;
fig. 2 is a flowchart illustrating a method for transmitting a verifiable statement according to an embodiment of the present disclosure;
fig. 3 is a schematic architecture diagram of a transmission system capable of verifying a claim according to an embodiment of the present disclosure;
fig. 4 is a flowchart illustrating another method for transmitting a verifiable claim according to an embodiment of the present disclosure;
fig. 5 is a schematic structural diagram of a transmission apparatus corresponding to one verifiable statement in fig. 2 according to an embodiment of the present disclosure;
fig. 6 is a schematic structural diagram of a transmission device corresponding to one verifiable assertion in fig. 2, provided in an embodiment of this specification.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail and completely with reference to the following specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The technical solutions provided by the embodiments of the present application are described in detail below with reference to the accompanying drawings.
Fig. 1 is a schematic diagram of an application context of a transmission method of a verifiable statement in an embodiment of the present specification. As shown in fig. 1, the client 101 may be a mobile terminal such as a mobile phone, or may be a device such as a desktop computer. The client is logged with the user's accounts, each of which may correspond to a distributed digital identity 102. In practical application: a distributed digital identity may correspond to an individual user, or to a merchant, or to a company, etc. A distributed digital identity may also correspond to an item in the physical world, for example, a device, or a ticket, etc.
A verifiable claim is to be understood as a claim whether the identity identified by a distributed digital identity is of some sort. Specifically to the data plane, a verifiable assertion can be data that records such an assertion.
A distributed digital identity may have multiple verifiable claims 103. Such as: for a distributed digital identity used by user A, the distributed digital identity may contain verifiable claim 1 for proving that user A is 18 years old, verifiable claim 2 for proving that user A has more than 100 million properties, verifiable claim 3 for proving that user A is qualified for motor vehicle driving, and so on. In practice, the verifiable claims may be issued by an authority with associated qualifications based on a user's request, the issued verifiable claims having a unique correspondence with the distributed digital identity of the user applying for the verifiable claims. For example, in the three specific examples above, the issuing authority for verifiable statement 1 may be the police station, the issuing authority for verifiable statement 2 may be the bank, and the issuing authority for verifiable statement 3 may be the vehicle authority.
In practical applications, there may be many (n) verifiable claims corresponding to the user a, i.e. a distributed digital identity. At this point, a plurality of verifiable claims need to be uniformly stored and managed, and thus, the data repository 104 may be employed to store verifiable claims 103 corresponding to distributed digital identities.
And the data warehouse is used for storing verifiable statements, and is called VC Repo for short. It should be noted that VC Repo is a logical concept, and may specifically be an application or a program. VC Repo may be deployed on various types of hardware devices. When storing the verifiable statements, the VCRepo can store the verifiable statements in a database that the VC Repo has usage rights.
The verifiable assertion data warehouse is mainly used for storing and forwarding the verifiable assertion for the management content of the verifiable assertion. In practical applications, some publishers of verifiable claims need to know the usage information of the verifiable claims issued by the publishers to users (e.g., which scenes the publishers are using, etc.), so as to perform statistical analysis on the usage process of the verifiable claims. While the original verifiable claims data repository cannot support this function.
Fig. 2 is a flowchart of a method for transmitting a verifiable statement according to an embodiment of the present disclosure. From the viewpoint of a program, the execution subject of the flow may be a program installed in an application server or an application client. For example, it may be a data repository for storing verifiable claims.
As shown in fig. 2, the process may include the following steps:
step 202: a first data repository obtaining a request to transmit a verifiable claim; the request comprises at least a first identification of the verifiable statement and a second identification of a target blockchain system;
the request may be device initiated that can verify the purported holder account. The holder may be a user of the first data repository having access to the first data repository. The identification of the holder account may be a distributed digital identity. The holder account may initiate the request through a device that it logs in to.
The first identity of the verifiable assertion can be represented by VCid. The second identifier of the target blockchain system may be denoted by VC Channel or Channel id.
Step 204: obtaining a verifiable statement corresponding to the first identification;
because the holder account is a user of the first data repository, a verifiable claim for the holder account may be pre-stored in the first data repository. After the request for transmitting the verifiable statement is acquired, the first data warehouse may search the verifiable statement to be transmitted corresponding to the request from the corresponding database according to the Vcid included in the request.
Step 206: sending the verifiable claims to the target blockchain system;
the holder of the verifiable assertion has usage rights of the first data repository and the verifier of the verifiable assertion has usage rights of the second data repository.
Wherein the data warehouse may have an account in the target blockchain system. After the data warehouse logs in the blockchain system through the account, data can be uploaded to the blockchain system. Alternatively, the data warehouse does not have an account, and data can be uploaded to the blockchain system through a third party platform with an account. This is not limited in the examples of this specification.
Fig. 3 is a schematic structural diagram of a transmission system capable of verifying a claim according to an embodiment of the present disclosure. As shown in fig. 3, 30 is a user terminal (also a sending device of a transmission request of an authenticatable claim), 31 is a first data repository, 32 is a second data repository, 33 is a database operable for the first data repository, and 34 is a server of an authenticatable party of the authenticatable claim. In the embodiment of the present specification, one of the roles of the transmission request of the verifiable declaration is to send the verifiable declaration to the server 34 of the verifier for verification.
In fig. 3, 11 is a first blockchain node, 12 is a second blockchain node, 13 is a third blockchain node, and the blockchain nodes 11, 12, and 13 belong to a first blockchain system. And 21 is a fourth blockchain node, 22 is a fifth blockchain node, 23 is a sixth blockchain node, and the blockchain nodes 21, 22 and 23 belong to a second blockchain system. A seventh block chain node 31, an eighth block chain node 32, a ninth block chain node 33, and the block chain link points 31, 32, and 33 belong to a third block chain system. It should be noted that fig. 3 is only a schematic diagram, and in practical applications, the number of blockchain systems to which the data warehouse can be connected may be greater, and the number of nodes in one blockchain system may also be greater.
In this embodiment of the present specification, the verifier of the verifiable assertion can use the second data repository to manage the verifiable assertion.
Since there may be more than one blockchain system to which the data warehouse may be connected, the second identifier needs to be included in the transmission request for the verifiable assertion in the step of fig. 2. The second indication may indicate which blockchain system the transmission of the verifiable claims needs to be completed through.
The principle of the method in fig. 2 is that first a chain of transaction data that can be stored on the blockchain is created by the first data repository based on verifiable statements. And uploading the transaction data on the chain to a blockchain node on the target blockchain system. The block link node may transmit transaction data on the link to other block link nodes in the system through a Peer-to-Peer network (also referred to as a P2P network) based on a consensus mechanism of the block link. When the consensus is achieved, each node receiving the transaction data on the chain can store the transaction data on the chain locally at each node. This allows all or most of the block nodes in the system to save transaction data on the chain. Through the above process, the transaction data on the chain can be transmitted to another blockchain node in the blockchain system. The second data warehouse can acquire transaction data on the chain from other blockchain nodes in the blockchain system, further acquire a corresponding verifiable statement and complete transmission of the verifiable statement. This transmission is different from the direct transmission in the general sense, and utilizes the common knowledge mechanism of the blockchain system originally used for accounting (or recording data) to indirectly realize the transmission. In addition, the method also utilizes the characteristic that the data recorded by the blockchain system cannot be tampered, so that the transmission process of the verifiable statement can be recorded by the blockchain system and can be traced. Therefore, the method in fig. 2 realizes recording of transmission or use process of the verifiable declaration and enables recorded data to have high credibility.
More specifically, when the method in fig. 2 is used to write the verifiable assertion into the blockchain system in the form of transaction data on a chain on the blockchain, the following example can be referred to for the information recording and query process of the usage process of the verifiable assertion:
when uploading the verifiable claims to the blockchain system, the verifiable claims can be uploaded to the blockchain system as a subject of transaction data on the chain, included in the transaction data on the chain. For example, the data constituting the verifiable assertion may be treated as a value corresponding to transactions field, and the transaction data on the chain may be generated in this manner. After the transaction data on the chain is uploaded to the blockchain system, the blockchain system generates a hash value for the transaction data on the chain. The use process of the verifiable statement can be recorded according to the hash value and the related information of the corresponding verifiable statement.
For example, the information of the verifier and the information of the holder of each use process of a certain verifiable statement can be recorded, and the hash value is recorded at the same time. This form of data record may be stored in the first data repository, and/or the second data repository. This form of data record itself can be used to enable traceability of the usage of the verifiable statement.
The data warehouse may also count usage information of the verifiable claim based on this form of data record, e.g., may count how many times the verifiable claim was used, etc.
If the data recorded in the data warehouse is questioned, data tracing can be carried out from the block chain system. For example, when the statistical data or the data record needs to be verified, the corresponding transaction data may be obtained from the blockchain system according to the stored hash value, and since the transaction data stored in the blockchain system cannot be tampered with, the statistical data or the data record may be verified using the transaction data stored in the blockchain system. Of course, if the record data of the usage process of the verifiable statement is not separately generated in advance, the related information of the usage process of the verifiable statement can be directly inquired according to the hash value corresponding to the verifiable statement when the usage process of the verifiable statement needs to be traced, so that the tracing of the usage process of the verifiable statement can be realized.
In practical applications, the request may further include: and (4) signature information. The transmission method can also adopt the following modes:
before sending the verifiable statement to the target blockchain system, the method may further include:
judging whether the signature information is the signature information of the holder account of the verifiable statement or not to obtain a first judgment result;
the sending the verifiable statement to the target blockchain system may specifically include:
and when the first judgment result shows that the signature information is the signature information of the holder account of the verifiable declaration, sending the verifiable declaration to the target block chain system.
In the foregoing manner, after receiving the transmission request, the first data warehouse may obtain the public key of the holding party, and perform signature verification on the signature information by using the public key. If the authentication is passed, it is verified that the sender of the transfer request is indeed a user of the first data repository. Specifically, the transmission request may also include a distributed digital identity of the holder, and the first data warehouse may query the public key of the holder from a corresponding distributed digital identity document (DID doc) according to the distributed digital identity.
The DID doc is explained here. The DID doc is a document corresponding to the distributed digital identity. A distributed digital identity has a DID doc corresponding to it. Various information related to the distributed digital identity may be recorded in the document. The DID doc may be stored on the blockchain. It should be noted that the block chain storing the DID doc may be a different block chain from the block chain in the embodiment of the present specification, which plays a role in transmitting the verifiable declaration.
In practical applications, the request may further include: a distributed digital identity of the verifiable asserted verifier account. The transmission method can also adopt the following modes:
the sending the verifiable statement to the target blockchain system specifically includes:
generating link transaction data containing the distributed digital identity; in the transaction data on the chain, a target object is the verifiable statement, a resource transfer-out account is a block chain account of a holder of the verifiable statement, and a resource transfer-in account is a block chain account of a verifier of the verifiable statement;
and sending the transaction data on the chain to the target block chain system.
The above method provides a specific method for generating transaction data on the link. And taking the verifiable statement as a subject matter, taking the blockchain account of the holding party as a resource transfer-out account, and taking the blockchain account of the verifying party as a resource transfer-in account. Specifically, the blockchain account of the holding party may be a distributed digital identity of the holding party, and the blockchain account of the verifying party may be a distributed digital identity of the verifying party.
In practical applications, the verifiable assertion may also be encrypted in order to protect the privacy of the user. Encryption may be performed in the following manner.
The generating of the data of the transaction on the chain including the distributed digital identity may further include:
encrypting the verifiable statement by adopting a symmetric key to obtain a symmetrically encrypted verifiable statement;
generating transaction data on an encryption chain containing the distributed digital identity; in the transaction data on the encryption chain, the object is the encrypted verifiable statement, and the authorization list contains the distributed digital identity of the verifier.
In the above manner, the authorization list is a field in the transaction data on the link. This field is used to indicate to which device the transaction data on the corresponding chain is sent. Because the verifier of the verifiable statement is the user of the second data warehouse, the second data warehouse can search the corresponding chain transaction data according to the distributed digital identity in the authorization list, and then forward the verifiable statement in the chain transaction data to the verifier for verification.
In practical applications, in order to further improve the protection of the privacy of the user, the symmetric key in the previous method may be encrypted. Specifically, the following manner can be adopted.
After encrypting the verifiable statement by using the symmetric key, the method may further include:
acquiring a public key of the verifier account;
encrypting the symmetric key by using the public key of the verifier account to obtain an authorization key;
the generating of the transaction data on the encryption chain including the distributed digital identity specifically includes:
generating transaction data on an encryption chain containing the distributed digital identity; in the transaction data on the encryption chain, the object is the encrypted verifiable statement, the authorization list comprises the distributed digital identity of the verifier account, and the authorization key list comprises the authorization key.
In the above manner, the authorization key can only be decrypted by using the private key of the verifier to obtain the symmetric key, and then the encrypted verifiable statement can be decrypted by using the symmetric key to obtain the verifiable statement original text. The private key of the verifier is usually only available to the verifier account. Therefore, the encryption mode is more secure.
In the foregoing manner, for obtaining the public key of the verifier account, the following manner may be specifically adopted:
and according to the distributed digital identity of the verifier account, acquiring the public key of the verifier account recorded in the distributed digital identity document of the distributed digital identity through a decentralized identity server.
The decentralized identity server is a server for providing a distributed Digital Identity Service (DIS). The server can store or read the DID doc. The server can generate the distributed digital identity and the corresponding DID doc for the user, and can also modify the DID doc. The server is correspondingly connected with another blockchain system. The DID doc is stored in another blockchain system, and the DIS server generated or modified DID doc can be ul stored in the other blockchain system according to the contract.
In practical application, after the verifiable statement is uploaded to the target blockchain system in a mode of exchanging data on a chain, a verifier account of the verifiable statement can be informed to acquire and verify the verifiable statement. The following may be specifically adopted:
after sending the verifiable claims to the target blockchain system, sending a verification request to a verifier account of the verifiable claims; the verification request comprises the first identification and the second identification.
In the above manner, the first identifier and the second identifier are sent to the device where the verifier account is located, so that the verifier account can determine the target blockchain system according to the first identifier and the second identifier, and further obtain the corresponding verifiable statement from the target blockchain system for verification.
In practical applications, if the verifiable statement is encrypted by using the symmetric key and the symmetric key is encrypted by using the public key of the verifier account to generate the authorization key, in the above manner, the verification request further includes the authorization key, so that the verifier account can be decrypted to obtain the original text of the verifiable statement.
Fig. 4 is a flowchart of another method for transmitting a verifiable statement according to an embodiment of the present disclosure. As shown in fig. 4, the method comprises the steps of:
step 401: a device of a holder of the verifiable claim sends a verifiable claim transmission request;
the transmission request may carry Vcid, VC channel, distributed digital identity of the verifying party, and signature of the holding party.
Step 402: the first data warehouse verifies whether the sender of the transmission request has the use right of the first data warehouse.
The determination may be made by the owner's signature information in the transmission request. When the authority verification is passed, step 403 is performed.
Step 403: the first data repository sends a request to the DIS server to find the public key of the verifier.
Step 404: the DIS server returns the public key of the authenticator to the first data repository.
Step 405: the first data warehouse encrypts the verifiable claims to generate transaction data on the chain.
The specific encryption mode may be to encrypt the verifiable statement original text by using the symmetric key to obtain the encrypted verifiable statement. And encrypting the symmetric key by using the public key of the verifier to obtain the authorization key. In the generated chain transaction data, the object is the encrypted verifiable statement, the authorization list includes the distributed digital identity of the account of the verifier, the authorization key list includes the authorization key, the resource transfer-out account is the block chain account (which may be a distributed digital identity) of the holder of the verifiable statement, and the resource transfer-in account is the block chain account (which may be a distributed digital identity) of the verifier of the verifiable statement.
Step 406: the transaction data on the chain generated in step 405 is uploaded to the target blockchain system.
Step 407: a verifiable claim verification request is sent to a verifier device.
Step 407 is an optional step. In practice, step 407 may be performed by the first data warehouse or by the owner device.
The method in fig. 4 is used to transmit the verifiable statement, on one hand, the transmission of the verifiable statement is realized by using a consensus mechanism of the block chain, and on the other hand, the transmission or use process of the verifiable statement can be recorded and traced by using the data recording capability of the block chain; on the other hand, the tamper-proof capability of the block chain is utilized, so that the record of the transmission or use process of the verifiable statement has high credibility; on the other hand, by means of encrypting the verifiable statements stored in the chain, the leakage of user privacy caused by the fact that data on the block chain has the characteristics of transparency and being inquired is avoided, and the safety of the user privacy is improved.
Based on the same idea, the embodiment of the present specification further provides a device corresponding to the above method. Fig. 5 is a schematic structural diagram of a transmission apparatus corresponding to one verifiable statement in fig. 2 according to an embodiment of the present disclosure. As shown in fig. 5, the apparatus may include:
a transmission request obtaining module 502, configured to obtain a request for transmitting a verifiable statement; the request comprises at least a first identification of the verifiable statement and a second identification of a target blockchain system;
a verifiable statement obtaining module 504, configured to obtain a verifiable statement corresponding to the first identifier;
a verifiable assertion sending module 506 for sending the verifiable assertion to the target blockchain system;
the authenticatable claimant account has usage rights of the first data repository, the authenticatable claimant account has usage rights of a second data repository; the first data repository has a first account in the target blockchain system and the second data repository has a second account in the target blockchain system.
According to the device, the verifiable statement is sent to the verifier equipment from the owner equipment through the block chain, so that the transmission process of the verifiable statement is recorded by the block chain system and can be traced. And because the data on the blockchain is not easy to be tampered, the record of the transmission or use process of the verifiable statement also has high credibility.
In practical applications, the request may further include: signing information;
the apparatus may further include:
the judging module is used for judging whether the signature information is the signature information of the owner account of the verifiable statement or not before the verifiable statement is sent to the target block chain system, and obtaining a first judging result;
the verifiable statement sending module 506 may specifically include:
a first sending unit, configured to send the verifiable statement to the target blockchain system when the first determination result indicates that the signature information is signature information of a holder account of the verifiable statement.
In practical applications, the request may further include: a distributed digital identity of the verifiable asserted verifier account;
the verifiable statement sending module 506 may specifically include:
the chain transaction data generating unit is used for generating chain transaction data containing the distributed digital identity; in the transaction data on the chain, a target object is the verifiable statement, a resource transfer-out account is a block chain account of a holder of the verifiable statement, and a resource transfer-in account is a block chain account of a verifier of the verifiable statement;
and the second sending unit is used for sending the transaction data on the link to the target block chain system.
In practical applications, the link transaction data generating unit may specifically include:
the encryption subunit is used for encrypting the verifiable statement by adopting a symmetric key to obtain a symmetrically encrypted verifiable statement;
the transaction data generation subunit is used for generating transaction data on the encryption chain containing the distributed digital identity; in the transaction data on the encryption chain, a target object is the encrypted verifiable statement, and an authorization list contains the distributed digital identity of the verification party account; the resource transfer-out account is a blockchain account of the holder of the verifiable statement, and the resource transfer-in account is a blockchain account of the verifier of the verifiable statement.
In practical application, the device may further include:
a public key obtaining module, configured to obtain a public key of the verifier account after encrypting the verifiable statement with a symmetric key;
the symmetric key encryption module is used for encrypting the symmetric key by adopting the public key of the verifier account to obtain an authorized key;
the transaction data generation subunit on the encryption chain may be specifically configured to:
generating transaction data on an encryption chain containing the distributed digital identity; in the transaction data on the encryption chain, a target object is the encrypted verifiable statement, an authorization list comprises the distributed digital identity of the verifier account, and an authorization key list comprises the authorization key; the resource transfer-out account is a blockchain account of the holder of the verifiable statement, and the resource transfer-in account is a blockchain account of the verifier of the verifiable statement.
In practical applications, the public key obtaining module may specifically include:
and the public key acquisition unit is used for acquiring the public key of the verifier account recorded in the distributed digital identity document of the distributed digital identity through a decentralized identity server according to the distributed digital identity of the verifier account.
In practical application, the device may further include:
a verification request sending module, configured to send a verification request to a verifier account of the verifiable statement after sending the verifiable statement to the target blockchain system; the verification request comprises the first identification and the second identification.
In practical applications, the verification request may further include: the authorization key.
Based on the same idea, the embodiment of the present specification further provides a device corresponding to the above method.
Fig. 6 is a schematic structural diagram of a transmission device corresponding to one verifiable assertion in fig. 2, provided in an embodiment of this specification. As shown in fig. 6, the apparatus 600 may include:
at least one processor 610; and the number of the first and second groups,
a memory 630 communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory 630 stores instructions 620 executable by the at least one processor 610 to enable the at least one processor 610 to:
obtaining a request to transmit a verifiable claim; the request comprises at least a first identification of the verifiable statement and a second identification of a target blockchain system;
obtaining a verifiable statement corresponding to the first identification;
sending the verifiable claims to the target blockchain system;
the authenticatable claimant account has usage rights of the first data repository and the authenticatable claimant account has usage rights of a second data repository.
Based on the same idea, the embodiment of the present specification further provides a system corresponding to the above method. The system may include:
a first data warehouse, a second data warehouse, and at least one target blockchain system;
the first data repository to obtain a request to transmit a verifiable claim; the request comprises at least a first identification of the verifiable statement and a second identification of a target blockchain system; obtaining a verifiable statement corresponding to the first identification; sending the verifiable claims to the target blockchain system;
the second data repository to obtain the verifiable claims from the target blockchain system;
the authenticatable claimant account has usage rights of the first data repository and the authenticatable claimant account has usage rights of the second data repository.
In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Language Description Language), traffic, pl (core unified Programming Language), HDCal, JHDL (Java Hardware Description Language), langue, Lola, HDL, laspam, hardsradware (Hardware Description Language), vhjhd (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.
The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functionality of the units may be implemented in one or more software and/or hardware when implementing the present application.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices, or any other non-transmission medium which can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims (18)
1. A method of transmission of a verifiable claim, comprising:
obtaining a request to transmit a verifiable claim; the request comprises at least a first identification of the verifiable statement and a second identification of a target blockchain system;
obtaining a verifiable statement corresponding to the first identification;
sending the verifiable claims to the target blockchain system;
the authenticatable claimant account has usage rights of the first data repository and the authenticatable claimant account has usage rights of a second data repository.
2. The method of claim 1, further comprising in the request: signing information;
before sending the verifiable statement to the target blockchain system, the method further comprises:
judging whether the signature information is the signature information of the holder account of the verifiable statement or not to obtain a first judgment result;
the sending the verifiable statement to the target blockchain system specifically includes:
and when the first judgment result shows that the signature information is the signature information of the holder account of the verifiable declaration, sending the verifiable declaration to the target block chain system.
3. The method of claim 1, further comprising in the request: a distributed digital identity of the verifiable asserted verifier account;
the sending the verifiable statement to the target blockchain system specifically includes:
generating link transaction data containing the distributed digital identity; in the transaction data on the chain, a target object is the verifiable statement, a resource transfer-out account is a block chain account of a holder of the verifiable statement, and a resource transfer-in account is a block chain account of a verifier of the verifiable statement;
and sending the transaction data on the chain to the target block chain system.
4. The method of claim 3, the generating of the on-chain transaction data containing the distributed digital identity, further comprising:
encrypting the verifiable statement by adopting a symmetric key to obtain a symmetrically encrypted verifiable statement;
generating transaction data on an encryption chain containing the distributed digital identity; in the transaction data on the encryption chain, the object is the encrypted verifiable statement, and the authorization list contains the distributed digital identity of the verification party account.
5. The method of claim 4, after encrypting the verifiable claim with a symmetric key, further comprising:
acquiring a public key of the verifier account;
encrypting the symmetric key by using the public key of the verifier account to obtain an authorization key;
the generating of the transaction data on the encryption chain including the distributed digital identity specifically includes:
generating transaction data on an encryption chain containing the distributed digital identity; in the transaction data on the encryption chain, the object is the encrypted verifiable statement, the authorization list comprises the distributed digital identity of the verifier account, and the authorization key list comprises the authorization key.
6. The method according to claim 5, wherein the obtaining the public key of the verifier account specifically includes:
and according to the distributed digital identity of the verifier account, acquiring the public key of the verifier account recorded in the distributed digital identity document of the distributed digital identity through a decentralized identity server.
7. The method of claim 5, after sending the verifiable claims to the target blockchain system, further comprising:
sending a verification request to a verifier account of the verifiable claim; the verification request comprises the first identification and the second identification.
8. The method of claim 7, further comprising in the authentication request: the authorization key.
9. A verifiable claim transmission device, comprising:
a transmission request acquisition module for acquiring a request for transmitting the verifiable statement; the request comprises at least a first identification of the verifiable statement and a second identification of a target blockchain system;
the verifiable statement acquisition module is used for acquiring the verifiable statement corresponding to the first identifier;
a verifiable assertion sending module for sending the verifiable assertion to the target blockchain system;
the authenticatable claimant account has usage rights of the first data repository and the authenticatable claimant account has usage rights of a second data repository.
10. The apparatus of claim 9, further comprising in the request: signing information;
the device further comprises:
the judging module is used for judging whether the signature information is the signature information of the owner account of the verifiable statement or not before the verifiable statement is sent to the target block chain system, and obtaining a first judging result;
the verifiable statement sending module specifically comprises:
a first sending unit, configured to send the verifiable statement to the target blockchain system when the first determination result indicates that the signature information is signature information of a holder account of the verifiable statement.
11. The apparatus of claim 9, further comprising in the request: a distributed digital identity of the verifiable asserted verifier account;
the verifiable statement sending module specifically comprises:
the chain transaction data generating unit is used for generating chain transaction data containing the distributed digital identity; in the transaction data on the chain, a target object is the verifiable statement, a resource transfer-out account is a block chain account of a holder of the verifiable statement, and a resource transfer-in account is a block chain account of a verifier of the verifiable statement;
and the second sending unit is used for sending the transaction data on the link to the target block chain system.
12. The apparatus according to claim 11, wherein the link transaction data generation unit specifically includes:
the encryption subunit is used for encrypting the verifiable statement by adopting a symmetric key to obtain a symmetrically encrypted verifiable statement;
the transaction data generation subunit is used for generating transaction data on the encryption chain containing the distributed digital identity; in the transaction data on the encryption chain, a target object is the encrypted verifiable statement, and an authorization list contains the distributed digital identity of the verification party account; the resource transfer-out account is a blockchain account of the holder of the verifiable statement, and the resource transfer-in account is a blockchain account of the verifier of the verifiable statement.
13. The apparatus of claim 12, further comprising:
a public key obtaining module, configured to obtain a public key of the verifier account after encrypting the verifiable statement with a symmetric key;
the symmetric key encryption module is used for encrypting the symmetric key by adopting the public key of the verifier account to obtain an authorized key;
the transaction data generation subunit on the encryption chain is specifically configured to:
generating transaction data on an encryption chain containing the distributed digital identity; in the transaction data on the encryption chain, a target object is the encrypted verifiable statement, an authorization list comprises the distributed digital identity of the verifier account, and an authorization key list comprises the authorization key; the resource transfer-out account is a blockchain account of the holder of the verifiable statement, and the resource transfer-in account is a blockchain account of the verifier of the verifiable statement.
14. The apparatus according to claim 13, wherein the public key obtaining module specifically includes:
and the public key acquisition unit is used for acquiring the public key of the verifier account recorded in the distributed digital identity document of the distributed digital identity through a decentralized identity server according to the distributed digital identity of the verifier account.
15. The apparatus of claim 13, further comprising:
a verification request sending module, configured to send a verification request to a verifier account of the verifiable statement after sending the verifiable statement to the target blockchain system; the verification request comprises the first identification and the second identification.
16. The apparatus of claim 15, further comprising in the authentication request: the authorization key.
17. A verifiable claim transmission device comprising:
at least one processor; and the number of the first and second groups,
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores instructions executable by the at least one processor to enable the at least one processor to:
obtaining a request to transmit a verifiable claim; the request comprises at least a first identification of the verifiable statement and a second identification of a target blockchain system;
obtaining a verifiable statement corresponding to the first identification;
sending the verifiable claims to the target blockchain system;
the authenticatable claimant account has usage rights of the first data repository and the authenticatable claimant account has usage rights of a second data repository.
18. A verifiable claim transmission system comprising:
a first data warehouse, a second data warehouse, and at least one target blockchain system;
the first data repository to obtain a request to transmit a verifiable claim; the request comprises at least a first identification of the verifiable statement and a second identification of a target blockchain system; obtaining a verifiable statement corresponding to the first identification; sending the verifiable claims to the target blockchain system;
the second data repository to obtain the verifiable claims from the target blockchain system;
the authenticatable claimant account has usage rights of the first data repository and the authenticatable claimant account has usage rights of the second data repository.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010277167.8A CN111193597B (en) | 2020-04-10 | 2020-04-10 | Transmission method, device, equipment and system capable of verifying statement |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010277167.8A CN111193597B (en) | 2020-04-10 | 2020-04-10 | Transmission method, device, equipment and system capable of verifying statement |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111193597A true CN111193597A (en) | 2020-05-22 |
| CN111193597B CN111193597B (en) | 2020-07-31 |
Family
ID=70710291
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010277167.8A Active CN111193597B (en) | 2020-04-10 | 2020-04-10 | Transmission method, device, equipment and system capable of verifying statement |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111193597B (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111769958A (en) * | 2020-09-02 | 2020-10-13 | 百度在线网络技术（北京）有限公司 | Block chain cross-chain processing method, device, equipment and storage medium |
| CN111770199A (en) * | 2020-08-31 | 2020-10-13 | 支付宝(杭州)信息技术有限公司 | Information sharing method, device and equipment |
| CN112380287A (en) * | 2020-11-13 | 2021-02-19 | 浙江数秦科技有限公司 | Distributed credible statement generation method, system, equipment and storage medium |
| CN113395281A (en) * | 2021-06-11 | 2021-09-14 | 网易（杭州）网络有限公司 | Verification method and device capable of verifying statement and electronic equipment |
| CN113806809A (en) * | 2021-11-17 | 2021-12-17 | 北京溪塔科技有限公司 | Job seeker information disclosure method and system based on block chain |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109493082A (en) * | 2018-09-25 | 2019-03-19 | 西安纸贵互联网科技有限公司 | A kind of agricultural product block chain source tracing method and device |
| WO2019143582A1 (en) * | 2018-01-22 | 2019-07-25 | Microsoft Technology Licensing, Llc | Attestation management |
| WO2019179535A2 (en) * | 2019-07-02 | 2019-09-26 | Alibaba Group Holding Limited | System and method for verifying verifiable claims |
| WO2019228557A2 (en) * | 2019-07-02 | 2019-12-05 | Alibaba Group Holding Limited | System and method for decentralized-identifier authentication |
| CN110795501A (en) * | 2019-10-11 | 2020-02-14 | 支付宝(杭州)信息技术有限公司 | Method, device, equipment and system for creating verifiable statement based on block chain |
-
2020
- 2020-04-10 CN CN202010277167.8A patent/CN111193597B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2019143582A1 (en) * | 2018-01-22 | 2019-07-25 | Microsoft Technology Licensing, Llc | Attestation management |
| CN109493082A (en) * | 2018-09-25 | 2019-03-19 | 西安纸贵互联网科技有限公司 | A kind of agricultural product block chain source tracing method and device |
| WO2019179535A2 (en) * | 2019-07-02 | 2019-09-26 | Alibaba Group Holding Limited | System and method for verifying verifiable claims |
| WO2019228557A2 (en) * | 2019-07-02 | 2019-12-05 | Alibaba Group Holding Limited | System and method for decentralized-identifier authentication |
| CN110795501A (en) * | 2019-10-11 | 2020-02-14 | 支付宝(杭州)信息技术有限公司 | Method, device, equipment and system for creating verifiable statement based on block chain |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111770199A (en) * | 2020-08-31 | 2020-10-13 | 支付宝(杭州)信息技术有限公司 | Information sharing method, device and equipment |
| US11263632B2 (en) | 2020-08-31 | 2022-03-01 | Alipay (Hangzhou) Information Technology Co., Ltd. | Information sharing methods, apparatuses, and devices |
| CN111769958A (en) * | 2020-09-02 | 2020-10-13 | 百度在线网络技术（北京）有限公司 | Block chain cross-chain processing method, device, equipment and storage medium |
| CN111769958B (en) * | 2020-09-02 | 2021-01-01 | 百度在线网络技术（北京）有限公司 | Block chain cross-chain processing method, device, equipment and storage medium |
| CN112380287A (en) * | 2020-11-13 | 2021-02-19 | 浙江数秦科技有限公司 | Distributed credible statement generation method, system, equipment and storage medium |
| CN112380287B (en) * | 2020-11-13 | 2022-06-10 | 浙江数秦科技有限公司 | Distributed credible statement generation method, system, equipment and storage medium |
| CN113395281A (en) * | 2021-06-11 | 2021-09-14 | 网易（杭州）网络有限公司 | Verification method and device capable of verifying statement and electronic equipment |
| CN113395281B (en) * | 2021-06-11 | 2022-11-01 | 网易（杭州）网络有限公司 | Verification method and device capable of verifying statement and electronic equipment |
| CN113806809A (en) * | 2021-11-17 | 2021-12-17 | 北京溪塔科技有限公司 | Job seeker information disclosure method and system based on block chain |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111193597B (en) | 2020-07-31 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111193597B (en) | Transmission method, device, equipment and system capable of verifying statement | |
| CN111741036B (en) | Trusted data transmission method, device and equipment | |
| CN111401902B (en) | Service processing method, device and equipment based on block chain | |
| CN111191268B (en) | Storage method, device and equipment capable of verifying statement | |
| CN111932426B (en) | Identity management method, device and equipment based on trusted hardware | |
| CN111931238B (en) | Block chain-based data asset transfer method, device and equipment | |
| CN111814196B (en) | Data processing method, device and equipment | |
| CN111814195B (en) | Data management method, device and equipment based on trusted hardware | |
| CN111814156B (en) | Data acquisition method, device and equipment based on trusted equipment | |
| CN111190974B (en) | Method, device and equipment for forwarding and acquiring verifiable statement | |
| US11520905B2 (en) | Smart data protection | |
| CN114884674B (en) | User data circulation method, device and equipment based on block chain | |
| CN113076527B (en) | Block chain-based digital asset processing method and device | |
| CN112100689B (en) | Trusted data processing method, device and equipment | |
| CN111930846B (en) | Data processing method, device and equipment | |
| CN115758418A (en) | Data management method, device and equipment based on block chain network | |
| CN116455657A (en) | Service providing method, device, equipment and system | |
| CN114626944A (en) | Service processing method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: DE Ref document number: 40030547 Country of ref document: HK |