Platform tamper-proofing method based on engine controller

By adopting the platform tamper-proof method in the engine controller, data files with verification codes are generated and verified, the problem of easy tampering of engine controller data is solved, and data security and management simplicity is improved.

CN119883726APending Publication Date: 2025-04-25KUNMING YUNNEI POWER +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411741383.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-11-29
Publication Date
2025-04-25

AI Technical Summary

Technical Problem

In the prior art, the data of the engine controller is easily tampered with, resulting in changes in engine performance and emissions not meeting standards, and the data tamper-proof solution has not been fully developed, resulting in the risk of data tamper-proof still exists.

Method used

The platform tamper-proof method based on the engine controller is adopted to calibrate the data, generate data files with verification codes, and verify the verification codes during the ECU software flashing and upgrading process to ensure the integrity and security of the data.

Benefits of technology

It effectively limits data tampering, enhances data security, simplifies verification code generation and management, reduces the complexity of software integration and data calibration, and realizes low-cost management tool versions and usage permissions.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119883726A_ABST
    Figure CN119883726A_ABST
Patent Text Reader

Abstract

The invention relates to the technical field of automobile electronic safety, in particular to a platform tamper-proofing method based on an engine controller, which comprises the following steps of: calibrating data, uploading a calibrated data file and an A2L file, generating a data file with a check code, and flashing and upgrading ECU software. According to the method, on the one hand, a small number of ECUs which have outflowed in the initial stage of project development and have the anti-tampering function not developed completely are limited to be used for data tampering through the method, and the safety of batched data is greatly enhanced; on the other hand, an independent check code calculation tool is adopted, a customized check code generation mode is facilitated, existing software integration, data calibration, production line generation and the like are not affected, finally, the check code calculation tool is called through a webpage, and tool versions and use permissions are conveniently managed at low cost.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of automobile electronic safety, and in particular to a platform tamper-proof method based on an engine controller. Background Art

[0002] The Engine Control Unit (ECU) is one of the key components of the engine and directly affects the engine performance and emissions. Currently, there are cases of illegal tampering with the engine controller data in the market, such as increasing the engine power output, turning on or off some vehicle functions, and modifying emissions by modifying the ECU data. This illegal behavior will not only cause changes in engine performance and fail to meet emission standards, but will also have an adverse impact on vehicle safety.

[0003] In the existing data anti-tampering scheme, if software with undeveloped data anti-tampering function is flashed into ECU, there is still the problem of arbitrary tampering of ECU data. At the same time, it is common for multiple companies to cooperate in developing a software in automobile manufacturing enterprises, and there are problems with the ease of use, update and iteration costs, leakage prevention, and permission management of the related software for calculating anti-tampering check codes. Summary of the invention

[0004] In view of the above problems, the present invention provides a platform tamper-proof method based on an engine controller.

[0005] The technical solution adopted is a platform anti-tampering method based on an engine controller, comprising the following steps: S1. Calibrate the data; S2. Upload the calibrated data file and A2L file; S3. Generate a data file with a checksum; S4. Flash and upgrade the ECU software; S5. Verify through a data file with a checksum; S6. Perform processing based on the verification result.

[0006] Furthermore, in S1, the calibration data interval writes the check code of all data in the interval at a position outside the calibration data interval.

[0007] Furthermore, in S2, a checksum calculation tool is developed based on the C# language to read the address and data information in the data hex file, and calculate the checksum of the data in the specified address range.

[0008] Furthermore, in S2, a checksum calculation tool is developed based on the C# language to parse the variable attributes and calculate the checksum in the A2L file.

[0009] Furthermore, in S3, the checksum is written into the address position specified in the data file, and a data file with the checksum is regenerated.

[0010] Furthermore, S5 includes Bootloader software upgrade verification code verification and APP verification code verification.

[0011] Furthermore, in the verification code verification of the Bootloader software upgrade, after the data is transmitted, the Bootloader calculates a verification code for the calibration area data and compares it with the verification value saved in the APP to determine whether it matches.

[0012] Furthermore, after the Bootloader software upgrade verification code is verified, in the APP verification code verification, after the controller is powered on, the APP calculates the verification code for the calibration area data and compares it with the verification code stored in the APP to determine whether it matches.

[0013] Furthermore, in S6, when the Bootloader software upgrade verification code verification fails, the flashing fails; When the APP verification code fails, the engine start is restricted.

[0014] Furthermore, S2 also includes a webpage remote call to calculate the verification code tool, which can upload data files and A2L files through the webpage interface, remotely call the tool to generate a data file with a verification code, and can download the generated data file through the webpage.

[0015] The beneficial effects of the present invention are: 1. On the one hand, this method limits the use of a small number of ECUs with incomplete anti-tampering functions that have been released in the early stage of project development to data tampering, greatly enhancing the data security after batch production. On the other hand, the use of an independent verification code calculation tool facilitates the customized verification code generation method without affecting the existing software integration, data calibration, production line generation, etc. Finally, the verification code calculation tool is called through the web page, which facilitates the low-cost management of tool versions and usage permissions; 2. To a large extent, it solves the problem that in the existing data tamper-proof solution, if the software with undeveloped data tamper-proof function is flashed into the ECU, the ECU data may still be tampered with at will. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 The present invention is a flow chart of a platform anti-tampering method based on an engine controller. DETAILED DESCRIPTION

[0017] The following describes the implementation of the present invention through specific examples. Those skilled in the art can easily understand other advantages and effects of the present invention from the contents disclosed in this specification. The present invention can also be implemented or applied through other different specific implementations, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present invention. It should be noted that the following embodiments and features in the embodiments can be combined with each other without conflict.

[0018] It should be noted that the illustrations provided in the following embodiments are only used to schematically illustrate the basic concept of the present invention, and thus the drawings only show components related to the present invention rather than being drawn according to the number, shape and size of components in actual implementation. In actual implementation, the type, quantity and proportion of each component may be changed arbitrarily, and the component layout may also be more complicated.

[0019] In this embodiment, Figure 1 As shown, a platform anti-tampering method based on an engine controller is provided, comprising the following steps: S1. Calibrate the data; S2. Upload the calibrated data file and A2L file; S3. Generate a data file with a checksum; S4. Flash and upgrade the ECU software; S5. Verify through a data file with a checksum; S6. Perform processing based on the verification result.

[0020] Meanwhile, in a specific implementation, in S1, the calibration data interval writes the check code of all data in the interval at a position outside the calibration data interval.

[0021] Furthermore, in S2, a checksum calculation tool is developed based on the C# language to read the address and data information in the data hex file, and calculate the checksum of the data in the specified address range.

[0022] At the same time, in S2, a checksum calculation tool is developed based on the C# language to parse the variable attributes and calculate the checksum in the A2L file.

[0023] Furthermore, in S3, the check code is written into the address position specified in the data file, and a data file with the check code is regenerated.

[0024] At the same time, S5 includes Bootloader software upgrade verification code verification and APP verification code verification.

[0025] The purpose of this design is, on the one hand, to limit the use of a small number of ECUs with incomplete anti-tampering functions that have been released in the early stage of project development for data tampering through this method, which greatly enhances the data security after batch production; on the other hand, the use of an independent verification code calculation tool facilitates the customized verification code generation method without affecting the existing software integration, data calibration, production line generation, etc.

[0026] In this embodiment, Bootloader software upgrade verification and APP verification methods are provided. In the Bootloader software upgrade verification code verification, after the data is transmitted, the Bootloader calculates a verification code for the calibration area data and compares it with the verification code saved in the APP to determine whether it matches. After the Bootloader software upgrade verification code verification passes, in the APP verification code verification, after the controller is powered on, the APP calculates a verification code for the calibration area data and compares it with the verification code saved in the APP to determine whether it matches.

[0027] Based on the above verification results, when the Bootloader software upgrade verification code verification fails, the flashing fails. When the APP verification code verification fails, the engine start is restricted.

[0028] In this way, on the one hand, if you flash an APP software whose anti-tampering function has not been fully developed, the bootloader will prompt that the verification fails, thus prohibiting the flashing. On the other hand, if you use a bootloader whose anti-tampering function has not been fully developed to flash the APP software, failure of the verification value in the APP will restrict the start of the engine. At the same time, a verification code calculation tool is developed to directly read the data file and write the verification code into the data file, which is convenient for writing the verification code into the data file after the data is solidified. The tool is independent of software integration, data calibration, and production line processes, and the existing process does not need to be adjusted.

[0029] It should be pointed out that the technical solution provided in this embodiment adopts a combination of software and hardware to prevent tampering of the engine controller, wherein the verification within the APP requires a verification code comparison at power-on, and at the same time the verification code in the software part needs to be placed in two areas and algorithms to increase the difficulty of cracking, and a comparison of verification codes is added to the Bootloader flash flow to prevent the software from being cracked after being flashed.

[0030] At the same time, in this embodiment, S2 also includes a web page remote call to calculate the verification code tool, which can upload data files and A2L files through the web page interface, and remotely call the tool to generate a data file with a verification code, and can download the generated data file through the web page.

[0031] The purpose of this design is to develop platform software to implement the webpage remote call tool for calculating the checksum. Upload data files and A2L files through the webpage interface, and remotely call the tool to generate data files with checksums, and also download the generated data files through the webpage.

[0032] User permission management has also been added to facilitate the establishment of dedicated data management personnel to use the tool. At the same time, the verification code calculation tool can be called through the web page to facilitate low-cost management of tool versions and usage permissions.

[0033] It should be noted that this embodiment adopts the development of an independent verification code calculation tool and the development of a remote calling tool based on Jenkins.

[0034] Finally, it should be noted that the above are only preferred embodiments of the present invention and are not intended to limit the present invention. Although the present invention has been described in detail with reference to the aforementioned embodiments, it is still possible for those skilled in the art to modify the technical solutions described in the aforementioned embodiments, or to make equivalent substitutions for some of the technical features therein. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the protection scope of the present invention.

Claims

1. A platform anti-tampering method based on an engine controller, characterized in that: The following steps are involved: S1. Calibrate the data; S2. Upload the calibrated data file and A2L file; S3. Generate a data file with a checksum; S4. Flash and upgrade the ECU software; S5. Verify through a data file with a checksum; S6. Perform processing based on the verification result.

2. The platform anti-tampering method based on the engine controller according to claim 1 is characterized in that: In S1, the data interval is calibrated and the check code of all data in the interval is written at a position outside the calibration data interval.

3. The platform anti-tampering method based on the engine controller according to claim 1 is characterized in that: In S2, a checksum calculation tool is developed based on the C# language to read the address and data information in the data hex file and calculate the checksum of the data in the specified address range.

4. The platform anti-tampering method based on the engine controller according to claim 3 is characterized in that: In S2, a checksum calculation tool is developed based on the C# language to parse the variable attributes and calculate the checksum in the A2L file.

5. The platform anti-tampering method based on the engine controller according to claim 4 is characterized in that: In S3, the checksum is written into the address position specified in the data file, and a data file with the checksum is regenerated.

6. The platform anti-tampering method based on the engine controller according to claim 5 is characterized in that: In S5, it includes Bootloader software upgrade verification code verification and APP verification code verification.

7. The platform anti-tampering method based on the engine controller according to claim 6 is characterized in that: In the Bootloader software upgrade verification code verification, after the data is transmitted, the Bootloader calculates the verification code for the calibration area data and compares it with the verification value saved in the APP to determine whether it matches.

8. The platform anti-tampering method based on the engine controller according to claim 7 is characterized in that: After the Bootloader software upgrade verification code verification is passed, in the APP verification code verification, after the controller is powered on, the APP calculates the verification code for the calibration area data and compares it with the verification code saved in the APP to determine whether it matches.

9. The platform anti-tampering method based on the engine controller according to claim 8, characterized in that: In S6, when the Bootloader software upgrade verification code verification fails, the flashing fails; When the APP verification code fails, the engine start is restricted.

10. A platform anti-tampering method based on an engine controller according to any one of claims 3 to 9, characterized in that: S2 also includes a webpage remote call to calculate the verification code tool, which can upload data files and A2L files through the webpage interface, remotely call the tool to generate a data file with a verification code, and can download the generated data file through the webpage.