SPRY345B february   2022  – april 2023 DP83TG720R-Q1 , DP83TG720S-Q1 , TCAN1043A-Q1

 

  1.   At a glance
  2.   Authors
  3.   Introduction
  4.   Overcoming E/E architecture challenges
  5.   Power distribution challenges and solutions
  6.   Decentralization of power distribution
  7.   Replacing melting fuses with semiconductor fuses
  8.   Smart sensor and actuator challenges and solutions
  9.   Zonal modules –new microcontroller requirements
  10.   Smart sensors and actuators
  11.   Data challenges and solutions
  12.   Types of data
  13.   Time sensitivity of data
  14.   Communication security
  15.   Conclusion

Conclusion

Zone architecture requirements necessitate new solutions to overcome power distribution, sensor and actuator, and data communication challenges.

The transition to decentralized smart fuses, more use of smart actuators and sensors, and higher-bandwidth interfaces with the right support on very diffuse data-type combinations may address the most apparent design problems in zone architecture implementations.

These solutions will not occur all at once, but rather in a sequential evolution that introduces changes over time as and when they make sense commercially, while minimizing risk of delays for being too early. The body domain, with its many distributed actuator and sensor ECUs, will be one of the first domains that moves to the zone architecture. Transitioning of ADAS or power train and chassis control into the zone architecture may need more time.

The ultimate goal of the zone architecture is a fully software-defined vehicle that combines ideally standardized components for sensors, actuators, zonal modules and data links. With that goal in mind, very diverse ideas in many different fields are combining in a holistic fashion, enabling software-based innovation for decades to come.