IDENTITY AUTHENTICATION METHOD, ELECTRONIC DEVICE, AND COMPUTER-READABLE STORAGE MEDIUM
The identity authentication method using Merkle Roof verification paths and blockchain technology allows users to selectively disclose attributes, enhancing privacy protection and security in identity verification processes.
Patent Information
- Application Number
- JP2024531379
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2021-12-02
- Filing Date
- 2022-11-30
- Publication Date
- 2024-11-19
- Estimated Expiration
- 2042-11-30
AI Technical Summary
Current identity verification methods expose users to significant risks of privacy information leakage and lack adequate protection for personal data security.
An identity authentication method utilizing a Merkle Roof verification path, where users select which attributes to disclose, generating an identity certificate with a simulated verification path that only reveals chosen attributes, and employing blockchain-based Merkle tree verification technology for secure authentication.
Enhances privacy protection by minimizing the disclosure of sensitive information while ensuring accurate and efficient identity verification through Merkle tree fast verification technology.
Smart Images

Figure 2024543166000001_ABST
Abstract
Description
[Technical field]
[0001] [CROSS REFERENCE TO RELATED APPLICATIONS] This application claims priority to Chinese patent application CN202111459938.6, filed on December 2, 2021, entitled "Identity authentication method, electronic device, and computer-readable storage medium," the entire contents of which are incorporated herein by reference.
[0002] [Technical field] TECHNICAL FIELD The embodiments of the present application relate to the field of information security authentication technology, and in particular to an identity authentication method, an electronic device, and a computer-readable storage medium. [Background technology]
[0003] As people's activities on the Internet become more and more frequent, the prerequisite for using Internet services is to solve the identity identification problem. Current identity authentication methods are simple, and there is a great risk of privacy information being leaked and hidden, and user information may be sold, causing significant property and related profit losses. How to solve the privacy protection problem of personal information data is the main challenge facing current digital identity authentication technology. Summary of the Invention [Problem to be solved by the invention]
[0004] The embodiments of the present application provide an identity authentication method, an electronic device, and a computer-readable storage medium, thereby reducing the risk of personal privacy information being leaked and improving the security of personal privacy data. [Means for solving the problem]
[0005] An embodiment of the present application provides an identity authentication method, including the steps of: obtaining a user's identity certificate, the identity certificate including identity attributes of the user and a Merkle Roof verification path, the Merkle Roof verification path in the identity certificate being a verification path obtained based on identity attributes selected by the user to be made public when generating the identity certificate; simulating a Merkle Roof verification path based on the identity attributes made public in the identity certificate; and authenticating the user's identity certificate based on the simulated verification path and the verification path in the identity certificate.
[0006] An embodiment of the present application further provides an electronic device including at least one processor and a memory communicatively connected to the at least one processor, the memory storing instructions executable by the at least one processor, and the instructions being executed by the at least one processor to enable the at least one processor to perform the above-mentioned identity authentication method.
[0007] An embodiment of the present application further provides a computer-readable storage medium storing a computer program which, when executed by a processor, implements the above identity authentication method. [Brief description of the drawings]
[0008] [Figure 1] 1 is a flowchart of an identity authentication method according to an embodiment of the present application; [Diagram 2] FIG. 2 is a schematic diagram of a graphical identity certificate according to an embodiment of the present application; [Diagram 3] FIG. 2 is a schematic diagram of a Merkle tree constructed according to an embodiment of the present application; [Figure 4] FIG. 2 is a schematic diagram of simulating a verification path based on published identity attributes according to an embodiment of the present application; [Diagram 5] 2 is a flow chart of a method for generating an identity certificate according to an embodiment of the present application; [Figure 6] FIG. 2 is a schematic diagram of employment evidence in graphical form according to an embodiment of the present application. [Figure 7] FIG. 1 is a schematic diagram of a distributed service-oriented software architecture according to an embodiment of the present application. [Figure 8] 1 is a flowchart of a model registration flow according to an embodiment of the present application. [Figure 9] 1 is a flowchart of an identity registration flow according to an embodiment of the present application. [Figure 10] 2 is a flow chart of an identity proof application flow according to an embodiment of the present application. [Figure 11] 1 is a flow chart of an identity certificate generation flow according to an embodiment of the present application; [Figure 12] 2 is a flowchart of an identity certificate examination flow according to an embodiment of the present application. [Figure 13] 1 is a structural schematic diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0009] In order to clarify the objectives, technical solutions and advantages of the embodiments of the present application, the embodiments of the present application will be described in detail below with reference to the drawings. However, as will be understood by those skilled in the art, many technical details are provided in the embodiments of the present application to allow the reader to better understand the embodiments of the present application. However, the technical solutions claimed to be protected by the embodiments of the present application can be realized without these technical details and various changes and modifications based on the following embodiments. The division of the following embodiments is for ease of explanation and does not limit the specific implementation of the embodiments of the present application, and the embodiments can be combined and referenced with each other on the premise that there is no contradiction.
[0010] In order to facilitate understanding of the embodiments of the present application, the following first describes related art to the embodiments of the present application.
[0011] Digital identity is the condensation of real identity information into public / private key in the form of digital code, so as to bind, query and verify personal real-time behavior information. Digital identity not only includes identity coding information such as birth information, individual description, biometric characteristics, etc., but also relates to personal behavior information with multiple attributes. The core of digital identity is digital evidence. With the development of digital identity into centralized, alliance and self-sovereign identity, the latest evolution direction of digital evidence is verifiable evidence.
[0012] Merkler Tree is an important technology for transaction and storage in blockchain blocks, and its role is to quickly compile and check the existence and completeness of block data. That is, even if you don't need to know the whole tree, you can check a single tree node. Merkler Tree's rapid verification technology is widely used to verify the validity of blockchain block transactions.
[0013] An embodiment of the present application provides an identity authentication method applied to an identity authentication side, where the identity authentication side may be an electronic device, such as a terminal, used by the authentication side, and the identity authentication side may also be understood as an identity examination side, and is abbreviated as examination side. The identity authentication method in this embodiment can be used in a public cloud Internet environment, and can also be used in a private cloud environment of a user enterprise. The system adopts a mode combining a server side and a terminal, where a digital identity service is mainly deployed on the server side, and an application APP is mainly deployed on the terminal, and the application APP may include two types of role views, namely, a use side user and an examination side user, and the two types of role views can be understood as user interfaces of two different roles. The user interface of the use side user mainly relates to operations such as registration, evidence application, and certificate generation, and the user interface of the examination side user mainly relates to performing a verification operation on the identity certificate presented to the user. The server side and the terminal can perform network communication through HTTP (Hyper Text Transfer Protocol). The flowchart of the identity authentication method in this embodiment can be referred to in FIG. 1, Step 101: obtaining a user's identity certificate, the identity certificate including the user's identity attributes and a Merkle Roof verification path, the identity attributes in the identity certificate including published identity attributes and unpublished identity attributes, and the Merkle Roof verification path in the identity certificate is a verification path obtained based on the identity attributes to be published selected by the user when generating the identity certificate; a step 102 of simulating a Merkle Roof verification path based on the identity attributes published in the identity certificate; and step 103 of authenticating the user's identity certificate based on the simulated validation path and the validation path in the identity certificate.
[0014] In the embodiment of the present application, when identity authentication is performed, the identity authentication can be completed based on the identity attributes that the user selects to be made public, and the identity attributes that the user does not want to make public can be set as the identity attributes that are not made public, which is advantageous to avoid the leakage of the identity attributes that the user does not want to make public. That is, in the embodiment of the present application, the identity authentication can be completed by only making public a small number of identity attributes, thereby avoiding the problem of the leakage of the user's privacy information. This solves the security problem that the traditional digital identity authentication method (e.g., all identity attributes need to be made public) is inferior in protecting personal privacy data and there is a possibility of privacy information leakage.
[0015] In step 101, the identity authentication side can obtain the identity certificate presented by the user, and the format of the identity certificate can be a graphic format or a text format. The identity certificate can be an employment certificate, an academic calendar certificate, etc., and the graphic format identity certificate can be referred to in FIG. 2. The identity authentication side can obtain the identity certificate by scanning the identity certificate presented by the user, and obtaining the identity certificate of the user can be understood as obtaining information in the identity certificate. The information in the identity certificate includes the identity attributes of the user and the Merkle Roof verification path, and the identity attributes in the identity certificate include the published identity attributes and the unpublished identity attributes, and the Merkle Roof verification path in the identity certificate is the verification path obtained based on the identity attributes to be published selected by the user when generating the identity certificate. That is, when generating the identity certificate, the user can select the identity attributes to be published as the identity attributes to be published, and the digital identity service can obtain the Merkle Roof verification path, i.e., the Merkle Roof verification path shown in FIG. 2, based on the identity attributes to be published selected by the user.
[0016] Here, the published identity attributes can be understood as the specific contents of the identity attributes known from the identity certificate, for example, the name, telephone number, and mailbox in Fig. 2 are all published identity attributes. The unpublished identity attributes can be understood as the specific contents of the identity attributes not known from the identity certificate, for example, the specific contents of the unpublished identity attributes are blurred, for example, see 2, the job number, department, and job function in Fig. 2 are all unpublished identity attributes.
[0017] In some embodiments, the identity certificate further includes the issuing mechanism of the identity certificate, the issuing mechanism ID, the mechanism signature on the issuing mechanism's Merkle Roof by the issuing mechanism's private key, the issuance time, the user signature on the user's identity certificate by the user's private key, the signature algorithm adopted by the user signature, and the two-dimensional verification code of the working certificate, and the two-dimensional verification code of the working certificate may be a URL (Uniform Resource Locator) generated according to the verification information of the identity certificate, the URL points to the online service address of the digital identity service, and the verification result of whether the identity certificate is valid or not, i.e., the authentication result of whether the authentication is passed or not can be obtained by accessing the URL. Referring to Figure 2, the Merkle Roof signature on the right side of Figure 2 is the mechanism signature on the issuing mechanism's Merkle Roof by the issuing mechanism's private key, and the signature in Figure 2 is the user signature on the user's identity certificate by the user's private key.
[0018] In step 102, the identity authentication party can simulate a Merkle Roof verification path based on the identity attributes published in the identity certificate.
[0019] In one embodiment, simulating the verification path of the Merkle loop includes calculating the hash value of the identity attributes published in the identity certificate based on the identity attributes published in the identity certificate, and simulating the verification path of the Merkle loop based on the hash value of the published identity attributes and the constructed Merkle tree. Here, a schematic diagram of the constructed Merkle tree can be referred to FIG. 3, and the Merkle tree can be constructed based on the identity attributes of the user (for example, name, job number, department, position, phone, mailbox in FIG. 3). In this embodiment, the high-speed verification technology of the Merkle tree can be used to verify multiple identity attributes at one time, and the efficiency is higher.
[0020] In one embodiment, the step of simulating the verification path of the Merkle tree based on the hash value of the published identity attributes and the constructed Merkle tree includes determining the node corresponding to the hash value of the published identity attributes in the L1 layer of the Merkle tree and adding the node to the simulation queue T1 corresponding to the L1 layer; simulating the Merkle tree from bottom to top, sequentially traversing the pair nodes (Hx, Hy) of each layer, and after traversing the pair nodes (Hx, Hy) of each layer, simulating to obtain the verification path of the Merkle loop. Here, the following operations are performed on (Hx, Hy) in the traversed Li layer. If one of the nodes in (Hx, Hy) is included in the simulation queue Ti corresponding to the Li layer, add the hash value of the other node in (Hx, Hy) to the verification path, calculate the hash value of (Hx, Hy), and add the hash value of (Hx, Hy) to the simulation queue Ti+1 corresponding to the Li+1 layer, where 1≤i<deep, and deep is the depth of the Merkle tree. If both of the two nodes in (Hx, Hy) are included in the simulation queue Ti corresponding to the Li layer, calculate the hash value of (Hx, Hy), and add the hash value of (Hx, Hy) to the simulation queue Ti+1 corresponding to the Li+1 layer. If there are no nodes in the simulation queue Ti corresponding to the Li layer at (Hx, Hy), then traverse the next (Hx, Hy).
[0021] To facilitate the understanding of the above simulation process, an example is described below. The number of identity attribute nodes is N, the depth of the Merkle tree is deep = log(N) + 1, the levels of the Merkle tree are denoted as Li (1 ≤ i < deep), where i = 1 starts from the L1 layer. The nodes in the L1 layer define the attribute value Hash of the identity attribute as Hj, and j is the node number (numbered continuously from 1). Referring to Figure 4, the Merkle tree includes L1, L2, and L3 layers. The published identity attributes include D1, D3, and D5, and the unpublished identity attributes include D2, D4, D6, D7, and D8. In the L1 layer of the Merkle tree, it is determined that the nodes corresponding to the Hash values of the published identity attributes include Hl, H3, and H5, and the nodes Hl, H3, and H5 are added to the simulation queue T1 corresponding to the L1 layer.
[0022] Simulate the Merkle tree from bottom to top. First, traverse each pair of nodes (Hx, Hy) in the L1 layer. The pairs of nodes in the L1 layer include (H1, H2), (H3, H4), (H5, H6), and (H7, H8). For the pair of nodes (H1, H2), if the node H1 located in T1 exists, add H2 to the verification path, calculate the Hash value of (H1, H2), that is, H9, and add H9 to the simulation queue T2 corresponding to the L2 layer. For the pair of nodes (H3, H4), if the node H3 located in T1 exists, add H4 to the verification path, calculate the Hash value of (H3, H4), that is, H10, and add H10 to the simulation queue T2 corresponding to the L2 layer. For the pair of nodes (H5, H6), if the node H5 located in T1 exists, add H6 to the verification path, calculate the Hash value of (H5, H6), that is, H11, and add H11 to the simulation queue T2 corresponding to the L2 layer. For the pair node (H7,H8), if there is no node located in T1, skip and start traversing the next (Hx,Hy), and since (H7,H8) is the last pair node in the L1 layer, the skip here refers to start traversing the pair node in the L2 layer. In a specific implementation, if (H7,H8) is not the last pair node in the L1 layer, the skip refers to start traversing the pair node after (H7,H8).
[0023] After traversing each pair node in the L1 layer, it is determined that the simulation queue T2 corresponding to the L2 layer includes H9, H10, and H11, and the verification path includes H2, H4, and H6. Start traversing each pair node in the L2 layer, and the pair nodes in the L2 layer include (H9, H10) and (H11, H12); For the pair node (H9, H10), if both nodes H9 and H10 are located in T2, calculate the hash value of (H9, H10), i.e., H13, and add H13 to the simulation queue T3 corresponding to the L3 layer. For the pair nodes (H11, H12), if node H11 located at T2 exists, H12 is added to the verification path, the hash value of (H11, H12), i.e., H14, is calculated, and H14 is added to the simulation queue T3 corresponding to the L3 layer.
[0024] After traversing each pair node in the L2 layer, it is determined that the simulation queue T3 corresponding to the L3 layer includes H13 and H14, and the verification path includes H2, H4, H6, and H12. Start traversing each pair node in the L3 layer, and the pair nodes in the L3 layer include (H13, H14); For the pair node (H13, H14), if both nodes H13 and H14 are located in T2, calculate the hash value of (H13, H14), i.e., the Merkle Root. Up to this point, each layer of the Merkle tree is traversed, and the final verification path includes H2, H4, H6, and H12.
[0025] In one embodiment, the method of determining the verification path of the identity certificate can also be obtained by referring to the above simulation process. The above simulation method provided in this embodiment makes it easy to obtain an accurate verification path through simulation, and can improve the accuracy and efficiency of identity authentication by verifying multiple undisclosed identity attributes at once.
[0026] In step 103, if the identity authenticator determines that the simulated verification path matches the verification path in the identity certificate, it can decide to pass identity authentication for the user.
[0027] In one embodiment, the identity certificate further includes a verification code of the identity certificate, and the method further includes the steps of: generating a graphic identity certificate according to the identity attributes selected by the user to be made public before obtaining the identity certificate of the user, the verification code of the identity certificate being displayed on the graphic identity certificate; and obtaining the identity authentication result for the user by scanning the verification code in the graphic identity certificate. Here, the verification code may be a URL generated based on the identity certificate, the URL is directed to an online service address of a digital identity service, and the verification result of whether the identity certificate is valid or not can be obtained by accessing the URL. After generating the graphic identity certificate, the identity authentication side can send the generated graphic identity certificate to a terminal used by the user, and when the identity certificate of the user needs to be authenticated, the identity authentication side can scan the graphic identity certificate presented by the user to obtain the identity authentication result. The verification code of the identity certificate may be the two-dimensional verification code in FIG. 2, and the identity authentication side can obtain the identity authentication result for the user by scanning the two-dimensional verification code. The code scanning verification method makes it easy to obtain the authentication result of the identity certificate.
[0028] In one embodiment, the identity certificate further includes the user's digital identity ID and a user signature on the user's identity certificate by the user's private key, and further includes the steps of obtaining the user's identity certificate from the blockchain based on the user's digital identity ID and verifying the user signature by the user's public key after obtaining the user's identity certificate. In step 103, the step of authenticating the user's identity certificate based on the simulated verification path and the verification path in the identity certificate determines that the identity authentication for the user is passed if the simulated verification path matches the verification path in the identity certificate and passes the verification on the user signature.
[0029] In one embodiment, the step of obtaining the user's public key from the blockchain based on the user's digital identity ID includes the steps of obtaining a user profile based on the user's digital identity ID, the user profile being obtained based on the user's identity registration information when performing identity registration for the user, and the user profile being stored in the blockchain; and obtaining the user's public key from the blockchain based on the user profile. The user can perform identity registration in a digital identity service deployed on a server side. The user profile does not include the user's privacy information, and the identity registration information can include the user's personal account, the identity model, the user's digital identity ID, the version of the identity model, and the user's public key. The identity model may be a model for generating an identity certificate created by an issuing mechanism, and the issuing mechanism may create the identity model and then issue it to the blockchain. In this embodiment, combining with the blockchain to associate the issuing mechanism, the user, and the identity authentication side makes it easy for the identity authentication side to obtain the user's public key from the blockchain.
[0030] In one embodiment, the identity certificate further includes a digital identity ID of the issuing institution of the identity certificate and an institution signature on the issuing institution's Merkle roof by the issuing institution's private key, and after obtaining the user's identity certificate, the method further includes obtaining the issuing institution's public key from the blockchain based on the issuing institution's digital identity ID and verifying the institution signature by the issuing institution's public key; and in step 103, authenticating the user's identity certificate based on the simulated verification path and the verification path in the identity certificate includes determining that identity authentication for the user is passed if the simulated verification path matches the verification path in the identity certificate and passes verification against the institution signature.
[0031] In one embodiment, the step of obtaining the public key of the issuing mechanism from the blockchain based on the digital identity ID of the issuing mechanism includes the steps of obtaining a profile of the issuing mechanism based on the digital identity ID of the issuing mechanism, the profile of the issuing mechanism being obtained based on the identity registration information of the issuing mechanism when performing identity registration with the issuing mechanism, and the profile of the issuing mechanism being stored in the blockchain; and obtaining the public key of the issuing mechanism from the blockchain based on the profile of the issuing mechanism. The profile of the issuing mechanism does not include the privacy information of the issuing mechanism, and the registration information of the issuing mechanism may include the mechanism name of the issuing mechanism, the digital identity ID of the issuing mechanism and the public key of the issuing mechanism, etc. Before the issuing mechanism issues an identity model in the blockchain, the issuing mechanism may first perform identity registration in a digital identity service deployed on the server side. In this embodiment, the association of the issuing mechanism, the user and the identity authentication side in combination with the blockchain makes it easy for the identity authentication side to obtain the public key of the issuing mechanism from the blockchain.
[0032] In one embodiment, the identity certificate further includes the user's digital identity ID, the digital identity ID of the issuing mechanism of the identity certificate, the mechanism signature on the issuing mechanism's Merkle roof by the issuing mechanism's private key, and the user signature on the user's identity certificate by the user's private key, and after obtaining the user's identity certificate, the method further includes obtaining the user's public key from the blockchain based on the user's digital identity ID, verifying the user signature by the user's public key, obtaining the issuing mechanism's public key from the blockchain based on the issuing mechanism's digital identity ID, and verifying the mechanism signature by the issuing mechanism's public key. In step 103, authenticating the user's identity certificate based on the simulated verification path and the verification path in the identity certificate includes determining that the identity authentication for the user is passed if the simulated verification path matches the verification path in the identity certificate, and passes the signature verification for the user and passes the signature verification for the mechanism.
[0033] In this embodiment, while verifying the verification path obtained by simulation, the user signature and / or mechanism signature are also verified, which is equivalent to raising the passing conditions for identity authentication and is advantageous in further improving the security of identity authentication.
[0034] In one embodiment, the identity certificate generation method can be seen in FIG. 5 ; determining 501 an identity proof issued to a user, the identity proof including all identity attributes of the user, a Merkle roof of all identity attributes, and an organization signature over the issuing organization's Merkle roof with the issuing organization's private key of the identity proof; Step 502: determining which identity attributes the user wishes to make public from among all identity attributes in the identity evidence; Step 503 of obtaining a verification path based on the identity attributes selected by the user to be made public; The method includes step 504 of generating an identity certificate based on the identity attributes, verification path, and mechanism signature selected by the user to be made public, signing the identity certificate with the user's private key to obtain a user signature, and obtaining an identity certificate including the user signature.
[0035] In this embodiment, in combination with the identity proof issued to the user and the identity attributes the user has selected to be made public, it may be advantageous to generate an identity certificate that makes public only a portion of the user's identity attributes, thereby protecting identity attributes that the user does not want to be leaked.
[0036] In step 50l, the identity evidence may be issued by a digital identity service deployed on the server side, and the identity evidence may be employment evidence, educational evidence, academic degree evidence, identity card, etc., and the issuing institution of the identity evidence is generally an authoritative institution, for example, the issuing institutions of the educational evidence, academic degree evidence, and identity card are all specific institutions stipulated by the state. The form of the identity evidence may be in graphic form or text form, and a schematic diagram of the employment evidence in graphic form can be referred to in FIG. 6, where the employment evidence may include all the identity attributes of the user (e.g., name, job number, department, job, phone, and mailbox in FIG. 6), the Merkle roof of all the identity attributes (e.g., the Merkle roof in the last row on the left side in FIG. 6), and the institution signature on the Merkle roof by the issuing institution's private key of the issuing institution of the identity evidence (e.g., company A in FIG. 6) (the institution signature is, for example, the Merkle roof signature in FIG. 6). Preferably, in some embodiments, the identity evidence may further include an institution ID of the issuing institution, an issuance time of the identity evidence, a signature on the identity evidence by the user's private key and the signature algorithm used for the signature, and an authentication code of the employment evidence. Here, the verification code of the employment evidence may be a URL generated based on the evidence verification information, the URL points to an online service address of a digital identity service, and the verification result of whether the employment evidence is valid can be obtained by accessing the URL. The display order of the identity attributes in the employment evidence may be the position order of the leaf nodes in the Merkle tree.
[0037] In step 502, the user can select identity attributes to be made public from all identity attributes displayed on the display screen of the application APP, and the identity authentication side thereby obtains the identity attributes to be made public selected by the user.
[0038] In step 503, the identity authentication side can obtain a verification path based on the identity attributes selected by the user to be made public. For a specific method of obtaining the verification path, refer to the schematic diagram of the simulation process of the verification path in Figure 4 above. In order to avoid duplication, the description will be omitted here.
[0039] In step 504, the identity authentication side generates an identity certificate including the published identity attributes, verification path and mechanism signature based on the identity attributes, verification path and mechanism signature selected by the user to be published, and signs the identity certificate with the user's private key to obtain a user signature, and obtains an identity certificate further including the user signature.
[0040] In one embodiment, the identity authentication method can adopt a distributed service-oriented software architecture for three parties, the three parties including a service provider of a digital identity service, a user side and an examination side (the examination side is also called an identity authentication side), and the three parties are in a many-to-many relationship and are related by a blockchain network. Referring to FIG. 7, the software architecture includes a digital identity service, a digital identity application, a blockchain network and a smart contract. Here, the digital identity service can include a digital identity service corresponding to an issuing mechanism X and a digital identity service corresponding to an issuing mechanism Y, the issuing mechanism X can provide the digital identity service X, the issuing mechanism Y can provide the digital identity service Y, and the digital identity application is a terminal APP, and the terminal APP can include an operation interface facing the user side and an operation interface facing the examination side. The software architecture will be described in detail below.
[0041] The blockchain network may be a common blockchain, such as Hyperledger Fabric, Fisco Bcos, etc., and is an alliance chain network built with digital identity services. It is used to add evidence to the blockchain and store evidence in the process of issuing model services, issuing digital identities and evidence, etc., to facilitate lookup and tracing.
[0042] A digital identity service is a software-as-a-service (SaaS) issued by a digital identity service and provided to terminal users. Different service providers can issue different digital identity services, and the digital identity service issues identity models to the blockchain network for terminal users to access. The terminal users find service addresses in the blockchain network based on the identity models and perform related identity registration and evidence application activities. The digital identity service includes an access layer, an identity management, an evidence management, a model management, a storage layer and a communication layer. The contents included in the digital identity service are described in detail below.
[0043] The access layer provides access operations to the digital identity service and may be a UI interface or a command line interface.
[0044] Identity management is a function for managing user identities registered with a digital identity service, including identity registration, establishment of a user profile, and logging out of a registered identity.
[0045] Evidence management is a management function that generates verifiable identity evidence based on an identity model and issues evidence, and includes the functions of issuing evidence and revoking evidence.
[0046] Model management includes functionality for modeling, publishing and adding identity models to the blockchain, and for configuring identity model publishing and identity-related evidence templates.
[0047] The storage layer stores identity model metadata and cryptographically stores identity attributes of registered users.
[0048] The communication layer provides an HTTP service interface for terminal users to access and a maintenance and transaction interface with the blockchain network.
[0049] The digital identity application is the application APP in the figure, which is deployed on the mobile phone or tablet terminal of the terminal user and includes two role views: application side user (i.e., the user in the lower left corner of the figure) and review side user (i.e., the review side in the lower right corner of the figure), the application APP mainly relates to registration, evidence application, and certificate generation operations, and review mainly relates to the verification operation for the presented certificate. The digital identity application mainly relates to human-computer interaction, service search, my identity, my evidence, evidence verification, TEE trusted environment, TEE interface layer, operating system layer, and hardware layer, and the following will specifically explain the contents mainly related to the digital identity application.
[0050] Human-computer interaction is a human-computer interaction UI that is realized by hardware input and output such as touch panels and touch buttons.
[0051] Service search searches for an identity model from the blockchain network and obtains a service access address of the digital identity service.
[0052] My Identity allows application users to register their identity with a digital identity service provider and obtain an identity identifier and an identity profile.
[0053] MyEvidence allows application side users to submit evidence to a digital identity service provider, obtain identity evidence, and generate identity certificates.
[0054] Evidence Verification provides identity authentication, profile inquiry, evidence review, and certificate validation functions for reviewing users.
[0055] The TEE trusted environment is a TEE trusted environment owned by the terminal device itself, which provides management of user privacy data and trusted applications, including user private key management and signing and decryption operations using the private key. All calculation processing on privacy data is performed in a trusted environment to protect the user's privacy security.
[0056] The TEE interface layer is a communication interface between the TEE environment and the outside world. The operating system layer is the operating system that the terminal itself has, such as Android (registered trademark), iOS, etc.
[0057] The hardware layer is the terminal hardware device, including chips, memory, touch panel, etc.
[0058] The smart contract is responsible for issuing digital identity services, adding identity registration to the blockchain, adding evidence issuance to the blockchain, and adding key information such as user screening and credit rating to the blockchain, making it easy to search and trace.
[0059] This embodiment adopts a distributed service-oriented software architecture, and the issuing mechanism, users, and examiners have a many-to-many relationship and are associated through a block chain network. The user registers with the issuing mechanism, and the issuing mechanism issues a digital identity ID to the user, publishes the digital identity ID and adds it to the block chain, and obtains the corresponding public key according to the digital identity ID in the block chain, which can be used for signature verification. The block chain Merkle tree fast verification technology is adopted in data identity authentication, which solves the security problem of data privacy leakage that exists in traditional identity verification. In this embodiment, the Merkle tree fast verification technology can be used to verify multiple identity attributes at one time, and the efficiency is higher.
[0060] In one embodiment, the identity attributes registered by the user are organized in the manner of a Merkle tree, and the Merkle roof of the Merkle tree is calculated, and the organization manner is shown in Figure 3. When the identity attributes are organized in the manner of a Merkle tree, the Merkle tree can be called an identity attribute tree.
[0061] In one embodiment, an issuing institution issues digital identity evidence, and the identity evidence can adopt a graphical display manner, which includes all identity attributes, a Merkle roof of an identity attribute tree, the Merkle roof of the issuing institution, and a signature on the identity evidence content, and the verifiable effect of the identity evidence can be realized by verifying the signature and the Merkle roof, and the graphical identity evidence is shown in Figure 6, where the display order of the evidence attributes is the position order of the leaf nodes in the Merkle tree.
[0062] In one embodiment, a user with proof selects and publishes some identity attributes to generate an identity certificate, and the identity certificate can adopt a graphical display manner, the diagram including some published identity attributes, a Merkle roof of the identity attributes, a verification path of the Merkle roof and a signature of the issuing organization on the Merkle roof, the signature on the content of the user's identity certificate can be verified by verifying the signature and verifying the Merkle roof based on the published attributes and the verification path to achieve the verifiable effect of the identity certificate, and the graphical identity certificate is shown in Figure 2, where the display order of the published identity attributes is the position order of the leaf nodes in the Merkle tree, and the identity attributes that are not published are displayed in a mosaic manner.
[0063] In this embodiment, a two-dimensional code scanning verification method is introduced into the graphic display method of identity evidence and identity certificate, so that the evidence and certificate can be easily inspected and verified.
[0064] In one embodiment, the identity authentication method includes a model registration flow, an identity registration flow, an identity proof application flow, an identity certificate generation flow, and an identity certificate review flow. The model registration flow is a flow in which an issuing organization creates a model and publishes a digital identity service in a blockchain. The identity registration flow is a flow in which a user searches for an identity model in a blockchain, registers with an issuing organization, creates a profile, and applies for identity proof. The identity proof application flow is a flow in which an issuing organization issues a verifiable identity proof to an applying user, and adds the process to a blockchain to store the proof. The identity certificate generation flow is a flow in which a user selects and publishes some identity attributes of the identity proof to generate an identity certificate. The identity certificate review flow is a flow in which the reviewing side checks the validity of the evidence when it obtains only a small number of identity attributes of the user, and verifies the reliability and validity of the identity certificate. Each of the above flows will be described in detail below.
[0065] Refer to FIG. 8, which is a flow chart of a model registration flow. Here, model registration refers to the registration of an identity model, where an issuing organization creates an identity model, and each type of identity model corresponds to one kind of digital identity. A user can register different identity models of one issuing organization, and can also register different identity models of different issuing organizations. The model registration flow is as follows: First, an issuing agency uses a model management function of the digital identity system to create an identity model and write model parameters of the identity model, the model parameters including name, version and metadata information of the model; Then, after creating the identity model, further configuring evidence information related to the identity model through a template configuration function of the model management, the configuration contents including a name and a template file (used for graphically displaying the evidence); Next, after the identity model is successfully issued, the model management system adds the created identity model to the blockchain, where the information added to the blockchain includes a model ID, a name, metadata information and a service access address, facilitating user search and access; Finally, the model manager returns a creation success message to the publisher.
[0066] Refer to FIG. 9, which is a flow chart of an identity registration flow. In this flow, a user uses an application APP to search for a relevant identity model from the blockchain, obtains a service access address based on the identity model, and registers the identity with a service providing institution corresponding to the service access address. The issuing institution generates a digital identity ID for the user, creates a profile, and adds the user's digital identity to the blockchain. The identity registration flow is as follows: First, the user enters the "service search" function screen of the APP, searches for services from the blockchain and obtains the service access address; Then, the user enters the “My Identity” function page of the APP to register his / her identity, and the registration information includes personal account, model, version and user public key; Next, the digital identity service issues a digital identity document (DID) to the user, creates a user profile, and adds the DID and the user profile to the blockchain to store evidence and facilitate searches by the examiner, where the user profile does not include the user's privacy information; Finally, the digital identity service returns a registration success message and the user's digital identity ID.
[0067] Refer to FIG. 10, which is a flowchart of the identity certificate application flow. After completing identity registration, a user can apply for identity evidence from the digital identity service deployed on the server side, where the identity evidence includes identity model information, the Merkle roof of identity attributes, and the issuing institution's signature on the Merkle roof, and the issuing institution adds the process to the blockchain to store the evidence and facilitate tracing. The identity certificate application flow is as follows: First, the user enters the “My Evidence” function page of the application APP, selects the corresponding identity model from the registered identity, and submits an evidence application to the digital identity service deployed on the server side; and after the organization administrator has approved and passed the approval, the data identity service builds a Merkle tree based on the identity attributes and calculates the Merkle roof; Next, the issuing authority signs the Merkle roof with the issuing authority's private key to generate a proof of identity that includes two display formats, a graphical one and a text one; Next, the issuing agency signs the identity proof with a private key, and adds the issuing process to the blockchain to store the evidence (the information added to the blockchain includes information such as the issuing agency's identity ID, the identity proof ID, the Merkle roof, and the user's digital identity ID); Finally, the data identity service returns the identity evidence to the application APP, and the application APP returns the identity evidence to the user.
[0068] Please refer to FIG. 11, which is a flowchart of the identity certificate generation flow. A user selects and publishes some of the identity attributes in the identity evidence to generate an identity certificate. (For example, the employment evidence generates an employment certificate, and the degree evidence generates a degree certificate). The identity certificate includes the published identity attributes, a Merkle roof, a signature on the Merkle roof by the issuing organization, a verification path that verifies that the published identity attributes belong to the Merkle roof, and a signature on the identity certificate by the user. The certificate generation flow is as follows: First, the user enters the “My Evidence” function screen of the application APP, selects the identity evidence that has already been issued, and clicks to generate an identity certificate; Then, selecting one or more identity attributes to be made public from the identity attributes in the identity evidence and clicking to submit; Then, the application APP generates an identity certificate and signs the identity certificate with the user's private key to obtain an identity certificate including the user's signature; Finally, the application APP returns the identity certificate.
[0069] Refer to FIG. 12, which is a flowchart of the identity certificate review flow. The reviewing side verifies the authenticity and validity of the identity certificate. The identity certificate includes some published identity attributes, a Merkle roof of a Merkle tree in which the some identity attributes are located, and a verification path, and the validity of the some published identity attributes can be verified by simulating the verification path, thus avoiding the risk of other privacy information of the user being leaked. The identity certificate review can also be understood as authentication of the identity certificate, and the review result for the identity certificate is the authentication result for the identity certificate. The identity certificate review flow is as follows: First, the examiner enters the “Certificate Verification” function screen of the application APP, scans the verification 2D code on the picture of the identity certificate provided by the user, and performs identity certificate verification; Then, the application APP obtains a user profile from the blockchain based on the user's digital identity ID, obtains the user's public key from the user profile, and verifies the validity of the signature of the user on the identity certificate (verification 1); Next, the application APP obtains the profile of the issuing institution from the blockchain based on the digital identity ID of the issuing institution, obtains the public key of the issuing institution from the profile of the issuing institution, and verifies the validity of the signature of the issuing institution on the Merkle roof (verification 2); Then, the application APP simulates a validation path based on the published identity attributes and verifies whether the simulated validation path is consistent with the validation path in the identity certificate (verification 3); Finally, if all of the above verifications 1 to 3 pass, it is determined as an inspection result that the identity certificate passes the inspection, and if any of the above verifications 1 to 3 do not pass the verification, it is determined as an inspection result that the identity certificate does not pass. The inspection side finally adds the result of this inspection to the blockchain to store evidence, and incorporates the discrediting act of certificate forgery into the user's credit record to facilitate subsequent retroactive review.
[0070] In this embodiment, the method of completing identity authentication by disclosing only a part of the user's identity attributes by adopting the blockchain Merkle roof rapid verification technology, the graphical display method of the identity certificate, and the two-dimensional code verification method of the identity certificate not only solve the problem of protecting personal privacy data, but also conform to the current usage habits of users, are easy to operate, and facilitate the market penetration of the product.
[0071] It should be noted that the above examples in the embodiments of the present application are described merely as examples for ease of understanding, and are not intended to limit the technical solutions of the embodiments of the present application.
[0072] The division of steps of the above various methods is merely for clarity of explanation. Merging into one step or dividing some steps and decomposing them into multiple steps during implementation is within the scope of protection of this patent as long as they contain the same logical relationship. Adding unnecessary modifications to the algorithm or flow or introducing unnecessary designs but not changing the core design of the algorithm and flow is also within the scope of protection of this patent.
[0073] One embodiment of the present application provides an electronic device including at least one processor 1301 and a memory 1302 communicatively connected to the at least one processor 1301, as shown in FIG. 13, wherein the memory 1302 stores instructions executable by the at least one processor 1301, and the instructions are executed by the at least one processor 1301 to enable the at least one processor 13 to perform the above-mentioned identity authentication method.
[0074] Here, the memory 1302 and the processor 1301 are connected in a bus manner, which may include any number of interconnected buses and bridges, and which connects various circuits of one or more processors 1301 and the memory 1302. The bus may further connect various other circuits, such as peripherals, regulators and power management circuits, all of which are known to those skilled in the art and therefore will not be further described herein. The bus interface provides an interface between the bus and a transceiver. The transceiver may be one element or multiple elements, for example multiple receivers and transmitters, providing a unit for communicating with various other devices over a transmission medium. The data processed by the processor 1301 is transmitted over a wireless medium via an antenna, which further receives the data and transmits the data to the processor 1301.
[0075] The processor 1301 is responsible for managing the bus and normal processing, and may further provide a variety of functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions. The memory 1302 may be used to store data used by the processor 1301 when performing operations.
[0076] An embodiment of the present application further provides a computer readable storage medium storing a computer program, which when executed by a processor, implements an embodiment of the method described above.
[0077] As can be understood by those skilled in the art, the implementation of all or part of the steps in the methods of the above embodiments can be completed by instructing related hardware through a program, and the program is stored in a storage medium and includes several instructions to make a device (which may be a one-chip microcomputer, chip, etc.) or a processor execute all or part of the steps of the methods of the embodiments of the present application. The storage medium mentioned above includes various media capable of storing program codes, such as U disks, removable hard disks, read-only memories (ROMs), random access memories (RAMs), magnetic disks, or optical disks.
[0078] As will be understood by those skilled in the art, the above-described embodiments are specific examples for realizing the present application, and various changes in form and details can be made in actual use without departing from the spirit and scope of the embodiments of the present application.
Claims
1. obtaining an identity certificate of a user, the identity certificate including identity attributes of the user and a Merkle Roof verification path, the Merkle Roof verification path in the identity certificate being a verification path obtained based on identity attributes to be made public selected by the user when generating the identity certificate; simulating a Merkle Roof verification path based on the identity attributes published in the identity certificate; and authenticating the user's identity certificate based on the simulated validation path and the validation path in the identity certificate. Identity authentication method.
2. The step of simulating a Merkle Roof verification path based on the identity attributes published in the identity certificate includes: calculating a hash value of the identity attributes published in the identity certificate based on the identity attributes published in the identity certificate; and simulating a verification path of a Merkle roof based on the Hash value of the published identity attributes and the constructed Merkle tree.
3. The step of simulating a verification path of the Merkle tree based on the Hash value of the published identity attributes and the constructed Merkle tree includes: determining a node in the L1 layer of the Merkle tree that corresponds to the Hash value of the published identity attribute, and adding the node to a simulation queue T1 that corresponds to the L1 layer; simulating the Merkle tree from bottom to top, sequentially traversing the pair nodes (Hx, Hy) of each layer, and simulating after traversing the pair nodes (Hx, Hy) of each layer to obtain a verification path of the Merkle roof; Here, the following operation is performed on (Hx, Hy) in the traversed Li layer: If a node in (Hx, Hy) is included in a simulation queue Ti corresponding to the Li layer, add the Hash values of other nodes in (Hx, Hy) to the verification path, calculate the Hash value of (Hx, Hy), and add the Hash value of (Hx, Hy) to a simulation queue Ti+1 corresponding to the Li+1 layer, where 1≦i<deep, deep is the depth of the Merkle tree; If both of the two nodes in (Hx, Hy) are included in the simulation queue Ti corresponding to the Li layer, calculate the Hash value of (Hx, Hy) and add the Hash value of (Hx, Hy) to the simulation queue Ti+1 corresponding to the Li+1 layer; The identity authentication method according to claim 2 , wherein if there is no node included in the simulation queue Ti corresponding to the Li layer in the (Hx, Hy), the next (Hx, Hy) is traversed.
4. The identity certificate further includes a verification code of the identity certificate, and before obtaining the identity certificate of the user, generating a graphical identity certificate based on the identity attributes selected by the user to be made public, the graphical identity certificate displaying a verification code of the identity certificate; 2. The method of claim 1, further comprising the step of: obtaining an identity authentication result for the user by scanning a verification code on the graphical identity certificate.
5. The identity certificate further includes a digital identity ID of the user and a user signature of the user on the identity certificate of the user by the private key of the user. After obtaining the identity certificate of the user, and / or, further comprising obtaining a public key of the user from a blockchain based on the digital identity ID of the user, and verifying the user signature with the public key of the user. The identity certificate further includes a digital identity ID of an issuing mechanism of the identity certificate and an issuing mechanism signature of the issuing mechanism on the Merkle roof by the private key of the issuing mechanism. After obtaining the identity certificate of the user, The identity authentication method of claim 1 , further comprising the steps of obtaining a public key of the issuing organization from a blockchain based on the digital identity ID of the issuing organization, and verifying the organization signature with the public key of the issuing organization.
6. The step of authenticating the identity certificate of the user based on the simulated verification path and the verification path in the identity certificate includes:
6. The identity authentication method of claim 5, further comprising the step of determining that identity authentication for the user is passed if the simulated verification path matches the verification path in the identity certificate and signature verification is passed, wherein passing the signature verification includes passing verification for the user signature and / or passing verification for the mechanism signature.
7. The step of obtaining the public key of the user from a blockchain based on the digital identity ID of the user includes: Obtaining a user profile based on the user's digital identity ID, the user profile being obtained based on the user's identity registration information when the user is registered, and the user profile being stored in a blockchain; and / or obtaining the public key of the user from the blockchain based on the user's profile. The step of obtaining a public key of the issuing organization from a blockchain based on a digital identity ID of the issuing organization includes: obtaining a profile of the issuing mechanism based on the digital identity ID of the issuing mechanism, the profile of the issuing mechanism being obtained based on the identity registration information of the issuing mechanism when registering with the issuing mechanism, and the profile of the issuing mechanism being stored in a blockchain; and obtaining a public key of the issuing organization from the blockchain based on a profile of the issuing organization.
8. The method of generating the identity certificate is as follows: determining an identity proof issued to the user, where the identity proof includes all identity attributes of the user, a Merkle roof of all the identity attributes, and a mechanism signature of an issuing mechanism of the identity proof over the Merkle roof by the issuing mechanism's private key; determining identity attributes selected by the user from all identity attributes in the identity evidence to be made public; Obtain a verification path based on the identity attributes selected by the user to be made public; The identity authentication method according to any one of claims 1 to 7, further comprising generating the identity certificate based on the identity attributes selected by the user to be made public, the verification path, and the mechanism signature, signing the identity certificate with the user's private key to obtain a user signature, and obtaining an identity certificate including the user signature.
9. At least one processor; a memory communicatively coupled to the at least one processor; The memory stores instructions executable by the at least one processor, and the instructions, when executed by the at least one processor, enable the at least one processor to perform the identity authentication method according to any one of claims 1 to 8. electronic equipment.
10. A computer readable storage medium storing a computer program which, when executed by a processor, implements the identity authentication method according to any one of claims 1 to 8.
Citation Information
Patent Citations
Certification method for authenticity of electronic document and publication system thereof
JP2006060722A
Certificate distribution system, certificate distribution method, and certificate distribution program
JP2018117287A
Identity authentication using barcode
JP2018186495A
2D barcode processing method, device, and system
JP2020502674A
Blocked tree authorization and status systems
US20050114666A1
