A vehicle communication network system, a vehicle control method, and a storage medium.

Abstract

This invention relates to the field of automotive electronics technology, and more particularly to a vehicle communication network system, a vehicle control method, and a storage medium. The system includes: at least one service controller, an engine compartment domain controller, a body domain controller, and a chassis domain controller, as well as domain nodes corresponding to the engine compartment domain controller, body domain controller, and chassis domain controller respectively; the engine compartment domain controller, body domain controller, and chassis domain controller are connected to at least one service controller via a first bus to form a first backbone network; the engine compartment domain controller, body domain controller, and chassis domain controller are each connected to their corresponding domain nodes via a second bus to form a second backbone network. Using the above vehicle communication network system can solve the problems of slow transmission rate, high packet loss rate, poor reliability, and susceptibility to interference in existing vehicle communication network systems, improving the accuracy and speed of data transmission and meeting the network requirements of the entire vehicle.

Description

Technical Field

[0001] This invention relates to the field of automotive electronics technology, and in particular to a vehicle communication network system, a vehicle control method, and a storage medium. Background Technology

[0002] In recent years, with the deepening development of vehicle electrification, intelligence, connectivity, and sharing, automotive electronic and electrical architecture is undergoing a transformation from distributed to domain controller-based architecture, with the number of Electronic Control Units (ECUs) continuously decreasing. Based on the vehicle's business functions, the entire vehicle can be divided into engine compartment domain controllers, body domain controllers, chassis domain controllers, and several business controllers. Through network communication between these domain controllers, the corresponding business functions of the vehicle are realized.

[0003] With the rapid development of autonomous driving, new energy and intelligent connected technologies in the automotive field, traditional vehicle communication network systems based on Controller Area Network (CAN) / Local Interconnect Network (LIN) buses have drawbacks such as slow transmission rate, high packet loss rate, poor reliability and susceptibility to interference. Therefore, there is an urgent need for a vehicle communication network system to solve the above defects and meet the network requirements of the whole vehicle. Summary of the Invention

[0004] This invention provides a vehicle communication network system, a vehicle control method, and a storage medium to solve the problems of slow transmission rate, high packet loss rate, poor reliability, and susceptibility to interference in existing vehicle communication network systems.

[0005] According to one aspect of the present invention, a vehicle communication network system is provided, the system comprising:

[0006] At least one business controller, engine compartment domain controller, body domain controller, chassis domain controller, and domain nodes corresponding to the engine compartment domain controller, body domain controller, and chassis domain controller respectively;

[0007] The engine compartment domain controller, body domain controller, and chassis domain controller are connected to at least one service controller via a first bus to form a first backbone network;

[0008] The engine compartment domain controller, body domain controller, and chassis domain controller are connected to their respective domain nodes via a second bus to form a second backbone network.

[0009] According to another aspect of the present invention, a vehicle control method is provided, applied to a vehicle communication network system, the method comprising:

[0010] The control business controller issues vehicle control commands, which are then sent via the first bus to at least one of the engine compartment domain controller, body domain controller, and chassis domain controller.

[0011] Control the nodes within the target domain of the corresponding engine compartment domain controller, body domain controller, and chassis domain controller to execute vehicle control commands.

[0012] According to another aspect of the present invention, a computer-readable storage medium is provided, the computer-readable storage medium storing computer instructions for causing a processor to execute and implement the vehicle control method according to any embodiment of the present invention.

[0013] This invention provides a vehicle communication network system in which an engine compartment domain controller, a body domain controller, and a chassis domain controller are connected to at least one service controller via a first bus to form a first backbone network; the engine compartment domain controller, body domain controller, and chassis domain controller are each connected to corresponding nodes within their respective domains via a second bus to form a second backbone network. This vehicle communication network system solves the problems of slow transmission rate, high packet loss rate, poor reliability, and susceptibility to interference found in existing vehicle communication network systems, improving the accuracy and speed of data transmission and meeting the network requirements of the entire vehicle.

[0014] 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

[0015] 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.

[0016] Figure 1 This is a schematic diagram of a vehicle communication network system according to Embodiment 1 of the present invention;

[0017] Figure 2 This is a schematic diagram of a vehicle communication network system according to Embodiment 2 of the present invention;

[0018] Figure 3 This is a schematic diagram of an Ethernet communication design architecture provided according to Embodiment 2 of the present invention;

[0019] Figure 4 This is a schematic diagram of an Ethernet power supply scheme provided according to Embodiment 2 of the present invention;

[0020] Figure 5 This is a flowchart of a vehicle control method provided according to Embodiment 3 of the present invention;

[0021] Figure 6 This is a flowchart of a vehicle control method provided in Embodiment 4 of the present invention;

[0022] Figure 7 This is a flowchart of a vehicle control method provided in Embodiment 5 of the present invention;

[0023] Figure 8 This is a flowchart of a vehicle control method provided in Embodiment Six of the present invention;

[0024] Figure 9 This is a schematic diagram of a CAN circuit according to Embodiment Six of the present invention. Detailed Implementation

[0025] 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.

[0026] It should be noted that the terms "first," "second," 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 the 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.

[0027] Example 1

[0028] Figure 1 This is a schematic diagram of a vehicle communication network system provided in Embodiment 1 of the present invention. Figure 1As shown, the vehicle communication network system includes: at least one service controller, an engine compartment domain controller, a body domain controller, a chassis domain controller, and domain nodes corresponding to the engine compartment domain controller, body domain controller, and chassis domain controller, respectively; wherein, the engine compartment domain controller, body domain controller, and chassis domain controller are connected to at least one service controller via a first bus to form a first backbone network; the engine compartment domain controller, body domain controller, and chassis domain controller are connected to their respective domain nodes via a second bus to form a second backbone network.

[0029] In this embodiment of the invention, the service controller can be understood as a region controller divided based on the vehicle's business functions. The service controller may include: a powertrain domain core controller, an advanced automated driving domain controller, a cockpit domain controller, etc. The engine compartment domain controller can refer to a region controller used to control vehicle control functions such as the engine, inertial navigation, redundant braking, and power steering. The body domain controller can refer to a region controller used to control vehicle control functions such as the lighting system, central locking, low-frequency antenna, digital key, and gateway. The chassis domain controller can refer to a region controller used to control vehicle braking, steering, suspension, and other lateral, longitudinal, and vertical control functions. Intra-domain nodes can be understood as controllers used to control the vehicle to achieve specific business functions. These intra-domain nodes can be controlled by corresponding engine compartment domain controllers, body domain controllers, and chassis domain controllers. For example, intra-domain nodes corresponding to the engine compartment domain controller may include: front motor control unit, integrated inertial navigation system, redundant brake control unit, power steering system, etc.; intra-domain nodes corresponding to the body domain controller may include: combination switch, digital key, RF transceiver, right front door controller, etc.; and intra-domain nodes corresponding to the chassis domain controller may include: rear taillight system, rear motor control unit, power amplifier system, charger system, etc. The first bus can refer to the bus used for communication between the engine compartment domain controller, body domain controller, and chassis domain controller and the business controller. The first bus can include: Controller Area Network (CAN) bus, Variable Rate Controller Area Network (CAN with flexible data rate, CAN FD) bus, in-vehicle Ethernet, etc. The first backbone network can refer to the vehicle communication network formed by the engine compartment domain controller, body domain controller, and chassis domain controller and the business controller via the first bus. The second bus can refer to the bus used for communication connections between the engine compartment domain controller, body domain controller, and chassis domain controller and their corresponding nodes within the domain. The second bus can include: CAN bus, CAN FD bus, automotive Ethernet, etc. The second backbone network can refer to the vehicle communication network formed by the engine compartment domain controller, body domain controller, and chassis domain controller and their corresponding nodes within the domain via the second bus.

[0030] Specifically, in the vehicle communication network system proposed in Embodiment 1 of this invention, the entire vehicle can be divided into three intelligent area controllers: an engine compartment domain controller, a body domain controller, and a chassis domain controller. At least one service controller is also defined based on the vehicle's business functions. Simultaneously, the engine compartment domain controller, body domain controller, and chassis domain controller can each control one or more nodes within their respective domains. These nodes can be used to control the vehicle to perform specific business functions, such as power steering control, right front door control, and rear motor control. The engine compartment domain controller, body domain controller, and chassis domain controller, along with the service controllers, form a first backbone network via a first bus. The engine compartment domain controller, body domain controller, and chassis domain controller, along with their corresponding nodes within their domains, form a second backbone network via a second bus. The first and second buses can include CAN bus, CAN FD bus, and in-vehicle Ethernet, among others.

[0031] This invention provides a vehicle communication network system in which an engine compartment domain controller, a body domain controller, and a chassis domain controller are connected to at least one service controller via a first bus to form a first backbone network; the engine compartment domain controller, body domain controller, and chassis domain controller are each connected to corresponding nodes within their respective domains via a second bus to form a second backbone network. This vehicle communication network system solves the problems of slow transmission rate, high packet loss rate, poor reliability, and susceptibility to interference found in existing vehicle communication network systems, improving the accuracy and speed of data transmission and meeting the network requirements of the entire vehicle.

[0032] Example 2

[0033] Figure 2 This is a schematic diagram of a vehicle communication network system provided in Embodiment 2 of the present invention. It is further optimized and expanded based on the above embodiments and can be combined with various optional technical solutions in the above embodiments. For example... Figure 2 As shown in Embodiment 2 of the present invention, a vehicle communication network system includes: three service controllers: a power domain core controller, an advanced autonomous driving domain controller, and a cockpit domain controller; three intelligent area controllers: an engine compartment domain controller, a body domain controller, and a chassis domain controller; and corresponding nodes within the engine compartment domain controller: a front motor control unit, a combined inertial navigation system, a redundant braking control unit, and a steering assist system; corresponding nodes within the body domain controller: a combination switch, a digital key, a radio frequency transceiver, and a right front door controller; and corresponding nodes within the chassis domain controller: a rear taillight system, a rear motor control unit, a power amplifier system, and a charger system.

[0034] Specifically, the engine compartment domain controller, body domain controller, and chassis domain controller communicate with each other via a first controller LAN bus and / or a first variable rate controller LAN bus. The engine compartment domain controller, body domain controller, and chassis domain controller also communicate with their respective intra-domain nodes via a second controller LAN bus and / or a second variable rate controller LAN bus. Furthermore, the engine compartment domain controller also has a 100base-T1 Ethernet communication connection with the powertrain domain core controller and the advanced autonomous driving domain controller; the body domain controller also has a 100base-T1 Ethernet communication connection with the advanced autonomous driving domain controller and the cockpit domain controller; the body domain controller also has a 100base-T1 Ethernet communication connection with the cockpit domain controller; and the chassis domain controller also has a 100base-T1 Ethernet communication connection with the powertrain domain core controller.

[0035] In this embodiment of the invention, the first Controller Area Network (CAN) bus and the first Variable Rate Controller Area Network (CAN FD) bus can refer to the CAN bus and CAN FD bus that enable communication between the engine compartment domain controller, body domain controller, and chassis domain controller and the powertrain domain core controller, advanced autonomous driving domain controller, and cockpit domain controller, respectively. The second Controller Area Network (CAN) bus and the second Variable Rate Controller Area Network (CAN FD) bus can refer to the CAN bus and CAN FD bus that enable communication between the engine compartment domain controller, body domain controller, and chassis domain controller and their corresponding nodes within the domain. 100base-T1 Ethernet and 100base-T1 Ethernet can refer to 100Mbps automotive Ethernet and 1Gbps automotive Ethernet, respectively.

[0036] Specifically, in the vehicle communication network system proposed in Embodiment 2 of this invention, the entire vehicle can be divided into three intelligent area controllers: an engine compartment domain controller, a body domain controller, and a chassis domain controller. Based on the vehicle's business functions, three business controllers are also defined: a powertrain domain core controller, an advanced autonomous driving domain controller, and a cockpit domain controller. The engine compartment domain controller, body domain controller, and chassis domain controller communicate with each other via a first CAN bus and / or a first CAN FD bus. The engine compartment domain controller, body domain controller, and chassis domain controller communicate with their respective intra-domain nodes via a second CAN bus and / or a second CAN bus. The FD bus is used for communication. To meet the higher network requirements of each intelligent area controller, the engine compartment domain controller can also include a 100base-T1 Ethernet communication connection with the powertrain domain core controller and the advanced autonomous driving domain controller, respectively. The body domain controller can also include a 100base-T1 Ethernet communication connection with the advanced autonomous driving domain controller and the cockpit domain controller, respectively. In addition, since the data volume of network communication between the body domain controller and the cockpit domain controller is large, a 1000base-T1 Ethernet communication connection can also be included between the body domain controller and the cockpit domain controller. The chassis domain controller can also include a 100base-T1 Ethernet communication connection with the powertrain domain core controller.

[0037] Figure 3 This is a schematic diagram of an Ethernet communication design architecture provided in Embodiment 2 of the present invention. Figure 3As shown, the Media Access Control (MAC) pins of the microcontroller unit (MCU) in each domain node can be reserved in the following two ways: Option 1: Use a single 100base-T1 to connect to the microcontroller via a Reduced Media Independent Interface (RMII); Option 2: Connect an Ethernet switch chip externally via a Reduced Gigabit Media Independent Interface (RGMII), using the five 100Mbps Physical Layer (PHY) interfaces integrated within the switch chip for communication, and connect a gigabit PHY externally via the Serial Gigabit Media Independent Interface (SGMII) of the switch chip for big data transmission. The boot program of the Ethernet switch chip is stored in the FLASH memory connected via the Queued Serial Peripheral Interface (QSPI).

[0038] Furthermore, based on the above embodiments of the invention, the engine compartment domain controller, body domain controller, and chassis domain controller in the embodiments of the present invention are all 3.3V single-chip microcomputer control systems, wherein the 3.3V single-chip microcomputer control system can adopt a 25MHz single-chip microcomputer minimum system design.

[0039] Furthermore, based on the above embodiments, to facilitate fault location of the engine compartment domain controller, body domain controller, and chassis domain controller, the power supply for the Ethernet section can be independent of the power management integrated circuit (PMIC) and the system base chip (SBC). Since the system does not require Ethernet communication in sleep mode, the power supply design can be divided according to the chip's pin requirements, as follows: Figure 4 The five components shown are used to implement a sleep / wake-up scheme based on Ethernet power.

[0040] This invention provides a vehicle communication network system in which the engine compartment domain controller, body domain controller, and chassis domain controller are respectively connected to the powertrain domain core controller, advanced autonomous driving domain controller, and cockpit domain controller via a first controller local area network (LAN) bus and / or a first variable rate controller local area network (VRF) bus. The engine compartment domain controller, body domain controller, and chassis domain controller are respectively connected to their corresponding intra-domain nodes via a second controller local area network (LAN) bus and / or a second variable rate controller local area network (VRF) bus. The engine compartment domain controller also includes a 100base-T1 Ethernet communication connection with the powertrain domain core controller and the advanced autonomous driving domain controller. The body domain controller also includes a 100base-T1 Ethernet communication connection with the advanced autonomous driving domain controller and the cockpit domain controller, and a 1000base-T1 Ethernet communication connection with the cockpit domain controller. The chassis domain controller also includes a 100base-T1 Ethernet communication connection with the powertrain domain core controller. By adopting the above vehicle communication network system, the problems of slow transmission rate, high packet loss rate, poor reliability and susceptibility to interference in the existing vehicle communication network system can be solved, the accuracy and speed of data transmission can be improved, and the network requirements of the whole vehicle can be met.

[0041] Example 3

[0042] Figure 5 This is a flowchart of a vehicle control method provided in Embodiment 3 of the present invention. This embodiment is applicable to situations where vehicles are controlled, and this vehicle control method can be applied to vehicle communication network systems. Figure 5 As shown, the vehicle control method provided in Embodiment 3 of the present invention specifically includes the following steps:

[0043] S310, the control business controller issues vehicle control commands, which are sent via the first bus to at least one of the engine compartment domain controller, body domain controller, and chassis domain controller.

[0044] Among them, vehicle control commands can refer to commands used to control the vehicle to perform a specific operation. Vehicle control commands can include: vehicle braking commands, vehicle steering commands, sleep / wake commands, etc.

[0045] In this embodiment of the invention, the service controller in the vehicle communication network system can be controlled to issue vehicle control commands, and these commands can be sent to at least one of the engine compartment domain controller, body domain controller, and chassis domain controller via a first bus. In a specific embodiment, taking the vehicle's parking brake as an example, the power domain core controller in the service controller can be controlled to issue vehicle control commands for parking brake, and these commands can be sent to the chassis domain controller via the first bus.

[0046] It is understood that the vehicle control commands in this embodiment of the invention can be issued by the business controller as an example only. In actual applications, they can also be issued by devices such as host computers and industrial control computers. This embodiment of the invention does not limit this.

[0047] S320 controls the execution of vehicle control commands by the nodes within the target domains of the corresponding engine compartment domain controller, body domain controller, and chassis domain controller.

[0048] In this context, a node within the target domain can refer to a node within the domain used to execute vehicle control commands.

[0049] In this embodiment of the invention, after at least one of the engine compartment domain controller, body domain controller, and chassis domain controller detects a vehicle control command via a first bus, it can forward the vehicle control command to the corresponding node in the target domain via a second bus, thereby controlling the node in the target domain to execute the vehicle control command. In a specific embodiment, continuing with the above-mentioned vehicle parking brake as an example, after the chassis domain controller detects a vehicle control command for parking brake via the first bus, it can forward the vehicle control command to the node in the target domain, namely the Electronic Parking Brake (EPB), via the second bus. The EPB then controls the EPB valve installed on the vehicle chassis to operate, controlling the release of parking brake air pressure in the brake chambers of each wheel to achieve vehicle parking brake control.

[0050] The technical solution of this invention involves a control service controller issuing vehicle control commands. These commands are transmitted via a first bus to at least one of the engine compartment domain controller, body domain controller, and chassis domain controller, thereby controlling the nodes within the target domain of the corresponding engine compartment domain controller, body domain controller, or chassis domain controller to execute the vehicle control commands. This invention utilizes a vehicle communication network system to control the service controller to issue vehicle control commands, which in turn control the nodes within the target domain corresponding to the engine compartment domain controller, body domain controller, or chassis domain controller to execute the vehicle control commands. This achieves rapid forwarding and execution of vehicle control commands, improving the execution response speed of the nodes within the target domain.

[0051] Example 4

[0052] Figure 6 This is a flowchart of a vehicle control method provided in Embodiment 4 of the present invention. Based on the above embodiments, this embodiment provides an implementation of the vehicle control method for vehicle control commands including sleep commands, enabling sleep control of nodes within a target domain. Figure 6 As shown, the method includes:

[0053] S410: The control business controller issues a hibernation command, which is sent via the first bus to at least one of the engine compartment domain controller, body domain controller, and chassis domain controller.

[0054] S420: Controls nodes within the target domain to receive sleep commands sent via the second bus.

[0055] S430. When a node in the target domain satisfies the hibernation command, the controller LAN transceiver of the node in the target domain is controlled to enter hibernation mode, thereby controlling the power supply of the node in the target domain to turn off the power output, so that the node in the target domain enters hibernation mode.

[0056] In this embodiment of the invention, the service controller can issue a sleep command to control a node within the target domain to enter a sleep state. After at least one of the engine compartment domain controller, body domain controller, and chassis domain controller detects a vehicle control command via a first bus, it can forward the sleep command to the corresponding node within the target domain via a second bus. When the node within the target domain satisfies the sleep command, for example, when the node currently has no communication needs or no service processes, the Controller Area Network (CAN) transceiver of the node within the target domain can be controlled to enter a sleep state, thereby controlling the power supply of the node within the target domain to shut down, so that the node within the target domain enters a sleep state. In a specific embodiment, when the MCU of the node within the target domain satisfies the sleep command, it controls the CAN transceiver of the node within the domain to enter a sleep state by sending a corresponding SPI command. After the CAN transceiver enters a sleep state, the INH pin of the CAN transceiver will be pulled low, controlling the 5V or 3V power supply to shut down the power supply output, indirectly causing the entire MCU system to process a power-down state, so that the node within the target domain successfully enters a sleep state.

[0057] The technical solution of this invention involves controlling the service controller to issue a hibernation command. This command is transmitted via a first bus to at least one of the engine compartment domain controller, body domain controller, and chassis domain controller. The target domain node receives the hibernation command transmitted via a second bus. When the target domain node satisfies the hibernation command, the controller LAN transceiver of the target domain node enters a hibernation state, thereby shutting down the power output of the target domain node and causing it to enter a hibernation state. This invention, by controlling the target domain node to receive the hibernation command through the vehicle communication network system and then controlling the target domain node to enter a hibernation state, can reduce the power consumption of the domain node and the vehicle battery, thereby increasing the driving range.

[0058] Example 5

[0059] Figure 7This is a flowchart of a vehicle control method provided in Embodiment 5 of the present invention. Based on the above embodiments, this embodiment provides an implementation of the vehicle control method, specifically addressing vehicle control commands including wake-up commands, and is capable of achieving wake-up control of nodes within a target domain. For example... Figure 7 As shown, the method includes:

[0060] S510: The control business controller issues a wake-up command, and the hibernation command is sent to at least one of the engine compartment domain controller, body domain controller, and chassis domain controller via the first bus.

[0061] S520 controls nodes within the target domain to receive wake-up commands sent via the second bus. The wake-up commands include network management messages.

[0062] In this embodiment of the invention, a network management message can refer to a message used to implement network management of nodes within a target domain. The network management message may include information such as: CAN message identifier, CAN FD message identifier, address or identifier of a node within the target domain, and valid wake-up flag.

[0063] S530: The controller LAN transceiver of the node in the target domain parses the network management message to obtain the target identification information.

[0064] The target identification information can refer to the identification information parsed from the network management message. The target identification information can include: CAN message identifier, CAN FD message identifier, etc.

[0065] In this embodiment of the invention, after a node in the target domain listens to a wake-up command via the second bus, it can control the CAN transceiver of the node in the target domain to parse the network management message in the wake-up command and obtain the corresponding target identification information. The target identification information may include, but is not limited to, CAN message identifier, CAN FD message identifier, etc.

[0066] S540 reads the preset wake-up configuration information from the controller LAN transceiver.

[0067] The preset wake-up configuration information can refer to the pre-configured configuration information used to manage the wake-up control of nodes within the target domain. The preset wake-up configuration information can include one or more CAN message identifiers and CAN FD message identifiers, etc. The preset wake-up configuration information can be pre-configured and stored in at least one register of the CAN transceiver.

[0068] In this embodiment of the invention, after a node in the target domain receives a wake-up command, it can read preset wake-up configuration information from the register of the CAN transceiver for subsequent wake-up detection.

[0069] S550: When the target identification information matches the preset wake-up configuration information, the network management message is determined to be a valid wake-up source.

[0070] Valid wake-up sources can include: whether the network management message is a specified CAN message, whether the network management message is a specified CAN FD message, etc.

[0071] In this embodiment of the invention, the parsed target identification information can be matched with the preset wake-up configuration information read from the register to determine whether the network management message is a specified CAN message or a specified CAN FD message. If the match is successful, the network management message is determined to be a valid wake-up source.

[0072] The S560 controller switches the LAN transceiver from sleep mode to standby mode, thereby controlling the normal power output of nodes within the target domain so that the nodes within the target domain can enter a normal state.

[0073] In this embodiment of the invention, when a node in the target domain determines that the received network management message is a valid wake-up source, it can control its CAN transceiver to switch from Sleep state to Standby state, thereby controlling the normal power output of the node in the target domain, so that the node in the target domain enters a normal state. In a specific embodiment, when the CAN transceiver of the node in the target domain is in Sleep state, it is in an extremely low power consumption state, but it will also simultaneously detect whether there is a valid wake-up source in the network; when the CAN transceiver identifies a valid wake-up source, it will automatically switch from Sleep state to Standby state. In Standby state, the INH pin of the CAN transceiver will be pulled high, controlling the normal power output of 5V or 3V, causing the entire MCU system to be powered normally, so that the node in the target domain enters a normal working state from a sleep state.

[0074] The technical solution of this invention involves controlling the service controller to issue a wake-up command. A sleep command is sent via a first bus to at least one of the engine compartment domain controller, body domain controller, and chassis domain controller. The target domain node receives the wake-up command sent via a second bus. The wake-up command includes a network management message. The controller LAN transceiver of the target domain node parses the network management message to obtain target identification information. The controller LAN transceiver reads preset wake-up configuration information. When the target identification information matches the preset wake-up configuration information, the network management message is determined to be a valid wake-up source. The controller LAN transceiver then switches from sleep mode to standby mode, thereby controlling the normal power output of the target domain node to bring it into normal operation. This invention, by controlling the wake-up command of the target domain node through the vehicle communication network system, and thus controlling the target domain node to switch from sleep mode to normal operation, can improve the wake-up speed of the target domain node, enabling it to quickly enter the working state.

[0075] Example 6

[0076] Figure 8 This is a flowchart of a vehicle control method provided in Embodiment Six of the present invention. Based on the above embodiments, this embodiment provides an implementation of the vehicle control method, capable of achieving sleep and wake-up control of nodes within a target domain. For example... Figure 8 As shown, the method includes:

[0077] S610: Power on the MCU of the node in the target domain.

[0078] S620. Determine whether the ECU status manager has identified a valid wake-up source.

[0079] S630 controls the communication manager module to enable communication, the basic software management module to enable control of other basic software modules, and controls the ECU status manager to enter RUN mode.

[0080] In this embodiment of the invention, after determining that the ECU Status Manager (EcuM) has identified a valid wake-up source, it can notify the Communication Manager (ComM) module to start communication, and at the same time notify the Basic Software Management (BswM) module to start the control of other Basic Software (BSW) modules, and control the EcuM to enter RUN mode.

[0081] S640: Control the CAN transceiver to enter Normal state.

[0082] In this embodiment of the invention, after the ComM module enables communication, the CAN transceiver can be controlled to enter the Normal state via SPI communication.

[0083] S650, nodes within the target domain are functioning normally.

[0084] S660. Determine whether the nodes within the target domain meet the hibernation conditions.

[0085] S670: Control the CAN transceiver to enter Sleep mode.

[0086] In this embodiment of the invention, after the MCU of the node in the target domain is powered on, if no valid wake-up source is detected, the power-down process will be directly performed, and the CAN transceiver will be controlled to enter the Sleep state, thereby ultimately controlling the node in the target domain to enter the sleep state. In addition, when the node in the target domain meets the sleep conditions, such as when there are no network management messages in the network, the CAN transceiver will be controlled to enter the Sleep state.

[0087] S680 controls the CAN transceiver to remain in a Sleep state.

[0088] S690. Determine whether the CAN transceiver has identified a valid wake-up source.

[0089] S6100 controls the CAN transceiver to automatically switch to Standby mode.

[0090] In this embodiment of the invention, when the CAN transceiver is in Sleep state, it can synchronously detect the wake-up source set before sleep. If the CAN transceiver recognizes a valid wake-up source, it can control the CAN transceiver to automatically switch to Standby state, thereby controlling the MCU of the node in the target domain to power on, so that the node in the target domain enters the normal working state from the sleep state.

[0091] Furthermore, based on the above embodiments of the invention, each domain node of the vehicle communication network system in these embodiments supports two wake-up methods: specific frame wake-up and arbitrary frame wake-up, and supports a domestically produced MCU 3.3V power supply system. For example... Figure 9As shown, the CAN circuit of the node within the domain can support three wake-up scenarios: First, cold start wake-up, characterized by: the MCU being in a power-down state, some peripheral circuits of the ECU such as the CAN transceiver being powered on, the wake-up event being recognizable by the CAN transceiver, and the CAN transceiver being able to decide whether to wake up the MCU based on the wake-up source; second, CAN channel sleep wake-up, characterized by: the MCU always being in a normal power-on state, at least some peripheral circuits of the ECU being powered on, the CAN transceiver being in a standby state, the wake-up event being recognizable by the CAN transceiver, and the CAN transceiver generating a soft interrupt to wake up the MCU after recognizing a valid wake-up source, or the MCU periodically checking for a valid wake-up source; and third, CAN channel and MCU sleep wake-up, characterized by: the MCU being in a low-power state, at least some peripheral circuits of the ECU being powered on, the CAN transceiver being in a standby state, the wake-up event being recognizable by the CAN transceiver, and the CAN transceiver generating a soft interrupt to wake up the MCU after recognizing a valid wake-up source.

[0092] The technical solution of this invention involves controlling the MCU of the node in the target domain to power on, determining whether the ECU status manager has identified a valid wake-up source, controlling the communication manager module to start communication, controlling the basic software management module to start the control of other basic software modules, controlling the ECU status manager to enter RUN mode, controlling the CAN transceiver to enter Normal state, ensuring the node in the target domain works normally, determining whether the node in the target domain meets the sleep conditions, controlling the CAN transceiver to enter Sleep state, controlling the CAN transceiver to maintain Sleep state, determining whether the CAN transceiver has identified a valid wake-up source, and controlling the CAN transceiver to automatically switch to Standby state.

[0093] This invention, through a vehicle communication network system, controls nodes within the target domain to hibernate and wake up, which can reduce the power consumption of nodes within the domain and the vehicle battery, and shorten the time for nodes within the target domain to wake up to normal operation, enabling nodes within the target domain to respond quickly to demands.

[0094] Example 7

[0095] This invention also provides a storage medium containing computer-executable instructions, which, when executed by a computer processor, are used to perform a vehicle control method, the method comprising:

[0096] The control business controller issues vehicle control commands, which are transmitted via a first bus to at least one of the engine compartment domain controller, body domain controller, and chassis domain controller.

[0097] The system controls the nodes within the target domains corresponding to the engine compartment domain controller, the body domain controller, and the chassis domain controller to execute the vehicle control commands.

[0098] Of course, the computer-executable instructions provided in the embodiments of the present invention are not limited to the method operations described above, but can also perform related operations in the vehicle control method provided in any embodiment of the present invention.

[0099] Based on the above description of the implementation methods, those skilled in the art can clearly understand that the present invention can be implemented using software and necessary general-purpose hardware, and of course, it can also be implemented using hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as a computer floppy disk, read-only memory (ROM), random access memory (RAM), flash memory, hard disk, or optical disk, etc., including several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the vehicle control method described in the various embodiments of the present invention.

[0100] 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.

[0101] 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 vehicle communication network system, characterized in that, The system includes: At least one business controller, engine compartment domain controller, body domain controller, chassis domain controller, and domain nodes corresponding to the engine compartment domain controller, body domain controller, and chassis domain controller respectively; The engine compartment domain controller, the body domain controller, and the chassis domain controller are connected to the at least one service controller via a first bus to form a first backbone network; The engine compartment domain controller, the body domain controller, and the chassis domain controller are respectively connected to the corresponding nodes within the domain via a second bus to form a second backbone network; The engine compartment domain controller, the body domain controller, and the chassis domain controller are respectively connected to the powertrain domain core controller, the advanced autonomous driving domain controller, and the cockpit domain controller through a first controller local area network bus and / or a first variable rate controller local area network bus. The engine compartment domain controller, the body domain controller, and the chassis domain controller are respectively connected to the corresponding nodes within the domain via the second controller LAN bus and / or the second variable rate controller LAN bus. The engine compartment domain controller also includes a 100base-T1 Ethernet communication connection with the power domain core controller and the advanced autonomous driving domain controller. The vehicle domain controller also includes a 100base-T1 Ethernet communication connection with the advanced autonomous driving domain controller and the cockpit domain controller, and the vehicle domain controller also includes a 1000base-T1 Ethernet communication connection with the cockpit domain controller; The chassis domain controller and the power domain core controller also include a 100base-T1 Ethernet communication connection; The power supply for the Ethernet portion is independent of the power management integrated circuit and the power generated by the system base chip.

2. The system according to claim 1, characterized in that, The business controller includes at least one of the following: power domain core controller, advanced autonomous driving domain controller, and cockpit domain controller.

3. The system according to claim 1, characterized in that, The nodes within the engine compartment domain controller include at least one of the following: front motor control unit, combined inertial navigation system, redundant brake control unit, and power steering system. The nodes within the body domain controller include at least one of the following: combination switch, digital key, radio frequency transceiver, and right front door controller. The nodes within the chassis domain controller include at least one of the following: rear taillight system, rear motor control unit, power amplifier system, and charger system.

4. A vehicle control method, applied to the vehicle communication network system as described in any one of claims 1-3, characterized in that, Applied to a vehicle communication network system, the method includes: The control business controller issues vehicle control commands, which are transmitted via a first bus to at least one of the engine compartment domain controller, body domain controller, and chassis domain controller. The system controls the nodes within the target domains corresponding to the engine compartment domain controller, the body domain controller, and the chassis domain controller to execute the vehicle control commands.

5. The method according to claim 4, characterized in that, The vehicle control commands include sleep commands. The control commands are executed by nodes within the target domains of the engine compartment domain controller, the body domain controller, and the chassis domain controller, including: Control the nodes within the target domain to receive the sleep command sent via the second bus; When a node in the target domain satisfies the hibernation command, the controller LAN transceiver of the node in the target domain is controlled to enter a hibernation state, thereby controlling the power supply of the node in the target domain to shut down the power output, so that the node in the target domain enters a hibernation state.

6. The method according to claim 4, characterized in that, The vehicle control command includes a wake-up command. The control commands are executed by nodes within the target domains of the engine compartment domain controller, the body domain controller, and the chassis domain controller, including: The system controls the nodes within the target domain to receive the wake-up command sent via the second bus, the wake-up command containing a network management message; The controller LAN transceiver controlling the nodes within the target domain parses the network management message to obtain the target identification information; Read preset wake-up configuration information from the controller LAN transceiver; When the target identification information matches the preset wake-up configuration information, the network management message is determined to be a valid wake-up source; The controller LAN transceiver is switched from sleep mode to standby mode, thereby controlling the power output of the nodes in the target domain to ensure that the nodes in the target domain enter a normal state.

7. The method according to claim 6, characterized in that, The controller LAN transceiver includes at least one register for storing the preset wake-up configuration information.

8. The method according to claim 4, characterized in that, The engine compartment domain controller, the body domain controller, and the chassis domain controller are all 3.3V single-chip microcomputer control systems, and the 3.3V single-chip microcomputer control system adopts a 25MHz single-chip microcomputer minimum system design.

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 vehicle control method of any one of claims 4-8.

Images