Vehicle controller refreshing method and apparatus, device, and storage medium

Abstract

The present application relates to the technical field of vehicles, and discloses a vehicle controller refreshing method and apparatus, a device, and a storage medium. The method comprises: when a refreshing device initiates a program updating request for a vehicle controller, receiving refreshing data of the vehicle controller by means of a refreshing bootstrap program (202); and by means of the refreshing bootstrap program and on the basis of the refreshing data, refreshing the vehicle controller (204). The refreshing data is used for updating the function of the vehicle controller, the refreshing bootstrap program and the refreshing data are provided by different providers, and the refreshing bootstrap program is used for providing the function of refreshing the vehicle controller according to a standard process. The refreshing bootstrap program and the refreshing data are provided by different providers, and the refreshing bootstrap program is integrated into the vehicle controller. In the process of refreshing the vehicle controller, as the refreshing bootstrap program is called, a supplier of the vehicle controller only needs to provide the refreshing data to refresh the vehicle controller according to a standard process.

Description

Refresh method, device, equipment and storage medium for vehicle controller

[0001] This application claims priority to Chinese patent application No. 202310773758.8 filed on June 27, 2023, entitled “Refresh method, device, equipment and storage medium for vehicle controller”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of vehicle technology, and in particular to a refreshing method, device, equipment and storage medium for a vehicle controller. Background Art

[0003] With the development of vehicle electrification, the number of vehicle controllers on vehicles is increasing, such as controllers related to vehicle power systems, controllers related to vehicle safety systems, and controllers related to vehicle comfort systems.

[0004] For vehicle controller refreshes, vehicle OEMs typically define refresh process specifications. Each vehicle controller supplier develops a refresh program based on these specifications. By transferring the refresh program, developed by the supplier based on these specifications, to the vehicle controller, and then running the refresh program on the vehicle controller, the vehicle controller can be refreshed, effectively updating its functionality.

[0005] After developing the flash program for an automotive controller, the supplier must deliver it to the vehicle's OEM. The OEM then performs functional testing and verification based on the flash process specifications, providing feedback on any issues until verification is complete. This process requires significant manpower, capital, and time, resulting in a low efficiency in flashing automotive controllers.

[0006] Summary of the Invention

[0007] This application provides a method, device, equipment, and storage medium for refreshing a vehicle controller, which can improve the efficiency of refreshing the vehicle controller. The technical solution is as follows:

[0008] According to one aspect of the present application, a method for refreshing a vehicle controller is provided, the method comprising:

[0009] When a refresh device initiates a program update request for the vehicle controller, receiving refresh data of the vehicle controller through a refresh boot program;

[0010] Refreshing the vehicle controller based on the refresh data by the refresh boot program;

[0011] The refresh data is used to update the function of the vehicle controller, the refresh boot program and the refresh data are provided by different providers, and the refresh boot program is used to provide the function of refreshing the vehicle controller according to a standard process.

[0012] According to another aspect of the present application, a refreshing device for a vehicle controller is provided, the device comprising:

[0013] A receiving module, configured to receive refresh data of the vehicle controller through a refresh boot program when a refresh device initiates a program update request for the vehicle controller;

[0014] A refresh module, configured to refresh the vehicle controller based on the refresh data through the refresh boot program;

[0015] The refresh data is used to update the function of the vehicle controller, the refresh boot program and the refresh data are provided by different providers, and the refresh boot program is used to provide the function of refreshing the vehicle controller according to a standard process.

[0016] In an optional design, the device further includes:

[0017] A storage module, configured to store the refresh data through the first subroutine of the refresh boot program;

[0018] The refresh module is used to execute a system restart instruction through the second subroutine of the refresh boot program, so that the vehicle controller operates according to the stored refresh data.

[0019] In an optional design, the device further includes:

[0020] a determination module, configured to determine the starting storage address of the refresh data in the memory of the controller through the third subroutine of the refresh boot program; and an acquisition module, configured to acquire the data length of the refresh data;

[0021] The storage module is used to store the refresh data according to the starting storage address and the data length through the first subroutine of the refresh boot program.

[0022] In an optional design, the receiving module is configured to download the refresh data in blocks based on the refresh device through a fourth subroutine of the refresh boot program;

[0023] The storage module is configured to sequentially store the downloaded data blocks of the refresh data according to the starting storage address through the first subroutine of the refresh boot program;

[0024] The determining module is configured to determine that the storage of the refresh data is completed when the total length of the received data blocks of the refresh data is equal to the data length.

[0025] In an optional design, the refresh data downloaded by the refresh device is encrypted data; the apparatus further includes:

[0026] a decryption module, configured to decrypt the refresh data downloaded by the refresh device through a fifth subroutine of the refresh boot program;

[0027] The storage module is used to store the refresh data after the decryption process through the first subroutine of the refresh boot program.

[0028] In an optional design, the device further includes:

[0029] a comparison module, configured to compare a first signature value and a second signature value through a sixth subroutine of the refresh boot program, wherein the first signature value is obtained by the refresh device and the second signature value is calculated based on the refresh data;

[0030] A determination module is used to determine that the acquisition of the refresh data is completed when it is determined that the first signature value and the second signature value match.

[0031] In an optional design, the device further includes:

[0032] a checking module, configured to perform an integrity check on all functional data of the vehicle controller through the seventh subroutine of the refresh boot program;

[0033] A storage module, configured to store a refresh completion flag in a first memory area of ​​the vehicle controller if the integrity check passes;

[0034] Among them, the first memory area is used to store the refresh data, the first memory area is the area in the vehicle controller except the second memory area, the second memory area is used to store the historical version function data corresponding to the function updated by the refresh data, and the refresh completion flag is used to indicate that the refresh data is called when the vehicle controller is started.

[0035] In an optional design, the receiving module is used to:

[0036] receiving the program update request initiated by the refresh device for the vehicle controller;

[0037] When it is determined through the eighth subroutine of the refresh boot program that the refresh device passes the security authentication, the refresh data of the vehicle controller is received through the refresh boot program.

[0038] In an optional design, the refresh boot program is provided by the vehicle's main engine manufacturer, and the refresh data is provided by the supplier of the vehicle controller.

[0039] In an optional design, the refresh boot program corresponds to a hardware driver of the vehicle controller; the device further includes:

[0040] An interaction module, configured to execute data interaction between the refresh boot program and a hardware driver of the vehicle controller through an interaction interface during the process of refreshing the vehicle controller;

[0041] The hardware driver of the vehicle controller includes at least one of the following:

[0042] Memory driver;

[0043] Communication driver;

[0044] Timing drive.

[0045] According to another aspect of the present application, a computer device is provided, which includes a processor and a memory, wherein the memory stores at least one instruction, at least one program, a code set or an instruction set, and the at least one instruction, the at least one program, the code set or the instruction set is loaded and executed by the processor to implement the refresh method of the vehicle controller as described above.

[0046] According to another aspect of the present application, a computer-readable storage medium is provided, in which at least one instruction, at least one program, a code set or an instruction set is stored. The at least one instruction, the at least one program, the code set or the instruction set is loaded and executed by a processor to implement the refresh method of the vehicle controller as described above.

[0047] According to another aspect of the present application, a computer program product or computer program is provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the vehicle controller refresh method provided in various optional implementations of the above aspects.

[0048] The beneficial effects of the technical solution provided by this application include at least:

[0049] By having the refresh boot program and refresh data provided by different providers and integrating the refresh boot program into the vehicle controller, for example, the vehicle's OEM provides the refresh boot program, while the vehicle controller supplier provides the refresh data. During the vehicle controller refresh process, since the refresh boot program is invoked, the vehicle controller supplier only needs to develop refresh data for the functions that need to be updated in the vehicle controller. This allows the vehicle controller to be refreshed according to standard procedures without having to consider the specific operating procedures for the vehicle controller refresh process, thereby improving the efficiency of the vehicle controller refresh process. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] FIG1 is a schematic diagram of an implementation process of refreshing a vehicle controller provided by an exemplary embodiment of the present application;

[0051] FIG2 is a flow chart of a method for refreshing a vehicle controller according to an exemplary embodiment of the present application;

[0052] FIG3 is a flow chart of a method for refreshing a vehicle controller according to an exemplary embodiment of the present application;

[0053] FIG4 is a schematic structural diagram of a refreshing device for a vehicle controller provided by an exemplary embodiment of the present application;

[0054] FIG5 is a schematic structural diagram of a refreshing device for a vehicle controller provided by an exemplary embodiment of the present application;

[0055] FIG6 is a schematic structural diagram of a refreshing device for a vehicle controller provided by an exemplary embodiment of the present application;

[0056] FIG7 is a schematic structural diagram of a refreshing device for a vehicle controller provided by an exemplary embodiment of the present application;

[0057] FIG8 is a schematic structural diagram of a refreshing device for a vehicle controller provided by an exemplary embodiment of the present application;

[0058] FIG9 is a schematic structural diagram of a refreshing device for a vehicle controller provided by an exemplary embodiment of the present application;

[0059] FIG10 is a schematic structural diagram of a refreshing device for a vehicle controller provided by an exemplary embodiment of the present application;

[0060] FIG11 is a schematic structural diagram of a computer device provided by an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0061] In order to make the objectives, technical solutions and advantages of this application clearer, the implementation methods of this application will be further described in detail below with reference to the accompanying drawings.

[0062] With the development of vehicle electrification, the number of vehicle controllers on vehicles is increasing. For the refresh of vehicle controllers, the main engine manufacturer generally predefines basic refresh process operating specifications to indicate the entire standard process for refreshing vehicle controllers. For example, it is defined that when refreshing the vehicle controller, it is necessary to determine whether the vehicle is in a safe state, and the vehicle controller cannot be refreshed while the vehicle is in motion. The supplier of each vehicle controller develops a complete refresh program based on the refresh process operating specifications. By running the refresh program, the vehicle controller can update the functions provided by the refresh program. After development is completed, the supplier of the vehicle controller will deliver the refresh program to the vehicle main engine manufacturer for testing and verification of the refresh function and to determine whether the refresh process provided by the refresh program complies with the refresh process operating specifications. If there are any problems, the supplier will report them to the supplier. As a result, the verification of the refresh programs of all vehicle controllers in a complete vehicle project requires a lot of manpower, funds, and time, which makes the efficiency of refreshing vehicle controllers low.

[0063] The method provided in the embodiments of the present application provides a universal refresh boot program. The refresh boot program and the hardware driver of the vehicle controller are implemented through code and modularized. Through the refresh boot program, a universal standard refresh process can be implemented. In addition, a set of standard interactive interface functions are implemented to realize data exchange between the refresh boot program code and the controller hardware driver code. When refreshing different vehicle controllers, only the corresponding hardware driver code needs to be modified and the refresh data for the refresh function is provided to achieve the refresh of different vehicle controllers, thereby saving a lot of repetitive development, testing and verification work and improving the efficiency of refreshing vehicle controllers.

[0064] FIG1 is a schematic diagram of an implementation process of refreshing a vehicle controller provided by an exemplary embodiment of the present application. As shown in FIG1 , when a refresh device (such as a background server) initiates a program update request for a vehicle controller, the vehicle controller performs security authentication on the refresh device through the security authentication function subroutine of the refresh boot program 101. When the security authentication is passed, the vehicle controller obtains the refresh data of the vehicle controller from the refresh device and stores it through the request write subroutine, data download subroutine, data decryption subroutine and data write subroutine of the refresh boot program 101. Afterwards, the vehicle controller performs signature authentication on the refresh data through the data signature authentication subroutine of the refresh boot program 101, and performs integrity check on all functional data of the vehicle controller through the data integrity subroutine. When both of the above two items are passed, the vehicle controller executes a system restart instruction through the system restart operation subroutine of the refresh boot program 101, so that the vehicle controller runs according to the updated refresh data, thereby achieving the refresh of the vehicle controller.

[0065] Among them, the above-mentioned refresh data is used to update the function of the vehicle controller, the refresh boot program 101 is provided by the vehicle's main engine manufacturer, and the refresh data is provided by the supplier of the vehicle controller. In addition, in the process of refreshing the vehicle controller through the refresh boot program 101, data interaction between the refresh boot program 101 and the hardware driver 103 of the vehicle controller will be involved, that is, it involves calling the hardware of the vehicle controller. In this process, the vehicle controller will execute the data interaction between the refresh boot program 101 and the hardware driver 103 of the vehicle controller through the interactive interface 102. The hardware driver 103 includes at least one of a memory driver, a communication driver, and a timing driver. Among them, the memory driver is used to implement related operations involving the memory of the vehicle controller, the communication driver is used to implement related operations involving data transmission of the vehicle controller, and the timing driver is used to implement related operations involving the timing of the vehicle controller.

[0066] The vehicle's OEM provides a standardized flash boot program for the vehicle controller, which is then integrated into the vehicle controller. During the flash process, the flash boot program is invoked, allowing the vehicle controller supplier to develop flash data only for the functions that need to be updated, without having to consider the flash process specifications. This improves flash efficiency.

[0067] FIG2 is a flow chart of a method for refreshing a vehicle controller provided by an exemplary embodiment of the present application. The method can be used for a vehicle controller. As shown in FIG2 , the method includes:

[0068] Step 202: When the refresh device initiates a program update request for the vehicle controller, refresh data of the vehicle controller is received through the refresh boot program.

[0069] A vehicle controller is a controller integrated into a vehicle and used to manage vehicle components. Examples include a controller for managing the vehicle's powertrain, a controller for managing the vehicle's safety system, and a controller for managing the vehicle's comfort system. The vehicles in the embodiments of this application include two-wheeled vehicles, three-wheeled vehicles, four-wheeled vehicles, and vehicles with a greater number of wheels. Vehicle drive types include front-wheel drive, rear-wheel drive, and four-wheel drive. Vehicle power sources include gasoline, electricity, hydrogen, and hybrid power. Examples include fuel-powered vehicles, electric vehicles, hybrid vehicles, fuel-powered motorcycles, electric motorcycles, and electric bicycles.

[0070] The refresh device is used to manage the refresh of the vehicle controller and provide relevant data used in the process of refreshing the vehicle controller. The refresh device is connected to the vehicle controller via wireless and / or wired means. Optionally, when the refresh device is connected to the vehicle controller wirelessly, the refresh device is a backend server of the vehicle controller supplier or the vehicle's main engine manufacturer. The program update request is used to request an update of the vehicle controller. Optionally, the program update request is initiated by a relevant management personnel when an update of the vehicle controller is required.

[0071] The refresh boot program can provide the function of refreshing the vehicle controller according to a standard process (unified process). That is, by running the refresh boot program, the vehicle controller can be refreshed according to the standard process defined in the refresh boot program. Optionally, the standard process includes receiving data used to refresh the vehicle controller, storing the data used to refresh the vehicle controller, and refreshing the vehicle controller according to the stored data. Optionally, the standard process provided by the refresh boot program is defined and implemented in code and is defined by the vehicle's main engine manufacturer.

[0072] Different vehicle controllers in the same vehicle are integrated with the same flash boot program. For example, the air conditioning controller, parking sensor controller, and sunroof controller all have flash boot programs integrated into them. This flash boot program is provided by the OEM. This flash boot program ensures that all vehicle controllers follow the same standard process for data flashing. In this case, each controller supplier does not need to develop their own flash program based on the standard process; they only need to provide their own flash data. The flash boot program provided by the OEM allows all vehicle controllers to be flashed according to the standard process.

[0073] With reference to FIG1 , the standard process of refreshing data provided by the refresh boot program includes:

[0074] 1. Security authentication; 2. Request refresh; 3. Download data; 4. Data decryption; 5. Data flashing; 6. Data signature authentication; 7. Data integrity; 8. System restart.

[0075] Each vehicle controller refreshes its own data according to a unified refresh data process. The steps in the above standard process are described below.

[0076] The refresh data is used to update the functions of the vehicle controller. For example, the refresh data is used to upgrade the existing functions of the vehicle controller, or the refresh data is used to enable the vehicle controller to provide new functions in addition to the existing functions. The vehicle controller operates according to the refresh data to obtain the functions updated by the refresh data. The refresh boot program and the refresh data are provided by different providers. For example, the refresh data is provided by the supplier of the vehicle controller, or is developed by a third party commissioned by the supplier of the vehicle controller, or is provided by the main manufacturer of the vehicle. The refresh boot program is provided by the main manufacturer of the vehicle, or is developed by a third party commissioned by the main manufacturer of the vehicle, or is provided by the supplier of the vehicle controller. In some embodiments, the refresh boot program is provided by the main manufacturer of the vehicle, and the refresh data is provided by the supplier of the vehicle controller.

[0077] Step 204 : Refreshing the vehicle controller based on the refresh data through the refresh boot program.

[0078] After receiving the refresh data through the refresh boot program, the vehicle controller is refreshed by executing the process provided by the refresh boot program to update the vehicle controller according to the refresh data. Optionally, during the process of refreshing the vehicle controller according to the refresh data, the refresh boot program also provides a verification process to verify the refresh data. This ensures that the refresh data has not been tampered with and / or that the vehicle controller can operate normally after the refresh data is used to update the vehicle controller functions. Optionally, after verification is successful, the refresh boot program will perform a system reboot, causing the vehicle controller to operate according to the refresh data, thus completing the refresh of the vehicle controller.

[0079] Optionally, in the process of refreshing the vehicle controller through the refresh boot program, data interaction between the refresh boot program and the vehicle controller hardware is involved, such as transmitting refresh data, storing refresh data, etc. The refresh boot program corresponds to the hardware driver of the vehicle controller. In the process of refreshing the vehicle controller, the vehicle controller performs data interaction between the refresh boot program and the hardware driver of the vehicle controller (i.e., data interaction with the vehicle controller hardware) through an interactive interface. The provider of the interactive interface is the same as or different from the provider of the refresh boot program. For example, the provider of the interactive interface and the provider of the refresh boot program are both the vehicle's main engine manufacturer.

[0080] In summary, the method provided in this embodiment integrates the refresh boot program into the vehicle controller by having different providers provide the refresh boot program and refresh data. For example, the vehicle's OEM provides the refresh boot program, while the vehicle controller supplier provides the refresh data. During the vehicle controller refresh process, since the refresh boot program is invoked, the vehicle controller supplier only needs to develop refresh data for the functions that need to be updated in the vehicle controller. This allows the vehicle controller to be refreshed according to standard procedures without having to consider the vehicle controller refresh process and operating specifications. This improves the efficiency of vehicle controller refresh.

[0081] FIG3 is a flow chart of a method for refreshing a vehicle controller provided by an exemplary embodiment of the present application. The method can be used for a vehicle controller. As shown in FIG3 , the method includes:

[0082] Step 302: Receive a program update request initiated by a refresh device for a vehicle controller.

[0083] The vehicle controller is integrated into the vehicle and is used to manage vehicle components. The refresh device manages the refresh of the vehicle controller and provides relevant data used in the refresh process. The refresh device is connected to the vehicle controller via wireless and / or wired connections. For example, the refresh device is a server. A program update request is used to request an update of the vehicle controller. Optionally, the program update request is initiated by a relevant administrator when an update of the vehicle controller is required.

[0084] Step 304 : When it is determined through the eighth subroutine of the refresh boot program that the refresh device passes the security authentication, the refresh data of the vehicle controller is received through the refresh boot program.

[0085] The flash boot program can provide a function for flashing the vehicle controller according to a standard process. That is, by running the flash boot program, the vehicle controller can be flashed according to the standard process defined in the flash boot program. Optionally, the standard process provided by the flash boot program is defined and implemented in code, and the standard process is defined by the vehicle's main engine manufacturer.

[0086] The refresh data is used to update the functionality of the vehicle controller. For example, the refresh data is used to upgrade existing functionality of the vehicle controller, or the refresh data is used to enable the vehicle controller to provide new functionality in addition to existing functionality. The refresh boot program and the refresh data are provided by different providers. In some embodiments, the refresh boot program is provided by the vehicle's OEM, and the refresh data is provided by the vehicle controller's supplier.

[0087] The eighth subroutine can provide a security authentication function. Optionally, the program update request carries the identifier of the refresh device, and the eighth subroutine compares the identifier of the stored refresh device that has passed the security authentication with the identifier carried by the program update request to determine whether the refresh device has passed the security authentication. Alternatively, the eighth subroutine generates a random number and sends it to the refresh device. The refresh device generates a check value based on the random number using a built-in algorithm and sends it to the vehicle controller. The eighth subroutine also generates a check value based on the random number using a built-in algorithm. The generated check value is then compared with the check value sent by the refresh device to see if they are consistent. If they are consistent, it is determined that the refresh device has passed the security authentication. For example, the algorithm corresponding to the eighth subroutine is provided by the vehicle's main engine manufacturer. When the refresh device is legal, its built-in algorithm is the same as the algorithm corresponding to the eighth subroutine.

[0088] The refresh boot program includes a first subroutine that provides a data flashing function. After receiving refresh data from the vehicle controller, the refresh boot program stores the refresh data through the first subroutine of the refresh boot program. During this process, the first subroutine interacts with the vehicle controller's data storage hardware driver to store the received refresh data in the vehicle controller's memory.

[0089] The refresh boot program includes a third subroutine that can provide a request refresh function. In the process of receiving refresh data, the vehicle controller can determine the starting storage address of the received refresh data in the vehicle controller's memory and obtain the data length of the refresh data through the third subroutine of the refresh boot program. Optionally, the starting storage address is randomly determined by the third subroutine in an idle area in the vehicle controller's memory based on the data length. In the process of storing refresh data through the first subroutine, the vehicle controller will store the received refresh data through the first subroutine of the refresh boot program according to the starting storage address and data length determined by the third subroutine.

[0090] The refresh boot program includes a fourth subroutine, which can provide a data download function. In the process of receiving the refresh data of the vehicle controller, the vehicle controller downloads the refresh data of the vehicle controller in blocks based on the refresh device through the fourth subroutine of the refresh boot program. Optionally, the size of each data block of the refresh data received by the fourth subroutine can be determined by configuration, and the size of the received data block is related to the resources of the vehicle controller hardware itself. For example, the stronger the storage performance of the vehicle controller, the larger the size of the data block received each time. In the process of storing the refresh data according to the starting storage address and data length through the first subroutine, the vehicle controller will store the downloaded refresh data blocks in sequence according to the starting storage address through the first subroutine of the refresh boot program, and determine that the storage of the refresh data is completed when the total length of the data blocks of the received refresh data is equal to the data length.

[0091] Optionally, the refresh boot program detects the available storage space of the vehicle controller in real time. When the remaining available storage space reaches the warning threshold, the refresh boot program stops or slows down the downloading of refresh data, and the refresh boot program no longer executes subsequent refresh processes until the detected remaining storage space is greater than the warning threshold.

[0092] For example, the third subroutine determines that the starting storage address of the refresh data is 00, and the data length is 10. During the process of downloading the refresh data in blocks through the fourth subroutine, the size of each downloaded data block is 2. The first subroutine stores the downloaded data blocks in sequence according to the starting storage address. When the fifth data block is stored, the first subroutine determines that the length of the stored data block is 10, which is equal to the data length determined by the third subroutine. At this point, the first subroutine determines that the storage of the refresh data is complete.

[0093] Optionally, the refresh data downloaded by the refresh device is encrypted data, and the refresh boot program includes a fifth subroutine, which can provide a data decryption function. In the process of downloading the refresh data through the fourth subroutine and storing the downloaded refresh data through the first subroutine, the vehicle controller will decrypt the refresh data downloaded by the refresh device through the fifth subroutine of the refresh boot program. Thereafter, the decrypted refresh data is stored through the first subroutine of the refresh boot program. Optionally, the encrypted data downloaded by the refresh device is obtained by processing the original data using an encryption algorithm. During the data decryption process, the fifth subroutine will use the encryption algorithm to process the encrypted data, thereby obtaining the original data and storing it through the first subroutine. Optionally, the encryption algorithm is agreed upon by the vehicle's main manufacturer and the provider of the refresh data.

[0094] Step 306: Perform signature authentication by refreshing the sixth subroutine of the boot program.

[0095] The refresh boot program includes a sixth subroutine, which can provide a data signature authentication function. After completing the reception of the refresh data, the vehicle controller will compare the first signature value and the second signature value through the sixth subroutine of the refresh boot program. When it is determined that the first signature value and the second signature value match, it will be determined that the acquisition of the refresh data is completed. Among them, the first signature value is obtained by the refresh device, and the second signature value is calculated based on the refresh data. For example, the sixth subroutine calculates the received refresh data through the signature algorithm, so as to obtain the second signature value, which will then be compared with the first signature value sent by the refresh device for the refresh data. By comparing the first signature value and the second signature value, the refresh data can be prevented from being tampered with, thereby ensuring data security.

[0096] Step 308: Perform an integrity check by refreshing the seventh subroutine of the boot program.

[0097] The refresh boot program includes a seventh subroutine, which can provide a data integrity check function. The vehicle controller performs an integrity check on all functional data of the vehicle controller through the seventh subroutine of the refresh boot program. All functional data is used to implement all functions provided by the vehicle controller, which includes the function of refreshing data updates. The integrity check is to check whether all functions provided by the vehicle controller are complete after the vehicle controller is refreshed, to avoid the situation where the vehicle controller has missing functions after the refresh. For example, before the refresh, the vehicle controller provides function 1, function 2 and function 3. After the refresh, it is determined based on all functional data that the vehicle controller provides function 1 and function 2, and function 3 is missing, then it will be determined that the integrity check has failed.

[0098] If the integrity check passes, the seventh subroutine will store a refresh completion flag in the first memory area of ​​the vehicle controller. The first memory area is used to store refresh data, and the first memory area is the area in the vehicle controller other than the second memory area. The second memory area is used to store historical version function data corresponding to the function updated by the refresh data. The refresh completion flag is used to indicate that the refresh data is called when the vehicle controller is started, that is, the function of the vehicle controller is provided according to the refresh data. Optionally, if the vehicle controller fails to call the refresh data startup, that is, the vehicle controller cannot provide the function of the refresh data update according to the refresh data, the vehicle controller will operate according to the above-mentioned historical version function data to ensure that the vehicle controller can operate normally in the event of a refresh failure.

[0099] The refresh boot program corresponds to the hardware driver of the vehicle controller. In the above-mentioned process of refreshing the vehicle controller, data interaction between the refresh boot program and the hardware driver of the vehicle controller is involved. For example, when storing refresh data, data interaction is performed with the hardware driver, so that the refresh data is stored in the memory of the vehicle controller. For different vehicle controllers, when the hardware is different, the hardware drivers will also be different. The data interaction between the refresh boot program and the hardware drivers of different vehicle controllers can be achieved through the interactive interface. In the process of refreshing the vehicle controller, the data interaction between the refresh boot program and the hardware driver of the vehicle controller is performed through the interactive interface. Optionally, the interactive interface refers to an interactive interface function, which is implemented by code. The interactive interface function is provided by the provider of the refresh boot program, such as the main engine manufacturer of the vehicle. Optionally, the interactive interface is a set of standard interactive interface functions for realizing data interaction between the refresh boot program and the hardware drivers of different vehicle controllers. The hardware driver of the vehicle controller is provided by the supplier of the vehicle controller. The hardware driver of the vehicle controller includes at least one of the following:

[0100] Memory driver;

[0101] Communication driver;

[0102] Timing drive.

[0103] The memory driver implements memory erase and write operations, as well as memory read operations. The communication driver enables data exchange between the vehicle controller and the refresh device. The timing driver implements interval processing for data transmission and reception message times, determining whether the interval between data transmission or reception meets the data transmission specification.

[0104] Step 310 : Execute the system restart instruction through the second subroutine of the refresh boot program to enable the vehicle controller to operate according to the stored refresh data.

[0105] The refresh boot program includes a second subroutine that provides control system restart functionality. After receiving and storing the refresh data and passing the aforementioned verification, and if restart conditions are met, the second subroutine executes system restart instructions, causing the vehicle controller to operate according to the stored refresh data and enable the vehicle controller to provide the updated functionality. For example, these restart conditions include the vehicle being stationary, the vehicle being turned off, and restarting the vehicle controller not affecting vehicle operation.

[0106] Optionally, when the first user of the vehicle has internal testing qualifications, the refresh boot program can receive the refresh data of the internal testing version and use the refresh data of the internal testing version to refresh the vehicle controller. The version number of the refresh data of the internal testing version is higher than the version number of the refresh data of the non-internal testing version, and the refresh data of the internal testing version can provide more / newer functions compared to the refresh data of the non-internal testing version. The first user with internal testing qualifications can authorize the second user of the same model vehicle and send the refresh data of the internal testing version to the second user's vehicle, so that the refresh boot program of the second user's vehicle can refresh the vehicle controller according to the authorization information and the refresh data of the internal testing version. Optionally, the authorization and sending of the refresh data can be performed by wired or wireless means. For example, the refresh data is authorized and transmitted by the vehicle's server, or the first user connects to the vehicle by wire to export the authorization information and refresh data, and then transmits them to the second vehicle by wire.

[0107] Optionally, after refreshing the vehicle controller using refresh data, if an operational anomaly occurs during the vehicle controller's operation, the vehicle can search for other normally operating vehicles of the same model within a preset range and retrieve the vehicle controller's refresh data from these vehicles. The retrieved refresh data is a different version from the current refresh data. The vehicle controller can then be refreshed using the retrieved refresh data to resolve the operational anomaly. Optionally, the vehicle search and communication with vehicles of the same model are implemented via a server, base station, or inter-vehicle side-by-side communication.

[0108] Optionally, if the vehicle cannot connect to the flash device, it can obtain the flash data currently used by other vehicles of the same model in the vicinity through side communication. If the version of the flash data obtained is higher than the flash data currently used by the vehicle, the vehicle controller will be refreshed with the higher version of the flash data after obtaining it.

[0109] In summary, the method provided in this embodiment integrates the refresh boot program into the vehicle controller by having different providers provide the refresh boot program and refresh data. For example, the vehicle's OEM provides the refresh boot program, while the vehicle controller supplier provides the refresh data. During the vehicle controller refresh process, since the refresh boot program is invoked, the vehicle controller supplier only needs to develop refresh data for the functions that need to be updated in the vehicle controller. This allows the vehicle controller to be refreshed according to standard procedures without having to consider the vehicle controller refresh process and operating specifications. This improves the efficiency of vehicle controller refresh.

[0110] Additionally, downloading refresh data in chunks reduces resource consumption. Storing refresh data according to the starting storage address and data length ensures the integrity of the received refresh data. Signature verification prevents tampering with the refresh data, ensuring data security. Integrity checks ensure the complete functionality of the vehicle controller after the refresh. Device security authentication ensures that only trusted devices initiate refreshes of the vehicle controller, ensuring the security of the refresh.

[0111] It should be noted that the order of the method steps provided in the embodiments of the present application can be appropriately adjusted, and the steps can be increased or decreased accordingly according to the circumstances. Any technical personnel familiar with this technical field can easily think of the changed methods within the technical scope disclosed in this application, and they should be covered within the scope of protection of this application, so they will not be repeated here.

[0112] In some embodiments, the OEM also develops customized standard processes for individual vehicle controllers and integrates these processes into the target vehicle controllers. For example, for a brake controller and a throttle controller developed by the same OEM, the OEM implements a data compatibility check in addition to the standard refresh boot process. The brake controller's customized refresh boot process checks the compatibility between the downloaded brake data to be refreshed and the current throttle data. If a mismatch occurs, the download of the brake data is stopped.

[0113] For example, if the downloaded brake data version is 8 and the current throttle data version is 2, the two versions are considered to be incompatible due to a large gap, and the brake data download is stopped. The brake data to be refreshed is of a higher version, which allows the user to generate a stronger braking force with a slight step, while the current throttle data version is lower, which allows the user to generate a weaker throttle force with a slight step.

[0114] This embodiment of the application provides the design and implementation of a universal online flash boot program. This modularizes the flash boot program code design and the specific vehicle controller hardware driver code. A set of standard interaction interface functions is designed to implement data exchange between the flash boot program and the vehicle controller hardware driver. This allows the development of online flash functionality for different vehicle controllers simply by modifying the vehicle controller driver code, thus saving a significant amount of repetitive development, testing, and verification work.

[0115] The programming of the entire refresh process is divided into 3 parts:

[0116] (1) Refresh boot program: realizes all service processing functions of online refresh of the whole vehicle, including security authentication processing, data message decryption processing, data packet starting address processing, data refresh length processing, refresh data signature authentication processing after data refresh is completed, data integrity verification processing after refresh, and program recovery processing after refresh.

[0117] (2) Hardware driver code: implements the vehicle communication bus signal reception and transmission processing, provides data transmission and reception cache mechanism, provides task scheduling processing, provides timing counting service, and provides memory erase and write operation service.

[0118] (3) Interaction interface code: It serves as a bridge for data interaction between hardware driver parameters and the refresh boot program.

[0119] The embodiment of this application optimizes the refresh boot program of the automobile controller, adopting a layered modular design concept. The refresh boot program extracts key information from the refresh process and organizes it into different sub-modules. The specific design is as follows:

[0120] 1. The basic design ideas for the main steps of the refresh process are as follows:

[0121] Step 1: Develop a security authentication function. This function allows legitimate refresh devices to initiate program update requests for the vehicle controller. Only legitimate refresh devices can pass the security authentication request, protecting the vehicle controller from the risk of intrusion by illegal devices.

[0122] Step 2: After step 1 is passed, the software begins to receive a request to flash. This sub-function processes the starting address and data length information used when the refresh boot program is about to start controlling the memory flash operation.

[0123] Step 3: After step 2 is passed, the downloaded refresh data is received in blocks. The size of the received data block can be determined by configuration and is related to the resources of the vehicle controller hardware itself.

[0124] Step 4: After step 3, the received refresh data needs to be decrypted. After decryption, the data starts calling the memory write operation service according to the memory start address provided in step 2.

[0125] Step 5: Based on the data length information received in step 2, repeat steps 3 and 4 until the received data length is equal to the data length information provided in step 2.

[0126] Step 6: Start receiving signature data and process the data signature value downloaded to the memory in steps 2 to 5, compare the received data signature value with the calculated signature value, and complete the refresh of the block data if the signature passes.

[0127] Step 7: After completing step 6, if there are other flash write requests, repeat the flash operation from step 2 to step 6. If there are no other data flash write requests, start the integrity check of the entire vehicle controller program. If the check passes, write the flash completion flag to a specific area of ​​the vehicle controller memory.

[0128] Step 8: After completing step 7, start executing the system restart command to allow the vehicle controller to run according to the updated program.

[0129] 2. The interactive interface part mainly completes the data interactive interface function between the refresh boot program and the hardware driver, and realizes the seamless compilation and linking of the refresh boot program and the underlying driver code of the vehicle controller. The details are as follows:

[0130] Memory read: convert the memory read interface function of the hardware driver chip into a standard interface form for the refresh boot program to call.

[0131] Memory write: convert the memory write interface function of the hardware driver chip into a standard interface form for the refresh boot program to call.

[0132] Receive data and convert the hardware driver chip's data receiving interface function into a standard interface format for the refresh boot program to call.

[0133] Send data, convert the data sending interface function of the hardware driver chip into a standard interface form for the refresh boot program to call.

[0134] Start timing, convert the start timing interface function of the hardware driver chip into a standard interface form for the refresh boot program to call.

[0135] Stop timing, convert the stop timing interface function of the hardware driver chip into a standard interface form for the refresh boot program to call.

[0136] Reset timing: convert the reset timing interface function of the hardware driver chip into a standard interface form for the refresh boot program to call.

[0137] Scheduling process: provides a scheduling process mechanism between various modules of the refresh boot program.

[0138] 3. The hardware driver section completes the driver function code for the vehicle controller chip. This code implementation is dependent on the vehicle controller's processor and requires redevelopment for different vehicle controllers. A typical vehicle controller refresh boot program only requires the development of a memory driver module, a communication driver module, and a counter driver module to implement the underlying driver functions of the refresh boot program.

[0139] ·Memory driver module, mainly realizes memory erase operation and memory information read operation function.

[0140] The communication driver module mainly realizes data exchange and communication with the refresh device. The vehicle network can realize data exchange between vehicle controllers through the Controller Area Network (CAN) bus.

[0141] The timing driver module is mainly used to process the time interval of data sending and receiving messages, and determine whether the time interval of data sending or receiving meets the data transmission specifications.

[0142] FIG4 is a schematic diagram of a refresh device for a vehicle controller according to an exemplary embodiment of the present application. As shown in FIG4 , the device includes:

[0143] The receiving module 401 is configured to receive refresh data of the vehicle controller through a refresh boot program when a refresh device initiates a program update request for the vehicle controller;

[0144] A refresh module 402 is configured to refresh the vehicle controller based on the refresh data through the refresh boot program;

[0145] The refresh data is used to update the function of the vehicle controller, the refresh boot program and the refresh data are provided by different providers, and the refresh boot program is used to provide the function of refreshing the vehicle controller according to a standard process.

[0146] In an optional design, as shown in FIG5 , the apparatus further includes:

[0147] A storage module 403 is configured to store the refresh data through the first subroutine of the refresh boot program;

[0148] The refresh module 402 is configured to execute a system restart instruction through the second subroutine of the refresh boot program, so that the vehicle controller operates according to the stored refresh data.

[0149] In an optional design, as shown in FIG6 , the apparatus further includes:

[0150] The determination module 404 is used to determine the starting storage address of the refresh data in the memory of the controller through the third subroutine of the refresh boot program; the acquisition module 405 is used to acquire the data length of the refresh data;

[0151] The storage module 403 is configured to store the refresh data according to the starting storage address and the data length through the first subroutine of the refresh boot program.

[0152] In an optional design, the receiving module 401 is configured to download the refresh data in blocks based on the refresh device through a fourth subroutine of the refresh boot program;

[0153] The storage module 403 is configured to sequentially store the downloaded data blocks of the refresh data according to the starting storage address through the first subroutine of the refresh boot program;

[0154] The determining module 404 is configured to determine that the storage of the refresh data is completed when the total length of the received data blocks of the refresh data is equal to the data length.

[0155] In an optional design, the refresh data downloaded by the refresh device is encrypted data; as shown in FIG7 , the apparatus further includes:

[0156] a decryption module 406 configured to decrypt the refresh data downloaded by the refresh device through the fifth subroutine of the refresh boot program;

[0157] The storage module 403 is configured to store the refresh data after the decryption process through the first subroutine of the refresh boot program.

[0158] In an optional design, as shown in FIG8 , the apparatus further includes:

[0159] a comparison module 407, configured to compare a first signature value and a second signature value through a sixth subroutine of the refresh boot program, wherein the first signature value is obtained by the refresh device and the second signature value is calculated based on the refresh data;

[0160] The determination module 404 is configured to determine that the acquisition of the refresh data is completed when it is determined that the first signature value and the second signature value match.

[0161] In an optional design, as shown in FIG9 , the apparatus further includes:

[0162] A checking module 408 is configured to perform an integrity check on all functional data of the vehicle controller through the seventh subroutine of the refresh boot program;

[0163] The storage module 403 is configured to store a refresh completion flag in the first memory area of ​​the vehicle controller if the integrity check passes;

[0164] Among them, the first memory area is used to store the refresh data, the first memory area is the area in the vehicle controller except the second memory area, the second memory area is used to store the historical version function data corresponding to the function updated by the refresh data, and the refresh completion flag is used to indicate that the refresh data is called when the vehicle controller is started.

[0165] In an optional design, the receiving module 401 is configured to:

[0166] receiving the program update request initiated by the refresh device for the vehicle controller;

[0167] When it is determined through the eighth subroutine of the refresh boot program that the refresh device passes the security authentication, the refresh data of the vehicle controller is received through the refresh boot program.

[0168] In an optional design, the refresh boot program is provided by the vehicle's main engine manufacturer, and the refresh data is provided by the supplier of the vehicle controller.

[0169] In an optional design, the refresh boot program corresponds to the hardware driver of the vehicle controller; as shown in FIG10 , the device further includes:

[0170] An interaction module 409 is configured to execute data interaction between the refresh boot program and the hardware driver of the vehicle controller through an interaction interface during the process of refreshing the vehicle controller;

[0171] The hardware driver of the vehicle controller includes at least one of the following:

[0172] Memory driver;

[0173] Communication driver;

[0174] Timing drive.

[0175] In an optional design, the interactive interface is provided by the vehicle's main engine manufacturer, and the hardware driver of the vehicle controller is provided by the supplier of the vehicle controller;

[0176] The interactive interface is used to implement data interaction between the refresh boot program and different hardware drivers of the vehicle controller.

[0177] In an optional design, the interactive interface includes:

[0178] Memory read interface, memory write interface, receive data interface, send data interface, start timing interface, stop timing interface, reset timing interface and scheduling processing interface.

[0179] It should be noted that the refresh device for a vehicle controller provided in the above embodiment is merely an example of the division of the aforementioned functional modules. In actual applications, the aforementioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. Furthermore, the refresh device for a vehicle controller provided in the above embodiment and the refresh method for a vehicle controller are based on the same concept. The specific implementation process is detailed in the method embodiment and will not be repeated here.

[0180] An embodiment of the present application also provides a computer device, which includes: a processor and a memory, wherein the memory stores at least one instruction, at least one program, code set or instruction set, and the at least one instruction, at least one program, code set or instruction set is loaded and executed by the processor to implement the refresh method of the vehicle controller provided by the above-mentioned method embodiments.

[0181] Optionally, the computer device is a server. For example, FIG11 is a schematic diagram of the structure of a computer device provided by an exemplary embodiment of the present application.

[0182] The computer device 1100 includes a central processing unit (CPU) 1101, a system memory 1104 including a random access memory (RAM) 1102 and a read-only memory (ROM) 1103, and a system bus 1105 connecting the system memory 1104 and the CPU 1101. The computer device 1100 also includes a basic input / output system (I / O system) 1106 for facilitating information transfer between various components within the computer device, and a mass storage device 1107 for storing an operating system 1113, application programs 1114, and other program modules 1115.

[0183] The basic input / output system 1106 includes a display 1108 for displaying information and an input device 1109 such as a mouse and keyboard for user input. The display 1108 and the input device 1109 are both connected to the central processing unit 1101 via an input / output controller 1110 connected to the system bus 1105. The basic input / output system 1106 may also include an input / output controller 1110 for receiving and processing input from a variety of other devices such as a keyboard, mouse, or electronic stylus. Similarly, the input / output controller 1110 also provides output to a display screen, printer, or other types of output devices.

[0184] The mass storage device 1107 is connected to the central processing unit 1101 via a mass storage controller (not shown) connected to the system bus 1105. The mass storage device 1107 and its associated computer-readable storage medium provide non-volatile storage for the computer device 1100. In other words, the mass storage device 1107 may include a computer-readable storage medium (not shown) such as a hard disk or a Compact Disc Read-Only Memory (CD-ROM) drive.

[0185] Without loss of generality, the computer-readable storage medium may include computer storage media and communication media. Computer storage media include volatile and non-volatile, removable and non-removable media implemented by any method or technology for storing information such as computer-readable storage instructions, data structures, program modules or other data. Computer storage media include RAM, ROM, Erasable Programmable Read Only Memory (EPROM), Electronically Erasable Programmable Read-Only Memory (EEPROM), flash memory or other solid-state storage devices, CD-ROM, Digital Versatile Disc (DVD) or other optical storage, tape cassettes, magnetic tape, disk storage or other magnetic storage devices. Of course, those skilled in the art will appreciate that the computer storage media are not limited to the above-mentioned ones. The above-mentioned system memory 1104 and mass storage device 1107 can be collectively referred to as memory.

[0186] The memory stores one or more programs, and the one or more programs are configured to be executed by one or more central processing units 1101. The one or more programs contain instructions for implementing the above-mentioned method embodiments. The central processing unit 1101 executes the one or more programs to implement the methods provided by the above-mentioned method embodiments.

[0187] According to various embodiments of the present application, the computer device 1100 may also be connected to a remote computer device on a network such as the Internet for operation. That is, the computer device 1100 may be connected to a network 1112 via a network interface unit 1111 connected to the system bus 1105. Alternatively, the network interface unit 1111 may be used to connect to other types of networks or remote computer device systems (not shown).

[0188] The memory also includes one or more programs, which are stored in the memory and include steps executed by a computer device in the method provided in the embodiment of the present application.

[0189] A computer-readable storage medium is also provided in an embodiment of the present application, which stores at least one instruction, at least one program, code set or instruction set. When the at least one instruction, at least one program, code set or instruction set is loaded and executed by the processor of a computer device, the refresh method of the vehicle controller provided by the above-mentioned method embodiments is implemented.

[0190] The present application also provides a computer program product or computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the refresh method for a vehicle controller provided in each of the above method embodiments.

Claims

1. A method for refreshing a vehicle controller, wherein: The method is applied to the vehicle controller, and the method comprises: When a refresh device initiates a program update request for the vehicle controller, receiving refresh data of the vehicle controller through a refresh boot program; Refreshing the vehicle controller based on the refresh data by the refresh boot program; The refresh data is used to update the function of the vehicle controller, the refresh boot program and the refresh data are provided by different providers, and the refresh boot program is used to provide the function of refreshing the vehicle controller according to a standard process.

2. The method according to claim 1, wherein: The refreshing of the vehicle controller based on the refresh data by the refresh boot program includes: The refresh data is stored through the first subroutine of the refresh boot program; The system restart instruction is executed through the second subroutine of the refresh boot program, so that the vehicle controller operates according to the stored refresh data.

3. The method according to claim 2, wherein: The method further comprises: Determine the starting storage address of the refresh data in the memory of the vehicle controller through the third subroutine of the refresh boot program; and obtain the data length of the refresh data; The storing of the refresh data through the first subroutine of the refresh boot program comprises: The refresh data is stored according to the start storage address and the data length through the first subroutine of the refresh boot program.

4. The method according to claim 3, wherein: The step of receiving the refresh data of the vehicle controller through a refresh boot program includes: Downloading the refresh data in blocks based on the refresh device through the fourth subroutine of the refresh boot program; The step of storing the refresh data according to the starting storage address and the data length through the first subroutine of the refresh boot program includes: By means of the first subroutine of the refresh boot program, the downloaded data blocks of the refresh data are sequentially stored according to the starting storage address; In a case where the total length of the received data blocks of the refresh data is equal to the data length, it is determined that the storage of the refresh data is completed.

5. The method according to any one of claims 1 to 4, wherein: The method further comprises: By means of a sixth subroutine of the refresh boot program, a first signature value and a second signature value are compared, wherein the first signature value is obtained by means of the refresh device, and the second signature value is calculated according to the refresh data; In the case where it is determined that the first signature value and the second signature value match, it is determined that the acquisition of the refresh data is completed.

6. The method according to claim 2, wherein: The method further comprises: Performing an integrity check on all functional data of the vehicle controller through the seventh subroutine of the refresh boot program; If the integrity check passes, storing a refresh completion flag in the first memory area of ​​the vehicle controller; Among them, the first memory area is used to store the refresh data, the first memory area is the area in the vehicle controller except the second memory area, the second memory area is used to store the historical version function data corresponding to the function updated by the refresh data, and the refresh completion flag is used to indicate that the refresh data is called when the vehicle controller is started.

7. The method according to claim 2, wherein: The method further comprises: The refresh data downloaded by the refresh device is decrypted through the fifth subroutine of the refresh boot program.

8. The method according to claim 2, wherein: The method further comprises: receiving the program update request initiated by the refresh device for the vehicle controller; When it is determined through the eighth subroutine of the refresh boot program that the refresh device passes the security authentication, it is determined to receive the refresh data of the vehicle controller through the refresh boot program.

9. The method according to claim 2, wherein: The refresh boot program is provided by the vehicle's main engine manufacturer, and the refresh data is provided by the supplier of the vehicle controller.

10. The method according to claim 2, wherein: The refresh boot program corresponds to the hardware driver of the vehicle controller, and the method further includes: During the process of refreshing the vehicle controller, data interaction between the refresh boot program and the hardware driver of the vehicle controller is executed through an interactive interface; wherein the hardware driver of the vehicle controller includes at least one of a memory driver, a communication driver, and a timing driver.

11. The method according to claim 10, wherein: The interactive interface is provided by the vehicle's main engine manufacturer, and the hardware driver of the vehicle controller is provided by the supplier of the vehicle controller; The interactive interface is used to implement data interaction between the refresh boot program and different hardware drivers of the vehicle controller.

12. The method according to claim 11, wherein: The interactive interface includes: Memory read interface, memory write interface, receive data interface, send data interface, start timing interface, stop timing interface, reset timing interface and scheduling processing interface.

13. A refreshing device for a vehicle controller, wherein: The device comprises: A receiving module, configured to receive refresh data of the vehicle controller through a refresh boot program when a refresh device initiates a program update request for the vehicle controller; A refresh module, configured to refresh the vehicle controller based on the refresh data through the refresh boot program; The refresh data is used to update the function of the vehicle controller, the refresh boot program and the refresh data are provided by different providers, and the refresh boot program is used to provide the function of refreshing the vehicle controller according to a standard process.

14. The device according to claim 13, wherein: The device also includes: A storage module, used for storing the refresh data through the first subroutine of the refresh boot program; The refresh module is further used to execute a system restart instruction through the second subroutine of the refresh boot program, so that the vehicle controller runs according to the stored refresh data.

15. The device according to claim 14, wherein: The device also includes a determination module and an acquisition module: The determination module is used to determine the starting storage address of the refresh data in the memory of the vehicle controller through the third subroutine of the refresh boot program; The acquisition module is used to acquire the data length of the refresh data; The storage module is further used to store the refresh data according to the starting storage address and the data length through the first subroutine of the refresh boot program.

16. The device according to claim 15, wherein: The receiving module is further used to download the refresh data in blocks based on the refresh device through the fourth subroutine of the refresh boot program; The storage module is further used to store the downloaded data blocks of the refresh data in sequence according to the starting storage address through the first subroutine of the refresh boot program; The determination module is further configured to determine that the storage of the refresh data is completed when the total length of the data blocks of the received refresh data is equal to the data length.

17. The device according to any one of claims 13 to 16, wherein: The device also includes: A comparison module, configured to compare a first signature value and a second signature value through a sixth subroutine of the refresh boot program, wherein the first signature value is obtained through the refresh device, and the second signature value is calculated based on the refresh data; A determination module is used to determine that the acquisition of the refresh data is completed when it is determined that the first signature value and the second signature value match.

18. A computer device, wherein: The computer device includes a processor and a memory, wherein the memory stores at least one program, and the at least one program is loaded and executed by the processor to implement the refreshing method of the vehicle controller as described in any one of claims 1 to 12.

19. A computer-readable storage medium, wherein: The readable storage medium stores at least one program, and the at least one program is loaded and executed by a processor to implement the refreshing method of the vehicle controller as described in any one of claims 1 to 12.

20. A computer program product, wherein: The computer program product includes computer instructions, which are stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the refresh method for a vehicle controller as described in any one of claims 1 to 12.

Images