Vehicle end calibration method, device and medium

By employing secure authentication and remote calibration methods at both the cloud and vehicle ends, the security risks associated with the lifetime use of vehicle keys are resolved. This enables remote key updates and rapid, secure management, thereby improving vehicle security and convenience.

CN119155684BActive Publication Date: 2026-03-31ANHUI JIANGHUAI AUTOMOBILE GRP CORP LTD
View PDF 1 Cites 0 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-09-24
Publication Date
2026-03-31

AI Technical Summary

Technical Problem

In existing technologies, once a vehicle's security key is written, it is used for life, posing a security risk of being leaked or cracked. Furthermore, updating the key requires manual operation at a 4S store, which cannot be handled in a timely manner and poses risks to property and personal safety.

Method used

After secure authentication between the cloud and the vehicle, it receives remote calibration commands, performs validity verification and parsing, controls the ECU to perform calibration, and verifies the actual results, thereby enabling remote key updates and secure management.

Benefits of technology

It improves vehicle security, allowing for quick and easy modification and locking of the vehicle in case the key is cracked, preventing theft or tampering. Key issues are handled conveniently and efficiently, without the need for professional diagnostic tools.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119155684B_ABST
    Figure CN119155684B_ABST
Patent Text Reader

Abstract

The present disclosure relates to a vehicle end calibration method, belonging to the technical field of vehicles. The method comprises: receiving a remote calibration instruction issued by a cloud end; replying whether a current state of the cloud end can calibrate; when replying that the cloud end can calibrate, receiving a calibration instruction package sent by the cloud end; checking validity and integrity of the calibration instruction package; if the checking passes, analyzing the calibration instruction package to obtain analysis data; based on the analysis data, controlling an ECU to execute calibration; checking an actual result after calibration; and if the checking succeeds, returning a calibration success result to the cloud end. The present disclosure improves the safety of vehicle use, and when a key is cracked and a vehicle is misused, the key can be changed in time and quickly through the cloud end to lock the vehicle. Remote calibration in the present disclosure makes calibration no longer dependent on professional diagnostic tools, and it is more convenient and efficient to handle key-induced faults or safety problems.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure pertains to the field of vehicle technology, and particularly relates to a vehicle-side calibration method, apparatus, and medium. Background Technology

[0002] With the rapid development of intelligent and connected vehicle technologies, major OEMs are increasingly emphasizing the intelligent service functions of vehicles, such as remote vehicle control and digital keys. The implementation architecture of these functions often involves an app or cloud-based system sending commands to the in-vehicle terminal, which then relays these commands to various vehicle actuators for execution. This involves numerous secure key exchanges and authentications between the in-vehicle terminal and the actuators. However, current key management for vehicles often follows a "write-once, use-for-life" principle. Typically, once the vehicle is successfully calibrated after production, the key remains unchanged. Subsequent key updates require manual rewriting at a dealership. This approach poses certain security risks: if the key is leaked or cracked, vehicle information could be stolen or altered, leading to financial losses and even personal safety risks for car owners and users. Furthermore, if functional problems arise due to the vehicle's security key, OEMs cannot provide customers with a timely and effective solution.

[0003] The current technical solution involves randomly generating or writing a fixed key during the initialization of the software of key ECUs (such as BCM and ECM) in the vehicle. During the end-of-life (EOL) testing after the vehicle rolls off the production line, a diagnostic service is used to calibrate and learn the two ECUs (such as TBOX and BCM) that require communication authentication, in order to obtain the key needed for subsequent vehicle control. After calibration, the vehicle is removed from the production line if the learning result is successful. This key is then used continuously until the vehicle is scrapped, provided there are no abnormalities. If an anomaly occurs and the key needs to be updated, it must be manually calibrated using a diagnostic tool by staff from the 4S store or manufacturer. Once the key is successfully exchanged, it is never updated. If the vehicle's security key is illegally stolen and used during operation, neither the customer nor the OEM has an immediate and effective method to lock the vehicle for tracking. Summary of the Invention

[0004] This disclosure proposes a vehicle-side calibration method, apparatus, and medium to solve the aforementioned technical problems.

[0005] According to a first aspect of this disclosure, a vehicle calibration method is provided, the method comprising: receiving a remote calibration command sent from the cloud; responding to the cloud regarding whether calibration can be performed; when responding to the cloud that calibration is possible, receiving a calibration command packet sent from the cloud; verifying the validity and completeness of the calibration command packet; if the verification passes, parsing the calibration command packet to obtain parsed data; controlling the ECU to perform calibration based on the parsed data; verifying the actual calibration result; and if the verification is successful, returning the calibration success result to the cloud.

[0006] In some embodiments, calibration ends when the cloud cannot be calibrated.

[0007] In some embodiments, if the verification fails, a verification failure message is returned to the cloud, and the calibration ends.

[0008] In some embodiments, verifying the actual calibration result includes: enabling two ECUs that need to exchange keys to perform routine learning, with one ECU responsible for teaching the key and the other responsible for learning the key. When the ECU learning the key receives the key, it stores it in a register and sends it to the CAN bus in the form of a CAN frame. When the learning key frame is received, it compares the learning key frame with the teaching key frame. If the comparison result is the same, the calibration is successful.

[0009] In some embodiments, before receiving the remote calibration command issued by the cloud, the method further includes: establishing a communication connection with the cloud, wherein the cloud combines the vehicle VIN code, cloud server IP address, current timestamp, and generated random number, and generates a communication key using the AES encryption algorithm; storing the communication key; receiving assembled encrypted information, wherein the cloud assembles and encrypts the serial number of the current communication message and the communication key to obtain assembled encrypted information; calculating and comparing the key for correctness; if correct, performing a second encryption on the first encryption result to obtain a second encryption result, and sending it to the cloud, wherein the cloud decrypts the second encryption result and compares the key information for correctness; if correct, passing security authentication, and issuing the remote calibration command.

[0010] According to a second aspect of this disclosure, a vehicle-side calibration device is provided, comprising: a remote calibration command receiving module for receiving remote calibration commands sent from the cloud; a calibration capability response module for responding to the cloud regarding whether calibration is currently possible; a calibration command packet receiving module for receiving a calibration command packet sent from the cloud when the cloud responds that calibration is possible; a calibration command packet verification module for verifying the validity and completeness of the calibration command packet; a calibration command packet parsing module for parsing the calibration command packet to obtain parsed data if the verification passes; a calibration control module for controlling the ECU to perform calibration based on the parsed data; a calibration result verification module for verifying the actual calibration result; and a calibration success result return module for returning a calibration success result to the cloud if the verification is successful.

[0011] According to a third aspect of this disclosure, a vehicle calibration apparatus is provided, comprising: a memory; and a processor coupled to the memory, the processor being configured to perform the vehicle calibration method as described above based on instructions stored in the memory.

[0012] According to a fourth aspect of this disclosure, a computer-storeable medium is provided having computer program instructions stored thereon, which, when executed by a processor, implement the vehicle-end calibration method as described above.

[0013] The beneficial effects of this disclosure are: improved vehicle security; in the event of a key breach and vehicle theft, the key can be changed and the vehicle locked quickly and promptly via the cloud; and remote calibration eliminates the need for specialized diagnostic tools, making it more convenient and efficient to handle key-related faults or security issues. Attached Figure Description

[0014] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments of the present disclosure and, together with their description, serve to explain the principles of the present disclosure.

[0015] Figure 1 This is a flowchart illustrating a vehicle-end calibration method according to some embodiments of the present disclosure.

[0016] Figure 2 This is a block diagram illustrating a vehicle-end calibration device according to some embodiments of the present disclosure.

[0017] Figure 3 This is a block diagram illustrating a vehicle-end calibration device according to other embodiments of the present disclosure.

[0018] Figure 4 This is a block diagram illustrating a computer system for implementing some embodiments of the present disclosure. Detailed Implementation

[0019] Various exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. It should be noted that, unless otherwise specifically stated, the relative arrangement, numerical expressions, and values ​​of the components and steps set forth in these embodiments do not limit the scope of the present disclosure.

[0020] At the same time, it should be understood that, for ease of description, the dimensions of the various parts shown in the accompanying drawings are not drawn according to actual scale.

[0021] The following description of at least one exemplary embodiment is merely illustrative and is in no way intended to limit this disclosure or its application or use.

[0022] Techniques, methods, and equipment known to those skilled in the art may not be discussed in detail, but where appropriate, such techniques, methods, and equipment should be considered part of the specification.

[0023] In all examples shown and discussed herein, any specific values ​​should be interpreted as merely exemplary and not as limitations. Therefore, other examples of exemplary embodiments may have different values.

[0024] It should be noted that similar labels and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be discussed further in subsequent figures.

[0025] Currently, vehicle-side key management often adopts the principle of "write once, use forever." Typically, once the vehicle is successfully calibrated after production, it remains unchanged. Subsequent key updates require manual rewriting at a dealership. This method poses certain security risks: if the key is leaked or cracked, vehicle information may be stolen or tampered with, leading to financial losses and even personal safety risks for car owners and users. Furthermore, if functional problems arise due to the vehicle-side security key, the OEM cannot provide customers with a timely and effective solution.

[0026] In view of this, this disclosure proposes a vehicle-side calibration method, device, and medium, which improves the security of vehicle use. When the key is cracked and the vehicle is stolen, the key can be changed quickly and promptly via the cloud to lock the vehicle. Remote calibration eliminates the need for professional diagnostic tools, making it more convenient and efficient to handle key-related faults or security issues.

[0027] Figure 1 This is a flowchart illustrating a vehicle-side calibration method according to some embodiments of the present disclosure. For example... Figure 1 As shown, the vehicle-side calibration method includes steps 110 to 180.

[0028] Before officially starting the calibration process, security authentication needs to be performed on both the cloud and the terminal.

[0029] Security authentication method: When the vehicle terminal registers with the cloud for the first time, it reports the Vehicle Identification Number (VIN), which is then stored in the cloud. Due to the importance of the data calibration function, the platform only authorizes this function to relevant management personnel accounts;

[0030] Each time the vehicle-mounted terminal establishes a connection with the cloud, the cloud generates a communication key using the AES encryption algorithm, combining information such as the vehicle's VIN code, the cloud server's IP address, the current timestamp, and a generated random number. The vehicle-mounted terminal stores this key.

[0031] The cloud assembles and encrypts the current communication message based on the serial number, the key generated when the connection was established, and other information, and then sends it to the terminal. After receiving it, the terminal first calculates and compares whether the key is correct. If it is correct, it mixes the result of the first encryption with the serial number, timestamp and other information for a second encryption and sends it to the cloud. If it is incorrect, the terminal refuses to perform subsequent calibration operations.

[0032] The cloud receives the secondary encryption result sent by the terminal, decrypts it, and compares whether the key information is correct. If it is correct, the security authentication is successful and the next calibration operation can be performed. If it is incorrect, the authentication fails and the calibration operation is not performed.

[0033] When the remote calibration function is executed, security authentication is performed first. During the entire calibration process, the cloud automatically performs security authentication with the terminal every minute. If the authentication fails, the current action is terminated.

[0034] In step 110, a remote calibration command is received from the cloud.

[0035] In step 120, reply to the cloud to check if the current status allows for calibration.

[0036] In some embodiments, the cloud sends a remote calibration command to the terminal. After receiving the command, the terminal replies with its current status indicating whether calibration can be performed. If the reply is successful, the next step is executed. If the reply status is busy, i.e., it conflicts with other tasks, the cloud waits for the terminal to reply successfully before executing the next step. If the cloud waits for more than 5 minutes, the task is terminated, and a message is displayed indicating that the vehicle terminal is currently busy and to try again. The task needs to be resent. If the terminal reply fails, the cloud tries 3 times. If it still fails, it returns a failure message.

[0037] In step 130, when the cloud responds that calibration is possible, the calibration instruction packet sent by the cloud is received.

[0038] In step 140, the validity and integrity of the calibration instruction package are verified.

[0039] In some embodiments, after the terminal responds successfully, the cloud performs calibration on the vehicle through the UDS diagnostic protocol, packages the instructions that need to be sent during the calibration process and sends them to the vehicle terminal. After receiving the instruction package, the terminal verifies the validity and completeness of the instruction package. If the verification passes, the next step is executed. If the verification fails, a failure message indicating that the instruction package verification failed is returned to the cloud, and the task ends.

[0040] In step 150, if the verification passes, the calibration instruction packet is parsed to obtain the parsed data.

[0041] In step 160, based on the parsed data, the control ECU performs calibration.

[0042] In step 170, the actual results after calibration are verified.

[0043] In some embodiments, the terminal parses the valid instruction packet and sends it to the vehicle's CAN network in the form of a CAN message. It controls the calibration of the two ECUs to be calibrated. The terminal acts as a detector during the ECU calibration stage to verify the actual result of the ECU completing the calibration.

[0044] In some embodiments, verifying the actual calibration result includes: adding a detection terminal to verify the actual calibration result during the calibration process of two ECUs that need to exchange keys; the terminal first enters the detection state, and then normally controls the two ECUs that need to exchange keys to perform routine learning, one is responsible for teaching the key, and the other is responsible for learning the key; when the ECU learning the key receives the key, it stores it in the register and immediately sends this data to the CAN bus in the form of a CAN frame; after the terminal receives the learned key frame, it compares it with the key teaching frame that was just received. If they are the same, the calibration is successful. If they are different or the learned key frame is not received within a timeout (e.g., 10s), the terminal returns failure. The terminal recalibrates the failed result twice. If the retry still fails, it directly returns failure.

[0045] In step 180, if the verification is successful, the calibration success result is returned to the cloud.

[0046] In some embodiments, if the verification is successful, the terminal will send the calibration success result back to the cloud, and the cloud will indicate that the calibration was successful and end the task. If the verification fails, the terminal will choose to re-execute the calibration process twice according to the failure prompt in the verification process. If the retry still fails, the terminal will return a failure to the cloud and end the task.

[0047] This disclosure provides a secure authentication method for remote calibration between the cloud and the vehicle, ensuring the security of remote calibration. It also provides a cloud-based method for calibrating vehicle-side security keys, enabling remote key updates. Furthermore, this disclosure allows for verification of the actual calibration results, ensuring the accuracy of the actual key calibration results for the entire vehicle.

[0048] Figure 2 This is a block diagram illustrating a vehicle-end calibration device according to some embodiments of the present disclosure. For example... Figure 2 As shown, the vehicle-side calibration device 200 includes a remote calibration command receiving module 210, a calibration response module 220, a calibration command packet receiving module 230, a calibration command packet verification module 240, a calibration command packet parsing module 250, a calibration control module 260, a calibration result verification module 270, and a calibration success result return module 280.

[0049] The remote calibration command receiving module 210 is configured to receive remote calibration commands sent from the cloud.

[0050] Whether the response module 220 can be calibrated, and whether it is configured to calibrate the current status of the cloud response;

[0051] The calibration instruction packet receiving module 230 is configured to receive calibration instruction packets sent by the cloud when the cloud responds that calibration is possible;

[0052] The calibration instruction packet verification module 240 is configured to verify the validity and integrity of the calibration instruction packet;

[0053] The calibration instruction packet parsing module 250 is configured to parse the calibration instruction packet and obtain parsed data if the verification passes.

[0054] The calibration control module 260 is configured to control the ECU to perform calibration based on the parsed data;

[0055] The calibration result verification module 270 is configured to verify the actual results after calibration.

[0056] The calibration success result return module 280 is configured to return a calibration success result to the cloud if the verification is successful.

[0057] The device in this embodiment improves vehicle security. When the key is cracked and the vehicle is stolen, the key can be changed quickly and promptly via the cloud to lock the vehicle. Remote calibration eliminates the need for specialized diagnostic tools, making it more convenient and efficient to handle key-related faults or security issues.

[0058] Figure 3 This is a block diagram illustrating a vehicle-end calibration device according to other embodiments of the present disclosure.

[0059] like Figure 3 As shown, the vehicle calibration apparatus 300 includes a memory 310 and a processor 320 coupled to the memory 310. The memory 310 is used to store instructions for executing embodiments of the vehicle calibration method. The processor 320 is configured to execute the vehicle calibration method in any of the embodiments of this disclosure based on the instructions stored in the memory 310.

[0060] Figure 4 This is a block diagram illustrating a computer system for implementing some embodiments of the present disclosure. Figure 4 As shown, the computer system 400 can be represented in the form of a general computing device. The computer system 400 includes a memory 410, a processor 420, and a bus 430 connecting different system components.

[0061] The memory 410 may include, for example, system memory, non-volatile storage media, etc. The system memory may store, for example, an operating system, application programs, a boot loader, and other programs. The system memory may include volatile storage media, such as random access memory (RAM) and / or cache memory. The non-volatile storage media may store, for example, instructions for executing at least one embodiment of the vehicle calibration method. Non-volatile storage media include, but are not limited to, disk storage, optical storage, flash memory, etc.

[0062] The processor 420 can be implemented using a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gates, or transistors, or other discrete hardware components. Correspondingly, each module, such as the remote calibration instruction receiving module, the calibration response module, the calibration instruction packet receiving module, the calibration instruction packet verification module, the calibration instruction packet parsing module, the calibration control module, the calibration result verification module, and the calibration success result return module, can be implemented by executing instructions from the central processing unit (CPU) memory to perform the corresponding steps, or by implementing dedicated circuitry to perform the corresponding steps.

[0063] Bus 430 can use any of the various bus architectures. For example, bus architectures include, but are not limited to, Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, and Peripheral Component Interconnect (PCI) bus.

[0064] The computer system 400 may also include an input / output interface 440, a network interface 450, and a storage interface 460. These interfaces 440, 450, and 460, as well as the memory 410 and processor 420, can be connected via a bus 430. The input / output interface 440 provides a connection interface for input / output devices such as a monitor, mouse, and keyboard. The network interface 450 provides a connection interface for various networked devices. The storage interface 460 provides a connection interface for external storage devices such as floppy disks, USB flash drives, and SD cards.

[0065] Various aspects of this disclosure are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatus, and computer program products according to embodiments of this disclosure. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations thereof, can be implemented by computer-readable program instructions.

[0066] These computer-readable program instructions are provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable device to produce a machine, such that execution of the instructions by the processor produces means for implementing the functions specified in one or more boxes of the flowchart and / or block diagram.

[0067] These computer-readable program instructions may also be stored in a computer-readable storage medium. These instructions cause a computer to work in a particular manner to produce an article of manufacture, including instructions that implement the functions specified in one or more boxes in a flowchart and / or block diagram.

[0068] This disclosure may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects.

[0069] This disclosure improves vehicle security by enabling rapid key changes and vehicle locking via the cloud should the key be cracked and the vehicle stolen. Remote calibration eliminates the need for specialized diagnostic tools, making it more convenient and efficient to handle key-related faults or security issues.

[0070] The vehicle calibration method, apparatus, and medium according to this disclosure have now been described in detail. To avoid obscuring the concept of this disclosure, some details known in the art have not been described. Those skilled in the art can fully understand how to implement the technical solutions disclosed herein based on the above description.

[0071] While specific embodiments of this disclosure have been described in detail by way of example, those skilled in the art should understand that the examples are for illustrative purposes only and not intended to limit the scope of this disclosure. Those skilled in the art should understand that modifications can be made to the above embodiments without departing from the scope and spirit of this disclosure. The scope of this disclosure is defined by the appended claims.

Claims

1. A method of calibrating a vehicle end, characterized by, The method comprises: When the vehicle end is registered for the first time in the cloud, the cloud stores the VIN code of the vehicle end; When the vehicle end establishes a connection with the cloud each time, the cloud generates a communication key by encryption using at least the stored VIN code, and the vehicle end saves the communication key; Before performing the calibration process, the cloud performs encryption again using the current communication message serial number and the aforementioned communication key; after receiving the assembled encrypted information, the vehicle end compares it with the saved aforementioned communication key; if the vehicle end compares correctly, the vehicle end performs secondary encryption on the first encryption result and sends it to the cloud; the cloud decrypts the secondary encryption content and compares again whether the key information is correct; if the cloud compares correctly finally, the vehicle end is allowed to perform the following calibration process: Receiving the remote calibration instruction issued by the cloud; Replying to the cloud whether the current state can calibrate; When replying to the cloud that it can calibrate, receiving the calibration instruction package sent by the cloud; Validating the effectiveness and integrity of the calibration instruction package; If the validation passes, analyzing the calibration instruction package to obtain analysis data; Based on the analysis data, controlling the ECU to perform calibration; Validating the actual result after calibration; If the validation succeeds, returning the calibration success result to the cloud.

2. The method of claim 1, wherein, When replying to the cloud that it cannot calibrate, ending the calibration.

3. The method of claim 1, wherein, If the validation does not pass, returning the validation failure prompt information to the cloud and ending the calibration.

4. The method of claim 1, wherein The validation of the actual result after calibration comprises: Making two ECUs that need to exchange keys perform routine learning, one ECU is responsible for teaching keys and the other ECU is responsible for learning keys, wherein when the ECU receiving the learning key receives the key, it is stored in the register and sent to the CAN bus in the form of a CAN frame; After receiving the learning key frame, compare the learning key frame with the teaching key frame; If the comparison result is the same, the calibration is successful.

5. A vehicle end marking device, characterized by It comprises: a memory; and a processor coupled to the memory, the processor is configured to execute the vehicle end calibration method according to any one of claims 1 to 4 based on the instructions stored in the memory.

6. A computer storable medium, characterized by A computer program instruction is stored thereon, which is executed by a processor to realize the vehicle end calibration method according to any one of claims 1 to 4.

Citation Information

Patent Citations

  • Vehicle control method, electronic equipment and storage medium

    CN118418995A