Method and device for calibrating and verifying automobile controller, electronic equipment and storage medium

Abstract

The application provides a calibration verification method and device of an automobile controller, an electronic equipment and a storage medium, and belongs to the technical field of intelligent automobile controller development. The method comprises the following steps: obtaining a safety access request carried in a calibration process of an automobile controller; when it is determined that the calibration process is in an unsafe access state based on the safety access request, performing verification calculation on a calibration value corresponding to the calibration process based on a verification algorithm to obtain a first verification value; obtaining a second verification value stored in the controller; determining whether the first verification value is consistent with the second verification value; and when the first verification value is consistent with the second verification value, determining that the calibration process of the automobile controller is verified to be passed. The application solves the technical problem that the calibration value memory is abnormal due to internal risks of the controller in the prior art.

Description

Technical Field

[0001] This invention relates to the field of intelligent vehicle controller development technology, specifically to a calibration and verification method, device, electronic device, and storage medium for an vehicle controller. Background Technology

[0002] The offline calibration of automotive controllers mainly uses the UDS (Unified Diagnostic Services) protocol to achieve service communication between the host computer (diagnostic instrument) and the ECU (Electronic Control Unit). When the DID calibration function needs to be implemented, the host computer (diagnostic instrument) needs to implement the session service, security verification service, calibration write service, calibration read service, and reset service according to the standard process to complete the modification of the offline calibration DID (the above services may vary depending on the calibration process of the controller).

[0003] Among them, the calibration value DID is an important data of the controller. In order to ensure that this value is not modified abnormally, a security verification service is usually required before the calibration is written to ensure that the calibration value DID is not tampered with by external abnormalities.

[0004] Existing calibration value DID anti-tampering security verification services only address abnormal modifications made by external host computers via the UDS service. However, they cannot address the issue of calibration value DID memory anomalies caused by internal controller risks or other information security attacks. Therefore, existing technologies suffer from a technical problem where calibration value memory anomalies can result from internal controller risks. Summary of the Invention

[0005] In view of this, it is necessary to provide a calibration and verification method, device and electronic device for automotive controllers to solve the technical problem in the prior art that calibration value memory abnormalities are caused by internal risks of the controller.

[0006] To address the aforementioned technical problems, this invention provides, on the one hand, a calibration and verification method for an automotive controller, comprising:

[0007] Obtain the security access request carried during the calibration process of the vehicle controller;

[0008] When the calibration process is determined to be insecure access state based on the secure access request, the calibration value corresponding to the calibration process is verified and calculated based on the verification algorithm to obtain the first verification value.

[0009] Obtain the second verification value stored internally by the controller, determine whether the first verification value and the second verification value are consistent, and if the first verification value and the second verification value are consistent, determine that the calibration process of the vehicle controller has passed the verification.

[0010] In one possible implementation, the step of performing a verification calculation on the calibration value corresponding to the calibration process based on a verification algorithm to obtain a first verification value includes:

[0011] The controller is flashed with software for the first time to obtain the power-off storage area of ​​the flashing software, the internal storage of the controller, the calibration value stored in the power-off storage area, and the second verification value stored in the internal storage of the controller.

[0012] The calibration value corresponding to the calibration process is verified and calculated based on the verification algorithm to obtain the first verification value.

[0013] In one possible implementation, the step of performing a verification calculation on the calibration value corresponding to the calibration process based on a verification algorithm to obtain a first verification value includes:

[0014] The calibration values ​​corresponding to the calibration process are read based on the verification algorithm to obtain read data. The read data is then verified and calculated based on the digest algorithm to obtain a first verification value.

[0015] In one possible implementation, determining whether the first check value and the second check value are consistent, and determining that the calibration value verification has passed if the first check value and the second check value are consistent, includes:

[0016] If the first check value and the second check value are inconsistent, the first check value and the second check value will be rewritten as historical values.

[0017] In one possible implementation, rewriting the first check value and the second check value as historical values ​​includes:

[0018] Rewrite the first and second verification values ​​as historical values ​​to restore the previous calibration value or the factory default calibration value.

[0019] In one possible implementation, when the calibration process is determined to be insecure based on the secure access request, a first verification value is obtained by performing a verification calculation on the calibration value corresponding to the calibration process based on a verification algorithm, including:

[0020] When the calibration process is determined to be in a secure access state based on the secure access request, the controller actively shuts down the verification algorithm and waits for the host computer to complete writing the calibration value corresponding to the calibration process.

[0021] In one possible implementation, the secure access request carried during the calibration process of the vehicle controller includes:

[0022] The system uses API interface functions to monitor and obtain secure access requests carried during the calibration process of the vehicle controller in real time.

[0023] On the other hand, the present invention also provides a calibration and verification device for an automotive controller, comprising:

[0024] The first acquisition module is used to acquire the security access request carried during the calibration process of the vehicle controller;

[0025] The secure access status module is used to perform verification calculation on the calibration value corresponding to the calibration process based on the verification algorithm when the calibration process is determined to be insecure access status based on the secure access request, and obtain a first verification value.

[0026] The verification module is used to obtain the second verification value stored inside the controller, determine whether the first verification value and the second verification value are consistent, and determine that the calibration process of the vehicle controller has passed verification if the first verification value and the second verification value are consistent.

[0027] On the other hand, the present invention also provides an electronic device, including a memory and a processor, wherein,

[0028] The memory is used to store programs;

[0029] The processor, coupled to the memory, is used to execute the program stored in the memory to implement the steps in the calibration and verification method of the vehicle controller in any of the above implementations.

[0030] On the other hand, the present invention also provides a computer-readable storage medium for storing a computer-readable program or instruction, which, when executed by a processor, can implement the steps in the calibration and verification method of the vehicle controller described in any of the above implementations.

[0031] The beneficial effects of this invention are as follows: The calibration and verification method for an automotive controller provided by this invention includes: acquiring a security access request carried during the calibration process of the automotive controller; when the calibration process is determined to be in an insecure access state based on the security access request, performing verification calculation on the calibration value corresponding to the calibration process based on a verification algorithm to obtain a first verification value. This is done to continuously monitor the integrity of all calibration values ​​of the controller; acquiring a second verification value stored internally in the controller; determining whether the first verification value and the second verification value are consistent; and determining that the calibration process of the automotive controller has passed verification if the first verification value and the second verification value are consistent. This is done so that when the calibration value is abnormally tampered with, the verification system immediately rewrites the calibration value to the historical value; when the verification of the historical value is also abnormal, the verification system writes the independently stored default value into the calibration value. This better solves the technical problem in the prior art where abnormal calibration value memory is caused by internal risks in the controller. Attached Figure Description

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

[0033] Figure 1 A schematic flowchart of an embodiment of the calibration and verification method for an automotive controller provided by the present invention;

[0034] Figure 2 A flowchart of the calibration and verification system software algorithm for an embodiment of the calibration and verification method for an automotive controller provided by the present invention;

[0035] Figure 3 A schematic diagram of the calibration and verification recovery process of an embodiment of the calibration and verification method for an automotive controller provided by the present invention;

[0036] Figure 4 A schematic diagram of the calibration value reading and writing software framework of an embodiment of the calibration and verification method for an automotive controller provided by the present invention;

[0037] Figure 5 A schematic diagram of an embodiment of the calibration and verification device for an automotive controller provided by the present invention;

[0038] Figure 6 A schematic diagram of an embodiment of the electronic device provided by the present invention. Detailed Implementation

[0039] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present invention, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative effort are within the scope of protection of the present invention.

[0040] In the description of the embodiments of this application, unless otherwise stated, "a plurality of" means two or more.

[0041] In this embodiment of the invention, the terms "comprising" and "having" and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, apparatus, product or device that includes a series of steps or modules is not necessarily limited to those steps or modules that are explicitly listed, but may include other steps or modules that are not explicitly listed or that are inherent to such process, method, product or device.

[0042] The naming or numbering of steps in the embodiments of the present invention does not mean that the steps in the method flow must be executed in the time / logical order indicated by the naming or numbering. The execution order of the named or numbered process steps can be changed according to the technical purpose to be achieved, as long as the same or similar technical effect can be achieved.

[0043] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of the invention. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0044] This invention provides a calibration and verification method, device, electronic device, and storage medium for an automotive controller, which will be described below.

[0045] Figure 1 A schematic flowchart of an embodiment of the calibration and verification method for an automotive controller provided by the present invention. Figure 2 A flowchart of the calibration and verification system software algorithm for an embodiment of the calibration and verification method for an automotive controller provided by the present invention includes:

[0046] S101. Obtain the security access request carried during the calibration process of the vehicle controller;

[0047] S102. When the calibration process is determined to be insecure access state based on the secure access request, the calibration value corresponding to the calibration process is verified and calculated based on the verification algorithm to obtain the first verification value.

[0048] S103. Obtain the second verification value stored inside the controller, determine whether the first verification value and the second verification value are consistent, and if the first verification value and the second verification value are consistent, determine that the calibration process of the vehicle controller has passed the verification.

[0049] It is understandable that the calibration and verification system mainly consists of:

[0050] 1) A host computer capable of communicating with the controller protocol (not limited to CAN (Controller Area Network) and Ethernet), which can initiate calibrated secure access and write calibration values.

[0051] 2) A controller capable of communicating with a host computer via protocols (not limited to CAN, Ethernet), which can acknowledge secure access requests from the host computer and accept calibration value write requests. Simultaneously, the host computer can perform tasks such as... Figure 2 The calibration and verification system software algorithm flow is shown.

[0052] It needs to be further explained that, Figure 2 In the calibration process, when the controller of the calibration system does not receive a secure access from the host computer or the access status fails, the controller continues to run the calibration algorithm. During this period, the controller reads all calibration values ​​in the power-off storage area and uses the digest algorithm to calculate the verification value. The controller then compares the first verification value with the second verification value stored inside the controller to determine if they are consistent. If the first verification value is consistent with the second verification value stored inside the controller, the calibration process of the vehicle controller is deemed to have passed.

[0053] It can be further understood that the calibration and verification method for an automotive controller provided by this invention includes: acquiring a security access request carried during the calibration process of the automotive controller; when the calibration process is determined to be in an insecure access state based on the security access request, performing verification calculation on the calibration value corresponding to the calibration process based on a verification algorithm to obtain a first verification value. The purpose of this is to continuously monitor the integrity of all calibration values ​​of the controller; acquiring a second verification value stored internally in the controller; determining whether the first verification value and the second verification value are consistent; and determining that the calibration process of the automotive controller has passed verification if the first verification value and the second verification value are consistent. The purpose of this is to ensure that when the calibration value is abnormally tampered with, the verification system immediately rewrites the calibration value to a historical value; when the verification of the historical value is also abnormal, the verification system writes the independently stored default value into the calibration value. This better solves the technical problem in the prior art where abnormal calibration value memory is caused by internal risks in the controller.

[0054] In some embodiments of the present invention, a first verification value is obtained by performing verification calculations on the calibration value corresponding to the calibration process based on a verification algorithm, including:

[0055] Perform the initial software flashing operation on the controller to obtain the power-off storage area of ​​the flashing software, the internal storage of the controller, the calibration value saved in the power-off storage area, and the second verification value stored in the internal storage of the controller.

[0056] The calibration value corresponding to the calibration process is verified and calculated based on the verification algorithm to obtain the first verification value.

[0057] It is understood that the calibration and verification method for the automotive controller provided by this invention includes:

[0058] Obtain the security access request carried during the calibration process of the vehicle controller;

[0059] When the calibration process is determined to be insecure access state based on the secure access request, the calibration value corresponding to the calibration process is verified and calculated based on the verification algorithm to obtain the first verification value;

[0060] Obtain the second verification value stored internally by the controller, determine whether the first verification value and the second verification value are consistent, and if the first verification value and the second verification value are consistent, determine that the calibration process of the vehicle controller has passed.

[0061] It should be further explained that when the controller of the calibration system does not receive secure access from the host computer or the access status is not passed, the controller continues to run the calibration algorithm. During this period, the controller reads all calibration values ​​in the power-off storage area and uses the digest algorithm to calculate the verification value. The controller then compares the first verification value with the second verification value stored inside the controller to determine whether they are consistent. If the first verification value is consistent with the second verification value stored inside the controller, the calibration value is determined to have passed the verification.

[0062] It should be further explained that when the controller's software is initially flashed, it has a default power-off storage area and an independent storage area to store default calibration values ​​and checksums, respectively. Each time the host computer successfully modifies the calibration values ​​via secure access, the controller saves these as historical calibration and checksums after successful verification. Historical calibration and checksums are overwritten upon successful verification, but default calibration and checksums are not overwritten or deleted.

[0063] The verification algorithm continuously performs periodic verifications under insecure access conditions. Its function is to write the historical calibration value plus the verification value (or even the default calibration value plus the verification value) into the current calibration value when the calibration value of the controller is abnormally modified due to software, hardware or information security attacks. This allows the controller to restore the previous calibration state or the factory setting calibration state after the calibration value is abnormally modified.

[0064] In some embodiments of the present invention, a first verification value is obtained by performing verification calculations on the calibration value corresponding to the calibration process based on a verification algorithm, including:

[0065] The calibration values ​​corresponding to the calibration process are read based on the verification algorithm to obtain the read data. The read data is then verified and calculated based on the digest algorithm to obtain the first verification value.

[0066] It is understood that the calibration and verification method for the automotive controller provided by this invention includes:

[0067] Obtain the security access request carried during the calibration process of the vehicle controller;

[0068] When the calibration process is determined to be insecure access state based on the secure access request, the calibration value corresponding to the calibration process is verified and calculated based on the verification algorithm to obtain the first verification value;

[0069] Obtain the second verification value stored internally by the controller, determine whether the first verification value and the second verification value are consistent, and if the first verification value and the second verification value are consistent, determine that the calibration process of the vehicle controller has passed.

[0070] Furthermore,

[0071] Perform the initial software flashing operation on the controller to obtain the power-off storage area of ​​the flashing software, the internal storage of the controller, the calibration value saved in the power-off storage area, and the second verification value stored in the internal storage of the controller.

[0072] The calibration value corresponding to the calibration process is verified and calculated based on the verification algorithm to obtain the first verification value.

[0073] It should be further explained that when the controller of the calibration system does not receive a secure access from the host computer or the access status fails, the controller continues to run the calibration algorithm. During this period, the controller reads all calibration values ​​in the power-off storage area and uses the digest algorithm to calculate the verification value. The controller then compares the first verification value with the second verification value stored inside the controller to determine if they are consistent. If the first verification value is consistent with the second verification value stored inside the controller, the calibration process of the vehicle controller is determined to have passed.

[0074] It should be further explained that when the controller's software is initially flashed, the software has a default power-off storage area and an independent storage area to store default calibration values ​​and checksums, respectively. Each time the host computer successfully modifies the calibration values ​​via secure access, the controller saves these as historical calibration and checksums after successful verification. Historical calibration and checksums are overwritten upon successful verification, but default calibration and checksums are not overwritten or deleted.

[0075] The verification algorithm continuously performs periodic verifications under insecure access conditions. Its function is to write the historical calibration value plus the verification value (or even the default calibration value plus the verification value) into the current calibration value when the calibration value of the controller is abnormally modified due to software, hardware or information security attacks. This allows the controller to restore the previous calibration state or the factory setting calibration state after the calibration value is abnormally modified.

[0076] In some embodiments of the present invention, determining whether a first verification value and a second verification value are consistent, and determining that the calibration value verification has passed if the first verification value and the second verification value are consistent, includes:

[0077] If the first check value and the second check value are inconsistent, the first check value and the second check value will be rewritten as historical values.

[0078] It is understood that the calibration and verification method for the automotive controller provided by this invention includes:

[0079] Obtain the security access request carried during the calibration process of the vehicle controller;

[0080] When the calibration process is determined to be insecure access state based on the secure access request, the calibration value corresponding to the calibration process is verified and calculated based on the verification algorithm to obtain the first verification value;

[0081] Obtain the second verification value stored internally by the controller, determine whether the first verification value and the second verification value are consistent, and if the first verification value and the second verification value are consistent, determine that the calibration process of the vehicle controller has passed.

[0082] Furthermore,

[0083] Perform the initial software flashing operation on the controller to obtain the power-off storage area of ​​the flashing software, the internal storage of the controller, the calibration value saved in the power-off storage area, and the second verification value stored in the internal storage of the controller.

[0084] The calibration value corresponding to the calibration process is verified and calculated based on the verification algorithm to obtain the first verification value.

[0085] Furthermore,

[0086] The calibration values ​​corresponding to the calibration process are read based on the verification algorithm to obtain the read data. The read data is then verified and calculated based on the digest algorithm to obtain the first verification value.

[0087] It should be further explained that when the controller of the calibration system does not receive a secure access from the host computer or the access status fails, the controller continues to run the calibration algorithm. During this period, the controller reads all calibration values ​​in the power-off storage area and uses the digest algorithm to calculate the verification value. The controller then compares the first verification value with the second verification value stored inside the controller to determine if they are consistent. If the first verification value is consistent with the second verification value stored inside the controller, the calibration process of the vehicle controller is determined to have passed.

[0088] It should be further explained that when the controller's software is initially flashed, the software has a default power-off storage area and an independent storage area to store default calibration values ​​and checksums, respectively. Each time the host computer successfully modifies the calibration values ​​via secure access, the controller saves these as historical calibration and checksums after successful verification. Historical calibration and checksums are overwritten upon successful verification, but default calibration and checksums are not overwritten or deleted.

[0089] The verification algorithm continuously performs periodic verifications under insecure access conditions. Its function is to write the historical calibration value plus the verification value (or even the default calibration value plus the verification value) into the current calibration value when the calibration value of the controller is abnormally modified due to software, hardware or information security attacks. This allows the controller to restore the previous calibration state or the factory setting calibration state after the calibration value is abnormally modified.

[0090] In some embodiments of the present invention, rewriting the first check value and the second check value as historical values ​​includes:

[0091] Rewrite the first and second check values ​​as historical values ​​to restore the previous calibration values ​​or restore the factory setting calibration values.

[0092] It is understood that the calibration and verification method for the automotive controller provided by this invention includes:

[0093] Obtain the security access request carried during the calibration process of the vehicle controller;

[0094] When the calibration process is determined to be insecure access state based on the secure access request, the calibration value corresponding to the calibration process is verified and calculated based on the verification algorithm to obtain the first verification value;

[0095] Obtain the second verification value stored internally by the controller, determine whether the first verification value and the second verification value are consistent, and if the first verification value and the second verification value are consistent, determine that the calibration process of the vehicle controller has passed.

[0096] Furthermore,

[0097] Perform the initial software flashing operation on the controller to obtain the power-off storage area of ​​the flashing software, the internal storage of the controller, the calibration value saved in the power-off storage area, and the second verification value stored in the internal storage of the controller.

[0098] The calibration values ​​corresponding to the calibration process are verified using a verification algorithm to obtain the first verification value. Further,

[0099] The calibration values ​​corresponding to the calibration process are read based on the verification algorithm to obtain the read data. The read data is then verified and calculated based on the digest algorithm to obtain the first verification value.

[0100] Furthermore,

[0101] If the first check value and the second check value are inconsistent, the first check value and the second check value will be rewritten as historical values.

[0102] It should be further explained that when the controller of the calibration system does not receive secure access from the host computer or the access status is not passed, the controller continues to run the calibration algorithm. During this period, the controller reads all calibration values ​​in the power-off storage area and uses the digest algorithm to calculate the verification value. The controller then compares the first verification value with the second verification value stored inside the controller to determine whether they are consistent. If the first verification value is consistent with the second verification value stored inside the controller, the calibration value is determined to have passed the verification.

[0103] It should be further explained that when the controller's software is initially flashed, the software has a default power-off storage area and an independent storage area to store default calibration values ​​and checksums, respectively. Each time the host computer successfully modifies the calibration values ​​via secure access, the controller saves these as historical calibration and checksums after successful verification. Historical calibration and checksums are overwritten upon successful verification, but default calibration and checksums are not overwritten or deleted.

[0104] The verification algorithm continuously performs periodic verifications under insecure access conditions. Its function is to write the historical calibration value plus the verification value (or even the default calibration value plus the verification value) into the current calibration value when the calibration value of the controller is abnormally modified due to software, hardware or information security attacks. This allows the controller to restore the previous calibration state or the factory setting calibration state after the calibration value is abnormally modified.

[0105] Figure 3 A schematic diagram of the calibration and verification recovery process of an embodiment of the calibration and verification method for an automotive controller provided by the present invention includes:

[0106] When the calibration process is determined to be in a secure access state based on the secure access request, the controller actively shuts down the verification algorithm and waits for the host computer to complete the writing of the calibration value corresponding to the calibration process.

[0107] Understandably, when the controller of the calibration system successfully receives secure access from the host computer and the access status is approved, the controller actively shuts down the calibration algorithm and waits for the host computer to complete writing the calibration values. Once all calibration values ​​from the host computer have been written and it exits the secure access state, the controller actively calculates the verification result of the current calibration value and writes it as the verification value. In the next cycle, the system's secure access state is closed, and the calibration algorithm is restarted. Since the system synchronously updates the verification value after modifying the calibration value, the verification value and the calibration value are now matched, and the verification passes.

[0108] It should be further understood that this application also includes calibration and verification recovery, the specific implementation process of which is as follows:

[0109] The calibration system of this patent operates continuously. When the UDS secure access service is not enabled, the controller continuously performs a CRC (Cyclical Redundancy Check) 16 check to verify whether the current calibration value matches the checksum (the checksum algorithm can be defined according to the controller's performance, such as hash 256, hash 128, CRC, etc.). If the checksum fails and the number of consecutive failures is less than 5, the historical calibration value + checksum is written to the controller ROM (Read Only Memory). If the checksum fails and the number of consecutive failures is greater than or equal to 5, it is determined that the saved historical calibration value + checksum is also abnormal. In this case, the default calibration value + checksum is written to the controller ROM. Note: The default calibration value + checksum should be stored in the controller's HSM (Hardware Security Module) or other information security chip as the final security guarantee for the calibration value. If the checksum is successful, the calibration checksum failure count will be cleared to zero, and the successful calibration value and checksum will be saved as historical values.

[0110] When secure access service is enabled, the controller determines that the external diagnostic tool has taken over permissions including calibration write, and no longer verifies the calibration value. It immediately saves the calibration value and checksum of the first time the device entered this state as historical values. The controller continuously monitors whether secure access service is currently disabled; if disabled, it immediately calculates the checksum of the calibration value and writes it to the ROM.

[0111] Figure 4 A schematic diagram of the calibration value reading and writing software framework for an embodiment of the calibration and verification method for an automotive controller provided by the present invention includes:

[0112] The system uses API interface functions to monitor and obtain secure access requests carried during the calibration process of the vehicle controller in real time.

[0113] It is understood that the controller calibration software system described in this patent mainly consists of: a host computer system (including hardware and software) capable of interacting with the controller via Ethernet and reading / writing calibration values; a diagnostic instrument (including hardware and software) capable of interacting with the controller via CAN (Controller Area Network) bus and reading / writing calibration values; and a controller system capable of performing Ethernet read / write and CAN read / write functions.

[0114] Ethernet and CAN bus are instantiations of data transmission methods, but other communication transmission methods can also be used.

[0115] It should be further explained that the calibration and verification process and external interaction are as follows:

[0116] The controller application layer of this patented solution monitors the DID value of the calibration cache in real time through API (Application Programming Interface) functions and calculates a checksum using a digest algorithm. When the calculated checksum is inconsistent with the checksum already stored in memory, the application layer software writes the default calibration value stored in the ROM / Flash of the controller into the calibration cache, and then writes the calibration cache value to the ROM / EEPROM space corresponding to the DID, thereby realizing an anti-tampering mechanism.

[0117] In addition, to prevent after-sales or maintenance personnel from modifying calibration values ​​using a host computer or diagnostic instrument, which could cause the "calibration value safety verification" to fail, this invention addresses this issue through the following two methods:

[0118] a) Host computer:

[0119] Data integrity check: The host computer uses information security algorithms to encrypt data during Ethernet transmission to ensure data integrity. The host computer calculates the checksum using the CRC16 (Digest Algorithm) algorithm on the pre-written calibration value. The calibration value (DID) plus the calibration checksum constitutes a portion of the transmitted data.

[0120] Calibration value verification: When the controller receives Ethernet data from the host computer, it first decrypts the data using an information security algorithm to obtain the calibration value and calibration verification value. Then, it writes the calibration value and verification value into the calibration buffer (RTE) respectively. Therefore, when the controller performs verification calculations on the calibration value again to obtain the verification value, this calculated verification value matches the verification value in the RTE, preventing verification failure.

[0121] b) Diagnostic instruments:

[0122] Data integrity check: The diagnostic instrument uses UDS to interact with the controller. The controller needs the diagnostic instrument to complete the service security check ($27) before it can write the calibration value to the service ($2E).

[0123] Calibration value verification: When the diagnostic instrument is connected to the controller UDS and the secure access service ($27) is successful, the controller saves the current calibration value plus the checksum as a historical value. During secure access, the diagnostic instrument can normally call the calibration value write service ($2E) to complete the expected DID write without performing a checksum comparison; when the secure access service exits, the controller recalculates the checksum based on the calibration value (DID) during the period and writes it to the RTE, thus ensuring that calibration verification will not fail when verification is restarted.

[0124] Figure 5 A schematic diagram of an embodiment of the calibration and verification device for an automotive controller provided by the present invention includes:

[0125] The first acquisition module 501 is used to acquire the security access request carried during the calibration process of the vehicle controller;

[0126] The secure access status module 502 is used to perform verification calculation on the calibration value corresponding to the calibration process based on the verification algorithm when the calibration process is determined to be insecure access state based on the secure access request, and obtain the first verification value.

[0127] The verification module 503 is used to obtain the second verification value stored inside the controller, determine whether the first verification value and the second verification value are consistent, and determine that the calibration process of the vehicle controller has passed the verification if the first verification value and the second verification value are consistent.

[0128] The vehicle controller calibration and verification device 500 provided in the above embodiments can realize the technical solutions described in the above vehicle controller calibration and verification method embodiments. The specific implementation principles of each module or unit can be found in the corresponding content in the above vehicle controller calibration and verification method embodiments, which will not be repeated here.

[0129] like Figure 6 As shown, the present invention also provides an electronic device 600. The electronic device 600 includes a processor 601, a memory 602, and a display 603. Figure 6 Only some components of the electronic device 600 are shown, but it should be understood that it is not required to implement all the components shown, and more or fewer components may be implemented instead.

[0130] In some embodiments, processor 601 may be a central processing unit (CPU), microprocessor, or other data processing chip, used to run program code stored in memory 602 or process data, such as the calibration and verification method for an automobile controller in this invention.

[0131] In some embodiments, processor 601 may be a single server or a group of servers. The server group may be centralized or distributed. In some embodiments, processor 601 may be local or remote. In some embodiments, processor 601 may be implemented on a cloud platform. In one embodiment, the cloud platform may include a private cloud, public cloud, hybrid cloud, community cloud, distributed cloud, internal cloud, multi-cloud, etc., or any combination thereof.

[0132] In some embodiments, memory 602 may be an internal storage unit of electronic device 600, such as a hard disk or memory of electronic device 600. In other embodiments, memory 602 may also be an external storage device of electronic device 600, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc. equipped on electronic device 600.

[0133] Furthermore, the memory 602 may include both internal storage units of the electronic device 600 and external storage devices. The memory 602 is used to store application software and various types of data installed on the electronic device 600.

[0134] In some embodiments, display 603 may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, or an OLED (Organic Light-Emitting Diode) touchscreen. Display 603 is used to display information from electronic device 600 and to display a visual user interface. Components 601-603 of electronic device 600 communicate with each other via a system bus.

[0135] In one embodiment, when the processor 601 executes the calibration and verification program of the vehicle controller in the memory 602, the following steps can be implemented:

[0136] Obtain the security access request carried during the calibration process of the vehicle controller;

[0137] When the calibration process is determined to be insecure access state based on the secure access request, the calibration value corresponding to the calibration process is verified and calculated based on the verification algorithm to obtain the first verification value;

[0138] Obtain the second verification value stored internally by the controller, determine whether the first verification value and the second verification value are consistent, and if the first verification value and the second verification value are consistent, determine that the calibration process of the vehicle controller has passed.

[0139] It should be understood that when the processor 601 executes the calibration and verification program of the vehicle controller in the memory 602, in addition to the functions mentioned above, it can also perform other functions, as detailed in the description of the corresponding method embodiments above.

[0140] Furthermore, this embodiment of the invention does not specifically limit the type of electronic device 600 mentioned. Electronic device 600 can be a mobile phone, tablet computer, personal digital assistant (PDA), wearable device, laptop computer, or other portable electronic device. Exemplary embodiments of portable electronic devices include, but are not limited to, portable electronic devices running iOS, Android, Microsoft, or other operating systems. The aforementioned portable electronic device can also be other portable electronic devices, such as a laptop computer with a touch-sensitive surface (e.g., a touch panel). It should also be understood that in some other embodiments of the invention, electronic device 600 may not be a portable electronic device, but rather a desktop computer with a touch-sensitive surface (e.g., a touch panel).

[0141] Accordingly, this application also provides a computer-readable storage medium for storing a computer-readable program or instruction. When the program or instruction is executed by a processor, it can implement the steps or functions of the vehicle controller calibration and verification method provided in the above-described method embodiments.

[0142] Those skilled in the art will understand that all or part of the processes of the methods described in the above embodiments can be implemented by a computer program instructing related hardware (such as a processor, controller, etc.), and the computer program can be stored in a computer-readable storage medium. The computer-readable storage medium may be a disk, optical disk, read-only memory, or random access memory, etc.

[0143] The calibration and verification method, device, electronic device, and storage medium for the automotive controller provided by this invention have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this invention. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of this invention. At the same time, those skilled in the art will recognize that there will be changes in the specific implementation methods and application scope based on the ideas of this invention. Therefore, the content of this specification should not be construed as a limitation of this invention.

Claims

1. A calibration and verification method for an automotive controller, characterized in that, include: Obtain the security access request carried during the calibration process of the vehicle controller; When the calibration process is determined to be insecure access state based on the secure access request, the calibration value corresponding to the calibration process is verified and calculated based on the verification algorithm to obtain the first verification value. When the calibration process is determined to be in a secure access state based on the security access request, the controller actively shuts down the verification algorithm and waits for the host computer to complete writing the calibration value corresponding to the calibration process. Obtain the second verification value stored internally by the controller, determine whether the first verification value and the second verification value are consistent, and if the first verification value and the second verification value are consistent, determine that the calibration process of the vehicle controller has passed the verification; wherein, if the first verification value and the second verification value are inconsistent, rewrite the first verification value and the second verification value as historical values, including: rewriting the first verification value and the second verification value as historical values ​​to restore the previous calibration value or restore the factory setting calibration value.

2. The calibration and verification method for an automotive controller according to claim 1, characterized in that, The step of performing verification calculations on the calibration values ​​corresponding to the calibration process based on the verification algorithm to obtain a first verification value includes: The controller is flashed with software for the first time to obtain the power-off storage area of ​​the flashing software, the internal storage of the controller, the calibration value stored in the power-off storage area, and the second verification value stored in the internal storage of the controller. The calibration value corresponding to the calibration process is verified and calculated based on the verification algorithm to obtain the first verification value.

3. The calibration and verification method for an automotive controller according to claim 2, characterized in that, The step of performing verification calculations on the calibration values ​​corresponding to the calibration process based on the verification algorithm to obtain a first verification value includes: The calibration values ​​corresponding to the calibration process are read based on the verification algorithm to obtain read data. The read data is then verified and calculated based on the digest algorithm to obtain a first verification value.

4. The calibration and verification method for an automotive controller according to claim 1, characterized in that, The secure access request carried during the calibration process of the vehicle controller includes: The system uses API interface functions to monitor and obtain secure access requests carried during the calibration process of the vehicle controller in real time.

5. A calibration and verification device for an automotive controller, characterized in that, include: The first acquisition module is used to acquire the security access request carried during the calibration process of the vehicle controller; The secure access status module is used to perform verification calculation on the calibration value corresponding to the calibration process based on the verification algorithm when the calibration process is determined to be insecure access status based on the secure access request, and obtain a first verification value. And when the calibration process is determined to be in a secure access state based on the security access request, the controller actively shuts down the verification algorithm and waits for the host computer to complete writing the calibration value corresponding to the calibration process. The verification module is used to obtain a second verification value stored internally by the controller, determine whether the first verification value and the second verification value are consistent, and determine that the calibration process of the vehicle controller has passed verification if the first verification value and the second verification value are consistent; wherein, if the first verification value and the second verification value are inconsistent, the first verification value and the second verification value are rewritten as historical values, including: rewriting the first verification value and the second verification value as historical values ​​to restore the previous calibration value or restore the factory setting calibration value.

6. An electronic device, characterized in that, Including memory and processor, among which, The memory is used to store programs; The processor, coupled to the memory, is used to execute the program stored in the memory to implement the steps in the calibration and verification method for an automotive controller as described in any one of claims 1 to 4.

7. A computer-readable storage medium, characterized in that, Used to store computer-readable programs or instructions, which, when executed by a processor, can implement the steps in the calibration and verification method of the vehicle controller as described in any one of claims 1 to 4.

Images