Cross-standard Lead Working Groups

WG-A (Lead Working Group Architecture)

Technical Scope

WG-A is the lead working group which deals with all software architectural design decisions in AUTOSAR (Adaptive and Classic Platform).

For Classic Platform this is related to:

  • Maintain and extend the existing Classic Platform (Layered SW Architecture; BSW; API)

For Adaptive Platform this is related to:

  • Maintain and extend the existing Adaptive Platform (Service Oriented Architecture; ARA API)

For both platforms this is related to (lead working group):

  • Foundation
  • Assessment of all standard related concepts
  • Mandatory vote in CCB

WG-MT (Lead Working Group Methodology & Templates)

Technical Scope

WG-MT is responsible for the definition of the overall AUTOSAR methodology and all template-, manifest-documents / exchange formats, including

  • System Template
  • Software Component Template
  • Manifest Specification
  • ECU Configuration Template
  • Basic Software Module Description Template
  • ECU Resource Template
  • Standardization Template
  • Generic Structure Template
  • Timing Extensions
  • Methodology

WG-SEC (Lead Working Group Security)

Technical Scope

  • Maintain and improve Security features in Adaptive and Classic Platform
  • Provide new features and maintain existing features at ECU level / In vehicle network / E/E architecture or connected vehicle that enable the development of secure systems
  • Ensure interoperability between Adaptive and Classic Platform:
    • At network level : Secure Communication between platforms / Secure Time Synchronization
    • At feature level : CryptoAPI that allows usage of different software or hardware implementation /key management and certificate handling / logging of security events / secure diagnostics.
  • Assist, coordinate and propose priority for security concepts and provide assessment of the affected standard (AP/CP).
  • Provide security expertise to other Working Group

WG-SAF (Lead Working Group Safety)

Technical Scope

WG-SAF is responsible for all requirements for Classic and Adaptive Platform with regards to ISO 26262. This includes cross-standard topics and reviews of safety related topics in Adaptive Platform and Classic Platform.

  • Safety Architecture:
    • Check the Requirement document(s) and Explanatory documents against established Safety requirements/Concepts
  • E2E protection for FO, CP and AP
    • Evolution of existing requirement specifications, specifications and explanatory documentation and code
    • Development of new concepts
    • Specification and code development
  • PHM development in FO, CP and AP
    • Evolution of existing requirement specifications, specifications and explanatory documentation and code
    • Development of new concepts
    • Specification and code development

Cross-standard Working Groups

WG-AIF (Working Group Application Interfaces)

Technical Scope

WG-AIF standardize interfaces between different application domains need to be identified and maintained in order to assure the compatibility of ECUs like powertrain and transmission management systems from different vendors.

This includes:

  • Standardize application interfaces in terms of syntax and semantics for well-established applications in order to emphasize software reuse and exchange
  • Standardize the common language: Keywords, Units, Datatypes
  • Design pattern catalogue and device abstraction approaches

In Adaptive Platform Automated Driving Interfaces are standardized to define interfaces between sensor services and automated driving functions based on ISO-23150. Objective is the specification of logical interfaces containing characteristics like object classification, position, speed, direction etc.

The interfaces are based on Adaptive Platform middleware ara::com.


WG-IVC (Working Group In-Vehicle Communication)

Technical Scope

WG-IVC deals with all aspects of communication between applications both for Adaptive and Classic Platform. This includes the communication protocols defined in the Foundation.

For CP this is related to:

  • Maintain and extend the existing Classic Platform (Communication stack)

For AP this is related to:

  • Maintain and extend the existing Adaptive Platform (ara::com, Network Management)

For both platforms this is related to Foundation:

  • SOME/IP protocol
  • Network Management protocol

WG-V2X (Working Group Vehicle2X)

Technical Scope

Work on rollout of V2X to Adaptive Platform including specification and Demonstrator Implementation.

  • Adaptive and Classic Platform:
    • Extension of V2X specific security topics in AUTOSAR
    • Specification of Triggering Conditions as AUTOSAR Application
  • Classic Platform:
    • Extend the specs by debugging, logging, fault injection and stimulation functionalities
    • Extend for new message types
    • Support for Day-n-scenarios based on C2C consortium results
    • Analysis of new V2X features and specification of respective functionality
    • Maintenance of the current specifications (handling and incorporation of change requests)
  • Support for harmonization within Europe:
    • An agreed common version for C2C (car to car) and C-Roads (vehicle to infrastructure) specifications shall be available for Europe
  • Ensure interoperability of implementation of different vendors
  • Harmonization with and integration of region-specific V2X parts

WG-DIA (Working Group Diagnostics)

Technical Scope

WG-DIA deals with all Diagnostic requirements in AUTOSAR (Adaptive and Classic Platform) by,

  • Defining the Diagnostic Basic Software modules (Classic Platform) & Functional Clusters (Adaptive Platform)
  • Defining system and software specifications for Diagnostic Services
  • Ensuring the compliance with Diagnostic related ISO standards like UDS and DoIP

WG-RES (Working Group Resources)

Technical Scope

WG-RES is an enabler for visualizing, analyzing, debugging, optimizing, supervising and testing automotive embedded systems.

This is related to:

  • functional aspects as well as the platform resources "time" and "memory"
  • all levels (car2X, network, RTOS, code)
  • all phases of the development (requirements, design, implementation, integration, test, after-market/maintenance/in-the-field)
  • all specification scopes (Classic Platform and Adaptive Platform)

Realized by definition of specific interfaces and specific methodology.


WG-UCM (Working Group Update and Configuration Management)

Technical Scope

WG-UCM is an enabler for OTA updates (Update over The Air) considering the vehicle infrastructure. This includes a master-subordinate mechanism inside a vehicle E/E-architecture to be able to update Classic and Adaptive Platform instances as well as defining a agnostic solution for the software package (i.e. the artifact containing the software to be updated) itself.

This is related to:

  • software package format
  • install/update/upgrade/deletion of software packages on Adaptive Platform instances
  • manage and trigger flash-jobs on Classic instances
  • resolve dependencies of software packages (including calibration data)
  • initiate and manage roll-back of faulty installations
  • manage the installation history

Scope shall be achieved by definition of interfaces and methodology.