In the automotive industry, the zonal architecture is a design approach that organizes a vehicle’s electronic and communication systems into specific zones. These zones group components based on their function and physical location, enabling more efficient integration and simplified communication between the vehicle’s various systems. An important aspect of this architecture is the implementation of the Controller Area Network (CAN) protocol. CAN is a serial communication protocol developed specifically for automotive applications, allowing various electronic devices within a vehicle, such as sensors, actuators, and Electronic Control Units (ECUs), to communicate with each other quickly and reliably, sharing information essential for the vehicle’s operation. However, due to its limitations, there is a need for more efficient protocols like Automotive Ethernet and Controller Area Network Flexible (CAN FD), which allow for higher transmission rates and larger data packets.
To centralize information more efficiently, zonal architecture groups ECUs based on their functionalities, facilitating faster information exchange between ECUs of the same category and providing greater prioritization filtering between different categories. Examples of common zones include Safety (responsible for vehicle safety information), Powertrain (covering data related to the engine, transmission, and emission control), and Chassis (representing the vehicle’s structural functions, such as stability, steering, suspension, and braking). The article highlights how the structure of zonal architecture is constituted, explaining the physical separation and the implementation of the CAN protocol within this type of grouping. It also points out the main advantages and disadvantages of using this architecture compared to other existing ones.