Hierarchical power management method for communication domain controllers

Abstract

This invention discloses a hierarchical power management method for communication domain controllers. The main design concept of this invention lies in differentiating different wake-up events based on business requirements and executing corresponding wake-up actions. A hierarchical power-on / off control strategy is adopted to optimize power-on / off times and effectively control overall vehicle power consumption. Specifically, different wake-up sources are detected, and different working areas are controlled in the power-on control. Software filtering is used to distinguish different business scenarios after wake-up. Furthermore, multiple power-off working areas are set up, and the power-off working area is selected for execution based on different power-on paths. This invention performs power-on / off control on different peripherals based on business scenarios, solving key problems such as high static power consumption, long power-on time, and vehicle current fluctuations and long power-off sleep times caused by abnormal scenarios in communication domain controllers after wake-up.

Description

Technical Field

[0001] This invention relates to the field of autonomous driving technology, and in particular to a hierarchical power management method for a communication domain controller. Background Technology

[0002] As the automotive industry enters the stage of fully implementing Level 2 and actively exploring Level 3 autonomous driving, the demand for cross-integration of sensors has increased significantly. Single mechatronic systems can no longer meet the needs of automotive electronics technology development, and the field of in-vehicle electronics has embarked on a path of integrated system-to-system integration. The trend of intelligent, connected, and integrated automotive electronics is unstoppable. Communication domain controllers integrating in-vehicle Ethernet gateway technology, high-precision positioning technology, V2X technology, and vehicle-to-everything (V2X) T-BOX encompass comprehensive communication and interaction functions within the vehicle, outside the vehicle, and the vehicle-to-cloud, representing the cutting-edge technology and inevitable trend in the development of vehicle communication networks.

[0003] The MCU is the core module of the communication domain controller, responsible for communication and interaction with in-vehicle nodes. The MCU connects to the CAN transceiver module, handling CAN communication with the entire vehicle and supporting CAN message wake-up functionality. The MCU connects to the Ethernet switch module; the 5G and 3A modules communicate through this switch, while other in-vehicle Ethernet nodes communicate with the communication domain controller via Ethernet. The MCU connects to the 5G module, enabling remote MCU upgrades. The MCU connects to the V2X module, reporting acquired vehicle CAN information to the V2X system. Simultaneously, the MCU manages the power supply for the entire communication domain controller, controlling the power-on and power-off of peripherals such as the CAN transceiver, Ethernet switch, 5G module, and 3A module.

[0004] The MCU needs to be equipped with power management strategies to manage the power-on and power-off of peripherals, while ensuring that the controller meets static power consumption requirements (generally less than 2mA per unit) after entering sleep mode. When the MCU is in sleep mode, it needs to power on the relevant peripherals upon receiving a valid wake-up source to fulfill functional requirements. Valid wake-up sources include IG local power wake-up, CAN message wake-up, and 5G network wake-up. However, for different wake-up sources, it is not necessary for all peripherals to be powered on. For example, in the case of remote MCU upgrades, after the 5G module receives the command, it only needs to wake up the MCU; other peripherals such as V2X modules, Ethernet switches, and CAN transceiver chips do not need to operate. Otherwise, excessive current consumption may occur during upgrades. Therefore, it is necessary to distinguish which peripherals need to be powered on based on the specific application scenario.

[0005] In existing technical solutions, power management strategies are coupled together and power management is not partitioned based on business scenarios, which has the following problems:

[0006] 1. All modules work after wake-up, resulting in high power consumption and a long power-on time after wake-up;

[0007] 2. After being woken up by unexpected CAN messages, the MCU frequently powers on and off, causing fluctuations in the vehicle's current.

[0008] 3. For occasional expected CAN message wake-up, the power-down sleep time is long. Summary of the Invention

[0009] In view of the above, the present invention aims to provide a hierarchical power management method for communication domain controllers to solve the aforementioned technical problems.

[0010] The technical solution adopted in this invention is as follows:

[0011] This invention provides a hierarchical power management method for a communication domain controller, comprising:

[0012] The wake-up source has been triggered and is valid;

[0013] Detect the wake-up source priority and set the corresponding power-on request flag according to the priority;

[0014] Before executing the corresponding power-on work area, determine whether the corresponding power-on work area identifier is valid;

[0015] If the power-on work area identifier is valid, then execute the corresponding power-on work area and determine whether the power-on work area has been executed successfully.

[0016] If a power-on timeout occurs, an exception handling mode will be triggered; if the power-on is completed, the corresponding power-off work area will be enabled.

[0017] Execute the corresponding power-down work area and determine whether the power-down work area has been completed;

[0018] If a power-down occurs after a timeout, the exception handling mode will be triggered.

[0019] In at least one of the possible implementations, the power-on working area includes: a first power-on working area corresponding to the power-on control of the Ethernet switch, a second power-on working area corresponding to the power-on control of the 5G module, and a third power-on working area corresponding to the power-on control of the V2X module.

[0020] In at least one of the possible implementations, the power-down working area includes: a first power-down working area corresponding to the power-on operation of the Ethernet switch, a second power-down working area corresponding to the power-down operation of the 5G module, a third power-down working area corresponding to the power-down operation of the V2X module, and a fourth power-down working area that triggers direct power-down and sets the MCU to enter sleep mode.

[0021] In at least one of the possible implementations, the triggering exception handling mode includes: directly switching and executing the fourth power-down working zone.

[0022] In at least one of the possible implementations, during the power-down phase, the exception handling mode further includes: if a valid wake-up time is received during the power-down process, then power-on control is restarted.

[0023] In at least one possible implementation, the control method further includes: when an unwanted message is received, performing hardware filtering without triggering the power-on process; if only an occasional desired message is received, executing the fourth power-off working area.

[0024] In at least one of the possible implementations, the priority is: IG wake-up > CAN wake-up > 5G network wake-up.

[0025] In at least one of the possible implementations, the power-on request flag is reset after a higher-priority wake-up event occurs.

[0026] The main design concept of this invention lies in differentiating different wake-up events based on business needs and executing corresponding wake-up actions. A hierarchical power-on / off control strategy is adopted to optimize power-on / off times and effectively control vehicle power consumption. Specifically, different wake-up sources are detected, and different working areas in the power-on control are controlled. Software filtering is used to distinguish different business scenarios after wake-up. Furthermore, multiple power-off working areas are set up, and the power-off working area is selected for execution based on different power-on paths. This invention provides power-on / off control for different peripherals based on business scenarios, solving key problems such as high static power consumption and long power-on time for communication domain controllers after wake-up, as well as vehicle current fluctuations and long power-off sleep times caused by abnormal scenarios. Attached Figure Description

[0027] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described below with reference to the accompanying drawings, wherein:

[0028] Figure 1 A flowchart of a hierarchical power management method for a communication domain controller provided in an embodiment of the present invention. Detailed Implementation

[0029] Embodiments of the present invention are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present invention, and should not be construed as limiting the present invention.

[0030] This invention proposes an embodiment of a hierarchical power management method for communication domain controllers, specifically, as follows: Figure 1 As shown, it includes:

[0031] Step S1: The wake-up source is triggered and valid;

[0032] Step S2: Detect the wake-up source priority and set the corresponding power-on request flag according to the priority;

[0033] Step S3: Before executing the corresponding power-on work area, determine whether the corresponding power-on work area identifier is valid;

[0034] Step S4: If the power-on work area identifier is valid, execute the corresponding power-on work area and determine whether the power-on work area has been executed.

[0035] Step S5: If a power-on timeout occurs, trigger the exception handling mode; if the power-on is completed, set the corresponding power-off working area to be valid.

[0036] Step S6: Execute the corresponding power-down work area and determine whether the power-down work area has been completed.

[0037] Step S7: If a timeout occurs and power-off occurs, the exception handling mode is triggered.

[0038] Furthermore, the power-on working area includes a first power-on working area corresponding to the power-on control of the Ethernet switch, a second power-on working area corresponding to the power-on control of the 5G module, and a third power-on working area corresponding to the power-on control of the V2X module.

[0039] Furthermore, the power-down working area includes: a first power-down working area corresponding to the power-on operation of the Ethernet switch, a second power-down working area corresponding to the power-down operation of the 5G module, a third power-down working area corresponding to the power-down operation of the V2X module, and a fourth power-down working area that triggers direct power-down (turns off the main power supply of peripherals) and sets the MCU to enter sleep mode.

[0040] Based on this, the triggering exception handling mode includes: directly switching and executing the fourth power-down working area.

[0041] Furthermore, during the power-down phase, the abnormal handling mode also includes: if a valid wake-up time is received during the power-down process, then power-on control is restarted.

[0042] Therefore, the method further includes: when receiving an unexpected message, performing hardware filtering without triggering the power-on process; if only an occasional expected message is received, executing the fourth power-off working area.

[0043] Finally, it should be noted that the priority is: IG wake-up > CAN wake-up > 5G network wake-up; based on this, when a higher priority wake-up event occurs, the power-on request flag is reset.

[0044] The foregoing embodiments can be implemented based on the following power management system architecture, which includes a wake-up source module, a wake-up source detection module, a power-on execution module, a power-off execution module, and an exception handling module.

[0045] The wake-up source module described herein may include a first wake-up source, a second wake-up source, and a third wake-up source.

[0046] The first wake-up source represents IG hard-wired wake-up. When the user presses the ignition switch to the ON position, the first wake-up source becomes effective, indicating that the user expects to use the vehicle's functions. This type has the highest priority, and in this case, all functions need to be enabled.

[0047] The second wake-up source represents CAN wake-up. After the CAN message on the bus is received by the CAN transceiver, it can be first filtered by hardware before being passed to the MCU. The MCU determines the functional module to be woken up based on the content of the CAN message. The following message example table can be used as a reference:

[0048] byte0 byte1 byte2 byte3 byte4 byte5 byte6 byte7 SA DA Wake-up parameters / / / / /

[0049] SA: Represents the source address of the wake-up message;

[0050] DA: Represents the target address of the wake-up message;

[0051] Wake-up parameters: These are enumerated to represent the wake-up event; for example, 0x00 represents a full wake-up and 0x1 represents waking up only the Ethernet switch.

[0052] Continuing from the previous text, the third wake-up source represents 5G network wake-up. The MCU and 5G module are connected via UART, and the transmission control command format is similar to CAN. This can also be achieved through enumeration; for example, 0x00 represents full wake-up, and 0x1 represents OTA upgrade wake-up (only requiring power to the 5G module).

[0053] The wake-up source detection module identifies different wake-up sources, determines their priorities, and sets different power-on request flags. The priorities are: IG wake-up > CAN wake-up > 5G network wake-up; furthermore, when a high-priority wake-up event occurs, the power-on request flag is reset.

[0054] The power-on execution module is configured with three power-on work areas. The first power-on work area controls the power-on of the Ethernet switch, the second power-on work area controls the power-on of the 5G module, and the third power-on work area controls the power-on of the V2X module. Before entering each power-on work area, the corresponding power-on work area identifier needs to be checked. Simultaneously, upon completion of power-on in that work area, a work area completion identifier is set. If the work area has not completed power-on, an exception handling procedure is invoked.

[0055] The power-down execution module is configured with four power-down working areas. The first three power-down working areas correspond to the power-on working areas and respectively execute power-down operations on the Ethernet switch, 5G module, and V2X module. A normal power-down will set the working area completion flag, and if the working area has not completed the power-down, an exception handling program will be invoked. The fourth power-down working area performs the operation of shutting down the main power supply of peripherals and setting the MCU to sleep mode.

[0056] Regarding the exception handling module, it performs exception handling for the power-on and power-off processes, including but not limited to three exception power-on handling procedures and three exception power-off handling procedures. Specifically, the exception power-on handling procedure is as follows: when a power-on timeout is detected, it directly switches to the aforementioned fourth power-off working area; the exception power-off handling procedure is as follows: on the one hand, after a power-off timeout is detected, it directly switches to the aforementioned fourth power-off working area; on the other hand, if a valid wake-up time is received during the power-off process, the power-on operation is restarted.

[0057] In particular, when an unexpected message is received, hardware filtering is performed and the power-on process is not triggered; while when only an occasional expected message is received, the fourth power-down working area is executed, triggering direct power-down.

[0058] Here, we will take the following example of upgrading the MCU of a 5G module to further describe the entire testing process:

[0059] (1) When the MCU is in sleep mode (1G is in OFF mode), the 5G module wakes up the MCU after receiving the remote upgrade command. In this scenario, you only need to power on the 5G module.

[0060] (2) After the wake-up source detection module detects a valid wake-up source, it sets the first power-on working area valid flag to invalid, the second power-on working area valid flag to valid, and the third power-on working area valid flag to invalid.

[0061] (3) The power-on execution module only executes the second power-on working area, namely the power-on of the 5G module.

[0062] (4) After power-on is completed, the second power-off working area valid flag is set to valid.

[0063] (5) After the upgrade is completed, 5G no longer needs the network and needs to perform a hibernation action, and perform the second power-down working area (fourth power-down working area) to complete the power-down action.

[0064] In summary, the main design concept of this invention lies in differentiating different wake-up events based on business needs and executing corresponding wake-up actions. A hierarchical power-on / off control strategy is adopted to optimize power-on / off times and effectively control vehicle power consumption. Specifically, different wake-up sources are detected, and different working areas in the power-on control are controlled. Software filtering is used to distinguish different business scenarios after wake-up. Furthermore, multiple power-off working areas are set up, and the power-off working area is selected for execution based on different power-on paths. This invention provides power-on / off control for different peripherals based on business scenarios, solving key problems such as high static power consumption and long power-on time for communication domain controllers after wake-up, as well as vehicle current fluctuations and long power-off sleep times caused by abnormal scenarios.

[0065] In this embodiment of the invention, "at least one" refers to one or more, and "more than one" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent the existence of A alone, A and B simultaneously, or B alone. A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects have an "or" relationship. "At least one of the following" and similar expressions refer to any combination of these items, including any combination of singular or plural items. For example, at least one of a, b, and c can represent: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, and c can be single or multiple.

[0066] The above description of the structure, features, and effects of the present invention is based on the embodiments shown in the figures. However, the above are only preferred embodiments of the present invention. It should be noted that the technical features involved in the above embodiments and their preferred methods can be reasonably combined and matched by those skilled in the art to form a variety of equivalent solutions without departing from or changing the design concept and technical effects of the present invention. Therefore, the present invention is not limited to the scope of implementation shown in the figures. Any changes made in accordance with the concept of the present invention, or modifications to equivalent embodiments, that do not exceed the spirit covered by the specification and figures, should be within the protection scope of the present invention.

Claims

1. A hierarchical power management method for a communication domain controller, the method comprising: determining a power level of the communication domain controller; and adjusting a power level of a power supply of the communication domain controller based on the determined power level of the communication domain controller. The method comprises the following steps: The wake-up source is triggered to be valid; The priority of the wake-up source is detected, and a corresponding power-on request identifier is set according to the priority; the priority is: IG wake-up > CAN wake-up > 5G network wake-up; and when a wake-up event of higher priority occurs, the power-on request identifier is reset; Before executing a corresponding power-on work area, it is judged whether a corresponding power-on work area identifier is valid, wherein the power-on work area comprises: a first power-on work area corresponding to the power-on control of the Ethernet switch, a second power-on work area corresponding to the power-on control of the 5G module, and a third power-on work area corresponding to the power-on control of the V2X module; If the power-on work area identifier is valid, the corresponding power-on work area is executed, and it is judged whether the power-on work area is executed completely; If the power-on is timed out, an abnormal processing mode is triggered; if the power-on is completed, a corresponding power-off work area is set to be valid; The corresponding power-off work area is executed, and it is judged whether the power-off work area is executed completely, wherein the power-off work area comprises: a first power-off work area corresponding to the power-on operation of the Ethernet switch, a second power-off work area corresponding to the power-off operation of the 5G module, a third power-off work area corresponding to the power-off operation of the V2X module, and a fourth power-off work area for triggering direct power-off and setting the MCU to enter the sleep mode; If the power-off is timed out, the abnormal processing mode is triggered. The method further comprises: when an unexpected packet is received, hardware filtering is executed and the power-on process is not triggered; if only an occasional frame of expected packet is received, the fourth power-off work area is executed.

2. The hierarchical power management method for a communication domain controller according to claim 1, wherein, The triggering of the abnormal processing mode comprises: directly switching and executing the fourth power-off work area.

3. The hierarchical power management method for a communication domain controller of claim 1, wherein, In the power-off stage, the triggering of the abnormal processing mode further comprises: if a valid wake-up time is received during the power-off process, the power-on control is performed again.

Images