A method and system for OTA (Over-The-Air) update testing of vehicles

Abstract

This application discloses an OTA (Over-The-Air) refresh testing method and system for vehicles. The method includes: in each refresh test, for each subprocess, if the refresh test of the subprocess fails, a first stress test is performed on the subprocess, and the error information of this stress test is determined after the failed stress test to perform fault tolerance preprocessing for the subprocess. After the fault tolerance preprocessing is completed, the next stress test is performed on the subprocess until the first stress test of the subprocess is completed, and then the refresh test of the next subprocess begins; if the refresh test of a subprocess is successful, the refresh test of the next subprocess begins directly. This application breaks down the testing process into multiple subprocesses, performs a separate stress test on each subprocess after the refresh test of each subprocess fails, and determines the error information when the stress test fails, providing targeted information for fault tolerance preprocessing, which greatly shortens the testing cycle.

Description

Technical Field

[0001] This application relates to the field of OTA update technology, and more specifically, to an OTA update test method and OTA update test system for vehicles. Background Technology

[0002] OTA (Over-the-Air Technology) update testing technology has been widely applied in the passenger vehicle sector. With the development of intelligent connected vehicle technology, the iterative upgrades of vehicle and its subsystems have become a user demand, and OTA upgrades provide a channel for these upgrades. Through the technical practice of OTA upgrade technology in mass-produced vehicles, market users have been provided with upgrade services such as MP5 theme upgrades and HVAC (Heating, Ventilation and Air Conditioning) controller software quality issues, which have received positive feedback from market users and improved the efficiency of vehicle service in the market.

[0003] However, during the OTA update test, occasional failures occurred when upgrading OTA for vehicles in the market, which placed higher demands on the reliability of OTA testing.

[0004] In traditional vehicle OTA refresh testing methods, the vehicle starts the refresh test after polling the task issued by the vehicle OTA platform. However, this method has problems such as difficulty in accurately locating error nodes and the inability to conduct local OTA stress tests on error nodes. It cannot achieve "testing where the error is", resulting in long testing cycles and a lack of targeted testing. Summary of the Invention

[0005] This application provides an OTA update testing method and system for vehicles. The testing process is divided into multiple sub-processes. After each sub-process fails to update, a separate stress test is performed on that sub-process. The error information is determined each time the stress test fails, providing targeted information for fault tolerance preprocessing. Thus, while ensuring the integrity of OTA testing, the scope of error information determination and fault tolerance preprocessing is narrowed, achieving "testing where the error occurs and fixing where the error occurs", which greatly shortens the testing cycle and ensures the reliability and stability of OTA update testing.

[0006] This application provides a method for testing OTA updates for vehicles. The update process includes multiple independent sub-processes. In each update test, each sub-process is tested once in sequence.

[0007] OTA refresh testing methods include:

[0008] In each refresh test, for each child process, if the refresh test of the child process fails, the first stress test is performed on the child process. After the failed stress test, the error information of this stress test is determined so as to perform fault tolerance preprocessing on the child process. After the fault tolerance preprocessing is completed, the next stress test is performed on the child process until the first stress test of the child process is completed, and then the refresh test of the next child process begins.

[0009] If the refresh test of a certain child process is successful, the refresh test of the next child process will proceed directly.

[0010] Preferably, the error information of the failed stress test is determined after the stress test fails, specifically including:

[0011] The communication data between the platform and the vehicle's remote communication processor and the communication data between the vehicle's remote communication processor and the refreshed controller during this stress test are parsed using message frames. The failure status data is locked and used as the first part of the error message.

[0012] The stage where the failure status data occurred is taken as the error point of this stress test and is included as the second part of the error message.

[0013] Preferably, in each refresh test, the first count for each subprocess is determined by the stress test correction factor, the empirical coefficient, and the first count when the subprocess failed its most recent refresh.

[0014] Preferably, in the OTA refresh test method, the refresh test is performed in rounds, wherein each round includes a preset number of refresh tests;

[0015] After the current round of refresh tests is completed, calculate the success rate of the stress test for each subprocess after the refresh test fails in that round;

[0016] If the success rate of at least one child process in the current round fails to meet the target, the refresh test will proceed to the next round; if the success rate of all child processes in the current round meets the target, the refresh test will end.

[0017] Preferably, for each refresh test after the first round, the first number of times each subprocess performs a refresh test in the first refresh test is determined by the number of stress tests performed when all of the subprocesses failed to refresh in the previous refresh test.

[0018] Preferably, for each refresh test after the first round, the method for determining the first count of each subprocess in the first refresh test is as follows, specifically including:

[0019] Calculate the expected number of times the subprocess performs the second stress test after all refresh failures in the previous refresh test;

[0020] The first refresh test of the subprocess in the current round is calculated based on the expected value, stress test correction factor, and empirical coefficient.

[0021] Preferably, the multiple independent sub-processes include online self-check, test sequence configuration, task release, vehicle-side task polling, vehicle-side task download, and vehicle-side task installation.

[0022] This application also provides an OTA refresh test system for vehicles, wherein the refresh process includes multiple independent sub-processes; in each refresh test, each sub-process is refreshed once in sequence;

[0023] The OTA refresh testing system includes a refresh module and a stress testing module;

[0024] The refresh module is used to perform refresh tests on each subprocess;

[0025] The stress testing module is used to perform the first stress test on a child process after the refresh test fails. After the failed stress test, the error information of the stress test is determined so as to perform fault tolerance preprocessing on the child process. After the fault tolerance preprocessing is completed, the next stress test is performed on the child process until the first stress test on the child process is completed.

[0026] Preferably, the OTA refresh test system further includes a test equipment monitoring module, which is used to monitor the communication data between test equipment;

[0027] The stress test module includes an error detection module. The error detection module is used to parse the message frames of the communication data between the platform and the vehicle's remote communication processor and the communication data between the vehicle's remote communication processor and the refreshed controller during this stress test, lock the failure status data as the first part of the error information, and take the link where the failure status data is located as the error point of this stress test, and take the error point as the second part of the error information.

[0028] Preferably, the stress test module further includes a count calculation module, which is used to determine the first count of the subprocess in the current refresh test by using the stress test correction factor, the empirical coefficient, and the first count when each subprocess failed the most recent refresh.

[0029] Preferably, the OTA refresh testing system further includes a test effect monitoring module, which monitors the refresh test effect in rounds, each round including a preset number of refresh tests. After the refresh test of the current round is completed, the test effect monitoring module calculates the success rate of the stress test after each subprocess fails to refresh in the round; and outputs the monitoring result for entering the next round of refresh test when the success rate of at least one subprocess in the current round is not up to standard, and outputs the monitoring result for the end of refresh test when the success rates of all subprocesses in the current round are up to standard.

[0030] Preferably, the count calculation module is used to determine the first count of the subprocess in the first refresh test of the current round by the number of stress tests performed by each subprocess when all refreshes failed in the previous round of refresh test.

[0031] Preferably, the number of calculation modules includes an expected value calculation module and a correction module;

[0032] The expected value calculation module is used to calculate the expected value of the second stress test performed by this subprocess after all refresh failures in the previous round of refresh test;

[0033] The correction module is used to calculate the first refresh test count of the subprocess in the current round based on the expected value, stress test correction factor, and empirical coefficient.

[0034] Preferably, the multiple independent sub-processes include online self-check, test sequence configuration, task release, vehicle-side task polling, vehicle-side task download, and vehicle-side task installation.

[0035] Other features and advantages of this application will become clear from the following detailed description of exemplary embodiments with reference to the accompanying drawings. Attached Figure Description

[0036] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments of the present application and, together with their description, serve to explain the principles of the present application.

[0037] Figure 1 A flowchart of a refresh test provided for this application;

[0038] Figure 2 A flowchart for stress testing of child processes provided in this application;

[0039] Figure 3 The format of the communication data provided in this application;

[0040] Figure 4 A flowchart of a preferred embodiment of the OTA update testing method for vehicles provided in this application;

[0041] Figure 5A structural diagram of the OTA update test system for the vehicle provided in this application. Detailed Implementation

[0042] Various exemplary embodiments of the present application will now be described in detail with reference to the accompanying drawings. It should be noted that, unless otherwise specifically stated, the relative arrangement, numerical expressions, and values ​​of the components and steps set forth in these embodiments do not limit the scope of the present application.

[0043] The following description of at least one exemplary embodiment is merely illustrative and is in no way intended to limit the scope of this application and its application or use.

[0044] Techniques, methods, and equipment known to those skilled in the art may not be discussed in detail, but where appropriate, they should be considered part of the specification.

[0045] In all the examples shown and discussed herein, any specific values ​​should be interpreted as merely exemplary and not as limitations. Therefore, other examples of exemplary embodiments may have different values.

[0046] This application provides an OTA (Over-The-Air) refresh testing method and system for vehicles. The testing process is divided into multiple sub-processes. After each sub-process fails, a separate stress test is performed on that sub-process. Error information is identified upon each stress test failure, providing targeted information for fault tolerance preprocessing. This ensures the integrity of the OTA test while narrowing the scope of error information identification and fault tolerance preprocessing, achieving "testing where the error occurs and fixing where the error occurs," significantly shortening the testing cycle while ensuring the reliability and stability of the OTA refresh test. Furthermore, when identifying error information, frame structure parsing is performed on the communication data of the failed stress test process to initially lock down the failure state data, improving the efficiency of vulnerability repair and further shortening the testing cycle. Moreover, the number of stress tests for each sub-process in each refresh test is determined based on the number of previous stress tests for that sub-process, ensuring the sufficiency of the test sample and providing important data for subsequent experiments. Based on this, the sub-processes of this application include online self-test, test sequence configuration, task release, vehicle-side task polling, vehicle-side task download, and vehicle-side task installation. This splitting method is universal and can be split into these six sub-processes, whether it is OTA parts, bench flashing, or real vehicle flashing. Therefore, this technology has strong compatibility and can flexibly adapt to various testing needs.

[0047] It should be noted that in this application, the refresh process includes multiple independent sub-processes; in each refresh test, a refresh test is performed on each sub-process in turn.

[0048] As one example, multiple independent sub-processes include online self-check, test sequence configuration, task publishing, vehicle-side task polling, vehicle-side task download, and vehicle-side task installation.

[0049] In this application, the OTA platform includes a lower-level machine for performing refresh tests and an upper-level machine for managing the refresh tests. The lower-level machine tests the test equipment and sends the relevant test data to the upper-level machine. The upper-level machine outputs a test report to the user, enabling the user to perform fault-tolerant preprocessing and other operations. The test report includes the stress test results for each subprocess (including logs when the stress test is successful and error messages when the stress test fails), the overall results of each refresh test, and the overall results of each round of refresh tests. These will be further explained in conjunction with the following content.

[0050] The OTA update test method for vehicles provided in this application first determines the test conditions and initialization of the entire vehicle.

[0051] The testing conditions for the whole vehicle include:

[0052] 1. Define a test condition that the vehicle must meet before a refresh test can be performed.

[0053] As an example, the test condition was an open environment with the vehicle stationary.

[0054] Understandably, other test conditions can also be selected according to requirements.

[0055] 2. Set the vehicle test parameters, including: the number of refresh tests in each round of refresh testing (i.e., the subsequent preset number of times) P, and the stress test correction factor. The empirical coefficient N′, the truncation ΔT, and the test objective are used. The test objective represents the target success rate of each subprocess in each round of the refresh test under stress. Understandably, the target success rates of different subprocesses can be the same or different.

[0056] 3. Determine the child process monitor S ki ={PASS,Failed},i≤P-1,i∈Z + ,1≤k≤6,k∈Z + Among them, S 1i ~S 6i These represent the online self-check, test sequence configuration, task deployment, vehicle-side task polling, vehicle-side task download, and vehicle-side task installation in the i-th refresh test, respectively. Where S... ki =PASS indicates that the refresh test of the k-th child process in the i-th refresh test of the current round is successful, and the process can proceed to the next child process S. (k+1)i Refresh test; S ki=Failed indicates that the refresh test of the k-th child process failed in the i-th refresh test of the current round, and then the stress test of that child process is entered.

[0057] 4. Set pressure parameters for the vessel. in θ represents the set of stress test counts for all child processes in the i-th refresh test. ki θ represents the number of stress tests performed on the k-th child process during the i-th refresh test. 1i ~θ 6i These represent the number of stress tests performed during the i-th refresh test, including online self-check, test sequence configuration, task deployment, vehicle-side task polling, vehicle-side task download, and vehicle-side task installation.

[0058] 5. Set the load test cutoff T kij =[t s +ΔT,t e +ΔT], where j≤θ k ,j∈Z + Pressure test cutoff T kij t represents the time period during the j-th stress test of the k-th subprocess in the i-th refresh test. s and t e This indicates the start and end times of this stress test.

[0059] As an example, the OTA refresh test method for vehicles in this application only performs one refresh test, that is, each subprocess performs one refresh test.

[0060] In this embodiment, during initialization, i = 0, k = 1. θ 01 ,θ 02 ,...,θ 06 This indicates the number of stress tests performed on each subprocess during the first refresh test of the entire OTA refresh test. This number can be preset manually or calculated based on big data.

[0061] In each refresh test, for each child process, if the refresh test of that child process fails (i.e., S... ki =Failed), then the first stress test is performed on the child process. If the refresh test of a child process is successful (i.e., S...), the stress test is performed on the child process. ki If the result is PASS, then proceed directly to the refresh test of the next child process.

[0062] Specifically, such as Figure 1 As shown, each refresh test includes:

[0063] S1010: Perform a refresh test on the S1 online self-test;

[0064] S1020: Determine whether the refresh test of S1 was successful. If yes, proceed to S1030; otherwise, proceed to S1130.

[0065] S1030: Refresh the S2 test sequence configuration;

[0066] S1040: Determine whether the refresh test of S2 was successful. If yes, proceed to S1050; otherwise, proceed to S1140.

[0067] S1050: Refresh test of S3 task deployment;

[0068] S1060: Determine whether the refresh test of S3 was successful. If yes, proceed to S1070; otherwise, proceed to S1150.

[0069] S1070: Refresh test of S4 vehicle-side task polling;

[0070] S1080: Determine whether the refresh test of S4 was successful. If yes, proceed to S1090; otherwise, proceed to S1160.

[0071] S1090: Refresh test of S5 vehicle-side task download;

[0072] S1100: Determine whether the refresh test of S5 was successful. If yes, execute S1110; otherwise, execute S1170.

[0073] S1110: Refresh test of S6 vehicle-side task installation;

[0074] S1120: Determine whether the refresh test in S6 was successful. If yes, the refresh test ends; otherwise, proceed to S1180.

[0075] S1130: Perform a stress test on S1. Then execute S1030.

[0076] S1140: Perform a stress test on S2. Then execute S1050.

[0077] S1150: Perform a stress test on S3. Then execute S1070.

[0078] S1160: Perform a stress test on S4. Then execute S1090.

[0079] S1170: Perform a stress test on S5. Then execute S1110.

[0080] S1180: Perform stress testing on S6. The refresh test then ends.

[0081] When performing a stress test on a subprocess, first calculate the number of times the stress test is performed, which is taken as the first count θ. ki Then, the stress test begins. After a failed stress test, the error message is identified to perform fault-tolerant preprocessing on the child process. After the fault-tolerant preprocessing is complete, the next stress test is performed on the child process until the first θ is completed. ki After the stress test, the process proceeds to the refresh test of the next subprocess.

[0082] As an example, in each refresh test, the first refresh count θ of each subprocess is... ki Stress test correction factor The empirical coefficient N′ and the first number θ when the most recent refresh failure of the subprocess occurred. kl (l < i) Determine:

[0083]

[0084] The number of stress tests for each subprocess varies as the test progresses, ensuring the sufficiency of the test sample and providing important evidence for subsequent experiments.

[0085] Specifically, such as Figure 2 As shown, stress tests are performed on each child process, including:

[0086] S210: Initialize j = 1.

[0087] S220: Perform the j-th stress test on the child process.

[0088] S230: Determine whether the j-th stress test was successful. If yes, proceed to S240; otherwise, proceed to S250.

[0089] S240: Record this stress test log (including stress test truncation T) kij Upload the data to the host computer of the OTA platform and determine whether j = θ. ki If yes, then terminate the stress test of the subprocess; otherwise, execute S270.

[0090] Since S4 to S6 are performed on the vehicle, the logs of these three sub-processes are first uploaded to the vehicle's T-box, and then uploaded from the T-box to the host computer of the OTA platform.

[0091] S270: Let j = j + 1. Then return to S220.

[0092] S250: Determine the error information from this stress test and upload it to the host computer of the OTA platform. The host computer will then output the error information and perform fault-tolerant preprocessing on the subprocess. It should be noted that fault-tolerant preprocessing can be done manually or automatically.

[0093] As an example, after a failed stress test, the error information for that stress test is determined, specifically including:

[0094] S2501: Message frames are parsed for the communication data between the platform and the vehicle's remote communication processor and the communication data between the vehicle's remote communication processor and the refreshed controller during this stress test. The failure status data is locked and used as the first part of the error message.

[0095] The lower-level machine is equipped with a test equipment monitoring module, which is used to monitor communication data and other data between test equipment. The test equipment includes an OTA platform (specifically a host computer), a vehicle's remote communication processor (such as a T-box), and controllers installed on the vehicle.

[0096] Communication between the OTA platform and the vehicle (platform-T-box) and communication between the vehicle's remote communication processor and the updated controller (T-box-controller) are transmitted via byte streams.

[0097] As an example, the communication protocols between the OTA platform and the vehicle (platform-T-box) and between the vehicle's remote communication processor and the controller being updated (T-box-controller) are shown in the table below:

[0098] Table 1 Communication Protocol Table

[0099]

[0100] like Figure 3 As shown in the above embodiment of the communication protocol, the communication data includes four parts: Frame_Type, Msg_Type, Msg_Data, and CRC.

[0101] Among them, Frame_Type determines whether the message originates from "Platform-T-box" or "T-box-controller". r01 indicates that the message comes from "Platform-T-box", r02 indicates that the message comes from "T-box-controller", and r03 indicates that the message has an error.

[0102] Msg_Type determines whether the message type indicates successful or failed command transmission. r01 indicates successful command transmission, r02 indicates failed command transmission, and r03 indicates an error in the command transmission.

[0103] Msg_Data is the flush data stream, and its final length is determined by the message type.

[0104] There are two possible scenarios for Msg_Data:

[0105] (1) When Frame_Type is “Platform-T-box”, Msg_Data includes two parts: Arrival_Times and Error_Type. Arrival_Times indicates the number of times “Platform-T-box” communication data is transmitted, and Error_Type indicates the error type of “Platform-T-box” communication data.

[0106] (2) When Frame_Type is “T-box-controller”, Msg_Data includes four parts: Up_State1, Up_State2, Arrival_Times and Error_Type. Up_State1 indicates that the software upgrade was successful; Up_State2 indicates that the software upgrade failed; Arrival_Times indicates the number of times the communication data of “T-box-controller” was transmitted; and Error_Type indicates the error type of the communication data of “T-box-controller”.

[0107] CRC is a check bit used to verify whether data packets in the "Platform-T-box-ECU" communication are corrupted.

[0108] Therefore, by identifying the message source, message type, and flush data stream in the communication data, failure status data can be obtained, and the message and error type of the flush failure can be identified.

[0109] S2502: The stage where the failure status data is located is taken as the error point of this stress test and is used as the second part of the error message.

[0110] It contains error information including failure status data and error points, which can be used for targeted repair with a minimal scope during fault tolerance preprocessing, improving repair efficiency and thus increasing the speed of stress testing and refresh testing.

[0111] S260: Determine whether fault-tolerant preprocessing is complete. If yes, execute S240; otherwise, return to S260.

[0112] Based on the above, preferably, the OTA refresh test method performs refresh tests in rounds, with each round including a preset number P of refresh tests. The test objective should be achieved at the end of the test.

[0113] In other words, after each round of refresh testing, the success rate of the stress test for each subprocess after a refresh test failure in that round is calculated. If the success rate of at least one subprocess in the current round fails to meet the target, the next round of refresh testing begins; if the success rate of all subprocesses in the current round meets the target, the overall OTA refresh test ends.

[0114] The success rate of stress testing after each subprocess fails to refresh in this round can be the average or arithmetic mean of the success rates of stress testing after each failure of refresh in this round for that subprocess.

[0115] Specifically, such as Figure 4 As shown, in this preferred embodiment, the OTA refresh test method includes:

[0116] S410: Initialize the number of rounds L = 1.

[0117] S420: Execute the Lth round of refresh test, wherein the number of refresh tests in the Lth round of refresh test is a preset number P, and the process of each refresh test is described above.

[0118] S430: Calculate the success rate of the stress test for each subprocess in the Lth round of refresh test, and determine whether the Lth round of refresh test has achieved the test objective. If yes, end the entire OTA refresh test for the vehicle; otherwise, execute S440.

[0119] S440: Let L = L + 1. Return to S420.

[0120] In this embodiment, for each refresh test after the first round, the first count of each subprocess in the first refresh test is determined by the number of stress tests performed when all of that subprocess failed to refresh in the previous refresh test. For the first refresh test, the first counts of S1 to S6 in the first refresh test are θ respectively. 01 ,θ 02 ,θ 03 ,θ 04 ,θ 05 ,θ 06 Please see the above explanation.

[0121] As an example, for each refresh test after the first round, the method for determining the first count of each subprocess in the first refresh test is as follows:

[0122] P1: Calculate the expected value N of the second stress test performed by this subprocess after all refresh failures in the previous refresh test round. False :

[0123]

[0124] Where n represents the number of refresh failures of this subprocess in the previous refresh test, N′ False 1. N′ False 2. N′ Falsen These represent the second stress test performed by the subprocess after the first, second, and nth refresh failures in the previous refresh test, respectively.

[0125] P2: Based on the expected value N False Stress test correction factor And the empirical coefficient N′ calculates the first refresh test θ of the subprocess in the current round. ki :

[0126]

[0127] Where δ represents the desired parameter or stress test parameter.

[0128] Based on the above, this application also provides an OTA (Over-The-Air) update testing system for vehicles. For example... Figure 5 As shown, the OTA refresh test system includes a refresh module 510 and a stress test module 520.

[0129] The refresh module 510 is used to perform refresh tests on each subprocess.

[0130] The stress testing module 520 is used to perform the first stress test on a subprocess after the refresh test of a subprocess fails. After the failed stress test, the error information of this stress test is determined so as to perform fault tolerance preprocessing on the subprocess. After the fault tolerance preprocessing is completed, the next stress test on the subprocess is performed until the first stress test on the subprocess is completed.

[0131] Preferably, the OTA refresh test system further includes a test equipment monitoring module 530, which is used to monitor the communication data between test equipment.

[0132] The stress test module 520 includes an error-finding module 5201. The error-finding module 5201 parses message frames of the communication data between the platform and the vehicle's remote communication processor, and between the vehicle's remote communication processor and the refreshed controller during this stress test. It then identifies the failure status data as the first part of the error information. The stage in which the failure status data occurs is then identified as the error point in this stress test, and this error point is considered the second part of the error information.

[0133] Preferably, the stress test module 520 further includes a count calculation module 5202, which is used to determine the first count of the subprocess in the current refresh test by using the stress test correction factor, the empirical coefficient, and the first count when each subprocess failed the most recent refresh.

[0134] Preferably, the OTA refresh testing system further includes a test effect monitoring module 540. The test effect monitoring module 540 monitors the refresh test effect in rounds, where each round includes a preset number of refresh tests. After the current round of refresh testing is completed, the test effect monitoring module 540 calculates the success rate of the stress test for each sub-process after a refresh test failure in that round; and outputs the monitoring result for proceeding to the next round of refresh testing when the success rate of at least one sub-process in the current round fails to meet the target, and outputs the monitoring result for the end of the refresh test when the success rates of all sub-processes in the current round meet the target.

[0135] Preferably, the count calculation module 5202 is used to determine the first count of the subprocess in the first refresh test of the current round by the number of stress tests performed by each subprocess when all refreshes failed in the previous round of refresh test.

[0136] Preferably, the number of times calculation module 5202 includes an expected value calculation module 52021 and a correction module 52022.

[0137] The expected value calculation module 52021 is used to calculate the expected value of the second stress test performed by the subprocess after all refresh failures in the previous round of refresh test.

[0138] The correction module 52022 is used to calculate the first refresh test count of the subprocess in the current round based on the expected value, stress test correction factor and empirical coefficient.

[0139] While specific embodiments of this application have been described in detail by way of examples, those skilled in the art should understand that the above examples are for illustrative purposes only and are not intended to limit the scope of this application. Those skilled in the art should understand that modifications can be made to the above embodiments without departing from the scope and spirit of this application. The scope of this application is defined by the appended claims.

Claims

1. A method for testing OTA (Over-The-Air) updates for vehicles, characterized in that, The refresh process involves multiple independent sub-processes; In each refresh test, a refresh test is performed once for each child process in sequence; The OTA refresh test method includes: In each refresh test, for each child process, if the refresh test of the child process fails, the first stress test is performed on the child process. After the failed stress test, the error information of this stress test is determined so as to perform fault tolerance preprocessing on the child process. After the fault tolerance preprocessing is completed, the next stress test is performed on the child process until the first stress test of the child process is completed, and then the refresh test of the next child process begins. In the OTA refresh test method, refresh tests are performed in rounds. Each round includes a preset number of refresh tests. For each refresh test after the first round, the first number of each subprocess in the first refresh test is determined by the number of stress tests performed when all of the subprocesses failed to refresh in the previous refresh test. Furthermore, in each refresh test, the first count of each child process... Stress test correction factor Empirical coefficient And the first number of times the child process failed to refresh most recently. (l < i) Determine: ； If the refresh test of a certain child process is successful, the refresh test of the next child process will proceed directly.

2. The OTA update test method for vehicles according to claim 1, characterized in that, After a failed stress test, identify the error message for that stress test, specifically including: The communication data between the platform and the vehicle's remote communication processor and the communication data between the vehicle's remote communication processor and the refreshed controller during this stress test are parsed using message frames. The failure status data is locked and used as the first part of the error information. The stage in which the failure status data occurred is taken as the error point of this stress test, and is considered as the second part of the error information.

3. The OTA update test method for vehicles according to claim 1, characterized in that, After the current round of refresh tests is completed, calculate the success rate of the stress test for each subprocess after the refresh test fails in that round; If the success rate of at least one child process in the current round fails to meet the target, the refresh test will proceed to the next round; if the success rate of all child processes in the current round meets the target, the refresh test will end.

4. The OTA update test method for vehicles according to claim 1, characterized in that, The multiple independent sub-processes include online self-check, test sequence configuration, task release, vehicle-side task polling, vehicle-side task download, and vehicle-side task installation.

5. An OTA update testing system for vehicles, characterized in that, The refresh process involves multiple independent sub-processes; in each refresh test, a refresh test is performed on each sub-process in turn. The OTA refresh test system includes a refresh module and a stress test module; The refresh module is used to perform refresh tests on each subprocess; The stress testing module is used to perform the first stress test on a subprocess after the refresh test of a subprocess fails, and to determine the error information of the stress test after the failed stress test in order to perform fault tolerance preprocessing on the subprocess. After the fault tolerance preprocessing is completed, the next stress test on the subprocess is performed until the first stress test on the subprocess is completed. In each refresh test, the first refresh count of each subprocess is... Stress test correction factor Empirical coefficient And the first number of times the child process failed to refresh most recently. (l < i) Determine: 。 6. The vehicle OTA update testing system according to claim 5, characterized in that, The OTA refresh test system also includes a test equipment monitoring module, which is used to monitor the communication data between test equipment. The stress test module includes an error detection module, which is used to parse message frames of the communication data between the platform and the vehicle's remote communication processor and the communication data between the vehicle's remote communication processor and the refreshed controller during this stress test, and lock the failure status data as the first part of the error information. The stage in which the failure status data occurred is taken as the error point of this stress test, and the error point is taken as the second part of the error information.

7. The vehicle OTA update testing system according to claim 5, characterized in that, The OTA refresh test system also includes a test effect monitoring module, which is used to monitor the refresh test effect in rounds, wherein each round includes a preset number of refresh tests; After the current round of refresh testing is completed, the test effect monitoring module calculates the success rate of the stress test for each subprocess after the refresh test fails in that round. If the success rate of at least one subprocess in the current round fails to meet the target, the monitoring result for entering the next round of refresh test will be output. If the success rate of all subprocesses in the current round meets the target, the monitoring result for the end of refresh test will be output.

8. The vehicle OTA update testing system according to claim 7, characterized in that, The stress testing module also includes a count calculation module, which is used to determine the first count of the subprocess in the first refresh test of the current round by the number of stress tests performed by each subprocess when all refreshes failed in the previous round of refresh test.

9. The vehicle OTA update testing system according to claim 5, characterized in that, The multiple independent sub-processes include online self-check, test sequence configuration, task release, vehicle-side task polling, vehicle-side task download, and vehicle-side task installation.

Images