Software sleep test verification control method and device, equipment and storage medium

Abstract

The invention discloses a software dormancy test verification control method and device, equipment and a storage medium, and relates to the technical field of software tests.The software dormancy test verification control method comprises the steps that the state of vehicle-mounted software is detected, and an initialization state, a sleep timer starting state and a sleep timer delay state are obtained; determining a dormant state based on the sleep timer on state and the sleep timer delay state; and performing intelligent function testing based on the initialization state and the dormant state to determine a function testing result, and controlling the system to enter a low-power-consumption mode based on the function testing result. The dormant state is determined by intelligently detecting the vehicle-mounted software, and the test result is determined by performing the function test, so that the system is accurately controlled to execute the dormant strategy, the problem of high power consumption caused by software failure or other abnormalities is fundamentally solved, vehicle power shortage is avoided, the strategy implementation is simple, the cost is low, and the method is suitable for popularization and application. An existing software and hardware system is not greatly changed, and the whole vehicle performance and the use experience of a user are remarkably improved.

Description

Technical Field

[0001] The present application relates to the field of software testing technology, and in particular to a software dormancy test verification control method, device, equipment and storage medium. Background Art

[0002] With the development of automobile technology, Boot software and App software have gradually become important components of vehicle-mounted ECU software. When the ECU is powered on or reset, the boot program is first executed to complete the hardware initialization, and then the external programming request flag is checked. If the flag has been set, the boot program will continue to run even if the application is valid. If the external programming flag is invalid, the status of the application will be further detected. If the application is valid, it will jump from the boot program to the application and start in the default session mode. If the application is invalid, the ECU continues to execute the boot program in the default session mode and waits for external programming requests. When the actual vehicle is tested for ECU flashing, after a certain ECU flashing upgrade fails and the vehicle is locked and powered off for a period of time, the vehicle will have a power loss phenomenon and cannot start normally. After further investigation and analysis: the ECU that failed to flash was erased because the old App software was erased and the new App software failed to download, resulting in its internal App software being invalid and maintained in the Boot program. The current was measured by the current clamp and it was found that the power consumption of the ECU in Boot mode has not been reduced, resulting in a power loss phenomenon after the vehicle is powered off. Therefore, it is necessary to perform software sleep test verification control.

[0003] At present, the existing practice is to adopt the strategy of boot or data partitioning of ECU to ensure that the ECU can recover even if an abnormality occurs in time during the flashing process, and to prevent the ECU from entering the Boot mode and maintaining a high power consumption state due to application software failure.

[0004] However, the existing practices involve changes at the software and hardware levels, resulting in high development costs, and the difficulty of developing boot or data partitioning solutions increases, which is likely to affect the stability of software quality. In addition, general OEMs do not require boot or data partitioning for non-safety-related ECUs. At the same time, the boot or data partitioning solution does not fundamentally solve the problem of continuous high power consumption in Boot mode. Once a problem occurs inside the ECU software, such as the failure of the boot or data partition application software, the ECU still cannot enter the low-power mode normally, and the vehicle is at risk of power shortage. Therefore, how to more conveniently, economically and effectively test and verify that the software sleep state control system enters the low-power mode has become an urgent problem to be solved.

[0005] The above contents are only used to assist in understanding the technical solution of the present application and do not constitute an admission that the above contents are prior art. Summary of the invention

[0006] The main purpose of this application is to provide a software sleep test verification control method, device, equipment and storage medium, aiming to solve the technical problem of how to more conveniently, economically and effectively test and verify that the software sleep state control system enters a low power consumption mode.

[0007] To achieve the above purpose, the present application proposes a software sleep test verification control method, the method comprising:

[0008] Detect the vehicle software status to obtain the initialization status, sleep timer start status and sleep timer delay status;

[0009] Determine a sleep state based on the sleep timer on state and the sleep timer delay state;

[0010] An intelligent functional test is performed based on the initialization state and the sleep state to determine a functional test result, and the system is controlled to enter a low power consumption mode based on the functional test result.

[0011] In one embodiment, the step of detecting the vehicle software status to obtain the initialization status, the sleep timer start status and the sleep timer delay status includes:

[0012] Get the status of the flash request flag, the status of the application flag, and the timing information of the target sleep timer;

[0013] Determine a mode state and an initialization state based on the flash request flag state and the application flag state;

[0014] Determine the operating current state based on the mode state, the sleep timer timing information and the target sleep timer timing information, and determine the sleep timer on state;

[0015] A sleep timer extension state is determined based on the mode state and the target sleep timer timing information.

[0016] In one embodiment, the step of determining the sleep state based on the sleep timer start state and the sleep timer delay state comprises:

[0017] If the sleep timer on state is on and the sleep timer delay state is sleep timer timeout, the sleep state is entering sleep mode;

[0018] If the sleep timer start state is restart and restart timing and the sleep timer delay state is power on or initialization before the sleep timer times out, the sleep state is not entering the sleep mode.

[0019] In one embodiment, the step of performing intelligent functional testing based on the initialization state and the sleep state to determine the functional test result includes:

[0020] If the initialization state is that the initialization is completed and the current mode is maintained and the sleep state is that the sleep timer has timed out, a forward test is performed to verify that the sleep function state is entered to obtain a forward function test result;

[0021] If the initialization state is power-on or reinitialization and the dormant state is that the sleep timer has not timed out, a reverse test is performed to verify the restart function state and obtain a reverse function test result;

[0022] A functional test result is obtained based on the forward functional test result and the reverse functional test result.

[0023] In one embodiment, the step of performing a forward test to verify entering a dormant function state and obtaining a forward function test result includes:

[0024] Perform a forward test to obtain the memory status of flashing and erasing, the sleep timer on time, and the sleep timer off time;

[0025] determining a forward test sleep timer timing time based on the sleep timer off timing time and the sleep timer on timing time;

[0026] Determine the download status of the forward test application based on the flash erase memory status and the forward test sleep timer timing;

[0027] A forward functional test result is determined based on the forward test application download status.

[0028] In one embodiment, the step of performing a reverse test to verify the restart function status and obtain a reverse function test result includes:

[0029] Perform reverse test to obtain the memory status of flashing and erasing, the sleep timer start time, the sleep timer restart time and the sleep timer timeout time;

[0030] Determine a reverse test sleep timer timing time based on the sleep timer timeout timing time and the sleep timer restart timing time;

[0031] Determine the reverse test application download status based on the flash erase memory status and the reverse test sleep timer timing;

[0032] A reverse functional test result is determined based on the reverse test application download status.

[0033] In one embodiment, after the step of controlling the system to enter the low power consumption mode based on the functional test result, the step further includes:

[0034] When the functional test result is that the forward functional test result is successfully verified and the reverse functional test result is successfully verified, the control system enters a low power consumption mode;

[0035] When the functional test result is a forward functional test result verification failure or a reverse functional test result verification failure, the control system does not enter the low power consumption mode.

[0036] In addition, to achieve the above purpose, the present application also proposes a software dormancy test verification control device, the software dormancy test verification control device comprising:

[0037] An acquisition module is used to detect the vehicle software status to obtain the initialization status, the sleep timer start status and the sleep timer delay status;

[0038] A processing module, configured to determine a sleep state based on the sleep timer start state and the sleep timer delay state;

[0039] The execution module is used to perform an intelligent functional test based on the initialization state and the sleep state to determine a functional test result, and control the system to enter a low power consumption mode based on the functional test result.

[0040] In addition, to achieve the above-mentioned purpose, the present application also proposes a software dormancy test verification control device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, and the computer program is configured to implement the steps of the software dormancy test verification control method as described above.

[0041] In addition, to achieve the above-mentioned purpose, the present application also proposes a storage medium, which is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by the processor, the steps of the software dormancy test verification control method described above are implemented.

[0042] One or more technical solutions proposed in this application have at least the following technical effects:

[0043] The present application proposes a software dormancy test verification control method, which detects the vehicle-mounted software status to obtain the initialization status, the sleep timer on status and the sleep timer delay status; determines the dormancy status based on the sleep timer on status and the sleep timer delay status; performs an intelligent function test based on the initialization status and the dormancy status to determine the function test result, and controls the system to enter a low power consumption mode based on the function test result. The present application comprehensively detects the initialization status of the vehicle-mounted software, the sleep timer on status and the sleep timer delay status, thereby intelligently determining the dormancy status, performing an intelligent function test to determine the test result, and accurately controlling the system to execute the dormancy strategy based on the test result, fundamentally solving the problem of high power consumption caused by software failure or other abnormalities, avoiding vehicle power loss, and the strategy is simple to implement and low-cost, and will not cause major changes to the existing software and hardware systems, reducing development costs, improving software stability, ensuring vehicle energy efficiency and safety, and significantly improving the performance of the entire vehicle and the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0045] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0046] Figure 1 A flowchart of the first embodiment of the software dormancy test verification control method of the present application is provided;

[0047] Figure 2 A flowchart of the second embodiment of the software sleep test verification control method of the present application is provided;

[0048] Figure 3 A flowchart of the third embodiment of the software sleep test verification control method of the present application is provided;

[0049] Figure 4 A brief flowchart of the software sleep test verification control method provided in an embodiment of the present application;

[0050] Figure 5 This is a schematic diagram of the module structure of the software dormancy test verification control device according to an embodiment of the present application;

[0051] Figure 6 Schematic diagram of the device structure of the hardware operating environment involved in the software sleep test verification control method in the embodiment of the present application.

[0052] The purpose, features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0053] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.

[0054] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0055] The main solution of the embodiment of the present application is: detect the status of the on-board software to obtain the initialization status, the sleep timer on status and the sleep timer delay status; determine the sleep state based on the sleep timer on status and the sleep timer delay status; perform intelligent function testing based on the initialization status and the sleep state to determine the function test result, and control the system to enter the low power consumption mode based on the function test result.

[0056] In this embodiment, for ease of description, the following description is made by taking the identification software sleep test verification control device as the execution subject.

[0057] Since the existing technology involves changes at the software and hardware levels, high development costs are generated, and the development difficulty of the boot or data partitioning solution increases, it is very likely to affect the stability of software quality. In addition, general OEMs do not require boot or data partitioning for non-safety-related ECUs. At the same time, the boot or data partitioning solution does not fundamentally solve the problem of continuous high power consumption in Boot mode. Once a problem occurs inside the ECU software, such as the failure of the boot or data partitioning application software, the ECU still cannot enter the low power mode normally, and the vehicle is at risk of running out of power.

[0058] The present application provides a solution, which detects the status of the vehicle-mounted software to obtain the initialization status, the sleep timer on status and the sleep timer delay status; determines the sleep state based on the sleep timer on status and the sleep timer delay status; performs an intelligent functional test based on the initialization status and the sleep state to determine the functional test result, and controls the system to enter a low power consumption mode based on the functional test result.

[0059] It can be seen from the above embodiments that the present application comprehensively detects the initialization state of the on-board software, the start state of the sleep timer, and the delay state of the sleep timer, thereby intelligently determining the sleep state, performing intelligent function testing to determine the test results, and accurately controlling the system to execute the sleep strategy based on the test results, thereby fundamentally solving the high power consumption problem caused by software failure or other abnormalities, avoiding vehicle power outages, and the strategy is simple to implement and low-cost, and will not cause major changes to the existing software and hardware systems, thereby reducing development costs, improving software stability, ensuring vehicle energy efficiency and safety, and significantly improving the performance of the entire vehicle and user experience.

[0060] Based on this, the embodiment of the present application provides a software sleep test verification control method, referring to Figure 1 , Figure 1 This is a flowchart of the first embodiment of the software sleep test verification control method of the present application.

[0061] In this embodiment, the software dormancy test verification control method includes steps S10 to S30:

[0062] Step S10, detecting the vehicle software status to obtain the initialization status, the sleep timer start status and the sleep timer delay status;

[0063] It should be noted that the initialization state reflects the characteristics of the hardware initialization state of the vehicle-mounted software after power-on or reset, the sleep timer start state reflects the characteristics of the timing state when the sleep timer is expected to enter a low power consumption mode, and the sleep timer delay state reflects the characteristics of the timing state from the start of the sleep timer to timeout.

[0064] It can be understood that the initialization state can represent the state of hardware completing initialization and determine whether the software can enter the working mode normally. The sleep timer on state can represent that the system automatically enters the sleep state after a certain period of time to reduce power consumption. The sleep timer delay state represents the duration of the ECU maintaining a high power consumption state in the Boot mode. The ECU is an electronic control unit.

[0065] For ease of understanding, the initialization state, the sleep timer start state and the sleep timer delay state are taken as an example for explanation, wherein the information collection device is an information collection module, and the storage device is a memory.

[0066] Executing the boot program completes hardware initialization, and the information acquisition module obtains the status of the flash request flag. If the status of the flash request flag is that the external programming request flag has been set, then even if the application is valid, the boot program continues to run. If the status of the flash request flag is that the external programming flag is invalid, the application flag status is obtained. If the application flag status is that the application is valid, it jumps from the boot program to the application and starts in the default session mode. If the application flag status is that the application is invalid, the ECU continues to execute the boot program in the default session mode and waits for an external programming request.

[0067] The mode state and initialization state are determined based on the flash request flag state and the application flag state, such as the mode state is high power consumption mode and sleep mode, and the initialization state is initialization completed or incomplete. The working current state is judged based on the mode state, the sleep timer timing information and the target sleep timer timing information, and the sleep timer on state is determined.

[0068] When the initialization state is initialization completed and the mode state is high power consumption mode, the sleep timer start state is start, and the timing starts to determine the sleep timer timing information, such as 301s, and the target sleep timer timing information is obtained, such as 300s. The sleep timer delay state is determined based on the mode state and the target sleep timer timing information. At this time, the sleep timer timing information exceeds the target sleep timer timing information, and the sleep timer delay state is timeout. The software puts the ECU in a low power consumption state, and the ECU enters sleep mode.

[0069] When the initialization state is initialization completed and the mode state is high power consumption mode, the sleep timer start state is start, and the timing starts to determine the sleep timer timing information, such as 299s, and the target sleep timer timing information is obtained, such as 300s. The sleep timer delay state is determined based on the mode state and the target sleep timer timing information. At this time, the sleep timer timing information is less than the target sleep timer timing information. If the initialization state is ECU power-on or initialization, the sleep timer start state is restart and restart timing until the sleep timer meets the timeout condition to put the ECU into sleep. At this time, the sleep timer delay state is power-on or initialization before the sleep timer times out.

[0070] The initialization state, the sleep timer on state and the sleep timer delay state are stored in a memory, and subsequent processing is performed based on the initialization state, the sleep timer on state and the sleep timer delay state.

[0071] In a feasible implementation, step S10 may include steps A11 to A14:

[0072] Step A11, obtaining the flash request flag status, application flag status and target sleep timer timing information;

[0073] It should be noted that the flash request flag status reflects the characteristics of expecting to receive an external programming request, the application flag status reflects the characteristics of the effective state of the application software, and the target sleep timer timing information reflects the characteristics of the set value of the duration of maintaining the high power consumption state.

[0074] Step A12, determining a mode state and an initialization state based on the flash request flag state and the application flag state;

[0075] It should be noted that the mode status reflects the characteristics of the current working mode.

[0076] It can be understood that when the flash request flag status is valid, it indicates that the ECU has received an external flash request. Even if the application is valid at this time, the ECU will continue to run the boot program to update or repair the software. When the flash request flag status is invalid, the application flag status is obtained. When the application flag status is valid, the ECU will jump from the boot program to the application and start in the default session mode. When the application status is invalid, the ECU will continue to execute the boot program and wait for external programming requests.

[0077] Step A13, judging the working current state based on the mode state, the sleep timer timing information and the target sleep timer timing information, and determining the sleep timer on state;

[0078] It can be understood that the target sleep timer timing information is used to control the time when the ECU automatically enters a low power consumption state when there is no operation, thereby controlling the energy consumption of the ECU and avoiding vehicle power loss due to long-term high power consumption operation, improving the energy efficiency of the vehicle, and enhancing the user experience.

[0079] Step A14: determining a sleep timer delay state based on the mode state and the target sleep timer timing information.

[0080] It is understandable that the energy efficiency of the ECU can be significantly improved by controlling the control system to enter sleep mode when there is no operation. The ECU will not maintain a high power consumption state indefinitely in Boot mode, thereby extending the battery life of the vehicle and reducing the risk of hardware damage such as overheating caused by long-term high power consumption operation, thereby improving the reliability and durability of the ECU.

[0081] Step S20, determining a sleep state based on the sleep timer start state and the sleep timer delay state;

[0082] It should be noted that the sleep state reflects the characteristics of the working mode that is expected to be entered.

[0083] It can be understood that when the sleep state enters the sleep mode, the ECU can automatically reduce power consumption when there is no operation, reduce battery consumption, avoid vehicle power loss due to long-term high power consumption operation, and at the same time maintain the system's responsiveness and stability.

[0084] For ease of understanding, the determination of the sleep state is taken as an example for explanation, wherein the information collection device is the information collection module, the storage device is the memory, and the processing device is the processing module.

[0085] The information acquisition module obtains the sleep timer start state and the sleep timer delay state and stores them in the memory, determines the sleep timer delay state based on the mode state and the target sleep timer timing information, if the sleep timer start state is on and the sleep timer delay state is sleep timer timeout, then the sleep state is entering sleep mode, if the sleep timer start state is restart and restart timing and the sleep timer delay state is power on or initialization before the sleep timer times out, then the sleep state is not entering sleep mode, and subsequent processing is performed based on the sleep state.

[0086] In a feasible implementation, step S20 may include steps B11 to B12:

[0087] Step B11, if the sleep timer on state is on and the sleep timer delay state is sleep timer timeout, the sleep state is entering sleep mode;

[0088] It is understandable that after the ECU completes the initialization process and the sleep timer has started timing and reached the preset timeout period, the ECU should enter low-power mode to reduce energy consumption, thereby extending battery life, reducing the risk of hardware damage, and improving the user experience. It is simple to implement and low-cost, and will not cause major changes to the existing software and hardware systems. It reduces development costs, improves software stability, ensures the energy efficiency and safety of the vehicle, and significantly improves the performance of the entire vehicle.

[0089] Step B12: If the sleep timer start state is restart and restart timing and the sleep timer delay state is power on or initialization before the sleep timer times out, the sleep state is not entering the sleep mode.

[0090] It is understandable that when the ECU is in Bootloader mode, it will be interrupted and enter sleep mode due to external events, such as power-on or system initialization. Even if the sleep timer has started timing, the ECU will not enter sleep mode as planned because it detects a signal that requires restart or initialization. Instead, it will remain in Bootloader mode to quickly respond to external requests, thereby improving the reliability and response speed of the system. At the same time, it avoids the risk of vehicle failure to start or other functional failures due to the ECU mistakenly entering sleep mode, thereby improving the user experience and vehicle operating efficiency.

[0091] Step S30 , performing an intelligent functional test based on the initialization state and the sleep state to determine a functional test result, and controlling the system to enter a low power consumption mode based on the functional test result.

[0092] It should be noted that the functional test results reflect the characteristics of software function performance in a specific sleep state and initialization state during functional testing, and the low power consumption mode reflects the characteristics of reducing power consumption after the system goes into sleep mode.

[0093] It can be understood that the functional test results include forward functional test results and reverse functional test results, wherein the forward functional test results can verify the performance status of the ECU under expected sleep conditions, while the reverse functional test results can verify the recovery ability of the ECU under interruption or unexpected sleep conditions, so as to timely discover and correct possible defects in the software, enhance the stability and reliability of the system, and improve the performance of the entire vehicle and the user experience.

[0094] For ease of understanding, the following description is given by taking determining a functional test result as an example, wherein the information acquisition device is an information acquisition module, the storage device is a memory, and the execution device is an execution module.

[0095] Perform a forward test, power on the ECU and wait for the communication to be stable, execute the Bootloader download process, and immediately terminate the flash process after completing the memory erase step to obtain the flash erase memory status. If the flash erase memory status is that the flash erase memory is successful, the App software in the ECU is invalidated, thereby ensuring that the ECU can maintain the Boot mode even if it is powered on or initialized again. Wait 5s after powering off the ECU and then power it on again, record the sleep timer start timing time T1, and use the test equipment to continuously monitor the ECU's working current. When the ECU's working current is significantly reduced, it is judged that the sleep timer has timed out, record the sleep timer shutdown timing time T2, and observe the static current for 5 minutes, and verify that the ECU has entered a low power consumption state. state and there is no abnormal change in static current, determine the forward test sleep timer timing time T=T2-T1 based on the sleep timer closing timing time and the sleep timer opening timing time, if the forward test sleep timer timing time is 300s, determine the forward test application download status based on the flash erase memory state and the forward test sleep timer timing time, obtain the target forward test sleep timer timing time, such as 300s, at this time the forward test sleep timer timing time is not less than the target forward test sleep timer timing time, use the test equipment to re-execute the Bootloader download process, ECU re-executes the correct application download to obtain the forward test application download status, and determines the forward function test result based on the forward test application download status.

[0096] Perform a reverse test, power on the ECU and wait for the communication to be stable, execute the Bootloader download process, and immediately terminate the flash process after completing the memory erasing step to obtain the flash memory status. If the flash memory status is that the flash memory is successful, the App software in the ECU is invalidated, thereby ensuring that the ECU can remain in Boot mode even if it is powered on or initialized again. Wait 5s after powering off the ECU and then power it on again, record the sleep timer start timing time T1, and use the test equipment to continuously monitor the ECU's working current. Before the sleep timer start timing time T1 times out, power off the ECU and record the sleep timer restart timing time T3. When the ECU working current is significantly reduced, it is judged that the sleep timer has timed out, and record it. The sleep timer times out timing time T4, and the reverse test sleep timer timing time T=T4-T3 is determined based on the sleep timer timeout timing time and the sleep timer restart timing time. If the reverse test sleep timer timing time is 300s, the reverse test application download status is determined based on the flash erase memory status and the reverse test sleep timer timing time, and the target reverse test sleep timer timing time is obtained, such as 300s. At this time, the reverse test sleep timer timing time is not less than the target reverse test sleep timer timing time, and the Bootloader download process is re-executed using the test equipment. The ECU re-executes the correct application download to obtain the reverse test application download status, and the reverse function test result is determined based on the reverse test application download status.

[0097] A functional test result is obtained based on the forward functional test result and the reverse functional test result. When the functional test result is that the forward functional test result is successfully verified and the reverse functional test result is successfully verified, the control system enters a low power consumption mode. When the functional test result is that the forward functional test result is failed to be verified or the reverse functional test result is failed to be verified, the control system does not enter a low power consumption mode.

[0098] The present application proposes a software dormancy test verification control method, which detects the vehicle software status to obtain the initialization status, the sleep timer on status and the sleep timer delay status; determines the dormancy status based on the sleep timer on status and the sleep timer delay status; performs intelligent function test based on the initialization status and the dormancy status to determine the function test result, and controls the system to enter the low power consumption mode based on the function test result. The method solves the technical problem of how to control the system to enter the low power consumption mode more accurately. Compared with the prior art, the present application detects the initialization status of the vehicle software, the sleep timer on status and the sleep timer delay status, intelligently judges the dormancy status of the electronic control unit and performs function test to obtain the function test result, thereby accurately controlling the ECU to automatically enter the low power consumption mode under specific conditions according to the result of the intelligent function test, avoiding the vehicle from losing power, improving the responsiveness and stability of the ECU, and is simple to implement, low cost, and will not cause major changes to the existing software and hardware systems, reducing the development cost, improving the stability of the software, and ensuring the energy efficiency and safety of the vehicle, significantly improving the performance of the vehicle and the user experience.

[0099] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as those in the above-mentioned embodiment 1 can be referred to the above introduction and will not be repeated later.

[0100] In this embodiment, refer to Figure 2 , Figure 2 This is a flow chart of the second embodiment of the software dormancy test verification control method of this application, where step S30 specifically includes steps S31 to S33:

[0101] Step S31, if the initialization state is initialization completed and maintaining the current mode and the sleep state is sleep timer timeout, then perform a forward test to verify entering the sleep function state to obtain a forward function test result;

[0102] It should be noted that the forward functional test result reflects the characteristics of the state of the verification system executing the sleep strategy according to the established process.

[0103] It can be understood that the forward functional test results can characterize the software function performance and system responsiveness of the ECU, that is, the system successfully enters the low power consumption mode within the predetermined time without external interference. Through the forward functional test, the performance status of the ECU under the expected sleep conditions can be verified, and possible defects in the software can be discovered and corrected in time, thereby enhancing the stability and reliability of the system, improving the performance of the entire vehicle, and optimizing the user experience.

[0104] For ease of understanding, obtaining a positive functional test result is taken as an example for explanation, wherein the information acquisition device is an information acquisition module, the storage device is a memory, and the execution device is an execution module.

[0105] Perform a forward test, power on the ECU and wait for the communication to be stable, execute the Bootloader download process, and immediately terminate the flash process after completing the memory erase step to obtain the flash erase memory status. If the flash erase memory status is that the flash erase memory is successful, the App software in the ECU is invalidated, thereby ensuring that the ECU can maintain the Boot mode even if it is powered on or initialized again. Wait 5s after powering off the ECU and then power it on again, record the sleep timer start timing time T1, and use the test equipment to continuously monitor the ECU's working current. When the ECU's working current is significantly reduced, it is judged that the sleep timer has timed out, record the sleep timer shutdown timing time T2, and observe the static current for 5 minutes, and verify that the ECU has entered a low power consumption state. state and there is no abnormal change in static current, determine the forward test sleep timer timing time T=T2-T1 based on the sleep timer closing timing time and the sleep timer opening timing time, if the forward test sleep timer timing time is 300s, determine the forward test application download status based on the flash erase memory state and the forward test sleep timer timing time, obtain the target forward test sleep timer timing time, such as 300s, at this time the forward test sleep timer timing time is not less than the target forward test sleep timer timing time, use the test equipment to re-execute the Bootloader download process, ECU re-executes the correct application download to obtain the forward test application download status, and determines the forward function test result based on the forward test application download status.

[0106] In a feasible implementation, step S31 may include steps C11 to C14:

[0107] Step C11, performing a forward test to obtain the flashing and erasing memory status, the sleep timer on timing time, and the sleep timer off timing time;

[0108] It should be noted that the flash erase memory status reflects the characteristics of the application memory erase status during the software update process, the sleep timer start timing time reflects the characteristics of the moment when the sleep timer starts timing, and the sleep timer stop timing time reflects the characteristics of the moment when the sleep timer stops timing.

[0109] It can be understood that only when the memory is successfully erased, that is, the flash erase memory status is successfully erased, can the ECU be correctly maintained in Boot mode and start the sleep timer, and the sleep timer start timing time is the start time of the sleep process, and the sleep timer off timing time is the end time of the sleep process.

[0110] Step C12, determining the forward test sleep timer timing time based on the sleep timer off timing time and the sleep timer on timing time;

[0111] It should be noted that the timing time of the forward test sleep timer reflects the characteristics of the total time used from starting the sleep timer to actually entering the sleep mode.

[0112] It can be understood that by accurately calculating the forward test sleep timer timing time, the system can verify the sleep strategy execution status, reduce energy consumption, and improve the vehicle's energy efficiency and user experience.

[0113] Step C13, determining the download status of the forward test application based on the flash erase memory status and the forward test sleep timer timing;

[0114] It should be noted that the forward test application download status reflects the feature of expecting to re-execute the correct application download after the forward test.

[0115] Step C14, determining a forward functional test result based on the download status of the forward test application.

[0116] It is understandable that after completing the forward test, the application download status of the ECU is evaluated, and it is expected that the ECU should be able to re-execute the correct application download. When the forward functional test results show that the application can be successfully downloaded and executed, it proves that the ECU can normally execute the sleep strategy, thereby reducing the risk of high power consumption caused by software problems.

[0117] Step S32, if the initialization state is power-on or reinitialization and the sleep state is that the sleep timer has not timed out, a reverse test is performed to verify the restart function state and obtain a reverse function test result;

[0118] It should be noted that the reverse functional test result reflects the characteristics of the restart state of the verification system when the dormant process is interrupted when encountering an interruption or an external event.

[0119] It can be understood that the reverse functional test results show that when the sleep process is interrupted and the Bootloader mode is maintained, the external request can be responded to quickly, simulating the interruption situation that the ECU may encounter when trying to enter the sleep mode. Therefore, when the ECU encounters an interruption in sleep, the normal operation of the system can be maintained and the sleep mode can be avoided, thereby preventing the risk of the vehicle failing to start or causing functional failures.

[0120] For ease of understanding, obtaining reverse function test results is taken as an example for explanation, wherein the information acquisition device is an information acquisition module, the storage device is a memory, and the execution device is an execution module.

[0121] Perform a reverse test, power on the ECU and wait for the communication to be stable, execute the Bootloader download process, and immediately terminate the flash process after completing the memory erasing step to obtain the flash memory status. If the flash memory status is that the flash memory is successful, the App software in the ECU is invalidated, thereby ensuring that the ECU can remain in Boot mode even if it is powered on or initialized again. Wait 5s after powering off the ECU and then power it on again, record the sleep timer start timing time T1, and use the test equipment to continuously monitor the ECU's working current. Before the sleep timer start timing time T1 times out, power off the ECU and record the sleep timer restart timing time T3. When the ECU working current is significantly reduced, it is judged that the sleep timer has timed out, and record it. The sleep timer times out timing time T4, and the reverse test sleep timer timing time T=T4-T3 is determined based on the sleep timer timeout timing time and the sleep timer restart timing time. If the reverse test sleep timer timing time is 300s, the reverse test application download status is determined based on the flash erase memory status and the reverse test sleep timer timing time, and the target reverse test sleep timer timing time is obtained, such as 300s. At this time, the reverse test sleep timer timing time is not less than the target reverse test sleep timer timing time, and the Bootloader download process is re-executed using the test equipment. The ECU re-executes the correct application download to obtain the reverse test application download status, and the reverse function test result is determined based on the reverse test application download status.

[0122] In a feasible implementation, step S32 may include steps D11 to D14:

[0123] Step D11, performing a reverse test to obtain the memory status of flashing and erasing, the sleep timer start time, the sleep timer restart time, and the sleep timer timeout time;

[0124] It should be noted that the sleep timer restart timing time reflects the characteristics of the moment when the timer is restarted after the interruption, and the sleep timer timeout timing time reflects the characteristics of the moment when the sleep timer is started again after the interruption and then turned off.

[0125] Step D12, determining a reverse test sleep timer timing time based on the sleep timer timeout timing time and the sleep timer restart timing time;

[0126] It should be noted that the timing time of the reverse test sleep timer reflects the characteristics of the total time taken from restarting the sleep timer after interrupting the sleep mode to actually entering the sleep mode.

[0127] Step D13, determining the reverse test application download status based on the flash erase memory status and the reverse test sleep timer timing;

[0128] It should be noted that the reverse test application download status reflects the feature of expecting to re-execute the correct application download after the reverse test.

[0129] Step D14, determining a reverse function test result based on the reverse test application download status.

[0130] It is understandable that after completing the reverse test, the application download status of the ECU is evaluated, and it is expected that the ECU should be able to re-execute the correct application download. When the reverse functional test results show that the application can be successfully downloaded and executed, it proves that the ECU can normally execute the restart after interruption and then enter the sleep strategy, thereby reducing the risk of high power consumption caused by software problems.

[0131] Step S33, obtaining a function test result based on the forward function test result and the reverse function test result.

[0132] It can be understood that based on the forward functional test and the reverse functional test, it can be verified that the ECU can enter the low power mode in the Boot mode, and verify that the sleep timer timeout meets the design requirements. At the same time, it can be verified that the ECU can restart the timing if an abnormal initialization occurs after the sleep timer is turned on, so as to accurately judge the execution status of the sleep strategy, and then control the ECU to enter the low power mode, reduce energy consumption, extend battery life, and improve the vehicle's energy efficiency and user experience.

[0133] For ease of understanding, obtaining functional test results is taken as an example for explanation, wherein the information acquisition device is the information acquisition module, the storage device is the memory, and the execution device is the execution module.

[0134] Perform a forward test and a reverse test, obtain a functional test result based on the forward functional test result and the reverse functional test result, and perform subsequent processing based on the functional test result.

[0135] The present application proposes a software sleep test verification control method. If the initialization state is that the initialization is completed and the current mode is maintained and the sleep state is that the sleep timer has timed out, a forward test is performed to verify the sleep function state and obtain the forward function test result; if the initialization state is that the power is turned on again or reinitialized and the sleep state is that the sleep timer has not timed out, a reverse test is performed to verify the restart function state and obtain the reverse function test result; the function test result is obtained based on the forward function test result and the reverse function test result. The technical problem of how to perform a function test to verify the function state of the system is solved. Compared with the prior art, the present application verifies the function state of the system by performing forward and reverse tests, verifies that the ECU can enter the low power mode in the Boot mode, verifies that the sleep timer timeout meets the design requirements, and verifies that the ECU can restart the timing after abnormal initialization occurs after the sleep timer is turned on, thereby optimizing the vehicle performance and user experience.

[0136] Based on the first and second embodiments of the present application, in the third embodiment of the present application, the same or similar contents as those of the first and second embodiments can be referred to the above description, and will not be described in detail later. Figure 3 After step S30, the software dormancy test verification control method further includes steps S34 to S35:

[0137] Step S34, when the functional test result is that the forward functional test result is successfully verified and the reverse functional test result is successfully verified, the control system enters a low power consumption mode;

[0138] It is understandable that if both the forward functional test result and the reverse functional test result are verified successfully, the low power consumption mode is entered, and its power consumption state is intelligently adjusted according to the test results to ensure energy efficiency and extend battery life.

[0139] For ease of understanding, the following description is given by taking obtaining a function test result as an example, wherein the information acquisition device is an information acquisition module, the storage device is a memory, and the execution device is an execution module.

[0140] Perform forward test and reverse test, obtain functional test result based on the forward functional test result and the reverse functional test result, and when the functional test result is that the forward functional test result is successfully verified and the reverse functional test result is successfully verified, the control system enters a low power consumption mode.

[0141] Step S35, when the function test result is a forward function test result verification failure or a reverse function test result verification failure, the control system does not enter the low power consumption mode.

[0142] It is understandable that when the functional test result is a forward functional test result verification failure or a reverse functional test result verification failure, the current power consumption state is intelligently maintained according to the test result to facilitate further diagnosis and repair.

[0143] For ease of understanding, the following description is given by taking obtaining a function test result as an example, wherein the information acquisition device is an information acquisition module, the storage device is a memory, and the execution device is an execution module.

[0144] Perform forward test and reverse test, obtain functional test result based on the forward functional test result and the reverse functional test result, and when the functional test result is a forward functional test result verification failure or a reverse functional test result verification failure, the control system does not enter low power consumption mode.

[0145] For example, in order to help understand the implementation process of the software sleep test verification control method obtained by combining this embodiment with the above-mentioned embodiment 1, please refer to Figure 4 , Figure 4 A brief flow chart of a software sleep test verification control method is provided, specifically:

[0146] When the ECU is initialized and maintained in Boot mode, the Boot software will start a sleep timer and begin timing. When the sleep timer times out (the recommended sleep timer is 300s), the Boot software puts the ECU into a low power state, and the ECU enters sleep mode. After the sleep timer is turned on and before it times out, if the ECU is powered on / initialized again, the sleep timer will restart and start timing again until the sleep timer meets the timeout condition and the ECU enters sleep. Referring to Example 1, the vehicle software status is detected to obtain the initialization status, the sleep timer start status and the sleep timer delay status; the sleep state is determined based on the sleep timer start status and the sleep timer delay status; the intelligent function test is performed based on the initialization status and the sleep state to determine the function test result, and the sleep strategy execution state is determined based on the function test result to control the system to enter low power mode. Referring to Example 2, if the initialization state is that the initialization is completed and the current mode is maintained and the sleep state is that the sleep timer has timed out, a forward test is performed to verify the entry into the sleep function state to obtain a forward function test result; if the initialization state is that the power is turned on again or reinitialized and the sleep state is that the sleep timer has not timed out, a reverse test is performed to verify the restart function state to obtain a reverse function test result; a function test result is obtained based on the forward function test result and the reverse function test result. Referring to Example 3, when the function test result is that the forward function test result is successfully verified and the reverse function test result is successfully verified, the sleep strategy execution state is that the sleep strategy is successfully executed, and the software sleeps normally and enters a low power consumption mode; when the function test result is that the forward function test result is failed to be verified or the reverse function test result is failed to be verified, the sleep strategy execution state is that the sleep strategy is failed to be executed, and the software does not sleep normally and enters a low power consumption mode.

[0147] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the software sleep test verification control method of the present application. More simple transformations based on this technical concept are all within the protection scope of the present application.

[0148] This application also provides a software sleep test verification control device, please refer to Figure 5 , the software dormancy test verification control device comprises:

[0149] An acquisition module 10 is used to detect the vehicle software status to acquire the initialization status, the sleep timer start status and the sleep timer delay status;

[0150] A processing module 20, configured to determine a sleep state based on the sleep timer start state and the sleep timer delay state;

[0151] The execution module 30 is used to perform an intelligent function test based on the initialization state and the sleep state to determine a function test result, and determine a sleep strategy execution state based on the function test result to control the system to enter a low power consumption mode.

[0152] The acquisition module 10 is further used to acquire the flash request flag status, the application flag status and the target sleep timer timing information;

[0153] Determine a mode state and an initialization state based on the flash request flag state and the application flag state;

[0154] Determine the operating current state based on the mode state, the sleep timer timing information and the target sleep timer timing information, and determine the sleep timer on state;

[0155] A sleep timer extension state is determined based on the mode state and the target sleep timer timing information.

[0156] The processing module 20 is further configured to: if the sleep timer on state is on and the sleep timer delay state is sleep timer timeout, the sleep state is to enter the sleep mode;

[0157] If the sleep timer start state is restart and restart timing and the sleep timer delay state is power on or initialization before the sleep timer times out, the sleep state is not entering the sleep mode.

[0158] The execution module 30 is further configured to execute a forward test to verify the entry into the sleep function state and obtain a forward function test result if the initialization state is that the initialization is completed and the current mode is maintained and the sleep state is that the sleep timer has timed out;

[0159] If the initialization state is power-on or reinitialization and the dormant state is that the sleep timer has not timed out, a reverse test is performed to verify the restart function state and obtain a reverse function test result;

[0160] A functional test result is obtained based on the forward functional test result and the reverse functional test result.

[0161] The execution module 30 is also used to perform a forward test to obtain the flashing and erasing memory status, the sleep timer on timing time, and the sleep timer off timing time;

[0162] determining a forward test sleep timer timing time based on the sleep timer off timing time and the sleep timer on timing time;

[0163] Determine the download status of the forward test application based on the flash erase memory status and the forward test sleep timer timing;

[0164] A forward functional test result is determined based on the forward test application download status.

[0165] The execution module 30 is further used to perform a reverse test to obtain the flashing and erasing memory status, the sleep timer start timing time, the sleep timer restart timing time and the sleep timer timeout timing time;

[0166] Determine a reverse test sleep timer timing time based on the sleep timer timeout timing time and the sleep timer restart timing time;

[0167] Determine the reverse test application download status based on the flash erase memory status and the reverse test sleep timer timing;

[0168] A reverse functional test result is determined based on the reverse test application download status.

[0169] The execution module 30 is further configured to, when the function test result is that the forward function test result is successfully verified and the reverse function test result is successfully verified, the sleep strategy execution state is that the sleep strategy is successfully executed, and the software normally sleeps and enters the low power consumption mode;

[0170] When the functional test result is a forward functional test result verification failure or a reverse functional test result verification failure, the sleep strategy execution status is a sleep strategy execution failure, and the software does not normally sleep and enter the low power consumption mode.

[0171] The software sleep test verification control device provided by the present application adopts the software sleep test verification control method in the above embodiment, which can solve the technical problem of how to test and verify the software sleep state control system to enter the low power consumption mode more conveniently, economically and effectively. Compared with the prior art, the beneficial effects of the software sleep test verification control device provided by the present application are the same as the beneficial effects of the software sleep test verification control method provided by the above embodiment, and the other technical features in the software sleep test verification control device are the same as the features disclosed in the above embodiment method, which will not be repeated here.

[0172] The present application provides a software sleep test verification control device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the software sleep test verification control method in the above-mentioned embodiment one.

[0173] Reference below Figure 6, which shows a schematic diagram of the structure of a software dormancy test verification control device suitable for implementing an embodiment of the present application. The software dormancy test verification control device in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 6 The software sleep test verification control device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0174] like Figure 6 As shown, the software sleep test verification control device may include a processing device 1001 (such as a central processing unit, a graphics processor, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 1002 or a program loaded from a storage device 1003 to a random access memory (RAM: Random Access Memory) 1004. In RAM1004, various programs and data required for the operation of the software sleep test verification control device are also stored. The processing device 1001, ROM1002 and RAM1004 are connected to each other through a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems can be connected to the I / O interface 1006: input devices 1007 including, for example, a touch screen, a touchpad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; output devices 1008 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; storage devices 1003 including, for example, a magnetic tape, a hard disk, etc.; and communication devices 1009. The communication device 1009 can allow the software dormancy test verification control device to communicate wirelessly or wired with other devices to exchange data. Although the figure shows a software dormancy test verification control device with various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems may be implemented or have instead.

[0175] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.

[0176] The software sleep test verification control device provided by the present application adopts the software sleep test verification control method in the above embodiment, which can solve the technical problem of how to test and verify the software sleep state control system to enter the low power consumption mode more conveniently, economically and effectively. Compared with the prior art, the beneficial effects of the software sleep test verification control device provided by the present application are the same as the beneficial effects of the software sleep test verification control method provided by the above embodiment, and the other technical features in the software sleep test verification control device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.

[0177] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0178] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0179] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, and the computer-readable program instructions are used to execute the software dormancy test verification control method in the above-mentioned embodiment.

[0180] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination of the above.

[0181] The computer-readable storage medium may be included in the software dormancy test verification control device; or may exist independently without being assembled into the software dormancy test verification control device.

[0182] The above-mentioned computer-readable storage medium carries one or more programs. When the above-mentioned one or more programs are executed by the software sleep test verification control device, the software sleep test verification control device: detects the status of the vehicle-mounted software to obtain the initialization status, the sleep timer on status and the sleep timer delay status; determines the sleep status based on the sleep timer on status and the sleep timer delay status; performs an intelligent function test based on the initialization status and the sleep status to determine the function test result, and determines the sleep strategy execution status based on the function test result to control the system to enter the low power consumption mode.

[0183] Computer program code for performing the operations of the present application may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0184] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0185] The modules involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the module does not constitute a limitation on the unit itself in some cases.

[0186] The readable storage medium provided by the present application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned software sleep test verification control method, and can solve the technical problem of how to more conveniently, economically and effectively test and verify that the software sleep state control system enters a low power consumption mode. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided by the present application are the same as the beneficial effects of the software sleep test verification control method provided by the above-mentioned embodiment, and will not be repeated here.

[0187] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.

Claims

1. A software dormancy test verification control method, characterized in that: The method includes: Detect the vehicle software status to obtain the initialization status, sleep timer start status and sleep timer delay status; Determine a sleep state based on the sleep timer on state and the sleep timer delay state; An intelligent functional test is performed based on the initialization state and the sleep state to determine a functional test result, and the system is controlled to enter a low power consumption mode based on the functional test result.

2. The method according to claim 1, characterized in that The step of detecting the vehicle software status to obtain the initialization status, the sleep timer start status and the sleep timer delay status comprises: Get the status of the flash request flag, the status of the application flag, and the timing information of the target sleep timer; Determine a mode state and an initialization state based on the flash request flag state and the application flag state; Determine the operating current state based on the mode state, the sleep timer timing information and the target sleep timer timing information, and determine the sleep timer on state; A sleep timer extension state is determined based on the mode state and the target sleep timer timing information.

3. The method according to claim 1, characterized in that The step of determining the sleep state based on the sleep timer start state and the sleep timer delay state comprises: If the sleep timer on state is on and the sleep timer delay state is sleep timer timeout, the sleep state is entering sleep mode; If the sleep timer start state is restart and restart timing and the sleep timer delay state is power on or initialization before the sleep timer times out, the sleep state is not entering the sleep mode.

4. The method according to claim 1, characterized in that The step of performing intelligent functional testing based on the initialization state and the sleep state to determine the functional test result comprises: If the initialization state is that the initialization is completed and the current mode is maintained and the sleep state is that the sleep timer has timed out, a forward test is performed to verify that the sleep function state is entered to obtain a forward function test result; If the initialization state is power-on or reinitialization and the dormant state is that the sleep timer has not timed out, a reverse test is performed to verify the restart function state and obtain a reverse function test result; A functional test result is obtained based on the forward functional test result and the reverse functional test result.

5. The method according to claim 4, characterized in that The step of performing a forward test to verify entering a dormant function state and obtaining a forward function test result comprises: Perform a forward test to obtain the memory status of flashing and erasing, the sleep timer on time, and the sleep timer off time; determining a forward test sleep timer timing time based on the sleep timer off timing time and the sleep timer on timing time; Determine the download status of the forward test application based on the flash erase memory status and the forward test sleep timer timing; A forward functional test result is determined based on the forward test application download status.

6. The method according to claim 4, characterized in that The step of performing a reverse test to verify the restart function status and obtain a reverse function test result comprises: Perform reverse test to obtain the memory status of flashing and erasing, the sleep timer start time, the sleep timer restart time and the sleep timer timeout time; Determine a reverse test sleep timer timing time based on the sleep timer timeout timing time and the sleep timer restart timing time; Determine the reverse test application download status based on the flash erase memory status and the reverse test sleep timer timing; A reverse functional test result is determined based on the reverse test application download status.

7. The method according to claim 1, characterized in that After the step of controlling the system to enter the low power consumption mode based on the functional test result, the following steps are further included: When the functional test result is that the forward functional test result is successfully verified and the reverse functional test result is successfully verified, the control system enters a low power consumption mode; When the functional test result is a forward functional test result verification failure or a reverse functional test result verification failure, the control system does not enter the low power consumption mode.

8. A software dormancy test verification control device, characterized in that: The device comprises: An acquisition module is used to detect the vehicle software status to obtain the initialization status, the sleep timer start status and the sleep timer delay status; A processing module, configured to determine a sleep state based on the sleep timer start state and the sleep timer delay state; The execution module is used to perform an intelligent functional test based on the initialization state and the sleep state to determine a functional test result, and control the system to enter a low power consumption mode based on the functional test result.

9. A software dormancy test verification control device, characterized in that: The device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the software dormancy test verification control method according to any one of claims 1 to 7.

10. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the software dormancy test verification control method according to any one of claims 1 to 7 are implemented.

Images