Intelligent vehicle electronic and electrical architecture based on central domain control

Abstract

The invention belongs to the technical field of automotive electronics and electrical, and particularly relates to an intelligent vehicle electronic and electrical architecture based on central domain control, which comprises a CCU (central control unit) and a ZCU (zero control unit) which are in communication connection through Ethernet or CAN (FD). The ZCU area controllers are at least arranged on the front portion, the middle of the left side, the middle of the right side and the rear portion of the vehicle and connected to the electric control components at the corresponding positions. The CCU provides power distribution and intelligent protection for the central computing platform and the ZCU area controller; on the hardware architecture, the number of used ECUs can be extremely reduced, a traditional architecture mode according to function domains is broken up, and the function of distributing nearby according to position areas is achieved; the SOA service-oriented development and design concept is adopted on the software architecture, interfaces between the hierarchies are clear, and the novel architecture based on the hardware integrally improves the development efficiency and interface reuse, powerfully supports user-defined scenes, greatly expands the vehicle use scenes and improves the value.

Description

Technical Field

[0001] The present invention relates to the technical field of automotive electronics and electrical engineering, and particularly to an intelligent vehicle electronics and electrical architecture based on a central domain controller. Background Art

[0002] The automotive electrical / electronic architecture (EEA) integrates various sensors, ECUs (electronic control units), wiring harness topologies, and electrical / electronic distribution systems in a vehicle to complete the distribution and control of computing, information, and energy, thereby realizing various functions of the entire vehicle. It plays a crucial role in the intelligentization of the entire vehicle and ultimately determines the upper limit of the intelligentization level of the vehicle.

[0003] In traditional automotive electrical / electronic architectures, the ECUs of each functional module are separated from each other, which results in a large number of ECUs, complex hardware interface wiring harnesses, and the need to develop MCU software for each ECU. The underlying layers of each software are not unified, and the development duplication is high, making it impossible to achieve consistency in the underlying interfaces.

[0004] The current development trend of automotive control is towards higher intelligence at a rapid pace. However, this also leads to an increasing number of ECU electronic control modules in the entire vehicle, resulting in complex hardware wiring harness connections in the entire vehicle and serious software control logic coupling between each ECU. In this context, the traditional electrical / electronic architecture conflicts with the increasing demand for intelligent functions from automotive OEMs and the requirement for shortening the development cycle. The traditional distributed electrical / electronic architecture is already overburdened and cannot meet the development needs of automotive intelligence. Therefore, the birth of a new type of electrical / electronic architecture with decoupled software and hardware is imperative.

[0005] The upgrade of the automotive electrical / electronic architecture is mainly reflected in three aspects: the hardware architecture develops from a distributed to a domain control / centralized direction, the software architecture develops from a highly coupled software and hardware to a layered decoupled direction, and the communication architecture develops from LIN / CAN (FD) buses to Ethernet. Summary of the Invention

[0006] (I) Object of the Invention

[0007] To solve the technical problems in the background art, the present invention proposes an intelligent vehicle electrical / electronic architecture based on a central domain controller. The new automotive electrical / electronic architecture of the present invention centrally arranges the functions of each ECU, and the application logic is concentrated in the central high-performance computing unit CCU. The relevant hardware sensing and driving are distributed in each regional control unit ZCU according to different regions, significantly reducing the number of MCUs and the wiring harness of the entire vehicle.

[0008] (2) Technical Solution

[0009] To solve the above technical problems, the present invention provides an intelligent vehicle electronic and electrical architecture based on a central domain controller, which includes a CCU central computing unit and a ZCU regional controller, and the two are communicatively connected through Ethernet and CAN(FD);

[0010] The ZCU regional controller is at least arranged at the front, the middle left, the middle right, and the rear of the vehicle, and is respectively connected to the electric control components at the corresponding positions;

[0011] The CCU central computing unit provides power distribution and protection for the central computing platform and the ZCU regional controller;

[0012] The ZCU regional controller serves as a secondary electrical distribution center and centrally powers the electric control components within the region;

[0013] All the ZCUs can be communicatively connected to each other through Ethernet and CAN(FD) to form a network path, achieving the purpose of intelligent communication as needed between the ZCU regional controllers;

[0014] The CCU central computing unit is based on the application logic of SOA and is provided with an SOA service set and an SOA protocol set;

[0015] The SOA service set includes a combined service module and a logic service module for the CCU central computing unit, an atomic service module and an IO device abstraction service module for the ZCU regional controller;

[0016] The SOA protocol set includes an application layer module, a transport layer module, a network layer module, and a link layer module, realizing gateway functions and OTA flashing functions.

[0017] Further, the electric control components include a controller, a sensor, and an actuator. The ZCU regional controller realizes the acquisition of control instructions and sensor data in each region, the execution of regional logic, and the output drive of the actuator, and exchanges data with the CCU central computing unit and executes its instructions.

[0018] Further, the ZCU regional controller includes: a ZCU_F regional controller at the front, a ZCU_R regional controller at the rear, a ZCU_ML regional controller in the middle left, and a ZCU_MR regional controller in the middle right;

[0019] The ZCU_F regional controller at the front controls all inputs, in-domain logic control, and output drive at the front of the vehicle;

[0020] The ZCU_R regional controller at the rear controls all inputs, in-domain logic control, and output drive at the rear of the vehicle;

[0021] The ZCU_ML regional controller in the middle of the left side controls all inputs, in-domain logic control, and output drive in the middle left of the vehicle;

[0022] The ZCU_MR regional controller in the middle of the right side controls all inputs, in-domain logic control, and output drive in the middle right of the vehicle;

[0023] Each regional controller is connected to the sensors and actuators in its respective area through CAN(FD) / LIN buses and traditional hardwiring.

[0024] Furthermore, the combined service module: according to different vehicle model requirements, it can meet flexible definition of different scenario requirements;

[0025] The logic service module: using the interfaces provided by the atomic services, it has a certain degree of logical complexity, but is basically a general logical control behavior, arbitrates the application service priorities for different scenarios, and comprehensively meets the upper-layer scenario service requirements;

[0026] The atomic service module: does not involve direct interaction with the MCAL or the underlying system. It can use the interfaces provided by the IO device abstraction service layer to execute simple combined logic, realize atomic service capabilities, and basically does not involve complex logical requirements;

[0027] The IO device abstraction service module: the underlying basic module, responsible for IO output and input, and needs to directly interact with the MCAL or the underlying system.

[0028] Furthermore, the CCU central computing unit also supports connecting to the intelligent cockpit controller CDC and the intelligent driving controller ADC through CAN(FD) or Ethernet;

[0029] The CCU central computing unit can be compatible with one of the intelligent cockpit controller CDC and the intelligent driving controller ADC;

[0030] Or both are merged into the CCU.

[0031] Furthermore, the CCU and ZCU can achieve functional safety requirements up to ISO26262 ASIL D level.

[0032] Furthermore, the user co-creation platform includes a platform mode, a co-creation mode, and a full-stack delivery mode.

[0033] The above technical solutions of the present invention have the following beneficial technical effects:

[0034] In terms of the hardware architecture, the present invention achieves an extremely streamlined use of the number of ECUs, breaks up the traditional architecture method according to functional domains, and realizes the allocation of functions according to the location area in the vicinity.

[0035] The present invention adopts the SOA service-oriented development and design concept in the software architecture. The interfaces between each layer are clear. Based on this new architecture of the hardware, the overall development efficiency and interface reuse are improved, strongly supporting user-defined scenarios and greatly expanding the vehicle usage scenarios and value enhancement. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] Figure 1 It is the general diagram of the central domain control intelligent network architecture of the present invention;

[0037] Figure 2 It is the network architecture design diagram of the regional controller of the present invention;

[0038] Figure 3 It is the architecture diagram of the ZCU system of the present invention;

[0039] Figure 4 It is the schematic diagram of the user co-creation platform of the present invention;

[0040] Figure 5 It is the schematic diagram of the body domain control service interface of the present invention;

[0041] Figure 6 It is the schematic diagram of the service layering and communication architecture of the present invention;

[0042] Figure 7 It is the schematic diagram of different combinations of the evolution of CCU, ADC, and CDC of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0043] To make the objectives, technical solutions, and advantages of the present invention clearer and more understandable, the present invention will be further described in detail below in conjunction with the specific embodiments and with reference to the accompanying drawings. It should be understood that these descriptions are merely exemplary and are not intended to limit the scope of the present invention. In addition, in the following description, the descriptions of well-known structures and technologies are omitted to avoid unnecessarily confusing the concepts of the present invention.

[0044] As Figure 1-7 shown, an intelligent vehicle electronic and electrical architecture based on central domain control proposed by the present invention, an intelligent vehicle electronic and electrical architecture based on central domain control, includes a CCU central computing unit and a ZCU regional controller, and the two are communicatively connected through Ethernet and CAN(FD);

[0045] The ZCU regional controller is at least arranged at the front, the middle left, the middle right, and the rear of the vehicle, and is respectively connected to the electric control components at the corresponding positions (the traditional ECU is an independent software and is difficult to uniformly manage);

[0046] The CCU central computing unit provides power distribution and protection for the central computing platform and the ZCU regional controller;

[0047] Among all the ZCUs, they can be interconnected through Ethernet and CAN (FD) communication to form a network path, achieving the purpose of intelligent communication on demand between the zone controllers ZCU;

[0048] The ZCU zone controller serves as a secondary electrical distribution center, centrally providing intelligent power supply and distribution to each electrical control component within the zone.

[0049] It can be understood that the CCU central computing unit is a central computing platform, playing the roles of intelligent routing and data center. The electrical control components include controllers, sensors, and actuators, which are used to monitor and operate the basic equipment of the vehicle and the remaining electrical control components;

[0050] The electrical control components include but are not limited to door locks, seats, interior lights, exterior lights, windows, sunroofs, sunshades, windshield wipers, audio systems, ambient lights, power-on / off systems, tailgates, fuel tank caps, air conditioners, aromatherapy, thermal management, gear shifting, suspensions, parking brakes, steering wheel adjustment and heating, etc.

[0051] Among them, the CCU central computing unit has a built-in central computing platform, and connects to each ZCU zone controller through Gigabit Ethernet and CAN / CANFD. The ZCU zone controller realizes the acquisition of control commands and sensor data in each zone, the execution of zone logic, and the output drive of actuators, and exchanges data with the CCU central computing unit and executes its instructions. In this application, the ZCU zone controller includes: the ZCU_F zone controller in the front, the ZCU_R zone controller in the rear, the ZCU_ML zone controller in the middle on the left, and the ZCU_MR zone controller in the middle on the right;

[0052] The ZCU_F zone controller in the front controls all inputs, in-zone logic control, and output drive in the front of the vehicle;

[0053] The ZCU_R zone controller in the rear controls all inputs, in-zone logic control, and output drive in the rear of the vehicle;

[0054] The ZCU_ML zone controller in the middle on the left controls all inputs, in-zone logic control, and output drive in the middle left of the vehicle;

[0055] The ZCU_MR zone controller in the middle on the right controls all inputs, in-zone logic control, and output drive in the middle right of the vehicle;

[0056] Each zone controller connects the sensors and actuators in its respective zone through CANFD / LIN buses and traditional hardwiring.

[0057] Among them, the ZCU regional controller communicates and exchanges data with the CCU central computing unit through Ethernet and CAN / CANFD. The four ZCU regional controllers process and convert the input signals of the collected sensors and triggers and then transmit them to the CCU central computing unit. At the same time, they execute the control instructions issued by the CCU central computing unit to drive the actuator to work;

[0058] The ZCU regional controller can be designed with an MCU / SoC chip as the main control unit. It can have rich signal interfaces such as ETH / CAN / CANFD / LIN, and at the same time, it can also have a large number of rich directly driven hardware interfaces, such as PWM, LSD, HSD, H-Bridge, Half-Bridge, Power, eFuse and other interfaces, to achieve fast and flexible signal acquisition and drive control functions. It can deploy abstract services and some atomic services to achieve the maximum deployment of product capabilities and a continuously growing ecological type of product.

[0059] During actual operation, the CCU central computing unit is connected to the four regional controllers ZCU_F, ZCU_ML, ZCU_MR, and ZCU_R through 100M Ethernet and CAN / CANFD for sensor execution data exchange. It can also communicate and exchange data with the power domain and chassis domain controllers through CAN / CANFD, minimizing the number of ECUs used, breaking the traditional architecture method according to functional domains, and realizing the allocation of functions according to the location area. As the intelligent brain of intelligent vehicle control, the CCU central computing unit can intelligently and efficiently coordinate and control the vehicle's resources, issue and transmit instructions accurately and in a timely manner, and safely and intelligently monitor and integrate the vehicle's data status to meet the intelligent requirements of the vehicle.

[0060] It should be added that: CCU and ZCU can meet the functional safety requirements up to ISO26262 ASIL D level.

[0061] Such as Figure 7 shown: The CCU central computing unit can be compatible with one of the intelligent cockpit controller CDC and the intelligent driving controller ADC, or both can be merged into the CCU;

[0062] It can intelligently connect the intelligent cockpit controller CDC, the intelligent driving controller ADC, and the T-Box through Gigabit Ethernet for vehicle data exchange and control work.

[0063] As an optional combination example of the CCU central computing unit, the intelligent cockpit controller CDC, and the intelligent driving controller ADC:

[0064] The following effects can be achieved:

[0065] 1. Intelligent driving + intelligent cockpit (ADC + CDC), intelligent vehicle control CCU;

[0066] 2. Intelligent driving ADC, intelligent vehicle control + intelligent cockpit (CCU + CDC);

[0067] 3. Intelligent cockpit CDC, intelligent vehicle control + intelligent driving (CCU + ADC);

[0068] 4. Intelligent vehicle control + intelligent driving + intelligent cockpit (CCU + ADC + CDC).

[0069] Among them, the Telematics BOX, abbreviated as in-vehicle T-BOX, is mainly used for communicating with the back-end system / mobile APP to realize the display and control of vehicle information on the mobile APP.

[0070] At the software layer, the CCU central computing unit is based on the application logic of SOA, and is provided with an SOA service set and an SOA protocol set;

[0071] [[ID=1,8]]The SOA service set includes a composite service module and a logic service module for the CCU central computing unit, an atomic service module and an IO device abstraction service module for the ZCU regional controller;

[0072] The SOA protocol set includes an application layer module, a transport layer module, a network layer module and a link layer module to implement gateway functions and OTA flashing functions.

[0073] In the software architecture, the composite service module of the CCU central computing unit can define different scenario requirements according to different vehicle models;

[0074] The logic service module uses the interfaces provided by the atomic services, has a certain logical complexity, but is basically a general logical control behavior, arbitrates the application service priorities of different scenarios, and comprehensively meets the upper-layer scenario service requirements;

[0075] The atomic service module of the ZCU regional controller does not involve direct interaction with the MCAL or the underlying system. Using the interfaces provided by the IO device abstraction service layer, it executes simple composite logic to implement atomic service capabilities and basically does not involve complex logical requirements;

[0076] The IO device abstraction service module is a basic underlying module responsible for IO output and input, and needs to have direct interaction with the MCAL or the underlying system;

[0077] Adopting the SOA service-oriented development and design concept, the interfaces between each layer are clear;

[0078] The upper layer is the human-computer interaction layer, which can perform user-defined intelligent scenarios, mode and parameter storage customization modules, turn on and off the customized blocks, and a function real-time effect display module;

[0079] The middle layer is the CCU layer, and its combined service module is controlled by the human-computer interaction layer and interacts bidirectionally with the logic service module;

[0080] The lower layer is the ZCU layer, and the atomic service module interacts bidirectionally with the CCU layer and also interacts bidirectionally with the IO device abstraction service module. The IO device abstraction service module controls the operation of the electronic control components.

[0081] Based on this new hardware architecture, the overall development efficiency and interface reuse are improved, strongly supporting user-defined scenarios, greatly expanding the vehicle usage scenarios and value enhancement;

[0082] Such as Figure 4 shown, the user co-creation platform includes three modes: the platform mode, the co-creation mode, and the full-stack delivery mode;

[0083] The platform mode is mainly used when users have strong design and development capabilities for the application function layer. This architecture supports providing product capabilities such as the underlying layer and middleware;

[0084] The co-creation mode means that when customers do not have the complete ability to independently design and develop application layer functions, this architecture can support a mode of jointly developing with users;

[0085] Full-stack delivery is mainly to meet customers who do not have or do not intend to independently develop. This platform supports providing a full-stack solution for turnkey delivery.

[0086] It should be understood that the above specific embodiments of the present invention are only used for exemplary illustration or explanation of the principles of the present invention, and do not constitute a limitation to the present invention. Therefore, any modifications, equivalent replacements, improvements, etc. made without departing from the spirit and scope of the present invention shall be included within the protection scope of the present invention. In addition, the appended claims of the present invention are intended to cover all changes and modification examples that fall within the scope and boundaries of the appended claims, or equivalent forms of such scope and boundaries.

Claims

1. An intelligent vehicle electronic and electrical architecture based on a central domain controller, characterized in that, It includes a CCU central computing unit and a ZCU zone controller, and the two are communicatively connected via Ethernet and CAN (FD); The ZCU zone controller is at least arranged at the front, the middle left, the middle right, and the rear of the vehicle, and is respectively connected to the electronic control components at the corresponding positions; The CCU central computing unit provides power distribution and intelligent protection for the central computing platform and the ZCU zone controller; Among all the ZCUs, they can be interconnected with each other via Ethernet and CAN (FD) communication to form a network path, so as to achieve the purpose of intelligent communication on demand between the ZCU zone controllers; The ZCU zone controller serves as a secondary electrical distribution center to centrally supply and distribute power intelligently to the electronic control components within the zone; Based on the application logic of SOA, the CCU central computing unit is provided with an SOA service set and an SOA protocol set; The SOA service set includes a composite service module and a logic service module for the CCU central computing unit, an atomic service module and an IO device abstraction service module for the ZCU zone controller; The SOA protocol set includes an application layer module, a transport layer module, a network layer module, and a link layer module to implement gateway functions and OTA flashing functions.

2. The intelligent vehicle electronic and electrical architecture based on a central domain controller according to claim 1, wherein The electronic control components include a controller, a sensor, and an actuator. The ZCU zone controller realizes the acquisition of control instructions and sensor data in each zone, the execution of zone logic, and the output drive of the actuator, and exchanges data with the CCU central computing unit and executes its instructions.

3. The intelligent vehicle electronic and electrical architecture based on a central domain controller according to claim 1, wherein The ZCU zone controller includes: the ZCU_F zone controller at the front, the ZCU_R zone controller at the rear, the ZCU_ML zone controller in the middle left, and the ZCU_MR zone controller in the middle right; The ZCU_F zone controller at the front controls all inputs, in-zone logic control, and output drive at the front of the vehicle; The ZCU_R zone controller at the rear controls all inputs, in-zone logic control, and output drive at the rear of the vehicle; The ZCU_ML zone controller in the middle left controls all inputs, in-zone logic control, and output drive in the middle left of the vehicle; The ZCU_MR zone controller in the middle right controls all inputs, in-zone logic control, and output drive in the middle right of the vehicle; Each zone controller is connected to the sensors and actuators in its respective zone via CAN (FD) / LIN bus and traditional hard wires.

4. An intelligent vehicle electronic and electrical architecture based on a central domain controller according to claim 1, characterized in that, The composite service module: According to different vehicle type requirements, it meets the flexible definition of different scenario requirements; The logic service module: Using the interfaces provided by the atomic services, it has a certain degree of logical complexity, but basically it is a general logical control behavior, arbitrates the application service priorities in different scenarios, and comprehensively meets the upper-layer scenario service requirements; The atomic service module: It does not involve direct interaction with the MCAL or the underlying system. Using the interfaces provided by the IO device abstraction service layer, it executes simple composite logic to achieve atomic service capabilities and basically does not involve complex logical requirements; The IO device abstraction service module: The underlying basic module is responsible for IO output and input and needs to directly interact with the MCAL or the underlying system.

5. The intelligent vehicle electronic and electrical architecture based on a central domain controller according to claim 1, characterized in that The CCU central computing unit also supports connecting the intelligent cockpit controller CDC and the intelligent driving controller ADC through CAN (FD) or Ethernet; The CCU central computing unit is compatible with one of the intelligent cockpit controller CDC and the intelligent driving controller ADC; Or both are merged into the CCU.

6. The intelligent vehicle electronic and electrical architecture based on a central domain controller according to claim 1, characterized in that, The CCU and ZCU can achieve functional safety requirements up to ISO26262 ASIL D level.

7. An intelligent vehicle electronic and electrical architecture based on a central domain controller according to claim 1, characterized in that It also includes a user co-creation platform: the user co-creation platform includes a platform mode, a co-creation mode, and a full-stack delivery mode.

Images