An identity authentication method and device

By establishing two-way identity authentication between the access controller and the requesting device, and utilizing a combination of pre-shared keys and digital certificates for verification, the problem of inconsistent identity authentication in existing technologies is solved, thus achieving reliability and security of two-way identity authentication.

CN114760028BActive Publication Date: 2026-11-10CHINA IWNCOMM
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202011569181.1
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-12-26
Publication Date
2026-11-10
Estimated Expiration
2040-12-26

AI Technical Summary

Technical Problem

In existing technologies, when an entity identity authentication scheme uses a digital certificate on one end and a pre-shared key on the other end, there is a lack of a simple and effective identity authentication mechanism.

Method used

By using the pre-shared key of the trusted first authentication server to generate an identity authentication code through the authentication access controller, and verifying the digital certificate of the requesting device by the second authentication server trusted by the requesting device, two-way identity authentication is achieved.

Benefits of technology

This ensures that only legitimate users can communicate with legitimate networks, thus achieving the reliability and security of two-way identity authentication.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114760028B_ABST
    Figure CN114760028B_ABST
Patent Text Reader

Abstract

This application discloses an identity authentication method, comprising: an authentication access controller (AAC) receiving an identity message including a REQ digital certificate sent by a requesting device (REQ), and sending a first authentication request message carrying the REQ digital certificate and an AAC authentication code to a first authentication server trusted by the AAC; the first authentication server verifying the AAC authentication code to obtain a first verification result; a second authentication server trusted by the REQ verifying the legality of the REQ digital certificate to obtain a second verification result; the AAC receiving a first authentication response message carrying the first and second verification results sent by the first authentication server; the AAC obtaining the REQ's identity authentication result based on the message; and sending a third authentication response message including the first verification result to the REQ; and the REQ obtaining the AAC's identity authentication result based on the message, thereby achieving two-way identity authentication.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of network communication security technology, and in particular to an identity authentication method and apparatus. Background Technology

[0002] Currently, communication networks typically require two-way authentication between users and network access points to ensure that legitimate users access legitimate networks. In existing entity authentication schemes, entity credentials either uniformly take the form of digital certificates or pre-shared keys. However, in practical applications, situations often arise where one end uses digital certificates as authentication credentials while the other uses pre-shared keys, posing a challenge to entity authentication mechanisms. Summary of the Invention

[0003] To address the aforementioned technical issues, this application provides an identity authentication method and apparatus that enables two-way entity identity authentication when the requesting device uses a digital certificate and the authentication access controller uses a pre-shared key as identity credentials.

[0004] In view of this, the first aspect of this application provides an identity authentication method, comprising:

[0005] The authentication access controller receives an identity message sent by the requesting device, the identity message including the digital certificate of the requesting device;

[0006] The authentication access controller sends a first authentication request message to a first authentication server it trusts. The first authentication request message includes the digital certificate of the requesting device and the authentication code of the authentication access controller. The authentication code of the authentication access controller is generated by the authentication access controller using a pre-shared key with the first authentication server and a cryptographic algorithm agreed upon with the first authentication server to calculate information including the digital certificate of the requesting device.

[0007] The authentication access controller receives a first authentication response message sent by the first authentication server. The first authentication response message includes first authentication result information, a first digital signature of the second authentication server trusted by the requesting device, second authentication result information, and a first message authentication code of the first authentication server. The first authentication result information includes a first verification result of the authentication access controller's identity authentication code. The first digital signature is a digital signature calculated by the second authentication server on signature data including the first authentication result information. The second authentication result information includes a second verification result of the requesting device's digital certificate. The first message authentication code of the first authentication server is calculated by the first authentication server using a pre-shared key with the authentication access controller and a cryptographic algorithm agreed upon with the authentication access controller on information including the second authentication result information.

[0008] The authentication access controller uses a pre-shared key with the first authentication server and a cryptographic algorithm agreed upon with the first authentication server to verify the first message authentication code of the first authentication server. If the verification is successful, the authentication access controller determines the authentication result of the requesting device based on the second verification result in the second authentication result information. When the authentication access controller determines that the authentication result of the requesting device is valid, it sends a third authentication response message to the requesting device; or...

[0009] The authentication access controller uses a pre-shared key with the first authentication server and a cryptographic algorithm agreed upon with the first authentication server to verify the first message authentication code of the first authentication server. If the verification is successful, the authentication access controller sends a third authentication response message to the requesting device and determines the authentication result of the requesting device based on the second verification result in the second authentication result information; or...

[0010] The authentication access controller uses a pre-shared key with the first authentication server and employs a cryptographic algorithm agreed upon with the first authentication server to verify the first message authentication code of the first authentication server; if the first message authentication code of the first authentication server is verified successfully, the authentication access controller determines the identity authentication result of the requesting device based on the second verification result in the second authentication result information; the authentication access controller sends a third authentication response message to the requesting device.

[0011] The third authentication response message includes the first authentication result information and the first digital signature;

[0012] After receiving the third authentication response message, the requesting device uses the public key of the second authentication server to verify the first digital signature. If the verification is successful, the authentication result of the authentication access controller is determined according to the first verification result in the first authentication result information.

[0013] A second aspect of this application provides a requesting device, comprising:

[0014] The sending module is used to send an identity message to the authentication access controller, the identity message including the digital certificate of the requesting device;

[0015] The receiving module is configured to receive a third authentication response message sent by the authentication access controller, the third authentication response message including first authentication result information and a first digital signature; the first authentication result information includes a first verification result of the authentication access controller, and the first digital signature is a digital signature calculated by the second authentication server trusted by the requesting device on signature data including the first authentication result information;

[0016] The verification module is used to verify the first digital signature using the public key of the second authentication server;

[0017] The determination module is used to determine the identity authentication result of the authentication access controller based on the first verification result in the first authentication result information if the verification is successful.

[0018] A third aspect of this application provides an authentication access controller, comprising:

[0019] The receiving module is used to receive an identity message sent by the requesting device, wherein the identity message includes the digital certificate of the requesting device;

[0020] The generation module is used to calculate and generate the identity verification code of the authentication access controller by using a pre-shared key of a first authentication server trusted by the authentication access controller and employing a cryptographic algorithm agreed upon with the first authentication server, including the digital certificate of the requesting device.

[0021] The sending module is used to send a first authentication request message to the first authentication server, wherein the first authentication request message includes the digital certificate of the requesting device and the identity authentication code of the authentication access controller;

[0022] The receiving module is further configured to receive a first authentication response message sent by the first authentication server. The first authentication response message includes first authentication result information, a first digital signature of the second authentication server trusted by the requesting device, second authentication result information, and a first message authentication code of the first authentication server. The first authentication result information includes a first verification result of the identity authentication code of the authentication access controller. The first digital signature is a digital signature calculated and generated by the second authentication server on signature data including the first authentication result information. The second authentication result information includes a second verification result of the digital certificate of the requesting device. The first message authentication code of the first authentication server is calculated and generated by the first authentication server using a pre-shared key with the authentication access controller and a cryptographic algorithm agreed upon with the authentication access controller on information including the second authentication result information.

[0023] The verification module is used to verify the first message authentication code of the first authentication server using a pre-shared key with the first authentication server and a cryptographic algorithm agreed upon with the first authentication server; if the verification is successful, the determining module determines the identity authentication result of the requesting device based on the second verification result in the second authentication result information; when the determining module determines that the identity authentication result of the requesting device is valid, the sending module sends a third authentication response message to the requesting device; or...

[0024] The sending module uses a pre-shared key with the first authentication server and an agreed-upon cryptographic algorithm to verify the first message authentication code of the first authentication server. If the verification is successful, the sending module sends a third authentication response message to the requesting device, and the determining module determines the authentication result of the requesting device based on the second verification result in the second authentication result information; or...

[0025] The module is used to verify the first message authentication code of the first authentication server using a pre-shared key with the first authentication server and a cryptographic algorithm agreed upon with the first authentication server; if the first message authentication code of the first authentication server is verified, the determining module determines the identity authentication result of the requesting device based on the second verification result in the second authentication result information; the sending module sends a third authentication response message to the requesting device.

[0026] The third authentication response message includes the first authentication result information and the first digital signature.

[0027] A fourth aspect of this application provides a first authentication server, comprising:

[0028] The receiving module is configured to receive a first authentication request message sent by the authentication access controller. The first authentication request message includes the digital certificate of the requesting device and the authentication code of the authentication access controller. The authentication code of the authentication access controller is generated by the authentication access controller using a pre-shared key with the first authentication server and employing a cryptographic algorithm agreed upon with the first authentication server to calculate information including the digital certificate of the requesting device.

[0029] The sending module is configured to send a first authentication response message to the authentication access controller. The first authentication response message includes first authentication result information, a first digital signature of the second authentication server trusted by the requesting device, second authentication result information, and a first message authentication code of the first authentication server. The first authentication result information includes a first verification result of the authentication access controller's identity authentication code. The first digital signature is a digital signature calculated by the second authentication server on signature data including the first authentication result information. The second authentication result information includes a second verification result of the requesting device's digital certificate. The first message authentication code of the first authentication server is calculated by the first authentication server using a pre-shared key with the authentication access controller and a cryptographic algorithm agreed upon with the authentication access controller on information including the second authentication result information.

[0030] The fifth aspect of this application provides a second authentication server, comprising:

[0031] The receiving module is configured to receive a second authentication request message sent by a first authentication server. The second authentication request message includes first authentication result information, a digital certificate of the requesting device, and a second digital signature; or the second authentication request message includes first authentication result information, a digital certificate of the requesting device, and a second message authentication code. The first authentication result information is generated by the first authentication server verifying the identity authentication code of the authentication access controller to obtain a first verification result, based on information including the first verification result. The second digital signature is calculated and generated by the first authentication server using signature data including the first authentication result information and the digital certificate of the requesting device, or the second message authentication code is calculated and generated by the first authentication server using a pre-shared key with the second authentication server and an agreed-upon cryptographic algorithm with the second authentication server, based on information including the first authentication result information and the digital certificate of the requesting device.

[0032] The verification module is used to verify the second digital signature using the public key of the first authentication server or to verify the second message authentication code using a pre-shared key with the first authentication server and a cryptographic algorithm agreed upon with the first authentication server. If the verification is successful, the module performs a legality verification on the digital certificate of the requesting device to obtain a second verification result.

[0033] The generation module is used to generate second authentication result information based on information including the second verification result, calculate and generate a first digital signature on signature data including the first authentication result information, calculate and generate a third digital signature on signature data including the second authentication result information, or use a pre-shared key with the first authentication server and a cryptographic algorithm agreed upon with the first authentication server to calculate and generate a third message authentication code on information including the second authentication result information.

[0034] The sending module is used to send a second authentication response message to the first authentication server. The second authentication response message includes the first authentication result information, the first digital signature, the second authentication result information, and the third digital signature, or the second authentication response message includes the first authentication result information, the first digital signature, the second authentication result information, and the third message authentication code.

[0035] As can be seen from the above: In the identity authentication method provided in this application, the requesting device uses a digital certificate as its identity credential, and the authentication access controller uses a pre-shared key as its identity credential. During the identity authentication process, the requesting device first sends an identity message to the authentication access controller, which includes the requesting device's digital certificate. The authentication access controller uses the pre-shared key with a trusted first authentication server and employs a cryptographic algorithm agreed upon with the first authentication server to calculate and generate an authentication code for the authentication access controller, including the requesting device's digital certificate. Then, it sends a first authentication request message to the first authentication server, including the requesting device's digital certificate and the authentication code of the authentication access controller. The second authentication server, trusted by the requesting device, verifies the legitimacy of the requesting device's digital certificate and obtains a verification result. The first authentication server verifies the authentication code of the authentication access controller and obtains a verification result. The first authentication server sends a first authentication response message to the authentication access controller. The authentication access controller obtains the verification result of the requesting device from the first authentication response message to determine whether the requesting device is legitimate. The requesting device obtains the verification result of the authentication access controller from the third authentication response message sent by the authentication access controller to determine whether the authentication access controller is legitimate. This achieves two-way identity authentication between the authentication access controller and the requesting device, laying the foundation for ensuring that only legitimate users can communicate with legitimate networks. Attached Figure Description

[0036] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0037] Figure 1 A schematic diagram illustrating an identity authentication method provided in an embodiment of this application;

[0038] Figure 2 This is a schematic diagram of an identity authentication method provided in an embodiment of this application, where "*" represents an optional field or optional operation;

[0039] Figure 3 This is a schematic diagram of an identity authentication method provided in an embodiment of this application, where "*" represents an optional field or optional operation;

[0040] Figure 4 This is a schematic diagram of an identity authentication method provided in an embodiment of this application, where "*" represents an optional field or optional operation;

[0041] Figure 5 This is a schematic diagram of an identity authentication method provided in an embodiment of this application, where "*" represents an optional field or optional operation;

[0042] Figure 6 A structural block diagram of a request device REQ provided in an embodiment of this application;

[0043] Figure 7 A structural block diagram of an authentication access controller (AAC) provided in this application embodiment;

[0044] Figure 8 A structural block diagram of a first authentication server AS-AAC provided in an embodiment of this application;

[0045] Figure 9 This is a structural block diagram of a second authentication server AS-REQ provided in an embodiment of this application. Detailed Implementation

[0046] In a communication network, a requesting device can access the network through an authentication access controller. To ensure that the requesting device is a legitimate user and that the network accessed by the requesting device is a legitimate network, two-way identity authentication (MIA) is required between the authentication access controller and the requesting device.

[0047] Taking current wireless and mobile communication scenarios as examples, in scenarios where a requesting device accesses a wireless network through an authentication access controller, the requesting device can be a terminal device such as a mobile phone, a personal digital assistant (PDA), or a tablet computer, while the authentication access controller can be a network-side device such as a wireless access point or a wireless router. In scenarios where a requesting device accesses a wired network through an authentication access controller, the requesting device can be a terminal device such as a desktop computer or a laptop computer, while the authentication access controller can be a network-side device such as a switch or a router. In scenarios where a requesting device accesses a 4G / 5G network through an authentication access controller, the requesting device can be a terminal device such as a mobile phone or a tablet computer, while the authentication access controller can be a network-side device such as a base station. Of course, this application is also applicable to various data communication scenarios, including other wired networks and short-range communication networks.

[0048] However, in existing entity authentication schemes, entity identity credentials either uniformly adopt the form of digital certificates or uniformly adopt the form of pre-shared keys. However, no simple and effective identity authentication mechanism has been proposed for the real-world scenario where one end uses digital certificates as identity credentials and the other end uses pre-shared keys as identity credentials.

[0049] To address the aforementioned technical issues, this application provides an identity authentication method. For application scenarios where the requesting device uses a digital certificate and the authentication access controller uses a pre-shared key, a first authentication server trusted by the authentication access controller verifies the identity authentication code generated by the authentication access controller based on the pre-shared key to obtain a first verification result. A second authentication server trusted by the requesting device verifies the legitimacy of the requesting device's digital certificate to obtain a second verification result. Both the requesting device and the authentication access controller determine the legitimacy of the other entity based on its verification result, thus achieving bidirectional identity authentication between the authentication access controller and the requesting device. This lays the foundation for ensuring that only legitimate users can communicate with legitimate networks.

[0050] For ease of explanation, in this embodiment of the application, the identity authentication method of the present application will be described using the requesting device (REQuester, abbreviated as REQ), the authentication access controller (AAC, abbreviated as AAC), and the authentication server (AS, abbreviated as AS) as examples.

[0051] In this system, the AS trusted by AAC is called the first authentication server AS-AAC, and the AS trusted by REQ is called the second authentication server AS-REQ. AS-REQ holds a digital certificate conforming to ISO / IEC 9594-8 / ITU X.509, other standards, or other technical systems, along with the corresponding private key. AS-AAC can verify the identity of AAC, and AS-REQ can verify the identity of REQ. AS-AAC and AS-REQ can be the same AS or different ASs. When AS-AAC and AS-REQ are the same, it's a non-roaming situation; when AS-AAC and AS-REQ are different, it's a roaming situation. In this case, AS-REQ and AS-AAC have a valid pre-shared key. Alternatively, when AS-AAC holds a digital certificate conforming to ISO / IEC 9594-8 / ITU X.509, other standards, or other technical systems, along with the corresponding private key, AS-AAC and AS-REQ are aware of each other's digital certificates or the public key within the digital certificate.

[0052] REQ can be one endpoint participating in the authentication process, establishing a connection with AAC, accessing the services provided by AAC, and accessing AS through AAC. REQ holds a digital certificate and its corresponding private key conforming to ISO / IEC 9594-8 / ITU X.509, other standards, or other technical systems, and is aware of AS-REQ's digital certificate or the public key within the digital certificate. AAC can be another endpoint participating in the authentication process, establishing a connection with REQ, providing services, communicating with REQ, and directly accessing AS-AAC. AAC and AS-AAC have a valid pre-shared key.

[0053] The following is combined Figure 1 This application provides an embodiment of an identity authentication method, which includes:

[0054] S101, AAC receives the identity message REQInit sent by REQ.

[0055] The REQInit includes REQ's digital certificate Cert. REQ .

[0056] S102, AAC sends a first authentication request message AACVeri to the AS-AAC it trusts.

[0057] The AACeri includes Cert in REQInit. REQ And AAC's authentication code MIC AAC Among them, MIC AAC AAC utilizes the pre-shared key K with AS-AAC. AAC_ASThe cryptographic algorithm agreed upon with AS-AAC is used to process the Cert. REQ The information included is calculated and generated. For example, the cryptographic algorithm agreed upon by AAC and AS-AAC can be a hash algorithm, and AAC utilizes the K... AAC_AS The hash algorithm agreed upon with AS-AAC is used to analyze the MICs in AACVeri. AAC Other fields preceding the field, such as those including the Cert REQ The information, including the hash value, is used to perform a hash operation on the data to obtain the hash value, which serves as the MIC (Authentication Code) for the AAC. AAC .

[0058] In this embodiment, AAC uses MIC. AAC As identity information, REQ uses Cert. REQ As identity information, AS-AAC, trusted by AAC, can verify the MIC. AAC To determine the legitimacy of an AAC identity, the AS-REQ trusted by the REQ can verify the Cert. REQ The legitimacy of the REQ status is determined.

[0059] It should be noted that when the AS-AAC trusted by AAC and the AS-REQ trusted by REQ are the same authentication server, the authentication server jointly trusted by AAC and REQ can be represented by AS-AAC (or AS-REQ). In this case, the Certification is verified by AS-AAC (which can also be represented as AS-REQ). REQ and the MIC AAC AS-AAC (which can also be represented as AS-REQ) utilizes a pre-shared key K with AAC. AAC_AS The MIC is verified using a cryptographic algorithm agreed upon with AAC. AAC The first verification result Res was obtained. AAC According to Res AAC The information included generates the first identification result information Pub AAC , for Cert REQ The second verification result, Res, is obtained by performing a validity verification. REQ According to Res REQ The information included generates the second identification result information Pub REQ and using the K AAC_AS Using cryptographic algorithms agreed upon with AAC, including Pub REQ The information included is used to calculate and generate the first message authentication code (MIC) for AS-AAC. AS_AAC (It can also be represented as the first message authentication code MIC of AS-REQ) AS_REQ ), for including Pub AACThe signature data, including the first digital signature Sig, is calculated to generate the first digital signature. AS_AAC1 (can also be represented as Sig) AS_REQ1 According to the Pub AAC The Sig AS_AAC1 (can also be represented as Sig) AS_REQ1 The Pub REQ and the MIC AS_AAC (can also be represented as MIC) AS_REQ The information, including the first authentication response message ASVeri, is generated.

[0060] When AS-AAC, trusted by AAC, and AS-REQ, trusted by REQ, are two different authentication servers, AS-AAC utilizes the pre-shared key K with AAC. AAC_AS The MIC is verified using a cryptographic algorithm agreed upon with AAC. AAC The first verification result Res was obtained. AAC According to Res AAC The information included generates the first identification result information Pub AAC For including Pub AAC and Cert REQ The second digital signature Sig is generated from the signature data. AS_AAC2 And send a second authentication request message AS-AACVeri to AS-REQ, wherein AS-AACVeri includes the Pub AAC The Cert REQ and the Sig AS_AAC2 Among them, Sig AS_AAC2 Can be replaced with MIC AS_AAC2 MIC AS_AAC2 AS-AAC uses a pre-shared key with AS-REQ and employs a cryptographic algorithm (which can be a hash algorithm) agreed upon with AS-REQ to analyze the Pub database. AAC and the Cert REQ The second message authentication code is generated by calculating the information included.

[0061] After receiving the AS-AACVeri, AS-REQ verifies the Sig using the AS-AAC public key. AS_AAC2 Alternatively, the MIC can be verified using a pre-shared key with AS-AAC and a cryptographic algorithm agreed upon with AS-AAC. AS_AAC2 After successful verification, AS-REQ will process the Cert. REQ The second verification result, Res, is obtained by performing a validity verification. REQ According to Res REQ The information included generates the second identification result information Pub REQFor including the Pub AAC The signature data, including the first digital signature Sig, is calculated to generate the first digital signature. AS_REQ1 For including the Pub REQ The signature data, including the third digital signature Sig, is calculated to generate the third digital signature. AS_REQ3 And send a second authentication response message AS-REQVeri to AS-AAC, wherein the AS-REQVeri includes the Pub AAC The Sig AS_REQ1 The Pub REQ and the Sig AS_REQ3 Among them, Sig AS_REQ3 Can be replaced with MIC AS_REQ3 MIC AS_REQ3 AS-REQ utilizes a pre-shared key with AS-AAC and employs a cryptographic algorithm agreed upon with AS-AAC to process the Pub database. REQ The third message authentication code is generated by calculating the information included.

[0062] After receiving the AS-REQVeri, AS-AAC verifies the Sig using the public key of AS-REQ. AS_REQ3 Alternatively, the MIC can be verified using a pre-shared key with AS-REQ and a cryptographic algorithm agreed upon with AS-REQ. AS_REQ3 After successful verification, AS-AAC uses the pre-shared key K with AAC. AAC_AS The cryptographic algorithm agreed upon with AAC is used to target the Pub database. REQ The information included is used to calculate and generate the first message authentication code (MIC) for AS-AAC. AS_AAC According to the Pub AAC The Sig AS_REQ1 The Pub REQ and the MIC AS_AAC The information included generates the first authentication response message ASVeri.

[0063] S103, AAC receives the first authentication response message ASVeri sent by AS-AAC.

[0064] The ASVeri includes the first identification result information Pub. AAC The first digital signature of AS-REQ, Sig AS_REQ1 Second identification result information Pub REQ The first message authentication code (MIC) of AS-AAC AS_AAC .

[0065] S104, AAC utilizes the pre-shared key K with AS-AAC. AAC_ASThe MIC is verified using a cryptographic algorithm agreed upon with AS-AAC. AS_AAC .

[0066] Among them, AAC utilizes the K AAC_AS The cryptographic algorithm described above is used to analyze ASVeri, including Pub. REQ The information included is used to calculate the MIC locally. AS_AAC and the MIC received from ASVeri AS_AAC By comparing, the MIC can be completed. AS_AAC Verification.

[0067] S105, AAC according to the Pub REQ Res in REQ Determine the identity verification result of REQ.

[0068] S106. AAC sends a third authentication response message, AACAuth, to REQ.

[0069] The AACAuth includes Pub. AAC and the Sig AS_REQ1 .

[0070] It should be noted that the execution order of S104 to S106 does not affect the specific implementation of this application. In practical applications, the execution order of S104 to S106 can be set according to requirements. A preferred suggestion is to execute S104 first, when the AAC operates on the MIC... AS_AAC If the verification fails, discard the ASVeri of S103. When AAC checks the MIC... AS_AAC After successful verification, S105 is executed. If AAC determines that REQ is valid, S106 is executed. If AAC determines that REQ is invalid, AAC will choose whether to execute S106 according to its local policy. Considering efficiency, the preferred solution is not to execute S106 and end the current authentication process.

[0071] S107, REQ uses the AS-REQ public key to verify the Sig. AS_REQ1 If the verification passes, then according to the aforementioned Pub AAC Res in AAC Determine the identity verification result of AAC.

[0072] REQ for the Sig AS_REQ1 After successful verification, you can refer to the Pub. AAC Res in AAC Determining the legitimacy of AAC lays the foundation for ensuring that REQ accesses a legitimate network; if REQ accesses the stated Sig... AS_REQ1 If verification fails, AACAuth is discarded.

[0073] As shown above, in the authentication scenario where the requesting device uses a digital certificate and the authentication access controller uses a pre-shared key, the first authentication server trusted by the authentication access controller verifies the identity authentication code generated by the authentication access controller using the pre-shared key to obtain the first verification result. The second authentication server trusted by the requesting device verifies the legitimacy of the requesting device's digital certificate to obtain the second verification result. The requesting device and the authentication access controller determine whether the other entity is legitimate based on the verification result of the other entity, thereby realizing two-way identity authentication between the authentication access controller and the requesting device, laying the foundation for ensuring that only legitimate users can access the legitimate network.

[0074] Please refer to Figure 1 The REQInit of S101 can also include the digital signature Sig of the REQ. REQ Sig REQ The signature data includes the Sig in REQInit. REQ Other fields mentioned earlier; therefore, before S105, AAC also needs to determine the Sig. REQ Whether the verification passed, if confirmed, Sig REQ If the verification passes, AAC will then proceed based on Pub. REQ Res in REQ Determine the identity authentication result of REQ. Specifically, AAC determines the Sig... REQ Whether the verification passes includes the following methods:

[0075] As a method for verifying the Sig by an authentication server REQ In an embodiment where AS-REQ and AS-AAC are the same authentication server (i.e., non-roaming), when AS-AAC (which can also be represented as AS-REQ) verifies the Sig... REQ At that time, Sig REQ It can be carried in the AACVeri of S102 and transmitted to AS-AAC (also represented as AS-REQ). AS-AAC (also represented as AS-REQ) utilizes the Cert in AACVeri. REQ Verify the Sig REQ If the verification passes, the process of generating and sending the first authentication response message ASVeri continues; if the verification fails, ASVeri is discarded. Therefore, the AAC can determine the Sig based on whether it can receive the ASVeri from S103. REQ Whether the verification passes or not, if the AAC can receive the ASVeri from S103, then the AAC can determine the Sig. REQ Verification successful.

[0076] As a method for verifying the Sig by an authentication serverREQ In another embodiment, where AS-REQ and AS-AAC are two different authentication servers (i.e., roaming), when AS-REQ verifies the Sig... REQ At that time, Sig REQ It can be carried in the AACVeri of S102, and the second authentication request message AS-AACVeri sent by AS-AAC to AS-REQ is transmitted to AS-REQ. AS-REQ uses the Cert in AS-AACVeri. REQ Verify the Sig REQ If the verification passes, AS-REQ continues to generate and send the second authentication response message AS-REQVeri, and AS-AAC continues to generate and send the first authentication response message ASVeri; if the verification fails, AS-REQ discards AS-AACVeri. Therefore, AAC can determine the Sig based on whether it can receive the ASVeri from S103. REQ Whether the verification passes or not, if the AAC can receive the ASVeri from S103, then the AAC can determine the Sig. REQ Verification successful.

[0077] As a method for verifying the Sig by AAC REQ In one embodiment, AAC utilizes the Cert in REQInit of S101. REQ Verify the Sig REQ Based on the verification results, determine Sig REQ Whether the verification passes or fails, REQInit is discarded. Of course, if Pub... REQ It also includes Cert REQ Then AAC can first verify Pub. REQ Cert in REQ Cert in REQInit REQ If consistent, then AAC will use Cert. REQ Verify the Sig REQ Based on the verification results, determine Sig REQ Whether the verification passed. Note that AAC may also not verify Pub. REQ Cert in REQ Cert in REQInit REQ Consistency, and directly using Pub REQ Cert in REQ Verify the Sig REQ .

[0078] It should be noted that the random number and identity identifier of REQ and / or AAC can be transmitted in the messages exchanged during the identity authentication process. Normally, the random number and / or identity identifier carried in the received message should be the same as those carried in the sent message. However, in situations such as network jitter or attacks, the parameter information in the message may be lost or tampered with. Therefore, in some embodiments of this application, the reliability of the authentication result can also be ensured by comparing whether the random number and / or identity identifier in the sent and received messages are consistent. Specifically:

[0079] Please refer to Figure 1 Before S101, AAC can send the first message AACInit to REQ, which includes the first random number Nonce generated by AAC. AAC Correspondingly, the REQInit of S101 may also include the Nonce. AAC Then, after receiving REQInit, AAC will check the Nonce in REQInit. AAC Nonce generated by AAC AAC (That is, the nonce sent by AAC through AACinit) AAC The consistency of the Nonce is verified to ensure that the REQInit received by AAC is a response message to AACInit. AAC If the consistency verification passes, AAC will then send AACVeri to S102.

[0080] In other embodiments, the AACVeri of S102 may also include the AAC's identity ID. AAC and / or the first random number Nonce generated by AAC AAC Correspondingly, the ASVeri of S103 may also include the ID. AAC and / or the stated Nonce AAC Before S105, AAC also needs to process the ID in ASVeri. AAC and AAC's own identity ID AAC (That is, the ID sent by AAC through AACVeri) AAC Verify the consistency of ) and / or, the Nonce in ASVeri AAC Nonce generated by AAC AAC (That is, the Nonce sent by AAC through AACCVeri) AAC The consistency of the ) is verified; if the verification passes, AAC then verifies the consistency of the Pub. REQ Res in REQ Determine the identity verification result of REQ.

[0081] Of course, to ensure the reliability of the identification results, REQ can also adjust the second random number Nonce generated by REQ. REQ and / or REQ's identity ID REQ Consistency verification is performed.

[0082] Please refer to Figure 1 The REQInit of S101 can also include the REQ's identity ID. REQ and / or the second random number Nonce generated by REQ REQ Then, the ID can also be included in the AACVeri of S102, the second authentication request message AS-AACVeri, the second authentication response message AS-REQVeri, the ASVeri of S103, and the AACAuth of S106 in subsequent interactions. REQ and / or the stated Nonce REQ Therefore, in S107, REQ is based on Pub. AAC Res in AAC Before determining the identity authentication result of AAC, REQ also needs to verify the ID in AACAuth. REQ and REQ's own identity ID REQ (That is, the ID sent by REQ through REQInit) REQ Verify the consistency of ) and / or verify the Nonce in AACAuth. REQ Nonce generated by REQ REQ (That is, the nonce sent by REQ through REQInit) REQ The consistency of the REQ is verified; if the verification passes, the REQ is then verified against the Pub. AAC Res in AAC Determine the identity verification result of AAC.

[0083] It should be noted that in some other embodiments, if the Pub AAC It also includes the AAC's identity ID. AAC Correspondingly, S106's AACAuth also includes the AAC's identity ID. AAC Alternatively, before S101, the first message AACInit sent by AAC to REQ may also include AAC's identity ID. AAC Then in S107, REQ is based on Pub. AAC Res in AAC Before determining the identity verification result of AAC, REQ can also check Pub. AAC ID in AAC ID in AACAuth AACTo verify consistency, or to test the Pub... AAC ID in AAC ID in AACInit AAC The consistency is verified; if the verification passes, the REQ is then verified based on the Pub. AAC Res in AAC Determine the identity verification result of AAC.

[0084] In the above embodiment, before S101, the first message AACInit sent by AAC to REQ may also include security capability parameters supported by AAC. AAC Security capabilities AAC This includes AAC-supported authentication suites (which contain one or more authentication methods), enabling REQ to meet the security capabilities stated above. AAC Select the specific security policy used by REQ (Security Capabilities) REQ Security capabilities REQ This indicates that the REQ will determine the authentication method used. Accordingly, REQInit in S101 also includes the aforementioned Security capabilities. REQ Then AAC, based on the aforementioned security capabilities REQ The security policy used in this authentication process can be determined. This application also provides a method for determining the first authentication server and / or the second authentication server used in this authentication process by utilizing information exchange between AAC and REQ:

[0085] One implementation involves AAC proactively sending the identity ID of at least one trusted authentication server to REQ. AS_AAC For example, before S101, the first message AACInit sent by AAC to REQ also includes the ID. AS_AAC Then REQ from ID AS_AAC Select at least one authentication server that it trusts as its ID. AS_REQ If the selection fails, REQ will use the identity of at least one trusted authentication server as its ID. AS_REQ (Where, successful selection corresponds to a non-roaming situation, and failed selection corresponds to a roaming situation), and the ID... AS_REQ The REQInit function in S101 is added and sent to AAC. AAC can then use the ID... AS_AAC and ID AS_REQThe primary authentication server, such as AAC, can be used to determine the ID. AS_REQ and ID AS_AAC If at least one identical authentication server identifier exists, it indicates a non-roaming situation. AAC determines the first authentication server to participate in authentication from among the at least one authentication server identifier trusted by both REQ and AAC. If no such identifier exists, it indicates a roaming situation, and AAC needs to determine the first authentication server based on the ID. AS_AAC Determine the first authentication server AS-AAC involved in identity authentication and set the ID. AS_REQ Send to AS-AAC so that AS-AAC can process the data based on the ID. AS_REQ Determine the second authentication server AS-REQ.

[0086] Another implementation is that AAC does not need to send the ID to REQ. AS_AAC The REQ actively identifies at least one trusted authentication server's identity ID. AS_REQ Send to AAC, for example, REQ will send ID AS_REQ Add it to REQInit in S101 and send it to AAC. Based on ID AS_REQ The identity ID of the authentication server trusted by AAC itself. AS_AAC The specific implementation methods for determining the first authentication server and / or the second authentication server participating in the identity authentication process are as described in the previous implementation method.

[0087] Since the authentication servers trusted by REQ and AAC can be the same or different, when the authentication servers trusted by REQ and AAC are the same, it is a non-roaming situation; when the authentication servers trusted by REQ and AAC are different, it is a roaming situation. Based on the foregoing embodiments, the identity authentication method of this application embodiment is described below in conjunction with non-roaming and roaming application scenarios for the following four situations: (I) In the non-roaming situation, AAC verifies Sig REQ (ii) In non-roaming situations, the identity verification method is performed by AS-AAC. REQ (iii) In roaming situations, the identity verification method is performed by AAC. REQ (iv) In roaming situations, the Sig identity verification method is performed by AS-REQ. REQ Identification methods.

[0088] See Figure 2 This is an embodiment of the identity authentication method under the above-described (i) scenario, wherein AS-AAC (or AS-REQ) can be used to represent the authentication server jointly trusted by REQ and AAC. The identity authentication method includes:

[0089] S201, AAC generates Nonce AACGenerate security capabilities as needed. AAC .

[0090] S202, AAC sends the first message AACInit to REQ.

[0091] The AACInit includes Nonce AAC and Security capabilities AAC Among them, Security capabilities AAC This is an optional field that represents the security capability parameters supported by AAC, including the identity authentication suites supported by AAC (the same applies below).

[0092] S203. After receiving AACInit, REQ performs the following operations (unless otherwise specified or logically related, the actions numbered (1), (2)... in this document do not necessarily have a sequential order due to their numbering, and the same applies throughout the document), including:

[0093] (1) Generate Nonce REQ ;

[0094] (2) Generate Security capabilities as needed REQ ;

[0095] (3) Calculate and generate the digital signature Sig of REQ REQ .

[0096] S204, REQ sends the identity message REQInit to AAC.

[0097] The REQInit includes Nonce AAC Nonce REQ Security capabilities REQ ID REQ Cert REQ and Sig REQ Among them, security capabilities REQ This is an optional field; REQ specifies whether to generate security capabilities. REQ Depending on whether the AACInit sent by AAC to REQ carries security capabilities AAC Security capabilities REQ REQ indicates that it is based on security capabilities AACThe selection of a specific security strategy, i.e., the REQ determines the authentication method to be used (hereinafter the same). Sig REQ The signature data includes the Sig in REQInit. REQ Other fields mentioned earlier; for example, when REQInit includes Nonce in sequence. AAC Nonce REQ Security capabilities REQ ID REQ Cert REQ and Sig REQ At that time, Sig REQ The signature data includes the Nonce AAC Nonce REQ Security capabilities REQ ID REQ and Cert REQ In this application, the object to be signed is referred to as signature data.

[0098] S205. After receiving REQInit, AAC performs the following operations, including:

[0099] (1) Check the Nonce in REQInit AAC Nonce generated by AAC AAC Check if they match; if not, discard REQInit.

[0100] (2) Calculate and generate the AAC authentication code MIC AAC .

[0101] S206, AAC sends the first authentication request message AACVeri to AS-AAC.

[0102] The AACeri includes ID REQ Cert REQ Nonce REQ ID AAC Nonce AAC and MIC AAC Among them, ID REQ Cert REQ Nonce REQ It should equal the corresponding field in REQInit; Nonce AAC It should be equal to the Nonce generated by AAC. AAC ;MIC AAC AAC utilizes the pre-shared key K with AS-AAC. AAC_AS The cryptographic algorithm agreed upon with AS-AAC is used to target MICs in AACeri.AAC Other fields were calculated previously, for example, when AACVeri includes ID in sequence. REQ Cert REQ Nonce REQ ID AAC Nonce AAC and MIC AAC At that time, AAC utilizes the K AAC_AS It employs cryptographic algorithms agreed upon with AS-AAC to handle IDs. REQ Cert REQ Nonce REQ ID AAC Nonce AAC Including information calculation to generate MIC AAC .

[0103] S207. After receiving AACVeri, AS-AAC performs the following operations, including:

[0104] (1) Verify MIC AAC Get Res AAC According to ID AAC and Res AAC Information generated in Pub AAC ;

[0105] MIC verification AAC The process includes: AS-AAC based on the ID in AACeri AAC Determine the pre-shared key K agreed with AAC. AAC_AS And cryptographic algorithms, utilizing the K AAC_AS The cryptographic algorithm described above is used to target the MIC in AACeri. AAC The other fields were previously calculated locally to determine the MIC. AAC and the received MIC AAC Compare them; if they are the same, then MIC... AAC If the verification passes, AS-AAC determines that the AAC's identity authentication result is valid; otherwise, MIC... AAC If verification fails, AS-AAC may handle the situation in the following ways according to local policies, including discarding AACVeri or determining that the AAC's identity authentication result is invalid.

[0106] (2) Verify Cert REQ The legitimacy of Res REQ According to Res REQ and Cert REQ Information generated in Pub REQ ;

[0107] (3) Calculate the first message authentication code (MIC) of AS-AAC. AS_AAC And the first digital signature Sig AS_AAC1 .

[0108] S208, AS-AAC sends the first authentication response message ASVeri to AAC.

[0109] The ASVeri includes ID REQ Nonce REQ Pub AAC Sig AS_AAC1 ID AAC Nonce AAC Pub REQ and MIC AS_AAC Among them, ID REQ Nonce REQ ID AAC Nonce AAC They should be equal to the corresponding fields in AACVeri. MIC AS_AAC AS-AAC utilizes the pre-shared key K with AAC. AAC_AS The cryptographic algorithm agreed upon with AAC is used to process the ID. AAC Nonce AAC Pub REQ Information generated by computation, including; Sig AS_AAC1 AS-AAC includes ID REQ Nonce REQ Pub AAC The signature data, including the signature data, is calculated and generated.

[0110] S209. After receiving ASVeri, AAC performs the following operations, including:

[0111] (1) Check the ID in ASVeri AAC Nonce AAC Are they respectively related to AAC's own identity ID? AAC Nonce generated by AAC AAC same;

[0112] (2) Verify MIC AS_AAC ;

[0113] MIC verification AS_AAC The process includes: AAC using the pre-shared key K with AS-AAC AAC_AS The cryptographic algorithm agreed upon with AS-AAC is used to process the ID in ASVeri. AAC Nonce AAC Pub REQIncluding information calculation to generate MIC AS_AAC and the received MIC AS_AAC The comparison is performed; if they are the same, the verification passes; if they are different, the verification fails.

[0114] (3) Check Pub REQ Cert in REQ Does it match the Cert in the received REQInit? REQ same;

[0115] (4) Using Cert REQ Verify Sig REQ ;

[0116] (5) If any step of the above checks and verifications fails, the ASVer shall be discarded immediately; if all the above checks and verifications pass, the ASVer shall be determined according to the Pub. REQ Res in REQ Determine the identity verification result of REQ; if REQ is determined to be illegitimate, then end the current verification process.

[0117] S210, AAC sends a third authentication response message AACAuth to REQ.

[0118] The AACAuth includes ID. REQ Nonce REQ Pub AAC Sig AS_AAC1 and ID AAC Among them, ID REQ Nonce REQ Pub AAC Sig AS_AAC1 Source: ASVeri; ID AAC AAC's own identity ID AAC .

[0119] S211. After receiving AACAuth, REQ performs the following operations, including:

[0120] (1) Check ID REQ Nonce REQ Are they respectively related to REQ's own identity ID? REQ Nonce generated by REQ REQ same;

[0121] (2) Check ID AAC With Pub AAC ID in AAC Are they the same?

[0122] (3) Verify Sig using AS-AAC public key AS_AAC1 ;

[0123] (4) If any step of the above checks and verifications fails, AACAuth is immediately discarded; if all the above checks and verifications pass, AACAuth is discarded according to Pub. AAC Res in AAC Determine the identity verification result of AAC.

[0124] See Figure 3 This is an embodiment of the identity authentication method under scenario (ii) above, wherein AS-AAC (or AS-REQ) can be used to represent the authentication server jointly trusted by REQ and AAC. The identity authentication method includes:

[0125] S301, AAC generates Nonce AAC Generate security capabilities as needed. AAC .

[0126] S302, AAC sends the first message AACInit to REQ.

[0127] The AACInit includes Nonce AAC and Security capabilities AAC Among them, Security capabilities AAC This is an optional field.

[0128] After receiving AACInit, S303 and REQ perform the following operations, including:

[0129] (1) Generate Nonce REQ ;

[0130] (2) Generate Security capabilities as needed REQ ;

[0131] (3) Calculate and generate the digital signature Sig of REQ REQ .

[0132] S304, REQ sends the identity message REQInit to AAC.

[0133] The REQInit includes Nonce AAC Nonce REQ Security capabilities REQ ID REQ Cert REQ and Sig REQAmong them, security capabilities REQ This is an optional field. Sig REQ The signature data includes the Sig in REQInit. REQ Other fields mentioned earlier.

[0134] S305. After receiving REQInit, AAC performs the following operations, including:

[0135] (1) Check the Nonce in REQInit AAC Nonce generated by AAC AAC Check if they match; if not, discard REQInit.

[0136] (2) Calculate and generate the AAC authentication code MIC AAC .

[0137] S306, AAC sends the first authentication request message AACVeri to AS-AAC.

[0138] The AACVeri includes REQInit and ID. AAC and MIC AAC Among them, MIC AAC AAC utilizes the pre-shared key K with AS-AAC. AAC_AS The cryptographic algorithm agreed upon with AS-AAC is used to target MICs in AACeri. AAC This was generated from calculations performed on other fields previously.

[0139] After receiving the AACVeri, S307 and AS-AAC perform the following operations, including:

[0140] (1) Verify MIC AAC Get Res AAC According to ID AAC and Res AAC Information generated in Pub AAC Among them, MIC AAC See the verification process. Figure 2 Relevant descriptions in the embodiments;

[0141] (2) Using Cert in REQInit REQ Verify Sig REQ If the verification fails, discard the AACVeri.

[0142] (3) Verify the Cert in REQInit REQ The legitimacy of Res REQ According to Res REQInformation generated in Pub REQ ;

[0143] (4) Calculate the first message authentication code (MIC) of AS-AAC. AS_AAC And the first digital signature Sig AS_AAC1 .

[0144] S308, AS-AAC sends the first authentication response message ASVeri to AAC.

[0145] The ASVeri includes ID REQ Nonce REQ Pub AAC Sig AS_AAC1 ID AAC Nonce AAC Pub REQ and MIC AS_AAC Among them, ID REQ Nonce REQ ID AAC Nonce AAC They should be equal to the corresponding fields in AACVeri. MIC AS_AAC AS-AAC utilizes the pre-shared key K with AAC. AAC_AS The cryptographic algorithm agreed upon with AAC is used to process the ID. AAC Nonce AAC Pub REQ Information generated by computation, including; Sig AS_AAC1 AS-AAC includes ID REQ Nonce REQ Pub AAC The signature data, including the signature data, is calculated and generated.

[0146] S309. After receiving ASVeri, AAC performs the following operations, including:

[0147] (1) Check the ID in ASVeri AAC Nonce AAC Are they respectively related to AAC's own identity ID? AAC Nonce generated by AAC AAC same;

[0148] (2) Verify MIC AS_AAC ;

[0149] MIC verification AS_AAC The process includes: AAC using the pre-shared key K with AS-AAC AAC_AS The cryptographic algorithm agreed upon with AS-AAC is used to process the ID in ASVeri.AAC Nonce AAC Pub REQ Including information calculation to generate MIC AS_AAC and the received MIC AS_AAC The comparison is performed; if they are the same, the verification passes; if they are different, the verification fails.

[0150] (3) If any step of the above checks and verifications fails, ASVeri shall be discarded immediately; if all the above checks and verifications pass, ASVeri shall be discarded according to the Pub. REQ Res in REQ Determine the identity verification result of REQ; if REQ is determined to be illegitimate, then end the current verification process.

[0151] S310, AAC sends a third authentication response message AACAuth to REQ.

[0152] The AACAuth includes ID. REQ Nonce REQ Pub AAC Sig AS_AAC1 and ID AAC Among them, ID REQ Nonce REQ Pub AAC Sig AS_AAC1 Originating from ASVeri.

[0153] S311. After receiving AACAuth, REQ performs the following operations, including:

[0154] (1) Check ID REQ Nonce REQ Are they respectively related to REQ's own identity ID? REQ Nonce generated by REQ REQ same;

[0155] (2) Check ID AAC With Pub AAC ID in AAC Are they the same?

[0156] (3) Verify Sig using AS-AAC public key AS_AAC1 ;

[0157] (4) If any step of the above checks and verifications fails, AACAuth is immediately discarded; if all the above checks and verifications pass, AACAuth is discarded according to Pub. AAC Res in AAC Determine the identity verification result of AAC.

[0158] See Figure 4 This is an embodiment of the identity authentication method under the above-described (iii) scenario, and the identity authentication method includes:

[0159] S401, AAC generates Nonce AAC Generate security capabilities as needed. AAC .

[0160] S402, AAC sends the first message AACInit to REQ.

[0161] The AACInit includes Nonce AAC Security capabilities AAC and ID AS_AAC Among them, Security capabilities AAC and ID AS_AAC It is an optional field, and ID AS_AAC The identity identifier of at least one authentication server representing AAC trust is used to enable REQ to be based on the ID. AS_AAC Determine if a mutually trusted authentication server exists (the same applies below).

[0162] After receiving AACInit, S403 and REQ perform the following operations, including:

[0163] (1) Generate Nonce REQ ;

[0164] (2) Generate ID as needed AS_REQ ;

[0165] (3) Generate Security capabilities as needed REQ ;

[0166] (4) Calculate and generate the digital signature Sig of REQ REQ .

[0167] S404, REQ sends the identity message REQInit to AAC.

[0168] The REQInit includes Nonce AAC Nonce REQ Security capabilities REQ ID AS_REQ ID REQ Cert REQ and Sig REQ Among them, Nonce AACIt should equal the corresponding field in AACInit; Security capabilities REQ and ID AS_REQ It is an optional field, and ID AS_REQ The identity identifier of at least one authentication server representing REQ trust, when an ID exists in AACInit. AS_AAC At that time, REQ will try to select at least one authentication server from its trusted authentication servers that matches the ID. AS_AAC The same authentication server in the middle as ID AS_REQ If the choice fails, at least one authentication server trusted by the user will be used as the ID. AS_REQ When the ID does not exist in AACInit AS_AAC At that time, REQ uses at least one authentication server it trusts as its ID. AS_REQ (The same applies below). Sig REQ The signature data includes the Sig in REQInit. REQ Other fields mentioned earlier.

[0169] After receiving REQInit, S405 and AAC perform the following operations, including:

[0170] (1) Check the Nonce in REQInit AAC Nonce generated by AAC AAC Check if they match; if not, discard REQInit.

[0171] (2) Calculate and generate the AAC authentication code MIC AAC ;

[0172] (3) If REQInit carries ID AS_REQ And AACInit carries an ID AS_AAC Then AAC determines ID AS_REQ and ID AS_AAC If at least one identical authentication server identity exists, it indicates a non-roaming scenario. AAC determines the first authentication server to participate in authentication from among the identity identifiers of at least one authentication server commonly trusted by both REQ and AAC. If no such server exists, it indicates a roaming scenario, and AAC needs to determine the first authentication server based on the ID. AS_AAC Determine the first authentication server AS-AAC involved in identity authentication and set the ID. AS_REQ Send to AS-AAC so that AS-AAC can process the data based on the ID. AS_REQ Determine the second authentication server AS-REQ; or,

[0173] If REQInit carries an ID AS_REQ However, AACInit does not carry an ID. AS_AACThen AAC determines ID AS_REQ If at least one authentication server with the same identity identifier exists as the authentication server trusted by AAC, then in a non-roaming scenario, AAC determines the first authentication server to participate in identity authentication from among the identity identifiers of at least one authentication server commonly trusted by both REQ and AAC. If none exists, then in a roaming scenario, AAC needs to determine the first authentication server AS-AAC to participate in identity authentication based on its own trusted authentication servers, and then record the ID. AS_REQ Send to AS-AAC so that AS-AAC can process the data based on the ID. AS_REQ Determine the second authentication server AS-REQ;

[0174] It should be noted that the result determined in this embodiment should be the roaming status.

[0175] S406, AAC sends the first authentication request message AACVeri to AS-AAC.

[0176] The AACeri includes Nonce REQ ID AS_REQ ID REQ Cert REQ ID AAC Nonce AAC and MIC AAC Among them, Nonce REQ ID AS_REQ ID REQ Cert REQ They should be equal to the corresponding fields in REQInit; Nonce AAC It should be equal to the Nonce generated by AAC. AAC ID AS_REQ This is an optional field. MIC AAC AAC utilizes the pre-shared key K with AS-AAC. AAC_AS The hash algorithm agreed upon with AS-AAC is used to analyze the MICs in AACVeri. AAC The hash value generated from the calculation of other fields previously.

[0177] After receiving the AACVeri, S407 and AS-AAC perform the following operations, including:

[0178] (1) Verify MIC AAC Get Res AAC According to Res AAC and ID AAC Information generated in Pub AAC The verification process is detailed in [link to documentation]. Figure 2 Description of relevant content in the implementation examples;

[0179] (2) Calculate and generate the second digital signature Sig AS_AAC2 .

[0180] S408, AS-AAC sends a second authentication request message AS-AACVeri to AS-REQ.

[0181] The AS-AACVeri includes Nonce REQ ID REQ Cert REQ ID AAC Nonce AAC Pub AAC and Sig AS_AAC2 Among them, Sig AS_AAC2 The signature data includes Sig in AS-AACVeri. AS_AAC2 Other fields mentioned earlier.

[0182] After receiving AS-AACVeri, S409 and AS-REQ perform the following operations, including:

[0183] (1) Verify Sig using AS-AAC public key AS_AAC2 If the verification fails, discard AS-AACVeri.

[0184] (2) Verify Cert REQ The legitimacy of Res REQ According to Cert REQ and Res REQ Information generated in Pub REQ ;

[0185] (3) Calculate the first digital signature Sig AS_REQ1 and third digital signature Sig AS_REQ3 .

[0186] S410, AS-REQ sends a second authentication response message AS-REQVeri to AS-AAC.

[0187] The AS-REQVeri includes ID REQ Nonce REQ Pub AAC Sig AS_REQ1 ID AAC Nonce AAC Pub REQ and Sig AS_REQ3 Among them, ID REQ Nonce REQ Pub AAC IDAAC Nonce AAC These should be equal to the corresponding fields in AS-AACVeri. Sig AS_REQ1 AS-REQ pairs include ID REQ Nonce REQ Pub AAC The signature data is generated by calculation; Sig AS_REQ3 AS-REQ pairs include ID AAC Nonce AAC Pub REQ The signature data, including the signature data, is calculated and generated.

[0188] S411. After receiving AS-REQVeri, AS-AAC performs the following operations, including:

[0189] (1) Verify Sig using the public key of AS-REQ AS_REQ3 If the verification fails, discard the AS-REQVeri.

[0190] (2) Calculate the first message authentication code (MIC) of AS-AAC. AS_AAC .

[0191] S412, AS-AAC sends the first authentication response message ASVeri to AAC.

[0192] The ASVeri includes ID REQ Nonce REQ Pub AAC Sig AS_REQ1 ID AAC Nonce AAC Pub REQ and MIC AS_AAC Among them, ID REQ Nonce REQ Pub AAC Sig AS_REQ1 ID AAC Nonce AAC Pub REQ They should be equal to the corresponding fields in AS-REQVeri; MIC AS_AAC AS-AAC utilizes the pre-shared key K with AAC. AAC_AS The hash algorithm agreed upon with AAC is used to process the ID. AAC Nonce AAC Pub REQ The hash value is generated by calculating the information included.

[0193] S413. After receiving ASVeri, AAC performs the following operations, including:

[0194] (1) Check the ID in ASVeri AAC Nonce AAC Are they respectively related to AAC's own identity ID? AAC Nonce generated by AAC AAC same;

[0195] (2) Verify MIC AS_AAC See the verification process. Figure 2 Description of relevant content in the illustrated embodiments;

[0196] (3) Check Pub REQ Cert in REQ Does it match the Cert in the received REQInit? REQ same;

[0197] (4) Using Cert REQ Verify Sig REQ ;

[0198] (5) If any step of the above checks and verifications fails, ASVeri shall be discarded immediately; if all the above checks and verifications pass, ASVeri shall be discarded according to the Pub. REQ Res in REQ Determine the identity verification result of REQ; if REQ is determined to be illegitimate, then end the current verification process.

[0199] S414, AAC sends a third authentication response message AACAuth to REQ.

[0200] The AACAuth includes ID. REQ Nonce REQ Pub AAC Sig AS_REQ1 and ID AAC Among them, ID REQ Nonce REQ Pub AAC Sig AS_REQ1 Source: ASVeri; ID AAC AAC's own identity ID AAC .

[0201] S415. After receiving AACAuth, REQ performs the following operations, including:

[0202] (1) Check ID REQ Nonce REQ Are they respectively related to REQ's own identity ID?REQ Nonce generated by REQ REQ Are they the same?

[0203] (2) Check ID AAC With Pub AAC ID in AAC Are they the same?

[0204] (3) Verify Sig using the public key of AS-REQ AS_REQ1 ;

[0205] (4) If any step of the above checks and verifications fails, AACAuth is immediately discarded; if all the above checks and verifications pass, AACAuth is discarded according to Pub. AAC Res in AAC Determine the identity verification result of AAC.

[0206] It should be noted that the second digital signature Sig in S407 and S408 AS_AAC2 It can be replaced with the second message authentication code (MIC). AS_AAC2 , among which, MIC AS_AAC2 AS-AAC uses a pre-shared key with AS-REQ and employs a hash algorithm agreed upon with AS-REQ to process MICs in AS-AAC. AS_AAC2 The hash value calculated from other fields previously; then the AS-REQ verification Sig in S409 AS_AAC2 Replace with verification MIC AS_AAC2 The third digital signature Sig in S409 and S410 AS_REQ3 It can be replaced with a third message authentication code (MIC). AS_REQ3 , among which, MIC AS_REQ3 AS-REQ uses a pre-shared key with AS-AAC and employs a hash algorithm agreed upon with AS-AAC to hash the IDs in AS-REQVeri. AAC Nonce AAC Pub REQ The hash value calculated from the fields included; then the AS-AAC verification Sig in S411 AS_REQ3 Replace with verification MIC AS_REQ3 .

[0207] See Figure 5 This is an embodiment of the identity authentication method under the above-described (iv) scenario, and the identity authentication method includes:

[0208] S501, AAC generates Nonce AAC Generate security capabilities as needed. AAC .

[0209] S502 and AAC send the first message AACInit to REQ.

[0210] The AACInit includes Nonce AAC Security capabilities AAC and ID AS_AAC Among them, Security capabilities AAC and ID AS_AAC This is an optional field.

[0211] After receiving AACInit, S503 and REQ perform the following operations, including:

[0212] (1) Generate Nonce REQ ;

[0213] (2) Generate ID as needed AS_REQ ;

[0214] (3) Generate Security capabilities as needed REQ ;

[0215] (4) Calculate and generate the digital signature Sig of REQ REQ .

[0216] S504, REQ sends the identity message REQInit to AAC.

[0217] The REQInit includes Nonce AAC Nonce REQ Security capabilities REQ ID AS_REQ ID REQ Cert REQ and Sig REQ Among them, Nonce AAC It should equal the corresponding field in AACInit; Security capabilities REQ and ID AS_REQ This is an optional field; Sig REQ The signature data includes the Sig in REQInit. REQ Other fields mentioned earlier.

[0218] When S505 and AAC receive REQInit, they perform the following operations, including:

[0219] (1) Check the Nonce in REQInit AAC Nonce generated by AAC AACCheck if they match; if not, discard REQInit.

[0220] (2) Calculate and generate the AAC authentication code MIC AAC ;

[0221] (3) AAC determines the first authentication server AS-AAC participating in identity authentication, and AS-AAC determines the second authentication server AS-REQ as described in Example 4; it should be noted that the result determined in this example should be the roaming situation.

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

[0223] The AACVeri includes REQInit and ID. AAC and MIC AAC Among them, MIC AAC AAC utilizes the pre-shared key K with AS-AAC. AAC_AS The hash algorithm agreed upon with AS-AAC is used to analyze the MICs in AACVeri. AAC The hash value generated from the calculation of other fields previously.

[0224] After receiving the AACVeri, S507 and AS-AAC perform the following operations, including:

[0225] (1) Verify MIC AAC Get Res AAC According to Res AAC and ID AAC Information generated in Pub AAC The verification process is detailed in [link to documentation]. Figure 2 Description of relevant content in the implementation examples;

[0226] (2) Calculate and generate the second digital signature Sig AS_AAC2 .

[0227] S508, AS-AAC sends a second authentication request message AS-AACVeri to AS-REQ.

[0228] The AS-AACVeri includes REQInit and ID. AAC Pub AAC and Sig AS_AAC2 Among them, Sig AS_AAC2 The signature data includes Sig in AS-AACVeri. AS_AAC2 Other fields mentioned earlier.

[0229] After receiving AS-AACVeri, S509 and AS-REQ perform the following operations, including:

[0230] (1) Verify Sig using AS-AAC public key AS_AAC2 And, using Cert in REQInit REQ Verify Sig REQ If the verification fails, discard AS-AACVeri;

[0231] (2) Verify Cert REQ The legitimacy of Res REQ According to Res REQ Information generated in Pub REQ ;

[0232] (3) Calculate the first digital signature Sig AS_REQ1 and third digital signature Sig AS_REQ3 .

[0233] S510 and AS-REQ send a second authentication response message AS-REQVeri to AS-AAC.

[0234] The AS-REQVeri includes ID REQ Nonce REQ Pub AAC Sig AS_REQ1 ID AAC Nonce AAC Pub REQ and Sig AS_REQ3 Among them, ID REQ Nonce REQ Pub AAC ID AAC Nonce AAC These should be equal to the corresponding fields in AS-AACVeri. Sig AS_REQ1 AS-REQ pairs include ID REQ Nonce REQ Pub AAC The signature data is generated by calculation; Sig AS_REQ3 AS-REQ pairs include ID AAC Nonce AAC Pub REQ The signature data, including the signature data, is calculated and generated.

[0235] S511, after receiving AS-REQVeri, AS-AAC performs the following operations, including:

[0236] (1) Verify Sig using the public key of AS-REQ AS_REQ3 If the verification fails, discard the AS-REQVeri.

[0237] (2) Calculate the first message authentication code (MIC) of AS-AAC. AS_AAC .

[0238] S512, AS-AAC sends the first authentication response message ASVeri to AAC.

[0239] The ASVeri includes ID REQ Nonce REQ Pub AAC Sig AS_REQ1 ID AAC Nonce AAC Pub REQ and MIC AS_AAC Among them, ID REQ Nonce REQ Pub AAC Sig AS_REQ1 ID AAC Nonce AAC Pub REQ They should be equal to the corresponding fields in AS-REQVeri; MIC AS_AAC AS-AAC utilizes the pre-shared key K with AAC. AAC_AS The hash algorithm agreed upon with AAC is used to process the ID. AAC Nonce AAC Pub REQ The hash value is generated by calculating the information included.

[0240] S513. After receiving ASVeri, AAC performs the following operations, including:

[0241] (1) Check the ID in ASVeri AAC Nonce AAC Are they respectively related to AAC's own identity ID? AAC Nonce generated by AAC AAC same;

[0242] (2) Verify MIC AS_AAC See the verification process. Figure 3 Description of relevant content in the implementation examples;

[0243] (3) If any step of the above checks and verifications fails, ASVeri shall be discarded immediately; if all the above checks and verifications pass, ASVeri shall be discarded according to the Pub. REQ Res in REQDetermine the identity verification result of REQ; if REQ is determined to be illegitimate, then end the current verification process.

[0244] S514, AAC sends a third authentication response message AACAuth to REQ.

[0245] The AACAuth includes ID. REQ Nonce REQ Pub AAC Sig AS_REQ1 and ID AAC Among them, ID REQ Nonce REQ Pub AAC Sig AS_REQ1 Source: ASVeri; ID AAC AAC's own identity ID AAC .

[0246] After receiving AACAuth, S515 and REQ perform the following operations, including:

[0247] (1) Check ID REQ Nonce REQ Are they respectively related to REQ's own identity ID? REQ Nonce generated by REQ REQ same;

[0248] (2) Check ID AAC With Pub AAC ID in AAC Are they the same?

[0249] (3) Verify Sig using the public key of AS-REQ AS_REQ1 ;

[0250] (4) After all the above checks and verifications are passed, according to Pub AAC Res in AAC Determine the identity authentication result of AAC; if any step of the above checks and verifications fails, discard AACAuth immediately.

[0251] It should be noted that the second digital signature Sig in S507 and S508 AS_AAC2 It can be replaced with the second message authentication code (MIC). AS_AAC2 , among which, MIC AS_AAC2 AS-AAC uses a pre-shared key with AS-REQ and employs a hash algorithm agreed upon with AS-REQ to process MICs in AS-AAC. AS_AAC2 The hash value calculated from other fields previously; then the AS-REQ verification Sig in S509AS_AAC2 Replace with verification MIC AS_AAC2 The third digital signature Sig in S509 and S510 AS_REQ3 It can be replaced with a third message authentication code (MIC). AS_REQ3 , among which, MIC AS_REQ3 AS-REQ uses a pre-shared key with AS-AAC and employs a hash algorithm agreed upon with AS-AAC to hash the IDs in AS-REQVeri. AAC Nonce AAC Pub REQ The hash value calculated from the fields included; then the AS-AAC verification Sig in S511 AS_REQ3 Replace with verification MIC AS_REQ3 .

[0252] In the above embodiments, each message may also carry a hash value. X_Y The hash value X_Y This is calculated by the sending entity X using a hash algorithm on the latest preceding message received from the peer entity Y. It is used by the peer entity Y to verify whether entity X has received the complete latest preceding message. Here, HASH... REQ_AAC This represents the hash value calculated by REQ for the latest preceding message sent by AAC. AAC_REQ HASH represents the hash value calculated by AAC for the latest preceding message sent by the received REQ. AAC_AS-AAC HASH represents the hash value calculated by AAC for the latest preceding message received from AS-AAC. AS-AAC_AAC HASH represents the hash value calculated by AS-AAC for the latest preceding message sent by AAC. AS-AAC_AS-REQ HASH represents the hash value calculated by AS-AAC for the latest preceding message sent by AS-REQ. AS-REQ_AS-AAC This represents the hash value calculated by AS-REQ for the latest preceding message received from AS-AAC. If the message currently sent by sender entity X is the first message exchanged between entity X and entity Y, meaning that entity X has not received any preceding messages from peer entity Y, then the hash value in this message... X_Y It may not exist or be meaningless.

[0253] Correspondingly, after the peer entity Y receives a message sent by entity X, if the message contains a hash... X_Y If entity Y has not sent a preceding message to entity X, then entity Y ignores the hash. X_YWhen entity Y has previously sent a preceding message to entity X, entity Y uses a hash algorithm to calculate a hash value locally for the latest preceding message previously sent to entity X, and then hashes it with the hash value carried in the received message. X_Y If they match, proceed with the next steps; otherwise, discard or end the identification process.

[0254] In this invention, for entity X, the preceding message sent by peer entity Y to entity X refers to any message received by entity X from peer entity Y before entity X sends message M to peer entity Y; the latest preceding message sent by peer entity Y to entity X refers to the latest message received by entity X from peer entity Y before entity X sends message M to peer entity Y. If message M sent by entity X to its peer entity Y is the first message exchanged between entity X and entity Y, then there are no preceding messages sent by peer entity Y to entity X before entity X sends message M to its peer entity Y.

[0255] The above Figures 2 to 5 The optional fields and optional operations in the corresponding embodiments are shown in the accompanying drawings. Figures 2 to 5 The asterisk (*) indicates the content. The order of the various contents included in the messages in all the above embodiments is not limited, and unless otherwise specified, the order in which the message recipient operates on the relevant messages and processes the contents included in the messages is not limited.

[0256] based on Figures 1 to 5 For the corresponding method implementation examples, please refer to... Figure 6 This application embodiment also provides a requesting device 600, including:

[0257] Sending module 610 is used to send an identity message to the authentication access controller, the identity message including the digital certificate of the requesting device;

[0258] The receiving module 620 is configured to receive a third authentication response message sent by the authentication access controller, the third authentication response message including first authentication result information and a first digital signature; the first authentication result information includes a first verification result of the authentication access controller, and the first digital signature is a digital signature calculated by the second authentication server trusted by the requesting device on signature data including the first authentication result information;

[0259] The verification module 630 is used to verify the first digital signature using the public key of the second authentication server;

[0260] The determination module 640 is used to determine the identity authentication result of the authentication access controller based on the first verification result in the first authentication result information if the verification is successful.

[0261] Optionally, the receiving module 620 is further configured to: receive a first message sent by the authentication access controller before the sending module 610 sends an identity message to the authentication access controller, wherein the first message includes a first random number generated by the authentication access controller; then the identity message also includes the first random number.

[0262] Optionally, the first message may also include security capability parameter information supported by the authentication access controller; the determining module 640 is further configured to: determine the specific security policy used by the requesting device based on the security capability parameter information; then the identity message may also include the specific security policy.

[0263] Optionally, the first message may further include the identity identifier of at least one authentication server trusted by the authentication access controller; the determining module 640 is further configured to: determine the identity identifier of at least one authentication server trusted by the requesting device based on the identity identifier of at least one authentication server trusted by the authentication access controller; then the identity message may further include the identity identifier of at least one authentication server trusted by the requesting device.

[0264] Optionally, the identity message sent by the sending module 610 may also include the identity identifier of at least one authentication server trusted by the requesting device.

[0265] Optionally, the identity message may further include the identity identifier of the requesting device and / or a second random number generated by the requesting device; then the third authentication response message may further include the identity identifier of the requesting device and / or the second random number; the verification module 630 is further configured to: verify the consistency between the identity identifier of the requesting device in the third authentication response message and the identity identifier of the requesting device itself before the determining module 640 determines the identity authentication result of the authentication access controller, and / or verify the consistency between the second random number in the third authentication response message and the second random number generated by the requesting device.

[0266] Optionally, the first authentication result information further includes the identity identifier of the authentication access controller; the verification module 630 is further configured to: verify the consistency between the identity identifier of the authentication access controller in the first authentication result information and the identity identifier of the authentication access controller carried in the third authentication response message before the determining module 640 determines the identity authentication result of the authentication access controller; or, verify the consistency between the identity identifier of the authentication access controller in the first authentication result information and the identity identifier of the authentication access controller carried in the first message.

[0267] Optionally, the message sent by the requesting device to the authentication access controller may also include a hash value calculated by the requesting device for the latest preceding message sent by the authentication access controller.

[0268] See Figure 7 This application also provides an authentication access controller 700, comprising:

[0269] The receiving module 710 is configured to receive an identity message sent by the requesting device, wherein the identity message includes the digital certificate of the requesting device;

[0270] The generation module 720 is used to generate the identity authentication code of the authentication access controller by using a pre-shared key of a first authentication server trusted by the authentication access controller and employing a cryptographic algorithm agreed upon with the first authentication server to calculate information including the digital certificate of the requesting device.

[0271] Sending module 730 is used to send a first authentication request message to the first authentication server, wherein the first authentication request message includes the digital certificate of the requesting device and the identity authentication code of the authentication access controller;

[0272] The receiving module 710 is further configured to receive a first authentication response message sent by the first authentication server. The first authentication response message includes first authentication result information, a first digital signature of the second authentication server trusted by the requesting device, second authentication result information, and a first message authentication code of the first authentication server. The first authentication result information includes a first verification result of the identity authentication code of the authentication access controller. The first digital signature is a digital signature calculated and generated by the second authentication server on signature data including the first authentication result information. The second authentication result information includes a second verification result of the digital certificate of the requesting device. The first message authentication code of the first authentication server is calculated and generated by the first authentication server using a pre-shared key with the authentication access controller and a cryptographic algorithm agreed upon with the authentication access controller on information including the second authentication result information.

[0273] Verification module 740 is used to verify the first message authentication code of the first authentication server using a pre-shared key with the first authentication server and a cryptographic algorithm agreed upon with the first authentication server. If the verification is successful, determination module 750 determines the identity authentication result of the requesting device based on the second verification result in the second authentication result information. When determination module 750 determines that the identity authentication result of the requesting device is valid, sending module 730 sends a third authentication response message to the requesting device; or...

[0274] Verification module 740 is used to verify the first message authentication code of the first authentication server using a pre-shared key with the first authentication server and a cryptographic algorithm agreed upon with the first authentication server. If the verification is successful, sending module 730 sends a third authentication response message to the requesting device, and determining module 750 determines the identity authentication result of the requesting device based on the second verification result in the second authentication result information; or...

[0275] The verification module 740 is used to verify the first message authentication code of the first authentication server using a pre-shared key with the first authentication server and a cryptographic algorithm agreed upon with the first authentication server; if the first message authentication code of the first authentication server is verified successfully, the determination module 750 determines the identity authentication result of the requesting device based on the second verification result in the second authentication result information; and the sending module 730 sends a third authentication response message to the requesting device.

[0276] The third authentication response message includes the first authentication result information and the first digital signature.

[0277] Optionally, the sending module 730 is further configured to: send a first message to the requesting device before the receiving module 710 receives the identity message sent by the requesting device, wherein the first message includes a first random number generated by the authentication access controller; then the identity message also includes the first random number.

[0278] The verification module 740 is further configured to: after the receiving module 710 receives the identity message, verify the consistency between the first random number in the identity message and the first random number generated by the authentication access controller.

[0279] Optionally, the first message further includes the identity identifier of at least one authentication server trusted by the authentication access controller; the identity message further includes the identity identifier of at least one authentication server trusted by the requesting device; the determining module 750 is further configured to: determine the first authentication server based on the identity identifier of at least one authentication server trusted by the requesting device in the identity message and the identity identifier of at least one authentication server trusted by the authentication access controller in the first message.

[0280] Optionally, the identity message may further include the identity identifier of at least one authentication server trusted by the requesting device; the determining module 750 is further configured to: determine the first authentication server based on the identity identifier of the at least one authentication server trusted by the requesting device and the identity identifier of the authentication server trusted by the authentication access controller.

[0281] Optionally, the first authentication request message further includes the identity identifier of the authentication access controller and / or the first random number generated by the authentication access controller; correspondingly, the first authentication response message further includes the identity identifier of the authentication access controller and / or the first random number; then the verification module 740 is further configured to: verify the consistency between the identity identifier of the authentication access controller in the first authentication response message and the identity identifier of the authentication access controller itself before the determining module 750 determines the authentication result of the requesting device, and / or verify the consistency between the first random number in the first authentication response message and the first random number generated by the authentication access controller.

[0282] Optionally, the identity message may also include the digital signature of the requesting device. In this case, the determining module 750 is specifically used to: determine whether the digital signature of the requesting device has been verified before the determining module 750 determines the identity authentication result of the requesting device; if the digital signature of the requesting device has been verified, then determine the identity authentication result of the requesting device based on the second verification result in the second authentication result information.

[0283] Optionally, the determining module 750 determines whether the digital signature of the requesting device has been verified, specifically including:

[0284] The second authentication server uses the digital certificate of the requesting device to verify the digital signature of the requesting device. If the receiving module 710 receives the first authentication response message, the determining module 750 determines that the digital signature of the requesting device has been verified successfully; or...

[0285] The determining module 750 verifies the digital signature of the requesting device using the digital certificate of the requesting device in the identity message, and determines whether the digital signature of the requesting device has passed verification based on the verification result; or...

[0286] When the second authentication result information also includes the digital certificate of the requesting device, the determining module 750 uses the digital certificate of the requesting device in the second authentication result information to verify the digital signature of the requesting device, and determines whether the digital signature of the requesting device has passed verification based on the verification result; or...

[0287] When the second authentication result information also includes the digital certificate of the requesting device, the determining module 750 verifies the consistency between the digital certificate of the requesting device in the second authentication result information and the digital certificate of the requesting device in the identity message; if they are consistent, the digital certificate of the requesting device is used to verify the digital signature of the requesting device, and the verification result is used to determine whether the digital signature of the requesting device has been verified.

[0288] Optionally, the message sent by the authentication access controller to the requesting device may further include a hash value calculated by the authentication access controller for the latest preamble message received from the requesting device; the message sent by the authentication access controller to the first authentication server may further include a hash value calculated by the authentication access controller for the latest preamble message received from the first authentication server.

[0289] See Figure 8 This application embodiment also provides a first authentication server 800, including:

[0290] The receiving module 810 is configured to receive a first authentication request message sent by the authentication access controller. The first authentication request message includes the digital certificate of the requesting device and the authentication code of the authentication access controller. The authentication code of the authentication access controller is generated by the authentication access controller using a pre-shared key with the first authentication server and employing a cryptographic algorithm agreed upon with the first authentication server to calculate information including the digital certificate of the requesting device.

[0291] The sending module 820 is configured to send a first authentication response message to the authentication access controller. The first authentication response message includes first authentication result information, a first digital signature of the second authentication server trusted by the requesting device, second authentication result information, and a first message authentication code of the first authentication server. The first authentication result information includes a first verification result of the authentication access controller's identity authentication code. The first digital signature is a digital signature calculated by the second authentication server on signature data including the first authentication result information. The second authentication result information includes a second verification result of the requesting device's digital certificate. The first message authentication code of the first authentication server is calculated by the first authentication server using a pre-shared key with the authentication access controller and a cryptographic algorithm agreed upon with the authentication access controller on information including the second authentication result information.

[0292] Optionally, the first authentication server 800 may also include:

[0293] The first verification module is used to verify the identity verification code of the authentication access controller to obtain a first verification result, and to verify the legality of the digital certificate of the requesting device to obtain a second verification result;

[0294] The first generation module is configured to generate the first authentication result information based on information including the first verification result, generate the second authentication result information based on information including the second verification result, calculate and generate the first message authentication code of the first authentication server based on information including the second authentication result information, and calculate and generate the first digital signature based on signature data including the first authentication result information.

[0295] The second generation module is used to generate the first authentication response message based on information including the first authentication result information, the first digital signature, the second authentication result information, and the first message authentication code.

[0296] Optionally, the first authentication server 800 may also include:

[0297] The second verification module is used to verify the identity verification code of the authentication access controller to obtain the first verification result;

[0298] The third generation module is used to generate the first authentication result information based on information including the first verification result, calculate and generate a second digital signature on the signature data including the first authentication result information and the digital certificate of the requesting device, or use a pre-shared key with the second authentication server and a cryptographic algorithm agreed upon with the second authentication server to calculate and generate a second message authentication code on the information including the first authentication result information and the digital certificate of the requesting device.

[0299] The sending module 820 is also configured to send a second authentication request message to the second authentication server, wherein the second authentication request message includes the first authentication result information, the digital certificate of the requesting device and the second digital signature, or the second authentication request message includes the first authentication result information, the digital certificate of the requesting device and the second message authentication code.

[0300] The receiving module 810 is further configured to receive a second authentication response message sent by the second authentication server, wherein the second authentication response message includes the first authentication result information, the first digital signature, the second authentication result information, and a third digital signature, or the second authentication response message includes the first authentication result information, the first digital signature, the second authentication result information, and a third message authentication code; the second authentication result information is generated by the second authentication server based on the second verification result obtained by verifying the digital certificate of the requesting device; the first digital signature is calculated and generated by the second authentication server based on the signature data including the first authentication result information; the third digital signature is calculated and generated by the second authentication server based on the signature data including the second authentication result information, or the third message authentication code is calculated and generated by the second authentication server using a pre-shared key with the first authentication server and a cryptographic algorithm agreed upon with the first authentication server based on the information including the second authentication result information;

[0301] The third verification module is used to verify the third digital signature using the public key of the second authentication server or to verify the third message authentication code using a pre-shared key with the second authentication server and a cryptographic algorithm agreed upon with the second authentication server.

[0302] The fourth generation module is used to calculate and generate the first message authentication code based on the information including the second authentication result information if the verification is successful, and to generate the first authentication response message based on the information including the first authentication result information, the first digital signature, the second authentication result information and the first message authentication code.

[0303] Optionally, the message sent by the first authentication server to the authentication access controller may also include a hash value calculated by the first authentication server for the latest preceding message received from the authentication access controller; the message sent by the first authentication server to the second authentication server may also include a hash value calculated by the first authentication server for the latest preceding message received from the second authentication server.

[0304] See Figure 9 This application embodiment also provides a second authentication server 900, including:

[0305] The receiving module 910 is configured to receive a second authentication request message sent by a first authentication server. The second authentication request message includes first authentication result information, a digital certificate of the requesting device, and a second digital signature; or the second authentication request message includes first authentication result information, a digital certificate of the requesting device, and a second message authentication code. The first authentication result information is generated by the first authentication server verifying the identity authentication code of the authentication access controller to obtain a first verification result, based on information including the first verification result. The second digital signature is calculated and generated by the first authentication server using signature data including the first authentication result information and the digital certificate of the requesting device; or the second message authentication code is calculated and generated by the first authentication server using a pre-shared key with the second authentication server and an agreed-upon cryptographic algorithm with the second authentication server, based on information including the first authentication result information and the digital certificate of the requesting device.

[0306] The verification module 920 is used to verify the second digital signature using the public key of the first authentication server or to verify the second message authentication code using a pre-shared key with the first authentication server and a cryptographic algorithm agreed upon with the first authentication server. If the verification is successful, the digital certificate of the requesting device is verified to obtain a second verification result.

[0307] The generation module 930 is used to generate second authentication result information based on information including the second verification result, calculate and generate a first digital signature on the signature data including the first authentication result information, calculate and generate a third digital signature on the signature data including the second authentication result information, or use a pre-shared key with the first authentication server and a cryptographic algorithm agreed with the first authentication server to calculate and generate a third message authentication code on the information including the second authentication result information.

[0308] The sending module 940 is used to send a second authentication response message to the first authentication server. The second authentication response message includes the first authentication result information, the first digital signature, the second authentication result information, and the third digital signature, or the second authentication response message includes the first authentication result information, the first digital signature, the second authentication result information, and the third message authentication code.

[0309] Optionally, the message sent by the second authentication server to the first authentication server may also include a hash value calculated by the second authentication server for the latest preceding message received from the first authentication server.

[0310] Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps of the above method embodiments. The aforementioned storage medium can be at least one of the following media: read-only memory (ROM), RAM, magnetic disk, or optical disk, etc., and other media capable of storing program code.

[0311] It should be noted that the various embodiments in this specification are described in a progressive manner, and the same or similar parts between the various embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, for the device and system embodiments, since they are consistent with and correspond to the method embodiments, the description is relatively simple, and relevant parts can be referred to the description of the method embodiments. The device and system embodiments described above are merely illustrative. The modules described as separate components may or may not be physically separate, and the components shown as modules may or may not be physical modules, that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment solution according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0312] The above description is merely one specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for identity verification, characterized in that, The method includes: The authentication access controller receives an identity message sent by the requesting device, the identity message including the digital certificate of the requesting device; The authentication access controller sends a first authentication request message to a first authentication server it trusts. The first authentication request message includes the digital certificate of the requesting device and the authentication code of the authentication access controller. The authentication code of the authentication access controller is generated by the authentication access controller using a pre-shared key with the first authentication server and a cryptographic algorithm agreed upon with the first authentication server to calculate information including the digital certificate of the requesting device. The authentication access controller receives a first authentication response message sent by the first authentication server. The first authentication response message includes first authentication result information, a first digital signature of the second authentication server trusted by the requesting device, second authentication result information, and a first message authentication code of the first authentication server. The first authentication result information includes a first verification result of the authentication access controller's identity authentication code. The first digital signature is a digital signature calculated by the second authentication server on signature data including the first authentication result information. The second authentication result information includes a second verification result of the requesting device's digital certificate. The first message authentication code of the first authentication server is calculated by the first authentication server using a pre-shared key with the authentication access controller and a cryptographic algorithm agreed upon with the authentication access controller on information including the second authentication result information. The authentication access controller uses a pre-shared key with the first authentication server and a cryptographic algorithm agreed upon with the first authentication server to verify the first message authentication code of the first authentication server. If the verification is successful, the authentication access controller determines the authentication result of the requesting device based on the second verification result in the second authentication result information. When the authentication access controller determines that the authentication result of the requesting device is valid, it sends a third authentication response message to the requesting device; or... The authentication access controller uses a pre-shared key with the first authentication server and a cryptographic algorithm agreed upon with the first authentication server to verify the first message authentication code of the first authentication server. If the verification is successful, the authentication access controller sends a third authentication response message to the requesting device and determines the authentication result of the requesting device based on the second verification result in the second authentication result information; or... The authentication access controller uses a pre-shared key with the first authentication server and employs a cryptographic algorithm agreed upon with the first authentication server to verify the first message authentication code of the first authentication server; if the first message authentication code of the first authentication server is verified successfully, the authentication access controller determines the identity authentication result of the requesting device based on the second verification result in the second authentication result information; the authentication access controller sends a third authentication response message to the requesting device. The third authentication response message includes the first authentication result information and the first digital signature; After receiving the third authentication response message, the requesting device uses the public key of the second authentication server to verify the first digital signature. If the verification is successful, the authentication result of the authentication access controller is determined according to the first verification result in the first authentication result information.

2. The method according to claim 1, characterized in that, Before the authentication access controller receives the identity message sent by the requesting device, the method further includes: The authentication access controller sends a first message to the requesting device, the first message including a first random number generated by the authentication access controller; The identity message also includes the first random number; After receiving the identity message, the authentication access controller verifies the consistency between the first random number in the identity message and the first random number generated by the authentication access controller. If the verification is successful, the authentication access controller will then send the first authentication request message again.

3. The method according to claim 2, characterized in that, The first message also includes security capability parameter information supported by the authentication access controller; the method further includes: The requesting device determines the specific security policy to be used by the requesting device based on the security capability parameter information; The identity message also includes the specific security policy.

4. The method according to claim 2, characterized in that, The first message also includes the identity identifier of at least one authentication server trusted by the authentication access controller; the method further includes: The requesting device determines the identity of at least one authentication server trusted by the authentication access controller based on the identity of at least one authentication server trusted by the requesting device. The identity message further includes the identity identifier of at least one authentication server trusted by the requesting device; the method further includes: The authentication access controller determines the first authentication server based on the identity identifier of at least one authentication server trusted by the requesting device in the identity message and the identity identifier of at least one authentication server trusted by the authentication access controller in the first message.

5. The method according to claim 1, characterized in that, The identity message also includes the identity identifier of at least one authentication server that the requesting device trusts; the method further includes: The authentication access controller determines the first authentication server based on the identity identifier of at least one authentication server trusted by the requesting device and the identity identifier of the authentication server trusted by the authentication access controller.

6. The method according to claim 2, characterized in that, The first authentication request message also includes the identity identifier of the authentication access controller and / or a first random number generated by the authentication access controller; Correspondingly, the first authentication response message also includes the identity identifier of the authentication access controller and / or the first random number; Before the authentication access controller determines the authentication result of the requesting device, the method further includes: The authentication access controller verifies the consistency between the authentication access controller's identity identifier in the first authentication response message and the authentication access controller's own identity identifier, and / or verifies the consistency between the first random number in the first authentication response message and the first random number generated by the authentication access controller. If the verification is successful, the authentication access controller then determines the identity authentication result of the requesting device based on the second verification result in the second authentication result information.

7. The method according to claim 2, characterized in that, The identity message also includes the identity identifier of the requesting device and / or a second random number generated by the requesting device; the third authentication response message also includes the identity identifier of the requesting device and / or the second random number; Before the requesting device determines the authentication result of the authentication access controller, the method further includes: The requesting device verifies the consistency between the identity identifier of the requesting device in the third authentication response message and the identity identifier of the requesting device itself, and / or verifies the consistency between the second random number in the third authentication response message and the second random number generated by the requesting device. If the verification is successful, the requesting device then determines the identity authentication result of the authentication access controller based on the first verification result in the first authentication result information.

8. The method according to claim 1, characterized in that, If the identity message also includes the digital signature of the requesting device, then before the authentication access controller determines the identity authentication result of the requesting device, the method further includes: The authentication access controller determines whether the digital signature of the requesting device has been verified. If the digital signature of the requesting device has been verified, the authentication access controller then determines the identity authentication result of the requesting device based on the second verification result in the second authentication result information.

9. The method according to claim 8, characterized in that, The authentication access controller determines whether the digital signature of the requesting device has been verified, specifically including: The second authentication server uses the digital certificate of the requesting device to verify the digital signature of the requesting device. If the authentication access controller receives the first authentication response message, the authentication access controller determines that the digital signature of the requesting device has been verified successfully; or... The authentication access controller verifies the digital signature of the requesting device using the digital certificate of the requesting device in the identity message, and determines whether the digital signature of the requesting device has passed verification based on the verification result; or... When the second authentication result information also includes the digital certificate of the requesting device, the authentication access controller uses the digital certificate of the requesting device in the second authentication result information to verify the digital signature of the requesting device, and determines whether the digital signature of the requesting device has passed verification based on the verification result; or... When the second authentication result information also includes the digital certificate of the requesting device, the authentication access controller verifies the consistency between the digital certificate of the requesting device in the second authentication result information and the digital certificate of the requesting device in the identity message; if they are consistent, the authentication access controller uses the digital certificate of the requesting device to verify the digital signature of the requesting device, and determines whether the digital signature of the requesting device has been verified based on the verification result.

10. The method according to claim 1, characterized in that, If the first authentication result information also includes the identity identifier of the authentication access controller, then before the requesting device determines the identity authentication result of the authentication access controller, the method further includes: The requesting device verifies the consistency between the identity identifier of the authentication access controller in the first authentication result information and the identity identifier of the authentication access controller carried in the third authentication response message; or... The requesting device verifies the consistency between the identity identifier of the authentication access controller in the first authentication result information and the identity identifier of the authentication access controller carried in the first message sent by the authentication access controller to the requesting device; If the verification is successful, the requesting device then determines the identity authentication result of the authentication access controller based on the first verification result in the first authentication result information.

11. The method according to any one of claims 1 to 10, characterized in that, The first authentication server trusted by the authentication access controller and the second authentication server trusted by the requesting device are the same authentication server; the method further includes: The first authentication server verifies the identity authentication code of the authentication access controller to obtain a first verification result, verifies the legality of the digital certificate of the requesting device to obtain a second verification result, generates the first authentication result information based on the information including the first verification result, generates the second authentication result information based on the information including the second verification result, calculates and generates the first message authentication code based on the information including the second authentication result information, calculates and generates the first digital signature based on the signature data including the first authentication result information, and generates the first authentication response message based on the information including the first authentication result information, the first digital signature, the second authentication result information, and the first message authentication code.

12. The method according to any one of claims 1 to 10, characterized in that, The first authentication server trusted by the authentication access controller and the second authentication server trusted by the requesting device are two different authentication servers; the method further includes: The first authentication server verifies the identity authentication code of the authentication access controller to obtain a first verification result, generates the first authentication result information based on the information including the first verification result, calculates and generates a second digital signature on the signature data including the first authentication result information and the digital certificate of the requesting device, or uses a pre-shared key with the second authentication server and adopts a cryptographic algorithm agreed with the second authentication server to calculate and generate a second message authentication code on the information including the first authentication result information and the digital certificate of the requesting device. The first authentication server sends a second authentication request message to the second authentication server. The second authentication request message includes the first authentication result information, the digital certificate of the requesting device, and the second digital signature, or the second authentication request message includes the first authentication result information, the digital certificate of the requesting device, and the second message authentication code. The second authentication server verifies the second digital signature using the public key of the first authentication server, or verifies the second message authentication code using a pre-shared key with the first authentication server and a cryptographic algorithm agreed upon with the first authentication server. If the verification is successful, the second authentication server verifies the legality of the digital certificate of the requesting device to obtain a second verification result. Based on the information including the second verification result, the second authentication result information is generated. The first digital signature is calculated on the signature data including the first authentication result information. The third digital signature is calculated on the signature data including the second authentication result information, or a third message authentication code is calculated on the information including the second authentication result information using a pre-shared key with the first authentication server and a cryptographic algorithm agreed upon with the first authentication server. The first authentication server receives a second authentication response message sent by the second authentication server. The second authentication response message includes the first authentication result information, the first digital signature, the second authentication result information, and the third digital signature, or the second authentication response message includes the first authentication result information, the first digital signature, the second authentication result information, and the third message authentication code. The first authentication server verifies the third digital signature using the public key of the second authentication server, or the first authentication server verifies the third message authentication code using a pre-shared key with the second authentication server and a cryptographic algorithm agreed upon with the second authentication server. If the verification is successful, the first authentication server calculates and generates the first message authentication code based on the information including the second authentication result information, and generates the first authentication response message based on the information including the first authentication result information, the first digital signature, the second authentication result information, and the first message authentication code.

13. The method according to any one of claims 1 to 10, characterized in that, The message sent by the requesting device to the authentication access controller also includes a hash value calculated by the requesting device for the latest preceding message received from the authentication access controller; When the authentication access controller receives a message from the requesting device, it first verifies the hash value in the received message, and then performs subsequent operations after the verification is successful. The message sent by the authentication access controller to the requesting device also includes a hash value calculated by the authentication access controller for the latest preceding message sent by the requesting device. When the requesting device receives a message from the authentication access controller, it first verifies the hash value in the received message, and then performs subsequent operations after the verification is successful. The message sent by the authentication access controller to the first authentication server also includes a hash value calculated by the authentication access controller for the latest preceding message received from the first authentication server; When the first authentication server receives a message from the authentication access controller, it first verifies the hash value in the received message, and then performs subsequent operations after the verification is successful. The message sent by the first authentication server to the authentication access controller also includes a hash value calculated by the first authentication server for the latest preceding message sent by the authentication access controller. When the authentication access controller receives a message from the first authentication server, it first verifies the hash value in the received message, and then performs subsequent operations after the verification is successful. The message sent by the first authentication server to the second authentication server also includes a hash value calculated by the first authentication server for the latest preceding message received from the second authentication server; When the second authentication server receives a message from the first authentication server, it first verifies the hash value in the received message, and then performs subsequent operations after the verification is successful. The message sent by the second authentication server to the first authentication server also includes a hash value calculated by the second authentication server for the latest preceding message sent by the first authentication server. When the first authentication server receives a message from the second authentication server, it first verifies the hash value in the received message, and then performs subsequent operations after the verification is successful.

14. A requesting device, characterized in that, The requesting device includes: The sending module is used to send an identity message to the authentication access controller, the identity message including the digital certificate of the requesting device; The receiving module is configured to receive a third authentication response message sent by the authentication access controller, the third authentication response message including first authentication result information and a first digital signature; the first authentication result information includes a first verification result of the authentication access controller's identity authentication code, and the first digital signature is a digital signature calculated by the second authentication server trusted by the requesting device on signature data including the first authentication result information; The verification module is used to verify the first digital signature using the public key of the second authentication server; The determination module is used to determine the identity authentication result of the authentication access controller based on the first verification result in the first authentication result information if the verification is successful.

15. The requesting device according to claim 14, characterized in that, The receiving module is further configured to: receive a first message sent by the authentication access controller before the sending module sends an identity message to the authentication access controller, wherein the first message includes a first random number generated by the authentication access controller; The identity message then also includes the first random number.

16. The requesting device according to claim 15, characterized in that, The first message also includes security capability parameter information supported by the authentication access controller; The determining module is further configured to: determine the specific security policy used by the requesting device based on the security capability parameter information; The identity message also includes the specific security policy.

17. The requesting device according to claim 15, characterized in that, The first message also includes the identity identifier of at least one authentication server trusted by the authentication access controller; The determining module is further configured to: determine the identity identifier of at least one authentication server trusted by the requesting device based on the identity identifier of at least one authentication server trusted by the authentication access controller; The identity message also includes the identity identifier of at least one authentication server trusted by the requesting device.

18. The requesting device according to claim 14, characterized in that, The identity message sent by the sending module also includes the identity identifier of at least one authentication server trusted by the requesting device.

19. The requesting device according to claim 15, characterized in that, The identity message further includes the identity identifier of the requesting device and / or a second random number generated by the requesting device; therefore, the third authentication response message further includes the identity identifier of the requesting device and / or the second random number. The verification module is further configured to: verify the consistency between the identity identifier of the requesting device in the third authentication response message and the identity identifier of the requesting device itself before the determining module determines the identity authentication result of the authentication access controller, and / or verify the consistency between the second random number in the third authentication response message and the second random number generated by the requesting device.

20. The requesting device according to claim 14, characterized in that, The first authentication result information also includes the identity identifier of the authentication access controller; The verification module is further configured to: verify the consistency between the identity identifier of the authentication access controller in the first authentication result information and the identity identifier of the authentication access controller carried in the third authentication response message before the determining module determines the identity authentication result of the authentication access controller; or, The verification module is further configured to: verify the consistency between the identity identifier of the authentication access controller in the first authentication result information and the identity identifier of the authentication access controller carried in the first message sent by the authentication access controller before the determining module determines the identity authentication result of the authentication access controller.

21. The requesting device according to any one of claims 14 to 20, characterized in that, The message sent by the requesting device to the authentication access controller also includes a hash value calculated by the requesting device for the latest preceding message received from the authentication access controller.

22. An authentication access controller, characterized in that, The authentication access controller includes: The receiving module is used to receive an identity message sent by the requesting device, wherein the identity message includes the digital certificate of the requesting device; The generation module is used to calculate and generate the identity verification code of the authentication access controller by using a pre-shared key of a first authentication server trusted by the authentication access controller and employing a cryptographic algorithm agreed upon with the first authentication server, including the digital certificate of the requesting device. The sending module is used to send a first authentication request message to the first authentication server, wherein the first authentication request message includes the digital certificate of the requesting device and the identity authentication code of the authentication access controller; The receiving module is further configured to receive a first authentication response message sent by the first authentication server. The first authentication response message includes first authentication result information, a first digital signature of the second authentication server trusted by the requesting device, second authentication result information, and a first message authentication code of the first authentication server. The first authentication result information includes a first verification result of the identity authentication code of the authentication access controller. The first digital signature is a digital signature calculated and generated by the second authentication server on signature data including the first authentication result information. The second authentication result information includes a second verification result of the digital certificate of the requesting device. The first message authentication code of the first authentication server is calculated and generated by the first authentication server using a pre-shared key with the authentication access controller and a cryptographic algorithm agreed upon with the authentication access controller on information including the second authentication result information. The verification module is used to verify the first message authentication code of the first authentication server using a pre-shared key with the first authentication server and a cryptographic algorithm agreed upon with the first authentication server. If the verification is successful, the determining module determines the identity authentication result of the requesting device based on the second verification result in the second authentication result information. When the determining module determines that the identity authentication result of the requesting device is valid, the sending module sends a third authentication response message to the requesting device; or... The sending module uses a pre-shared key with the first authentication server and an agreed-upon cryptographic algorithm to verify the first message authentication code of the first authentication server. If the verification is successful, the sending module sends a third authentication response message to the requesting device, and the determining module determines the authentication result of the requesting device based on the second verification result in the second authentication result information; or... The module is used to verify the first message authentication code of the first authentication server using a pre-shared key with the first authentication server and a cryptographic algorithm agreed upon with the first authentication server; if the first message authentication code of the first authentication server is verified, the determining module determines the identity authentication result of the requesting device based on the second verification result in the second authentication result information; the sending module sends a third authentication response message to the requesting device. The third authentication response message includes the first authentication result information and the first digital signature.

23. The authentication access controller according to claim 22, characterized in that, The sending module is further configured to: send a first message to the requesting device before the receiving module receives the identity message sent by the requesting device, wherein the first message includes a first random number generated by the authentication access controller; The identity message also includes the first random number; The verification module is further configured to: after the receiving module receives the identity message, verify the consistency between the first random number in the identity message and the first random number generated by the authentication access controller.

24. The authentication access controller according to claim 23, characterized in that, The first message also includes the identity identifier of at least one authentication server trusted by the authentication access controller; The identity message also includes the identity identifier of at least one authentication server trusted by the requesting device; The determining module is further configured to: determine the first authentication server based on the identity identifier of at least one authentication server trusted by the requesting device in the identity message and the identity identifier of at least one authentication server trusted by the authentication access controller in the first message.

25. The authentication access controller according to claim 22, characterized in that, The identity message also includes the identity identifier of at least one authentication server trusted by the requesting device; The determining module is further configured to: determine the first authentication server based on the identity identifier of at least one authentication server trusted by the requesting device and the identity identifier of the authentication server trusted by the authentication access controller.

26. The authentication access controller according to claim 23, characterized in that, The first authentication request message also includes the identity identifier of the authentication access controller and / or a first random number generated by the authentication access controller; Correspondingly, the first authentication response message also includes the identity identifier of the authentication access controller and / or the first random number; The verification module is further configured to: verify the consistency between the identity identifier of the authentication access controller in the first authentication response message and the identity identifier of the authentication access controller itself before the determining module determines the identity authentication result of the requesting device, and / or verify the consistency between the first random number in the first authentication response message and the first random number generated by the authentication access controller.

27. The authentication access controller according to claim 22, characterized in that, If the identity message also includes the digital signature of the requesting device, then the determining module is specifically used for: Before the determining module determines the identity authentication result of the requesting device, it determines whether the digital signature of the requesting device has been verified. If the digital signature of the requesting device has been verified, the identity authentication result of the requesting device is then determined according to the second verification result in the second authentication result information.

28. The authentication access controller according to claim 27, characterized in that, The determination module determines whether the digital signature of the requesting device has been verified, specifically including: The second authentication server uses the digital certificate of the requesting device to verify the digital signature of the requesting device. If the receiving module receives the first authentication response message, the determining module determines that the digital signature of the requesting device has been verified successfully; or... The determining module uses the digital certificate of the requesting device in the identity message to verify the digital signature of the requesting device, and determines whether the digital signature of the requesting device has passed verification based on the verification result; or... When the second authentication result information also includes the digital certificate of the requesting device, the determining module uses the digital certificate of the requesting device in the second authentication result information to verify the digital signature of the requesting device, and determines whether the digital signature of the requesting device has passed verification based on the verification result; or... When the second authentication result information also includes the digital certificate of the requesting device, the determining module verifies the consistency between the digital certificate of the requesting device in the second authentication result information and the digital certificate of the requesting device in the identity message; if they are consistent, the digital certificate of the requesting device is used to verify the digital signature of the requesting device, and the verification result is used to determine whether the digital signature of the requesting device has been verified.

29. The authentication access controller according to any one of claims 22 to 28, characterized in that, The message sent by the authentication access controller to the requesting device also includes a hash value calculated by the authentication access controller for the latest preamble message received from the requesting device; the message sent by the authentication access controller to the first authentication server also includes a hash value calculated by the authentication access controller for the latest preamble message received from the first authentication server.

30. A first authentication server, characterized in that, The first authentication server is a first authentication server trusted by the authentication access controller, and the first authentication server includes: The receiving module is configured to receive a first authentication request message sent by the authentication access controller. The first authentication request message includes the digital certificate of the requesting device and the authentication code of the authentication access controller. The authentication code of the authentication access controller is generated by the authentication access controller using a pre-shared key with the first authentication server and employing a cryptographic algorithm agreed upon with the first authentication server to calculate information including the digital certificate of the requesting device. The sending module is configured to send a first authentication response message to the authentication access controller. The first authentication response message includes first authentication result information, a first digital signature of the second authentication server trusted by the requesting device, second authentication result information, and a first message authentication code of the first authentication server. The first authentication result information includes a first verification result of the authentication access controller's identity authentication code. The first digital signature is a digital signature calculated by the second authentication server on signature data including the first authentication result information. The second authentication result information includes a second verification result of the requesting device's digital certificate. The first message authentication code of the first authentication server is calculated by the first authentication server using a pre-shared key with the authentication access controller and a cryptographic algorithm agreed upon with the authentication access controller on information including the second authentication result information.

31. The first authentication server according to claim 30, characterized in that, The first authentication server also includes: The first verification module is used to verify the identity verification code of the authentication access controller to obtain a first verification result, and to verify the legality of the digital certificate of the requesting device to obtain a second verification result; The first generation module is configured to generate the first authentication result information based on information including the first verification result, generate the second authentication result information based on information including the second verification result, calculate and generate the first message authentication code of the first authentication server based on information including the second authentication result information, and calculate and generate the first digital signature based on signature data including the first authentication result information. The second generation module is used to generate the first authentication response message based on information including the first authentication result information, the first digital signature, the second authentication result information, and the first message authentication code.

32. The first authentication server according to claim 30, characterized in that, The first authentication server also includes: The second verification module is used to verify the identity verification code of the authentication access controller to obtain a first verification result; The third generation module is used to generate the first authentication result information based on information including the first verification result, calculate and generate a second digital signature on the signature data including the first authentication result information and the digital certificate of the requesting device, or use a pre-shared key with the second authentication server and a cryptographic algorithm agreed upon with the second authentication server to calculate and generate a second message authentication code on the information including the first authentication result information and the digital certificate of the requesting device. The sending module is further configured to send a second authentication request message to the second authentication server, wherein the second authentication request message includes the first authentication result information, the digital certificate of the requesting device and the second digital signature, or the second authentication request message includes the first authentication result information, the digital certificate of the requesting device and the second message authentication code. The receiving module is further configured to receive a second authentication response message sent by the second authentication server, wherein the second authentication response message includes the first authentication result information, the first digital signature, the second authentication result information, and a third digital signature, or the second authentication response message includes the first authentication result information, the first digital signature, the second authentication result information, and a third message authentication code; the second authentication result information is generated by the second authentication server based on the second verification result obtained by verifying the digital certificate of the requesting device; the first digital signature is calculated and generated by the second authentication server based on the signature data including the first authentication result information; the third digital signature is calculated and generated by the second authentication server based on the signature data including the second authentication result information, or the third message authentication code is calculated and generated by the second authentication server using a pre-shared key with the first authentication server and a cryptographic algorithm agreed upon with the first authentication server based on the information including the second authentication result information; The third verification module is used to verify the third digital signature using the public key of the second authentication server or to verify the third message authentication code using a pre-shared key with the second authentication server and a cryptographic algorithm agreed upon with the second authentication server. The fourth generation module is used to calculate and generate the first message authentication code based on the information including the second authentication result information if the verification is successful, and to generate the first authentication response message based on the information including the first authentication result information, the first digital signature, the second authentication result information and the first message authentication code.

33. The first authentication server according to any one of claims 30 to 32, characterized in that, The message sent by the first authentication server to the authentication access controller also includes a hash value calculated by the first authentication server for the latest preamble message received from the authentication access controller; the message sent by the first authentication server to the second authentication server also includes a hash value calculated by the first authentication server for the latest preamble message received from the second authentication server.

34. A second authentication server, characterized in that, The second authentication server is the second authentication server that requests device trust, and the first authentication server is the first authentication server that authenticates access controller trust. The second authentication server includes: The receiving module is configured to receive a second authentication request message sent by a first authentication server. The second authentication request message includes first authentication result information, a digital certificate of the requesting device, and a second digital signature; or the second authentication request message includes first authentication result information, a digital certificate of the requesting device, and a second message authentication code. The first authentication result information is generated by the first authentication server verifying the identity authentication code of the authentication access controller to obtain a first verification result, based on information including the first verification result. The second digital signature is calculated and generated by the first authentication server using signature data including the first authentication result information and the digital certificate of the requesting device, or the second message authentication code is calculated and generated by the first authentication server using a pre-shared key with the second authentication server and an agreed-upon cryptographic algorithm with the second authentication server, based on information including the first authentication result information and the digital certificate of the requesting device. The verification module is used to verify the second digital signature using the public key of the first authentication server or to verify the second message authentication code using a pre-shared key with the first authentication server and a cryptographic algorithm agreed upon with the first authentication server. If the verification is successful, the module performs a legality verification on the digital certificate of the requesting device to obtain a second verification result. The generation module is used to generate second authentication result information based on information including the second verification result, calculate and generate a first digital signature on signature data including the first authentication result information, calculate and generate a third digital signature on signature data including the second authentication result information, or use a pre-shared key with the first authentication server and a cryptographic algorithm agreed upon with the first authentication server to calculate and generate a third message authentication code on information including the second authentication result information. The sending module is used to send a second authentication response message to the first authentication server. The second authentication response message includes the first authentication result information, the first digital signature, the second authentication result information, and the third digital signature, or the second authentication response message includes the first authentication result information, the first digital signature, the second authentication result information, and the third message authentication code.

35. The second authentication server according to claim 34, characterized in that, The message sent by the second authentication server to the first authentication server also includes a hash value calculated by the second authentication server for the latest preceding message received from the first authentication server.

Citation Information

Patent Citations

  • Downloading method, management method, downloading management method, downloading management device and downloading management system for secret key

    CN103220271A

  • An access authentication method suitable for wired and wireless network

    CN1668005A