Identity authentication method and device, equipment and medium

Abstract

The invention relates to an identity authentication method and device, equipment and a medium. The method comprises the following steps: sending a service request to a service platform to indicate the service platform to query an identity authentication result representing that a user has a third-party platform permission from a block chain; if not, encrypting identity plaintext information of the user on the third-party platform by using a public key provided by the trusted component; sending the encrypted identity ciphertext information to the trusted component to indicate the trusted component to generate first verification information, decrypting the identity ciphertext information by using a private key matched with the public key in a trusted domain provided by the trusted component, and sending the first verification information to a third-party platform based on the decrypted identity plaintext information; and sending second verification information to the trusted component to instruct the trusted component to generate an identity authentication result and store the identity authentication result to the block chain after comparing that the second verification information is consistent with the first verification information, the identity authentication result being used for instructing the service platform to provide services for the user. By adopting the method, the privacy data of the user can be protected.

Description

Technical Field

[0001] This application relates to blockchain technology, and more specifically to the field of cross-platform identity authentication, and in particular to an identity authentication method, apparatus, device, and medium. Background Art

[0002] With the advancement of computer technology, cross-platform user authentication is a common occurrence in our daily lives. For example, a service platform may require users to have permissions on a third-party platform before providing services. Therefore, when a user requests a service from a service platform, the platform must first verify whether the user has permissions on the third-party platform. Only after verifying that the user does have permissions will the platform provide the service.

[0003] Traditionally, cross-platform user authentication requires users to send their registered identity information, which is in plain text, to the service platform. The service platform then communicates with the third-party platform based on this plain text information to verify the user's permissions on the third-party platform. However, this plain text information constitutes the user's private data on the third-party platform. Implementing cross-platform authentication by sending this plain text information to the service platform can lead to the leakage of user privacy data. Summary of the Invention

[0004] Based on this, it is necessary to provide an identity authentication method, device, equipment and medium that can protect user privacy data in response to the above technical problems.

[0005] In a first aspect, the present application provides an identity authentication method, the method comprising:

[0006] In response to a user's request triggering operation, a service request is sent to a service platform that requires the user to have third-party platform permissions, wherein the service request is used to instruct the service platform to query the blockchain for an identity authentication result indicating that the user has the third-party platform permissions;

[0007] When the identity authentication result is not found, the public key provided by the trusted component is used to encrypt the plain text identity information of the user registered on the third-party platform to obtain the encrypted identity information;

[0008] Sending the encrypted identity information to the trusted component, where the encrypted identity information is used to instruct the trusted component to generate first verification information; decrypting the encrypted identity information using a private key that matches the public key within a trusted domain provided by the trusted component to obtain the plaintext identity information; and sending the first verification information to the third-party platform based on the obtained plaintext identity information;

[0009] Sending second verification information to the trusted component, where the second verification information is used to instruct the trusted component to compare the second verification information with the first verification information. When the comparison is consistent, generating the identity authentication result, and storing the identity authentication result in the blockchain, the identity authentication result is used to instruct the service platform to provide services to the user.

[0010] In a second aspect, the present application provides an identity authentication device, the device comprising:

[0011] A sending module, configured to trigger an operation in response to a user's request, and send a service request to a service platform that requires the user to have third-party platform permissions, wherein the service request is used to instruct the service platform to query the blockchain for an identity authentication result indicating that the user has the third-party platform permissions;

[0012] An encryption module is used to encrypt the plain text identity information of the user registered on the third-party platform using the public key provided by the trusted component to obtain cipher text identity information when the identity authentication result is not found;

[0013] The sending module is further configured to send the encrypted identity information to the trusted component, where the encrypted identity information is used to instruct the trusted component to generate first verification information, decrypt the encrypted identity information using a private key that matches the public key within a trusted domain provided by the trusted component to obtain the plaintext identity information, and send the first verification information to the third-party platform based on the obtained plaintext identity information;

[0014] The sending module is further used to send second verification information to the trusted component, and the second verification information is used to instruct the trusted component to compare the second verification information with the first verification information. When the comparison is consistent, the identity authentication result is generated and stored in the blockchain. The identity authentication result is used to instruct the service platform to provide services to the user.

[0015] In one embodiment, after generating the first verification information, the trusted component encrypts the first verification information to obtain a first verification ciphertext, and stores the first verification ciphertext. The sending module is also used to encrypt the second verification information using the public key to obtain a second verification ciphertext; send the second verification ciphertext to the trusted component, and the second verification ciphertext is used to instruct the trusted component to obtain and decrypt the pre-stored first verification ciphertext to obtain the first verification information, decrypt the second verification ciphertext using the private key to obtain the second verification information, compare the second verification information with the first verification information, and when the comparison is consistent, generate the identity authentication result, and store the identity authentication result in the blockchain. The identity authentication result is used to instruct the service platform to provide services to the user.

[0016] In one embodiment, the trusted component stores the first verification ciphertext in the blockchain. After receiving the second verification ciphertext, the trusted component obtains the pre-stored first verification ciphertext from the blockchain, and decrypts the obtained first verification ciphertext to obtain the first verification information.

[0017] In one embodiment, after generating the first verification information, the trusted component uses the symmetric encryption key provided by the trusted component to encrypt the first verification information, obtain a first verification ciphertext, and stores the first verification ciphertext. After receiving the second verification ciphertext, the trusted component obtains and uses the symmetric encryption key to decrypt the pre-stored first verification ciphertext to obtain the first verification information.

[0018] In one embodiment, the sending module is further configured to select a service platform from a plurality of candidate service platforms that require the user to have the third-party platform authority in response to the user's platform selection operation; the plurality of candidate service platforms are respectively connected to the blockchain; and in response to the user's request triggering operation for the service platform, a service request is sent to the service platform, wherein the service request is used to instruct the service platform to query the blockchain for an identity authentication result indicating that the user has the third-party platform authority.

[0019] In one embodiment, the sending module is further configured to, in response to a request trigger operation by the user for the service platform, send a service request carrying the user identifier of the user and the platform identifier of the third-party platform to the service platform; wherein the service request is configured to instruct the service platform to query the blockchain for an authentication result stored in association with the user identifier and the platform identifier, and obtain an identity authentication result indicating that the user has authority over the third-party platform.

[0020] In one embodiment, the sending module is further configured to select a new service platform other than the service platform from the multiple candidate service platforms in response to a new round of platform selection operation by the user; and to send a service request to the new service platform in response to a request trigger operation by the user for the new service platform. The service request sent to the new service platform is used to instruct the new service platform to query the blockchain for an identity authentication result indicating that the user has the authority to the third-party platform, and the identity authentication result is used to instruct the new service platform to provide services to the user.

[0021] In one embodiment, the blockchain also stores the validity period corresponding to the identity authentication result. After receiving the service request, the new service platform queries the blockchain for an identity authentication result that indicates that the user has the third-party platform authority and is within the validity period.

[0022] In one embodiment, the blockchain pre-stores a public key provided by the trusted component. The public key is stored by the blockchain after the blockchain verifies the legitimacy of the trusted component based on the component certification information provided by the trusted component and the public key. The encryption module is also used to obtain the pre-stored public key provided by the trusted component from the blockchain when the identity authentication result is not queried and the user trusts the blockchain, and use the public key to encrypt the plaintext identity information of the user registered on the third-party platform to obtain the ciphertext identity information.

[0023] In one embodiment, the encryption module is also used to obtain the component certification information and the public key from the trusted component when the identity authentication result is not queried and the user does not trust the blockchain; based on the component certification information and the public key, the legitimacy of the trusted component is verified; when the legitimacy verification of the trusted component is passed, the public key is used to encrypt the plaintext identity information of the user registered on the third-party platform to obtain ciphertext identity information.

[0024] In one embodiment, the apparatus further comprises:

[0025] The receiving module is configured to receive, when the identity authentication result is queried, service authorization information fed back by the service platform and used to indicate that the service platform provides services to the user.

[0026] In one embodiment, the identity plaintext information is the communication information of the electronic media registered by the user on the third-party platform, and the identity ciphertext information is obtained by the trusted component using the public key to encrypt the communication information; the sending module is also used to send the identity ciphertext information to the trusted component, and the identity ciphertext information is used to instruct the trusted component to generate first verification information, and within the trusted domain provided by the trusted component, the identity ciphertext information is decrypted using a private key matching the public key to obtain the communication information, and based on the obtained communication information, the first verification information is sent to the electronic media registered by the user on the third-party platform.

[0027] In a third aspect, the present application provides a computer device including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the steps in the method embodiments of the present application are implemented.

[0028] In a fourth aspect, the present application provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps in the various method embodiments of the present application.

[0029] In a fifth aspect, the present application provides a computer program product, including a computer program, which implements the steps in the method embodiments of the present application when the computer program is executed by a processor.

[0030] The above-mentioned identity authentication method, device, equipment and medium trigger an operation in response to a user's request, and send a service request to a service platform that requires the user to have third-party platform permissions. The service request is used to instruct the service platform to query the blockchain for an identity authentication result that indicates that the user has third-party platform permissions; when no identity authentication result is found, the public key provided by the trusted component is used to encrypt the identity plaintext information of the user registered on the third-party platform to obtain identity ciphertext information; the identity ciphertext information is sent to the trusted component, and the identity ciphertext information is used to instruct the trusted component to generate first verification information. Within the trusted domain provided by the trusted component, the identity ciphertext information is decrypted using a private key matching the public key to obtain identity plaintext information, and the first verification information is sent to the third-party platform based on the obtained identity plaintext information; second verification information is sent to the trusted component, and the second verification information is used to instruct the trusted component to compare the second verification information and the first verification information. When the comparison is consistent, an identity authentication result is generated, and the identity authentication result is stored in the blockchain. The identity authentication result is used to instruct the service platform to provide services to the user. Compared to traditional identity authentication methods, this application introduces a trusted component and blockchain. Users use the public key provided by the trusted component to encrypt their identity information on a third-party platform and then send it to the trusted component. Within the trusted domain provided by the trusted component, the corresponding private key is used to decrypt the identity information. The trusted component then communicates with the third-party platform to provide verification information to the user. After the identity is authenticated, the authentication result is stored on the trusted blockchain. The service platform can then retrieve the authentication result from the blockchain to authenticate the user. This prevents the user from directly sending their identity information to the service platform, thus protecting the user's privacy data on the third-party platform. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Figure 1 A diagram of an application environment of an identity authentication method in one embodiment;

[0032] Figure 2 1 is a flow chart of an identity authentication method according to an embodiment;

[0033] Figure 3 This is a flowchart of the traditional identity authentication method;

[0034] Figure 4 This is an architecture diagram of an identity authentication system in one embodiment;

[0035] Figure 5 This is a schematic diagram of the identity authentication process for a new service platform in one embodiment;

[0036] Figure 6 FIG1 is a schematic diagram of a process for legitimacy verification of a trusted component in one embodiment;

[0037] Figure 7A schematic diagram of a process for user requesting identity authentication in one embodiment;

[0038] Figure 8 A schematic diagram of a cross-platform identity authentication process in one embodiment;

[0039] Figure 9 A schematic diagram of a process for user requesting identity authentication in another embodiment;

[0040] Figure 10 A schematic diagram of a cross-platform identity authentication process in another embodiment;

[0041] Figure 11 A schematic diagram of an identity authentication process in which first verification information is sent via email in one embodiment;

[0042] Figure 12 Schematic diagram of the process of identity authentication method in another embodiment;

[0043] Figure 13 is a structural block diagram of an identity authentication device in one embodiment;

[0044] Figure 14 is a structural block diagram of an identity authentication device in another embodiment;

[0045] Figure 15 FIG. 1 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0046] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0047] The identity authentication method provided in this application can be applied to Figure 1In the application environment shown, terminal 102 communicates with server 104 via a network. A data storage system can be separately configured to store data that server 104 needs to process. The data storage system can be integrated with server 104 or placed in the cloud or on another server. Terminal 102 can be, but is not limited to, various desktop computers, laptops, smartphones, tablets, in-vehicle terminals, intelligent voice interaction devices, aircraft, smart home appliances, and portable wearable devices. Smart home appliances can include smart speakers, smart TVs, and smart air conditioners. Portable wearable devices can include smart watches, smart bracelets, head-mounted devices, etc. Server 104 can be a standalone physical server, a server cluster or distributed system consisting of multiple physical servers, or a cloud server that provides network security services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, cloud security, host security, CDN, and basic cloud computing services such as big data and artificial intelligence platforms. Terminal 102 and server 104 can be connected directly or indirectly via wired or wireless communication, which is not limited in this application.

[0048] It is understandable that the trusted component can be set in the server 104. The terminal 102 can trigger an operation in response to the user's request, and send a service request to the service platform that requires the user to have the third-party platform authority. The service request is used to instruct the service platform to query the blockchain for an identity authentication result that indicates that the user has the third-party platform authority. When the identity authentication result is not found, the terminal 102 can use the public key provided by the trusted component to encrypt the identity plaintext information registered by the user on the third-party platform to obtain the identity ciphertext information. The terminal 102 can send the identity ciphertext information to the trusted component. The identity ciphertext information is used to instruct the trusted component to generate a first verification information. Within the trusted domain provided by the trusted component, the identity ciphertext information is decrypted using a private key that matches the public key to obtain the identity plaintext information, and the first verification information is sent to the third-party platform based on the obtained identity plaintext information. The terminal 102 can send a second verification information to the trusted component. The second verification information is used to instruct the trusted component to compare the second verification information and the first verification information. When the comparison is consistent, an identity authentication result is generated and the identity authentication result is stored in the blockchain. The identity authentication result is used to instruct the service platform to provide services to the user. It is understandable that Figure 1 The application scenarios are only for illustration and are not limited to this.

[0049] In one embodiment, Figure 2 As shown, an identity authentication method is provided. This embodiment uses this method to Figure 1 Taking the terminal 102 in FIG. 1 as an example, the method includes the following steps:

[0050] Step 202, in response to the user's request triggering operation, sends a service request to the service platform that requires the user to have third-party platform permissions. The service request is used to instruct the service platform to query the blockchain for an identity authentication result indicating that the user has third-party platform permissions.

[0051] Specifically, the service platform requires the user to have the third-party platform's permissions before it can provide the corresponding service. Therefore, when a user initiates a request trigger operation against the service platform, the terminal can respond to the user's request trigger operation and send a service request to the service platform. The service platform can receive the service request sent by the terminal and query the blockchain for the identity authentication result indicating that the user has the third-party platform's permissions.

[0052] In one embodiment, a blockchain can be connected to a service platform. In response to a user's request to trigger an operation on the blockchain-connected service platform, the terminal can send a service request to the blockchain-connected service platform. The blockchain-connected service platform can receive the service request sent by the terminal and query the blockchain for an identity authentication result indicating that the user has permission to use the third-party platform.

[0053] In one embodiment, the content of the identity authentication result may specifically be "the user has the authority of the third-party platform."

[0054] In step 204, when no identity authentication result is found, the public key provided by the trusted component is used to encrypt the plain text identity information registered by the user on the third-party platform to obtain the encrypted identity information.

[0055] Specifically, when no identity authentication result is found, the terminal can obtain the plaintext identity information of the user registered on the third-party platform, and obtain the public key provided by the trusted component, and use the public key to encrypt the plaintext identity information of the user registered on the third-party platform to obtain the encrypted identity information.

[0056] In one embodiment, the trusted component stores the component certification information and public key of the trusted component, wherein the component certification information is information used to prove whether the trusted component is legitimate. The terminal can obtain the component certification information and public key from the trusted component and verify the legitimacy of the trusted component based on the component certification information and public key. When the legitimacy verification of the trusted component passes, it means that the trusted component is trustworthy. The terminal can use the public key to encrypt the user's identity plaintext information registered on the third-party platform to obtain the identity ciphertext information. When the legitimacy verification of the trusted component fails, it means that the trusted component is untrustworthy, and the terminal can terminate the identity authentication process.

[0057] In one embodiment, the identity plain text information may include at least one piece of information such as an email address, a mobile phone number, or an instant messaging account of the third-party platform registered by the user.

[0058] Step 206: Send identity encrypted information to the trusted component. The identity encrypted information is used to instruct the trusted component to generate first verification information. Within the trusted domain provided by the trusted component, the identity encrypted information is decrypted using a private key that matches the public key to obtain identity plaintext information. The first verification information is sent to the third-party platform based on the obtained identity plaintext information.

[0059] The trusted component provides a trusted domain, a hardware-based secure computing environment. Data within the trusted domain cannot be accessed by the external environment without active output. Decrypting the ciphertext identity information within the trusted domain to obtain the plaintext identity information, and sending the first verification information to the third-party platform based on the obtained plaintext identity information, can ensure that the plaintext identity information cannot be obtained by the service platform, thereby protecting the user's private data on the third-party platform.

[0060] Specifically, the terminal can send encrypted identity information to the trusted component. After receiving the encrypted identity information sent by the terminal, the trusted component can generate first verification information. Within the trusted domain provided by the trusted component, the trusted component uses the private key that matches the public key to decrypt the received encrypted identity information to obtain plaintext identity information. Based on the obtained plaintext identity information, the generated first verification information is sent to the third-party platform. It is understood that the first verification information sent to the third-party platform can be obtained by the user.

[0061] Step 208: Send the second verification information to the trusted component. The second verification information is used to instruct the trusted component to compare the second verification information with the first verification information. When the comparison is consistent, an identity authentication result is generated and stored in the blockchain. The identity authentication result is used to instruct the service platform to provide services to the user.

[0062] Specifically, the terminal can obtain the second verification information entered by the user and send the second verification information to the trusted component. After obtaining the second verification information sent by the terminal, the trusted component can compare the second verification information with the first verification information. When the second verification information and the first verification information are consistent, an identity authentication result is generated, indicating that the user has permission to access the third-party platform, and the identity authentication result is stored in the blockchain. The service platform can obtain the identity authentication result from the blockchain and provide services to the user after obtaining the identity authentication result. It can be understood that if the user has permission to access the third-party platform, the user can obtain the first verification information from the third-party platform and enter the first verification information into the terminal. In this case, the first verification information entered by the user becomes the second verification information, and the second verification information is consistent with the first verification information. If the user does not have permission to access the third-party platform, the user cannot obtain the first verification information from the third-party platform. In this case, the user enters the second verification information on their own, and the second verification information is inconsistent with the first verification information.

[0063] In one embodiment, after obtaining the identity authentication result, the service platform may also feed back to the terminal service authorization information indicating that the service platform provides services to the user, so as to prompt the user that the identity authentication has been passed.

[0064] In one embodiment, the terminal may send the second verification information itself to the trusted component. It is understood that in this embodiment, the second verification information is not encrypted before being sent to the trusted component.

[0065] In the above-mentioned identity authentication method, an operation is triggered in response to a user's request, and a service request is sent to a service platform that requires the user to have third-party platform permissions. The service request is used to instruct the service platform to query the blockchain for an identity authentication result indicating that the user has third-party platform permissions; when no identity authentication result is found, the public key provided by the trusted component is used to encrypt the identity plaintext information of the user registered on the third-party platform to obtain identity ciphertext information; the identity ciphertext information is sent to the trusted component, and the identity ciphertext information is used to instruct the trusted component to generate first verification information. Within the trusted domain provided by the trusted component, the identity ciphertext information is decrypted using a private key matching the public key to obtain identity plaintext information, and the first verification information is sent to the third-party platform based on the obtained identity plaintext information; second verification information is sent to the trusted component, and the second verification information is used to instruct the trusted component to compare the second verification information and the first verification information. When the comparison is consistent, an identity authentication result is generated, and the identity authentication result is stored in the blockchain. The identity authentication result is used to instruct the service platform to provide services to the user. Compared to traditional identity authentication methods, this application introduces a trusted component and blockchain. Users use the public key provided by the trusted component to encrypt their identity information on a third-party platform and then send it to the trusted component. Within the trusted domain provided by the trusted component, the corresponding private key is used to decrypt the identity information. The trusted component then communicates with the third-party platform to provide verification information to the user. After the identity is authenticated, the authentication result is stored on the trusted blockchain. The service platform can then retrieve the authentication result from the blockchain to authenticate the user. This prevents the user from directly sending their identity information to the service platform, thus protecting the user's privacy data on the third-party platform.

[0066] like Figure 3As shown, if the plaintext identity information is the email address of the email address that the user will register on the third-party platform, in traditional identity authentication methods, cross-platform user identity authentication requires the user to send the email address registered on the third-party platform to the service platform. The service platform's email service will send a verification code generated by the service platform's business system to the email address corresponding to the email address to verify whether the user has the permission of the third-party platform. However, the email address is the user's private data on the third-party platform. Sending the email address to the service platform to achieve cross-platform identity authentication of the user will lead to the leakage of user privacy data. However, this application introduces a trusted component and blockchain. The user uses the public key provided by the trusted component to encrypt the email address registered on the third-party platform and then sends it to the trusted component. The email address is decrypted using the corresponding private key within the trusted domain provided by the trusted component to obtain the email address. The trusted component then communicates with the email address on the third-party platform to provide the user with a verification code. After the identity authentication is passed, the identity authentication result is stored in the trusted blockchain. The service platform can obtain the identity authentication result from the blockchain to achieve user identity authentication, avoiding the user directly sending the email address to the service platform and protecting the user's private data on the third-party platform.

[0067] In one embodiment, after generating the first verification information, the trusted component encrypts the first verification information to obtain the first verification ciphertext, stores the first verification ciphertext, and sends the second verification information to the trusted component, including: encrypting the second verification information with the public key to obtain the second verification ciphertext; sending the second verification ciphertext to the trusted component, the second verification ciphertext is used to instruct the trusted component to obtain and decrypt the pre-stored first verification ciphertext to obtain the first verification information, decrypt the second verification ciphertext with the private key to obtain the second verification information, compare the second verification information with the first verification information, and when the comparison is consistent, generate an identity authentication result, and store the identity authentication result in the blockchain. The identity authentication result is used to instruct the service platform to provide services to the user.

[0068] Specifically, the terminal can trigger an operation in response to a user's request, sending a service request to a service platform that requires the user to have third-party platform permissions. After receiving the service request from the terminal, the service platform can query the blockchain for an identity authentication result indicating that the user has third-party platform permissions. If no identity authentication result is found, the terminal can obtain a public key provided by the trusted component and use it to encrypt the user's plaintext identity information registered on the third-party platform to obtain ciphertext identity information. The terminal can send the ciphertext identity information to the trusted component. After receiving the ciphertext identity information from the terminal, the trusted component can generate first verification information, encrypt the first verification information to obtain first verification ciphertext, store the first verification ciphertext, and decrypt the ciphertext identity information within the trusted domain provided by the trusted component using a private key that matches the public key to obtain the plaintext identity information. Based on the obtained plaintext identity information, the terminal can then obtain second verification information and encrypt the second verification information using the public key to obtain second verification ciphertext. The terminal can send a second verification ciphertext to the trusted component. After receiving the second verification ciphertext, the trusted component can obtain the pre-stored first verification ciphertext, decrypt the first verification ciphertext, obtain the first verification information, use the private key to decrypt the second verification ciphertext, obtain the second verification information, compare the second verification information and the first verification information, and when the comparison is consistent, generate an identity authentication result and store the identity authentication result in the blockchain. The identity authentication result is used to instruct the service platform to provide services to the user.

[0069] In one embodiment, the trusted component may store the first verification ciphertext in a ciphertext database. After receiving the second verification ciphertext, the trusted component obtains the pre-stored first verification ciphertext from the ciphertext database and decrypts the obtained first verification ciphertext to obtain the first verification information.

[0070] In one embodiment, after generating the first verification information, the trusted component may use the public key provided by the trusted component to encrypt the first verification information to obtain a first verification ciphertext, and then store the first verification ciphertext. After receiving the second verification ciphertext, the trusted component may use the private key that matches the public key provided by the trusted component to decrypt the pre-stored first verification ciphertext to obtain the first verification information.

[0071] In the above embodiment, the first verification information is encrypted by the trusted component to obtain the first verification ciphertext, which is then stored. This prevents leakage of the first verification information and ensures the security of the first verification information. The second verification information is encrypted using the public key to obtain the second verification ciphertext, which is then sent to the trusted component. The trusted component then obtains and decrypts the pre-stored first verification ciphertext to obtain the first verification information, and the private key is used to decrypt the second verification ciphertext to obtain the second verification information. This prevents the second verification information from being obtained by the service platform and ensures its security.

[0072] In one embodiment, the trusted component stores the first verification ciphertext in the blockchain. After receiving the second verification ciphertext, the trusted component obtains the pre-stored first verification ciphertext from the blockchain, decrypts the obtained first verification ciphertext, and obtains the first verification information.

[0073] Specifically, the terminal can trigger an operation in response to a user's request, sending a service request to a service platform that requires the user to have third-party platform permissions. After receiving the service request from the terminal, the service platform can query the blockchain for an identity authentication result indicating that the user has third-party platform permissions. If no identity authentication result is found, the terminal can obtain a public key provided by the trusted component and use it to encrypt the user's plaintext identity information registered on the third-party platform to obtain ciphertext identity information. The terminal can send the ciphertext identity information to the trusted component. After receiving the ciphertext identity information from the terminal, the trusted component can generate first verification information, encrypt the first verification information to obtain first verification ciphertext, store the first verification ciphertext in the blockchain, and decrypt the ciphertext identity information using a private key matching the public key within the trusted domain provided by the trusted component to obtain the plaintext identity information. Based on the obtained plaintext identity information, the first verification information is then sent to the third-party platform. The terminal can obtain second verification information and encrypt the second verification information using the public key to obtain second verification ciphertext. The terminal can send a second verification ciphertext to the trusted component. After receiving the second verification ciphertext, the trusted component can obtain the pre-stored first verification ciphertext from the blockchain, decrypt the first verification ciphertext, obtain the first verification information, use the private key to decrypt the second verification ciphertext, obtain the second verification information, compare the second verification information and the first verification information, and when the comparison is consistent, generate an identity authentication result and store the identity authentication result in the blockchain. The identity authentication result is used to instruct the service platform to provide services to the user.

[0074] In the above embodiment, the first verification ciphertext is directly stored in the blockchain through the trusted component, avoiding the introduction of additional storage components, thereby saving the maintenance cost for the additional storage components.

[0075] In one embodiment, after generating the first verification information, the trusted component uses the symmetric encryption key provided by the trusted component to encrypt the first verification information, obtain the first verification ciphertext, and store the first verification ciphertext. After receiving the second verification ciphertext, the trusted component obtains and uses the symmetric encryption key to decrypt the pre-stored first verification ciphertext to obtain the first verification information.

[0076] Specifically, the terminal can trigger an operation in response to a user's request, sending a service request to a service platform that requires the user to have third-party platform permissions. After receiving the service request from the terminal, the service platform can query the blockchain for an identity authentication result indicating that the user has third-party platform permissions. If no identity authentication result is found, the terminal can obtain a public key provided by the trusted component and use it to encrypt the user's plaintext identity information registered on the third-party platform to obtain ciphertext identity information. The terminal can send the ciphertext identity information to the trusted component. After receiving the ciphertext identity information from the terminal, the trusted component can generate first verification information, encrypt the first verification information using the symmetric encryption key provided by the trusted component to obtain first verification ciphertext, store the first verification ciphertext, and decrypt the ciphertext identity information using the private key that matches the public key within the trusted domain provided by the trusted component to obtain plaintext identity information. Based on the obtained plaintext identity information, the terminal can then obtain second verification information and encrypt the second verification information using the public key to obtain second verification ciphertext. The terminal can send a second verification ciphertext to the trusted component. After receiving the second verification ciphertext, the trusted component can obtain the pre-stored first verification ciphertext, use the symmetric encryption key to decrypt the first verification ciphertext, obtain the first verification information, use the private key to decrypt the second verification ciphertext, obtain the second verification information, compare the second verification information and the first verification information, generate an identity authentication result when the comparison is consistent, and store the identity authentication result in the blockchain. The identity authentication result is used to instruct the service platform to provide services to the user.

[0077] In the above embodiment, by encrypting the first verification information using the symmetric encryption key provided by the trusted component to obtain the first verification ciphertext, the encryption efficiency of the first verification information can be improved. After receiving the second verification ciphertext, the trusted component uses the symmetric encryption key provided by the trusted component to decrypt the first verification ciphertext to obtain the first verification information. This improves the decryption efficiency of the first verification ciphertext and thus improves the efficiency of identity authentication.

[0078] In one embodiment, in response to a user's request triggering operation, a service request is sent to a service platform that requires the user to have third-party platform permissions, including: in response to the user's platform selection operation, a service platform is selected from multiple candidate service platforms that require the user to have third-party platform permissions; the multiple candidate service platforms are respectively connected to the blockchain; in response to the user's request triggering operation for the service platform, a service request is sent to the service platform, where the service request is used to instruct the service platform to query the blockchain for an identity authentication result indicating that the user has third-party platform permissions.

[0079] Specifically, if Figure 4As shown, a blockchain can connect to multiple candidate service platforms that require users to have third-party platform permissions. In response to a user's platform selection operation, a terminal can select a service platform from the multiple candidate service platforms that require users to have third-party platform permissions. In response to a user's request for a service platform, the terminal can trigger an operation and send a service request to the service platform that requires users to have third-party platform permissions. After receiving the service request, the service platform can query the blockchain for an identity authentication result indicating that the user has third-party platform permissions. If no identity authentication result is found, the terminal can use the public key provided by the trusted component to encrypt the user's plaintext identity information registered on the third-party platform to obtain ciphertext identity information. The terminal can send the ciphertext identity information to the trusted component. Upon receiving the ciphertext identity information, the trusted component can generate first verification information. Within the trusted domain provided by the trusted component, the trusted component can decrypt the ciphertext identity information using the private key that matches the public key to obtain the plaintext identity information. Based on the obtained plaintext identity information, the terminal can send the first verification information to the third-party platform. The terminal can also send second verification information to the trusted component. After receiving the second verification information, the trusted component can compare the second verification information with the first verification information. When the comparison is consistent, it generates an identity authentication result and stores the identity authentication result in the blockchain. The identity authentication result is used to instruct the service platform to provide services to users.

[0080] In the above embodiment, the blockchain can be connected to multiple service platforms to realize the sharing of identity authentication results of third-party platform permissions on multiple service platforms, without having to go through the process of generating identity authentication results based on trusted components and storing them in the blockchain again, thereby improving the efficiency of identity authentication.

[0081] In one embodiment, in response to a user's request triggering operation for the service platform, a service request is sent to the service platform, including: in response to the user's request triggering operation for the service platform, a service request carrying the user's user identifier and the platform identifier of the third-party platform is sent to the service platform; wherein the service request is used to instruct the service platform to query the authentication result stored in association with the user identifier and the platform identifier from the blockchain, and obtain an identity authentication result indicating that the user has authority over the third-party platform.

[0082] Among them, the user identifier is used to uniquely identify the user's identity, and the platform identifier of the third-party platform is used to uniquely identify the third-party platform.

[0083] Specifically, the blockchain can connect to multiple candidate service platforms that require users to have third-party platform permissions. In response to a user's platform selection operation, the terminal can select a service platform from the multiple candidate service platforms that require users to have third-party platform permissions. In response to a user's request triggering operation for a service platform, the terminal can send a service request to the service platform containing the user's user ID and the platform ID of the third-party platform. After receiving the service request, the service platform can query the blockchain for authentication results associated with the user ID and platform ID to obtain an identity authentication result indicating that the user has third-party platform permissions. If no identity authentication result is found, the terminal can use the public key provided by the trusted component to encrypt the user's registered identity plaintext information on the third-party platform to obtain ciphertext identity information. The terminal can send the ciphertext identity information to the trusted component. Upon receiving the ciphertext identity information, the trusted component can generate first verification information and, within the trusted domain provided by the trusted component, decrypt the ciphertext identity information using a private key that matches the public key to obtain the plaintext identity information. Based on the obtained plaintext identity information, the terminal can send the first verification information to the third-party platform. The terminal can also send second verification information to the trusted component. After receiving the second verification information, the trusted component can compare the second verification information with the first verification information. When the comparison is consistent, it generates an identity authentication result and associates the identity authentication result with the user identifier and the platform identifier and stores it in the blockchain. The identity authentication result is used to instruct the service platform to provide services to the user.

[0084] In the above embodiment, based on the user identifier of the user and the platform identifier of the third-party platform, the authentication result stored in association with the user identifier and the platform identifier is queried from the blockchain to obtain an identity authentication result indicating that the user has the authority of the third-party platform. This can improve the query accuracy of the identity authentication result, thereby improving the efficiency of identity authentication.

[0085] In one embodiment, the method further includes: in response to a new round of platform selection operation by the user, selecting a new service platform other than the service platform from multiple candidate service platforms; in response to the user's request triggering operation for the new service platform, sending a service request to the new service platform, where the service request sent to the new service platform is used to instruct the new service platform to query the blockchain for an identity authentication result indicating that the user has third-party platform authority, and the identity authentication result is used to instruct the new service platform to provide services to the user.

[0086] Specifically, the blockchain can connect to multiple candidate service platforms that require users to have third-party platform permissions. In response to a user's platform selection operation, the terminal can select a service platform from the multiple candidate service platforms that require users to have third-party platform permissions. In response to a user's request for a service platform, the terminal can trigger an operation and send a service request to the service platform that requires users to have third-party platform permissions. After receiving the service request, the service platform can query the blockchain for an identity authentication result indicating that the user has third-party platform permissions. If no identity authentication result is found, the terminal can use the public key provided by the trusted component to encrypt the user's plaintext identity information registered on the third-party platform to obtain ciphertext identity information. The terminal can send the ciphertext identity information to the trusted component. Upon receiving the ciphertext identity information, the trusted component can generate first verification information. Within the trusted domain provided by the trusted component, the trusted component can decrypt the ciphertext identity information using a private key that matches the public key to obtain the plaintext identity information. Based on the obtained plaintext identity information, the terminal can send the first verification information to the third-party platform. The terminal can then send second verification information to the trusted component. After receiving the second verification information, the trusted component can compare the second verification information with the first verification information. When the comparison is consistent, it generates an identity authentication result and stores the identity authentication result on the blockchain. The identity authentication result is used to instruct the service platform to provide services to the user. In response to the user's new round of platform selection operation, the terminal can select a new service platform from multiple candidate service platforms in addition to the service platform. In response to the user's request for the new service platform, the terminal can trigger an operation and send a service request to the new service platform. After receiving the service request, the new service platform can query the blockchain for an identity authentication result indicating that the user has permission to the third-party platform. The identity authentication result is used to instruct the new service platform to provide services to the user.

[0087] In one embodiment, Figure 5 As shown, a user can initiate a request trigger operation on a terminal to a new service platform to request cross-platform authentication. In response to the user's request trigger operation, the terminal can send a service request to the new service platform. After receiving the service request, the new service platform can query the blockchain for an identity authentication result indicating that the user has permission to use the third-party platform. This identity authentication result is used to instruct the new service platform to provide services to the user. It is understood that once the new service platform obtains the identity authentication result from the blockchain, it can directly provide services to the user.

[0088] In the above embodiment, after the user reselects a new service platform, the new service platform can directly obtain the identity authentication result of the third-party platform authority from the blockchain to perform identity authentication, without having to go through the process of generating the identity authentication result based on the trusted component and storing it in the blockchain again, thereby improving the efficiency of identity authentication.

[0089] In one embodiment, the blockchain also stores the validity period corresponding to the identity authentication result. After receiving the service request, the new service platform queries the blockchain for the identity authentication result that indicates that the user has the third-party platform authority and is within the validity period.

[0090] Specifically, the blockchain can connect to multiple candidate service platforms that require users to have third-party platform permissions. In response to a user's platform selection operation, the terminal can select a service platform from the multiple candidate service platforms that require users to have third-party platform permissions. In response to a user's request for a service platform, the terminal can trigger an operation and send a service request to the service platform that requires users to have third-party platform permissions. After receiving the service request, the service platform can query the blockchain for an identity authentication result that indicates the user has third-party platform permissions and is within its validity period. If no identity authentication result is found, the terminal can use the public key provided by the trusted component to encrypt the user's plaintext identity information registered on the third-party platform to obtain ciphertext identity information. The terminal can send the ciphertext identity information to the trusted component. Upon receiving the ciphertext identity information, the trusted component can generate first verification information. Within the trusted domain provided by the trusted component, the trusted component can decrypt the ciphertext identity information using a private key that matches the public key to obtain the plaintext identity information. Based on the obtained plaintext identity information, the terminal can send the first verification information to the third-party platform. The terminal can also send second verification information to the trusted component. After receiving the second verification information, the trusted component can compare the second verification information with the first verification information. When the comparison is consistent, it generates an identity authentication result and stores the identity authentication result and the corresponding validity period on the blockchain. The identity authentication result is used to instruct the service platform to provide services to the user. In response to the user's new round of platform selection operation, the terminal can select a new service platform from multiple candidate service platforms other than the service platform. In response to the user's request for the new service platform, the terminal triggers an operation and sends a service request to the new service platform. After receiving the service request, the new service platform can query the blockchain for an identity authentication result that indicates that the user has permission to the third-party platform and is within the validity period. The identity authentication result is used to instruct the new service platform to provide services to the user.

[0091] In the above embodiment, by attaching a validity period to the identity authentication results stored on the blockchain, the service platform must ensure that the authentication results retrieved from the blockchain are valid only within the validity period. If the validity period expires, the user must re-authenticate using the trusted component, and the new authentication result and the new validity period are associated and stored on the blockchain. This improves authentication efficiency while further protecting user privacy.

[0092] In one embodiment, a public key provided by a trusted component is pre-stored in the blockchain. The public key is stored by the blockchain after the legitimacy of the trusted component is verified based on the component certification information and public key provided by the trusted component. When no identity authentication result is found, the public key provided by the trusted component is used to encrypt the identity plaintext information registered by the user on the third-party platform to obtain the identity ciphertext information, including: when no identity authentication result is found and the user trusts the blockchain, the public key provided by the pre-stored trusted component is obtained from the blockchain, and the public key is used to encrypt the identity plaintext information registered by the user on the third-party platform to obtain the identity ciphertext information.

[0093] Specifically, before the identity authentication process begins, the trusted component can conduct interactive remote attestation with the blockchain to verify the legitimacy of the trusted component through the blockchain. The steps of interactive remote attestation are as follows: Figure 6 As shown, this can specifically involve activating a trusted component. Upon activation, the trusted component generates component certification information, a public key, and a matching private key. The trusted component can then send this certification information and public key to the blockchain. Upon receiving this certification information and public key, the blockchain can execute a smart contract configured on the blockchain to verify the legitimacy of the trusted component based on the certification information and public key. If the trusted component passes the legitimacy verification, the blockchain can store the public key for subsequent provision to the user to encrypt the plaintext identity information. It is understood that the matching private key can be stored within the trusted component's trusted domain and subsequently used to decrypt the user's ciphertext identity information within the trusted domain to obtain the plaintext identity information. In response to the user's request, the terminal can trigger an operation by sending a service request to a service platform that requires the user to have third-party platform permissions. After receiving the service request, the service platform can query the blockchain for an identity authentication result indicating that the user has third-party platform permissions. If no identity authentication result is found and the user trusts the blockchain's verification of the trusted component's legitimacy, the terminal can retrieve the public key provided by the pre-stored trusted component from the blockchain and directly use the public key to encrypt the user's plaintext identity information registered on the third-party platform, obtaining the encrypted identity information. The terminal can send the encrypted identity information to the trusted component. Upon receiving the encrypted identity information, the trusted component can generate first verification information. Within the trusted domain provided by the trusted component, it can decrypt the encrypted identity information using the private key that matches the public key to obtain the plaintext identity information. Based on the obtained plaintext identity information, the first verification information is sent to the third-party platform. The terminal can send second verification information to the trusted component. Upon receiving the second verification information, the trusted component can compare the second verification information with the first verification information. If the comparison is consistent, it generates an identity authentication result and stores it on the blockchain. The identity authentication result is used to instruct the service platform to provide services to the user.

[0094] In the above embodiment, when the identity authentication result is not queried and the user trusts the blockchain's legitimacy verification of the trusted component, the public key provided by the pre-stored trusted component is directly obtained from the blockchain, and the public key is used to encrypt the user's identity plaintext information registered on the third-party platform to obtain the identity ciphertext information. During the user's identity authentication request, there is no need for the terminal to verify the legitimacy of the trusted component, thereby further improving the efficiency of identity authentication.

[0095] In one embodiment, the method further includes: when no identity authentication result is found and the user does not trust the blockchain, obtaining component certification information and a public key from a trusted component; performing legitimacy verification on the trusted component based on the component certification information and the public key; when the legitimacy verification of the trusted component passes, using the public key to encrypt the user's identity plaintext information registered on the third-party platform to obtain identity ciphertext information.

[0096] Specifically, a terminal can trigger an operation in response to a user's request, sending a service request to a service platform that requires the user to have third-party platform permissions. After receiving the service request, the service platform can query the blockchain for an identity authentication result indicating that the user has third-party platform permissions. If no identity authentication result is found and the user does not trust the blockchain's legitimacy verification of the trusted component, the terminal can independently conduct interactive remote attestation with the trusted component to re-verify the legitimacy of the trusted component through the terminal. This interactive remote attestation step can specifically involve the terminal obtaining component certification information and a public key from the trusted component and then performing legitimacy verification of the trusted component based on the component certification information and public key. If the legitimacy verification of the trusted component is successful, the terminal can use the public key to encrypt the user's plaintext identity information registered on the third-party platform to obtain ciphertext identity information. The terminal can then send the ciphertext identity information to the trusted component. Upon receiving the ciphertext identity information, the trusted component can generate first verification information. Within the trusted domain provided by the trusted component, the trusted component can decrypt the ciphertext identity information using a private key that matches the public key to obtain the plaintext identity information. Based on the obtained plaintext identity information, the terminal can then send the first verification information to the third-party platform. The terminal can then send second verification information to the trusted component. After receiving the second verification information, the trusted component can compare the second verification information with the first verification information. When the comparison is consistent, it generates an identity authentication result and stores the identity authentication result in the blockchain. The identity authentication result is used to instruct the service platform to provide services to users.

[0097] In one embodiment, Figure 7As shown, the blockchain pre-stores the public key provided by the trusted component. If the service platform fails to retrieve the identity authentication result from the blockchain, and the user trusts the blockchain's verification of the trusted component's legitimacy, the terminal can retrieve the pre-stored public key provided by the trusted component from the blockchain and directly use the public key to encrypt the user's plaintext identity information registered on the third-party platform, obtaining the ciphertext identity information. If the identity authentication result is not retrieved and the user does not trust the blockchain's verification of the trusted component's legitimacy, the terminal can perform interactive remote attestation with the trusted component to re-verify the legitimacy of the trusted component through the terminal. The interactive remote attestation step can specifically involve the terminal obtaining component certification information and a public key from the trusted component and then verifying the legitimacy of the trusted component based on the component certification information and public key. If the legitimacy verification of the trusted component is successful, the terminal can use the public key to encrypt the user's plaintext identity information registered on the third-party platform, obtaining the ciphertext identity information. The terminal can then send the ciphertext identity information to the trusted component. After receiving the identity ciphertext information, the trusted component can generate first verification information, use the symmetric encryption key provided by the trusted component to encrypt the first verification information, obtain the first verification ciphertext, store the first verification ciphertext in the ciphertext database, and decrypt the identity ciphertext information within the trusted domain provided by the trusted component using the private key matching the public key to obtain the identity plaintext information, and send the first verification information to the third-party platform based on the obtained identity plaintext information.

[0098] Furthermore, if Figure 8 As shown, the user can enter second verification information, and the terminal can obtain the second verification information entered by the user. If the terminal does not store the public key provided by the trusted component, previously obtained from the blockchain, the terminal can obtain the public key provided by the trusted component from the blockchain and store it locally. The terminal can also conduct interactive remote attestation with the trusted component to re-verify the legitimacy of the trusted component through the terminal. The interactive remote attestation step can specifically involve the terminal obtaining component certification information and public key from the trusted component and then verifying the legitimacy of the trusted component based on the component certification information and public key. If the legitimacy verification of the trusted component is successful, the terminal can store the public key locally. If the terminal stores the public key provided by the trusted component, previously obtained from the blockchain, it uses the public key to encrypt the second verification information to obtain a second verification ciphertext. The terminal can send a second verification ciphertext to the trusted component. After receiving the second verification ciphertext, the trusted component can obtain the first verification ciphertext from the ciphertext database, use the symmetric encryption key provided by the trusted component to decrypt the first verification ciphertext, obtain the first verification information, use the private key to decrypt the second verification ciphertext, obtain the second verification information, compare the second verification information with the first verification information, and when the comparison is consistent, it indicates that the identity authentication is passed, generate an identity authentication result, and store the identity authentication result in the blockchain. The identity authentication result is used to instruct the service platform to provide services to the user.

[0099] In one embodiment, Figure 9 As shown, the blockchain pre-stores the public key provided by the trusted component. If the service platform fails to retrieve the identity authentication result from the blockchain, and the user trusts the blockchain's verification of the trusted component's legitimacy, the terminal can retrieve the pre-stored public key provided by the trusted component from the blockchain and directly use the public key to encrypt the user's plaintext identity information registered on the third-party platform, obtaining the ciphertext identity information. If the identity authentication result is not retrieved and the user does not trust the blockchain's verification of the trusted component's legitimacy, the terminal can perform interactive remote attestation with the trusted component to re-verify the legitimacy of the trusted component through the terminal. The interactive remote attestation step can specifically involve the terminal obtaining component certification information and a public key from the trusted component and then verifying the legitimacy of the trusted component based on the component certification information and public key. If the legitimacy verification of the trusted component is successful, the terminal can use the public key to encrypt the user's plaintext identity information registered on the third-party platform, obtaining the ciphertext identity information. The terminal can then send the ciphertext identity information to the trusted component. After receiving the identity ciphertext information, the trusted component can generate first verification information, use the symmetric encryption key provided by the trusted component to encrypt the first verification information, obtain the first verification ciphertext, store the first verification ciphertext in the blockchain, and decrypt the identity ciphertext information within the trusted domain provided by the trusted component using the private key matching the public key to obtain the identity plaintext information, and send the first verification information to the third-party platform based on the obtained identity plaintext information.

[0100] Furthermore, if Figure 10 As shown, the user can enter second verification information, and the terminal can obtain the second verification information entered by the user. If the terminal does not store the public key provided by the trusted component, previously obtained from the blockchain, the terminal can obtain the public key provided by the trusted component from the blockchain and store it locally. The terminal can also conduct interactive remote attestation with the trusted component to re-verify the legitimacy of the trusted component through the terminal. The interactive remote attestation step can specifically involve the terminal obtaining component certification information and public key from the trusted component and then verifying the legitimacy of the trusted component based on the component certification information and public key. If the legitimacy verification of the trusted component is successful, the terminal can store the public key locally. If the terminal stores the public key provided by the trusted component, previously obtained from the blockchain, it uses the public key to encrypt the second verification information to obtain a second verification ciphertext. The terminal can send a second verification ciphertext to the trusted component. After receiving the second verification ciphertext, the trusted component can obtain the first verification ciphertext from the blockchain, use the symmetric encryption key provided by the trusted component to decrypt the first verification ciphertext, obtain the first verification information, use the private key to decrypt the second verification ciphertext, obtain the second verification information, compare the second verification information and the first verification information, and when the comparison is consistent, it indicates that the identity authentication is passed, generate an identity authentication result, and store the identity authentication result in the blockchain. The identity authentication result is used to instruct the service platform to provide services to the user.

[0101] In the above embodiment, when the identity authentication result is not queried and the user does not trust the blockchain's legitimacy verification of the trusted component, the user's terminal can obtain component certification information and public key from the trusted component, and based on the component certification information and public key, perform legitimacy verification on the trusted component by itself. When the legitimacy verification of the trusted component is passed, the public key is used to encrypt the user's identity plaintext information registered on the third-party platform to obtain identity ciphertext information, which can further protect the user's privacy data.

[0102] In one embodiment, when the identity authentication result is queried, service authorization information fed back by the service platform is received to indicate that the service platform provides services to the user.

[0103] Specifically, in response to a user's request triggering an operation, the terminal may send a service request to the service platform, which requires the user to have third-party platform permissions. Upon receiving the service request, the service platform may query the blockchain for an identity authentication result indicating that the user has third-party platform permissions. Upon receiving the identity authentication result, indicating that the user has third-party platform permissions, the service platform may provide services to the user and generate service authorization information indicating that the service platform has provided services to the user. The service authorization information is then sent to the terminal, which receives the service authorization information so that the user can confirm that the identity authentication was successful.

[0104] In the above embodiment, when the identity authentication result is queried from the blockchain, the service platform can directly provide services to the user without having to go through the identity authentication process based on the trusted component generation again, further improving the efficiency of identity authentication.

[0105] In one embodiment, the identity plaintext information is the communication information of the electronic media registered by the user on the third-party platform, and the identity ciphertext information is obtained by the trusted component using the public key to encrypt the communication information; sending the identity ciphertext information to the trusted component includes: sending the identity ciphertext information to the trusted component, the identity ciphertext information is used to instruct the trusted component to generate first verification information, within the trusted domain provided by the trusted component, using the private key matching the public key to decrypt the identity ciphertext information to obtain the communication information, and based on the obtained communication information, sending the first verification information to the electronic media registered by the user on the third-party platform.

[0106] Specifically, a terminal can trigger an operation in response to a user's request, sending a service request to a service platform that requires the user to have third-party platform permissions. After receiving the service request, the service platform can query the blockchain for an identity authentication result indicating that the user has third-party platform permissions. If no identity authentication result is found, the terminal can use the public key provided by the trusted component to encrypt the communication information of the electronic media registered by the user on the third-party platform to obtain ciphertext identity information. The terminal can send the ciphertext identity information to the trusted component. Upon receiving the ciphertext identity information, the trusted component can generate first verification information. Within the trusted domain provided by the trusted component, the trusted component can decrypt the ciphertext identity information using the private key that matches the public key to obtain the communication information of the electronic media. Based on the obtained communication information, the first verification information can be sent to the electronic media on the third-party platform. The terminal can send second verification information to the trusted component. Upon receiving the second verification information, the trusted component can compare the second verification information with the first verification information. If the comparison is consistent, an identity authentication result is generated and stored on the blockchain. The identity authentication result is used to instruct the service platform to provide services to the user.

[0107] In one embodiment, the electronic medium can specifically be at least one of an email address, a text messaging application, or an instant messaging application. It is understood that when the electronic medium is an email address, the communication information is the email address. When the electronic medium is a text messaging application, the communication information is the mobile phone number. When the electronic medium is an instant messaging application, the communication information is the instant messaging account.

[0108] For example, the electronic medium is an email address, and the communication information is an email address, such as Figure 11 As shown, a terminal can trigger an operation in response to a user's request, sending a service request to a service platform that requires the user to have third-party platform permissions. After receiving the service request, the service platform can query the blockchain for an identity authentication result indicating that the user has third-party platform permissions. If no identity authentication result is found, the terminal can use the public key provided by the trusted component to encrypt the user's email address registered on the third-party platform to obtain encrypted identity information. The terminal can send the encrypted identity information to the trusted component. Upon receiving the encrypted identity information, the trusted component can generate first verification information. Within the trusted domain provided by the trusted component, the trusted component can use the private key that matches the public key to decrypt the encrypted identity information to obtain the email address. Based on the obtained email address, the first verification information can be sent to an email address on the third-party platform. The terminal can send second verification information to the trusted component. Upon receiving the second verification information, the trusted component can compare the second verification information with the first verification information. If the comparison is consistent, an identity authentication result is generated and stored on the blockchain. The identity authentication result is used to instruct the service platform to provide services to the user.

[0109] In the above embodiment, the first verification information is generated by a trusted component, and within the trusted domain provided by the trusted component, the identity ciphertext information is decrypted using a private key matching the public key to obtain communication information, and based on the obtained communication information, the first verification information is sent to the electronic media registered by the user on the third-party platform, which can ensure that the user can quickly obtain the first verification information, thereby improving the efficiency of identity authentication.

[0110] like Figure 12 As shown, in one embodiment, an identity authentication method is provided, which specifically includes the following steps:

[0111] In step 1202, the terminal selects a service platform from a plurality of candidate service platforms that require the user to have third-party platform permissions in response to the user's platform selection operation; the plurality of candidate service platforms are respectively connected to the blockchain.

[0112] Step 1204 : In response to the user's request triggering operation for the service platform, the terminal sends a service request carrying the user's user ID and the platform ID of the third-party platform to the service platform.

[0113] In step 1206, the service platform queries the blockchain for the authentication result associated with the user ID and the platform ID, and obtains an identity authentication result indicating that the user has the third-party platform authority.

[0114] The blockchain also pre-stores the public key provided by the trusted component. The public key is stored after the blockchain verifies the legitimacy of the trusted component based on the component certification information and public key provided by the trusted component.

[0115] In step 1208, when no identity authentication result is found and the user trusts the blockchain, the terminal obtains the public key provided by the pre-stored trusted component from the blockchain, and uses the public key to encrypt the user's identity plaintext information registered on the third-party platform to obtain the identity ciphertext information.

[0116] In step 1210, when no identity authentication result is found and the user does not trust the blockchain, the terminal obtains component certification information and public key from the trusted component.

[0117] In step 1212, the terminal verifies the legitimacy of the trusted component based on the component certification information and the public key.

[0118] In step 1214, when the legitimacy verification of the trusted component is passed, the terminal uses the public key to encrypt the user's identity plain text information registered on the third-party platform, obtains the identity cipher text information, and sends the identity cipher text information to the trusted component.

[0119] In step 1216, the trusted component generates first verification information, encrypts the first verification information using the symmetric encryption key provided by the trusted component to obtain a first verification ciphertext, and stores the first verification ciphertext in the blockchain. Within the trusted domain provided by the trusted component, the private key matching the public key is used to decrypt the identity ciphertext information to obtain the identity plaintext information, and the first verification information is sent to the third-party platform based on the obtained identity plaintext information.

[0120] In step 1218, the terminal obtains the second verification information, encrypts the second verification information using the public key, obtains the second verification ciphertext, and sends the second verification ciphertext to the trusted component.

[0121] In step 1220, the trusted component obtains and uses the symmetric encryption key from the blockchain to decrypt the pre-stored first verification ciphertext to obtain the first verification information, decrypts the second verification ciphertext using the private key to obtain the second verification information, and compares the second verification information with the first verification information.

[0122] In step 1222, when the comparison is consistent, the trusted component generates an identity authentication result and stores the identity authentication result and the corresponding validity period in the blockchain. The identity authentication result is used to instruct the service platform to provide services to the user.

[0123] In step 1224, when the identity authentication result is found, the terminal receives service authorization information fed back by the service platform, which is used to indicate that the service platform provides services to the user.

[0124] Step 1226: In response to the user's new round of platform selection operation, the terminal selects a new service platform other than the service platform from multiple candidate service platforms, and in response to the user's request trigger operation for the new service platform, sends a service request to the new service platform.

[0125] In step 1228, the new service platform queries the blockchain for an identity authentication result indicating that the user has the third-party platform authority and is within the validity period. The identity authentication result is used to instruct the new service platform to provide services to the user.

[0126] This application also provides an application scenario that utilizes the aforementioned identity authentication method. Specifically, this identity authentication method can be applied to scenarios where identity authentication is achieved by sending a verification code via email. It should be understood that the plaintext identity information in this application is the email address of the user registered on a third-party platform, and the ciphertext identity information is obtained by encrypting the email address using a public key by a trusted component. The verification information is a verification code. Specifically, in response to a user's platform selection operation, a terminal selects a service platform from multiple candidate service platforms that require the user to have third-party platform permissions. These candidate service platforms are each connected to a blockchain. In response to a user's request triggering operation for a service platform, the terminal sends a service request to the service platform containing the user's user ID and the platform ID of the third-party platform. The service platform queries the blockchain for the authentication result associated with the user ID and platform ID to obtain an identity authentication result indicating that the user has third-party platform permissions. The blockchain pre-stores a public key provided by the trusted component. The public key is stored by the blockchain after the trusted component has been verified for legitimacy based on the component certification information and public key provided by the trusted component.

[0127] If no identity authentication result is found and the user trusts the blockchain, the terminal retrieves the public key provided by the pre-stored trusted component from the blockchain and uses it to encrypt the user's email address registered on the third-party platform to obtain the ciphertext identity information. If no identity authentication result is found and the user does not trust the blockchain, the terminal retrieves the component's certification information and public key from the trusted component. Based on the component's certification information and public key, the terminal verifies the legitimacy of the trusted component. If the legitimacy verification of the trusted component is successful, the terminal uses the public key to encrypt the user's email address registered on the third-party platform to obtain the ciphertext identity information and sends it to the trusted component.

[0128] The trusted component generates a first verification code and encrypts it using the symmetric encryption key provided by the trusted component to obtain a first verification ciphertext. The first verification ciphertext is then stored on the blockchain. Within the trusted domain provided by the trusted component, the private key matching the public key is used to decrypt the identity ciphertext information, obtaining an email address. Based on the obtained email address, the terminal composes an email and sends the first verification code to the third-party platform. The terminal obtains a second verification code and encrypts it using the public key to obtain a second verification ciphertext. The terminal then sends the second verification ciphertext to the trusted component. The trusted component obtains and uses the symmetric encryption key from the blockchain to decrypt the pre-stored first verification ciphertext to obtain the first verification code. The trusted component then decrypts the second verification ciphertext using the private key to obtain the second verification code. The trusted component compares the second verification code with the first verification code. If the comparison is consistent, an identity authentication result is generated and stored along with the corresponding validity period on the blockchain. The identity authentication result is used to instruct the service platform to provide services to the user. Upon receiving the identity authentication result, the terminal receives service authorization information from the service platform, indicating that the service platform has provided services to the user.

[0129] In response to the user's new platform selection operation, the terminal selects a new service platform from multiple candidate service platforms, in addition to the service platform. In response to the user's request trigger operation for the new service platform, it sends a service request to the new service platform. The new service platform queries the blockchain for an identity authentication result that indicates that the user has permission to use the third-party platform and is within the validity period. The identity authentication result is used to instruct the new service platform to provide services to the user.

[0130] As can be understood, this application introduces a trusted component and blockchain. Users use the public key provided by the trusted component to encrypt their email address registered on the third-party platform and then send it to the trusted component. The corresponding private key is then used within the trusted domain provided by the trusted component to decrypt the email address. The trusted component then communicates with the third-party platform's email address to provide the user with a verification code. After the identity verification is successful, the authentication result is stored on the trusted blockchain. The service platform can then retrieve the authentication result from the blockchain to authenticate the user, eliminating the need for the user to directly send the email address to the service platform and protecting the user's privacy data on the third-party platform.

[0131] This application also provides an application scenario that utilizes the aforementioned identity authentication method. Specifically, this identity authentication method can be applied to scenarios where identity authentication is achieved by sending a verification code via SMS text message. It is understood that the plaintext identity information in this application is the mobile phone number registered by the user on a third-party platform, and the encrypted identity information is obtained by encrypting the mobile phone number using the public key of the trusted component. The verification information is the verification code. Specifically, by triggering an operation in response to a user's request, a service request is sent to a service platform that requires the user to have third-party platform permissions. The service request is used to instruct the service platform to query the blockchain for an identity authentication result indicating that the user has third-party platform permissions; when no identity authentication result is found, the public key provided by the trusted component is used to encrypt the mobile phone number registered by the user on the third-party platform to obtain identity ciphertext information; the identity ciphertext information is sent to the trusted component, and the identity ciphertext information is used to instruct the trusted component to generate a first verification code. Within the trusted domain provided by the trusted component, the identity ciphertext information is decrypted using a private key matching the public key to obtain the mobile phone number, and a mobile phone text message is edited based on the obtained mobile phone number to send the first verification code to the third-party platform; a second verification code is sent to the trusted component, and the second verification code is used to instruct the trusted component to compare the second verification code and the first verification code. When the comparison is consistent, an identity authentication result is generated, and the identity authentication result is stored in the blockchain. The identity authentication result is used to instruct the service platform to provide services to the user.

[0132] As can be understood, this application introduces a trusted component and blockchain. Users use the public key provided by the trusted component to encrypt their mobile phone number on a third-party platform and then send it to the trusted component. The corresponding private key is then used within the trusted domain provided by the trusted component to decrypt the mobile phone number. The trusted component then communicates with the third-party platform to provide the user with a verification code. After the identity verification is successful, the authentication result is stored on the trusted blockchain. The service platform can then retrieve the authentication result from the blockchain to authenticate the user, eliminating the need for the user to directly send their mobile phone number to the service platform and protecting the user's privacy data on the third-party platform.

[0133] It should be understood that, although the various steps in the flow chart of the above-mentioned embodiments are shown in sequence, these steps are not necessarily performed in sequence. Unless clearly stated herein, the execution of these steps does not have strict order restrictions, and these steps can be performed in other sequences. Moreover, at least a portion of the steps in the above-mentioned embodiments may include a plurality of sub-steps or a plurality of stages, and these sub-steps or stages are not necessarily performed at the same time, but can be performed at different times, and the execution order of these sub-steps or stages is not necessarily performed in sequence, but can be performed in turn or alternately with at least a portion of other steps or sub-steps or stages of other steps.

[0134] In one embodiment, Figure 13 As shown, an identity authentication device 1300 is provided, which specifically includes:

[0135] Sending module 1302 is used to trigger an operation in response to a user's request, and send a service request to the service platform that requires the user to have third-party platform permissions. The service request is used to instruct the service platform to query the blockchain for an identity authentication result indicating that the user has third-party platform permissions;

[0136] The encryption module 1304 is used to encrypt the user's identity plain text information registered on the third-party platform using the public key provided by the trusted component to obtain the identity cipher text information when no identity authentication result is found;

[0137] The sending module 1302 is further configured to send encrypted identity information to the trusted component, where the encrypted identity information is used to instruct the trusted component to generate first verification information, decrypt the encrypted identity information using a private key that matches the public key within the trusted domain provided by the trusted component to obtain plaintext identity information, and send the first verification information to the third-party platform based on the obtained plaintext identity information.

[0138] The sending module 1302 is also used to send second verification information to the trusted component. The second verification information is used to instruct the trusted component to compare the second verification information with the first verification information. When the comparison is consistent, an identity authentication result is generated and stored in the blockchain. The identity authentication result is used to instruct the service platform to provide services to users.

[0139] In one embodiment, after generating the first verification information, the trusted component encrypts the first verification information to obtain a first verification ciphertext, and stores the first verification ciphertext. The sending module 1302 is also used to encrypt the second verification information using the public key to obtain the second verification ciphertext; send the second verification ciphertext to the trusted component, and the second verification ciphertext is used to instruct the trusted component to obtain and decrypt the pre-stored first verification ciphertext to obtain the first verification information, use the private key to decrypt the second verification ciphertext to obtain the second verification information, compare the second verification information and the first verification information, and when the comparison is consistent, generate an identity authentication result, and store the identity authentication result in the blockchain. The identity authentication result is used to instruct the service platform to provide services to the user.

[0140] In one embodiment, the trusted component stores the first verification ciphertext in the blockchain. After receiving the second verification ciphertext, the trusted component obtains the pre-stored first verification ciphertext from the blockchain, decrypts the obtained first verification ciphertext, and obtains the first verification information.

[0141] In one embodiment, after generating the first verification information, the trusted component uses the symmetric encryption key provided by the trusted component to encrypt the first verification information, obtain the first verification ciphertext, and store the first verification ciphertext. After receiving the second verification ciphertext, the trusted component obtains and uses the symmetric encryption key to decrypt the pre-stored first verification ciphertext to obtain the first verification information.

[0142] In one embodiment, the sending module 1302 is further used to select a service platform from multiple candidate service platforms that require the user to have third-party platform permissions in response to the user's platform selection operation; the multiple candidate service platforms are respectively connected to the blockchain; in response to the user's request trigger operation for the service platform, a service request is sent to the service platform, and the service request is used to instruct the service platform to query the blockchain for an identity authentication result indicating that the user has third-party platform permissions.

[0143] In one embodiment, the sending module 1302 is further used to respond to a user's request triggering operation for the service platform, and send a service request carrying the user's user identifier and the platform identifier of the third-party platform to the service platform; wherein the service request is used to instruct the service platform to query the authentication result stored in association with the user identifier and the platform identifier from the blockchain, and obtain an identity authentication result indicating that the user has the authority of the third-party platform.

[0144] In one embodiment, the sending module 1302 is further used to select a new service platform other than the service platform from multiple candidate service platforms in response to a new round of platform selection operation by the user; and to send a service request to the new service platform in response to a user request trigger operation for the new service platform. The service request sent to the new service platform is used to instruct the new service platform to query the blockchain for an identity authentication result indicating that the user has third-party platform authority. The identity authentication result is used to instruct the new service platform to provide services to the user.

[0145] In one embodiment, the blockchain also stores the validity period corresponding to the identity authentication result. After receiving the service request, the new service platform queries the blockchain for the identity authentication result that indicates that the user has the third-party platform authority and is within the validity period.

[0146] In one embodiment, the blockchain pre-stores a public key provided by a trusted component. The public key is stored by the blockchain after the blockchain verifies the legitimacy of the trusted component based on the component certification information and public key provided by the trusted component. The encryption module 1304 is also used to obtain the pre-stored public key provided by the trusted component from the blockchain when no identity authentication result is queried and the user trusts the blockchain, and use the public key to encrypt the user's identity plaintext information registered on the third-party platform to obtain the identity ciphertext information.

[0147] In one embodiment, the encryption module 1304 is also used to obtain component certification information and public keys from trusted components when no identity authentication result is found and the user does not trust the blockchain; based on the component certification information and public keys, the legitimacy of the trusted components is verified; when the legitimacy verification of the trusted components is passed, the public key is used to encrypt the user's identity plaintext information registered on the third-party platform to obtain identity ciphertext information.

[0148] In one embodiment, Figure 14 As shown, the identity authentication device 1300 further includes:

[0149] The receiving module 1306 is configured to receive service authorization information fed back by the service platform when the identity authentication result is found, which is used to indicate that the service platform provides services to the user.

[0150] In one embodiment, the identity plaintext information is the communication information of the electronic media registered by the user on the third-party platform, and the identity ciphertext information is obtained by the trusted component using the public key to encrypt the communication information; the sending module 1302 is also used to send the identity ciphertext information to the trusted component, and the identity ciphertext information is used to instruct the trusted component to generate the first verification information, and within the trusted domain provided by the trusted component, the private key matching the public key is used to decrypt the identity ciphertext information to obtain the communication information, and based on the obtained communication information, the first verification information is sent to the electronic media registered by the user on the third-party platform.

[0151] The above-mentioned identity authentication device triggers an operation in response to a user's request, and sends a service request to a service platform that requires the user to have third-party platform permissions. The service request is used to instruct the service platform to query the blockchain for an identity authentication result indicating that the user has third-party platform permissions; when no identity authentication result is found, the public key provided by the trusted component is used to encrypt the identity plaintext information of the user registered on the third-party platform to obtain identity ciphertext information; the identity ciphertext information is sent to the trusted component, and the identity ciphertext information is used to instruct the trusted component to generate first verification information. Within the trusted domain provided by the trusted component, the identity ciphertext information is decrypted using a private key matching the public key to obtain identity plaintext information, and the first verification information is sent to the third-party platform based on the obtained identity plaintext information; the second verification information is sent to the trusted component, and the second verification information is used to instruct the trusted component to compare the second verification information and the first verification information. When the comparison is consistent, an identity authentication result is generated, and the identity authentication result is stored in the blockchain. The identity authentication result is used to instruct the service platform to provide services to the user. Compared to traditional identity authentication methods, this application introduces a trusted component and blockchain. Users use the public key provided by the trusted component to encrypt their identity information on a third-party platform and then send it to the trusted component. Within the trusted domain provided by the trusted component, the corresponding private key is used to decrypt the identity information. The trusted component then communicates with the third-party platform to provide verification information to the user. After the identity is authenticated, the authentication result is stored on the trusted blockchain. The service platform can then retrieve the authentication result from the blockchain to authenticate the user. This prevents the user from directly sending their identity information to the service platform, thus protecting the user's privacy data on the third-party platform.

[0152] Each module in the above-mentioned identity authentication device can be implemented in whole or in part through software, hardware, or a combination thereof. Each module can be embedded in or independent of the processor of the computer device in hardware form, or can be stored in the memory of the computer device in software form, so that the processor can call and execute the corresponding operations of each module.

[0153] In one embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as follows: Figure 15As shown. The computer device includes a processor, memory, an input / output interface, a communication interface, a display unit, and an input device. The processor, memory, and input / output interface are connected via a system bus, and the communication interface, display unit, and input device are connected to the system bus via the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner. The wireless manner can be achieved through WIFI, a mobile cellular network, NFC (near field communication), or other technologies. When the computer program is executed by the processor, it implements an identity authentication method. The display unit of the computer device is used to form a visually visible image, and can be a display screen, a projection device or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen. The input device of the computer device can be a touch layer covering the display screen, or a button, trackball or touchpad set on the computer device casing, or an external keyboard, touchpad or mouse, etc.

[0154] Those skilled in the art will understand that Figure 15 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0155] In one embodiment, a computer device is further provided, including a memory and a processor. The memory stores a computer program, and the processor implements the steps in the above method embodiments when executing the computer program.

[0156] In one embodiment, a computer-readable storage medium is provided, storing a computer program, which implements the steps in the above-mentioned method embodiments when executed by a processor.

[0157] In one embodiment, a computer program product is provided, including a computer program. When the computer program is executed by a processor, the steps in the above method embodiments are implemented.

[0158] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of relevant countries and regions.

[0159] Those skilled in the art will appreciate that all or part of the processes in the above-described method embodiments can be implemented by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the above-described method embodiments. Any reference to memory, storage, database, or other media used in the embodiments provided herein may include at least one of non-volatile and volatile memory. Non-volatile memory may include read-only memory (ROM), magnetic tape, floppy disk, flash memory, or optical storage. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM).

[0160] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0161] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present invention. It should be noted that a person skilled in the art could make various modifications and improvements without departing from the spirit of the present application, all of which fall within the scope of protection of the present application. Therefore, the scope of protection of the present patent application shall be determined by the appended claims.

Claims

1. An identity authentication method, characterized in that: The method comprises: In response to a user's request triggering operation, a service request is sent to a service platform that requires the user to have third-party platform permissions, wherein the service request is used to instruct the service platform to query the blockchain for an identity authentication result indicating that the user has the third-party platform permissions; When the identity authentication result is not found, the public key provided by the trusted component is used to encrypt the plain text identity information of the user registered on the third-party platform to obtain the encrypted identity information; Sending the encrypted identity information to the trusted component, where the encrypted identity information is used to instruct the trusted component to generate first verification information; decrypting the encrypted identity information using a private key that matches the public key within a trusted domain provided by the trusted component to obtain the plaintext identity information; and sending the first verification information to the third-party platform based on the obtained plaintext identity information; Sending second verification information to the trusted component, where the second verification information is used to instruct the trusted component to compare the second verification information with the first verification information. When the comparison is consistent, generating the identity authentication result, and storing the identity authentication result in the blockchain, the identity authentication result is used to instruct the service platform to provide services to the user.

2. The method according to claim 1, characterized in that After generating the first verification information, the trusted component encrypts the first verification information to obtain a first verification ciphertext, and stores the first verification ciphertext. The sending the second verification information to the trusted component includes: Encrypt the second verification information using the public key to obtain a second verification ciphertext; The second verification ciphertext is sent to the trusted component, where the second verification ciphertext is used to instruct the trusted component to obtain and decrypt the pre-stored first verification ciphertext to obtain the first verification information, decrypt the second verification ciphertext using the private key to obtain the second verification information, compare the second verification information with the first verification information, and when the comparison is consistent, generate the identity authentication result, and store the identity authentication result in the blockchain. The identity authentication result is used to instruct the service platform to provide services to the user.

3. The method according to claim 2, characterized in that The trusted component stores the first verification ciphertext in the blockchain. After receiving the second verification ciphertext, the trusted component obtains the pre-stored first verification ciphertext from the blockchain, decrypts the obtained first verification ciphertext, and obtains the first verification information.

4. The method according to claim 2, characterized in that After generating the first verification information, the trusted component uses the symmetric encryption key provided by the trusted component to encrypt the first verification information to obtain a first verification ciphertext, and stores the first verification ciphertext. After receiving the second verification ciphertext, the trusted component obtains and uses the symmetric encryption key to decrypt the pre-stored first verification ciphertext to obtain the first verification information.

5. The method according to claim 1, wherein The triggering operation in response to the user's request to send a service request to a service platform that requires the user to have third-party platform permissions includes: In response to the platform selection operation of the user, a service platform is selected from a plurality of candidate service platforms that require the user to have the third-party platform authority; the plurality of candidate service platforms are respectively connected to the blockchain; In response to the user's request triggering operation for the service platform, a service request is sent to the service platform, where the service request is used to instruct the service platform to query the blockchain for an identity authentication result indicating that the user has the authority of the third-party platform.

6. The method according to claim 5, characterized in that The sending of a service request to the service platform in response to the user's request triggering operation for the service platform includes: In response to a request triggering operation by the user for the service platform, sending a service request carrying the user identifier of the user and the platform identifier of the third-party platform to the service platform; The service request is used to instruct the service platform to query the authentication result stored in association with the user identifier and the platform identifier from the blockchain, and obtain an identity authentication result indicating that the user has the authority of the third-party platform.

7. The method according to claim 5, characterized in that The method further comprises: In response to a new round of platform selection operation by the user, selecting a new service platform other than the service platform from the multiple candidate service platforms; In response to the user's request triggering operation for the new service platform, a service request is sent to the new service platform, where the service request sent to the new service platform is used to instruct the new service platform to query the blockchain for an identity authentication result indicating that the user has the authority of the third-party platform, and the identity authentication result is used to instruct the new service platform to provide services to the user.

8. The method according to claim 7, characterized in that The blockchain also stores the validity period corresponding to the identity authentication result. After receiving the service request, the new service platform queries the blockchain for an identity authentication result that indicates that the user has the permission to the third-party platform and is within the validity period.

9. The method according to claim 1, characterized in that The blockchain pre-stores a public key provided by the trusted component. The public key is stored after the blockchain verifies the legitimacy of the trusted component based on the component certification information provided by the trusted component and the public key. When the identity authentication result is not found, the public key provided by the trusted component is used to encrypt the plain text identity information of the user registered on the third-party platform to obtain the encrypted identity information, including: When the identity authentication result is not found and the user trusts the blockchain, the public key provided by the pre-stored trusted component is obtained from the blockchain, and the public key is used to encrypt the plaintext identity information of the user registered on the third-party platform to obtain the encrypted identity information.

10. The method according to claim 9, characterized in that The method further comprises: When the identity authentication result is not found and the user does not trust the blockchain, obtaining the component certification information and the public key from the trusted component; Performing legitimacy verification on the trusted component based on the component certification information and the public key; When the legitimacy verification of the trusted component is passed, the public key is used to encrypt the plain text identity information of the user registered on the third-party platform to obtain encrypted identity information.

11. The method according to claim 1, wherein The method further comprises: When the identity authentication result is queried, service authorization information fed back by the service platform is received, which is used to indicate that the service platform provides services to the user.

12. The method according to any one of claims 1 to 11, characterized in that The identity plaintext information is the communication information of the electronic medium registered by the user on the third-party platform, and the identity ciphertext information is obtained by the trusted component encrypting the communication information using the public key; The sending the identity ciphertext information to the trusted component includes: The identity ciphertext information is sent to the trusted component, where the identity ciphertext information is used to instruct the trusted component to generate first verification information. Within the trusted domain provided by the trusted component, the identity ciphertext information is decrypted using a private key that matches the public key to obtain the communication information. Based on the obtained communication information, the first verification information is sent to the electronic medium registered by the user on the third-party platform.

13. An identity authentication device, characterized in that: The device comprises: A sending module, configured to trigger an operation in response to a user's request, and send a service request to a service platform that requires the user to have third-party platform permissions, wherein the service request is used to instruct the service platform to query the blockchain for an identity authentication result indicating that the user has the third-party platform permissions; An encryption module is used to encrypt the plain text identity information of the user registered on the third-party platform using the public key provided by the trusted component to obtain cipher text identity information when the identity authentication result is not found; The sending module is further configured to send the encrypted identity information to the trusted component, where the encrypted identity information is used to instruct the trusted component to generate first verification information, decrypt the encrypted identity information using a private key that matches the public key within a trusted domain provided by the trusted component to obtain the plaintext identity information, and send the first verification information to the third-party platform based on the obtained plaintext identity information; The sending module is further used to send second verification information to the trusted component, and the second verification information is used to instruct the trusted component to compare the second verification information with the first verification information. When the comparison is consistent, the identity authentication result is generated and stored in the blockchain. The identity authentication result is used to instruct the service platform to provide services to the user.

14. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 12 are implemented.

15. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 12 are implemented.

16. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 12 are implemented.

Images