SNIP_ADAPTIVE_CAN_FIGURE_Figure_2_6_METHODOLOGY

Figure 2.6: Map software entities from Vehicle Software Architecture to ECU-Instances or Machines The overall Vehicle Hardware Architecture (as outlined in figure 2.7) covers the topology of all ECUs along with the interconnecting communication infrastructure in a vehicle. This hardware topology consists of • Nodes representing physical or virtual ECU-HW items that host either a specific CP ECU-Instance or a specific AP Machine or a specific combination of these. • Connectors between nodes representing the communication possibilities. This allows to take part in the communication clusters of the required communication technologies like CAN or Ethernet for CP and SOME/IP for AP. • Connectors for over-the-air communication (e.g. for vehicle-to-vehicle communication use cases or software update over-the-air use cases).