Load power supply scheduling method and system, and vehicle

Abstract

The application provides a load power supply scheduling method and system and a vehicle, and relates to the technical field of power management. By identifying the current running scene of the vehicle, determining a plurality of target loads to be powered and scheduled and power supply parameters of the target loads in the current running scene in the loads contained in the vehicle, the power supply resource configuration of each load can be adaptively adjusted under dynamic working conditions, the power supply parameters include power supply priority, power supply domain and power supply power budget, and the flexibility of multi-load power supply scheduling can be improved. Based on the power supply priority, the power supply domain and the power supply power budget are allocated to the target loads corresponding to the current running scene, differentiated power supply allocation can be realized, the flexibility of load power supply scheduling is improved, and the power supply efficiency of the whole vehicle is improved.

Description

Technical Field

[0001] This application relates to the field of power management technology, and in particular to a load power supply scheduling method, system and vehicle. Background Technology

[0002] In modern intelligent vehicles, with the widespread adoption of high-power chassis actuators, thermal management devices, and high-power comfort equipment, traditional 12V power supply systems face challenges such as power bottlenecks, complex wiring harness layouts, carpet bulging, and difficulties with vias. In contrast, 48V power supply systems, by increasing the voltage level, can simultaneously improve wiring harness weight reduction, power capacity, intelligent power distribution, and the responsiveness of high-power actuators, making them a core infrastructure of the vehicle's electronic and electrical architecture.

[0003] In related technologies, 48V power systems typically employ a static power supply strategy, which allocates fixed power supply domains (e.g., 48V / 12V) and power budgets to different loads through preset rules to achieve power supply scheduling for the loads. For example, chassis actuators are powered by a 48V power system to ensure high power requirements, while comfort equipment is powered by a 12V power system to reduce complexity. However, this load power supply scheduling method has poor flexibility, resulting in low energy efficiency. Summary of the Invention

[0004] This application provides a load power supply scheduling method, system, and vehicle to improve the flexibility of load power supply scheduling, thereby improving the overall vehicle power supply efficiency.

[0005] In a first aspect, this application provides a load power supply scheduling method, including:

[0006] Identify the vehicle's current operating scenario;

[0007] Based on the current operating scenario, multiple target loads to be scheduled for power supply are identified from the loads contained in the vehicle, as well as the power supply parameters of the target loads under the current operating scenario. The power supply parameters include power supply priority, power supply domain and power supply budget.

[0008] Based on power supply priority, a power supply domain and power supply budget are allocated to the target load corresponding to the current operating scenario.

[0009] In one possible implementation, based on the current operating scenario, multiple target loads to be scheduled for power supply are determined from the loads contained in the vehicle, along with the power supply parameters of the target loads under the current operating scenario, including:

[0010] Based on the vehicle model or configuration, determine the corresponding preset scene template for the vehicle;

[0011] Based on the current operating scenario, a preset scenario template is invoked to determine multiple target loads to be scheduled for power supply from the loads contained in the vehicle, as well as the power supply parameters of the target loads under the current operating scenario. The preset scenario template contains the power supply parameters of the loads under different operating scenarios.

[0012] In one possible implementation, the preset scene template is generated in the following way:

[0013] Read the scene state and determine the scene label corresponding to the scene state;

[0014] Read the load migration results in the vehicle to determine the available power supply domains for each load and whether multi-path power supply is supported;

[0015] Read the service priority to obtain the power supply priority, power budget, wake-up order and degradation mode of each load under the scene tag;

[0016] Based on the template selector, preset scenario templates are generated according to scenario tags, available power domains for each load, whether multi-path power supply is supported, power supply priority, power supply budget, wake-up order, and degradeable method.

[0017] In one possible implementation, after allocating a power domain and power budget to the target load corresponding to the current operating scenario based on power supply priority, the method further includes:

[0018] For the target load, perform the following operations:

[0019] Real-time monitoring of the execution results of the target load for the power supply domain and power supply budget, including the power supply domain allocation results and the power supply budget execution status;

[0020] Based on the execution results, determine the energy efficiency and response indicators of the target load;

[0021] Based on energy efficiency and response metrics, the effectiveness of power supply allocation to the target load is evaluated, and the effectiveness of power supply allocation is used to optimize the preset scenario templates corresponding to the vehicle.

[0022] In one possible implementation, the power supply parameters also include wake-up data, which includes a network wake-up object, wake-up timing, wake-up hold time, and allowed sleep conditions.

[0023] The method also includes:

[0024] Based on the wake-up data, determine whether the target load has a load wake-up requirement;

[0025] If the target load has a load wake-up requirement, then the wake-up of the target load is controlled based on the wake-up data.

[0026] In one possible implementation, after allocating a power domain and power budget to the target load corresponding to the current operating scenario based on power supply priority, the method further includes:

[0027] If there is a conflict in the power supply domain or power supply budget of different loads among multiple target loads, then based on the power supply priority of different loads, the load with higher power supply priority is controlled to perform power supply preemption, and the load with lower power supply priority is controlled to perform power supply rollback. Power supply rollback includes reducing the power supply budget.

[0028] In one possible implementation, before allocating a power domain and power budget to the target load corresponding to the current operating scenario based on power supply priority, the method further includes:

[0029] Determine the duration for which the current operating scenario will remain stable.

[0030] In one possible implementation, identifying the vehicle's current operating scenario includes:

[0031] Obtain the current scene status of the vehicle;

[0032] Normalize and verify the current scene state;

[0033] Based on the current scene state that has passed verification, a rule machine or state machine is applied to identify the current operating scene of the vehicle.

[0034] Secondly, this application provides a load power supply scheduling system, comprising: a scenario input layer, a strategy decision layer, and an execution linkage layer, wherein:

[0035] The scene input layer, connected to the strategy decision layer, is used to obtain the current scene state of the vehicle and transmit it to the strategy decision layer;

[0036] The strategy decision layer, connected to the execution linkage layer, is used to identify the current operating scenario of the vehicle based on the current scenario state, and based on the current operating scenario, determine multiple target loads to be scheduled for power supply among the loads contained in the vehicle, as well as the power supply parameters of the target loads under the current operating scenario. The power supply parameters include power supply priority, power supply domain and power supply budget; and send the power supply parameters to the execution linkage layer.

[0037] The execution linkage layer is used to allocate power domains and power budgets to target loads corresponding to the current operating scenario based on power supply priority.

[0038] Thirdly, this application provides an electronic device, including: a memory and a processor;

[0039] The memory stores instructions that the computer executes;

[0040] The processor executes computer execution instructions stored in memory, causing the processor to perform the first aspect and / or various possible implementations of the first aspect as described above.

[0041] Fourthly, this application provides a vehicle, including a vehicle body and a load power supply dispatching system as described in the second aspect above.

[0042] Fifthly, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a device such as a processor, are used to implement the first aspect and / or various possible embodiments of the first aspect.

[0043] In a sixth aspect, this application provides a computer program product, including a computer program that, when executed by a device such as a processor, implements the first aspect and / or various possible implementations of the first aspect.

[0044] The load power supply scheduling method, system, and vehicle provided in this application identify the current operating scenario of the vehicle and, based on this scenario, determine multiple target loads to be scheduled for power supply among the loads included in the vehicle, as well as the power supply parameters of the target loads under the current operating scenario. This enables adaptive adjustment of the power supply resource configuration for each load under dynamic operating conditions. The power supply parameters include power supply priority, power supply domain, and power supply budget, allowing for flexible differentiation of power supply quotas between critical and non-critical loads for different scenarios. This enables limiting the power output of unnecessary loads as needed and prioritizing power supply resources for core loads, improving the flexibility and adjustability of multi-load power supply scheduling. Based on power supply priority, power supply domains and power supply budgets are allocated to target loads corresponding to the current operating scenario, enabling differentiated power supply allocation, improving the flexibility of load power supply scheduling, and ultimately improving the overall vehicle power supply efficiency. Attached Figure Description

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

[0046] Figure 1 A schematic flowchart of the load power supply scheduling method provided in the embodiments of this application;

[0047] Figure 2 This is a schematic diagram illustrating an application of the load power supply scheduling method provided in an embodiment of this application.

[0048] Figure 3 A schematic diagram of the load power supply scheduling system provided in the embodiments of this application;

[0049] Figure 4 This is an application diagram of the load power supply scheduling system provided in the embodiments of this application;

[0050] Figure 5 A timing interaction diagram of the load power supply scheduling system provided in the embodiments of this application;

[0051] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0052] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0053] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0054] In related technologies, 48V power systems still employ static power supply strategies in different vehicle scenarios, leading to a mismatch between critical business operations, energy consumption, and response speed. Without scenario-based scheduling, 48V chassis, thermal management, and high-power comfort loads can only use static power supply strategies, making it difficult to simultaneously achieve energy saving, response speed, and critical business continuity. Furthermore, existing static solutions cannot explain why the same load should adopt different power domains or different power budgets in different scenarios.

[0055] Specifically, the requirements for power supply domain, power budget, and wake-up actions differ depending on the scenario of parking, driving, recharging, remote wake-up, and intelligent driving standby. If controlled by a fixed switch or fixed power limit, it can easily lead to problems such as slow response of critical loads, premature power consumption of comfort loads, resource competition between recharging thermal management and cabin loads, and insufficient power supply to critical chassis or thermal management objects during intelligent driving standby. The 48V load is not a fixed switch, but rather needs to be dynamically allocated among the chassis, thermal management, and high-power comfort objects according to scenarios such as parking, driving, recharging, and remote wake-up.

[0056] To overcome the limitations of existing load power supply scheduling methods, this application provides a load power supply scheduling method that combines the current operating scenario of the vehicle with the load characteristics to dynamically adjust the power supply domain and power supply budget of the target load, thereby improving the flexibility of load power supply scheduling and improving the overall vehicle power supply efficiency.

[0057] In other words, in scenarios such as parking, driving, recharging, remote wake-up, and intelligent driving standby, the 48V / 12V power supply of the chassis, thermal management, and high-power comfort load is dynamically scheduled according to the power supply priority and target load.

[0058] The purpose of this application is to combine system architecture, migration threshold, control strategy, safety closed loop and continuous evolution mechanism to improve the flexibility of load power supply scheduling in the context of the gradual introduction of centralized intelligent power distribution in zone control units (ZCU), battery management system (BMS) / on-board charger (OBC) distributed DC-DC converter (DCDC), thermal management, high-power chassis and high-power comfort load.

[0059] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0060] Figure 1 This is a flowchart illustrating a load power supply scheduling method provided in an embodiment of this application. Figure 1 As shown, the load power supply scheduling method includes:

[0061] S101. Identify the current operating scenario of the vehicle.

[0062] For example, the current operating scenarios may include parking, driving, recharging, remote wake-up, and intelligent driving standby scenarios.

[0063] In this step, the current operating scenario characterizes the vehicle's current operating state and serves as the basis for subsequently determining the target load and power supply parameters. The current operating scenario can be any of the operating scenarios mentioned above.

[0064] Optionally, the vehicle operation information includes at least one or more of the following: vehicle speed, gear status, ignition status, braking status, charging gun connection status, high-voltage system status, 48V bus voltage, battery charge status, and vehicle power-on / off status.

[0065] In one possible embodiment, when the vehicle is in a parking-related state, the current operating scenario can be identified as a parking scenario; when the vehicle is in a driving-related state, the current operating scenario can be identified as a driving scenario; when the vehicle is in a charging or recharging-related state, the current operating scenario can be identified as a recharging scenario.

[0066] S102. Based on the current operating scenario, determine multiple target loads to be scheduled for power supply from the loads contained in the vehicle, as well as the power supply parameters of the target loads under the current operating scenario. The power supply parameters include power supply priority, power supply domain, and power supply budget.

[0067] In this step, the target load is used to characterize the specific load object participating in this round of power supply scheduling under the current operating scenario, and the power supply parameters are used to describe the power supply configuration corresponding to the target load.

[0068] In practice, after identifying the current operating scenario, all candidate load information is read from the locally stored load list. The load list records the load identifier, power supply priority, rated power, minimum sustaining power, power supply status, and current connection status of each load. Subsequently, based on the current operating scenario and the status of each load, the loads are filtered to obtain multiple target loads to be scheduled for power supply.

[0069] For example, in a parking scenario, the target load may include a parking air conditioner, a vehicle refrigerator, cabin lighting, door actuators, and some communication modules; in a driving scenario, the target load may include active chassis actuators, steering-related 48V loads, a thermal management pump, a cooling fan, and some comfort equipment; in a charging scenario, the target load may include a battery thermal management unit, a charging communication module, cooling actuators, and necessary body control loads. Loads not selected in the current scenario are marked as non-target loads and kept in a powered-off, power-limited, or standby state.

[0070] Furthermore, the power supply parameters of the target load under the current operating scenario are determined, including power supply priority, power supply domain, and power supply budget. The power supply priority indicates the order or importance of power supply to the target load in this round of scheduling; the power supply domain indicates the power supply range or channel accessed by the load, such as 48V / 12V; and the power supply budget indicates the upper limit of power available to the load under the current operating scenario. Optionally, the power supply parameters of the target load can be determined by combining the current operating scenario, the target load status, and available resources.

[0071] It's important to note that the power supply priority for loads differs across operating scenarios. While loads inherently have a basic power supply priority (e.g., chassis safety loads take precedence over comfort loads), specific operating scenarios add weights to determine the current power supply priority. This priority is determined by a combination of factors, including safety relevance, regulatory or functional safety requirements, necessity in the current scenario, user perception impact, power demands, and whether delays are possible. For example, in refueling scenarios, BMS, charging management, and thermal management take priority; in driving scenarios, chassis safety and power-related loads take priority; and in remote wake-up scenarios, communication, door locks, cabin preprocessing, and necessary thermal management take priority.

[0072] S103. Based on power supply priority, allocate power supply domain and power supply budget to the target load corresponding to the current operating scenario.

[0073] This step is used to perform differentiated power scheduling for each of the multiple target loads; that is, to allocate power domains and power objects differently for each target load. Target loads may include chassis loads, thermal management loads, and high-power comfort loads.

[0074] In this step, power supply priority drives the resource allocation order, while power supply domains and power budgets constitute the actual power supply resources executed. Specifically, after determining the target load and its power supply parameters, all target loads are first sorted according to their power supply priority, forming a scheduling queue from high to low. Then, power supply domain allocation and power budget distribution are executed item by item according to the scheduling queue. For power supply domain allocation, the corresponding domain switches, relays, electronic fuses, or semiconductor power distribution channels are controlled to connect the target load to its target power supply domain. For power budget allocation, the power budget value is issued to the corresponding load controller or domain controller. The power budget value can be expressed as the maximum allowable power, the maximum allowable current, the upper limit of the duty cycle, or a tiered power level.

[0075] Optionally, if the target load is already in the target power domain, the domain connection is maintained, and only its power supply budget is updated; if the target load is currently in a different power domain and adjustment is possible, power domain adjustment is performed, and the corresponding power supply budget is enabled after the adjustment is completed. It should be noted that after each allocation, the bus voltage, current, and remaining power in the domain are read, the allocable resources are updated in real time, and then the next target load in the queue is processed.

[0076] In one possible implementation, for allocated loads, if the scenario remains unchanged and the power reserve is stable in subsequent scheduling cycles, the original power supply domain and power budget are kept unchanged; if the scenario changes, the available power on the source side decreases, or a new high-priority load is added, the queue calculation and resource reallocation are retried.

[0077] The load power supply scheduling method provided in this application identifies the current operating scenario of the vehicle and, based on this scenario, determines multiple target loads to be scheduled for power supply among the loads included in the vehicle, as well as the power supply parameters of the target loads under the current operating scenario. This allows for adaptive adjustment of the power supply resource configuration of each load under dynamic operating conditions. The power supply parameters include power supply priority, power supply domain, and power supply budget. This allows for flexible differentiation of power supply quotas between critical and non-critical loads for different scenarios, restricting the power output of unnecessary loads as needed and prioritizing power supply resources for core loads, thereby improving the flexibility and adjustability of multi-load power supply scheduling. Based on power supply priority, a power supply domain and power supply budget are allocated to the target load corresponding to the current operating scenario, enabling differentiated power supply allocation, improving the flexibility of load power supply scheduling, and ultimately improving the overall vehicle power supply efficiency.

[0078] Based on the above embodiments, S102, determining multiple target loads to be scheduled for power supply from the loads included in the vehicle, and the power supply parameters of the target loads in the current operating scenario, may further include: determining a preset scenario template corresponding to the vehicle based on the vehicle model or configuration; and calling the preset scenario template to determine multiple target loads to be scheduled for power supply from the loads included in the vehicle, and the power supply parameters of the target loads in the current operating scenario, wherein the preset scenario template contains the power supply parameters of the loads in different operating scenarios.

[0079] In this embodiment, vehicle identification information is first read, and a preset scenario template matching the vehicle is retrieved from the template library based on the vehicle model code or configuration parameters. The preset scenario template contains power supply parameters for loads under different operating scenarios. Further, based on the current operating scenario, the preset scenario template is invoked, and multiple target loads to be scheduled for power supply are determined in the part corresponding to the current operating scenario, and the power supply parameters of the target loads under the current operating scenario are extracted.

[0080] This template-based approach eliminates the need to re-establish power supply rules when switching scenarios. Instead, it directly obtains the target load and its power supply parameters that are suitable for the current operating scenario based on the vehicle model or configuration, and uses these parameters for subsequent power allocation. The preset scenario templates pre-contain power supply parameter configurations for different operating scenarios, enabling rapid lookup and output of target load power supply parameters upon detecting scenario changes, thus ensuring that power supply scheduling remains consistent with the vehicle's current operating conditions.

[0081] This embodiment determines a preset scenario template based on the vehicle model or configuration, and calls the preset scenario template based on the current operating scenario to determine the target load and its power supply parameters. This enables the vehicle to accurately select a preset scenario template that matches its own model or configuration, and quickly determine the target load and its power supply parameters in the current operating scenario. This reduces the parameter reconstruction overhead when switching scenarios, improves the adaptability and response speed of multi-load power supply scheduling, and keeps the power supply parameters consistent with the actual assembly state of the vehicle.

[0082] Optionally, the preset scenario template is generated in the following way: read the scenario status and determine the scenario label corresponding to the scenario status; read the load migration results in the vehicle and determine the available power supply domains for each load and whether multi-path power supply is supported; read the service priority and obtain the power supply priority, power supply budget, wake-up order and degradation mode of each load under the scenario label; based on the template selector, the preset scenario template is formed according to the scenario label, the available power supply domains for each load, whether multi-path power supply is supported, power supply priority, power supply budget, wake-up order and degradation mode.

[0083] As can be understood, a preset scenario template is a set of parameters for power supply and wake-up behaviors of multiple target loads under different operating scenarios. Specifically, it includes: scenario tags, applicable conditions, load object list, load family, power domain configuration, power budget, wake-up order, delay time, degradeable mode, preemption rules, fallback rules, recovery conditions, network wake-up actions, and log recording fields. Preset scenario templates are used to transform abstract operating scenarios into executable power control parameters.

[0084] In some embodiments, the scenario state is first read to determine the scenario label corresponding to the scenario state, such as power replenishment, driving, or remote wake-up. Then, the load migration results in the vehicle are read to determine the available power supply domain for each load and whether it supports multi-path power supply, such as 48V / 12V dual-path power supply. Next, the service priority is read to obtain the power supply priority, power budget, wake-up order, and degradation mode for each load in the current scenario. Finally, based on the template selector, a preset scenario template is formed according to the scenario label, available power supply domain for each load, whether multi-path power supply is supported, power supply priority, power budget, wake-up order, and degradation mode.

[0085] Specifically, business priorities can be defined as a business priority matrix. Elements in the business priority matrix represent the priority and power supply parameter mapping between scenarios, services, and loads. Matrix rows can represent vehicle operating scenarios, and matrix columns can represent service categories or load families, such as chassis, safety, thermal management, BMS / charging, cabin comfort, and high-power accessories. Matrix elements must include at least power supply priority, allowed power supply domain, power budget level, wake-up order, allowable delay time, degradeable mode, preemption permission, and recovery conditions.

[0086] During power supply allocation, for loads supporting multi-path power supply, the power supply path is dynamically selected based on the current operating scenario. For example, in a driving scenario, if the target load supports dual-path power supply of 48V / 12V, the 48V power supply domain is prioritized to improve response speed; in a parked scenario, if 48V power supply domain resources are scarce, the system switches to the 12V power supply domain to free up 48V resources for high-priority loads. For loads supporting degraded power, their power level is dynamically adjusted based on the current operating scenario. For example, in a charging scenario, if a comfort load supports power degradation, its power budget is reduced from a high-power level, such as 100W, to a medium-power level, such as 50W, to ensure the high power requirements of the BMS and charging manager.

[0087] For example, a preset scenario template may include a power supply template and a wake-up template. The power supply template may include the load's power supply domain, power budget, current limiting threshold, preemptibility flag, and recovery conditions; the wake-up template may include the network wake-up object, wake-up sequence, wake-up hold time, and allowed sleep conditions.

[0088] The load migration result refers to configuration results such as whether the load has been migrated from 12V to 48V, whether the 12V power supply path is still retained, whether 48V / 12V dual-path is supported, and whether tiered wake-up and power-limited operation are supported. The load migration result directly participates in template selection to limit the range of selectable templates. That is, only loads that have been migrated to 48V or support dual-path can enter the 48V power supply template; loads that are still at 12V can only enter the 12V power supply template or the delayed wake-up template.

[0089] In this embodiment, by organizing the upgraded 48V loads (i.e., the migrated loads) into executable preset scenario templates according to different operating scenarios, the 48V power supply no longer uses a static configuration but is dynamically scheduled based on the current operating scenario and service priority. Since the preset scenario templates simultaneously include scenario dimensions, power supply domain constraints, and service constraints, they can quickly output load power supply configurations that match the current operating conditions when the vehicle is in different operating conditions.

[0090] It should be noted that the preset scene templates can be managed in layers according to vehicle model and configuration, and the version of the preset scene template is uniformly bound to the vehicle model or configuration.

[0091] This embodiment generates a preset scenario template by combining scenario status, load migration results, and service priority. This allows the preset scenario template to be updated synchronously with the actual load status of the vehicle. It also provides a unified expression of power supply priority, power budget, and wake-up order under different scenarios, thereby improving the matching degree between the template and the current operating scenario and providing a more stable parameter basis for subsequent power supply scheduling.

[0092] In some embodiments, after allocating a power domain and power budget to the target load corresponding to the current operating scenario based on power supply priority, the method may further include: performing the following operations on the target load: real-time monitoring of the target load's execution results for the power domain and power budget, the execution results including the power domain allocation results and the power budget execution status; determining the energy efficiency indicators and response indicators of the target load based on the execution results; and evaluating the effectiveness of the power supply allocation for the target load based on the energy efficiency indicators and response indicators, the effectiveness of the power supply allocation being used to optimize the preset scenario template corresponding to the vehicle.

[0093] In this embodiment, after the power supply domain and power budget are issued, the actual access domain information, bus current, voltage, load power and load status flag of the target load are continuously collected, and the collected results are compared with the preset scheduling parameters to obtain the power supply domain allocation result and the power supply budget execution status.

[0094] Furthermore, energy efficiency indicators are calculated based on the deviation between the actual power consumption and the budgeted power of the target load, the effective working output per unit power, and the continuous operating time. Simultaneously, response indicators are calculated based on the time difference between the target load receiving the scheduling instruction and entering the target working state. Based on these indicators, the effectiveness of power supply allocation to the target load is scored, and the scoring results are written into a template parameter table corresponding to the current vehicle model and current scenario label. This is used to update the preset scenario template corresponding to the vehicle, such as optimizing the power supply domain, power budget, and wake-up sequence configuration under this operating scenario.

[0095] This implementation introduces real-time monitoring and template optimization after power distribution, enabling the actual execution of the load to directly participate in template optimization. It also ensures that the power domain and power budget configuration during subsequent scenario calls are consistent with the actual operating conditions of the vehicle, thereby improving the adaptability of the template to different operating scenarios and enhancing the accuracy of critical load scheduling and the consistency of resource utilization.

[0096] In one possible implementation, the power supply parameters also include wake-up data, which includes a network wake-up object, wake-up timing, wake-up hold time, and allowed sleep conditions. The method may also include:

[0097] Based on the wake-up data, determine whether the target load has a wake-up requirement; if the target load has a wake-up requirement, control the wake-up of the target load based on the wake-up data.

[0098] In the specific implementation, the wake-up data in the power supply parameters is first read, and combined with the current working status of the target load, the network online status, and the current operating scenario, it is determined whether the target load is in a state awaiting wake-up. If the target load is in a sleep, low-power standby, or unresponsive state, and its corresponding network wake-up object is consistent with the currently scheduled object, then it is determined that the target load has a load wake-up requirement. If the target load is already in a normal working state, or the conditions for allowing sleep have not yet been met, then it is determined that there is no load wake-up requirement.

[0099] Optionally, if it is determined that the target load has a load wake-up requirement, a network wake-up message is sent to the target load according to the wake-up sequence, carrying the target load identifier, wake-up priority, and wake-up trigger time in the wake-up message, so that the target load is activated in a predetermined order. Subsequently, the power supply enable state of the target load is maintained according to the wake-up hold time, and the operation feedback signal of the target load is continuously monitored. When the sleep condition is detected to be met, a sleep control command is issued to the target load to switch it to sleep state.

[0100] This implementation integrates the network wake-up target, wake-up sequence, wake-up hold time, and allowed sleep conditions into the power supply parameters, directly linking load power supply scheduling with wake-up control. Wake-up determination and execution are then performed based on the current state of the target load. Consequently, the target load can be woken up promptly when needed and resume sleep according to control constraints after the conditions are met, thus ensuring that power supply scheduling remains consistent with the vehicle's current operating condition.

[0101] As one possible implementation, after allocating power domains and power budgets for the target loads corresponding to the current operating scenario based on power supply priority, it may also include: if there is a conflict between the power supply domains or power budgets of different loads among multiple target loads, then based on the power supply priority of different loads, control the load with higher power supply priority to perform power preemption, and control the load with lower power supply priority to perform power rollback, wherein power rollback includes reducing the power budget.

[0102] In this embodiment, after the power supply domain and power budget allocation are completed, the power supply domain occupancy status and power budget occupancy status of each target load are continuously compared. When it is detected that multiple target loads simultaneously request the same power supply domain, or that the requested power of a target load exceeds the currently allocable budget, based on the power supply priority of different loads, the load with higher power supply priority is controlled to perform power preemption. For example, a preemption control command is sent to the power converter or relay switch corresponding to the load, so that it obtains the effective power supply permission of the corresponding power supply domain. At the same time, the load with lower power supply priority is controlled to perform power rollback. For example, a rollback control command is sent to the load to reduce its power supply budget to the allowable range, rather than directly disconnecting the power supply, and restoring it after the resources are released.

[0103] The reduction in the power supply budget can be achieved by cutting it by a fixed percentage, by a differential amount, or by reducing it to a minimum guaranteed budget. The minimum guaranteed budget is used to maintain the basic standby operation of the load. Optionally, the effectiveness of preemption and fallback can be confirmed based on current sampling values, voltage feedback values, and load response status, and the current power supply configuration can be updated accordingly.

[0104] In some embodiments, load migration results can affect power preemption. For example, loads migrated to 48V with high power priority can preempt the power budget of comfort-type loads when power is insufficient. Complex loads that only support a single power path and have low power priority will fall back first in case of conflict.

[0105] This embodiment performs preemption or rollback based on power supply priority when conflicts exist in the power supply domain or power budget. This ensures that loads with high power supply priority receive timely power supply guarantees during resource conflicts, while loads with low power supply priority release their occupied resources through rollback. This maintains consistency between the allocation results of the power supply domain and power budget and the current power supply priority. Based on this, resource allocation when multiple loads are supplied concurrently can better align with vehicle operating conditions, and improves the determinism and consistency of power supply scheduling.

[0106] As one possible implementation, during the process of allocating the power domain and power budget for the target load corresponding to the current operating scenario, the scheduling log can record the object, budget, and reason code. Here, the object represents the target load, the budget includes the power domain and power budget, and the reason code records the triggering reason for the scheduling decision, such as scenario switching or power conflict.

[0107] Furthermore, after executing critical actions, an object number, reason code, timestamp, and current version information are generated and saved in association with the execution result. Among them, critical actions are control actions that have a substantial impact on the power supply status, power budget, or network wake-up status, such as connecting the 48V branch, switching to the 12V backup path, increasing or decreasing the power budget, waking up the load, freezing the load, performing preemption, and performing rollback.

[0108] Optionally, before allocating a power supply domain and power supply budget to the target load corresponding to the current operating scenario based on power supply priority, the process may further include: determining the duration for which the current operating scenario will be continuously set to a stable state.

[0109] In this embodiment, a stabilization duration, also known as a scenario stabilization observation window, is set and can be determined based on vehicle configuration, load type, and current power management strategy. After identifying the current operating scenario, the vehicle's scenario status is continuously collected, and the duration is accumulated while the scenario status remains consistent with the current operating scenario. When the duration reaches the set stabilization duration, a scenario stabilization confirmation signal is output, serving as the trigger condition for subsequent allocation of power domains and power budgets based on power supply priority. In practical applications, the stabilization duration can also be configured according to vehicle operating requirements; this application does not limit this.

[0110] In other words, before allocating a power domain and power budget to the target load for the current operating scenario, it is necessary to confirm that the scenario state and execution results remain stable within a set stabilization period. Specific conditions include: the vehicle scenario label has not changed; vehicle speed / gear / recharge status / remote wake-up status remains continuously valid; the 48V bus and 12V bus voltages are within allowable ranges; critical loads within the target load have completed wake-up or entered the target power supply state; the power budget has not continuously exceeded limits; no execution failures have been reported; and no new faults or preemption requests have been added to critical loads. By setting a stabilization period, the allocation strategy can be confirmed to be effective after scenario changes.

[0111] This implementation method first confirms the stable duration of the current operating scenario before allocating power supply domains and power budgets. This ensures that scenario determination has a continuous constraint, so that power allocation only takes effect in a stable state after scenario switching. As a result, the matching degree between power supply scheduling results and the current operating condition of the vehicle can be improved, and the continuity and consistency of power supply resource allocation can be maintained.

[0112] In some embodiments, identifying the current operating scenario of a vehicle may include: obtaining the current scenario state of the vehicle; performing normalization processing and consistency verification on the current scenario state; and applying a rule machine or state machine to identify the current operating scenario of the vehicle based on the verified current scenario state.

[0113] It is understandable that the current state of a vehicle can include its speed and gear, recharging status, and remote wake-up status, which can be obtained at fixed intervals.

[0114] In this embodiment, after obtaining the current scene state of the vehicle, the current scene state is normalized and its consistency is verified. Specifically, normalization can be achieved through field mapping, unified enumeration values, null value filling, and outlier truncation. Based on the processed current scene state, the states at the same time are cross-compared. When the states meet the preset combination relationship, they are determined to be valid scene states, that is, the current scene states that have passed the verification.

[0115] Furthermore, based on the verified current scenario state, a rule machine or state machine is applied to identify the vehicle's current operating scenario. Specifically, when the rule machine or state machine performs scenario identification, it first defines a set of scenario states, such as parking, driving, charging, remote wake-up, intelligent driving standby, and unlocking for boarding; then it defines input conditions, including vehicle speed, gear position, charging connection status, charging current, remote wake-up request, intelligent driving standby flag, door lock status, battery state of charge (SOC), BMS status, and user operation. The rule machine determines the current operating scenario based on the combination of conditions, which can be represented as a current operating scenario label. The state machine adds state transition conditions, entry conditions, exit conditions, and hysteresis time to this, and performs state transitions based on the above conditions to obtain the current operating scenario. For example, if a charging gun connection is detected and the BMS enters charging mode, the vehicle enters the charging scenario; if a remote air conditioning request is received and the vehicle is not powered on, the vehicle enters the remote wake-up scenario; if the vehicle speed is greater than a threshold and the gear is in D mode, the vehicle enters the driving scenario.

[0116] This embodiment normalizes and verifies the current scene state of the vehicle, and then executes rules or state transition identification based on the verification results. This can alleviate the problem of inconsistent states from different sources and ensure that the identified current operating scene is consistent with the actual operating condition of the vehicle, thereby providing a reliable scene basis for subsequent load power supply scheduling.

[0117] Figure 2 This is a schematic diagram illustrating an application of the load power supply scheduling method provided in an embodiment of this application. For example... Figure 2 As shown, the process first obtains the vehicle's current scene state and identifies the vehicle's current operating scene based on this state. Then, it retrieves the corresponding preset scene template to determine the target load to be scheduled and its power supply parameters. After confirming that the current operating scene will remain stable for a set duration, it allocates a power domain, power budget, and wake-up action to the target load. If power domain or power budget conflicts occur between different loads, power preemption and fallback are performed based on power supply priority. Furthermore, the execution results of the entire scheduling scheme are monitored in real time to determine the energy efficiency and response indicators corresponding to the load power supply scheduling, thus completing the scenario-based dynamic power supply scheduling of the vehicle's 48V loads.

[0118] In one specific embodiment, when the vehicle enters a charging scenario, priority is given to ensuring power supply to the BMS, charging manager, and key thermal management objects, while high-power comfort loads are delayed in being activated. When the vehicle switches from charging to unlocking and waiting to get in, high-power objects and comfort loads in the cabin are gradually restored. For intelligent driving standby scenarios, high-critical chassis objects and thermal management backup objects have higher priority than general comfort objects.

[0119] In summary, the load power supply scheduling method provided in this application has at least the following advantages:

[0120] First, by combining scenario status, load migration results, and business priorities, preset scenario templates are generated. These templates are updated synchronously with the actual load status of the vehicle, improving the matching degree between the templates and the current operating scenario. Preset scenario templates are determined based on vehicle model or configuration, and the target load and its power supply parameters are determined by calling the preset scenario templates based on the current operating scenario. This allows the vehicle to quickly determine the target load and its power supply parameters under the current operating scenario, improving the adaptability and response speed of multi-load power supply scheduling, while ensuring that the power supply parameters remain consistent with the actual assembly status of the vehicle.

[0121] Secondly, by first confirming the stable duration of the current operating scenario before allocating power supply domains and power budgets, the power allocation can be made effective only in stable conditions after scenario switching. This improves the matching degree between power supply scheduling results and the current operating conditions of vehicles, and maintains the continuity and consistency of power resource allocation. Furthermore, by introducing real-time monitoring and template optimization after power allocation, the adaptability of templates to different operating scenarios is improved, and the accuracy of critical load scheduling and the consistency of resource utilization are enhanced.

[0122] Third, by unifying network wake-up targets, wake-up timing, wake-up hold time, and allowed hibernation conditions into power supply parameters, target loads can be woken up promptly when needed and resume hibernation according to control constraints after conditions are met, thereby ensuring that power supply scheduling is consistent with the current operating conditions of the vehicle. By performing preemption or rollback based on power supply priority when there are conflicts in the power supply domain or power supply budget, resource allocation when multiple loads are supplied concurrently can be more in line with the vehicle's operating conditions, and the determinism and consistency of power supply scheduling can be improved.

[0123] Fourth, based on power supply priority, a power supply domain and power budget are allocated to the target load corresponding to the current operating scenario, enabling differentiated power supply allocation, improving the flexibility of load power supply scheduling, and thus improving the overall vehicle power supply efficiency. Since this solution clearly defines object boundaries, parameter boundaries, state transitions, and record results, it can directly proceed to detailed design, verification, calibration, and after-sales traceability processes, effectively shortening the development and debugging cycle, reducing testing and calibration workload, and improving after-sales troubleshooting efficiency.

[0124] In summary, the load power supply scheduling method provided in this application embodiment can improve the flexibility of load power supply scheduling, thereby improving the overall vehicle power supply efficiency.

[0125] Figure 3 This is a schematic diagram of the load power supply scheduling system 30 provided in an embodiment of this application. Figure 3 As shown, the load power supply scheduling system provided in this application embodiment includes a scene input layer 301, a strategy decision layer 302, and an execution linkage layer 303, wherein:

[0126] The scene input layer 301 is connected to the strategy decision layer 302 and is used to obtain the current scene state of the vehicle and transmit it to the strategy decision layer 302.

[0127] For example, the current scene status of a vehicle may include vehicle speed and gear, recharging status, and remote wake-up status, which can be obtained at fixed intervals.

[0128] The strategy decision layer 302, connected to the execution linkage layer 303, is used to identify the current operating scenario of the vehicle based on the current scenario state, and based on the current operating scenario, determine multiple target loads to be scheduled for power supply among the loads contained in the vehicle, as well as the power supply parameters of the target loads under the current operating scenario. The power supply parameters include power supply priority, power supply domain and power supply budget; and send the power supply parameters to the execution linkage layer 303.

[0129] In this embodiment, the strategy decision layer 302 may include a scene recognizer, a service priority matrix, and a template selector. The scene recognizer identifies the vehicle's current operating scenario based on the current scenario state. The template selector, based on the current operating scenario, calls a preset scene template library to determine multiple target loads to be scheduled for power supply from the loads included in the vehicle, as well as the power supply parameters of the target loads under the current operating scenario. The current operating scenario includes at least parking, driving, recharging, remote wake-up, and intelligent driving standby.

[0130] Execute linkage layer 303, which is used to allocate power domain and power budget to the target load corresponding to the current operating scenario based on power supply priority.

[0131] In this embodiment, the execution linkage layer 303 may include a zone power controller, a power budget controller, and a Wake-on-LAN manager. The target load may include a chassis load, a thermal management load, and a high-power comfort load. The zone power controller is used to allocate power domains to the target load; the power budget controller is used to allocate power budgets to the target load; and the Wake-on-LAN manager is used to control the wake-up of the target load.

[0132] The regional power controller, power budget controller, and network wake-up manager output control results according to preset priorities. These preset priorities are not entirely fixed and consist of two parts: a base priority and a scenario-adjusted priority. The base priority is determined by power supply priority, load type, and safety relevance, and is typically fixed based on vehicle model configuration. The scenario-adjusted priority is dynamically adjusted based on the current scenario, business requirements, power margin, and fault status. For example, comfort loads have higher priority in parking or welcoming scenarios, but their priority decreases during refueling thermal management or when critical driving loads are preempted. The final preset priority is determined based on the base priority, scenario weights, and state constraints.

[0133] Optionally, the load power supply scheduling system 30 can be deployed on a 48V platform containing a scene identifier, a service priority matrix, load migration results, and a network wake-up controller, and establish an interactive link around the scene identifier, template selector, area power controller, and power budget controller.

[0134] For example, the load power supply scheduling system 30 also provides a version management interface for managing parameters, rules, templates, and log objects by vehicle model, software version, or configuration version. Parameters are calibrable or configurable data, such as scene entry threshold, exit threshold, stable observation window time, power budget upper limit, current limiting threshold, delay time, wake-up hold time, and recovery conditions. Rules are the logic for performing judgments based on parameters and status, such as scene identification rules, template selection rules, preemption rules, rollback rules, recovery rules, and hibernation rules. Log objects are record objects generated after the system runs, including scene tag, template number, object number, power supply domain, budget value, action result, reason code, timestamp, version number, and abnormal status.

[0135] Figure 4 This is a schematic diagram illustrating an application of the load power supply scheduling system provided in an embodiment of this application. For example... Figure 4 As shown, the vehicle scenario manager outputs scenario tags to the central power strategy controller, which integrates the business priority matrix. The central power strategy controller then calls the regional power supply template library, such as the preset scenario template library, based on the power supply priority. The regional power supply template library outputs three types of templates: front compartment, right side, and rear compartment, which are then distributed to the corresponding ZCU-ML front compartment area controller, ZCU-MR right front compartment area controller, and ZCU-R rear compartment area controller, respectively. The ZCU-ML front compartment area controller manages chassis load through chassis budget control, the ZCU-MR right front compartment area controller outputs thermal management power supply to control thermal management loads, and the ZCU-R rear compartment area controller relies on a comfort load wake-up mechanism to control high-power loads. This achieves hierarchical power supply scheduling for the entire vehicle based on region and load type.

[0136] Figure 5 A timing interaction diagram of the load power supply scheduling system provided in an embodiment of this application. For example... Figure 5 As shown, the scene recognizer submits the vehicle's current operating scene tag to the template selector. After matching the corresponding preset scene template, the template selector determines the target load and sends the power supply parameters of the target load to the execution linkage layer. Based on the received power supply parameters, the execution linkage layer performs power supply and wake-up actions on the target load, namely, allocating a power supply domain and power budget to the target load, and controlling the wake-up of the target load. After the target load completes its execution, it sends the execution results and energy efficiency data back to the template selector, forming a complete closed-loop on-board load scenario-based power supply scheduling interaction link. The energy efficiency data includes energy efficiency indicators and response indicators.

[0137] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 6 As shown, the electronic device 60 provided in this application embodiment includes at least one processor 601 and a memory 602. Optionally, the electronic device 60 further includes a communication component 603. The processor 601, memory 602, and communication component 603 are connected via a bus.

[0138] In the specific implementation process, at least one processor 601 executes computer execution instructions stored in memory 602, causing at least one processor 601 to execute the above-described load power supply scheduling method.

[0139] The specific implementation process of processor 601 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0140] In the above embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this application can be directly manifested as being executed by a hardware processor, or executed by a combination of hardware and software modules within the processor.

[0141] The memory may include high-speed memory (HSM) and may also include non-volatile memory (NVM), such as at least one disk storage device.

[0142] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0143] This application also provides a vehicle, including the vehicle body and the aforementioned load power supply dispatching system.

[0144] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described load power supply scheduling method.

[0145] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the above-described load power supply scheduling method.

[0146] The aforementioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as Static Random Access Memory (SRAM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Erasable Programmable Read-Only Memory (EPROM), Programmable Read-Only Memory (PROM), Read-Only Memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.

[0147] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an application-specific integrated circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components in the device.

[0148] The division of units is merely a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.

[0149] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0150] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0151] If a function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, random access memory (RAM), magnetic disks, or optical disks.

[0152] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0153] Finally, it should be noted that other embodiments of this application will readily conceive of by those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein, and is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and alterations may be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A load power supply scheduling method, characterized in that, include: Identify the vehicle's current operating scenario; Based on the current operating scenario, multiple target loads to be scheduled for power supply are determined from the loads contained in the vehicle, and the power supply parameters of the target loads under the current operating scenario are determined. The power supply parameters include power supply priority, power supply domain and power supply budget. Based on the power supply priority, the power supply domain and the power supply budget are allocated to the target load corresponding to the current operating scenario.

2. The load power supply scheduling method according to claim 1, characterized in that, The step of determining multiple target loads to be powered and scheduled from the loads contained in the vehicle based on the current operating scenario, and the power supply parameters of the target loads under the current operating scenario, includes: Based on the vehicle's model or configuration, determine the corresponding preset scene template for the vehicle; Based on the current operating scenario, the preset scenario template is invoked to determine multiple target loads to be scheduled for power supply from the loads contained in the vehicle, as well as the power supply parameters of the target loads under the current operating scenario. The preset scenario template contains the power supply parameters of the loads under different operating scenarios.

3. The load power supply scheduling method according to claim 2, characterized in that, The preset scene template is generated in the following way: Read the scene state and determine the scene label corresponding to the scene state; Read the load migration results in the vehicle to determine the available power supply domain for each load and whether multipath power supply is supported; Read the service priority to obtain the power supply priority, power budget, wake-up order and degradation mode of each load under the scene tag; Based on the template selector, the preset scene template is formed according to the scene tag, the available power domain for each load, whether multi-path power supply is supported, power supply priority, power supply budget, wake-up order and degradeable method.

4. The load power supply scheduling method according to claim 2, characterized in that, After allocating the power supply domain and the power supply budget to the target load corresponding to the current operating scenario based on the power supply priority, the method further includes: For the target load, perform the following operations: Real-time monitoring of the execution results of the target load for the power supply domain and power supply budget, the execution results including the power supply domain allocation results and the power supply budget execution status; Based on the execution results, the energy efficiency and response indicators of the target load are determined. Based on the energy efficiency index and the response index, the effectiveness of power supply allocation for the target load is evaluated, and the effectiveness of power supply allocation is used to optimize the preset scenario template corresponding to the vehicle.

5. The load power supply scheduling method according to any one of claims 1 to 4, characterized in that, The power supply parameters also include wake-up data, which includes network wake-up object, wake-up sequence, wake-up hold time and allowed sleep conditions; The method further includes: Based on the wake-up data, determine whether the target load has a load wake-up requirement; If the target load has a load wake-up requirement, then based on the wake-up data, control the wake-up of the target load.

6. The load power supply scheduling method according to any one of claims 1 to 4, characterized in that, After allocating the power supply domain and the power supply budget to the target load corresponding to the current operating scenario based on the power supply priority, the method further includes: If there is a conflict in the power supply domain or power supply budget of different loads among the multiple target loads, then based on the power supply priority of different loads, the load with higher power supply priority is controlled to perform power supply preemption, and the load with lower power supply priority is controlled to perform power supply rollback, the power supply rollback includes reducing the power supply budget.

7. The load power supply scheduling method according to any one of claims 1 to 4, characterized in that, Before allocating the power supply domain and the power supply budget to the target load corresponding to the current operating scenario based on the power supply priority, the method further includes: Determine the duration for which the current operating scenario will remain stable.

8. The load power supply scheduling method according to any one of claims 1 to 4, characterized in that, The identification of the vehicle's current operating scenario includes: Obtain the current scene status of the vehicle; The current scene state is normalized and its consistency is verified. Based on the verified current scene state, a rule machine or state machine is applied to identify the current operating scene of the vehicle.

9. A load power supply dispatching system, characterized in that, It includes a scene input layer, a strategy decision layer, and an execution linkage layer, among which: The scene input layer is connected to the strategy decision layer and is used to obtain the current scene state of the vehicle and transmit it to the strategy decision layer. The strategy decision layer, connected to the execution linkage layer, is used to identify the current operating scenario of the vehicle based on the current scenario state, and based on the current operating scenario, determine multiple target loads to be scheduled for power supply from the loads contained in the vehicle, as well as the power supply parameters of the target loads under the current operating scenario, the power supply parameters including power supply priority, power supply domain and power supply budget; and send the power supply parameters to the execution linkage layer. The execution linkage layer is used to allocate the power supply domain and the power supply budget to the target load corresponding to the current operating scenario based on the power supply priority.

10. A vehicle, characterized in that, It includes the vehicle body and the load power supply scheduling system as described in claim 9.

Images