Firmware upgrade pressure test method and device, electronic equipment and storage medium

Abstract

The invention discloses a firmware upgrade pressure testing method and device, electronic equipment and a storage medium. The method comprises the following steps: determining firmware test information and pressure test times of a pressure test, and obtaining a firmware running state corresponding to the firmware test information; when the firmware running state meets the pressure test limiting condition, creating a firmware upgrading task based on the firmware test information; and performing firmware upgrading pressure testing on the target firmware in the test vehicle based on the firmware upgrading task and the pressure testing times. According to the technical scheme provided by the embodiment of the invention, the firmware test information and the pressure test times of the pressure test are determined, and the firmware running state corresponding to the firmware test information is obtained, so that the problems of incomplete coverage and fragmentation of storage of firmware test data can be solved; the firmware upgrade pressure test is performed on the target firmware in the test vehicle based on the firmware upgrade task and the pressure test frequency, so that full-automatic firmware upgrade pressure test can be realized, the test efficiency is remarkably improved, and the test cost is reduced.

Description

Technical Field

[0001] This invention relates to the field of intelligent connected vehicle technology, and in particular to a firmware upgrade stress test method, apparatus, electronic device, and storage medium. Background Technology

[0002] With the gradual development of intelligent connected vehicle technology, remote wireless upgrade technology has become a core means for firmware function iteration and system upgrades in vehicles. The transmission reliability and stability of this technology are directly related to vehicle operation safety and user experience. As the commercialization of driverless cars progresses, the firmware in vehicles needs to be updated frequently and on a large scale through remote wireless upgrade technology, which places stringent requirements on vehicle-to-cloud link data transmission, fault tolerance, and upgrade reliability.

[0003] Current mainstream stress testing methods for remote wireless upgrade technologies test the vehicle-to-cloud link by generating virtual vehicle nodes to simulate data transmission. However, the data transmission of these virtual vehicle nodes is mostly based on ideal conditions, resulting in low simulation accuracy of real-world upgrade scenarios and discrepancies between the test results and actual operating conditions, leading to low reliability of the results. Manual stress testing, on the other hand, is relatively reliable and flexible, capable of handling some non-standardized special scenarios. However, manual stress testing largely relies on operator experience, resulting in high testing costs and difficulty in achieving continuous, 24 / 7 upgrade testing. Therefore, how to construct an automated stress testing system that can simulate a real vehicle-to-cloud interaction environment and cover the entire remote wireless upgrade link has become a key technical problem urgently needing to be solved in this field. Summary of the Invention

[0004] This invention provides a firmware upgrade stress test method, apparatus, electronic device, and storage medium to solve the problems of low accuracy and high cost in firmware upgrade stress testing.

[0005] According to one aspect of the present invention, a firmware upgrade stress test method is provided, the method comprising:

[0006] Determine the firmware test information and number of stress tests for the stress test, and obtain the firmware running status corresponding to the firmware test information;

[0007] When the firmware running state meets the stress test limits, a firmware upgrade task is created based on the firmware test information;

[0008] Based on the firmware upgrade task and the number of stress tests, a firmware upgrade stress test is performed on the target firmware in the test vehicle.

[0009] According to another aspect of the present invention, a firmware upgrade stress testing apparatus is provided, the apparatus comprising:

[0010] The information determination module is used to determine the firmware test information and the number of stress tests for stress testing, and to obtain the firmware running status corresponding to the firmware test information.

[0011] The task creation module is used to create a firmware upgrade task based on the firmware test information when the firmware running state meets the stress test limit conditions.

[0012] The stress testing module is used to perform a firmware upgrade stress test on the target firmware in the test vehicle based on the firmware upgrade task and the number of stress tests.

[0013] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:

[0014] At least one processor; and

[0015] A memory communicatively connected to the at least one processor; wherein,

[0016] The memory stores a computer program that can be executed by the at least one processor, which enables the at least one processor to perform the firmware upgrade stress test method according to any embodiment of the present invention.

[0017] According to another aspect of the present invention, a computer-readable storage medium is provided, the computer-readable storage medium storing computer instructions for causing a processor to execute the firmware upgrade stress test method described in any embodiment of the present invention.

[0018] The technical solution of this invention determines the firmware test information and the number of stress tests, and obtains the firmware running status corresponding to the firmware test information. Then, when the firmware running status meets the stress test constraints, a firmware upgrade task is created based on the firmware test information. Finally, a firmware upgrade stress test is performed on the target firmware in the test vehicle based on the firmware upgrade task and the number of stress tests. This technical solution, by determining the firmware test information and the number of stress tests, and obtaining the firmware running status corresponding to the firmware test information, can solve the problems of incomplete firmware test data coverage and fragmented storage. By performing a firmware upgrade stress test on the target firmware in the test vehicle based on the firmware upgrade task and the number of stress tests, fully automated firmware upgrade stress testing can be achieved, resulting in improved firmware upgrade stress testing efficiency and reduced firmware upgrade stress testing costs.

[0019] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0020] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0021] Figure 1 This is a flowchart of a firmware upgrade stress test method provided in Embodiment 1 of the present invention;

[0022] Figure 2 This is a flowchart of another firmware upgrade stress test method provided in Embodiment 2 of the present invention;

[0023] Figure 3 This is a flowchart of a firmware upgrade stress test method provided in Embodiment 3 of the present invention;

[0024] Figure 4 This is a flowchart of another firmware upgrade stress test method provided in Embodiment 3 of the present invention;

[0025] Figure 5 This is a schematic diagram of a firmware upgrade stress testing device according to Embodiment 4 of the present invention;

[0026] Figure 6 This is a schematic diagram of the structure of an electronic device that implements the firmware upgrade stress test method of Embodiment 5 of the present invention. Detailed Implementation

[0027] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0028] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention 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 the invention 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, system, product, or apparatus 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 apparatus.

[0029] Example 1

[0030] Figure 1 This is a flowchart of a firmware upgrade stress testing method provided in Embodiment 1 of the present invention. This embodiment is applicable to situations where firmware upgrade stress testing is performed automatically. The method can be executed by a firmware upgrade stress testing device, which can be implemented in hardware and / or software and can be configured in an electronic device. Figure 1 As shown, the method includes:

[0031] S110. Determine the firmware test information and number of stress tests for the stress test, and obtain the firmware running status corresponding to the firmware test information.

[0032] Stress testing refers to a testing method that verifies the stability of firmware upgrades by repeatedly testing the target firmware on a target vehicle. Firmware test information refers to a set of parameter information describing the basic attributes and test conditions of the target firmware, which originates from the target vehicle and the target firmware. The number of stress tests refers to the number of times the stress test is repeatedly performed on the target firmware; this number is pre-set based on information such as the target vehicle's weight, model, and firmware model. Firmware operating status refers to a set of data reflecting the real-time performance of the target firmware, which may include vehicle attributes, online status, firmware type information, and supplier information.

[0033] Specifically, before performing stress testing on the target firmware of the target vehicle, the system obtains the firmware test information and the number of stress tests input by the user, and collects the firmware operation status data corresponding to the firmware test information in real time. The firmware test information includes at least the information of the target vehicle and the target firmware. The number of stress tests is preset manually based on information such as the weight of the target vehicle, the model of the target vehicle, and the model of the target firmware. The firmware operation status includes the vehicle attributes of the target vehicle, the online status of the target vehicle, the type information of the target firmware, and the supplier information of the target firmware. The real-time collection of firmware test information can be achieved through methods such as direct bus connection or cloud relay.

[0034] S120. When the firmware running status meets the stress test limit conditions, create a firmware upgrade task based on the firmware test information.

[0035] Among them, stress testing constraints refer to a pre-defined set of conditions used to determine whether the firmware is qualified to perform an upgrade operation. These constraints may include vehicle attribute constraints, online status constraints, type information constraints, and supplier information constraints. A firmware upgrade task refers to a planned unit created for the target firmware, containing specific upgrade content and execution instructions. Firmware upgrade tasks may include target firmware version upgrades, target firmware parameter and configuration updates, and may include upgrade verification strategies used during task execution, upgrade task priority information, etc.

[0036] Specifically, the system collects firmware running status data corresponding to firmware test information in real time through direct bus connection or cloud relay. It then compares the firmware running status with the pre-set stress test limits. If all data indicators corresponding to the firmware running status meet the stress test limits, the system creates the corresponding firmware upgrade task based on the firmware test information. If any data indicator corresponding to the firmware running status does not meet the stress test limits, the system terminates the current stress test task.

[0037] S130. Based on the firmware upgrade task and the number of stress tests, perform firmware upgrade stress tests on the target firmware in the test vehicle.

[0038] In this context, "test vehicle" refers to a physical vehicle equipped with the firmware. "Target firmware" refers to the firmware installed in the test vehicle to be subjected to stress testing. "Firmware upgrade stress testing" refers to the process of repeatedly performing firmware upgrades in a real vehicle operating environment according to a pre-set number of stress tests. Firmware upgrade refers to the upgrade operation performed according to the firmware upgrade task created by the system.

[0039] Specifically, a firmware upgrade stress test is performed on the target firmware in the test vehicle according to the firmware upgrade task. During the firmware upgrade process, relevant information of the target firmware and the firmware upgrade results are collected. The firmware upgrade stress test is repeated a predetermined number of times. After the target firmware in the test vehicle completes one firmware upgrade, the execution status of the firmware upgrade task is recorded, and the task execution count is incremented by one. This process is repeated again until the number of firmware upgrades meets the predetermined number of stress tests.

[0040] The technical solution of this invention determines the firmware test information and the number of stress tests, and obtains the firmware running status corresponding to the firmware test information. Then, when the firmware running status meets the stress test constraints, a firmware upgrade task is created based on the firmware test information. Finally, a firmware upgrade stress test is performed on the target firmware in the test vehicle based on the firmware upgrade task and the number of stress tests. This technical solution, by determining the firmware test information and the number of stress tests, and obtaining the firmware running status corresponding to the firmware test information, can solve the problems of incomplete firmware test data coverage and fragmented storage. By performing a firmware upgrade stress test on the target firmware in the test vehicle based on the firmware upgrade task and the number of stress tests, fully automated firmware upgrade stress testing can be achieved, significantly improving testing efficiency and reducing testing costs.

[0041] Example 2

[0042] Figure 2 This is a flowchart of a firmware upgrade stress test method provided in Embodiment 2 of the present invention. This embodiment further refines the above embodiment:

[0043] like Figure 2 As shown, the method includes:

[0044] S210. Obtain the firmware test information and number of stress tests input by the user, wherein the firmware test information includes at least the information of the target vehicle and the target firmware.

[0045] Firmware test information refers to a set of parameter information describing the basic attributes and test conditions of the target firmware. This firmware test information includes at least information about the target vehicle and the target firmware. The target vehicle refers to the physical vehicle equipped with the firmware. The target firmware refers to the firmware installed in the target vehicle and intended for stress testing.

[0046] In this embodiment of the invention, the system can receive user-inputted firmware test information and load test counts. The firmware test information includes at least information indicating the target vehicle and target firmware used for the firmware upgrade stress test. For example, the firmware test information may include the vehicle model of the target vehicle and the firmware identifier of the target firmware. The user can input the firmware test information and load test counts through a visual interface or voice input. For instance, the user can access the system's graphical user interface (GUI) to input the firmware test information and load test counts. The system then obtains the user-input firmware test information and load test counts through the GUI for subsequent execution of the corresponding firmware upgrade stress test based on this information.

[0047] S220: Collect vehicle attributes and online status of the target vehicle, as well as type and supplier information of the target firmware, from the preset server as the firmware running status.

[0048] The preset server refers to a remote or local server that stores and manages data related to the target vehicle and its firmware. This server may include a vehicle cloud platform, firmware management server, etc. Vehicle attributes refer to a set of data reflecting the characteristics of the target vehicle, including vehicle model information, production year, vehicle weight, hardware configuration version, and chassis structure information. Online status refers to the real-time connection status between the target vehicle and the preset server, including connection success, connection interruption, signal strength, initial connection time, and online duration. Type information refers to a set of data describing the characteristics of the target firmware, including supplier information, model information, and compatible hardware interface protocols. Supplier information refers to information about the manufacturer and supplier of the target firmware.

[0049] Specifically, based on the target vehicle and target firmware information input by the user in the firmware test information, the system sends a request to the preset server to collect the vehicle attributes, online status, target firmware type information, and supplier information of the target vehicle. After receiving the data collection request from the system, the preset server queries the vehicle attributes, online status, target firmware type information, and supplier information of the target vehicle in sequence, and returns the retrieved data to the system. The system then processes and integrates this data to form the firmware running status.

[0050] S230. Match the vehicle attributes, online status, type information, and supplier information of the firmware running status with the standard parameters of the stress test constraints.

[0051] The load testing constraints refer to a pre-defined set of conditions used to determine whether the firmware is qualified to perform an upgrade operation. These constraints may include vehicle attribute constraints, online status constraints, type information constraints, and supplier information constraints. Standard parameters refer to the minimum thresholds or requirements that must be met to satisfy the load testing constraints. These parameters may include a whitelist of vehicle models and hardware configurations corresponding to vehicle attributes, minimum online status requirements, a whitelist of target firmware models and hardware interface protocols corresponding to type information, and a supplier whitelist.

[0052] For example, the system matches the vehicle attributes of the firmware running status with the vehicle attribute restrictions in the preset stress test restrictions; matches the online status of the firmware running status with the online status restrictions in the preset stress test restrictions; matches the type information of the firmware running status with the type information restrictions in the preset stress test restrictions; and matches the supplier information of the firmware running status with the supplier information restrictions in the preset stress test restrictions, thereby obtaining the matching results of the vehicle attributes, online status, type information, and supplier information of the firmware running status with the standard parameters of the stress test restrictions.

[0053] S240. If the vehicle attributes, online status, type information, and supplier information meet the standard parameters, then create a firmware upgrade task on the preset test server according to the target firmware in the firmware test information.

[0054] Specifically, if all matching results obtained after matching vehicle attributes, online status, type information, and supplier information with the stress test constraints are either passed or meet the requirements, then the corresponding firmware upgrade task configuration parameters are generated based on the firmware test information. Subsequently, the system calls the application programming interface of the preset test server to create a corresponding firmware upgrade task for the target firmware based on the firmware task configuration parameters. The firmware upgrade task configuration parameters include firmware core data and upgrade configuration data.

[0055] S250 performs firmware upgrade stress tests on the target firmware in the test vehicle based on the firmware upgrade task and the number of stress tests.

[0056] In this context, "test vehicle" refers to a physical vehicle equipped with the stress test task to be performed. "Target firmware" refers to the firmware installed in the test vehicle to be subjected to the stress test task. "Firmware upgrade stress test" refers to the test process of repeatedly performing firmware upgrades in a simulated or real vehicle operating environment according to a pre-set number of stress tests. "Firmware upgrade" refers to the upgrade operation performed according to the firmware upgrade task created by the system.

[0057] Specifically, a firmware upgrade stress test is performed on the target firmware in the test vehicle according to the firmware upgrade task. The firmware upgrade stress test is repeated a predetermined number of times. After the target firmware in the test vehicle completes one firmware upgrade, the execution status of the firmware upgrade task is recorded, and the task execution count is incremented by one. This process is repeated again until the number of firmware upgrades meets the predetermined number of stress tests.

[0058] The technical solution of this invention obtains firmware test information and the number of stress tests input by the user. The firmware test information includes at least information about the target vehicle and the target firmware. Then, the vehicle attributes and online status of the target vehicle, as well as the type and supplier information of the target firmware, are collected on a preset server as the firmware running status. The vehicle attributes, online status, type information, and supplier information of the firmware running status are matched with standard parameters of the stress test constraints. If the vehicle attributes, online status, type information, and supplier information meet the standard parameters, a firmware upgrade task is created on the preset test server according to the target firmware in the firmware test information. Finally, a firmware upgrade stress test is performed on the target firmware in the test vehicle based on the firmware upgrade task and the number of stress tests. This technical solution, by obtaining the firmware test information and the number of stress tests input by the user, can solve the problem of incomplete firmware test data coverage. By determining that the vehicle attributes, online status, type information, and supplier information meet the standard parameters, and by creating a firmware upgrade task on the preset test server according to the target firmware in the firmware test information and performing a firmware upgrade stress test on the target firmware in the test vehicle based on the firmware upgrade task and the number of stress tests, fully automated firmware upgrade stress testing can be achieved, significantly improving testing efficiency and reducing testing costs.

[0059] Furthermore, based on the above embodiments of the invention, determining the firmware test information and the number of stress tests for the stress test, and obtaining the firmware running status corresponding to the firmware test information, further includes:

[0060] If the target vehicle is determined to be offline, then the target vehicle is woken up.

[0061] "Offline" refers to a state where the connection between the target vehicle and the preset server is interrupted or unresponsive. "Wake-up" refers to sending a signal to the target vehicle to restore its connection with the preset server and put it into a ready-to-test state that can respond to commands. This signal can include network wake-up commands, radio frequency signals, vehicle networking service requests, etc.

[0062] Specifically, while the system acquires the firmware running status corresponding to the firmware information, it sends a status query command to a preset server to query the online status of the target vehicle. Upon receiving the query command, the preset server queries the online status of the target vehicle and returns the result to the system. When the system detects that the target vehicle is offline, the system or server can send a signal to the target vehicle to restore its connection with the preset server and place it in a ready-to-test state, capable of responding to commands. This signal can include a wake-up call command, radio frequency signals, or vehicle networking service requests.

[0063] Furthermore, based on the above embodiments, creating a firmware upgrade task on a preset test server according to the target firmware of the firmware test information further includes:

[0064] Locate the core firmware data and upgrade configuration data that match the target firmware within the preset test server;

[0065] The preset test server is controlled to encapsulate the firmware core data and upgrade configuration data into a firmware upgrade task.

[0066] Firmware core data refers to the basic data set of the firmware itself, which may include program entity data, digital signatures, firmware version identifiers, etc. Upgrade configuration data refers to the set of parameters that guide the firmware upgrade, which may include firmware version number, automation script configuration, security authentication key, post-upgrade verification script path, etc.

[0067] Specifically, when creating a firmware upgrade task based on firmware test information, the system sends a data query instruction and a packaging task instruction to the preset server. After receiving the data query instruction and the packaging task instruction, the preset server queries the database for firmware core data and upgrade configuration data that match the target firmware, and packages the obtained firmware core data and upgrade configuration data that match the target firmware into a firmware upgrade task.

[0068] Furthermore, based on the above embodiments of the invention, a firmware upgrade stress test is performed on the target firmware in the test vehicle based on the firmware upgrade task and the number of stress tests, including:

[0069] Initialize the number of times the firmware upgrade task is executed; call the firmware upgrade task to upgrade the firmware device corresponding to the firmware test information; if the firmware device completes the firmware upgrade, record the execution status of the firmware upgrade task and increment the task execution count by 1. The execution status includes at least the task name, task start time, task end time, and upgrade time; determine whether the number of task executions meets the stress test count. If yes, end the firmware upgrade stress test; otherwise, return to call the firmware upgrade task to upgrade the firmware device corresponding to the firmware test information.

[0070] The task execution count refers to the number of firmware upgrade operations that have been performed so far, with an initial value set to 0. The firmware device refers to the hardware module in the target vehicle that carries the target firmware.

[0071] Specifically, the system sets the firmware upgrade task execution count to 0, and then calls the instructions and data encapsulated in the firmware upgrade task to upgrade the firmware device corresponding to the firmware test information. When the system receives an upgrade success confirmation signal from the firmware device or determines through the verification mechanism that the upgrade has been completed, it considers this round of firmware upgrade task execution to be completed, increments the task execution count by one, and checks whether the task execution count meets the preset stress test count. If it does, the firmware upgrade stress test ends; if not, it returns and continues to call the firmware upgrade task to upgrade the firmware device corresponding to the firmware test information until the task execution count meets the preset stress test count.

[0072] Furthermore, based on the above embodiments, the invention also includes:

[0073] If the duration of a firmware upgrade task exceeds a threshold time, the execution of the current firmware upgrade task will be terminated.

[0074] The task duration refers to the time elapsed from the start of the firmware upgrade task to the current moment. The threshold time refers to the pre-set maximum allowed execution time for a single firmware upgrade task.

[0075] Specifically, during the firmware upgrade process, the system will activate the time monitoring module to monitor the execution duration of the task in real time. Once the execution duration of the firmware upgrade task exceeds the preset threshold time, the time monitoring module will send an instruction to the system to terminate the current firmware upgrade task. After receiving the instruction to terminate the current firmware upgrade task, the system will terminate the current firmware upgrade task and record the task as a failure. The time monitoring module refers to the timing module that can receive and send tasks.

[0076] Example 3

[0077] Figure 3 This is a flowchart of a firmware upgrade stress test method provided in Embodiment 3 of the present invention.

[0078] For details, see Figure 3 The project flowchart of the firmware upgrade stress test method described in this embodiment mainly consists of three parts: method encapsulation module, result storage directory, and upgrade execution program. The specific contents are as follows:

[0079] The method encapsulation module comprises two parts: platform function encapsulation and action execution encapsulation. Platform function encapsulation includes user classes and operation / maintenance classes, while action execution encapsulation includes business classes. Specifically, the user class contains methods for obtaining user authorization information; the operation / maintenance class contains methods for querying vehicle information, querying vehicle status, creating remote wireless upgrade tasks, querying remote wireless upgrade task information, publishing remote wireless upgrade tasks, and remotely waking up vehicles; and the business class contains methods for determining vehicle existence, determining vehicle online status, remote power-on operation and vehicle status detection, determining task creation results, determining remote wireless upgrade task publishing results, remote wireless upgrade task creation, publishing and detection, obtaining task execution status, monitoring remote wireless upgrade task status, and generating and storing test result files. The methods for determining vehicle existence consist of a method for querying vehicle information; the method for determining vehicle online status consists of a method for querying vehicle status and a method for determining vehicle existence; the method for remote power-on operation and vehicle status detection consists of a method for remote vehicle wake-up and a method for determining vehicle online status; the method for determining task creation results consists of a method for querying remote wireless upgrade task information; the method for determining remote wireless upgrade task publication results consists of a method for querying remote wireless upgrade task information; the method for remote wireless upgrade task creation, publication, and detection consists of a method for creating a remote wireless upgrade task, a method for determining task creation results, a method for publishing a remote wireless upgrade task, and a method for determining remote wireless upgrade task publication results; the method for obtaining task execution status consists of a method for querying remote wireless upgrade task information; and the method for monitoring remote wireless upgrade task status consists of a method for obtaining task execution status.

[0080] The results storage directory is the location where the test results files of the firmware upgrade stress test are stored. The upgrade execution program is a firmware upgrade stress test program executed on the target firmware after determining that the vehicle identification, the type of electronic control unit under test, the number of target stress tests meet the upgrade conditions, and the vehicle itself meets the upgrade conditions. The upgrade execution program includes two types: electronic control unit upgrade programs that do not require power-off and electronic control unit upgrade programs that require power-off.

[0081] Figure 4 This is a flowchart of another firmware upgrade stress test method provided in Embodiment 3 of the present invention.

[0082] For details, see Figure 4 The firmware upgrade stress test method described in this embodiment mainly consists of four parts: upgrade condition check process, vehicle condition check process, cyclic upgrade and monitoring process, and stress test record storage process. The specific contents are as follows:

[0083] S310, Upgrade Condition Check Process.

[0084] When running the upgrade condition check process, the firmware upgrade stress test program receives three parameters as input: vehicle identification, type of electronic control unit (ECU) under test, and target number of stress tests. Based on the received ECU type, the program determines whether the specified ECU supports remote wireless upgrades. If the result indicates support, the process continues; otherwise, it exits and outputs an error through the log module. Furthermore, the same ECU type may be provided by multiple vendors, and a single vendor may provide different models of the same type of ECU. Therefore, after selecting the vendor, the ECU device model must be selected for receiving the matching test firmware in the method for creating the remote wireless upgrade task.

[0085] S320, Vehicle Condition Inspection Procedure.

[0086] When running the vehicle condition check process, a method to determine vehicle existence is called. Based on the received vehicle identifier parameters, it determines whether the vehicle exists in the cloud. If it exists, the process continues; otherwise, the program exits and an error is output through the log module. The next step is to call a method to determine vehicle online status, again based on the received vehicle identifier parameters. If the vehicle is online, the process continues; otherwise, a remote power-on operation and vehicle status detection method is called to attempt to wake up the vehicle. The remote power-on operation and vehicle status detection method includes logic to verify the vehicle wake-up result. If the wake-up is successful, the process continues; otherwise, the program exits / the stress test ends and an error is output through the log module. Specifically, if it's the first check, the program exits; otherwise, if it's a subsequent check, the stress test ends and an error is output through the log module.

[0087] S330, cyclical upgrade and monitoring process.

[0088] During the cyclical upgrade and monitoring process, the remote wireless upgrade task creation, publishing, and detection method is invoked. This method creates a remote wireless upgrade task in the cloud based on the vehicle identifier received by the program and the electronic control unit device type selected in the upgrade condition check process. Additionally, the remote wireless upgrade task creation, publishing, and detection method includes a judgment on the creation and publishing results. If it is determined that all operations have been completed, the process continues; otherwise, the program exits / the stress test ends, and errors are output through the log module. Specifically, if it is the first check, the program exits; if it is not the first check, the stress test ends, and errors are output through the log module.

[0089] During the cyclical upgrade and monitoring process, the system also calls a method to monitor the remote wireless upgrade task status in real time. When the task's execution status changes from running to any completed state, the process continues. Conversely, if the task remains in the running state for an extended period, the program exits / the load test ends, and an error is output through the log module. "Extended period" refers to a pre-set waiting time based on the load test type and the target device's parameters. If it's the first check, the program exits; otherwise, it ends the load test and outputs an error through the log module. Furthermore, the program determines whether the current load test count has reached the target number. If not, it jumps to the vehicle condition check process to begin the next upgrade; otherwise, the process continues.

[0090] In addition, the program will temporarily store the information of this upgrade task when running the cyclic upgrade and monitoring process. The information of the upgrade task can include the task name, task start time, end time, upgrade time, upgrade result, etc. The information of the upgrade task can be customized according to actual needs. The end time is mainly used to define the log time when the upgrade fails. The upgrade time is mainly used to locate the excessively long time-consuming task for subsequent analysis.

[0091] S340, stress test record saving process.

[0092] When running the load test record saving process, the test result file generation and storage method is called to generate a load test result file in the storage directory, and all the load test information stored in the loop upgrade and monitoring process is written into the load test result file.

[0093] The technical solution of this invention can determine whether the firmware of the vehicle under test meets the firmware upgrade conditions through the upgrade condition check process; it can also determine whether the vehicle under test meets the firmware upgrade conditions through the vehicle condition check process; it can achieve fully automated firmware upgrade stress testing through the cyclic upgrade and monitoring process, significantly improving testing efficiency and reducing testing costs; and it can solve the problems of incomplete firmware test data coverage and fragmented storage through the stress test record saving process.

[0094] Example 4

[0095] Figure 5 This is a schematic diagram of a firmware upgrade stress testing device provided in Embodiment 4 of the present invention. Figure 5 As shown, the device includes: an information determination module 510, a task creation module 520, and a stress testing module 530, wherein,

[0096] The information determination module 510 is used to determine the firmware test information and the number of stress tests for stress testing, and to obtain the firmware running status corresponding to the firmware test information.

[0097] The task creation module 520 is used to create a firmware upgrade task based on firmware test information when the firmware running state meets the stress test limit conditions.

[0098] The stress test module 530 is used to perform firmware upgrade stress tests on the target firmware in the test vehicle based on the firmware upgrade task and the number of stress tests.

[0099] The technical solution of this invention involves an information determination module that determines the firmware test information and the number of stress tests for stress testing and obtains the firmware running status corresponding to the firmware test information. Then, a task creation module creates a firmware upgrade task based on the firmware test information when the firmware running status meets the stress test constraints. Finally, a stress test module performs a firmware upgrade stress test on the target firmware in the test vehicle based on the firmware upgrade task and the number of stress tests. This technical solution, by determining the firmware test information and the number of stress tests for stress testing and obtaining the firmware running status corresponding to the firmware test information, can solve the problems of incomplete firmware test data coverage and fragmented storage. By performing a firmware upgrade stress test on the target firmware in the test vehicle based on the firmware upgrade task and the number of stress tests, fully automated firmware upgrade stress testing can be achieved, significantly improving testing efficiency and reducing testing costs.

[0100] Optionally, the information determination module 510 is specifically used for:

[0101] Determine the firmware test information and number of stress tests, and obtain the firmware running status corresponding to the firmware test information.

[0102] Optionally, determine the firmware test information and the number of stress tests, and obtain the firmware running status corresponding to the firmware test information, including:

[0103] Obtain the firmware test information and number of load tests input by the user. The firmware test information shall include at least the information of the target vehicle and the target firmware.

[0104] The system collects vehicle attributes and online status of the target vehicle, as well as type and supplier information of the target firmware, from a preset server to determine the firmware's running status.

[0105] Optionally, determining the firmware test information and the number of stress tests, and obtaining the firmware running status corresponding to the firmware test information, also includes:

[0106] If the target vehicle is determined to be offline, then the target vehicle is woken up.

[0107] Optional, task creation module 520, specifically used for:

[0108] When the firmware's running status meets the load testing limits, a firmware upgrade task is created based on the firmware test information.

[0109] Optionally, when the firmware's running state meets the load testing limitations, a firmware upgrade task is created based on the firmware test information, including:

[0110] Match the vehicle attributes, online status, type information, and supplier information of the firmware running status with the standard parameters of the stress test limits;

[0111] If the vehicle attributes, online status, type information, and supplier information are confirmed to meet the standard parameters, then a firmware upgrade task is created on the preset test server according to the target firmware in the firmware test information.

[0112] Optional, stress testing module 530, specifically used for:

[0113] Firmware upgrade stress tests are performed on the target firmware in the test vehicle based on the firmware upgrade task and the number of stress tests.

[0114] Optionally, a firmware upgrade stress test is performed on the target firmware in the test vehicle based on the firmware upgrade task and the number of stress tests, including:

[0115] Initialize the number of times the firmware upgrade task will be executed;

[0116] Invoke the firmware upgrade task to upgrade the firmware of the device corresponding to the firmware test information;

[0117] Once the firmware device has completed the firmware upgrade, record the execution status of the firmware upgrade task and increment the task execution count by 1. The execution status includes at least the task name, task start time, task end time, and upgrade time.

[0118] Determine if the number of task executions meets the load test limit. If yes, end the firmware upgrade load test. Otherwise, return to call the firmware upgrade task to upgrade the firmware device corresponding to the firmware test information.

[0119] Furthermore, based on the above embodiments of the invention, a firmware upgrade task is created on a preset test server according to the target firmware of the firmware test information, including:

[0120] Locate the core firmware data and upgrade configuration data that match the target firmware within the preset test server;

[0121] The preset test server is controlled to encapsulate the firmware core data and upgrade configuration data into a firmware upgrade task.

[0122] Furthermore, based on the above embodiments, the invention also includes:

[0123] If the duration of a firmware upgrade task exceeds a threshold time, the execution of the current firmware upgrade task will be terminated.

[0124] The firmware upgrade stress testing device provided in this embodiment of the invention can execute the firmware upgrade stress testing method provided in any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the method.

[0125] Example 5

[0126] Figure 6 A schematic diagram of an electronic device 10, which can be used to implement embodiments of the present invention, is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0127] like Figure 6 As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded from storage unit 18 into the RAM 13. The RAM 13 can also store various programs and data required for the operation of the electronic device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0128] Multiple components in electronic device 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0129] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as firmware upgrade stress testing methods.

[0130] In some embodiments, the firmware upgrade stress testing method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on electronic device 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the firmware upgrade stress testing method described above may be performed. Alternatively, in other embodiments, processor 11 may be configured to perform the firmware upgrade stress testing method by any other suitable means (e.g., by means of firmware).

[0131] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0132] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0133] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0134] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0135] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or middleware components (e.g., application servers), or frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0136] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0137] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0138] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A firmware upgrade stress test method, characterized in that, The method includes: Determine the firmware test information and number of stress tests for the stress test, and obtain the firmware running status corresponding to the firmware test information; When the firmware running state meets the stress test limits, a firmware upgrade task is created based on the firmware test information; Based on the firmware upgrade task and the number of stress tests, a firmware upgrade stress test is performed on the target firmware in the test vehicle.

2. The method according to claim 1, characterized in that, The process of determining the firmware test information and the number of stress tests, and obtaining the firmware running status corresponding to the firmware test information, includes: Obtain the firmware test information and the number of stress tests input by the user, wherein the firmware test information includes at least information about the target vehicle and the target firmware; The target vehicle's vehicle attributes and online status, as well as the target firmware's type and supplier information, are collected from a preset server as the firmware's running status.

3. The method according to claim 2, characterized in that, Also includes: If the target vehicle is determined to be offline, then the target vehicle is woken up.

4. The method according to claim 1, characterized in that, When the firmware running state meets the stress test limitations, creating a firmware upgrade task based on the firmware test information includes: The vehicle attributes, online status, type information, and supplier information of the firmware running state are matched with the standard parameters of the stress test limiting conditions, respectively. If the vehicle attributes, online status, type information, and supplier information are determined to conform to the standard parameters, then the firmware upgrade task is created on the preset test server according to the target firmware of the firmware test information.

5. The method according to claim 4, characterized in that, The step of creating the firmware upgrade task on a preset test server according to the target firmware based on the firmware test information includes: Locate the firmware core data and upgrade configuration data that match the target firmware within the preset test server; The preset test server is controlled to encapsulate the firmware core data and the upgrade configuration data into the firmware upgrade task.

6. The method according to claim 1, characterized in that, The firmware upgrade stress test performed on the target firmware in the test vehicle based on the firmware upgrade task and the number of stress tests includes: Initialize the number of times the firmware upgrade task is executed; The firmware upgrade task is invoked to upgrade the firmware device corresponding to the firmware test information. Once it is determined that the firmware device has completed the firmware upgrade, the execution status of the firmware upgrade task is recorded, and the task execution count is incremented by 1. The execution status includes at least the task name, task start time, task end time, and upgrade time. Determine whether the number of times the task is executed meets the number of stress tests. If yes, end the firmware upgrade stress test. If not, return to call the firmware upgrade task to upgrade the firmware device corresponding to the firmware test information.

7. The method according to claim 1 or 6, characterized in that, Also includes: If the duration of the firmware upgrade task exceeds a threshold time, the execution of the current firmware upgrade task will be terminated.

8. A firmware upgrade stress testing device, characterized in that, The device includes: The information determination module is used to determine the firmware test information and the number of stress tests for stress testing, and to obtain the firmware running status corresponding to the firmware test information. The task creation module is used to create a firmware upgrade task based on the firmware test information when the firmware running state meets the stress test limit conditions. The stress testing module is used to perform a firmware upgrade stress test on the target firmware in the test vehicle based on the firmware upgrade task and the number of stress tests.

9. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the firmware upgrade stress test method according to any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions for causing a processor to execute the firmware upgrade stress test method according to any one of claims 1-7.

Images