Identity authentication method, device, system and electronic device
By using blockchain technology to obtain and verify identity identification, the problems of cumbersome identity verification and data leakage risks in the existing technology are solved, and efficient and secure sharing of identity authentication is achieved, and identity authentication data interoperability is achieved across groups.
Patent Information
- Application Number
- CN202010439564.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-05-21
- Publication Date
- 2024-11-19
- Estimated Expiration
- 2040-05-21
AI Technical Summary
The prior art requires providing multiple credential data during entity authentication, which leads to cumbersome operations and high risk of data leakage, and has data island problems, making it difficult to achieve coexistence, sharing, mutual recognition and interoperability of identity authentication data within or across groups.
By obtaining the identity identity of the entity object to be authenticated, sending a request to the identity authentication service, and using the authentication results on the first and second blockchains for identity authentication, realizing the coexistence and sharing of identity authentication data within the same group or cross-group The identity authentication data between them is mutually recognized and communicated, reducing the multiple provisions of original identity data.
It improves the efficiency and security of identity authentication, avoids providing original identity data multiple times, thereby protecting data security, and achieving efficient sharing and interoperability of identity authentication data within or across groups.
Smart Images

Figure CN113704712B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of blockchain technology, and in particular to an identity authentication method, device, system and electronic device. Background Art
[0002] In the real world, people, objects, and groups can all be considered entities. A wide variety of credential data exists to describe the identities of entities or the relationships between them, such as ID cards, driver's licenses, bank deposit certificates, prescriptions, graduation certificates, and real estate certificates. Verifying an entity's identity requires providing these credential data. Each verification requires providing the original identity data, which is not only cumbersome but also poses a risk of data leakage. Summary of the Invention
[0003] In view of this, an object of the present invention is to provide an identity authentication method, device, system and electronic device to simplify the identity authentication process while protecting data security.
[0004] In a first aspect, an embodiment of the present invention provides an identity authentication method, including: obtaining an identity identifier of an entity object to be authenticated; sending an identity authentication request to an identity authentication service based on the identity identifier, wherein the identity authentication request is used to request authentication of the identity of the entity object to be authenticated, and the identity authentication service is used to obtain an authentication result of the entity object to be authenticated recorded on a first blockchain and / or a second blockchain based on the identity identifier, and the objects to which the first blockchain and the second blockchain belong are different; receiving the authentication result sent by the identity authentication service in response to the identity authentication request.
[0005] In a second aspect, an embodiment of the present invention provides an identity authentication method, comprising: obtaining an identity authentication request sent by a terminal device, wherein the identity authentication request is used to request authentication of the identity of an entity object to be authenticated; obtaining an identity identifier of the entity object to be authenticated based on the identity authentication request; obtaining an authentication result of the entity object to be authenticated recorded on a first blockchain and / or a second blockchain based on the identity identifier, wherein the objects to which the first blockchain and the second blockchain belong are different; and sending the authentication result to the terminal device.
[0006] In a third aspect, an embodiment of the present invention provides an identity authentication device, comprising: a first acquisition module, used to obtain an identity identifier of an entity object to be authenticated; a first sending module, used to send an identity authentication request to an identity authentication service based on the identity identifier, wherein the identity authentication request is used to request authentication of the identity of the entity object to be authenticated, and the identity authentication service is used to obtain the authentication result of the entity object to be authenticated recorded on the first blockchain and / or the second blockchain based on the identity identifier, and the objects to which the first blockchain and the second blockchain belong are different; a receiving module, used to receive the authentication result sent by the identity authentication service in response to the identity authentication request.
[0007] In a fourth aspect, an embodiment of the present invention provides an identity authentication device, comprising: a second acquisition module, used to obtain an identity authentication request sent by a terminal device, wherein the identity authentication request is used to request authentication of the identity of the entity object to be authenticated; a third acquisition module, used to obtain the identity identifier of the entity object to be authenticated according to the identity authentication request; a fourth acquisition module, used to obtain the authentication result of the entity object to be authenticated recorded on the first blockchain and / or the second blockchain according to the identity identifier, wherein the objects to which the first blockchain and the second blockchain belong are different; a second sending module, used to send the authentication result to the terminal device.
[0008] In a fifth aspect, an embodiment of the present invention provides an identity authentication system, comprising a terminal device, an identity authentication service, a first blockchain, and a second blockchain; the terminal device is used to: obtain an identity identifier of an entity object to be authenticated; based on the identity identifier, send an identity authentication request to the identity authentication service, wherein the identity authentication request is used to request authentication of the identity of the entity object to be authenticated; the identity authentication service is used to: obtain the identity authentication request sent by the terminal device; based on the identity authentication request, obtain the identity identifier of the entity object to be authenticated; based on the identity identifier, obtain the authentication result of the entity object to be authenticated recorded on the first blockchain and / or the second blockchain, the objects to which the first blockchain and the second blockchain belong are different; and send the authentication result to the terminal device.
[0009] In a sixth aspect, an embodiment of the present invention provides an electronic device comprising a processor and a memory, wherein the memory stores machine-executable instructions that can be executed by the processor, and the processor executes the machine-executable instructions to implement any of the above-mentioned identity authentication methods.
[0010] In the seventh aspect, an embodiment of the present invention provides a machine-readable storage medium, which stores machine-executable instructions. When the machine-executable instructions are called and executed by a processor, the machine-executable instructions prompt the processor to implement the identity authentication method described in any one of the first aspect or the second aspect.
[0011] The identity authentication method, device, system, and electronic device provided by the present invention first send an identity authentication request to an identity authentication service based on the identity identifier of the entity object to be authenticated, wherein the identity authentication request is used to request authentication of the identity of the entity object to be authenticated, and the identity authentication service is used to obtain the authentication result of the entity object to be authenticated recorded on the first blockchain and / or the second blockchain based on the identity identifier, and then receive the authentication result sent by the identity authentication service in response to the identity authentication request. In this method, the entity object to be authenticated only needs to perform identity authentication once, and then the authentication result of the entity object to be authenticated recorded on the first blockchain and / or the second blockchain can be obtained through the identity authentication service based on the identity identifier, thereby realizing the coexistence and sharing of identity authentication data within the same group, or the mutual recognition and intercommunication of identity authentication data across groups, thereby improving the efficiency of identity authentication.
[0012] Other features and advantages of the present invention will be described in the following description, and in part will become apparent from the description, or understood by practicing the present invention. The purposes and other advantages of the present invention are realized and obtained by the structures particularly pointed out in the description, claims and drawings.
[0013] In order to make the above-mentioned objects, features and advantages of the present invention more obvious and easy to understand, preferred embodiments are given below and described in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS
[0014] In order to more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the specific embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without paying any creative work.
[0015] Figure 1 A flowchart of an identity authentication method provided by an embodiment of the present invention;
[0016] Figure 2 A flowchart of another identity authentication method provided by an embodiment of the present invention;
[0017] Figure 3 A flowchart of another identity authentication method provided by an embodiment of the present invention;
[0018] Figure 4 A flowchart of another identity authentication method provided by an embodiment of the present invention;
[0019] Figure 5 A flowchart of another identity authentication method provided by an embodiment of the present invention;
[0020] Figure 6 A flowchart of another identity authentication method provided by an embodiment of the present invention;
[0021] Figure 7 A schematic diagram of an identity authentication system architecture provided by an embodiment of the present invention;
[0022] Figure 8 A schematic diagram of the relationship between identity data provided by an embodiment of the present invention;
[0023] Figure 9 A schematic structural diagram of an identity authentication device provided by an embodiment of the present invention;
[0024] Figure 10 A schematic structural diagram of another identity authentication device provided by an embodiment of the present invention;
[0025] Figure 11 A schematic diagram of the architecture of an identity authentication system provided by an embodiment of the present invention;
[0026] Figure 12 A schematic structural diagram of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION
[0027] To make the objectives, technical solutions, and advantages of the embodiments of the present invention more clear, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the embodiments described are only part of the embodiments of the present invention, not all of them. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work shall fall within the scope of protection of the present invention.
[0028] In related technologies, verifying an entity's identity typically requires providing multiple relevant credentials. The collection, storage, authorized use, transmission, or authentication of this credential data presents data privacy risks and data silos within groups or alliances. Entity identification and trusted data solutions in related technologies can provide a trusted mapping between the real-world identities of entities, such as people or objects, and their on-chain identities, enabling secure access authorization and data exchange between entities. The solution currently consists of two main modules: the DID (Decentralized Identifier) module and the Credential module. DID, which can also be understood as a distributed identity, implements a distributed multi-center identity protocol that complies with the W3C (World Wide Web Consortium) DID specification on the FISCO-BCOS blockchain underlying platform, enabling the real-world identities of entities such as people or objects to be identified on the chain. At the same time, DID also gives entities such as people or objects the ability to directly own and control their own identities. The above-mentioned FISCO BCOS can be understood as a completely open source consortium blockchain underlying technology platform and is the financial branch of the BCOS (Be Credible, Open & Secure, an open source blockchain technology platform for enterprise-level application services) open source platform.
[0029] Credential is a verifiable digital credential. In the real world, there are various data used to describe the identity of an entity and the relationship between entities, such as identity cards, driving licenses, deposit certificates, prescriptions, graduation certificates, real estate certificates, etc. Credential provides a complete set of solutions based on the W3C VC (VC is a software development tool) specification, which aims to standardize and digitize this type of data and generate verifiable and exchangeable credentials (Credential). However, this system is a framework-type technical solution and does not provide specific solutions for the presentation and verification of customer identity credentials, or the acquisition and storage of user identity credentials. Based on this, the embodiments of the present invention provide an identity authentication method, device, system and electronic device. This technology can be applied to applications that require identity authentication of entities such as people, objects or groups.
[0030] To facilitate understanding of this embodiment, an identity authentication method disclosed in an embodiment of the present invention is first described in detail. Figure 1 As shown, the method includes the following steps:
[0031] Step S102: Obtain the identity of the entity object to be authenticated.
[0032] The above-mentioned entity objects may include people, objects or groups, etc.; the above-mentioned identity identifier can be understood as an identifier that can prove the identity of entity objects such as people, objects or groups. For each entity object, its identity identifier is usually unique, and it can also be understood that there is usually a one-to-one correspondence between the identity identifier and the entity object; the identity identifier can be in various forms such as a QR code or a barcode; in actual implementation, it is necessary to first obtain the identity identifier of the entity object to be authenticated, and the identity identifier can be represented by the above-mentioned DID.
[0033] Step S104: Send an identity authentication request to the identity authentication service based on the identity identifier, wherein the identity authentication request is used to request authentication of the identity of the entity object to be authenticated, and the identity authentication service is used to obtain the authentication result of the entity object to be authenticated recorded on the first blockchain and / or the second blockchain based on the identity identifier, and the objects to which the first blockchain and the second blockchain belong are different.
[0034] The above-mentioned identity authentication service can run on a server; the above-mentioned blockchain can be understood as a shared database, and the data or information stored therein usually has the characteristics of being unforgeable, traceable throughout the process, traceable, open and transparent, and collectively maintained; the above-mentioned first blockchain can usually include multiple node devices; the above-mentioned second blockchain can also usually include multiple node devices; the above-mentioned identity authentication service can be communicated with the first blockchain and the second blockchain; in actual implementation, the first blockchain or the second blockchain, or the first blockchain and the second blockchain usually record the authentication results of the entity object to be authenticated. After obtaining the identity identifier of the entity object to be authenticated, an identity authentication request is sent to the identity authentication service based on the identity identifier, so that the identity authentication service obtains the authentication results of the entity object to be authenticated recorded on the first blockchain or the second blockchain, or the first blockchain and the second blockchain based on the identity identifier. It is understood that in embodiments of the present invention, both the first blockchain and the second blockchain may be multiple in number. For example, the first blockchain is the blockchain of the acquirer that obtains the identity of the entity to be authenticated, and the acquirer may have one or more blockchains. The second blockchain is the blockchain of a person or group other than the acquirer, and there may be multiple persons or groups other than the acquirer, and each person or group other than the acquirer may have one or more blockchains. The present invention does not limit the specific number of the first blockchain and the second blockchain.
[0035] Step S106: Receive the authentication result sent by the identity authentication service in response to the identity authentication request.
[0036] The authentication result may include a successful or failed authentication of the entity to be authenticated. When the authentication is successful, the authentication result typically also includes relevant data about the entity to be authenticated, such as the entity's real identity information or identity profile. After sending an authentication request to the authentication service, the authentication result received from the authentication service in response to the authentication request may be one or more. For example, if both the first and second blockchains record the authentication result for the entity to be authenticated, the number of received authentication results may be multiple. For another example, if there is one first blockchain, which does not record the authentication result for the entity to be authenticated, and there are K second blockchains, L of which record the authentication result for the entity to be authenticated, then L authentication results will be received, where K is greater than or equal to 2 and L is less than or equal to K, and both K and L are positive integers.
[0037] An embodiment of the present invention provides an identity authentication method, which first sends an identity authentication request to an identity authentication service based on the identity identifier of the entity object to be authenticated, wherein the identity authentication request is used to request authentication of the identity of the entity object to be authenticated, and the identity authentication service is used to obtain the authentication result of the entity object to be authenticated recorded on the first blockchain and / or the second blockchain based on the identity identifier, and then receives the authentication result sent by the identity authentication service in response to the identity authentication request. In this method, the entity object to be authenticated only needs to perform identity authentication once, and then the authentication result of the entity object to be authenticated recorded on the first blockchain and / or the second blockchain can be obtained through the identity authentication service based on the identity identifier, thereby realizing the coexistence and sharing of identity authentication data within the same group, or the mutual recognition and intercommunication of identity authentication data across groups, thereby improving the efficiency of identity authentication, and eliminating the need to provide the original identity data multiple times, thereby improving the security of the identity authentication data.
[0038] An embodiment of the present invention also provides another identity authentication method, which is implemented on the basis of the method of the above embodiment; in this method, when the identity identifier of the entity object to be authenticated is stored in the first blockchain, the identity identifier of the entity object to be authenticated stored in the first blockchain is used to indicate the authentication result of the entity object to be authenticated, wherein the first blockchain also stores the identity file corresponding to the identity identifier of the entity object to be authenticated.
[0039] In a case where the identity identifier of the entity object to be authenticated is stored in the second blockchain, the identity identifier of the entity object to be authenticated stored in the second blockchain is used to indicate an authentication result indicating that the entity object to be authenticated has been authenticated, wherein the second blockchain also stores an identity profile corresponding to the identity identifier of the entity object to be authenticated; wherein the identity profile is used to provide a method for accessing the real identity information of the entity object to be authenticated; and the authentication result generally includes: the real identity information and / or the identity profile of the entity object to be authenticated.
[0040] The above-mentioned identity profile can be understood as a set of data sets that meet preset standards and are used to describe the corresponding identity identification characteristics. For example, the identity profile may include the access address of the real identity information of the entity object to be authenticated, but does not include the real identity information of the entity object to be authenticated. In actual implementation, the identity profile is usually stored in a distributed storage system. The above-mentioned real identity information can be understood as the specific attributes or feature data of the entity object to be authenticated, or it can be understood as digital identity key data and original data, such as the name, ID number, contact number, picture or original file of the entity object to be authenticated. In actual implementation, if the identity identification of the entity object to be authenticated is stored in the first blockchain, it means that the first blockchain records the authentication result of the entity object to be authenticated being passed; if the identity identification of the entity object to be authenticated is stored in the second blockchain, it means that the second blockchain records the authentication result of the entity object to be authenticated being passed; the authentication result usually also includes: the real identity information of the entity object to be authenticated, or the identity profile, or both the real identity information and the identity profile of the entity object to be authenticated.
[0041] like Figure 2 As shown, the method includes the following steps:
[0042] Step S202: Obtain the identity of the entity object to be authenticated.
[0043] In step S204, an identity authentication request is sent to the identity authentication service based on the identity identifier, wherein the identity authentication request is used to request authentication of the identity of the entity object to be authenticated, and the identity authentication service is used to obtain the authentication result of the entity object to be authenticated recorded on the first blockchain and / or the second blockchain based on the identity identifier, and the objects to which the first blockchain and the second blockchain belong are different.
[0044] Step S206: Receive the authentication result sent by the identity authentication service in response to the identity authentication request.
[0045] Step S208: Send an authentication result selection instruction to the identity authentication service; the authentication result selection instruction is used to select a target authentication result from the authentication results.
[0046] The target authentication result described above can be understood as selecting one or more authentication results as the target authentication result. In actual implementation, for the same entity object to be authenticated, after sending an identity authentication request to the identity authentication service based on the obtained identity identifier of the entity object to be authenticated, multiple authentication results may be received. For example, if the identity identifier of the entity object to be authenticated is stored in both the first blockchain and the second blockchain, the identity authentication service can obtain multiple authentication results for the entity object to be authenticated recorded in the first blockchain and the second blockchain based on the identity identifier. In this case, it is usually necessary to send an authentication result selection instruction to the identity authentication service to select a target authentication result from the multiple authentication results.
[0047] Step S210: receiving the identity profile and / or real identity information of the entity object to be authenticated sent by the identity authentication service based on the target authentication result.
[0048] In actual implementation, since the target authentication result usually includes the real identity information of the entity object to be authenticated, or the identity file, or both the real identity information and the identity file of the entity object to be authenticated, after the target authentication result is determined from multiple authentication results, the real identity information of the entity object to be authenticated, or the identity file sent by the identity authentication service based on the target authentication result can be received, or both the real identity information and the identity file of the entity object to be authenticated can be received.
[0049] It should be noted that the first blockchain and the second blockchain can correspond to different groups respectively, and the group includes multiple entity objects; the group can also be called an alliance. In actual implementation, the group can be a bank, and the group includes all branches of the bank; the first blockchain or the second blockchain corresponding to the group stores the identity identifiers of the registered users of each branch of the bank; the objects belonging to the above-mentioned first blockchain and second blockchain are usually different. For example, the first blockchain corresponds to Bank A, and its objects are the users of Bank A, and the second blockchain corresponds to Bank B, and its objects are the users of Bank B, etc.
[0050] The following uses Bank A corresponding to the first blockchain as an example. Since the first blockchain stores the identity identifiers of registered users of each branch of Bank A, if a user has completed registration at one of Bank A's branches, when the user needs to conduct business at another branch of Bank A, there is no need to re-register. Identity authentication can be directly performed based on the user's identity identifier stored in the first blockchain to obtain the authentication result.
[0051] For example, the first blockchain corresponds to Bank A, the second blockchain corresponds to Bank B, and both the first and second blockchains are connected to the identity authentication service. If a user has completed registration at Bank A, the user's identity identifier is stored in the first blockchain. When the user conducts business at Bank B, there is no need to re-register. The user's identity identifier is obtained from the first blockchain through the identity authentication service. Based on the identity identifier, identity authentication is directly performed to obtain the authentication result.
[0052] Through the above-mentioned identity authentication method, users do not need to provide original identity data, such as identity cards, degree certificates, driver's licenses, etc., multiple times, thereby effectively protecting the user's original identity data. If the user presents the original identity data multiple times, the original identity data is easily leaked. The method adopted by the present invention is that the user only needs to perform identity authentication or registration once, and save the generated corresponding identity identifier in the corresponding first blockchain or second blockchain. The identity authentication service obtains the authentication result of the entity object to be authenticated recorded on the first blockchain and / or the second blockchain based on the identity identifier, so that the coexistence and sharing of identity authentication data within the same group can be realized, or through the mutual recognition and intercommunication of identity authentication data across groups, the identity authentication can be completed without the user having to re-perform identity authentication or registration, which can avoid the user from presenting the original identity data multiple times, thereby achieving the purpose of protecting the original identity data.
[0053] Another identity authentication method provided by an embodiment of the present invention first sends an identity authentication request to an identity authentication service based on the identity identifier of the entity object to be authenticated, then receives the authentication result sent by the identity authentication service in response to the identity authentication request, and finally sends an authentication result selection instruction to the identity authentication service to select a target authentication result from the authentication results, and receives the identity file and / or real identity information of the entity object to be authenticated sent by the identity authentication service based on the target authentication result. In this method, the entity object to be authenticated only needs to perform identity authentication once, and then, based on the identity identifier, the identity authentication service can obtain the authentication result of the entity object to be authenticated recorded on the first blockchain and / or the second blockchain, thereby realizing the coexistence and sharing of identity authentication data within the same group, or the mutual recognition and intercommunication of identity authentication data across groups, thereby improving the efficiency of identity authentication, and eliminating the need to provide the original identity data multiple times, thereby improving the security of the identity authentication data.
[0054] The embodiment of the present invention also provides another identity authentication method, such as Figure 3 As shown, the method includes the following steps:
[0055] Step S302: obtaining an identity authentication request sent by the terminal device, wherein the identity authentication request is used to request authentication of the identity of the entity object to be authenticated.
[0056] The above-mentioned terminal device can be a computer or mobile phone terminal; in actual implementation, when identity authentication is required, it is first necessary to obtain an identity authentication request sent by the computer or mobile phone terminal, requesting authentication of the identity of the entity object to be authenticated.
[0057] Step S304: Obtain the identity identifier of the entity object to be authenticated according to the identity authentication request.
[0058] The above-mentioned identity authentication request usually includes the authentication materials required for identity authentication; for example, when the entity object to be authenticated is a person, considering that each person has a unique ID number corresponding to him or her, the corresponding identity identifier can be obtained based on the ID number contained in the identity authentication request; in actual implementation, after obtaining the identity authentication request sent by the terminal device, the identity identifier corresponding to the entity object to be authenticated is usually obtained based on the authentication materials contained in the identity authentication request.
[0059] Step S306: Obtain, based on the identity identifier, an authentication result of the entity object to be authenticated recorded on the first blockchain and / or the second blockchain, where the objects belonging to the first blockchain and the second blockchain are different.
[0060] Step S308: Send the authentication result to the terminal device.
[0061] Another identity authentication method provided by an embodiment of the present invention first obtains an identity identifier of the entity object to be authenticated based on an identity authentication request sent by a terminal device; then, based on the identity identifier, obtains the authentication result of the entity object to be authenticated recorded on the first blockchain and / or the second blockchain, and finally sends the authentication result to the terminal device. In this method, the entity object to be authenticated only needs to perform identity authentication once, and then, based on the identity identifier, the authentication result of the entity object to be authenticated recorded on the first blockchain and / or the second blockchain can be obtained through the identity authentication service, thereby realizing the coexistence and sharing of identity authentication data within the same group, or the mutual recognition and intercommunication of identity authentication data across groups, thereby improving the efficiency of identity authentication, and eliminating the need to provide the original identity data multiple times, thereby improving the security of the identity authentication data.
[0062] The embodiment of the present invention also provides another identity authentication method, which is implemented on the basis of the method of the above embodiment; the method focuses on the specific process of obtaining the authentication result of the entity object to be authenticated recorded on the first blockchain and / or the second blockchain according to the identity identifier, which specifically corresponds to the following steps S406 to S414; Figure 4 As shown, the method includes the following steps:
[0063] Step S402: obtaining an identity authentication request sent by the terminal device, wherein the identity authentication request is used to request authentication of the identity of the entity object to be authenticated.
[0064] Step S404: Obtain the identity identifier of the entity object to be authenticated according to the identity authentication request.
[0065] Step S406: Obtain the storage result of the identity, where the storage result is used to indicate whether the identity of the entity object to be authenticated is stored in the first blockchain and the second blockchain.
[0066] In actual implementation, after obtaining the identity identifier of the entity object to be authenticated, it is necessary to confirm whether the identity identifier of the entity object to be authenticated is stored in the first blockchain and the second blockchain. For example, taking the first blockchain corresponding to Bank A and the second blockchain corresponding to Bank B as an example, if the user is opening an account at the bank for the first time, the first blockchain corresponding to Bank A and the second blockchain corresponding to Bank B do not store the identity identifier of the entity object to be authenticated; if the user has opened an account with Bank A or Bank B, the identity identifier of the entity object to be authenticated is stored in the first blockchain or the second blockchain.
[0067] Step S408: Determine the authentication result of the entity object to be authenticated recorded on the first blockchain and / or the second blockchain based on the stored result, wherein, when the identity identifier of the entity object to be authenticated is stored in the first blockchain, the identity identifier of the entity object to be authenticated stored in the first blockchain is used to indicate that the first blockchain records the authentication result that the entity object to be authenticated is passed; when the identity identifier of the entity object to be authenticated is stored in the second blockchain, the identity identifier of the entity object to be authenticated stored in the second blockchain is used to indicate that the second blockchain records the authentication result that the entity object to be authenticated is passed.
[0068] After obtaining the above-mentioned stored result, the authentication result of the entity object to be authenticated recorded in the first blockchain or the second blockchain, or in the first blockchain and the second blockchain, is determined according to the stored result. If the identity identifier of the entity object to be authenticated is stored in the first blockchain, it means that the first blockchain has recorded the authentication result that the entity object to be authenticated is passed; if the identity identifier of the entity object to be authenticated is stored in the second blockchain, it means that the second blockchain has recorded the authentication result that the entity object to be authenticated is passed; if the identity identifier of the entity object to be authenticated is stored in both the first blockchain and the second blockchain, it means that the first blockchain and the second blockchain have both recorded the authentication result that the entity object to be authenticated is passed.
[0069] Step S410: obtaining an authentication result selection instruction sent by the terminal device; the authentication result selection instruction is used to select a target authentication result from the authentication results.
[0070] In actual implementation, for the same entity object to be authenticated, multiple authentication results of the entity object to be authenticated recorded on the first blockchain and the second blockchain may be obtained. At this time, it is usually necessary to obtain the authentication result selection instruction sent by the terminal device to select a target authentication result from the multiple authentication results.
[0071] Step S412: selecting an instruction based on the authentication result and determining a target authentication result.
[0072] According to the obtained authentication result selection instruction, a target authentication result is determined from multiple authentication results; for example, when the first blockchain and the second blockchain both record the authentication results of the entity object to be authenticated, if the authentication result selection instruction indicates to select the authentication result of the entity object to be authenticated recorded in the first blockchain, then according to the authentication result selection instruction, the authentication result of the entity object to be authenticated recorded in the first blockchain is determined to be the target authentication result.
[0073] Step S414: Based on the target authentication result, the real identity information of the entity to be authenticated is authenticated. Specifically, step S414 can be implemented by following the steps 1 or 2:
[0074] In step 1, if the target authentication result is recorded on the first blockchain, the first blockchain also stores an identity profile corresponding to the identity identifier of the entity to be authenticated; the identity profile is used to provide access to the real identity information of the entity to be authenticated. The identity profile corresponding to the identity identifier of the entity to be authenticated is retrieved from the first blockchain; and the authentication result of the entity to be authenticated is obtained using the retrieved identity profile.
[0075] In actual implementation, if the authentication result of the entity object to be authenticated recorded in the first blockchain is determined as the target authentication result, the identity file corresponding to the identity identifier of the entity object to be authenticated is queried from the first blockchain. The identity file usually provides an access method for the real identity information of the entity object to be authenticated, such as the access address of the real identity information of the entity object to be authenticated. Based on the queried identity file, the authentication result of the entity object to be authenticated is obtained.
[0076] In step 2, if the target authentication result is recorded on the second blockchain, the second blockchain also stores an identity profile corresponding to the identity identifier of the entity to be authenticated. The identity profile provides access to the real identity information of the entity to be authenticated. The identity profile corresponding to the identity identifier of the entity to be authenticated is retrieved from the second blockchain. The authentication result of the entity to be authenticated is obtained using the retrieved identity profile.
[0077] In actual implementation, if the authentication result of the entity object to be authenticated recorded in the second blockchain is determined as the target authentication result, the identity file corresponding to the identity identifier of the entity object to be authenticated is queried from the second blockchain. The identity file usually provides an access method for the real identity information of the entity object to be authenticated, such as the access address of the real identity information of the entity object to be authenticated. Based on the queried identity file, the authentication result of the entity object to be authenticated is obtained.
[0078] Step S416: Send the authentication result to the terminal device.
[0079] Another identity authentication method provided by an embodiment of the present invention first obtains the identity identifier of the entity object to be authenticated based on the identity authentication request sent by the terminal device; then obtains the storage result of the identity identifier, and determines the authentication result of the entity object to be authenticated recorded on the first blockchain and / or the second blockchain based on the storage result, and finally sends the authentication result to the terminal device. In this method, the entity object to be authenticated only needs to perform identity authentication once, and then can obtain the authentication result of the entity object to be authenticated recorded on the first blockchain and / or the second blockchain through the identity authentication service based on the identity identifier, thereby realizing the coexistence and sharing of identity authentication data within the same group, or the mutual recognition and intercommunication of identity authentication data across groups, thereby improving the efficiency of identity authentication, and eliminating the need to provide the original identity data multiple times, thereby improving the security of the identity authentication data.
[0080] The embodiment of the present invention also provides another identity authentication method, which is implemented on the basis of the method of the above embodiment; the method focuses on the specific process of obtaining the authentication result of the entity object to be authenticated recorded on the first blockchain according to the identity identifier, which specifically corresponds to the following steps S506 to S508. In this method, when the identity identifier of the entity object to be authenticated is stored in the first blockchain, the first blockchain also stores the identity file corresponding to the identity identifier of the entity object to be authenticated; the identity file is used to provide an access method for the real identity information of the entity object to be authenticated; Figure 5 As shown, the method includes the following steps:
[0081] Step S502: obtaining an identity authentication request sent by the terminal device, wherein the identity authentication request is used to request authentication of the identity of the entity to be authenticated.
[0082] Step S504: Obtain the identity identifier of the entity object to be authenticated according to the identity authentication request.
[0083] Step S506: When the identity identifier of the entity object to be authenticated is stored in the first blockchain, the identity file corresponding to the identity identifier of the entity object to be authenticated is searched from the first blockchain.
[0084] Step S508: Obtain the authentication result of the entity object to be authenticated through the queried identity file.
[0085] Step S510: Send the authentication result to the terminal device.
[0086] Another identity authentication method provided by an embodiment of the present invention first obtains the identity identifier of the entity object to be authenticated based on the identity authentication request sent by the obtained terminal device; when the identity identifier of the entity object to be authenticated is stored in the first blockchain, the identity file corresponding to the identity identifier of the entity object to be authenticated is queried from the first blockchain, and then the authentication result of the entity object to be authenticated is obtained through the queried identity file, and finally the authentication result is sent to the terminal device. In this method, the entity object to be authenticated only needs to perform identity authentication once, and then the authentication result of the entity object to be authenticated recorded on the first blockchain and / or the second blockchain can be obtained through the identity authentication service based on the identity identifier, thereby realizing the coexistence and sharing of identity authentication data within the same group, or the mutual recognition and intercommunication of identity authentication data across groups, thereby improving the efficiency of identity authentication, and eliminating the need to provide the original identity data multiple times, thereby improving the security of the identity authentication data.
[0087] The embodiment of the present invention also provides another identity authentication method, which is implemented on the basis of the method of the above embodiment; the method focuses on describing the specific process of obtaining the authentication result of the entity object to be authenticated recorded on the second blockchain according to the identity identifier, which specifically corresponds to the following steps S606 to S608. In this method, when the identity identifier of the entity object to be authenticated is stored in the second blockchain, the second blockchain also stores the identity file corresponding to the identity identifier of the entity object to be authenticated; the identity file is used to provide an access method for the real identity information of the entity object to be authenticated; the identity file usually includes a hash value of the real identity information of the entity object and an access address of the real identity information of the entity object, but does not include the real identity information of the entity object; in actual implementation, the identity file is usually stored in a distributed storage system; the hash value can be understood as a hash value obtained through a certain hash algorithm, such as MD5 (Message Digest Algorithm 5, Message Digest Algorithm Version 5), SHA-1 (Secure Hash Algorithm 1, Secure Hash Algorithm 1) and other algorithms map the real identity information of an entity object into a shorter piece of data. This short piece of data is the hash value of the real identity information of the entity object. Once the real identity information of the entity object changes, the corresponding hash value will also change. That is, there is a one-to-one correspondence between the real identity information of the entity object and the hash value. The above-mentioned access address can be understood as the address where the real identity information of the entity object is stored. In actual implementation, the access address can be represented by a URI (Uniform Resource Identifier). The identity file usually also includes data information such as the public key, authentication, and service corresponding to the identity identifier.
[0088] The above-mentioned real identity information usually includes the identity certificate of the entity object; the identity certificate is used to prove that the entity object has the specified identity attribute; the identity certificate can be understood as a verifiable electronic certificate provided by the entity object to prove the identity of the entity object; the number of identity certificates can be multiple, for example, it can be the entity object's driver's license, social security card or relevant qualification certificate, etc.; the identity attribute can be understood as a specific identity, for example, if the identity certificate is a driver's license, the driver's license can prove that the entity object has the driving qualification and has the corresponding driver identity attribute.
[0089] like Figure 6 As shown, the method includes the following steps:
[0090] Step S602: obtaining an identity authentication request sent by the terminal device, wherein the identity authentication request is used to request authentication of the identity of the entity to be authenticated.
[0091] Step S604: Obtain the identity identifier of the entity object to be authenticated according to the identity authentication request.
[0092] Step S606: When the identity identifier of the entity object to be authenticated is stored in the second blockchain, the identity file corresponding to the identity identifier of the entity object to be authenticated is queried from the second blockchain.
[0093] Step S608: Obtain the authentication result of the entity object to be authenticated through the queried identity file.
[0094] Specifically, step S608 can be implemented by following steps 3 to 6:
[0095] Step three: obtain the real identity information of the entity object to be authenticated through the access address in the queried identity file; and verify whether the real identity information of the entity object to be authenticated has been tampered with through the hash value in the queried identity file.
[0096] In actual implementation, the real identity information of the entity object to be authenticated is usually stored in a distributed storage system, and is not directly stored on the blockchain. Instead, the access address and hash value of the real identity information of the entity object to be authenticated are stored on the blockchain; when the entity object to be authenticated needs to be authenticated, the real identity information of the entity object to be authenticated can be obtained through the access address; since the hash value and the real identity information of the entity object to be authenticated are in a one-to-one correspondence, if the queried hash value changes, it can be confirmed that the real identity information of the entity object to be authenticated has been tampered with; if the queried hash value does not change, it can be confirmed that the real identity information of the entity object to be authenticated has not been tampered with.
[0097] Step 4: If the real identity information of the entity object to be authenticated has not been tampered with, obtain the identity certificate of the entity object to be authenticated from the real identity information of the entity object to be authenticated.
[0098] If the hash value in the queried identity file has not changed, it means that the real identity information of the entity object to be authenticated has not been tampered with. At this time, the identity certificate of the entity object to be authenticated can be obtained from the real identity information of the entity object to be authenticated; in actual implementation, in some special application scenarios, it may be necessary to further obtain the relevant identity certificate of the entity object to be authenticated and verify the identity certificate. For example, in a recruitment scenario, it is not enough for the recruitment company to obtain only the applicant's ID number, but also the applicant's academic certificate, degree certificate and other related identity credentials; in the traffic management department, it is also necessary to obtain the driver's license, etc.; at this time, it is necessary to obtain the required relevant identity credentials from the real identity information of the entity object to be authenticated according to different application scenarios.
[0099] Step 5: Verify whether the obtained identity credentials are legal; if the identity credentials are legal, determine whether the entity object to be authenticated has the identity attributes corresponding to the identity credentials.
[0100] After obtaining the relevant identity credentials of the entity object to be authenticated, it is usually necessary to first verify whether the identity credentials are legal. For example, after a recruitment company obtains the applicant's academic certificate, degree certificate and other identity credentials, it needs to confirm the authenticity of these certificates; after the traffic management department obtains the driver's license, it needs to verify whether the type of vehicle driven by the driver exceeds the range of permitted vehicle types approved by the driver's license. If the identity credentials are legal, it can be confirmed that the entity object to be authenticated has the identity attributes corresponding to the identity credentials. For example, if the applicant's academic certificate and degree certificate are legal, it means that the applicant has the corresponding academic qualifications and degree; if the driver's license is legal, it means that the driver is allowed to drive the corresponding vehicle.
[0101] Step 6: The real identity information and / or identity file of the entity to be authenticated is determined as the authentication result of the entity to be authenticated.
[0102] If the real identity information of the entity object to be authenticated has not been tampered with, the real identity information of the entity object to be authenticated, or the identity file, or the real identity information and the identity file, are determined as the authentication result of the entity object to be authenticated.
[0103] Step S610: Send the authentication result to the terminal device.
[0104] Another identity authentication method provided by an embodiment of the present invention first obtains the identity identifier of the entity object to be authenticated based on the identity authentication request sent by the obtained terminal device; when the identity identifier of the entity object to be authenticated is stored in the second blockchain, the identity file corresponding to the identity identifier of the entity object to be authenticated is queried from the second blockchain, and then the authentication result of the entity object to be authenticated is obtained through the queried identity file, and finally the authentication result is sent to the terminal device. In this method, the entity object to be authenticated only needs to perform identity authentication once, and then the authentication result of the entity object to be authenticated recorded on the first blockchain and / or the second blockchain can be obtained through the identity authentication service based on the identity identifier, thereby realizing the coexistence and sharing of identity authentication data within the same group, or the mutual recognition and intercommunication of identity authentication data across groups, thereby improving the efficiency of identity authentication, and eliminating the need to provide the original identity data multiple times, thereby improving the security of the identity authentication data.
[0105] In actual applications, the first blockchain may include a first consortium chain; the second blockchain may include a second consortium chain; the first consortium chain, the second consortium chain, and the identity authentication service may be connected via a preset relay service engine. The consortium may be understood as a blockchain business group consisting of several members, with consortium members participating in the construction of the blockchain network. A consortium chain may be understood as a permissioned blockchain jointly managed by several groups, each of which operates one or more nodes. Data within the consortium is only accessible to different groups within the system for reading, writing, and sending transactions, and transaction data is jointly recorded. In actual implementation, both the first and second consortium chains may be intra-group consortium chains, which may be understood as a consortium deployed only within a group. The identity authentication service may enable authorized data exchange between different organizations, groups, or between groups. The relay service engine may provide a unified data relay bridge service between the first and second consortium chains and the identity authentication service. In actual implementation, the first and second consortium chains and the identity authentication service typically utilize a unified identity identification specification, such as the DID specification, for mutual recognition and interoperability.
[0106] To further understand the above embodiments, the identity chain is used as an example for illustration. The identity chain provides a solution for associating, collecting, storing, transmitting, and authenticating the attribute characteristics of entities such as people, objects, and groups in the real world with identity credentials in the virtual world. The identity chain stores the hash value of the digital identity key data and the hash value of the original data of the entity object on the blockchain. The digital identity key data and original data can be stored in a distributed storage system.
[0107] Based on the functional differences of identity chains in different scenarios, identity chains are categorized as intra-group identity chains (corresponding to the first and / or second blockchains mentioned above) and open identity chains (corresponding to the identity authentication service mentioned above). An intra-group identity chain can be understood as an intra-group consortium chain deployed within a specific organization to coordinate and manage the identity data of entities within that group. It can be deployed within various industry groups, such as banks, insurance companies, and corporate groups. The storage and use of data are subject to oversight by relevant industry regulators, and its design must meet relevant regulatory requirements. An open identity chain can be understood as an open consortium chain that encrypts the transmission, authorizes use, and authenticates the authenticity of entity identity data between different organizations. Its design must take into account requirements such as data privacy protection, regulation, and authorized data use. Both intra-group and open identity chains can be implemented as independent products. For example, the open identity chain can be understood as a separate service, while the intra-group identity chain is a concrete product. The open identity chain can provide external services through interfaces, connecting to intra-group identity chains 1, 2, or 3, etc. All that is required is for the node devices in the intra-group identity chain to provide relevant data through these interfaces. The group's internal identity chain and the open identity chain can also be combined into the same product.
[0108] In actual implementation, the intra-group identity chain can adopt an intra-group alliance chain for the coexistence and sharing of digital credential data, providing real-name authentication between various node devices within the group; the open identity chain can adopt an open alliance chain for the ecological mutual recognition and interoperability of digital credential data, providing identity authentication within the intra-group identity chain across the group. Both are built on different alliance chains, that is, the identity chain system adopts a dual-chain architecture of intra-group alliance chain and open alliance chain. The two chains interact through a unified DID specification and relay service engine. For example, if a group corresponds to a bank, the open identity chain can be used for identity authentication of the authentication entity objects between multiple different banks.
[0109] The following is an explanation of some terms related to the identity chain. Among them, the group can be understood as the entity that deploys the identity chain within the group. It is the owner of the identity chain platform within the group and a participant in the open identity chain. The group DID can be understood as the system DID of the identity chain within the group. The group is also a management agency. The management agency can be understood as an agency involved in the operation of the platform. It can maintain and use the identity information of individual entities and group entities within its business scope, and can issue and verify identity credentials. The management agency can also maintain the permissions of its branch groups and group users. The management agency itself is also a group entity, and its group users are also individual entities. Among them, the individual entity can be understood as an entity registered with an individual as the DID. It can maintain personal identity information and authorize identity information through the C-end Client. Here, the C-end represents the individual consumer. The group entity is an entity registered with the group as the DID. It can maintain the identity information of an enterprise or organization and authorize identity information through the B-end Client. Here, the B-end represents the business user.
[0110] In actual implementation, each group usually has its own unique regulator, which owns the super key of the group. The regulator is the industry regulatory unit of the group that deploys the identity chain. It has regulatory authority over the operation and data of the identity chain within the group and can perform unlimited query operations on the data within the group system through the supervision client.
[0111] To further understand the above embodiments, the following is provided: Figure 7 A schematic diagram of an identity authentication system architecture is shown, which includes an open identity chain (corresponding to the above-mentioned identity authentication service), a relay service engine, and multiple intra-group identity chains (corresponding to the above-mentioned first blockchain or second blockchain). The multiple intra-group identity chains are intra-group identity chain 1, intra-group identity chain 2, through intra-group identity chain M. The number of intra-group identity chains can be set according to actual application scenarios or needs. Each intra-group identity chain includes multiple nodes, such as node 1, node 2, through node N. The number of nodes contained in each intra-group identity chain can also be set according to actual application scenarios or needs.
[0112] The relay service engine can provide a unified data relay bridging service for multiple intra-group identity chains and open identity chains. Multiple intra-group identity chains and open identity chains can mutually recognize and communicate with each other through a unified DID specification. For example, the identity identifier of the entity object to be authenticated is stored in the intra-group identity chain 1. When the entity object to be authenticated in the intra-group identity chain 1 sends an identity authentication request to the open identity chain through a terminal device, the identity identifier of the entity object to be authenticated is extracted from the identity authentication request; based on the identity identifier, the identity file corresponding to the identity identifier of the entity object to be authenticated is queried from the intra-group identity chain 1. Based on the queried identity file, the authentication result of the entity object to be authenticated is obtained, which realizes the coexistence and sharing of identity authentication data between each node device in the intra-group identity chain 1.
[0113] Taking the example that both the intra-group identity chain 1 and the intra-group identity chain 2 are communicatively connected to the open identity chain, and only the intra-group identity chain 2 stores the identity identifier of the entity object to be authenticated, when the entity object to be authenticated in the intra-group identity chain 1 sends an identity authentication request to the open identity chain through the terminal device, the identity identifier of the entity object to be authenticated is extracted from the identity authentication request; based on the identity identifier, the identity file corresponding to the identity identifier of the entity object to be authenticated is queried from the intra-group identity chain 2, and the authentication result of the entity object to be authenticated is obtained based on the queried identity file, thereby realizing the mutual recognition and intercommunication of identity authentication data between the intra-group identity chain 1 and the intra-group identity chain 2.
[0114] The identity data of entities in the real world are mapped to the identity chain, and its attributes usually include DID (corresponding to the above-mentioned identity identifier), DID Document (corresponding to the above-mentioned identity file), DID Data (corresponding to the above-mentioned identity information), DID Redentials (corresponding to the above-mentioned identity credentials) and other elements.
[0115] In the identity chain system, DID can be used to uniquely identify entities such as people, groups, and objects. Through DID, the relevant archival data and verification methods of the entity it represents can be found in the identity chain system. In an optional embodiment of the present invention, the formulation of relevant specifications can refer to the W3C Decentralized Identifiers (DIDs) v1.0 specification and the W3C Verifiable Credentials Data Model 1.0 specification; among them, the W3C Decentralized Identifiers (DIDs) v1.0 specification is a distributed ID specification promulgated by the W3C organization; the W3C Verifiable Credentials Data Model 1.0 specification is a verifiable credential data model specification promulgated by the W3C organization. It is understood that the formulation specifications of identity identification, identity archives, identity information, and identity credentials in the embodiments of the present invention are not limited to the above examples. The present invention does not limit the specific formulation specifications used. The formulation specifications and implementation standards in the embodiments of the present invention are only examples.
[0116] A DID Document, also known as a DID archive, typically contains a set of datasets that describe the DID's characteristics and conform to the JSON-LD standard (JavaScript Object Notation for Linked Data, a method for representing and transmitting interconnected data based on JSON, which can be understood as a lightweight data exchange format). This includes, for example, the public key, authentication, services, and other data corresponding to the DID. A DID Document typically does not include the specific attributes or characteristic data of the entity corresponding to the DID, such as name, ID number, or contact number. To obtain identity information such as the entity's specific attributes or characteristic data, or other DID-related services, you must access the access address for the entity's identity information provided in the DID Document. There is a one-to-one relationship between a DID and a DID Document, and DID Documents are typically stored on the blockchain, rather than in a database or centralized server.
[0117] DID Data can be understood as a JSON-compliant dataset representing the detailed attributes or characteristics of the entity corresponding to the DID, such as name, ID number, and contact number. DID Data is not stored directly on the blockchain, but rather in the data system owned by the data provider or storage group. This data system can be the distributed storage system of the blockchain group. The DID Document defines the URI for retrieving DID Data (corresponding to the access address mentioned above). The DID Data structure must conform to the DID Data Schema.
[0118] DID Data Schema is equivalent to a DID Data data template, which is usually saved on the blockchain and is completely public. It defines information such as DID Data data type, attribute definition, KYC (Know Your Customer) level, etc.
[0119] DID Credentials are equivalent to identity credentials, and are usually verifiable electronic credentials provided by groups or individuals that join the identity chain system to prove the identity of the DID entity. Based on each DID, any number of Credentials can be issued, and a Credential may contain several data items in the DID Data. The publisher of the DID Credential can be called the Issuer, and the structured data related to the entity corresponding to the DID issued by the Issuer in accordance with the DID Data Schema definition can be called the Claim. The verifier who verifies the authenticity of the DID Credential can be called the Verifier; the holder of the issued DID Credential can be called the Holder. The Holder applies to the Issuer for the issuance of the DID Credential and provides it to the Verifier for verification. It is generally the entity represented by the DID in the DID Credentials. The data structure in DID Credentials usually needs to conform to the DID Credential Schema definition.
[0120] DID Credential Schema is equivalent to a DID identity credential template, which is usually a verifiable electronic credential provided by a group or individual joining the identity chain system to prove the identity of the DID entity.
[0121] To further understand the above embodiments, the following is provided: Figure 8The figure shows a relationship diagram of identity data, where Entity represents the entity object to be authenticated, DID is the identity identifier used to represent the Entity, and DID Document is a DID file used to explain the DID characteristics, including the access address corresponding to the Entity's DID Data. The access address points to the DID Data. The DID Data is used to specifically describe the detailed attributes or characteristics of the Entity. Based on each DID, several DID Credentials can be published. The data items contained in the DID Credentials usually depend on the data items in the DID Data. Each DID Credential can contain several data items in the DID Data.
[0122] The following uses the identity chain's application in a bank's KYC scenario as an example. For example, a customer named Zhang successfully opens an account at a bank. During the account opening process, when the real-name authentication is completed, the bank generates a unique DID corresponding to Zhang. Only basic identity credentials are generated when opening the account, and other derived identity credentials can be generated based on later needs. For example, if Zhang goes to the traffic police department, he may need to generate his corresponding driver's license.
[0123] If Mr. Zhang needs to open an account at the bank in Singapore, under the current model, he would need to submit real-name authentication documents again at the bank in Singapore. Once the bank deploys the identity chain system, Mr. Zhang will only need to submit real-name authentication documents once at the bank and can conduct business at all of the bank's branches worldwide. This is equivalent to an intra-group identity chain application scenario, which can be extended to open identity chain application scenarios. For example, the bank can achieve identity chain interoperability with other banks or groups, share real-name authentication documents with customer authorization, and realize the application of identity chain across groups or organizations. The identity chain can be tried for cross-domain mutual recognition of driving licenses and graduation certificates.
[0124] In practice, when a customer conducts business at another branch of the same bank, they usually only need to provide their DID. If a customer needs to conduct business at a different bank, they usually need to query the DID document on the identity chain that stores the customer's identity based on the DID, and finally obtain the DID data based on the access address of the DID data stored in the DID document.
[0125] The embodiment of the present invention provides a structural diagram of an identity authentication device, such as Figure 9As shown, the device includes: a first acquisition module 90, which is used to obtain the identity identifier of the entity object to be authenticated; a first sending module 91, which is used to send an identity authentication request to the identity authentication service according to the identity identifier, wherein the identity authentication request is used to request authentication of the identity of the entity object to be authenticated, and the identity authentication service is used to obtain the authentication result of the entity object to be authenticated recorded on the first blockchain and / or the second blockchain according to the identity identifier, and the objects to which the first blockchain and the second blockchain belong are different; a receiving module 92, which is used to receive the authentication result sent by the identity authentication service in response to the identity authentication request.
[0126] An embodiment of the present invention provides an identity authentication device that first sends an identity authentication request to an identity authentication service based on the identity identifier of the entity object to be authenticated, wherein the identity authentication request is used to request authentication of the identity of the entity object to be authenticated, and the identity authentication service is used to obtain the authentication result of the entity object to be authenticated recorded on the first blockchain and / or the second blockchain based on the identity identifier, and then receives the authentication result sent by the identity authentication service in response to the identity authentication request. In this device, the entity object to be authenticated only needs to perform identity authentication once, and then can obtain the authentication result of the entity object to be authenticated recorded on the first blockchain and / or the second blockchain through the identity authentication service based on the identity identifier, thereby realizing the coexistence and sharing of identity authentication data within the same group, or the mutual recognition and intercommunication of identity authentication data across groups, thereby improving the efficiency of identity authentication, and eliminating the need to provide the original identity data multiple times, thereby improving the security of the identity authentication data.
[0127] Furthermore, when the identity identifier of the entity object to be authenticated is stored in the first blockchain, the identity identifier of the entity object to be authenticated stored in the first blockchain is used to indicate the authentication result of the entity object to be authenticated, wherein the first blockchain also stores the identity file corresponding to the identity identifier of the entity object to be authenticated; when the identity identifier of the entity object to be authenticated is stored in the second blockchain, the identity identifier of the entity object to be authenticated stored in the second blockchain is used to indicate the authentication result of the entity object to be authenticated, wherein the second blockchain also stores the identity file corresponding to the identity identifier of the entity object to be authenticated; wherein the identity file is used to provide an access method for the real identity information of the entity object to be authenticated; the device is further used to: send an authentication result selection instruction to the identity authentication service; the authentication result selection instruction is used to select a target authentication result from the authentication results; and receive the identity file and / or real identity information of the entity object to be authenticated sent by the identity authentication service based on the target authentication result.
[0128] Furthermore, when the identity identifier of the entity object to be authenticated is stored in the first blockchain, the identity identifier of the entity object to be authenticated stored in the first blockchain is used to indicate the authentication result of the entity object to be authenticated being passed, wherein the first blockchain also stores the identity file corresponding to the identity identifier of the entity object to be authenticated; when the identity identifier of the entity object to be authenticated is stored in the second blockchain, the identity identifier of the entity object to be authenticated stored in the second blockchain is used to indicate the authentication result of the entity object to be authenticated being passed, wherein the second blockchain also stores the identity file corresponding to the identity identifier of the entity object to be authenticated; wherein the identity file is used to provide an access method to the real identity information of the entity object to be authenticated; and the authentication result includes: the real identity information and / or identity file of the entity object to be authenticated.
[0129] The identity authentication device provided in the embodiment of the present invention has the same implementation principle and technical effects as those of the aforementioned identity authentication method embodiment. For the sake of brief description, any matters not mentioned in the embodiment of the identity authentication device can be referred to the corresponding content in the aforementioned identity authentication method embodiment.
[0130] The embodiment of the present invention provides a structural diagram of another identity authentication device, such as Figure 10 As shown, the apparatus includes: a second acquisition module 100, used to obtain an identity authentication request sent by a terminal device, wherein the identity authentication request is used to request authentication of the identity of the entity object to be authenticated; a third acquisition module 101, used to obtain the identity identifier of the entity object to be authenticated according to the identity authentication request; a fourth acquisition module 102, used to obtain the authentication result of the entity object to be authenticated recorded on the first blockchain and / or the second blockchain according to the identity identifier, where the objects to which the first blockchain and the second blockchain belong are different; a second sending module 103, used to send the authentication result to the terminal device.
[0131] Another identity authentication device provided by an embodiment of the present invention first obtains the identity identifier of the entity object to be authenticated based on the identity authentication request sent by the terminal device; then, based on the identity identifier, obtains the authentication result of the entity object to be authenticated recorded on the first blockchain and / or the second blockchain, and finally sends the authentication result to the terminal device. In this device, the entity object to be authenticated only needs to perform identity authentication once, and then, based on the identity identifier, the authentication result of the entity object to be authenticated recorded on the first blockchain and / or the second blockchain can be obtained through the identity authentication service, thereby realizing the coexistence and sharing of identity authentication data within the same group, or the mutual recognition and intercommunication of identity authentication data across groups, thereby improving the efficiency of identity authentication and eliminating the need to provide the original identity data multiple times, thereby improving the security of the identity authentication data.
[0132] Furthermore, the fourth acquisition module 102 is also used to: obtain the storage result of the identity identifier, wherein the storage result is used to indicate whether the identity identifier of the entity object to be authenticated is stored in the first blockchain and the second blockchain; determine the authentication result of the entity object to be authenticated recorded on the first blockchain and / or the second blockchain based on the storage result, wherein, when the identity identifier of the entity object to be authenticated is stored in the first blockchain, the identity identifier of the entity object to be authenticated stored in the first blockchain is used to indicate that the first blockchain records the authentication result that the entity object to be authenticated is authenticated; when the identity identifier of the entity object to be authenticated is stored in the second blockchain, the identity identifier of the entity object to be authenticated stored in the second blockchain is used to indicate that the second blockchain records the authentication result that the entity object to be authenticated is authenticated.
[0133] Furthermore, the fourth acquisition module 102 is also used to: obtain the authentication result selection instruction sent by the terminal device; the authentication result selection instruction is used to select the target authentication result from the authentication results; based on the authentication result selection instruction, determine the target authentication result; based on the target authentication result, authenticate the true identity information of the entity object to be authenticated.
[0134] Furthermore, the fourth acquisition module 102 is also used for: when the target authentication result is recorded by the first blockchain, the first blockchain also stores an identity file corresponding to the identity identifier of the entity object to be authenticated; the identity file is used to provide an access method for the real identity information of the entity object to be authenticated; the identity file corresponding to the identity identifier of the entity object to be authenticated is queried from the first blockchain; and the authentication result of the entity object to be authenticated is obtained through the queried identity file.
[0135] Furthermore, the fourth acquisition module 102 is also used for: when the target authentication result is recorded by the second blockchain, the second blockchain also stores an identity file corresponding to the identity identifier of the entity object to be authenticated; the identity file is used to provide an access method for the real identity information of the entity object to be authenticated; query the identity file corresponding to the identity identifier of the entity object to be authenticated from the second blockchain; and obtain the authentication result of the entity object to be authenticated through the queried identity file.
[0136] Furthermore, when the identity identifier of the entity object to be authenticated is stored in the first blockchain, the first blockchain also stores an identity profile corresponding to the identity identifier of the entity object to be authenticated; the identity profile is used to provide an access method for the real identity information of the entity object to be authenticated; the fourth acquisition module 102 is further used to: when the identity identifier of the entity object to be authenticated is stored in the first blockchain, query the identity profile corresponding to the identity identifier of the entity object to be authenticated from the first blockchain; and obtain the authentication result of the entity object to be authenticated through the queried identity profile.
[0137] Furthermore, when the identity identifier of the entity object to be authenticated is stored in the second blockchain, the second blockchain also stores an identity profile corresponding to the identity identifier of the entity object to be authenticated; the identity profile is used to provide an access method for the real identity information of the entity object to be authenticated; the fourth acquisition module 102 is further used to: when the identity identifier of the entity object to be authenticated is stored in the second blockchain, query the identity profile corresponding to the identity identifier of the entity object to be authenticated from the second blockchain; and obtain the authentication result of the entity object to be authenticated through the queried identity profile.
[0138] Furthermore, the identity profile includes a hash value of the real identity information of the entity object and an access address of the real identity information of the entity object; the fourth acquisition module 102 is further used to: obtain the real identity information of the entity object to be authenticated through the access address in the queried identity profile; verify whether the real identity information of the entity object to be authenticated has been tampered with through the hash value in the queried identity profile; if the real identity information of the entity object to be authenticated has not been tampered with, determine the real identity information and / or identity profile of the entity object to be authenticated as the authentication result of the entity object to be authenticated.
[0139] Furthermore, the real identity information includes the identity credentials of the entity object; the identity credentials are used to prove that the entity object has the specified identity attributes; the fourth acquisition module 102 is also used to: obtain the identity credentials of the entity object to be authenticated from the real identity information of the entity object to be authenticated; verify whether the obtained identity credentials are legal; if the identity credentials are legal, determine that the entity object to be authenticated has the identity attributes corresponding to the identity credentials.
[0140] The identity authentication device provided in the embodiment of the present invention has the same implementation principle and technical effects as those of the aforementioned identity authentication method embodiment. For the sake of brief description, any matters not mentioned in the embodiment of the identity authentication device can be referred to the corresponding content in the aforementioned identity authentication method embodiment.
[0141] The embodiment of the present invention provides an identity authentication system, such as Figure 11 As shown, the system includes a terminal device 110, an identity authentication service 111, a first blockchain 112, and a second blockchain 113;
[0142] The terminal device 110 is used to: obtain the identity identifier of the entity object to be authenticated; and send an identity authentication request to the identity authentication service 111 according to the identity identifier, wherein the identity authentication request is used to request authentication of the identity of the entity object to be authenticated.
[0143] The identity authentication service 111 is used to: obtain an identity authentication request sent by the terminal device 110; obtain the identity identifier of the entity object to be authenticated based on the identity authentication request; obtain the authentication result of the entity object to be authenticated recorded on the first blockchain 112 and / or the second blockchain 113 based on the identity identifier, where the objects to which the first blockchain 112 and the second blockchain 113 belong are different; and send the authentication result to the terminal device.
[0144] Through the above-mentioned identity authentication system, the KYC requirements of "one-time authentication, multiple uses" within the same group and the identity data transmission and authentication requirements across groups can be taken into account. That is, the digital credential acquisition and storage solution provided by this application takes into account the needs of data coexistence and sharing within the group, as well as the mutual recognition and interoperability of digital credentials across groups or organizations. It can achieve data controllability. In addition, the DID and verifiable credential methods can ensure KYC without exposing private data.
[0145] The embodiment of the present invention further provides an electronic device, see Figure 12 As shown, the electronic device includes a processor 130 and a memory 131. The memory 131 stores machine-executable instructions that can be executed by the processor 130. The processor 130 executes the machine-executable instructions to implement the above-mentioned identity authentication method.
[0146] Furthermore, Figure 12 The electronic device shown further includes a bus 132 and a communication interface 133 , and the processor 130 , the communication interface 133 and the memory 131 are connected via the bus 132 .
[0147] The memory 131 may include high-speed random access memory (RAM) and may also include non-volatile memory, such as at least one disk storage. The communication connection between the system network element and at least one other network element is achieved through at least one communication interface 133 (which may be wired or wireless), and the Internet, wide area network, local area network, metropolitan area network, etc. may be used. The bus 132 may be an ISA bus, a PCI bus, or an EISA bus. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 12 Only one bidirectional arrow is used in the diagram, but this does not mean that there is only one bus or one type of bus.
[0148] The processor 130 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by hardware integrated logic circuits in the processor 130 or by software instructions. The above processor 130 may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it may also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present invention. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in conjunction with the embodiments of the present invention can be directly implemented and executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium well-known in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in memory 131, and processor 130 reads information in memory 131 and, in conjunction with its hardware, completes the steps of the method of the aforementioned embodiment.
[0149] An embodiment of the present invention also provides a machine-readable storage medium, which stores machine-executable instructions. When the machine-executable instructions are called and executed by the processor, the machine-executable instructions prompt the processor to implement the above-mentioned identity authentication method. The specific implementation can be found in the method embodiment and will not be repeated here.
[0150] The computer program products of the identity authentication methods, devices, systems, and electronic devices provided in the embodiments of the present invention include a computer-readable storage medium storing program code. The instructions included in the program code can be used to execute the methods described in the previous method embodiments. For specific implementation, please refer to the method embodiments and will not be repeated here.
[0151] If the functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the portion that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in various embodiments of the present invention. The aforementioned storage media include various media capable of storing program code, such as USB flash drives, mobile hard drives, read-only memories (ROMs), random access memories (RAMs), magnetic disks, or optical disks.
[0152] Finally, it should be noted that the above embodiments are only specific implementation methods of the present invention, which are used to illustrate the technical solutions of the present invention, rather than to limit them. The scope of protection of the present invention is not limited thereto. Although the present invention has been described in detail with reference to the above embodiments, those skilled in the art should understand that any person skilled in the art can modify or easily conceive of changes to the technical solutions described in the above embodiments within the technical scope disclosed by the present invention, or replace some of the technical features therein with equivalents. Such modifications, changes or replacements do not deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should be included in the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be based on the scope of protection of the claims.
Claims
1. An identity authentication method, characterized in that: include: Obtain the identity of the entity object to be authenticated; According to the identity identifier, an identity authentication request is sent to an identity authentication service, wherein the identity authentication request is used to request authentication of the identity of the entity object to be authenticated, and the identity authentication service is used to obtain the authentication result of the entity object to be authenticated recorded on the first blockchain and / or the second blockchain according to the identity identifier, and the first blockchain and the second blockchain belong to different objects; Receiving the authentication result sent by the identity authentication service in response to the identity authentication request; In the case where the identity identifier of the entity object to be authenticated is stored in the first blockchain, the identity identifier of the entity object to be authenticated stored in the first blockchain is used to indicate an authentication result of passing the authentication of the entity object to be authenticated, wherein the first blockchain also stores an identity file corresponding to the identity identifier of the entity object to be authenticated; In the case where the identity identifier of the entity object to be authenticated is stored in the second blockchain, the identity identifier of the entity object to be authenticated stored in the second blockchain is used to indicate the authentication result of the entity object to be authenticated, wherein the second blockchain also stores an identity file corresponding to the identity identifier of the entity object to be authenticated; wherein the identity file is used to provide an access method for the real identity information of the entity object to be authenticated; The authentication result includes: the real identity information and / or identity file of the entity object to be authenticated.
2. The method according to claim 1, characterized in that After the step of receiving the authentication result sent by the identity authentication service in response to the identity authentication request, the method further includes: Sending an authentication result selection instruction to the identity authentication service; the authentication result selection instruction is used to select a target authentication result from the authentication results; Receive the identity profile and / or real identity information of the entity object to be authenticated sent by the identity authentication service based on the target authentication result.
3. An identity authentication method, characterized in that: include: Obtaining an identity authentication request sent by a terminal device, wherein the identity authentication request is used to request authentication of the identity of an entity object to be authenticated; According to the identity authentication request, obtaining the identity identifier of the entity object to be authenticated; According to the identity identifier, obtaining an authentication result of the entity object to be authenticated recorded on the first blockchain and / or the second blockchain, where the first blockchain and the second blockchain belong to different objects; Sending the authentication result to the terminal device; In the case where the identity identifier of the entity object to be authenticated is stored in the first blockchain, the identity file corresponding to the identity identifier of the entity object to be authenticated is also stored in the first blockchain; The step of obtaining the authentication result of the entity object to be authenticated recorded on the first blockchain according to the identity identifier includes: In a case where the identity identifier of the entity object to be authenticated is stored in the first blockchain, querying the identity file corresponding to the identity identifier of the entity object to be authenticated from the first blockchain; Obtaining the authentication result of the entity object to be authenticated through the queried identity file; In the case where the identity identifier of the entity object to be authenticated is stored in the second blockchain, the identity file corresponding to the identity identifier of the entity object to be authenticated is also stored in the second blockchain; the identity file is used to provide an access method for the real identity information of the entity object to be authenticated; The step of obtaining the authentication result of the entity object to be authenticated recorded on the second blockchain according to the identity identifier includes: In a case where the identity identifier of the entity object to be authenticated is stored in the second blockchain, querying the identity file corresponding to the identity identifier of the entity object to be authenticated from the second blockchain; The authentication result of the entity object to be authenticated is obtained through the queried identity file.
4. The method according to claim 3, characterized in that The step of obtaining, according to the identity identifier, an authentication result of the entity object to be authenticated recorded on the first blockchain and / or the second blockchain comprises: obtaining a storage result of the identity identifier, wherein the storage result is used to indicate whether the identity identifier of the entity object to be authenticated is stored in the first blockchain and the second blockchain; According to the stored result, the authentication result of the entity object to be authenticated recorded on the first blockchain and / or the second blockchain is determined, wherein, when the identity identifier of the entity object to be authenticated is stored in the first blockchain, the identity identifier of the entity object to be authenticated stored in the first blockchain is used to indicate that the first blockchain records the authentication result of the entity object to be authenticated being passed, and when the identity identifier of the entity object to be authenticated is stored in the second blockchain, the identity identifier of the entity object to be authenticated stored in the second blockchain is used to indicate that the second blockchain records the authentication result of the entity object to be authenticated being passed.
5. The method according to claim 4, characterized in that After the step of determining the authentication result of the entity object to be authenticated recorded on the first blockchain and / or the second blockchain according to the stored result, the method further includes: Acquire an authentication result selection instruction sent by the terminal device; the authentication result selection instruction is used to select a target authentication result from the authentication results; Selecting an instruction based on the authentication result to determine a target authentication result; Based on the target authentication result, the real identity information of the entity object to be authenticated is authenticated.
6. The method according to claim 5, characterized in that The step of authenticating the real identity information of the entity object to be authenticated based on the target authentication result includes: In the case where the target authentication result is recorded by the first blockchain, the first blockchain also stores an identity file corresponding to the identity identifier of the entity object to be authenticated; the identity file is used to provide an access method for the real identity information of the entity object to be authenticated; The identity file corresponding to the identity identifier of the entity object to be authenticated is queried from the first blockchain; and the authentication result of the entity object to be authenticated is obtained through the queried identity file.
7. The method according to claim 5, characterized in that The step of authenticating the real identity information of the entity object to be authenticated based on the target authentication result includes: In the case where the target authentication result is recorded by the second blockchain, the second blockchain also stores an identity file corresponding to the identity identifier of the entity object to be authenticated; the identity file is used to provide an access method for the real identity information of the entity object to be authenticated; The identity file corresponding to the identity identifier of the entity object to be authenticated is queried from the second blockchain; and the authentication result of the entity object to be authenticated is obtained through the queried identity file.
8. The method according to any one of claims 6-7, characterized in that: The identity profile includes a hash value of the real identity information of the entity object and an access address of the real identity information of the entity object; The step of obtaining the authentication result of the entity object to be authenticated by querying the identity file includes: Obtain the real identity information of the entity object to be authenticated by using the access address in the queried identity file; verify whether the real identity information of the entity object to be authenticated has been tampered with by using the hash value in the queried identity file; If the real identity information of the entity object to be authenticated has not been tampered with, the real identity information and / or identity file of the entity object to be authenticated is determined as the authentication result of the entity object to be authenticated.
9. The method according to claim 8, characterized in that The real identity information includes the identity certificate of the entity object; the identity certificate is used to prove that the entity object has the specified identity attribute; Before the step of determining the real identity information and / or identity file of the entity object to be authenticated as the authentication result of the entity object to be authenticated, the method further includes: Obtaining the identity credential of the entity object to be authenticated from the real identity information of the entity object to be authenticated; Verify whether the obtained identity credential is legal; if the identity credential is legal, determine whether the entity object to be authenticated has the identity attribute corresponding to the identity credential.
10. An identity authentication device, characterized in that: include: A first acquisition module, used to acquire the identity of the entity object to be authenticated; A first sending module, configured to send an identity authentication request to an identity authentication service according to the identity identifier, wherein the identity authentication request is used to request authentication of the identity of the entity object to be authenticated, and the identity authentication service is used to obtain an authentication result of the entity object to be authenticated recorded on a first blockchain and / or a second blockchain according to the identity identifier, and the first blockchain and the second blockchain belong to different objects; A receiving module, configured to receive the authentication result sent by the identity authentication service in response to the identity authentication request; In the case where the identity identifier of the entity object to be authenticated is stored in the first blockchain, the identity identifier of the entity object to be authenticated stored in the first blockchain is used to indicate an authentication result of passing the authentication of the entity object to be authenticated, wherein the first blockchain also stores an identity file corresponding to the identity identifier of the entity object to be authenticated; In the case where the identity identifier of the entity object to be authenticated is stored in the second blockchain, the identity identifier of the entity object to be authenticated stored in the second blockchain is used to indicate the authentication result of the entity object to be authenticated, wherein the second blockchain also stores an identity file corresponding to the identity identifier of the entity object to be authenticated; wherein the identity file is used to provide an access method for the real identity information of the entity object to be authenticated; The authentication result includes: the real identity information and / or identity file of the entity object to be authenticated.
11. An identity authentication device, characterized in that: include: A second acquisition module is used to acquire an identity authentication request sent by a terminal device, wherein the identity authentication request is used to request authentication of the identity of the entity object to be authenticated; A third acquisition module, used to acquire the identity identifier of the entity object to be authenticated according to the identity authentication request; a fourth acquisition module, configured to acquire, according to the identity identifier, an authentication result of the entity object to be authenticated recorded on the first blockchain and / or the second blockchain, where the first blockchain and the second blockchain belong to different objects; A second sending module, used to send the authentication result to the terminal device; In the case where the identity identifier of the entity object to be authenticated is stored in the first blockchain, the first blockchain also stores an identity file corresponding to the identity identifier of the entity object to be authenticated; the identity file is used to provide an access method for the real identity information of the entity object to be authenticated; The fourth acquisition module is also used for: In a case where the identity identifier of the entity object to be authenticated is stored in the first blockchain, querying the identity file corresponding to the identity identifier of the entity object to be authenticated from the first blockchain; Obtaining the authentication result of the entity object to be authenticated through the queried identity file; In the case where the identity identifier of the entity object to be authenticated is stored in the second blockchain, the identity file corresponding to the identity identifier of the entity object to be authenticated is also stored in the second blockchain; the identity file is used to provide an access method for the real identity information of the entity object to be authenticated; The fourth acquisition module is also used for: In a case where the identity identifier of the entity object to be authenticated is stored in the second blockchain, querying the identity file corresponding to the identity identifier of the entity object to be authenticated from the second blockchain; The authentication result of the entity object to be authenticated is obtained through the queried identity file.
12. An identity authentication system, characterized in that: The system includes a terminal device, an identity authentication service, a first blockchain and a second blockchain; The terminal device is used to: obtain the identity identifier of the entity object to be authenticated; and send an identity authentication request to the identity authentication service according to the identity identifier, wherein the identity authentication request is used to request authentication of the identity of the entity object to be authenticated; The identity authentication service is used to: obtain an identity authentication request sent by a terminal device; obtain an identity identifier of the entity object to be authenticated according to the identity authentication request; obtain an authentication result of the entity object to be authenticated recorded on a first blockchain and / or a second blockchain according to the identity identifier, wherein the first blockchain and the second blockchain belong to different objects; and send the authentication result to the terminal device; In the case where the identity identifier of the entity object to be authenticated is stored in the first blockchain, the identity identifier of the entity object to be authenticated stored in the first blockchain is used to indicate an authentication result of passing the authentication of the entity object to be authenticated, wherein the first blockchain also stores an identity file corresponding to the identity identifier of the entity object to be authenticated; In the case where the identity identifier of the entity object to be authenticated is stored in the second blockchain, the identity identifier of the entity object to be authenticated stored in the second blockchain is used to indicate the authentication result of the entity object to be authenticated, wherein the second blockchain also stores an identity file corresponding to the identity identifier of the entity object to be authenticated; wherein the identity file is used to provide an access method for the real identity information of the entity object to be authenticated; The authentication result includes: the real identity information and / or identity file of the entity object to be authenticated; The step of obtaining the authentication result of the entity object to be authenticated recorded on the first blockchain according to the identity identifier includes: In a case where the identity identifier of the entity object to be authenticated is stored in the first blockchain, querying the identity file corresponding to the identity identifier of the entity object to be authenticated from the first blockchain; Obtaining the authentication result of the entity object to be authenticated through the queried identity file; The step of obtaining the authentication result of the entity object to be authenticated recorded on the second blockchain according to the identity identifier includes: In a case where the identity identifier of the entity object to be authenticated is stored in the second blockchain, querying the identity file corresponding to the identity identifier of the entity object to be authenticated from the second blockchain; The authentication result of the entity object to be authenticated is obtained through the queried identity file.
13. An electronic device, characterized in that: It comprises a processor and a memory, wherein the memory stores machine executable instructions that can be executed by the processor, and the processor executes the machine executable instructions to implement the identity authentication method described in any one of claims 1 to 9.
14. A machine-readable storage medium, characterized in that: The machine-readable storage medium stores machine-executable instructions. When the machine-executable instructions are called and executed by a processor, the machine-executable instructions prompt the processor to implement the identity authentication method described in any one of claims 1-9.
Citation Information
Patent Citations
Authentication methods and devices and electronic equipment
CN109327312A
Service data access method, apparatus and system, and electronic device
CN109327314A
Blockchain platform-based autonomous and supervisable digital identity authentication system
WO2019196834A1
