Vehicle controller hibernation method, vehicle, and storage medium

Abstract

The embodiment of the application provides a vehicle controller hibernation method, a vehicle and a storage medium, the method comprises the following steps: monitoring whether a plurality of controllers in the vehicle have working requirements when the vehicle is in a whole vehicle security state; in response to the plurality of controllers all having no working requirements, monitoring whether at least one controller in the plurality of controllers continuously actively wakes up a vehicle local area network of the vehicle to obtain a monitoring result; and determining a hibernation adjustment mode corresponding to the plurality of controllers based on the monitoring result. The application solves the technical problem of poor vehicle electric energy management efficiency and poor system reliability caused by the fact that the new energy vehicle cannot hibernate due to controller software abnormalities in the related art.

Description

Technical Field

[0001] This application relates to the field of vehicle technology, and more specifically, to a vehicle controller hibernation method, a vehicle, and a storage medium. Background Technology

[0002] With the popularization of new energy vehicles, energy management during non-use has become a key factor in ensuring a good user experience. New energy vehicles, especially electric vehicles, face greater demands on dark current monitoring and control due to the complexity of their battery management and electronic architecture. Dark current refers to the current consumption of the vehicle when it is off. Proper control of dark current not only extends the vehicle's idle time but also prevents starting failures or safety issues caused by low battery, thus ensuring vehicle reliability and user experience. In related technologies, when a controller software malfunctions and fails to enter sleep mode, even if the battery management system attempts to replenish power from the battery, the limitations of the number of replenishments and the battery's capacity only temporarily alleviate the dark current problem. This cannot resolve the overall vehicle sleep mode failure and battery depletion risk caused by the specific controller malfunction, resulting in poor energy management efficiency and reliability.

[0003] There is currently no good solution to the above problems. Summary of the Invention

[0004] This application provides a vehicle controller hibernation method, a vehicle, and a storage medium to at least solve the technical problems in the related art where new energy vehicles cannot hibernate due to controller software malfunctions, resulting in low vehicle power management efficiency and poor system reliability.

[0005] According to one aspect of the embodiments of this application, a vehicle controller hibernation method is provided, comprising: when the vehicle is in a fully armed state, monitoring whether multiple controllers in the vehicle have working needs; in response to the multiple controllers having no working needs, monitoring whether at least one of the multiple controllers continuously and actively wakes up the vehicle's on-board local area network, and obtaining the monitoring result; and determining the hibernation adjustment mode corresponding to the multiple controllers based on the monitoring result.

[0006] Optionally, determining the hibernation adjustment method for multiple controllers based on the monitoring results includes: responding to the determination based on the monitoring results that at least one controller among the multiple controllers continuously and actively wakes up the vehicle local area network and meets the first hibernation adjustment condition, triggering at least one controller to re-enter hibernation mode by restarting at least one controller.

[0007] Optionally, the first hibernation adjustment condition includes: when the vehicle arming duration is greater than or equal to a first preset duration and the vehicle's battery charge is less than or equal to a preset percentage, the monitoring device in the vehicle detects that at least one controller continuously and actively wakes up the vehicle local area network for a duration greater than or equal to a second preset duration.

[0008] Optionally, triggering at least one controller to re-enter hibernation mode by restarting at least one controller includes: obtaining the diagnostic identifier of at least one controller; and sending a controller restart command to at least one controller based on the diagnostic identifier, so as to trigger at least one controller to re-enter hibernation mode by restarting at least one controller.

[0009] Optionally, determining the hibernation adjustment method for multiple controllers based on the monitoring results includes: responding to the monitoring results determining that at least one of the multiple controllers does not continuously and actively wake up the vehicle local area network and meets the second hibernation adjustment condition, triggering multiple controllers to re-enter hibernation mode by restarting multiple controllers.

[0010] Optionally, the second sleep adjustment conditions include: when the vehicle's battery sensor detects that the duration of the vehicle's static current is greater than or equal to a second preset duration, the ratio between the vehicle's static current value and the target value is greater than or equal to a preset value, and the vehicle's battery charge is less than or equal to a preset percentage, the duration for which the battery sensor requests to wake up the monitoring device is greater than or equal to a third preset duration, and multiple controllers are not communicating through the vehicle's local area network.

[0011] Optionally, triggering multiple controllers to re-enter sleep mode by restarting multiple controllers includes: using a monitoring device to wake up multiple controllers to enter communication state; in response to multiple controllers entering communication state, sending a controller restart command to multiple controllers via function addressing broadcast, so as to trigger multiple controllers to re-enter sleep mode by restarting multiple controllers.

[0012] Optionally, the vehicle controller hibernation method further includes: in response to multiple controllers having operational needs, using a monitoring device to control multiple controllers to maintain communication.

[0013] According to another aspect of the embodiments of this application, a vehicle controller hibernation device is also provided, comprising: a first monitoring module, used to monitor whether multiple controllers in the vehicle have working needs when the vehicle is in a fully armed state; a second monitoring module, used to monitor whether at least one controller among the multiple controllers continuously and actively wakes up the vehicle's on-board local area network in response to the multiple controllers having no working needs, and obtain monitoring results; and a determination module, used to determine the hibernation adjustment mode corresponding to the multiple controllers based on the monitoring results.

[0014] Optionally, the determining module is further configured to: respond to a determination based on monitoring results that at least one of the multiple controllers continuously and actively wakes up the vehicle local area network and meets the first sleep adjustment condition, and trigger at least one controller to re-enter sleep mode by restarting at least one controller.

[0015] Optionally, the first hibernation adjustment condition includes: when the vehicle arming duration is greater than or equal to a first preset duration and the vehicle's battery charge is less than or equal to a preset percentage, the monitoring device in the vehicle detects that at least one controller continuously and actively wakes up the vehicle local area network for a duration greater than or equal to a second preset duration.

[0016] Optionally, the determining module is further configured to: obtain a diagnostic identifier of at least one controller; and send a controller restart command to at least one controller based on the diagnostic identifier, so as to trigger at least one controller to re-enter hibernation mode by restarting at least one controller.

[0017] Optionally, the determining module is also used to: respond to the determination based on the monitoring results that at least one of the multiple controllers does not continuously and actively wake up the vehicle local area network and meet the second sleep adjustment condition, and trigger the multiple controllers to re-enter the sleep mode by restarting the multiple controllers.

[0018] Optionally, the second sleep adjustment conditions include: when the vehicle's battery sensor detects that the duration of the vehicle's static current is greater than or equal to a second preset duration, the ratio between the vehicle's static current value and the target value is greater than or equal to a preset value, and the vehicle's battery charge is less than or equal to a preset percentage, the duration for which the battery sensor requests to wake up the monitoring device is greater than or equal to a third preset duration, and multiple controllers are not communicating through the vehicle's local area network.

[0019] Optionally, the determining module is also used to: wake up multiple controllers to enter the communication state using the monitoring device; and in response to multiple controllers entering the communication state, send a controller restart command to multiple controllers via function addressing broadcast, so as to trigger multiple controllers to re-enter the sleep mode by restarting multiple controllers.

[0020] Optionally, the vehicle controller sleep device further includes: a control module for controlling multiple controllers to maintain communication status using a monitoring device in response to multiple controllers having operational needs.

[0021] According to another aspect of the embodiments of this application, a vehicle is also provided, including: a memory storing an executable program; and a processor for running the program, wherein the program executes the methods in various embodiments of this application when it runs.

[0022] According to another aspect of the embodiments of this application, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored executable program, wherein, when the executable program is running, it controls the device where the computer-readable storage medium is located to perform the methods of various embodiments of this application.

[0023] According to another aspect of the embodiments of this application, a computer program product is also provided, including a computer program that, when executed by a processor, implements the methods of various embodiments of this application.

[0024] According to another aspect of the embodiments of this application, a computer program product is also provided, including a non-volatile computer-readable storage medium storing a computer program that, when executed by a processor, implements the methods in various embodiments of this application.

[0025] According to another aspect of the embodiments of this application, a computer program is also provided, which, when executed by a processor, implements the methods of the various embodiments of this application.

[0026] In this embodiment, by monitoring whether multiple controllers within the vehicle have operational needs when the vehicle is in a fully armed state, and further monitoring whether at least one controller continuously and actively wakes up the vehicle's onboard local area network when none of the controllers have operational needs, the monitoring results are obtained. Finally, based on the monitoring results, the corresponding sleep adjustment methods for multiple controllers are determined. This ensures the energy management efficiency and safety performance of the vehicle during long-term parking, further enhancing the user experience during vehicle idling. By dynamically monitoring network activity in the armed state, the phenomenon of increased dark current caused by abnormal controller wake-ups can be detected and intervened in a timely manner. By implementing a controller restart strategy under specific conditions, not only can the problem of controllers failing to enter sleep mode be specifically solved, but also the risk of vehicle-wide power loss caused by abnormal dark current is effectively reduced without increasing hardware costs. This achieves the technical effect of improving vehicle energy management efficiency and system reliability, thereby solving the technical problem of poor energy management efficiency and poor system reliability in new energy vehicles due to controller software abnormalities preventing them from entering sleep mode. Attached Figure Description

[0027] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0028] Figure 1 This is a flowchart of a vehicle controller sleep method according to an embodiment of this application;

[0029] Figure 2 This is a schematic diagram of a vehicle controller sleep system according to an embodiment of this application;

[0030] Figure 3 This is a schematic diagram of a vehicle controller sleep method according to an embodiment of this application;

[0031] Figure 4 This is a structural block diagram of a vehicle controller sleep device according to an embodiment of this application. Detailed Implementation

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

[0033] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0034] According to an embodiment of this application, a method embodiment for a vehicle controller to go into sleep mode is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0035] This method embodiment can be executed in an electronic device or similar computing device that includes memory and a processor. Taking operation on a computer terminal as an example, the computer terminal may include one or more processors (processors may include, but are not limited to, central processing units (CPUs), graphics processing units (GPUs), digital signal processing (DSP) chips, microcontroller units (MCUs), field-programmable gate arrays (FPGAs), neural network processors (NPUs), tensor processors (TPUs), artificial intelligence (AI) type processors, etc.) and memory for storing data. Optionally, the computer terminal may also include transmission devices, input / output devices, and display devices for communication functions. Those skilled in the art will understand that the above structural description is merely illustrative and does not limit the structure of the computer terminal. For example, the computer terminal may include more or fewer components than described above, or have a different configuration than described above.

[0036] The memory can be used to store computer programs, such as application software programs and modules, like the computer program corresponding to the vehicle controller sleep method in this embodiment. The processor executes various functional applications and data processing by running the computer program stored in the memory, thereby implementing the aforementioned vehicle controller sleep method. The memory may include high-speed random access memory and non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory may further include memory remotely located relative to the processor, and these remote memories can be connected to the mobile terminal via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0037] The transmission device is used to receive or send data via a network. Specific examples of the network mentioned above may include a wireless network provided by the mobile terminal's communication provider. In one example, the transmission device includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device may be a Radio Frequency (RF) module, used for wireless communication with the Internet.

[0038] Display devices can be, for example, touchscreen liquid crystal displays (LCDs) and touch displays (also referred to as "touchscreens" or "touch displays"). The LCD allows users to interact with the user interface of the mobile terminal. In some embodiments, the mobile terminal has a graphical user interface (GUI), which allows users to interact with the GUI through finger contact and / or gestures on a touch-sensitive surface. Optional human-computer interaction functions include: creating web pages, drawing, word processing, creating electronic documents, playing games, video conferencing, instant messaging, sending and receiving emails, call interfaces, playing digital video, playing digital music, and / or web browsing, etc. Executable instructions for performing the above human-computer interaction functions are configured / stored in one or more processor-executable computer program products or readable storage media.

[0039] This embodiment provides a method for putting a vehicle controller into sleep mode. Figure 1 This is a flowchart of a vehicle controller sleep method according to an embodiment of this application, such as... Figure 1 As shown, the process includes the following steps:

[0040] Step S11: When the vehicle is in a fully armed state, monitor whether multiple controllers inside the vehicle have operational requirements.

[0041] Step S12: In response to the fact that none of the multiple controllers have a working requirement, monitor whether at least one of the multiple controllers continuously and actively wakes up the vehicle's in-vehicle local area network, and obtain the monitoring results.

[0042] Step S13: Determine the sleep adjustment method for multiple controllers based on the monitoring results.

[0043] The aforementioned vehicle armed state refers to the vehicle being locked via the central locking system after the engine is shut off, the high-voltage system is disconnected, and the doors are closed. In this state, the vehicle is stationary and unauthorized wake-up operations are not permitted. Monitoring the controllers' operational needs in this state means checking whether each controller needs to perform necessary non-driver-operated functions such as remote updates, anti-theft alarms, and battery status monitoring. This operational need checking is based on the vehicle's communication protocol, confirming whether the controllers are sending signals indicating that tasks are pending.

[0044] For example, when the vehicle is in a fully armed state, it is possible to monitor whether multiple controllers within the vehicle have operational needs. This process can be performed by a monitoring device (such as a gateway). The monitoring device can check whether each controller needs to perform any tasks or functions in the current state through communication with each controller.

[0045] The aforementioned operational requirements include, but are not limited to, remote software updates, vehicle status monitoring, anti-theft system activation, or other necessary background operations. The monitoring device can accurately determine whether each controller is in a necessary active state or should enter a sleep mode to save power when the vehicle is in full-arm mode. If no operational requirements are detected, the next step is to further monitor the network for any abnormal controller wake-ups to ensure that all non-essential controllers enter a deep sleep state, thereby effectively managing the vehicle's dark current and avoiding unnecessary power consumption.

[0046] When multiple controllers have no operational needs, the system monitors whether at least one controller continuously and actively wakes up the vehicle's onboard local area network (VLAN). The monitoring results are then obtained. The VLAN is a network standard used for exchanging data between multiple Electronic Control Units (ECUs) within a vehicle. When at least one controller continuously and actively wakes up the vehicle's VLAN, it indicates that a controller is sending continuous network communication requests or data packets, causing the entire network to be in an active state rather than a dormant state, thereby increasing the vehicle's dark current consumption. The monitoring results refer to the information obtained through the monitoring device, namely whether the VLAN has been abnormally woken up, and whether one or more controllers are continuously sending wake-up signals.

[0047] For example, the monitoring device can determine whether a controller has violated normal sleep logic by parsing network management messages, such as heartbeat messages or status messages. If an abnormally awakened controller is detected, the monitoring device will record this information as a monitoring result. The monitoring result helps in subsequent decisions on whether and how to restart these controllers to restore them to normal sleep state. The monitoring result is crucial for subsequent sleep adjustment measures and is a key basis for ensuring that the vehicle can effectively manage energy when there is no driver operation, avoiding power waste and excessive battery discharge.

[0048] Based on the monitoring results, the corresponding sleep adjustment mode for multiple controllers is determined. The sleep adjustment mode can be a control strategy implemented after an abnormal wake-up situation is detected, in order to prompt the vehicle and its controller to enter the energy-saving mode and reduce dark current.

[0049] Specifically, when the monitoring device detects that at least one controller has failed to enter deep sleep mode as expected and instead continues to send wake-up signals, causing the vehicle's dark current to exceed a predetermined target value, it can analyze the monitored data to determine which controller(s) caused the anomaly. Subsequently, the monitoring device will adopt different sleep adjustment strategies. For example, if the specific abnormal controller can be identified through network management messages, the monitoring device will directly send an ECU restart command corresponding to the specific diagnostic service identifier (SID 0x12) to that controller, forcing it to restart and re-enter network sleep mode.

[0050] If it is difficult to determine exactly which controller is causing the abnormal dark current, the monitoring device will take more comprehensive measures. It will send the above-mentioned ECU restart command to all network controllers through function address 0x7DF, prompting all controllers to reinitialize and ensuring that the overall dark current level of the vehicle drops to the normal range.

[0051] The sleep adjustment method based on monitoring results can not only effectively deal with the dark current problem caused by individual controller software failures, but also quickly restore the vehicle's sleep state through a collective restart strategy in complex situations. This ensures that the battery is not depleted during long-term parking or non-use, and that the vehicle can start and run normally when needed, effectively improving the safety and efficiency of vehicle power management.

[0052] Based on steps S11 to S13 above, by monitoring whether multiple controllers within the vehicle have operational needs when the vehicle is in a fully armed state, and then, in response to the absence of operational needs from multiple controllers, monitoring whether at least one controller continuously and actively wakes up the vehicle's onboard local area network, the monitoring results are obtained. Finally, based on the monitoring results, the corresponding sleep adjustment methods for multiple controllers are determined. This ensures the energy management efficiency and safety performance of the vehicle during long-term parking, further enhancing the user experience during vehicle idling. By dynamically monitoring network activity in the vehicle's armed state, the phenomenon of increased dark current caused by abnormal controller wake-ups can be detected and intervened in a timely manner. By implementing controller restart strategies under specific conditions, not only can the problem of controllers failing to enter sleep mode be specifically addressed, but also the risk of vehicle-wide power loss caused by abnormal dark current is effectively reduced without increasing hardware costs. This achieves the technical effect of improving vehicle energy management efficiency and system reliability, thereby solving the technical problem of low energy management efficiency and poor system reliability in new energy vehicles due to controller software malfunctions preventing them from entering sleep mode.

[0053] The vehicle controller hibernation method in the embodiments of this application will be further described below.

[0054] In one optional embodiment, determining the hibernation adjustment method corresponding to multiple controllers based on monitoring results includes: responding to the determination based on monitoring results that at least one controller among the multiple controllers continuously and actively wakes up the vehicle local area network and meets the first hibernation adjustment condition, triggering at least one controller to re-enter hibernation mode by restarting at least one controller.

[0055] When monitoring results determine that at least one of the multiple controllers is continuously and actively waking up the vehicle's local area network, it indicates that the monitoring device has reached a conclusion regarding whether the vehicle's local area network has been abnormally woken up, based on data received from the battery sensors and monitoring of the network activity status of multiple controllers.

[0056] The key indicators specifically included in the first hibernation adjustment conditions are: the vehicle's arming duration, the vehicle's battery charge, and the duration for which the vehicle's monitoring device detects at least one controller continuously and actively waking up the vehicle's local area network. The vehicle's arming duration refers to the time from the start of the vehicle's armed state to the current moment. During this period, the vehicle should be stationary, and all controllers should enter an energy-saving hibernation mode except for specific operational requirements. The vehicle's battery charge is expressed in the form of State of Charge (SOC), reflecting the current charging and discharging level of the vehicle's battery. When the battery charge is less than or equal to a preset percentage, it is considered to meet the low charge indicator in the first hibernation adjustment conditions. Furthermore, the monitoring device monitors the activity of each controller in the network. If, while the vehicle is armed, any controller continuously sends a network wake-up signal for a specific duration, it is considered to have violated the normal hibernation procedure and met the network wake-up duration indicator in the first hibernation adjustment conditions.

[0057] When monitoring results determine that at least one controller among multiple controllers is continuously and actively waking up the vehicle's local area network (LAN), and the first hibernation adjustment condition is met, at least one controller is restarted, triggering it to re-enter hibernation mode. The monitoring device can force the corresponding controller to stop its current operation and restart by sending a specific diagnostic service SID 0x12 ECU restart command to it. This aims to eliminate the root cause of abnormal LAN wake-ups, forcing the controller to return to its initial state or enter deep hibernation mode, thereby reducing dark current consumption. Re-entering hibernation mode describes the expected state of the restarted controller, ensuring that even when the vehicle is armed, each controller maintains minimal power consumption, avoiding energy waste caused by abnormal controller activity.

[0058] Based on the above optional embodiments, by responding to the monitoring results and determining that at least one of the multiple controllers continuously and actively wakes up the vehicle local area network and meets the first sleep adjustment condition, at least one controller is restarted to trigger at least one controller to re-enter the sleep mode, which can quickly restore to the energy-saving sleep state, significantly reduce the dark current of the whole vehicle caused by abnormal wake-up of the controller, reduce power loss, and prevent the battery from prematurely losing power when unsupervised, thereby bringing users a more reliable and economical vehicle use experience.

[0059] In one optional embodiment, the first sleep adjustment condition includes: when the vehicle arming duration is greater than or equal to a first preset duration and the vehicle's battery charge is less than or equal to a preset percentage, the monitoring device in the vehicle detects that at least one controller continuously and actively wakes up the vehicle local area network for a duration greater than or equal to a second preset duration.

[0060] The vehicle arming duration is the time elapsed from the last time the vehicle was powered off and entered arming mode until the current moment. This helps determine the length of time the vehicle has been idle or parked, and is an important reference for deciding whether a new energy vehicle needs to enter deep hibernation mode. The aforementioned first preset duration is a threshold, such as 60 minutes, used to distinguish between short-term parking and long-term parking. Only when the vehicle arming duration is greater than or equal to this preset duration is the vehicle considered to have entered a suitable long-term parking state for deep hibernation, and then the need for hibernation adjustment is considered.

[0061] By defining the condition that the vehicle's battery charge is less than or equal to a preset percentage, this application embodiment clarifies another important indicator for implementing the hibernation adjustment strategy. Specifically, when the vehicle's battery capacity is low (e.g., SOC ≤ 50%), managing dark current becomes more urgent to prevent power depletion due to excessive energy consumption. The preset percentage, as a threshold, reflects the importance of taking preventative measures before the battery charge reaches a dangerous level.

[0062] The monitoring device detects the duration for which at least one controller continuously and actively wakes up the vehicle's local area network. This focuses on the vehicle's internal monitoring system's ability to detect controllers that have not entered deep sleep mode as usual, but instead continuously send wake-up signals to the network, leading to increased dark current. A second preset duration is used to distinguish between occasional network activity and persistent abnormal wake-ups. Only when the abnormal wake-up duration of a controller is greater than or equal to this preset duration, for example, ≥5 minutes, will the monitoring device consider it a serious situation requiring intervention.

[0063] For example, after the vehicle enters the armed state, the monitoring device begins recording the entire vehicle's armed duration while simultaneously monitoring the vehicle's battery level. Upon reaching or exceeding a first preset duration, the monitoring device also needs to confirm whether the vehicle's battery level is below a preset percentage, ensuring that the impact of the network wake-up event is only further evaluated when the vehicle is parked for an extended period and the battery level is low. When the entire vehicle's armed duration meets the conditions and the battery level also meets the low-battery requirement, the monitoring device will closely monitor the vehicle network to identify whether a controller is continuously and actively waking up the vehicle's local area network; this monitoring duration must reach a second preset duration standard.

[0064] Based on the above optional embodiments, by setting the first hibernation adjustment conditions, the abnormal dark current of new energy vehicles when they are parked for a long time and have insufficient power is precisely controlled. This not only improves the efficiency of power management, but also provides new energy vehicle users with higher safety and convenience while avoiding power waste. It ensures the stability of the vehicle's electronic control system during non-driving periods, extends the service life of the battery, optimizes the vehicle's storage and transportation characteristics, and reduces maintenance costs.

[0065] In one optional embodiment, triggering at least one controller to re-enter hibernation mode by restarting at least one controller includes: obtaining a diagnostic identifier of at least one controller; and sending a controller restart command to at least one controller based on the diagnostic identifier, so as to trigger at least one controller to re-enter hibernation mode by restarting at least one controller.

[0066] The aforementioned diagnostic identifier (ID) is a unique code used to uniquely identify controllers within the vehicle, enabling monitoring devices to accurately locate the controller requiring a restart. Defined in the vehicle's communication protocol, the diagnostic identifier ensures the identifiability of each controller within the network. By acquiring the diagnostic identifier of at least one controller, the monitoring device can achieve precise control of a specific controller, avoiding erroneous operations on unrelated controllers and improving the accuracy and efficiency of restart operations.

[0067] The controller restart command described above is a restart service defined according to diagnostic service SID 0x12. It can be sent to the target controller via a specific communication message, forcing it to stop its current operating state and restart. The controller restart command includes the target controller's diagnostic identifier and the instruction of SID 0x12, ensuring the correct sending and receiving of the restart command, thereby quickly and effectively eliminating the source of abnormal network wake-ups. The data flow between the monitoring device and the controller is shown in Table 1:

[0068] Table 1 Controller Data Flow Correspondence Table

[0069]

[0070] After the monitoring device has identified that the abnormal network wake-up was caused by a specific controller, it needs to accurately obtain the diagnostic identifier of that controller from the communication network to ensure that subsequent restart operations can be performed precisely. When obtaining the diagnostic identifier, it can be done through analysis of network management messages or by directly reading from an established network node database, ensuring that the monitoring device can quickly locate the controller that needs to be restarted.

[0071] Once the monitoring device obtains the diagnostic identifier of the malfunctioning controller, it sends an ECU Reset command with SID 0x12 to the target controller based on the diagnostic identifier. The transmission of the controller restart command follows a standard communication protocol and uses a defined communication line to ensure that the command is transmitted to the designated controller in a timely and accurate manner, triggering the subsequent restart process. By using targeted diagnostic service commands, indiscriminate restarts across the entire network are avoided, reducing the impact on the normal operation of the vehicle's electronic control system.

[0072] Based on the above optional embodiments, by obtaining the diagnostic identifier of at least one controller, and then sending a controller restart command to at least one controller based on the diagnostic identifier, the at least one controller is triggered to re-enter the hibernation mode by restarting at least one controller. This ensures that even under adverse conditions such as the whole vehicle being protected and the battery power being low, the dark current problem caused by the abnormality of individual controllers can be quickly identified and resolved, avoiding the risk of power loss caused by excessive power consumption. This not only enhances the self-repair capability of the vehicle's electronic control system, but also improves the overall stability and energy management efficiency of the electronic control system.

[0073] In one optional embodiment, determining the hibernation adjustment method for multiple controllers based on monitoring results includes: responding to the determination based on monitoring results that at least one of the multiple controllers does not continuously and actively wake up the vehicle local area network and meets the second hibernation adjustment condition, triggering multiple controllers to re-enter hibernation mode by restarting multiple controllers.

[0074] The aforementioned second sleep adjustment condition is the basis for the monitoring device to decide to restart multiple controllers, ensuring that under specific dark current anomalies, the controllers can be effectively restarted through software strategies to re-enter sleep mode. The second sleep adjustment condition specifically includes the following key indicators: the duration of the vehicle's static current, the ratio between the current value and the target value, the vehicle's battery charge, the duration for which the battery sensor requests to wake up the monitoring device, and whether multiple controllers communicate via the vehicle's local area network.

[0075] The duration of the vehicle's static current is the duration during which the monitoring device detects abnormal dark current through the battery sensor. When the duration of the vehicle's static current reaches or exceeds a second preset duration (e.g., 5 minutes), it indicates abnormal energy consumption. The ratio between the current value and the target value reflects the degree of deviation of the dark current from the target value of the dark current in normal sleep mode. When this ratio is greater than or equal to a preset value (e.g., twice), it indicates a significant abnormality in dark current. The vehicle's battery charge is expressed in the form of SOC. When it is less than or equal to a preset percentage (e.g., 50%), it indicates that the vehicle's energy reserves are at a low level, and measures need to be taken to avoid further energy waste. When the battery sensor detects an abnormal dark current, it will continuously send wake-up requests to the monitoring device. If the duration of the battery sensor's wake-up request reaches or exceeds a third preset duration (e.g., 1 minute), it will trigger the monitoring device to enter working mode and begin executing a restart command. In the armed state, if the monitoring device detects that all network controllers are not communicating effectively on the vehicle's local area network, it indicates that the vehicle is in deep sleep mode, but the dark current is still abnormal, and further measures need to be taken.

[0076] Based on the above optional embodiments, by responding to the monitoring results and determining that at least one of the multiple controllers does not continuously and actively wake up the vehicle local area network and meet the second sleep adjustment condition, multiple controllers are restarted to trigger them to re-enter sleep mode. This can intelligently and accurately identify the situation where the dark current is abnormally increased in the deep sleep state of the vehicle, and then cause all network controllers to re-enter sleep mode by restarting them. This effectively reduces the dark current of the whole vehicle, avoids the risk of battery depletion caused by excessive power consumption, not only improves the stability of the electronic control system, but also helps to extend the battery life and ensure the energy safety of the vehicle during non-driving periods.

[0077] In one optional embodiment, the second sleep adjustment condition includes: when the vehicle's battery sensor detects that the duration of the vehicle's static current is greater than or equal to a second preset duration, the ratio between the vehicle's static current value and the target value is greater than or equal to a preset value, and the vehicle's battery charge is less than or equal to a preset percentage, the duration for which the battery sensor requests to wake up the monitoring device is greater than or equal to a third preset duration, and multiple controllers are not communicating through the vehicle's local area network.

[0078] The aforementioned vehicle quiescent current refers to the total current consumed by all electrical equipment and control systems when the vehicle is in an armed state. The vehicle quiescent current is typically very small, but sufficient to maintain basic vehicle functions, such as the anti-theft system. Monitoring the duration of the vehicle quiescent current helps to promptly detect abnormal increases in quiescent current and prevent battery depletion caused by prolonged quiescent current consumption.

[0079] The aforementioned second preset duration is a time threshold, for example, 5 minutes, used by the monitoring device to determine whether the dark current is abnormal. When the vehicle's static current remains above the normal level for the second preset duration, the monitoring device will consider the dark current abnormal and take action. The setting of the second preset duration reflects the sensitivity to dark current anomalies, helping to detect problems and intervene in the early stages.

[0080] The aforementioned target value can be a pre-set reasonable upper limit for the vehicle's static current. When the ratio between the actual monitored current value and the target value is greater than or equal to the preset value, it indicates that the dark current exceeds the normal range, which may lead to energy waste and shorten battery life.

[0081] The aforementioned preset value serves as a comparison standard and can quantify the severity of dark current anomalies. For example, the preset value can be set to twice the target value.

[0082] The aforementioned preset percentage is a set battery power threshold, such as 50%. When the battery power is lower than the preset percentage, the monitoring device will take measures to reduce energy consumption and prevent power loss.

[0083] To ensure the monitoring device can respond promptly to dark current anomalies, the battery sensor continuously attempts to wake the monitoring device. If the wake-up request duration reaches or exceeds a third preset duration (e.g., 1 minute), the monitoring device is deemed to need to intervene immediately. This third preset duration is the time threshold for the monitoring device to be woken from sleep mode and begin processing dark current anomalies; for example, it is set to 1 minute.

[0084] Based on the above optional embodiments, by setting a second hibernation adjustment condition, multiple controllers can be restarted in a timely manner, prompting them to re-enter a safe hibernation state, effectively avoiding battery depletion caused by excessive dark current, thereby ensuring the power safety of new energy vehicles and the reliability of vehicle functions during non-use periods.

[0085] In one optional embodiment, triggering multiple controllers to re-enter sleep mode by restarting multiple controllers includes: waking up multiple controllers to enter communication state using a monitoring device; and in response to multiple controllers entering communication state, sending a controller restart command to multiple controllers via function addressing broadcast, so as to trigger multiple controllers to re-enter sleep mode by restarting multiple controllers.

[0086] By using a monitoring device to wake up multiple controllers and put them into communication mode, multiple controllers can be activated, enabling them to receive and process network communication commands. This ensures that all relevant controllers are in a communication state capable of receiving commands before the restart strategy is implemented, thereby guaranteeing the accurate execution of the restart command.

[0087] When multiple controllers enter a communication state, a controller restart command is sent to all controllers via function addressing broadcast. Function addressing broadcast is a specific network communication strategy that broadcasts restart commands to multiple controllers on the network through function addressing, avoiding point addressing by a single controller and improving the efficiency of command sending and the comprehensiveness of the restart.

[0088] The controller restart command can be a restart instruction defined based on the diagnostic service SID 0x12. This command is sent to the target controller via network communication, forcing it to stop its current operating state and restart.

[0089] Upon receiving the restart command, multiple controllers will immediately cease their current activity and restart. After restarting, multiple controllers will re-enter sleep mode, thereby effectively reducing the vehicle's dark current and preventing battery depletion caused by sustained high dark current.

[0090] Based on the above optional embodiments, by using a monitoring device to wake up multiple controllers and put them into communication mode, and then responding to the multiple controllers entering communication mode, a controller restart command is sent to multiple controllers through a function addressing broadcast method. By restarting multiple controllers, multiple controllers are triggered to re-enter the sleep mode, which can effectively reduce the dark current of the whole vehicle, prevent the battery from being depleted, and thus ensure the power safety of the vehicle and the stability of the electronic control system during non-use periods.

[0091] In an alternative embodiment, the vehicle controller hibernation method further includes: in response to multiple controllers having operational needs, using a monitoring device to control the multiple controllers to maintain a communication state.

[0092] When a vehicle is armed, some or all of the multiple controllers still need to perform specific tasks or functions, such as charging management, emergency communication, and remote monitoring. Identifying the operational needs of multiple controllers allows the monitoring device to distinguish between normal operational needs and abnormal wake-ups, thereby avoiding unnecessary restarts of the controllers when there are legitimate reasons.

[0093] When the monitoring device identifies a controller among multiple controllers that has operational needs, it will control the multiple controllers to remain in communication to ensure that they can continue to perform the necessary tasks.

[0094] Based on the above optional embodiments, by responding to the working needs of multiple controllers, the monitoring device controls multiple controllers to maintain communication, which not only avoids the functional loss caused by improper hibernation, but also significantly reduces the energy consumption of the vehicle in the armed state through precise energy management, effectively prevents the battery from running out of power, and ensures the power safety and functional integrity of new energy vehicles during long-term parking or non-use periods.

[0095] Figure 2 This is a schematic diagram of a vehicle controller sleep system according to an embodiment of this application, as shown below. Figure 2 As shown, the system includes: a battery sensor, a monitoring device (usually a gateway), and multiple controllers, namely controller 1, controller 2, ..., controller n. The monitoring device can communicate with each controller and the battery sensor via communication lines. If controller 1 cannot enter network sleep mode, the monitoring device can determine that the target controller is controller 1 through the network management message ID. The monitoring device uses the diagnostic ID of controller 1 and the controller restart command to restart controller 1, thereby causing controller 1 to re-enter network sleep mode.

[0096] If controller 1 can enter network sleep mode but cannot enter deep sleep mode, causing the vehicle's static current to be significantly higher than the target value, the monitoring device can detect the abnormal dark current of the entire vehicle through the battery sensor, but cannot determine which controller is affected. In this case, the monitoring device can use function address 0x7DF and the controller restart command to restart all network controllers, allowing controllers that are not in deep sleep mode to re-enter sleep mode.

[0097] Figure 3 This is a schematic diagram of a vehicle controller sleep method according to an embodiment of this application, as shown below. Figure 3 As shown, when the vehicle is in a fully armed state, the system monitors whether multiple controllers within the vehicle have operational needs. If none of the controllers have operational needs, the system monitors whether at least one controller continuously and actively wakes up the vehicle's onboard local area network (LAN). If at least one controller continuously and actively wakes up the LAN and meets the first sleep adjustment condition (armed duration greater than or equal to 60 minutes, and the vehicle's battery charge less than or equal to 50%), and a controller is still detected to continuously (≥5 minutes) actively wake up the communication network, the system triggers that controller to re-enter sleep mode by restarting the specific controller. If no controller continuously and actively wakes up the LAN and meets the second sleep adjustment condition (the battery sensor detects a vehicle static current for a duration greater than or equal to ≥5 minutes, the ratio between the vehicle static current value and the target value is greater than or equal to 2, and the vehicle's battery charge is less than or equal to 50%), the system actively wakes up the monitoring device and triggers multiple controllers to re-enter sleep mode by restarting them.

[0098] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0099] According to an embodiment of this application, an apparatus embodiment for a vehicle controller sleep method is provided. It should be noted that the apparatus can be used to execute the above-described vehicle controller sleep method.

[0100] Figure 4 This is a structural block diagram of a vehicle controller sleep device according to an embodiment of this application, such as... Figure 4 As shown, the device includes:

[0101] The first monitoring module 401 is used to monitor whether multiple controllers inside the vehicle have operational requirements when the vehicle is in a fully armed state.

[0102] The second monitoring module 402 is used to monitor whether at least one of the multiple controllers continuously and actively wakes up the vehicle's in-vehicle local area network in response to the fact that none of the multiple controllers have any working requirements, and obtain the monitoring results.

[0103] The determination module 403 is used to determine the sleep adjustment mode corresponding to multiple controllers based on the monitoring results.

[0104] Optionally, the determining module 403 is further configured to: respond to the determination based on the monitoring results that at least one of the multiple controllers continuously and actively wakes up the vehicle local area network and meets the first sleep adjustment condition, and trigger at least one controller to re-enter the sleep mode by restarting at least one controller.

[0105] Optionally, the first hibernation adjustment condition includes: when the vehicle arming duration is greater than or equal to a first preset duration and the vehicle's battery charge is less than or equal to a preset percentage, the monitoring device in the vehicle detects that at least one controller continuously and actively wakes up the vehicle local area network for a duration greater than or equal to a second preset duration.

[0106] Optionally, the determining module 403 is further configured to: obtain a diagnostic identifier of at least one controller; and send a controller restart command to at least one controller based on the diagnostic identifier, so as to trigger at least one controller to re-enter the hibernation mode by restarting at least one controller.

[0107] Optionally, the determining module 403 is further configured to: respond to the determination based on the monitoring results that at least one of the multiple controllers does not continuously and actively wake up the vehicle local area network and meets the second sleep adjustment condition, and trigger the multiple controllers to re-enter the sleep mode by restarting the multiple controllers.

[0108] Optionally, the second sleep adjustment conditions include: when the vehicle's battery sensor detects that the duration of the vehicle's static current is greater than or equal to a second preset duration, the ratio between the vehicle's static current value and the target value is greater than or equal to a preset value, and the vehicle's battery charge is less than or equal to a preset percentage, the duration for which the battery sensor requests to wake up the monitoring device is greater than or equal to a third preset duration, and multiple controllers are not communicating through the vehicle's local area network.

[0109] Optionally, the determining module 403 is further configured to: wake up multiple controllers to enter the communication state using the monitoring device; and in response to multiple controllers entering the communication state, send a controller restart command to multiple controllers via function addressing broadcast, so as to trigger multiple controllers to re-enter the sleep mode by restarting multiple controllers.

[0110] Optionally, the vehicle controller sleep device further includes: a control module 404, used to control multiple controllers to maintain communication status in response to multiple controllers having operational needs, using a monitoring device.

[0111] It should be noted that the above modules can be implemented by software or hardware. For the latter, they can be implemented in the following ways, but are not limited to: all the above modules are located in the same processor; or, the above modules are located in different processors in any combination.

[0112] Embodiments of this application also provide a vehicle, including: a memory storing an executable program; and a processor for running the program, wherein the program executes the methods described in various embodiments of this application when it runs.

[0113] Optionally, in this embodiment, the processor can be configured to perform the following steps via a computer program:

[0114] S1, when the vehicle is in a fully armed state, monitor whether multiple controllers inside the vehicle have operational requirements;

[0115] S2, in response to the fact that multiple controllers have no working requirements, monitor whether at least one of the multiple controllers continuously and actively wakes up the vehicle's in-vehicle local area network, and obtain the monitoring results;

[0116] S3 determines the sleep adjustment method for multiple controllers based on the monitoring results.

[0117] Embodiments of this application also provide a computer-readable storage medium including a stored executable program, wherein, when the executable program is running, it controls the device where the computer-readable storage medium is located to perform the methods of various embodiments of this application.

[0118] Optionally, in this embodiment, the storage medium may be configured to store a computer program for performing the following steps:

[0119] S1, when the vehicle is in a fully armed state, monitor whether multiple controllers inside the vehicle have operational requirements;

[0120] S2, in response to the fact that multiple controllers have no working requirements, monitor whether at least one of the multiple controllers continuously and actively wakes up the vehicle's in-vehicle local area network, and obtain the monitoring results;

[0121] S3 determines the sleep adjustment method for multiple controllers based on the monitoring results.

[0122] Embodiments of this application also provide a computer program product, including a computer program that, when executed by a processor, implements the methods of various embodiments of this application.

[0123] Embodiments of this application also provide a computer program product, including a non-volatile computer-readable storage medium for storing a computer program that, when executed by a processor, implements the methods in various embodiments of this application.

[0124] Embodiments of this application also provide a computer program that, when executed by a processor, implements the methods described in the various embodiments of this application.

[0125] In the above embodiments of this application, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0126] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For instance, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling, direct coupling, or communication connection may be through some interfaces; the indirect coupling or communication connection between units or modules may be electrical or other forms.

[0127] 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 units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

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

[0129] 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 described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard drive, magnetic disk, or optical disk.

[0130] The above description is only a preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A method for putting a vehicle controller into sleep mode, characterized in that, include: When the vehicle is in a fully armed state, monitor whether multiple controllers inside the vehicle have operational requirements; In response to the fact that none of the multiple controllers have a working requirement, the system monitors whether at least one of the multiple controllers continuously and actively wakes up the vehicle's on-board local area network, and obtains the monitoring results. Based on the monitoring results, the sleep adjustment method corresponding to the multiple controllers is determined; The method for determining the hibernation adjustment mode corresponding to the plurality of controllers based on the monitoring results includes: responding to the determination based on the monitoring results that at least one of the plurality of controllers does not continuously and actively wake up the vehicle local area network and meets the second hibernation adjustment condition; using the monitoring device to wake up the plurality of controllers to enter the communication state; and responding to the plurality of controllers entering the communication state by sending a controller restart command to the plurality of controllers through a function addressing broadcast method, so as to trigger the plurality of controllers to re-enter the hibernation mode by restarting the plurality of controllers.

2. The vehicle controller sleep method according to claim 1, characterized in that, Based on the monitoring results, the sleep adjustment methods corresponding to the multiple controllers are determined as follows: Based on the monitoring results, if it is determined that at least one of the multiple controllers continuously and actively wakes up the vehicle local area network and meets the first sleep adjustment condition, the controller is restarted to trigger the controller to re-enter sleep mode.

3. The vehicle controller sleep method according to claim 2, characterized in that, The first hibernation adjustment conditions include: When the duration of vehicle arming is greater than or equal to a first preset duration, and the battery charge of the vehicle is less than or equal to a preset percentage, the monitoring device in the vehicle detects that the duration of the at least one controller continuously and actively waking up the vehicle local area network is greater than or equal to a second preset duration.

4. The vehicle controller sleep method according to claim 2, characterized in that, Triggering the at least one controller to re-enter the hibernation mode by restarting the at least one controller includes: Obtain the diagnostic identifier of the at least one controller; Based on the diagnostic identifier, a controller restart command is sent to the at least one controller to trigger the at least one controller to re-enter the hibernation mode by restarting the at least one controller.

5. The vehicle controller sleep method according to claim 1, characterized in that, The second hibernation adjustment conditions include: When the vehicle's battery sensor detects that the duration of the vehicle's static current is greater than or equal to a second preset duration, the ratio between the vehicle's static current value and the target value is greater than or equal to a preset value, and the vehicle's battery charge is less than or equal to a preset percentage, the duration for which the battery sensor requests to wake up the monitoring device is greater than or equal to a third preset duration, and the multiple controllers do not communicate through the vehicle's local area network.

6. The vehicle controller sleep method according to claim 1, characterized in that, The vehicle controller sleep method further includes: In response to the operational needs of the multiple controllers, a monitoring device is used to control the multiple controllers to maintain communication.

7. A vehicle, characterized in that, include: The system includes a battery sensor, a battery, a monitoring device, and multiple controllers, wherein the monitoring device is used to execute the vehicle controller sleep method according to any one of claims 1 to 6.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored executable program, wherein, when the executable program is executed, it controls the device on which the storage medium is located to perform the vehicle controller hibernation method according to any one of claims 1 to 6.

Images