ABOUT ADAPTIVE AUTOSAR

INTRODUCTION TO

ADAPTIVE AUTOSAR

Adaptive AUTOSAR

(AUTomotive Open System ARchitecture) is a development partnership of
- OEMs
- Suppliers
- Tool Vendors
- Software Vendors
- Semiconductor
- Companies

Intention

Jointly develop a de-facto standard for service oriented automotive software architecture

Motto

Cooperate on standards, compete on implementation

Flexibility

Integrating software modules from various suppliers
Introducing changes to meet the market demands of OEMs

High Computing Power (HPC) for Performance

High Computing Power(HPC) addresses requirements of high complexity, faster communications and continuous updates.
The dynamicity offered by Adaptive AUTOSAR address architecture expands the solution to the many-cores architecture.

Exchangeability

Transferability of functional SW-modules within a particular E/E-system at least at the final software linking process
Adaptability of solutions within and across vehicle product lines

Reusability

Higher penetration of "Commercial off the Shelf" SW and HW components across vehicle product lines
Improved containment of product and process complexity
and risk

Scalability

Scalability of E/E-system across the entire range of vehicle product lines
Cost optimization of scalable systems

ADAPTIVE AUTOSAR

ARCHITECTURE

Adaptive Applications: Adaptive application runs on top of the architecture and uses the services provided by ARA (AUTOASR Runtime for Adaptive Applications). ARA provides APIs for Adaptive AUTOSAR services like Software Configuration Management, Security Management, and Diagnostics.
Adaptive AUTOSAR Foundation (APIs): The Adaptive AUTOSAR foundation contains the basic services for the applications, which abstract the hardware and provides an opportunity for applications to run efficiently and to gain access down.
Adaptive AUTOSAR Services: Adaptive AUTOSAR services manages the communication between the Adaptive AUTOSAR applications.
Hardware / Virtual Machine: This is the first layer of the architecture and is referred to as a virtual machine, on which the Adaptive AUTOSAR foundation is formed, and Adaptive applications run.
POSIX: Adaptive applications typically use POSIX based OS in contrast to OSEK based OS of classic platform
Simultaneous execution of instances of Adaptive AUTOSAR on a hypervisor

Figure 1 : Adaptive AUTOSAR Architecture

LEGACY OR CLASSIC AUTOSAR TO

ADAPTIVE AUTOSAR MIGRATION PLANS

Some of the major requirements of Adaptive AUTOSAR is to address increasing high complexity, high computing power(HPC), faster communications and continuous updates are, to name a few. Here HPC (High Performance Computing) deals with the joint usage of not one, or two, but many cores, processors, GPUs and other processing units.

Adaptive AUTOSAR Platform address the challenge of static nature of Classic AUTOSAR Platform and legacy platforms which is inflexible in certain aspects. E. g. legacy platform and Classic AUTOSAR Platform already face challenges with multi-cores, not flexible to define a solid structural model for the new processing needs. Even though, higher bandwidth provided by ethernet is already use by Classic AUTOSAR Platform , but its architecture cannot fully harness its power. Here, the new architecture of Adaptive AUTOSAR Platform address this challenge. E.g. In Classic AUTOSAR Platform , its scheduling algorithm doesn’t comply to dynamically assign tasks to cores, therefore the usage at one core could be complete, while another core/s barely used. Here, the dynamicity offered by Adaptive AUTOSAR Platform address this challenge and expands the solution to the many-cores architecture.

This migration plans assure the interoperability and co-existence of Adaptive AUTOSAR Platform with Classic AUTOSAR Platform and legacy software. This enables the re-use of existing AUTOSAR classic and non-AUTOSAR compliant software along with harnessing the capabilities of dynamicity provided by HPC (High Performance Computing) using Adaptive AUTOSAR architecture

The roll-out of Adaptive AUTOSAR in vehicles does not happen in one go and is done in continuous agile manner with continuous updates.

Every car maker applies various migration scenarios depending on what kind of products are suitable at the developing phase of the specific models

Software suppliers apply the migration scenarios depending on their internal product plans and ability with respect to Adaptive AUTOSAR

As modularity & layering concepts are not new in the automotive software, in order to work out the conversion solution, one begins by comparing the existing Legacy software or AUTOSAR classic platform with Adaptive AUTOSAR architecture

Based on this a decision is made regarding the modules that can remain or be replaced by standard software

After an analysis of overlapping functionalities and integration options, a mapping of existing architecture with Adaptive AUTOSAR architecture is arrived

Communication Mechanism: Adaptive AUTOSAR supports various communication mechanism to establish inter and intra-platform communications.

S2S (Signal to Service) – Converting AUTOSAR Classic Signals and Offer same as a Service
IPC – Inter-core communication between AUTOSAR Classic and AUTOSAR Adaptive.
IPC (shared memory) for efficient data exchange across AUTOSAR Adaptive applications
SOME/IP communication over Ethernet