Whole vehicle sleep wake-up control method, system and device based on gateway and vehicle

Abstract

The embodiment of the invention provides a whole vehicle sleep wake-up control method, system and device based on a gateway and a vehicle, and belongs to the technical field of vehicle control. The method comprises the steps that whole vehicle network information is acquired, network state machine configuration, an abnormal controller and a target network segment where the abnormal controller is located are determined according to the whole vehicle network information, and the whole vehicle network information comprises network state information of all electronic controllers, gateways and network segments in a whole vehicle network; determining a control strategy according to the network state machine configuration, and controlling the gateway to stop sending a network management message to a normal network segment except the target network segment according to the control strategy, so that an electronic controller in the normal network segment enters dormancy; and in response to detecting that the vehicle is powered on and started, controlling the gateway to wake up the electronic controllers in all the network segments. The embodiment of the invention aims to reduce the influence of the abnormal controller on the whole vehicle network, so that the static stoppable time and reliability of the vehicle are improved.

Description

Technical Field

[0001] This application relates to the field of vehicle control technology, and in particular to a gateway-based vehicle sleep / wake-up control method, system, device, and vehicle. Background Technology

[0002] In related technologies, as the integration of vehicle functions increases, the number of electronic controllers on board also increases. This means that more and more electronic controllers need to maintain communication when the vehicle is powered off, which leads to a larger static current and a greater drain on the vehicle's static shutdown capability. Therefore, controlling the vehicle's electronic controllers to enter sleep mode is an important operation to avoid power depletion in this scenario.

[0003] Currently, for electronic controllers that malfunction and fail to hibernate, the general approach is to force them into hibernation or force a reset, attempting to restore them to a normal state where they can enter hibernation, thus enabling the entire vehicle network to hibernate smoothly. However, this method relies on the malfunctioning electronic controller still having the ability to respond to commands, which is uncertain and makes it difficult to reduce the impact of malfunctioning electronic controllers on the vehicle.

[0004] In summary, the technical problems existing in the relevant technologies need to be improved. Summary of the Invention

[0005] The main objective of this application is to propose a gateway-based vehicle sleep / wake-up control method, system, device, and vehicle, which aims to reduce the impact of abnormal controllers on the vehicle network, thereby improving the vehicle's static shutdown time and reliability.

[0006] To achieve the above objectives, one aspect of this application proposes a gateway-based vehicle sleep / wake-up control method, the method comprising: Obtain vehicle network information, and determine network state machine configuration, abnormal controller and its target network segment based on the vehicle network information. The vehicle network information includes network status information of each electronic controller, gateway and network segment in the vehicle network. The control policy is determined based on the network state machine configuration, and the gateway is controlled to stop sending network management messages to normal network segments other than the target network segment, so that the electronic controllers in the normal network segments can enter hibernation. In response to the detection of vehicle power-on and startup, the gateway is controlled to wake up the electronic controllers in all network segments.

[0007] In some embodiments, determining a control policy based on the network state machine configuration and controlling the gateway to stop sending network management messages to normal network segments other than the target network segment according to the control policy includes: In response to the network state machine being configured for single network state machine management, the gateway is maintained in a normal working state, and the normal network segment is marked as a pseudo-dormant state; Control the gateway to stop sending network management messages to the network segment in the pseudo-dormant state.

[0008] In some embodiments, determining a control policy based on the network state machine configuration and controlling the gateway to stop sending network management messages to normal network segments other than the target network segment according to the control policy includes: In response to the network state machine being configured for multi-network state machine management, the network management message of the abnormal controller is removed from the pre-sleep condition of the gateway. The gateway enters a pre-sleep state according to the updated pre-sleep condition and stops sending the network management message to any network segment in the pre-sleep state.

[0009] In some embodiments, after removing the network management message of the abnormal controller from the pre-sleep condition of the gateway, the method further includes: Remove the network management message of the abnormal controller from the wake-up condition of the gateway.

[0010] In some embodiments, after removing the network management message of the abnormal controller from the wake-up condition of the gateway, the method further includes: The feature timer of the anomaly controller is set, and the timer of the feature timer is reset when the gateway receives a network management message sent by the anomaly controller; In response to the feature timer reaching a preset timing threshold, the network management message of the anomaly controller is re-added to the pre-sleep condition and the wake-up condition of the gateway.

[0011] In some embodiments, after the electronic controller in the normal network segment enters sleep mode, the system further includes: In response to the gateway receiving a network management message sent by the electronic controller in the normal network segment, the network state of the vehicle network is restored, and the process of obtaining vehicle network information is returned. Based on the vehicle network information, the network state machine configuration, the abnormal controller and its target network segment are determined.

[0012] In some embodiments, the network management message received by the gateway is defined as the target message, and after receiving the network management message sent by the electronic controller in the normal network segment, the method further includes: In response to the wake-up condition including the target message, the gateway is controlled to wake up the electronic controllers in all network segments.

[0013] To achieve the above objectives, another aspect of this application proposes a gateway-based vehicle sleep / wake-up control system, the system comprising: The network analysis module is used to acquire vehicle network information and determine the network state machine configuration, abnormal controllers and their target network segments based on the vehicle network information. The vehicle network information includes the network status information of each electronic controller, gateway and network segment in the vehicle network. The hibernation policy processing module is used to determine a control policy based on the network state machine configuration, and control the gateway to stop sending network management messages to normal network segments other than the target network segment according to the control policy, so that the electronic controllers in the normal network segment enter hibernation. The wake-up module is used to control the gateway to wake up the electronic controllers in all network segments in response to the detection of vehicle power-on and start-up.

[0014] To achieve the above objectives, another aspect of the embodiments of this application proposes a vehicle control device, the device including a memory and a processor, the memory storing a computer program, and the processor executing the computer program to implement the method described above.

[0015] To achieve the above objectives, another aspect of this application provides a vehicle equipped with the vehicle control device described above and implementing the method described above.

[0016] The embodiments of this application include at least the following beneficial effects: This application provides a gateway-based vehicle sleep / wake-up control method, system, device, and vehicle. This solution obtains vehicle network information, confirms the network status information of each electronic controller, gateway, and network segment in the vehicle network based on the vehicle network information, and determines the network state machine configuration, abnormal controllers that cannot normally sleep, and the target network segment where the abnormal controller is located. Based on the network state machine configuration, an applicable control strategy is determined. According to the control strategy, the gateway stops sending network management messages to normal network segments other than the target network segment, causing the electronic controllers in the normal network segments to enter sleep mode. Then, when the vehicle is detected to be powered on and started, the gateway wakes up the electronic controllers in all network segments. Compared with forcibly putting abnormal electronic controllers into sleep mode or forcibly resetting them, the method of this application does not rely on the instruction response capability of the abnormal electronic controller. Instead, it sets a corresponding control strategy based on the network state machine configuration, and controls the sleep mode of electronic controllers in normal network segments through the control strategy. This allows electronic controllers in normal network segments to still sleep mode even when abnormal controllers exist, reducing the impact of abnormal controllers on the vehicle network, thereby improving the vehicle's static shutdown time and reliability. Attached Figure Description

[0017] Figure 1This is a flowchart of a gateway-based vehicle sleep / wake-up control method provided in an embodiment of this application; Figure 2 This is a schematic diagram of the vehicle network according to an embodiment of this application; Figure 3 yes Figure 1 The flowchart of step S102 in the document; Figure 4 yes Figure 1 Another flowchart of step S102 in the process; Figure 5 This is a schematic diagram of a gateway-based vehicle sleep / wake-up control system provided in an embodiment of this application; Figure 6 This is a schematic diagram of the vehicle control device provided in the embodiments of this application. Detailed Implementation

[0018] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of this application and are not intended to limit it. In the following description, when referring to the accompanying drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with those of this application; they are merely examples of apparatuses and methods consistent with some aspects of the embodiments of this application as detailed in the appended claims.

[0019] It is understood that the terms “first,” “second,” etc., used in this application may be used herein to describe various concepts, but unless otherwise stated, these concepts are not limited by these terms. These terms are only used to distinguish one concept from another. For example, without departing from the scope of the embodiments of this application, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the words “if,” “when,” or “in response to a determination” as used herein may be interpreted as “when…” or “when…” or “in response to a determination.”

[0020] As used in this application, the terms "at least one", "multiple", "each", "any", etc., "at least one" includes one, two or more, "multiple" includes two or more, "each" refers to each of the corresponding multiples, and "any" refers to any one of the multiples.

[0021] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.

[0022] Before providing a detailed description of the embodiments of this application, some of the nouns and terms involved in the embodiments of this application will be explained first. The nouns and terms involved in the embodiments of this application are subject to the following interpretations.

[0023] 1) Electronic Control Unit (ECU) is an electronic control unit in a car. These ECUs are distributed across various modules of the car, such as the powertrain, chassis, and cabin. As a bridge between sensors and actuators, the ECU is responsible for reading, processing, and analyzing data and issuing control commands to support the functionality of various modules in the car.

[0024] 2) CAN (Controller Area Network) is a bus-type network in which electronic controllers are connected to the CAN bus and share information by transmitting messages through the CAN bus, thereby realizing data interaction between electronic controllers and between electronic controllers and gateways.

[0025] 3) Network management messages: Messages transmitted between electronic controllers and between electronic controllers and gateways include application messages and network management messages. Application messages are used to carry actual business data, such as the engine controller sending a message of the current speed to the transmission control unit. Network management messages are used to coordinate the state of network nodes, such as coordinating the electronic controller to enter sleep mode or wake up the electronic controller.

[0026] 4) Sleep state: Under the NM (Network Management) protocol, electronic controllers and gateways have multiple states, including NMStart, NMNormal, NMNormalPresleep, NMWaitBusSleep, and NMBusSleep. They can switch between these states when preset conditions are met.

[0027] NMBusSleep is the sleep state; NMNormal is the normal operating state, in which application messages and network management messages are sent and received normally; NMNormalPresleep is the pre-sleep state, in which the electronic controller itself has no need to maintain the network and will stop sending network management messages, but still needs to respond to other electronic controllers that need to maintain the network and continue to send application messages. If no network management message is received from other electronic controllers in this state after a timeout, it will enter NMWaitBusSleep to prepare for sleep; NMWaitBusSleep is the waiting-for-bus sleep state, which is used to ensure that all nodes have time to stop network activity before entering the sleep state. After entering the waiting-for-bus sleep state, the electronic controller should stop sending all messages and reset the NM data bytes.

[0028] In related technologies, as the integration of vehicle functions increases, the number of electronic controllers on board also increases. This means that more and more electronic controllers need to maintain communication when the vehicle is powered off, which leads to a larger static current and a greater drain on the vehicle's static shutdown capability. Therefore, controlling the vehicle's electronic controllers to enter sleep mode is an important operation to avoid power depletion in this scenario.

[0029] Currently, for electronic controllers that malfunction and fail to hibernate, the general approach is to force them into hibernation or force a reset, attempting to restore them to a normal state where they can enter hibernation, thus enabling the entire vehicle network to hibernate smoothly. However, this method relies on the malfunctioning electronic controller still having the ability to respond to commands, which is uncertain and makes it difficult to reduce the impact of malfunctioning electronic controllers on the vehicle.

[0030] In view of this, this application provides a gateway-based vehicle sleep / wake-up control method, system, device, and vehicle. This solution acquires vehicle network information, confirms the network status information of each electronic controller, gateway, and network segment in the vehicle network based on this information, and determines the network state machine configuration, abnormal controllers that cannot normally sleep, and the target network segment where the abnormal controller is located. Based on the network state machine configuration, an applicable control strategy is determined. According to this control strategy, the gateway stops sending network management messages to normal network segments other than the target network segment, causing the electronic controllers in the normal network segments to enter sleep mode. Then, when the vehicle is detected to be powered on and started, the gateway wakes up the electronic controllers in all network segments. Compared with forcibly putting abnormal electronic controllers into sleep mode or forcibly resetting them, this application's method does not rely on the command response capability of the abnormal electronic controller. Instead, it sets a corresponding control strategy based on the network state machine configuration, and controls the sleep mode of electronic controllers in normal network segments through the control strategy. This allows electronic controllers in normal network segments to still sleep mode even when abnormal controllers are present, reducing the impact of abnormal controllers on the vehicle network, thereby improving the vehicle's static shutdown time and reliability.

[0031] The gateway-based vehicle sleep / wake-up control method provided in this application relates to the field of vehicle control technology. This gateway-based vehicle sleep / wake-up control method can be applied to a vehicle control device, or it can be software running within the vehicle control device. The software can be an application that implements the gateway-based vehicle sleep / wake-up control method, but it is not limited to the above forms.

[0032] This application can be used in a wide variety of general-purpose or special-purpose computer system environments or configurations. It can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a specific task or implement a specific abstract data type. This application can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0033] Figure 1 This is an optional flowchart of the gateway-based vehicle sleep / wake-up control method provided in the embodiments of this application. Figure 1 The method may include, but is not limited to, steps S101 to S103.

[0034] Step S101: Obtain vehicle network information; determine network state machine configuration, abnormal controller and its target network segment based on vehicle network information; vehicle network information includes network status information of each electronic controller, gateway and network segment in the vehicle network. The various electronic controllers on the vehicle are connected to other electronic controllers and gateways via a CAN bus, thus forming a system such as... Figure 2 The vehicle network is shown. Figure 2 The network shown includes a first network segment consisting of a first electronic controller and a second electronic controller, and a second network segment consisting of a third electronic controller and a fourth electronic controller. Both the first and second network segments are connected to the gateway via a CAN bus. On the gateway side, each CAN bus is connected to a port on the gateway and is divided into different network segments according to different ports. Each port corresponds to several electronic controllers in the same network segment. In addition, a network state machine is configured on the gateway to manage the entire vehicle network from a software perspective.

[0035] First, it should be noted that the implementation of this embodiment presupposes a scenario where the vehicle is powered off and the entire vehicle network needs to enter sleep mode. By analyzing the vehicle network information, abnormal electronic controllers within the vehicle network can be located and defined as abnormal controllers. The network segment where the abnormal controller resides is defined as the target network segment. One characteristic of abnormal controllers is that they continuously send network management messages while in normal working condition, without entering sleep mode. In typical scenarios, these network management messages will keep other electronic controllers in the same network segment in a pre-sleep state, while the gateway remains in normal working condition. This will also affect electronic controllers in other normal network segments, ultimately preventing the entire vehicle network from successfully entering sleep mode.

[0036] Step S102: Determine the control policy according to the network state machine configuration, and control the gateway to stop sending network management messages to normal network segments outside the target network segment according to the control policy, so that the electronic controllers in the normal network segments can enter hibernation. For different vehicle networks, the configuration of the network state machine may vary, such as single network state machine management or multiple network state machine management. Based on these differences, different control strategies can be set to better adapt to the conditions provided by the corresponding network state machine configuration, thereby improving the processing efficiency of the solution.

[0037] These control strategies all revolve around the same objective: to control the gateway to stop sending network management messages to network segments other than the target network segment, i.e., normal network segments. For the target network segment, because the malfunctioning controller continues to send network management messages, other electronic controllers in the target network segment can only remain in a pre-sleep state. However, for normal network segments, when the gateway stops sending network management messages, the electronic controllers there will time out while waiting for network management messages, entering a bus-waiting sleep state from the pre-sleep state, and eventually achieving sleep. In this way, electronic controllers in normal network segments can still enter sleep mode even in the presence of a malfunctioning controller, reducing the impact of the malfunctioning controller on the overall vehicle network.

[0038] refer to Figure 3 In some embodiments, step S102 may include, but is not limited to: Step S201: In response to the network state machine being configured for single network state machine management, maintain the gateway in a normal working state; Step S202: Control the gateway to stop sending network management messages to normal network segments and mark normal network segments as pseudo-dormant state.

[0039] When the network state machine is configured for single network state machine management, the gateway controls the sending and receiving of network management messages on all ports (and network segments) simultaneously using the same set of policies. For this purpose, a separate control policy is set for the normal network segments.

[0040] Under the control strategy of this embodiment, the gateway maintains a normal operating state, i.e., normally sending and receiving network management messages and application messages. For the target network segment, the abnormal controller continuously sends network management messages, and the gateway also continues to send network management messages to the target network segment, marking the target network segment as an abnormal sleep state. For the normal network segment, the control strategy controls the gateway to stop sending network management messages to the normal network segment. After stopping the sending of network management messages, a first timer begins. When the first timer expires, the sending of application messages also stops. The first timer timeout standard is set to, for example, 1 second or 1.2 seconds. Ultimately, the gateway stops sending all messages to the normal network segment, marking the normal network segment as a pseudo-sleep state. In this way, the electronic controller in the normal network segment will no longer receive network management messages to maintain the network from the gateway, realizing the transition from the pre-sleep state to the waiting bus sleep state, and finally to the sleep state.

[0041] By specifically controlling the gateway to stop sending network management messages to normal network segments during single network state machine management, the electronic controllers in normal network segments can still go into hibernation even in the presence of abnormal controllers, thus reducing the impact of abnormal controllers on the vehicle network.

[0042] refer to Figure 4 In some embodiments, step S102 may include, but is not limited to: In step S301, in response to the network state machine being configured for multi-network state machine management, the network management message of the abnormal controller is removed from the pre-sleep condition of the gateway. The gateway enters the pre-sleep state according to the updated pre-sleep condition and stops sending network management messages to any network segment in the pre-sleep state.

[0043] When the network state machine is configured for multi-network state machine management, it is equivalent to assigning a separate network state machine to each bus, allowing the gateway to control the sending and receiving of network management messages on each bus. This differs from the single-network state machine management described in the previous embodiment. Setting separate sending and receiving strategies for normal network segments requires editing each network state machine, which is cumbersome. In this case, it is more suitable to utilize the conditions provided by multi-network state machine management to set another control strategy.

[0044] Under the control strategy of this embodiment, the gateway removes the network management messages of the abnormal controller from its pre-sleep condition. Even if the abnormal controller continues to send network management messages, it does not affect the gateway's entry into the pre-sleep state. After all ports of the gateway enter the pre-sleep state, for the target network segment, since the abnormal controller continues to send network management messages, other electronic controllers and corresponding ports in the target network segment remain in the pre-sleep state. For the normal network segment, according to the design that network management messages will be stopped in the pre-sleep state, the gateway in the pre-sleep state stops sending network management messages to any network segment, including the normal network segment. After stopping the sending of network management messages, the first timer begins. When the first timer expires, the sending of application messages stops, ultimately achieving the goal of the gateway stopping sending all messages to the normal network segment, and the electronic controllers in the normal network segment can enter the sleep state normally.

[0045] By adjusting the pre-sleep conditions of the gateway during multi-network state machine management, the gateway can stop sending network management messages to the normal network segment according to the design of the pre-sleep conditions, thereby reducing the implementation cost of the solution. Ultimately, it also enables the electronic controller in the normal network segment to still go into sleep mode in the presence of an abnormal controller, reducing the impact of the abnormal controller on the entire vehicle network.

[0046] In some embodiments, after removing the network management message of the abnormal controller from the pre-sleep condition of the gateway in step S301, the method further includes: Remove the network management message of the abnormal controller from the wake-up condition of the gateway.

[0047] Specifically, the gateway is also set with wake-up conditions. In general, these wake-up conditions are associated with a preset CAN port. When the gateway receives a network management message within the set ID range on the preset CAN port (without distinguishing which electronic controller in the corresponding network segment sent it), it determines that the wake-up condition is met and then wakes up the entire vehicle network, that is, wakes up the electronic controllers in all network segments.

[0048] Even if the network management message of the malfunctioning controller is removed from the gateway's pre-sleep condition, it may still be a wake-up condition for the gateway, thus affecting the entire vehicle network. Therefore, it is first determined whether the network management message of the malfunctioning controller is a wake-up condition for the gateway. If so, the network management message is removed from the gateway's wake-up condition; otherwise, no action is taken. This prevents the network management message of the malfunctioning controller from waking up normal network segments that are already in sleep mode, improving the stability of the vehicle network's sleep control.

[0049] In some embodiments, after removing the network management message of the abnormal controller from the wake-up condition of the gateway, the method further includes: Configure a feature timer for the anomaly controller. The feature timer is reset when the gateway receives a network management message from the anomaly controller. In response to the feature timer reaching a preset timing threshold, the network management message of the abnormal controller is re-added to the gateway's pre-sleep and wake-up conditions.

[0050] After putting the electronic controllers on the normal network segment into sleep mode, the status of abnormal controllers is monitored by setting a characteristic timer. Specifically, the characteristic timer is reset when the gateway receives a network management message from the abnormal controller. Therefore, as long as the abnormal controller remains abnormal and continues to send network management messages, the characteristic timer will continuously reset based on the interval between these message transmissions. A preset timing threshold, such as 1 second or 1.2 seconds, is set, which is greater than the interval between network management message transmissions by the abnormal controller. When the characteristic timer reaches the preset threshold, it indicates that the abnormal controller has stopped sending network management messages and may have recovered due to external factors. In this case, its network management messages are re-added to the gateway's pre-sleep and wake-up conditions; if its network management messages were not originally subject to the wake-up condition, only the pre-sleep condition is re-added. After restoration, the original abnormal controller that has recovered can also enter sleep mode normally.

[0051] In other embodiments, a feature timer can also be set for the abnormal controller in a single network state machine management scenario, and the timing of the feature timer can also be checked to see if it reaches a preset timing threshold. When the feature timer reaches the preset timing threshold, the abnormal sleep state flag of the target network segment is restored, and the original abnormal controller that has returned to normal will stop sending network management messages. Based on this, the gateway can also switch from the normal working state to the pre-sleep state, thereby stopping the sending of network management messages to the target network segment, and finally causing the original abnormal controller to also enter sleep mode.

[0052] By monitoring the status of the abnormal controller through the timing of the feature timer, the network status of the whole vehicle network can be restored in a timely manner when the abnormal controller recovers to normal. It also makes it easier for the abnormal controller to enter sleep mode like a normal electronic controller after it recovers to normal, thereby improving the stability of the whole vehicle network.

[0053] In step S103, in response to detecting that the vehicle is powered on and started, the control gateway wakes up the electronic controllers in all network segments.

[0054] Specifically, the vehicle IG ON (Ignition On) scenario refers to the vehicle's ignition switch being powered on. At this time, the vehicle's electronic systems are fully activated, but the engine has not yet started. This scenario typically occurs during the preparation phase before vehicle startup. Therefore, when vehicle IG ON is detected, it also means that the entire vehicle network needs to be woken up. The control gateway wakes up the electronic controllers in all network segments to support the startup of various modules on the vehicle.

[0055] In some embodiments, after the electronic controller in the normal network segment enters sleep mode, the system further includes: In response to the gateway receiving a network management message sent by an electronic controller in a normal network segment, the network state of the entire vehicle network is restored, and the process returns to obtain the vehicle network information. Based on the vehicle network information, the network state machine configuration, the abnormal controller, and its target network segment are determined.

[0056] After an electronic controller in a normal network segment enters sleep mode, the gateway may still receive network management messages sent by these electronic controllers. This indicates that an electronic controller in the normal network segment has switched from sleep mode back to normal operation mode. The reason may be that the electronic controller has become an abnormal controller, or the user operates the vehicle and wakes up the corresponding electronic controller based on the function-driven needs, which is a normal operating condition.

[0057] Regardless of the cause, the method of this application embodiment must be re-executed. First, restore the network state of the vehicle network. For example, if the network state machine is configured for multi-network state machine management, the network management message of the abnormal controller is re-added to the pre-sleep condition and wake-up condition of the gateway. If the network management message is not a wake-up condition, only the pre-sleep condition is re-added. Then, steps S101 to S102 are re-executed. If the electronic controller in the normal network segment becomes an abnormal controller, the abnormal controller and the target network segment can be updated through step S101, and then the electronic controller in the normal network segment can be re-controlled to sleep through step S102.

[0058] By responding to network management messages from the electronic controllers of normal network segments, the vehicle network can be woken up from its dormant state, thereby improving the stability of the vehicle network operation.

[0059] In some embodiments, after receiving the network management message sent by the electronic controller in the normal network segment, the method further includes: In response to wake-up conditions including target messages, the control gateway wakes up electronic controllers in all network segments.

[0060] For ease of explanation, the network management message received by the gateway in the above embodiment is defined as the target message. For this target message, another possibility is that the message falls under the gateway's wake-up condition. If it is determined that the target message falls under the gateway's wake-up condition, this is equivalent to waking up the entire vehicle network under normal operating conditions. Therefore, in addition to restoring the network state and returning to step S101 as described in the above embodiment, it is also necessary to control the gateway to wake up the electronic controllers in all network segments, just as when the vehicle is powered on and the entire vehicle network is woken up.

[0061] By determining whether the target message meets the wake-up condition, the vehicle network can be woken up by the target message under normal operating conditions after being put into hibernation by the method of this embodiment, thereby improving the stability of the vehicle network operation.

[0062] Steps S101 to S103 as shown in the embodiments of this application are implemented by setting corresponding control strategies according to the configuration of the network state machine. The control strategies are used to control the electronic controllers in the normal network segment to go into sleep mode, so that the electronic controllers in the normal network segment can still go into sleep mode in the presence of abnormal controllers, thereby reducing the impact of abnormal controllers on the vehicle network and improving the vehicle's static shutdown time and reliability.

[0063] The following is a detailed description and explanation of the solutions in the embodiments of the present invention, using specific application examples: This application provides a gateway-based vehicle sleep / wake-up control method. This method is applied to vehicles to control the sleep and wake-up of the vehicle's network. First, the vehicle network information is acquired. Based on this information, the network status information of each electronic controller, gateway, and network segment in the vehicle network is determined. The network state machine configuration, abnormal controllers that are not in sleep mode, and their target network segments are also identified.

[0064] The corresponding control strategy is determined based on the network state machine configuration. Specifically, when the network state machine is configured for single-network state machine management, the gateway is maintained in normal working state, the gateway is controlled to stop sending network management messages to normal network segments, and the normal network segments are marked as pseudo-sleep state. When the network state machine is configured for multi-network state machine management, the network management messages of the abnormal controller are removed from the gateway's pre-sleep conditions and also removed from the gateway's wake-up conditions. The gateway enters a pre-sleep state according to the updated pre-sleep conditions and stops sending network management messages to any network segment in the pre-sleep state. Through the above two control strategies, the gateway stops sending network management messages to normal network segments other than the target network segment, thereby causing the electronic controllers in the normal network segments to enter sleep mode. In addition, for the abnormal controller, a characteristic timer for the abnormal controller is set. The timer is reset when the gateway receives a network management message sent by the abnormal controller. When the timer reaches a preset time threshold, the network management message of the abnormal controller is re-added to the gateway's pre-sleep and wake-up conditions.

[0065] After the vehicle network goes into sleep mode, when the vehicle is detected to be powered on and started, the control gateway wakes up the electronic controllers in all network segments. Furthermore, when the gateway receives a network management message (defined as a target message) from an electronic controller in a normal network segment, it can restore the network state of the entire vehicle network and return to the steps of obtaining vehicle network information and determining the network state machine configuration, the abnormal controller, and its target network segment based on the vehicle network information. If the wake-up condition includes a target message, the control gateway must also wake up the electronic controllers in all network segments.

[0066] This application embodiment sets a corresponding control strategy according to the configuration of the network state machine. The control strategy controls the electronic controller in the normal network segment to hibernate, so that the electronic controller in the normal network segment can still hibernate in the presence of abnormal controllers, thereby reducing the impact of abnormal controllers on the vehicle network and improving the vehicle's static shutdown time and reliability.

[0067] Please see Figure 5 This application also provides a gateway-based vehicle sleep / wake-up control system that can implement the above-mentioned method. The system includes: The network analysis module is used to obtain vehicle network information and determine the network state machine configuration, abnormal controllers and their target network segments based on the vehicle network information. The vehicle network information includes the network status information of each electronic controller, gateway and network segment in the vehicle network. The hibernation policy processing module is used to determine the control policy based on the network state machine configuration, and control the gateway to stop sending network management messages to normal network segments outside the target network segment according to the control policy, so that the electronic controllers in the normal network segment can enter hibernation. The wake-up module is used to wake up the electronic controllers in all network segments in response to the detection of vehicle power-on and start-up.

[0068] It is understood that the content of the above method embodiments is applicable to this system embodiment. The specific functions implemented in this system embodiment are the same as those in the above method embodiments, and the beneficial effects achieved are also the same as those achieved in the above method embodiments.

[0069] Reference Figure 6 The present invention also provides a vehicle control device, including a memory, a processor, and a program stored in the memory and executable on the processor. When the program is executed by the processor, it implements the gateway-based vehicle sleep-wake control method described in the above embodiments.

[0070] Memory, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs and non-transitory computer-executable programs. Furthermore, memory may include high-speed random access memory, and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, memory may optionally include memory remotely located relative to a control processor, and these remote memories can be connected to the control device via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0071] The non-transient software program and instructions required to implement the control method of the above embodiments are stored in memory. When executed by a processor, the control method of the above embodiments is executed. For example, executing... Figure 1 The method steps S101 to S103 are described above. It is understood that the content of the above method embodiments is applicable to this device, and the specific functions implemented in this device embodiment are the same as those in the above method embodiments, and the beneficial effects achieved are also the same as those achieved in the above method embodiments.

[0072] This invention also provides a vehicle, including the vehicle control device described in the above embodiments.

[0073] The vehicle can be a private car, such as a sedan, SUV, MPV, or pickup truck. It can also be a commercial vehicle, such as a van, bus, small truck, or large semi-trailer. The vehicle must have an electric motor capable of outputting power or acting as a generator to store mechanical energy. When the vehicle is a new energy vehicle, it can be a hybrid or a pure electric vehicle.

[0074] Since the vehicle applies all the technical solutions of the above-described system or vehicle control device, it has at least all the beneficial effects brought about by the technical solutions of the above embodiments, which will not be repeated here.

[0075] This application provides a gateway-based vehicle sleep / wake-up control method, system, device, and vehicle. This solution acquires vehicle network information, confirms the network status information of each electronic controller, gateway, and network segment in the vehicle network based on this information, and determines the network state machine configuration, abnormal controllers that cannot normally sleep, and the target network segment where the abnormal controller is located. Based on the network state machine configuration, an applicable control strategy is determined. According to this control strategy, the gateway stops sending network management messages to normal network segments other than the target network segment, causing the electronic controllers in the normal network segments to enter sleep mode. Then, when the vehicle is detected to be powered on and started, the gateway wakes up the electronic controllers in all network segments. Compared to forcibly putting abnormal electronic controllers into sleep mode or forcibly resetting them, this application's method does not rely on the command response capability of abnormal electronic controllers. Instead, it sets a corresponding control strategy based on the network state machine configuration, and controls the sleep mode of electronic controllers in normal network segments through the control strategy. This allows electronic controllers in normal network segments to still sleep mode even when abnormal controllers are present, reducing the impact of abnormal controllers on the vehicle network, thereby improving the vehicle's static shutdown time and reliability.

[0076] The embodiments described in this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided by the embodiments of this application. As those skilled in the art will know, with the evolution of technology and the emergence of new application scenarios, the technical solutions provided by the embodiments of this application are also applicable to similar technical problems.

[0077] Those skilled in the art will understand that the technical solutions shown in the figures do not constitute a limitation on the embodiments of this application, and may include more or fewer steps than shown, or combine certain steps, or different steps.

[0078] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0079] Those skilled in the art will understand that all or some of the steps in the methods disclosed above, as well as the functional modules / units in the systems and devices, can be implemented as software, firmware, hardware, or suitable combinations thereof.

[0080] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0081] It should be understood that in this application, "at least one (item)" means one or more, and "more than" means two or more. "And / or" is used to describe the relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can represent three cases: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or 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.

[0082] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of the units described above is only a logical functional division, and 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 through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0083] The units described above 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.

[0084] Furthermore, 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. The integrated unit can be implemented in hardware or as a software functional unit.

[0085] If the integrated unit 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 all or 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 multiple 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 programs, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0086] The preferred embodiments of the present application have been described above with reference to the accompanying drawings, but this does not limit the scope of the claims of the present application. Any modifications, equivalent substitutions, and improvements made by those skilled in the art without departing from the scope and substance of the embodiments of the present application shall be within the scope of the claims of the present application.

Claims

1. A gateway-based whole vehicle hibernation wake-up control method, characterized by, The method comprises the following steps: Obtaining vehicle network information, determining network state machine configuration, abnormal controller and target network segment where the abnormal controller is located according to the vehicle network information, wherein the vehicle network information comprises network state information of each electronic controller, gateway and network segment in the vehicle network; Determining control strategy according to the network state machine configuration, and controlling the gateway to stop sending network management messages to normal network segments outside the target network segment according to the control strategy, so that the electronic controllers in the normal network segments enter sleep; In response to detecting vehicle power-on start, controlling the gateway to wake up the electronic controllers in all network segments.

2. The method of claim 1, wherein, The step of determining control strategy according to the network state machine configuration, and controlling the gateway to stop sending network management messages to normal network segments outside the target network segment according to the control strategy comprises: In response to the network state machine configuration being single network state machine management, maintaining the gateway in normal working state; Controlling the gateway to stop sending the network management messages to the normal network segments, and marking the normal network segments as pseudo-sleep state.

3. The method of claim 1, wherein, The step of determining control strategy according to the network state machine configuration, and controlling the gateway to stop sending network management messages to normal network segments outside the target network segment according to the control strategy comprises: In response to the network state machine configuration being multi-network state machine management, removing the network management messages of the abnormal controller from the pre-sleep condition of the gateway, and the gateway entering pre-sleep state according to the updated pre-sleep condition, and stopping sending the network management messages to any network segment in the pre-sleep state.

4. The method of claim 3, wherein, After removing the network management messages of the abnormal controller from the pre-sleep condition of the gateway, the method further comprises: Removing the network management messages of the abnormal controller from the wake-up condition of the gateway.

5. The method of claim 4, wherein, After removing the network management messages of the abnormal controller from the wake-up condition of the gateway, the method further comprises: Setting a feature timer of the abnormal controller, wherein the timing of the feature timer is reset when the gateway receives the network management messages sent by the abnormal controller; In response to the timing of the feature timer reaching a preset timing threshold, re-adding the network management messages of the abnormal controller to the pre-sleep condition and the wake-up condition of the gateway.

6. The method according to any one of claims 1 to 5, characterized in that, After the electronic controllers in the normal network segments enter sleep, the method further comprises: In response to the gateway receiving the network management messages sent by the electronic controllers in the normal network segments, restoring the network state of the vehicle network, and returning to execute the steps of obtaining vehicle network information, determining network state machine configuration, abnormal controller and target network segment where the abnormal controller is located according to the vehicle network information.

7. The method of claim 6, wherein, Defining the network management messages received by the gateway as target messages, after receiving the network management messages sent by the electronic controllers in the normal network segments, the method further comprises: In response to the wake-up condition including the target messages, controlling the gateway to wake up the electronic controllers in all network segments.

8. A gateway-based whole vehicle hibernation wake-up control system, characterized by, The system comprises: The network analysis module is configured to acquire whole vehicle network information, determine a network state machine configuration, an abnormal controller and a target network segment where the abnormal controller is located according to the whole vehicle network information, and the whole vehicle network information comprises network state information of each electronic controller, gateway and network segment in the whole vehicle network. The hibernation strategy processing module is configured to determine a control strategy according to the network state machine configuration, and control the gateway to stop sending network management messages to normal network segments other than the target network segment according to the control strategy, so that the electronic controllers in the normal network segments enter hibernation. The wake-up module is configured to control the gateway to wake up the electronic controllers in all network segments in response to detecting that the vehicle is powered on.

9. A vehicle control device characterized by comprising: The device comprises a memory and a processor, the memory stores a computer program, and the processor implements the method in any one of claims 1 to 7 when executing the computer program.

10. A vehicle characterized by comprising: The vehicle is configured with the vehicle control device in claim 9.

Images