Power-off test method, system and related device for head unit upgrade

Abstract

The application discloses a power-off test method and system for vehicle machine upgrading and related equipment, and relates to the field of vehicle simulation test, and mainly aims to solve the problem that the existing power-off test method for vehicle upgrading relies on manual intervention and has low automation degree. The method comprises the following steps: monitoring a to-be-tested vehicle machine to generate an execution log under the condition that the to-be-tested vehicle machine executes an upgrading task; generating a power-off instruction under the condition that an upgrading stage corresponding to the execution log is a target stage, wherein the target stage is determined based on a power-off test node of the to-be-tested vehicle machine under the condition of upgrading, and the power-off test node comprises trigger time information of the power-off test; and controlling the disconnection of a relay of the to-be-tested vehicle machine based on the power-off instruction, wherein the disconnection of the relay is used for controlling the power-off of the to-be-tested vehicle machine.

Description

Technical Field

[0001] This invention relates to the field of vehicle simulation testing, and in particular to a power-off testing method, system, and related equipment for vehicle infotainment system upgrades. Background Technology

[0002] In the current development of automotive intelligence, the complexity of in-vehicle infotainment systems is increasing, and firmware upgrades via over-the-air (OTA) have become a core means to ensure continuous vehicle optimization and functional iteration. However, the reliability of the upgrade process, especially its self-recovery capability in the event of unexpected power outages or other abnormal situations, directly affects the vehicle's functional safety and user experience. This makes testing for power outage anomalies an indispensable verification step. While some existing technologies use software testing scenarios or inject simulated anomalies, these methods heavily rely on manual intervention. Not only do they require manually triggering simulated faults at key points, but they also require manual verification of device status and version information after testing to confirm the recovery result. The entire process is inefficient, error-prone, and difficult to automate. Summary of the Invention

[0003] In view of the above problems, the present invention provides a power-off testing method, system and related equipment for vehicle system upgrades, the main purpose of which is to solve the problem that the existing power-off testing methods for vehicle upgrades rely on manual intervention and have a low degree of automation.

[0004] To address at least one of the aforementioned technical problems, in a first aspect, the present invention provides a power-off test for vehicle infotainment system upgrades. method The method includes: When the vehicle-mounted system under test is performing an upgrade task, the system is monitored to generate an execution log; If the upgrade stage corresponding to the execution log is the target stage, a power-off command is generated. The target stage is determined based on the power-off test node of the vehicle under test during the upgrade. The power-off test node includes the trigger time information of the power-off test. The relay of the vehicle under test is disconnected based on the power-off command, wherein the disconnection of the relay is used to control the power-off of the vehicle under test.

[0005] Optionally, when the vehicle-mounted unit under test is performing an upgrade task, monitoring the vehicle-mounted unit under test to generate an execution log includes: Based on the power outage test requirements input by the user, the upgrade task of the vehicle system under test and the power outage test process when executing the upgrade task are determined. When the vehicle-mounted system under test performs the upgrade task, the system generates the execution log.

[0006] Optionally, if the upgrade stage corresponding to the execution log is the target stage, generating a power-off command includes: The execution logs are analyzed to determine the search keywords; The upgrade stage is determined based on the search keywords; When the upgrade phase is in the power-off test node, the power-off command is generated.

[0007] Optionally, the upgrade task is divided into different upgrade stages, and the method further includes: Select a preset power outage triggering stage from the upgrade stage. Each preset power outage triggering stage corresponds to a power outage time ratio. The power outage time ratio is used to control the host module to trigger the power outage test node corresponding to the power outage command within the current preset power outage triggering stage.

[0008] Optionally, the above methods also include: When the relay is cut off to control the power-off of the vehicle unit under test for a preset duration, a power-on command is generated. The relay is closed based on the power-on command to control the power-on restart of the vehicle's infotainment system under test.

[0009] Optionally, the above methods also include: When the vehicle-mounted system under test is powered on and restarted, the current execution status of the upgrade task of the vehicle-mounted system under test is determined based on the execution log, wherein the current execution status includes rolling back the version and continuing the upgrade; Obtain the current version number of the vehicle infotainment system under test; The verification result of the power outage test is determined based on the comparison between the current execution status of the upgrade task and the current version number.

[0010] Optionally, the power-off test nodes of the vehicle-mounted system under test include a download stage, a verification stage, and a flashing stage. The verification result of the power-off test is determined based on a comparison between the current execution status of the upgrade task and the current version number, including: If the power-off test node of the vehicle's infotainment system under test is in the download or verification phase, and the current version number corresponds to the version number of the rollback version, then the rollback result of the power-off test is determined to be successful. If the power-off test node of the vehicle's infotainment system under test is the flashing stage, and the current version number corresponds to the version number of the rollback version, then the rollback result of the power-off test is determined to be successful. If the power-off test node of the vehicle's infotainment system under test is the flashing stage, and the current version number corresponds to the version number to be upgraded, then the upgrade result of the power-off test is determined to be successful.

[0011] Secondly, embodiments of the present invention also provide a power failure testing system for vehicle infotainment system upgrades, comprising: The log monitoring module is used to monitor the vehicle under test and generate execution logs when the vehicle under test performs an upgrade task. The host module is used to generate a power-off command when the upgrade stage corresponding to the execution log is the target stage; The programmable power supply module is used to control the relay of the vehicle under test to disconnect based on the power-off command.

[0012] To achieve the above objectives, according to a third aspect of the present invention, a computer-readable storage medium is provided, the computer-readable storage medium comprising a stored program, wherein, when the program is executed by a processor, the steps of the above-described power-off test method for vehicle system upgrade are implemented.

[0013] To achieve the above objectives, according to a fourth aspect of the present invention, an electronic device is provided, including at least one processor and at least one memory connected to the processor; wherein the processor is configured to call program instructions in the memory to execute the steps of the above-described power-off test method for vehicle system upgrade.

[0014] By employing the above technical solution, the power-off testing method, system, and related equipment for vehicle infotainment system upgrades provided by this invention address the problem of over-reliance on intelligent electronic devices for power-off testing of vehicle infotainment system upgrades. This invention monitors the vehicle infotainment system under test (VMS) to generate an execution log while it is performing an upgrade task; if the upgrade stage corresponding to the execution log is a target stage, a power-off command is generated. The target stage is determined based on the power-off test node of the VMS under test during the upgrade process, and the power-off test node includes the trigger time information of the power-off test. Based on the power-off command, the relays of the VMS under test are disconnected, wherein the disconnection of the relays is used to control the power-off of the VMS under test.

[0015] In the above solution, real-time data from execution logs is automatically collected and analyzed during the upgrade task, replacing the need for continuous manual monitoring of device output. The solution automatically identifies the upgrade stage corresponding to the log content and compares this identification with the preset test strategy, specifically the trigger time defined by the power-off test node. When the conditions match, a power-off command is automatically generated, replacing the manual function of analyzing logs and deciding when to cut off power. Finally, this command controls the relays that control the power supply circuit, physically cutting off the power supply to the vehicle's infotainment system, simulating a real-world hardware anomaly scenario of unexpected power interruption, rather than simulating a fault at the software level. This automated process, from status monitoring to decision generation to physical execution, not only reduces the uncertainty introduced by delays, negligence, and inconsistent judgment standards caused by manual operation but also creates more realistic test conditions than software simulation by directly manipulating the hardware power supply.

[0016] Correspondingly, the power failure testing system, equipment, and computer-readable storage medium for vehicle system upgrades provided in this embodiment of the invention also have the above-mentioned technical effects.

[0017] The above description is merely an overview of the technical solution of the present invention. In order to better understand the technical means of the present invention and to implement it in accordance with the contents of the specification, and in order to make the above and other objects, features and advantages of the present invention more apparent and understandable, specific embodiments of the present invention are described below. Attached Figure Description

[0018] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the invention. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings: Figure 1 A flowchart illustrating a power-off testing method for vehicle infotainment system upgrades provided by an embodiment of the present invention is shown. Figure 2 This diagram illustrates the composition of a power-off testing system for vehicle infotainment system upgrades according to an embodiment of the present invention. Figure 3 This diagram illustrates the composition of a power-off testing electronic device for vehicle infotainment system upgrades, as provided in an embodiment of the present invention. Detailed Implementation

[0019] Exemplary embodiments of the invention will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the invention are shown in the drawings, it should be understood that the invention may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this invention will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.

[0020] To address the issue that power-off testing for vehicle infotainment system upgrades relies too heavily on intelligent electronic devices, this invention provides a power-off testing method for vehicle infotainment system upgrades, such as... Figure 1 As shown, the method includes: S101. When the vehicle-mounted unit under test is performing an upgrade task, monitor the vehicle-mounted unit under test to generate an execution log; In one embodiment, monitoring the vehicle-to-the-test (V2T) system to generate an execution log when the V2T system is performing an upgrade task includes: Based on the power outage test requirements input by the user, the upgrade task of the vehicle system under test and the power outage test process when executing the upgrade task are determined. When the vehicle-mounted system under test performs the upgrade task, the system generates the execution log.

[0021] For example, the power outage test requirement mentioned above refers to the user's definition of the test scope and objectives, the upgrade task specifically refers to the complete upgrade process from a specific old version to a new version, and the power outage test process is a pre-planned test strategy, including the upgrade phase that needs to trigger a power outage and its triggering conditions.

[0022] Before initiating the actual testing process, this application first requires the standardized configuration of the test scenario. Testers, based on the established testing objectives, clearly specify the specific upgrade task to be tested. This task involves two key elements: the initial version of the vehicle's infotainment system before the upgrade, i.e., the old version, such as a version explicitly identified as old_v1.0; and the target version to which the system is planned to be upgraded, i.e., the new version, such as a version explicitly identified as new_v1.1. The complete upgrade packages for both versions must be uploaded to the OTA server beforehand to ensure accessibility. Simultaneously, testers need to define a specific power-off test process. The core content of this process includes: identifying the key stages requiring power-off testing from the complete OTA (Over-The-Air) upgrade process, such as specifying the download and flashing stages as the coverage of this test; and further setting more granular trigger parameters for each selected stage, such as triggering a power-off within a specific progress interval of the download stage.

[0023] After completing the above configuration, when the control system instructs the vehicle under test to begin executing the specific upgrade task, i.e., upgrading from old_v1.0 to new_v1.1, the log monitoring module is simultaneously started according to the pre-set test procedure. The log monitoring module continuously and automatically collects raw operational record data, i.e., the execution log, from the system output of the vehicle under test. This provides a unique and objective data source for subsequent automatic identification of the upgrade phase. The entire process's initiation and execution strictly depends on the previously completed configuration, ensuring that the test conditions are fixed and the process is repeatable.

[0024] By using the above technical solutions, the standardized configuration of test scenarios and strategies can be completed before the test starts, providing a clear basis for the execution of all subsequent automated steps. This reduces the arbitrariness introduced by unclear test conditions or temporary configuration, and enables the entire test process to run automatically under the preset specifications, laying the foundation for achieving consistency and repeatability of test results.

[0025] In one embodiment, the upgrade task is divided into different upgrade stages, and the method further includes: Select a preset power outage triggering stage from the upgrade stage. Each preset power outage triggering stage corresponds to a power outage time ratio. The power outage time ratio is used to control the host module to trigger the power outage test node corresponding to the power outage command within the current preset power outage triggering stage.

[0026] For example, the above upgrade phase refers to the different segments of the complete upgrade task according to its internal process, such as the download phase, verification phase and burning phase; the preset power-off trigger phase refers to the specific phase selected from all upgrade phases that needs to be tested by power-off; the power-off time ratio is a time control parameter that is configured independently for each preset power-off trigger phase, which defines a certain relative time point within the duration of the phase.

[0027] This application constructs a test intervention framework by meticulously dividing the complete upgrade task into stages. Testers, based on verification requirements, explicitly designate key stages from the multiple upgrade stages requiring power outage anomalies as preset power outage trigger stages, and independently configure a power outage time ratio for each selected stage. This power outage time ratio is a core control parameter that defines the relative time point at which a power outage is triggered within the duration range of the corresponding preset power outage trigger stage. Once the host module detects that the upgrade process has entered any preset power outage trigger stage, it will begin tracking the progress of that stage and generate a power outage command based on the specific time calculated according to the power outage time ratio set for that stage. For example, if the test strategy sets the download stage as a preset power outage trigger stage and sets its power outage time ratio to a randomly selected value within the range of 50% to 90%, after the host module confirms the entry into the download stage through log parsing, it will monitor the download progress in real time. When the progress reaches the specific value randomly selected according to the aforementioned ratio, it will immediately generate a power outage command.

[0028] This mechanism allows power outage testing to cover potential anomalies at different points in time within critical phases, rather than being limited to fixed locations such as the start or end of a phase. This significantly enhances the depth and breadth of the testing, more effectively probing the robustness of the vehicle's infotainment system at each stage of the upgrade process. By refining the trigger control of power outage testing to specific time points within each phase, the randomness and blindness of the testing are reduced. This makes the verification of the vehicle's self-recovery capabilities more accurately simulate the unpredictability of real-world power outages, improving the depth and effectiveness of the testing.

[0029] S102. If the upgrade stage corresponding to the execution log is the target stage, generate a power-off command, wherein the target stage is determined based on the power-off test node of the vehicle under test in the upgrade situation, and the power-off test node includes the trigger time information of the power-off test. In one embodiment, generating a power-off command when the upgrade stage corresponding to the execution log is the target stage includes: The execution logs are analyzed to determine the search keywords; The upgrade stage is determined based on the search keywords; When the upgrade phase is in the power-off test node, the power-off command is generated.

[0030] For example, the above execution log refers to the real-time operation record generated by the vehicle system under test during the upgrade process; the target stage refers to the specific upgrade stage determined based on the preset power-off test node, which needs to trigger a power-off; the power-off test node is a predefined power-off trigger condition, including the specific upgrade stage and its trigger time information; the search keyword refers to the feature string extracted from the execution log to identify a specific upgrade stage.

[0031] This application achieves automatic identification of upgrade stages by running a pre-configured log parsing script on the host module. This script continuously monitors the real-time execution log stream forwarded by the log monitoring module. Internally, it defines specific search keywords corresponding to each upgrade stage, such as "Downloading..." associated with the download stage, "Verifying..." associated with the verification stage, and "Flashing..." associated with the burning stage. When the log parsing script identifies a string matching a pre-configured keyword in the log stream, it immediately outputs the corresponding upgrade stage identifier. The host module then retrieves this identifier and records it as the status information of the current upgrade stage. Subsequently, the host module compares the currently identified upgrade stage with a pre-configured power-off test node. The power-off test node explicitly defines the target stage that needs to be triggered by a power-off and its triggering conditions. Once it is confirmed that the current stage meets the requirements of the power-off test node and satisfies the triggering time conditions defined by the node, the host module automatically generates a power-off command. For example, when the power outage test node is set to be triggered during the download phase and the progress reaches 50%, the host module will first confirm the entry into the download phase through log parsing, and then continuously monitor the download progress. When the progress meets the 50% condition, a power outage command will be generated immediately.

[0032] The above technical solution automates and intelligentizes the power outage trigger decision-making process. By analyzing execution logs in real time and matching keywords to automatically identify upgrade stages, it can accurately capture preset test nodes and automatically generate power outage commands. This reduces reliance on manual real-time monitoring and subjective judgment, minimizes test deviations caused by untimely human intervention or inconsistent judgment standards, and thus improves the objectivity and consistency of the testing process.

[0033] S103. Based on the power-off command, control the relay of the vehicle under test to disconnect, wherein the disconnection of the relay is used to control the power-off of the vehicle under test.

[0034] For example, the aforementioned power-off command refers to a control signal generated by the host module to indicate the cutting off of power supply; a relay is an electronic switching element controlled by an electrical signal, and its off state means that the circuit connection is physically disconnected.

[0035] After the host module generates a power-off command, this application sends the command to the programmable power supply module via a preset communication interface. The command parsing unit embedded in the programmable power supply module decodes the received command and identifies its intended operation as cutting off the power supply. After successful decoding, the programmable power supply module sends a control signal to the relay drive circuit directly electrically connected to it. Upon receiving the signal, the drive circuit changes its output state, thereby driving the electromagnetic mechanism inside the relay to operate, causing its internal switch contacts to physically switch from a continuously closed state to a stable open state. This physical disconnection of the contacts directly interrupts the current path in the power supply circuit from the programmable power supply module through the relay to the vehicle under test, thus achieving hardware-level power-off of the vehicle under test. For example, the host module sends a specific command string to the programmable power supply via the standard SCPI communication protocol. After recognizing that the command requires disconnection, the programmable power supply immediately changes the level state of its output terminal. This change signal is transmitted to the relay, ultimately causing its switch contacts to switch, and the power input to the vehicle under test is cut off.

[0036] By using the above technical solution, the control commands at the logic level are transformed into actual physical operations on the power supply line. The hardware-level power-off method simulates unexpected power interruption scenarios in the real world. This physical disconnection based on relay execution, compared with purely software-simulated anomalies, can more realistically reflect the hardware state changes of the vehicle system when encountering a power outage in actual use, thereby reducing the difference between the test environment and the real scenario and improving the reliability and practical reference value of the test results.

[0037] In one embodiment, the above method further includes: When the relay is cut off to control the power-off of the vehicle unit under test for a preset duration, a power-on command is generated. The relay is closed based on the power-on command to control the power-on restart of the vehicle's infotainment system under test.

[0038] For example, the aforementioned power outage preset duration refers to the power outage duration preset to achieve a complete power outage of the vehicle under test and prepare for restart; the power-on command refers to the control signal generated by the host module to indicate the restoration of power supply; the closed state of the relay means that the circuit connection is physically reconnected.

[0039] In this application, after the relay trips, causing a power outage in the vehicle under test (VAT), an internal independent timing unit immediately starts to precisely calculate the duration of the power outage. This timing process continues until the accumulated time reaches a preset specific value. This preset duration is designed to ensure that energy storage components such as capacitors in the VAT have fully discharged, thereby achieving a stable state of complete power failure. Once this time condition is met, the host module automatically generates a clearly formatted power-on command. This power-on command is immediately sent to the programmable power supply module via a designated communication link. Upon receiving the command, the control circuit inside the programmable power supply module parses it and confirms its validity, then generates a drive signal. This drive signal acts on the relay connected in series with the output of the programmable power supply, causing its internal electromagnetic mechanism to respond and reliably switch the switch contacts from the current off state to the closed state, allowing current to flow back into the VAT. After receiving power, the VAT's internal hardware circuitry completes a power-on reset and begins executing the built-in bootloader, thus entering the restart process. For example, the system is preset to a duration of ten seconds. After the relay cuts off the power supply for ten seconds, the host module generates a specific SCPI (Standard Commands for Programmable Instruments) instruction and sends it to the programmable power supply through the GPIB (General-Purpose Interface Bus) or LAN (Local Area Network) interface. The programmable power supply then changes its output control signal level to drive the relay coil to be energized and the contacts to close, and the vehicle's infotainment system is then powered on and started.

[0040] The above technical solution enables an automatic power restoration process after a power outage simulation, freeing testers from manually waiting and performing a power-on reactivation. By controlling the preset duration, the abnormal duration of each power outage test is kept consistent, reducing the differences in test conditions caused by human operation and making the results of different test cases comparable. At the same time, the automated power-on restart creates the necessary conditions for subsequent automatic verification of the vehicle's status, promoting the automation of the testing process.

[0041] In one embodiment, the above method further includes: When the vehicle-mounted system under test is powered on and restarted, the current execution status of the upgrade task of the vehicle-mounted system under test is determined based on the execution log, wherein the current execution status includes rolling back the version and continuing the upgrade; Obtain the current version number of the vehicle infotainment system under test; The verification result of the power outage test is determined based on the comparison between the current execution status of the upgrade task and the current version number.

[0042] For example, the above execution log refers to the continuous running records generated by the vehicle system under test during the upgrade and restart process; the current execution status refers to the direction of the response strategy adopted by the vehicle system after restart, as determined by analyzing the execution log, mainly including two states: rollback and continued upgrade; the current version number refers to the actual version identifier inside the operation of the vehicle system under test after restart, obtained through user commands; the verification result refers to the conclusion drawn from comprehensive judgment regarding whether this power outage test has achieved the expected goal.

[0043] This application initiates an automatic verification process after the vehicle's infotainment system under test is powered on and restarted. First, the log monitoring module continuously runs, collecting all execution logs generated during the restart boot and system loading process of the vehicle's infotainment system under test, and transmitting these logs to the host module in real time. Upon receiving the log stream, the host module initiates its built-in log analysis logic, which scans and matches the log content line by line based on a pre-defined keyword list. For example, it specifically searches for characteristic strings such as "rollback to an older version" or "continue upgrading," which clearly indicate the intention of the infotainment system after power failure and recovery. Once such a keyword is matched in the log, the host module determines the operation type corresponding to that keyword as the current execution state of the vehicle's infotainment system under test. Simultaneously, during the parallel determination of the execution state, the host module sends a specific command to the vehicle's infotainment system under test through the established communication connection. This command queries the currently effective system build version number of the device. Upon receiving this query command, the vehicle's infotainment system under test returns its current version identifier information, which the host module records as the current version number upon successful reception.

[0044] After obtaining the two key pieces of information—the current execution state and the current version number—the host module executes the final verification logic. It compares the behavioral intent represented by the current execution state (e.g., log keywords indicating the system is executing "rollback to an old version") with the actual system state reflected by the current version number (e.g., the obtained version number is indeed the old version number old_v1.0). If they match, the power outage test is considered successful; otherwise, it is marked as a failure. For example, if the log contains a record of "rollback to an old version" and the retrieved current version number is indeed a previously known old version number, the system automatically determines the rollback is successful and records the test case as passed. This technical solution automates the verification and determination of power outage test results. By automatically analyzing logs and verifying version numbers, manual checking and verification are replaced, making test conclusions no longer dependent on the subjective judgment and tedious operations of testers. This reduces potential misjudgments or delays caused by human factors, improves the objectivity and efficiency of result determination, and ultimately completes a fully automated testing loop from exception injection to state verification.

[0045] In one embodiment, the power-off test node of the vehicle-mounted system under test includes a download phase, a verification phase, and a flashing phase. The determination of the verification result of the power-off test based on the comparison between the current execution status of the upgrade task and the current version number includes: If the power-off test node of the vehicle's infotainment system under test is in the download or verification phase, and the current version number corresponds to the version number of the rollback version, then the rollback result of the power-off test is determined to be successful. If the power-off test node of the vehicle's infotainment system under test is the flashing stage, and the current version number corresponds to the version number of the rollback version, then the rollback result of the power-off test is determined to be successful. If the power-off test node of the vehicle's infotainment system under test is the flashing stage, and the current version number corresponds to the version number to be upgraded, then the upgrade result of the power-off test is determined to be successful.

[0046] For example, the aforementioned power outage test node refers to a pre-set key upgrade stage that requires the injection of power outage anomalies, specifically including the download stage, verification stage, and flashing stage; the current execution status refers to the vehicle's intentional behavior after restarting, as determined by analyzing the execution logs; the current version number refers to the actual version identifier of the vehicle after restarting; the rollback version number refers to the original old version identifier of the vehicle under test before the upgrade task started; and the version number for continued upgrades refers to the new version identifier that the upgrade task is planned to achieve.

[0047] After obtaining the current execution status and version number, this application performs automated result determination based on preset business rules bound to the power outage test node. A verification rule mapping table defines the set of expected legal states corresponding to different power outage test nodes. For example, when the test node triggering the power outage is identified as either the download or verification phase, the mapping table specifies that its only expected legal state is "rollback to the old version and the version number is indeed the old version." At this point, the actual obtained current execution status (such as the "rollback to the old version" or "continue upgrading" intent parsed from the logs) and the current version number are compared with this expected state. If the current execution status is "rollback version" and the current version number matches the known rollback version number, the system determines that the rollback is successful; if the current execution status is "continue upgrading" or the version number does not match the old version, the test is determined to have failed, and the reason for failure is recorded as "version not rolled back correctly."

[0048] When the power-off test node is in the flashing stage, the mapping table specifies that its expected legal state includes two possible scenarios: "rollback to the old version and the version number is indeed the old version" or "continue upgrading and the version number is indeed the new version". The actual state is checked sequentially to see if it matches either of these scenarios. If it matches the first scenario, the rollback is considered successful; if it matches the second scenario, the upgrade is considered successful; if the current execution state and version number do not match either of the above expected scenarios (e.g., the log shows "continue upgrading" but the version number is still the old version, or the version number is the new version but the log shows "rollback to the old version"), the test is considered a failure, and the reason for failure is recorded as "state and version mismatch". This rule-based dual verification mechanism ensures accurate evaluation of the vehicle's system behavior under complex power-off scenarios, while providing a clear conclusion of success or failure for each test result.

[0049] By employing the aforementioned technical solutions, precise judgment rules that align with the OTA upgrade business logic are injected into the automated verification process. This enables intelligent judgment based on the expected results of professional testers in different test scenarios. By transforming abstract verification results into clear success criteria closely related to specific power outage scenarios, the accuracy and technical rationality of test conclusions are improved, and the risk of misjudgment caused by ambiguous judgment rules or disconnection from business logic is reduced, thereby enhancing the credibility and practicality of automated testing.

[0050] In one embodiment, the method further includes an exception handling mechanism for intervening and recording when the verification process deviates from expectations.

[0051] For example, the above exception handling mechanism includes the following logic: After the vehicle-mounted unit under test is powered on, if it is determined from the execution log that the automatic restart process has not been executed, a restart command is sent to the vehicle-mounted unit under test through a preset communication connection, and the execution status of the test case is marked as abnormal. If the verification fails based on the comparison between the current execution status of the upgrade task and the current version number, for example, if the current version number does not match the expected rollback version or the version number to be upgraded, a detailed failure log is recorded, and an alarm message is generated and sent to the relevant testers.

[0052] In one embodiment, the above method further includes: Natural language processing technology based on machine learning models is used to replace or assist established keyword matching rules in order to improve the accuracy and robustness of parsing complex or non-standard execution logs, thereby more accurately identifying upgrade stages.

[0053] The programmable power supply module can be further configured to simulate complex power anomalies in the real world, such as continuous fluctuations or instantaneous drops in voltage, rather than just a complete disconnection of physical power supply, in order to create test conditions that are closer to actual fault scenarios.

[0054] The power-down testing method for vehicle infotainment system upgrades is encapsulated as an automatically scheduled task and integrated into the continuous integration / continuous deployment pipeline. This enables the automatic triggering and execution of full-stage power-down regression testing after each OTA upgrade package update, thereby improving verification efficiency.

[0055] An analytical model is built based on historical test data to dynamically adjust the test frequency or power outage time ratio threshold for each preset power outage triggering stage. For example, for upgrade stages with a high failure rate in abnormal recovery in historical tests, the power outage test coverage in subsequent test tasks is automatically increased.

[0056] By introducing the aforementioned extended capabilities, the testing system can continuously evolve to adapt to the ever-changing OTA technical specifications and testing requirements.

[0057] Furthermore, as a response to the above Figure 1 In addition to the implementation of the method shown, this embodiment of the invention also provides a power-off testing system for vehicle infotainment system upgrades, used for testing the aforementioned... Figure 1 The method shown is implemented accordingly. This system embodiment corresponds to the foregoing method embodiment. For ease of reading, this system embodiment will not repeat the details of the foregoing method embodiment, but it should be clear that the system in this embodiment can implement all the contents of the foregoing method embodiment. Figure 2 As shown, the system includes: a log monitoring module 21, a host module 22, and a programmable power supply module 23, wherein... Log monitoring module 21 is used to monitor the vehicle under test to generate execution logs when the vehicle under test performs an upgrade task; Host module 22 is used to generate a power-off command when the upgrade stage corresponding to the execution log is the target stage; The programmable power supply module 23 is used to control the disconnection of the relays of the vehicle-mounted unit under test based on the power-off command. The processor contains a kernel, which retrieves the corresponding program units from memory. One or more kernels can be configured, and by adjusting the kernel parameters, a power-off testing method for vehicle-mounted unit upgrades can be implemented, solving the problem that existing power-off testing methods for vehicle upgrades rely on manual intervention and have a low degree of automation.

[0058] This invention provides a computer-readable storage medium including a stored program that, when executed by a processor, implements a power-off test method for vehicle system upgrade.

[0059] This invention provides a processor for running a program, wherein the program executes the power-off test method for vehicle system upgrade.

[0060] This invention provides an electronic device, which includes at least one processor and at least one memory connected to the processor; wherein the processor is used to call program instructions in the memory to execute the power-off test method for vehicle infotainment system upgrades as described above. This invention provides an electronic device 30, such as... Figure 3 As shown, the electronic device includes at least one processor 301, and at least one memory 302 and bus 303 connected to the processor; wherein, the processor 301 and the memory 302 communicate with each other through the bus 303; the processor 301 is used to call program instructions in the memory to execute the above-mentioned power-off test method for vehicle system upgrade.

[0061] The smart electronic devices mentioned in this article can be PCs, tablets, mobile phones, etc.

[0062] This application also provides a computer program product that, when executed on a process management electronic device, is suitable for executing a program that initializes the power-off test method steps of the above-mentioned vehicle system upgrade.

[0063] It should be noted that the descriptions of each embodiment in the above embodiments have different focuses. For parts that are not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0064] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0065] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create a machine for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A system that specifies functions in one or more boxes.

[0066] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including an instruction set implemented in a process. Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0067] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0068] This application also provides a computer program product, which includes computer software instructions that, when executed on a processing device, cause the processing device to perform actions such as... Figure 1 The control flow of the memory in the corresponding embodiment.

[0069] A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable system. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk (SSD)).

[0070] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0071] In the embodiments provided in this application, it should be understood that the disclosed systems, methods, and approaches can be implemented in other ways. For example, the system embodiments described above are merely illustrative; for instance, the division of units 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 system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between systems or units may be electrical, mechanical, or other forms.

[0072] The units described 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.

[0073] 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.

[0074] 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 several 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 program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0075] The above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A power-off test method for vehicle infotainment system upgrades, characterized in that, Also includes: When the vehicle-mounted system under test is performing an upgrade task, the system is monitored to generate an execution log; If the upgrade stage corresponding to the execution log is the target stage, a power-off command is generated. The target stage is determined based on the power-off test node of the vehicle-mounted vehicle under upgrade. The power-off test node includes the trigger time information of the power-off test. The relay of the vehicle under test is disconnected based on the power-off command, wherein the disconnection of the relay is used to control the power-off of the vehicle under test.

2. The method according to claim 1, characterized in that, When the vehicle-mounted unit under test is performing an upgrade task, monitoring the vehicle-mounted unit under test to generate an execution log includes: Based on the power outage test requirements input by the user, the upgrade task of the vehicle system under test and the power outage test process when executing the upgrade task are determined. When the vehicle-mounted system under test performs the upgrade task, the system generates the execution log.

3. The method according to claim 1, characterized in that, When the upgrade stage corresponding to the execution log is the target stage, a power-off command is generated, including: The execution logs are analyzed to determine the search keywords; The upgrade stage is determined based on the search keywords; When the upgrade phase is in the power-off test node, the power-off command is generated.

4. The method according to claim 2, characterized in that, The upgrade task is divided into different upgrade phases, and the method further includes: Select a preset power outage triggering stage from the upgrade stage. Each preset power outage triggering stage corresponds to a power outage time ratio. The power outage time ratio is used to control the host module to trigger the power outage test node corresponding to the power outage command within the current preset power outage triggering stage.

5. The method according to claim 1, characterized in that, Also includes: When the relay is cut off to control the power-off of the vehicle unit under test for a preset duration, a power-on command is generated. The relay is closed based on the power-on command to control the power-on restart of the vehicle's infotainment system under test.

6. The method according to claim 5, characterized in that, Also includes: When the vehicle-mounted system under test is powered on and restarted, the current execution status of the upgrade task of the vehicle-mounted system under test is determined based on the execution log, wherein the current execution status includes rolling back the version and continuing the upgrade; Obtain the current version number of the vehicle infotainment system under test; The verification result of the power outage test is determined based on the comparison between the current execution status of the upgrade task and the current version number.

7. The method according to claim 6, characterized in that, The power-off test nodes for the vehicle-mounted system under test include a download phase, a verification phase, and a flashing phase. The verification result of the power-off test is determined based on the comparison between the current execution status of the upgrade task and the current version number, including: If the power-off test node of the vehicle's infotainment system under test is in the download or verification phase, and the current version number corresponds to the version number of the rollback version, then the rollback result of the power-off test is determined to be successful. If the power-off test node of the vehicle's infotainment system under test is the flashing stage, and the current version number corresponds to the version number of the rollback version, then the rollback result of the power-off test is determined to be successful. If the power-off test node of the vehicle's infotainment system under test is the flashing stage, and the current version number corresponds to the version number to be upgraded, then the upgrade result of the power-off test is determined to be successful.

8. A power failure testing system for vehicle infotainment system upgrades, characterized in that, include: The log monitoring module is used to monitor the vehicle under test and generate execution logs when the vehicle under test performs an upgrade task. The host module is used to generate a power-off command when the upgrade stage corresponding to the execution log is the target stage; The programmable power supply module is used to control the relay of the vehicle under test to disconnect based on the power-off command.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored program, wherein, when the program is executed by a processor, it implements the steps of the power-off testing method for vehicle system upgrade as described in any one of claims 1 to 7.

10. An electronic device, characterized in that, The electronic device includes at least one processor and at least one memory connected to the processor; wherein the processor is used to call program instructions in the memory to execute the steps of the power-off test method for vehicle system upgrade as described in any one of claims 1 to 7.

Images