A whole vehicle OTA upgrading progress display method

Abstract

The application provides a whole vehicle OTA upgrading progress display method, comprising: obtaining the upgrading configuration time of each ECU to be upgraded based on the OTA cloud, determining the cumulative upgrading time of all ECUs to be upgraded; adding the cumulative upgrading time to the upgrading task information, and issuing the upgrading task information to the vehicle end; after the vehicle end obtains the upgrading task information, uniformly displaying the ECU upgrading progress of the current vehicle based on the cumulative upgrading time; uploading the upgrading feedback data to the OTA cloud after the upgrading is completed at the vehicle end, and correcting the upgrading configuration time based on the upgrading feedback data. The OTA cloud of the application issues the upgrading time based on dynamic differential upgrading, which realizes the progress display suitable for whole package upgrading and the smooth jump of the whole vehicle upgrading progress suitable for differential upgrading.

Description

Technical Field

[0001] This invention relates to the field of display technology, and in particular to a method for displaying the progress of over-the-air (OTA) upgrades for a whole vehicle. Background Technology

[0002] Over-the-air (OTA) updates are increasingly becoming standard equipment in automobiles. With technological advancements, cars are equipped with an increasing number of ECUs (Electronic Control Units). A single OTA update often requires upgrading multiple ECUs, including CAN units and intelligent units (ECUs with intelligent operating systems are generally called intelligent ECUs). CAN units typically use UDS flashing, while intelligent units generally use self-upgrades. Different upgrade methods, such as differential upgrades and full package upgrades, can occur, and the time required varies depending on the upgrade method and firmware version. Furthermore, there is a possibility of communication breakdown between the ECU and the OTA component during the upgrade process, preventing the ECU from reporting upgrade progress. Accurately displaying the remaining upgrade time and smoothly showing the upgrade progress during a full vehicle OTA update is a challenge. Existing ECU upgrade progress displays typically rely on a fixed upgrade package size, but this method only applies to full package upgrades. For differential upgrades, since upgrade time is not linearly related to upgrade package size, the above method cannot accurately display the upgrade progress. Summary of the Invention

[0003] This invention provides a method for displaying the progress of over-the-air (OTA) upgrades for the entire vehicle. The TA cloud distributes upgrade times based on dynamic and differentiated upgrades, achieving a smooth display of the progress of both full-package upgrades and differential upgrades.

[0004] This invention provides a method for displaying the progress of a vehicle OTA upgrade, comprising:

[0005] The upgrade configuration time of each ECU to be upgraded is obtained from the OTA cloud, and the cumulative upgrade time of all ECUs to be upgraded is determined.

[0006] Add the cumulative upgrade time to the upgrade task information and send the upgrade task information to the vehicle terminal;

[0007] After the vehicle obtains the upgrade task information, it displays the current ECU upgrade progress evenly based on the cumulative upgrade time.

[0008] After the vehicle-side upgrade is completed, upgrade feedback data is uploaded to the OTA cloud, and the upgrade configuration time is corrected based on the upgrade feedback data.

[0009] Preferably, in a method for displaying the progress of a vehicle OTA upgrade, the upgrade configuration time of each ECU is obtained from the OTA cloud, and the cumulative upgrade time of all ECUs to be upgraded is determined, including:

[0010] Obtain the list of ECUs to be upgraded for the current vehicle, and determine the upgrade version and corresponding upgrade type for each ECU;

[0011] Based on the upgraded version and its corresponding upgrade type, and referring to the preset time comparison table, the upgrade configuration time for each ECU to be upgraded is obtained respectively;

[0012] The total upgrade time is obtained by summing up the upgrade configuration times of all ECUs to be upgraded.

[0013] Preferably, a method for displaying the progress of a vehicle OTA upgrade further includes:

[0014] Acquire a large amount of vehicle upgrade information, and classify the vehicle upgrade information based on the upgrade type to obtain full package upgrade sets and differential upgrade sets;

[0015] Based on different upgrade sets, the upgrade versions corresponding to different ECUs of different vehicles are determined, and the upgrade time from the original version to the upgraded version is determined. The upgrade time is taken as the first time. The original version and the upgrade version number are not necessarily adjacent.

[0016] Based on the original version information, the full package upgrade set and the differential upgrade set are further classified to obtain multiple first upgrade subsets;

[0017] The duplicate version data in each of the first upgrade subsets are deduplicated to obtain the second upgrade subset. Based on the second upgrade subset, the second time when the original version is upgraded to any upgradable version is obtained.

[0018] Based on the second time and upgrade type classification results, a preset time comparison table is generated.

[0019] Preferably, in a method for displaying the progress of a vehicle OTA upgrade, duplicate version data in each first upgrade subset are deduplicated to obtain a second upgrade subset. Based on the second upgrade subset, a second time for upgrading from the original version to any upgradable version is obtained, including:

[0020] Get the upgrade version corresponding to the original version in any first upgrade subset, and determine whether there are multiple first times for the same upgrade version in the same first upgrade subset;

[0021] If it exists, the weighted average of the multiple first times is used to obtain the average time, and the deduplication process is completed to obtain the second upgrade subset. The average time is then used as the second time of the upgrade version.

[0022] If it exists, the first upgrade subset is directly used as the second upgrade subset, and the first time corresponding to the upgrade version is used as the second time.

[0023] Preferably, in a method for displaying the progress of a vehicle OTA upgrade, after the vehicle obtains the upgrade task information, the current ECU upgrade progress is displayed evenly based on the cumulative upgrade time, including:

[0024] The vehicle analyzes the upgrade task information to obtain the current vehicle's cumulative upgrade time;

[0025] The upgrade progress bar is assigned a value based on the cumulative upgrade time, and the actual size of the upgrade progress bar is obtained.

[0026] Determine the time scale of the upgrade progress bar based on the actual size and cumulative upgrade time;

[0027] The progress display unit controls the upgrade progress bar to display in a uniform jump based on the time scale.

[0028] Preferably, in a method for displaying the progress of a vehicle OTA upgrade, the process of displaying the upgrade progress bar includes:

[0029] A virtual progress bar is generated synchronously, and an upgrade switching node is generated by marking the actual upgrade progress of the ECU to be upgraded on the virtual progress bar.

[0030] Based on the upgrade switching node, determine the first actual upgrade time and the second actual upgrade time recorded by the virtual progress bar for each ECU that has completed the upgrade;

[0031] The first and second actual upgrade times are used as upgrade feedback data, and a feedback data packet is generated.

[0032] Preferably, in a method for displaying the progress of a vehicle OTA upgrade, after the upgrade is completed on the vehicle side, upgrade feedback data is uploaded to the OTA cloud, and the upgrade configuration time is corrected based on the upgrade feedback data, including:

[0033] After the vehicle-side upgrade is completed, the feedback data packet will be uploaded to the OTA cloud.

[0034] The OTA cloud parses the feedback data packets to obtain the first actual upgrade time and the second actual upgrade time, and compares the second actual upgrade time with the cumulative upgrade time.

[0035] When the second actual upgrade time is the same as the cumulative upgrade time, the cumulative upgrade time is determined to be correct.

[0036] Otherwise, if the cumulative upgrade time is found to be inaccurate, the upgrade configuration time of the ECU to be upgraded is compared with its corresponding first actual upgrade time to obtain the error ECU and its corresponding actual upgrade time.

[0037] Based on the actual upgrade time, the upgrade configuration time of the error ECU corresponding to the preset time comparison table is routinely corrected.

[0038] Preferably, in a method for displaying the progress of a vehicle OTA upgrade, an upgrade switching node is generated by marking the actual upgrade progress of the ECU to be upgraded on a virtual progress bar, including:

[0039] The upgrade status of each ECU to be upgraded is monitored in real time to determine whether the upgrade process of the current ECU to be upgraded is normal. If the upgrade of the current ECU to be upgraded fails, the upgrade switching node corresponding to the current ECU to be upgraded is highlighted.

[0040] Among them, the first actual upgrade time corresponding to the highlighted mark cannot be used as the basis for correcting the error ECU;

[0041] If the upgrade of the ECU to be upgraded proceeds normally, continue monitoring the upgrade status of the ECU to be upgraded.

[0042] Preferably, in a method for displaying the progress of a vehicle OTA upgrade, the number of errors by the faulty ECU is statistically analyzed, error-prone ECUs are identified based on the statistical results, and these error-prone ECUs are then given priority for correction, including:

[0043] The OTA cloud generates a special statistical table based on the ECU storage list, and triggers the counter in the special statistical table every time feedback data is received from the vehicle.

[0044] According to the statistical table, all ECUs are checked for errors in turn to determine the position of the erroneous ECU in the statistical table and to determine whether the error of the erroneous ECU is due to upgrade failure. If so, the error of the next erroneous ECU is then checked.

[0045] If not, update the error count of the error ECU based on the counter, and after the update is completed, obtain the error count results of all ECUs;

[0046] Based on the error counting results and the preset algorithm, the error factor corresponding to each ECU is determined. When the error factor corresponding to the ECU is greater than or equal to the first preset value, the ECU is determined to be an error-prone ECU. Multiple error upgrade configuration times corresponding to the error-prone ECU and their corresponding historical actual upgrade times are obtained. Based on multiple historical actual upgrade times, the average upgrade time and the time error amplitude value corresponding to the actual upgrade time are obtained.

[0047] When the time error amplitude value is greater than the second preset value, the vehicle type corresponding to each error of the error-prone ECU is obtained, and the vehicles are clustered based on the similarity of the historical actual upgrade time to obtain multiple vehicle classification sets.

[0048] Multiple upgrade influencing factors are calculated based on the actual upgrade time and average upgrade time corresponding to each vehicle category set. These multiple upgrade influencing factors and their corresponding vehicle types are added as multi-data configuration labels to the error-prone ECUs in the preset time lookup table. At the same time, the average upgrade time is used as the correction time to correct the time corresponding to the error-prone ECUs in the preset time lookup table.

[0049] When the time error amplitude is less than or equal to the second preset value, the average upgrade time will be used as the correction time for the error-prone ECU to be corrected according to the corresponding time in the preset time reference table;

[0050] When the error factors corresponding to the ECU are all less than the first preset value and the error ECUs included in the upgrade feedback data include the ECU, the ECU is routinely corrected.

[0051] Preferably, in a method for displaying the progress of a vehicle OTA upgrade, the upgrade configuration time for each ECU to be upgraded is obtained from the OTA cloud, and further includes:

[0052] When the ECU to be upgraded has multiple data configuration tags in the preset time lookup table, it is necessary to obtain the vehicle type of the current vehicle and determine the target upgrade impact factor corresponding to the ECU to be upgraded based on the vehicle type.

[0053] Based on the target upgrade impact factor, the upgrade configuration time of the ECU to be upgraded displayed in the preset time comparison table is corrected to obtain the final upgrade configuration time of the ECU to be upgraded.

[0054] Compared with the prior art, the present invention has at least the following beneficial effects:

[0055] This invention obtains the upgrade configuration time of each ECU to be upgraded from the OTA cloud, determines the cumulative upgrade time of all ECUs to be upgraded, adds the cumulative upgrade time to the upgrade task information, and sends the upgrade task information to the vehicle. After the vehicle receives the upgrade task information, it displays the current vehicle's ECU upgrade progress evenly based on the cumulative upgrade time. The OTA cloud sends upgrade times based on dynamic differential upgrades, achieving a smooth jump in the progress display applicable to both full package upgrades and differential upgrades. After the vehicle upgrade is completed, it uploads upgrade feedback data to the OTA cloud, corrects the upgrade configuration time based on the upgrade feedback data, and performs data statistics based on the actual upgrade times of the ECUs reported by all vehicles, correcting the preset upgrade time in the cloud database. The more vehicles upgraded, the more objective the corrected data, and the more accurate the upgrade progress displayed for subsequent vehicles.

[0056] Other features and advantages of the invention will be set forth in the description which follows, and will be apparent in part from the description, or may be learned by practicing the invention. The objects and other advantages of the invention may be realized and obtained by means of the structures particularly pointed out in the written description, claims, and drawings.

[0057] The technical solution of the present invention will be further described in detail below with reference to the accompanying drawings and embodiments. Attached Figure Description

[0058] The accompanying drawings are provided to further illustrate the invention and form part of the specification. They are used in conjunction with embodiments of the invention to explain the invention and do not constitute a limitation thereof. In the drawings:

[0059] Figure 1 This is a flowchart illustrating the progress display method for over-the-air (OTA) upgrades of a vehicle according to the present invention.

[0060] Figure 2 This is a flowchart of step 1 of the method for displaying the progress of a vehicle OTA upgrade according to the present invention;

[0061] Figure 3 This is a flowchart of step 2 of the method for displaying the progress of a vehicle OTA upgrade according to the present invention;

[0062] Figure 4 This is a flowchart of step 4 of the method for displaying the progress of a vehicle OTA upgrade according to the present invention. Detailed Implementation

[0063] The preferred embodiments of the present invention will be described below with reference to the accompanying drawings. It should be understood that the preferred embodiments described herein are for illustration and explanation only and are not intended to limit the present invention.

[0064] Example 1:

[0065] A method for displaying the progress of a vehicle OTA upgrade, such as... Figure 1 As shown, it includes:

[0066] Step 1: Obtain the upgrade configuration time of each ECU to be upgraded from the OTA cloud, and determine the cumulative upgrade time of all ECUs to be upgraded;

[0067] Step 2: Add the cumulative upgrade time to the upgrade task information and send the upgrade task information to the vehicle terminal;

[0068] Step 3: After obtaining the upgrade task information from the vehicle, the ECU upgrade progress of the current vehicle is displayed evenly based on the cumulative upgrade time;

[0069] Step 4: After the vehicle upgrade is completed, upload the upgrade feedback data to the OTA cloud and correct the upgrade configuration time based on the upgrade feedback data.

[0070] In this embodiment, the upgrade configuration time refers to the time required for the upgrade of each ECU.

[0071] In this embodiment, the cumulative upgrade time refers to the sum of all upgrade configuration times.

[0072] In this embodiment, upgrade feedback data refers to the time data required for the actual upgrade of the vehicle.

[0073] In this embodiment, ECU (Electronic Control Unit) refers to an electronic control unit.

[0074] The beneficial effects of the above technical solution are as follows: This invention obtains the upgrade configuration time of each ECU to be upgraded based on OTA cloud, and determines the cumulative upgrade time of all ECUs to be upgraded; the cumulative upgrade time is added to the upgrade task information, and the upgrade task information is sent to the vehicle; after the vehicle obtains the upgrade task information, it displays the ECU upgrade progress of the current vehicle evenly based on the cumulative upgrade time. The OTA cloud sends the upgrade time based on dynamic differential upgrade, realizing a smooth jump in the upgrade progress that is applicable to both full package upgrades and differential upgrades. After the upgrade is completed on the vehicle, upgrade feedback data is uploaded to the OTA cloud, and the upgrade configuration time is corrected based on the upgrade feedback data. The cloud performs data statistics based on the actual upgrade time of the ECUs reported by all vehicles, and corrects the preset upgrade time in the cloud database. The more vehicles are upgraded, the more objective the corrected data becomes, and the more accurate the upgrade progress displayed for subsequent vehicles becomes.

[0075] Example 2:

[0076] Based on Example 1, Step 1: Obtain the upgrade configuration time of each ECU from the OTA cloud, and determine the cumulative upgrade time of all ECUs to be upgraded, including:

[0077] Step 101: Obtain the list of ECUs to be upgraded for the current vehicle, and determine the upgrade version and corresponding upgrade type for each ECU to be upgraded;

[0078] Step 102: Based on the upgraded version and its corresponding upgrade type, refer to the preset time comparison table to obtain the upgrade configuration time for each ECU to be upgraded;

[0079] Step 103: Add up the upgrade configuration times of all ECUs to be upgraded to obtain the total upgrade time.

[0080] In this embodiment, the upgraded version refers to the version that the ECU to be upgraded to.

[0081] In this embodiment, the upgrade types include full package upgrade and differential upgrade.

[0082] In this embodiment, the preset time reference table refers to an upgrade time table pre-configured in the OTA cloud, which can be obtained through experimental testing or based on historical upgrade data.

[0083] The beneficial effects of the above technical solution are as follows: This invention obtains a list of ECUs to be upgraded in the current vehicle, determines the upgrade version and corresponding upgrade type of each ECU, and simultaneously obtains the upgrade type and upgrade version, which is conducive to quickly and accurately obtaining the target upgrade configuration time; based on the upgrade version and its corresponding upgrade type, and referring to a preset time comparison table, the upgrade configuration time of each ECU to be upgraded is obtained respectively, and the upgrade configuration times of all ECUs to be upgraded are accumulated to obtain the cumulative upgrade time, which quickly completes the vehicle upgrade time, improves the efficiency of upgrade progress display calculation, shortens the waiting time for sending upgrade task information, and improves the efficiency of vehicle upgrade task confirmation response.

[0084] Example 3:

[0085] Based on Example 2, a method for displaying the progress of a vehicle OTA upgrade further includes:

[0086] Acquire a large amount of vehicle upgrade information, and classify the vehicle upgrade information based on the upgrade type to obtain full package upgrade sets and differential upgrade sets;

[0087] Based on different upgrade sets, the upgrade versions corresponding to different ECUs of different vehicles are determined, and the upgrade time from the original version to the upgraded version is determined. The upgrade time is taken as the first time. The original version and the upgrade version number are not necessarily adjacent.

[0088] Based on the original version information, the full package upgrade set and the differential upgrade set are further classified to obtain multiple first upgrade subsets;

[0089] The duplicate version data in each of the first upgrade subsets are deduplicated to obtain the second upgrade subset. Based on the second upgrade subset, the second time when the original version is upgraded to any upgradable version is obtained.

[0090] Based on the second time and upgrade type classification results, a preset time comparison table is generated.

[0091] In this embodiment, the full package upgrade set refers to the data set formed by using vehicle upgrade information from the full package upgrade; the differential upgrade set refers to the data set formed by using vehicle upgrade information from the differential upgrade.

[0092] In this embodiment, the upgrade set includes a full package upgrade set and a differential upgrade set.

[0093] In this embodiment, the first time refers to the time taken for the vehicle to upgrade from the original version to the upgraded version, as indicated by the vehicle upgrade information.

[0094] In this embodiment, refined classification refers to classifying vehicle upgrade information in the full package upgrade set and the differential upgrade set based on the original version, with the same original vehicle upgrade information in a first upgrade subset.

[0095] In this embodiment, the second upgrade subset refers to the first upgrade subset after deduplication, and duplicate version data refers to data in the first upgrade subset where the original version and the upgrade version are the same.

[0096] In this embodiment, the second time refers to the time when a vehicle in the second upgrade subset is upgraded from the original version to any upgradable version.

[0097] The beneficial effects of the above technical solution are as follows: This invention acquires a large amount of vehicle upgrade information, classifies the vehicle upgrade information based on upgrade type to obtain a full package upgrade set and a differential upgrade set, and obtains data for different upgrade types. This allows the obtained preset time reference table to satisfy different upgrade types while ensuring the accuracy of upgrade time calculation as much as possible. Based on different upgrade sets, the upgrade version corresponding to different ECUs of different vehicles is determined, and the upgrade time from the original version to the upgraded version is determined. This upgrade time is used as the first time, where the original version and upgrade version number are not necessarily adjacent. Based on the original version information, the full package upgrade set and the differential upgrade set are further classified to obtain multiple first upgrade subsets. Duplicate version data in each first upgrade subset are deduplicated to obtain a second upgrade subset. Based on the second upgrade subset, the second time to upgrade from the original version to any upgradable version is obtained. Based on the second time and the upgrade type classification results, a preset time reference table is generated, generating an upgrade time calculation reference table that satisfies both full package upgrades and differential upgrades, thereby improving the efficiency of upgrade time calculation.

[0098] Example 4:

[0099] Based on Example 3, duplicate version data in each of the first upgrade subsets are deduplicated to obtain a second upgrade subset. Based on the second upgrade subset, the second time for upgrading the original version to any upgradable version is obtained, including:

[0100] Get the upgrade version corresponding to the original version in any first upgrade subset, and determine whether there are multiple first times for the same upgrade version in the same first upgrade subset;

[0101] If it exists, the weighted average of the multiple first times is used to obtain the average time, and the deduplication process is completed to obtain the second upgrade subset. The average time is then used as the second time of the upgrade version.

[0102] If it exists, the first upgrade subset is directly used as the second upgrade subset, and the first time corresponding to the upgrade version is used as the second time.

[0103] The beneficial effects of the above technical solution are as follows: Based on the upgraded version, the present invention performs deduplication processing on the first upgrade subset to obtain the second upgrade set, ensuring that there is only one reference time for the same upgrade process in the same upgrade type, thus ensuring the uniqueness of the reference time in the preset time lookup table and avoiding multiple upgrade configuration times for the same upgrade process, which would interfere with the cumulative upgrade time calculation process.

[0104] Example 5:

[0105] Based on Example 1, step 2: After the vehicle obtains the upgrade task information, it displays the current vehicle's ECU upgrade progress evenly based on the cumulative upgrade time, including:

[0106] Step 201: The vehicle parses the upgrade task information to obtain the current vehicle's cumulative upgrade time;

[0107] Step 202: Assign values ​​to the upgrade progress bar based on the cumulative upgrade time, and obtain the actual size of the upgrade progress bar;

[0108] Step 203: Determine the time scale of the upgrade progress bar based on the actual dimensions and cumulative upgrade time;

[0109] Step 204: The progress display unit controls the upgrade progress bar to display in a uniform jump based on the time scale.

[0110] In this embodiment, the time scale refers to the time length represented by each unit length of the upgrade progress bar.

[0111] In this embodiment, assigning a value refers to determining the actual duration corresponding to the upgrade progress bar. The upgrade progress bar is fixed to a fixed length.

[0112] The beneficial effects of the above technical solution are as follows: The present invention assigns a value to the upgrade progress bar based on the cumulative upgrade time and obtains the actual size of the upgrade progress bar, thereby determining the actual duration corresponding to the upgrade progress bar; based on the actual size and the cumulative upgrade time, the time scale of the upgrade progress bar is determined, providing a basis for selecting the jump speed of the upgrade progress bar; the progress display unit controls the upgrade progress bar to jump evenly based on the time scale, thereby realizing a smooth display of the vehicle upgrade progress.

[0113] Example 6:

[0114] Based on Example 1, the process of displaying the upgrade progress bar includes:

[0115] A virtual progress bar is generated synchronously, and an upgrade switching node is generated by marking the actual upgrade progress of the ECU to be upgraded on the virtual progress bar.

[0116] Based on the upgrade switching node, determine the first actual upgrade time and the second actual upgrade time recorded by the virtual progress bar for each ECU that has completed the upgrade;

[0117] The first and second actual upgrade times are used as upgrade feedback data, and a feedback data packet is generated.

[0118] In this embodiment, the virtual progress bar refers to a progress bar that is automatically generated by the vehicle during the upgrade process but is not displayed. The running program generated by the virtual progress bar is sent to the vehicle along with the upgrade task information, and the running program is automatically deleted after the vehicle upgrade is completed.

[0119] In this embodiment, the upgrade switching node refers to the node where the upgrade of one ECU is completed and the upgrade of the next ECU begins. The switching node of the first ECU to begin upgrading is the upgrade start node.

[0120] In this embodiment, the first actual upgrade time refers to the total time spent on the vehicle ECU upgrade as represented by the virtual upgrade progress bar.

[0121] In this embodiment, the second actual upgrade time refers to the actual time required for the upgrade of each ECU on the virtual upgrade progress bar.

[0122] In this embodiment, the feedback data packet refers to the data packet generated by packaging upgrade feedback data.

[0123] The beneficial effects of the above technical solution are as follows: While performing the upgrade on the vehicle, the present invention simultaneously generates a virtual progress bar and marks the actual upgrade progress of the ECU to be upgraded on the virtual progress bar, generates upgrade switching nodes, records the upgrade time of each ECU, and determines the first actual upgrade time and the second actual upgrade time recorded by the virtual progress bar based on the upgrade switching nodes. The first and second actual upgrade times are used as upgrade feedback data, and a feedback data packet is generated, which provides a basis for the continuous correction of the preset time reference table and helps to improve the accuracy of the upgrade progress display described in this application through continuous use.

[0124] Example 7:

[0125] Based on Example 1, step 4: After the vehicle-side upgrade is completed, upload the upgrade feedback data to the OTA cloud, and correct the upgrade configuration time based on the upgrade feedback data, including:

[0126] Step 401: After the vehicle-side upgrade is completed, upload the feedback data packet to the OTA cloud.

[0127] Step 402: The OTA cloud parses the feedback data packet to obtain the first actual upgrade time and the second actual upgrade time, and compares the second actual upgrade time with the cumulative upgrade time;

[0128] When the second actual upgrade time is the same as the cumulative upgrade time, the cumulative upgrade time is determined to be correct.

[0129] Otherwise, if the cumulative upgrade time is found to be inaccurate, the upgrade configuration time of the ECU to be upgraded is compared with its corresponding first actual upgrade time to obtain the error ECU and its corresponding actual upgrade time.

[0130] Based on the actual upgrade time, the upgrade configuration time of the error ECU corresponding to the version in the preset time comparison table is routinely corrected.

[0131] In this embodiment, the error ECU refers to the ECU to be upgraded whose upgrade configuration time is different from the first actual time.

[0132] In this embodiment, conventional correction refers to replacing the erroneous data in the preset time lookup table with the actual upgrade time corresponding to the error ECU.

[0133] The beneficial effects of the above technical solution are as follows: After the vehicle-side upgrade is completed, the present invention evaluates the current vehicle upgrade progress display based on the upgrade feedback data in the feedback data packet. When there is a deviation in the cumulative upgrade time corresponding to the progress display, the data in the preset time reference table in the OTA cloud is corrected based on the upgrade feedback data, thereby improving the accuracy of each upgrade configuration time in the preset time reference table, improving the objectivity of the cumulative upgrade time, and preparing for the next OTA upgrade.

[0134] Example 8:

[0135] Based on Example 7, an upgrade switching node is generated by marking the actual upgrade progress of the ECU to be upgraded on the virtual progress bar, including:

[0136] The upgrade status of each ECU to be upgraded is monitored in real time to determine whether the upgrade process of the current ECU to be upgraded is normal. If the upgrade of the current ECU to be upgraded fails, the upgrade switching node corresponding to the current ECU to be upgraded is highlighted.

[0137] Among them, the first actual upgrade time corresponding to the highlighted mark cannot be used as the basis for correcting the error ECU;

[0138] If the upgrade of the ECU to be upgraded proceeds normally, continue monitoring the upgrade status of the ECU to be upgraded.

[0139] The beneficial effects of the above technical solution are as follows: This invention monitors the upgrade status of each ECU to be upgraded in real time, determines whether the upgrade process of the current ECU to be upgraded is normal, and if the upgrade of the current ECU to be upgraded fails, the upgrade switching node corresponding to the current ECU to be upgraded is highlighted, and it is stipulated that the first actual upgrade time corresponding to the highlighted mark cannot be used as the correction basis for the error ECU. This avoids errors in the upgrade time caused by the abnormal upgrade of the ECU to be upgraded, which would lead to the actual upgrade time being different from the progress display. In this case, the abnormal upgrade ECU to be upgraded is erroneously corrected, which effectively improves the accuracy of each upgrade configuration time in the preset time comparison table and improves the scientific nature of the data.

[0140] Example 9:

[0141] Based on Example 8, the number of errors of the error ECUs is statistically analyzed. Error-prone ECUs are identified based on the statistical results, and these ECUs are then targeted for correction, including:

[0142] The OTA cloud generates a special statistical table based on the ECU storage list, and triggers the counter in the special statistical table every time feedback data is received from the vehicle.

[0143] According to the statistical table, all ECUs are checked for errors in turn to determine the position of the erroneous ECU in the statistical table and to determine whether the error of the erroneous ECU is due to upgrade failure. If so, the error of the next erroneous ECU is then checked.

[0144] If not, update the error count of the error ECU based on the counter, and after the update is completed, obtain the error count results of all ECUs;

[0145] Based on the error counting results and the preset algorithm, the error factor corresponding to each ECU is determined. When the error factor corresponding to the ECU is greater than or equal to the first preset value, the ECU is determined to be an error-prone ECU. Multiple error upgrade configuration times corresponding to the error-prone ECU and their corresponding historical actual upgrade times are obtained. Based on multiple historical actual upgrade times, the average upgrade time and the time error amplitude value corresponding to the actual upgrade time are obtained.

[0146] When the time error amplitude value is greater than the second preset value, the vehicle type corresponding to each error of the error-prone ECU is obtained, and the vehicles are clustered based on the similarity of the historical actual upgrade time to obtain multiple vehicle classification sets.

[0147] Multiple upgrade influencing factors are calculated based on the actual upgrade time and average upgrade time corresponding to each vehicle category set. These multiple upgrade influencing factors and their corresponding vehicle types are added as multi-data configuration labels to the error-prone ECUs in the preset time lookup table. At the same time, the average upgrade time is used as the correction time to correct the time corresponding to the error-prone ECUs in the preset time lookup table.

[0148] When the time error amplitude is less than or equal to the second preset value, the average upgrade time will be used as the correction time for the error-prone ECU to be corrected according to the corresponding time in the preset time reference table;

[0149] When the error factors corresponding to the ECU are all less than the first preset value and the error ECUs included in the upgrade feedback data include the ECU, the ECU is routinely corrected.

[0150] In this embodiment, the dedicated statistics table refers to a table in the OTA cloud specifically used to count the number of errors that occur during the configuration upgrade of each ECU. After the error-prone ECU is corrected, the count of the error-prone ECU in the dedicated statistics table is reset to zero, and a new counting cycle begins.

[0151] In this embodiment, the reasons for the error include both upgrade failure and non-upgrade failure.

[0152] In this embodiment, the error factor is an indicator used to evaluate the degree of error of each ECU in the statistical table. The larger the error factor, the less accurate the upgrade configuration time of the ECU.

[0153] In this embodiment, an error-prone ECU refers to an ECU with an error factor greater than or equal to a first preset value.

[0154] In this embodiment, the error upgrade configuration time refers to the upgrade configuration time that participates in the cumulative upgrade time each time the error-prone ECU experiences an error; the historical actual upgrade time refers to the actual upgrade time corresponding to each time the error-prone ECU experiences an error.

[0155] In this embodiment, the average upgrade time refers to the average of multiple historical actual upgrade times.

[0156] In this embodiment, there is a time difference between each error upgrade configuration time and its corresponding historical actual upgrade time. The range of the time difference between all error upgrade configuration times and their corresponding historical actual upgrade times is the time error amplitude value.

[0157] In this embodiment, vehicle clustering refers to vehicles with similar historical upgrade times forming a vehicle classification set.

[0158] In this embodiment, the upgrade hardware varies due to different vehicle types, and the upgrade impact factor is used to characterize the actual impact of the differences on the OAT upgrade.

[0159] In this embodiment, a multi-data configuration label refers to a label containing multiple types of data.

[0160] The beneficial effects of the above technical solution are as follows: The OTA cloud-based system generates a dedicated statistical table based on the ECU storage list to count the number of errors occurring during each ECU upgrade. It stipulates that upgrade failures are not included in the statistical table, ensuring the accuracy of data correction and reducing the possibility of increased upgrade configuration time errors due to incorrect corrections. Based on the error counting results and a preset algorithm, the error factor corresponding to each ECU is determined, identifying whether each ECU is a fault-prone ECU and thus determining the correction strategy, which is beneficial to the accuracy of correction. Furthermore, based on the time error amplitude corresponding to the actual upgrade time of fault-prone ECUs, it determines whether the impact of vehicle hardware on the upgrade needs to be considered, improving the depth of fault-prone ECU correction, comprehensively considering the impact of vehicle hardware, minimizing the error amplitude, improving the accuracy of upgrade configuration time, and enhancing the accuracy of OTA upgrade display.

[0161] Example 10:

[0162] Based on Example 9, the upgrade configuration time of each ECU to be upgraded is obtained from the OTA cloud, and the method further includes:

[0163] When the ECU to be upgraded has multiple data configuration tags in the preset time lookup table, it is necessary to obtain the vehicle type of the current vehicle and determine the target upgrade impact factor corresponding to the ECU to be upgraded based on the vehicle type.

[0164] Based on the target upgrade impact factor, the upgrade configuration time of the ECU to be upgraded displayed in the preset time comparison table is corrected to obtain the final upgrade configuration time of the ECU to be upgraded.

[0165] The beneficial effects of the above technical solution are as follows: When the ECU to be upgraded has multiple data configuration tags in the preset time lookup table, the present invention needs to obtain the vehicle type of the current vehicle and determine the target upgrade influence factor corresponding to the ECU to be upgraded based on the vehicle type; the upgrade configuration time of the ECU to be upgraded displayed in the preset time lookup table is corrected based on the target upgrade influence factor to obtain the final upgrade configuration time of the ECU to be upgraded, taking into account the upgrade time error caused by vehicle hardware, and improving the accuracy of the cumulative upgrade time calculation as much as possible.

[0166] Obviously, those skilled in the art can make various modifications and variations to this invention without departing from its spirit and scope. Therefore, if these modifications and variations fall within the scope of the claims of this invention and their equivalents, this invention also intends to include these modifications and variations.

Claims

1. A method for displaying the progress of a vehicle OTA upgrade, characterized in that, include: The upgrade configuration time of each ECU to be upgraded is obtained from the OTA cloud, and the cumulative upgrade time of all ECUs to be upgraded is determined. Add the cumulative upgrade time to the upgrade task information and send the upgrade task information to the vehicle terminal; After the vehicle obtains the upgrade task information, it displays the current ECU upgrade progress evenly based on the cumulative upgrade time. After the vehicle-side upgrade is completed, the upgrade feedback data is uploaded to the OTA cloud, and the upgrade configuration time is corrected based on the upgrade feedback data; The process of displaying the upgrade progress bar includes: A virtual progress bar is generated synchronously, and an upgrade switching node is generated by marking the actual upgrade progress of the ECU to be upgraded on the virtual progress bar. Based on the upgrade switching node, determine the first actual upgrade time and the second actual upgrade time recorded by the virtual progress bar for each ECU that has completed the upgrade; The first and second actual upgrade times are used as upgrade feedback data, and a feedback data packet is generated. After the vehicle-side upgrade is completed, upgrade feedback data is uploaded to the OTA cloud, and the upgrade configuration time is corrected based on the upgrade feedback data, including: After the vehicle-side upgrade is completed, the feedback data packet will be uploaded to the OTA cloud. The OTA cloud parses the feedback data packets to obtain the first actual upgrade time and the second actual upgrade time, and compares the second actual upgrade time with the cumulative upgrade time. When the second actual upgrade time is the same as the cumulative upgrade time, the cumulative upgrade time is determined to be correct. Otherwise, if the cumulative upgrade time is found to be inaccurate, the upgrade configuration time of the ECU to be upgraded is compared with its corresponding first actual upgrade time to obtain the error ECU and its corresponding actual upgrade time. Based on the actual upgrade time, the upgrade configuration time of the error ECU corresponding to the version in the preset time comparison table is routinely corrected. The number of errors by the error ECUs is statistically analyzed. Based on the statistical results, error-prone ECUs are identified and prioritized for correction, including: The OTA cloud generates a special statistical table based on the ECU storage list, and triggers the counter in the special statistical table every time feedback data is received from the vehicle. According to the statistical table, all ECUs are checked for errors in turn to determine the position of the erroneous ECU in the statistical table and to determine whether the error of the erroneous ECU is due to upgrade failure. If so, the error of the next erroneous ECU is then checked. If not, update the error count of the error ECU based on the counter, and after the update is completed, obtain the error count results of all ECUs; Based on the error counting results and the preset algorithm, the error factor corresponding to each ECU is determined. When the error factor corresponding to the ECU is greater than or equal to the first preset value, the ECU is determined to be an error-prone ECU. Multiple error upgrade configuration times corresponding to the error-prone ECU and their corresponding historical actual upgrade times are obtained. Based on multiple historical actual upgrade times, the average upgrade time and the time error amplitude value corresponding to the actual upgrade time are obtained. When the time error amplitude value is greater than the second preset value, the vehicle type corresponding to each error of the error-prone ECU is obtained, and the vehicles are clustered based on the similarity of the historical actual upgrade time to obtain multiple vehicle classification sets. Multiple upgrade influencing factors are calculated based on the actual upgrade time and average upgrade time corresponding to each vehicle category set. These multiple upgrade influencing factors and their corresponding vehicle types are added as multi-data configuration labels to the error-prone ECUs in the preset time lookup table. At the same time, the average upgrade time is used as the correction time to correct the time corresponding to the error-prone ECUs in the preset time lookup table. When the time error amplitude is less than or equal to the second preset value, the average upgrade time will be used as the correction time for the error-prone ECU to be corrected according to the corresponding time in the preset time reference table; When the error factors corresponding to the ECU are all less than the first preset value and the error ECUs included in the upgrade feedback data include the ECU, the ECU is subject to routine correction. The upgrade configuration time for each ECU to be upgraded is obtained via OTA cloud sync, and also includes: When the ECU to be upgraded has multiple data configuration tags in the preset time lookup table, it is necessary to obtain the vehicle type of the current vehicle and determine the target upgrade impact factor corresponding to the ECU to be upgraded based on the vehicle type. Based on the target upgrade impact factor, the upgrade configuration time of the ECU to be upgraded displayed in the preset time comparison table is corrected to obtain the final upgrade configuration time of the ECU to be upgraded.

2. The method for displaying the progress of a vehicle OTA upgrade according to claim 1, characterized in that, Based on the OTA cloud acquisition of the upgrade configuration time of each ECU, the cumulative upgrade time of all ECUs to be upgraded is determined, including: Obtain the list of ECUs to be upgraded for the current vehicle, and determine the upgrade version and corresponding upgrade type for each ECU; Based on the upgraded version and its corresponding upgrade type, and referring to the preset time comparison table, the upgrade configuration time for each ECU to be upgraded is obtained respectively; The total upgrade time is obtained by summing up the upgrade configuration times of all ECUs to be upgraded.

3. The method for displaying the progress of a vehicle OTA upgrade according to claim 2, characterized in that, Also includes: Acquire a large amount of vehicle upgrade information, and classify the vehicle upgrade information based on the upgrade type to obtain full package upgrade sets and differential upgrade sets; Based on different upgrade sets, the upgrade versions corresponding to different ECUs of different vehicles are determined, and the upgrade time from the original version to the upgraded version is determined. The upgrade time is taken as the first time. The original version and the upgrade version number are not necessarily adjacent. Based on the original version information, the full package upgrade set and the differential upgrade set are further classified to obtain multiple first upgrade subsets; The duplicate version data in each of the first upgrade subsets are deduplicated to obtain the second upgrade subset. Based on the second upgrade subset, the second time when the original version is upgraded to any upgradable version is obtained. Based on the second time and upgrade type classification results, a preset time comparison table is generated.

4. The method for displaying the progress of a vehicle OTA upgrade according to claim 3, characterized in that, Each first upgrade subset is deduplicated to obtain a second upgrade subset. Based on the second upgrade subset, the second time for upgrading the original version to any upgradable version is obtained, including: Get the upgrade version corresponding to the original version in any first upgrade subset, and determine whether there are multiple first times for the same upgrade version in the same first upgrade subset; If it exists, the weighted average of the multiple first times is used to obtain the average time, and the deduplication process is completed to obtain the second upgrade subset. The average time is then used as the second time of the upgrade version. If it exists, the first upgrade subset is directly used as the second upgrade subset, and the first time corresponding to the upgrade version is used as the second time.

5. The method for displaying the progress of a vehicle OTA upgrade according to claim 1, characterized in that, After the vehicle receives the upgrade task information, it displays the current ECU upgrade progress evenly based on the cumulative upgrade time, including: The vehicle analyzes the upgrade task information to obtain the current vehicle's cumulative upgrade time; The upgrade progress bar is assigned a value based on the cumulative upgrade time, and the actual size of the upgrade progress bar is obtained. Determine the time scale of the upgrade progress bar based on the actual size and cumulative upgrade time; The progress display unit controls the upgrade progress bar to display in a uniform jump based on the time scale.

6. The method for displaying the progress of a vehicle OTA upgrade according to claim 1, characterized in that, Based on the actual upgrade progress of the ECU to be upgraded, mark it on the virtual progress bar to generate upgrade switch nodes, including: The upgrade status of each ECU to be upgraded is monitored in real time to determine whether the upgrade process of the current ECU to be upgraded is normal. If the upgrade of the current ECU to be upgraded fails, the upgrade switching node corresponding to the current ECU to be upgraded is highlighted. Among them, the first actual upgrade time corresponding to the highlighted mark cannot be used as the basis for correcting the error ECU; If the upgrade of the ECU to be upgraded proceeds normally, continue monitoring the upgrade status of the ECU to be upgraded.

Images