Identity authentication method and apparatus, storage medium, program, and program product

[0001] This application is filed based on and claims priority to Chinese Patent Application No. 202011569230.1, filed on Dec. 26, 2020 and entitled “IDENTITY AUTHENTICATION METHOD AND APPARATUS”, the entire content of which is incorporated herein by reference in its entirety.

[0002] The present application relates to the technical field of network communication security, and particularly to a method and a device of identity authentication, a storage medium, a program, and a program product.

[0003] In a communication network, a requester may access the network through an authentication access controller. In some cases where security requirements are relatively high, the requester needs to authenticate the identity of the authentication access controller, so as to ensure that the accessed network is a legal network. Furthermore, node-to-node transmission in blockchain technology also requires that a trust relationship is established between different nodes, so that identity authentication performed on nodes is also very important.

[0004] During identity authentication performed for the authentication access controller, the authentication access controller needs to provide identity information thereof for the identity authentication. However, such identity information typically carries private or sensitive information such as geographic location information, information about an institution thereof, etc. Furthermore, during actual application, such identity information is usually comprised in a digital certificate of an entity, and the digital certificate is used as an identity certificate of the entity.

[0005] If the identity information of the authentication access controller is intercepted by an attacker during the identity authentication of the authentication access controller, and is used for illegal purposes, severe security risks are posed to the authentication access controller, the requester, and even the network.

[0006] Provided in the present application are a method and a device of identity authentication, a storage medium, a program, and a program product. Confidentiality processing is performed on identity information and identity authentication result information, so that information such as a digital certificate, a verification result, or the like can be prevented from being exposed during transmission, and it is ensured that an attacker cannot acquire private or sensitive information, thereby ensuring the security of an authentication access controller, a requester, and even a network.

[0007] Provided in the embodiments of the present application is the following technical solution.

[0008] According to a first aspect, provided in an embodiment of the present application is a method of identity authentication, which includes the following operations.

[0009] An authentication access controller acquires a first authentication response message from a first authentication server trusted thereby, the first authentication response message including an identity authentication result information ciphertext and a digital signature of a second authentication server trusted by a requester. The identity authentication result information ciphertext is generated by the first authentication server by using a protection nonce to encrypt information comprising identity authentication result information of the authentication access controller, and the identity authentication result information includes a verification result of a digital certificate of the authentication access controller.

[0010] The requester acquires an authentication result message sent by the authentication access controller, the authentication result message including authentication result information that is obtained by the authentication access controller by using a message encryption key to encrypt to-be-encrypted data including the identity authentication result information ciphertext, the digital signature of the second authentication server, and the protection nonce. The requester uses the message encryption key to decrypt the authentication result information to obtain the protection nonce, the identity authentication result information ciphertext, and the digital signature of the second authentication server.

[0011] The requester uses a public key of the second authentication server to verify the digital signature of the second authentication server; after verification is successful, the requester uses the protection nonce to decrypt the identity authentication result information ciphertext to obtain identity authentication result information of the authentication access controller; and the requester determines an identity authentication result of the authentication access controller according to a verification result of the digital certificate in the identity authentication result information.

[0012] According to a second aspect, provided in an embodiment of the present application is a requester, which includes: a first acquisition portion, a decryption portion, a first verification portion, and a first determination portion.

[0013] The first acquisition portion is configured to acquire an authentication result message sent by the authentication access controller, the authentication result message comprising authentication result information that is obtained by the authentication access controller by using a message encryption key to encrypt to-be-encrypted data comprising an identity authentication result information cyphertext, a digital signature of a second authentication server trusted by the requester, and a protection nonce.

[0014] The identity authentication result information ciphertext is generated by a first authentication server trusted by the authentication access controller by using the protection nonce to encrypt information comprising identity authentication result information of the authentication access controller, and the identity authentication result information includes a verification result of a digital certificate of the authentication access controller.

[0015] The decryption portion is configured to use the message encryption key to decrypt the authentication result information to obtain the protection nonce, the identity authentication result information ciphertext, and the digital signature of the second authentication server.

[0016] The first verification portion is configured to use a public key of the second authentication server to verify the digital signature of the second authentication server.

[0017] The decryption portion is further configured to use the protection nonce to decrypt the identity authentication result information ciphertext to obtain the identity authentication result information of the authentication access controller when verification for the digital signature of the second authentication server is successful.

[0018] The first determination portion is configured to determine an identity authentication result of the authentication access controller according to the verification result of the digital certificate in the identity authentication result information.

[0019] According to a third aspect, provided in an embodiment of the present application is an authentication access controller, which includes: a first acquisition portion and a first sending portion.

[0020] The first acquisition portion is configured to acquire a first authentication response message sent by a first authentication server trusted by the authentication access controller, the first authentication response message including an identity authentication result information ciphertext and a digital signature of a second authentication server trusted by a requester. The identity authentication result information ciphertext is generated by the first authentication server by using a protection nonce to encrypt information comprising identity authentication result information of the authentication access controller, and the identity authentication result information includes a verification result of a digital certificate of the authentication access controller.

[0021] The first sending portion is configured to send an authentication result message to the requester, the authentication result message including authentication result information that is obtained by the authentication access controller by using a message encryption key to encrypt to-be-encrypted data comprising the identity authentication result information ciphertext, the digital signature of the second authentication server, and the protection nonce.

[0022] According to a fourth aspect, provided in an embodiment of the present application is a first authentication server, trusted by an authentication access controller, which includes: a first acquisition portion, a decryption portion, a first verification portion, and a generation portion.

[0023] The first acquisition portion is configured to acquire a first authentication request message sent by the authentication access controller, the first authentication request message including an identity information ciphertext that is obtained by the authentication access controller by using a public key of an encryption certificate to encrypt information including the digital certificate of the authentication access controller and the protection nonce.

[0024] The decryption portion is configured to use a private key corresponding to the encryption certificate to decrypt the identity information ciphertext to obtain the digital certificate and the protection nonce.

[0025] The first verification portion is configured to perform legality verification on the digital certificate to obtain a verification result of the digital certificate of the authentication access controller.

[0026] The generation portion is configured to generate identity authentication result information of the authentication access controller according to information including the verification result, and further configured to use the protection nonce to encrypt information comprising the identity authentication result information to generate the identity authentication result information cyphertext, and perform calculation on to-be-signed data including the identity authentication result information ciphertext to generate a digital signature of the first authentication server.

[0027] According to a fifth aspect, provided in an embodiment of the present application is a requester, including:

• • [0028] a first processor; and
  • [0029] a first memory for storing instructions executable by the first processor.

[0030] The first processor is configured to invoke the instructions stored in the first memory to perform steps performed by the requester in the method of identity authentication according to the first aspect.

[0031] According to a six aspect, provided in an embodiment of the present application is an authentication access controller, including:

• • [0032] a second processor; and
  • [0033] a second memory for storing instructions executable by the second processor.

[0034] The second processor is configured to invoke the instructions stored in the second memory to perform steps performed by the authentication access controller in the method of identity authentication according to the first aspect.

[0035] According to a seventh aspect, provided in an embodiment of the present application is a first authentication server, including:

• • [0036] a third processor; and
  • [0037] a third memory for storing instructions executable by the third processor.

[0038] The third processor is configured to invoke the instructions stored in the third memory to perform steps performed by the first authentication server in the method of identity authentication according to the first aspect.

[0039] According to an eighth aspect, further provided in an embodiment of the present application is a computer-readable storage medium, having a computer program stored thereon, the computer program performing, when run by a processor, steps performed by the authentication access controller, the requester, or the first authentication server in the method of identity authentication according to the first aspect.

[0040] According to a ninth aspect, provided in an embodiment of the present application is a computer program, comprising computer-readable codes. When the computer-readable codes are run in a computer device, a processor in the computer device performs steps performed by the authentication access controller, the requester, or the first authentication server in the method of identity authentication according to the first aspect.

[0041] According to a tenth aspect, provided in an embodiment of the present application is a computer program product, including computer program instructions, the computer program instructions causing a computer to perform steps performed by the authentication access controller, the requester, or the first authentication server in the method of identity authentication according to the first aspect.

[0042] According to the above technical solution, during identity authentication performed for an authentication access controller by a requester, confidentiality processing is performed on identity information carrying private or sensitive information and identity authentication result information, so that even if an attacker intercepts an exchanged message during transmission, the attacker cannot acquire the private or sensitive information therein, thereby preventing the attacker from focusing on attacking a legal authentication access controller, and ensuring the security of an authentication access controller, a requester, and even a network.

[0058] In a communication network, a requester may access the network through an authentication access controller. In order to ensure that the network accessed by the requester is a legal network, the requester needs to authenticate the identity of the authentication access controller.

[0059] Current wireless communication and mobile communication scenarios are used as an example. In a scenario where a requester accesses a wireless network through an authentication access controller, the requester may be a terminal device such as a mobile phone, a personal digital assistant (PDA), a tablet computer, or other terminal devices, and the authentication access controller may be a network side device such as a wireless access point, a wireless router, or other network side devices. In a scenario where a requester accesses a wired network through an authentication access controller, the requester may be a terminal device such as a desktop computer, a notebook computer, or the like, and the authentication access controller may be a network side device such as a switch, a router, or the like. In a scenario where a requester accesses a network of the 4th/5th generation mobile communication technology (abbreviated as 4G/5G) by an authentication access controller, the requester may be a terminal device such as a mobile phone, a tablet computer, or the like, and the authentication access controller may be a network side device such as a base station or the like. Certainly, the present application is likewise applicable to various data communication scenarios such as other wired networks, near field communication networks, and the like.

[0060] However, during identity authentication performed for the authentication access controller, the authentication access controller needs to provide identity information thereof for the identity authentication. The identity information is usually comprised in a digital certificate of the authentication access controller, and carries private or sensitive information. If an attacker intercepts the private or sensitive information in the digital certificate, severe security risks are posed to the authentication access controller, the requester, and the network.

[0061] To address the above technical problem, provided in an embodiment of the present application is a method of identity authentication. An authentication access controller acquires, from a first authentication server trusted thereby, a first authentication response message including an identity authentication result information ciphertext and a digital signature of a second authentication server trusted by a requester. The identity authentication result information ciphertext is generated by the first authentication server by using a protection nonce to encrypt information including identity authentication result information of the authentication access controller, and the identity authentication result information carries private or sensitive information. Confidentiality processing is performed on the identity authentication result information by the protection nonce, thereby ensuring the security of transmission of the identity authentication result information between the authentication server and the authentication access controller. Then, the authentication access controller sends an authentication result message to the requester. The authentication result message includes authentication result information that is obtained by the authentication access controller by using a message encryption key to encrypt to-be-encrypted data including the identity authentication result information ciphertext, the digital signature of the second authentication server, and the protection nonce, thereby ensuring the security of transmission of the private or sensitive information. Then, the requester uses the message encryption key to decrypt the authentication result information to obtain the protection nonce, the identity authentication result information ciphertext, and the digital signature of the second authentication server. The requester verifies the digital signature of the second authentication server, and after verification is successful, the requester uses the protection nonce to decrypt the identity authentication result information ciphertext to obtain the identity authentication result information of the authentication access controller, and the requester determines an identity authentication result of the authentication access controller according to the authentication result information. Confidentiality processing is performed on identity information and identity authentication result information, thereby protecting private or sensitive information, preventing an attacker from focusing on attacking a legal authentication access controller, and ensuring the security of an authentication access controller, a requester, and a network.

[0062] The above are merely examples of the requester, the authentication access controller, and the authentication server, and are not limitations set on the requester, the authentication access controller, and the authentication server. In other possible implementations of the embodiments of the present application, the requester, the authentication access controller, and the authentication server may also be other devices.

[0063] The method of identity authentication provided in the embodiment of the present application is used for unilateral identity authentication of the authentication access controller by the requester (AAC Authentication with an Unauthenticated REQ (AAUR)).

[0064] For ease of description, in the embodiments of the present application, the method of identity authentication of the present application will be described by using a requester (REQ), an authentication access controller (AAC), and an authentication server (AS) as an example.

[0065] An AS trusted by an AAC is referred to as a first authentication server AS-AAC. An AS trusted by an REQ is referred to as a second authentication server AS-REQ. AS-AAC and AS-REQ each hold a digital certificate that complies with specifications of ISO/IEC 9594-8/ITU X.509, other standards, or other technical systems, and a private key corresponding to the digital certificate, and AS-AAC has the capability of verifying the legality of a digital certificate of an AAC. When AS-AAC and AS-REQ are two different authentication servers. AS-AAC and AS-REQ trust each other, and know the digital certificate of each other or the public key in each other's digital certificate. A Certificate Sever-Decrypt (CS-DEC) holds an encryption certificate that complies with specifications of ISO/IEC 9594-8/ITU X.509, other standards, or other technical systems, and a private key corresponding to the encryption certificate. The CS-DEC may be a stand-alone server, or may be reside in AS-AAC.

[0066] The REQ may be an end point participating in an identity authentication process, is connected to the AAC, accesses a service provided by the AAC, and accesses the AS through the AAC. The REQ knows the digital certificate of AS-REQ trusted thereby or a public key in the digital certificate. The AAC may be another end point participating in the identity authentication process, is connected to the REQ, provides a service and communicates with the REQ, and can access AS-AAC directly. The AAC holds a digital certificate that complies with specifications of ISO/IEC 9594-8/ITU X.509, other standards, or other technical systems, and a private key corresponding to the digital certificate, and knows the encryption certificate of the CS-DEC or a public key in the encryption certificate.

[0067] A method of identity authentication provided in an embodiment of the present application will be described below with reference to FIG. 1. The method includes the following operations.

[0068] In S101, an AAC acquires a first authentication response message ASVeri from AS-AAC trusted thereby.

[0069] The ASVeri includes an identity authentication result information ciphertext and a digital signature Sig_{AS_REQ} of AS-REQ trusted by a REQ. The identity authentication result information ciphertext is generated by AS-AAC by using a protection nonce to encrypt information including identity authentication result information of the AAC. The identity authentication result information includes a verification result Res_AAC of verification for a digital certificate Cert_AAC of the AAC. Res_AAC is obtained after AS-AAC verifies the legality of Cert_AAC. Sig_{AS_REQ} is a digital signature generated by AS-REQ by performing calculation on other fields before Sig_{AS_REQ} in ASVeri.

[0070] It should be noted that if AS-AAC trusted by the AAC and AS-REQ trusted by the REQ are the same authentication server, that is, in the case of non-roaming, the authentication server trusted by both the REQ and the AAC may be represented by AS-AAC (or by AS-REQ). In this case, before the AAC acquires ASVeri, the AAC may send a first authentication request message AACVeri to AS-AAC (which may also be represented by AS-REQ). The AACVeri includes an identity information ciphertext EncPub_AS. The EncPub_AS is obtained by the AAC by using a public key of an encryption certificate to encrypt information including Cert_AAC and the protection nonce. AS-AAC (which may also be represented by AS-REQ) may use a private key corresponding to an encryption certificate of a Certificate Sever-Decrypt (CS-DEC) residing in AS-AAC (which may also be represented by AS-REQ) to decrypt EncPub_AS to obtain Cert_AAC and the protection nonce. Alternatively. AS-AAC (which may also be represented by AS-REQ) may send EncPub_AS to a stand-alone CS-DEC having an interactive and trust relationship therewith for decryption, acquire Cert_AAC and the protection nonce obtained by means of decryption, then verify legality of Cert_AAC to obtain a verification result Res_AAC, generate identity authentication result information of the AAC according to information including Res_AAC, use the protection nonce to encrypt information including the identity authentication result information to generate an identity authentication result information ciphertext, perform calculation on to-be-signed data including the identity authentication result information ciphertext to generate a digital signature Sig_{AS_AAC} (which may also be Sig_{AS_REQ}) of AS-AAC (which may also be represented by AS-REQ), generate a first authentication response message ASVeri according to information including the identity authentication result information ciphertext and Sig_{AS_AAC} (which may also be represented by Sig_{AS_REQ}), and send the ASVeri to the AAC.

[0071] If AS-AAC trusted by the AAC and AS-REQ trusted by the REQ are two different authentication servers, that is, in the case of roaming, before the AAC acquires ASVeri, the AAC may send a first authentication request message AACVeri to AS-AAC. The AACVeri includes an identity information ciphertext EncPub_AS. The EncPub_AS is obtained by the AAC by using a public key of an encryption certificate to encrypt information including Cert_AAC and the protection nonce. AS-AAC may use a private key corresponding to an encryption certificate of a certificate sever-decrypt (CS-DEC) residing in AS-AAC to decrypt EncPub_AS to obtain Cert_AAC and the protection nonce. Alternatively, AS-AAC may send EncPub_AS to a CS-DEC having an interactive and trust relationship therewith for decryption, acquire Cert_AAC and the protection nonce that are obtained by means of decryption, verify legality of Cert_AAC to obtain Res_AAC, generate identity authentication result information of the AAC according to information including Res_AAC, use the protection nonce to encrypt information including the identity authentication result information to generate an identity authentication result information ciphertext, perform calculation on to-be-signed data including the identity authentication result information ciphertext to generate a digital signature Sig_{AS_AAC} of AS-AAC, and send a second authentication request message AS-AACVeri to AS-REQ. The AS-AACVeri includes the identity authentication result information ciphertext and the Sig_{AS_AAC}, AS-REQ uses a public key of AS-AAC to verify the Sig_{AS_AAC}, performs, after verification is successful, calculation on to-be-signed data including the identity authentication result information ciphertext to generate a digital signature Sig_{AS_REQ} of AS-REQ, and sends a second authentication response message AS-REQVeri to AS-AAC. The AS-REQVeri includes the identity authentication result information ciphertext and the Sig_{AS_REQ}. AS-AAC generates a first authentication response message ASVeri according to information including the identity authentication result information ciphertext and the Sig_{AS_REQ}, and sends the ASVeri to the AAC.

[0072] In S102, an REQ acquires an authentication result message AACAuth sent by the AAC.

[0073] AACAuth includes authentication result information EncData_AAC. EncData_AAC is obtained by the AAC by using a message encryption key and using a symmetric encryption algorithm to encrypt to-be-encrypted data including the identity authentication result information ciphertext, the digital signature Sig_{AS_REQ} of the second authentication server, and the protection nonce. The message encryption key may be obtained by means of negotiation between the REQ and the AAC, or may be pre-shared by the REQ and the AAC. In the present application, an object to be encrypted is referred to as to-be-encrypted data.

[0074] In S103, the REQ uses a message encryption key to decrypt EncData_AAC to obtain a protection nonce, an identity authentication result information ciphertext, and Sig_{AS_REQ}.

[0075] EncData_AAC is obtained by the AAC by using the message encryption key and the symmetric encryption algorithm to encrypt information including the identity authentication result information ciphertext, the digital signature of the second authentication server, and the protection nonce, so that upon receiving EncData_AAC sent by the AAC, the REQ may use the message encryption key to decrypt EncData_AAC to obtain the protection nonce, the identity authentication result information ciphertext, and Sig_{AS_REQ}.

[0076] In S104, the REQ uses a public key of AS-REQ to verify Sig_{AS_REQ}.

[0077] REQ knows the public key of the authentication server trusted thereby, so that the REQ may use the public key of AS-REQ to verify Sig_{AS_REQ}. When verification is not successful, the received AACAuth may be discarded.

[0078] In S105, the REQ uses the protection nonce to decrypt the identity authentication result information ciphertext to obtain identity authentication result information.

[0079] In S106, the REQ determines an identity authentication result of the AAC according to Res_AAC in the identity authentication result information.

[0080] Res_AAC may indicate whether the AAC is legal, so that the REQ may determine, according to Res_AAC, whether the AAC is legal, thereby ensuring that the REQ can access a legal network.

[0081] It can be seen that confidentiality processing performed on identity authentication result information can prevent private or sensitive information from being exposed, so that even if an attacker intercepts identity authentication result information, the attacker cannot acquire private or sensitive information therein, thereby preventing the attacker from focusing on attacking a legal authentication access controller, and ensuring the security of an authentication access controller, a requester, and even a network. In addition, an authentication server is introduced, so that a requester can perform real-time unilateral identity authentication on an authentication access controller while confidentiality of identity related information of entities is ensured, thereby establishing the foundation for ensuring that a user can access a legal network.

[0082] It should be noted that the identity authentication result information of the AAC may be represented by Pub_AAC, and the protection nonce may be represented by Nonce_AACPub. The identity authentication result information ciphertext may be generated in the following manner: using a symmetric encryption algorithm and the protection nonce Nonce_AACPub to encrypt information including the identity authentication result information Pub_AAC of the AAC to obtain the identity authentication result information ciphertext. For example, an exclusive OR (XOR) operation may be performed on Nonce_AACPub and information including Pub_AAC to obtain an identity authentication result information ciphertext Pub_AAC^⊕Nonce_AACPub.

[0083] Before determining the identity authentication result of the AAC, the REQ may further determine whether verification for a digital signature of the AAC is successful. Please refer to FIG. 1. In some embodiments, AACAuth of S102 may further include a digital signature Sig_AAC of the AAC. To-be-signed data of Sig_AAC includes other fields before Sig_AAC in AACAuth. Correspondingly, the identity authentication result information Pub_AAC of the AAC may further include Cert_AAC, so that before determining the identity authentication result of the AAC according to Res_AAC in the identity authentication result information, the REQ further needs to determine whether verification for Sig_AAC is successful, and only after the verification is successful, the REQ can determine the identity authentication result of the AAC. A manner in which the REQ determines whether verification for Sig_AAC is successful is as follows: the REQ uses Cert_AAC in the identity authentication result information obtained by decrypting the identity authentication result information ciphertext to verify Sig_AAC, and determines, according to a verification result, whether verification for Sig_AAC is successful. In the present application, an object to be signed is referred to as to-be-signed data.

[0084] In some other embodiment, AACVeri sent by the AAC to AS-AAC may further include the digital signature Sig_AAC of the AAC. To-be-signed data of Sig_AAC includes other fields before Sig_AAC in AAC_Veri. Therefore, before determining the identity authentication result of the AAC according to Res_AAC in the identity authentication result information, the REQ further needs to determine whether verification for Sig_AAC is successful, and only after the verification is successful, the REQ can determine the identity authentication result of the AAC. The REQ determines, in the following manner, whether verification for Sig_AAC is successful: AS-AAC trusted by the AAC uses Cert_AAC obtained by decrypting the identity information ciphertext EncPub_AS in AACVeri to verify Sig_AAC, and only after verification is successful, a subsequent process is performed. Therefore, if the REQ can receive AACAuth of S102, the REQ determines that the verification for Sig_AAC is successful.

[0085] Please refer to FIG. 1, messages transmitted between the REQ, the AAC, and the authentication server may further include parameter information such as nonces generated by the AAC and/or the REQ, identifiers, etc. Normally, during identity authentication, these nonces and/or identifiers should remain unchanged when being transmitted via various messages. However, if cases such as a network jitter or attack, or the like occur, the parameter information such as the nonce and/or the identifier or the like in the message may be lost or tampered with. Thus, consistency verification may further be performed on the identifier and/or the nonce in the message during identity authentication, so as to ensure the reliability and freshness of the authentication result. The consistency verification includes the followings.

[0086] In some embodiments, if the AAC acquires a second nonce Nonce_REQ sent by the REQ and/or the identifier ID_REQ of the REQ, AACVeri sent by the AAC to AS-AAC may further include Nonce_REQ and/or ID_REQ, then in the case of non-roaming. ASVeri of S101 may further include Nonce_REQ and/or ID_REQ, and in the case of roaming, AS-AACVeri sent by AS-AAC to AS-REQ may further include Nonce_REQ and/or ID_REQ, and AS-REQVeri sent by AS-REQ to AS-AAC may further include Nonce_REQ and/or ID_REQ. ASVeri of S101 may further include Nonce_REQ and/or ID_REQ. The to-be-encrypted data of EncData_AAC in AACAuth of S102 further includes Nonce_REQ and/or ID_REQ. Correspondingly, in S103, the REQ decrypts EncData_AAC to further obtain Nonce-REQ and/or ID_REQ. Therefore, before performing S106, the REQ further needs to perform comparison to determine whether Nonce_REQ and/or ID_REQ obtained by decrypting EncData_AAC is consistent with Nonce_REQ generated by the REQ and/or the identifier ID_REQ of the REQ itself, and if they are consistent, the REQ further performs S106, or if not, the REQ discards AACAuth.

[0087] In some other embodiments. AACAuth of S102 may further include a message integrity check code MacTag_AAC. MacTag_AAC is generated by the AAC by using a message integrity check key to perform integrity check calculation on fields, other than MacTag_AAC, in AACAuth. Correspondingly, before performing S106, the REQ further needs to check MacTag_AAC, and if the check of MacTag_AAC is successful, the REQ further performs S106. During the check of MacTag_AAC, the REQ should use the message integrity check key to perform calculation on fields, other than MacTag_AAC, in AACAuth to generate MacTag_AAC, and compare calculated MacTag_AAC with MacTag_AAC, in received AACAuth. If the calculated MacTag_AAC is consistent with the MacTag_AAC in received AACAuth, the check is successful; otherwise, the check is not successful. A manner of generating the message integrity check key used by the REQ and the AAC will be described in a next embodiment.

[0088] In the above embodiments, the message encryption key used by the AAC and the REQ may be obtained by means of negotiation between the REQ and the AAC. Therefore, further provided in the present embodiment is a method for negotiating a message encryption key by a REQ and an AAC. Referring to FIG. 2, the method includes the following operations.

[0089] In S201, an AAC sends a key request message AACInit to a REQ.

[0090] The AACInit includes a key exchange parameter KeyInfo_AAC of the AAC. KeyInfo_AAC includes a temporary public key of the AAC. Key exchange refers to a key exchange algorithm such as Diffie-Hellman (DR), etc. The AACInit may further include a first nonce Nonce_AAC generated by the AAC.

[0091] In addition, the AACInit may further include Security capabilities AA c. Security capabilities_AAC represents security capability parameter information supported by the AAC, and includes an identity authentication suite (the identity authentication suite includes one or more identity authentication methods), one or more symmetric encryption algorithms, one or more integrity check algorithms, and/or one or more key derivation algorithms etc., supported by the AAC, so that the REQ selects and uses a particular security policy. Therefore, the REQ may select, according to Security capabilities_AAC, the particular security policy security capabilities_REQ to be used by the REQ. Security capabilities_REQ represents an identity authentication method, a symmetric encryption algorithm, an integrity check algorithm, and/or a key derivation algorithm etc., correspondingly determined and used by the REQ.

[0092] In S202, the REQ performs key exchange calculation according to a temporary private key corresponding to a key exchange parameter KeyInfo_REQ of the REQ and a temporary public key included in KeyInfo_AAC to generate a first key, and calculates, according to information including the first key, a message encryption key by using a key derivation algorithm.

[0093] If AACInit of S201 further includes Nonce_AAC generated by the AAC, the REQ may perform key exchange calculation according to a temporary private key corresponding to KeyInfo_REQ and a temporary public key included in KeyInfo_AAC to generate a first key K1, and calculate a message encryption key according to K1 in combination with information including Nonce_AAC and a second nonce Nonce_REQ generated by the REQ and by using a negotiated or preset key derivation algorithm. The negotiated key derivation algorithm may be selected to use by the REQ according to Security capabilities_AAC sent by the AAC. KeyInfo_REQ is the key exchange parameter generated by the REQ, and includes the temporary public key of the REQ. The temporary private key corresponding to KeyInfo_REQ is generated by the REQ, and corresponds to the temporary public key of the REQ. That is, the temporary public key and the temporary private key are a temporary public-private key pair.

[0094] In S203, the REQ sends a key response message REQInit to the AAC.

[0095] The REQInit includes KeyInfo_REQ, so that the AAC performs calculation according to information including the temporary private key corresponding to KeyInfo_AAC and the temporary public key included in KeyInfo_REQ to obtain the message encryption key. The temporary private key corresponding to KeyInfo_AAC is generated by the AAC, and corresponds to the temporary public key of the AAC. That is, the temporary public key and the temporary private key are a temporary public-private key pair.

[0096] The REQInit may further include Security capabilities_REQ. The REQInit may further include Nonce_REQ, so that the AAC performs calculation according to information including the temporary private key corresponding to KeyInfo_AAC the temporary public key included in KeyInfo_REQ, the Nonce_AAC, and the Nonce_AAC to obtain the message encryption key.

[0097] The REQInit may further include Nonce_AAC, and before calculating the message encryption key, the AAC may verify consistency between Nonce_AAC in REQInit and Nonce_AAC generated by the AAC, so as to ensure that REQInit received by the AAC is a response message for AACInit.

[0098] In S204, the AAC performs key exchange calculation according to a temporary private key corresponding to KeyInfo_AAC and a temporary public key included in KeyInfo_REQ to generate the first key, and calculates, according to information including the first key, a message encryption key by using the key derivation algorithm.

[0099] If the REQInit further includes Nonce_REQ, the AAC may perform key exchange calculation according to the temporary private key corresponding to the KeyInfo_AAC and the temporary public key included in the KeyInfo_REQ to generate the first key K1, and calculate the message encryption key according to K1 in combination with information including Nonce_AAC and Nonce_REQ and by using a negotiated or preset key derivation algorithm. The negotiated key derivation algorithm may be selected to use by the AAC according to Security capabilities_REQ sent by the REQ.

[0100] It should be noted that in the embodiment in FIG. 2, the REQ and the AAC may also generate a message integrity check key. An implementation manner in which the REQ and the AAC each generates a message integrity check key is the same as the implementation manner illustrated in the embodiment in FIG. 2 in which the REQ and the AAC each generates a message encryption key. For example, the AAC may use the key derivation algorithm to derive a string of key data as in the embodiment in FIG. 2. The string of key data may be used as the message encryption key, and may also be used as the message integrity check key. Alternatively, part of key data in the string of key data is used as the message encryption key, and another part thereof is used as the message integrity check key. The AAC may also use the key derivation algorithm to derive two identical or different strings of key data separately as in the embodiment in FIG. 2, where one string of key data is used as the message encryption key, and the other string of key data is used as the message integrity check key. The REQ may use the key derivation algorithm to derive a string of key data as in the embodiment in FIG. 2. The string of key data may not only be used as the message encryption key, but also may be used as the message integrity check key. Alternatively, part of key data in the string of key data is used as the message encryption key, and another part thereof is used as the message integrity check key. The REQ may also use the key derivation algorithm to derive two identical or different strings of key data separately as in the embodiment in FIG. 2, where one string of key data is used as the message encryption key, and the other string of key data is used as the message integrity check key.

[0101] Further provided in an embodiment of the present application is a method of using information exchange between an AAC and a REQ to determine a first authentication server and/or a second authentication server used in a current authentication process.

[0102] Please refer to FIG. 2. The AAC adds the identifier ID_{AS_AAC} of at least one authentication server trusted by the AAC to AACInit of S201, and the REQ determines an identifier ID_{AS_REQ} of at least one authentication server trusted thereby according to ID_{AS_AAC} in AACInit. During implementation, the REQ selects the identifier of at least one authentication server trusted thereby from ID_{AS_AAC} as ID_{AS_REQ}, and if selection is not successful, the REQ uses an identifier of at least one authentication server trusted thereby as IDs_{AS_REQ} (where successful selection corresponds to the case of non-roaming, and unsuccessful selection corresponds to the case of roaming), and adds ID_{AS_REQ} to REQInit of step S203 to send the same to the AAC. In turn, the AAC is able to determine the first authentication server according to ID_{AS_AAC} and ID_{AS_REQ}. For example, the AAC may determine whether an identifier of at least one identical authentication server is present in ID_{AS_REQ} and ID_{AS_AAC} and if so, i.e., in the case of non-roaming, the AAC determines, from the identifier of the at least one authentication server trusted by both the REQ and the AAC, the first authentication server participating in identity authentication, or if not, i.e., in the case of roaming, the AAC needs to determine, according to ID_{AS_AAC}, the first authentication server AS-AAC participating in identity authentication, and send ID_{AS_REQ} to AS-AAC, so that AS-AAC determines the second authentication server AS-REQ according to ID_{AS_REQ}.

[0103] In another implementation manner, the AAC may not have to send ID_{AS_AAC} to the REQ, and the REQ adds the identifier ID_{AS_REQ} of at least one authentication server trusted thereby to REQInit of step S203. A specific implementation manner in which the first authentication server and/or the second authentication server participating in the identity authentication process is determined according to ID_{AS_REQ} and the identifier ID_{AS_AAC} of the authentication server trusted by the AAC is the same as the preceding implementation manner.

[0104] An authentication server trusted by the REQ and an authentication server trusted by the AAC may be the same or different. The authentication server trusted by the REQ and the authentication server trusted by the AAC being the same is the case of non-roaming, and the authentication server trusted by the REQ and the authentication server trusted by the AAC being different is the case of roaming.

[0105] Referring to FIG. 3, FIG. 3 is an embodiment of a method of identity authentication in the case of non-roaming, hi this case, an authentication server trusted by both a REQ and an AAC may be represented by AS-AAC (or AS-REQ). Before the embodiment is performed, the REQ and the AAC both have a message encryption key. The message encryption key is pre-shared between the REQ and the AAC or negotiated by using the method shown in FIG. 2. On the basis of the embodiment of FIG. 1, before S101, the method of identity authentication of the embodiment of FIG. 3 further includes the following operations.

[0106] In S301, the AAC sends a first authentication request message AACVeri to AS-AAC.

[0107] The AACVeri includes an identity information ciphertext EncPub_AS. EncPub_AS is obtained by the AAC by using a public key of an encryption certificate to encrypt information including Cert_AAC and a protection nonce Nonce_AACPub.

[0108] In S302, AS-AAC uses a private key corresponding to the encryption certificate to decrypt EncPub_AS to obtain Cert_AAC and Nonce_AACPub, verifies legality of Cert_AAC to obtain Res_AAC, and generates identity authentication result information Pub_AAC of the AAC according to information including Res_AAC.

[0109] In S303, the AS-AAC uses Nonce_AACPub to encrypt information including Pub_AAC generate an identity authentication result information ciphertext, performs calculation on to-be-signed data including the identity authentication result information ciphertext to generate a digital signature Sig_{AS_AAC} of AS-AAC, and generates a first authentication response message ASVeri according to information including the identity authentication result information ciphertext and Sig_{AS_AAC}.

[0110] It should be noted that S304 to S309 in FIG. 3 sequentially correspond to S101 to S106 in FIG. 1, and AS-AAC and Sig_{AS_AAC} in S304 to S309 correspond to AS-REQ and Sig_{AS_REQ} in S101 to S106.

[0111] Referring to FIG. 4, FIG. 4 is an embodiment of a method of identity authentication in the case of roaming. Before the embodiment is performed, a REQ and an AAC both have a message encryption key. The message encryption key is pre-shared between the REQ and the AAC or negotiated by using the method shown in FIG. 2. On the basis of the embodiment of FIG. 1, before S101, the method of identity authentication of the embodiment of FIG. 4 further includes the following operations.

[0112] In S401, the AAC sends a first authentication request message AACVeri to AS-AAC.

[0113] The AACVeri includes an identity information ciphertext EncPub_AS. EncPub_AS is obtained by the AAC by using a public key of an encryption certificate to encrypt information including Cert_AAC and a protection nonce Nonce_AACPub.

[0114] In S402, AS-AAC uses a private key corresponding to the encryption certificate to decrypt EncPub_AS to obtain Cert_AAC and Nonce_AACPub, verifies legality of Cert_AAC to obtain Res_AAC, generates identity authentication result information Pub_AAC of the AAC according to information including Res_AAC, uses Nonce_AACPub to encrypt information including Pub_AAC to generate an identity authentication result information ciphertext, and performs calculation on to-be-signed data including the identity authentication result information ciphertext generate a digital signature Sig_{AS_AAC} of AS-AAC.

[0115] In S403, AS-AAC sends a second authentication request message AS-AACVeri to AS-REQ.

[0116] The AS-AACVeri includes the identity authentication result information ciphertext and Sig_{AS_AAC}.

[0117] In S404, AS-REQ uses a public key of AS-AAC to verify Sig_{AS_AAC}.

[0118] If verification is successful, S405 is performed.

[0119] In S405, AS-REQ performs calculation on to-be-signed data including the identity authentication result information ciphertext to generate a digital signature Sig_{AS_REQ} of AS-REQ.

[0120] In S406, AS-REQ sends a second authentication response message AS-REQVeri to AS-AAC.

[0121] The AS-REQVeri includes the identity authentication result information ciphertext and Sig_{AS_REQ}.

[0122] In S407. AS-AAC sends a first authentication response message ASVeri to the AAC.

[0123] The ASVeri includes the identity authentication result information ciphertext and Sig_{AS_REQ} in AS-REQVeri.

[0124] It should be noted that S407 to S412 in FIG. 4 correspond to S101 to S106 in FIG. 1.

[0125] Referring to FIG. 5, FIG. 5 is an embodiment of a method of identify authentication in the case of non-roaming. In this case, an authentication server trusted by both a REQ and an AAC may be represented by AS-AAC (or AS-REQ). In the embodiment, a message encryption key negotiation process between a REQ and an AAC is fused into an identity authentication process, thereby facilitating project implementation. A digital signature Sig_AAC of an AAC is verified by a REQ. The method includes the following operations.

[0126] In S501, an AAC generates Nonce_AAC and KeyInfo_AAC, and generates Security capabilities_AAC as desired.

[0127] In S502, the AAC sends a key request message AACInit to a REQ.

[0128] The AACInit includes Nonce_AAC, KeyInfo_AAC, and Security capabilities_AAC. Security capabilities_AAC is an optional field, represents security capability parameter information supported by the AAC, and includes an identity authentication suite, one or more symmetric encryption algorithms, one or more integrity check algorithms, and/or one or more key derivation algorithms etc., supported by the AAC (applicable herein).

[0129] In S503, the REQ generates Nonce_REQ and KeyInfo_REQ, generates Security capabilities_REQ as desired, performs key exchange calculation according to a temporary private key corresponding to KeyInfo_REQ and a temporary public key included in KeyInfo_AAC to generate a first key K1, calculates a message encryption key and a message integrity check key according to K1 in combination with Nonce_AAC, Nonce_REQ, and other information (other information used by the REQ and the AAC is the same, and is optional, such as a particular string, etc.) and by using a negotiated or preset key derivation algorithm, and uses the message encryption key and a symmetric encryption algorithm to calculate an identifier ciphertext EncData_REQ of the REQ.

[0130] Security capabilities_REQ is an optional field, and represents selection of a particular security policy performed by the REQ according to Security capabilities_AAC, i.e., an identity authentication method, a symmetric encryption algorithm, an integrity check algorithm, and/or a key derivation algorithm, etc., determined and used by the REQ (applicable herein). Whether the REQ generates Security capabilities_REQ depends on whether AACInit sent by the AAC to the REQ carries Security capabilities_AAC. The generating, by the REQ, the message integrity check key is an optional operation, and this step may be performed subsequently as required.

[0131] In S504, the REQ sends a key response message REQInit to the AAC.

[0132] The REQInit includes Nonce_AAC, Nonce_REQ, Security capabilities_REQ, KeyInfo_REQ, and EncData_REQ. Security capabilities_REQ is an optional field. Nonce_AAC should be equal to a corresponding field in AACInit. To-be-encrypted data of EncData_REQ includes ID_REQ.

[0133] In S505, the AAC performs, upon receiving REQInit, the following operations (if not specified otherwise or if not due to a logical relationship, actions numbered (1), (2), herein do not necessarily have a sequential order according to the numbers, applicable herein), including:

• • [0134] (1) checking whether Nonce_AAC in REQInit is the same as Nonce_AAC generated by the AAC, and if they are different, discarding REQInit;
  • [0135] (2) performing key exchange calculation according to the temporary private key corresponding to KeyInfo_AAC and the temporary public key included in KeyInfo_REQ to generate a first key K1, and calculating a message encryption key and a message integrity check key according to K1 in combination with Nonce_AAC, Nonce_REQ, and other information (other information used by the AAC and the REQ is the same, and is optional, such as a particular string, etc.) and by using a negotiated or preset key derivation algorithm, wherein the generating, by the AAC, the message integrity check key is an optional operation, and this step may be performed subsequently as required;
  • [0136] (3) using the message encryption key and the symmetric encryption algorithm to decrypt EncData_REQ to obtain ID_REQ;
  • [0137] (4) generating a protection nonce Nonce_AACPub; and
  • [0138] (5) using a public key of an encryption certificate to calculate an identity information ciphertext EncPub_AS.

[0139] In S506, the AAC sends a first authentication request message AACVeri to AS-AAC.

[0140] The AACVeri includes ID_REQ, Nonce_REQ, and EncPub_AS. ID_REQ and Nonce_REQ should be respectively equal to corresponding fields in REQInit. To-be-encrypted data of EncPub_AS includes Cert_AAC and Nonce_AACPub.

[0141] In S507. AS-AAC performs, upon receiving AACVeri, the following operations:

• • [0142] (1) using a private key corresponding to the encryption certificate to decrypt EncPub_AS to obtain Cert_AAC and Nonce_AACPub;
  • [0143] (2) verifying legality of Cert_AAC to obtain Res_AAC, and generating identity authentication result information Pub_AAC according to information including Cert_AAC and Res_AAC;
  • [0144] (3) performing an XOR operation on Pub_AAC and Nonce_AACPub to generate an identity authentication result information ciphertext Pub_AAC ⊕Nonce_AACPub; and
  • [0145] (4) calculating a digital signature Sig_{AS_AAC} of AS-AAC.

[0146] In S508, AS-AAC sends a first authentication response message ASVeri to the AAC.

[0147] The ASVeri includes ID_REQ, Nonce_REQ, Pub_AAC^⊕Nonce_AACPub, and Sig_{AS_AAC}. ID_REQ, Nonce_REQ. Nonce_AACPub should be respectively equal to corresponding fields in AACVeri. To-be-signed data of Sig_{AS_AAC} includes other fields before Sig_{AS_AAC} in ASVeri. For example, when ASVeri sequentially includes ID_REQ, Nonce_REQ, Pub_AAC^⊕Nonce_AACPub, and Sig_{AS_AAC}, the to-be-signed data of Sig_{AS_AAC} includes ID_REQ, Nonce_REQ, and Pub_AAC^⊕Nonce_AACPub.

[0148] In S509, the AAC performs, upon receiving ASVeri, the following operations:

• • [0149] (1) using the message encryption key and the symmetric encryption algorithm to calculate authentication result information EncData_AAC;
  • [0150] (2) calculating a digital signature Sig_AAC of the AAC; and
  • [0151] (3) calculating MacTag_AAC as desired.

[0152] In S510, the AAC sends an authentication result message AACAuth to the REQ.

[0153] The AACAuth includes EncData_AAC, Sig_AAC, and MacTag_AAC. To-be-encrypted data of EncData_AAC includes ID_REQ, Nonce_REQ, Pub_AAC^⊕Nonce_AACPub, Sig_{AS_AAC}, and Nonce_AACPub ID_REQ, Nonce_REQ, Pub_AAC^⊕Nonce_AACPub, and Sig_{AS_AAC} should be respectively equal to corresponding fields in ASVeri. To-be-signed data of Sig_AAC includes other fields before the Sig_AAC field in AACAuth. MacTag_AAC is an optional field, and a calculation process thereof includes: using the message integrity check key and the integrity check algorithm to perform calculation on information including fields, other than MacTag_AAC, in AACAuth to generate MacTag_AAC.

[0154] In S511, the REQ performs, upon receiving the AACAuth, the following operations:

• • [0155] (1) if MacTag_AAC is present in AACAuth, verifying MacTag_AAC,
  • [0156] a verification process of MacTag_AAC including: using the message integrity check key
  • [0157] and the integrity check algorithm to perform calculation locally on information including fields, other than MacTag_AAC, in AACAuth to generate MacTag_AAC (the calculation manner is the same as a manner in which the AAC calculates MacTag_AAC), and comparing calculated MacTag_AAC with MacTag_AAC in received AACAuth;
  • [0158] (2) using the message encryption key and the symmetric encryption algorithm to decrypt EncData_AAC to obtain ID_REQ, Nonce_REQ, Pub_AAC^⊕Nonce_AACPub, Sig_{AS_AAC}, and Nonce_AACPub;
  • [0159] (3) checking whether Nonce_REQ and ID_REQ are respectively the same as Nonce_REQ generated by the REQ and the identifier ID_REQ of the REQ itself;
  • [0160] (4) performing an XOR operation on Nonce_AACPub and Pub_AAC^⊕Nonce_AACPub, to recover Pub_AAC;
  • [0161] (5) using Cert_AAC in Pub_AAC to verify Sig_AAC;
  • [0162] (6) using a public key of AS-AAC to verify Sig_{AS_AAC}; and
  • [0163] (7) after the above checking and verifications are successful, determining an identity authentication result of the AAC according to Res_AAC in Pub_AAC, or if any step in the above checking and verifications is not successful, discarding AACAuth immediately.

[0164] Referring to FIG. 6, FIG. 6 is another embodiment of a method of identity authentication in the case of non-roaming. In this case, an authentication server trusted by both a REQ and an AAC may be represented by AS-AAC (or AS-REQ), in the embodiment, a message encryption key negotiation process between a REQ and an AAC is fused into an identity authentication process, thereby facilitating project implementation. A digital signature Sig_AAC of an AAC is verified by AS-AAC. The method includes the following operations.

[0165] In S601, an AAC generates Nonce_AAC and KeyInfo_AAC, and generates Security capabilities_AAC as desired.

[0166] In S602, the AAC sends a key request message AACInit to a REQ.

[0167] The AACInit includes Nonce_AAC, KeyInfo_AAC, and Security capabilities_AAC. Security capabilities_AAC is an optional field.

[0168] In S603, the REQ generates Nonce_REQ and KeyInfo_REQ, generates Security capabilities_REQ as desired, performs key exchange calculation according to a temporary private key corresponding to KeyInfo_REQ and a temporary public key included in KeyInfo_AAC to generate a first key K1 calculates a message encryption key and a message integrity check key according to K1 in combination with Nonce_AAC, Nonce_REQ, and other information (other information used by the REQ and the AAC is the same, and is optional, such as a particular string, etc.) and by using a negotiated or preset key derivation algorithm, and uses the message encryption key and a symmetric encryption algorithm to calculate an identifier ciphertext EncData_REQ of the REQ.

[0169] In S604, the REQ sends a key response message REQInit to the AAC.

[0170] The REQInit includes Nonce_AAC, Nonce_REQ, Security capabilities_REQ, KeyInfo_REQ, and EncData_REQ. To-be-encrypted data of EncData_REQ includes ID_REQ. Nonce_AAC should be equal to a corresponding field in AACInit. Security capabilities_REQ is an optional field.

[0171] In S605, the AAC performs, upon receiving REQInit, the following operations:

• • [0172] (1) checking whether Nonce_AAC in REQInit is the same as Nonce_AAC generated by the AAC, and if they are different, discarding REQInit;
  • [0173] (2) performing key exchange calculation according to the temporary private key corresponding to KeyInfo_AAC and the temporary public key included in KeyInfo_REQ to generate a first key K1, and calculating a message encryption key and a message integrity check key according to K1 in combination with Nonce_AAC, Nonce_REQ, and other information (other information used by the AAC and the REQ is the same, and is optional, such as a particular string, etc.) and by using a negotiated or preset key derivation algorithm;
  • [0174] (3) using the message encryption key and the symmetric encryption algorithm to decrypt EncData_REQ to obtain ID_REQ;
  • [0175] (4) generating a protection nonce Nonce_AACPub;
  • [0176] (5) using a public key of an encryption certificate to calculate an identity information ciphertext EncPub_AS; and
  • [0177] (6) calculating a digital signature Sig_AAC, of the AAC.

[0178] In S606, the AAC sends a first authentication request message AACVeri to AS-AAC.

[0179] The AACVeri includes ID_REQ, EncPub_AS Nonce_REQ, and Sig_AAC. ID_REQ and Nonce_REQ should be respectively equal to corresponding fields in REQInit. To-be-encrypted data of EncPub_AS includes Cert_AAC and Nonce_AACPub. To-be-signed data of Sig_AAC includes other fields before Sig_AAC in AACVeri.

[0180] In S607, AS-AAC performs, upon receiving AACVeri the following operations:

• • [0181] (1) using a private key corresponding to the encryption certificate to decrypt EncPub_AS to acquire Cert_AAC and Nonce_AACPub;
  • [0182] (2) using Cert_AAC to verify Sig_AAC, and if verification is not successful, discarding AACVeri;
  • [0183] (3) verifying legality of Cert_AAC to obtain Res A m, and generating Pub_AAC according to information including Res_AAC;
  • [0184] (4) performing an XOR operation on Pub_AAC and Nonce_AACPub to generate Pub_AAC^⊕Nonce_AACPub; and
  • [0185] (5) calculating a digital signature Sig_{AS_AAC} of AS-AAC.

[0186] In S608, AS-AAC sends a first authentication response message ASVeri to the AAC.

[0187] The ASVeri includes ID_REQ, Nonce_REQ, Pub_AAC^⊕Nonce_AACPub, and Sig_{AS_AAC}. Nonce_REQ, and Nonce_AACPub should be respectively equal to corresponding fields in AACVeri. To-be-signed data of Sig_{AS_AAC} includes ID_REQ, Nonce_REQ, and Pub_AAC^⊕Nonce_AACPub.

[0188] In S609, the AAC performs, upon receiving ASVeri, the following operations:

• • [0189] (1) using the message encryption key and the symmetric encryption algorithm to calculate authentication result information EncData_AAC; and
  • [0190] (2) calculating MacTag_AAC.

[0191] In S610, the AAC sends an authentication result message AACAuth to the REQ.

[0192] The AACAuth includes EncData_AAC and MacTag_AAC. To-be-encrypted data of EncData_AAC includes ID_REQ, Nonce_REQ, Pub_AAC^⊕Nonce_AACPub, Sig_{AS_AAC}, and Nonce_AACPub. ID_REQ, Nonce_REQ, Pub_AAC^⊕Nonce_AACPub, and Sig_{AS_AAC} should be respectively equal to corresponding fields in ASVeri. A calculation process of MacTag_AAC is as described in the embodiment of FIG. 5.

[0193] In S611, the REQ performs, upon receiving the AACAuth, the following operations:

• • [0194] (1) verifying MacTag_AAC, a verification process being as described in the embodiment of FIG. 5;
  • [0195] (2) using the message encryption key and the symmetric encryption algorithm to decrypt EncData_AAC to obtain ID_REQ, Nonce_REQ, Pub_AAC^⊕Nonce_AACPub, Sig^AS_AAC, and Nonce_AACPub;
  • [0196] (3) checking whether Nonce_REQ and ID_REQ are respectively the same as Nonce_REQ generated by the REQ and the identifier ID_REQ of the REQ itself;
  • [0197] (4) using a public key of AS-AAC to verify Sig_{AS_AAC}; and
  • [0198] (5) if the above checking and verifications are successful, performing an XOR operation on Nonce_AACPub and Pub_AAC^⊕Nonce_AACPub to recover Pub_AAC, and determining an identity authentication result of the AAC according to Res_AAC in Pub_AAC; if any step in the above checking and verifications is not successful, discarding AACAuth immediately.

[0199] Referring to FIG. 7, FIG. 7 is an embodiment of a method of identity authentication in the case of roaming. In the embodiment, a message encryption key negotiation process between a REQ and an AAC is fused into an identity authentication process, thereby facilitating project implementation. A digital signature Sig_AAC of an AAC is verified by a REQ. The method includes:

[0200] in S701, an AAC generates Nonce_AAC and KeyInfo_AAC, and generates Security capabilities_AAC as desired.

[0201] In S702, the AAC sends a key request message AACInit to a REQ.

[0202] The AACInit includes Nonce_AAC, KeyInfo_AAC, Security capabilities_AAC, and ID_{AS_AAC}. Security capabilities_AAC and ID_{AS_AAC} are optional fields. ID_{AS_AAC} represents an identifier of at least one authentication server trusted by the AAC, and is used to allow the REQ to determine, according to ID_{AS_AAC}, whether a mutually trusted authentication server exists (applicable herein).

[0203] In S703, the REQ generates Nonce_REQ and KeyInfo_REQ, generates ID_{AS_REQ} and Security capabilities_REQ as desired, performs key exchange calculation according to a temporary private key corresponding to KeyInfo_REQ and a temporary public key included in KeyInfo_AAC to generate a first key K1, calculates a message encryption key and a message integrity check key according to K1 in combination with Nonce_AAC, Nonce_REQ, and other information (other information used by the REQ and the AAC is the same, and is optional, such as a particular string, etc.) and by using a negotiated or preset key derivation algorithm, and uses the message encryption key and a symmetric encryption algorithm to calculate an identifier ciphertext EncData_REQ of the REQ.

[0204] ID_{AS_REQ} and Security capabilities_REQ are optional fields. The generating, by the REQ, the message integrity check key is an optional operation, and this step may be performed subsequently as required. ID_{AS_REQ} represents an identifier of at least one authentication server trusted by the REQ. When ID_{AS_AAC} is present in AACInit, the REQ selects, if possible, from authentication servers trusted thereby, at least one authentication server identifier, which is the same as that in ID_{AS_AAC}, as ID_{AS_REQ}, and if selection is not successful, uses an identifier of at least one authentication server trusted thereby as ID_{AS_REQ}; when ID_{AS_AAC} is not present in AACInit, the REQ uses an identifier of at least one authentication server trusted thereby as ID_{AS_REQ} (applicable herein).

[0205] In S704, the REQ sends a key response message REQInit to the AAC.

[0206] The REQInit includes Nonce_AAC, Nonce_REQ, Security capabilities_REQ, KeyInfo_REQ, EncData_REQ, and ID_{AS_REQ}. To-be-encrypted data of EncData_REQ includes ID_REQ. Nonce_AAC should be equal to a corresponding field in AACInit. Security capabilities_REQ and ID_{AS_REQ} are optional fields.

[0207] In S705, the AAC performs, upon receiving REQInit, the following operations:

• • [0208] (1) checking whether Nonce_AAC in REQInit is the same as Nonce_AAC generated by the AAC, and if they are different, discarding REQInit;
  • [0209] (2) performing key exchange calculation according to the temporary private key corresponding to KeyInfo_AAC and the temporary public key included in KeyInfo_REQ to generate a first key K1, and calculating a message encryption key and a message integrity check key according to K1 in combination with Nonce_AAC, Nonce_REQ, and other information (other information used by the AAC and the REQ is the same, and is optional, such as a particular string, etc.) and by using a negotiated or preset key derivation algorithm, wherein the generating, by the AAC, the message integrity check key is an optional operation, and this step may be performed subsequently as required;
  • [0210] (3) using the message encryption key and the symmetric encryption algorithm to decrypt EncData_REQ to obtain ID_REQ;
  • [0211] (4) generating a protection nonce Nonce_AACPub;
  • [0212] (5) using a public key of an encryption certificate to calculate an identity information ciphertext EncPub_AS; and
  • [0213] (6) if REQInit carries ID_{AS_REQ} and AACInit carries ID_{AS_AAC}, determining, by the AAC, whether an identifier of at least one identical authentication server is present in ID_{AS_REQ} and ID_{AS_AAC}, wherein if so, i.e., in the case of non-roaming, the AAC determines, from the identifier of the at least one authentication server trusted by both the REQ and the AAC, a first authentication server participating in identity authentication; and if not, i.e., in the case of roaming, the AAC needs to determine, according to ID_{AS_AAC}, a first authentication server AS-AAC participating in identity authentication, and send ID_{AS_REQ} to AS-AAC, so that AS-AAC determines a second authentication server AS-REQ according to ID_{AS_REQ}; or,
  • [0214] if REQInit carries ID_{AS_REQ}, but AACInit does not carry ID_{AS_AAC}, determining, by the AAC, whether an identifier of at least one identical authentication server is present in ID_{AS_REQ} and authentication servers trusted by the AAC, wherein if so, i.e., in the case of non-roaming, the AAC determines, from the identifier of the at least one authentication server trusted by both the REQ and the AAC, a first authentication server participating in identity authentication, and if not, i.e., in the case of roaming, the AAC needs to determine, according to the authentication servers trusted thereby, a first authentication server AS-AAC participating in identity authentication, and send ID_{AS_REQ} to AS-AAC, so that AS-AAC determines a second authentication server AS-REQ according to ID_{AS_REQ}.

[0215] It should be noted that a result determined in this embodiment is the case of roaming.

[0216] In S706, the AAC sends a first authentication request message AACVeri to AS-AAC.

[0217] The AACVeri includes EncPub_AS, ID_REQ, Nonce_REQ, and ID_{AS_REQ}, ID_REQ, Nonce_REQ, and ID_{AS_REQ} should be respectively equal to corresponding fields in REQInit. To-be-encrypted data of EncPub_AS includes Cert_AAC and Nonce_AACPub. ID_{AS_REQ} is an optional field, and is used to cause AS-AAC to determine, according to ID_{AS_REQ}, the authentication server trusted by the REQ.

[0218] In S707, AS-AAC sends, upon receiving the AACVeri, a decryption request message AS-AACRReq to a Certificate Sever-Decrypt (CS-DEC).

[0219] The AS-AACReq includes EncPub_AS. The EncPub_AS should be equal to a corresponding field in AACVeri.

[0220] In S708, the CS-DEC uses, upon receiving the AS-AACReq private key corresponding to the encryption certificate to decrypt EncPub_AS to obtain Cert_AAC and Nonce_AACPub.

[0221] In S709, the CS-DEC sends, a decryption response message CS-DECRep to AS-AAC.

[0222] The CS-DECReq includes Cert_AAC and Nonce_AACpub, obtained by means of decryption:

[0223] In S710, AS-AAC performs, upon receiving the CS-DECRep, the following operations:

• • [0224] (1) verifying legality of Cert_AAC to obtain Res_AAC, and generating Pub_AAC according to information including Cert_AAC and Res_AAC;
  • [0225] (2) performing an XOR operation on Pub_AAC and Nonce_AACPub to generate Pub_{AAC_hu ⊕}Nonce_AACPub;
  • [0226] (3) calculating a digital signature Sig_{AS_AAC} of AS-AAC; and
  • [0227] (4) if IDS_{AS_REQ} is present in AACVeri, determining, by AS-AAC, the second authentication server AS-REQ according to ID_{AS_REQ}; if ID_{AS_REQ} is not present in AACVeri, it is indicated that AS-AAC has determined and learned AS-REQ.

[0228] In S711, AS-AAC sends a second authentication request message AS-AACVeri to AS-REQ.

[0229] The AS-AACVeri includes ID_REQ, Nonce_REQ, Pub_AAC^⊕Nonce_AACPub and Sig_{AS_AAC}. ID_REQ, Nonce_REQ, and Nonce_AACPub should be respectively equal to corresponding fields in AACVeri. To-be-signed data of Sig_{AS_AAC} includes other fields before Sig_{AS_AAC} in AS-AACVeri.

[0230] In S712, AS-REQ performs, upon receiving AS-AACVeri, the following operations:

• • [0231] (1) using a public key of AS-AAC to verify Sig_{AS_AAC}, and if verification is not successful, discarding AS-AACVeri; and
  • [0232] (2) calculating a digital signature Sig_{AS_REQ} of AS-REQ.

[0233] In S713, AS-REQ sends a second authentication response message AS-REQVeri to AS-AAC.

[0234] The AS-REQVeri includes ID_REQ, Nonce_REQ, Pub_AAC^⊕Nonce_AACPub, and Sig_{AS_REQ}. ID_REQ, Nonce_REQ, and Pub_AAC^⊕Nonce_{AAC_Pub} should be respectively equal to corresponding fields in AS-AACVeri. To-be-signed data of Sig_{AS_REQ} includes ID_REQ, Nonce_REQ, and Pub_AAC^⊕Nonce_AACPub.

[0235] In S714, AS-AAC sends, upon receiving AS-REQVeri, a first authentication response message ASVeri to the AAC.

[0236] The ASVeri includes ID_REQ, Nonce_REQ, Pub_AAC^⊕Nonce_AACPub, and Sig_{AS_REQ}. Nonce_REQ, Pub_AAC^⊕Nonce_AACPub, and Sig_{AS_REQ} should be respectively equal to corresponding fields in AS-REQVeri.

[0237] In S715, the AAC performs, upon receiving ASVeri, the following operations:

• • [0238] (1) using the message encryption key and the symmetric encryption algorithm to calculate authentication result information EncData_AAC;
  • [0239] (2) calculating a digital signature Sig_AAC of the AAC; and
  • [0240] (3) calculating MacTag_AAC as desired.

[0241] S716, the AAC sends an authentication result message AACAuth to the REQ.

[0242] The AACAuth includes EncData_AAC, Sig_AAC, and MacTag_AAC. To-be-encrypted data of EncData_AAC includes ID_REQ, Nonce_REQ, Pub_AAC^⊕Nonce_AACPub, Sig_{AS_REQ}, and Nonce_AACPub. ID_REQ, Nonce_REQ, Pub_AAC^⊕Nonce_AACPub, and Sig_{AS_REQ} should be respectively equal to corresponding fields in ASVeri. To-be-signed data of Sig_AAC includes other fields before Sig_AAC in AACAuth. MacTag_AAC is an optional field. A calculation process of MacTag_AAC is as described above.

[0243] In S717, the REQ receives the AACAuth, and then performs the following operations including:

• • [0244] (1) if MacTag_AAC is present in AACAuth, verifying MacTag_AAC, wherein a verification process is as described above;
  • [0245] (2) using the message encryption key and the symmetric encryption algorithm to decrypt EncData_AAC to obtain ID_REQ, Nonce_REQ, Pub_ACC^⊕Nonce_AACPub, Sig_{AS_REQ}, and Nonce_AACPub;
  • [0246] (3) checking whether Nonce_REQ and ID_REQ are respectively the same as Nonce_REQ generated by the REQ and the identifier ID REQ of the REQ itself;
  • [0247] (4) performing an XOR operation on Nonce_AACPub and Pub_AAC^⊕Nonce_AACPub to recover Pub_AAC;
  • [0248] (5) using Cert_AAC in Pub_AAC to verify Sig_AAC;
  • [0249] (6) using a public key of AS-REQ to verify Sig_{AS_REQ}; and
  • [0250] (7) after the above checking and verifications are successful, determining an identity authentication result of the AAC according to Res AAC in Pub_AAC, or if any step in the above checking and verifications is not successful, discarding AACAuth immediately.

[0251] Referring to FIG. 8, FIG. 8 is another embodiment of a method of identity authentication in the case of roaming. In the embodiment, a message encryption key negotiation process between a REQ and an AAC is fused into an identity authentication process, thereby facilitating project implementation. A digital signature Sig_AAC of an AAC is verified by AS-AAC. The method includes the following operations.

[0252] In S801, an AAC generates Nonce_AAC and KeyInfo_AAC, and generates Security capabilities_AAC as needed.

[0253] In S802, the AAC sends a key request message AACInit to a REQ.

[0254] The AACInit includes Nonce_AAC, KeyInfo_AAC, Security capabilities_AAC, and ID_{AS_AAC}. Security capabilities_AAC and ID_{AS_AAC} are optional fields.

[0255] In S803, the REQ generates Nonce_REQ and KeyInfo_REQ, generates ID_{AS_REQ} and Security capabilities_REQ as desired, performs key exchange calculation according to a temporary private key corresponding to KeyInfo_REQ and a temporary public key included in KeyInfo_AAC to generate a first key K1, calculates a message encryption key and a message integrity check key according to K1 in combination with Nonce_AAC, Nonce_REQ, and other information (other information used by the REQ and the AAC is the same, and is optional, such as a particular string, etc.) and by using a negotiated or preset key derivation algorithm, and uses the message encryption key and a symmetric encryption algorithm to calculate an identifier ciphertext EncData_REQ of the REQ.

[0256] In S804, the REQ sends a key response message REQInit to the AAC.

[0257] The REQInit includes Nonce_AAC, Nonce_REQ, Security capabilities_REQ, KeyInfo_REQ, EncData_REQ, and ID_{AS_REQ}. To-be-encrypted data of EncData_REQ includes ID_REQ. Nonce_AAC should be equal to a corresponding field in AACInit. Security capabilities_REQ and ID_{AS_REQ} are optional fields.

[0258] In S805, the AAC performs, upon receiving REQInit, the following operations:

• • [0259] (1) checking whether Nonce_AAC in REQInit is the same as Nonce_AAC generated by the AAC, and if they are different, discarding REQInit;
  • [0260] (2) performing key exchange calculation according to a temporary private key corresponding to KeyInfo_AAC and a temporary public key included in KeyInfo_REQ to generate a first key K1, and calculating a message encryption key and a message integrity check key according to K1 in combination with Nonce_AAC, Nonce_REQ, and other information (other information used by the AAC and the REQ is the same, and is optional, such as a particular string, etc.) and by using a negotiated or preset key derivation algorithm;
  • [0261] (3) using the message encryption key and the symmetric encryption algorithm to decrypt EncData_REQ to obtain ID_REQ;
  • [0262] (4) generating a protection nonce Nonce_AACPub;
  • [0263] (5) using a public key of an encryption certificate to calculate an identity information ciphertext EncPub_AS;
  • [0264] (6) calculating a digital signature Sig_AAC of the AAC;
  • [0265] (7) a method used by the AAC to determine AS-AAC being the same as that in Embodiment 7.

[0266] In S806, the AAC sends a first authentication request message AACVeri to AS-AAC.

[0267] The AACVeri includes ID_REQ, Nonce_REQ, ID_{AS_REQ}, EncPub_AS, and Sig_AAC. ID_{AS_REQ} is an optional field, and ID_REQ, Nonce_REQ, and ID_{AS_REQ} should be respectively equal to corresponding fields in REQInit. To-be-encrypted data of EncPub_AS includes Cert_AAC and Nonce_AACPub. To-be-signed data of Sig_AAC includes other fields before Sig_AAC in AACVeri.

[0268] In S807, AS-AAC sends, upon receiving the AACVeri, a decryption request message AS-AACReq to a certificate sever-decrypt (CS-DEC).

[0269] The AS-AACReq includes EncPub_AS. The EncPub_AS should be equal to a corresponding field in AACVeri.

[0270] In S808, the CS-DEC uses, upon receiving the AS-AACReq, a private key corresponding to the encryption certificate to decrypt EncPub_AS to obtain Cert_AAC and Nonce_AACPub.

[0271] In S809, the CS-DEC sends a decryption response message CS-DECRep to AS-AAC.

[0272] The CS-DECReq includes Cert_AAC and Nonce_AACPub obtained by means of decryption.

[0273] In S810, AS-AAC performs, upon receiving the CS-DECRep, the following operations:

• • [0274] (1) using Cert_AAC to verify Sig_AAC, and if verification is not successful, discarding CS-DECRep;
  • [0275] (2) verifying legality of Cert_AAC to obtain Res_AAC, and generating Pub_AAC according to information including Res_AAC;
  • [0276] (3) performing an XOR operation on Pub_AAC and Nonce_AACPub to generate Pub_AAC^⊕Nonce_AACPub;
  • [0277] (4) a method used by AS-AAC to determine a second authentication server AS-REQ being the same as that in embodiment 7; and
  • [0278] (5) calculating a digital signature Sig_{AS_AAC} of AS-AAC.

[0279] In S811, AS-AAC sends a second authentication request message AS-AACVeri to AS-REQ.

[0280] The AS-AACVeri includes ID_REQ, Nonce_REQ, Pub_AAC^⊕Nonce_AACPub and Sig_{AS_AAC}. ID_REQ, Nonce_REQ, and Nonce_AACPub should be respectively equal to corresponding fields in AACVeri. To-be-signed data of Sig_{AS_AAC} includes other fields before Sig_{AS_AAC} in AS-AACVeri.

[0281] In S812, AS-REQ performs, upon receiving AS-AACVeri, the following operations:

• • [0282] (1) using a public key of AS-AAC to verify Sig_{AS_AAC}, and if verification is not successful, discarding AS-AACVeri; and
  • [0283] (2) calculating a digital signature Sig_{AS_REQ} of AS-REQ.

[0284] In S813, AS-REQ sends a second authentication response message AS-REQVeri to AS-AAC.

[0285] The AS-REQVeri includes ID_REQ, Nonce_REQ, Pub_AAC^⊕Nonce_AACPub, and Sig_{AS_REQ}. ID_REQ, Nonce_REQ, and Pub_AAC⊕Nonce_AACPub should be respectively equal to corresponding fields in AS-AACVeri. To-be-signed data of Sig_{AS_REQ} includes ID_REQ, Nonce_REQ, and Pub_AAC^⊕Nonce_AACPub.

[0286] In S814, AS-AAC sends, upon receiving AS-REQVeri, a first authentication response message ASVeri to the AAC.

[0287] The ASVeri includes ID_REQ, Nonce_REQ, Pub_AAC^⊕Nonce_AACPub, and Sig_{AS_REQ}, ID_REQ, Nonce_REQ, Pub_AAC^⊕Nonce_AACPub, and Sig_{AS_REQ} should be respectively equal to corresponding fields in AS-REQVeri.

[0288] In S815, the AAC performs, upon receiving ASVeri, the following operations:

• • [0289] (1) using the message encryption key and the symmetric encryption algorithm to calculate authentication result information EncData_AAC; and
  • [0290] (2) calculating MacTag_AAC.

[0291] In S816, the AAC sends an authentication result message AACAuth to the REQ.

[0292] The AACAuth includes EncData_AAC and MacTag_AAC. To-be-encrypted data of EncData_AAC includes ID_REQ, Nonce_REQ, Pub_AAC^⊕Nonce_AACPub, Sig_{AS_REQ}, and Nonce_AACPub, and ID_REQ, Nonce_REQ, Pub_AAC^⊕Nonce_AACPub, and Sig_{AS_REQ} should be respectively equal to corresponding fields in ASVeri. A calculation process of MacTag_AAC is as described above.

[0293] In S817, the REQ receives the AACAuth, and then performs the following operations, including:

• • [0294] (1) verifying, MacTag_AAC, a verification process being as described above;
  • [0295] (2) using the message encryption key and the symmetric encryption algorithm to decrypt EncData_AAC to obtain ID_REQ, Nonce_REQ, Pub_AAC⊕Nonce_AACPub, Sig_{AS_REQ}, and Nonce_AACPub;
  • [0296] (3) checking whether Nonce_REQ and ID_REQ are respectively the same as Nonce_REQ generated by the REQ and the identifier ID_REQ of the REQ itself;
  • [0297] (4) using a public key of AS-REQ to verify Sig_{AS_REQ}; and
  • [0298] (5) after the above checking and verifications are successful, performing an XOR

[0299] operation on Nonce_AACPub and Pub_AAC^⊕Nonce_AACPub, to recover Pub_AAC, and determining an identity authentication result of the AAC according to Res_AAC in Pub_AAC; if any step in the above checking and verifications is not successful, discarding AACAuth immediately.

[0300] In each of the above embodiments, each message may also carry a hash value HASH_{X_Y}. The hash value HASH_{X_Y} is obtained by sender entity X of sending the message using a hash algorithm to perform a calculation on a latest preceding message received from peer entity Y, and is used by peer entity Y to verify whether entity X has received the complete latest preceding message. HASH_{REQ_AAC} represents a hash value calculated by the REQ for a received latest preceding message sent by the AAC. HASH_{AAC_REQ} represents a hash value calculated by the AAC for a received latest preceding message sent by the REQ. HASH_{AAC_AS-AAC} represents a hash value calculated by the AAC for a received latest preceding message sent by AS-AAC. HASH_{AS-AAC_AAC} represents a hash value calculated by AS-AAC for a received latest preceding message sent by the AAC. HASH_{AS-AAC_AS-REQ} represents a hash value calculated by AS-AAC for a received latest preceding message sent by AS-REQ. HASH_{AS-REQ_AS-AAC} represents a hash value calculated by AS-REQ for a received latest preceding message sent by AS-AAC. If a message currently sent by sender entity X is a first message interacting between entity X and entity Y, it means that entity X has not received a preceding message sent by peer entity Y, then the HASH_{X_Y} in the message may not exist or is meaningless.

[0301] Correspondingly, after peer entity Y receives a message sent by entity X, if HASH_{X_Y} is included in the message, when entity Y has not sent a preceding message(s) to entity X, entity Y will ignore the HASH_{X_Y}; and when entity Y has sent the preceding message(s) to entity X, entity Y will locally calculate a harsh value of the latest preceding message previously sent to entity X by using a hash algorithm, and compare the hash value with the HASH_{X_Y} carried in the received message. If they are consistent, subsequent steps will be performed, otherwise the message will be discarded or the authentication process terminated.

[0302] In the present invention, for entity X, the preceding message(s) sent by peer entity Y to entity X refers to a message(s) sent by peer entity Y to entity X and received before entity X sends message M to peer entity Y. The latest preceding message sent by peer entity Y to entity X refers to a latest message sent by peer entity Y to entity X and received before entity X sends message M to peer entity Y. If the message M sent by entity X to its peer entity Y is a first message for interaction between entity X and entity Y, there is no preceding message sent by peer entity Y to entity X before entity X sends the message M to its peer entity Y.

[0303] It should be noted that the optional fields and optional operations in the corresponding embodiments of FIGS. 5, 6, 7 and 8 described above are denoted by “*” in FIGS. 5, 6, 7 and 8 of the drawings. The order of the contents included in the messages involved in all the above embodiments is not limited, and unless otherwise specified, there is no limitation on the order in which a message receiver operates on related messages and processes the contents included in the messages after receiving the messages.

[0304] On the basis of the method embodiments corresponding to FIGS. 1-8, referring to FIG. 9, provided in an embodiment of the present application is a requester REQ, including: a first acquisition portion 901, a decryption portion 902, a first verifying portion 903, and a first determination portion 904.

[0305] The first acquisition portion 901 is configured to acquire an authentication result message sent by the authentication access controller, the authentication result message comprising authentication result information that is obtained by the authentication access controller by using a message encryption key to encrypt to-be-encrypted data comprising an identity authentication result information ciphertext, a digital signature of a second authentication server trusted by the requester, and a protection nonce.

[0306] The identity authentication result information ciphertext is generated by a first authentication server trusted by the authentication access controller by using the protection nonce to encrypt information comprising identity authentication result information of the authentication access controller, and the identity authentication result information comprises a verification result of a digital certificate of the authentication access controller.

[0307] The decryption portion 902 is configured to use the message encryption key to decrypt the authentication result information to obtain the protection nonce, the identity authentication result information ciphertext, and the digital signature of the second authentication server.

[0308] The first verification portion 903 is configured to use a public key of the second authentication server to verify the digital signature of the second authentication server.

[0309] The decryption portion 902 is further configured to use the protection nonce to decrypt the identity authentication result information ciphertext to obtain the identity authentication result information of the authentication access controller when verification for the digital signature of the second authentication server is successful.

[0310] The first determination portion 904 is configured to determine an identity authentication result of the authentication access controller according to the verification result of the digital certificate in the identity authentication result information.

[0311] Optionally, the requester further comprises:

• • [0312] a second acquisition portion, configured to acquire a key request message sent by the authentication access controller, the key request message comprising a key exchange parameter of the authentication access controller;
  • [0313] a calculation portion, configured to perform key exchange calculation according to a temporary private key corresponding to a key exchange parameter of the requester and a temporary public key comprised in the key exchange parameter of the authentication access controller to generate a first key, and calculate, according to information comprising the first key, the message encryption key by using a key derivation algorithm; and
  • [0314] a sending portion, configured to send a key response message to the authentication access controller, the key response message comprising the key exchange parameter of the requester.

[0315] Optionally, the key request message obtained by the second acquisition portion further comprises a first nonce generated by the authentication access controller, and the key response message sent by the sending portion further comprises a second nonce generated by the requester.

[0316] The calculation portion is further configured to calculate the message encryption key according to information comprising the first key, the first nonce, and the second nonce.

[0317] Optionally, the key response message sent by the sending portion further includes the first nonce.

[0318] Optionally, when the key response message sent by the sending portion further includes the second nonce, the to-be-encrypted data of the authentication result information in the authentication result message further includes the second nonce. The decryption portion 902 is further configured to decrypt the authentication result information to obtain the second nonce, and the first verification portion 903 is further configured to verify consistency between the second nonce obtained by the decryption portion 902 by means of decryption and the second nonce generated by the requester.

[0319] Optionally, the requester further comprises:

[0320] an encryption portion, configured to use the message encryption key to perform calculation on information including an identifier of the requester to obtain an identifier ciphertext. Correspondingly, the key response message sent by the sending portion further includes the identifier ciphertext.

[0321] Optionally, when the key response message sent by the sending portion further includes the identifier ciphertext, the to-be-encrypted data of the authentication result information in the authentication result message further includes the identifier of the requester. The decryption portion 902 is further configured to decrypt the authentication result information to obtain the identifier of the requester, and the first verification portion 903 is further configured to verify consistency between the identifier of the requester obtained by the decryption portion 902 by means of decryption and the identifier of the requester itself.

[0322] Optionally, the key request message acquired by the second acquisition portion further includes security capability parameter information supported by the authentication access controller, and the requester further includes:

[0323] a second determination portion, configured to determine, according to the security capability parameter information, a particular security policy used by the requester.

[0324] Correspondingly, the key response message sent by the sending portion further includes the particular security policy.

[0325] Optionally, the authentication result message acquired by the first acquisition portion 901 further includes a message integrity check code calculated by the authentication access controller, and the requester further includes:

[0326] a second verification portion, configured to use a message integrity check key to verify the message integrity check code, wherein the message integrity check key and the message encryption key are generated in the same manner.

[0327] Optionally, the key request message acquired by the second acquisition portion further comprises an identifier of at least one authentication server trusted by the authentication access controller, and the requester further comprises:

[0328] a third determination portion, configured to determine, according to the identifier of the at least one authentication server trusted by the authentication access controller, an identifier of at least one authentication server trusted by the requester.

[0329] The key response message sent by the sending portion further includes the identifier of the at least one authentication server trusted by the requester.

[0330] Optionally, the key response message sent by the sending portion further includes the identifier of the at least one authentication server trusted by the requester.

[0331] Optionally, the first determination portion 904 is further configured to determine, before determining the identity authentication result of the authentication access controller, whether verification for a digital signature of the authentication access controller is successful, and responsive to determining that the verification for the digital signature of the authentication access controller is successful, further determine the identity authentication result of the authentication access controller according to the verification result of the digital certificate in the identity authentication result information.

[0332] Optionally, the first determination portion 904 is further configured to:

• • [0333] when a first authentication request message sent by the authentication access controller to the first authentication server comprises the digital signature of the authentication access controller, the first authentication server uses a digital certificate of the authentication access controller obtained by decrypting the identity information ciphertext in the first authentication request message to verify the digital signature of the authentication access controller, and responsive to that the first acquisition portion 901 receives the authentication result message, the first determination portion 904 is configured to determine that verification for the digital signature of the authentication access controller is successful; or
  • [0334] when the authentication result message acquired by the first acquisition portion 901 further comprises the digital signature of the authentication access controller, and correspondingly, the identity authentication result information further comprise the digital certificate of the authentication access controller, the first determination portion 904 is further configured to use the digital certificate of the authentication access controller in the identity authentication result information to verify the digital signature of the authentication access controller, and determine, according to the verification result, whether verification for the digital signature of the authentication access controller is successful.

[0335] Optionally, the message sent by the requester to the authentication access controller further include a hash value calculated by the requester for a received latest preceding message sent by the authentication access controller.

[0336] On the basis of the method embodiments corresponding to FIGS. 1-8, referring to FIG. 10, provided in an embodiment of the present application is an authentication access controller AAC, including: a first acquisition portion 1001 and a first sending portion 1002.

[0337] The first acquisition portion 1001 is configured to acquire a first authentication response message sent by a first authentication server trusted by the authentication access controller, the first authentication response message comprising an identity authentication result information ciphertext and a digital signature of a second authentication server trusted by a requester. The identity authentication result information ciphertext is generated by the first authentication server by using a protection nonce to encrypt information comprising identity authentication result information of the authentication access controller, and the identity authentication result information includes a verification result of a digital certificate of the authentication access controller.

[0338] The first sending portion 1002 is configured to send an authentication result message to the requester, the authentication result message comprising authentication result information that is obtained by the authentication access controller by using a message encryption key to encrypt to-be-encrypted data comprising the identity authentication result information ciphertext, the digital signature of the second authentication server, and the protection nonce.

[0339] Optionally, the authentication access controller further comprises:

[0340] a second sending portion, configured to send a first authentication request message to the first authentication server, the first authentication request message comprising an identity information ciphertext that is obtained by the authentication access controller by using a public key of an encryption certificate to encrypt information comprising the digital certificate of the authentication access controller and the protection nonce.

[0341] Optionally, the authentication access controller further comprises:

• • [0342] a third sending portion, configured to send a key request message to the requester, the key request message comprising a key exchange parameter of the authentication access controller;
  • [0343] a second acquisition portion, configured to acquire a key response message sent by the requester, the key response message comprising a key exchange parameter of the requester; and
  • [0344] a calculation portion, configured to perform key exchange calculation according to a temporary private key corresponding to the key exchange parameter of the authentication access controller and a temporary public key comprised in the key exchange parameter of the requester to generate a first key, and calculate, according to information comprising the first key, the message encryption key by using a key derivation algorithm.

[0345] Optionally, the key request message sent by the third sending portion further comprises a first nonce generated by the authentication access controller, and the key response message acquired by the second acquisition portion further comprises a second nonce generated by the requester.

[0346] The calculation portion is further configured to calculate the message encryption key according to information comprising the first key, the first nonce, and the second nonce.

[0347] Optionally, the key response message acquired by the second acquisition portion further comprises the first nonce, and the authentication access controller further comprises:

[0348] a verification portion, configured to verity consistency between the first nonce in the key response message and the first nonce generated by the authentication access controller.

[0349] Optionally, the key response message acquired by the second acquisition portion further comprises an identifier ciphertext generated by the requester, and the authentication access controller further comprises: a decryption portion, configured to use the message encryption key to decrypt the identifier ciphertext to obtain an identifier of the requester.

[0350] Optionally, the key request message sent by the third sending portion further comprises security capability parameter information supported by the authentication access controller, and the key response message acquired by the second acquisition portion further comprises a particular security policy used by the requester and determined by the requester according to the security capability parameter information.

[0351] Optionally, the authentication result message sent by the first sending portion 1002 further comprises a message integrity check code that is generated by the authentication access controller by using a message integrity check key to perform calculation on fields, other than the message integrity check code, in the authentication result message. The message integrity check key of the authentication access controller and the message encryption key are generated in the same manner.

[0352] Optionally, the key request message sent by the third sending portion further comprises an identifier of at least one authentication server trusted by the authentication access controller, and the key response message acquired by the second acquisition portion further comprises an identifier of at least one authentication server trusted by the requester. The authentication access controller further comprises:

[0353] a first determination portion, configured to determine, according to the identifier of the at least one authentication server trusted by the requester and the identifier of the at least one authentication server trusted by the authentication access controller in the key request message, the first authentication server participating in an identity authentication process.

[0354] Optionally, the key response message acquired by the second acquisition portion further includes an identifier of at least one authentication server trusted by the requester, and the authentication access controller further includes:

[0355] a second determination portion, configured to determine, according to the identifier of the at least one authentication server trusted by the requester and an identifier of an authentication server trusted by the authentication access controller, the first authentication server participating in an identity authentication process.

[0356] Optionally, a message seat by the authentication access controller to the requester further include a hash value calculated by the authentication access controller for a received latest preceding message sent by the requester, and a message sent by the authentication access controller to the first authentication server further comprises a hash value calculated by the authentication access controller for a received latest preceding message sent by the first authentication serer.

[0357] On the basis of the method embodiments corresponding to FIGS. 1-8, referring to FIG. 11, further provided in an embodiment of the present application is a first authentication server AS-AAC. The first authentication server is an authentication server trusted by the authentication access controller shown in FIG. 10, and includes: a first acquisition portion 1101, a decryption portion 1102, a first verification portion 1103, and a generation portion 1104.

[0358] The first acquisition portion 1101 is configured to acquire a first authentication request message sent by the authentication access controller, the first authentication request message comprising an identity information ciphertext that is obtained by the authentication access controller by using a public key of an encryption certificate to encrypt information comprising the digital certificate of the authentication access controller and the protection nonce.

[0359] The decryption portion 1102 is configured to use a private key corresponding to the encryption certificate to decrypt the identity information ciphertext to obtain the digital certificate and the protection nonce.

[0360] The first verification portion 1103 is configured to perform legality verification on the digital certificate to obtain a verification result of the digital certificate of the authentication access controller.

[0361] The generation portion 1104 is configured to generate identity authentication result information of the authentication access controller according to information comprising the verification result; and further configured to use the protection nonce to encrypt information comprising the identity authentication result information to generate the identity authentication result information ciphertext, and perform calculation on to-be-signed data comprising the identity authentication result information ciphertext to generate a digital signature of the first authentication server.

[0362] Optionally, when a second authentication server trusted by the requester and the first authentication server trusted by the authentication access controller are the same authentication server, the first authentication server further comprises:

[0363] a first sending portion, configured to send to the authentication access controller a first authentication response message comprising the identity authentication result information ciphertext and the digital signature of the first authentication server.

[0364] Optionally, when a second authentication server trusted by the requester and the first authentication server trusted by the authentication access controller are two different authentication servers, the first authentication server further comprises:

• • [0365] a second sending portion, configured to send a second authentication request message to the second authentication server, the second authentication request message comprising the identity authentication result information ciphertext and the digital signature of the first authentication server, wherein the second authentication server uses a public key of the first authentication server to verify the digital signature of the first authentication server, and after verification is successful, the second authentication server performs calculation on to-be-signed data comprising the identity authentication result information ciphertext to generate a digital signature of the second authentication server;
  • [0366] a second acquisition portion, configured to acquire a second authentication response message sent by the second authentication server, the second authentication response message comprising the identity authentication result information ciphertext and the digital signature of the second authentication server; and
  • [0367] a third sending portion, configured to send to the authentication access controller a first authentication response message comprising the identity authentication result information ciphertext and the digital signature of the second authentication server.

[0368] Optionally, the first authentication request message acquired by the first acquisition portion 1101 further comprises a digital signature of the authentication access controller, and the first authentication server further comprises:

[0369] a second verification portion, configured to use the digital certificate obtained by the decryption portion 1102 to verify the digital signature of the authentication access controller.

[0370] Optionally, a message sent by the first authentication server to the authentication access controller further comprises a hash value calculated by the first authentication server for a received latest preceding message sent by the authentication access controller, and a message sent by the first authentication server to the second authentication server farther comprises a hash value calculated by the first authentication server for a received latest preceding message sent by the second authentication server.

[0371] It should be noted that in the embodiments of the present application and other embodiments, the “portion” may be part of a circuit(s), part of a processor(s), part of a program(s) or software, or the like, or may also be a unit, and may be modular or non-modular.

[0372] Referring to FIG. 12, further provided in an embodiment of the present application is a requester REQ, including: a first processor 1110 and a first memory 1120. The first processor 1110 can invoke and execute a computer program from the first memory 1120 to implement the steps performed by the REQ in the above embodiments.

[0373] The first memory 1120 may be a separate device independent of the first processor 1110, or may be integrated in the first processor 1110.

[0374] It should be understood that the requester may implement the respective processes implemented by the REQ in various methods of the embodiments of the present application, which are not described herein again for brevity.

[0375] Referring to FIG. 13, further provided in an embodiment of the present application is an authentication access controller AAC, including: a second processor 1210 and a second memory 1220. The second processor 1210 can invoke and execute a computer program from the second memory 1220 to implement the steps performed by the AAC in the above embodiments.

[0376] The second memory 1220 may be a separate device independent of the second processor 1210, or may be integrated in the second processor 1210.

[0377] It should be understood that the authentication access controller may implement the respective processes implemented by the AAC in various methods of the embodiments of the present application, which are not described herein again for brevity.

[0378] Referring to FIG. 14, further provided in an embodiment of the present application is a first authentication server AS-AAC, including: a third processor 1310 and a third memory 1320. The third processor 1310 can invoke and execute a computer program from the third memory 1320 to implement the steps performed by AS-AAC in the above embodiments.

[0379] The third memory 1320 may be a separate device independent of the third processor 1310, or may be integrated in the third processor 1310.

[0380] It should be understood that the first authentication server may implement the respective processes implemented by the AS-AAC in various methods of the embodiments of the present application, which are not described herein again for brevity.

[0381] A computer-readable storage medium is further provided in an embodiment of the present application. The computer-readable storage medium stores thereon a computer program that, when run by a processor, performs the steps performed by the authentication access controller AAC, the requester REQ, or the first authentication server AS-AAC in the method of identity authentication described above. The storage medium may be a volatile or non-volatile computer-readable storage medium.

[0382] It should be noted that the storage medium may be at least one of a read-only memory (ROM), a RAM, a magnetic or optical disk, and other media that may store program codes.

[0383] Further provided in an embodiment of the present application is a computer program, including computer-readable codes. When the computer-readable codes are ran in an electronic device, a processor in the electronic device performs steps performed by the authentication access controller AAC, the requester REQ, or the first authentication server AS-AAC in the above method of identity authentication.

[0384] A computer program product is further provided in an embodiment of the present application. The computer program product comprises computer program instructions, which may be used to perform the steps performed by the authentication access controller AAC, the requester REQ, or the first authentication server AS-AAC in the method of identity authentication described above. Reference may be made to the above-mentioned method embodiments for details, which are not described herein again.

[0385] It should be noted that various embodiments in the description are described in a progressive manner, the same and similar parts of each embodiment may be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for device and system embodiments, since they are consistent and corresponding to the method embodiments, they are relatively simply described, and reference may be made to part of the description of the method embodiments for related parts. The device and system embodiments described above are only illustrative, wherein the parts described as separate components may or may not be physically separated, and the components displayed as parts may or may not be physical parts, that is, they may be located in one place, or may be distributed to a plurality of network parts. A part or all of the modules may be selected according to actual needs to achieve the objective of the solutions of the present embodiments. A person of ordinary skill in the art may understand and implement the solutions without any creative effort.

[0386] The detailed descriptions of the present application are merely described above, but the scope of protection of the present application is not limited thereto. Any person skilled in the art can easily conceive of changes or substitutions within the technical scope disclosed in the present application, and all of the changes or substitutions should be covered by the scope of protection of the present application. Therefore, the scope of protection of the present application should be defined by the scope of protection of the claims.

[0387] In the method of identity authentication provided in the embodiments of the present application, during identity authentication performed for an authentication access controller by a requester, confidentiality processing can be performed on identity information carrying, private or sensitive information and identity authentication result information, so that even if an attacker intercepts an exchanged message during transmission, the attacker cannot acquire the private or sensitive information therein, thereby preventing the attacker from focusing on attacking a legal authentication access controller, and ensuring the security of an authentication access controller, a requester, and even a network.