Communication network architecture for EMB system

Abstract

The utility model relates to the technical field of brake-by-wire systems, in particular to a communication network architecture for an EMB system, which comprises a domain controller internally comprising a domain controller unit VM1 and a domain controller unit VM2 which are independent from each other; the EMB wheel edge actuators comprise a right front wheel actuator, a left front wheel actuator, a right rear wheel actuator and a left rear wheel actuator; the plurality of private CANs are used for connecting the domain controller units and the EMB wheel edge actuators to realize data communication; and the at least one backup CAN is used for providing a redundant path for data communication when the private CAN bus fails, in the EMB system, even if one path of EMB unit fails to affect two paths of private CAN networks, the EMB system still has at least two EMB units capable of realizing a braking function, and the reliability of the EMB system is improved. The problem of high communication load rate and the problem of CAN communication network paralysis caused by single-point failure are effectively solved.

Description

TECHNICAL FIELD

[0001] The utility model relates to a line control brake system technical field, especially relates to a communication network architecture for EMB system. BACKGROUND

[0002] In the field of online control brake system, the dynamic safety of vehicle has always been a core issue that attracts much attention. Especially under the promotion of electronic mechanical brake system (EMB), the performance and safety of brake system are improved to a new height. However, at the same time, EMB system also brings a series of new challenges, especially in safety and redundancy.

[0003] One of the remarkable features of EMB brake system is the complete decoupling of brake pedal and vehicle brake system. This design not only improves the response speed and flexibility of the system, but also provides the possibility for intelligent and adaptive control of brake system. However, this also brings a problem that cannot be ignored: since the key components of EMB system (such as brake actuator, etc.) are directly installed on the wheel knuckle, its height from the ground is much lower than that of the traditional hydraulic brake system. Hydraulic brake system is usually installed in the engine compartment, which is relatively high in position, so the risk of wading is relatively low. However, the installation environment of EMB system exposes it to a higher risk of wading, and once the system is flooded, it may cause serious failure or even safety accidents.

[0004] Therefore, the present application develops a communication network architecture for EMB system to solve the problems existing in the prior art. UTILITY MODEL CONTENT

[0005] The utility model aims at: provide a kind of communication network architecture for EMB system, to solve the problem that when one EMB unit connector is accidentally damaged in prior art, leading to communication paralysis, in turn, domain controller has no way to communicate with EMB unit and realizes brake function.

[0006] The technical scheme of the utility model is: a kind of communication network architecture for EMB system, comprising:

[0007] Domain controller, the domain controller inside includes two independent domain controller units VM1 and domain controller unit VM2;

[0008] Four EMB wheel edge actuators, which are right front wheel actuator, left front wheel actuator, right rear wheel actuator and left rear wheel actuator respectively;

[0009] A plurality of private CANs are used to connect the domain controller units and the EMB wheel edge actuators to realize data communication.

[0010] At least one backup CAN is used to provide a redundant path for data communication when the private CAN bus fails.

[0011] Preferably, the private CAN comprises at least four independent communication paths, each path connecting one domain controller unit and two EMB wheel-side actuators, forming a redundant and separated communication network.

[0012] Preferably, the private CAN comprises private CAN1, private CAN2, private CAN3 and private CAN4.

[0013] Preferably, the domain controller unit VM1 is connected with the right front wheel actuator and the left rear wheel actuator through the private CAN1, and is connected with the left front wheel actuator and the right rear wheel actuator through the private CAN2, to realize data communication and control.

[0014] Preferably, the domain controller unit VM2 is connected with the right front wheel actuator and the left rear wheel actuator through the private CAN3, and is connected with the left front wheel actuator and the right rear wheel actuator through the private CAN4, to realize data communication and control.

[0015] Preferably, the domain controller unit VM1 and the domain controller unit VM2 can independently or cooperatively work to control the operation of the EMB wheel-side actuators, improving the reliability and redundancy of the system.

[0016] Preferably, the left front wheel actuator, the right front wheel actuator, the left rear wheel actuator and the right rear wheel actuator are all connected to the backup CAN through one CAN, to provide a redundant path for data communication when the private CAN fails.

[0017] Compared with the prior art, the utility model has the advantages that:

[0018] (1) The reliability and safety of the EMB system are improved, and even in the case that one EMB unit fails and affects two private CAN networks, the EMB system still has at least two EMB units to realize the braking function;

[0019] (2) The problem of high CAN communication load rate is effectively reduced, and the EMB system runs more stably;

[0020] (3) The problems of high communication load rate and single-point failure leading to CAN communication network paralysis are effectively solved, and no hardware cost overhead is increased. BRIEF DESCRIPTION OF DRAWINGS

[0021] The utility model will be further described below in combination with the drawings and embodiments:

[0022] Figure 1The utility model discloses a communication network architecture diagram for EMB system. DETAILED DESCRIPTION

[0023] The utility model will be further explained in detail as follows in combination with specific embodiments:

[0024] As Figure 1 shown, a kind of communication network architecture for EMB system, including domain controller, EMB wheel edge executor, private CAN and backup CAN, domain controller unit VM1 is connected with the right front wheel executor and the left rear wheel executor by private CAN1, is connected with the left front wheel executor and the right rear wheel executor by private CAN2;Domain controller unit VM2 is connected with the right front wheel executor and the left rear wheel executor by private CAN3, is connected with the left front wheel executor and the right rear wheel executor by private CAN4, domain controller VM1 and domain controller VM2 as the core of communication network, responsible for receiving brake instruction from vehicle upper controller, such as brake pedal sensor, ABS controller etc., and issue instruction to corresponding EMB wheel edge executor by private CAN1, private CAN2, private CAN3 and private CAN4, EMB wheel edge executor is rotated according to received instruction, and then realizes brake through mechanical structure such as clamping device, the use of multiple private CAN can realize more flexible resource allocation, and different private CAN can be responsible for transmission different priority or different type data, to ensure that each domain controller can efficiently handle its control task, by reasonable resource allocation, can avoid resource waste and conflict, improve the operating efficiency of entire system, in the case where one EMB unit fails to affect two private CAN networks, EMB system still has at least two EMB units to realize brake function, will not affect the work of EMB system.

[0025] Further, the left front wheel actuator, the right front wheel actuator, the left rear wheel actuator and the right rear wheel actuator are all connected to the backup CAN through a CAN, and the private CAN and the backup CAN are provided with redundancy paths for the communication network, so that when the private CAN communication fails, the backup CAN can quickly take over the communication task to ensure continuous transmission of the brake command, improve the reliability and stability of the communication network, and reduce the risk of brake failure caused by communication failure. Moreover, due to the use of high-speed CAN communication technology and distributed control strategy, the communication network architecture can quickly respond to brake commands to achieve fast and accurate brake control, so that the communication network can still work normally when facing single-point failure, improve the fault tolerance and reliability of the system, and help reduce the risk of brake failure caused by communication network failure, improve the overall safety of the vehicle. Compared with the traditional hydraulic brake system, the EMB system uses electronic signals for transmission and control, greatly simplifying the wiring structure inside the vehicle, reducing the production and maintenance costs of the vehicle, and improving the maintainability and expandability of the vehicle.

[0026] The domain controller unit VM1 and the domain controller unit VM2 can work independently or cooperatively to control the operation of the EMB wheel edge actuator, improve the reliability and redundancy of the system, and when one of the domain controllers, such as VM1, fails, the other domain controller, such as VM2, can immediately take over its control task to ensure the continuous and stable operation of the EMB wheel edge actuator. Under normal circumstances, VM1 and VM2 can work cooperatively to handle control tasks together to improve the response speed and processing capacity of the system.

[0027] Under normal circumstances, the domain controller unit VM1 communicates with the right front wheel actuator, the left front wheel actuator, the right rear wheel actuator and the left rear wheel actuator through private CAN1 and private CAN2 to realize brake control, and when the domain controller unit VM1 fails, the domain controller unit VM2 communicates with the right front wheel actuator, the left front wheel actuator, the right rear wheel actuator and the left rear wheel actuator through private CAN3 and private CAN4 to realize brake control; when the domain controller unit VM1 and the domain controller unit VM2 fail at the same time, the right front wheel actuator, the left front wheel actuator, the right rear wheel actuator and the left rear wheel actuator are connected to other controllers through the backup CAN to realize brake control by sending brake requests from other controllers;

[0028] When one of the right front wheel actuator, the left front wheel actuator, the right rear wheel actuator, the left rear wheel actuator plug-in occurs a problem or an internal problem causes two private CAN failures (private CAN1 and private CAN3 or private CAN2 and private CAN4), if the right front wheel actuator failure causes private CAN1 and private CAN3 failure, at this time the domain controller unit VM1 will communicate with the left front wheel actuator and the right rear wheel actuator through private CAN2 to realize brake control, if the right front wheel actuator failure does not affect the communication of other nodes of private CAN1 and private CAN3, the domain controller unit VM1 will still communicate with the left front wheel actuator, the right rear wheel actuator, the right front wheel actuator through private CAN1 and private CAN3 to realize brake control; if the left rear wheel actuator failure causes private CAN1 and private CAN3 failure, at this time the domain controller unit VM1 will communicate with the left front wheel actuator and the right rear wheel actuator through private CAN2 to realize brake control, if the left rear wheel actuator failure does not affect the communication of other nodes of private CAN1 and private CAN3, the domain controller unit VM1 will still communicate with the left front wheel actuator, the right rear wheel actuator, the right front wheel actuator through private CAN1 and private CAN3 to realize brake control; if the left front wheel actuator failure causes private CAN2 and private CAN4 failure, at this time the domain controller unit VM2 will communicate with the left rear wheel actuator and the right front wheel actuator through private CAN3 to realize brake control, if the left front wheel actuator failure does not affect the communication of other nodes of private CAN2 and private CAN4, the domain controller unit VM2 will still communicate with the left rear wheel actuator, the right rear wheel actuator, the right front wheel actuator through private CAN2 and private CAN4 to realize brake control; if the right rear wheel actuator failure causes private CAN2 and private CAN4 failure, at this time the domain controller unit VM2 will communicate with the left rear wheel actuator and the right front wheel actuator through private CAN3 to realize brake control, if the right rear wheel actuator failure does not affect the communication of other nodes of private CAN2 and private CAN4, the domain controller unit VM2 will still communicate with the left rear wheel actuator, the left front wheel actuator, the right front wheel actuator through private CAN2 and private CAN4 to realize brake control.

[0029] The above embodiments are only for illustrating the technical concept and characteristics of the present application, and the purpose is to enable those skilled in the art to understand the content of the present application and implement it, and cannot limit the protection scope of the present application. For those skilled in the art, it is obvious that the present application is not limited to the details of the above exemplary embodiments, and can be implemented in other specific forms without departing from the spirit or basic characteristics of the present application, therefore, from any point of view, the embodiments should be regarded as exemplary and non-limiting, the scope of the present application is defined by the appended claims rather than the above description, therefore, all changes falling within the meaning and scope of the equivalent elements of the claims are intended to be included in the present application.

Claims

1. A communication network architecture for an EMB system, characterized in that, Comprising: a domain controller, which internally comprises two independent domain controller units VM1 and VM2; four EMB wheel edge actuators, which comprise a right front wheel actuator, a left front wheel actuator, a right rear wheel actuator, and a left rear wheel actuator; a plurality of private CANs for connecting the domain controller units and the EMB wheel edge actuators to realize data communication; at least one backup CAN for providing a redundant path for data communication when the private CAN bus fails.

2. The communication network architecture for an EMB system according to claim 1, wherein: The private CAN comprises at least four independent communication paths, each path connecting one domain controller unit and two EMB wheel edge actuators to form a redundant and separated communication network.

3. The communication network architecture for an EMB system of claim 2, wherein: The private CAN comprises private CAN1, private CAN2, private CAN3, and private CAN4.

4. The communication network architecture for an EMB system of claim 3, wherein: The domain controller unit VM1 is connected to the right front wheel actuator and the left rear wheel actuator through private CAN1, and to the left front wheel actuator and the right rear wheel actuator through private CAN2 to realize data communication and control.

5. The communication network architecture for an EMB system of claim 3, wherein: The domain controller unit VM2 is connected to the right front wheel actuator and the left rear wheel actuator through private CAN3, and to the left front wheel actuator and the right rear wheel actuator through private CAN4 to realize data communication and control.

6. The communication network architecture for an EMB system of claim 3, wherein: The domain controller unit VM1 and the domain controller unit VM2 can work independently or cooperatively to control the operation of the EMB wheel edge actuators, improving the reliability and redundancy of the system.

7. The communication network architecture for an EMB system of claim 3, wherein: The left front wheel actuator, the right front wheel actuator, the left rear wheel actuator, and the right rear wheel actuator are each connected to the backup CAN through a CAN to provide a redundant path for data communication when the private CAN fails.

Images