Time-sensitive Networking in the Automotive Industry
- PDF / 802,550 Bytes
- 5 Pages / 595.276 x 790.866 pts Page_size
- 29 Downloads / 224 Views
© TSN Systems
Time-sensitive Networking in the Automotive Industry
The request for time-precise communication grows with increasing vehicle automation and the transition to serviceoriented architectures. To robustly implement such time- sensitive networks into future vehicles, the development engineers must have suitable measurement and analysis instrumentation. TSN Systems and BEB Consulting & Coaching describe the required tools and process steps.
DISRUPTIVE DEVELOPMENTS
Connectivity, electrical and automated driving are forcing the automotive industry into massive changes, and par tially, it even has to reinvent itself. Even though all vehicle areas are hit by these changes, the cut in electrics/electronics is the deepest. The current EE Architec
54
tures (EEA) are coming to their per formance limits, and at the same time, Automated Driving (AD) calls for new validation approaches because of the variants’ diversity. Almost all OEMs move from current Domain Architec tures (DA) toward Service-oriented Architectures (SoA), a move mainly driven by AD and its extended require
AUTHORS
Dipl.-Phys. Jürgen Scheuring is CEO of TSN Systems GmbH in Fulda (Germany).
Prof. Dr.-Ing. Ulrich Bernhard is CEO of BEB Consulting & Coaching in Alsbach-Hähnlein (Germany).
ments regarding safe communication, as late and/or lost information can lead to serious and even fatal consequences. PRESSURE TO ADJUST THE E /E ARCHITECTURE
There was a continuous growth over the last decades regarding functional content
as well as the number of ECUs. The complexity of the EEAs has increased tremendously, and today’s cars are typically equipped with a mixture of protocols such as LIN, CAN, MOST, Flexray, or Ethernet. Even though a share of vehicle connectivity services and calculating capacity will probably be transferred into the cloud in the near future, the pressure on the performance of In-vehicle (IV) communication net work will further increase. The demand for redundancy with SAE level 3 for safety reasons and the total integration of the vehicles into the IoT are just two examples of this. Software and feature updates in the field are other central requirements to EEA. The OEMs react to this pressure to change by converting their current DAs step by step into SoAs. At the end of this process, SoAs will consist of a small number of powerful central computers being connected via highperformance, reliable and time-sensitive data lines to so-called zonal computers to which the sensors and actuators will be linked, FIGURE 1. CONSEQUENCE FOR IN-VEHICLE COMMUNICATION
The change in EEAs is already happen ing at many OEMs. To ensure a good balance between speed of change and risk, the individual steps are targeted, for example converting the domains with the highest pressure first, like the infotainment domain. In the com munication between zonal computers and sensors and actuators, LIN and CAN networks will still be seen for some time where these established busses can place their advantages if the required data volumes do not
Data Loading...
