A method for canceling a vehicle digital key and related equipment

Abstract

The present application discloses a method for canceling a vehicle digital key and related equipment, the method comprising: receiving a key cancellation request sent by a user and updating the key status, pushing the key cancellation request to a client; if the cancellation result fed back by the client is not received within a first preset time, updating a pre-created key blacklist according to the key cancellation request; sending the updated key blacklist to a digital key controller, receiving an execution result returned by the digital key controller of completing the local blacklist update according to the updated key blacklist, and canceling the key according to the execution result. The present application provides a flexible key cancellation method, increases the reliability of the system, ensures timely key cancellation, avoids possible safety risks, improves the efficiency and accuracy of key cancellation, and further increases the safety of the vehicle.

Description

Technical Field

[0001] The present application relates to the technical field of vehicle digital keys, and in particular to a method, system, vehicle, and computer-readable storage medium for canceling a vehicle digital key. Background Art

[0002] In recent years, new car key designs have emerged one after another. Aiming to reduce the burden on car owners and enhance the user experience, car keys have evolved from the original single-function physical key to the later virtual Bluetooth key. The Bluetooth key itself features comprehensive features, including key downloading, key sharing, key deletion, key recovery by the owner, key return by the sharer, key information query, key sharing history query, and key owner revocation.

[0003] In existing technologies, digital key sharing and cancellation requests can be transmitted via the HTTPS (Hypertext Transfer Protocol Secure) network protocol or Bluetooth. When the backend server receives a key cancellation request from the car owner or the shared person, the digital key's status is updated to pending cancellation. The cancellation request is then pushed to the car owner or the shared person. Upon receiving the cancellation request, the car owner or the shared person deletes the corresponding digital key and then sends the cancellation result back to the backend server.

[0004] However, there is a situation where the backend server does not receive the feedback result of the digital key cancellation. If this situation is not collected and processed, it is easy to cause information difference between the client and the backend server, which will cause the cancellation information to be out of sync and the key usage status cannot be updated in time.

[0005] Therefore, the existing technology still needs to be improved and developed. Summary of the Invention

[0006] The main purpose of this application is to provide a method, system, vehicle and computer-readable storage medium for canceling a vehicle digital key, aiming to solve the technical problem in the prior art that there is no solution to the problem that the backend server does not receive the key feedback result, resulting in the backend server and client information being out of sync, and the cancelled digital key can still continue to be used.

[0007] The first aspect of the present application provides a method for cancelling a vehicle digital key, comprising the following steps: receiving a key cancellation request sent by a user and updating the key status, and pushing the key cancellation request to a client; if no cancellation result is received from the client within a first preset time, updating a pre-created key blacklist according to the key cancellation request; sending the updated key blacklist to a digital key controller, receiving an execution result returned by the digital key controller of completing the local blacklist update according to the updated key blacklist, and canceling the key according to the execution result.

[0008] According to the above-mentioned technical means, the embodiment of the present application can receive a key cancellation request and push it to the client, set a first preset time and determine whether the client has fed back the cancellation result of the key cancellation request within the first preset time. If there is no cancellation, the blacklist push process is automatically initiated, and the updated key blacklist is pushed to the digital key controller. After updating the local blacklist, the key is cancelled according to the local blacklist. By waiting for the client's cancellation feedback within the preset time, a flexible management method is provided, the reliability of the system is increased, and the timely cancellation of the key is ensured to avoid possible security risks. Moreover, since it is an automated cancellation process, no manual intervention is required, the management process is simplified, the workload of manual operations and possible errors in manual operations are reduced, and the efficiency and accuracy of key cancellation are improved. At the same time, it prevents the cancelled digital key from continuing to have access rights due to information asynchrony, ensuring that the cancelled key can no longer be used, further increasing the safety of the vehicle.

[0009] Optionally, in one embodiment of the present application, the client includes a car owner end and a shared person end; receiving the key cancellation request sent by the user and updating the key status, and pushing the key cancellation request to the client, specifically includes: receiving the key cancellation request initiated by the user through the car owner end or the shared person end; updating the key status to a pending cancellation status; pushing the key cancellation request to the car owner end or the shared person end in the form of a message notification.

[0010] According to the above-mentioned technical means, the embodiment of the present application can initiate a key cancellation request through the client (the car owner's side or the shared person's side). After the vehicle receives the key cancellation request, the key status is updated to the pending cancellation status, and the relevant content of the key cancellation request is sent to the client in the form of a notification. The car owner or the shared person can immediately receive the notification of the key cancellation request, which is convenient for timely processing and feedback, improving the timeliness and efficiency of communication, and the user can initiate a cancellation request on the client without additional steps or complicated processes, providing a convenient user experience and reducing the complexity of operations. At the same time, the key status is updated in real time according to the key cancellation request, so that the user can clearly understand the key status information, making the entire key cancellation process more transparent and convenient for subsequent operations and management.

[0011] Optionally, in one embodiment of the present application, if the deregistration result fed back by the client is not received within the first preset time, the pre-created key blacklist is updated according to the key deregistration request, specifically including: starting the timing when the key deregistration request is received; if the deregistration result is not received within the first preset time, adding the key corresponding to the key deregistration request to the key blacklist; wherein, the deregistration result is the execution status feedback of the key deregistration request instruction by the client.

[0012] According to the above technical means, the embodiment of the present application can make a preliminary judgment on whether the client has completed the deregistration of the key by whether the deregistration result sent by the client is received within the first preset time. If the deregistration result is still not received within the first preset time, it proves that there may be a problem in the deregistration process, and the key deregistration is unsuccessful. The key corresponding to the key deregistration request is added to the key blacklist, thereby providing instant deregistration feedback. Even if the deregistration is not successful, there will be a corresponding solution, so that the deregistered key is marked as unusable by the blacklist, preventing the deregistered but unsuccessful key from still being able to access the vehicle, thereby improving the safety of the vehicle and providing better protection for the user's property safety. The user does not need to worry about the key that failed to be deregistered still being able to access the vehicle, thereby improving the user experience.

[0013] Optionally, in one embodiment of the present application, sending the updated key blacklist to the digital key controller specifically includes: sending the key blacklist to a vehicle-mounted terminal, and sending the key blacklist to the digital key controller via the vehicle-mounted terminal.

[0014] According to the above-mentioned technical means, the embodiment of the present application can synchronize the key blacklist to the digital key controller through the vehicle-mounted terminal, so that the digital key controller also has a local blacklist with the same content as the key blacklist, ensuring the timely update of the local blacklist of the digital key controller, avoiding message asymmetry, and effectively preventing the blacklisted keys from continuing to be used. There is also no need to request access to the key blacklist again every time the key is verified, which reduces the workflow, improves the efficiency of key verification, improves the protection capability of the system, and improves the convenience of key verification.

[0015] Optionally, in one embodiment of the present application, the key blacklist is sent to the vehicle terminal, and then further includes: starting timing when the key blacklist is sent to the vehicle terminal; judging whether a feedback result sent by the vehicle terminal is received within a second preset time, wherein the feedback result is the feedback result of the vehicle terminal when receiving the key blacklist, and the feedback result includes success feedback and error feedback; if the feedback result is not received within the second preset time or the error feedback is received, the key blacklist is sent to the vehicle terminal again, and the timing is restarted and the number of retransmissions is recorded; judging again according to the timing duration of sending the blacklist again, until the number of retransmissions reaches the preset number, and stopping the operation of sending the key blacklist again; if the success feedback is received within the second preset time, the operation of sending the key blacklist again is not performed.

[0016] According to the above-mentioned technical means, the embodiment of the present application can judge whether the vehicle terminal has completely received the key blacklist by judging whether the vehicle terminal returns the feedback result of whether the key blacklist is received within the second preset time. If the key blacklist is not successfully received, the key blacklist is resent to the vehicle terminal and the number of times is recorded. If the number of retransmissions reaches the predetermined number of times, the retransmission is stopped. If a successful feedback is received, the retransmission operation is not performed, thereby realizing real-time detection of the vehicle terminal, and timely understanding whether the key blacklist is successfully sent, and quickly responding to any errors in sending or failure to receive feedback, and quickly correcting errors or communication problems to ensure that the key blacklist can be successfully sent to the vehicle terminal, and to ensure that the process of canceling the key through the key blacklist is carried out smoothly.

[0017] Optionally, in one embodiment of the present application, the execution result of completing the local blacklist update according to the updated key blacklist and receiving it returned by the digital key controller, and canceling the key according to the execution result, specifically includes: after receiving the execution result sent by the digital key controller, deleting the corresponding key data according to the data of the local blacklist; updating the key status and pushing the key cancellation success information to the client; wherein, the execution result is the execution result of the digital key controller completing the update of the local blacklist data according to the data of the blacklist.

[0018] According to the above-mentioned technical means, the embodiment of the present application can delete the corresponding key data according to the local blacklist data after the digital controller completes the data synchronization of the local blacklist, and push the corresponding deregistration success information to the client after the deregistration is successful, thereby ensuring that the deregistered key is no longer valid, ensuring the consistency of the key blacklist data and the local blacklist data, avoiding security vulnerabilities caused by information conflicts, and notifying the user of the deregistration success in real time, so that the user can quickly know the deregistration status of the key.

[0019] Optionally, in one embodiment of the present application, the execution result of completing the local blacklist update according to the updated key blacklist and receiving it returned by the digital key controller also includes: if the connected key is in the local blacklist, it is determined that the security authentication has failed and the connection with the key is disconnected; when the unconnected key performs key authentication, if the key is in the local blacklist, it is determined that the security authentication has failed and the key connection request of the key is rejected.

[0020] According to the above technical means, the embodiment of the present application can judge the validity of the key after the data of the local blacklist is updated. If the key is connecting, it will be determined that the key security authentication has failed and the connection will be disconnected. If the unconnected key is about to connect, and the unconnected key is on the local blacklist, it will be determined that the security authentication has failed and the key connection request will be rejected. A real-time response method is provided. Regardless of whether the key is connected or not, it will fall within the judgment range, and the key on the blacklist will be blocked from access in time, thereby ensuring the safety of the vehicle, further ensuring the property safety of the user, reducing potential risks and safety issues, and greatly improving user satisfaction.

[0021] The second aspect of the present application provides a vehicle digital key cancellation system, which includes: a request receiving module, which is used to push the key cancellation request to the client when receiving the key cancellation request sent by the user and updating the key status; a blacklist updating module, which is used to update the pre-created key blacklist according to the key cancellation request if the cancellation result feedback from the client is not received within the first preset time; a key cancellation module, which is used to send the updated key blacklist to the digital key controller, receive the execution result returned by the digital key controller of completing the local blacklist update according to the updated key blacklist, and cancel the key according to the execution result.

[0022] Optionally, in one embodiment of the present application, the client includes a car owner end and a shared person end, and the request receiving module includes: a cancellation request receiving unit, used to receive a key cancellation request initiated by the user through the car owner end or the shared person end; a first status update unit, used to update the key status to a pending cancellation status; a cancellation request push unit, used to push the key cancellation request to the car owner end or the shared person end in the form of a message notification.

[0023] Optionally, in one embodiment of the present application, the deregistration result is the execution status feedback of the key deregistration request instruction by the client, and the blacklist update module includes: a first timing unit, which is used to start timing when the key deregistration request is received; and a blacklist adding unit, which is used to add the key corresponding to the key deregistration request to the key blacklist if the deregistration result is not received within the first preset time.

[0024] Optionally, in one embodiment of the present application, the key cancellation module includes: a blacklist transmission unit, which sends the key blacklist to the vehicle terminal, and sends the key blacklist to the digital key controller through the vehicle terminal.

[0025] Optionally, in one embodiment of the present application, the execution result is the execution result of the digital key controller completing the update of the local blacklist data according to the blacklist data, and the key cancellation module also includes: a key cancellation unit, which deletes the corresponding key data according to the local blacklist data after receiving the execution result sent by the digital key controller; a cancellation information push unit, which updates the key status and pushes the key cancellation success information to the client.

[0026] Optionally, in one embodiment of the present application, the system of the embodiment of the present application further includes: a second timing unit, configured to start timing when the key blacklist is sent to the vehicle-mounted terminal; a feedback result judgment unit, configured to judge whether the feedback result sent by the vehicle-mounted terminal is received within a second preset time, wherein the feedback result is the feedback result of the vehicle-mounted terminal when receiving the key blacklist, and the feedback result includes success feedback and error feedback; a retransmission operation unit, configured to send the key blacklist to the vehicle-mounted terminal again if the feedback result is not received within the second preset time or the error feedback is received, and to re-time and record the number of retransmissions; a retransmission judgment unit, configured to make a judgment again based on the timing duration of resending the blacklist until the number of retransmissions reaches the preset number, and stop the operation of resending the key blacklist; a success feedback judgment unit, configured to not resend the key blacklist if the success feedback is received within the second preset time.

[0027] Optionally, in one embodiment of the present application, the system of the embodiment of the present application further includes: a first security authentication unit, for determining that the security authentication has failed and disconnecting the connection with the key if the connected key is in the local blacklist; a second security authentication unit, for determining that the security authentication has failed and rejecting the key connection request of the key when the unconnected key performs key authentication if the key is in the local blacklist.

[0028] A third aspect of the present application provides a vehicle, comprising: a memory, a processor, and a vehicle digital key cancellation program stored on the memory and runnable on the processor, wherein the vehicle digital key cancellation program, when executed by the processor, implements the steps of the vehicle digital key cancellation method as described in the above embodiment.

[0029] The fourth aspect of the present application provides a computer-readable storage medium, which stores a vehicle digital key cancellation program. When the vehicle digital key cancellation program is executed by a processor, it implements the steps of the vehicle digital key cancellation method as described in the above embodiment.

[0030] Beneficial effects of this application:

[0031] (1) In the embodiment of the present application, a key cancellation request can be initiated through the client (the vehicle owner or the shared person). After the vehicle receives the key cancellation request, the key status is updated to the pending cancellation status, and the relevant content of the key cancellation request is sent to the client in the form of a notification. The vehicle owner or the shared person can immediately receive the notification of the key cancellation request, which is convenient for timely processing and feedback, improving the timeliness and efficiency of communication. In addition, the user can initiate the cancellation request on the client without additional steps or complicated processes, providing a convenient user experience and reducing the complexity of operations. At the same time, the key status is updated in real time according to the key cancellation request, so that the user can clearly understand the key status information, making the entire key cancellation process more transparent and convenient for subsequent operations and management.

[0032] (2) The embodiment of the present application can make a preliminary judgment on whether the client has completed the deregistration of the key by whether the deregistration result sent by the client is received within the first preset time. If the deregistration result is still not received within the first preset time, it proves that there may be a problem in the deregistration process. The key deregistration is unsuccessful, and the key corresponding to the key deregistration request is added to the key blacklist, thereby providing immediate deregistration feedback. Even if the deregistration is not successful, there will be a corresponding solution, so that the deregistered key is marked as unusable by the blacklist, preventing the deregistered but unsuccessful key from still being able to access the vehicle, thereby improving the safety of the vehicle and providing better protection for the user's property safety. The user does not need to worry about the key that failed to be deregistered still being able to access the vehicle.

[0033] (3) The embodiment of the present application can judge whether the vehicle terminal has completely received the key blacklist by checking whether the vehicle terminal returns the feedback result of whether the key blacklist has been received within the second preset time. If the key blacklist is not successfully received, the key blacklist is resent to the vehicle terminal and the number of times is recorded. If the number of resends reaches the predetermined number of times, the resend is stopped. If a successful feedback is received, the resend operation is not performed, thereby realizing real-time detection of the vehicle terminal, timely understanding whether the key blacklist has been successfully sent, and quickly responding to any errors in sending or failure to receive feedback, and quickly correcting errors or communication problems to ensure that the key blacklist can be successfully sent to the vehicle terminal and the process of canceling the key through the key blacklist is carried out smoothly.

[0034] (4) The embodiment of the present application can judge the validity of the key after the data of the local blacklist is updated. If the key is connecting, it will be determined that the key security authentication has failed and the connection will be disconnected. If the unconnected key is about to connect, and the unconnected key is on the local blacklist, it will be determined that the security authentication has failed and the key connection request will be rejected. A real-time response method is provided. Regardless of whether the key is connected or not, it will fall within the judgment range, and the key on the blacklist will be blocked from access in time, thereby ensuring the safety of the vehicle, further ensuring the property safety of the user, and reducing potential risks and safety issues.

[0035] (5) The embodiment of the present application can receive a key cancellation request and push it to the client, set a first preset time and determine whether the client has fed back the cancellation result of the key cancellation request within the first preset time. If there is no cancellation, the blacklist push process is automatically initiated, and the updated key blacklist is pushed to the digital key controller. After updating the local blacklist, the key is cancelled according to the local blacklist. By waiting for the cancellation feedback from the client within the preset time, a flexible management method is provided, the reliability of the system is increased, and the timely cancellation of the key is ensured to avoid possible security risks. Moreover, since the cancellation process is automated, no manual intervention is required, the management process is simplified, the workload of manual operations and possible errors in manual operations are reduced, and the efficiency and accuracy of key cancellation are improved. At the same time, it prevents the cancelled digital key from continuing to have access rights due to information asynchrony, ensures that the cancelled key can no longer be used, and further increases the safety of the vehicle.

[0036] Additional aspects and advantages of the present application will be given in part in the description below, and in part will become apparent from the description below, or will be learned through practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the embodiments or descriptions of the prior art. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0038] Figure 1 This is a flowchart of a preferred embodiment of the method for canceling a vehicle digital key of the present application;

[0039] Figure 2 This is a second flow chart of a preferred embodiment of the method for canceling a vehicle digital key of the present application;

[0040] Figure 3 This is a structural diagram of a preferred embodiment of the vehicle digital key cancellation system of the present application;

[0041] Figure 4 This is a schematic structural diagram of a preferred embodiment of the vehicle of the present application.

[0042] Among them, 10-vehicle digital key cancellation system; 100-request receiving module, 200-blacklist update module and 300-key cancellation module; 501-memory, 502-processor and 503-communication interface. DETAILED DESCRIPTION

[0043] The following describes in detail embodiments of the present application, examples of which are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present application, and should not be construed as limiting the present application.

[0044] The following describes a method and related apparatus for canceling a vehicle digital key according to an embodiment of the present application with reference to the accompanying drawings. In response to the technical problem mentioned in the background art above that the prior art does not address the issue of a backend server failing to receive a key feedback result, resulting in information asynchronization between the backend server and the client, and the continued use of a canceled digital key, the present application provides a method for canceling a vehicle digital key. In this method, a key cancellation request can be received and pushed to a client. A first preset time is set and a determination is made as to whether the client has responded to the key cancellation request within the first preset time. If no cancellation is made, a blacklist push process is automatically initiated, an updated key blacklist is pushed to the digital key controller, a local blacklist is updated, and the key is then cancelled according to the local blacklist. By waiting for the client's cancellation feedback within the preset time, a flexible management method is provided, which increases system reliability, ensures timely key cancellation processing, and avoids potential security risks. Furthermore, since the cancellation process is automated, no manual intervention is required, which simplifies the management process, reduces the workload and errors that may occur in manual operations, and improves the efficiency and accuracy of key cancellation. Furthermore, the method prevents a cancelled digital key from continuing to have access rights due to information asynchronization, ensuring that the cancelled key cannot be used again, further increasing vehicle safety. This solves the technical problem in the prior art that the backend server does not receive the key feedback result, resulting in information asynchrony between the backend server and the client, and the cancelled digital key can still be used.

[0045] Specifically, Figure 1 This is a flow chart of a method for canceling a vehicle digital key provided in an embodiment of the present application. Figure 2 This is a second flow chart of a preferred embodiment of a method for canceling a vehicle digital key provided in an embodiment of the present application.

[0046] like Figure 1 and Figure 2 As shown, the method for canceling the vehicle digital key includes the following steps:

[0047] In step S101 , a key cancellation request sent by a user is received, the key status is updated, and the key cancellation request is pushed to the client.

[0048] It can be understood that the client includes the car owner side and the shared person side (that is, the car owner APP and the APP corresponding to the temporary key shared by the car owner through the key sharing operation). The car owner and the shared person can initiate a key cancellation request on the corresponding client. When the car owner initiates a key cancellation request, all shared keys will be cancelled together (including the shared person's key, or the car owner can actively cancel the key of any shared person), and the key cancellation request initiated by the shared person can only cancel his own key; after receiving the key cancellation request initiated by the user on the client, the vehicle updates the key status to pending. Cancellation status (the key status is divided into the key status of the sharee and the key status of the car owner. The key status of the sharee is mainly: to be generated, generated, to be recycled, recycled, to be cancelled, and cancelled. The key status of the car owner is mainly: to be generated, generated, to be cancelled, and cancelled). Then the key cancellation request is pushed to the corresponding client in the form of a message notification (for example, when the sharee cancels the key, it will be sent to the sharee's client in the form of a message notification, and will also be sent to the car owner's end in the form of a message notification; when the car owner cancels the key, the message notification will only be sent to the car owner's end).

[0049] That is to say, this application can initiate a key cancellation request through the client (the car owner or the shared person). After the vehicle (in this application, the vehicle can refer to the TSP, that is, the remote communication service provider or the cloud) receives the key cancellation request, it will update the key status to the pending cancellation status, and send the relevant content of the key cancellation request to the client in the form of a notification. The car owner or the shared person can immediately receive the notification of the key cancellation request, which is convenient for timely processing and feedback, improving the timeliness and efficiency of communication, and the user can initiate a cancellation request on the client without additional steps or complicated processes, providing a convenient user experience and reducing the complexity of operations. At the same time, the key status is updated in real time according to the key cancellation request, so that the user can clearly understand the key status information, making the entire key cancellation process more transparent and convenient for subsequent operations and management.

[0050] In step S102, if the deregistration result fed back by the client is not received within the first preset time, the pre-created key blacklist is updated according to the key deregistration request.

[0051] It is understandable that after receiving the key cancellation request, the client will delete the corresponding key data (such as the owner's key and the shared person's key, etc., specifically expressed as the key ID, the owner's key ID and the shared person's key ID are independent and unique), and then feedback the cancellation result to the vehicle. The cancellation result is the client's execution status feedback of the key cancellation request instruction (for example, cancellation success or cancellation failure, that is, whether cancellation is successful or failed will be fed back). When the vehicle receives the key cancellation request, the timer starts (it can also start when the key status is updated to the pending cancellation state). If it is not within the first preset time (the first The preset time can be set in the background as needed. In a preferred embodiment of the present application, it is 48 hours. If no cancellation result is received from the client within the preset time (whether the cancellation is successful or failed), the key corresponding to the key cancellation request will be added to the key blacklist pre-set on the vehicle; if the cancellation result is received normally, the vehicle will proceed to the next cancellation process according to the cancellation result. If the cancellation result is a successful cancellation, the vehicle will directly delete the key data and revoke the corresponding authority; if the cancellation result is a failed cancellation, the vehicle will analyze the reason for the failure and send it to the client, and prompt the user to re-initiate the key cancellation request.

[0052] It should be noted that when the client logs in the key, the user's identity will be verified to determine whether the user is the car owner or the shared person; when the user initiates a key cancellation request, the user's identity will be verified again to prevent unauthorized people from intentionally deleting or misoperating, which will cause the key to be cancelled.

[0053] That is to say, this application can make a preliminary judgment on whether the client has completed the deregistration of the key by whether the deregistration result sent by the client is received within the first preset time. If the deregistration result is still not received within the first preset time, it proves that there may be a problem in the deregistration process, and the key deregistration is unsuccessful. The key corresponding to the key deregistration request will be added to the key blacklist, thereby providing instant deregistration feedback. Even if the deregistration is not successful, there will be a corresponding solution, so that the deregistered key will be marked as unusable on the blacklist, preventing the deregistered but unsuccessful key from still being able to access the vehicle, thereby improving the safety of the vehicle and providing better protection for the user's property safety. The user does not need to worry about the key that failed to be deregistered still being able to access the vehicle, thereby improving the user experience.

[0054] In step S103, the updated key blacklist is sent to the digital key controller, and the execution result of completing the local blacklist update according to the updated key blacklist returned by the digital key controller is received, and the key is cancelled according to the execution result.

[0055] It can be understood that after adding the keys that have not received feedback on the cancellation results for more than the first preset time to the key blacklist, the vehicle will send the key blacklist to the on-board terminal (in this application, the on-board terminal can refer to the on-board information assembly THU). When the on-board terminal receives the key blacklist issuance notification sent by the vehicle, it sends a receive signal (for example: TBOX_EseUpdataHUWakeUpReq) to the vehicle and downloads the corresponding key blacklist data. After downloading the key blacklist data, the on-board terminal will send the key blacklist to the digital key controller through the data stream message communication specification of the signal bus (for example: CAN bus).

[0056] In other words, the present application can synchronize the key blacklist to the digital key controller through the vehicle terminal, so that the digital key controller also has a local blacklist with the same content as the key blacklist, ensuring the timely update of the local blacklist of the digital key controller, avoiding message asymmetry, and effectively preventing the blacklisted keys from continuing to be used. There is also no need to request access to the key blacklist again every time the key is verified, which reduces the workflow, improves the efficiency of key verification, improves the protection capability of the system, and increases the convenience of key verification.

[0057] Furthermore, the present application starts timing when the vehicle sends the key blacklist to the on-board terminal, and waits for the on-board terminal to send a feedback result, and determines whether the feedback result sent by the on-board terminal is received within a second preset time (the second preset time can also be set in the background as needed, and is 180 seconds in a preferred embodiment of the present invention), wherein the feedback result is the feedback result of the on-board terminal when receiving the key blacklist, and the feedback result specifically includes success feedback (that is, reception success feedback) and error feedback (that is, reception failure feedback, such as data format error feedback), that is, it is actually a process of determining whether the on-board terminal has successfully received the key blacklist; if the vehicle does not receive the feedback result or error feedback sent by the on-board terminal within the second preset time, it proves that the on-board terminal If the key blacklist is not received, the vehicle will send the key blacklist to the on-board terminal again, and reset the time and record the number of retransmissions each time it is resent, and judge again whether the successful feedback sent by the on-board terminal is received within the second preset time. If not, it will continue to resend, but when the number of retransmissions reaches the preset number, it will stop the resending operation (for example, the preset number of times is two, plus the first sending, the key blacklist is sent up to three times, but the preset number of times can also be set as needed). At this time, the vehicle will determine that the key blacklist has failed to be sent, and wait for resending the next time the vehicle is online; if the vehicle receives successful feedback sent by the on-board terminal within the second preset time, it proves that the on-board terminal has successfully received the key blacklist, and the vehicle will no longer resend it to the on-board terminal.

[0058] It should be noted that after the vehicle determines that the key blacklist has failed to be sent, it will resend it the next time the onboard terminal is online, where the onboard terminal being online refers to when the onboard terminal is connected to the Internet and has data interaction needs with the vehicle. In addition, while the vehicle is waiting for the onboard terminal to return the feedback result, the vehicle cannot send other blacklist data. In other words, during the entire process of processing the key blacklist, the vehicle cannot process other data sending requests in parallel. Only after the current key blacklist is successfully or unsuccessfully sent can other data be sent. Only after the entire key blacklist sending process is completed can other blacklist data be sent.

[0059] That is to say, the present application can judge whether the vehicle terminal has completely received the key blacklist by judging whether the vehicle terminal returns the feedback result of whether the key blacklist is received within the second preset time. If the key blacklist is not successfully received, the key blacklist is resent to the vehicle terminal and the number of times is recorded. If the number of retransmissions reaches the predetermined number of times, the retransmission is stopped. If a successful feedback is received, the retransmission operation is not performed, thereby realizing real-time detection of the vehicle terminal, and timely understanding whether the key blacklist is successfully sent, and quickly responding to any errors in sending or failure to receive feedback, and quickly correcting errors or communication problems to ensure that the key blacklist can be successfully sent to the vehicle terminal, and to ensure that the process of canceling the key through the key blacklist is carried out smoothly.

[0060] Furthermore, when the digital key controller receives the key blacklist sent by the vehicle terminal, it will update the local blacklist set on the digital key controller according to the key blacklist (that is, synchronize the local blacklist and the key blacklist data), and then the digital key controller returns the updated execution result to the vehicle after the update. After receiving the execution result of the digital key controller, the vehicle will delete the corresponding key data according to the data in the local blacklist, and then update the key status to cancelled, and push the key cancellation success information to the client through message notification.

[0061] That is to say, after the digital controller completes the data synchronization of the local blacklist, this application can delete the corresponding key data according to the local blacklist data, and push the corresponding deregistration success information to the client after the deregistration is successful, thereby ensuring that the deregistered key is no longer valid, ensuring the consistency of the key blacklist data and the local blacklist data, avoiding security vulnerabilities caused by information conflicts, and notifying the user of the deregistration success in real time, so that the user can quickly know the deregistration status of the key.

[0062] It should be noted that, after the digital key controller completes the update of the local blacklist, if the connected key is on the local blacklist, the vehicle will determine that the key has failed security authentication and disconnect the key. If the unconnected key is on the local blacklist during key authentication, the vehicle will also determine that the security authentication has failed and reject the key connection request. In addition, the local blacklist of the digital key controller is capped at 50 keys (configurable according to user needs). When the limit is exceeded, the keys in the local blacklist are updated using a first-in-first-out method.

[0063] That is to say, this application can judge the validity of the key after the data in the local blacklist is updated. If the key is connecting, the key security authentication will be deemed to have failed and the connection will be disconnected. If the unconnected key is about to connect, and the unconnected key is on the local blacklist, the security authentication will be deemed to have failed and the key connection request will be rejected. This provides a real-time response method. Regardless of whether the key is connected or not, it will fall within the judgment range, and the key on the blacklist will be blocked from access in a timely manner, thereby ensuring the safety of the vehicle, further ensuring the property safety of the user, reducing potential risks and safety issues, and greatly improving user satisfaction.

[0064] In summary, the embodiment of the present application can receive a key cancellation request and push it to the client, set a first preset time and determine whether the client has fed back the cancellation result of the key cancellation request within the first preset time. If there is no cancellation, the blacklist push process is automatically initiated, and the updated key blacklist is pushed to the digital key controller. After updating the local blacklist, the key is cancelled according to the local blacklist. By waiting for the client's cancellation feedback within the preset time, a flexible management method is provided, the reliability of the system is increased, and the timely cancellation of the key is ensured to avoid possible security risks. Moreover, since it is an automated cancellation process, no manual intervention is required, the management process is simplified, the workload of manual operations and possible errors in manual operations are reduced, and the efficiency and accuracy of key cancellation are improved. At the same time, it prevents the cancelled digital key from continuing to have access rights due to information asynchrony, ensures that the cancelled key can no longer be used, and further increases the safety of the vehicle.

[0065] Next, the vehicle digital key cancellation system proposed in accordance with an embodiment of the present application will be described with reference to the accompanying drawings.

[0066] Figure 3 It is a block diagram of a vehicle digital key cancellation system according to an embodiment of the present application.

[0067] like Figure 3 As shown, the vehicle digital key cancellation system 10 includes: a request receiving module 100, a blacklist updating module 200, and a key cancellation module 300.

[0068] Specifically, the request receiving module 100 is used to receive a key cancellation request sent by a user and update the key status, and push the key cancellation request to the client;

[0069] The blacklist updating module 200 is configured to update a pre-created key blacklist according to the key cancellation request if no cancellation result is received from the client within a first preset time;

[0070] The key cancellation module 300 is used to send the updated key blacklist to the digital key controller, receive the execution result returned by the digital key controller of completing the local blacklist update according to the updated key blacklist, and cancel the key according to the execution result.

[0071] Optionally, in one embodiment of the present application, the client includes a vehicle owner end and a shared person end, and the request receiving module 100 includes: a cancellation request receiving unit and a first status updating unit.

[0072] The deregistration request receiving unit is configured to receive a key deregistration request initiated by a user via the vehicle owner terminal or the shared person terminal;

[0073] A first state updating unit, configured to update the key state to a pending cancellation state;

[0074] The cancellation request pushing unit is used to push the key cancellation request to the car owner terminal or the shared person terminal in the form of a message notification.

[0075] Optionally, in one embodiment of the present application, the deregistration result is the execution status feedback of the key deregistration request instruction by the client, and the blacklist updating module 200 includes: a first timing unit and a blacklist adding unit.

[0076] Wherein, the first timing unit is used to start timing when receiving the key cancellation request;

[0077] The blacklist adding unit is configured to add the key corresponding to the key cancellation request to the key blacklist if the cancellation result is not received within the first preset time.

[0078] Optionally, in one embodiment of the present application, the key cancellation module 300 includes: a blacklist transmission unit.

[0079] The blacklist transmission unit sends the key blacklist to the vehicle terminal, and sends the key blacklist to the digital key controller through the vehicle terminal.

[0080] Optionally, in one embodiment of the present application, the execution result is the execution result of the digital key controller completing the update of the local blacklist data according to the blacklist data, and the key cancellation module 300 also includes: a key cancellation unit and a cancellation information push unit.

[0081] wherein the key cancellation unit, upon receiving the execution result sent by the digital key controller, deletes the corresponding key data according to the data in the local blacklist;

[0082] The deregistration information push unit updates the key status and pushes the key deregistration success information to the client.

[0083] Optionally, in one embodiment of the present application, the vehicle digital key cancellation system 10 of the embodiment of the present application further includes: a second timing unit, a feedback result judgment unit, a resending operation unit, a resending judgment unit and a success feedback judgment unit.

[0084] Wherein, the second timing unit is used to start timing when the key blacklist is sent to the vehicle terminal;

[0085] A feedback result judging unit, configured to judge whether a feedback result sent by the vehicle terminal is received within a second preset time, wherein the feedback result is a feedback result of the vehicle terminal when receiving the key blacklist, and the feedback result includes success feedback and error feedback;

[0086] a resending operation unit, configured to resend the key blacklist to the vehicle terminal if the feedback result is not received within the second preset time or the error feedback is received, and to re-time and record the number of resending times;

[0087] A resending judgment unit is used to make a judgment again according to the timing length of resending the blacklist until the number of resending times reaches a preset number, and then stop the operation of resending the key blacklist;

[0088] The success feedback judgment unit is configured to not send the key blacklist again if the success feedback is received within the second preset time.

[0089] Optionally, in one embodiment of the present application, the vehicle digital key cancellation system 10 of the embodiment of the present application further includes: a first security authentication unit and a second security authentication unit.

[0090] The first security authentication unit is configured to determine that the security authentication has failed and disconnect the key if the connected key is in the local blacklist;

[0091] The second security authentication unit is configured to, when an unconnected key performs key authentication, determine that the security authentication fails and reject the key connection request of the key if the key is in the local blacklist.

[0092] It should be noted that the above explanation of the embodiment of the vehicle digital key cancellation method is also applicable to the vehicle digital key cancellation system of this embodiment, and will not be repeated here.

[0093] According to the vehicle digital key cancellation system proposed in the embodiment of the present application, a key cancellation request can be received and pushed to the client, a first preset time can be set, and it can be determined whether the client has fed back the cancellation result of the key cancellation request within the first preset time. If there is no cancellation, a blacklist push process is automatically initiated, and the updated key blacklist is pushed to the digital key controller. After updating the local blacklist, the key is cancelled according to the local blacklist. By waiting for the client's cancellation feedback within the preset time, a flexible management method is provided, the reliability of the system is increased, and the timely cancellation of the key is ensured to avoid possible security risks. Moreover, since the cancellation process is automated, no manual intervention is required, the management process is simplified, the workload of manual operations and possible errors in manual operations are reduced, and the efficiency and accuracy of key cancellation are improved. At the same time, it prevents the cancelled digital key from continuing to have access rights due to information asynchrony, ensures that the cancelled key can no longer be used, and further increases the safety of the vehicle.

[0094] This solves the technical problem in the prior art that the backend server does not receive the key feedback result, resulting in information asynchrony between the backend server and the client, and the cancelled digital key can still be used.

[0095] Figure 4 A schematic diagram of the structure of a vehicle provided in an embodiment of the present application. The vehicle may include:

[0096] Memory 501 , processor 502 , and computer programs stored in the memory 501 and executable on the processor 502 .

[0097] When the processor 502 executes the program, the vehicle digital key cancellation method provided in the above embodiment is implemented.

[0098] Furthermore, the vehicle further comprises:

[0099] The communication interface 503 is used for communication between the memory 501 and the processor 502 .

[0100] The memory 501 is used to store computer programs that can be run on the processor 502 .

[0101] The memory 501 may include a high-speed RAM memory, and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.

[0102] If the memory 501, processor 502, and communication interface 503 are implemented independently, the communication interface 503, memory 501, and processor 502 can be connected to each other via a bus and communicate with each other. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EIS) bus. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 4 Only one thick line is used in the diagram, but this does not mean that there is only one bus or one type of bus.

[0103] Optionally, in a specific implementation, if the memory 501, the processor 502 and the communication interface 503 are integrated on a chip, the memory 501, the processor 502 and the communication interface 503 can communicate with each other through an internal interface.

[0104] The processor 502 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application.

[0105] This embodiment also provides a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, the above-mentioned method for canceling a vehicle digital key is implemented.

[0106] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described can be combined in any one or N embodiments or examples in a suitable manner. In addition, those skilled in the art can combine and combine different embodiments or examples described in this specification and features of different embodiments or examples without contradiction.

[0107] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be understood to indicate or imply relative importance or implicitly specify the number of technical features indicated. Thus, a feature specified as "first" or "second" may explicitly or implicitly include at least one such feature. In the description of this application, "N" means at least two, for example, two, three, etc., unless otherwise specifically defined.

[0108] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, fragment or portion of code comprising one or N executable instructions for implementing a custom logical function or process step, and the scope of the preferred embodiments of the present application includes alternative implementations in which functions may be performed in a different order than shown or discussed, including performing functions in a substantially simultaneous manner or in a reverse order depending on the functions involved, which should be understood by those skilled in the art to which the embodiments of the present application pertain.

[0109] The logic and / or steps represented in the flowcharts or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing the logical functions, and can be embodied in any computer-readable storage medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (e.g., a computer-based system, a system including a processor, or other system that can fetch and execute instructions from an instruction execution system, apparatus, or device). For purposes of this specification, a "computer-readable storage medium" can be any device that can contain, store, communicate, propagate, or transport a program for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of computer-readable storage media include the following: an electrical connection having one or N wires (electronic devices), a portable computer disk cartridge (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable and programmable read-only memory (EPROM or flash memory), a fiber optic device, and a portable compact disc read-only memory (CDROM). In addition, the computer-readable storage medium may even be paper or other suitable medium on which the program is printed, since the program can be obtained electronically by optically scanning the paper or other medium and then editing, interpreting or processing it in other suitable ways as necessary, and then storing it in a computer memory.

[0110] It should be understood that various parts of the present application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiment, the N steps or methods can be implemented using software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented using hardware, as in another embodiment, any one of the following technologies known in the art or a combination thereof can be used to implement: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application-specific integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

[0111] Those skilled in the art will understand that all or part of the steps in the method of the above embodiment can be completed by instructing related hardware through a program, and the program can be stored in a computer-readable storage medium. When the program is executed, it includes one or a combination of the steps of the method embodiment.

[0112] In addition, the functional units in the various embodiments of the present application may be integrated into a processing module, or each unit may exist physically separately, or two or more units may be integrated into a module. The above-mentioned integrated module may be implemented in the form of hardware or in the form of a software functional module. If the integrated module is implemented in the form of a software functional module and sold or used as an independent product, it may also be stored in a computer-readable storage medium.

[0113] The storage medium mentioned above may be a read-only memory, a magnetic disk, or an optical disk, etc. Although the embodiments of the present application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present application. Persons skilled in the art may make changes, modifications, substitutions, and variations to the above embodiments within the scope of the present application.

[0114] It should be understood that the application of this application is not limited to the above examples. For ordinary technicians in this field, they can make improvements or changes based on the above description. All these improvements and changes should fall within the scope of protection of the claims attached to this application.

Claims

1. A method for cancelling a vehicle digital key, wherein the method is applied to a vehicle and is characterized in that: The method for cancelling the vehicle digital key includes: Receive the key cancellation request sent by the user and update the key status, and push the key cancellation request to the client; The client includes the car owner's terminal and the shared person's terminal; The receiving a key cancellation request sent by the user and updating the key status, and pushing the key cancellation request to the client, specifically includes: receiving a key cancellation request initiated by the user through the car owner terminal or the shared person terminal; Update the key status to pending cancellation; Pushing the key cancellation request to the car owner terminal or the shared person terminal in the form of a message notification; If the deregistration result fed back by the client is not received within the first preset time, the pre-created key blacklist is updated according to the key deregistration request; The updated key blacklist is sent to the digital key controller, an execution result of completing the local blacklist update according to the updated key blacklist is received from the digital key controller, and the key is deregistered according to the execution result.

2. The method for canceling a vehicle digital key according to claim 1, characterized in that: If the deregistration result fed back by the client is not received within the first preset time, updating the pre-created key blacklist according to the key deregistration request specifically includes: starting the timer when the key deregistration request is received; If the cancellation result is not received within the first preset time, adding the key corresponding to the key cancellation request to the key blacklist; The deregistration result is the execution status feedback of the key deregistration request instruction by the client.

3. The method for canceling a vehicle digital key according to claim 1, wherein: Sending the updated key blacklist to the digital key controller specifically includes: The key blacklist is sent to a vehicle terminal, and the key blacklist is sent to the digital key controller via the vehicle terminal.

4. The method for canceling a vehicle digital key according to claim 3, characterized in that: The step of sending the key blacklist to the vehicle terminal further includes: The timing starts when the key blacklist is sent to the vehicle terminal; Determining whether a feedback result sent by the vehicle terminal is received within a second preset time, wherein the feedback result is a feedback result of the vehicle terminal when receiving the key blacklist, and the feedback result includes success feedback and error feedback; If the feedback result is not received within the second preset time or the error feedback is received, the key blacklist is sent to the vehicle terminal again, and the timing and resending times are restarted; The judgment is made again according to the time length of the resending of the blacklist, until the resending times reaches a preset number, and the operation of resending the key blacklist is stopped; If the success feedback is received within the second preset time, the operation of sending the key blacklist again is not performed.

5. The method for canceling a vehicle digital key according to claim 1, characterized in that: The receiving, returned by the digital key controller, an execution result of completing the local blacklist update according to the updated key blacklist, and performing a key cancellation process according to the execution result, specifically includes: After receiving the execution result sent by the digital key controller, deleting the corresponding key data according to the data in the local blacklist; updating the key status and pushing the key cancellation success information to the client; The execution result is the execution result of the digital key controller completing the update of the local blacklist data according to the blacklist data.

6. The method for canceling a vehicle digital key according to claim 1, characterized in that: The receiving of the execution result of completing the local blacklist update according to the updated key blacklist returned by the digital key controller further includes: If the connected key is in the local blacklist, it is determined that the security authentication has failed and the connection with the key is disconnected; When a key that is not connected performs key authentication, if the key is in the local blacklist, it is determined that the security authentication has failed and the key connection request of the key is rejected.

7. A vehicle digital key cancellation system, characterized in that: The vehicle digital key cancellation system is applied to the vehicle digital key cancellation method according to any one of claims 1 to 6, and the vehicle digital key cancellation system includes: A request receiving module, configured to receive a key cancellation request from a user, update the key status, and push the key cancellation request to the client; A blacklist updating module, configured to update a pre-created key blacklist according to the key cancellation request if no cancellation result fed back by the client is received within a first preset time; The key cancellation module is used to send the updated key blacklist to the digital key controller, receive the execution result returned by the digital key controller of completing the local blacklist update according to the updated key blacklist, and cancel the key according to the execution result.

8. A vehicle, characterized in that: The vehicle includes: a memory, a processor, and a vehicle digital key cancellation program stored in the memory and runnable on the processor. When the vehicle digital key cancellation program is executed by the processor, the steps of the vehicle digital key cancellation method as described in any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a cancellation program for a vehicle digital key, and when the cancellation program for the vehicle digital key is executed by a processor, the steps of the vehicle digital key cancellation method according to any one of claims 1 to 6 are implemented.

Images