Power management method, device, electronic device and medium for vehicle controller
Through hierarchical processing and status diagram management, the complexity and high power consumption problems of the power management system of the automotive controller are solved, efficient power supply and status switching are achieved, and the diversified power supply needs of the entire vehicle system are adapted to the diversified power supply needs.
Patent Information
- Application Number
- CN202310321074.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2023-03-29
- Publication Date
- 2025-08-26
- Estimated Expiration
- 2043-03-29
AI Technical Summary
The power management system of existing automotive controllers cannot effectively take into account the different power requirements of various functional modules in the vehicle system, resulting in high management complexity, large power consumption, and a single design method, making it difficult to adapt to the complex vehicle power environment.
By obtaining the multi-stage power requirement level of the automotive controller, performing domain-based hierarchical processing, defining multiple power domain power supplies, and building a power state diagram to realize one-to-many power supply and dynamic state switching to reduce power consumption.
It simplifies the power state and switching control logic, improves power supply management efficiency, reduces power consumption, and adapts to complex vehicle power supply environments.
Smart Images

Figure CN116300640B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of power management technology, and in particular to a power management method, device, electronic device, and medium for a vehicle controller. Background Art
[0002] With the advancement of digitalization and automation, the number of electronic control units (ECUs) in modern vehicles has rapidly increased, reaching hundreds. This has led to the increasing complexity of the entire control system, nearing its upper limit. This has necessitated the development of domain controllers (DCs). These DCs integrate core functions that previously required multiple ECUs, significantly improving system integration. Combined with standardized interfaces for data exchange, these DCs can significantly reduce development and manufacturing costs.
[0003] Current domain controllers, or vehicle controllers, are becoming increasingly complex as their functionality increases. Multi-chip designs lead to multi-domain power supply designs, necessitating refined power management. As vehicle controllers become increasingly integrated, the management framework and logic of existing vehicle power management systems are no longer adequate. Even if power management is implemented through domain controllers, allowing for separate power management for different functional domains, this approach lacks hierarchical management of the power domain system and cannot accommodate the diverse power requirements of various functional modules within the vehicle system.
[0004] At the same time, improving energy efficiency is crucial for both fuel-powered and electric vehicles. This requires not only low-power management but also energy management during controller operation to improve energy efficiency. Furthermore, the controller must provide an external power interface to facilitate user access, which complicates the controller's power supply design. Furthermore, given the complex power supply environment of the entire vehicle, the overall controller power supply design must account for abnormal operating conditions. However, current controller power supply designs often rely on a single power supply and a mechanically mapped structure. This results in a very simplistic design approach and power supply framework, resulting in cumbersome and complex hardware designs and inefficient control management.
[0005] Therefore, there is an urgent need for an efficient power management technology solution for automotive controllers. Summary of the Invention
[0006] In view of the above-mentioned shortcomings of the prior art, the present invention provides a power management technical solution for a vehicle controller to solve the above-mentioned technical problems.
[0007] To achieve the above-mentioned objectives and other related objectives, the present invention provides the following technical solutions.
[0008] A power management method for a vehicle controller, comprising:
[0009] Acquiring parameters of the vehicle controller, and acquiring a multi-level power demand level of the vehicle controller according to the parameters of the vehicle controller;
[0010] Providing an initial power supply, dividing the initial power supply into different domains and grading them according to the multi-level power demand levels of the vehicle controller to obtain multiple power domain power supplies, and performing one-to-many power supply within each power demand level according to each power domain power supply to aggregate the power supply modes of the vehicle controller;
[0011] Multiple power states of the vehicle controller are defined according to each of the power domain power supplies, and a power state diagram of the vehicle controller is constructed according to each of the power states. Management is performed through the power state diagram, and dynamic switching is performed between the multiple power states to reduce power consumption.
[0012] Optionally, the parameters of the vehicle controller include various functional domains of the vehicle controller and the inclusion and subordination relationships between the functional domains, the functional domains include a main functional domain and a subfunctional domain, each power requirement level includes one functional domain or multiple parallel functional domains, and the step of obtaining the multi-level power requirement level of the vehicle controller based on the parameters of the vehicle controller includes:
[0013] Obtaining each parallel main functional domain in the vehicle controller, and hierarchically processing each main functional domain according to the inclusion and subordination relationship between each functional domain until a specific component is obtained, thereby obtaining the subdomain level of each main functional domain;
[0014] Planning each of the main functional domains of the same level to the first level power requirement level, and planning each of the sub-functional domains of the i-th level sub-domain in each of the main functional domains to the (i+1)-th level power requirement level;
[0015] Wherein, i is an integer from 1 to n, n is the maximum number of subdomain levels of each of the main functional domains, and n is greater than or equal to 2.
[0016] Optionally, the step of performing domain-based and hierarchical processing on the initial power supply according to the multi-level power demand level of the vehicle controller to obtain multiple power domain power supplies, and performing one-to-many power supply within each power demand level according to each of the power domain power supplies to aggregate the power supply modes of the vehicle controller includes:
[0017] In each power demand level, the initial power supply is hierarchically processed to obtain a plurality of power domain power supplies of different sizes, some of the power domain power supplies are switched on and off, and then the power domain power supplies are correspondingly supplied to the functional domains in each power demand level;
[0018] The power demand levels of each level are cascaded in sequence, the initial power supply of the next power demand level is a power supply of the power domain of the previous power demand level, and the initial power supply of the first power demand level is a battery power supply.
[0019] Optionally, in each power demand level, the number of values of the initial power supply is greater than or equal to 1.
[0020] Optionally, within each power demand level, the initial power supply is graded by step-by-step step-down conversion to obtain multiple power domain power supplies of different sizes; and by connecting a controllable switch in series in the power supply circuit of the power domain power supply, switching control is performed on part of the power domain power supplies.
[0021] Optionally, the power domain power supply that is subjected to switch control is recorded as a controllable power domain power supply, and the power domain power supply that is not subjected to switch control is recorded as a common power domain power supply. The step of defining multiple power states of the vehicle controller according to each of the power domain power supplies, constructing a power state graph of the vehicle controller according to each of the power states, managing through the power state graph, and dynamically switching between the multiple power states to reduce power consumption includes:
[0022] Defining a plurality of power states of the vehicle controller according to a combination of states of power supplies in each of the power domains, wherein the power states include at least a power-on state, a safety state, a working state, and a low power consumption state;
[0023] Constructing a power state diagram of the vehicle controller according to each of the power states and the mutual evolution relationship between the power states;
[0024] State switching management is performed through the power state diagram, dynamic switching is performed between the multiple power states, and the low power consumption state is entered when the sleep condition is met to reduce power consumption.
[0025] Optionally, the working state includes at least a first working state and a second working state, the low power consumption state includes at least a first low power consumption state and a second low power consumption state, the sleep condition includes a first sleep condition and a second sleep condition, and the step of performing state switching management through the power state diagram and dynamically switching between the multiple power states includes:
[0026] Under normal circumstances, the device switches from the power-on state to the safe state, switches from the safe state to the first working state, or switches back and forth between the first working state and the second working state;
[0027] In the event of an abnormality, switching from the first working state or the second working state to the safe state;
[0028] When the first sleep condition is met, switching from the first working state or the second working state to the first low-power state; when awakened from the first low-power state, switching from the first low-power state to the first working state or the second working state;
[0029] When the second sleep condition is met, the first low power state is switched to the second low power state; when awakened from the second low power state, the second low power state is switched to the safe state.
[0030] Optionally, when state switching management is performed through the power state diagram and dynamic switching is performed between multiple power states, the power state request, state switching action and the power state are separated and operated asynchronously. First, it is determined whether there is a power state request. If there is a power state transition request, it is further determined whether the power switching conditions are met. If the power switching conditions are met, the state switching action is executed, and the power state is updated after the state switching action is completed.
[0031] A power management device for a vehicle controller, the device comprising:
[0032] A data acquisition module, used to obtain parameters of the vehicle controller;
[0033] A first processing module, configured to obtain a multi-level power demand level of the vehicle controller according to parameters of the vehicle controller;
[0034] a second processing module, configured to perform domain-based and hierarchical processing on the initial power supply according to the multi-level power demand level of the vehicle controller to obtain multiple power domain power supplies, and further configured to perform one-to-many power supply within each power demand level according to each of the power domain power supplies to aggregate the power supply modes of the vehicle controller;
[0035] The third processing module is used to define multiple power states of the vehicle controller according to each of the power domain power supplies, to construct a power state diagram of the vehicle controller according to each of the power states, and to manage through the power state diagram and dynamically switch between the multiple power states to reduce power consumption.
[0036] An electronic device, comprising:
[0037] one or more processors;
[0038] A storage device is used to store one or more programs, and when the one or more programs are executed by the one or more processors, the electronic device implements any of the above-mentioned methods for managing the power supply of the vehicle controller.
[0039] A computer-readable storage medium is characterized in that computer-readable instructions are stored thereon, and when the computer-readable instructions are executed by a processor of a computer, the computer is caused to execute any of the above-mentioned power management methods for a vehicle controller.
[0040] The beneficial effects of the present invention are as follows: first, a multi-level power demand level of the vehicle controller is obtained, and then the initial power supply is domain-divided and graded according to the multi-level power demand level to obtain multiple power domain power supplies, and one-to-many power supply is performed based on each power domain power supply within each power demand level, which can effectively aggregate the power supply mode of the vehicle controller. It is no longer a cumbersome one-to-one point-to-point power supply, but a one-to-many power supply aggregated by each functional domain. The corresponding hardware design and control logic are simpler, and the supply efficiency of the power supply is improved; multiple power states of the vehicle controller are defined according to each power domain power supply, and a power state diagram of the vehicle controller is constructed according to each power state. Management is performed through the power state diagram, and dynamic switching is performed between multiple power states based on various working conditions. The power state and switching control logic are simplified and clarified, the management efficiency of the power supply is improved, and the power consumption is effectively reduced.
[0041] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS
[0042] The accompanying drawings are incorporated into and constitute a part of the specification, illustrating embodiments consistent with the present application and, together with the specification, serving to explain the principles of the present application. It is obvious that the drawings described below are merely some embodiments of the present application, and a person of ordinary skill in the art can derive other drawings based on these drawings without inventive effort. In the drawings:
[0043] Figure 1 is a schematic diagram of a power management method for a vehicle controller in the prior art shown in an exemplary embodiment of the present application;
[0044] Figure 2 1 is a schematic diagram of the steps of a power management method for a vehicle controller according to an exemplary embodiment of the present application;
[0045] Figure 3 This is a flow chart of a process for performing domain-based and hierarchical processing on power supply according to an exemplary embodiment of the present application;
[0046] Figure 4 is a structural schematic diagram of a power state diagram of a vehicle controller shown in an exemplary embodiment of the present application;
[0047] Figure 51 is a schematic structural diagram of a power management device for a vehicle controller according to an exemplary embodiment of the present application;
[0048] Figure 6 It is a structural diagram of a computer system corresponding to an electronic device shown in an exemplary embodiment of the present application. DETAILED DESCRIPTION
[0049] The following describes the embodiments of the present invention with reference to the accompanying drawings and preferred embodiments. Those skilled in the art will readily appreciate the other advantages and benefits of the present invention from the disclosure herein. The present invention may also be implemented or applied through various other specific embodiments, and the various details in this specification may be modified or altered based on different viewpoints and applications without departing from the spirit of the present invention. It should be understood that the preferred embodiments are intended only to illustrate the present invention and are not intended to limit the scope of protection of the present invention.
[0050] It should be noted that the illustrations provided in the following embodiments are merely schematic illustrations of the basic concept of the present invention. Therefore, the illustrations only show components related to the present invention and are not drawn according to the number, shape, and size of components in actual implementation. In actual implementation, the type, quantity, and proportion of each component may be changed arbitrarily, and the component layout may also be more complex.
[0051] In the following description, numerous details are discussed to provide a more thorough explanation of the embodiments of the present invention. However, it will be apparent to those skilled in the art that the embodiments of the present invention may be practiced without these specific details. In other embodiments, well-known structures and devices are shown in block diagram form rather than in detail to avoid obscuring the embodiments of the present invention.
[0052] As described above in the background technology, the inventors have discovered that in order to integrate and manage hundreds of electronic control units in modern cars, domain controllers or vehicle controllers have emerged. Figure 1 FIG. 1 is a schematic diagram of a power management method for a vehicle controller according to an exemplary embodiment of the present application. Figure 1As shown, the vehicle is equipped with a large number of domain controllers, such as the powertrain, chassis, body, cockpit, and autonomous driving domain controllers. Whether fuel-powered or electric, each domain controller requires power from a power battery. The initial power from the power battery undergoes various buck-boost conversions to provide various power supply specifications, such as 5V, 3.3V, and 1.2V. However, with the increasing integration of domain controllers or vehicle controllers, the management framework and logic of existing vehicle power management systems are no longer suitable. Existing power supply methods generally rely on point-to-point power supply, with a single power battery providing power to multiple domain controllers of varying specifications. This results in complex and cumbersome power supply hardware design, and unified power management, resulting in complex and cumbersome control logic. In a few cases, power management is performed through domain controllers, with power management being divided into separate domains for different functional domains. Each power supply within a functional domain requires connection to the external power battery's conversion circuitry, resulting in a relatively complex hardware design and placing high demands on the power battery's power supply load, making it difficult to address the diverse power requirements of various functional modules within the vehicle system.
[0053] At the same time, whether it is a fuel vehicle or an electric vehicle, improving energy efficiency is particularly important. This requires not only low-power management, but also energy consumption management during the controller's operation to improve energy efficiency. In addition, the controller also needs to provide an external power interface to facilitate user power access, which increases the complexity of the controller power design. The vehicle power environment is relatively complex, and the overall controller power design also needs to consider abnormal operating conditions. However, current controller power designs often use a single power supply design with a mechanical mapping structure. Its design method and power framework are very simple, the hardware design is bloated and complex, and the corresponding control management efficiency is low.
[0054] To solve these problems, the embodiments of the present application respectively propose a power management method for a vehicle controller, a power management device for a vehicle controller, an electronic device, a computer-readable storage medium, and a computer program product. These embodiments will be described in detail below.
[0055] Figure 2 FIG. 1 is a schematic diagram showing the steps of a power management method for a vehicle controller according to an exemplary embodiment of the present application. Figure 2 As shown, in an exemplary embodiment of the present application, a power management method for a vehicle controller includes at least the steps of:
[0056] S21, obtaining parameters of the vehicle controller, and obtaining a multi-level power supply requirement level of the vehicle controller according to the parameters of the vehicle controller;
[0057] S22. Providing initial power, dividing and grading the initial power according to the multi-level power demand levels of the vehicle controller to obtain multiple power domains, and performing one-to-many power supply within each power demand level based on the power domains to aggregate the power supply modes of the vehicle controller;
[0058] S23. Define multiple power states of the vehicle controller according to the power supplies of each power domain, and construct a power state map of the vehicle controller according to each power state. Manage through the power state map and dynamically switch between multiple power states to reduce power consumption.
[0059] In detail, in step S21, the parameters of the vehicle controller include the various functional domains of the vehicle controller and the inclusion and subordination relationships between the various functional domains. The functional domains include main functional domains and sub-functional domains. The parameters of the vehicle controller can be obtained through the cloud or the internal configuration storage of the controller.
[0060] In an exemplary embodiment of the present application, the vehicle controller may be a whole vehicle controller, which includes a power domain controller, a chassis domain controller, and a body domain controller, that is, the vehicle controller includes main functional domains such as the power domain, chassis domain, and body domain, and each main functional domain further includes sub-functional domains, such as the body domain including the integrated lighting domain, the wiper and washing domain, the central control door lock domain, and the window control domain. Each sub-domain can be further subdivided into other sub-domains, such as the window control domain including the input and output domain, the window control domain, and other sub-domains. The sub-domains can be nested and divided until the final electronic components or processing chips. In another exemplary embodiment of the present application, the vehicle controller can also be a domain controller, such as one of the power domain controller, the chassis domain controller, the body domain controller, the cockpit domain controller, and the autonomous driving domain controller, which is not limited here.
[0061] Specifically, in step S21, the step of obtaining the multi-level power demand level of the vehicle controller according to the parameters of the vehicle controller further includes:
[0062] S211, obtaining each parallel main functional domain in the vehicle controller, and hierarchically processing each main functional domain according to the inclusion and subordination relationship between each functional domain until a specific component is obtained, thereby obtaining the subdomain level of each main functional domain;
[0063] S211, planning each main functional domain of the same level to the first level power demand level, and planning each sub-functional domain of the i-th level sub-domain in each main functional domain to the i+1-th level power demand level;
[0064] Wherein, i is an integer from 1 to n, n is the maximum number of subdomain levels of each main functional domain, and n is greater than or equal to 2.
[0065] More specifically, in step S211, the primary functional domains (or primary chips) in the vehicle controller are first determined. Then, based on the inclusion and subordination relationships between the functional domains, each primary functional domain is hierarchically processed, sequentially identifying the first-level sub-functional domain, the second-level sub-functional domain, and so on, until a specific component or chip that cannot be further subdivided is found. The number of sub-domain levels for each primary functional domain is generally different. For example, the number of sub-domain levels for electronic components from primary functional domain 1 is four, while the number of sub-domain levels for electronic components from primary functional domain 2 is six.
[0066] More specifically, in step S212, each primary functional domain of the same level is allocated to the first power requirement level, and each sub-functional domain of the i-th sub-domain within each primary functional domain is allocated to the i+1-th power requirement level. Specifically, each sub-functional domain of the first-level sub-domain within each primary functional domain is allocated to the second power requirement level, and each sub-functional domain of the second-level sub-domain within each primary functional domain is allocated to the third power requirement level. This process is repeated in this manner, ultimately resulting in n+1 power requirement levels. Each power requirement level includes at least one functional domain, i.e., each power requirement level includes one functional domain or multiple parallel functional domains. Here, i is an integer from 1 to n, and n is the maximum number of sub-domain levels within each primary functional domain.
[0067] Specifically, in step S22, an initial power supply is provided for each power demand level, and the initial power supply is hierarchically processed within each power demand level to obtain multiple power domain power supplies of different sizes, thereby achieving one-to-many power supply within each power demand level, which further includes:
[0068] In each power demand level, the initial power supply is hierarchically processed to obtain multiple power domains of different sizes. Some power domains are switched on and off, and then the power of each power domain is supplied to each functional domain in each power demand level accordingly.
[0069] The power demand levels are cascaded in sequence, the initial power supply of the next power demand level is a power domain power supply of the previous power demand level, and the initial power supply of the first power demand level is a battery power supply.
[0070] In more detail, in step S22, within each power demand level, the number of values of the initial power supply is greater than or equal to 1.
[0071] When the first-level power demand level includes only one functional domain, the number of values of its initial power supply is 1. Voltage conversion and grading processing is performed within the power demand level, and multiple power domain power supplies of different sizes are obtained from one initial power supply to power the various sub-functional domains within the power demand level, realizing one-to-many power supply.
[0072] When the first-level power demand level includes multiple (two or more) functional domains, the number of values of its initial power supply can be 1, such as Figure 3 As shown, in an exemplary embodiment of the present application, the power demand level includes two functional domains, corresponding to power domain 1 and power domain 2, and the initial power supply value is 12V. Voltage conversion and grading processing is performed within the power demand level, and multiple power domain power supplies of different sizes are obtained from an initial power supply to power each sub-functional domain (i.e., power domain 1 and power domain 2) within the power demand level, thereby realizing one-to-many power supply.
[0073] It is understandable that when the first power demand level includes multiple functional domains, such as Figure 3 The next power demand level of power domain 1 and power domain 2 shown includes multiple functional domains such as peripheral domain 1, peripheral domain 2, peripheral domain 3, peripheral domain 4, main chip 1 power domain and main chip 2 power domain. When the power supplies within each functional domain are graded, the initial power supply of peripheral domain 1 is controllable 5V_1 (i.e. 5V), and the initial power supply of peripheral domain 2 is other controllable_1 (such as 1.2V). Within this power demand level, the number of values of the initial power supply can be 2 or a larger number.
[0074] In more detail, in step S22, within each power demand level, the initial power supply is graded through step-by-step step-down conversion to obtain multiple power domain power supplies of different sizes; by inserting a controllable switch in series in the power supply circuit of the power domain power supply, switching control is performed on part of the power domain power supply.
[0075] In an exemplary embodiment of the present application, Figure 3 As shown, within each power demand level, before the initial power supply 12V is gradually stepped down, a controllable switch is first connected in series to the power supply circuit of the initial power supply 12V to obtain a controllable 12V power supply, and then the controllable 12V power supply is stepped down to obtain a 5V power supply and a 3.3V power supply. The 5V power supply and the 3.3V power supply are then stepped down to obtain other voltage power supplies (such as a 1.2V power supply). At the same time, a controllable switch is connected in series to the power supply circuit to obtain controllable power supplies such as controllable 5V_1, controllable 5V_1, other controllable_1, and other controllable_2, or the power supply normal power 5V_3 is directly output. In this way, multiple power domain power supplies of different sizes are obtained, and after switching control of some power domain power supplies, the obtained power domain power supplies are supplied to power domain 1 and power domain 2 as needed.
[0076] Among them, the power domain power supply with switch control is recorded as the controllable power domain power supply, and the power domain power supply without switch control is recorded as the common power domain power supply. In power domain 1 and power domain 2, since the peripheral power supplies need to be independently controlled and can be turned on and off independently, their power supplies are set as controllable power domain power supplies, such as controllable 5V_1, controllable 5V_2, other controllable power supplies_1, and other controllable power supplies_2 in the power supply design. Since the main chip needs to work continuously, its power supply is set as the common power domain power supply, such as normal power 5V_3.
[0077] It's important to note that the power supply hardware at each power demand level is cascaded sequentially. The initial power source for the next power demand level is a power domain power source from the previous power demand level, while the initial power source for the first power demand level is a battery power source (e.g., 12V). This one-to-many power supply, based on the sequential cascading of power demand levels and the domain-based, hierarchical processing within each level, not only implements domain-based, hierarchical power management but also effectively centralizes power supply methods, avoiding the cumbersome, one-to-one correspondence, point-to-point power supply method and improving power supply efficiency.
[0078] Specifically, the step S23 of defining multiple power states of the vehicle controller according to the power supplies of each power domain, constructing a power state map of the vehicle controller according to each power state, managing the power state map, and dynamically switching between the multiple power states to reduce power consumption further includes:
[0079] S231, defining multiple power states of the vehicle controller according to the state combination of power supplies in each power domain, where the power states include at least a power-on state, a safe state, a working state, and a low power state;
[0080] S232: Construct a power state diagram of the vehicle controller based on the power states and the evolutionary relationship between the power states.
[0081] S233. Perform state switching management through a power state diagram, dynamically switch between multiple power states, and enter a low power state when a sleep condition is met to reduce power consumption.
[0082] In more detail, in step S231, multiple power states of the vehicle controller are defined based on the state combination of the power supplies of each power domain, and in particular, different power states are defined based on the different on / off states of the controllable power domain power supplies. Compared with two different power states, at least one controllable power domain power supply has a different on / off state; the power states include at least a power-on state, a safe state, a working state, and a low-power state. Among them, the working state can include a variety of different working states, and the low-power state can include a variety of different low-power states, which will not be described in detail here. A low-power state is provided, and when the triggering conditions of the low-power state are met, the power supply is switched to the low-power state, which can effectively reduce the power consumption of the power supply.
[0083] In more detail, in step S232, based on each power state and the mutual evolutionary progressive relationship between each power state, a power state diagram of the vehicle controller is constructed with each power state as a node and the mutual evolutionary progressive relationship between each power state as the node relationship.
[0084] In an exemplary embodiment of the present application, Figure 3 As shown, the working state includes the first working state and the second working state, the low power consumption state includes the first low power consumption state and the second low power consumption state, plus the power-on state and the safety state, a total of 6 different power states are constructed, and the power state diagram of the vehicle controller is constructed by combining the mutual evolution progressive relationship between the 6 different power states. After entering the power-on state for a period of time, it enters the safety state, and after entering the safety state for a period of time, it enters the first working state. The first working state and the second working state can switch with each other, and can switch from the first working state or the second working state to the safe state, and can switch from the first working state or the second working state to the first low power consumption state, and can switch from the first low power consumption state to the first working state or the second working state, or switch from the first low power consumption state to the second low power consumption state, and switch from the second low power consumption state to the safe state.
[0085] In more detail, in step S233, state switching management is performed through the power state diagram, and dynamic switching is performed between multiple power states, which can improve the efficiency of power switching management. When the sleep conditions are met, the system switches to a low power state to reduce power consumption.
[0086] In an exemplary embodiment of the present application, Figure 3 As shown, the sleep condition includes a first sleep condition and a second sleep condition, and the state switching management is performed through the power state diagram. Step S233 of dynamically switching between multiple power states further includes:
[0087] S2331, when normal, switching from the power-on state to the safe state, switching from the safe state to the first working state, or switching back and forth between the first working state and the second working state;
[0088] S2332: When an abnormality occurs, the system switches from the first working state or the second working state to a safe state;
[0089] S2333: When a first sleep condition is met, switching from the first working state or the second working state to the first low power state; when awakened from the first low power state, switching from the first low power state to the first working state or the second working state;
[0090] S2334: When the second sleep condition is met, switch from the first low power state to the second low power state; when awakened from the second low power state, switch from the second low power state to the safe state.
[0091] Furthermore, in step S2331, after the vehicle controller is powered on, it is in the default power-on state. After a period of time, it switches from the power-on state to the safe state, and then waits for the power state request. Under normal working conditions, it can enter the first working state or the second working state.
[0092] Furthermore, in step S2332, when an abnormal event occurs, the first working state or the second working state can be returned to the safe state, and after processing the abnormal event, the safe state can be returned to the first working state or the second working state again.
[0093] Further, in step S2333, the first sleep condition is a shallow sleep condition. After the vehicle controller meets the first sleep condition, it can enter the first low power consumption state from the first working state and the second working state respectively; and after the vehicle controller wakes up, it can return to the first working state or the second working state from the first low power consumption state.
[0094] Furthermore, in step S2334, the second sleep condition is a deep sleep condition. For example, the second sleep condition may be that after the duration of the first low power state is greater than a set threshold, the vehicle controller can enter the second low power state from the first low power state after meeting the second sleep condition; in order to ensure safe power-on, when a wake-up command is received in the second low power state, it enters the safe state by default from the second low power state, and then enters each working state (first working state or second working state) according to the power state request.
[0095] In more detail, in step S233, when state switching management is performed through the power state diagram and dynamic switching is performed between multiple power states, the power state request, state switching action and power state are separated and operated asynchronously. First, it is determined whether there is a power state request. If there is a power state request, it is further determined whether the power switching conditions are met. If the power switching conditions are met, the state switching action is executed, and the power state is updated after the state switching action is completed.
[0096] Furthermore, during the specific power state diagram transition process, when a transition request is issued, only a request instruction is recorded, as the power state transition takes time. During the actual execution process, it is necessary to determine whether a request instruction is currently in place and whether the power switching conditions are currently met. If so, the power state is switched, and during the switching process, the power state remains in the previous operating state. When the state switch action is completed, the state is marked and the power state in the power state diagram is updated. The controller then begins operating according to the new power state. In this way, through an asynchronous operation strategy that separates the power state request, state switching action, and power state, reliable power state switching management is achieved.
[0097] Figure 5 FIG. 1 is a block diagram of a power management device for a vehicle controller according to an exemplary embodiment of the present application. Figure 5 As shown, the exemplary power management device of the vehicle controller includes:
[0098] A data acquisition module 51 is used to obtain parameters of the vehicle controller;
[0099] A first processing module 52 is configured to obtain a multi-level power demand level of the vehicle controller according to parameters of the vehicle controller;
[0100] The second processing module 53 is configured to perform domain-based and hierarchical processing on the initial power supply according to the multi-level power demand level of the vehicle controller to obtain multiple power domain power supplies, and further configured to perform one-to-many power supply within each power demand level according to the power domain power supplies to aggregate the power supply modes of the vehicle controller;
[0101] The third processing module 54 is used to define multiple power states of the vehicle controller according to the power supplies of each power domain, to construct a power state diagram of the vehicle controller according to each power state, and to manage through the power state diagram and dynamically switch between multiple power states to reduce power consumption.
[0102] The parameters of the vehicle controller include various functional domains of the vehicle controller and the inclusion and subordination relationships between the functional domains. The functional domains include main functional domains and sub-functional domains.
[0103] It should be noted that the power management device for a vehicle controller provided in the above-described embodiment and the power management method for a vehicle controller provided in the above-described embodiment are based on the same concept. The specific manner in which the various modules and units perform their operations has been described in detail in the method embodiments and will not be repeated here. In actual applications, the power management device for a vehicle controller provided in the above-described embodiment can, as needed, allocate the aforementioned functions to different functional modules, i.e., divide the internal structure of the device into different functional modules to perform all or part of the functions described above. This is not a limitation herein.
[0104] An embodiment of the present application also provides an electronic device, comprising: one or more processors; a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the electronic device implements the power management method of the vehicle controller provided in the above-mentioned embodiments.
[0105] Figure 6 The following is a schematic diagram showing the structure of a computer system suitable for implementing an electronic device according to an embodiment of the present application. Figure 6 The computer system 6 of the electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.
[0106] like Figure 6 As shown, the computer system 600 includes a central processing unit (CPU) 601, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 602 or the program loaded from the storage part 608 into the random access memory (RAM) 603, such as executing the method described in the above embodiment. Various programs and data required for system operation are also stored in the RAM 603. The CPU 601, ROM 602 and RAM 603 are connected to each other via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.
[0107] The following components are connected to the I / O interface 605: an input section 606 including a keyboard, a mouse, and the like; an output section 607 including devices such as a cathode ray tube (CRT), a liquid crystal display (LCD), and a speaker; a storage section 608 including a hard disk; and a communication section 609 including a network interface card such as a LAN (Local Area Network) card or a modem. The communication section 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to the I / O interface 605 as needed. Removable media 611, such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory, is installed in the drive 610 as needed, so that computer programs read from the removable media can be installed in the storage section 608 as needed.
[0108] In particular, according to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a computer program for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 609, and / or installed from a removable medium 611. When the computer program is executed by the central processing unit (CPU) 601, the various functions defined in the system of the present application are executed.
[0109] It should be noted that the computer-readable medium shown in the embodiments of the present application may be a computer-readable signal medium or a computer-readable storage medium or any combination of the two. The computer-readable storage medium may be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or component, 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), a 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 the present application, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, which carries a computer-readable computer program. This propagated data signal may take a variety of forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. A computer program embodied on a computer-readable medium may be transmitted using any suitable medium, including but not limited to wireless, wired, or any suitable combination thereof.
[0110] The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present application. Among them, each box in the flowchart or block diagram can represent a module, program segment, or part of the code, and the above-mentioned module, program segment, or part of the code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in an order different from that marked in the accompanying drawings. For example, two 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 box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart, can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.
[0111] The units involved in the embodiments described in this application may be implemented by software or hardware, and the units described may also be set in a processor. In some cases, the names of these units do not constitute limitations on the units themselves.
[0112] Another aspect of the present application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the aforementioned power management method for a vehicle controller. The computer-readable storage medium may be included in the electronic device described in the above embodiments, or may exist independently and not be incorporated into the electronic device.
[0113] Another aspect of the present application provides a computer program product or computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the power management method for a vehicle controller provided in each of the above embodiments.
[0114] In summary, in the power management method, device, electronic device and medium of the vehicle controller provided by the present invention, the multi-level power demand level of the vehicle controller is first obtained, and then the initial power supply is domained and graded according to the multi-level power demand level to obtain multiple power domain power supplies. One-to-many power supply is performed based on each power domain power supply within each power demand level, which can effectively aggregate the power supply mode of the vehicle controller. It is no longer a cumbersome one-to-one point-to-point power supply, but a one-to-many power supply cascaded step by step. The power supply mode is aggregated, the corresponding hardware design and control logic are simpler, and the supply efficiency of the power supply is improved; multiple power states of the vehicle controller are defined according to each power domain power supply, and a power state diagram of the vehicle controller is constructed according to each power state. Management is performed through the power state diagram, and dynamic switching is performed between multiple power states based on various working conditions, which simplifies and clarifies the power state and switching control logic, and improves the switching management efficiency of the power supply; at the same time, a low power state is set, and the low power state is triggered when the sleep conditions are met, which effectively reduces the power consumption of the vehicle controller and improves energy utilization efficiency.
[0115] The above embodiments are merely illustrative of the principles and effects of the present invention and are not intended to limit the present invention. Anyone familiar with the art may modify or alter the above embodiments without departing from the spirit and scope of the present invention. Therefore, all equivalent modifications or alterations made by a person of ordinary skill in the art without departing from the spirit and technical concepts disclosed by the present invention shall still be covered by the claims of the present invention. It should be emphasized that the flowcharts and block diagrams in the accompanying drawings illustrate the system architecture, functions, and operations that may be implemented by the system according to various embodiments of the present application. Each box in the flowchart or block diagram may represent a module, program segment, or part of the code, and the above module, program segment, or part of the code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the boxes may also occur in an order different from that marked in the drawings. For example, two boxes shown in succession may actually be executed substantially in parallel, or they may sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and combinations of boxes in the block diagram or flowchart, can be implemented by a dedicated hardware-based system that performs the specified function or operation, or can be implemented by a combination of dedicated hardware and computer instructions.
[0116] The modules and units described in the embodiments of this application may be implemented in software or hardware, and the modules and units described may also be provided in a processor. The names of these modules and units do not, in some cases, limit the modules and units themselves.
[0117] The above embodiments are merely illustrative of the principles and effects of the present invention and are not intended to limit the present invention. Anyone skilled in the art may modify or alter the above embodiments without departing from the spirit and scope of the present invention. Therefore, any equivalent modifications or alterations made by one of ordinary skill in the art without departing from the spirit and technical principles disclosed herein are intended to be covered by the claims of the present invention.
Claims
1. A power management method for a vehicle controller, characterized in that: include: Acquiring parameters of the vehicle controller, and acquiring a multi-level power demand level of the vehicle controller according to the parameters of the vehicle controller; The parameters of the vehicle controller include the functional domains of the vehicle controller and the inclusion and subordination relationships between the functional domains. The functional domains include main functional domains and sub-functional domains. Each level of the power demand level includes one functional domain or multiple parallel functional domains. The step of obtaining the multi-level power demand level of the vehicle controller according to the parameters of the vehicle controller includes: obtaining the parallel main functional domains in the vehicle controller, and performing hierarchical processing on each main functional domain step by step according to the inclusion and subordination relationships between the functional domains until specific components are obtained to obtain the sub-domain level of each main functional domain; planning each main functional domain of the same level to the first-level power demand level, and planning each sub-functional domain of the i-th level sub-domain in each main functional domain to the i+1-th level power demand level; wherein i is an integer from 1 to n, n is the maximum number of the sub-domain levels of each main functional domain, and n is greater than or equal to 2; Providing an initial power supply, domain-dividing and hierarchically processing the initial power supply according to the multi-level power requirement level of the vehicle controller to obtain multiple power domain power supplies, and performing one-to-many power supply within each power requirement level according to each power domain power supply to aggregate the power supply mode of the vehicle controller; the step of domain-dividing and hierarchically processing the initial power supply according to the multi-level power requirement level of the vehicle controller to obtain multiple power domain power supplies, and performing one-to-many power supply within each power requirement level according to each power domain power supply to aggregate the power supply mode of the vehicle controller includes: hierarchically processing the initial power supply within each power requirement level to obtain multiple power domain power supplies of different sizes, switching and controlling some of the power domain power supplies, and then correspondingly supplying each power domain power supply to each functional domain within each power requirement level; wherein the power requirement levels of each level are cascaded in sequence, the initial power supply of the next power requirement level is a power domain power supply of the previous power requirement level, and the initial power supply of the first power requirement level is a battery power supply; The vehicle controller defines multiple power states according to each of the power domain power supplies, constructs a power state graph of the vehicle controller according to each of the power states, manages the multiple power states through the power state graph, and dynamically switches between the multiple power states to reduce power consumption; the power domain power supplies that are switched on and off are recorded as controllable power domain power supplies, and the power domain power supplies that are not switched on and off are recorded as common power domain power supplies. The steps of defining multiple power states according to each of the power domain power supplies, constructing a power state graph of the vehicle controller according to each of the power states, managing the multiple power states through the power state graph, and dynamically switching between the multiple power states to reduce power consumption include: defining multiple power states of the vehicle controller according to a combination of states of each of the power domain power supplies, the power states including at least a power-on state, a safe state, a working state, and a low power state; constructing a power state graph of the vehicle controller according to each of the power states and the mutual evolution and progressive relationship between the power states; managing state switching through the power state graph, dynamically switching between the multiple power states, and entering the low power state when a sleep condition is met to reduce power consumption.
2. The power management method of a vehicle controller according to claim 1, characterized in that: In each power demand level, the number of values of the initial power supply is greater than or equal to 1.
3. The power management method of a vehicle controller according to claim 1, characterized in that: In each power demand level, the initial power supply is graded by step-by-step step-down conversion to obtain multiple power domain power supplies of different sizes; by connecting a controllable switch in series in the power supply circuit of the power domain power supply, switching control is performed on part of the power domain power supplies.
4. The power management method for a vehicle controller according to claim 1, wherein: The working state includes at least a first working state and a second working state, the low power consumption state includes at least a first low power consumption state and a second low power consumption state, the sleep condition includes a first sleep condition and a second sleep condition, and the step of dynamically switching between the plurality of power states by managing the state switching through the power state diagram includes: Under normal circumstances, the device switches from the power-on state to the safe state, switches from the safe state to the first working state, or switches back and forth between the first working state and the second working state; In the event of an abnormality, switching from the first working state or the second working state to the safe state; When the first sleep condition is met, switching from the first working state or the second working state to the first low-power state; when awakened from the first low-power state, switching from the first low-power state to the first working state or the second working state; When the second sleep condition is met, the first low power state is switched to the second low power state; when awakened from the second low power state, the second low power state is switched to the safe state.
5. The power management method for a vehicle controller according to claim 1 or 4, characterized in that: When state switching management is performed through the power state diagram and dynamic switching is performed between multiple power states, the power state request, state switching action and the power state are separated and operated asynchronously. First, it is determined whether there is a power state request. If there is a power state request, it is further determined whether the power switching conditions are met. If the power switching conditions are met, the state switching action is executed, and the power state is updated after the state switching action is completed.
6. A power management device for a vehicle controller that executes the power management method for a vehicle controller according to any one of claims 1 to 5, characterized in that: The device comprises: A data acquisition module, used to obtain parameters of the vehicle controller; A first processing module, configured to obtain a multi-level power demand level of the vehicle controller according to parameters of the vehicle controller; a second processing module, configured to perform domain-based and hierarchical processing on the initial power supply according to the multi-level power demand level of the vehicle controller to obtain multiple power domain power supplies, and further configured to perform one-to-many power supply within each power demand level according to each of the power domain power supplies to aggregate the power supply modes of the vehicle controller; The third processing module is used to define multiple power states of the vehicle controller according to each of the power domain power supplies, to construct a power state diagram of the vehicle controller according to each of the power states, and to manage through the power state diagram and dynamically switch between the multiple power states to reduce power consumption.
7. An electronic device, characterized in that: include: one or more processors; A storage device for storing one or more programs, which, when executed by the one or more processors, enables the electronic device to implement the power management method for a vehicle controller as described in any one of claims 1 to 5.
8. A computer-readable storage medium, characterized in that Computer-readable instructions are stored thereon, and when the computer-readable instructions are executed by a processor of a computer, the computer is caused to execute the power management method for a vehicle controller according to any one of claims 1 to 5.
Citation Information
Patent Citations
Power domain system for vehicle and vehicle
CN115395500A
New energy automobile low-voltage power supply control system and method based on domain controller
CN115402242A