Power management method and device of vehicle, vehicle and storage medium

Abstract

The invention relates to the technical field of vehicles, in particular to a power management method and device of a vehicle, the vehicle and a storage medium, and the method comprises the steps that the whole vehicle power supply demand of the current vehicle in each power mode is acquired; determining a plurality of target power utilization combinations according to the whole vehicle power supply demand of the current vehicle in each power supply mode; and based on a preset SOA architecture strategy, determining a plurality of target controllers, and distributing the plurality of target power utilization combinations to the plurality of target controllers so as to control and supply power to the corresponding power utilization equipment through the plurality of target controllers. Therefore, the problems that traditional vehicle power management cannot be subjected to function dissociation and calling, the flexibility is low, and the function requirement of the vehicle is difficult to meet are solved, the function flexibility and the development efficiency can be improved, the maintainability and the iterativity are improved, meanwhile, the development cost can be reduced, and resources are saved.

Description

Technical Field

[0001] The present application relates to the technical field of vehicles, and particularly to a power management method, device, vehicle and storage medium for a vehicle. Background Art

[0002] As a closed circuit system similar to a mobile phone, the whole vehicle needs to have basic functions such as energy conservation and avoiding component heating and shortened lifespan caused by high power consumption.

[0003] The power management of the whole vehicle mainly focuses on the management of low-voltage power distribution. Physically, the core is the battery, and each controller and other electrical appliances form a parallel circuit around the battery. The power management system is responsible for supplying power to different electrical appliances in different scenarios to achieve the purpose of making customers comfortable, ensuring vehicle safety, and saving energy.

[0004] In related technologies, the physical architecture design of the whole vehicle power management revolves around relays, commonly ACC / IG1 and IG2, and each electrical appliance is hung behind the relay. In the OFF scenario, no power supply is energized. In the ACC scenario, the ACC relay is energized. In the ON scenario, ACC+IG1+IG2 are energized. In the ST scenario, IG1 is energized.

[0005] However, the design with relays as the sub-core leads to great limitations in power supply, fixed scenarios, inability to be flexibly combined, and difficult to modify due to the involved hard-wired circuit. In addition, there is also a power management solution using the ECU architecture. Most manufacturers have moved from the embedded architecture to the AUTOSAR CP architecture, which has improved standardization, iteration, and agile development, but has not achieved atomic-level function extraction and invocation, resulting in the inability to flexibly combine functions to meet more scenario requirements.

[0006] In summary, automobiles are gradually advancing towards intelligence, the functional requirements of automotive electronic technologies are constantly increasing, and the software architecture is also developing towards modularization, platformization, and standardization. Moreover, with the expansion of automotive functions and the improvement of performance, as well as the increase in some non-functional requirements, the complexity of automotive electronic systems will further increase, which will further lead to a sharp increase in the new product development cycle and cost. The traditional whole vehicle power management architecture and ECU architecture are no longer suitable for the current functional requirements of automobiles. Summary of the Invention

[0007] The present application provides a power management method, device, vehicle and storage medium for a vehicle to solve the problem that traditional whole vehicle power management cannot perform function extraction and invocation, has low flexibility, and is difficult to meet the functional requirements of vehicles. The present application can improve functional flexibility and development efficiency, increase maintainability and iterability, and at the same time reduce development costs and save resources.

[0008] The first aspect of the present application provides a power management method for a vehicle, including the following steps:

[0009] Obtain the vehicle's overall power supply demand in each power mode;

[0010] Determine multiple target power consumption combinations according to the vehicle's overall power supply demand in each power mode;

[0011] Based on a preset SOA architecture strategy, determine multiple target controllers, and allocate the multiple target power consumption combinations to the multiple target controllers, so as to control and supply power to the corresponding electrical devices through the multiple target controllers.

[0012] Optionally, in some embodiments, the determining multiple target power consumption combinations according to the vehicle's overall power supply demand in each power mode includes:

[0013] Generate an initial power consumption combination according to the vehicle's overall power supply demand in each power mode;

[0014] Based on the initial power supply combination, the physical topology of the vehicle's electrical system, and the vehicle's functional requirements, determine the multiple target power consumption combinations.

[0015] Optionally, in some embodiments, the based on a preset SOA architecture strategy, determine multiple target controllers, and allocate the multiple target power consumption combinations to the multiple target controllers, so as to control and supply power to the corresponding electrical devices through the multiple target controllers, includes:

[0016] Based on the preset SOA architecture strategy, determine the to-be-connected controller corresponding to each target power consumption combination from the multiple target controllers;

[0017] Based on the to-be-connected controller corresponding to each target power consumption combination, allocate the multiple target power consumption combinations to the multiple target controllers.

[0018] Optionally, in some embodiments, the based on the preset SOA architecture strategy, determine the to-be-connected controller corresponding to each target power consumption combination from the multiple target controllers, includes:

[0019] Based on the preset SOA architecture strategy, determine the allocation type of each target power consumption combination;

[0020] According to the allocation type of each target power consumption combination, determine the to-be-connected controller corresponding to each target power consumption combination.

[0021] Optionally, in some embodiments, the allocation type includes at least one of priority, load balancing requirement, and power type.

[0022] The second aspect embodiment of this application provides a power management device for a vehicle, including:

[0023] An acquisition module, configured to acquire the vehicle's overall power supply demand in each power mode;

[0024] A determination module, configured to determine multiple target power consumption combinations according to the vehicle's overall power supply demand in each power mode;

[0025] A management module, configured to determine multiple target controllers based on a preset SOA architecture strategy, and allocate the multiple target power consumption combinations to the multiple target controllers, so as to control and supply power to corresponding electrical devices through the multiple target controllers.

[0026] Optionally, in some embodiments, the determination module includes:

[0027] A generation unit, configured to generate an initial power consumption combination according to the vehicle's overall power supply demand in each power mode;

[0028] A first determination unit, configured to determine the multiple target power consumption combinations based on the initial power supply combination, the physical topology of the vehicle's electrical system, and the vehicle's functional requirements.

[0029] Optionally, in some embodiments, the management module includes:

[0030] A second determination unit, configured to determine the controller to be connected corresponding to each target power consumption combination from the multiple target controllers based on the preset SOA architecture strategy;

[0031] An allocation unit, configured to allocate the multiple target power consumption combinations to the multiple target controllers based on the controller to be connected corresponding to each target power consumption combination.

[0032] Optionally, in some embodiments, the second determination unit includes:

[0033] A first determination subunit, configured to determine the allocation type of each target power consumption combination based on the preset SOA architecture strategy;

[0034] A second determination subunit, configured to determine the controller to be connected corresponding to each target power consumption combination according to the allocation type of each target power consumption combination.

[0035] Optionally, in some embodiments, the allocation type includes at least one of priority, load balancing requirement, and power type.

[0036] A third aspect embodiment of the present application provides a vehicle, including: a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor executes the program to implement the vehicle power management method as described in the above embodiments.

[0037] A fourth aspect embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored, and the program is executed by a processor to implement the vehicle power management method as described in the above embodiments.

[0038] Thus, by obtaining the vehicle's overall power supply demand in each power mode, determining multiple target power consumption combinations based on the vehicle's overall power supply demand in each power mode, determining multiple target controllers based on a preset SOA architecture strategy, and allocating multiple target power consumption combinations to the multiple target controllers, the corresponding electrical devices are controlled and powered by the multiple target controllers. Thus, the problem that traditional vehicle power management cannot perform function extraction and invocation, has low flexibility, and is difficult to meet the vehicle's functional requirements is solved. The present application can improve functional flexibility and development efficiency, increase maintainability and iterability, while reducing development costs and saving resources.

[0039] Additional aspects and advantages of the present application will be given in part in the following description, become apparent in part from the following description, or be understood through the practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] The above and / or additional aspects and advantages of the present application will become apparent and be readily understood from the following description of the embodiments in conjunction with the drawings, where:

[0041] Figure 1 is a flowchart of the vehicle power management method according to an embodiment of the present application;

[0042] Figure 2 is a schematic diagram of the principle of the vehicle power management method according to an embodiment of the present application;

[0043] Figure 3 is a schematic diagram of the ports / port interfaces and internal behaviors of software components in AUTOSAR according to an embodiment of the present application;

[0044] Figure 4 is a block diagram of the vehicle power management device according to an embodiment of the present application;

[0045] Figure 5 is a schematic diagram of the structure of the vehicle according to an embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0046] Embodiments of the present application will be described in detail below. Examples of the embodiments are shown in the accompanying drawings, where the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to explain the present application, but should not be construed as limiting the present application.

[0047] The power management method, device, vehicle, and storage medium of the vehicle according to the embodiments of the present application will be described below with reference to the accompanying drawings. In view of the problem in the above-mentioned background technology that the traditional vehicle power management cannot perform function extraction and invocation, has low flexibility, and is difficult to meet the functional requirements of the vehicle, the present application provides a power management method for a vehicle. In this method, by obtaining the vehicle's power supply requirements in each power mode of the current vehicle, determining multiple target power consumption combinations according to the vehicle's power supply requirements in each power mode of the current vehicle, determining multiple target controllers based on a preset SOA architecture strategy, and allocating the multiple target power consumption combinations to the multiple target controllers, so as to control and supply power to the corresponding electrical devices through the multiple target controllers. Thus, the problem that the traditional vehicle power management cannot perform function extraction and invocation, has low flexibility, and is difficult to meet the functional requirements of the vehicle is solved. The present application can improve functional flexibility and development efficiency, increase maintainability and iterability, and at the same time reduce development costs and save resources.

[0048] The current design of vehicle power management mainly focuses on the power mode as the core scenario. Before introducing the power management method of the vehicle according to the embodiments of the present application, common power modes will be introduced first. Common power modes include OFF / ACC / ON and ST. Among them, the electrical appliances powered under OFF are mainly the functional entities required for vehicle dormancy. The OFF power is generally directly supplied by the battery through a fuse and does not belong to the scope of vehicle power management. The type of power constantly supplied under OFF is called constant power or KL30; the newly added electrical appliances powered under ACC are mainly the functional entities for comfort requirements. On the basis of KL30, the power supply for auxiliary functional entities such as audio-visual and interior lighting assistance is added. The type of power constantly supplied newly under ACC compared with OFF is called auxiliary power, also called KLR; the newly added electrical appliances powered under ON are mainly the functional entities required for driving. On the basis of KL30 + KLR, the power supply required for driving such as power steering and braking is newly added. The type of power constantly supplied newly under ON compared with ACC is called ON power, also called KL15. In the ON scenario, the vehicle electrical appliances are in a state where they can be used, which means that the entire vehicle circuit is powered or in a state where it can be powered at any time; under ST, it is mainly a high-power power source required for starting. When the vehicle starts, it requires an instantaneous starting current of about one hundred amperes. To avoid the vehicle battery being unable to supply power and causing the vehicle to fail to start, or abnormal operation of each electrical appliance due to low voltage caused by large current output, when starting, some non-essential power sources for starting, such as window lifters and seat adjusters, are disconnected, so that the vehicle can start safely.

[0049] Specifically, Figure 1 FIG. is a schematic flowchart of a power management method for a vehicle provided by an embodiment of the present application.

[0050] As Figure 1 shown, the power management method for the vehicle includes the following steps:

[0051] In step S101, obtain the vehicle's overall power supply demand in each power mode.

[0052] Specifically, the embodiment of the present application is based on the SOA architecture concept, extracts functions around the core scenario of vehicle power management, the power mode, and disassembles the vehicle's power consumption requirements.

[0053] In the actual execution process, the core scenario of the power management function is the power mode. Therefore, relevant personnel need to extract the requirements for the functions of other electrical appliances in each power mode according to the three-level functions of the products of their respective departments. The specific work is counted using a form. The left side of the form is the three-level functions and function descriptions, and the upper side is the power modes and various electrical appliances. After relevant personnel mark and combine them, they submit them to the architecture.

[0054] In step S102, determine multiple target power consumption combinations according to the vehicle's overall power supply demand in each power mode.

[0055] Further, in some embodiments, determining multiple target power consumption combinations according to the vehicle's overall power supply demand in each power mode includes: generating an initial power consumption combination according to the vehicle's overall power supply demand in each power mode; and determining multiple target power consumption combinations based on the initial power supply combination, the physical topology of the vehicle electrical system, and the vehicle function requirements.

[0056] Specifically, classify the power consumption combination requirements of the functions in each power mode for the vehicle's overall power supply. According to the power consumption combination requirements, considering the physical TOPO and functions, disassemble the vehicle's power consumption combinations into 32 types; specifically, the system architecture extracts the common power supply combinations of electrical appliances according to the marked form, and analyzes their rationality based on the physical TOPO and functions, and then disassembles and combines them again to determine multiple target power consumption combinations.

[0057] In step S103, based on a preset SOA architecture strategy, determine multiple target controllers, and allocate multiple target power consumption combinations to the multiple target controllers, so as to control and supply power to the corresponding electrical devices through the multiple target controllers.

[0058] Further, in some embodiments, based on a preset SOA architecture policy, multiple target controllers are determined, and various target power consumption combinations are allocated to the multiple target controllers to control and supply power to the corresponding electrical devices through the multiple target controllers, including: determining the to-be-connected controller corresponding to each target power consumption combination from the multiple target controllers based on the preset SOA architecture policy; and allocating various target power consumption combinations to the multiple target controllers based on the to-be-connected controller corresponding to each target power consumption combination.

[0059] Among them, the preset SOA architecture policy is preset by relevant personnel.

[0060] Specifically, as shown in Figure 2 According to the SOA architecture concept in the embodiments of the present application, functions need to be flexibly combined. Considering the overall architecture, three main domain controls are selected, and the split 32-channel downstream power consumption combinations are allocated to 32 PINs of the three main controllers. According to the allocation results and functional requirements, detailed system function specifications and system constraint files are compiled; the main responsible domain control is selected based on factors such as function entity, inheritance, cost, and security, and the power supply combinations are hung on the domain control PINs and physical TOPO, detailed function specifications, and system interaction documents are compiled. For the purpose of realizing flexible invocation, each power consumption combination uses an independent CS interface.

[0061] During the actual execution process, according to factors such as functional requirements, physical topology structure, inheritance, cost, and security, the most suitable controller is selected from the multiple target controllers as the to-be-connected controller for each power consumption combination. According to the principles of independent interface, load balancing, and function priority, various power consumption combinations are allocated to the multiple target controllers. At the same time, cross-domain interaction interfaces and software architecture support are designed to ensure that the functions of the power consumption combinations can be correctly implemented on the allocated controllers.

[0062] Optionally, in some embodiments, determining the to-be-connected controller corresponding to each target power consumption combination from the multiple target controllers based on the preset SOA architecture policy includes: determining the allocation type of each target power consumption combination based on the preset SOA architecture policy; and determining the to-be-connected controller corresponding to each target power consumption combination according to the allocation type of each target power consumption combination.

[0063] Among them, the allocation type includes at least one of priority, load balancing requirement, and power supply type.

[0064] Specifically, based on the preset SOA architecture policy, the allocation type of each target power consumption combination is determined, where the allocation type includes at least one of priority, load balancing requirement, and power supply type.

[0065] Specifically, priority refers to the importance and urgency of the electrical load combinations in the vehicle system. For example, high-priority electrical load combinations are usually closely related to the safety and critical functions of the vehicle, such as the braking system, airbag system, etc.; medium-priority electrical load combinations may be related to the driving functions of the vehicle, such as power steering, ABS, etc.; low-priority electrical load combinations are mostly comfort functions, such as seat heating, air conditioning, etc. The priority of the electrical load combinations is determined according to their functional characteristics and the degree of impact on vehicle safety and driving. For example, safety-related electrical load combinations (such as airbag control) are classified as high priority; driving-related electrical load combinations (such as power steering) are classified as medium priority; comfort-related electrical load combinations (such as seat heating) are classified as low priority.

[0066] The load balancing requirement means that, based on the processing capacity of the controller, resource occupancy, and the overall system load, electrical load combinations are reasonably allocated to avoid overloading a certain controller. The purpose of the load balancing requirement is to ensure the stability and efficiency of the system. For example, by analyzing the processing capacity of each controller (such as CPU performance, memory capacity, number of I / O interfaces, etc.) and the current resource occupancy, the load of each controller is evaluated. According to the resource requirements of the electrical load combinations (such as processing complexity, data transmission volume, etc.), they are allocated to the controller with a lighter load to achieve load balancing.

[0067] The power supply type refers to the power supply characteristics required by the electrical load combinations, such as voltage level, current magnitude, power supply stability, etc. Different electrical load combinations may require different types of power supplies. For example, some high-power devices (such as electric seat adjustment) may require a high-current power supply, while some low-power devices (such as sensors) may require a low-voltage power supply. During the actual implementation process, according to the electrical characteristic requirements of the electrical load combinations, the required power supply type is determined. For example, high-power devices (such as electric seat adjustment) are classified as high-current power supply types; low-power devices (such as sensors) are classified as low-voltage power supply types.

[0068] After determining the allocation type of each electrical load combination, a suitable controller can be selected according to the priority, load balancing requirement, and power supply type, which can ensure that each electrical load combination is allocated to the most suitable controller, thus achieving efficient, flexible, and reliable power management.

[0069] It should be noted that the power management method of the vehicle in the embodiment of the present application adopts SOA and AUTOSAR architecture ideas in the design of ECU-level software architecture, designs the software architecture, improves the design of the SWC interaction language, that is, the software component-level interaction XML file, imports the ECU-level and software component interaction ARXML into the engineering configuration tool of AUTOSAR for configuration and design, exports the SWC-level ARXML file, and performs modular software development. Specifically, the software architecture is divided into ASW / RTE and BSW from top to bottom, wherein the ASW layer is further disassembled, and the SWC therein is divided into three categories, namely, application SWC: the main function is function trigger judgment, enhanced SWC: the main function is function priority judgment, outputs the final execution result of multiple triggers, atomic SWC: the main function is basic function execution, such as whether a certain PIN is turned on or not, and each SWC interacts through RTE, and the interaction interface type is CS, so as to meet the requirements of high quality, flexibility and efficiency.

[0070] In terms of software development, firstly, the design of the ARXML file of the software component framework is completed through the "top-down" workflow: in the "top-down" workflow of the AUTOSAR system solution, it is different from the "bottom-up" workflow. It is necessary to convert the designed interaction file into ARXML format first, and then import it into the ARCH design tool. The ARCH tool will generate the corresponding interface and data elements according to the system constraint definition and map them with the AUTOSAR elements, and automatically generate and map the ADT, IDT, BT, CM, and DC related to the data elements. If ARCH does not have the automatic generation and mapping functions, it can be configured manually. Then, according to the generated interface and data elements, the SWC level configuration is performed. When designing SWC, you only need to create a port and associate the port interface. The data elements contained in the SR interface can be freely selected, and the default is to select all. The CS interface needs to select the RUNABLE that needs to be called, and then add RTE EVNET / RUNABLE and PORT ACCESS. The synchronization task needs to select the timeout time. After the SWC component XML design is completed, it needs to be imported into the ECU-level XML for interface connection. If it involves a cross-domain control interface, the interface needs to be exposed at the outermost end and connected in the vehicle ARCH. The cross-domain transmission interface requires signal mapping. At this point, the configuration and design of the XML are completed. The completed SWC-level XML file is exported to the ARCH design tool and imported into SIMULINK to verify its correctness and complete the implementation of the internal algorithm and MIL test. Then, Matlab / Simulink is used to generate code that complies with the AUTOSAR specification. The generated code is preprocessed, compiled, assembled, and linked to generate an executable file. After being flashed into the ECU, it is debugged and accepted at the bench level and actual vehicle level.

[0071] Figure 3This is the software structure of the application layer of the automotive power mode management under the AUTOSAR architecture provided in the embodiments of this application. This diagram shows the design architecture of the power mode management software, which is the basis for the development of the entire process. In this XML, the ports / interfaces / data types and internal behaviors of the power management mode are defined. For subsequent development, only the RUNABL implementation algorithm inside the XML needs to be filled in according to the specification requirements.

[0072] In summary, the embodiments of this application avoid the defect of the traditional power design architecture that there are too many associated components to be changed later and the hardware circuit needs to be changed. The functional architecture establishes 32 power supply combinations according to different scenario functions and power modes. Each combination is necessary for the realization of the function, and the ECU-level architecture design of SOA and AUTOSAR is adopted. The controllers under each combination can cooperate flexibly, providing more scenario-based functions for the whole vehicle, improving the redundancy of the architecture design, and further optimizing the power-saving and safety requirements based on the power mode management. Overall, it achieves the effects of high quality, flexibility, and efficiency.

[0073] According to the vehicle power management method proposed in the embodiments of this application, by obtaining the vehicle's overall power supply requirements in each power mode, determining multiple target power consumption combinations based on the vehicle's overall power supply requirements in each power mode, determining multiple target controllers based on a preset SOA architecture strategy, and allocating multiple target power consumption combinations to multiple target controllers to control and supply power to the corresponding electrical devices through the multiple target controllers. Thus, the problem that traditional vehicle power management cannot perform function extraction and invocation, has low flexibility, and is difficult to meet the vehicle's functional requirements is solved. This application can improve functional flexibility and development efficiency, increase maintainability and iterability, while reducing development costs and saving resources.

[0074] Next, refer to the accompanying drawings to describe the vehicle power management device proposed in the embodiments of this application.

[0075] Figure 4 This is a block diagram of the vehicle power management device according to the embodiments of this application.

[0076] As Figure 4 shown, the vehicle power management device 10 includes: an acquisition module 100, a management module 200, and a management module 300.

[0077] Among them, the acquisition module 100 is used to obtain the vehicle's overall power supply requirements in each power mode.

[0078] The determination module 200 is used to determine multiple target power consumption combinations according to the vehicle's overall power supply requirements in each power mode.

[0079] The management module 300 is configured to determine multiple target controllers based on a preset SOA architecture policy, and allocate multiple target power consumption combinations to the multiple target controllers, so as to control and supply power to corresponding electrical devices through the multiple target controllers.

[0080] Optionally, in some embodiments, the determination module 200 includes: a generation unit and a first determination unit.

[0081] The generation unit is configured to generate an initial power consumption combination according to the vehicle's overall power supply requirements in each power mode.

[0082] The first determination unit is configured to determine multiple target power consumption combinations based on the initial power supply combination, the physical topology of the vehicle's electrical system, and the vehicle's functional requirements.

[0083] Optionally, in some embodiments, the management module 300 includes: a second determination unit and an allocation unit.

[0084] The second determination unit is configured to determine the to-be-connected controller corresponding to each target power consumption combination from multiple target controllers based on the preset SOA architecture policy.

[0085] The allocation unit is configured to allocate multiple target power consumption combinations to multiple target controllers based on the to-be-connected controller corresponding to each target power consumption combination.

[0086] Optionally, in some embodiments, the second determination unit includes: a first determination subunit and a second determination subunit.

[0087] The first determination subunit is configured to determine the allocation type of each target power consumption combination based on the preset SOA architecture policy.

[0088] The second determination subunit is configured to determine the to-be-connected controller corresponding to each target power consumption combination according to the allocation type of each target power consumption combination.

[0089] Optionally, in some embodiments, the allocation type includes at least one of priority, load balancing requirement, and power type.

[0090] It should be noted that the foregoing explanation of the embodiments of the vehicle power management method also applies to the vehicle power management device of this embodiment, and will not be elaborated here.

[0091] The power management device of a vehicle proposed according to an embodiment of the present application obtains the vehicle's overall power supply requirements in each power mode, determines multiple target power consumption combinations based on the vehicle's overall power supply requirements in each power mode, determines multiple target controllers based on a preset SOA architecture strategy, and allocates the multiple target power consumption combinations to the multiple target controllers to control and supply power to the corresponding electrical devices through the multiple target controllers. Thus, the problem that traditional vehicle power management cannot perform function extraction and invocation, has low flexibility, and is difficult to meet the vehicle's functional requirements is solved. The present application can improve functional flexibility and development efficiency, increase maintainability and iterability, while reducing development costs and saving resources.

[0092] Figure 5 It is a schematic structural diagram of a vehicle provided by an embodiment of the present application. The vehicle may include:

[0093] A memory 501, a processor 502, and a computer program stored on the memory 501 and executable on the processor 502.

[0094] When the processor 502 executes the program, it implements the vehicle power management method provided in the above embodiment.

[0095] Furthermore, the vehicle further includes:

[0096] A communication interface 503 for communication between the memory 501 and the processor 502.

[0097] The memory 501 is used to store a computer program executable on the processor 502.

[0098] The memory 501 may include a high-speed RAM (Random Access Memory) memory, and may also include a non-volatile memory, such as at least one disk memory.

[0099] If the memory 501, the processor 502, and the communication interface 503 are implemented independently, the communication interface 503, the memory 501, and the processor 502 can be interconnected through a bus and communicate with each other. The bus can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component) bus, or an EISA (Extended Industry Standard Architecture) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For the sake of representation, Figure 5 only a thick line is shown in the figure, but it does not mean that there is only one bus or one type of bus.

[0100] Optionally, in a specific implementation, if the memory 501, the processor 502, and the communication interface 503 are integrated on a single chip, the memory 501, the processor 502, and the communication interface 503 can communicate with each other through an internal interface.

[0101] The processor 502 may be a CPU (Central Processing Unit), or an ASIC (Application Specific Integrated Circuit), or one or more integrated circuits configured to implement the embodiments of the present application.

[0102] The embodiments of the present application further provide a computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, the power management method of the vehicle as described above is implemented.

[0103] In the description of this specification, the descriptions with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples", etc. mean that the specific features, structures, materials, or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representations of the above terms are not necessarily directed to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described may be combined in any one or N embodiments or examples in a suitable manner. In addition, without conflict, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of different embodiments or examples.

[0104] In addition, the terms "first" and "second" are only used for descriptive purposes and cannot be construed as indicating or implying relative importance or implicitly specifying the quantity of the indicated technical features. Thus, the features defined with "first" and "second" may explicitly or implicitly include at least one of the features. In the description of the present application, the meaning of "N" is at least two, such as two, three, etc., unless otherwise specifically defined.

[0105] Any process or method description shown in a flowchart or described in other ways herein may be understood to represent a module, segment, or portion of code including one or more executable instructions for implementing a customized logic function or process, and the scope of the preferred embodiments of the present application includes additional implementations, where the functions may be executed in a substantially simultaneous manner or in a reverse order according to the involved functions, rather than in the order shown or discussed, which should be understood by those skilled in the art to which the embodiments of the present application pertain.

[0106] It should be understood that each part of the present application can be implemented by hardware, software, firmware, or a combination thereof. In the above embodiments, the N steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented by hardware, as in another embodiment, any one or a combination of the following techniques well known in the art can be used: discrete logic circuits having logic gate circuits for implementing logic functions on data signals, application specific integrated circuits having appropriate combinational logic gate circuits, programmable gate arrays, field programmable gate arrays, and the like.

[0107] Those of ordinary skill in the art can understand that all or part of the steps carried by the methods in the above embodiments can be completed by instructing relevant hardware through a program, and the program can be stored in a computer-readable storage medium. When the program is executed, it includes one or a combination of the steps of the method embodiments.

[0108] Although the embodiments of the present application have been shown and described above, it can be understood that the above embodiments are exemplary and should not be construed as limiting the present application. Those of ordinary skill in the art can make changes, modifications, substitutions, and variations to the above embodiments within the scope of the present application.

Claims

1. A vehicle power management method, characterized in that: The following steps are involved: Obtain the vehicle power supply requirements in each power mode. Determining multiple target power consumption combinations according to the vehicle power supply demand of the current vehicle in each power supply mode; Based on a preset SOA architecture strategy, a plurality of target controllers are determined, and the plurality of target power consumption combinations are allocated to the plurality of target controllers, so that corresponding power-consuming devices are controlled and supplied with power through the plurality of target controllers.

2. The method according to claim 1, characterized in that The determining of multiple target power consumption combinations according to the vehicle power supply demand of the current vehicle in each power supply mode includes: Generate an initial power consumption combination according to the vehicle power supply demand of the current vehicle in each power supply mode; Based on the initial power supply combination, the physical topology of the vehicle electrical system and the functional requirements of the vehicle, the multiple target power consumption combinations are determined.

3. The method according to claim 1, characterized in that The method of determining a plurality of target controllers based on a preset SOA architecture strategy and allocating the plurality of target power consumption combinations to the plurality of target controllers so as to control and supply power to corresponding power-consuming devices through the plurality of target controllers includes: Based on the preset SOA architecture strategy, determining a controller to be connected corresponding to each target power consumption combination from the multiple target controllers; Based on the to-be-connected controllers corresponding to each target power usage combination, the multiple target power usage combinations are allocated to the multiple target controllers.

4. The method according to claim 3, characterized in that The determining, based on the preset SOA architecture strategy, a controller to be connected corresponding to each target power consumption combination from the multiple target controllers includes: Based on the preset SOA architecture strategy, determining the allocation type of each target power consumption combination; The controller to be connected corresponding to each target power consumption combination is determined according to the allocation type of each target power consumption combination.

5. The method according to claim 4, characterized in that The allocation type includes at least one of priority, load balancing requirement and power type.

6. A power management device for a vehicle, characterized in that: include: An acquisition module is used to obtain the vehicle power supply demand of the current vehicle in each power mode; A determination module, configured to determine a plurality of target power consumption combinations according to the vehicle power supply demand of the current vehicle in each power supply mode; The management module is used to determine multiple target controllers based on a preset SOA architecture strategy, and allocate the multiple target power consumption combinations to the multiple target controllers, so as to control and supply power to corresponding power-consuming devices through the multiple target controllers.

7. The device according to claim 6, characterized in that The determining module comprises: A generating unit, configured to generate an initial power consumption combination according to the whole vehicle power supply demand of the current vehicle in each power supply mode; The first determination unit is used to determine the multiple target power consumption combinations based on the initial power supply combination, the physical topology of the vehicle electrical system and the functional requirements of the vehicle.

8. The device according to claim 6, characterized in that The management module comprises: A second determining unit, configured to determine, from the plurality of target controllers, a controller to be connected corresponding to each target power consumption combination based on the preset SOA architecture strategy; The allocating unit is used to allocate the multiple target power usage combinations to the multiple target controllers based on the to-be-connected controllers corresponding to each target power usage combination.

9. A vehicle, characterized in that: include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the power management method for a vehicle as described in any one of claims 1 to 5.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: The program is executed by a processor to implement the vehicle power management method as described in any one of claims 1 to 5.

Images