An improved network management method based on AUTOSAR

Abstract

The application discloses an improved network management method based on AUTOSAR, wherein the network node state comprises a network mode and a sleep mode; the node receives and sends network management messages in the network mode; when the number of errors in sending or receiving network management messages exceeds a threshold value, or a network management message with a sleep flag is received, the node enters a fault detection state; the node stops communication work in the sleep mode; if the duration of no communication work exceeds a certain time, the node enters the sleep mode; if the expected stay time of the node in the sleep mode is less than a preset time, the node enters a light sleep mode; if the expected stay time of the node in the sleep mode is greater than the preset time or the duration of the node in the light sleep mode exceeds a certain time, the node enters a deep sleep mode. The application adds a fault detection stage, a light sleep mode and a deep sleep mode to the original network node state, and improves the accuracy and flexibility of network management.

Description

Technical Field

[0001] This invention relates to the field of vehicle network management, and more particularly to a network management method based on AUTOSAR. Background Technology

[0002] A crucial task of network management is ensuring the security and reliability of network communication. Network management can initialize controller resources, start the network, detect, process, and notify the network and node status, and coordinate network nodes to synchronously enter sleep mode. Existing AUTOSAR network management systems primarily rely on traditional wake-up and sleep modes to manage the energy consumption of ECUs (Electronic Control Units). However, with the increasing complexity of automotive electronic systems and ever-increasing energy consumption requirements, traditional modes are no longer sufficient to meet practical needs. Furthermore, in current technology, if a node experiences a fault while in network mode, it will not send network management messages, causing other nodes to perceive it as preparing to sleep, thus failing to recognize the fault.

[0003] Therefore, a more refined energy management strategy is needed to improve network management and optimize the overall energy consumption of vehicles. Summary of the Invention

[0004] This invention proposes a method for introducing a light sleep mode, a deep sleep mode, and a fault detection status into an AUTOSAR network management system, aiming to optimize vehicle energy consumption and improve the flexibility of network management.

[0005] The technical solution adopted in this invention is:

[0006] An improved network management method based on AUTOSAR is provided. The network node states include network mode and sleep mode. In network mode, the node receives and sends network management messages. When the number of errors in sending or receiving network management messages exceeds a threshold, or when a network management message with a sleep flag is received, the node enters a fault detection state. In the fault detection state, the node repeatedly sends network management messages. If the number of failed transmissions reaches a preset value, the node is determined to be faulty.

[0007] Nodes cease communication in sleep mode. If the duration of no communication exceeds a certain time, the node enters sleep mode. If the expected duration of sleep mode is less than a preset time, the node enters light sleep mode. If the expected duration of sleep mode is greater than the preset time or the duration of light sleep mode exceeds a certain time, the node enters deep sleep mode.

[0008] According to the above scheme, after the ECU is powered on, the network node initializes and enters a light sleep mode;

[0009] When a node detects an active wake-up request or receives a valid network management message while in light sleep mode, or when a node receives a specific wake-up request while in deep sleep mode, the node enters a repeat message state; the specific wake-up request specifically includes a power-on signal or a specific hardware reset signal.

[0010] If a node remains in the repeat message state for longer than the repeat message timer duration, it will enter the normal operation state if there is an active network request; otherwise, it will enter the sleep preparation state.

[0011] According to the above scheme, when a node sends an error that reaches the threshold or receives an error that exceeds the threshold during the timed period of normal operation or repeated message state, or when a node receives a network management message with a sleep flag, the node enters the fault detection state.

[0012] When a node is in fault detection state and receives a network management message without a sleep flag, the node enters a sleep-ready state.

[0013] When a node is preparing to sleep, if it detects an active network request, it enters the normal operation state; if it does not detect an active network request and the network management timeout timer expires, the node enters the pre-sleep mode.

[0014] When a node is in pre-sleep mode, it no longer receives active or passive wake-up requests and the timer expires. If the expected dwell time is less than a certain preset value, the node enters light sleep mode; if the expected dwell time is greater than a certain preset value, the node enters deep sleep mode.

[0015] According to the above scheme, if a node detects an active wake-up request while in light sleep mode, the node enters the fast transmission state in the repeated message state.

[0016] When a node is in light sleep mode, if it receives a valid network management message, the node enters the normal sending state in the repeated message state and sends network management messages at a normal cycle.

[0017] When a node enters the fast transmission state, it starts a counter. When the counter reaches zero, the node enters the normal transmission state and waits for a certain period of time before sending network management messages at a normal cycle.

[0018] According to the above scheme, if a node receives a network management message with duplicate message request bit 1 when it is in normal operation state or in sleep preparation state, the node enters duplicate message state.

[0019] According to the above scheme, when a node is in normal operation, if it releases all network requests and no longer needs to actively request the network, the node will immediately enter a sleep state and immediately stop sending network management messages.

[0020] According to the above scheme, when a node can correctly send network management messages and receive network management messages without a sleep flag in the fault detection state, the node enters the duplicate message state.

[0021] According to the above scheme, if a node detects an active wake-up request while in pre-sleep mode, the node enters a fast sending state for repeated messages.

[0022] When a node is in pre-sleep mode, if a passive wake-up request is detected, the node enters the normal sending state of repeating messages.

[0023] According to the above scheme, the fault detection status is introduced into a dynamically updated network management table in the network management interface module. The network management table includes three key fields: node ID, time interval, and fault counter. The node ID is used to uniquely identify each node, the time interval is used to record the longest interval at which each node should send a message, and the fault counter is used to accumulate the number of times a node fails to send a message on time. When the value of the fault counter exceeds a preset value, the node is determined to be in a fault state.

[0024] A computer-readable storage medium containing a computer program that, when invoked by a motor controller, implements the AUTOSAR-based improved network management method described above.

[0025] The beneficial effects of this invention are:

[0026] 1. This invention adds a fault detection stage to the original network communication node status, which effectively solves the problem that when a node is in network mode, if a fault occurs and it does not send network management messages, but other nodes confirm that the node is preparing to sleep, thus improving the accuracy of network management.

[0027] 2. This invention introduces light sleep and deep sleep modes, which reduce the energy consumption of the vehicle when it is not in use, improve overall energy efficiency, and provide more options for the AUTOSAR network management system, enabling the system to make flexible adjustments according to different scenarios and needs, reducing malfunctions and instability caused by frequent ECU wake-up and hibernation, and improving the flexibility of network management. Attached Figure Description

[0028] Figure 1 This is a schematic diagram of network node status according to an embodiment of the present invention;

[0029] Figure 2 This is a schematic diagram of network node state transitions according to another embodiment of the present invention;

[0030] Figure 3This is a schematic diagram of the structure of a computer device provided in another embodiment of the present invention. Detailed Implementation

[0031] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the invention.

[0032] The vehicle's ignition switch has four states: OFF, ACC, ON, and START. Based on the working state of the ECU after the ignition switch is turned OFF, this patent divides the ECUs in the CAN network into two categories: Category I and Category II.

[0033] Class I ECU: A node that only starts communicating when the ignition switch is switched from OFF to ON / ACC, and immediately stops or delays communication for a period of time after switching from OFF to OFF.

[0034] Class II ECUs: Can still maintain CAN communication when the ignition switch is OFF.

[0035] Class I ECUs use indirect network management; Class II ECUs use AUTOSAR network management.

[0036] Example 1

[0037] This embodiment provides a network management method based on AUTOSAR, such as... Figure 1 As shown, the network node state includes network mode and sleep mode. In network mode, the node receives and sends network management messages. When the number of errors in sending or receiving network management messages exceeds the threshold, or when a network management message with a sleep flag is received, the node enters the fault detection state. In the fault detection state, the node repeatedly sends network management messages. If the number of failed transmissions reaches a preset value, the node is determined to be faulty.

[0038] Nodes cease communication in sleep mode. If the duration of no communication exceeds a certain time, the node enters sleep mode. If the expected duration of sleep mode is less than a preset time, the node enters light sleep mode. If the expected duration of sleep mode is greater than the preset time or the duration of light sleep mode exceeds a certain time, the node enters deep sleep mode.

[0039] In this embodiment, to address the issue that if a node in the network is active but experiences a sudden failure that prevents it from sending network management messages, other nodes might mistakenly believe that the node is preparing to enter a dormant state, a fault detection state is added. To solve this problem, this embodiment introduces a dynamically updated network management table into the network management interface module.

[0040] The network management table includes three key fields: node ID, time interval, and fault counter. The node ID is used to uniquely identify each node, the time interval is used to record the interval at which each node should send messages, and the fault counter is used to accumulate the number of times a node fails to send messages on time.

[0041] When the system starts, all nodes enter the REPEAT state by default and send network management messages in a specific order. Whenever the network management interface module receives a management message from another node, it records the sender's ID in the network management table (if the ID already exists, it is not recorded again). Simultaneously, after each successful message reception, the corresponding node's "time interval" and "fault counter" are reset to 0. If a node sends or receives messages incorrectly a certain number of times within the set time interval, the system considers that the node to be potentially faulty. In this case, if further detection is necessary, the system will send a network management message in the REPEAT state to the node as a probe. Normally, the node receiving this message will respond with the same REPEAT state management message in its next sending cycle. If the node fails to respond, the corresponding fault counter will increment by 1. This detection process continues until the fault counter reaches a preset threshold. Once this threshold is reached, the system determines that the node is in a faulty state and reports this fault to the application layer.

[0042] This embodiment also introduces a light sleep mode and a deep sleep mode. The light sleep mode and deep sleep mode can rationally switch states based on the actual operating conditions and energy consumption requirements of the vehicle. This logic intelligently selects the ECU's sleep mode based on multiple factors such as network load, ECU task priority, and vehicle driving status, and configures timers: a light sleep timer is set for switching from network mode to light sleep mode; a deep sleep timer is set for switching from light sleep mode to deep sleep mode, and state switching is performed when necessary. In light sleep mode, power consumption is lower, maintaining a minimum level of functional activity. In this mode, the ECU can still respond to certain types of wake-up signals, such as specific types of network management messages or hardware interrupts. In deep sleep mode, operation ceases, and all unnecessary hardware functions are turned off to maximize energy savings. In this mode, the ECU only responds to a very limited number of wake-up signals, such as power-on signals or specific hardware reset signals.

[0043] Example 2

[0044] In this embodiment, NM is an abbreviation for Network Management.

[0045] As another embodiment of the present invention, this embodiment specifically divides the operating mode of a network node into the following operating modes:

[0046] (1) Network Mode

[0047] In a network mode, a node is either in an active or operational mode (including preparation phases for starting and ending operations). A network mode is further subdivided into the following four phases:

[0048] ① Repeat Message State (RMS)

[0049] When a node enters Network Mode from other modes, it defaults to the Repeat Message State. This stage is a preparation phase before the network officially begins operation, used to wait for all relevant nodes in the network to prepare and initiate communication. The Repeat Message State includes the following two states:

[0050] 1) Normal Transmit State (NTS)

[0051] When a remote wake-up occurs, it enters the NTS state and passively communicates.

[0052] 2) Immediate Transmit State (ITS)

[0053] When a local wake-up occurs, it enters the ITS state and initiates communication.

[0054] ②Normal Operation State (NOS)

[0055] The node transitions from Repeat Message State to Normal Operation State, a state where node communication is functioning normally.

[0056] ③Ready Sleep State (RSS)

[0057] Once a node has completed its task, it transitions from the Normal Operation State to the Ready Sleep State, preparing to enter a sleep state. This phase is used to wait for all nodes in the network to complete their tasks before they all enter a sleep state.

[0058] ④ Fault Detection State (FDS)

[0059] The system monitors network status and the operational status of each node in real time, enabling rapid fault detection and response. When the number of sending or receiving errors by a node in network mode exceeds a threshold, the node enters the FDS state and repeatedly sends FDS messages at regular intervals. If, within a specified time, the node fails to send any messages or receive any network management messages, it indicates that the node cannot use bus communication normally, and the node will report the error to the application layer.

[0060] (2) Sleep Mode

[0061] Sleep mode is a mode in which nodes stop working, saving energy consumption and representing the ultimate goal of network management. Network management involves managing how nodes orderly enter and resume sleep mode. Nodes should enter sleep mode by default upon power-on or reset. Sleep mode includes the following three modes:

[0062] ①Prepare Sleep State (PSS)

[0063] A node transitions from the pre-sleep state in network mode to pre-sleep mode. This stage is similar to the function of RSS, but it no longer belongs to network mode; it is a further preparation stage before officially entering the sleep stage.

[0064] ②Light Sleep State (LSS)

[0065] When the vehicle experiences a short period of inactivity, it enters a light sleep phase, maintaining minimal functional activity (such as modules receiving wake-up signals and time-holding modules). Typical applicable scenarios include brief stops or waiting periods requiring short-term restarts. Triggering conditions include door closures, engine shutdown, and CAN bus inactivity exceeding a set time.

[0066] ③Deep Sleep State (DSS)

[0067] When a vehicle experiences no activity signals for an extended period, it enters a deep sleep phase and ceases operation. Common applicable scenarios include: prolonged parking with no significant activity signals and a long expected duration. Triggering conditions include CAN bus inactivity exceeding a set time, the driver being away from the vehicle, and low vehicle battery.

[0068] like Figure 2 As shown, the state transitions of network nodes in this embodiment include:

[0069] 1. When the ECU is powered on, it will initialize and enter a light sleep mode.

[0070] 2. When light sleep lasts for a certain period of time, it enters deep sleep mode.

[0071] 3. System power failure.

[0072] 4. If a node detects an active wake-up request while in light sleep mode, the node must send a network management message to actively wake up the network. During this process, the node must first enter the NM fast transmission state. When the node needs to wake up the network due to the active wake-up request, it must quickly send consecutive NM messages.

[0073] 5. When a node is in light sleep mode, if it receives a valid network management message, the node will leave light sleep mode and enter the NM normal transmission state in the repeat message state. After entering the NM normal transmission state, the node must send network management messages at normal intervals before the repeat message timer expires. When the node receives a network management message, the first message it sends to the bus can be either a network management message or an application message.

[0074] 6. When a node in the NM fast transmission state reaches zero, it will enter the NM normal transmission state and begin to wait for a period of time before sending network management messages at the normal cycle.

[0075] 7. For an active network request node in the repeat message state, if the RepeatMessage Timer times out but the node's active network requests continue, the node must enter the normal operating state. The node continues to send network management messages and application messages at the normal cycle.

[0076] 8. When a node is in the normal operation phase, if it receives a network management message with the Repeat MessageRequest bit set to 1, it will be forced to re-enter the repeat message phase.

[0077] 9. If a node in the repeat message state does not detect an active network request, it will enter a sleep state once the RepeatMessage Timer expires.

[0078] 10. When a node is in a sleep-ready state, if it receives a network management message with the Repeat MessageRequest bit set to 1, it will be forced to re-enter the repeat message state.

[0079] 11. If a node in the pre-sleep state does not detect an active network request, it will enter pre-sleep mode once the network management timeout timer (NM Timeout Timer) expires.

[0080] 12. If a node in pre-sleep mode detects an active wake-up request, the node will enter the NM fast transmission state of repeating messages.

[0081] 13. If a node in pre-sleep mode receives a passive wake-up request, the node will enter the NM normal transmission state of the duplicate message state.

[0082] 14. If a node in a sleep state detects an active network request, it must immediately enter a normal operating state and begin sending network management messages and application messages at a normal cycle.

[0083] 15. If a node in normal operation state releases all network requests and no longer needs to actively request the network, it must immediately switch its network management state to the ready-to-sleep state, and at the same time, the node must immediately stop sending network management messages.

[0084] 16. When a node sends a message and receives a message, or when the number of errors exceeds the threshold, the node enters a fault detection state.

[0085] 17. The node was previously in a fault detection state and received a network management message without sleep mode. The node then enters a sleep mode.

[0086] 18. When a node receives a network management message with a sleep flag, the node enters a fault detection state.

[0087] 19. If a node's sending error reaches or receiving error exceeds the threshold during the repeated message state timeout period, the node enters the fault detection state.

[0088] 20. If a node can correctly send network management messages and receive network management messages without a sleep flag, the node enters the duplicate message state.

[0089] 21. If a node in pre-sleep mode no longer receives active or passive wake-up requests, it will enter light sleep mode once the timer expires and the expected dwell time is short (less than a certain preset value).

[0090] 22. If a node in pre-sleep mode no longer receives active or passive wake-up requests, it will enter deep sleep mode once the timer expires and the expected dwell time is relatively long (greater than a certain preset value).

[0091] 23. If a node in deep sleep mode receives a specific wake-up request, it will enter a repeat message state.

[0092] In this embodiment, to address the issue that if a node in the network is active but experiences a sudden failure that prevents it from sending network management messages, other nodes might mistakenly believe that the node is preparing to enter a dormant state, a fault detection state is added. To solve this problem, this embodiment employs two strategies:

[0093] 1. Optimize and implement the vehicle hibernation mechanism as described above.

[0094] 2. Introduce a dynamically updated network management table in the network management interface module.

[0095] The network management table includes three key fields: node ID, time interval, and fault counter. The node ID is used to uniquely identify each node, the time interval is used to record the interval at which each node should send messages, and the fault counter is used to accumulate the number of times a node fails to send messages on time.

[0096] When the system starts, all nodes enter the REPEAT state by default and send network management messages in a specific order. Whenever the network management interface module receives a management message from another node, it records the sender's ID in the network management table (if the ID already exists, it is not recorded again). Simultaneously, after each successful message reception, the corresponding node's "time interval" and "fault counter" are reset to 0. If a node sends or receives messages incorrectly a certain number of times within the set time interval, the system considers that the node to be potentially faulty. In this case, if further detection is necessary, the system will send a network management message in the REPEAT state to the node as a probe. Normally, the node receiving this message will respond with the same REPEAT state management message in its next sending cycle. If the node fails to respond, the corresponding fault counter will increment by 1. This detection process continues until the fault counter reaches a preset threshold. Once this threshold is reached, the system determines that the node is in a faulty state and reports this fault to the application layer.

[0097] This embodiment also introduces a light sleep mode and a deep sleep mode. The light sleep mode and deep sleep mode can rationally switch states based on the actual operating conditions and energy consumption requirements of the vehicle. This logic intelligently selects the ECU's sleep mode based on multiple factors such as network load, ECU task priority, and vehicle driving status, and configures timers: a light sleep timer is set to transition from the ready-to-sleep state to light sleep mode; a deep sleep timer is set to transition from light sleep mode to deep sleep mode, and to switch states when necessary. In light sleep mode, power consumption is lower, maintaining a minimum level of functional activity. In this mode, the ECU can still respond to certain types of wake-up signals, such as specific types of network management messages or hardware interrupts. In deep sleep mode, operation ceases, and all unnecessary hardware functions are turned off to maximize energy savings. In this mode, the ECU only responds to a very limited number of wake-up signals, such as power-on signals or specific hardware reset signals.

[0098] The conversion between the various modes is shown in the table below:

[0099] Network mode No network activity and timeout Preparing for sleep Preparing for sleep No online activity and timeout, expected stay is short. Light sleep mode Preparing for sleep No online activity and timeout, expected stay is long. Deep sleep mode Light sleep mode Specific wake-up signal Network mode Light sleep mode No activity and further timeout Deep sleep mode Deep sleep mode Specific wake-up signal Network mode

[0100] Example 3

[0101] like Figure 3 The diagram shown is a structural schematic of a computer device provided in an embodiment of the present invention, such as a smartphone, tablet computer, laptop computer, desktop computer, rack server, blade server, tower server, or cabinet server (including a standalone server or a server cluster composed of multiple servers), etc., capable of executing programs. The computer device 20 in this embodiment includes, but is not limited to, a memory 21 and a processor 22 that can be interconnected via a system bus, such as... Figure 3 As shown. It should be noted that, Figure 3 Only a computer device 20 with components 21-22 is shown; however, it should be understood that it is not required to implement all of the components shown, and more or fewer components may be implemented instead.

[0102] In this embodiment, the memory 21 (i.e., the readable storage medium) includes flash memory, hard disk, multimedia card, card-type memory (e.g., SD or DX memory), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), and programmable read-only memory (PROM). The memory 21 can also be an external storage device of the computer device 20, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the computer device 20. Of course, the memory 21 can also include both internal storage units of the computer device 20 and its external storage devices. In this embodiment, the memory 21 is typically used to store the operating system and various application software installed on the computer device 20. Furthermore, the memory 21 can also be used to temporarily store various types of data that have been output or will be output.

[0103] In some embodiments, processor 22 may be a central processing unit (CPU), controller, microcontroller, microprocessor, or other data processing chip. This processor 22 is typically used to control the overall operation of computer device 20. In this embodiment, processor 22 is used to run program code stored in memory 21 or process data to implement an AUTOSAR-based improved network management method according to the present invention.

[0104] The above embodiments add a fault detection state to the original network communication node status, effectively solving the problem that when a node is in network mode, if a fault occurs and it does not send network management messages, but other nodes confirm that the node is preparing to sleep, thus improving the accuracy of network management. Furthermore, the introduction of light sleep and deep sleep modes reduces the energy consumption level of the vehicle when it is not in use, improving overall energy efficiency. At the same time, it provides more options for the AUTOSAR network management system, enabling the system to flexibly adjust according to different scenarios and needs, reducing faults and instability caused by frequent ECU wake-up and hibernation, and improving the flexibility of network management.

[0105] It should be understood that those skilled in the art can make improvements or modifications based on the above description, and all such improvements and modifications should fall within the protection scope of the appended claims.

Claims

1. A network management method based on an improved AUTOSAR, wherein the network node state includes network mode and sleep mode, characterized in that, In network mode, a node receives and sends network management messages. When the number of errors in sending or receiving network management messages in network mode exceeds a threshold, the node enters a fault detection state. When a node receives a network management message with a sleep flag in network mode, the node enters a fault detection state. The node repeatedly sends network management messages in the fault detection state. If the number of failed transmissions reaches a preset value, the node is determined to be faulty. Nodes stop communicating in sleep mode. If the duration of no communication exceeds a certain time, the node enters sleep mode. If the expected duration of the node entering sleep mode is less than the preset time, the node enters light sleep mode. If the expected duration of the node entering sleep mode is greater than the preset time or the duration of the node entering light sleep mode exceeds a certain time, the node enters deep sleep mode. When a node detects an active wake-up request or receives a valid network management message while in light sleep mode, the node enters the duplicate message state. When a node receives a specific wake-up request while in deep sleep mode, the node enters a repeat message state. If a node enters the normal operation state when the duration of the repeated message state exceeds the repeated message timer time, and there is an active network request, the node will enter the normal operation state. When a node enters a fault detection state, it sends an error threshold or receives an error exceeding a threshold within a timed period during normal operation or repeated message state, or when it receives a network management message with a sleep flag. When a node is in fault detection state, it can correctly send network management messages and receive network management messages without a sleep flag, and then the node enters the duplicate message state. After the ECU is powered on, the network node initializes and enters a light sleep mode; The specific wake-up request specifically includes a power-on signal or a specific hardware reset signal; If a node remains in the duplicate message state for longer than the duplicate message timer duration, and there are no active network requests, the node will enter a sleep-ready state. When a node is in light sleep mode, if it detects an active wake-up request, the node enters the fast transmission state in the repeated message state. When a node is in light sleep mode, if it receives a valid network management message, the node enters the normal sending state in the repeated message state and sends network management messages at a normal cycle.

2. The network management method based on AUTOSAR improvement according to claim 1, characterized in that, When a node is in fault detection state and receives a network management message without a sleep flag, the node enters a sleep-ready state. When a node is preparing to sleep, if it detects an active network request, it enters the normal operation state; if it does not detect an active network request and the network management timeout timer expires, the node enters the pre-sleep mode. When a node is in pre-sleep mode, it no longer receives active or passive wake-up requests and the timer expires. If the expected dwell time is less than a certain preset value, the node enters light sleep mode; if the expected dwell time is greater than a certain preset value, the node enters deep sleep mode.

3. The network management method based on AUTOSAR improvement according to claim 1, characterized in that, When a node enters the fast transmission state, it starts a counter. When the counter reaches zero, the node enters the normal transmission state and waits for a certain period of time before sending network management messages at a normal cycle.

4. The network management method based on AUTOSAR improvement according to claim 1, characterized in that, When a node is in normal operation or in a sleep-ready state, if it receives a network management message requesting a location for a duplicate message, the node enters the duplicate message state.

5. The network management method based on AUTOSAR improvement according to claim 1, characterized in that, When a node is in normal operation, if it releases all network requests and no longer needs to actively request the network, the node immediately enters a sleep-ready state and immediately stops sending network management messages.

6. The network management method based on AUTOSAR improvement according to claim 2, characterized in that, When a node is in pre-sleep mode, if it detects an active wake-up request, the node enters a fast-sending state with repeated message state. When a node is in pre-sleep mode, if a passive wake-up request is detected, the node enters the normal sending state of repeating messages.

7. The network management method based on AUTOSAR improvement according to claim 1, characterized in that, The fault detection status is introduced into a dynamically updated network management table in the network management interface module. The network management table includes three key fields: node ID, time interval, and fault counter. The node ID is used to uniquely identify each node, the time interval is used to record the longest interval at which each node should send a message, and the fault counter is used to accumulate the number of times a node fails to send a message on time. When the value of the fault counter exceeds a preset value, the node is determined to be in a fault state.

8. A computer-readable storage medium, characterized in that, It contains a computer program, which, when called by the motor controller, implements the AUTOSAR-based improved network management method as described in any one of claims 1-7.

Images