Blockchain-based identity authentication method and apparatus

By introducing level fields and real-name identity proofs from different providers in blockchain identity authentication, combining digital signatures and signature verification, the problems of cross-chain identity authentication and real-name verification in decentralized digital identity system are solved, and the problem of cross-chain identity authentication and real-name verification in the decentralized digital identity system is realized. Flexibility and security of proof of identity.

WO2024227404A1PCT designated stage expired Publication Date: 2024-11-07ALIPAY (HANGZHOU) INFORMATION TECH CO LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2024/088916
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-04
Filing Date
2024-04-19
Publication Date
2024-11-07

AI Technical Summary

Technical Problem

The existing technology is difficult to implement cross-chain identity authentication in a decentralized digital identity system, and it is impossible to effectively distinguish and verify the identity proof of person and real-name identity, resulting in insufficient identity proof in scenarios where real-name verification is required and real-name verification is not required. The proof of identity is too complicated in the scenario.

Method used

Introduce the level field in the identity proof, expand the types of real-person identity proof and real-name identity proof, generate and verify the authenticated person and real-name identity proof through different providers on the blockchain, and combine digital signature and signature verification mechanisms to ensure identity authentication. authenticity and credibility, and use traditional identity proof in scenarios where real-name verification is not required.

Benefits of technology

It realizes the security of identity proof being guaranteed to be authenticated in scenarios where real-name verification is required, and simplifies the identity proof process in scenarios where real-name verification is not required to ensure the efficiency and accuracy of identity authentication.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024088916_07112024_PF_FP_ABST
    Figure CN2024088916_07112024_PF_FP_ABST
Patent Text Reader

Abstract

Disclosed in the present invention is a blockchain-based identity authentication method, comprising: receiving an authorization request for an identity certificate initiated by a user in a blockchain, wherein the authorization request comprises a real person identity certificate and a real name identity certificate of the user, the real person identity certificate is an identity certificate that is digitally signed by a first provider in the blockchain by using a locally stored first identity private key, and the real name identity certificate is an identity certificate that is digitally signed by a second provider in the blockchain by using a locally stored second identity private key; in response to the authorization request, querying from the blockchain a first identity public key and a second identity public key; on the basis of the first identity public key, performing signature verification on the digital signature of the real person identity certificate, and on the basis of the second identity public key, performing signature verification on the digital signature of the real name identity certificate; and once the digital signature of the real person identity certificate and the digital signature of the real name identity certificate both pass the signature verification, determining that identity authentication for the user is successful.
Need to check novelty before this filing date? Find Prior Art

Description

A blockchain-based identity authentication method and device Technical Field

[0001] The present invention relates to a blockchain technology, and in particular to an identity authentication method and device based on a blockchain. Background Art

[0002] Blockchain technology, also known as distributed ledger technology, is an emerging technology that enables multiple computing devices to jointly maintain a complete distributed database. Due to its decentralized, transparent nature, the ability of each computing device to participate in database recording, and the rapid synchronization of data between computing devices, blockchain technology has been widely applied in numerous fields.

[0003] Decentralized Identity (DID) is a digital identity system based on blockchain technology, which has the characteristics of ensuring data authenticity, protecting user privacy and security, and strong portability.

[0004] Summary of the Invention

[0005] One of the objectives of the present invention is to provide a blockchain-based identity authentication method that can achieve cross-chain authentication of decentralized digital identities.

[0006] Based on the above invention purpose, the present invention proposes a blockchain-based identity authentication method, which is applied to the identity verification party of the decentralized digital identity blockchain, wherein the blockchain stores the identity public key associated with the decentralized digital identity uploaded by each blockchain member; the blockchain members include the identity proof provider, the identity proof user and the identity proof verification party; the method comprises: receiving an identity proof authorization request initiated by the user in the blockchain; wherein the authorization request includes the real-person identity proof and the real-name identity proof of the user; the real-person identity proof is provided by the first provider in the blockchain after the real-person verification of the user is passed, using the locally stored an identity certificate digitally signed by a first identity private key; the real-name identity certificate is digitally signed by a second provider in the blockchain using a locally stored second identity private key after the real-person identity certificate is verified; in response to the authorization request, the first identity public key stored by the first provider and the second identity public key stored by the second provider are queried from the blockchain; the digital signature of the real-person identity certificate is verified based on the first identity public key, and the digital signature of the real-name identity certificate is verified based on the second identity public key; after the digital signatures of the real-person identity certificate and the real-name identity certificate are both verified, it is determined that the identity authentication for the user is passed.

[0007] Furthermore, in some embodiments, the identity certificate issued by the provider is provided with a level field indicating the type of identity certificate; the field value of the level field includes a first field value for indicating real-person identity certificate, a second field value for indicating real-name identity certificate, and a third field value for indicating ordinary identity certificate.

[0008] Furthermore, in some embodiments, the real-name identity certificate is also provided with an associated field indicating an associated real-person identity certificate; the associated real-person identity certificate refers to the real-person identity certificate that has passed the signature verification before the second provider issues the real-name identity certificate.

[0009] Furthermore, in some embodiments, the real-person identity certificate and real-name identity certificate in the authorization request are encrypted by the user using the third identity public key of the verification method stored in the blockchain; before querying the first identity public key stored by the first provider and the second identity public key stored by the second provider from the blockchain, it also includes: using the locally stored third identity private key to decrypt the encrypted real-person identity certificate and real-name identity certificate to obtain the plaintext real-person identity certificate and real-name identity certificate.

[0010] Furthermore, in some embodiments, after determining that the identity authentication for the user is passed, it also includes: obtaining the identity information in the plain text real-person identity certificate and the business information in the real-name identity certificate; and performing relevant business operations based on the identity information and business information.

[0011] The present invention also provides another blockchain-based identity authentication method for the same purpose as the above method, which is applied to the user of identity proof in the blockchain of decentralized digital identity, wherein the blockchain stores the identity public key associated with the decentralized digital identity uploaded by each blockchain member; the blockchain members include the provider of identity proof, the user of identity proof and the verifier of identity proof; the method comprises: sending a first request for real-person identity proof to the first provider in the blockchain, wherein the first request includes the decentralized digital identity of the user; so that the first provider performs real-person verification on the user, and after the real-person verification is passed, based on the decentralized digital identity of the user and the identity of the user obtained during the real-person verification process, The method comprises the steps of: generating a real-name identity certificate based on a copy of the user's information; storing the real-name identity certificate issued by the first provider; wherein the real-name identity certificate is digitally signed by the first provider using the locally stored first identity private key; sending a second request for real-name identity certification to the second provider in the blockchain, wherein the second request includes the decentralized digital identity of the user and the real-name identity certificate; enabling the second provider to verify the real-name identity certificate and generate a real-name identity certificate based on the decentralized digital identity of the user and the real-name identity certificate after the verification is passed; storing the real-name identity certificate issued by the second provider; wherein the real-name identity certificate is digitally signed by the second provider using the locally stored second identity private key.

[0012] Furthermore, in some embodiments, it also includes: initiating an authorization request for identity proof to the verifier in the blockchain; wherein the authorization request includes the real-person identity proof and real-name identity proof of the user; so that the verifier verifies the real-person identity proof and real-name identity proof.

[0013] Furthermore, in some embodiments, the identity certificate issued by the provider of the blockchain is provided with a level field indicating the type of identity certificate; the field value of the level field includes a first field value for indicating real-person identity certificate, a second field value for indicating real-name identity certificate, and a third field value for indicating ordinary identity certificate.

[0014] Furthermore, in some embodiments, the real-name identity certificate is also provided with an associated field indicating an associated real-person identity certificate; the associated real-person identity certificate refers to the real-person identity certificate that has passed the signature verification before the second provider issues the real-name identity certificate.

[0015] Furthermore, in some embodiments, the real-person identity certificate and real-name identity certificate in the authorization request are encrypted by the user using the third identity public key of the verification method stored in the blockchain; the verifier verifies the real-person identity certificate and real-name identity certificate, including: the verifier uses the locally stored third identity private key to decrypt the encrypted real-person identity certificate and real-name identity certificate to obtain the plaintext real-person identity certificate and real-name identity certificate; queries the first identity public key stored by the first provider and the second identity public key stored by the second provider from the blockchain; verifies the digital signature of the real-person identity certificate based on the first identity public key, and verifies the digital signature of the real-name identity certificate based on the second identity public key; after the digital signatures of the real-person identity certificate and the real-name identity certificate are both verified and passed, it is determined that the identity authentication for the user is passed.

[0016] The present invention also provides an identity authentication device based on blockchain, which is applied to the verification party of identity proof in the blockchain of decentralized digital identity, wherein the blockchain stores the identity public key associated with the decentralized digital identity uploaded by each blockchain member; the blockchain members include the provider of identity proof, the user of identity proof and the verification party of identity proof; the device includes: a receiving module for receiving the authorization request for identity proof initiated by the user in the blockchain; wherein the authorization request includes the real-person identity proof and real-name identity proof of the user; the real-person identity proof is verified by the first provider in the blockchain using the locally stored first identity private key after the real-person verification of the user is passed. The real-name identity certificate is a digitally signed identity certificate by the second provider in the blockchain after the real-person identity certificate is verified and passed, and the digitally signed identity certificate is a locally stored second identity private key; the query module is used to query the first identity public key stored by the first provider and the second identity public key stored by the second provider from the blockchain; the signature verification module is used to verify the digital signature of the real-person identity certificate based on the first identity public key, and to verify the digital signature of the real-name identity certificate based on the second identity public key; the determination module is used to determine that the identity authentication for the user is passed after the real-person identity certificate and the digital signature of the real-name identity certificate are both verified and passed.

[0017] The present invention also provides an identity authentication device based on blockchain, which is applied to the user of identity proof in the blockchain of decentralized digital identity, wherein the blockchain stores identity public keys associated with decentralized digital identities uploaded by respective blockchain members; the blockchain members include providers of identity proof, users of identity proof and verifiers of identity proof; the device comprises: a first application module, which is used to send a first request for real-person identity proof to a first provider in the blockchain, wherein the first request includes the decentralized digital identity of the user; so that the first provider performs real-person verification on the user, and after the real-person verification is passed, generates a real-person identity proof based on the decentralized digital identity of the user and the identity information of the user obtained during the real-person verification process; the first storage module A storage module is used to store the real-name identity certificate issued by the first provider; wherein the real-name identity certificate is digitally signed by the first provider using the locally stored first identity private key; a second application module is used to send a second request for applying for real-name identity certificate to the second provider in the blockchain, wherein the second request includes the decentralized digital identity of the user and the real-name identity certificate; so that the second provider verifies the real-name identity certificate and generates a real-name identity certificate based on the decentralized digital identity of the user and the real-name identity certificate after the verification is passed; a second storage module is used to store the real-name identity certificate issued by the second provider; wherein the real-name identity certificate is digitally signed by the second provider using the locally stored second identity private key.

[0018] The blockchain-based identity authentication method and device described in this invention have the following beneficial effects: The invention introduces a level field into the traditional identity verification format, thereby expanding the types of identity verification, specifically expanding to real-person identity verification and real-name identity verification. Thus, in scenarios where real-name verification is required, the combined use of real-name and real-person identity verification can ensure that the user's identity verification has been verified by real name; in scenarios where real-name verification is not required, traditional identity verification can still be used. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] FIG1 exemplarily shows a schematic diagram of a blockchain for decentralized digital identity;

[0020] FIG2 exemplarily shows a flowchart of a blockchain-based identity authentication method with a user as the execution subject of the present invention;

[0021] FIG3 exemplarily shows a schematic diagram of the blockchain of the improved decentralized digital identity of the present invention;

[0022] FIG4 exemplarily shows a data structure diagram of the real-person identity certification and the real-name identity certification extended by the present invention;

[0023] FIG5 exemplarily shows a flowchart of a blockchain-based identity authentication method with a verifier as the execution subject according to the present invention;

[0024] FIG6 exemplarily shows a module diagram of a blockchain-based identity authentication device according to the present invention;

[0025] FIG7 exemplarily shows a module diagram of the blockchain-based identity authentication device according to the present invention. DETAILED DESCRIPTION

[0026] The blockchain-based identity authentication method and device, computer-readable storage medium, and electronic device described in the present invention will be further described in detail below in conjunction with the accompanying drawings and specific embodiments of the specification, but this detailed description does not constitute a limitation of the present invention.

[0027] First, some technical concepts involved in the present invention are introduced.

[0028] Decentralized Identity (DID) is a digital identity system based on blockchain technology, which has the characteristics of ensuring data authenticity, protecting user privacy and security, and strong portability.

[0029] When implementing DID, it also requires the use of a decentralized public key infrastructure (DPKI). DPKI-based blockchains can provide a cryptographically secure infrastructure. Specifically, this infrastructure generates a public-private key pair associated with the DID and digitally signs and verifies the data being transmitted based on the public-private key pair, ensuring the authenticity and trustworthiness of the data being transmitted.

[0030] Please refer to Figure 1 below for a schematic diagram of a decentralized digital identity blockchain.

[0031] Based on their roles, blockchain members can be divided into identity providers, identity users, and identity verifiers. Providers, users, and verifiers all need to register their own DIDs in the blockchain.

[0032] During the application stage, the user can apply for identity proof from the provider, and the provider will endorse certain identity information of the user and generate an identity proof for the user.

[0033] During the usage phase, if the user has certain business needs that require the verification party to execute, the user can authorize the identity certificate to the verification party, which will verify the identity certificate to confirm the authenticity of the identity certificate; and after confirming the authenticity of the identity certificate, it will execute relevant business operations for the user.

[0034] In some application scenarios, in addition to verifying the authenticity of the identity certificate provided by the user, the verifier also needs to confirm whether the user corresponding to the identity certificate has undergone real-name verification.

[0035] For example, a decentralized digital identity DID holds an identity certificate for the digital blind and uses this identity certificate to apply to the verification party for related business operations.

[0036] At this point, in addition to verifying the validity of the identity certificate, the verifier also needs to determine whether the user of the digital blind person's identity certificate is really a blind person.

[0037] Correspondingly, similar scenarios also involve the application process for identity proof, and the provider also needs to conduct real-name verification with the user before issuing the identity proof to the user.

[0038] For example, when a user uses DID to apply for a digital blind identity certificate from the Blind Association, the Blind Association needs to verify the real-name identity of the DID to ensure that the user is indeed blind.

[0039] In related technologies, real-name verification can be performed during the user registration process of DID, but the identity certificates generated in this way are all subject to real-name verification. This not only goes against the original intention of decentralized digital identity, but also not all application scenarios require real-name verification.

[0040] Based on this, the present invention aims to provide a blockchain-based identity authentication solution that takes into account the needs of different application scenarios. By introducing a level field into the traditional identity verification format, the different types of identity verification are expanded, specifically expanding the real-person identity verification and real-name identity verification. Thus, in scenarios where real-name verification is required, the combined use of real-name and real-person identity verification can ensure that the user's identity verification has been verified by real name. In scenarios where real-name verification is not required, traditional identity verification (without real-name verification) can still be used.

[0041] In one embodiment of the present invention, a blockchain-based identity authentication method is proposed. FIG2 exemplarily illustrates a flow chart of the blockchain-based identity authentication method of the present invention in one embodiment, which can be applied to users of identity proof in a blockchain.

[0042] Please explain below with reference to the schematic diagram of the improved decentralized digital identity blockchain shown in Figure 3.

[0043] As previously mentioned, the present invention expands upon different types of identity verification, including real-person identity verification and real-name identity verification, as well as traditional identity verification (hereinafter referred to as ordinary identity verification). As shown in FIG3 , the present invention also classifies the providers of identity verification into different levels, with providers capable of generating real-person identity verification being referred to as first providers, providers capable of generating real-name identity verification being referred to as second providers, and providers capable of generating ordinary identity verification being referred to as third providers. Generally, the first provider may include some authoritative institutions with real-name verification capabilities.

[0044] The user of the identity certificate can apply for ordinary identity certificate, real-person identity certificate and / or real-name identity certificate according to actual needs.

[0045] It should be noted that before applying for real-name identity verification, you need to hold a real-name identity certificate. Accordingly, when authorizing real-name identity verification, you need to authorize both the real-name identity certificate and the real-name identity certificate to the verification party.

[0046] Returning to FIG. 2 , the above-mentioned blockchain-based identity authentication method may include the following steps 210 to 240 .

[0047] 210. Send a first request for real-person identity proof to a first provider in the blockchain, where the first request includes the decentralized digital identity of the user; so that the first provider can perform real-person verification on the user, and after the real-person verification is passed, generate a real-person identity proof based on the decentralized digital identity of the user and the identity information of the user obtained during the real-person verification process.

[0048] During implementation, the user can apply for real-person identity proof from the first provider. After obtaining the user's DID, the first provider can verify the user's real person.

[0049] Specifically, the real-person verification may include collecting the identity information of the user and determining whether the user corresponding to the DID is the user himself based on the identity information.

[0050] The identity information may include but is not limited to name, ID number, biometric features, etc.

[0051] The biological features involved in the biometric identification may include, for example, eye features, voiceprints, fingerprints, palm prints, heartbeat, pulse, chromosomes, DNA, bite marks, etc. Eye prints may include iris, sclera and other biological features.

[0052] When the first provider compares the collected identity information with the identity information reserved by the user and they are consistent, it is determined that the real person verification is successful.

[0053] Furthermore, after the real-person verification is passed, a real-person identity certificate is generated based on the user's DID and the (full or partial) identity information of the user obtained during the real-person verification process.

[0054] In the present invention, a level field is introduced into the format of the traditional identity certificate, so that the identity certificate issued by the blockchain provider is provided with a level field indicating the type of identity certificate;

[0055] The field value of the level field includes a first field value for representing real-person identity proof, a second field value for representing real-name identity proof, and a third field value for representing ordinary identity proof.

[0056] The real person identity proof, real name identity proof and common identity proof may all include, for example, verifiable claims or verifiable credentials (VC). In addition to the endorsed identity information, the verifiable credential may also include a digital signature of the provider of the identity proof.

[0057] For real-person identity proof, it can be expressed as the first provider's endorsement of certain identity information of the user.

[0058] Generally, the format of identity proof may refer to existing standards, such as W3C (World Wide Web Consortium) standards.

[0059] According to the W3C standard, the fields and meanings of the identity certificate can be as follows: the "issuer" field indicates the DID of the provider corresponding to this VC; the "issuanceDate" field indicates the generation time of this VC;

[0060] The "VCID" field indicates the identification ID of the current VC; the "SubjectDID" field indicates the user of this VC; the "values" field indicates the identity information of the user endorsing this VC; and the "proof" field indicates the digital signature of the provider that generated this VC.

[0061] The data structure diagram of the extended real-person identity certification and real-name identity certification of the present invention is shown below in conjunction with FIG. 4 .

[0062] Taking the real-person identity certificate (real-person VC) shown in the upper part of Figure 4 as an example, the level field is extended on the basis of the traditional VC format of the W3C standard; according to the level field, it can be known that this VC is a real-person VC; according to other fields, it can be known that the identifier of this real-person VC is "VC001ID", which is generated by the first provider of "DID002" and provided to the user of "DID001" for use; the endorsed identity information is "{Name: Zhang San; ID number: 112334466}", and the signature string digitally signed by the first provider of "DID002" is "xx001".

[0063] 220. Store the real-person identity certificate issued by the first provider; wherein the real-person identity certificate is digitally signed by the first provider using the locally stored first identity private key.

[0064] After obtaining the real-person identity certificate issued by the first provider, the user can store it locally. This real-person identity certificate can be digitally signed by the first provider using the locally stored first identity private key. For example, in Figure 4, the signature string "xx001" in the "proof" field of the real-person VC is the result of the first provider's digital signature.

[0065] 230. Send a second request for real-name identity proof to a second provider in the blockchain, where the second request includes the user's decentralized digital identity and the real-person identity proof; so that the second provider verifies the real-person identity proof and generates a real-name identity proof based on the user's decentralized digital identity and the real-person identity proof after the verification is passed.

[0066] After the user successfully applies for real-person identity verification, he or she can further apply for real-name identity verification.

[0067] During implementation, the user can apply for real-person identity verification from the second provider and send the user's DID along with the previously requested real-person identity verification to the second provider. After obtaining the user's real-person identity verification, the second provider can verify the real-person identity verification to confirm its authenticity.

[0068] Since the real person identity certificate is digitally signed by the first provider using the first identity private key, the first identity public key corresponding to the first identity private key can be used to verify the signature of the real person identity certificate.

[0069] If the signature verification is successful, it means that the real-person identity certificate is indeed generated and digitally signed by the first provider. Based on the credit of the first provider, it can be considered that the identity information in the real-person identity certificate is also true and valid.

[0070] After the signature verification is passed, the second provider can generate a real-name identity certificate based on the user's decentralized digital identity and the real-person identity certificate.

[0071] Similar to the real-person identity verification, a level field is also added to the real-name identity verification, but the field value of the level field is the second field value (indicating real-name identity verification).

[0072] Furthermore, in some embodiments, the real-name identity certificate is also provided with an associated field indicating an associated real-person identity certificate; the associated real-person identity certificate refers to the real-person identity certificate that has passed the signature verification before the second provider issues the real-name identity certificate.

[0073] Referring to Figure 4 again, taking the real-name identity certificate (real-name VC) shown in the lower part of Figure 4 as an example, according to the level field, it can be known that this VC is a real-name VC, and according to the association field, it can be known that the associated "VC001ID" is a real-person VC (that is, the real-person VC in the upper part of Figure 4); according to other fields, it can be known that the identifier of this real-name VC is "VC002ID", which is generated by the second provider of "DID003" and provided to the user of "DID001" for use; the endorsed identity information is "{business type: XX}", and the signature string digitally signed by the second provider of "DID003" is "xx002".

[0074] By adding an associated field to the real-name identity certificate, the real-person identity certificate submitted when applying for the real-name identity certificate can be traced back.

[0075] 240. Store the real-name identity certificate issued by the second provider; wherein the real-name identity certificate is digitally signed by the second provider using the second identity private key stored locally.

[0076] After obtaining the real-name identity proof issued by the second provider, the user can store it locally. This real-name identity proof can be digitally signed by the second provider using the locally stored second identity private key. For example, in Figure 4, the signature string "xx002" in the "proof" field of the real-name VC is the result of the second provider's digital signature.

[0077] It should be noted that the first provider and the second provider shown in the present invention are different providers. In actual applications, the first provider and the second provider may also be the same provider.

[0078] Through the above embodiments, the level field is introduced into the traditional identity verification format, thereby expanding the different types of identity verification, specifically expanding to real-person identity verification and real-name identity verification. In this way, in scenarios where real-name verification is required, the combination of real-name and real-person identity verification can ensure that the user's identity verification has been verified by real name. In scenarios where real-name verification is not required, traditional identity verification (without real-name verification) can still be used.

[0079] For scenarios where real names are required, further, in some embodiments, it also includes: initiating an authorization request for identity proof to the verifier in the blockchain; wherein the authorization request includes the real-person identity proof and real-name identity proof of the user; so that the verifier verifies the real-person identity proof and real-name identity proof.

[0080] During implementation, since both the real-person identity proof and the real-name identity proof are digitally signed, the verifier needs to verify the signatures of the real-person identity proof and the real-name identity proof authorized by the user to confirm their authenticity. The specific details of the verification process will be described in the subsequent embodiment related to Figure 5.

[0081] Furthermore, in some embodiments, the real-person identity certificate and real-name identity certificate in the authorization request are encrypted by the user using the third identity public key of the verification method stored in the blockchain; the verifier verifies the real-person identity certificate and real-name identity certificate, including: the verifier uses the locally stored third identity private key to decrypt the encrypted real-person identity certificate and real-name identity certificate to obtain the plaintext real-person identity certificate and real-name identity certificate; queries the first identity public key stored by the first provider and the second identity public key stored by the second provider from the blockchain; verifies the digital signature of the real-person identity certificate based on the first identity public key, and verifies the digital signature of the real-name identity certificate based on the second identity public key; after the digital signatures of the real-person identity certificate and the real-name identity certificate are both verified and passed, it is determined that the identity authentication for the user is passed.

[0082] During implementation, since the real-person identity verification and real-name identity verification are encrypted by the user, the verifier needs to decrypt the encrypted real-person identity verification and real-name identity verification to obtain the plaintext real-person identity verification and real-name identity verification. The specific details of encryption and decryption will be described in the subsequent embodiment related to Figure 5.

[0083] In addition to Figure 2, Figure 5 of the present invention exemplarily shows a flow chart of another blockchain-based identity authentication method of the present invention in one embodiment, which can be applied to the verification party in the blockchain.

[0084] As shown in FIG5 , the above-mentioned blockchain-based identity authentication method may include the following steps 510 to 540 .

[0085] 510: Receive an authorization request for identity proof initiated by a user in the blockchain; wherein the authorization request includes the real-person identity proof and real-name identity proof of the user; the real-person identity proof is an identity proof digitally signed by the first provider in the blockchain using the locally stored first identity private key after the real-person verification of the user is passed; the real-name identity proof is an identity proof digitally signed by the second provider in the blockchain using the locally stored second identity private key after the signature verification of the real-person identity proof is passed.

[0086] In actual applications, some services require the user to prove his or her identity. This requires the user to authorize the verification party to verify the identity so that the verification party can verify the identity proof and provide relevant services or perform relevant business operations for the user after the verification is passed (indicating that the user's identity is authentic).

[0087] In scenarios where real-name verification is required, the user is required to provide the verification party with proof of both the user's real-person identity and real-name identity.

[0088] Regarding real-person identity proof and real-name identity proof, reference can be made to the aforementioned embodiments. For example, in some embodiments, the identity proof issued by the provider is provided with a level field indicating the type of identity proof; the field value of the level field includes a first field value for indicating real-person identity proof, a second field value for indicating real-name identity proof, and a third field value for indicating ordinary identity proof.

[0089] In some embodiments, the real-name identity certificate is further provided with an associated field indicating an associated real-person identity certificate; the associated real-person identity certificate refers to the real-person identity certificate that has passed the signature verification before the second provider issues the real-name identity certificate.

[0090] For specific relevant technical details, please refer to the aforementioned embodiments and will not be repeated here.

[0091] 520: In response to the authorization request, query the first identity public key stored by the first provider and the second identity public key stored by the second provider from the blockchain.

[0092] 530: Verify the digital signature of the real-person identity certificate based on the first identity public key, and verify the digital signature of the real-name identity certificate based on the second identity public key.

[0093] Since both the real-person identity certificate and the real-name identity certificate are digitally signed, the verifier needs to verify the signatures of the real-person identity certificate and the real-name identity certificate authorized by the user to confirm the authenticity of the real-person identity certificate and the real-name identity certificate.

[0094] In the present invention, the provider, user and verifier can all store the public key associated with their own DID in the blockchain, while the private key corresponding to the public key is stored locally by the blockchain member.

[0095] During implementation, the verifier can query the first identity public key stored by the first provider and the second identity public key stored by the second provider from the blockchain; and verify the digital signature of the real-person identity certificate based on the first identity public key, and verify the digital signature of the real-name identity certificate based on the second identity public key.

[0096] 540: After the digital signatures of the real-person identity certificate and the real-name identity certificate are both verified, it is determined that the identity authentication of the user is successful.

[0097] If the digital signatures of the real-person identity certificate and the real-name identity certificate are both verified, it means that the real-person identity certificate is indeed generated by the first provider and the real-name identity certificate is indeed generated by the second provider; then based on the credit of the first provider and the second provider, it can be considered that the real-person identity certificate and the real-name identity certificate are both authentic, and further prove that the identity of the user is also real and credible; in this way, it can be determined that the identity authentication of the user is passed.

[0098] Through the above embodiments, the level field is introduced into the traditional identity verification format, thereby expanding the different types of identity verification, specifically expanding to real-person identity verification and real-name identity verification. In this way, in scenarios where real-name verification is required, the combination of real-name and real-person identity verification can ensure that the user's identity verification has been verified by real name. In scenarios where real-name verification is not required, traditional identity verification (without real-name verification) can still be used.

[0099] Furthermore, in some embodiments, after determining that the identity authentication for the user is passed, it also includes: obtaining the identity information in the plain text real-person identity certificate and the business information in the real-name identity certificate; and performing relevant business operations based on the identity information and business information.

[0100] Taking Figure 4 as an example, the real-person identity proof includes the user's identity information {Name: Zhang San; ID Number: 112334466}, and the real-name identity proof includes the business type: XX; assuming that "XX" is a phone bill query and the verifier is a telecommunications operator, then after confirming that the user's identity authentication is successful, the verifier can query the phone bill of the user "Zhang San, ID Number 112334466" and return the queried phone bill to the user.

[0101] Through the above embodiments, real-person identity proof and real-name identity proof can not only realize the real-name authentication requirements of the real-name scenario, but also use the relevant information in the real-person identity proof and real-name identity proof to perform related business operations in the scenario, and feedback the business operation results to the user; thereby completing the complete process of the related business.

[0102] Furthermore, in some embodiments, the real-person identity certificate and real-name identity certificate in the authorization request are encrypted by the user using the third identity public key of the verification method stored in the blockchain; before querying the first identity public key stored by the first provider and the second identity public key stored by the second provider from the blockchain, it also includes: using the locally stored third identity private key to decrypt the encrypted real-person identity certificate and real-name identity certificate to obtain the plaintext real-person identity certificate and real-name identity certificate.

[0103] In actual applications, due to the risk of data leakage during data transmission, the user can encrypt the real-person identity certificate and real-name identity certificate sent to the verifier.

[0104] The specific encryption processing process can be shown as follows: As mentioned above, the provider, user and verifier can all store the public key associated with their own DID in the blockchain, while the private key corresponding to the public key is stored locally by the blockchain member.

[0105] The user can query the third-party identity public key corresponding to the verifier's DID from the blockchain; and encrypt the real-person identity certificate and real-name identity certificate based on the third-party identity public key, and encrypt the encrypted real-person identity certificate and real-name identity certificate and send them to the verifier.

[0106] After receiving the encrypted real-person identity certificate and real-name identity certificate, the verifier can decrypt them based on the locally stored third-party identity private key to obtain the plaintext real-person identity certificate and real-name identity certificate.

[0107] According to the above embodiment, since the real-person identity certificate and the real-name identity certificate are encrypted, even if the real-person identity certificate and the real-name identity certificate are intercepted by other third parties, without the third-party private key for decryption, the plaintext real-person identity certificate and the real-name identity certificate cannot be obtained. Therefore, data security can be effectively guaranteed.

[0108] Corresponding to the aforementioned blockchain-based identity authentication method embodiment, the present invention also provides an embodiment of a blockchain-based identity authentication device.

[0109] Please refer to FIG6 , which is a block diagram of a blockchain-based identity authentication device according to the present invention. The device corresponds to the embodiment shown in FIG5 . The device can be applied to verify identity proof in a decentralized digital identity blockchain. The blockchain stores public keys associated with decentralized digital identities uploaded by each blockchain member. The blockchain members include a provider of identity proof, a user of identity proof, and a verifier of identity proof; the device includes: a receiving module 610 for receiving an authorization request for identity proof initiated by a user in the blockchain; wherein the authorization request includes the user's real-person identity proof and real-name identity proof; the real-person identity proof is an identity proof digitally signed by a first provider in the blockchain using a locally stored first identity private key after the user has passed real-person verification; the real-name identity proof is an identity proof digitally signed by a second provider in the blockchain using a locally stored second identity private key after the real-person identity proof has passed signature verification; a query module 620 for querying the blockchain for a first identity public key stored by the first provider and a second identity public key stored by the second provider; a signature verification module 630 for verifying the digital signature of the real-person identity proof based on the first identity public key and the digital signature of the real-name identity proof based on the second identity public key; and a determination module 640 for determining that the identity authentication of the user has succeeded after both the real-person identity proof and the digital signature of the real-name identity proof have passed signature verification.

[0110] Furthermore, in some embodiments, the identity certificate issued by the provider is provided with a level field indicating the type of identity certificate; the field value of the level field includes a first field value for indicating real-person identity certificate, a second field value for indicating real-name identity certificate, and a third field value for indicating ordinary identity certificate.

[0111] Furthermore, in some embodiments, the real-name identity certificate is also provided with an associated field indicating an associated real-person identity certificate; the associated real-person identity certificate refers to the real-person identity certificate that has passed the signature verification before the second provider issues the real-name identity certificate.

[0112] Furthermore, in some embodiments, the real-person identity certificate and real-name identity certificate in the authorization request are encrypted by the user using the third identity public key of the verification method stored in the blockchain; before the query module 620, it also includes: a decryption module, which is used to use the locally stored third identity private key to decrypt the encrypted real-person identity certificate and real-name identity certificate to obtain the plaintext real-person identity certificate and real-name identity certificate.

[0113] Furthermore, in some embodiments, after the determination module 640, it also includes: an execution module for obtaining the identity information in the plain text real-name identity certificate and the business information in the real-name identity certificate; and performing relevant business operations based on the identity information and business information.

[0114] Please refer to Figure 7, which is a module diagram of the blockchain-based identity authentication device shown in the present invention. The device corresponds to the embodiment shown in Figure 2. The device can be applied to the user of the identity certificate in the blockchain of decentralized digital identity. The blockchain stores the identity public key associated with the decentralized digital identity uploaded by each blockchain member; the blockchain members include the provider of the identity certificate, the user of the identity certificate and the verifier of the identity certificate; the device includes: a first application module 710, which is used to send a first request for real-person identity certification to the first provider in the blockchain, wherein the first request includes the decentralized digital identity of the user; so that the first provider performs real-person verification on the user, and after the real-person verification is passed, generates a real-person identity certificate based on the decentralized digital identity of the user and the identity information of the user obtained during the real-person verification process. A real-name identity certificate is formed; a first storage module 720 is used to store the real-name identity certificate issued by the first provider; wherein the real-name identity certificate is digitally signed by the first provider using the locally stored first identity private key; a second application module 730 is used to send a second request for applying for real-name identity certificate to the second provider in the blockchain, wherein the second request includes the decentralized digital identity of the user and the real-name identity certificate; so that the second provider verifies the real-name identity certificate and generates a real-name identity certificate based on the decentralized digital identity of the user and the real-name identity certificate after the verification is passed; a second storage module 740 is used to store the real-name identity certificate issued by the second provider; wherein the real-name identity certificate is digitally signed by the second provider using the locally stored second identity private key.

[0115] Furthermore, in some embodiments, it also includes: an authorization module, which is used to initiate an authorization request for identity proof to the verifier in the blockchain; wherein the authorization request includes the real-person identity proof and real-name identity proof of the user; so that the verifier can verify the real-person identity proof and real-name identity proof.

[0116] Furthermore, in some embodiments, the identity certificate issued by the provider of the blockchain is provided with a level field indicating the type of identity certificate; the field value of the level field includes a first field value for indicating real-person identity certificate, a second field value for indicating real-name identity certificate, and a third field value for indicating ordinary identity certificate.

[0117] Furthermore, in some embodiments, the real-name identity certificate is also provided with an associated field indicating an associated real-person identity certificate; the associated real-person identity certificate refers to the real-person identity certificate that has passed the signature verification before the second provider issues the real-name identity certificate.

[0118] Furthermore, in some embodiments, the real-person identity certificate and real-name identity certificate in the authorization request are encrypted by the user using the third identity public key of the verification method stored in the blockchain; the verifier in the second application module 730 verifies the real-person identity certificate and real-name identity certificate, further including: the verifier uses the locally stored third identity private key to decrypt the encrypted real-person identity certificate and real-name identity certificate to obtain the plaintext real-person identity certificate and real-name identity certificate; queries the first identity public key stored by the first provider and the second identity public key stored by the second provider from the blockchain; verifies the digital signature of the real-person identity certificate based on the first identity public key, and verifies the digital signature of the real-name identity certificate based on the second identity public key; after the digital signatures of the real-person identity certificate and the real-name identity certificate are verified, it is determined that the identity authentication for the user is passed.

[0119] The implementation process of the functions and effects of each module in the above-mentioned device is specifically described in the implementation process of the corresponding steps in the above-mentioned method, and will not be repeated here.

[0120] For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to the partial description of the method embodiments. The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the present invention. A person of ordinary skill in the art can understand and implement the present invention without inventive work.

[0121] The internal functional modules and structural diagram of the blockchain-based identity authentication device described above may actually be an electronic device, including: a processor; a memory for storing processor-executable instructions; wherein the processor is configured to execute any of the above-mentioned embodiments of the blockchain-based identity authentication method.

[0122] In the embodiment of the above-mentioned electronic device, it should be understood that the processor can be a processing unit (Central Processing Unit, abbreviated as: CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), etc. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc., and the aforementioned memory can be a read-only memory (ROM), a random access memory (RAM), a flash memory, a hard disk or a solid-state drive. The steps of the method disclosed in the embodiment of the present invention can be directly embodied as being executed by a hardware processor, or can be executed by a combination of hardware and software modules in the processor.

[0123] In addition, the present invention also provides a computer-readable storage medium. When the instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device can execute any of the above-mentioned embodiments of the blockchain-based identity authentication method.

[0124] It should be noted that the above examples are merely specific embodiments of the present invention. Obviously, the present invention is not limited to the above examples, and many similar variations are possible. All variations directly derived from or associating with the present invention by those skilled in the art are intended to fall within the scope of protection of the present invention.

Claims

1. A blockchain-based identity authentication method, applied to the verification party of identity proof in a decentralized digital identity blockchain, wherein the blockchain stores the identity public key associated with the decentralized digital identity uploaded by each blockchain member; The blockchain members include a provider of identity proof, a user of identity proof and a verifier of identity proof; the method includes: Receive an authorization request for identity proof initiated by a user in the blockchain; wherein the authorization request includes the real-person identity proof and real-name identity proof of the user; the real-person identity proof is an identity proof digitally signed by the first provider in the blockchain using the locally stored first identity private key after the real-person verification of the user is passed; the real-name identity proof is an identity proof digitally signed by the second provider in the blockchain using the locally stored second identity private key after the signature verification of the real-person identity proof is passed; In response to the authorization request, querying the first identity public key stored by the first provider and the second identity public key stored by the second provider from the blockchain; Verify the digital signature of the real-person identity certificate based on the first identity public key, and verify the digital signature of the real-name identity certificate based on the second identity public key; After the digital signatures of the real-person identity certificate and the real-name identity certificate are both verified, it is determined that the identity authentication for the user is successful.

2. The blockchain-based identity authentication method according to claim 1, wherein the identity certificate issued by the provider is provided with a level field indicating the type of identity certificate; The field value of the level field includes a first field value for representing real-person identity proof, a second field value for representing real-name identity proof, and a third field value for representing ordinary identity proof.

3. In the blockchain-based identity authentication method as described in claim 2, the real-name identity certificate is also provided with an associated field representing the associated real-person identity certificate; the associated real-person identity certificate refers to the real-person identity certificate that has passed the signature verification before the second provider issues the real-name identity certificate.

4. The blockchain-based identity authentication method according to claim 1, wherein the real person identity certificate and the real name identity certificate in the authorization request are encrypted by the user using the third identity public key of the verification method stored in the blockchain; Before querying the first identity public key stored by the first provider and the second identity public key stored by the second provider from the blockchain, the method further includes: The encrypted real-person identity certificate and real-name identity certificate are decrypted using a locally stored third identity private key to obtain the real-person identity certificate and real-name identity certificate in plain text.

5. The blockchain-based identity authentication method according to claim 4, after determining that the identity authentication for the user is passed, further comprising: Obtaining identity information in the plain text real-name identity certificate and business information in the real-name identity certificate; Perform relevant business operations based on the identity information and business information.

6. A blockchain-based identity authentication method, applied to a user of identity proof in a decentralized digital identity blockchain, wherein the blockchain stores identity public keys associated with decentralized digital identities uploaded by respective blockchain members; the blockchain members include a provider of identity proof, a user of identity proof, and a verifier of identity proof; the method comprises: Sending a first request for applying for real-person identity proof to a first provider in the blockchain, wherein the first request includes the decentralized digital identity of the user; so that the first provider verifies the real-person identity of the user, and after the real-person verification is passed, generates a real-person identity proof based on the decentralized digital identity of the user and the identity information of the user obtained during the real-person verification process; Storing the real person identity certificate issued by the first provider; wherein the real person identity certificate is digitally signed by the first provider using the first identity private key stored locally; Sending a second request for applying for real-name identity proof to a second provider in the blockchain, wherein the second request includes the decentralized digital identity of the user and the real-person identity proof; so that the second provider verifies the real-person identity proof and generates a real-name identity proof based on the decentralized digital identity of the user and the real-person identity proof after the verification; The real-name identity certificate issued by the second provider is stored; wherein the real-name identity certificate is digitally signed by the second provider using the second identity private key stored locally.

7. The blockchain-based identity authentication method according to claim 6, further comprising: Initiate an authorization request for identity proof to the verifier in the blockchain; wherein the authorization request includes the real-person identity proof and real-name identity proof of the user; so that the verifier can verify the real-person identity proof and real-name identity proof.

8. The blockchain-based identity authentication method according to claim 6, wherein the identity certificate issued by the blockchain provider is provided with a level field indicating the type of identity certificate; The field value of the level field includes a first field value for representing real-person identity proof, a second field value for representing real-name identity proof, and a third field value for representing ordinary identity proof.

9. According to the blockchain-based identity authentication method as described in claim 8, the real-name identity certificate is also provided with an associated field representing the associated real-person identity certificate; the associated real-person identity certificate refers to the real-person identity certificate that has passed the signature verification before the second provider issues the real-name identity certificate.

10. The blockchain-based identity authentication method according to claim 7, wherein the real person identity certificate and the real name identity certificate in the authorization request are encrypted by the user using the third identity public key of the verification method stored in the blockchain; The verification party verifies the real person identity certificate and the real name identity certificate, including: The verifier uses a locally stored third identity private key to decrypt the encrypted real-person identity certificate and real-name identity certificate to obtain plain text real-person identity certificate and real-name identity certificate; queries the first identity public key stored by the first provider and the second identity public key stored by the second provider from the blockchain; verifies the digital signature of the real-person identity certificate based on the first identity public key, and verifies the digital signature of the real-name identity certificate based on the second identity public key; after the digital signatures of the real-person identity certificate and the real-name identity certificate are verified, it is determined that the identity authentication for the user is passed.

11. A blockchain-based identity authentication device, applied to the verification party of identity proof in a decentralized digital identity blockchain, wherein the blockchain stores the identity public key associated with the decentralized digital identity uploaded by each blockchain member; The blockchain members include a provider of identity proof, a user of identity proof and a verifier of identity proof; the device includes: A receiving module, configured to receive an authorization request for identity proof initiated by a user in a blockchain; wherein the authorization request includes the real-person identity proof and the real-name identity proof of the user; the real-person identity proof is an identity proof digitally signed by a first provider in the blockchain after the real-person verification of the user is passed, using a locally stored first identity private key; the real-name identity proof is an identity proof digitally signed by a second provider in the blockchain after the real-person identity proof is verified and passed, using a locally stored second identity private key; A query module, used to query the first identity public key stored by the first provider and the second identity public key stored by the second provider from the blockchain; A signature verification module, configured to verify the digital signature of the real-person identity certificate based on the first identity public key, and to verify the digital signature of the real-name identity certificate based on the second identity public key; The determination module is used to determine that the identity authentication of the user has passed after the digital signatures of the real-person identity certificate and the real-name identity certificate have been verified.

12. A blockchain-based identity authentication device, applied to a user of identity certification in a decentralized digital identity blockchain, wherein the blockchain stores identity public keys associated with decentralized digital identities uploaded by respective blockchain members; The blockchain members include a provider of identity proof, a user of identity proof and a verifier of identity proof; the device includes: The first application module is used to send a first request for applying for real-person identity proof to a first provider in the blockchain, wherein the first request includes the decentralized digital identity of the user; so that the first provider can verify the real person of the user, and after the real person verification is passed, the decentralized digital identity and real person verification of the user are verified. The identity information of the user obtained during the process generates a real person identity certificate; A first storage module is used to store the real person identity certificate issued by the first provider; wherein the real person identity certificate is digitally signed by the first provider using a locally stored first identity private key; A second application module is used to send a second request for applying for real-name identity proof to a second provider in the blockchain, wherein the second request includes the decentralized digital identity of the user and the real-person identity proof; so that the second provider verifies the real-person identity proof and generates a real-name identity proof based on the decentralized digital identity of the user and the real-person identity proof after the verification is passed; The second storage module is used to store the real-name identity certificate issued by the second provider; wherein the real-name identity certificate is digitally signed by the second provider using the second identity private key stored locally.

13. A computer-readable storage medium, wherein the storage medium stores a computer program, wherein the computer program, when executed by a processor, implements the method according to any one of claims 1 to 10.

14. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method according to any one of claims 1 to 10 when executing the program.

Citation Information

Patent Citations

  • Real-name authentication method and system based on blockchain

    CN107682378A

  • Identity authentication method, device and system, equipment and readable storage medium

    CN109829273A

  • Identity recognition and verification method and system based on block chain wallet

    CN113487321A

  • Identity authentication method and device based on block chain

    CN116662950A

  • System and method for verifying verifiable claims

    US20200127845A1