Network management method and device for vehicle-mounted electronic control unit and control unit

Abstract

The application discloses a network management method and device of a vehicle-mounted electronic control unit and the control unit. The network management method comprises the following steps: when the current vehicle-mounted ECU is switched from the bus sleep mode to the network mode, starting the repeated message state; determining the target associated ECU; when the current vehicle-mounted ECU is switched from the network mode to the normal working state and a network release signal is received, or when the repeated message timer of the current vehicle-mounted ECU is timed out and a network release signal is received, starting the message waiting state; when the message waiting timer of the current vehicle-mounted ECU is timed out and in the message waiting state, no message sent by the target associated ECU is received, but a network release signal is received, entering the preparation sleep state; after the current vehicle-mounted ECU enters the preparation sleep state, determining the target switch-in state and switching into the target switch-in state. The technical scheme of the embodiment of the application can avoid missing important messages to the maximum extent under the condition that the system allows.

Description

Technical Field

[0001] This invention relates to the field of automotive electronics technology, and in particular to a network management method, device, and control unit for an in-vehicle electronic control unit. Background Technology

[0002] In recent years, the automotive industry has gradually evolved towards intelligent connectivity, and consumer demands for vehicle functions have become increasingly complex, leading to a rise in the number of onboard ECUs (Electronic Control Units). While this enables more intelligent services, it also brings about increased power consumption. Therefore, network management, ECU sleep and wake-up mechanisms, and power reduction have become particularly important.

[0003] Currently, the on-board ECUs in vehicles enter a sleep state at the same time. In this case, it is difficult to guarantee the working requirements of some important ECU nodes. Moreover, the network management state used by the ECU does not determine important messages when waking up or putting the ECU into sleep. This will cause important messages to be missed because the sleep time is too short. Summary of the Invention

[0004] This invention provides a network management method, device, and control unit for vehicle electronic control units (ECUs) to solve the problems of missing important message determination and loss of important messages in vehicle ECUs.

[0005] According to one aspect of the present invention, a network management method for an on-board electronic control unit is provided, comprising:

[0006] When the current vehicle ECU switches from bus sleep mode to network mode, the repeat message state is enabled and the repeat message timer is started.

[0007] Based on the associated node messages obtained from the duplicate message status, determine the target associated ECU;

[0008] When the current vehicle ECU switches from network mode to normal operation and receives a network release signal, or when the current vehicle ECU's repeat message timer expires and a network release signal is received, the message waiting state for the target associated ECU is enabled, and the message waiting timer is started.

[0009] If the message waiting timer of the current vehicle ECU expires and no message is received from the target associated ECU while in the message waiting state, but a network release signal is received, then it enters the preparation sleep state.

[0010] After the current vehicle ECU enters the sleep preparation state, the target transition state is determined based on the network manager timer duration, the bus sleep timer duration, and the data reception behavior, or only based on the data reception behavior, and then the target transition state is entered.

[0011] According to another aspect of the present invention, a network management device for an on-board electronic control unit is provided, comprising:

[0012] The repeated message state enabling module is used to enable the repeated message state and start the repeated message timer when the current vehicle ECU switches from bus sleep mode to network mode.

[0013] The target associated ECU determination module is used to determine the target associated ECU based on the associated node messages obtained from the duplicate message status.

[0014] The message waiting state activation module is used to enable the message waiting state for the target associated ECU and start the message waiting timer when the current vehicle ECU switches from network mode to normal working state and receives a network release signal, or when the current vehicle ECU's repeat message timer expires and receives a network release signal.

[0015] The sleep state preparation module is used to enter the sleep state if the message waiting timer of the current vehicle ECU expires and no message is received from the target associated ECU during the message waiting state, but a network release signal is received.

[0016] The target transition state determination module is used to determine the target transition state and transition to the target transition state after the current vehicle ECU enters the preparation hibernation state, based on the network manager timer duration, bus hibernation timer duration, and data reception behavior, or only based on data reception behavior.

[0017] According to another aspect of the present invention, an in-vehicle electronic control unit is provided, the in-vehicle electronic control unit comprising:

[0018] At least one processor; and

[0019] A memory communicatively connected to the at least one processor; wherein,

[0020] The memory stores a computer program that can be executed by the at least one processor, which enables the at least one processor to perform the network management method of the vehicle electronic control unit according to any embodiment of the present invention.

[0021] According to another aspect of the present invention, a computer-readable storage medium is provided, the computer-readable storage medium storing computer instructions, the computer instructions being configured to cause a processor to execute and implement the network management method of the vehicle electronic control unit according to any embodiment of the present invention.

[0022] The technical solution of this invention involves enabling a repeat message state and starting a repeat message timer when the current vehicle ECU transitions from bus sleep mode to network mode. Based on the associated node messages obtained in the repeat message state, the target associated ECU is determined. Then, when the current vehicle ECU transitions from network mode to normal operation and receives a network release signal, or when the repeat message timer of the current vehicle ECU times out and a network release signal is received, a message waiting state for the target associated ECU is initiated, and a message waiting timer is started. Further, if the message waiting timer of the current vehicle ECU times out and no message is received from the target associated ECU during the message waiting state, but a network release signal is received, the ECU enters a sleep preparation state. After the current vehicle ECU enters the sleep preparation state, the target transition state is determined based on the network manager timing duration, the bus sleep timing duration, and data reception behavior, or only based on data reception behavior, and the ECU transitions to the target transition state. In this solution, the target associated ECU that frequently sends messages to the current vehicle ECU can be identified, and the messages sent by the target associated ECU are regarded as important messages. By setting a message waiting state, the vehicle ECU can be prevented from switching directly from the current normal working state or the repeated message state to the sleep state. Time is reserved for the current vehicle ECU to receive important messages (which can be set according to the needs of the vehicle system). This solves the problem of the vehicle ECU lacking important message identification and the loss of important messages. It can minimize the loss of important messages when the system allows.

[0023] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0024] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0025] Figure 1 A flowchart illustrating a network management method for an in-vehicle electronic control unit provided in Embodiment 1 of the present invention;

[0026] Figure 2 A flowchart illustrating a network management method for an in-vehicle electronic control unit provided in Embodiment 2 of the present invention;

[0027] Figure 3 This is a schematic diagram of a network management process provided according to Embodiment 2 of the present invention;

[0028] Figure 4 This is a schematic diagram of the network management device for an in-vehicle electronic control unit provided in Embodiment 3 of the present invention;

[0029] Figure 5 A schematic diagram of the structure of an on-board electronic control unit that can be used to implement an embodiment of the present invention is shown. Detailed Implementation

[0030] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0031] It should be noted that the terms "target," etc., in the specification, claims, and accompanying drawings of this invention 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 embodiments of the invention 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 a 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.

[0032] Example 1

[0033] Figure 1 This is a flowchart of a network management method for an in-vehicle electronic control unit (ECU) according to Embodiment 1 of the present invention. This embodiment is applicable to situations where the in-vehicle ECU misses important messages. This method can be executed by a network management device for the ECU, which can be implemented in hardware and / or software and can be configured within the ECU. Figure 1 As shown, the method includes:

[0034] S110. When the current vehicle ECU switches from bus sleep mode to network mode, enable the repeat message state and start the repeat message timer.

[0035] Among them, bus sleep mode can be a sleep mode for the vehicle ECU, where the bus communication wake-up mechanism is activated, and power consumption is in a power-saving state under sleep mode. Network mode can be a state in which the bus network is activated, and the vehicle ECU has the ability to receive and send messages on the bus. Repeat message state can be a sub-state of network mode, in which the vehicle ECU in the vehicle system periodically sends network management messages. Repeat message timer can be a timer that operates when repeat message state is enabled and does not operate when non-repeating message state is enabled.

[0036] Specifically, after the vehicle system powers on and the vehicle ECU completes initialization, the current vehicle ECU will enter bus sleep mode. When the current vehicle ECU meets the state switching conditions for transitioning from bus sleep mode to network mode, the current vehicle ECU will enter network mode, thereby enabling the repeat message state by default and simultaneously starting the repeat message timer.

[0037] S120. Determine the target associated ECU based on the associated node messages obtained from the duplicate message status.

[0038] The associated node message can be a message sent by an associated on-board ECU that the current on-board ECU obtains during the process of enabling repeated message sending. The target associated ECU can be an on-board ECU that sends messages to the current on-board ECU at a frequency that reaches a preset threshold.

[0039] In this embodiment of the invention, the current vehicle ECU can record the associated node messages obtained in the current repeated message state, and then designate the vehicle ECU that sends messages to the current vehicle ECU at a frequency that reaches a preset threshold as the target associated ECU.

[0040] S130. When the current vehicle ECU switches from network mode to normal operation and receives a network release signal, or when the current vehicle ECU's repeat message timer expires and a network release signal is received, the message waiting state for the target associated ECU is enabled, and the message waiting timer is started.

[0041] The normal operating state refers to a state where the network is active and communication between vehicle ECUs is normal, provided a network request is received. The network release signal indicates that a network release is required. The message waiting state is a state before the vehicle ECU prepares to sleep, used to receive important messages from the target associated ECU. The message waiting timer is a timer that operates when the message waiting state is active and does not operate when the message waiting state is not active.

[0042] In this embodiment of the invention, if the current vehicle ECU switches from network mode to normal working state and receives a network release signal, a message waiting state is enabled to wait for a message sent by the target associated ECU, and a message waiting timer is started; if the current vehicle ECU's repeated message timer times out and a network release signal is received, a message waiting state for the target associated ECU is enabled, and a message waiting timer is started.

[0043] S140. If the message waiting timer of the current vehicle ECU expires and no message is received from the target associated ECU while in the message waiting state, but a network release signal is received, then the vehicle enters the preparation hibernation state.

[0044] The "preparing to hibernate" state can be the previous state before entering the pre-hibernation state if no messages or network requests are received within a preset waiting sleep period.

[0045] In this embodiment of the invention, the message sent by the target associated ECU can be regarded as an important message of the current vehicle ECU. If the message waiting timer of the current vehicle ECU in the message waiting state times out, and no message sent by the target associated ECU is received during the message waiting state, but a network release signal is received, then the ECU enters the preparation sleep state. That is, if no important message and network release signal are received within a certain reserved time, the ECU can enter the preparation sleep state.

[0046] S150: After the current vehicle ECU enters the preparation hibernation state, determine the target transition state based on the network manager timer duration, the bus hibernation timer duration, and the data receiving behavior, or only based on the data receiving behavior, and then transition to the target transition state.

[0047] The target transition state can be the next stage the current vehicle ECU needs to transition to after entering the sleep preparation state. The network manager timer duration can be the timer duration set for the network management timer. The bus sleep timer duration can be the timer duration set for the bus sleep waiting timer. The network management timer can be a timer that starts working after the vehicle ECU enters the sleep preparation state and does not work in non-sleep preparation states. The bus sleep waiting timer can be a timer that starts working after the vehicle ECU enters the bus pre-sleep state and does not work in non-bus pre-sleep states.

[0048] Correspondingly, if the current vehicle ECU enters a sleep preparation state, a network management timer is activated. If the network management timer does not expire and the current vehicle ECU is receiving data, the target transition state can be determined based on the type of data received, and the ECU will then transition to the target transition state. If the network management timer expires, a bus sleep timer is activated, and the target transition state is determined based on the bus sleep timer duration and the data receiving behavior, and the ECU then transitions to the target transition state.

[0049] The technical solution of this invention involves enabling a repeat message state and starting a repeat message timer when the current vehicle ECU transitions from bus sleep mode to network mode. Based on the associated node messages obtained in the repeat message state, the target associated ECU is determined. Then, when the current vehicle ECU transitions from network mode to normal operation and receives a network release signal, or when the repeat message timer of the current vehicle ECU times out and a network release signal is received, a message waiting state for the target associated ECU is initiated, and a message waiting timer is started. Further, if the message waiting timer of the current vehicle ECU times out and no message is received from the target associated ECU during the message waiting state, but a network release signal is received, the ECU enters a sleep preparation state. After the current vehicle ECU enters the sleep preparation state, the target transition state is determined based on the network manager timing duration, the bus sleep timing duration, and data reception behavior, or only based on data reception behavior, and the ECU transitions to the target transition state. In this solution, the target associated ECU that frequently sends messages to the current vehicle ECU can be identified, and the messages sent by the target associated ECU are regarded as important messages. By setting a message waiting state, the vehicle ECU can be prevented from switching directly from the current normal working state or the repeated message state to the sleep state. Time is reserved for the current vehicle ECU to receive important messages (which can be set according to the needs of the vehicle system). This solves the problem of the vehicle ECU lacking important message identification and the loss of important messages. It can minimize the loss of important messages when the system allows.

[0050] Example 2

[0051] Figure 2 This is a flowchart of a network management method for an in-vehicle electronic control unit provided in Embodiment 2 of the present invention. This embodiment is based on the above embodiment and is further specified, providing specific optional implementation methods for determining the target associated ECU based on the associated node messages obtained from the duplicate message status. Figure 2 As shown, the method includes:

[0052] S210. When the current ECU switches from bus sleep mode to network mode, enable the repeat message state and start the repeat message timer.

[0053] In an optional embodiment of the present invention, the current vehicle electronic control unit (ECU) switching from bus sleep mode to network mode may include: when the current vehicle ECU is in bus sleep mode, receiving a message sent by an associated vehicle ECU, or receiving a network request, then switching from bus sleep mode to network mode.

[0054] Among them, the associated vehicle ECU can be the vehicle ECU that sends messages to the current vehicle ECU.

[0055] Correspondingly, when the current vehicle ECU is in bus sleep mode, if the current vehicle ECU receives a message from a related vehicle ECU in the vehicle system, or receives a network request, it will switch the current bus sleep mode to network mode.

[0056] S220. Based on the associated node message, determine the associated vehicle ECU that sent the message to the current vehicle ECU in the duplicate message state.

[0057] Among them, the associated vehicle ECU and the current vehicle ECU are located in the same vehicle system.

[0058] In this embodiment of the invention, the current vehicle ECU can parse the received associated node message to determine the target associated ECU to which the message is sent when the current vehicle ECU is in a duplicate message state.

[0059] S230. Determine the target associated ECU based on the number of messages sent by the associated vehicle ECU to the current vehicle ECU.

[0060] In general, the number of associated vehicle ECUs is not unique. The number of messages sent by each associated vehicle ECU to the current vehicle ECU can be recorded, and the vehicle ECU that sends the most messages to the current vehicle ECU can be used as the target associated ECU.

[0061] S240. When the current vehicle ECU switches from network mode to normal operation and receives a network release signal, or when the current vehicle ECU's repeat message timer expires and a network release signal is received, the message waiting state for the target associated ECU is enabled, and the message waiting timer is started.

[0062] In an optional embodiment of the present invention, after the current vehicle ECU switches from network mode to normal working state, it may further include: if a duplicate message indication or duplicate message request is received, then switch the normal working state to network mode and return to the step of enabling duplicate message state.

[0063] In this embodiment of the invention, after the current vehicle ECU switches from network mode to normal working state, if it receives a duplicate message indication or duplicate message request, it can switch the current normal working state back to network mode and return to the step of enabling duplicate message state.

[0064] S250: If the message waiting timer of the current vehicle ECU expires and no message is received from the target associated ECU while in the message waiting state, but a network release signal is received, then the system enters the sleep preparation state.

[0065] S260. After the current vehicle ECU enters the preparation hibernation state, determine the target transition state based on the network manager timer duration, the bus hibernation timer duration, and the data reception behavior, or only based on the data reception behavior, and then transition to the target transition state.

[0066] In an optional embodiment of the present invention, determining the target transition state based solely on data reception behavior may include: if the data reception behavior determines that the current vehicle ECU has received a network request, then the system transitions from a ready-to-sleep state to a normal working state; if the data reception behavior determines that the current vehicle ECU has received a duplicate message indication or a duplicate message request, then the system transitions from a ready-to-sleep state to network mode.

[0067] In this embodiment of the invention, when the current vehicle ECU enters the preparation for hibernation state, a network management timer can be started. If the network management timer has not reached its designated duration, only data reception behavior needs to be parsed. If the data reception behavior indicates that the current vehicle ECU has received a network request, it transitions from the preparation for hibernation state to the normal operating state. If the data reception behavior indicates that the current vehicle ECU has received a duplicate message indication or duplicate message request, it transitions from the preparation for hibernation state to network mode.

[0068] In an optional embodiment of the present invention, determining the target transition state based on the network manager timing duration, the bus sleep timing duration, and the data receiving behavior may include: when the duration of the current vehicle ECU entering the sleep preparation state is greater than the network manager timing duration, transitioning from the sleep preparation state to the bus pre-sleep mode; and determining the target transition state from the bus pre-sleep mode based on the bus sleep timing duration and the data receiving behavior.

[0069] In this embodiment of the invention, when the duration of the current vehicle ECU entering the sleep preparation state is greater than the network manager timeout duration, i.e., the network manager timeout occurs, the current vehicle ECU can switch from the sleep preparation state to the bus pre-sleep mode, and then start the waiting bus sleep timer. If the duration of the current vehicle ECU entering the bus pre-sleep mode is greater than the bus sleep timeout duration set by the waiting bus sleep timer, it is determined that the waiting bus sleep timer has timed out. Furthermore, by parsing the data receiving behavior, the target state to be switched from the bus pre-sleep mode is determined.

[0070] In an optional embodiment of the present invention, determining the target transition state from the bus pre-sleep mode based on the bus sleep timer duration and data reception behavior may include: transitioning from the bus pre-sleep mode to the network mode when it is determined, based on the data reception behavior, that a message sent by an associated vehicle ECU to the current vehicle ECU has been received, or a network request has been received; and transitioning from the bus pre-sleep mode to the bus sleep mode when the duration of the current vehicle ECU's entry into the bus pre-sleep mode is longer than the bus sleep timer duration, and it is determined, based on the data reception behavior, that a message sent by an associated vehicle ECU to the current vehicle ECU has been received.

[0071] In this embodiment of the invention, if the current vehicle ECU is in bus pre-sleep mode, the duration of the current vehicle ECU in bus pre-sleep mode is less than the bus sleep timer duration, and data receiving behavior exists, then the data receiving behavior is parsed. If, based on the data receiving behavior, it is determined that a message sent by an associated vehicle ECU to the current vehicle ECU has been received, or a network request has been received, then the system switches from bus pre-sleep mode to network mode. If the duration of the current vehicle ECU in bus pre-sleep mode is greater than the bus sleep timer duration, and data receiving behavior exists, then the data receiving behavior is parsed. If, based on the data receiving behavior, it is determined that a message sent by an associated vehicle ECU to the current vehicle ECU has been received, then the system switches from bus pre-sleep mode to bus sleep mode.

[0072] In a specific example, each onboard ECU (Electronic Control Unit) in the network management of an vehicle can independently manage its network status. Therefore, an ECU can also be called an NM (Network Management) node. Each NM node in the same physical network periodically broadcasts messages. This solution adjusts the network management status judgment mechanism by adding a new state machine. This ensures that ECUs can sleep and wake up in an orderly manner while reducing the probability of missing important messages, thus improving the quality of network management. The network management process is as follows: Figure 3 As shown, it includes the following steps:

[0073] Step 1: After the system is powered on, NM initialization is completed. The current vehicle ECU enters bus sleep mode and does not send NM messages to associated vehicle ECUs, but can receive NM messages from associated vehicle ECUs.

[0074] Step 2: When either condition a or condition b is met, the current vehicle ECU switches from bus sleep mode to network mode, defaulting to a repetitive message state, periodically sending and receiving NM messages. The number of messages received from associated vehicle ECUs is recorded, and the node receiving the most messages is designated as the target associated ECU. Condition a, receiving an NM message from an associated vehicle ECU, indicates that the sending node is committed to network wake-up. Condition b, receiving a network request, indicates that an application has made a network request through state management, hoping to wake up the network.

[0075] Step 3: When conditions c and d are both met, the current vehicle ECU transitions from the duplicate message state to the normal operating state, periodically sending and receiving NM messages, and the network remains in a wake-up state. However, if a message with the duplicate request indication bit set to 1 (duplicate message indication or duplicate message request) is received, the current vehicle ECU returns from the normal operating state to the duplicate message state. Here, condition c is the duplicate message timer timeout, and condition d is receiving a network request from the application via state management.

[0076] Step 4, Case 1: When both conditions e and f are met, the current vehicle ECU transitions from the repeat message state to the message waiting state, still periodically sending and receiving NM messages. Condition e is the repeat message timer timeout. Condition f is receiving a network release signal from the application via state management.

[0077] Scenario 2: When the network release signal sent by the application through state management is received, the current vehicle ECU switches from normal working state to message waiting state, and still periodically sends and receives NM messages.

[0078] Step 5: When the message waiting timer expires, and no NM message is received from the target associated ECU within this time period and the network request is released, the current vehicle ECU enters the ready-to-sleep state from the message waiting state, and can normally receive NM messages, while ceasing to send NM messages. If a network request is received from the application through state management, the current vehicle ECU directly transitions from the ready-to-sleep state to the normal operating state. If a message with the repeat request indication bit set to 1 is received, the current vehicle ECU directly transitions from the ready-to-sleep state to the repeat message state.

[0079] Step 6: When the network management timer times out, the network management timer is turned off, and the bus sleep timer is started. The current node enters the bus pre-sleep mode from the ready-to-sleep state, unable to send NM messages, but can receive NM messages normally. If an NM message is received from the associated vehicle ECU or a network request is received, the current vehicle ECU returns directly from the bus pre-sleep mode to the network mode, defaulting to the repeat message state. If the bus sleep timer times out and the current vehicle ECU has not received an NM message from the associated vehicle ECU, the current vehicle ECU enters the bus sleep mode from the bus pre-sleep mode.

[0080] In the specific example above, the network state is divided into six states: bus sleep mode, repeated message state, normal operation state, message waiting state, ready to sleep state, and bus pre-sleep mode. In the repeated message state, the target associated ECU can be recorded. After the current vehicle ECU enters the repeated message state, the number of messages received from associated vehicle ECUs is recorded, and the node with the most records is designated as the target associated ECU. When the repeated message timer expires and a network release signal is received from the application via state management, the current vehicle ECU transitions from the repeated message state to the message waiting state. When a network release signal is received from the application via state management, the current vehicle ECU transitions from the normal operation state to the message waiting state. If the message waiting timer expires and no NM message is received from the target associated ECU and a network release request is received, the ECU enters the ready to sleep state. This example implements ordered sleep and wake-up of ECU nodes, saving vehicle power consumption while ensuring interaction with important related nodes. It enables each ECU to independently manage its network state and provides a transition phase for ECU sleep.

[0081] The technical solution of this invention involves enabling a repeat message state and starting a repeat message timer when the current vehicle electronic control unit (ECU) transitions from bus sleep mode to network mode. Based on associated node messages, it identifies the associated vehicle ECU that sends messages to the current ECU in the repeat message state. Then, based on the number of messages sent by the associated vehicle ECU to the current ECU, it identifies the target associated ECU. Further, when the current ECU transitions from network mode to normal operation and receives a network release signal, or when the current ECU's repeat message timer expires and it receives a network release signal, it initiates a message waiting state for the target associated ECU and starts a message waiting timer. If the current ECU's message waiting timer expires and it does not receive a message from the target associated ECU while in the message waiting state, but receives a network release signal, it enters a sleep preparation state. After the current ECU enters the sleep preparation state, it determines the target transition state based on the network manager timing duration, the bus sleep timing duration, and data reception behavior, or only based on data reception behavior, and then transitions to the target transition state.

[0082] In this solution, the target associated ECU that frequently sends messages to the current vehicle ECU can be identified, and the messages sent by the target associated ECU are regarded as important messages. By setting a message waiting state, the vehicle ECU can be prevented from switching directly from the current normal working state or the repeated message state to the sleep state. Time is reserved for the current vehicle ECU to receive important messages (which can be set according to the needs of the vehicle system). This solves the problem of the vehicle ECU lacking important message identification and the loss of important messages. It can minimize the loss of important messages when the system allows.

[0083] Example 3

[0084] Figure 4 This is a schematic diagram of the network management device for an in-vehicle electronic control unit provided in Embodiment 3 of the present invention. Figure 4 As shown, the device includes: a repeat message state activation module 310, a target associated ECU determination module 320, a message waiting state activation module 330, a sleep preparation state activation module 340, and a target transition state determination module 350, wherein,

[0085] The repeat message state enabling module 310 is used to enable the repeat message state and start the repeat message timer when the current vehicle ECU switches from bus sleep mode to network mode.

[0086] The target associated ECU determination module 320 is used to determine the target associated ECU based on the associated node message obtained from the repeated message status;

[0087] The message waiting state activation module 330 is used to activate the message waiting state for the target associated ECU and start the message waiting timer when the current vehicle ECU switches from network mode to normal working state and receives a network release signal, or when the current vehicle ECU's repeat message timer expires and receives a network release signal.

[0088] The sleep state preparation module 340 is used to enter the sleep state when the message waiting timer of the current vehicle ECU expires and no message is received from the target associated ECU during the message waiting state, but the network release signal is received.

[0089] The target transition state determination module 350 is used to determine the target transition state and transition to the target transition state after the current vehicle ECU enters the preparation hibernation state, based on the network manager timer duration, the bus hibernation timer duration, and the data receiving behavior, or only based on the data receiving behavior.

[0090] The technical solution of this invention involves enabling a repeat message state and starting a repeat message timer when the current vehicle ECU transitions from bus sleep mode to network mode. Based on the associated node messages obtained in the repeat message state, the target associated ECU is determined. Then, when the current vehicle ECU transitions from network mode to normal operation and receives a network release signal, or when the repeat message timer of the current vehicle ECU times out and a network release signal is received, a message waiting state for the target associated ECU is initiated, and a message waiting timer is started. Further, if the message waiting timer of the current vehicle ECU times out and no message is received from the target associated ECU during the message waiting state, but a network release signal is received, the ECU enters a sleep preparation state. After the current vehicle ECU enters the sleep preparation state, the target transition state is determined based on the network manager timing duration, the bus sleep timing duration, and data reception behavior, or only based on data reception behavior, and the ECU transitions to the target transition state. In this solution, the target associated ECU that frequently sends messages to the current vehicle ECU can be identified, and the messages sent by the target associated ECU are regarded as important messages. By setting a message waiting state, the vehicle ECU can be prevented from switching directly from the current normal working state or the repeated message state to the sleep state. Time is reserved for the current vehicle ECU to receive important messages (which can be set according to the needs of the vehicle system). This solves the problem of the vehicle ECU lacking important message identification and the loss of important messages. It can minimize the loss of important messages when the system allows.

[0091] Optionally, the target associated ECU determination module 320 is specifically used to determine, based on the associated node message, the associated vehicle ECU that sent the message to the current vehicle ECU in the repeated message state; and to determine the target associated ECU based on the number of messages sent by the associated vehicle ECU to the current vehicle ECU.

[0092] Optionally, the message waiting state activation module 330 includes a bus sleep mode state switching unit, which is used to switch from the bus sleep mode to the network mode when the current vehicle ECU is in the bus sleep mode and receives a message sent by the associated vehicle ECU or a network request.

[0093] Optionally, the network management device of the vehicle electronic control unit also includes a normal operation state switching unit, which, upon receiving a duplicate message indication or duplicate message request, switches the normal operation state to network mode and returns to the step of enabling the duplicate message state.

[0094] Optionally, the target transition state determination module 350 includes a first target transition state determination unit, used to transition from the prepared hibernation state to the normal working state if it is determined from the data receiving behavior that the current vehicle ECU has received a network request; and to transition from the prepared hibernation state to network mode if it is determined from the data receiving behavior that the current vehicle ECU has received a duplicate message indication or duplicate message request.

[0095] Optionally, the target transition state determination module 350 includes a second target transition state determination unit, used to transition from the prepared hibernation state to the bus pre-hibernation mode when the duration of the current vehicle ECU entering the prepared hibernation state is greater than the network manager timing duration; and to determine the target transition state from the bus pre-hibernation mode based on the bus hibernation timing duration and data reception behavior.

[0096] Optionally, the second target transition state determination unit is specifically used to transition from the bus pre-sleep mode to the network mode when it is determined, based on the data receiving behavior, that a message sent by the associated vehicle ECU to the current vehicle ECU has been received, or a network request has been received; and when the duration of the current vehicle ECU entering the bus pre-sleep mode is longer than the bus sleep timer duration, and it is determined, based on the data receiving behavior, that a message sent by the associated vehicle ECU to the current vehicle ECU has been received, then the transition from the bus pre-sleep mode to the bus sleep mode is made.

[0097] The network management device for the vehicle electronic control unit provided in the embodiments of the present invention can execute the network management method for the vehicle electronic control unit provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of executing the method.

[0098] Example 4

[0099] Figure 5 A schematic diagram of a vehicle electronic control unit that can be used to implement embodiments of the present invention is shown. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the invention described and / or claimed herein.

[0100] like Figure 5 As shown, the vehicle electronic control unit 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded into the RAM 13 from the storage unit 18. The RAM 13 can also store various programs and data required for the operation of the vehicle electronic control unit 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0101] Multiple components in the vehicle electronic control unit 10 are connected to the I / O interface 15, including: an input unit 16, such as a keyboard, mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a disk, optical disk, etc.; and a communication unit 19, such as a network card, modem, wireless transceiver, etc. The communication unit 19 allows the vehicle electronic control unit 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0102] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as network management methods for in-vehicle electronic control units.

[0103] In some embodiments, the network management method for the vehicle electronic control unit can be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program can be loaded and / or installed onto the vehicle electronic control unit 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the network management method for the vehicle electronic control unit described above can be performed. Alternatively, in other embodiments, processor 11 can be configured to perform the network management method for the vehicle electronic control unit by any other suitable means (e.g., by means of firmware).

[0104] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0105] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0106] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0107] To provide interaction with the user, the systems and techniques described herein can be implemented on an in-vehicle electronic control unit (EVU) having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the EVU. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0108] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or computing systems that include middleware components (e.g., application servers), or computing systems that include frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0109] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0110] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0111] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A network management method for an on-board electronic control unit, characterized in that, include: When the current vehicle electronic control unit (ECU) switches from bus sleep mode to network mode, the repeat message state is enabled and the repeat message timer is started. Based on the associated node messages obtained from the repeated message status, the target associated ECU is determined; When the current vehicle ECU switches from the network mode to normal operation and receives the network release signal, or when the current vehicle ECU's repeat message timer expires and the network release signal is received, the message waiting state for the target associated ECU is enabled, and the message waiting timer is started. If the message waiting timer of the current vehicle ECU times out and no message is received from the target associated ECU while in the message waiting state, but the network release signal is received, then the system enters the sleep preparation state. After the current vehicle ECU enters the preparation hibernation state, the target transition state is determined based on the network manager timeout duration, the bus hibernation timeout duration, and the data receiving behavior, or only based on the data receiving behavior, and the system transitions to the target transition state. The determination of the target associated ECU based on the associated node messages obtained from the duplicate message status includes: Based on the associated node message, determine the associated vehicle ECU that sent the message to the current vehicle ECU in the repeated message state; The target associated ECU is determined based on the number of messages sent by the associated vehicle ECU to the current vehicle ECU. The target associated ECU is an on-board ECU that sends messages to the current on-board ECU at a frequency that reaches a preset threshold. The message waiting state is a state before the vehicle ECU prepares to hibernate, in order to prevent the vehicle ECU from directly switching from the current normal working state or the repeated message state to the hibernation state, and to reserve time for the current vehicle ECU to receive important messages; the message waiting state is used to receive important messages sent by the target associated ECU. The message waiting timer is a timer that operates when the message waiting state is enabled and does not operate when the message waiting state is not enabled; The target transition state is the next stage state that the current vehicle ECU needs to transition to after preparing for hibernation; the network manager timer duration is the timer duration set for the network management timer; and the bus hibernation timer duration is the timer duration set for the bus hibernation timer.

2. The method according to claim 1, characterized in that, The current vehicle ECU has switched from bus sleep mode to network mode, including: When the current vehicle ECU is in bus sleep mode, if a message is received from the associated vehicle ECU or a network request is received, the system will switch from bus sleep mode to network mode.

3. The method according to claim 1, characterized in that, After the on-board ECU switches from the network mode to normal operating status, it also includes: Upon receiving a duplicate message indication or duplicate message request, the system switches from normal operation to network mode and returns to the step of enabling duplicate message status.

4. The method according to claim 3, characterized in that, The target transition status is determined solely based on the data reception behavior, including: If it is determined from the data receiving behavior that the current vehicle ECU has received a network request, then it will switch from the preparation for hibernation state to the normal working state. If the data reception behavior determines that the current vehicle ECU is receiving a duplicate message indication or duplicate message request, then the system will switch from the sleep mode to network mode.

5. The method according to claim 1, characterized in that, Based on the network manager's timer duration, the bus sleep timer duration, and data reception behavior, determine the target transition status, including: When the duration during which the current vehicle ECU enters the sleep preparation state exceeds the timeout duration of the network manager, the system transitions from the sleep preparation state to the bus pre-sleep mode. Based on the bus sleep timeout duration and data reception behavior, the target transition state from the bus pre-sleep mode is determined.

6. The method according to claim 5, characterized in that, Based on the bus sleep timer duration and data reception behavior, determine the target transition state from the bus pre-sleep mode, including: When it is determined, based on the data receiving behavior, that a message sent by the associated vehicle ECU to the current vehicle ECU has been received, or a network request has been received, the bus pre-sleep mode is switched to network mode. If the duration of the current vehicle ECU entering the bus pre-sleep mode is longer than the bus sleep timer duration, and it is determined from the data receiving behavior that a message sent by the associated vehicle ECU to the current vehicle ECU has been received, then the system will switch from the bus pre-sleep mode to the bus sleep mode.

7. A network management device for an on-board electronic control unit, the device being used to implement the method as described in any one of claims 1-6, characterized in that, include: The repeated message state enabling module is used to enable the repeated message state and start the repeated message timer when the current vehicle ECU switches from bus sleep mode to network mode. The target associated ECU determination module is used to determine the target associated ECU based on the associated node messages obtained from the repeated message status. The message waiting state activation module is used to activate the message waiting state for the target associated ECU and start the message waiting timer when the current vehicle ECU switches from network mode to normal working state and receives a network release signal, or when the current vehicle ECU's repeat message timer expires and receives a network release signal. The sleep state preparation module is used to enter the sleep state when the message waiting timer of the current vehicle ECU expires and no message is received from the target associated ECU during the message waiting state, but the network release signal is received. The target transition state determination module is used to determine the target transition state and transition to the target transition state after the current vehicle ECU enters the preparation hibernation state, based on the network manager timer duration, the bus hibernation timer duration, and the data receiving behavior, or only based on the data receiving behavior.

8. A vehicle-mounted electronic control unit, characterized in that, The vehicle-mounted electronic control unit includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the network management method of the vehicle electronic control unit according to any one of claims 1-6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that, when executed by a processor, implement the network management method of any one of claims 1-6 for the vehicle electronic control unit.

Images