Road test vehicle software upgrading management method and device, electronic equipment and program product
By generating road test problem reports and developing test firmware using the vehicle software development platform, remote controller upgrades were achieved, solving the high cost problem caused by controller anomalies during the vehicle development phase and improving development efficiency.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-11-28
- Publication Date
- 2026-03-17
AI Technical Summary
During the vehicle development phase, if the controller malfunctions during road testing, existing solutions require recalling vehicles or dispatching personnel to rewrite the firmware, resulting in high costs and stalled development progress.
The system generates road test problem reports, develops test firmware through the vehicle software development platform, and remotely sends it to the target controller via an over-the-air download module to control the loading of the test firmware, thereby enabling remote diagnosis and upgrades.
It reduced vehicle road testing costs, shortened downtime, improved R&D efficiency, and eliminated physical distance limitations.
Smart Images
Figure CN121680902A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of software upgrade technology, and in particular to methods, devices, electronic equipment and program products for managing software upgrades of road test vehicles. Background Technology
[0002] During the vehicle development phase, if a controller malfunctions during road testing, the current solution is usually to recall the vehicle to the R&D base or send R&D personnel to the test location to re-flash the firmware. However, this undoubtedly increases the cost of vehicle road testing and brings the vehicle development process to a standstill. Summary of the Invention
[0003] The main objective of this application is to provide a method, apparatus, electronic device, and program product for managing software upgrades of road test vehicles, aiming to reduce the cost of vehicle road testing and improve vehicle development efficiency.
[0004] To achieve the above objectives, one aspect of this application proposes a method for managing software upgrades of road test vehicles, the method comprising: A road test problem report is generated and sent to the vehicle software development platform. The road test problem report is used to record abnormal problems that occur in the target controller in the road test vehicle during the road test, so that the R&D personnel can develop test firmware based on the road test problem report on the vehicle software development platform. Receive the test firmware sent by the vehicle software development platform via the over-the-air download module; Control the target controller to load the test firmware.
[0005] In some embodiments, the method further includes: Control the target controller to restart and activate the test firmware; A road test problem verification report is generated and sent to the vehicle software development platform. The road test problem verification report is used to record whether the abnormal problem has been resolved, so that the vehicle software development platform can record and store the test firmware, its corresponding development information, and the road test problem verification report.
[0006] In some embodiments, controlling the target controller to load the test firmware includes: The target controller is instructed to store the test firmware in a preset cache area; When the road test vehicle meets the preset upgrade conditions, the target controller is controlled to first back up and then erase the currently running old version firmware stored in the preset executable area through the bootloader program, and then migrate the test firmware stored in the preset cache area to the preset executable area for storage.
[0007] In some embodiments, the road test vehicle meets preset upgrade conditions including the road test vehicle speed being zero, the road test vehicle power system being in a non-operating state, and the road test vehicle power supply voltage being higher than a preset voltage threshold.
[0008] To achieve the above objectives, another aspect of this application provides a road test vehicle software upgrade management device, the device comprising: The first sending module is used to generate a road test problem report and send it to the vehicle software development platform. The road test problem report is used to record abnormal problems that occur in the target controller in the road test vehicle during the road test, so that the R&D personnel can develop test firmware on the vehicle software development platform based on the road test problem report. A receiving module is used to receive the test firmware sent by the vehicle software development platform through the over-the-air download module; A loading module is used to control the target controller to load the test firmware.
[0009] In some embodiments, the apparatus further includes: The activation module is used to control the target controller to restart and activate the test firmware; The second sending module is used to generate a road test problem verification report and send it to the vehicle software development platform. The road test problem verification report is used to record whether the abnormal problem has been resolved, so that the vehicle software development platform can record and store the test firmware and its corresponding development information and the road test problem verification report.
[0010] In some embodiments, the loading module includes: The first processing unit is used to control the target controller to store the test firmware to a preset cache area; The second processing unit is used to control the target controller to first back up and then erase the currently running old version firmware stored in the preset executable area through the bootloader when the road test vehicle meets the preset upgrade conditions, and then migrate the test firmware stored in the preset cache area to the preset executable area for storage.
[0011] In some embodiments, the road test vehicle meets preset upgrade conditions including the road test vehicle speed being zero, the road test vehicle power system being in a non-operating state, and the road test vehicle power supply voltage being higher than a preset voltage threshold.
[0012] To achieve the above objectives, another aspect of this application provides an electronic device, which includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the above-described road test vehicle software upgrade management method.
[0013] To achieve the above objectives, another aspect of this application provides a computer program product, including a computer program that, when executed by a processor, implements the above-described road test vehicle software upgrade management method.
[0014] The embodiments of this application include at least the following beneficial effects: When the target controller in the road test vehicle encounters an abnormal problem during the road test, a corresponding road test problem report is first generated and sent to the vehicle software development platform, so that the R&D personnel can develop test firmware based on the road test problem report on the vehicle software development platform, which can achieve remote diagnosis. Then, the test firmware sent by the vehicle software development platform through the over-the-air download module is received, and then the abnormal target controller is controlled to load the test firmware. There is no need to recall the road test vehicle or send R&D personnel to the test location for physical flashing, which can eliminate physical distance limitations, reduce vehicle road test costs, reduce vehicle road test interruption time, and thus improve vehicle development efficiency.
[0015] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description
[0016] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the description of the embodiments taken in conjunction with the following drawings, in which: Figure 1 This is a flowchart illustrating a method for managing software upgrades of road test vehicles provided in an embodiment of this application; Figure 2 This is a schematic diagram of the composition of a road test vehicle software upgrade management device provided in an embodiment of this application; Figure 3 This is a schematic diagram of the hardware structure of the electronic device provided in the embodiments of this application. Detailed Implementation
[0017] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the reference to "embodiment" herein means that a specific feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments. The implementation methods described in the following exemplary embodiments do not represent all implementation methods consistent with the embodiments of this application; they are merely examples of apparatuses and methods consistent with some aspects of the embodiments of this application as detailed in the appended claims.
[0018] It is understood that the terms "first," "second," etc., used in this application may be used to describe various concepts herein, but unless specifically stated otherwise, these concepts are not limited by these terms. These terms are only used to distinguish one concept from another. For example, without departing from the scope of the embodiments of this application, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the words "if" or "when" as used herein may be interpreted as "when," "in response to a determination," or "at least one," "multiple," "each," "any," etc., as used in this application, at least one includes one, two, or more than two, multiple includes two or more, each refers to each of the corresponding multiple, and any refers to any one of the multiple.
[0019] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.
[0020] As vehicles become increasingly electronic, the role of vehicle software in realizing overall vehicle functionality is becoming more and more prominent. Traditional vehicle software updates mainly rely on returning the vehicle to the factory or a 4S dealership for physical connection flashing, but this method suffers from inefficiency and high costs. In recent years, the automotive industry has gradually introduced OTA (Over-The-Air) technology to achieve remote software upgrades, which can effectively improve user experience and vehicle performance. It is worth noting that existing OTA technology primarily focuses on software upgrades after vehicle mass production, with relatively limited application during the vehicle development phase.
[0021] During the vehicle development phase, if a controller malfunctions during road testing, the current solution is usually to recall the vehicle to the R&D base or send R&D personnel to the test location to re-flash the firmware. However, this undoubtedly increases the cost of vehicle road testing and brings the vehicle development process to a standstill.
[0022] In view of this, this application proposes a method, device, electronic device, and program product for managing software upgrades of road test vehicles. This solution proposes that when a target controller in a road test vehicle encounters an abnormal problem during road testing, a corresponding road test problem report is first generated and sent to the vehicle software development platform. This allows developers to create test firmware on the platform based on the road test problem report, enabling remote diagnostics. The system then receives the test firmware sent by the vehicle software development platform via an over-the-air download module and subsequently controls the malfunctioning target controller to load the test firmware. This eliminates the need to recall the road test vehicle or dispatch developers to the test location for physical flashing, thus eliminating physical distance limitations, reducing vehicle road test costs, minimizing road test downtime, and improving vehicle development efficiency.
[0023] The road test vehicle software upgrade management method provided in this application embodiment can be applied to the electronic devices provided in this application embodiment. The electronic devices can be terminals or servers. Terminals can be tablet computers, laptops, desktop computers, etc., but are not limited to these. Servers can be independent physical servers, server clusters or distributed systems composed of multiple physical servers, or cloud servers that provide basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks, and big data and artificial intelligence platforms.
[0024] Please refer to Figure 1 , Figure 1 This is a flowchart illustrating a method for managing software upgrades of road test vehicles provided in an embodiment of this application. It should be noted that the steps shown in the flowchart can be executed in a computer system, such as a computer system containing a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.
[0025] The road test vehicle software upgrade management method provided in this application embodiment may include, but is not limited to, the three steps S101 to S103, as follows: S101. Generate a road test problem report and send it to the vehicle software development platform. The road test problem report is used to record abnormal problems that occur in the target controller in the road test vehicle during the road test, so that the R&D personnel can develop test firmware on the vehicle software development platform based on the road test problem report. S102, Receive test firmware sent by the vehicle software development platform via the over-the-air download module; S103, Control the target controller to load the test firmware.
[0026] The three steps S101 to S103 shown in this application embodiment involve first receiving test firmware sent by the vehicle software development platform via an over-the-air download module to assist in resolving target controller malfunctions, and then controlling the target controller to load it. This can reduce vehicle road test costs and improve vehicle road test efficiency while eliminating physical distance limitations.
[0027] In some embodiments, S101, the content regarding the R&D personnel developing test firmware based on road test problem reports on the vehicle software development platform can be further understood as follows: the R&D personnel obtain abnormal problems that occur in the target controller during road testing through the vehicle software development platform, analyze the abnormal problems to determine the corresponding solutions, and then convert the solutions into test firmware in the form of code on the vehicle software development platform.
[0028] In some embodiments, S102, the over-the-air download module can be understood as an application architecture built on the vehicle software development platform. It can establish a stable and reliable network transmission channel on which the vehicle software development platform sends the generated test firmware to the road test vehicle, and also provide basic support for rapid iteration in the subsequent vehicle development process.
[0029] In some embodiments, regarding the loading of test firmware by controlling the target controller in S103, the corresponding implementation may include, but is not limited to, the two steps S201 to S202, as follows: S201, The target controller stores the test firmware in its internal preset cache area; S202. When the road test vehicle meets the preset upgrade conditions, the target controller first backs up and erases the currently running old version firmware stored in the preset executable area through its internal bootloader, and then migrates the test firmware stored in the preset cache area to the preset executable area for storage, so that the target controller can directly locate the preset executable area to run the newly written test firmware.
[0030] In some embodiments, S202, the road test vehicle meets the preset upgrade conditions including: the road test vehicle's speed is zero (i.e., the vehicle is stationary), the road test vehicle's power system is in a non-operating state (e.g., the engine is off, the motor is stopped, etc.), and the road test vehicle's power supply voltage is higher than a preset voltage threshold. By limiting the road test vehicle's power supply voltage to be higher than the preset voltage threshold, it can be ensured that abnormal interruptions due to power loss occur during the firmware flashing process.
[0031] Optionally, when the test vehicle is idle (e.g., when the test vehicle is charging at night), it is determined that the test vehicle meets the preset upgrade conditions to avoid the upgrade process taking up the normal usage time of the test vehicle, thereby improving the user experience.
[0032] In some embodiments, S202, the content regarding controlling the target controller to back up the currently running old version firmware stored in its internal preset executable area through its internal bootloader can be understood as: controlling the target controller to copy the old version firmware through the bootloader and then write it to its internal preset backup storage area, so as to ensure that the target controller can enable the rollback mechanism in the event of subsequent failure to activate the test firmware, that is, first erase the test firmware stored in the preset executable area, and then migrate the old version firmware stored in the preset backup storage area to the preset executable area.
[0033] In some embodiments, the above-described road test vehicle software upgrade management method may further include steps S104 to S105, as follows: S104. Control the target controller to restart and activate the test firmware; S105. Generate a road test problem verification report and send it to the vehicle software development platform. The road test problem verification report is used to record whether the abnormal problems of the target controller in the road test vehicle during the road test have been resolved, so that the vehicle software development platform can record and store the test firmware and its corresponding development information and the road test problem verification report. Among them, the development information corresponding to the test firmware includes at least the reason for the development of the test firmware, the key development content, the development time, and the identity information of the R&D personnel.
[0034] In addition, by sending road test problem verification reports to the vehicle software development platform for feedback to the R&D personnel, a rapid closed-loop process for abnormal issues can be achieved.
[0035] In some embodiments, S105, the recording and storage of test firmware, its corresponding development information, and road test problem verification reports by the vehicle software development platform can be understood as follows: the vehicle software development platform integrates the test firmware, its corresponding development information, and road test problem verification reports to form a development record package for the target controller, and then stores this development record package in the built-in version control system (VCS). This version control system is essentially a dedicated ECU software change record system, enabling version traceability and solving the problem of chaotic traditional manual flashing records. This allows the development team to more clearly understand the software evolution process, facilitating problem localization and resolution.
[0036] Please refer to Figure 2 , Figure 2This is a schematic diagram of the composition of a road test vehicle software upgrade management device provided in an embodiment of this application, which can implement the above-mentioned road test vehicle software upgrade management method. The device may include, but is not limited to, the following: The first sending module 301 is used to generate a road test problem report and send it to the vehicle software development platform. The road test problem report is used to record abnormal problems of the target controller in the road test vehicle during the road test, so that the R&D personnel can develop test firmware on the vehicle software development platform based on the road test problem report. Receiver module 302 is used to receive the test firmware sent by the vehicle software development platform through the over-the-air download module; Loading module 303 is used to control the target controller that malfunctions to load the test firmware.
[0037] The over-the-air (OTA) download module can be understood as the application architecture built on the vehicle software development platform. It can establish a stable and reliable network transmission channel for the test firmware generated by the vehicle software development platform to be sent to the road test vehicle, and also provide basic support for rapid iteration in the subsequent vehicle development process.
[0038] In some embodiments, the loading module 303 may include, but is not limited to, the following: The first processing unit is used to control the target controller that malfunctions to store the test firmware in a preset cache area. The second processing unit is used to, when the road test vehicle meets the preset upgrade conditions, control the target controller that has an abnormality to first back up and then erase the currently running old version firmware stored in the preset executable area through the bootloader program, and then migrate the test firmware stored in the preset cache area to the preset executable area for storage.
[0039] The preset upgrade conditions for road test vehicles include: the vehicle speed is zero (i.e., the vehicle is stationary), the vehicle's power system is in a non-operating state (e.g., the engine is off, the motor is stopped, etc.), and the power supply voltage of the road test vehicle is higher than a preset voltage threshold. By limiting the power supply voltage of the road test vehicle to be higher than the preset voltage threshold, it can be ensured that abnormal interruptions will not occur due to power failure during the firmware flashing process.
[0040] Optionally, when the test vehicle is idle (e.g., when the test vehicle is charging at night), it is determined that the test vehicle meets the preset upgrade conditions to avoid the upgrade process taking up the normal usage time of the test vehicle, thereby improving the user experience.
[0041] In some embodiments, the above-described road test vehicle software upgrade management device may further include the following: Activation module 304 is used to control the target controller that malfunctions to restart and activate the test firmware. The second sending module 305 is used to generate a road test problem verification report and send it to the vehicle software development platform. The road test problem verification report is used to record whether the abnormal problems of the target controller in the road test vehicle during the road test have been resolved, so that the vehicle software development platform can record and store the test firmware and its corresponding development information and the road test problem verification report. The development information corresponding to the test firmware includes at least the reason for the development of the test firmware, the key development content, the development time, and the identity information of the R&D personnel.
[0042] It should be noted that data storage can be performed through the version control system built into the vehicle software development platform. This version control system is equivalent to a dedicated ECU software change record system, which can realize version traceability function, solve the problem of messy records in traditional manual flashing, and enable the R&D team to have a clearer understanding of the software evolution process, making it easier to locate and solve problems.
[0043] It is understood that the content of the above method embodiments is applicable to the present device embodiments. The functions specifically implemented by the present device embodiments are the same as those specifically implemented by the above method embodiments, and the beneficial effects achieved by the present device embodiments are also the same as those achieved by the above method embodiments.
[0044] This application also provides an electronic device, which includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the aforementioned road test vehicle software upgrade management method. The electronic device may include any smart terminal such as a tablet computer or an in-vehicle computer.
[0045] It is understood that the content of the above method embodiments is applicable to the present device embodiments. The specific functions implemented by the present device embodiments are the same as those implemented by the above method embodiments, and the beneficial effects achieved by the present device embodiments are also the same as those achieved by the above method embodiments.
[0046] Please see Figure 3 , Figure 3 This is a schematic diagram illustrating the hardware structure of an electronic device according to another embodiment. The electronic device includes: The processor 401 can be implemented using a general-purpose CPU (Central Processing Unit), microprocessor, application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this application. The memory 402 can be implemented in the form of read-only memory (ROM), static storage device, dynamic storage device, or random access memory (RAM). The memory 402 can store the operating system and other applications. When the technical solution provided in the embodiments of this application is implemented by software or firmware, the relevant program code is stored in the memory 402 and is called and executed by the processor 401. Input / output interface 403 is used to implement information input and output; The communication interface 404 is used to enable communication and interaction between this device and other devices. Communication can be achieved through wired means (such as USB, Ethernet cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.). Bus 405 transmits information between various components of the device (e.g., processor 401, memory 402, input / output interface 403, and communication interface 404); The processor 401, memory 402, input / output interface 403 and communication interface 404 are connected to each other within the device via bus 405.
[0047] This application also provides a computer program product, which includes a computer program that, when executed by one or more processors, implements the above-described road test vehicle software upgrade management method.
[0048] It is understood that the content of the above method embodiments is applicable to this computer program product. The specific functions implemented by the embodiments of this computer program product are the same as those implemented by the above method embodiments, and the beneficial effects achieved by the embodiments of this computer program product are also the same as those achieved by the above method embodiments.
[0049] The embodiments described in this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided by the embodiments of this application. As those skilled in the art will know, with the evolution of technology and the emergence of new application scenarios, the technical solutions provided by the embodiments of this application are also applicable to similar technical problems.
[0050] Those skilled in the art will understand that the technical solutions shown in the figures do not constitute a limitation on the embodiments of this application, and may include more or fewer steps than shown, or combine certain steps, or different steps.
[0051] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.
[0052] Those skilled in the art will understand that all or some of the steps, apparatuses, or functional modules / units in the methods disclosed above can be implemented as software, firmware, hardware, or suitable combinations thereof.
[0053] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, apparatus, product, or device that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or devices.
[0054] It should be understood that in this application, "at least one (item)" means one or more, and "more than" means two or more. "And / or" is used to describe the relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can represent three cases: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.
[0055] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of the units described above is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed between the devices or units may be through some interfaces, and the indirect coupling or communication connection may be electrical, mechanical, or other forms.
[0056] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0057] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.
[0058] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes multiple instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing programs, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
[0059] The preferred embodiments of this application have been described above with reference to the accompanying drawings, but this does not limit the scope of the claims of this application. Any modifications, equivalent substitutions, and improvements made by those skilled in the art without departing from the scope and substance of the embodiments of this application shall be within the scope of the claims of this application.
Claims
1. A road test vehicle software upgrade management method, characterized by, The method comprises: generating a road test problem report and sending it to a whole vehicle software development platform, the road test problem report being used to record abnormal problems of a target controller in a road test vehicle during a road test, so that a developer develops a test firmware on the whole vehicle software development platform according to the road test problem report; receiving the test firmware sent by the whole vehicle software development platform through an over-the-air download module; controlling the target controller to load the test firmware.
2. The OBU software upgrade management method of claim 1, wherein, The method further comprises: controlling the target controller to restart and activate the test firmware; generating a road test problem verification report and sending it to the whole vehicle software development platform, the road test problem verification report being used to record whether the abnormal problems are solved, so that the whole vehicle software development platform records and stores the test firmware and its corresponding development information and the road test problem verification report.
3. The OBU software upgrade management method of claim 1, wherein, The controlling the target controller to load the test firmware comprises: controlling the target controller to store the test firmware in a preset cache area; when the road test vehicle meets a preset upgrade condition, controlling the target controller to first back up and then erase the currently running old version firmware stored in a preset executable area through a boot loader, and then migrate the test firmware stored in the preset cache area to the preset executable area for storage.
4. The OBU software upgrade management method of claim 3, wherein, The road test vehicle meeting the preset upgrade condition comprises that the speed of the road test vehicle is zero, the power system of the road test vehicle is in a non-running state, and the power supply voltage of the road test vehicle is higher than a preset voltage threshold.
5. A road test vehicle software upgrade management apparatus characterized by comprising: The device comprises: a first sending module configured to generate a road test problem report and send it to a whole vehicle software development platform, the road test problem report being used to record abnormal problems of a target controller in a road test vehicle during a road test, so that a developer develops a test firmware on the whole vehicle software development platform according to the road test problem report; a receiving module configured to receive the test firmware sent by the whole vehicle software development platform through an over-the-air download module; a loading module configured to control the target controller to load the test firmware.
6. The OBU software upgrade management apparatus of claim 5, wherein, The device further comprises: an activating module configured to control the target controller to restart and activate the test firmware; a second sending module configured to generate a road test problem verification report and send it to the whole vehicle software development platform, the road test problem verification report being used to record whether the abnormal problems are solved, so that the whole vehicle software development platform records and stores the test firmware and its corresponding development information and the road test problem verification report.
7. The OBU software upgrade management apparatus of claim 5, wherein, The loading module comprises: a first processing unit configured to control the target controller to store the test firmware in a preset cache area; a second processing unit configured to, when the road test vehicle meets a preset upgrade condition, control the target controller to first back up and then erase the currently running old version firmware stored in a preset executable area through a boot loader, and then migrate the test firmware stored in the preset cache area to the preset executable area for storage.
8. The OBU software upgrade management apparatus of claim 7, wherein, The preset upgrade condition is met when the road test vehicle has a speed of zero, a power system of the road test vehicle is in a non-running state, and a power supply voltage of the road test vehicle is higher than a preset voltage threshold.
9. An electronic device, comprising: The electronic device includes a memory and a processor, the memory stores a computer program, and the processor implements the road test vehicle software upgrade management method of any one of claims 1 to 4 when executing the computer program.
10. A computer program product comprising a computer program, characterized in that, The computer program is executed by the processor to implement the road test vehicle software upgrade management method of any one of claims 1 to 4.