Vehicle domain controller updating method and device and vehicle

Abstract

The invention relates to a domain controller updating method and device of a vehicle, the vehicle and a remote information processor applied to the vehicle, and the method comprises the steps: for each updating file, compressing a to-be-sent current data packet of the updating file according to a control parameter, and obtaining compressed data; wherein each update file is used for updating a domain controller, and the control parameter is determined according to an update duration or an initial value obtained by the domain controller in response to compressed data corresponding to a previous data packet; and sending the compressed data to the corresponding domain controller based on a control parameter, so that the domain controller performs updating based on the compressed data. Therefore, the updating time of all domain controllers can be balanced while the updating efficiency of each domain controller is improved, so that the overall updating efficiency of the vehicle domain controller is improved, and the user experience is improved.

Description

Technical Field

[0001] The present application relates to the field of vehicle technology, and in particular to a method and device for updating a domain controller of a vehicle, and a vehicle. Background Art

[0002] At present, the continuous improvement of vehicle intelligence and personalization has led to frequent software updates, and the number and amount of data of domain controllers to be updated in the vehicle are constantly increasing, which may include but are not limited to: smart cockpit, autonomous driving, vehicle domain control and other vehicle ECUs (Electronic Control Units). At the same time, there are higher requirements for the flashing speed of OTA (Over-the-Air Technology).

[0003] Currently, the most common OTA vehicle domain controller update process is: the cloud server sends the update file to TBOX (TelematicsBOX, remote information processor), and then TBOX sends the update file to ECU through the gateway, so that the ECU is updated according to the update file.

[0004] However, the above process is subject to the limitation of the data transmission size of the CAN bus, and the ECU performance and FLASH writing speed caused by the ECU architecture are also different. This leads to the situation that some ECUs are upgraded first and the remaining ECUs are not upgraded yet during the vehicle upgrade. As a result, the overall writing efficiency is affected by the local writing efficiency, resulting in low overall update efficiency of the vehicle domain controller, affecting the user experience. Summary of the invention

[0005] The present application provides a method, device and vehicle for updating a domain controller of a vehicle, so as to solve the technical problem in the prior art that the overall flash writing efficiency is affected by the local flash writing efficiency, resulting in low overall update efficiency of the vehicle domain controller and affecting the user experience.

[0006] In a first aspect, the present application provides a method for updating a domain controller of a vehicle, which is applied to a telematics processor of the vehicle, and the method comprises:

[0007] For each update file, compress the current data packet of the update file to be sent according to the control parameter to obtain compressed data; wherein each update file is used to update a domain controller, and the control parameter is 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 parameter, so that the domain controller is updated based on the compressed data.

[0009] As a possible implementation manner, the control parameter includes a compression ratio; the compressed data is obtained by compressing a current data packet of the update file to be sent according to the compression ratio.

[0010] As a possible implementation manner, the control parameter includes a sending frequency; and the compressed data is sent to the corresponding domain controller according to the sending frequency.

[0011] As a possible implementation manner, the control parameter is determined by the following manner, including:

[0012] Acquire current initial control parameters, where the initial control parameters correspond to the previous data packet of the update file;

[0013] Determine the remaining update time of the domain controller according to the update time 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 of the domain controllers based on the remaining update time of all domain controllers;

[0015] The initial control parameter is adjusted according to the remaining update duration of each domain controller and the offset of the average remaining update duration to obtain the control parameter.

[0016] As a possible implementation method, 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 a possible implementation, determining the remaining update time of the domain controller according to the update time 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 data packets remaining to be sent in the update file to the amount of data sent corresponding to the last data packet sent last time;

[0019] Determine the sending time of the last data packet according to the current sending 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 a possible implementation manner, when the initial control parameter includes a compression ratio, adjusting the initial control parameter according to the remaining update duration of each domain controller and the offset of the average remaining update duration to obtain the control parameter includes:

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

[0023] When it is determined that the offset is greater than the first duration threshold, reducing the compression ratio according to a preset first adjustment rule to obtain an adjusted compression ratio;

[0024] When it is determined that the offset is less than the first duration threshold, increasing the compression ratio according to a preset second adjustment rule to obtain an adjusted compression ratio;

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

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

[0027] As a possible implementation manner, when the initial control parameter includes a sending frequency, adjusting the initial control parameter according to the remaining update duration of each domain controller and the offset of the average remaining update duration to obtain the control parameter includes:

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

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

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

[0031] The update duration, the total data volume, the sent data volume, and the target remaining update duration are calculated according to a preset formula to obtain an adjusted sending frequency.

[0032] As a possible implementation, the initial value is determined by the following method:

[0033] Receiving an initial compression ratio sent by a server, wherein the server determines file characteristics of the update file by performing character frequency distribution statistics on the update file, and determines the initial compression ratio according to the file characteristics;

[0034] Determine the initial compression ratio as the initial value;

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

[0036] In the case that the current data packet is the first data packet of the update file, the current data packet is compressed according to the initial value to obtain compressed data.

[0037] In a second aspect, the present application provides a domain controller updating device for a vehicle, which is applied to a telematics processor of the vehicle, and the device comprises:

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

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

[0040] In a third aspect, the present application provides a vehicle comprising a telematics processor and a memory, wherein the telematics processor is used to execute a domain controller update program of the vehicle stored in the memory to implement the domain controller update method of the vehicle described in any one of the first aspects.

[0041] In a fourth aspect, the present application provides a storage medium storing one or more programs, which can be executed by one or more processors to implement the domain controller update method for a vehicle described in any one of the first aspects.

[0042] The technical solution provided by the embodiment of the present application is to compress the current data packet of the update file to be sent according to the control parameter for each update file to obtain compressed data; wherein each update file is used to update a domain controller, and the control parameter is 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 parameter, so that the domain controller is updated based on the compressed data. This technical solution is to compress the current data packet of the update file to be sent according to the control parameter when sending the update file to the domain controller, and send the compressed data after compression, and the control parameter can be 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, that is, after compressing and sending the first data packet of the update file according to the initial value, the control parameter can be adjusted in real time according to the update duration of the data packet by the domain controller, so that the overall duration of the domain controller receiving and writing the update file can be controlled by adjusting the control parameter, so that the writing efficiency of the update file of all domain controllers can be balanced, and the update efficiency of each domain controller is improved while balancing the update duration of all domain controllers, thereby improving the overall update efficiency of the vehicle domain controller and improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0044] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the prior art texts are briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0045] One or more embodiments are exemplarily described by pictures in the corresponding drawings, and these exemplified descriptions do not constitute limitations on the embodiments. Elements with the same reference numerals in the drawings represent similar elements, and unless otherwise stated, the figures in the drawings do not constitute proportional limitations.

[0046] Figure 1 A flowchart of an embodiment of a method for updating a domain controller of a vehicle provided in an embodiment of the present application;

[0047] Figure 2 A flowchart of another method for updating a domain controller of a vehicle provided in an embodiment of the present application;

[0048] Figure 3A flowchart of another embodiment of a method for updating a domain controller of a vehicle provided in an embodiment of the present application;

[0049] Figure 4 A flowchart of an embodiment of a method for updating a domain controller of a vehicle provided in an embodiment of the present application;

[0050] Figure 5 A block diagram of an embodiment of a domain controller updating device for a vehicle provided in an embodiment of the present application;

[0051] Figure 6 A schematic diagram of the structure of a vehicle provided in an embodiment of the present application. DETAILED DESCRIPTION

[0052] In order to make the purpose, technical scheme and advantages of the embodiments of the present application clearer, the technical scheme in the embodiments of the present application will be clearly and completely described in conjunction with the drawings in the embodiments of the present application. Obviously, the embodiments described in the text are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0053] The disclosure below provides many different embodiments or examples to implement different structures of the present invention. In order to simplify the disclosure of the present invention, the parts and settings of specific examples are described below. Of course, they are only examples, and the purpose is not to limit the present invention. In addition, the present invention can repeat reference numbers and / or letters in different examples. This repetition is for the purpose of simplification and clarity, and does not itself indicate the relationship between the various embodiments and / or settings discussed.

[0054] In order to solve the technical problem in the prior art that the overall writing efficiency is affected by the local writing efficiency, resulting in low overall update efficiency of the vehicle domain controller and affecting user experience, the present application provides a vehicle domain controller update method, device and vehicle, which can compress the current data packet of the update file to be sent according to the control parameters when sending the update file to the domain controller, and send the compressed data after compression, and the control parameters can be 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, that is, after compressing and sending the first data packet of the update file according to the initial value, the above-mentioned control parameters can be adjusted in real time according to the update duration of the data packet by the domain controller, so that the overall duration of the domain controller's subsequent reception and writing of the update file can be controlled by adjusting the control parameters, so that the writing efficiency of the update file by all domain controllers can be balanced, and the update efficiency of each domain controller is improved while the update duration of all domain controllers is balanced, thereby improving the overall update efficiency of the vehicle domain controller and improving the user experience.

[0055] The vehicle domain controller update method provided by the present application is further explained below with reference to specific embodiments in conjunction with the accompanying drawings. The embodiments do not constitute a limitation on the embodiments of the present invention.

[0056] See also Figure 1 , is a flow chart of an embodiment of a method for updating a domain controller of a vehicle provided in an embodiment of the present application. As an embodiment, Figure 1 The process shown can be applied to the vehicle's telematics processor. 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 of 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 above update file refers to a file for updating the domain controller of the vehicle, and the domain controller can update itself according to the data in the update file. Each domain controller can correspond to an update file, and different domain controllers can correspond to different update files.

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

[0060]

[0061] Among them, the above C refers to the above compression ratio, and the above S 原 Refers to the original data before compression. The above S 压缩 The compressed data.

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

[0063] The above control parameters may also include a sending frequency, which is used to represent the frequency of sending data packets to the domain controller.

[0064] The above-mentioned data packet refers to a data packet that is pre-split into an 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. The embodiment of the present application does not impose any restrictions on this.

[0065] The above-mentioned update duration refers to the duration that the domain controller takes to update the received compressed data, which may include the total duration corresponding to all operations such as decompressing the compressed data and writing the decompressed data into the flash memory.

[0066] The above-mentioned initial value refers to the value of the initially determined control parameter, which may be the initial value of the compression ratio or the initial value of the sending frequency, and the embodiment of the present application does not impose any limitation on this.

[0067] In actual applications, when updating the domain controller of a vehicle, the update process is that the cloud server sends the update file to TBOX (TelematicsBOX, remote information processor), and then TBOX sends the update file to the domain controller corresponding to the update file through the gateway, and the domain controller updates itself according to the update file.

[0068] Based on this, the execution subject of the embodiment of the present application can be the above-mentioned telematics processor of the vehicle. In the embodiment of the present application, the above-mentioned telematics processor can receive the update file sent by the cloud server, and compress the current data packet of the update file to be sent according to the determined control parameters to obtain compressed data. Among them, the above-mentioned 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 control parameters include a compression ratio, the compression ratio can be determined according to 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 compression ratios or the same compression ratio, which is not limited in the present embodiment.

[0070] As for how the compression ratio is determined according to the update time obtained by the domain controller in response to the compressed data corresponding to the previous data packet, it can be described below. Figure 3 The process shown is explained and will not be described in detail here.

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

[0072] As an implementation manner, the initial value may be a value preset by a user via a visual interface.

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

[0074] As an exemplary implementation, the cloud server can Figure 2 The process shown sends multiple update files and the initial compression ratio corresponding to each update file to the telematics processor. Figure 2 , which is a flow chart of an embodiment of another method for updating a domain controller of a vehicle provided in an embodiment of the present application. Figure 2 The process shown in the figure describes how the cloud server sends multiple update files and the initial compression ratio corresponding to each update file to the telematics processor. Figure 2 As shown, the process may include the following steps:

[0075] Step 201: For each update file to be sent, character frequency distribution statistics are performed on the update file to obtain a statistical result corresponding to the update file.

[0076] Step 202: Determine the file characteristics of the update file according to the statistical results of the update file.

[0077] Step 203: Determine the compression algorithm and compression ratio corresponding to the update file according to the file characteristics.

[0078] The following is a unified description of steps 201 to 203:

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

[0080] Based on this, in order to enable the telematics processor to efficiently transmit each update file to the domain controller, the cloud server may determine an initial compression ratio and compression algorithm for each update file.

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

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

[0083] As an exemplary implementation, when performing character frequency distribution statistics on an update file, information such as the amount of repeated characters and the size of the vocabulary that appears in the update file may be counted.

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

[0085] Optionally, when the file characteristic of the update file is the first file characteristic (which may be a repetitive pattern), the cloud server may determine the first type of compression algorithm and compression ratio as the compression algorithm and compression ratio corresponding to the update file. For example, when the update file is a HEX, S19 or other file, its compression algorithm may be Huffman Coding or Lempel-Ziv-Welch (LZW) algorithm. The above compression algorithms can effectively compress data according to the repetitive pattern, wherein Huffman Coding is suitable for frequently appearing characters, while LZW is suitable for data with repetitive patterns.

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

[0087] Step 204: Send multiple update files, as well as the compression ratio and compression algorithm corresponding to each update file, to the telematics processor.

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

[0089] As an optional implementation, the cloud server may first send multiple update files, as well as the initial compression ratio and compression algorithm corresponding to each update file to the telematics processor.

[0090] As another optional implementation, the cloud server may first send multiple update files to the telematics processor, and then, after determining that the telematics processor has received the multiple update files, send the initial compression ratio and compression algorithm corresponding to each update file to the telematics processor.

[0091] As another optional implementation method, the cloud server may first send multiple update files and the initial compression ratio corresponding to each update file to the remote information processor. Thereafter, after determining that the remote information processor has received the multiple update files and the initial compression ratio of each update file, the compression algorithm of each update file may be sent to the above-mentioned remote information processor.

[0092] As another optional implementation method, the cloud server may first send multiple update files and the compression algorithm corresponding to each update file to the remote information processor. Thereafter, after determining that the remote information processor has received the multiple update files and the compression algorithm for each update file, the cloud server may send the initial compression ratio of each update file to the above-mentioned remote information processor.

[0093] So far, the Figure 2 Description of the process shown.

[0094] Based on the above Figure 2 In the process shown, the telematics processor can receive multiple update files sent by the cloud server, as well as the initial compression ratio and compression algorithm corresponding to each update file. Afterwards, the initial compression ratio corresponding to each update file can be determined as the initial value.

[0095] Based on this, when compressing the current data packet to be sent of 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 value to obtain compressed data.

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

[0097] Step 102: Send the compressed data to a corresponding domain controller based on the control parameters, so that the domain controller is updated based on the compressed data.

[0098] The above control parameter may be a sending frequency, which is used to represent the frequency of sending data packets to the domain controller.

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

[0100] As an optional implementation, when the control parameters include a sending frequency, the sending frequency may be determined according to the update duration obtained by the domain controller in response to the compressed data corresponding to the previous data packet. Different update files may correspond to different sending frequencies, or may correspond to the same sending frequency, which is not limited in the present embodiment.

[0101] As for how the sending frequency is determined according to the update duration obtained by the domain controller in response to the compressed data corresponding to the previous data packet, it can be described below. Figure 3 The process shown is explained and will not be described in detail here.

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

[0103] As an exemplary implementation, the telematics processor may obtain an initial value of the corresponding transmission frequency of each domain controller from a preset storage medium.

[0104] As another exemplary embodiment, the telematics processor may obtain an initial value set for a transmission frequency corresponding to each domain controller from a visualization interface, and store the received initial value and the correspondence between the domain controller and the initial value in a preset storage medium.

[0105] Furthermore, in an embodiment of the present application, the remote information processor compresses the current data packet to be sent for each update file, and after obtaining the compressed data, the compressed data and the compression ratio can be sent to the domain controller corresponding to the update file. The compression ratio can be an initial compression ratio or a compression ratio determined according to 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 the compression ratio, the domain controller can decompress the compressed data according to the compression ratio to obtain the original data, and then perform a flush operation on the original data.

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

[0108] As another optional implementation, when the telematics processor compresses the current data packet according to the compression algorithm corresponding to the update file sent by the remote server, the telematics processor may determine the decompression algorithm corresponding to the compression algorithm before sending the compressed data and the compression ratio to the corresponding domain controller. After that, the serial number of the domain controller corresponding to the update file may be determined, and the decompression algorithm may be sent to the domain controller corresponding to the update file according to the serial number.

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

[0110] Furthermore, the pre-controller may record a first duration consumed for decompressing the compressed data. Afterwards, a flush operation may be performed on the original data, and a second duration consumed for flushing the original data may be recorded. Finally, the domain controller may send the first duration and the second duration to the telematics processor.

[0111] In the embodiment of the present application, after sending the compressed data and the compression ratio to the corresponding domain controller, the telematics processor can obtain the update time of the compressed data by the domain controller.

[0112] As an optional implementation method, it can be seen from the above description that after receiving the compressed data and the compression ratio, the domain controller can decompress and flush the compressed data, record the first time length of the decompression and the second time length of the flush operation, and then send the first time length and the second time length to the remote information processor.

[0113] Based on this, the telematics processor may receive the first duration and the second duration sent by the pre-controller, and add the first duration and the second duration to obtain the update duration of the compressed data by the pre-controller.

[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 according to the update duration obtained by the domain controller in response to the compressed data corresponding to the previous data packet. Therefore, the overall duration of the domain controller's subsequent reception and flashing of update files can be controlled by adjusting the control parameters to balance the flashing 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 update files received for the convenience of storage and create data queues with the same number of files as the above, where each data queue can be used to store a corresponding update file.

[0116] Afterwards, for each update file, the update file and the compression ratio may be stored in a data queue corresponding to the update file.

[0117] Afterwards, after the update duration of the domain controller for the compressed data is obtained, the update duration may be stored in a data queue corresponding to the update file.

[0118] Furthermore, from the above description, it can be seen that the above update duration may include a first duration for decompressing the compressed data and a second duration for flashing the decompressed original data. Therefore, the above first duration and second duration can be stored in the data queue corresponding to the update file.

[0119] The technical solution provided by the embodiment of the present application is to compress the current data packet of the update file to be sent according to the control parameter for each update file to obtain compressed data; wherein each update file is used to update a domain controller, and the control parameter is 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 parameter, so that the domain controller is updated based on the compressed data. This technical solution is to compress the current data packet of the update file to be sent according to the control parameter when sending the update file to the domain controller, and send the compressed data after compression, and the control parameter can be 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, that is, after compressing and sending the first data packet of the update file according to the initial value, the control parameter can be adjusted in real time according to the update duration of the data packet by the domain controller, so that the overall duration of the domain controller receiving and writing the update file can be controlled by adjusting the control parameter, so that the writing efficiency of the update file of all domain controllers can be balanced, and the update efficiency of each domain controller is improved while balancing the update duration of all domain controllers, thereby improving the overall update efficiency of the vehicle domain controller and improving the user experience.

[0120] See also Figure 3 , which is a flow chart of an embodiment of another method for updating a domain controller of a vehicle provided in an embodiment of the present application. Figure 3 The process shown in Figure 1 Based on the process shown in FIG. 1 , the specific method for obtaining the control parameters is described. Figure 3 As shown, the process may include the following steps:

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

[0122] The above-mentioned initial control parameters refer to the control parameters used by the telematics processor when compressing and sending the previous data packet before the current data packet.

[0123] In one embodiment, after applying the control parameters to compress and send the current data packet to be sent, the telematics processor may store the control parameters. Based on this, when processing the latest current data packet, the telematics processor may first obtain the currently stored initial control parameters, adjust the initial control parameters to obtain the adjusted control parameters, and compress and send the latest current data packet according to the control parameters.

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

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

[0126] The following is a unified description of step 302 and step 303:

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

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

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

[0130] pass Figure 1 From the description of the process shown, it can be seen that after receiving the compressed data, the domain controller can decompress and flush the compressed data, record the first duration of the decompression and the second duration of the flush operation, and then send the first duration and the second duration to the telematics processor.

[0131] Based on this, the telematics processor may receive the first duration and the second duration sent by the pre-controller, and add the first duration and the second duration to obtain the update duration of the compressed data by the pre-controller.

[0132] In an embodiment of the present application, after obtaining the update duration of each domain controller, the remote information processor can obtain the number of data packets remaining 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 above update duration and number of data packets.

[0133] As an optional implementation, for each domain controller, the ratio of the total data volume corresponding to the number of data packets remaining to be sent in the update file corresponding to the domain controller and the data volume corresponding to the last data packet sent last time can be determined.

[0134] Afterwards, the sending time of the last data packet can be determined according to the current sending frequency. Specifically, the reciprocal of the sending frequency can be determined as the sending time of the last data packet.

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

[0136] As an implementation method, the remaining update time of the domain controller can be determined by the preset formula shown in the following formula (II):

[0137]

[0138] Among them, the above Ts is the above remaining update time, the above T is the above update time, the above D1 is the above total data volume, the above D2 is the above sent data volume, and the above F is the above sending frequency.

[0139] Based on the determined remaining update time of each domain controller, the remaining update times corresponding to all domain controllers can be added together to obtain the total remaining update time, and the total remaining update time can be divided by the total number of all domain controllers to obtain the average remaining update time of all domain controllers.

[0140] Step 304: According to the remaining update time of each domain controller and the offset of the average remaining update time, the initial control parameter is adjusted to obtain a control parameter.

[0141] The above-mentioned offset refers to the difference between the remaining update duration of each domain controller and the average remaining update duration, which can be obtained by subtracting the average remaining update duration from the remaining update duration of the domain controller. The offset may include positive and negative values. When the offset is a positive value, it indicates that the remaining update duration of the domain controller is greater than the average remaining update duration; when the offset is a negative value, it indicates that the remaining update duration of the domain controller is less than the average remaining update duration.

[0142] In an embodiment of the present 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 compared 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 is possible to determine for each domain controller whether the offset corresponding to the domain controller is greater than a preset first duration threshold. The first duration threshold is a preset threshold, which may be 0 or other values, and the embodiment of the present application does not limit this.

[0144] Optionally, when it is determined that the above offset is greater than the above first duration threshold, it means that the remaining update duration of the domain controller is greater than the average remaining update duration. At this time, 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, in order to reduce the remaining update duration of the domain controller, the above compression ratio can be reduced according to the preset first adjustment rule to obtain the adjusted compression ratio. By reducing the above compression ratio, the compression complexity of the original data can be reduced, thereby reducing the first duration of decompression of the compressed data and increasing the update efficiency of the domain controller. Among them, the above first adjustment rule can be to reduce the compression ratio according to the first preset step size.

[0145] On the contrary, when it is determined that the above offset is less than the above first duration threshold, it means that the remaining update duration of the domain controller is less than the average remaining update duration. At this time, 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 original data. Therefore, the above compression ratio can be increased according to the preset second adjustment rule to obtain the adjusted compression ratio. By increasing the compression ratio, the amount of data transmission can be reduced, thereby improving the data transmission efficiency and achieving the purpose of balancing the remaining update duration of all domain controllers. Among them, the above second adjustment rule can be to increase the above compression ratio according to the second preset step size.

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

[0147] In one embodiment, when the above-mentioned initial control parameters include the sending frequency, when adjusting the initial control parameters, it can be determined whether the above-mentioned offset is greater than a preset second duration threshold. The above-mentioned second duration threshold can be a pre-set duration threshold, which can be 0 or other values. The embodiment of the present application does not impose any restrictions on this.

[0148] Optionally, when the above-mentioned offset is greater than the above-mentioned second duration threshold, it means 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 may adjust the sending frequency of the domain controller, thereby reducing the remaining update time of the domain controller.

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

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

[0151] Afterwards, the total data volume corresponding to the number of data packets remaining to be sent in the corresponding update file of the domain controller and the one-to-one data volume sent for the last data packet sent can be determined, and the update duration, the above-mentioned total data volume, the above-mentioned data volume sent, and the target remaining update duration can be calculated according to the preset formula to obtain the adjusted sending frequency.

[0152] As an exemplary implementation, the above preset formula may be shown as the following formula (III):

[0153]

[0154] Among them, the above T2 is the above target remaining update time, the above T is the above update time, the above D1 is the above total data volume, the above D2 is the above sent data volume, and the above F1 is the adjusted sending frequency.

[0155] On the contrary, when the above-mentioned offset is less than or equal to the above-mentioned 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, which will not reduce the update efficiency of the overall domain controller. Therefore, the corresponding sending frequency of the domain controller does not need to be adjusted, that is, the current sending frequency is determined as the control parameter corresponding to the current data packet.

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

[0157] The technical solution provided by the embodiment of the present application obtains the current initial control parameter, the initial control parameter corresponds to the last data packet of the update file, obtains the update duration of each domain controller and the number of data packets of the corresponding update file remaining to be sent, determines the remaining update duration of the domain controller, determines the average remaining update duration of the domain controller according to the remaining update duration of all domain controllers, and adjusts the initial control parameter according to the remaining update duration of each domain controller and the offset of the above average remaining update duration to obtain the control parameter. This technical solution determines the remaining update duration of each domain controller and the average remaining update duration of all pre-controllers according to the update duration of the last data packet of the domain controller, thereby adjusting the remaining update duration of the domain controller to be close to the average remaining update duration, so that the total update duration of all domain controllers is close to equal, so that the writing efficiency of the update file of all domain controllers can be balanced, and the control parameters of the current data packet can be adjusted accurately and efficiently, so as to improve the update efficiency of each domain controller while balancing the update duration of all domain controllers, improving the overall update efficiency of the vehicle domain controller, and improving the user experience.

[0158] See also Figure 4 , which is a flow chart of an embodiment of another method for updating a domain controller of a vehicle provided in an embodiment of the present application. Figure 5 The process shown in the figure describes the data interaction process between the cloud server, the telematics processor, and the domain controller (ECU). Figure 4 As shown, the process may include the following:

[0159] 1. Cloud server data preparation:

[0160] The server calls the Python program to compress and analyze the HEX, BIN, and S19 file data of the firmware upgrade program used by the ECU, and performs data characteristic statistics on the update file. According to the data characteristics, a group of compression algorithms that can change the compression ratio C and are the most balanced are selected. For files such as HEX and S19, the most commonly used and effective method is to use Huffman Coding or Lempel-Ziv-Welch (LZW) algorithm. These algorithms can effectively compress according to the statistical characteristics of the data. Huffman coding is suitable for frequently appearing characters, while LZW is suitable for data with repeated patterns. For bin files, commonly used compression methods such as ZIP, GZIP, BZIP2 or more efficient algorithms such as LZ4 and Zstandard. They can handle various types of binary data. One ECU upgrade program corresponds to a group of compression and decompression algorithms, and then the compression algorithm, the update file for upgrading the firmware, and the initial compression ratio corresponding to each update file are sent to TBOX.

[0161] 2. TBOX initialization:

[0162] TBOX receives the data sent by the server (including update files and the compression algorithm and compression ratio corresponding to each update file), 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 flash protocol, compression ratio C, and response parameters replied by the ECU. The response parameters include ECU calculation decompression time T1, ECU FLASH writing time T2, parallel transmission frequency F, and remaining flash time T (remain).

[0163] 3. TBOX sends data:

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

[0165] 3. ECU data reception:

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

[0167] 4. TBOX adjusts the sending method:

[0168] TBOX receives the parameters sent back by ECU, calculates the remaining flashing time T(remain), and determines whether the upgrade of each ECU can be maximized to reach T11(remain)≈T12(remain)≈T13(remain)..., where the above T11(remain) is the remaining update time of the first domain controller, the above T12(remain) is the remaining update time of the second domain controller, the above 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 are selected for multi-packet compression and the compression ratio C is increased. By taking advantage of the high performance of the ECU, the sending 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 a preset duration threshold), the compression ratio C can be reduced to relieve the ECU pressure, and the sending frequency F can be dynamically adjusted according to the remaining upgrade time.

[0171] The remaining total time for ECU upgrade in the solution can be determined by 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 duration of the remaining process of ECU upgrade, T 1i Indicates the decompression time of the i-th ECU decompressing the data packet (i.e. Figure 1 The first duration in the process shown), T 2i Indicates the writing time of a data packet of the FLASH of the i-th ECU (i.e. Figure 1 The second duration in the process shown in the figure), D1i represents the total amount of remaining data of the update file corresponding to the i-th ECU (that is, the total amount of data that has not been sent by the update file), D2i represents the total amount of data corresponding to the i-th ECU sent by TBOX at one time (that is, the amount of data sent each time), and Fi represents the initial sending frequency of TBOX for the i-th update file.

[0174] Furthermore, the average remaining update time of ECU upgrade can be determined by the following formula (V):

[0175]

[0176] Where i represents the i-th ECU, n represents the total number of ECUs, Xt represents the average remaining update time of the remaining process of all ECU upgrades, T 1i Indicates the decompression time of the i-th ECU decompressing the data packet (i.e. Figure 1 The first duration in the process shown), T 2i Indicates the writing time of a data packet of the FLASH of the i-th ECU (i.e. Figure 1 The second duration in the process shown in the figure), D1i represents the total amount of remaining data of the update file corresponding to the ith ECU (that is, the total amount of data that has not been sent by the update file), D2i represents the total amount of data corresponding to the ith ECU sent by TBOX at one time (that is, the amount of data sent each time), and Fi represents the initial sending frequency of TBOX for the ith update file.

[0177] 5. Data verification and debugging

[0178] Data integrity verification: After data transfer 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 the embodiment of the present application maximizes the use of the data transmission volume per unit time of the CAN bus by compressing the upgrade data, and coordinates the transmission of data according to the performance computing power and FLSH writing time of each ECU and the number of CPU work tasks. The TBOX receives the decompression time T1 and FLASH writing time T2 sent by the ECU to calculate the incoming compression ratio C and the parallel communication frequency F, so as to determine the data compression degree of the frame data packet and the frequency of parallel transmission data update, thereby improving the parallel upgrade efficiency and greatly reducing the upgrade time of the entire vehicle.

[0180] See also Figure 5 , is a block diagram of an embodiment of a domain controller updating device for a vehicle provided in an embodiment of the present application. As an embodiment, Figure 5 The device shown can be applied to a vehicle's telematics processor. Figure 5 As shown, the device may include:

[0181] A compression module 51 is used to compress the current data packet of the update file to be sent according to the control parameters for each update file 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 the control parameters, so that the domain controller is updated based on the compressed data.

[0183] like Figure 6 As shown, it is a schematic diagram of the structure of a vehicle provided by an embodiment of the present application, including a processor 61, a communication interface 62, a memory 63 and a communication bus 64, wherein the processor 61, the communication interface 62, and the memory 63 communicate with each other through the communication bus 64.

[0184] Memory 63, used for storing computer programs;

[0185] In one embodiment of the present application, the processor 61 is used to execute the program stored in the memory 63 to implement the vehicle domain controller update method provided by any of the above method embodiments, including:

[0186] For each update file, compress the current data packet of the update file to be sent according to the control parameter to obtain compressed data; wherein each update file is used to update a domain controller, and the control parameter is 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 parameter, so that the domain controller is updated based on the compressed data.

[0188] An embodiment of the present application also provides a storage medium having a computer program stored thereon. When the computer program is executed by a processor, the steps of the vehicle domain controller update method provided in any of the aforementioned method embodiments are implemented.

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

[0190] Through the text of the above implementation methods, those skilled in the art can clearly understand that each implementation method can be implemented by means of software plus a general hardware platform, and of course, by hardware. Based on this understanding, the above technical solution is essentially or the part that contributes to the relevant technology can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, a disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or some parts of the embodiment.

[0191] It should be understood that the terms used in the text are only for the purpose of the specific example implementation of the text, and are not intended to be limited. Unless the context clearly indicates otherwise, the singular forms "one", "an" and "said" as used in the text can also be represented to include plural forms. The terms "include", "comprise", "contain", and "have" are inclusive, and therefore specify the existence of the stated features, steps, operations, elements and / or parts, but do not exclude the existence or addition of one or more other features, steps, operations, elements, parts, and / or their combinations. The method steps, processes, and operations of the text in the text are not interpreted as necessarily requiring them to be performed in the specific order of the text or description, unless the execution order is clearly indicated. It should also be understood that additional or alternative steps can be used.

[0192] The foregoing is merely a specific embodiment of the present invention, which enables those skilled in the art to understand or implement the present invention. Various modifications to these embodiments will be 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 present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A method for updating a domain controller of a vehicle, characterized in that: A telematics processor for a vehicle, the method comprising: For each update file, compress the current data packet of the update file to be sent according to the control parameter to obtain compressed data; wherein each update file is used to update a domain controller, and the control parameter is 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 parameter, so that the domain controller is updated based on the compressed data.

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

3. The method according to claim 1, characterized in that The control parameter includes a sending frequency; the compressed data is sent to the corresponding domain controller according to the sending frequency.

4. The method according to claim 1, characterized in that: The control parameters are determined by: Acquire current initial control parameters, where the initial control parameters correspond to the previous data packet of the update file; Determine the remaining update time of the domain controller according to the update time of each domain controller and the number of data packets remaining to be sent in the corresponding update file; Determine the average remaining update time of the domain controllers based on the remaining update time of all domain controllers; The initial control parameter is adjusted according to the remaining update duration of each domain controller and the offset of the average remaining update duration to obtain the control parameter.

5. The method according to claim 4, 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 flush operation based on the decompressed compressed data.

6. The method according to claim 4, characterized in that The determining, according to the update duration of each domain controller and the number of data packets remaining to be sent in the corresponding update file, the remaining update duration of the domain controller comprises: Determine the ratio of the total amount of data corresponding to the number of data packets remaining to be sent in the update file to the amount of data sent corresponding to the last data packet sent last time; Determine the sending time of the last data packet according to the current sending frequency; The product of the update duration, the ratio, and the sending time is determined as the remaining update duration of the domain controller.

7. The method according to claim 4, characterized in that In the case where the initial control parameter includes a compression ratio, adjusting the initial control parameter according to the remaining update duration of each domain controller and the offset of the average remaining update duration to obtain the control parameter includes: Determining whether the offset is greater than a preset first duration threshold; When it is determined that the offset is greater than the first duration threshold, reducing the compression ratio according to a preset first adjustment rule to obtain an adjusted compression ratio; When it is determined that the offset is less than the first duration threshold, increasing the compression ratio according to a preset second adjustment rule to obtain an adjusted compression ratio; The step of compressing the current data packet of the update file to be sent according to the control parameter to obtain compressed data includes: When it is determined that the offset is less than the first duration threshold, two or more current data packets to be sent are compressed simultaneously to obtain compressed data.

8. The method according to claim 4, characterized in that In the case where the initial control parameter includes a sending frequency, adjusting the initial control parameter according to the remaining update duration of each domain controller and the offset of the average remaining update duration to obtain the control parameter includes: Determining whether the offset is greater than a preset second duration threshold; When the offset is greater than the second duration threshold, updating the remaining update duration based on the offset to obtain a target remaining update duration; Determine the total amount of data corresponding to the number of data packets remaining to be sent in the update file, and the amount of sent data corresponding to the last data packet sent last time; The update duration, the total data volume, the sent data volume, and the target remaining update duration are calculated according to a preset formula to obtain an adjusted sending frequency.

9. The method according to claim 1, characterized in that: The initial value is determined by the following method: Receiving an initial compression ratio sent by a server, wherein the server determines file characteristics of the update file by performing character frequency distribution statistics on the update file, and determines the initial compression ratio according to the file characteristics; Determine the initial compression ratio as the initial value; The step of compressing the current data packet of the update file to be sent according to the control parameter to obtain compressed data includes: In the case that the current data packet is the first data packet of the update file, the current data packet is compressed according to the initial value to obtain compressed data.

10. A domain controller updating device for a vehicle, characterized in that: A telematics processor for a vehicle, the device comprising: A compression module, for compressing, for each update file, a current data packet to be sent of the update file according to a control parameter to obtain compressed data; wherein each update file is used to update a domain controller, and the control parameter is determined according to an update duration or an 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 the control parameters, so that the domain controller is updated based on the compressed data.

11. A vehicle, characterized in that: The vehicle comprises a telematics processor and a memory, wherein the telematics processor is used to execute a domain controller update program of the vehicle stored in the memory, so as to implement the domain controller update method of the vehicle according to any one of claims 1 to 9.

Images