In-vehicle HPC power management method and system for centralized architecture

Abstract

The present application discloses a vehicle-mounted HPC power management method and system for a centralized architecture, the method comprising obtaining status information of all PNC IDs in the current scenario; determining a wakeable PNC ID according to the status information; initiating an application pull-up request for an application corresponding to the wakeable PNC ID or a peripheral pull-up request for a peripheral corresponding to the wakeable PNC ID according to the wakeable PNC ID; obtaining the status of the corresponding application; pulling up the corresponding application according to the status of the corresponding application and the application pull-up request; obtaining the status of the corresponding peripheral, and pulling up the corresponding peripheral according to the status of the corresponding peripheral and the peripheral pull-up request. The present application avoids unnecessary energy waste and improves the system response speed and user experience.

Description

Technical Field

[0001] The present application belongs to the field of vehicle power management technology, and specifically relates to a vehicle HPC power management method and system for a centralized architecture. Background Art

[0002] In the traditional vehicle electrical and electronic architecture, each electronic control unit (ECU) is usually responsible for a specific function of the vehicle, such as engine management, brake system, body control, etc. In the centralized architecture, it is composed of a central controller (High Performance Computing, HPC) and a regional controller (MCU). The power management mode of HPC generally adopts the state of the entire HPC being pulled up or sleeping. This means that when the system needs to work, the entire HPC runs at full power; when it is not needed, it enters low power or sleep mode.

[0003] This approach has the following problems and disadvantages:

[0004] 1. High energy consumption: When the whole system is powered on, even if some functions or modules do not need to run, they will be activated due to the overall startup of the ECU or HPC, thus consuming unnecessary power. In this mode, power management lacks flexibility and cannot be fine-tuned according to actual needs.

[0005] 2. Limited response speed: In the overall sleep state, when a specific function or module needs to be started, it is necessary to wait for the entire ECU or HPC to wake up from the sleep state, which may cause a slow response speed and affect the user experience.

[0006] 3. Poor scalability: As the functions of automobiles continue to increase, the complexity of ECUs or HPCs is also increasing. If the power management mode of overall startup and overall sleep continues to be adopted, it will be difficult to adapt to the needs of future automobile function expansion.

[0007] 4. Difficulty in fault isolation: When the whole system is powered on, if a function or module fails, it may affect the operation of the entire ECU or HPC. In a more detailed power management mode, fault isolation can be achieved more easily, reducing the impact of the fault on the entire system. Summary of the invention

[0008] The technical purpose of this application is to provide a vehicle-mounted HPC power management method and system for a centralized architecture to address at least one of the above technical problems existing in the current HPC power management mode, so as to realize intelligent power management of a single HPC with finer-grained unit control.

[0009] In order to achieve the above technical objectives, this application adopts the following technical solutions.

[0010] In a first aspect, an embodiment of the present application provides a vehicle-mounted HPC power management method for a centralized architecture, including:

[0011] Get the status information of all PNC IDs in the current scenario;

[0012] Determine a PNC ID that can be woken up according to the state information;

[0013] Initiate, according to the wakeable PNC ID, an application pull-up request for an application corresponding to the wakeable PNC ID, or a peripheral pull-up request for a peripheral corresponding to the wakeable PNC ID;

[0014] Acquire the state of the corresponding application; and launch the corresponding application according to the state of the corresponding application and the application launch request;

[0015] The state of the corresponding peripheral device is obtained, and the corresponding peripheral device is pulled up according to the state of the corresponding peripheral device and the peripheral device pull-up request.

[0016] In some implementations, the vehicle-mounted HPC power management method further includes:

[0017] The logic configuration of power management is performed in advance based on the scenario, and the correspondence between the application and the peripheral and the PNC ID in each scenario is determined; wherein the correspondence between the application and the PNC ID is one-to-one, one-to-many or many-to-one; and the correspondence between the peripheral and the PNC ID is one-to-one, one-to-many or many-to-one.

[0018] In some implementations, the vehicle-mounted HPC power management method further includes: if the applications have dependencies, the dependent applications correspond to the same PNC ID.

[0019] In some implementations, the vehicle-mounted HPC power management method further includes:

[0020] Determine a dormant PNC ID according to the status information;

[0021] Initiating, according to the dormant PNC ID, an application release request for an application corresponding to the dormant PNC ID or a peripheral release request for a peripheral corresponding to the dormant PNC ID;

[0022] Acquiring the state of the corresponding application, and releasing the corresponding application according to the state of the corresponding application and the application release request;

[0023] Or, the state of the corresponding peripheral device is obtained, and the corresponding peripheral device is released according to the state of the corresponding peripheral device and a release request of the peripheral device.

[0024] In a second aspect, an embodiment of the present application provides an in-vehicle HPC power management system for a centralized architecture, including:

[0025] The local network management module is configured to obtain status information of all PNC IDs in the current scenario and send the status information to the power management module;

[0026] The power management module is configured to determine a wakeable PNC ID according to the state information; and initiate an application pull-up request for an application corresponding to the wakeable PNC ID or a peripheral pull-up request for a peripheral corresponding to the wakeable PNC ID according to the wakeable PNC ID;

[0027] The application state management module is configured to receive the application launch request, obtain the state of the corresponding application, and launch the corresponding application according to the state of the corresponding application and the application launch request;

[0028] The peripheral device driver module is configured to receive the peripheral device pull-up request, obtain the state of the corresponding peripheral device, and pull up the corresponding peripheral device according to the state of the corresponding peripheral device and the peripheral device pull-up request.

[0029] In some implementations, the local network management module is connected to the power management module via a first interface.

[0030] In some embodiments, the power management module is further configured to pre-configure the logic of power management based on the scenario, and determine the correspondence between the application and the peripheral and the PNC ID in each scenario; wherein the application and the PNC ID have a one-to-one, one-to-many or many-to-one correspondence; the peripheral and the PNC ID have a one-to-one, one-to-many or many-to-one correspondence.

[0031] In some implementations, the power management module is connected to the peripheral driver module via a second interface.

[0032] In some implementations, the power management module is connected to the application state management module via a third interface.

[0033] In a third aspect, an embodiment of the present application provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the steps of the vehicle-mounted HPC power management method for a centralized architecture provided in any possible implementation manner of the first aspect of the present application are implemented.

[0034] Compared with the prior art, the vehicle-mounted HPC power management method for a centralized architecture provided by the embodiment of the present application has the following beneficial technical effects: by obtaining the status information of all PNC IDs in the current scenario and determining which PNC IDs are wakeable, the method can ensure that only necessary peripherals or applications are awakened, thereby avoiding unnecessary energy waste; dynamically adjusting the awakened PNC ID according to actual needs makes the energy use of the vehicle-mounted HPC system more efficient, which helps to extend the overall endurance of the vehicle. Once the wakeable PNC ID is determined, the corresponding pull-up request is immediately initiated, and the application or peripheral can be quickly awakened to the working state, which improves the system's response speed and user experience. By centrally managing the wake-up process of the PNC ID, system resources can be allocated more effectively, ensuring that key tasks are given priority, and avoiding system conflicts or instability caused by the simultaneous awakening of multiple units.

[0035] The vehicle-mounted HPC power management system for a centralized architecture provided in the embodiment of the present application has the same technical effect as the above-mentioned vehicle-mounted HPC power management method for a centralized architecture, and will not be described in detail. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] The drawings described herein are for explanation purposes only and are not intended to limit the scope of the present application in any way. In addition, the shapes and proportional dimensions of the components in the drawings are only for illustration purposes and are used to help understand the present application. They do not specifically limit the shapes and proportional dimensions of the components of the present application. Under the guidance of the present application, those skilled in the art can select various possible shapes and proportional dimensions to implement the present application according to specific circumstances. In the drawings:

[0037] Figure 1 A schematic diagram of a vehicle-mounted HPC power management method for a centralized architecture provided in an embodiment of the present application;

[0038] Figure 2 A schematic diagram of the structure of an on-board HPC power management system for a centralized architecture provided in an embodiment of the present application. DETAILED DESCRIPTION

[0039] In order to enable those skilled in the art to better understand the technical solutions in the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this application.

[0040] In the description of this application, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Therefore, the features defined as "first" and "second" may explicitly or implicitly include one or more features.

[0041] At present, the power management mode of HPC is generally still the whole HPC is powered on or in sleep mode. This means that when the system needs to work, the whole HPC runs at full power; when it is not needed, it enters low power consumption or sleep mode. This mode has problems and disadvantages such as high energy consumption, limited response speed, poor scalability and difficulty in fault isolation.

[0042] See also Figure 1 The embodiment of the present application provides a vehicle-mounted HPC power management method for a centralized architecture, including: obtaining status information of all PNC IDs in the current scenario; determining a wakeable PNC ID according to the status information; initiating an application pull-up request for an application corresponding to the wakeable PNC ID, or a peripheral pull-up request for a peripheral corresponding to the wakeable PNC ID, according to the wakeable PNC ID; obtaining the status of the corresponding application; pulling up the corresponding application according to the status of the corresponding application and the application pull-up request; obtaining the status of the corresponding peripheral, and pulling up the corresponding peripheral according to the status of the corresponding peripheral and the peripheral pull-up request.

[0043] This application is based on the current mainstream centralized electronic and electrical architecture, which consists of a central controller (HPC) and a regional controller (MCU). HPC plays the role of the central brain in the entire architecture, and more and more applications and external devices are deployed on HPC.

[0044] The vehicle-mounted HPC power management method for a centralized architecture provided in the embodiment of the present application can be set inside the HPC. For a single HPC, a more sophisticated power management mode is adopted to coordinate the solution of the local network management of the whole vehicle, so as to realize an overall solution of scenario-based power management of the application layer APP and peripherals of the central control unit HPC itself, facilitate software updates and hardware expansions, and facilitate the introduction of new functions and services, while simplifying the system architecture.

[0045] In some embodiments, the vehicle-mounted HPC power management method also includes: pre-configuring the logic of power management based on scenarios, determining the correspondence between applications and peripherals and PNC (Partial Network Cluster) ID (Identification) information in each scenario; wherein the application and the PNC ID have a one-to-one, one-to-many or many-to-one correspondence; the peripheral and the PNC ID have a one-to-one, one-to-many or many-to-one correspondence.

[0046] In some embodiments, if there is a dependency relationship between the application programs, the dependent application programs correspond to the same PNC ID.

[0047] By pre-configuring the power management logic for different scenarios, the system can more intelligently adjust power distribution according to the current scenario, reduce unnecessary power consumption, and thus improve overall power management efficiency. Allowing applications and peripherals to establish a one-to-one, one-to-many, or many-to-one correspondence with the PNC ID provides the system with greater flexibility and scalability. As vehicle functions continue to increase and upgrade, the system can easily adjust the power management logic to adapt to new needs. In addition, through sophisticated power management, the vehicle's power consumption in non-essential states can be reduced, which helps energy conservation, emission reduction, and environmental protection.

[0048] In some embodiments, the vehicle-mounted HPC power management method also includes: determining a dormant PNCID based on status information; initiating an application release request for an application corresponding to the dormant PNC ID, or a peripheral release request for a peripheral corresponding to the dormant PNC ID, based on the dormant PNC ID; obtaining the status of the corresponding application, and releasing the corresponding application based on the status of the corresponding application and the application release request; or obtaining the status of the corresponding peripheral, and releasing the corresponding peripheral based on the status of the corresponding peripheral and the release request of the peripheral.

[0049] For the application layer applications (APP), the embodiments of the present application can be grouped and intelligently scheduled according to the specific functional scenarios of the application. This means that APPs are no longer run continuously without distinction, and all APPs on a single HPC are no longer kept running. Instead, APPs are divided into different functional groups according to the actual needs and usage habits of users, thereby ensuring efficient use of HPC resources and maximizing battery life. This method not only reduces unnecessary background activities, but also improves the smoothness and response speed of the user experience, ensuring that each function can function quickly and accurately at critical moments.

[0050] For the management of peripherals, the embodiments of the present application abandon the traditional "load at power-on" default configuration mode and adopt an interface abstraction solution. This method realizes on-demand calling and intelligent management and control of peripheral resources by logically encapsulating and abstractly defining the power status of various peripherals. Specifically, the system will dynamically determine which peripherals are necessary based on the current actual application scenario, and only load and power these devices, while keeping non-essential peripherals in low power consumption or sleep state. Such a mechanism greatly improves the energy efficiency of the system and reduces energy waste, while also ensuring the immediate response and optimal performance of peripherals at critical moments.

[0051] Based on the same inventive concept as the vehicle-mounted HPC power management method for a centralized architecture provided in the above embodiment, the embodiment of the present application also provides a vehicle-mounted HPC power management system for a centralized architecture, such as Figure 2 As shown, it includes: a local network management module, a power management module, an application status management module and a peripheral driver module.

[0052] The local network management module is configured to obtain status information of all PNC IDs in the current scenario and send the status information to the power management module.

[0053] The power management module is configured to determine a wakeable PNC ID according to the status information; and initiate an application startup request for an application corresponding to the wakeable PNC ID or a peripheral startup request for a peripheral corresponding to the wakeable PNC ID according to the wakeable PNC ID.

[0054] The application state management module is configured to receive an application launch request, obtain the state of a corresponding application, and launch the corresponding application according to the state of the corresponding application and the application launch request.

[0055] The peripheral device driver module is configured to receive a peripheral device pull-up request, obtain the state of the corresponding peripheral device, and pull up the corresponding peripheral device according to the state of the corresponding peripheral device and the peripheral device pull-up request.

[0056] In the embodiment, the local network management module sends the status information of all PNC IDs in the current scenario to the power management module. The power management module parses the received PNC ID status information according to the correspondence between the statically configured PNC ID and the application and the external device.

[0057] In some embodiments, the local network management module sends PNC ID status information to the power management module through a unified first interface using the data type and transmission method defined by the interface, ensuring that the network management module and the power management module parse the information equally, so that the PNC ID status information can be completely, accurately and timely transmitted to the power management module for subsequent execution of actions.

[0058] In the specific implementation, based on the design of the vehicle partial network management system, the power management module can match the applications deployed on the HPC and the connected peripherals with the PNC ID based on the PNC (Partial Network Cluster) functional scenario defined by the vehicle system requirements, and complete the cascade relationship sorting, which can support one-to-one, many-to-one, or one-to-many. It should be noted that if there is a dependency between APPs, they also need to be defined in the same PNC ID to ensure the correct execution of the functional scenario.

[0059] Static configuration is performed in the power management module to implement scenario-based power management logic processing. Through static configuration, the correspondence between applications and peripherals and PNC IDs can be optimized in advance according to application scenarios and requirements, which can reduce resource consumption and response time during dynamic adjustment.

[0060] In the status information, if the PNC ID is a wake-up PNC, that is, the local network corresponding to the PNC ID needs to be pulled up, and the corresponding APP and peripherals need to be woken up, then the PNC ID is 1, and the power management module initiates an application pull-up request for the application corresponding to the wake-up PNC ID, or a peripheral pull-up request for the peripheral corresponding to the wake-up PNC ID. Optionally, if the PNC ID is a sleep-enabled PNC, that is, the local network corresponding to the PNC ID needs to be released, and the corresponding APP and peripherals need to be released to sleep mode, then the PNC ID is 0, and the power management module initiates an application release request for the application corresponding to the sleep-enabled PNC ID, or a peripheral release request for the peripheral corresponding to the sleep-enabled PNC ID.

[0061] The application state management module launches or releases the corresponding application program according to the received application launch request or application release request.

[0062] In some embodiments, the application state management module processes application programs that need to be launched or released simultaneously in a parallel manner.

[0063] The peripheral driver module pulls up or releases the corresponding peripheral according to the received peripheral pull-up request or peripheral release request and the current state of the peripheral.

[0064] In some implementations, the peripheral driver module loads the peripheral or releases it to sleep mode by calling an abstract control interface of the external device.

[0065] In some embodiments, the power management module is connected to the peripheral driver module via a second interface, the power management module is connected to the application state management module via a third interface, and the application state management module is connected to each application via a fourth interface. It should be noted that those skilled in the art can design relevant interfaces as needed to ensure the connection and perfection of the execution link, and this application does not provide detailed descriptions of this.

[0066] The vehicle-mounted HPC power management system for a centralized architecture provided in the embodiment of the present application transforms the traditional HPC overall power management mode into a more sophisticated scenario-based power management mode, and realizes flexible adjustment of the HPC's own application layer APP and peripheral status through the solution of vehicle local network management. It not only saves energy consumption, but also allocates HPC resources to maximize utilization, which can better cope with the complex design of HPC and enhance the scalability of functions.

[0067] The embodiment of the present application greatly reduces the overall energy consumption of HPC by finely dividing the power domain and activating only necessary applications and peripherals. Fine-tuning HPC power management allows computing power to be allocated on demand, avoids idle resources, improves the CPU system performance of the central controller, and can deploy more functions (such as cabin-driver fusion applications) and reflect better performance; and can quickly allocate computing resources according to application requirements, achieve instant response, and provide a more personalized user experience. In a more detailed power management mode, fault isolation can be achieved more easily, reducing the impact of faults on the entire system.

[0068] An embodiment of the present application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the steps of the above-mentioned vehicle-mounted HPC power management method for a centralized architecture are implemented.

[0069] It should be noted that in the present application, the emphasis of the schemes described in various embodiments is different, but the various embodiments are also somewhat interrelated. When understanding the scheme of the present application, the various embodiments can refer to each other.

[0070] The above is a detailed introduction to the vehicle-mounted HPC power management method, system and electronic device for a centralized architecture provided by the present application. This article uses specific examples to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the concept of the present application and should not be understood as limiting the scope of protection of the present application.

Claims

1. A vehicle-mounted HPC power management method for a centralized architecture, characterized in that: The vehicle-mounted HPC power management method is set inside the HPC and is used for scenario-based power management of the application layer APP and peripherals of a single HPC; The vehicle-mounted HPC power management method comprises: Pre-configure the logic of power management based on the scenario, and determine the corresponding relationship between the application and peripherals and the PNCID in each scenario; Get the status information of all PNC IDs in the current scenario; Determine a PNC ID that can be woken up according to the state information; Initiate, according to the wakeable PNC ID, an application pull-up request for an application corresponding to the wakeable PNC ID, or a peripheral pull-up request for a peripheral corresponding to the wakeable PNC ID; Acquire the state of the corresponding application; and launch the corresponding application according to the state of the corresponding application and the application launch request; Acquire the state of the corresponding peripheral device, and pull up the corresponding peripheral device according to the state of the corresponding peripheral device and the peripheral device pull-up request; Determine a dormant PNC ID according to the status information; Initiating, according to the dormant PNC ID, an application release request for an application corresponding to the dormant PNC ID, or a peripheral release request for a peripheral corresponding to the dormant PNC ID; Acquiring the state of the corresponding application, and releasing the corresponding application according to the state of the corresponding application and the application release request; or, obtaining the state of the corresponding peripheral device, and releasing the corresponding peripheral device according to the state of the corresponding peripheral device and a release request of the peripheral device; If the PNC ID is a wake-up PNC ID, the PNC ID is 1; if the PNC ID is a sleep PNC ID, the PNC ID is 0.

2. The vehicle-mounted HPC power management method for a centralized architecture according to claim 1, characterized in that: The vehicle-mounted HPC power management method further includes: the application and the PNC ID are in a one-to-one, one-to-many or many-to-one correspondence relationship; the peripheral and the PNC ID are in a one-to-one, one-to-many or many-to-one correspondence relationship.

3. The vehicle-mounted HPC power management method for a centralized architecture according to claim 2, characterized in that: The vehicle-mounted HPC power management method further includes: if the application programs have dependencies, the application programs with dependencies correspond to the same PNC ID.

4. The vehicle-mounted HPC power management system for the centralized architecture is characterized by: The vehicle-mounted HPC power management system is set inside the HPC and is used for scenario-based power management of the application layer APP and peripherals of a single HPC; The vehicle-mounted HPC power management system includes: The local network management module is configured to obtain status information of all PNC IDs in the current scenario and send the status information to the power management module; The power management module is configured to pre-configure the logic of power management based on the scenario, determine the corresponding relationship between the application and the peripheral and the PNC ID in each scenario; determine the wakeable PNC ID according to the status information; initiate an application pull-up request for the application corresponding to the wakeable PNC ID, or a peripheral pull-up request for the peripheral corresponding to the wakeable PNC ID, according to the wakeable PNC ID; determine the sleepable PNC ID according to the status information; initiate an application release request for the application corresponding to the sleepable PNC ID, or a peripheral release request for the peripheral corresponding to the sleepable PNC ID, according to the sleepable PNC ID; wherein, if the PNC ID is a wakeable PNC ID, the PNC ID is 1; if the PNC ID is a sleepable PNC ID, the PNC ID is 0; The application state management module is configured to receive the application launch request, obtain the state of the corresponding application; launch the corresponding application according to the state of the corresponding application and the application launch request; or obtain the state of the corresponding application, and release the corresponding application according to the state of the corresponding application and the application release request; The peripheral driver module is configured to receive the peripheral pull-up request, obtain the state of the corresponding peripheral, and pull up the corresponding peripheral according to the state of the corresponding peripheral and the peripheral pull-up request; or obtain the state of the corresponding peripheral, and release the corresponding peripheral according to the state of the corresponding peripheral and the release request of the peripheral.

5. The vehicle-mounted HPC power management system for a centralized architecture according to claim 4, characterized in that: The local network management module is connected to the power management module via a first interface.

6. The vehicle-mounted HPC power management system for a centralized architecture according to claim 4, characterized in that: The power management module is further configured to establish a one-to-one, one-to-many or many-to-one correspondence between the application and the PNC ID; and a one-to-one, one-to-many or many-to-one correspondence between the peripheral and the PNC ID.

7. The vehicle-mounted HPC power management system for a centralized architecture according to claim 4, characterized in that: The power management module is connected to the peripheral driving module via a second interface.

8. The vehicle-mounted HPC power management system for a centralized architecture according to claim 4, characterized in that: The power management module is connected to the application status management module via a third interface.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the vehicle-mounted HPC power management method for a centralized architecture as described in any one of claims 1 to 3 are implemented.

Images