Contents

AUTOSAR Adaptive Platform

The service-oriented AUTOSAR platform for high-performance computers: POSIX operating system, C++ applications, dynamic deployment and updates.

Why it exists

Central computers run software that changes often, is deployed as packages and communicates through services. The static Classic Platform does not fit that. The Adaptive Platform, first released in 2017, standardises a dynamic, service-oriented environment.

What it is

  • Runs on a POSIX operating system (e.g. QNX, Linux).
  • Applications are C++ processes grouped into deployable packages.
  • Functional clusters provide services: communication (ara::com), Execution Management, State Management, Update & Configuration Management (UCM), Diagnostics, Persistency, Identity & Access Management, Crypto, Log & Trace and more.

How it works

Applications describe what they provide and require; the platform starts processes according to machine states, connects services via SOME/IP, DDS or local IPC, and installs updates through UCM.

When to use it

On HPCs and powerful zone or domain computers where software is updated frequently and communicates via services. Many OEMs combine Adaptive with in-house or open-source stacks.

Best practices

  • Separate platform and application release cycles.
  • Version service interfaces strictly.
  • Keep safety-critical control on a certified partition or safety island.

Common pitfalls

  • Expecting Classic-style determinism from a general-purpose OS without timing analysis.

What it means for your discipline

  • HPC & application software Core

    Application developers on HPCs build against ara::com and the Adaptive functional clusters.

  • Base software Core

    Platform teams integrate and configure Execution, State, Update & Configuration Management, communication and diagnostics.

  • Cybersecurity Partial

    Identity and access management, crypto services, secure communication and intrusion detection are part of the platform.

  • Functional safety Partial

    Safety on Adaptive relies on the OS, platform health management and partitioning; full ASIL D is usually achieved with help of a safety island.

  • Diagnostics & lifecycle Partial

    Provides diagnostic services and update management (UCM) for software packages.

  • Software update & OTA Partial

    Integrates update clients with Update & Configuration Management (UCM) to install software packages and coordinate activation with execution and machine states.

No direct stake: E/E architecture · Hardware & silicon · Networks & communication

Where it sits in the software stack

Generic layered software of a central HPC (application processor with hypervisor, plus a safety island) and of a classic MCU-based ECU (AUTOSAR Classic). Highlighted modules matter for this topic. Click any module to open its page.

HPC · application processor (MPU) and safety island (MCU)
  • AUTOSAR Adaptive — Provides ara::com, Execution Management, State Management and Platform Health Management for Adaptive applications.
  • QNX / RT Linux — Provides the POSIX operating system on which Adaptive processes run, with timing guarantees requiring separate analysis.
  • SOME/IP · DDS — Carries service communication over SOME/IP or DDS beneath Adaptive communication APIs.
  • OTA client · UCM — UCM installs software packages and coordinates activation with execution and machine states.
MCU-based ECU · AUTOSAR Classic

Not directly involved on this node type.