Identity authentication method, apparatus and system, communication device and storage medium

By pre-generating and asynchronously sending verification codes and validators on the server, the problem of terminal waiting and excessive server resource utilization in digital car key authentication is solved, and the efficiency and performance of identity verification are improved.

WO2024234901A1PCT designated stage expired Publication Date: 2024-11-21XIAOMI EV TECH CO LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2024/088107
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-15
Filing Date
2024-04-16
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

The existing digital car key authentication method can easily lead to an increase in waiting time when the terminal obtains verification code, resulting in request timeout, and excessive use of thread resources on the server side, resulting in performance pressure and stability problems.

Method used

The verification code and validator are generated by the server, and thread resources are released when a low load state is detected, and verification code and validator are sent asynchronously to the terminal and the vehicle, reducing terminal waiting time and alleviating thread blockage on the server.

Benefits of technology

It effectively reduces the waiting time for terminals to obtain verification codes, reduces the frequency of request timeout, alleviates the pressure of thread resource occupation on the server, and improves the efficiency and performance of authentication.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024088107_21112024_PF_FP_ABST
    Figure CN2024088107_21112024_PF_FP_ABST
Patent Text Reader

Abstract

The present disclosure relates to an identity authentication method, apparatus and system, a communication device and a storage medium. The identity authentication method executed by a server comprises: receiving an authentication code acquisition request sent by a terminal; sending an authentication code to the terminal, the authentication code being used for identity authentication between the terminal and a vehicle; releasing a first thread resource, the first thread resource being used for maintaining connection between the terminal and the server; and sending to the vehicle an authenticator for authenticating the authentication code. In this way, the waiting time when the terminal acquires the authentication code can be reduced, and the performance pressure of a server is relieved.
Need to check novelty before this filing date? Find Prior Art

Description

Authentication method, device, communication equipment, system and storage medium

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This disclosure claims priority to Chinese patent application number 202310546508.0, filed with the China Patent Office on May 15, 2023, entitled “Authentication Method, Apparatus, Communication Equipment, System and Storage Medium,” the entire contents of which are incorporated by reference into this disclosure. Technical Field

[0003] The present disclosure relates to the field of communication technologies, and in particular to an identity authentication method, apparatus, communication equipment, system, and storage medium. Background Art

[0004] Unlike traditional car keys, digital car keys can be maintained in the terminal and can realize functions such as vehicle entry, starting, parking, and air conditioning control. When generating or using digital car keys, identity authentication may be required between the owner's device, cloud services, and vehicles.

[0005] Summary of the Invention

[0006] The embodiments of the present disclosure provide an identity authentication method, apparatus, communication device, system, and storage medium.

[0007] According to a first aspect of an embodiment of the present disclosure, an identity authentication method is proposed, which is performed by a server. The method includes:

[0008] Receiving the verification code acquisition request sent by the terminal;

[0009] Sending a verification code to the terminal, the verification code being used for identity authentication between the terminal and the vehicle;

[0010] releasing a first thread resource, where the first thread resource is used to maintain a connection between the terminal and the server;

[0011] A verifier for verifying the verification code is sent to the vehicle.

[0012] According to a second aspect of an embodiment of the present disclosure, an identity authentication method is provided, which is performed by a terminal. The method includes:

[0013] Send a verification code acquisition request to the server;

[0014] Receiving a verification code sent by the server, the verification code being used for identity authentication between the terminal and the vehicle;

[0015] The server releases a first thread resource and sends a verifier for verifying the verification code to the vehicle. The first thread resource is used to maintain the connection between the terminal and the server.

[0016] According to a third aspect of an embodiment of the present disclosure, an identity authentication method is provided, including:

[0017] The terminal sends a verification code acquisition request to the server;

[0018] The server receives the verification code acquisition request;

[0019] The server sends a verification code to the terminal, and the verification code is used for identity authentication between the terminal and the vehicle;

[0020] The terminal receives the verification code sent by the server;

[0021] The server releases a first thread resource, where the first thread resource is used to maintain a connection between the terminal and the server;

[0022] The service end sends a verifier for verifying the verification code to the vehicle.

[0023] According to a fourth aspect of an embodiment of the present disclosure, a first identity authentication device is provided, which is applied to a server and includes:

[0024] A first receiving module is configured to receive a verification code acquisition request sent by a terminal;

[0025] a first sending module, configured to send a verification code to the terminal, wherein the verification code is used for identity authentication between the terminal and the vehicle;

[0026] A first execution module is configured to release a first thread resource, where the first thread resource is used to maintain a connection between the terminal and the server;

[0027] The second sending module is configured to send a verifier for verifying the verification code to the vehicle.

[0028] According to a fifth aspect of an embodiment of the present disclosure, a second identity authentication device is provided, which is applied to a terminal and includes:

[0029] A third sending module is configured to send a verification code acquisition request to the server;

[0030] a second receiving module, configured to receive a verification code sent by the server, the verification code being used for identity authentication between the terminal and the vehicle;

[0031] The server releases a first thread resource and sends a verifier for verifying the verification code to the vehicle. The first thread resource is used to maintain the connection between the terminal and the server.

[0032] According to a sixth aspect of an embodiment of the present disclosure, a communication device is provided, including:

[0033] one or more processors;

[0034] The processor is configured to call computer instructions to enable the communication device to execute the identity authentication method described in any one of the first and second aspects.

[0035] According to the seventh aspect of an embodiment of the present disclosure, an identity authentication system is proposed, comprising a terminal, a server, and a vehicle, wherein the server is configured to implement the identity authentication method described in any one of the first aspects above, the terminal is configured to implement the identity authentication method described in any one of the second aspects above, and the vehicle is configured to receive a verifier sent by the server, and to perform identity authentication with the terminal through the verifier.

[0036] According to the eighth aspect of an embodiment of the present disclosure, a computer-readable storage medium is proposed, wherein the computer-readable storage medium stores computer instructions. When the computer instructions are executed on a communication device, the communication device executes the identity authentication method as described in any one of the above-mentioned first and second aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following drawings required for describing the embodiments are introduced. The following drawings are merely some embodiments of the present disclosure and do not impose specific limitations on the protection scope of the present disclosure.

[0038] FIG1 is a flowchart illustrating an identity authentication process according to an embodiment of the present disclosure.

[0039] FIG2 is an interactive diagram illustrating an identity authentication method according to an embodiment of the present disclosure.

[0040] FIG3 is a flow chart showing an identity authentication method according to an embodiment of the present disclosure.

[0041] FIG4 is a flow chart showing an identity authentication method according to an embodiment of the present disclosure.

[0042] FIG5 is a flow chart showing an identity authentication method according to an embodiment of the present disclosure.

[0043] FIG6 is a flow chart showing an identity authentication method according to an embodiment of the present disclosure.

[0044] FIG7 is a flow chart showing an identity authentication method according to an embodiment of the present disclosure.

[0045] FIG8 is a schematic structural diagram of a first identity authentication device according to an embodiment of the present disclosure.

[0046] FIG9 is a schematic structural diagram of a second identity authentication device according to an embodiment of the present disclosure.

[0047] FIG10 is a schematic structural diagram of a communication device 8100 according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0048] In order to improve the user experience of digital car key pairing scenarios, the embodiments of the present disclosure propose an identity authentication method, apparatus, communication device, system and storage medium.

[0049] In a first aspect, an embodiment of the present disclosure provides an identity authentication method, which is performed by a server, and the method includes:

[0050] Receiving the verification code acquisition request sent by the terminal;

[0051] Sending a verification code to the terminal, the verification code being used for identity authentication between the terminal and the vehicle;

[0052] releasing a first thread resource, where the first thread resource is used to maintain a connection between the terminal and the server;

[0053] A verifier for verifying the verification code is sent to the vehicle.

[0054] In the above embodiment, the server can receive a verification code acquisition request sent by the terminal, send a verification code for identity authentication with the vehicle to the terminal, and release the first thread resource. In this way, the waiting time for the terminal to obtain the verification code can be reduced, which helps to reduce the request timeout phenomenon. Moreover, by releasing the first thread resource, the thread congestion phenomenon on the server can be alleviated, thereby alleviating the performance pressure on the server. In addition, the server can also send a verifier to the vehicle so that the vehicle can verify the verification code of the terminal according to the verifier, thereby performing identity authentication between the terminal and the vehicle.

[0055] In conjunction with some embodiments of the first aspect, in some embodiments, the method includes:

[0056] determining that the vehicle successfully receives the validator;

[0057] A message indicating that the verification code is available is sent to the terminal.

[0058] In the above embodiment, the server can send the verification code to the terminal without waiting for the vehicle to successfully receive the authenticator. After confirming that the vehicle has successfully received the authenticator, the server can send a message to the terminal indicating that the verification code is available. Therefore, the above embodiment can reduce the waiting time for the terminal to obtain the verification code, which helps to reduce request timeouts. In addition, the asynchronous notification method of the terminal that the verification code is available also allows the server to release the first thread resources after sending the verification code. This can alleviate thread congestion on the server side, thereby alleviating the performance pressure on the server side.

[0059] In conjunction with some embodiments of the first aspect, in some embodiments, sending a message to the terminal indicating that the verification code is available includes:

[0060] Sending a message indicating that the verification code is available to the terminal through a publish-subscribe mode; or,

[0061] A communication connection is established with the terminal, and a message indicating that the verification code is available is sent to the terminal through the established communication connection.

[0062] In the above embodiment, the server may send a message indicating that the verification code is available to the terminal through a publish-subscribe mode or by establishing a communication connection with the terminal.

[0063] In conjunction with some embodiments of the first aspect, in some embodiments, sending a message indicating that the verification code is available to the terminal through the established communication connection includes:

[0064] The interface of the terminal is called back, and a message indicating that the verification code is available is sent to the terminal.

[0065] In the above embodiment, the server may establish a communication connection with the terminal, and send a message indicating that the verification code is available to the terminal by calling back the interface of the terminal.

[0066] In conjunction with some embodiments of the first aspect, in some embodiments, the method includes:

[0067] The verification code and the verifier are generated in advance.

[0068] In the above embodiment, the server can pre-generate the verification code and authenticator. Compared with the method of generating the verification code and authenticator after receiving the verification code acquisition request from the terminal, the method in the above embodiment helps to quickly determine the verification code of the terminal and shorten the time the terminal waits for the verification code.

[0069] In conjunction with some embodiments of the first aspect, in some embodiments, pre-generating the verification code and the verifier includes:

[0070] Determine that the server load value is below the load threshold;

[0071] Generate the verification code and the verifier.

[0072] In the above embodiment, the server can pre-generate the verification code and authenticator during a period of low load. In this way, when receiving a verification code acquisition request from a terminal, the terminal's verification code can be quickly determined, thereby helping to shorten the time the terminal waits for the verification code.

[0073] In conjunction with some embodiments of the first aspect, in some embodiments, sending a verification code to the terminal includes:

[0074] determining a set of unused verification codes from pre-generated verification codes;

[0075] Sending the unused verification code to the terminal.

[0076] In the above embodiment, the server can determine a set of unused verification codes from the pre-generated verification codes and send the unused verification codes to the terminal. The above embodiment can quickly determine the terminal's verification code by pre-generating the verification code, which helps to shorten the time the terminal waits for the verification code.

[0077] In a second aspect, an embodiment of the present disclosure provides an identity authentication method, performed by a terminal, the method comprising:

[0078] Send a verification code acquisition request to the server;

[0079] Receiving a verification code sent by the server, the verification code being used for identity authentication between the terminal and the vehicle;

[0080] The server releases a first thread resource and sends a verifier for verifying the verification code to the vehicle. The first thread resource is used to maintain the connection between the terminal and the server.

[0081] In the above embodiment, the terminal can send a verification code acquisition request to the server, and the server can receive the verification code acquisition request sent by the terminal, send a verification code for identity authentication with the vehicle to the terminal, and release the first thread resource. In this way, the waiting time for the terminal to obtain the verification code can be reduced, which helps to reduce the request timeout phenomenon. Moreover, by releasing the first thread resource, the thread congestion phenomenon on the server can be alleviated, thereby alleviating the performance pressure on the server. In addition, the server can also send a verifier to the vehicle so that the vehicle can verify the verification code of the terminal according to the verifier, thereby performing identity authentication between the terminal and the vehicle.

[0082] In conjunction with some embodiments of the second aspect, in some embodiments, the method includes:

[0083] Perform configuration operations on the terminal according to the received verification code.

[0084] In the above embodiment, the terminal can configure itself based on the received verification code while waiting for the vehicle to successfully receive the authenticator. This allows the configuration process and the vehicle to receive the authenticator to proceed in parallel, improving time efficiency and enhancing the efficiency of the identity verification process between the terminal and the vehicle.

[0085] In conjunction with some embodiments of the second aspect, in some embodiments, the terminal performs identity authentication with the vehicle via Bluetooth, and the configuring operation on the terminal according to the received verification code includes:

[0086] The verification code is loaded into the Bluetooth cache.

[0087] In the above embodiment, the terminal can load the verification code into the Bluetooth cache while waiting for the vehicle to successfully receive the authenticator. In this way, the process of loading the verification code into the Bluetooth cache and the process of the vehicle receiving the authenticator can be carried out in parallel, thereby improving time utilization and helping to improve the efficiency of the identity verification process between the terminal and the vehicle.

[0088] In conjunction with some embodiments of the second aspect, in some embodiments, the method includes:

[0089] obtaining a message indicating that the verification code is available, the service generating the message after determining that the vehicle successfully receives the authenticator;

[0090] Authentication is performed with the vehicle based on the verification code.

[0091] In the above embodiment, the server can send the verification code to the terminal without waiting for the vehicle to successfully receive the authenticator. After confirming that the vehicle has successfully received the authenticator, the server can send a message to the terminal indicating that the verification code is available. Therefore, the above embodiment can reduce the waiting time for the terminal to obtain the verification code, helping to reduce request timeouts.

[0092] In conjunction with some embodiments of the second aspect, in some embodiments, obtaining a message indicating that the verification code is available includes:

[0093] Acquire the message indicating that the verification code is available through a publish-subscribe mode; or,

[0094] Establishing a communication connection with the server, and receiving a message sent by the server through the established communication connection to indicate that the verification code is available.

[0095] In the above embodiment, the terminal may obtain the message indicating that the verification code is available through a publish-subscribe mode or by establishing a communication connection with the server.

[0096] In a third aspect, an embodiment of the present disclosure provides an identity authentication method, including:

[0097] The terminal sends a verification code acquisition request to the server;

[0098] The server receives the verification code acquisition request;

[0099] The server sends a verification code to the terminal, and the verification code is used for identity authentication between the terminal and the vehicle;

[0100] The terminal receives the verification code sent by the server;

[0101] The server releases a first thread resource, where the first thread resource is used to maintain a connection between the terminal and the server;

[0102] The service end sends a verifier for verifying the verification code to the vehicle.

[0103] In a fourth aspect, an embodiment of the present disclosure provides a first identity authentication device, applied to a server, comprising:

[0104] A first receiving module is configured to receive a verification code acquisition request sent by a terminal;

[0105] a first sending module, configured to send a verification code to the terminal, wherein the verification code is used for identity authentication between the terminal and the vehicle;

[0106] A first execution module is configured to release a first thread resource, where the first thread resource is used to maintain a connection between the terminal and the server;

[0107] The second sending module is configured to send a verifier for verifying the verification code to the vehicle.

[0108] Optionally include:

[0109] a first determination module configured to determine whether the vehicle successfully receives the validator;

[0110] The fourth sending module is configured to send a message to the terminal indicating that the verification code is available.

[0111] Optionally, the fourth sending module includes:

[0112] A first sending submodule is configured to send a message indicating that the verification code is available to the terminal through a publish-subscribe mode; or

[0113] The second sending submodule is configured to establish a communication connection with the terminal, and send a message indicating that the verification code is available to the terminal through the established communication connection.

[0114] Optionally, the second sending submodule includes:

[0115] The first sending subunit is configured to call back the interface of the terminal and send a message to the terminal indicating that the verification code is available.

[0116] Optionally include:

[0117] The first generating module is configured to pre-generate the verification code and the verifier.

[0118] Optionally, the first generating module includes:

[0119] A first determining submodule is configured to determine whether the load value of the server is lower than a load threshold;

[0120] The first generating submodule is configured to generate the verification code and the verifier.

[0121] Optionally, the first sending module includes:

[0122] a second determining submodule, configured to determine a group of unused verification codes from pre-generated verification codes;

[0123] The third sending submodule is configured to send the unused verification code to the terminal.

[0124] In a fifth aspect, an embodiment of the present disclosure provides a second identity authentication device, applied to a terminal, comprising:

[0125] A third sending module is configured to send a verification code acquisition request to the server;

[0126] a second receiving module, configured to receive a verification code sent by the server, the verification code being used for identity authentication between the terminal and the vehicle;

[0127] The server releases a first thread resource and sends a verifier for verifying the verification code to the vehicle. The first thread resource is used to maintain the connection between the terminal and the server.

[0128] Optionally include:

[0129] The second execution module is configured to perform configuration operations on the terminal according to the received verification code.

[0130] Optionally, the terminal performs identity authentication with the vehicle via Bluetooth, and the second execution module includes:

[0131] The first loading submodule is configured to load the verification code into the Bluetooth cache.

[0132] Optionally include:

[0133] an acquisition module configured to acquire a message indicating that the verification code is available, the service end generating the message after determining that the vehicle successfully receives the verifier;

[0134] The verification module is configured to perform identity verification with the vehicle according to the verification code.

[0135] Optionally, the acquisition module includes:

[0136] A first acquisition submodule is configured to acquire the message indicating that the verification code is available through a publish-subscribe mode; or

[0137] The second acquisition submodule is configured to establish a communication connection with the server and receive a message sent by the server through the established communication connection to indicate that the verification code is available.

[0138] In a sixth aspect, an embodiment of the present disclosure provides a communication device, including:

[0139] one or more processors;

[0140] The processor is configured to call computer instructions to enable the communication device to execute the identity authentication method described in any one of the first and second aspects.

[0141] In the seventh aspect, an embodiment of the present disclosure provides an identity authentication system, comprising a terminal, a server, and a vehicle, wherein the server is configured to implement the identity authentication method described in any one of the first aspects above, the terminal is configured to implement the identity authentication method described in any one of the second aspects above, and the vehicle is configured to receive a verifier sent by the server, and to perform identity authentication with the terminal through the verifier.

[0142] In an eighth aspect, an embodiment of the present disclosure provides a computer-readable storage medium, which stores computer instructions. When the computer instructions are executed on a communication device, the communication device executes the identity authentication method as described in any one of the first and second aspects above.

[0143] In a ninth aspect, an embodiment of the present disclosure provides a computer program product. When the computer program product is executed by a communication device, the communication device executes the identity authentication method as described in any one of the first and second aspects.

[0144] It is understood that the first identity verification device, the second identity verification device, the communication device, the identity verification system, the computer-readable storage medium, and the computer program product described above are all used to implement the identity verification method provided in the embodiments of the present disclosure. Therefore, the beneficial effects achieved by the aforementioned methods can be referenced to the beneficial effects of the corresponding identity verification methods and will not be further elaborated here.

[0145] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0146] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure. The singular expressions "a," "an," "the," "above," "said," "aforementioned," "this," etc. in the embodiments of the present disclosure also include plural expressions, unless there is a clear contrary indication in the context. The predefined in the embodiments of the present disclosure can be understood as definition, pre-definition, storage, pre-storage, pre-negotiation, pre-configuration, curing, or pre-firing, etc.

[0147] Prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects, and have no limiting effect on the position, order, priority, quantity or content of the described objects. For example, if the described object is a "field", then the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields", and "first" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the described object is a "level", then the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of described objects is not limited by the ordinal number and can be one or more. Taking the "first device" as an example, the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is a "device," then the "first device" and the "second device" can be devices of the same type or different types. For another example, if the object being described is "information," then the "first information" and the "second information" can be information of the same content or information of different contents. In summary, the use of prefixes such as ordinal numbers in the embodiments of the present disclosure to distinguish between the described objects does not constitute a limitation on the described objects. For a description of the described objects, refer to the contextual description in the claims or embodiments, and the use of such prefixes should not constitute an unnecessary limitation.

[0148] In the embodiments of the present disclosure, "multiple" refers to two or more. In the embodiments of the present disclosure, "and / or" is used to describe the association relationship of associated objects, indicating three relationships that can exist independently. For example, A and / or B can mean: A exists alone, B exists alone, and A and B exist at the same time. In the embodiments of the present disclosure, descriptions such as "at least one of Al, A2, ..., An (or at least one, at least one)" include the situation where any one of Al, A2, ..., An exists alone, and also include any combination of any multiple of Al, A2, ..., An, each of which can exist alone; for example, the description of "at least one of A, B, C" includes the situation where A exists alone, B exists alone, C exists alone, A and B are combined, A and C are combined, B and C are combined, and A and B and C are combined.

[0149] In some embodiments, descriptions such as "in one case A, in another case B," or "in response to one case A, in response to another case B," may include the following technical solutions depending on the situation: executing A independently of B (in some embodiments, A); executing B independently of A (in some embodiments, B); selectively executing A and B (in some embodiments, selecting between A and B); and executing both A and B (in some embodiments, A and B). The same applies when there are more branches, such as A, B, and C.

[0150] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0151] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0152] In some embodiments, terms such as "greater than", "greater than or equal to", "above", "higher than", and "not less than" can be replaced with each other, and terms such as "less than", "less than or equal to", "below", "lower than", and "not greater than" can be replaced with each other.

[0153] In some embodiments, terms such as "function", "device", "equipment", "system", "chip", "chip system", etc. can be used interchangeably.

[0154] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile terminal (MT)", mobile unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, mobile client, client, etc. can be used interchangeably.

[0155] In some embodiments, the names of information, etc. are not limited to the names described in the embodiments, and terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codeword", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0156] In some embodiments, "obtain", "get", "obtain", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from a protocol, obtaining by self-processing, autonomous implementation, etc.

[0157] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0158] In some embodiments, "predetermined" or "preset" may be interpreted as pre-specified in a protocol, etc., or as a pre-set action performed by a device, etc. In some embodiments, determining may be interpreted as judging, determining, calculating, computing, processing, deriving, investigating, searching, looking up, searching, inquiring, ascertaining, receiving, transmitting, inputting, outputting, accessing, resolving, selecting, choosing, establishing, comparing, "assuming," "expecting," "considering," broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc., but is not limited thereto.

[0159] Digital car keys are a new type of car key that manage functions such as unlocking and starting the vehicle, enhancing the user experience. To ensure the security of digital car keys, security policies can be implemented when the owner creates their digital car key, i.e., during the key pairing process on the owner's terminal.

[0160] For example, in some methods, authentication can be performed using a verification code and a validator to improve security. FIG1 is a flowchart of an authentication method shown in an embodiment of the present disclosure. Referring to FIG1 , authentication can be performed in the following manner:

[0161] 1. The server authenticates the vehicle owner's identity. The server can be a vehicle manufacturer's cloud service or a device specified in the digital car key protocol for issuing verification codes and authenticators. During vehicle owner authentication, the vehicle owner can, for example, initiate authentication with the server through a terminal. For example, the vehicle owner can request authentication by submitting authentication information via their mobile phone. This authentication information can include the mobile phone number, ID number, vehicle manufacturer account number, and password registered when purchasing the vehicle. It should be noted that this authentication information can be submitted to the server with the user's permission.

[0162] 2. The server verifies the vehicle owner's identity. The server compares the authentication information submitted by the terminal with the registered vehicle owner's information to determine whether the terminal is the vehicle owner's. After confirming the legitimacy of the terminal, the server deems the terminal trustworthy.

[0163] 3. The terminal applies to the server for a verification code, i.e., a password, for identity authentication with the vehicle.

[0164] 4. After receiving the verification code request, the server maintains the synchronous network request and generates the verification code and its corresponding verifier. The verification code and verifier can be, for example, a pair of parameters that satisfy a security algorithm. For example, the verification code and verifier can be a pair of parameters that satisfy the elliptic curve corresponding to the SPAKE2+ algorithm. Therefore, the verifier can verify the verification code to determine whether it is correct.

[0165] 5. The server sends the authenticator to the owner’s vehicle through the vehicle-cloud service communication link.

[0166] 6. After the vehicle receives the validator, it will feedback the status of successful receipt of the validator through the vehicle-cloud service communication link.

[0167] 7. After the server determines that the vehicle has the authenticator to verify the password, it returns the password to the terminal through the synchronous network request in step 4.

[0168] 8. After the terminal receives the password, use the password to complete the relevant configuration on the mobile device side.

[0169] 9. The owner's mobile device sends the password to the vehicle in near-field communication, so that the vehicle can authenticate itself with the terminal through the authenticator.

[0170] However, this authentication method may still face some challenges. For example, to prevent network requests from waiting indefinitely, a request timeout can usually be set for the terminal. If no feedback is received within the time period determined by this time, the network request will be terminated directly. In Figure 1, due to the long duration of a single communication interaction between the vehicle and cloud service communication link, in some scenarios the terminal may trigger a request timeout error and provide feedback to the user that the digital car key pairing failed.

[0171] Furthermore, the authentication method in Figure 1 requires the server to consume thread resources to maintain synchronous network requests until the vehicle confirms receipt of the authenticator. Therefore, this method can cause server thread resources to become blocked. Consequently, when multiple terminals simultaneously request verification codes, a significant amount of thread resources may be consumed to maintain synchronous network requests, impacting server performance and stability.

[0172] Furthermore, the terminal may need to perform some configuration work between receiving the password and using it to connect to the vehicle. In the approach shown in Figure 1, the three actions of waiting for the password, using the password to complete the configuration, and then using the password to connect to the vehicle form a mutually dependent serial relationship, which can lead to time loss and reduce the efficiency of authentication.

[0173] FIG2 is an interactive diagram illustrating an identity authentication method according to an embodiment of the present disclosure. As shown in FIG2 , the method includes:

[0174] In step S21, the server pre-generates a verification code and a verifier.

[0175] In some embodiments, the server may pre-generate the verification code and the authenticator in response to a control instruction. For example, the control instruction may be an instruction generated by a user operation.

[0176] In some embodiments, the server may pre-generate the verification code and authenticator when a set condition is triggered.

[0177] For example, the set condition may be a time interval, so that the server can pre-generate the verification code and the authenticator when detecting that the current moment is within the time interval.

[0178] For example, the set condition may refer to a state condition of the server. For example, the state condition may be a low load state. That is, when the server detects that the server is in a low load state, the server pregenerates the verification code and the authenticator.

[0179] For example, the server may determine that the server is in a low-load state when it determines that the server's load value is lower than a load threshold. The load value may be, for example, a memory occupancy rate, a central processing unit occupancy rate, or one or more thereof. The load threshold may be set according to the type of load value. For example, when the load value is a memory occupancy rate, the load threshold may be a memory occupancy rate threshold. When the server's load value is lower than the load threshold, the server may generate the verification code and the verifier.

[0180] In some implementation scenarios, the server may pre-generate one or more sets of verification codes and authenticators associated with the verification codes.

[0181] In some implementation scenarios, the server may generate a verification code and a verifier associated with the verification code using a security algorithm. The verifier may be used to verify the verification code to be verified to determine whether the verification code to be verified is the verification code associated with the verifier.

[0182] For example, the server can randomly generate a first parameter and use the first parameter as the verification code. The server can also substitute the verification code into the calculation formula of the security algorithm to obtain a calculation result, which can be used as the verifier of the verification code.

[0183] During the verification process, the party holding the authenticator can substitute the verification code to be verified and the authenticator into the calculation formula of the security algorithm. If the authenticator and the verification code to be verified satisfy the calculation formula, it can be determined that the verification code to be verified is the verification code associated with the authenticator, and the verification is successful. If the authenticator and the verification code to be verified do not satisfy the calculation formula, it can be determined that the verification code to be verified is an incorrect verification code, and the verification fails.

[0184] Illustratively, the security algorithm may be the SPAKE2+ algorithm.

[0185] In step S22, the terminal requests the vehicle owner to be authenticated.

[0186] In some embodiments, the terminal may send authentication information to the server, requesting the server to determine whether the terminal belongs to the vehicle owner based on the authentication information. For example, the authentication information may be submitted to the server with the user's permission. The authentication information may include the mobile phone number, ID number, vehicle manufacturer account number, and password registered when purchasing the vehicle, or one or more of these.

[0187] In step S23, the service end confirms the identity of the vehicle owner.

[0188] In some embodiments, the server can compare the authentication information submitted by the terminal with the registered owner's information to determine whether the terminal is the owner's terminal. After confirming the legitimacy of the terminal, the server considers the terminal to be credible.

[0189] In step S24, the terminal sends a verification code acquisition request to the server.

[0190] In step S25, the server sends a verification code to the terminal.

[0191] In some implementations, the server may determine whether there is an unused verification code from pre-generated verification codes.

[0192] For example, if there are unused verification codes, the server determines a set of unused verification codes from pre-generated verification codes and sends the unused verification codes to the terminal. If there are no unused verification codes, the server may generate a verification code and an authenticator and send the generated verification code to the terminal.

[0193] In step S26, the server releases a first thread resource used to maintain the connection between the terminal and the server.

[0194] In step S27, the server sends a verifier for verifying the verification code to the vehicle.

[0195] In some embodiments, the server may determine the verifier corresponding to the verification code sent to the terminal based on the association between the verification code and the verifier, and send the verifier to the vehicle.

[0196] In some embodiments, the server sends the authenticator to the vehicle via a vehicle-to-cloud service communication link. Depending on the protocol used by the digital car key, the vehicle-to-cloud service communication link can be presented in different forms, which is not limited in the present disclosure.

[0197] In step S28, the terminal performs configuration operations on the terminal according to the received verification code.

[0198] The configuration operation may be a pre-processing operation required when the terminal authenticates the vehicle based on the verification code.

[0199] In some embodiments, the terminal performs identity authentication with the vehicle via Bluetooth, and the terminal configuring the terminal according to the received verification code may include: loading the verification code into a Bluetooth cache.

[0200] In some embodiments, the terminal performs identity authentication with the vehicle via NFC (Near Field Communication), and the terminal configures the terminal according to the received verification code, which may include encapsulating the verification code into a data packet for identity authentication.

[0201] In step S29 , the vehicle successfully receives the validator.

[0202] In step S210, the server sends a message to the terminal indicating that the verification code is available.

[0203] In some implementations, sending a message to the terminal indicating that the verification code is available includes sending a message to the terminal indicating that the verification code is available via a publish-subscribe mode.

[0204] For example, the server can publish the message to a messaging middleware and set a subject for the message. The terminal can subscribe to messages on the subject in the messaging middleware. Thus, after the server publishes the message to the messaging middleware, the terminal can obtain a message from the messaging middleware indicating that the verification code is available.

[0205] In some implementations, sending a message to the terminal indicating that the verification code is available includes: sending a message to the terminal via a message queue indicating that the verification code is available.

[0206] For example, the server may send the message to a message queue of a third party, and the message queue may send the message to the terminal.

[0207] In some implementations, sending a message indicating that the verification code is available to the terminal includes: establishing a communication connection with the terminal, and sending a message indicating that the verification code is available to the terminal through the established communication connection.

[0208] For example, the server can allocate a second thread resource and establish a communication connection with the terminal through the second thread resource. In this way, the server can send a message indicating that the verification code is available to the terminal through the established communication connection.

[0209] In some implementations, sending a message indicating that the verification code is available to the terminal through the established communication connection includes: calling back an interface of the terminal to send a message indicating that the verification code is available to the terminal.

[0210] In step S211, the terminal performs identity authentication with the vehicle based on the verification code.

[0211] In some implementations, the terminal authenticates itself with the vehicle via one or more of Bluetooth, NFC, and UWB (Ultra Wide Band).

[0212] In the embodiment of the present disclosure, steps S21, S22, S23, and S28 are optional. Steps S21 and S22 can be interchanged in order, steps S26 and S27 can be interchanged in order, and steps S27 and S28 can be interchanged in order. In addition, steps S21, S24 to S211 can be combined to implement as an independent embodiment, steps S21, S24 to S27, and steps S29 to S211 can be combined to implement as an independent embodiment, steps S22 and S211 can be combined to implement as an independent embodiment, steps S24 to S211 can be combined to implement as an independent embodiment, steps S22 to S27, and steps S29 to S211 can be combined to implement as an independent embodiment, and steps S24, S27, and steps S29 to S211 can be combined to implement as an independent embodiment.

[0213] FIG3 is a flow chart of an identity authentication method according to an embodiment of the present disclosure. As shown in FIG3 , the embodiment of the present disclosure relates to an identity authentication method, which is executed by a server and includes:

[0214] In step S31, it is determined that the load value of the server is lower than a load threshold.

[0215] In step S32, a verification code and a verifier are generated.

[0216] The optional implementation of step S31 and step S32 can refer to the optional implementation of step S21 in Figure 2, and will not be repeated here.

[0217] In step S33, an identity authentication request from the terminal is received.

[0218] The optional implementation of step S33 can refer to the optional implementation of step S22 in Figure 2, which will not be repeated here.

[0219] In step S34, the identity of the terminal is confirmed to be credible.

[0220] The optional implementation of step S34 can refer to the optional implementation of step S23 in Figure 2, which will not be repeated here.

[0221] In step S35, a verification code acquisition request sent by the terminal is received.

[0222] In step S36 , a group of unused verification codes is determined from pre-generated verification codes, and the verification codes are used for identity verification between the terminal and the vehicle.

[0223] In step S37, the unused verification code is sent to the terminal.

[0224] The optional implementation of step S36 and step S37 can refer to the optional implementation of step S25 in Figure 2, which will not be repeated here.

[0225] In step S38, the first thread resource is released, where the first thread resource is used to maintain the connection between the terminal and the server.

[0226] In step S39 , a verifier for verifying the verification code is sent to the vehicle.

[0227] The optional implementation of step S39 can refer to the optional implementation of step S27 in Figure 2, which will not be repeated here.

[0228] In step S310 , it is determined whether the vehicle successfully receives the validator.

[0229] In step S311, a message indicating that the verification code is available is sent to the terminal through the publish-subscribe mode.

[0230] The optional implementation of step S311 can refer to the optional implementation of step S210 in Figure 2, which will not be repeated here.

[0231] The identity authentication method involved in the embodiment of the present disclosure may include at least one of steps S31 to S311.

[0232] For example, steps S31, S32, and S35 to S311 can be implemented as independent embodiments. Steps S33 to S311 can be implemented as independent embodiments, and steps S35 to S311 can be implemented as independent embodiments, but are not limited thereto. Furthermore, in some embodiments, steps S31 and S32, and steps S33 and S34 are optional, and one or more of these steps can be omitted or replaced in different embodiments. In some implementations, steps S37 and S39 can be executed simultaneously, or their execution order can be swapped.

[0233] In the above embodiment, the server can receive a verification code acquisition request sent by the terminal, send a verification code for identity authentication with the vehicle to the terminal, and release the first thread resource. In this way, the waiting time for the terminal to obtain the verification code can be reduced, which helps to reduce the request timeout phenomenon. Moreover, by releasing the first thread resource, the thread congestion phenomenon on the server can be alleviated, thereby alleviating the performance pressure on the server. In addition, the server can also send a verifier to the vehicle so that the vehicle can verify the verification code of the terminal according to the verifier, thereby performing identity authentication between the terminal and the vehicle.

[0234] FIG4 is a flow chart of an identity authentication method according to an embodiment of the present disclosure. As shown in FIG4 , the embodiment of the present disclosure relates to an identity authentication method, which is executed by a server and includes:

[0235] In step S41, a verification code and a verifier are generated in advance.

[0236] The optional implementation of step S41 can refer to steps S31 and S32 in FIG3 and the optional implementation of step S21 in FIG2 , which will not be described in detail here.

[0237] In step S42, an identity authentication request from the terminal is received.

[0238] The optional implementation of step S42 can refer to the optional implementation of step S22 in Figure 2, which will not be repeated here.

[0239] In step S43, the identity of the terminal is confirmed to be credible.

[0240] The optional implementation of step S43 can refer to the optional implementation of step S23 in Figure 2, which will not be repeated here.

[0241] In step S44, a verification code acquisition request sent by the terminal is received.

[0242] In step S45 , a group of unused verification codes is determined from pre-generated verification codes, and the verification codes are used for identity verification between the terminal and the vehicle.

[0243] In step S46, the unused verification code is sent to the terminal.

[0244] The optional implementation of step S45 and step S46 can refer to the optional implementation of step S25 in Figure 2, which will not be repeated here.

[0245] In step S47, the first thread resource is released, where the first thread resource is used to maintain the connection between the terminal and the server.

[0246] In step S48, a verifier for verifying the verification code is sent to the vehicle.

[0247] The optional implementation of step S48 can refer to the optional implementation of step S27 in Figure 2, which will not be repeated here.

[0248] In step S49 , it is determined that the vehicle successfully received the validator.

[0249] In step S410, a message indicating that the verification code is available is sent to the terminal.

[0250] The optional implementation of step S410 can refer to step S311 in FIG. 3 and the optional implementation of step S210 in FIG. 2 , which will not be described in detail here.

[0251] The identity authentication method involved in the embodiment of the present disclosure may include at least one of steps S41 to S410.

[0252] For example, steps S41, S44 to S410 can be implemented as independent embodiments. Steps S42 to S410 can be implemented as independent embodiments, and steps S44 to S410 can be implemented as independent embodiments, but are not limited thereto. Furthermore, in some embodiments, steps S41, S42, and S43 are optional, and one or more of these steps can be omitted or replaced in different embodiments. In some implementations, steps S46 and S48 can be executed simultaneously, or the order of execution can be swapped. Steps S47 and S48 can be executed simultaneously, or the order of execution can be swapped.

[0253] In the above embodiment, the server can receive a verification code request from a terminal, send a verification code to the terminal for identity verification with the vehicle, and release the first thread resources. This approach can reduce the waiting time for the terminal to obtain the verification code, helping to reduce request timeouts. Furthermore, by releasing the first thread resources, thread congestion on the server can be alleviated, thereby alleviating performance pressure on the server.

[0254] FIG5 is a flow chart of an identity authentication method according to an embodiment of the present disclosure. As shown in FIG5 , the embodiment of the present disclosure relates to an identity authentication method, which is executed by a server and includes:

[0255] In step S51, a verification code and a verifier are generated in advance.

[0256] The optional implementation of step S51 can refer to steps S31 and S32 in FIG3 and the optional implementation of step S21 in FIG2 , which will not be described in detail here.

[0257] In step S52, an identity authentication request from the terminal is received.

[0258] The optional implementation of step S52 can refer to the optional implementation of step S22 in Figure 2, which will not be repeated here.

[0259] In step S53, it is confirmed that the identity of the terminal is credible.

[0260] The optional implementation of step S53 can refer to the optional implementation of step S23 in Figure 2, which will not be repeated here.

[0261] In step S54, a verification code acquisition request sent by the terminal is received.

[0262] In step S55, a verification code is sent to the terminal, and the verification code is used for identity verification between the terminal and the vehicle.

[0263] The optional implementation of step S55 can refer to steps S45 and S46 in FIG4 and the optional implementation of step S25 in FIG2 , which will not be described in detail here.

[0264] In step S56, the first thread resource is released, where the first thread resource is used to maintain the connection between the terminal and the server.

[0265] In step S57 , a verifier for verifying the verification code is sent to the vehicle.

[0266] The optional implementation of step S57 can refer to the optional implementation of step S27 in Figure 2, which will not be repeated here.

[0267] In step S58 , it is determined that the vehicle successfully received the validator.

[0268] In step S59, a message indicating that the verification code is available is sent to the terminal.

[0269] The optional implementation of step S59 can refer to the optional implementation of step S311 in FIG. 3 and step S210 in FIG. 2 , which will not be described in detail here.

[0270] The identity authentication method involved in the embodiment of the present disclosure may include at least one of steps S51 to S59.

[0271] For example, steps S51, S54 to S59 can be implemented as independent embodiments. Steps S52 to S59 can be implemented as independent embodiments, and steps S54 to S59 can be implemented as independent embodiments, but are not limited thereto. Furthermore, in some embodiments, steps S51, S52, and S53 are optional, and one or more of these steps can be omitted or replaced in different embodiments. In some implementations, steps S55 and S57 can be executed simultaneously, or their execution order can be swapped. Steps S56 and S57 can be executed simultaneously, or their execution order can be swapped.

[0272] In the above embodiment, the server can receive a verification code request from a terminal, send a verification code to the terminal for identity verification with the vehicle, and release the first thread resources. This approach can reduce the waiting time for the terminal to obtain the verification code, helping to reduce request timeouts. Furthermore, by releasing the first thread resources, thread congestion on the server can be alleviated, thereby alleviating performance pressure on the server.

[0273] FIG6 is a flow chart of an identity authentication method according to an embodiment of the present disclosure. As shown in FIG6 , the embodiment of the present disclosure relates to an identity authentication method, which is executed by a terminal and includes:

[0274] In step S61, an identity authentication request is sent to the server.

[0275] The optional implementation of step S61 can refer to the optional implementation of step S22 in Figure 2, which will not be repeated here.

[0276] In step S62, it is confirmed that the identity authentication is successful.

[0277] The optional implementation of step S62 can refer to the optional implementation of step S23 in Figure 2, which will not be repeated here.

[0278] In step S63, a verification code acquisition request is sent to the server.

[0279] In step S64, a verification code sent by the service end is received, and the verification code is used for identity verification between the terminal and the vehicle.

[0280] Optionally, the server releases a first thread resource and sends a verifier for verifying the verification code to the vehicle, and the first thread resource is used to maintain the connection between the terminal and the server.

[0281] In step S65, the verification code is loaded into the Bluetooth cache.

[0282] The optional implementation of step S65 can refer to the optional implementation of step S28 in Figure 2, which will not be repeated here.

[0283] In step S66 , a message indicating that the verification code is available is obtained through the publish-subscribe mode.

[0284] The optional implementation of step S66 can refer to the optional implementation of step S210 in Figure 2, which will not be repeated here.

[0285] Optionally, the server generates a message after determining that the vehicle successfully receives the validator.

[0286] In step S67, identity verification is performed with the vehicle based on the verification code.

[0287] The identity authentication method involved in the embodiment of the present disclosure may include at least one of steps S61 to S67.

[0288] For example, steps S63 to S67 can be implemented as independent embodiments, but are not limited thereto. Furthermore, in some embodiments, steps S61 and S62 are optional, and one or more of these steps can be omitted or replaced in different embodiments. In some implementations, steps S65 and S66 can be executed simultaneously, or their execution order can be swapped.

[0289] In the above embodiment, the terminal can send a verification code acquisition request to the server, and the server can receive the verification code acquisition request sent by the terminal, send a verification code for identity authentication with the vehicle to the terminal, and release the first thread resource. In this way, the waiting time for the terminal to obtain the verification code can be reduced, which helps to reduce the request timeout phenomenon. Moreover, by releasing the first thread resource, the thread congestion phenomenon on the server can be alleviated, thereby alleviating the performance pressure on the server. In addition, the server can also send a verifier to the vehicle so that the vehicle can verify the verification code of the terminal according to the verifier, thereby performing identity authentication between the terminal and the vehicle.

[0290] FIG7 is a flow chart of an identity authentication method according to an embodiment of the present disclosure. As shown in FIG7 , the embodiment of the present disclosure relates to an identity authentication method, which is executed by a terminal and includes:

[0291] In step S71, an identity authentication request is sent to the server.

[0292] The optional implementation of step S71 can refer to the optional implementation of step S22 in Figure 2, which will not be repeated here.

[0293] In step S72, it is confirmed that the identity authentication is successful.

[0294] The optional implementation of step S72 can refer to the optional implementation of step S23 in Figure 2, which will not be repeated here.

[0295] In step S73, a verification code acquisition request is sent to the server.

[0296] In step S74, a verification code sent by the service end is received, and the verification code is used for identity verification between the terminal and the vehicle.

[0297] Optionally, the server releases a first thread resource and sends a verifier for verifying the verification code to the vehicle, and the first thread resource is used to maintain the connection between the terminal and the server.

[0298] In step S75, the terminal is configured according to the received verification code.

[0299] The optional implementation of step S75 can refer to step S65 in FIG6 and the optional implementation of step S28 in FIG2 , which will not be described in detail here.

[0300] In step S76 , a message indicating that the verification code is available is obtained.

[0301] The optional implementation of step S76 can refer to the optional implementation of step S66 in FIG6 and step S210 in FIG2 , which will not be described in detail here.

[0302] Optionally, the server generates a message after determining that the vehicle successfully receives the validator.

[0303] In step S77, identity verification is performed with the vehicle based on the verification code.

[0304] The identity authentication method involved in the embodiment of the present disclosure may include at least one of steps S71 to S77.

[0305] For example, steps S73 to S77 can be implemented as independent embodiments, but are not limited thereto. Furthermore, in some embodiments, steps S71 and S72 are optional, and one or more of these steps can be omitted or replaced in different embodiments. In some implementations, steps S75 and S76 can be executed simultaneously, or their execution order can be swapped.

[0306] In the above embodiment, the terminal can send a verification code acquisition request to the server, and the server can receive the verification code acquisition request sent by the terminal, send a verification code for identity authentication with the vehicle to the terminal, and release the first thread resource. In this way, the waiting time for the terminal to obtain the verification code can be reduced, which helps to reduce the request timeout phenomenon. Moreover, by releasing the first thread resource, the thread congestion phenomenon on the server can be alleviated, thereby alleviating the performance pressure on the server. In addition, the server can also send a verifier to the vehicle so that the vehicle can verify the verification code of the terminal according to the verifier, thereby performing identity authentication between the terminal and the vehicle.

[0307] The embodiments of the present disclosure also provide an apparatus for implementing any of the above identity authentication methods. For example, an identity authentication apparatus is provided, which includes units for implementing each step performed by the terminal in any of the above identity authentication methods.

[0308] It should be understood that the division of the various units in the above device is only a division of logical functions. In actual implementation, they can be fully or partially integrated into a physical entity, or they can be physically separated. In addition, the units in the device can be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores computer instructions. The processor calls the computer instructions stored in the memory to implement any of the above identity authentication methods or implement the functions of the various units of the above device, where the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors. For example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), and the functions of some or all of the above units are realized by designing the logical relationship of the components in the circuit. For another example, in another implementation, the above-mentioned hardware circuit can be implemented by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by a configuration file, thereby realizing the functions of some or all of the above units. All units of the above devices can be implemented in the form of software called by the processor, or in the form of hardware circuits, or in part by software called by the processor, and the rest by hardware circuits.

[0309] In the embodiment of the present disclosure, the processor is a circuit with signal processing capability. In one implementation, the processor can be a circuit with instruction reading and execution capability, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP); in another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit, and the logical relationship of the above hardware circuit is fixed or reconfigurable, such as a hardware circuit implemented by a processor as an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0310] FIG8 is a schematic diagram of the structure of a first identity verification device provided by an embodiment of the present disclosure, which can be applied to a server. As shown in FIG8 , the first identity verification device 800 includes:

[0311] The first receiving module 801 is configured to receive a verification code acquisition request sent by a terminal;

[0312] A first sending module 802 is configured to send a verification code to the terminal, where the verification code is used for identity authentication between the terminal and the vehicle;

[0313] A first execution module 803 is configured to release a first thread resource, where the first thread resource is used to maintain the connection between the terminal and the server;

[0314] The second sending module 804 is configured to send a verifier for verifying the verification code to the vehicle.

[0315] In the above embodiment, the server can receive a verification code acquisition request sent by the terminal, send a verification code for identity authentication with the vehicle to the terminal, and release the first thread resource. In this way, the waiting time for the terminal to obtain the verification code can be reduced, which helps to reduce the request timeout phenomenon. Moreover, by releasing the first thread resource, the thread congestion phenomenon on the server can be alleviated, thereby alleviating the performance pressure on the server. In addition, the server can also send a verifier to the vehicle so that the vehicle can verify the verification code of the terminal according to the verifier, thereby performing identity authentication between the terminal and the vehicle.

[0316] In some embodiments, including:

[0317] a first determination module configured to determine whether the vehicle successfully receives the validator;

[0318] The fourth sending module is configured to send a message to the terminal indicating that the verification code is available.

[0319] In some embodiments, the fourth sending module includes:

[0320] A first sending submodule is configured to send a message indicating that the verification code is available to the terminal through a publish-subscribe mode; or

[0321] The second sending submodule is configured to establish a communication connection with the terminal, and send a message indicating that the verification code is available to the terminal through the established communication connection.

[0322] In some embodiments, the second sending submodule includes:

[0323] The first sending subunit is configured to call back the interface of the terminal and send a message to the terminal indicating that the verification code is available.

[0324] In some embodiments, including:

[0325] The first generating module is configured to pre-generate the verification code and the verifier.

[0326] In some embodiments, the first generation module includes:

[0327] A first determining submodule is configured to determine whether the load value of the server is lower than a load threshold;

[0328] The first generating submodule is configured to generate the verification code and the verifier.

[0329] In some embodiments, the first sending module includes:

[0330] a second determining submodule, configured to determine a group of unused verification codes from pre-generated verification codes;

[0331] The third sending submodule is configured to send the unused verification code to the terminal.

[0332] FIG9 is a schematic diagram of the structure of a second identity authentication device provided by an embodiment of the present disclosure, which can be applied to a terminal. As shown in FIG9 , the second identity authentication device 900 includes:

[0333] The third sending module 901 is configured to send a verification code acquisition request to the server;

[0334] The second receiving module 902 is configured to receive a verification code sent by the server, where the verification code is used for identity authentication between the terminal and the vehicle;

[0335] The server releases a first thread resource and sends a verifier for verifying the verification code to the vehicle. The first thread resource is used to maintain the connection between the terminal and the server.

[0336] In the above embodiment, the terminal can send a verification code acquisition request to the server, and the server can receive the verification code acquisition request sent by the terminal, send a verification code for identity authentication with the vehicle to the terminal, and release the first thread resource. In this way, the waiting time for the terminal to obtain the verification code can be reduced, which helps to reduce the request timeout phenomenon. Moreover, by releasing the first thread resource, the thread congestion phenomenon on the server can be alleviated, thereby alleviating the performance pressure on the server. In addition, the server can also send a verifier to the vehicle so that the vehicle can verify the verification code of the terminal according to the verifier, thereby performing identity authentication between the terminal and the vehicle.

[0337] In some embodiments, including:

[0338] The second execution module is configured to perform configuration operations on the terminal according to the received verification code.

[0339] In some embodiments, the terminal performs identity authentication with the vehicle via Bluetooth, and the second execution module includes:

[0340] The first loading submodule is configured to load the verification code into the Bluetooth cache.

[0341] In some embodiments, the method includes: an acquisition module configured to acquire a message indicating that the verification code is available, the service end generating the message after determining that the vehicle successfully receives the verification code;

[0342] The verification module is configured to perform identity verification with the vehicle according to the verification code.

[0343] In some embodiments, the acquisition module includes:

[0344] A first acquisition submodule is configured to acquire the message indicating that the verification code is available through a publish-subscribe mode; or

[0345] The second acquisition submodule is configured to establish a communication connection with the server and receive a message sent by the server through the established communication connection to indicate that the verification code is available.

[0346] Figure 10 is a schematic diagram of the structure of a communication device 8100 provided in an embodiment of the present disclosure. Communication device 8100 can be a network device configured as a server, a terminal (e.g., user equipment), a chip, a chip system, or a processor that supports a network device to implement any of the above-mentioned authentication methods, or a chip, a chip system, or a processor that supports a terminal to implement any of the above-mentioned authentication methods. Communication device 8100 can be used to implement the authentication method described in the above-mentioned method embodiment. For details, please refer to the description of the above-mentioned method embodiment.

[0347] As shown in Figure 10, the communication device 8100 includes one or more processors 8101, which are configured to invoke computer instructions to cause the communication device 8100 to perform any of the above authentication methods. Optionally, the communication device 8100 also includes one or more memories 8102 for storing computer instructions. In alternative embodiments, all or part of the memories 8102 may be located outside the communication device 8100.

[0348] Optionally, the communication device 8100 further includes one or more transceivers 8103. When the communication device 8100 includes one or more transceivers 8103, the communication steps such as sending and receiving in the above-mentioned identity authentication method are performed by the transceiver 8103, and the other steps are performed by the processor 8101.

[0349] The communication device 8100 described in the above embodiment may be a network device or a terminal, but the scope of the communication device 8100 described in the present disclosure is not limited thereto, and the structure of the communication device 8100 may not be limited by FIG. 10 . The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: (1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data or computer programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0350] The present disclosure also provides a readable storage medium having computer instructions stored thereon. When the computer instructions are executed on the communication device 8100, the communication device 8100 executes any of the above-mentioned identity verification methods. Optionally, the computer-readable storage medium can be a non-transitory computer-readable storage medium or a transitory computer-readable storage medium.

[0351] The present disclosure also provides a computer program product. When the computer program product is executed by the communication device 8100, it enables the communication device 8100 to perform any of the above identity authentication methods.

Claims

1. An identity authentication method, characterized in that: Executed by the server, the method includes: Receiving a verification code acquisition request sent by a terminal; Sending a verification code to the terminal, the verification code being used for identity authentication between the terminal and the vehicle; releasing a first thread resource, where the first thread resource is used to maintain a connection between the terminal and the server; A verifier for verifying the verification code is sent to the vehicle.

2. The method according to claim 1, characterized in that include: determining that the vehicle successfully receives the validator; A message indicating that the verification code is available is sent to the terminal.

3. The method according to claim 2, characterized in that The sending a message to the terminal indicating that the verification code is available includes: Sending a message indicating that the verification code is available to the terminal through a publish-subscribe mode; or, A communication connection is established with the terminal, and a message indicating that the verification code is available is sent to the terminal through the established communication connection.

4. The method according to claim 3, characterized in that The sending a message indicating that the verification code is available to the terminal through the established communication connection includes: The interface of the terminal is called back, and a message indicating that the verification code is available is sent to the terminal.

5. The method according to any one of claims 1 to 4, characterized in that include: The verification code and the verifier are generated in advance.

6. The method according to claim 5, characterized in that The pre-generating the verification code and the verifier comprises: Determine that the server load value is below the load threshold; Generate the verification code and the verifier.

7. The method according to any one of claims 1 to 4, characterized in that Sending a verification code to the terminal includes: determining a set of unused verification codes from among the pre-generated verification codes; The unused verification code is sent to the terminal.

8. An identity authentication method, characterized in that: Executed by a terminal, the method includes: Send a verification code acquisition request to the server; Receiving a verification code sent by the server, the verification code being used for identity authentication between the terminal and the vehicle; The server releases a first thread resource and sends a verifier for verifying the verification code to the vehicle, and the first thread resource is used to maintain a connection between the terminal and the server.

9. The method according to claim 8, characterized in that include: Perform configuration operations on the terminal according to the received verification code.

10. The method according to claim 9, characterized in that The terminal performs identity authentication with the vehicle via Bluetooth, and the configuration operation of the terminal according to the received verification code includes: The verification code is loaded into the Bluetooth cache.

11. The method according to any one of claims 8 to 10, characterized in that include: obtaining a message indicating that the verification code is available, the service end generating the message after determining that the vehicle successfully receives the verification code; Authentication is performed with the vehicle based on the verification code.

12. The method according to claim 11, characterized in that The obtaining of a message indicating that the verification code is available includes: Acquire the message indicating that the verification code is available through a publish-subscribe mode; or, Establishing a communication connection with the server, and receiving a message sent by the server through the established communication connection to indicate that the verification code is available.

13. An identity authentication method, characterized in that: include: The terminal sends a verification code acquisition request to the server; The server receives the verification code acquisition request; The server sends a verification code to the terminal, and the verification code is used for identity authentication between the terminal and the vehicle; The terminal receives the verification code sent by the server; The server releases a first thread resource, where the first thread resource is used to maintain a connection between the terminal and the server; The service end sends a verifier for verifying the verification code to the vehicle.

14. A first identity verification device, characterized in that: Applied to the server, including: A first receiving module is configured to receive a verification code acquisition request sent by a terminal; A first sending module is configured to send a verification code to the terminal, where the verification code is used for identity authentication between the terminal and the vehicle; A first execution module is configured to release a first thread resource, where the first thread resource is used to maintain a connection between the terminal and the server; The second sending module is configured to send a verifier for verifying the verification code to the vehicle.

15. A second identity verification device, characterized in that: Applied to terminals, including: A third sending module is configured to send a verification code acquisition request to the server; A second receiving module is configured to receive a verification code sent by the server, wherein the verification code is used for identity authentication between the terminal and the vehicle; The server releases a first thread resource and sends a verifier for verifying the verification code to the vehicle, and the first thread resource is used to maintain a connection between the terminal and the server.

16. A communication device, characterized in that: include: one or more processors; The processor is used to call computer instructions so that the communication device executes the identity authentication method described in any one of claims 1-12.

17. An identity authentication system, characterized in that: It includes a terminal, a server, and a vehicle, wherein the server is configured to implement the identity authentication method described in any one of claims 1 to 7, the terminal is configured to implement the identity authentication method described in any one of claims 8 to 12, and the vehicle is configured to receive a verifier sent by the server and perform identity authentication with the terminal through the verifier.

18. A computer-readable storage medium storing computer instructions, characterized in that: When the computer instructions are executed on a communication device, the communication device is caused to execute the identity authentication method as described in any one of claims 1 to 12.

Citation Information

Patent Citations

  • Communication method and device for terminal equipment and vehicle machine

    CN110417798A

  • Communication verification method and system, mobile terminal and vehicle terminal

    CN111083696A

  • Communication method, device and system based on equipment code

    CN111148275A

  • Identity verification method and device, communication equipment, system and storage medium

    CN116502200A

  • Identity authentication method and apparatus, and related device

    WO2021136290A1