Vehicle control system and vehicle

Abstract

The invention relates to the field of automobile electric control, and discloses a vehicle control system and a vehicle, and the vehicle control system comprises a central domain control unit and a plurality of area controllers connected with the central domain control unit; the central domain control unit comprises an application layer, an RTE communication layer and a base layer, and the application layer is provided with a plurality of functional sub-domain control units. According to the invention, a plurality of functional sub-domain control units are integrated in the central domain control unit to form a centralized domain control architecture, so that hardware and wire harnesses of an original domain controller can be cancelled, and the cost is reduced; external gateway signals can be reduced, bus and external interactive transmission links are reduced, and the function safety is improved; the user demand of the client can be directly acquired in the central domain control unit, and the customer demand can be responded more quickly.

Description

Technical Field

[0001] The present invention relates to the field of automobile electronic control, and in particular to a vehicle control system and a vehicle. Background Art

[0002] With the rapid development of modern automobile technology, intelligence and electrification have become the main trends in the automotive industry. At present, most OEMs adopt an architecture that combines a central domain control unit with domain control units at various levels (such as cockpit domain, power domain, chassis domain, intelligent driving domain, etc.), and realize communication and interaction between domain control units through gateways. However, from the perspective of the interactive link between the power domain and the central domain, there are obvious problems. The power domain sub-controller (covering BMS, DCDC, motor and power management system, etc.) must first communicate with the power domain control unit, and then interact with other control units (such as airbag control unit, body stability unit, steering control unit, etc.) through the central domain or gateway. In this process, the communication link is long, which not only affects the security and real-time performance of the communication, but also violates the original design intention of the centralized domain control architecture to reduce the cost of control unit devices and wiring harness connections.

[0003] Therefore, seeking a more efficient and secure domain control architecture has become an urgent need for the development of the industry. Summary of the invention

[0004] Based on this, it is necessary to provide a vehicle control system and a vehicle to address the above-mentioned technical problems, so as to reduce vehicle costs and improve the functional safety of the entire vehicle.

[0005] A vehicle control system comprises a central domain control unit and a plurality of regional controllers connected to the central domain control unit; The central domain control unit includes an application layer, an RTE communication layer and a basic layer, and the application layer is provided with a plurality of functional subdomain control units.

[0006] A vehicle, characterized by comprising the above-mentioned vehicle control system.

[0007] The above-mentioned vehicle control system and vehicle integrate multiple functional sub-domain control units into a central domain control unit to form a centralized domain control architecture, which can eliminate the hardware and wiring harnesses of the original domain controller and reduce costs; it can reduce external gateway signals, reduce buses and external interactive transmission links, and improve functional safety; it can directly obtain client user needs in the central domain control unit and respond to customer needs more quickly. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings required for use in the description of the embodiments of the present invention will be briefly introduced below. Obviously, the accompanying drawings in the following description are only some embodiments of the present invention. For ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without paying creative labor.

[0009] Figure 1 It is a structural schematic diagram of a vehicle control device in one embodiment of the present invention. DETAILED DESCRIPTION

[0010] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0011] In one embodiment, if Figure 1 As shown, a vehicle control system is provided, including a central domain control unit 10, and a plurality of regional controllers connected to the central domain control unit 10, such as a first regional controller 20, a second regional controller 30, a third regional controller 40, ..., an Nth regional controller 50; The central domain control unit 10 includes an application layer, an RTE communication layer and a basic layer. The application layer is provided with multiple functional subdomain control units, such as a first functional subdomain control unit 110, a second functional subdomain control unit 120, a third functional subdomain control unit 130, ..., an Nth functional subdomain control unit 140.

[0012] Understandably, the Central Domain Control Unit 10 (CDCU) is a high-level electronic control unit (ECU) that manages and coordinates multiple functional subdomain control units of the vehicle. The Central Domain Control Unit 10 processes a large amount of data from various sensors, actuators, and other regional controllers. As a key node in the vehicle control system, the Central Domain Control Unit 10 communicates with other regional controllers to exchange data and commands. The Central Domain Control Unit 10 can distribute A cores (application processor cores) and M cores (microcontroller cores) at the same time.

[0013] The software architecture inside the central domain control unit 10 can be divided into an application layer, an RTE communication layer, and a basic layer. The application layer includes all functional subdomain control units. Here, the functional subdomain control unit belongs to a software component (SWCs). These functional subdomain control units implement specific functions of the vehicle, such as power control, body control, network communication, etc.

[0014] The RTE communication layer is an important component of the vehicle control system middleware, providing a runtime environment that enables functional subdomain control units to communicate between different execution entities.

[0015] The base layer is the bottom layer of the software stack and directly interacts with the hardware resources of the central domain control unit. The base layer includes the operating system (OS), hardware abstraction layer (HAL), drivers, communication services, and diagnostic services. It provides access and control of hardware resources, as well as underlying communication services.

[0016] In some examples, the application layer includes multiple functional sub-domain control units, such as a power sub-domain control unit, a body sub-domain control unit, and a chassis safety sub-domain unit.

[0017] In this embodiment, multiple functional sub-domain control units are integrated into the central domain control unit 10 to form a centralized domain control architecture, which can eliminate the hardware and wiring harnesses of the original domain controller and reduce costs; it can reduce external gateway signals, reduce buses and external interactive transmission links, and improve functional safety; it can directly obtain client user needs in the central domain control unit 10 and respond to customer needs more quickly.

[0018] Optionally, the multiple functional sub-domain control units include a chassis safety sub-domain control unit, a body sub-domain control unit and / or a power sub-domain control unit.

[0019] It is understandable that the central domain control unit 10 can integrate multiple functional subdomain control units, such as a chassis safety subdomain control unit, a body subdomain control unit and / or a power subdomain control unit. The chassis safety subdomain control unit involves the chassis system of the vehicle, including steering, suspension, braking, stability control system (such as anti-lock braking system ABS, electronic stability control system ESC, traction control system TCS, etc.) and tire pressure monitoring system, etc. The chassis safety subdomain control unit can ensure the handling stability, safety and driving performance of the vehicle.

[0020] The body subdomain control unit is mainly responsible for the vehicle's body electronic system, including windows, doors, lights, wipers, body electronic modules (such as body control module BCM), etc. The body subdomain control unit can provide a comfortable, convenient and safe vehicle experience.

[0021] The power subdomain control unit is responsible for managing the vehicle's engine, transmission, battery (for electric vehicles), motor (for hybrid or electric vehicles) and related power control systems. The power subdomain controller ensures that the vehicle's power output is both efficient and stable, while also being responsible for emission control and energy management.

[0022] Optionally, the several zone controllers include a front zone controller, a rear zone controller, a left zone controller, a right zone controller, a cockpit domain controller and / or an intelligent driving domain controller.

[0023] It is understandable that in addition to the central domain control unit 10, multiple regional controllers can be set up, such as a front regional controller, a rear regional controller, a left regional controller, a right regional controller, a cockpit domain controller, an intelligent driving domain controller, etc.

[0024] The front area controller is responsible for the front lighting system, including headlights, daytime running lights, fog lights, etc.; controls the front wiper and washer system; manages front sensors such as radar, camera and ultrasonic sensors for adaptive cruise control, automatic emergency braking and lane keeping assist systems; monitors the status of components such as the front bumper and radiator.

[0025] The rear area controller controls the rear lighting system, such as taillights, brake lights, reverse lights, etc.; manages the backup camera and rear sensors for the reverse assist system; is responsible for the rear wiper and washer system (if the vehicle is equipped); and monitors the status of the rear bumper and other rear components.

[0026] The left zone controller controls the left turn signal and side marker lights; manages the left door module, including the windows, door locks and left camera; monitors the left blind spot monitoring system, which may include radar or ultrasonic sensors; and is responsible for part of the side collision detection system.

[0027] The right zone controller is similar to the left zone controller, but is responsible for the functions on the right side; controls the right turn signal and side marker lights; manages the right door module, including windows, door locks and right camera; monitors the blind spot monitoring system on the right side; is responsible for the side collision detection system on the right side.

[0028] The intelligent driving domain controller focuses on vehicle perception, decision-making and control, involving autonomous driving functions, driving assistance systems (such as adaptive cruise control, lane keeping assist, automatic parking, etc.) and related sensor data processing (such as radar, camera, lidar, etc.).

[0029] Optionally, any two of the functional sub-domain control units interact through the RTE communication layer; wherein the interaction interface includes an S / R interface.

[0030] Understandably, the functional subdomain control unit belongs to the internal software component of the central domain control unit and can interact directly through the RTE communication layer. The interaction interface can be an S / R interface (Sender / Receiver Port). For example, the power subdomain unit and the thermal management subdomain unit can use the S / R interface to directly interact through the RTE layer; the power subdomain unit and the chassis safety subdomain unit can use the S / R interface to directly interact through the RTE layer.

[0031] Optionally, the base layer comprises a base bottom layer; The functional subdomain control unit interacts with the basic underlying component through the RTE communication layer; wherein the interaction interface includes a C / S interface.

[0032] Understandably, the basic layer includes a variety of basic underlying components, such as diagnostic units, storage units, drive units, communication service units, etc. The functional subdomain control unit can interact with the basic underlying components through the RTE communication layer. The interactive interface can be a C / S interface (Client / Server Port). For example, the power subdomain unit and the diagnostic unit, the power subdomain unit and the storage unit can use the C / S interface to achieve the purpose of multi-interface calling.

[0033] Optionally, the functional subdomain control unit interacts with the regional controller through the RTE communication layer and the Com module; wherein the interaction interface includes a C / S interface or an S / R interface.

[0034] Understandably, the functional subdomain control unit can interact with the regional controller outside the central domain control unit 10 through the RTE communication layer and the Com module. The Com module is part of the middleware and is responsible for managing the sending and receiving of data through a specific communication protocol (such as CAN, LIN, FlexRay, Ethernet, etc.). The functional subdomain control unit interacts with the Com module through the sending and receiving ports provided by the RTE communication layer. The Com module then interacts the data with the regional controller. Here, the interaction interface can be a C / S interface, an S / R interface, or other types of interfaces that conform to the current architecture.

[0035] Optionally, the function controller associated with the function subdomain control unit is connected to the central domain control unit via a CAN bus or a CANFD bus.

[0036] Understandably, each functional subdomain control unit is associated with a corresponding functional controller. The functional controller is hardware. The functional controller can be connected to the central domain control unit via the CAN bus or the CAN FD bus. The CAN (Controller Area Network) bus is a bus protocol used for communication between devices in vehicles and other automated systems. The CAN FD (CAN with Flexible Data-Rate) bus is an extension of CAN, which allows different bit rates to be used in the same data frame, thereby increasing the data transmission rate.

[0037] Optionally, before constructing the vehicle control system, a feasibility assessment is performed on whether the central domain control unit allows integration of multiple functional subdomain control units; If the feasibility assessment is passed, the software / hardware in the functional domain controller that meets the preset requirements is connected to the central domain control unit; the functional domain controller is associated with the functional subdomain control unit; The hardware in the functional domain controller that does not meet the preset requirements is connected to the regional controller.

[0038] Understandably, in the original vehicle host domain control architecture, various functional domain controllers are included. The functional domain controller is the domain controller before being integrated into the central domain control unit. Each functional subdomain control unit has an associated functional domain controller.

[0039] Before building a new vehicle control system, it is necessary to conduct a feasibility assessment on whether the central domain control unit allows the integration of multiple functional subdomain control units. The feasibility assessment here includes the assessment of hardware drivers, processor capabilities, and memory. For example, different codes of functional subdomain control units have different storage requirements; it is necessary to evaluate whether the current central domain control unit supports the hardware drivers required by the functional subdomain control units. If the feasibility assessment fails, the software and hardware resources of the central domain control unit need to be updated.

[0040] After the feasibility assessment is passed, the software / hardware that meets the preset requirements in the original functional domain controller can be connected to the central domain control unit. Here, the preset requirements can be set according to the actual needs of the functional subdomain control unit. For the power subdomain control unit, the software / hardware that meets the preset requirements can be the drive and acquisition hardware with high real-time and safety requirements, such as the signal acquisition and control of the accelerator pedal, brake pedal, collision hard line, high-voltage emergency power-off and other hard lines. The software / hardware that does not meet the preset requirements in the functional domain controller can be connected to the regional controller outside the central domain control unit. For the power subdomain control unit, the software / hardware that does not meet the preset requirements can be the signal acquisition and drive of other auxiliary hardware, temperature sensors, water temperature sensors or other pressure sensors. Such software / hardware can be connected to the nearest regional controller. Signals can be transmitted between them through the LIN / CAN / CANFD bus.

[0041] It should be understood that each module in the above vehicle control system can be implemented in whole or in part by software, hardware, or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute operations corresponding to each module.

[0042] In one embodiment, a vehicle is provided, comprising any one of the above-mentioned vehicle control systems.

[0043] Those skilled in the art can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example. In actual applications, the above-mentioned functions can be distributed and completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above.

[0044] The embodiments described above are only used to illustrate the technical solutions of the present invention, rather than to limit the same. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be included in the protection scope of the present invention.

Claims

1. A vehicle control system, characterized in that: It includes a central domain control unit and a plurality of regional controllers connected to the central domain control unit; The central domain control unit includes an application layer, an RTE communication layer and a basic layer, and the application layer is provided with a plurality of functional subdomain control units.

2. The vehicle control system according to claim 1, characterized in that: The multiple functional sub-domain control units include a chassis safety sub-domain control unit, a body sub-domain control unit and / or a power sub-domain control unit.

3. The vehicle control system according to claim 1, characterized in that: The several area controllers include a front area controller, a rear area controller, a left area controller, a right area controller, a cockpit domain controller and / or an intelligent driving domain controller.

4. The vehicle control system according to claim 3, characterized in that: Any two of the functional sub-domain control units interact with each other through the RTE communication layer.

5. The vehicle control system according to claim 4, characterized in that: The functional subdomain control unit interacts with the RTE communication layer via an S / R interface.

6. The vehicle control system according to claim 1, characterized in that: The base layer comprises a base bottom layer member; The functional subdomain control unit interacts with the basic underlying component through the RTE communication layer; wherein the interaction interface includes a C / S interface.

7. The vehicle control system according to claim 1, characterized in that: The functional subdomain control unit interacts with the regional controller through the RTE communication layer and the Com module; wherein the interaction interface includes a C / S interface or an S / R interface.

8. The vehicle control system according to claim 1, characterized in that: The function controller associated with the function subdomain control unit is connected to the central domain control unit via a CAN bus or a CANFD bus.

9. The vehicle control system according to claim 1, characterized in that: Before constructing the vehicle control system, a feasibility assessment is performed on whether the central domain control unit allows integration of multiple functional subdomain control units; If the feasibility assessment is passed, the software / hardware in the functional domain controller that meets the preset requirements is connected to the central domain control unit; the functional domain controller is associated with the functional subdomain control unit; The hardware in the functional domain controller that does not meet the preset requirements is connected to the regional controller.

10. A vehicle, characterized in that: Comprising a vehicle control system as described in any one of claims 1 to 9.

Images