AUTOSAR Cross Platform

Methodology
illustrated using Signal/Service Translation

Robert Sakretz (Mercedes-Benz AG) AUTOSAR Open Conference 2024

11 June 2024
Agenda

► AUTOSAR Methodology
► Classic Platform Communication Matrix
► Adaptive Platform Service Definition
► AUTOSAR Signal/Service Translation
► Summary

Cross Platform Methodology - Robert Sakretz 11-Jun-24 2

AUTomotive Open System ARchitecture

Cross Platform Methodology - Robert Sakretz 11-Jun-24 3

AUTOSAR Vision OEM b
Exchangeability
between suppliers’
as of 2003
solutions
OEM c
OEM a Platform b.1
Platform b.2
Platform b.n

Supplier A Supplier B Platform c.1

➢ Chassis ➢ Chassis Platform c.2
Platform a.1 ➢ Safety Platform c.n
➢ Safety
Platform a.2 ➢ Body/ ➢ Telematics
Platform a.n Comfort
Exchangeability
between manufacturers’ OEM d
applications
Supplier C
➢ Body/Comfort
➢ Powertrain
➢ Telematics

OEM f Platform d.1

Platform d.2
Platform d.n

OEM e
Exchangeability
between vehicle
platforms
Platform f.1
Platform f.2
Platform f.n

Platform e.1
Platform e.2
Platform e.n

Cross Platform Methodology - Robert Sakretz 11-Jun-24 4

Architecture and Deployment of AUTOSAR
Example Zone-Architecture as of 2024
Vehicle ECUs based on
• Multi core μC / μP HW
• AUTOSAR Classic Platform(s)
• AUTOSAR Adaptive Platform(s)
• 3rd party partitions
Zone Zone • Encapsulated by a hypervisor
ECU ECU or similar technologies
Zone ECUs based on
High Speed Bus (Ethernet)
• Multi core μC
• AUTOSAR Classic Platform(s)
• Connected via PDU
communication to sensors and
Vehicle Vehicle
actuators
ECU ECU
• Connected via Services to
Vehicle ECUs
ECUs based on
Automotive Buses • μC HW
(e.g. CAN) • AUTOSAR Classic Platform(s)
Zone Zone • Connected to sensors and
ECU ECU actuators

Cross Platform Methodology - Robert Sakretz 11-Jun-24 5

 SW-C SW-C SW-C SW-C
Description Description Description Description

Methodology

SW-C 2
AUTOSAR
SW-C 1
AUTOSAR

SW-C 3
AUTOSAR

SW-C n
AUTOSAR
...
VFB

Virtual Functional Bus defines an

idealized interaction between Virtual Functional Bus

Application AUTOSAR Software

Components

Cross Platform Methodology - Robert Sakretz 11-Jun-24 6

 SW-C SW-C SW-C SW-C
Description Description Description Description

Methodology

SW-C 2
AUTOSAR
SW-C 1
AUTOSAR

SW-C 3
AUTOSAR

SW-C n
AUTOSAR
...
System Design

System Design takes the VFB setup

and distributes the software on the Virtual Functional Bus

available ECUs/Machines.
ECU System Constraint
Resources
System Design Description

Cross Platform Methodology - Robert Sakretz 11-Jun-24 7

 SW-C SW-C SW-C SW-C
Description Description Description Description

Methodology

SW-C 2
AUTOSAR
SW-C 1
AUTOSAR

SW-C 3
AUTOSAR

SW-C n
AUTOSAR
...
System Extract for Classic Platform ECUs

The System is partitioned into ECU

specific extracts. Virtual Functional Bus

ECU Extracts are handed over to

Tier1. ECU
System Design
System Constraint
Description
Resources

System
Extract

ECU I

AUTOSAR AUTOSAR
SW-C 1 SW-C 2

RTE
Classic Basic
Software

System
Description
Flex Ray

Cross Platform Methodology - Robert Sakretz 11-Jun-24 8

 SW-C SW-C SW-C SW-C
Description Description Description Description

Methodology

SW-C 2
AUTOSAR
SW-C 1
AUTOSAR

SW-C 3
AUTOSAR

SW-C n
AUTOSAR
...
System Extract for Classic Platform ECUs

The System is partitioned into ECU

specific extracts. Virtual Functional Bus

ECU Extracts are handed over to

Tier1. ECU
System Design
System Constraint
Description
Resources

System System
Extract Extract

ECU I ECU II

AUTOSAR AUTOSAR AUTOSAR

SW-C 1 SW-C 2 SW-C3 ...
RTE RTE
Classic Basic Classic Basic
Software Software

System
Gateway Description
Flex Ray Ethernet

Cross Platform Methodology - Robert Sakretz 11-Jun-24 9

Classic Platform AUTOSAR Stack Configuration

Application Layer

Runtime Environment
System Services Memory Crypto Off-board Communication I/O Hardware Complex
Services Services Communication Services Abstraction Drivers
Services

Onboard Memory Crypto Wireless Communication

Device Hardware Hardware Communication Hardware
Abstraction Abstraction Abstraction HW Abstraction Abstraction

Microcontroller Memory Crypto Drivers Wireless Communication I/O Drivers

Drivers Drivers Communication Drivers
Drivers

Microcontroller

Cross Platform Methodology - Robert Sakretz 11-Jun-24 10

Classic Platform AUTOSAR Stack Configuration
RTE

Communication
Signals
Manager

FlexRay TTCAN
Secure Diagnostic Eth State CAN State LIN State Generic
Diagnostic State State
SOME/IP Onboard IPDU AUTOSAR Communi- Manager Manager Manager NM interface
Log and Manager Manager
TP Communi- Multiplexer COM cation
Trace
cation Manager
NM
Coordinator
I-PDU I-PDU I-PDU I-PDU I-PDU I-PDU
XCP

PDU Router

TCP/IP Stack
I-PDU1 I-PDU1 NM
I-PDU I-PDU1 I-PDU I-PDU NM
Module
NM
See description Module
NM
CAN Tp Module
on next slide Module
FlexRay Tp J1939Tp

N-PDU N-PDU N-PDU

Communication
HW
LIN Interface
Eth Interface FlexRay Interface CAN Interface2 Abstraction
(incl. LIN TP)

L-PDU L-PDU L-PDU L-PDU

Communication Drivers

Eth Driver FlexRay Driver CAN Driver2 LIN Low Level Driver

Cross Platform Methodology - Robert Sakretz 11-Jun-24 11

 SW-C SW-C SW-C SW-C
Description Description Description Description

Methodology

SW-C 2
AUTOSAR
SW-C 1
AUTOSAR

SW-C 3
AUTOSAR

SW-C n
AUTOSAR
...
Machine Design

The System is partitioned into

Machine specific extracts. Virtual Functional Bus

Machine Designs are handed over to

Tier1. ECU
System Design
System Constraint
Description
Resources

System System Machine

Extract Extract Design

ECU I ECU II Machine

AUTOSAR AUTOSAR AUTOSAR AUTOSAR

SW-C 1 SW-C 2 SW-C3 ... SW-C n

RTE RTE Adaptive

Classic Basic Classic Basic Platform
Software Software Software

System
Gateway Description
Flex Ray Ethernet

Cross Platform Methodology - Robert Sakretz 11-Jun-24 12

Adaptive Platform Configuration
User Application

Application
Application

AUTOSAR Runtime for Adaptive applications - ARA

POSIX Platform Foundation Functional Clusters (FCs) Platform Service FCs Standardized Vehicle Service FCs
PSE51 / App/Interface FCs
C++ STL
Operating
System Communication Execution Management Diagnostic Intrusion Detection Update and Config Sensor Interfaces Vehicle Update and
Interface Management ara::exec Management System Manager Management ara:adi::sensoritf service Config Management
ara::com ara::diag ara::idsm ara::ucm service ara::vucm service

Network Management Persistency Time Synchronization Cryptography State Management

ara::nm ara::per ara::tsync ara::crypto ara::sm service

Raw Data Stream Platform Health Log and Trace

ara::rds Management ara::log
ara::phm

Firewall Core

…
ara::fw ara::core

Base Software
POSIX OS

Cross Platform Methodology - Robert Sakretz 11-Jun-24 13

Agenda

► AUTOSAR Methodology
► Classic Platform Communication Matrix
► Adaptive Platform Service Definition
► AUTOSAR Signal/Service Translation
► Summary

Cross Platform Methodology - Robert Sakretz 11-Jun-24 14

 SW-C SW-C SW-C SW-C
Description Description Description Description

SW-C 2
AUTOSAR
SW-C 1
AUTOSAR

SW-C 3
AUTOSAR

SW-C n
AUTOSAR
...

Methodology Virtual Functional Bus

From VFB to Software Component Definition

SW-C 1
AUTOSAR

SW-C 3
AUTOSAR
<<SenderReceiverInterface>> <<ClientServerInterface>>

Cross Platform Methodology - Robert Sakretz 11-Jun-24 15

 SW-C SW-C SW-C SW-C
Description Description Description Description

SW-C 2
AUTOSAR
SW-C 1
AUTOSAR

SW-C 3
AUTOSAR

SW-C n
AUTOSAR
...

Methodology Virtual Functional Bus

From Software Component Definition to Data Mapping on System

SW-C 1
AUTOSAR

SW-C 3
AUTOSAR
Signal 1 Signal 3

Signal 2 Signal 4

Cross Platform Methodology - Robert Sakretz 11-Jun-24 16

Communication Topology
System Template

Cross Platform Methodology - Robert Sakretz 11-Jun-24 17

Communication
Overview

Channel
Frame1
Pdu1
Sig1
Frame2
Pdu2
Sig21
Sig22
Sig23
Frame3
Pdu3
Sig3

Cross Platform Methodology - Robert Sakretz 11-Jun-24 18

Communication
Channel – Triggering

Channel
Frame1
Pdu1
Sig1

Cross Platform Methodology - Robert Sakretz 11-Jun-24 19

Communication
Channel – Triggering – Payload

Channel
Frame1
Pdu1
Sig1

Cross Platform Methodology - Robert Sakretz 11-Jun-24 20

Communication
Communication Connector

Channel ECU1
Frame1 s
Pdu1 s
Sig1 s
Frame2 r
Pdu2 r
Sig21 r
Sig22
Sig23
Frame3
Pdu3
Sig3

Cross Platform Methodology - Robert Sakretz 11-Jun-24 21

Communication
Channel – Communication Connector – Communication Port

Channel ECU1 ECU2 ECU3 ECU4 ECU5 ECU6

Frame1 s r r r
Pdu1 s r r r
Sig1 s r r r

Cross Platform Methodology - Robert Sakretz 11-Jun-24 22

Communication
Channel – Communication Connector – Communication Port – Triggering

Channel ECU1 ECU2 ECU3 ECU4 ECU5 ECU6

Frame1 s r r r
Pdu1 s r r r
Sig1 s r r r

Cross Platform Methodology - Robert Sakretz 11-Jun-24 23

Communication Matrix
Overview

Channel ECU1 ECU2 ECU3

Frame1 s r
Pdu1 s r
Sig1 s r
Frame2 r r s
Pdu2 r r s
Sig21 r s
Sig22 r s
Sig23 s
Frame3 s r
Pdu3 s r
Sig3 s r

Cross Platform Methodology - Robert Sakretz 11-Jun-24 24

Frame – Pdu – Signal
Definition of Network Messages

Sig11 Sig12 Sig13 Sig14 Sig21 Sig22 Sig23

PDU1 PDU2

Frame

Hierarchical Definition:
• Frame contains PDUs
• PDU contains Signals

Cross Platform Methodology - Robert Sakretz 11-Jun-24 25

Frame – Pdu – Signal
Definition of Network Messages

PDU1 PDU2

0 Frame 32

Relative Position
• Start Position of PDU in Frame

Cross Platform Methodology - Robert Sakretz 11-Jun-24 26

Frame – Pdu – Signal
Definition of Network Messages

Sig11 Sig12 Sig13 Sig14 Sig21 Sig22 Sig23

0 12 18 24 0 14 26
PDU1 PDU2

0 Frame 32

Relative Position
• Start Position of PDU in Frame
• Start Position of Signal in PDU

Cross Platform Methodology - Robert Sakretz 11-Jun-24 27

Frame – Pdu – Signal
Definition of Network Messages
12

Sig11 Sig12 Sig13 Sig14 Sig21 Sig22 Sig23

PDU1 PDU2

32 Frame

56
Size / Length defined for each
• Frame
• PDU
• Signal

Cross Platform Methodology - Robert Sakretz 11-Jun-24 28

COM Configuration PDU
TPS System Template as Upstream Definition

Signal
Endianness

Position of
Signal in PDU

Signal
Size / Length

Cross Platform Methodology - Robert Sakretz 11-Jun-24 29

COM Configuration Frame
TPS System Template as Upstream Definition

Frame
Size / Length

PDU
Endianness

Position of
PDU in Frame

PDU
Size / Length

Cross Platform Methodology - Robert Sakretz 11-Jun-24 30

Ethernet and SOME/IP on Classic Platform
Individual Signal Mappings vs. Rule-Based Signal Mapping

Traditional Communication Matrix SOME/IP Mapping

Sig22 Sig23 Sig21 Serialized

PDU2 PDU3

boolean: 1 bit
uint3, uint5
sint6, sint30
float

Cross Platform Methodology - Robert Sakretz 11-Jun-24 31

Ethernet and SOME/IP on Classic Platform
Individual Signal Mappings vs. Rule-Based Signal Mapping

Traditional Communication Matrix SOME/IP Mapping

Sig c Sig f Sig g Sig d Serialized

PDU2 PDU3

Cross Platform Methodology - Robert Sakretz 11-Jun-24 32

Ethernet and SOME/IP on Classic Platform
Individual Signal Mappings vs. Rule-Based Signal Mapping

Traditional Communication Matrix SOME/IP Mapping

Sig c Sig f Sig g Sig d Serialized

PDU2 PDU3

COM Module SOME/IP Transformer

COM Based Transformer

Cross Platform Methodology - Robert Sakretz 11-Jun-24 33

Agenda

► AUTOSAR Methodology
► Classic Platform Communication Matrix
► Adaptive Platform Service Definition
► AUTOSAR Signal/Service Translation
► Summary

Cross Platform Methodology - Robert Sakretz 11-Jun-24 34

AUTOSAR Service Interface
AUTOSAR Service may consist of:

• Events
• Operations / Methods <<ServiceInterface>>
PowerWindowInterface
• Call and Response
Events:
• Fire and Forget enum doorStatus

• Fields Operations / Methods:

power( IN percentage p, OUT status)
• Notifier
• Getter Fields:
percentage windowPosition
• Setter getWindowPosition()
setWindowPosition( IN percentage p )

Cross Platform Methodology - Robert Sakretz 11-Jun-24 35

 AUTOSAR Service Interface

<<ServiceInterface>>
PowerWindowInterface

Events:
enum doorStatus

Operations / Methods:
power( IN percentage p, OUT status)

Fields:
percentage windowPosition
getWindowPosition()
setWindowPosition( IN percentage p )

Cross Platform Methodology - Robert Sakretz 11-Jun-24 36

AUTOSAR Service Interface

<<ServiceInterface>>
PowerWindowInterface

Event:
enum doorStatus

Field:
percentage windowPosition

Cross Platform Methodology - Robert Sakretz 11-Jun-24 37

Ethernet and SOME/IP on Adaptive Platform
Initially no Individual Signal Mappings

Traditional Communication Matrix SOME/IP Mapping

Sig c Sig f Sig g Sig d Serialized

PDU2 PDU3

Cross Platform Methodology - Robert Sakretz 11-Jun-24 38

Agenda

► AUTOSAR Methodology
► Classic Platform Communication Matrix
► Adaptive Platform Service Definition
► AUTOSAR Signal/Service Translation
► Summary

Cross Platform Methodology - Robert Sakretz 11-Jun-24 39

Communication Classic and Adaptive

Adaptive Machine Classic ECU

Adaptive Application Classic SWC

Service oriented communication Signal based communication

Cross Platform Methodology - Robert Sakretz 11-Jun-24 40

Communication Classic and Adaptive

Adaptive Machine Classic ECU

Adaptive Application Classic SWC

Service oriented communication Signal based communication

Ethernet CAN

Signal / Service
Translation
SOME/IP Serialized Bytes PDU a c d b
SOME/IP
Header a b c d

Cross Platform Methodology - Robert Sakretz 11-Jun-24 41

Communication Classic and Adaptive

Adaptive Machine Classic ECU

Adaptive Application Classic SWC

Service oriented communication Signal based communication

Ethernet CAN

Gateway ECU
(Classic AUTOSAR)

SOME/IP Serialized Bytes

Signal/Service
Signal Translation
/ Service using PDU a c d b
SOME/IP
Header
Custom Application
Translationand RTE
a b c d

Cross Platform Methodology - Robert Sakretz 11-Jun-24 42

Communication Classic and Adaptive

Signal/Service Translation
in Gateway ECU may not be
desired due to “End To End”
requirements:
• Safety
• Security

Cross Platform Methodology - Robert Sakretz 11-Jun-24 43

Communication Classic and Adaptive

Classic ECU Classic ECU

Classic SWC Classic SWC
Signal based communication Signal based communication

Adaptive Machine
Adaptive Application
CAN CAN
Service oriented communication
Signal /
Service
Translation

Ethernet

Gateway ECU Gateway ECU

PDU 1
(Classic AUTOSAR) (Classic AUTOSAR) PDU 1
PDU 1

Cross Platform Methodology - Robert Sakretz 11-Jun-24 44

Communication Classic and Adaptive

Adaptive Machine Classic ECU

Process
Adaptive Application Classic SWC
translated service instance
Service oriented communication Signal based communication

Communication
Signal / Service Matrix
+
Translation signal-service
PDU Mapping

Communication Management
CAN

Gateway ECU
Ethernet
(Classic AUTOSAR)
PDU PDU

Cross Platform Methodology - Robert Sakretz 11-Jun-24 45

Need for Signal/Service Translation

struct { a : uint [0 .. 200]

b : uint [0 .. 6]
c : boolean
d : sint [-100 .. 100] }

Service Interface Sender / Receiver Interface

- Events - Data Elements

Adaptive Application Classic SWC

Service oriented communication Signal based communication

SOME/IP Serialized Bytes Com Pdu

SOME/IP
a b c d a d c b
Header

8bit 8bit 8bit 8bit 8bit 8bit 1b 3bit

Cross Platform Methodology - Robert Sakretz 11-Jun-24 46

Need for Signal/Service Translation
Full Mapping

Cross Platform Methodology - Robert Sakretz 11-Jun-24 47

Need for Signal/Service Translation
Mapping Example

Cross Platform Methodology - Robert Sakretz 11-Jun-24 48

Signal2Service detailed view

event x1 {
Adaptive a : uint8
Application b : uint8
c : boolean
d : sint8
}

a d c b

Cross Platform Methodology - Robert Sakretz 11-Jun-24 49

Signal2Service
detailed view

Cross Platform Methodology - Robert Sakretz 11-Jun-24 50

Signal/Service Translation
Translation Behavior

Cross Platform Methodology - Robert Sakretz 11-Jun-24 51

Serializer

Cross Platform Methodology - Robert Sakretz 11-Jun-24 52

Message Id

Using SOME/IP credentials

to configure
• Service Discovery
• Payload Messages

Cross Platform Methodology - Robert Sakretz 11-Jun-24 53

CommunicationConnector

Cross Platform Methodology - Robert Sakretz 11-Jun-24 54

Agenda

► AUTOSAR Methodology
► Classic Platform Communication Matrix
► Adaptive Platform Service Definition
► AUTOSAR Signal/Service Translation
► Summary

Cross Platform Methodology - Robert Sakretz 11-Jun-24 55

Architecture and Deployment of AUTOSAR
Example Zone-Architecture as of 2024
Vehicle ECUs based on
• Multi core μC / μP HW
• AUTOSAR Classic Platform(s)
• AUTOSAR Adaptive Platform(s)
• 3rd party partitions
Zone Zone • Encapsulated by a hypervisor
ECU ECU or similar technologies
Zone ECUs based on
High Speed Bus (Ethernet)
• Multi core μC
• AUTOSAR Classic Platform(s)
• Connected via PDU
communication to sensors and
Vehicle Vehicle
actuators
ECU ECU
• Connected via Services to
Vehicle ECUs
ECUs based on
Automotive Buses • μC HW
(e.g. CAN) • AUTOSAR Classic Platform(s)
Zone Zone • Connected to sensors and
ECU ECU actuators

Cross Platform Methodology - Robert Sakretz 11-Jun-24 56

Summary
Individual Signal Mappings vs. Rule-Based Signal Mapping

Traditional Communication Matrix SOME/IP Mapping

Sig c Sig f Sig g Sig d Serialized

PDU2 PDU3

Cross Platform Methodology - Robert Sakretz 11-Jun-24 57

Summary

Adaptive Machine Classic ECU

Process
Adaptive Application Classic SWC
translated service instance
Service oriented communication Signal based communication

Communication
Signal / Service Matrix
+
Translation signal-service
PDU Mapping

Communication Management
CAN

Gateway ECU
Ethernet
(Classic AUTOSAR)
PDU PDU

Cross Platform Methodology - Robert Sakretz 11-Jun-24 58

References

► AUTOSAR_CP_TPS_SystemTemplate.pdf
► AUTOSAR_AP_TPS_ManifestSpecification.pdf

► AUTOSAR_CP_EXP_VFB.pdf
► AUTOSAR_CP_TPS_SoftwareComponentTemplate.pdf
► AUTOSAR_CP_EXP_LayeredSoftwareArchitecture.pdf
► AUTOSAR_FO_PRS_SOMEIPProtocol.pdf

Cross Platform Methodology - Robert Sakretz 11-Jun-24 59

Thank You