A vehicle network management system, method, and vehicle

Abstract

The application provides a vehicle network management system and method and a vehicle, and relates to the technical field of vehicle control. The application starts a preset identification window in response to a wake-up event triggered by a communication interface module; analyzes and determines CAN messages received through the communication interface module within the identification window; if it is determined that there is a network management message meeting a preset effective PN condition, the wake-up event is determined to be an expected PN wake-up, and the electronic control unit is controlled to enter and maintain a normal working state; if it is determined that there is no network management message meeting the preset effective PN condition, the wake-up event is determined to be an unexpected PN wake-up, and the electronic control unit is controlled to return to a sleep state, so that the PN wake-up function is reliable, stable and flexible to adapt to different host factory network management protocols, and the hardware cost and system production cost are significantly reduced.

Description

Technical Field

[0001] This invention relates to the field of vehicle control technology, and more specifically, to a vehicle network management system, method, and vehicle. Background Technology

[0002] With the increasing complexity of automotive electronic and electrical architectures, network management based on the Controller Area Network (CAN) bus is crucial for vehicle energy consumption control. Partial Networking (PN) management is an advanced network management strategy that allows only a subset of functionally relevant electronic control units to be activated, rather than the entire network, thereby effectively reducing the vehicle's quiescent current consumption.

[0003] Currently, PN management primarily relies on dedicated CAN transceivers that support hardware PN filtering. These transceivers can directly identify and filter unexpected network management messages at the physical layer, generating a wake-up signal only when the message meets preset PN conditions. The advantage of this approach is that hardware-based filtering offers high reliability and reduces the burden on upper-layer software. However, a significant drawback is that the procurement cost of CAN transceivers supporting hardware PN filtering is far higher than that of general-purpose CAN transceivers that only support arbitrary frame wake-up. During mass production, this unit cost disadvantage will severely weaken the competitiveness of related controllers in the target market. Summary of the Invention

[0004] In view of this, the purpose of the present invention is to overcome the shortcomings of the prior art and provide a vehicle network management system, method and vehicle that realizes a reliable, stable and flexible PN wake-up function that can be adapted to different OEM network management protocols, thereby significantly reducing hardware costs and system production costs.

[0005] In a first aspect, this application provides a vehicle network management system, located in the electronic control unit of a vehicle, the vehicle network management system comprising: The communication interface module is used to connect to the vehicle controller area network bus and does not support hardware local network filtering based on message identifiers. The processing module is connected to the communication interface module. In response to a wake-up event triggered by the communication interface module, the processing module initiates a preset identification window. Within the identification window, it parses and judges the CAN messages received through the communication interface module. If a network management message matching the preset valid PN conditions is detected, the wake-up event is determined to be an expected PN wake-up, and the electronic control unit is controlled to enter and maintain normal operation. If no network management message matching the preset valid PN conditions is detected, the wake-up event is determined to be an unexpected PN wake-up, and the electronic control unit is controlled to return to sleep mode.

[0006] Optionally, the preset valid PN conditions include that the identifier of the network management message is located within the pre-configured set of valid PN message identifiers.

[0007] Optionally, the processing module includes a CAN driver unit and a network management unit. The CAN driver unit includes at least one receiving container with message filtering function. The filtering conditions of the receiving container are determined based on a set of valid PN message identifiers. The network management unit communicates with the CAN driver unit to receive successful reception messages sent by the receiving container and to determine the content of the messages.

[0008] Optionally, the duration of the preset recognition window is determined based on the network management message cycle defined in the vehicle's CAN network.

[0009] Optionally, the duration of the identification window is N times the network management message period, where N is an integer greater than 1.

[0010] Optionally, the duration of the identification window is twice the network management message cycle.

[0011] Optionally, the processing module is also configured to, upon confirmation of an unexpected wake-up, execute a fast power-down sequence to control the electronic control unit to return to a low-power sleep state.

[0012] Optionally, the processing module further includes a CAN interface unit, a CAN status management unit, and a communication management unit; the CAN driver unit establishes a communication channel with the network management unit through the CAN interface unit, the CAN status management unit, and the communication management unit, so that the CAN driver unit can send messages to the network management unit through the communication channel.

[0013] Secondly, this application provides a vehicle network management method, applicable to the processing module in the aforementioned vehicle network management system. The vehicle network management method includes: In response to a wake-up event triggered by the communication interface module, a preset identification window is started; wherein, the communication interface module is located in the vehicle's electronic control unit, is used to connect to the vehicle controller local area network bus, and does not support hardware local network filtering function based on message identifier; Within the identification window, the CAN messages received through the communication interface module are parsed and judged; If a network management message that meets the preset valid PN conditions is found, the wake-up event is determined to be an expected PN wake-up, and the electronic control unit is controlled to enter and maintain normal working state. If it is determined that there is no network management message that meets the preset valid PN conditions, the wake-up event is determined to be an unexpected PN wake-up, and the electronic control unit is controlled to return to the sleep state.

[0014] Thirdly, this application provides a vehicle including the aforementioned vehicle network management system.

[0015] This invention provides a vehicle network management system, method, and vehicle. In response to a wake-up event triggered by a communication interface module, a preset identification window is activated. Within the identification window, CAN messages received through the communication interface module are parsed and evaluated. If a network management message meeting preset valid PN conditions is detected, the wake-up event is determined to be an expected PN wake-up, and the electronic control unit (ECU) is controlled to enter and maintain normal operation. If no network management message meeting preset valid PN conditions is detected, the wake-up event is determined to be an unexpected PN wake-up, and the ECU is controlled to return to sleep mode. This achieves a reliable, stable, and flexibly adaptable PN wake-up function that can adapt to different OEM network management protocols, thereby significantly reducing hardware and system production costs.

[0016] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0017] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present invention and should not be regarded as a limitation on the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 This invention provides a schematic diagram of the structure of a vehicle network management system according to an embodiment of the invention. Figure 2 A schematic diagram illustrating the workflow of the processing module provided in an embodiment of the present invention is shown; Figure 3 A flowchart illustrating a vehicle network management method provided by an embodiment of the present invention is shown; Figure 4 A schematic diagram of the structure of an electronic device provided in an embodiment of the present invention is shown. Detailed Implementation

[0019] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. The components of the embodiments of the present invention described and shown in the accompanying drawings can generally be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present invention provided in the accompanying drawings is not intended to limit the scope of the claimed invention, but merely to illustrate selected embodiments of the invention. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without inventive effort are within the scope of protection of the present invention.

[0020] This application provides a vehicle network management system, see below. Figure 1 As shown in the embodiment of this application, the vehicle network management system is located in the vehicle's electronic control unit. The vehicle network management system includes a communication interface module 110 and a processing module 120. The communication interface module 110 is used to connect to the vehicle controller local area network bus and does not support hardware local network filtering based on message identifiers. The processing module 120 is communicatively connected to the communication interface module 110. The processing module 120 is used to start a preset identification window in response to a wake-up event triggered by the communication interface module. Within the identification window, the CAN message received through the communication interface module 110 is parsed and judged. If it is determined that there is a network management message that meets the preset valid PN conditions, the wake-up event is determined to be an expected PN wake-up, and the electronic control unit is controlled to enter and maintain a normal working state. If it is determined that there is no network management message that meets the preset valid PN conditions, the wake-up event is determined to be an unexpected PN wake-up, and the electronic control unit is controlled to return to a sleep state.

[0021] In this embodiment of the application, the vehicle network management system is located in the vehicle's electronic control unit. The vehicle network management system includes a communication interface module 110 and a processing module 120. The communication interface module is used to connect to the vehicle controller local area network bus, and the CAN transceiver used does not have a hardware local network filtering function based on message identifiers, that is, it does not support the direct filtering of network management messages with a specific message identifier range through hardware to achieve PN wake-up. The processing module 120 is communicatively connected to the communication interface module 110 and is used to perform logic judgment and control after wake-up. When any CAN message appears on the vehicle controller local area network bus, the communication interface module will detect the activity on the vehicle controller local area network bus and trigger a wake-up event, thereby waking up the power supply module of the electronic control unit and causing the processing module to start running. After the processing module is woken up, it first starts a recognition window of a preset duration. During the recognition window, the processing module continuously listens to the bus through the communication interface module and parses each frame of CAN message received. If the processing module parses at least one frame of CAN message within the recognition window that meets the preset valid PN condition range, it is determined that this wake-up is caused by the expected network management activity, that is, it is determined to be an expected PN wake-up. Subsequently, the processing module will control the electronic control unit to complete the complete initialization process and start all periodic software tasks to enable the system to enter and maintain a normal working state and respond to subsequent bus communication. If the processing module fails to parse any frame of CAN message that meets the valid PN condition within the entire recognition window duration, it is determined that this wake-up is an unexpected event, such as being caused by bus noise or irrelevant communication, that is, it is determined to be an unexpected PN wake-up. At this point, after the initialization process is complete, the processing module will control the electronic control unit to perform a fast power-down process, causing it to re-enter a low-power sleep state and wait for the next bus activity to trigger a new wake-up event.

[0022] By employing a general-purpose CAN transceiver without hardware PN filtering capabilities, and combining it with a multi-layered software architecture for message identification and status management, hardware costs are significantly reduced, eliminating the need to purchase dedicated high-priced transceivers and enhancing the product's competitiveness in cost-effective application scenarios. The vehicle network management system provided in this application embodiment, by setting an identification window with time redundancy, provides sufficient waiting time for receiving valid network management messages, effectively preventing the missed detection of expected wake-up due to bus delays or occasional message loss. This enhances the system's robustness and reliability in uncertain bus environments, and achieves multiple beneficial effects of cost control, flexible adaptation, and system reliability while ensuring the stable and accurate implementation of network management wake-up functions.

[0023] In one optional embodiment, the preset valid PN condition includes that the identifier of the network management message is located within a pre-configured set of valid PN message identifiers.

[0024] In this embodiment of the application, the preset valid PN condition is specifically as follows: the identifier of the network management message must be located within a pre-configured set of valid PN message identifiers; wherein, the set of valid PN message identifiers is usually defined by the vehicle manufacturer according to its network management specifications, and is represented as one or more consecutive message identifier ranges.

[0025] When the processing module performs message determination, it compares the received CAN message identifier with a pre-configured set of valid PN message identifiers. If the CAN message identifier belongs to a value in the set of valid PN message identifiers, the CAN message is determined to be a network management message that meets the preset valid PN conditions; otherwise, it is determined to be a message that does not meet the conditions. By pre-configuring the set of valid PN message identifiers, the determination criteria for valid wake-up messages are clear, configurable, and can adapt to the specific protocol requirements of different vehicle manufacturers.

[0026] In an optional embodiment, the processing module 120 includes a CAN driver unit 121 and a network management unit 125. The CAN driver unit 121 includes at least one receiving container with message filtering function. The filtering conditions of the receiving container are determined based on a set of valid PN message identifiers. The network management unit 125 is communicatively connected to the CAN driver unit 121 and is used to receive messages sent by the receiving container that have been successfully received and to determine the content of the messages.

[0027] In one optional embodiment, the duration of the preset identification window is determined based on the network management message cycle defined in the vehicle's CAN network.

[0028] Furthermore, the duration of the identification window is N times the network management message period, where N is an integer greater than 1.

[0029] Furthermore, the duration of the identification window is twice the network management message cycle.

[0030] In this application implementation, the processing module 120 includes a CAN driver unit 121 and a network management unit 125. The CAN driver unit 121 includes at least one receiving container with message filtering function. The filtering conditions of the receiving container are configured according to the set of valid PN message identifiers, so that the receiving container only receives and stores CAN messages whose identifiers fall within the set of valid PN message identifiers at the hardware level or the underlying driver level, while ignoring messages whose identifiers are not in the set. The network management unit 125 is communicatively connected to the CAN driver unit 121 and is used to obtain successfully received messages from the receiving container and further parse and logically determine the content of the messages. By setting up a receiving container with targeted filtering function, preliminary screening can be performed at the initial stage of bus message arrival, reducing the number of irrelevant messages transmitted to the upper-layer module, thereby reducing the processing load of the network management unit and improving the determination efficiency. The preset recognition window duration is not a fixed value, but is dynamically determined based on the network management message cycle explicitly defined in the vehicle CAN network, to ensure that the recognition window can cover sufficient network management activity time to adapt to the rhythm of network communication; The duration of the identification window is specifically set to an integer multiple of the network management message period, and this multiple is greater than 1. In this application, setting the window duration to a multiple of the period provides temporal redundancy, ensuring that even if there are slight jitters in the network timing or the message in a certain period is accidentally lost, the vehicle network management system still has sufficient opportunity to capture valid network management messages in subsequent periods, thereby avoiding the expected wake-up being incorrectly judged as unexpected due to occasional communication problems; In practical implementation, the duration of the identification window is preferably set to twice the network management message cycle. This ensures a good balance between a sufficient identification success rate and avoiding unnecessary power consumption increases in unexpected wake-up states due to an excessively long window, thus achieving a practical identification window setting scheme that takes into account reliability, response speed, and power consumption control.

[0031] In an alternative embodiment, the processing module 120 is further configured to, upon confirmation of an unexpected wake-up, execute a fast power-down sequence to control the electronic control unit to return to a low-power sleep state.

[0032] In this embodiment of the application, after confirming the occurrence of an unexpected wake-up event, the processing module 120 executes a fast power-down sequence to control the electronic control unit to return to a low-power sleep state. The fast power-down sequence includes a series of ordered operation steps, such as stopping periodic software tasks, turning off unnecessary on-chip peripherals, saving the controller state to a low-power retention memory, and finally issuing an instruction to the power management module to enter sleep mode.

[0033] By executing a predefined sequence, the vehicle network management system can quickly and orderly cut off power to unnecessary functions and save necessary context after determining an invalid wake-up. This minimizes the additional power consumption generated during unexpected wake-ups and ensures that the controller can safely and quickly re-enter a stable sleep state, waiting for the next valid bus activity to trigger. This effectively improves the overall energy efficiency and reliability of the vehicle network management system in complex bus environments.

[0034] In an optional embodiment, the processing module 120 further includes a CAN interface unit 122, a CAN status management unit 123, and a communication management unit 124; the CAN driver unit 121 establishes a communication channel with the network management unit 125 through the CAN interface unit 122, the CAN status management unit 123, and the communication management unit 124, so that the CAN driver unit 121 can send messages to the network management unit 125 through the communication channel.

[0035] In this embodiment, the processing module 120 is used to implement message transmission and status management. The processing module 120 includes a CAN driver unit 121, a CAN interface unit 122, a CAN status management unit 123, and a communication management unit 124. The CAN driver unit 121 interacts directly with the communication interface module 110 and is responsible for sending and receiving messages at the lower level (e.g., microcontroller, CAN transceiver, CAN driver unit, and external power management chip). It is also configured with an independent message receiving mailbox, which is set to only receive CAN messages whose identifiers fall within the preset valid PN condition range. This achieves preliminary filtering of network management messages at the software layer (i.e., the CAN interface unit, CAN status management unit, and communication management unit). The CAN interface unit 122 is connected to the CAN driver unit 121 and is responsible for transmitting the messages received by the driver layer to the upper layer (i.e., the application layer that implements specific vehicle control functions). The CAN interface unit has established a receiving channel corresponding to the network management function and is associated with a specific mailbox of the CAN driver layer. The CAN status management unit 123 is connected to the CAN interface unit 122, and is responsible for managing the communication status of the CAN controller and binding the network management message channel to a specific CAN controller instance; The communication management unit 124 is connected to the CAN status management unit 123 and is responsible for coordinating the status and mode of multiple communication channels and mapping the channels from the CAN status management unit to the user logic channels. In this application, a complete communication channel is established from the CAN driver unit to the network management unit by associating the user logic channel between the network management unit and the communication management unit. When the CAN driver unit receives a message in its dedicated mailbox, the message is transmitted to the network management unit in sequence through the CAN interface unit, the CAN status management unit, and the communication management unit. The network management unit performs the final message validity determination and wake-up logic control. The software layer units are connected and transmit data through predefined interfaces and configurations, and work together to realize the identification, transmission and processing of network management messages through software architecture on transceivers that do not support hardware filtering.

[0036] The processing module provided in this application embodiment can adapt to the different definitions of the effective network management message identifier range of different OEMs by simply adjusting the message identifier filtering range of the receiving mailbox at the CAN driver layer. No changes to the hardware or high-level software architecture are required, so that the solution can flexibly meet diverse customization needs.

[0037] like Figure 2 As shown in the embodiment of this application, the specific working process of the processing module in the vehicle network management system is as follows: The vehicle network management system is initially in a low-power controller mode, i.e., a sleep state. When the communication interface module detects any message activity on the vehicle controller's local area network bus, it triggers a wake-up event, and the controller is then woken up and begins to execute the power-on initialization task. After the initialization process begins, the processing module simultaneously opens a pre-defined identification window. Within this identification window, the vehicle network management system continuously listens for and attempts to receive bus messages through a receiver specifically configured for network management messages. The processing module will determine whether the message successfully transmitted by the network management message receiving container has been received again within this identification window. If the determination result is yes, that is, at least one network management message that meets the preset valid PN conditions has been successfully received within the above specific identification window, the processing module determines that this wake-up is a valid PN wake-up. Subsequently, the vehicle network management system continues to complete the remaining initialization process and starts all periodic task scheduling normally after the initialization is completed, so that the electronic control unit enters and maintains a full-function working state. In the working state, the vehicle network management system will continuously monitor whether there is a valid reason for maintaining wake-up in order to decide whether to maintain or change the subsequent state. If the judgment result is negative, meaning that no network management message matching the preset valid PN condition is successfully received within the entire specific identification window, the processing module determines that this network wake-up is an invalid PN wake-up. At this time, after completing the necessary initialization and cleanup work, the vehicle network management system will not start periodic task scheduling, but will directly execute a fast power-down sequence to control the electronic control unit to return to low-power sleep mode, waiting for the next bus activity to trigger.

[0038] The vehicle network management system provided in this application adopts a general-purpose CAN transceiver without hardware local network filtering function as the communication interface and designs a multi-layer collaborative software processing architecture. This enables a stable and reliable PN network management wake-up function on a low-cost hardware basis. While ensuring the accuracy of network management function, it significantly reduces hardware dependence and cost, and has good configurability to adapt to different customized needs. This improves the robustness and overall energy efficiency of the system in complex vehicle network environments.

[0039] This application provides a vehicle network management method, see below. Figure 3 As shown, the vehicle network management method provided in this application embodiment is applicable to the processing module in the above-mentioned vehicle network management system. The vehicle network management method includes: Step 310: In response to the wake-up event triggered by the communication interface module, start the preset identification window; wherein, the communication interface module is located in the vehicle's electronic control unit, is used to connect to the vehicle controller local area network bus, and does not support hardware local network filtering function based on message identifier; Step 320: Within the identification window, parse and determine the CAN message received through the communication interface module; Step 330: If it is determined that there is a network management message that meets the preset valid PN conditions, then the wake-up event is determined to be the expected PN wake-up, and the electronic control unit is controlled to enter and maintain normal working state. Step 340: If it is determined that there is no network management message that meets the preset valid PN conditions, then the wake-up event is determined to be an unexpected PN wake-up, and the electronic control unit is controlled to return to the sleep state.

[0040] This application provides a vehicle including the aforementioned vehicle network management system.

[0041] It should be noted that the principle of the vehicle network management method provided in this application embodiment to solve the technical problem is similar to that of the vehicle network management system provided in this application embodiment. Therefore, the implementation of the vehicle network management method provided in this application embodiment can refer to the implementation of the vehicle network management system provided in this application embodiment, and the repeated parts will not be described again.

[0042] After introducing the vehicle network management system and method provided in the embodiments of this application, the electronic equipment provided in the embodiments of this application will be briefly introduced next.

[0043] See Figure 4 As shown, the electronic device 500 provided in this application embodiment includes at least a processor 501, a memory 502, and a computer program stored in the memory 502 and executable on the processor 501. When the processor 501 executes the computer program, it implements the vehicle network management method provided in this application embodiment.

[0044] The electronic device 500 provided in this application embodiment may further include a bus 503 connecting different components (including processor 501 and memory 502). The bus 503 represents one or more types of bus structures, including memory bus, peripheral bus, local area bus, etc.

[0045] Memory 502 may include a readable storage medium in the form of volatile memory, such as random access memory (RAM) 5021 and / or cache memory 5022, and may further include read-only memory (ROM) 5023. Memory 502 may also include a program tool 5025 having a set (at least one) of program modules 5024, including but not limited to an operating subsystem, one or more application programs, other program modules, and program data, each or some combination of these examples may include an implementation of a network environment.

[0046] Processor 501 can be a single processing element or a collective term for multiple processing elements. For example, processor 501 can be a central processing unit (CPU) or one or more integrated circuits configured to implement the vehicle network management method provided in the embodiments of this application. Specifically, processor 501 can be a general-purpose processor, including but not limited to CPUs, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.

[0047] Electronic device 500 can communicate with one or more external devices 504 (e.g., keyboard, remote control, etc.), and also with one or more devices that enable a user to interact with electronic device 500 (e.g., mobile phone, computer, etc.), and / or with devices that enable electronic device 500 to communicate with one or more other electronic devices 500 (e.g., router, modem, etc.). This communication can be performed through input / output (I / O) interface 505. Furthermore, electronic device 500 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) through network adapter 506. Figure 4 As shown, network adapter 506 communicates with other modules of electronic device 500 via bus 503. It should be understood that, although... Figure 4 As not shown, other hardware and / or software modules may be used in conjunction with the electronic device 500, including but not limited to microcode, device drivers, redundant processors, external disk drive arrays, Redundant Arrays of Independent Disks (RAID) subsystems, tape drives, and data backup storage subsystems.

[0048] It should be noted that, Figure 4 The electronic device 500 shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0049] The computer-readable storage medium provided in the embodiments of this application is described below. The computer-readable storage medium provided in the embodiments of this application stores computer instructions, which, when executed by a processor, implement the vehicle network management method provided in the embodiments of this application. Specifically, the computer instructions can be built into or installed in a processor, so that the processor can implement the vehicle network management method provided in the embodiments of this application by executing the built-in or installed computer instructions.

[0050] In addition, the vehicle network management method provided in this application embodiment can also be implemented as a computer program product, which includes program code. The program code implements the vehicle network management method provided in this application embodiment when it is run on a processor.

[0051] The computer program product provided in this application embodiment may employ one or more computer-readable storage media, which may be, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination thereof. Specifically, more specific examples (a non-exhaustive list) of computer-readable storage media include electrical connections with one or more wires, portable disks, hard disks, RAM, ROM, erasable programmable read-only memory (EPROM), optical fibers, portable compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0052] The computer program product provided in this application embodiment can be a CD-ROM and include program code, and can also run on electronic devices such as computers. However, the computer program product provided in this application embodiment is not limited thereto. In this application embodiment, the computer-readable storage medium can be any tangible medium that contains or stores program code, which can be used by or in conjunction with an instruction execution system, device, or apparatus.

[0053] It should be noted that although several units or sub-units of the device have been mentioned in the detailed description above, this division is merely exemplary and not mandatory. In fact, according to embodiments of this application, the features and functions of two or more units described above can be embodied in one unit. Conversely, the features and functions of one unit described above can be further divided and embodied by multiple units.

[0054] Furthermore, although the operations of the method of this application are described in a specific order in the accompanying drawings, this does not require or imply that these operations must be performed in that specific order, or that all the operations shown must be performed to achieve the desired result. Additionally or alternatively, certain steps may be omitted, multiple steps may be combined into one step, and / or one step may be broken down into multiple steps.

[0055] Although preferred embodiments of this application have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of this application.

[0056] Obviously, those skilled in the art can make various modifications and variations to the embodiments of this application without departing from the spirit and scope of the embodiments of this application. Therefore, if these modifications and variations to the embodiments of this application fall within the scope of the claims of this application and their equivalents, this application also intends to include these modifications and variations.

Claims

1. A vehicle network management system, installed in the vehicle's electronic control unit, characterized in that, include: The communication interface module is used to connect to the vehicle controller area network bus and does not support hardware local network filtering based on message identifiers. The processing module is communicatively connected to the communication interface module; the processing module is used to start a preset identification window in response to a wake-up event triggered by the communication interface module; within the identification window, the CAN message received through the communication interface module is parsed and judged. If a network management message that meets the preset valid PN conditions is found, the wake-up event is determined to be an expected PN wake-up, and the electronic control unit is controlled to enter and maintain a normal working state; if a network management message that meets the preset valid PN conditions is found to be an unexpected PN wake-up, the electronic control unit is controlled to return to a sleep state.

2. The vehicle network management system according to claim 1, characterized in that, The preset valid PN condition includes that the identifier of the network management message is located within the pre-configured set of valid PN message identifiers.

3. The vehicle network management system according to claim 2, characterized in that, The processing module includes a CAN driver unit and a network management unit. The CAN driver unit includes at least one receiving container with message filtering function. The filtering conditions of the receiving container are determined based on the set of valid PN message identifiers. The network management unit is communicatively connected to the CAN driver unit and is used to receive a successful reception message sent by the receiving container and to determine the content of the message.

4. The vehicle network management system according to claim 1, characterized in that, The duration of the preset recognition window is determined based on the network management message cycle defined in the vehicle's CAN network.

5. The vehicle network management system according to claim 4, characterized in that, The duration of the identification window is N times the period of the network management message, where N is an integer greater than 1.

6. The vehicle network management system according to claim 4, characterized in that, The duration of the identification window is twice the period of the network management message.

7. The vehicle network management system according to any one of claims 1 to 3, characterized in that, The processing module is also configured to, upon confirming an unexpected wake-up, execute a rapid power-down sequence to control the electronic control unit to return to a low-power sleep state.

8. The vehicle network management system according to claim 3, characterized in that, The processing module further includes a CAN interface unit, a CAN status management unit, and a communication management unit; the CAN driver unit establishes a communication channel with the network management unit through the CAN interface unit, the CAN status management unit, and the communication management unit, so that the CAN driver unit can send the message to the network management unit through the communication channel.

9. A vehicle network management method, characterized in that, The method, applicable to a processing module in a vehicle network management system as described in any one of claims 1 to 8, comprises: In response to a wake-up event triggered by the communication interface module, a preset identification window is started; wherein, the communication interface module is located in the vehicle's electronic control unit, is used to connect to the vehicle controller local area network bus, and does not support hardware local network filtering function based on message identifier; Within the identification window, the CAN messages received through the communication interface module are parsed and judged; If a network management message that meets the preset valid PN conditions is found, the wake-up event is determined to be an expected PN wake-up, and the electronic control unit is controlled to enter and maintain normal working state. If it is determined that there is no network management message that meets the preset valid PN conditions, the wake-up event is determined to be an unexpected PN wake-up, and the electronic control unit is controlled to return to the sleep state.

10. A vehicle, characterized in that, The vehicle network management system includes any one of claims 1 to 8.

Images