Therefore, it is increasingly important that the infotainment domain of a vehicle is able to support AUTOSAR, at least where an interaction with other domains of its electric/electronics systems is necessary. The goal of this project was to investigate how to integrate MOST into AUTOSAR in such a way that AUTOSAR systems and conventional MOST systems work together in a vehicle network seamlessly and that the AUTOSAR methodology and architecture are followed as much as possible. This paper describes the results of the concept work investigating the integration of support for the MOST network (see ) into the AUTOSAR standard (see ) for the MOST Cooperation. Details are available in the project report .
Two scenarios for the integration with AUTOSAR were prioritized, together with the Working Group Device Architecture of the MOST Cooperation, as the basis of the subsequent concept development:
- One scenario is to provide a gateway between vehicle networks running AUTOSAR and a MOST network. The use case for this scenario is to transmit messages between AUTOSAR devices on a network using AUTOSAR and native MOST devices in a MOST network connected via an AUTOSAR/MOST gateway; for example, in order to access the current speed of the vehicle from an ECU in the MOST network.
- In the second scenario the communication of two AUTOSAR applications according to the AUTOSAR standard is tunneled through a MOST network. This scenario is mainly intended to (re-)use AUTOSAR modules in a MOST network, for example a stack for diagnostic protocols.
This section will briefly describe the necessary extensions to the AUTOSAR architecture for these two main scenarios. One major challenge was to bring together the dynamic configuration and communication mechanism of a MOST network and the static configuration-oriented characteristics of the AUTOSAR stack. For example: in AUTOSAR, many network settings may be defined pre-compile time and are hard-coded into the code using code generation.