Vehicle domain controller updating method and device and vehicle

Abstract

The application relates to a domain controller updating method and device of a vehicle and the vehicle, and is applied to a telematics processor of the vehicle. The method comprises the following steps: for each updating file, the current data packet to be sent of the updating file is compressed according to a control parameter, and compressed data is obtained; wherein each updating file is used for updating one domain controller, and the control parameter is determined according to the update time length or the initial value obtained by the domain controller in response to the compressed data corresponding to the last data packet; and the compressed data is sent to the corresponding domain controller based on the control parameter, so that the domain controller is updated based on the compressed data. Therefore, the updating efficiency of each domain controller can be improved, the update time length of all domain controllers is balanced, the overall updating efficiency of the vehicle domain controller is improved, and the user experience is improved.

Description

Technical Field

[0001] This application relates to the field of vehicle technology, and more particularly to a method, apparatus, and vehicle for updating a domain controller. Background Technology

[0002] Currently, the increasing intelligence and personalization of vehicles have led to frequent software updates, and the number and amount of data of domain controllers in vehicles that need to be updated are constantly increasing. These include, but are not limited to, vehicle ECUs (Electronic Control Units) such as smart cockpits, autonomous driving, and vehicle domain control. At the same time, there are also higher requirements for the speed of OTA (Over-the-Air Technology) updates.

[0003] The most common OTA (Over-The-Air) update process for vehicle domain controllers is as follows: the cloud server sends the update file to the TBOX (TelematicsBOX), and then the TBOX sends the update file to the ECU through the gateway, so that the ECU can update according to the update file.

[0004] However, the above process is limited by the size of the data transmitted by the CAN bus, and the performance of the ECUs and the FLASH writing speed are different due to the ECU architecture. This results in a situation where some ECUs are upgraded first, while the remaining ECUs are not upgraded for a long time. As a result, the overall writing efficiency is affected by the local writing efficiency, which leads to low overall update efficiency of the vehicle domain controller and affects the user experience. Summary of the Invention

[0005] This application provides a method, apparatus, and vehicle for updating a vehicle's domain controller, in order to solve the technical problem in the prior art where the overall writing efficiency is affected by the local writing efficiency, resulting in low overall update efficiency of the vehicle's domain controller and impacting user experience.

[0006] In a first aspect, this application provides a domain controller update method for a vehicle, applied to a vehicle's telematics processor, the method comprising:

[0007] For each update file, the current data packet to be sent for the update file is compressed according to the control parameters to obtain compressed data; wherein, each update file is used to update a domain controller, and the control parameters are determined according to the update duration or initial value obtained by the domain controller in response to the compressed data corresponding to the previous data packet;

[0008] The compressed data is sent to the corresponding domain controller based on the control parameters, so that the domain controller can update based on the compressed data.

[0009] As one possible implementation, the control parameters include a compression ratio; the compressed data is obtained by compressing the current data packet to be sent for the update file according to the compression ratio.

[0010] As one possible implementation, the control parameters include a transmission frequency; the compressed data is transmitted to the corresponding domain controller according to the transmission frequency.

[0011] As one possible implementation, the control parameters are determined in the following ways:

[0012] Obtain the current initial control parameters, which correspond to the previous data packet of the updated file;

[0013] The remaining update duration of each domain controller is determined based on the update duration of each domain controller and the number of data packets remaining to be sent in the corresponding update file.

[0014] Determine the average remaining update time for each domain controller based on the remaining update time for all domain controllers.

[0015] The initial control parameters are adjusted based on the remaining update duration of each domain controller and the offset of the average remaining update duration to obtain the control parameters.

[0016] As one possible implementation, the update duration includes the sum of a first duration and a second duration; the first duration includes the time consumed by the domain controller to decompress the compressed data based on the control parameters; the second duration includes the time consumed by the domain controller to perform a flush operation based on the decompressed compressed data.

[0017] As one possible implementation, determining the remaining update duration of the domain controller based on the update duration of each domain controller and the number of data packets remaining to be sent in the corresponding update file includes:

[0018] Determine the ratio of the total amount of data corresponding to the number of remaining data packets to be sent in the updated file to the amount of data sent corresponding to the previous data packet;

[0019] Determine the transmission time of the previous data packet based on the current transmission frequency;

[0020] The product of the update duration, the ratio, and the sending time is determined as the remaining update duration of the domain controller.

[0021] As one possible implementation, when the initial control parameters include a compression ratio, adjusting the initial control parameters based on the remaining update duration of each domain controller and the offset of the average remaining update duration to obtain the control parameters includes:

[0022] Determine whether the offset is greater than a preset first duration threshold;

[0023] If the offset is determined to be greater than the first duration threshold, the compression ratio is reduced according to a preset first adjustment rule to obtain the adjusted compression ratio.

[0024] If the offset is determined to be less than the first duration threshold, the compression ratio is increased according to a preset second adjustment rule to obtain the adjusted compression ratio.

[0025] The step of compressing the current data packet to be sent for the updated file according to the control parameters to obtain compressed data includes:

[0026] If the offset is determined to be less than the first duration threshold, two or more current data packets to be sent are compressed simultaneously to obtain compressed data.

[0027] As one possible implementation, when the initial control parameters include the transmission frequency, adjusting the initial control parameters based on the remaining update duration of each domain controller and the offset of the average remaining update duration to obtain the control parameters includes:

[0028] Determine whether the offset is greater than a preset second duration threshold;

[0029] If the offset is greater than the second duration threshold, the remaining update duration is updated based on the offset to obtain the target remaining update duration;

[0030] Determine the total amount of data corresponding to the number of remaining data packets to be sent in the updated file, and the amount of data sent corresponding to the previous data packet sent last time;

[0031] The adjusted transmission frequency is obtained by calculating the update duration, the total data volume, the transmitted data volume, and the target remaining update duration according to a preset formula.

[0032] As one possible implementation, the initial value is determined in the manner described above:

[0033] The server receives the initial compression ratio sent by the server, wherein the server determines the file characteristics of the updated file by performing character frequency distribution statistics on the updated file, and determines the initial compression ratio based on the file characteristics;

[0034] The initial compression ratio is determined as the initial value;

[0035] The step of compressing the current data packet to be sent for the updated file according to the control parameters to obtain compressed data includes:

[0036] If the current data packet is the first data packet of the updated file, the current data packet is compressed according to the initial value to obtain compressed data.

[0037] Secondly, this application provides a domain controller update device for a vehicle, applied to a vehicle's telematics processor, the device comprising:

[0038] A compression module is used to compress the current data packet to be sent for each update file according to control parameters to obtain compressed data; wherein each update file is used to update a domain controller, and the control parameters are determined based on the update duration or initial value obtained by the domain controller in response to the compressed data corresponding to the previous data packet;

[0039] The sending module is used to send the compressed data to the corresponding domain controller based on control parameters, so that the domain controller can update based on the compressed data.

[0040] Thirdly, this application provides a vehicle including a telematics processor and a memory, the telematics processor being configured to execute a domain controller update program for the vehicle stored in the memory to implement the domain controller update method for the vehicle as described in any one of the first aspects.

[0041] Fourthly, this application provides a storage medium storing one or more programs that can be executed by one or more processors to implement the domain controller update method for a vehicle as described in the first aspect.

[0042] The technical solution provided in this application compresses the current data packet to be sent for each update file according to control parameters to obtain compressed data. Each update file is used to update a domain controller, and the control parameters are determined based on the update duration or initial value obtained by the domain controller in response to the compressed data corresponding to the previous data packet. The compressed data is then sent to the corresponding domain controller based on the control parameters, so that the domain controller updates based on the compressed data. This technical solution compresses the current data packet to be sent according to control parameters when sending the update file to the domain controller, and sends the compressed data. The control parameters can be determined based on the update duration or initial value obtained by the domain controller in response to the compressed data corresponding to the previous data packet. That is, after compressing and sending the first data packet of the update file according to the initial value, the control parameters can be adjusted in real time according to the update duration of the data packet by the domain controller. In this way, the overall time for the domain controller to receive and write the update file can be controlled by adjusting the control parameters, thereby balancing the writing efficiency of the update file by all domain controllers. This improves the update efficiency of each domain controller while balancing the update duration of all domain controllers, thereby improving the overall update efficiency of the vehicle domain controller and enhancing the user experience. Attached Figure Description

[0043] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.

[0044] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the embodiments or the prior art will be briefly introduced below. Obviously, those skilled in the art can obtain other drawings based on these drawings without creative effort.

[0045] One or more embodiments are illustrated by way of example with reference numerals in the accompanying drawings. These illustrations do not constitute a limitation on the embodiments. Elements with the same reference numerals in the drawings are denoted as similar elements. Unless otherwise stated, the figures in the drawings are not to be limited by scale.

[0046] Figure 1 A flowchart illustrating an embodiment of a domain controller update method for a vehicle provided in this application;

[0047] Figure 2 A flowchart illustrating an embodiment of another vehicle domain controller update method provided in this application;

[0048] Figure 3A flowchart illustrating an embodiment of another vehicle domain controller update method provided in this application;

[0049] Figure 4 A flowchart illustrating another embodiment of a vehicle domain controller update method provided in this application;

[0050] Figure 5 A block diagram illustrating an embodiment of a domain controller update device for a vehicle provided in this application;

[0051] Figure 6 This is a structural schematic diagram of a vehicle provided in an embodiment of this application. Detailed Implementation

[0052] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the embodiments described below are only some, not all, of the embodiments of this application. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0053] The following disclosure provides numerous different embodiments or examples for implementing various structures of the invention. To simplify the disclosure, specific examples of components and arrangements are described below. These are merely examples and are not intended to limit the scope of the invention. Furthermore, reference numerals and / or letters may be repeated in different examples. Such repetition is for simplification and clarity and does not in itself indicate a relationship between the various embodiments and / or arrangements discussed.

[0054] To address the technical problem in existing technologies where overall write efficiency is affected by local write efficiency, leading to low overall update efficiency of vehicle domain controllers and impacting user experience, this application provides a vehicle domain controller update method, apparatus, and vehicle. This method compresses the current data packet to be sent according to control parameters when sending an update file to the domain controller, and then sends the compressed data. The control parameters can be determined based on the update duration or initial value obtained from the domain controller's response to the compressed data of the previous data packet. That is, after compressing and sending the first data packet of the update file according to the initial value, the control parameters can be adjusted in real time based on the update duration of the data packet by the domain controller. This allows for control over the overall time for the domain controller to subsequently receive and write update files, thereby balancing the write efficiency of all domain controllers. This improves the update efficiency of each domain controller while balancing the update duration of all domain controllers, ultimately enhancing the overall update efficiency of the vehicle domain controller and improving the user experience.

[0055] The domain controller update method for vehicles provided in this application will be further explained and described below with reference to the accompanying drawings and specific embodiments. The embodiments do not constitute a limitation on the embodiments of the present invention.

[0056] See Figure 1 This is a flowchart illustrating an embodiment of a domain controller update method for a vehicle provided in this application. As one embodiment, Figure 1 The illustrated process can be applied to a vehicle's telematics processor. For example... Figure 1 As shown, the process may include the following steps:

[0057] Step 101: For each update file, compress the current data packet to be sent for the update file according to the control parameters to obtain compressed data; wherein, each update file is used to update a domain controller, and the control parameters are determined according to the update duration or initial value obtained by the domain controller in response to the compressed data corresponding to the previous data packet.

[0058] The aforementioned update file refers to the file used to update the vehicle's domain controller. The domain controller can update itself based on the data in this update file. Each domain controller can have one update file, and different domain controllers can have different update files.

[0059] The aforementioned control parameters may include a compression ratio, which can be used to compress data packets in the update file. This compression ratio can be the ratio of the original data before compression to the compressed data after compression, such as C in formula (i):

[0060]

[0061] Wherein, C refers to the compression ratio, and S refers to... 原 The S refers to the original data before compression. 压缩 This is the compressed data.

[0062] Based on this, the compressed data is obtained by compressing the current data packet to be sent for the update file according to the compression ratio.

[0063] The aforementioned control parameters may also include a transmission frequency, which characterizes the frequency at which data packets are sent to the domain controller.

[0064] The aforementioned data packet refers to a data packet that is pre-splittered from the update file. The data packet may include one or more frame data. The number of frame data contained in different data packets may be the same or different, and the amount of data corresponding to each data packet may be the same or different. This application embodiment does not impose any restrictions on this.

[0065] The aforementioned update duration refers to the time it takes for the domain controller to update the received compressed data, which may include the total time for all operations such as decompressing the compressed data and writing the decompressed data to flash memory.

[0066] The aforementioned initial value refers to the value of the initially determined control parameter, which can be the initial value of the compression ratio or the initial value of the transmission frequency. This application embodiment does not limit this.

[0067] In practical applications, when updating the domain controller of a vehicle, the update process is as follows: the cloud server sends the update file to the TBOX (TelematicsBOX), and then the TBOX sends the update file to the corresponding domain controller through the gateway. The domain controller then updates itself according to the update file.

[0068] Based on this, the execution entity in this application embodiment can be the aforementioned remote information processor of the vehicle. In this application embodiment, the aforementioned remote information processor can receive an update file sent by a cloud server and compress the current data packet of the update file to be sent according to determined control parameters to obtain compressed data. The aforementioned data packet can be one or more frame data corresponding to the flashing protocol in the domain controller.

[0069] As an optional implementation, when the above control parameters include a compression ratio, the compression ratio can be determined based on the update time obtained by the domain controller in response to the compressed data corresponding to the previous data packet. Different update files may correspond to different compression ratios, or they may correspond to the same compression ratio; this embodiment does not impose any restrictions on this.

[0070] The specific method by which the compression ratio is determined based on the update time obtained by the domain controller in response to the compressed data of the previous data packet will be explained below. Figure 3 The process shown will be explained in detail here.

[0071] As another optional implementation, if the above control parameters include the compression ratio, the compression ratio can be a preset initial value.

[0072] As one implementation method, the initial value mentioned above can be a value preset by the user through a visual interface.

[0073] As another implementation method, the initial value mentioned above can be determined by the cloud server for different update files. By selecting different compression ratios for different update files, the cloud server can more efficiently compress each update file to different degrees, thereby improving the efficiency of data transmission.

[0074] As an exemplary implementation, a cloud server can... Figure 2 The process shown sends multiple update files and the initial compression ratio for each update file to the remote information processor. See also... Figure 2 This is a flowchart illustrating an embodiment of another vehicle domain controller update method provided in this application. Figure 2 The illustrated process describes how the cloud server sends multiple update files and the initial compression ratio for each update file to the remote information processor. For example... Figure 2 As shown, the process may include the following steps:

[0075] Step 201: For each updated file to be sent, perform character frequency distribution statistics on the updated file to obtain the corresponding statistical results.

[0076] Step 202: Based on the statistical results of the updated files, determine the file characteristics of the updated files.

[0077] Step 203: Based on the above file characteristics, determine the compression algorithm and compression ratio corresponding to the updated file.

[0078] The following provides a unified explanation of steps 201 to 203:

[0079] In this embodiment of the application, the cloud server may pre-store update files for multiple domain controllers in the vehicle. These update files may be update files pre-uploaded by the user or update files pre-downloaded from other clients. This embodiment of the application does not impose any restrictions on this.

[0080] Therefore, in order to enable the remote information processor to transmit each update file to the domain controller efficiently, the cloud server can determine an initial compression ratio and compression algorithm for each update file.

[0081] As an optional implementation, the cloud server can obtain the initial compression ratio and compression algorithm for each updated file through a visual interface or from a preset storage medium. Different updated files may have the same initial compression ratio and compression algorithm or different initial compression ratios and compression algorithms. This application embodiment does not limit this.

[0082] As another optional implementation, the cloud server can perform character frequency distribution statistics on each update file to be sent, and obtain the corresponding statistical results for that update file.

[0083] As an exemplary implementation, when performing character frequency distribution statistics on an updated file, information such as the number of repeated characters and the size of the vocabulary appearing in the updated file can be counted.

[0084] Based on this, the cloud server can determine the file characteristics of the updated file according to the above statistical results, and determine the corresponding compression algorithm and initial compression ratio based on these file characteristics. These file characteristics may include, but are not limited to, characteristics such as the repeating pattern and vocabulary size of the updated file.

[0085] Optionally, when the updated file's file characteristics are the first file characteristics (which can be a repetition pattern), the cloud server can determine the first type of compression algorithm and compression ratio as the corresponding compression algorithm and compression ratio for the updated file. For example, when the updated file is a HEX, S19, or similar file, its compression algorithm can be Huffman coding or the Lempel-Ziv-Welch (LZW) algorithm. These compression algorithms can effectively compress data based on its repetition pattern. Huffman coding is suitable for frequently occurring characters, while LZW is suitable for data with repetition patterns.

[0086] Optionally, when the updated file's file characteristics are the second file characteristics (which can be vocabulary size), the cloud server can determine the second type of compression algorithm and compression ratio as the compression algorithm and compression ratio corresponding to the updated file. For example, when the updated file is a bin file, its compression algorithm can be ZIP, GZIP, BZIP2, or more efficient algorithms such as LZ4 and Zstandard. It can handle various types of binary data.

[0087] Step 204: Send multiple update files, along with the compression ratio and compression algorithm for each update file, to the remote information processor.

[0088] In this embodiment of the application, after determining the initial compression ratio and compression algorithm corresponding to each updated file, the cloud server can send multiple updated files to be sent, as well as the initial compression ratio and compression algorithm corresponding to each updated file, to the remote information processor.

[0089] As an optional implementation, the cloud server can first send multiple update files, along with the initial compression ratio and compression algorithm corresponding to each update file, to the remote information processor.

[0090] As another optional implementation, the cloud server can first send multiple update files to the remote information processor. Then, after confirming that the remote information processor has received multiple update files, it can send the initial compression ratio and compression algorithm corresponding to each update file to the remote information processor.

[0091] As another optional implementation, the cloud server can first send multiple update files and the initial compression ratio corresponding to each update file to the remote information processor. Then, after determining that the remote information processor has received multiple update files and the initial compression ratio of each update file, it can send the compression algorithm of each update file to the remote information processor.

[0092] As another optional implementation, the cloud server can first send multiple update files and the compression algorithm corresponding to each update file to the remote information processor. Then, after determining that the remote information processor has received multiple update files and the compression algorithm of each update file, it can send the initial compression ratio of each update file to the remote information processor.

[0093] This completes the work on... Figure 2 Description of the process shown.

[0094] Based on the above Figure 2 As shown in the process, the remote information processor can receive multiple update files sent by the aforementioned cloud server, along with the initial compression ratio and compression algorithm corresponding to each update file. Then, the initial compression ratio corresponding to each update file can be determined as an initial value.

[0095] Based on this, when compressing the current data packet to be sent for the update file according to the control parameters, if the current data packet is the first data packet of the update file, the current data packet can be compressed according to the above initial values ​​to obtain compressed data.

[0096] Furthermore, for each received update file, the corresponding compression algorithm can be determined, and the current data packet to be sent for that update file can be compressed according to the aforementioned compression algorithm to obtain compressed data.

[0097] Step 102: Send the compressed data to the corresponding domain controller based on the control parameters so that the domain controller can update based on the compressed data.

[0098] The aforementioned control parameter can be the transmission frequency, which characterizes the frequency at which data packets are sent to the domain controller.

[0099] Based on this, in the embodiments of this application, before sending the corresponding compressed data to each domain controller, the remote information processor can first determine the transmission frequency corresponding to each domain controller, and after determining the transmission frequency corresponding to each domain controller, send the compressed data to the corresponding domain controller according to the transmission frequency.

[0100] As an optional implementation, when the above control parameters include the transmission frequency, the transmission frequency can be determined based on the update duration obtained by the domain controller in response to the compressed data corresponding to the previous data packet. Different update files can correspond to different transmission frequencies, or they can correspond to the same transmission frequency; this embodiment does not impose any limitations on this.

[0101] The specific method by which the transmission frequency is determined based on the update duration obtained by the domain controller in response to the compressed data corresponding to the previous data packet will be explained below. Figure 3 The process shown will be explained in detail here.

[0102] As another optional implementation, if the above control parameters include the transmission frequency, the transmission frequency can be a preset initial value.

[0103] As an example implementation, the remote information processor can obtain the initial value of the transmission frequency corresponding to each domain controller from a preset storage medium.

[0104] As another exemplary implementation, the remote information processor can obtain the initial value of the transmission frequency setting for each domain controller from the visual interface, and store the received initial value, the correspondence between the domain controller and the initial value in a preset storage medium.

[0105] Furthermore, in this embodiment of the application, the remote information processor compresses the current data packet to be sent for each updated file, and after obtaining compressed data, it can send the compressed data and compression ratio to the domain controller corresponding to the updated file. The compression ratio can be an initial compression ratio or a compression ratio determined based on the update duration obtained by the domain controller in response to the compressed data corresponding to the previous data packet.

[0106] Based on this, after receiving the compressed data and compression ratio, the domain controller can decompress the compressed data according to the compression ratio to obtain the original data, and then perform a write operation on the original data.

[0107] As an optional implementation, when the remote information processor compresses the current data packet according to a preset compression algorithm, the domain controller can decompress the compressed data according to a preset decompression algorithm corresponding to the compression algorithm.

[0108] As an alternative implementation, when the remote information processor compresses the current data packet according to the compression algorithm corresponding to the update file sent by the remote server, the remote information processor can determine the decompression algorithm corresponding to the compression algorithm before sending the compressed data and compression ratio to the corresponding domain controller. Then, it can determine the serial number of the domain controller corresponding to the update file and send the decompression algorithm to the domain controller corresponding to the update file based on that serial number.

[0109] Based on this, the domain controller can decompress the compressed data according to the decompression algorithm described above.

[0110] Furthermore, the pre-controller can record the first duration consumed in decompressing the compressed data. Then, a flush operation can be performed on the original data, and the second duration of this flush operation can be recorded. Finally, the domain controller can send the first and second durations to the remote information processor.

[0111] In this embodiment of the application, after the remote information processor sends the compressed data and compression ratio to the corresponding domain controller, it can obtain the update time of the domain controller for the compressed data.

[0112] As an optional implementation, as described above, after receiving the compressed data and compression ratio, the domain controller can perform decompression and write operations on the compressed data, record the first duration of decompression and the second duration of writing operations, and then send the first duration and the second duration to the remote information processor.

[0113] Based on this, the remote information processor can receive the first duration and the second duration sent by the pre-controller, and add the first duration and the second duration together to obtain the update duration of the pre-controller for the compressed data.

[0114] Based on the update duration obtained above, the remote information processor can continue to adjust the current control parameters according to the update duration to determine the control parameters for the new current data packet to be sent. In this way, except for the first current data packet to be sent, a control parameter can be determined for each current data packet to be sent based on the update duration obtained by the domain controller in response to the compressed data corresponding to the previous data packet. Thus, by adjusting the control parameters, the overall duration of the domain controller receiving and writing update files can be controlled to balance the writing efficiency of update files by all domain controllers.

[0115] In addition, after receiving multiple update files sent by the cloud server, and the compression ratio corresponding to each update file, the remote information processor can determine the number of received update files for easy storage, and create a data queue with the number of files mentioned above. Each data queue can be used to store one update file.

[0116] Then, for each updated file, the updated file and compression ratio can be stored in the data queue corresponding to the updated file.

[0117] Subsequently, once the update duration of the compressed data by the domain controller is obtained, the update duration can be stored in the data queue corresponding to the updated file.

[0118] Furthermore, as described above, the update duration may include a first duration for decompressing the compressed data and a second duration for writing the decompressed original data. Therefore, the first and second durations can be stored in the data queue corresponding to the update file.

[0119] The technical solution provided in this application compresses the current data packet to be sent for each update file according to control parameters to obtain compressed data. Each update file is used to update a domain controller, and the control parameters are determined based on the update duration or initial value obtained by the domain controller in response to the compressed data corresponding to the previous data packet. The compressed data is then sent to the corresponding domain controller based on the control parameters, so that the domain controller updates based on the compressed data. This technical solution compresses the current data packet to be sent according to control parameters when sending the update file to the domain controller, and sends the compressed data. The control parameters can be determined based on the update duration or initial value obtained by the domain controller in response to the compressed data corresponding to the previous data packet. That is, after compressing and sending the first data packet of the update file according to the initial value, the control parameters can be adjusted in real time according to the update duration of the data packet by the domain controller. In this way, the overall time for the domain controller to receive and write the update file can be controlled by adjusting the control parameters, thereby balancing the writing efficiency of the update file by all domain controllers. This improves the update efficiency of each domain controller while balancing the update duration of all domain controllers, thereby improving the overall update efficiency of the vehicle domain controller and enhancing the user experience.

[0120] See Figure 3 This is a flowchart illustrating another embodiment of a vehicle domain controller update method provided in this application. Figure 3 The process shown is in Figure 1 Based on the illustrated process, the specific methods for obtaining the control parameters are described. For example... Figure 3 As shown, the process may include the following steps:

[0121] Step 301: Obtain the current initial control parameters, which correspond to the previous data packet of the update file.

[0122] The aforementioned initial control parameters refer to the control parameters used by the remote information processor to compress and send the previous data packet before the current data packet.

[0123] In one embodiment, after the remote information processor compresses and sends the current data packet to be sent using the applied control parameters, it can store the control parameters. Based on this, when processing the latest current data packet, the remote information processor can first obtain the currently stored initial control parameters, adjust the initial control parameters to obtain the adjusted control parameters, and then compress and send the latest current data packet according to the adjusted control parameters.

[0124] Step 302: Obtain the update duration of each domain controller and the number of data packets remaining to be sent for the corresponding update file, and determine the remaining update duration of the domain controller.

[0125] Step 303: Determine the average remaining update time of the domain controllers based on the remaining update time of all domain controllers.

[0126] The following provides a unified explanation of steps 302 and 303:

[0127] The update duration may include a first duration and a second duration. The first duration includes the time consumed by the domain controller to decompress the compressed data based on the control parameters, and the second duration may include the time consumed by the domain controller to perform a flash operation based on the decompressed compressed data.

[0128] The remaining update time mentioned above refers to the remaining time required for the domain control to complete all updates to the corresponding update file.

[0129] The average remaining update time mentioned above refers to the average of the remaining update time for all domain controllers.

[0130] pass Figure 1 As can be seen from the description of the process, after receiving the compressed data, the domain controller can perform decompression and flashing operations on the compressed data, record the first duration of decompression and the second duration of flashing operations, and then send the first duration and the second duration to the remote information processor.

[0131] Based on this, the remote information processor can receive the first duration and the second duration sent by the pre-controller, and add the first duration and the second duration together to obtain the update duration of the pre-controller for the compressed data.

[0132] In this embodiment of the application, after obtaining the update duration of each domain controller, the remote information processor can obtain the number of data packets to be sent in the corresponding update file of each domain controller, and determine the remaining update duration of each domain controller based on the update duration and the number of data packets.

[0133] As an optional implementation, for each domain controller, the total amount of data corresponding to the number of remaining packets to be sent in the update file corresponding to that domain controller can be determined, as well as the ratio of the amount of data sent to the previous packet sent.

[0134] Then, based on the current transmission frequency, the transmission time of the previous data packet can be determined. Specifically, the reciprocal of the transmission frequency can be used to determine the transmission time of the previous data packet.

[0135] Finally, the product of the above update duration, the above ratio, and the above sending time can be determined as the remaining update duration of the domain controller.

[0136] As one implementation method, the remaining update duration of the domain controller can be determined using the preset formula shown in Equation (II):

[0137]

[0138] Wherein, Ts is the remaining update duration, T is the update duration, D1 is the total data volume, D2 is the data volume sent, and F is the transmission frequency.

[0139] Based on the determined remaining update duration for each domain controller, the remaining update durations for all domain controllers can be summed to obtain the total remaining update duration. The total remaining update duration can then be divided by the total number of domain controllers to obtain the average remaining update duration for all domain controllers.

[0140] Step 304: Adjust the initial control parameters based on the remaining update duration of each domain controller and the offset of the average remaining update duration to obtain the control parameters.

[0141] The aforementioned offset refers to the difference between the remaining update duration of each domain controller and the average remaining update duration. It can be obtained by subtracting the average remaining update duration from the remaining update duration of the domain controller. The offset can be positive or negative. When the offset is positive, it means that the remaining update duration of the domain controller is greater than the average remaining update duration; when the offset is negative, it means that the remaining update duration of the domain controller is less than the average remaining update duration.

[0142] In this embodiment of the application, in order to balance the remaining update time of all domain controllers, that is, to make the remaining update time of all domain controllers approximately equal, thereby improving the overall update efficiency of the domain controllers, the remote information processor can determine the offset of the remaining update time of each domain controller relative to the average remaining update time, and adjust the initial control parameters corresponding to each domain controller according to the offset to obtain the control parameters corresponding to the current data packet to be sent.

[0143] In one embodiment, when the initial control parameters include a compression ratio, when adjusting the initial control parameters corresponding to each pre-controller, it can be determined whether the offset corresponding to each domain controller is greater than a preset first duration threshold. The first duration threshold is a preset threshold, which can be 0 or other values, and this embodiment does not limit it.

[0144] Optionally, if the offset is greater than the first time threshold, it indicates that the remaining update time of the domain controller is greater than the average remaining update time. In this case, the domain controller updates the compressed data slowly, which may include slow decompression of the compressed data or a long flush operation on the decompressed original data. Therefore, to reduce the remaining update time of the domain controller, the compression ratio can be reduced according to a preset first adjustment rule to obtain an adjusted compression ratio. By reducing the compression ratio, the compression complexity of the original data can be reduced, thereby reducing the first time of decompressing the compressed data and increasing the update efficiency of the domain controller. The first adjustment rule can be to reduce the compression ratio according to a first preset step size.

[0145] Conversely, if the offset is less than the first duration threshold, it indicates that the remaining update duration of the domain controller is less than the average remaining update duration. In this case, the domain controller updates the compressed data faster, which may include faster decompression of the compressed data or a shorter flush operation on the decompressed raw data. Therefore, the compression ratio can be increased according to a preset second adjustment rule to obtain an adjusted compression ratio. Increasing the compression ratio reduces the data transmission volume, thereby improving data transmission efficiency and achieving a balance in the remaining update duration of all domain controllers. The second adjustment rule can be to increase the compression ratio by a second preset step size.

[0146] Furthermore, in order to improve the update efficiency of the domain controller, if the offset is determined to be less than the first duration threshold, two or more current data packets to be sent can be compressed simultaneously to obtain compressed data.

[0147] In one embodiment, when the initial control parameters include the transmission frequency, when adjusting the initial control parameters, it can be determined whether the offset is greater than a preset second duration threshold. The second duration threshold can be a preset duration threshold, which can be 0 or other values. This application embodiment does not limit this.

[0148] Optionally, if the offset is greater than the second duration threshold, it indicates that the remaining update duration of the domain controller is greater than the average remaining update duration. In order to improve the overall update efficiency of the domain controller, the remote information processor can adjust the transmission frequency of the domain controller to reduce the remaining update duration of the domain controller.

[0149] As an optional implementation, the remaining update duration of the domain controller can be updated based on the above offset to obtain the target remaining update duration.

[0150] As an exemplary implementation, the above-mentioned average remaining update duration can be determined as the target remaining update duration.

[0151] Then, the total amount of data corresponding to the number of remaining data packets to be sent in the update file of the domain controller can be determined, as well as the amount of data sent one-to-one with the previous data packet sent. The update duration, the total amount of data, the amount of data sent, and the target remaining update duration are calculated according to a preset formula to obtain the adjusted sending frequency.

[0152] As an exemplary implementation, the above-mentioned preset formula can be represented by the following equation (iii):

[0153]

[0154] Wherein, T2 is the remaining update duration of the target, T is the update duration, D1 is the total data volume, D2 is the data volume to be sent, and F1 is the adjusted transmission frequency.

[0155] Conversely, if the offset is less than or equal to the second duration threshold, it means that the remaining update duration of the domain controller is less than or equal to the average remaining update duration. This will not reduce the overall update efficiency of the domain controller. Therefore, the transmission frequency corresponding to the domain controller does not need to be adjusted, that is, the current transmission frequency is determined as the control parameter corresponding to the current data packet.

[0156] Through the above adjustment process, the adjusted control parameters can be obtained. These control parameters may include the adjusted compression ratio and the adjusted transmission frequency. Based on this, the remote information processor can compress the current data packet to be transmitted according to the adjusted compression ratio to obtain compressed data, and send the compressed data to the domain controller according to the adjusted transmission frequency.

[0157] The technical solution provided in this application obtains the current initial control parameters, which correspond to the previous data packet of the update file. It then obtains the update duration of each domain controller and the number of remaining data packets to be sent for the corresponding update file, determines the remaining update duration of each domain controller, determines the average remaining update duration of all domain controllers based on the remaining update duration of all domain controllers, and adjusts the initial control parameters based on the offset between the remaining update duration of each domain controller and the average remaining update duration. This technical solution, by determining the remaining update duration of each domain controller and the average remaining update duration of all domain controllers based on the update duration of the previous data packet, adjusts the remaining update duration of each domain controller to be close to the average remaining update duration, making the total update duration of all domain controllers approximately equal. This balances the writing efficiency of all domain controllers to the update file, achieving accurate and efficient adjustment of the control parameters for the current data packet. This improves the update efficiency of each domain controller while balancing the update duration of all domain controllers, thereby improving the overall update efficiency of the vehicle domain controller and enhancing the user experience.

[0158] See Figure 4 This is a flowchart illustrating another embodiment of a vehicle domain controller update method provided in this application. Figure 5 The illustrated flow describes the data interaction process between the cloud server, the remote information processor, and the domain controller (ECU). For example... Figure 4 As shown, the process may include the following:

[0159] 1. Cloud server data preparation:

[0160] The server-side uses a Python program to compress and analyze the HEX, BIN, and S19 files used in the firmware upgrade program for the ECU. It performs data characteristic statistics on the updated files and selects the most balanced compression algorithm with adjustable compression ratio C based on these characteristics. For HEX and S19 files, the most common and effective methods are Huffman coding or Lempel-Ziv-Welch (LZW) algorithms. These algorithms effectively compress data based on its statistical characteristics. Huffman coding is suitable for frequently occurring characters, while LZW is suitable for repetitive patterns. Common compression methods for BIN files include ZIP, GZIP, BZIP2, or more efficient algorithms such as LZ4 and Zstandard. These can handle various types of binary data. Each ECU upgrade program corresponds to a set of compression and decompression algorithms. The compression algorithms, the firmware update files, and the initial compression ratio for each update file are then sent to the TBOX.

[0161] 2. TBOX initialization:

[0162] When TBOX receives data sent by the server (including update files and the compression algorithm and compression ratio corresponding to each update file), it creates N data queues, where N is the number of ECUs to be upgraded. The data fields in the data queues include: original firmware data (update files), compressed data sent in one frame of the flashing protocol, compression ratio C, and response parameters from the ECU. These response parameters include the ECU's decompression time T1, the ECU's FLASH write time T2, the parallel transmission frequency F, and the remaining flashing time T (remain).

[0163] 3. TBOX sends data:

[0164] TBOX sends decompression functions to each ECU in parallel based on the ECU serial number. After receiving the function, the ECU writes it into RAM. The ECU waits for the remaining data from TBOX (compressed data corresponding to the frame data to be sent in the update file). Next, TBOX extracts the data packets to be sent from the update file, compresses them, selects the compression ratio C, and obtains the corresponding compressed data.

[0165] 3. ECU data reception:

[0166] After the ECU receives the decompression function sent by the TBOX for the first time and writes it into RAM, it waits for the upgrade program (i.e., update file) sent by the TBOX. The ECU receives the data from the TBOX, decompresses it according to the compression ratio, records the decompression time T1, and records the FLASH write time T2 and feeds it back to the TBOX.

[0167] 4. Adjust the sending method of TBOX:

[0168] TBOX receives the parameters sent back by the ECU, calculates the remaining flashing time T(remain), and determines whether each ECU upgrade can maximize T11(remain)≈T12(remain)≈T13(remain)... where T11(remain) is the remaining update time of the first domain controller, T12(remain) is the remaining update time of the second domain controller, T13(remain) is the remaining update time of the third domain controller, and so on.

[0169] Optionally, if the sum of the decompression time T1 and the FLASH writing time, i.e., T1+T2, is small (less than the preset duration threshold), multiple frame data can be selected for multi-packet compression and the compression ratio C can be increased. Taking advantage of the high performance of the ECU, the transmission frequency F can be dynamically adjusted according to the remaining upgrade time.

[0170] Optionally, if the sum of the decompression time T1 and the FLASH writing time, i.e., T1+T2, is large (greater than the preset duration threshold), the compression ratio C can be reduced to alleviate the pressure on the ECU, and the sending frequency F can be dynamically adjusted according to the remaining upgrade time.

[0171] The remaining total time for ECU upgrades in the plan can be determined using the following formula (iv):

[0172]

[0173] Where i represents the i-th ECU, n represents the total number of ECUs, Xt represents the remaining total time of the ECU upgrade process, and T 1i This represents the decompression time of the data packet decompressed by the i-th ECU (i.e., Figure 1 The first duration in the process shown), T 2i This represents the write time of a single data packet to the FLASH memory of the i-th ECU (i.e., Figure 1 The second duration in the process shown), D1i represents the total amount of remaining data in the update file corresponding to the i-th ECU (that is, the total amount of data in the update file that has not been sent), D2i represents the total amount of data sent by TBOX to the i-th ECU in one go (that is, the amount of data sent each time), and Fi represents the initial sending frequency of TBOX to the i-th update file.

[0174] Furthermore, the average remaining update time for ECU upgrades can be determined using the following formula (v):

[0175]

[0176] Where i represents the i-th ECU, and n represents the total number of ECUs. Xt represents the average remaining update time for the entire ECU upgrade process, T 1i This represents the decompression time of the data packet decompressed by the i-th ECU (i.e., Figure 1 The first duration in the process shown), T 2i This represents the write time of a single data packet to the FLASH memory of the i-th ECU (i.e., Figure 1 The second duration in the process shown), D1i represents the total amount of remaining data in the update file corresponding to the i-th ECU (that is, the total amount of data in the update file that has not been sent), D2i represents the total amount of data corresponding to the i-th ECU sent by TBOX in one go (that is, the amount of data sent each time), and Fi represents the initial sending frequency of TBOX for the i-th update file.

[0177] 5. Data verification and debugging

[0178] Data integrity verification: After the data transmission is completed, the integrity and accuracy of the FLASH data are verified to ensure that all data is loaded correctly.

[0179] The technical solution provided in this application maximizes the data transmission volume of the CAN bus per unit time by compressing the upgrade data. It coordinates data transmission based on the different performance computing power of each ECU, the different FLASH write time, and the different number of CPU tasks. The TBOX receives the decompression time T1 and FLASH write time T2 sent by the ECU to calculate the input compression ratio C and the parallel communication frequency F, thereby determining the data compression degree of the framed data packets and the frequency of parallel data update, improving the parallel upgrade efficiency and greatly reducing the upgrade time of the whole vehicle.

[0180] See Figure 5 This is a block diagram illustrating an embodiment of a vehicle domain controller update device provided in this application. As one embodiment, Figure 5 The device shown can be applied to a vehicle's telematics processor. For example... Figure 5 As shown, the device may include:

[0181] Compression module 51 is used to compress the current data packet to be sent for each update file according to control parameters to obtain compressed data; wherein each update file is used to update a domain controller, and the control parameters are determined according to the update duration or initial value obtained by the domain controller in response to the compressed data corresponding to the previous data packet;

[0182] The sending module 52 is used to send the compressed data to the corresponding domain controller based on control parameters, so that the domain controller can update based on the compressed data.

[0183] like Figure 6 The diagram shown is a structural schematic of a vehicle according to an embodiment of this application, including a processor 61, a communication interface 62, a memory 63, and a communication bus 64. The processor 61, communication interface 62, and memory 63 communicate with each other via the communication bus 64.

[0184] Memory 63 is used to store computer programs;

[0185] In one embodiment of this application, when the processor 61 executes the program stored in the memory 63, it implements the vehicle domain controller update method provided in any of the foregoing method embodiments, including:

[0186] For each update file, the current data packet to be sent for the update file is compressed according to the control parameters to obtain compressed data; wherein, each update file is used to update a domain controller, and the control parameters are determined according to the update duration or initial value obtained by the domain controller in response to the compressed data corresponding to the previous data packet;

[0187] The compressed data is sent to the corresponding domain controller based on the control parameters, so that the domain controller can update based on the compressed data.

[0188] This application also provides a storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of the vehicle domain controller update method provided in any of the foregoing method embodiments.

[0189] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0190] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented using software and a general-purpose hardware platform, or of course, using hardware. Based on this understanding, the above technical solutions, in essence or the parts that contribute to the related technology, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0191] It should be understood that the terminology used herein is for the purpose of illustrating specific embodiments of the text only and is not intended to be limiting. Unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “described” as used herein may also include the plural forms. The terms “comprising,” “including,” “containing,” and “having” are inclusive and therefore indicate the presence of the stated features, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, elements, components, and / or combinations thereof. The method steps, processes, and operations described herein are not construed as requiring them to be performed in the specific order described or illustrated unless the order is explicitly indicated. It should also be understood that additional or alternative steps may be used.

[0192] The above description is merely a specific embodiment of the present invention, enabling those skilled in the art to understand or implement the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Therefore, the present invention is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A method for updating a vehicle's domain controller, characterized in that, A telematics processor applied to a vehicle, the method comprising: For each update file, the current data packet to be sent for the update file is compressed according to the control parameters to obtain compressed data; wherein, each update file is used to update a domain controller, and the control parameters are determined according to the update duration or initial value obtained by the domain controller in response to the compressed data corresponding to the previous data packet; The compressed data is sent to the corresponding domain controller based on the control parameters, so that the domain controller can be updated based on the compressed data; The control parameters are determined in the following manner: Obtain the current initial control parameters, which correspond to the previous data packet of the updated file, and the initial control parameters include compression ratio and transmission frequency; The remaining update duration of each domain controller is determined based on its update duration and the number of data packets remaining to be sent in the corresponding update file. This includes: determining the ratio of the total data volume corresponding to the number of data packets remaining to be sent in the update file to the data volume corresponding to the previous data packet; determining the sending time of the previous data packet based on the current sending frequency; and multiplying the update duration, the ratio, and the sending time to determine the remaining update duration of the domain controller. Determine the average remaining update time for each domain controller based on the remaining update time for all domain controllers. The initial control parameters are adjusted based on the remaining update duration of each domain controller and the offset of the average remaining update duration to obtain the control parameters.

2. The method according to claim 1, characterized in that, The control parameters include a compression ratio; the compressed data is obtained by compressing the current data packet to be sent for the update file according to the compression ratio.

3. The method according to claim 1, characterized in that, The control parameters include the transmission frequency; the compressed data is transmitted to the corresponding domain controller according to the transmission frequency.

4. The method according to claim 1, characterized in that, The update duration includes the sum of a first duration and a second duration; the first duration includes the time consumed by the domain controller to decompress the compressed data based on the control parameters; the second duration includes the time consumed by the domain controller to perform a flash operation based on the decompressed compressed data.

5. The method according to claim 1, characterized in that, When the initial control parameters include a compression ratio, adjusting the initial control parameters based on the remaining update time of each domain controller and the offset of the average remaining update time to obtain the control parameters includes: Determine whether the offset is greater than a preset first duration threshold; If the offset is determined to be greater than the first duration threshold, the compression ratio is reduced according to a preset first adjustment rule to obtain the adjusted compression ratio. If the offset is determined to be less than the first duration threshold, the compression ratio is increased according to a preset second adjustment rule to obtain the adjusted compression ratio. The step of compressing the current data packet to be sent for the updated file according to the control parameters to obtain compressed data includes: If the offset is determined to be less than the first duration threshold, two or more current data packets to be sent are compressed simultaneously to obtain compressed data.

6. The method according to claim 1, characterized in that, When the initial control parameters include the transmission frequency, adjusting the initial control parameters based on the remaining update duration of each domain controller and the offset of the average remaining update duration to obtain the control parameters includes: Determine whether the offset is greater than a preset second duration threshold; If the offset is greater than the second duration threshold, the remaining update duration is updated based on the offset to obtain the target remaining update duration; Determine the total amount of data corresponding to the number of remaining data packets to be sent in the updated file, and the amount of data sent corresponding to the previous data packet sent last time; The adjusted transmission frequency is obtained by calculating the update duration, the total data volume, the transmitted data volume, and the target remaining update duration according to a preset formula.

7. The method according to claim 1, characterized in that, The initial value is determined in the following way: The server receives the initial compression ratio sent by the server, wherein the server determines the file characteristics of the updated file by performing character frequency distribution statistics on the updated file, and determines the initial compression ratio based on the file characteristics; The initial compression ratio is determined as the initial value; The step of compressing the current data packet to be sent for the updated file according to the control parameters to obtain compressed data includes: If the current data packet is the first data packet of the updated file, the current data packet is compressed according to the initial value to obtain compressed data.

8. A domain controller update device for a vehicle, characterized in that, A telematics processor for use in vehicles, the device comprising: A compression module is used to compress the current data packet to be sent for each update file according to control parameters to obtain compressed data; wherein each update file is used to update a domain controller, and the control parameters are determined based on the update duration or initial value obtained by the domain controller in response to the compressed data corresponding to the previous data packet; A sending module is used to send the compressed data to the corresponding domain controller based on control parameters, so that the domain controller can be updated based on the compressed data; The control parameters are determined in the following manner: Obtain the current initial control parameters, which correspond to the previous data packet of the updated file, and the initial control parameters include compression ratio and transmission frequency; The remaining update duration of each domain controller is determined based on its update duration and the number of data packets remaining to be sent in the corresponding update file. This includes: determining the ratio of the total data volume corresponding to the number of data packets remaining to be sent in the update file to the data volume corresponding to the previous data packet; determining the sending time of the previous data packet based on the current sending frequency; and multiplying the update duration, the ratio, and the sending time to determine the remaining update duration of the domain controller. Determine the average remaining update time for each domain controller based on the remaining update time for all domain controllers. The initial control parameters are adjusted based on the remaining update duration of each domain controller and the offset of the average remaining update duration to obtain the control parameters.

9. A vehicle, characterized in that, The vehicle includes a telematics processor and a memory, the telematics processor being used to execute a domain controller update program for the vehicle stored in the memory, to implement the domain controller update method for the vehicle according to any one of claims 1 to 7.

Images