OTA upgrade method and device

Abstract

The present invention provides an OTA upgrade method and device, relating to the technical field of automotive software upgrades. The method comprises: testing the target software to be upgraded and obtaining test results; obtaining an upgrade package for the target software based on the test results; determining the functional type of the target software based on the upgrade package; and determining a corresponding upgrade method based on the functional type of the target software to perform an OTA upgrade on the target software. This solution can reduce the number of testers, conserve test vehicle resources, shorten the testing cycle, and thereby accelerate the software release cycle, improving software availability and reliability.

Description

Technical Field

[0001] The present invention relates to the technical field of automobile software upgrades, and in particular to an OTA upgrade method and device. Background Art

[0002] As smart devices and smart cars communicate and interact, the integration and version updates of multiple data sources in the connected vehicle (IoV) have become challenges that automakers and relevant standards departments need to address. It is crucial to comprehensively consider how to use advanced Over-the-Air (OTA) technology to update electronic controller software throughout the vehicle lifecycle.

[0003] With the rapid development of intelligent new energy vehicles and the constant updating of software versions, traditional electronic and electrical architectures feature a large number of ECUs (electronic control units), dispersed functions, and complex in-vehicle communication networks. ECU software upgrades are frequent and necessary, making comprehensive testing time-consuming and difficult. Currently, to ensure the safety and data security of new energy vehicles, the electronic control testing process requires functional link testing, single-component OTA testing, single-vehicle reliability testing, and multi-vehicle reliability testing. Testing cycles can take several months and require significant manpower, material, and financial resources, significantly increasing R&D costs. For example, a full package upgrade for a vehicle model requires four hours. Assuming one person works 10 hours per day, basic testing with two people simultaneously would take two months to complete, and reliability testing with two people simultaneously would take five months. Such a long testing cycle constantly occupies engineering resources and test vehicle resources, resulting in high costs. Summary of the Invention

[0004] The purpose of the present invention is to provide an OTA upgrade method and device to solve the problem of complex software upgrade process and waste of resources for electronic control units in automobiles in the prior art.

[0005] To achieve the above objectives, an embodiment of the present invention provides an OTA upgrade method, which is applied to a test system and includes:

[0006] Test the target software to be upgraded and obtain the test results;

[0007] Obtaining an upgrade package for the target software according to the test result;

[0008] Determining the function type of the target software according to the upgrade package of the target software;

[0009] According to the function type to which the target software belongs, a corresponding upgrade method is determined to perform OTA upgrade on the target software.

[0010] Optionally, the upgrade method includes at least one of the following: a first upgrade method, a second upgrade method, and a third upgrade method; wherein,

[0011] The security function corresponds to the first upgrade method;

[0012] The basic functions correspond to the second upgrade method;

[0013] The entertainment function corresponds to the third upgrade method.

[0014] Optionally, determining a corresponding upgrade method to perform OTA upgrade on the target software according to the function type to which the target software belongs includes:

[0015] When the upgrade method is the first upgrade method, the target vehicle is controlled to perform OTA upgrade on the target software according to the upgrade package of the target software.

[0016] Optionally, determining a corresponding upgrade method to perform OTA upgrade on the target software according to the function type to which the target software belongs includes:

[0017] When the upgrade mode is the second upgrade mode, sending the upgrade package of the target software to the target vehicle;

[0018] If a first authorization upgrade request fed back by the target vehicle is obtained, determining, according to the first authorization upgrade request, that the target vehicle perform an OTA upgrade on the target software;

[0019] The first authorization upgrade request is used to indicate instruction information for allowing the target software to be upgraded OTA.

[0020] Optionally, determining a corresponding upgrade method to perform OTA upgrade on the target software according to the function type to which the target software belongs includes:

[0021] When the upgrade mode is the third upgrade mode, sending the upgrade package of the target software to the target vehicle according to the acquired second authorization upgrade request of the target vehicle;

[0022] Determining, according to the upgrade package of the target software, that the target vehicle performs an OTA upgrade on the target software;

[0023] The second authorization upgrade request is used to indicate instruction information for allowing the target software to be upgraded OTA.

[0024] Optionally, the method further includes:

[0025] Perform OTA upgrade on the target software according to the R&D upgrade method;

[0026] The R&D upgrade method includes controlling a target vehicle to perform OTA upgrade on the target software according to an upgrade package of the target software.

[0027] Optionally, after determining the corresponding upgrade method to perform OTA upgrade on the target software, the method further includes:

[0028] After determining the corresponding upgrade method, obtain N test cases to be executed;

[0029] Perform an OTA upgrade on the target software according to the N test cases.

[0030] Optionally, after determining the corresponding upgrade method to perform OTA upgrade on the target software, the method further includes:

[0031] According to N test cases and the time stamp after each test case is executed, a test report having a corresponding relationship between the time stamp and the test case is generated.

[0032] To achieve the above objectives, an embodiment of the present invention further provides an OTA upgrade device, comprising:

[0033] The first processing module is used to test the target software to be upgraded and obtain the test results;

[0034] A second processing module is used to obtain an upgrade package of the target software according to the test result;

[0035] A third processing module is configured to determine the function type to which the target software belongs based on the upgrade package of the target software;

[0036] The fourth processing module is used to determine a corresponding upgrade method to perform OTA upgrade on the target software according to the function type to which the target software belongs.

[0037] To achieve the above objectives, an embodiment of the present invention further provides a readable storage medium having a program or instruction stored thereon, which, when executed by a processor, implements the steps in the OTA upgrade method as described in any one of the above items.

[0038] The beneficial effects of the above technical solution of the present invention are as follows:

[0039] In the above technical solution, the method includes: testing the target software to be upgraded and obtaining test results; obtaining an upgrade package for the target software based on the test results; determining the functional type of the target software based on the upgrade package; and determining a corresponding upgrade method based on the functional type of the target software to perform an OTA upgrade on the target software. By selecting a corresponding upgrade method based on the functional type of the target software, the present invention can reduce the number of testers, conserve test vehicle resources, shorten the testing cycle, and improve the availability and reliability of the software. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] Figure 1 A schematic diagram of the OTA upgrade process provided by an embodiment of the present invention;

[0041] Figure 2 A schematic diagram of the modules of the OTA upgrade device provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0042] In order to make the technical problems, technical solutions and advantages to be solved by the present invention clearer, a detailed description will be given below with reference to the accompanying drawings and specific embodiments.

[0043] It should be understood that references throughout this specification to "one embodiment" or "an embodiment" mean that a particular feature, structure, or characteristic associated with the embodiment is included in at least one embodiment of the present invention. Therefore, the appearances of "in one embodiment" or "in an embodiment" throughout this specification do not necessarily refer to the same embodiment. Furthermore, these particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0044] In various embodiments of the present invention, it should be understood that the size of the serial numbers of the following processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0045] Additionally, the terms "system" and "network" are often used interchangeably herein.

[0046] In the embodiments provided herein, it should be understood that "B corresponding to A" means that B is associated with A and B can be determined based on A. However, it should also be understood that determining B based on A does not mean determining B based solely on A; B can also be determined based on A and / or other information.

[0047] like Figure 1 As shown, an optional embodiment of the present invention provides an OTA upgrade method applied to a test system, comprising:

[0048] Step 100: Test the target software to be upgraded and obtain the test results;

[0049] Step 200: Obtain an upgrade package for the target software based on the test result;

[0050] In this embodiment, in steps 100 to 200, the target software to be upgraded can be automatically tested by the test system to obtain test results, or the relevant technicians can first perform a single-vehicle flash test and verification on the OTA upgrade package. After completing the test and verification, the relevant technicians will compress the tested software and upload it to the test system through the test system operation. The test system will send the upgrade package of the target software to all vehicles that meet the upgrade conditions through the network, and then the background will update it or the owner can choose whether to update it.

[0051] Step 300: determining the function type of the target software according to the upgrade package of the target software;

[0052] Step 400: Determine a corresponding upgrade method according to the function type of the target software and perform OTA upgrade on the target software.

[0053] It should be understood that the above-mentioned test system is a remotely controllable cloud platform or cloud server, etc.

[0054] In this embodiment, the automated remote OTA upgrade method proposed in the present invention performs OTA upgrade by selecting a suitable upgrade method in steps 100 to 400, which can reduce the number of test personnel, save test vehicle resources, shorten the test cycle, and thus accelerate the software release cycle and improve the availability and reliability of the software.

[0055] Optionally, the upgrade method includes at least one of the following: a first upgrade method, a second upgrade method, and a third upgrade method; wherein,

[0056] The security function corresponds to the first upgrade method;

[0057] The basic functions correspond to the second upgrade method;

[0058] The entertainment function corresponds to the third upgrade method.

[0059] It should be noted that the safety functions include but are not limited to vehicle functions, battery functions, motor functions, etc., the basic functions include but are not limited to air-conditioning functions, compressor functions, etc., and the entertainment functions include but are not limited to central control instruments, etc. The present invention further improves the diversity of upgrade methods by selecting different upgrade methods for software involving different functions, and improves the efficiency of OTA upgrades according to appropriate upgrade methods.

[0060] Optionally, step 400 includes:

[0061] Step 410 , when the upgrade method is the first upgrade method, controlling the target vehicle to perform OTA upgrade on the target software according to the upgrade package of the target software.

[0062] In this embodiment, the first upgrade method is a silent upgrade mode: the user does not need to authorize downloading and upgrading, and remote flashing can be directly controlled by an automated test program, which can ensure the reliability of the target software of the safety function class and improve the safety of the car.

[0063] Optionally, step 400 further includes:

[0064] Step 421, when the upgrade mode is the second upgrade mode, sending the upgrade package of the target software to the target vehicle;

[0065] Step 422: If a first authorization upgrade request fed back by the target vehicle is obtained, determining that the target vehicle performs an OTA upgrade on the target software according to the first authorization upgrade request;

[0066] The first authorization upgrade request is used to indicate instruction information for allowing the target software to be upgraded OTA.

[0067] In this embodiment, the second upgrade method is a forced upgrade mode: it does not require user authorization for downloading, but does require user authorization for upgrading. Receiving the first authorized upgrade request from the target vehicle can be understood as requiring the controller area network (CAN) to receive a prompt message from the central control screen, use a manipulator to touch the central control screen to start the task, use a camera to monitor the task progress, and an automated test program to check the accumulated flashing results.

[0068] Optionally, step 400 further includes:

[0069] Step 431: When the upgrade mode is the third upgrade mode, sending the upgrade package of the target software to the target vehicle according to the acquired second authorization upgrade request of the target vehicle;

[0070] Step 432 , determining that the target vehicle performs an OTA upgrade on the target software based on the upgrade package of the target software;

[0071] The second authorization upgrade request is used to indicate instruction information for allowing the target software to be upgraded OTA.

[0072] In this embodiment, the third upgrade method is a standard upgrade mode, requiring user authorization for both the upgrade and the download. In steps 431 and 432, the test system issues a standard upgrade task, prompting the central control screen to prompt "whether to proceed with the standard upgrade." The CAN receives a prompt message from the central control screen, prompting the robot to touch the central control screen to initiate the task. The camera monitors the task's progress, and the automated test program checks the cumulative flash results.

[0073] Optionally, the method further includes:

[0074] Step 510, performing OTA upgrade on the target software according to the R&D upgrade method;

[0075] Step 520, the R&D upgrade method includes controlling the target vehicle to perform OTA upgrade on the target software according to the upgrade package of the target software.

[0076] In this embodiment, the R&D upgrade method does not require users to authorize downloading and upgrading, and can directly use an automated test program to control remote flashing. Vehicles can be randomly selected for upgrading during the R&D stage, ensuring the authenticity of data during the R&D stage.

[0077] Optionally, after step 400, the method further includes:

[0078] Step 441: After determining the corresponding upgrade method, obtain N test cases to be executed;

[0079] Step 442: Perform OTA upgrade on the target software according to the N test cases.

[0080] In this embodiment, the test case is a remote OTA test case. Relevant technicians can edit the remote OTA test case online or offline. After storage, they can be accessed online or downloaded for offline viewing and editing. The test system has the functions of test case editing, cloud storage and version management. On the test system, the remote flashing platform can be accessed from the cloud, and the automated execution of the case can be set to start. After completing N test cases for OTA upgrade, the present invention can execute the collaborative robot arm and the cloud platform 24 hours a day without interruption, which shortens the test time by 59% compared to a manual working time of 10 hours a day. Moreover, the present invention is not limited by the work location and working environment, saving time and labor costs.

[0081] Optionally, after step 400, the method further includes:

[0082] According to N test cases and the time stamp after each test case is executed, a test report having a corresponding relationship between the time stamp and the test case is generated.

[0083] In a specific real-time mode, the first upgrade mode and the R&D upgrade mode flash test are executed continuously in the automated test remote OTA software. After a test case is executed, the test process and test results are packaged and named "test case name + timestamp" and stored in a selected folder. The next flash test case is executed sequentially until all flash test cases are executed or the case execution is manually stopped.

[0084] A test case cannot be manually ended during execution. If you click the "End this test case" button during the execution of the test case, the flash task will be completed and the next task will not be executed in sequence, and the execution process will stop.

[0085] An automated control device, consisting of a collaborative robotic arm and a camera, is placed in front of the central control display. The collaborative robotic arm can be remotely controlled by an engineer to start and stop operation. When the user authorization download interface pops up on the central control, the CAN network receives the corresponding message. The automated testing software controls the collaborative robotic arm to execute different test cases according to the engineer's settings, automatically clicking OK to start or cancel the download. The camera monitors and records the entire test process, packaging and storing the recorded data by timestamp so that any test problems can be located and corrected.

[0086] The second upgrade method is to set up continuous execution in the automated test software, which does not require user authorization for automatic downloading. After the download is complete, the central control will pop up the user authorization upgrade interface, and the collaborative robotic arm will automatically click "Start Upgrade".

[0087] The third upgrade method is to set the automated test software to run continuously. When the central control prompts the user authorization download interface, the collaborative robot arm automatically clicks "Start Download". After the download is complete, when the central control prompts the user authorization upgrade interface, the collaborative robot arm automatically clicks "Start Upgrade".

[0088] It should be noted that the above automated testing solution also has the following improvements:

[0089] Add a programmable power supply to automate testing of abnormal power outages during the upgrade process. During testing, if an abnormal power outage occurs due to test case writing problems or vehicle problems, the programmable power supply can be used to automatically resume the test process from the breakpoint.

[0090] Add Ethernet data acquisition equipment to collect Ethernet data for data analysis. Use pre-set tools to collect CAN signals for test problem location and data analysis.

[0091] Add a robot arm + camera to automate the human-computer interaction part.

[0092] Add remote OTA software control through automated testing to automate cloud access.

[0093] To sum up, the technical solution of the present invention can maximize the use of existing resources for design under the condition of test system and test resources; the collaborative robotic arm and cloud platform can be executed 24 hours a day without interruption, which shortens the test time by 59% compared with the 10-hour working day of manual labor; the collaborative robotic arm can be controlled remotely in the background, without being restricted by the work location and work environment, saving time and labor costs; the collaborative robotic arm is used to control the start or cancellation of the central control task, saving labor costs; automated testing avoids misoperation during human testing and improves the reliability of the software; the test process is monitored and recorded with a camera to facilitate problem location and reproduction.

[0094] like Figure 2 As shown, an optional embodiment of the present invention further provides an OTA upgrade device, comprising:

[0095] The first processing module 10 is used to test the target software to be upgraded and obtain the test results;

[0096] A second processing module 20 is configured to obtain an upgrade package of the target software according to the test result;

[0097] The third processing module 30 is used to determine the function type of the target software according to the upgrade package of the target software;

[0098] The fourth processing module 40 is configured to determine a corresponding upgrade method according to the function type to which the target software belongs, and perform OTA upgrade on the target software.

[0099] It should be noted that the upgrade method includes at least one of the following: a first upgrade method, a second upgrade method, and a third upgrade method; wherein,

[0100] The security function corresponds to the first upgrade method;

[0101] The basic functions correspond to the second upgrade method;

[0102] The entertainment function corresponds to the third upgrade method.

[0103] Optionally, the fourth processing module 40 includes:

[0104] The first processing unit is configured to control the target vehicle to perform OTA upgrade on the target software according to the upgrade package of the target software when the upgrade method is the first upgrade method.

[0105] Optionally, the fourth processing module 40 includes:

[0106] a second processing unit, configured to send the upgrade package of the target software to a target vehicle when the upgrade mode is the second upgrade mode;

[0107] a third processing unit, configured to, if a first authorization upgrade request fed back by the target vehicle is obtained, determine, based on the first authorization upgrade request, that the target vehicle perform an OTA upgrade on the target software;

[0108] The first authorization upgrade request is used to indicate instruction information for allowing the target software to be upgraded OTA.

[0109] Optionally, the fourth processing module 40 includes:

[0110] a fourth processing unit, configured to, when the upgrade mode is the third upgrade mode, send the upgrade package of the target software to the target vehicle according to the acquired second authorized upgrade request of the target vehicle;

[0111] a fifth processing unit, configured to determine, based on the upgrade package of the target software, that the target vehicle performs an OTA upgrade on the target software;

[0112] The second authorization upgrade request is used to indicate instruction information for allowing the target software to be upgraded OTA.

[0113] Optionally, the device further includes:

[0114] A fifth processing module, configured to perform OTA upgrade on the target software according to a research and development upgrade method;

[0115] The R&D upgrade method includes controlling a target vehicle to perform OTA upgrade on the target software according to an upgrade package of the target software.

[0116] Optionally, the device further includes:

[0117] The sixth processing module is used to obtain N test cases to be executed after determining the corresponding upgrade method;

[0118] The seventh processing module is used to perform OTA upgrade on the target software according to the N test cases.

[0119] Optionally, the device further includes:

[0120] The eighth processing module is configured to generate, according to the N test cases and the time stamp after each test case is executed, a test report having a correspondence between the time stamp and the test case.

[0121] A readable storage medium according to an embodiment of the present invention stores a program or instruction thereon. When the program or instruction is executed by a processor, the steps in the OTA upgrade method described above are implemented and the same technical effect can be achieved. To avoid repetition, they will not be described here.

[0122] The processor is the processor in the OTA upgrade method described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), random access memory (RAM), a magnetic disk, or an optical disk.

[0123] In embodiments of the present invention, modules can be implemented in software so that they can be executed by various types of processors. For example, an identified executable code module can include one or more physical or logical blocks of computer instructions, for example, which can be constructed as objects, procedures, or functions. Nevertheless, the executable code of the identified module does not need to be physically located together, but can include different instructions stored in different locations, which, when logically combined together, constitute the module and achieve the specified purpose of the module.

[0124] In fact, executable code module can be a single instruction or many instructions, and can even be distributed on a plurality of different code segments, distributed in the middle of different programs, and distributed across a plurality of memory devices.Similarly, operating data can be identified in the module, and can be implemented and organized in the data structure of any appropriate type according to any appropriate form.Described operating data can be collected as a single data set, or can be distributed in different locations (including on different storage devices), and can only be present on a system or network as an electronic signal at least in part.

[0125] When a module can be implemented using software, given the current state of hardware technology, those skilled in the art can build corresponding hardware circuits to implement the corresponding functions of the module, regardless of cost. The hardware circuits may include conventional very large scale integration (VLSI) circuits or gate arrays, as well as existing semiconductors such as logic chips and transistors, or other discrete components. Modules may also be implemented using programmable hardware devices, such as field programmable gate arrays, programmable array logic, or programmable logic devices.

[0126] The above exemplary embodiments are described with reference to the accompanying drawings. Many different forms and embodiments are possible without departing from the spirit and teachings of the present invention. Therefore, the present invention should not be construed as limited to the exemplary embodiments set forth herein. Rather, these exemplary embodiments are provided so that this disclosure will be thorough and complete and will convey the scope of the invention to those skilled in the art. In the drawings, component sizes and relative sizes may be exaggerated for clarity. The terminology used herein is for purposes of describing specific exemplary embodiments only and is not intended to be limiting. As used herein, the singular forms "a," "an," and "the" are intended to encompass plural forms, unless the context clearly indicates otherwise. It will be further understood that the terms "comprising" and / or "including," when used in this specification, indicate the presence of stated features, integers, steps, operations, components, and / or elements, but do not preclude the presence or addition of one or more other features, integers, steps, operations, components, elements, and / or groups thereof. Unless otherwise indicated, when stated, a range of values ​​includes the upper and lower limits of that range and any subranges therebetween.

[0127] The above is a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and modifications should also be regarded as within the scope of protection of the present invention.

Claims

1. An OTA upgrade method, characterized in that: Applicable to test systems, including: Test the target software to be upgraded and obtain the test results; Obtaining an upgrade package for the target software according to the test result; Determining the function type of the target software according to the upgrade package of the target software; Determine, according to the function type of the target software, a corresponding upgrade method to perform OTA upgrade on the target software; The upgrade method includes at least one of the following: a first upgrade method, a second upgrade method, and a third upgrade method; wherein the safety function corresponds to the first upgrade method; the basic function corresponds to the second upgrade method; and the entertainment function corresponds to the third upgrade method; The step of determining a corresponding upgrade method to perform OTA upgrade on the target software according to the function type to which the target software belongs includes: When the upgrade mode is the first upgrade mode, controlling the target vehicle to perform OTA upgrade on the target software according to the upgrade package of the target software; When the upgrade mode is the second upgrade mode, sending the upgrade package of the target software to the target vehicle; if a first authorization upgrade request fed back by the target vehicle is obtained, determining that the target vehicle performs an OTA upgrade on the target software according to the first authorization upgrade request; wherein the first authorization upgrade request is used to indicate instruction information allowing the target software to be upgraded OTA; When the upgrade mode is the third upgrade mode, sending the upgrade package of the target software to the target vehicle according to the obtained second authorization upgrade request of the target vehicle; determining, according to the upgrade package of the target software, that the target vehicle performs an OTA upgrade on the target software; wherein the second authorization upgrade request is used to indicate instruction information allowing the target software to be upgraded OTA; The first upgrade mode is a silent upgrade mode: it does not require user authorization for downloading and upgrading, and can be directly controlled by an automated test program to remotely flash. The second upgrade mode is a forced upgrade mode: it does not require user authorization for downloading, but requires user authorization for upgrading. The third upgrade mode is a standard upgrade mode: it requires user authorization for upgrading and downloading. The method further includes: performing an OTA upgrade on the target software according to a research and development upgrade method; the research and development upgrade method includes controlling a target vehicle to perform an OTA upgrade on the target software according to an upgrade package of the target software; Among them, the flash test of the first upgrade method and the R&D upgrade method is executed continuously in the automated test remote OTA software setting. After the execution of a test case is completed, the executed test process and test results are packaged and named as the test case name and timestamp, and stored in the selected folder; the next flash test case is executed sequentially downward until all flash test cases are executed or the case execution is manually stopped; A test case cannot be manually ended during execution. If you click the "End" button during execution, the flash task will be completed and the next task will not be executed in sequence, and the execution process will stop. An automated control device is placed in front of the central control display screen. The automated control device includes a collaborative robotic arm and a camera. The collaborative robotic arm is used to start and shut down by remote control by an engineer. When the user authorization download interface pops up on the central control display screen, the CAN network receives the corresponding message. The OTA software controls the collaborative robotic arm to execute different test cases according to the engineer's settings, automatically clicking OK to start or cancel the download. The camera monitors and records the entire test process, and the test process recorded data is packaged and stored according to the timestamp. The second upgrade method is to continuously execute the OTA software settings without user authorization for automatic download. After the download is completed, the central control display pops up a user authorization upgrade interface, and the collaborative robot arm automatically clicks to start the upgrade; The third upgrade method is executed continuously in the OTA software setting. When the central control display screen pops up the user authorization download interface, the collaborative robotic arm automatically clicks to start downloading. After the download is completed, when the central control display screen pops up the user authorization upgrade interface, the collaborative robotic arm automatically clicks to start upgrading.

2. The method according to claim 1, characterized in that After determining the corresponding upgrade method to perform OTA upgrade on the target software, the method further includes: After determining the corresponding upgrade method, obtain N test cases to be executed; Perform OTA upgrade on the target software according to the N test cases.

3. The method according to claim 2, characterized in that After determining the corresponding upgrade method to perform OTA upgrade on the target software, the method further includes: According to N test cases and the time stamp after each test case is executed, a test report having a corresponding relationship between the time stamp and the test case is generated.

4. An OTA upgrade device, characterized in that: include: The first processing module is used to test the target software to be upgraded and obtain the test results; A second processing module is used to obtain an upgrade package of the target software according to the test result; A third processing module is configured to determine the function type to which the target software belongs based on the upgrade package of the target software; A fourth processing module is configured to determine a corresponding upgrade method according to the function type of the target software and perform OTA upgrade on the target software; The upgrade method includes at least one of the following: a first upgrade method, a second upgrade method, and a third upgrade method; wherein the safety function corresponds to the first upgrade method; the basic function corresponds to the second upgrade method; and the entertainment function corresponds to the third upgrade method; The fourth processing module includes: a first processing unit, configured to, when the upgrade mode is the first upgrade mode, control the target vehicle to perform OTA upgrade on the target software according to the upgrade package of the target software; a second processing unit configured to send the upgrade package of the target software to the target vehicle if the upgrade method is the second upgrade method; and a third processing unit configured to, if a first authorization upgrade request fed back by the target vehicle is obtained, determine, based on the first authorization upgrade request, that the target vehicle perform an OTA upgrade on the target software; wherein the first authorization upgrade request is used to indicate instruction information allowing the target software to be upgraded OTA; a fourth processing unit, configured to, when the upgrade mode is the third upgrade mode, send an upgrade package of the target software to the target vehicle based on the second authorized upgrade request obtained from the target vehicle; a fifth processing unit, configured to determine, based on the upgrade package of the target software, that the target vehicle performs an OTA upgrade on the target software; wherein the second authorized upgrade request is used to indicate instruction information allowing the target software to be upgraded OTA; The first upgrade mode is a silent upgrade mode: it does not require user authorization for downloading and upgrading, and can be directly controlled by an automated test program to remotely flash. The second upgrade mode is a forced upgrade mode: it does not require user authorization for downloading, but requires user authorization for upgrading. The third upgrade mode is a standard upgrade mode: it requires user authorization for upgrading and downloading. The device further includes: a fifth processing module configured to perform an OTA upgrade on the target software according to a research and development upgrade method; the research and development upgrade method includes controlling a target vehicle to perform an OTA upgrade on the target software according to an upgrade package of the target software; Among them, the flash test of the first upgrade method and the R&D upgrade method is executed continuously in the automated test remote OTA software setting. After the execution of a test case is completed, the executed test process and test results are packaged and named as the test case name and timestamp, and stored in the selected folder; the next flash test case is executed sequentially downward until all flash test cases are executed or the case execution is manually stopped; A test case cannot be manually ended during execution. If you click the "End" button during execution, the flash task will be completed and the next task will not be executed in sequence, and the execution process will stop. An automated control device is placed in front of the central control display screen. The automated control device includes a collaborative robotic arm and a camera. The collaborative robotic arm is used to start and shut down by remote control by an engineer. When the user authorization download interface pops up on the central control display screen, the CAN network receives the corresponding message. The OTA software controls the collaborative robotic arm to execute different test cases according to the engineer's settings, automatically clicking OK to start or cancel the download. The camera monitors and records the entire test process, and the test process recorded data is packaged and stored according to the timestamp. The second upgrade method is to continuously execute the OTA software settings without user authorization for automatic download. After the download is completed, the central control display pops up a user authorization upgrade interface, and the collaborative robot arm automatically clicks to start the upgrade; The third upgrade method is executed continuously in the OTA software setting. When the central control display screen pops up the user authorization download interface, the collaborative robotic arm automatically clicks to start downloading. After the download is completed, when the central control display screen pops up the user authorization upgrade interface, the collaborative robotic arm automatically clicks to start upgrading.

5. A readable storage medium having a program or instruction stored thereon, characterized in that: When the program or instruction is executed by a processor, the steps in the OTA upgrade method according to any one of claims 1 to 3 are implemented.

Images