An electronic and electrical architecture for commercial vehicles based on regional and functional domain fusion

Abstract

The application discloses an electronic and electrical architecture of a commercial vehicle based on regional and functional domain fusion. The electronic and electrical architecture comprises a central server for performing function control and information routing of the whole vehicle; a power function domain controller for performing power transmission and speed control of the whole vehicle; a chassis function domain controller for performing control of steering, braking and suspension of the whole vehicle; an intelligent driving function domain controller for performing automatic driving auxiliary control; a cab area controller for performing door control, vehicle interior light control and switch control; and a chassis area controller for performing chassis light control, superstructure control and starting control. The above technical scheme fuses the electronic and electrical architecture by the regional controller and the functional domain controller, can better adapt to the characteristics of the complex body structure and the multiple optional function configuration of the commercial vehicle, optimizes the wire harness length, and makes the electronic and electrical architecture layout of the commercial vehicle more reasonable.

Description

Technical Field

[0001] This invention relates to the field of automotive electronic and electrical architecture technology, and more particularly to an electronic and electrical architecture for commercial vehicles based on the integration of regional and functional domains. Background Technology

[0002] The automotive electrical / electronic architecture (EEA) integrates various sensors, electronic control units, wiring harness topologies, and electronic and electrical distribution systems in a vehicle to perform computation, power, and energy distribution, thereby enabling the vehicle to perform its various functions.

[0003] Currently, the design of area-controlled electronic and electrical architectures for passenger vehicles is becoming increasingly mature, reducing the amount of wiring harnesses compared to centralized electronic and electrical architectures. However, commercial vehicles, compared to passenger vehicles, require consideration of the cab, chassis, or superstructure, resulting in a more complex structure. Furthermore, the sensors, actuators, switches, and controllers related to the electronic and electrical systems of commercial vehicles are distributed throughout the cab, chassis, or superstructure, making their layout even more complex. Therefore, area-controlled electronic and electrical architectures for passenger vehicles are not suitable for commercial vehicles, and their electronic and electrical architectures need to be designed according to the specific circumstances of commercial vehicles. Summary of the Invention

[0004] This invention provides an electronic and electrical architecture for commercial vehicles based on the integration of regional and functional domain controllers. By integrating regional controllers and functional domain controllers into the electronic and electrical architecture design, it can better adapt to the complex body structure and numerous optional functional configurations of commercial vehicles. It also optimizes the wiring harness length while making the electronic and electrical architecture layout of commercial vehicles more reasonable.

[0005] In a first aspect, embodiments of the present invention provide an electronic and electrical architecture for a commercial vehicle based on the fusion of regional and functional domains, including: a central server and a power functional domain controller, a chassis functional domain controller, an intelligent driving functional domain controller, a cab area controller, and a chassis area controller respectively connected to the central server;

[0006] The central server is used for the functional control and information routing of the entire vehicle;

[0007] The power functional domain controller is used for power transmission and speed control of the entire vehicle.

[0008] The chassis functional domain controller is used to control the vehicle's steering, braking, and suspension.

[0009] The intelligent driving function domain controller is used for autonomous driving assistance control;

[0010] The driver's cab area controller is used for door control, interior lighting control, and switch control.

[0011] The chassis area controller is used for chassis lighting control, superstructure control, and start-up control.

[0012] Furthermore, the powertrain function domain controller is a domain controller for controlling traditional gasoline-powered vehicles. Accordingly, the powertrain function domain controller is specifically used for:

[0013] The engine controller and transmission controller are connected via one CAN controller area network or one CANFD controller area network that supports variable rate.

[0014] Connect smart sensors and smart actuators via a single local area network (LIN).

[0015] The central server is connected via one CANFD and one Ethernet connection.

[0016] Furthermore, the powertrain functional domain controller is a domain controller for controlling new energy vehicles. Accordingly, the powertrain functional domain controller is specifically used for:

[0017] The battery management system and motor controller are connected via a single CAN FD connection.

[0018] Connect the smart sensor and smart actuator via a single LIN connection;

[0019] The central server is connected via one CANFD and one Ethernet connection.

[0020] Furthermore, the chassis functional domain controller is specifically used for:

[0021] The controllers of the power steering system, braking system and suspension system are connected via a CANFD.

[0022] The central server is connected via one CANFD and one Ethernet connection.

[0023] Furthermore, the intelligent driving function domain controller is specifically used for:

[0024] Connect the radar and cameras needed to achieve partial autonomous driving;

[0025] The central server is connected via a CANFD connection.

[0026] Furthermore, the intelligent driving function domain controller is specifically used for:

[0027] Connect the radar and cameras required to achieve conditional autonomous driving or highly autonomous driving;

[0028] The central server is connected via one CANFD and one Ethernet connection.

[0029] Furthermore, the cab area controller includes:

[0030] A cab center sub-area controller is used for accelerator pedal sensor control, vehicle interior lighting control, switch control, air conditioning control, and windshield wiper control.

[0031] The left door area controller is used to control the left side window, the left side door opening and closing, the left side door light, and the left side rearview mirror.

[0032] The right door area controller is used to control the right-side window, the right-side door opening and closing, the right-side door light, and the right-side rearview mirror.

[0033] Furthermore, the chassis area controller includes:

[0034] A front sub-area controller for chassis, which is used for controlling the front lights and starting of the chassis;

[0035] A chassis center sub-area controller, which is used for controlling the lighting in the center of the chassis and the lighting on the superstructure;

[0036] A rear sub-area controller for chassis, which is used to control the rear lighting of the chassis.

[0037] Furthermore, the sub-area controllers included in the cab area controller or the sub-area controllers included in the chassis area controller are configured based on the deployment of sensors, actuators or switches related to the application scenario.

[0038] Furthermore, the electronic and electrical architecture also includes:

[0039] An infotainment function domain controller is used to connect to the central server via one CANFD and one Ethernet connection to provide multimedia services for the entire vehicle.

[0040] The technical solution of this invention integrates the regional controller and functional domain controller in the design of the electronic and electrical architecture, which can better adapt to the characteristics of complex body structure and many optional functional configurations of commercial vehicles. It optimizes the wiring harness length and makes the electronic and electrical architecture layout of commercial vehicles more reasonable.

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

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

[0043] Figure 1 This is a schematic diagram of the electronic and electrical architecture of a commercial vehicle based on the fusion of regional and functional domains according to Embodiment 1 of the present invention;

[0044] Figure 2 This is a schematic diagram of the electronic and electrical architecture of a commercial vehicle based on the fusion of regional and functional domains according to Embodiment 2 of the present invention;

[0045] Figure 3 This is a schematic diagram of the electronic and electrical architecture of a commercial vehicle based on the fusion of regional and functional domains according to Embodiment 3 of the present invention;

[0046] Figure 4 This is a schematic diagram of another electronic and electrical architecture for commercial vehicles based on the fusion of regional and functional domains, according to Embodiment 3 of the present invention.

[0047] Figure 5 This is a schematic diagram of the electronic and electrical architecture of a commercial vehicle based on the fusion of regional and functional domains, according to Embodiment 3 of the present invention. Detailed Implementation

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

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

[0050] Example 1

[0051] Figure 1 This is a schematic diagram of the electronic and electrical architecture of a commercial vehicle based on the integration of regional and functional domains according to Embodiment 1 of the present invention. This embodiment is applicable to the design of electronic and electrical architectures for commercial vehicles. Figure 1 As shown, the electronic and electrical architecture includes:

[0052] Central server 10 and power functional domain controller 20, chassis functional domain controller 30, intelligent driving functional domain controller 40, cab area controller 50 and chassis area controller 60 respectively connected to central server 10;

[0053] Central server 10 is used for vehicle function control and information routing;

[0054] The power functional domain controller 20 is used for power transmission and speed control of the entire vehicle;

[0055] The chassis functional domain controller 30 is used to control the steering, braking and suspension of the entire vehicle;

[0056] The intelligent driving function domain controller 40 is used for autonomous driving assistance control;

[0057] The cab area controller 50 is used for door control, interior lighting control, and switch control.

[0058] The chassis area controller 60 is used for chassis lighting control, superstructure control, and start-up control.

[0059] Specifically, the central server 10 supports multiple Ethernet and Controller Area Network (CANFD) interfaces with flexible data rate. The central server 10 can connect to the powertrain functional domain controller 20, chassis functional domain controller 30, intelligent driving functional domain controller 40, cab area controller 50, and chassis area controller 60 via these multiple Ethernet and CANFD interfaces. The central server 10 can be implemented using a high-performance computing chip (S32G+TC397) and surrounding circuitry, responsible for vehicle function control and information routing. Alternatively, the central server 10 can be implemented using other hardware components capable of handling vehicle function control and information routing; this invention does not limit the specific implementation.

[0060] The powertrain domain controller 20 is used for power transmission and speed control of the entire vehicle. The powertrain domain controller 20 can support power transmission and speed control for both traditional gasoline-powered vehicles and new energy vehicles. When the powertrain domain controller 20 is used to control traditional gasoline-powered vehicles, it can connect to the engine controller, transmission controller, intelligent generator, and electronic cooling fan, etc. When the powertrain domain controller 20 is used to control new energy vehicles, it can connect to the battery management system, motor control unit, water valve, oil pump, air pump, etc. The powertrain domain controller 20 connects to the central server 10 via one CANFD and one Ethernet connection to enable information exchange between the engine controller, transmission controller, battery management system, or motor control unit and the central server 10, thereby achieving power transmission and speed control of the entire vehicle.

[0061] The chassis functional domain controller 30 is used to control the steering, braking, and suspension of the entire vehicle. The chassis functional domain controller 30 can connect via a CAN-FD to various controllers included in the braking system, suspension system, and power steering system, such as the Anti-lock Braking System (ABS), Electronically Controlled Braking System (EBS), Electric Power Steering System (EPS), or Electronic Controlled Air Suspension System (ECAS). The chassis functional domain controller 30 is connected to the central server 10 via one CAN-FD and one Ethernet connection to enable information exchange between the ABS, EBS, EPS, or ECAS systems and the central server 10, thereby achieving control of the vehicle's steering, braking, and suspension.

[0062] The intelligent driving function domain controller 40 is used for autonomous driving assistance control. The intelligent driving function domain controller 40 can realize partial autonomous driving (Level 2 autonomous driving), conditional autonomous driving (Level 3 autonomous driving), or highly autonomous driving (Level 4 autonomous driving) control. For example, the intelligent driving function domain controller 40 can connect to the radars and cameras required for Level 2, Level 3, or Level 4 autonomous driving, and can also connect to the central server 10 to realize information interaction between each radar and camera and the central server 10, thereby realizing autonomous driving assistance control.

[0063] The cab area controller 50 is used for door control, interior lighting control, and switch control. The cab area controller 50 connects to the sensors, actuators, switches, loads, or electronic control units required for door control, interior lighting control, and switch control. Simultaneously, the cab area controller 50 connects to the central server 10 via one CANFD and one Ethernet connection to realize door control, interior lighting control, and switch control. The cab area controller 50 is used for door control, such as controlling door locking and unlocking, or controlling the raising and lowering of windows on the doors; the cab area controller 50 is used for interior lighting control, such as controlling the interior backlight and interior lights; the cab area controller 50 is also used to collect data on interior switches.

[0064] The chassis area controller 60 is used for chassis lighting control, superstructure control, and starting control. The chassis area controller 60 connects to the sensors, actuators, switches, loads, or electronic control units required for chassis lighting control, superstructure control, and starting control. Simultaneously, the chassis area controller 60 connects to the central server 10 via one CANFD and one Ethernet connection to realize chassis lighting control, superstructure control, and starting control. The chassis area controller 60 is used for chassis lighting control, such as front chassis lighting control, mid-chassis lighting control, or rear chassis lighting control; the chassis area controller 60 is also used for superstructure control, such as trailer (superstructure) lighting control.

[0065] The technical solution of this invention integrates the regional controller and functional domain controller in the design of the electronic and electrical architecture, which can better adapt to the characteristics of complex body structure and many optional functional configurations of commercial vehicles. It optimizes the wiring harness length and makes the electronic and electrical architecture layout of commercial vehicles more reasonable.

[0066] Example 2

[0067] Figure 2This is a schematic diagram of the electronic and electrical architecture of a commercial vehicle based on the integration of regional and functional domains according to Embodiment 2 of the present invention. This embodiment is based on Embodiment 1 above, and further refines the structure of the cab area controller 50, the structure of the chassis area controller 60, and the structures also included in the electronic and electrical architecture.

[0068] In this embodiment of the invention, the cab area controller 50 includes:

[0069] The cab center sub-area controller 51 is used for accelerator pedal sensor control, vehicle interior lighting control, switch control, air conditioning control, and windshield wiper control.

[0070] The left door area controller 52 is used to control the left side window, the left side door opening and closing, the left side door light, and the left side rearview mirror.

[0071] The right door area controller 53 is used to control the right-side window, the right-side door opening and closing, the right-side door light, and the right-side rearview mirror.

[0072] The central sub-area controller 51 in the cab is used for accelerator pedal sensor control, brake switch control, steering wheel switch control, instrument panel switch control, roof switch acquisition, backlight control, vehicle interior lighting control, intelligent accessories control in the cab, air conditioning control, and wiper control, etc.

[0073] The left door area controller 52 is used for left-side window lifting control, left-side window anti-pinch control, left-side door locking / unlocking control, left-side rearview mirror adjustment, left-side rearview mirror heating, left-side door opening / closing data acquisition, and left-side door light control, etc.

[0074] The right door area controller 53 is used for controlling the right side window lifting, the right side window anti-pinch control, the right side door locking and unlocking control, the right side rearview mirror adjustment, the right side rearview mirror heating, the right side door opening and closing data acquisition, and the right side door light control.

[0075] Each sub-area controller included in the cab area controller 50 is connected to the central server 10 via one CANFD and one Ethernet.

[0076] In this embodiment of the invention, the chassis area controller 60 includes:

[0077] The front sub-area controller 61 of the chassis is used for controlling the front lights and starting of the chassis.

[0078] The chassis center sub-area controller 62 is used for controlling the lighting in the center of the chassis and the lighting on the superstructure.

[0079] The rear sub-area controller 63 is used for controlling the rear lighting of the chassis.

[0080] The front sub-area controller 61 is used for controlling the front lights, horn, retarder, and start-up of the chassis.

[0081] The chassis center sub-area controller 62 is used for controlling the chassis center lighting, trailer or superstructure lighting, fuel level sensor, air tank pressure sensor, and auxiliary power unit (APU) control valves, etc.

[0082] The rear sub-area controller 63 is used for controlling the rear lights, differential lock solenoid valve, hill start assist solenoid valve, and reversing buzzer, etc.

[0083] Each of the sub-region controllers included in the chassis region controller 60 is connected to the central server 10 via one CANFD and one Ethernet.

[0084] Furthermore, the sub-area controllers included in the cab area controller 50 or the sub-area controllers included in the chassis area controller 60 are configured based on the deployment of sensors, actuators or switches related to the application scenario.

[0085] For example, when the control requirements for the vehicle doors are not high, and the deployment of sensors, actuators, or switches related to the cab area control indicates that most of them are deployed in the area corresponding to the cab position, then only the cab center sub-area controller 51 needs to be set up. Similarly, when the deployment of sensors, actuators, or switches related to the chassis area control indicates that most of them are deployed in the areas corresponding to the front and center positions of the chassis, then only the front chassis sub-area controller 61 and the center chassis sub-area controller 62 need to be set up. Furthermore, the sub-area controllers included in the cab area controller 50 or the chassis area controller 60 can be optimized based on the deployment of the intelligent nodes.

[0086] In this embodiment of the invention, the electronic and electrical architecture further includes:

[0087] The infotainment function domain controller 70 is used to connect to the central server 10 via one CAN FD and one Ethernet; providing multimedia services for the entire vehicle.

[0088] The sensors, actuators, or electronic control units that the infotainment function domain controller 70 needs to connect to are concentrated in the dashboard central control area, which may be an instrument cluster and a large in-vehicle screen, or a multi-screen solution. In the instrument cluster and large in-vehicle screen solution, the instrument cluster display controller and the in-vehicle infotainment controller are connected to the infotainment function domain controller 70, and the infotainment function domain controller 70 is connected to the central server 10 via a CAN-FD connection. In the multi-screen solution, the infotainment function domain controller 70 is connected to the central server 10 via a CAN-FD connection and an Ethernet connection.

[0089] In this embodiment of the invention, the powertrain functional domain controller 20 is a domain controller for controlling conventional gasoline-powered vehicles. Accordingly, the powertrain functional domain controller 20 is specifically used for:

[0090] The engine controller and transmission controller are connected via one CAN controller area network or one CANFD controller area network that supports variable rate.

[0091] Connect smart sensors and smart actuators via a single local area network (LIN).

[0092] The central server 10 is connected via one CANFD and one Ethernet connection.

[0093] The sensors, actuators, or electronic control units that need to be connected to the power function domain controller 20 are concentrated in the chassis area of ​​the vehicle, such as the engine controller, transmission controller, intelligent generator, or electric cooling fan. The engine controller and transmission controller share one CANFD or CAN connection to the power function domain controller 20, while the intelligent generator and electric cooling fan are connected to the power function domain controller 20 via one LIN connection. The power function domain controller 20 is connected to the central server 10 via one CANFD and one Ethernet connection to realize the power transmission and transmission control of traditional fuel vehicles.

[0094] In this embodiment of the invention, the power function domain controller 20 is a domain controller for controlling new energy vehicles. Accordingly, the power function domain controller 20 is specifically used for:

[0095] The battery management system and motor controller are connected via a single CAN FD connection.

[0096] Connect the smart sensor and smart actuator via a single LIN connection;

[0097] The central server 10 is connected via one CANFD and one Ethernet connection.

[0098] The sensors, actuators, or electronic control units that need to be connected to the power function domain controller 20 are concentrated in the chassis area of ​​the vehicle, such as the battery management system, motor controller, water valve, oil pump, or air pump. The battery management system and motor controller are connected to the power function domain controller 20 via 1 to 2 CANFDs, and the water valve, oil pump, and air pump are connected to the power function domain controller 20 via 1 LIN. The power function domain controller 20 is connected to the central server 10 via one CANFD and one Ethernet to realize the power transmission and speed control of the new energy vehicle.

[0099] In this embodiment of the invention, the chassis functional domain controller 30 is specifically used for:

[0100] The controllers of the power steering system, braking system and suspension system are connected via a CANFD.

[0101] The central server 10 is connected via one CANFD and one Ethernet connection.

[0102] The components such as sensors, actuators, or electronic control units that need to be connected to the chassis functional domain controller 30 are concentrated in the chassis and suspension area of ​​the vehicle, such as the braking system, suspension system, and power steering system. Its ABS, EBS, EPS, ECAS and other controllers are connected to the chassis functional domain controller 30 via one CANFD. The chassis functional domain controller 30 is connected to the central server 10 via one CANFD and one Ethernet to realize the control of the vehicle's steering, braking and suspension.

[0103] In this embodiment of the invention, the intelligent driving function domain controller 40 is specifically used for:

[0104] Connect the radar and cameras needed to achieve partial autonomous driving;

[0105] The central server 10 is connected via a CANFD connection.

[0106] When partial autonomous driving (Level 2) is required, one millimeter-wave radar controller and one camera controller are connected to one CANFD to the intelligent driving functional domain controller 40. The intelligent driving functional domain controller 40 is connected to the central server 10 through one CANFD to realize autonomous driving assistance control.

[0107] In this embodiment of the invention, the intelligent driving function domain controller 40 is specifically used for:

[0108] Connect the radar and cameras required to achieve conditional autonomous driving or highly autonomous driving;

[0109] The central server 10 is connected via one CANFD and one Ethernet connection.

[0110] When conditional autonomous driving (Level 3) is required, one lidar, seven millimeter-wave radars, ten ultrasonic radars, and seven cameras are connected to the intelligent driving functional domain controller 40. The intelligent driving functional domain controller 40 is connected to the central server 10 via one CANFD and one Ethernet to achieve autonomous driving assistance control.

[0111] When highly automated driving (Level 4) is required, 5 LiDARs, 7 millimeter-wave radars, 10 ultrasonic radars and 13 cameras are connected to the intelligent driving functional domain controller 40. The intelligent driving functional domain controller 40 is connected to the central server 10 via 1 CAN FD and 1 Ethernet to achieve automated driving assistance control.

[0112] In one embodiment, the powertrain functional domain controller 20, chassis functional domain controller 30, intelligent driving functional domain controller 40, and infotainment functional domain controller 70 can be selected for whether or not to be set according to the configuration of each functional domain. For example, when the requirements for infotainment functions are not high, the infotainment functional domain controller 70 can be omitted, and the electronic control unit required to realize the infotainment functions can be directly connected to the central server 10 via CANFD.

[0113] The technical solution of this invention, by dividing the cab into a central sub-area controller, a left door sub-area controller, a right door sub-area controller, a front chassis sub-area controller, a central chassis sub-area controller, and a rear chassis sub-area controller, addresses the issue of a large number of wiring harnesses connecting the cab and chassis in a centralized electronic and electrical architecture of commercial vehicles, which requires connecting both cab components and chassis components. The electronic and electrical architecture provided in this application can optimize wiring harness length while making the electronic and electrical architecture layout of commercial vehicles more reasonable.

[0114] The technical solution of this invention, which includes a powertrain functional domain controller, a chassis functional domain controller, an intelligent driving functional domain controller, and an infotainment functional domain controller, can be selected for or not set according to the configuration of each functional domain, making the design of the electronic and electrical architecture more flexible and closer to actual application needs.

[0115] Example 3

[0116] The embodiments of the present invention are exemplary descriptions of the above embodiments.

[0117] Figure 3 This is a schematic diagram of the electronic and electrical architecture of a commercial vehicle based on the fusion of regional and functional domains according to Embodiment 3 of the present invention, as shown below. Figure 3As shown, the electronic and electrical architecture includes: a central control section, a powertrain functional domain section, a chassis functional domain section, an intelligent driving functional domain section, an infotainment functional domain section, a left door area section, a right door area section, a central cab area section, a front chassis area section, a central chassis area section, and a rear chassis area section.

[0118] The central control unit consists of a high-performance central server that supports a large number of Ethernet and CANFD interfaces, connecting various functional domains and regional sections, and is responsible for the overall vehicle function control and information routing.

[0119] The power functional domain section includes a power domain controller and various sensors, actuators, or electronic control units (ECUs) connected to the power domain controller. The power domain controller is connected to a central server via one CANFD and one Ethernet.

[0120] The chassis functional domain includes the chassis domain controller (i.e., chassis functional domain controller) and various sensors, actuators or electronic control units connected to the chassis domain controller. The chassis domain controller is connected to the central server via one CANFD and one Ethernet.

[0121] The intelligent driving functional domain includes the intelligent driving domain controller (i.e., the intelligent driving functional domain controller) and various sensors, actuators or electronic control units connected to the intelligent driving domain controller. The intelligent driving domain controller is connected to the central server via one CANFD and one Ethernet.

[0122] The infotainment functional domain includes an infotainment domain controller (i.e., infotainment functional domain controller) and various sensors, actuators or electronic control units connected to the infotainment domain controller. The infotainment domain controller is connected to a central server via one CAN FD and one Ethernet.

[0123] The central area of ​​the cab includes the central area controller (i.e., the central sub-area controller) and various sensors, actuators, ECUs, switches or loads connected to the central area controller. The central area controller is connected to a central server via one CANFD and one Ethernet.

[0124] The right door area section includes the right door area controller (i.e., the right door sub-area controller) and various sensors, actuators, ECUs, switches or loads connected to the right door area controller. The right door area controller is connected to a central server via one CANFD and one Ethernet.

[0125] The left door area section includes the left door area controller (i.e., the left door sub-area controller) and various sensors, actuators, ECUs, switches or loads connected to the left door area controller. The left door area controller is connected to a central server via one CANFD and one Ethernet.

[0126] The front area of ​​the chassis includes the front area controller (i.e., the front sub-area controller) and various sensors, actuators, ECUs, switches or loads connected to the front area controller. The front area controller is connected to a central server via one CANFD and one Ethernet.

[0127] The central area of ​​the chassis includes the central area controller (i.e., the central sub-area controller) and various sensors, actuators, ECUs, switches or loads connected to the central area controller. The central area controller is connected to a central server via one CANFD and one Ethernet.

[0128] The rear area of ​​the chassis includes the rear area controller (i.e., the rear sub-area controller) and various sensors, actuators, ECUs, switches or loads connected to the rear area controller. The rear area controller is connected to a central server via one CAN FD and one Ethernet.

[0129] The powertrain functional domain, chassis functional domain, infotainment functional domain, and intelligent driving functional domain include centralized and distributed functional domain variations, which can be selected according to the configuration of each functional domain.

[0130] The number of cab areas and chassis areas can be optimized based on the deployment of sensors, actuators, switches, and intelligent nodes in the vehicle body.

[0131] When there are high requirements for the overall vehicle functionality, including new energy power, advanced braking systems, L4 autonomous driving, high-end body functions, and basic in-vehicle information terminals, it is possible to... Figure 3 The electronic and electrical architecture shown is modified accordingly. Figure 4 This is a schematic diagram of another electronic and electrical architecture for commercial vehicles based on the fusion of regional and functional domains according to Embodiment 3 of the present invention, as shown below. Figure 4 As shown, compared to Figure 3 The electronic and electrical architecture shown retains the same design for the powertrain functional domain, chassis functional domain, and intelligent driving functional domain. The ECUs in each functional domain are connected to the corresponding domain controllers, which are then directly connected to the central server via CANFD and Ethernet. In contrast, the infotainment functional domain removes the infotainment domain controller and connects the ECUs within it directly to the central server to fulfill simple in-vehicle information needs.

[0132] When the requirements for the overall vehicle functionality are relatively low, including traditional power, ABS braking, L1 intelligent driving, low-end body functions, monochrome instrument panel, and multi-screen information system, it is possible to... Figure 3 The electronic and electrical architecture shown is modified accordingly. Figure 5 This is a schematic diagram of another electronic and electrical architecture for a commercial vehicle based on the fusion of regional and functional domains according to Embodiment 3 of the present invention, as shown below. Figure 5 As shown, compared to Figure 3 The electronic and electrical architecture shown has the ECUs in the powertrain, chassis, and intelligent driving functional domains directly connected to the central server, while the design of the infotainment functional domain remains unchanged. The central area of ​​the cab, the left door area, and the right door area are merged into the cab area area, with only one cab area controller retained. The cab area controller is directly connected to the central server via CANFD and Ethernet.

[0133] The present invention provides an electronic and electrical architecture for commercial vehicles, which is based on the integration of regional control and functional domain control. It can better adapt to the characteristics of complex body structure and many optional function configurations of commercial vehicles, and can optimize the wiring harness length while also taking into account the requirements of product transformation.

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

[0135] 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. An electronic and electrical architecture for commercial vehicles based on the integration of regional and functional domains, characterized in that, include: A central server and a power functional domain controller, a chassis functional domain controller, an intelligent driving functional domain controller, a cab area controller, and a chassis area controller, all connected to the central server respectively. The central server is used for the functional control and information routing of the entire vehicle; The power functional domain controller is used for power transmission and speed control of the entire vehicle. The chassis functional domain controller is used to control the vehicle's steering, braking, and suspension. The intelligent driving function domain controller is used for autonomous driving assistance control; The driver's cab area controller is used for door control, interior lighting control, and switch control. The chassis area controller is used for chassis lighting control, superstructure control, and start-up control; The cab area controller includes: A cab center sub-area controller is used for accelerator pedal sensor control, vehicle interior lighting control, switch control, air conditioning control, and windshield wiper control. The left door area controller is used to control the left side window, the left side door opening and closing, the left side door light, and the left side rearview mirror. The right door area controller is used to control the right-side window, the right-side door opening and closing, the right-side door light, and the right-side rearview mirror. The chassis area controller includes: A front sub-area controller for chassis, which is used for controlling the front lights and starting of the chassis; A chassis center sub-area controller, which is used for controlling the lighting in the center of the chassis and the lighting on the superstructure; A rear sub-area controller for chassis, wherein the rear sub-area controller is used for controlling the rear lights of the chassis; When the powertrain function domain controller is a domain controller for controlling conventional gasoline-powered vehicles, the powertrain function domain controller is specifically used for: The engine controller and transmission controller are connected via one CAN controller area network or one CANFD controller area network that supports variable rate. Connect smart sensors and smart actuators via a single local area network (LIN). The central server is connected via one CANFD and one Ethernet connection; or... When the powertrain function domain controller is a domain controller for controlling new energy vehicles, the powertrain function domain controller is specifically used for: The battery management system and motor controller are connected via a single CAN FD connection. Connect the smart sensor and smart actuator via a single LIN connection; The central server is connected via one CANFD and one Ethernet connection.

2. The electronic and electrical architecture according to claim 1, characterized in that, The chassis functional domain controller is specifically used for: The controllers of the power steering system, braking system and suspension system are connected via a CANFD. The central server is connected via one CANFD and one Ethernet connection.

3. The electronic and electrical architecture according to claim 1, characterized in that, The intelligent driving function domain controller is specifically used for: Connect the radar and cameras needed to achieve partial autonomous driving; The central server is connected via a CANFD connection.

4. The electronic and electrical architecture according to claim 1, characterized in that, The intelligent driving function domain controller is specifically used for: Connect the radar and cameras required to achieve conditional autonomous driving or highly autonomous driving; The central server is connected via one CANFD and one Ethernet connection.

5. The electronic and electrical architecture according to claim 1, characterized in that, Whether to set up each sub-area controller included in the cab area controller or the sub-area controller included in the chassis area controller depends on the deployment of sensors, actuators or switches related to the application scenario.

6. The electronic and electrical architecture according to claim 1, characterized in that, Also includes: An infotainment function domain controller, wherein the infotainment function domain controller is used to connect to the central server via one CANFD and one Ethernet; Provides multimedia services for the entire vehicle.

Images