Introduction To Autosar Architecture
Expert-defined terms from the Masterclass Certificate in Autosar Compliance Testing and Validation course at London School of Planning and Management. Free to read, free to share, paired with a professional course.
AUTOSAR – A global development partnership of automotive manufacturers an… #
Classic AUTOSAR, Adaptive AUTOSAR. Example: a vehicle infotainment system built on AUTOSAR layers. Challenge: coordinating cross‑company standards while meeting diverse OEM requirements.
Adaptive AUTOSAR – A newer AUTOSAR platform targeting high‑performance co… #
Related: Classic AUTOSAR, POSIX. Example: autonomous driving functions that need run‑time reconfiguration. Challenge: ensuring deterministic behavior in a flexible environment.
Application Layer – The topmost AUTOSAR layer where software components (… #
Related: Runtime Environment (RTE), Basic Software (BSW). Example: an SWC that calculates fuel consumption. Challenge: mapping functional requirements to reusable components.
ARXML – AUTOSAR XML format used to describe system, software component, a… #
Related: ECU Configuration Description, Meta‑model. Example: an ARXML file defining a CAN signal mapping. Challenge: maintaining consistency between design tools and generated code.
Basic Software (BSW) – The layer beneath the RTE that provides generic se… #
Related: ECU Abstraction Layer, Microcontroller Abstraction Layer (MCAL). Example: the CAN driver module in BSW. Challenge: ensuring portability across microcontroller families.
CAN (Controller Area Network) – A widely used automotive field‑bus protoc… #
Related: FlexRay, Ethernet. Example: transmitting engine speed data over CAN. Challenge: bandwidth limitation in high‑data‑rate applications.
COM (Communication Stack) – Part of BSW that implements network protocols… #
Related: Network Management (NM), Transport Layer. Example: the CAN Transport Protocol handling multi‑frame messages. Challenge: handling protocol-specific timing constraints.
Configuration Description – A set of ARXML files that describe the mappin… #
Related: ECU Configuration, System Description. Example: assigning a task to a specific CPU core. Challenge: avoiding configuration drift during iterative development.
ECU – Electronic Control Unit, a hardware node that runs AUTOSAR software… #
Related: ECU Abstraction Layer, Microcontroller. Example: an ECU responsible for powertrain management. Challenge: integrating multiple ECUs with heterogeneous hardware.
ECU Abstraction Layer (ECU‑AL) – BSW sub‑layer that abstracts ECU‑specifi… #
g., ADC, PWM) from higher layers. Related: Microcontroller Abstraction Layer (MCAL). Example: a driver that reads sensor voltage via ECU‑AL. Challenge: providing a consistent API across different ECU designs.
ECU Configuration Description (ECU‑CD) – ARXML document that captures the… #
Related: System Description. Example: specifying the size of the diagnostic buffer. Challenge: synchronizing ECU‑CD with the actual hardware layout.
Ethernet – High‑speed automotive network technology supporting large data… #
Related: AVB (Audio Video Bridging), DoIP (Diagnostics over IP). Example: streaming high‑resolution camera data between ADAS ECUs. Challenge: guaranteeing real‑time determinism on a shared medium.
FlexRay – Deterministic, high‑bandwidth automotive network used for safet… #
Related: CAN, Ethernet. Example: coordinating chassis control messages on a FlexRay bus. Challenge: complex time‑triggered scheduling and fault tolerance.
Function Cluster – A grouping of SWCs that collectively implement a highe… #
g., powertrain). Related: Software Component (SWC). Example: a cluster that manages gear shifting logic. Challenge: managing inter‑SWC dependencies and data flow.
GENERIC AUTOSAR – The set of specifications that define the AUTOSAR archi… #
Related: Specification Release. Example: the AUTOSAR 4.4.0 release. Challenge: staying up‑to‑date with evolving standards.
HAL (Hardware Abstraction Layer) – In Adaptive AUTOSAR, the HAL provides… #
Related: POSIX. Example: HAL functions for GPIO access. Challenge: mapping HAL calls to diverse hardware platforms.
INTEGRATION TESTING – Testing phase where multiple SWCs and BSW modules a… #
Related: Unit Testing, System Testing. Example: checking data exchange between an engine control SWC and a diagnostics BSW module. Challenge: reproducing timing conditions of the production environment.
Interface – Defined ports (provided or required) of a SWC that describe t… #
Related: Port, Connector. Example: a required port for speed sensor data. Challenge: ensuring compatibility of data types across suppliers.
IP (Integration Package) – A pre‑validated set of AUTOSAR modules (often… #
Related: Software Component (SWC). Example: a pre‑certified CAN driver IP. Challenge: adapting the IP to project‑specific configuration.
ISO 26262 – International functional safety standard for road vehicles, o… #
Related: ASIL (Automotive Safety Integrity Level). Example: ensuring an SWC meets ASIL‑B requirements. Challenge: aligning AUTOSAR development processes with safety analysis.
Kernel – Part of the AUTOSAR OS that implements task management, interrup… #
Related: OS Scheduler. Example: a pre‑emptive kernel managing 10 periodic tasks. Challenge: configuring priority ceiling protocols to avoid deadlocks.
LIN (Local Interconnect Network) – Low‑cost serial network used for simpl… #
Related: CAN. Example: controlling interior lighting via LIN. Challenge: limited bandwidth and single‑master topology constraints.
Microcontroller (MCU) – The physical processor on which AUTOSAR software… #
Related: Microcontroller Abstraction Layer (MCAL). Example: an ARM Cortex‑R5 MCU in a brake ECU. Challenge: handling memory constraints while meeting performance targets.
Microcontroller Abstraction Layer (MCAL) – BSW sub‑layer that provides st… #
g., ADC, PWM). Related: ECU Abstraction Layer. Example: an MCAL driver for the CAN controller. Challenge: achieving deterministic latency across different MCU families.
OS (Operating System) – AUTOSAR OS is a real‑time operating system confor… #
Related: Kernel, Task. Example: a cyclic task executing every 10 ms. Challenge: configuring interrupt nesting without violating timing constraints.
OS Scheduler – The component of the AUTOSAR OS that decides which task ru… #
Related: Pre‑emptive Scheduling. Example: a fully pre‑emptive schedule for safety‑critical tasks. Challenge: avoiding priority inversion and ensuring bounded response times.
Port – The endpoint of a SWC interface, either provided (output) or requi… #
Related: Interface, Connector. Example: a required port for vehicle speed. Challenge: matching port data types and communication patterns across suppliers.
Pre‑emptive Scheduling – Scheduling mode where a higher‑priority task can… #
Related: OS Scheduler. Example: an emergency brake task pre‑empting a background diagnostic task. Challenge: guaranteeing that pre‑emptions do not corrupt shared resources.
RTE (Runtime Environment) – Middleware that connects SWCs to BSW and to e… #
Related: Application Layer, BSW. Example: RTE generating code to copy a sensor value from a CAN message to a SWC variable. Challenge: maintaining low overhead while supporting complex communication patterns.
Safe State – A defined system condition that ensures vehicle safety when… #
Related: Diagnostic Event Manager (DEM). Example: transitioning to limp‑home mode after an engine sensor failure. Challenge: designing safe state transitions that meet ISO 26262 requirements.
Scheduler – See OS Scheduler #
Scheduler – See OS Scheduler.
Service‑Oriented Architecture (SOA) – In Adaptive AUTOSAR, services are p… #
Related: Adaptive AUTOSAR, POSIX. Example: a navigation service offering route calculations to other ECUs. Challenge: handling service versioning and latency guarantees.
Signal – A piece of data transmitted over a network (e #
g., a CAN signal). Related: Message, ARXML. Example: a 16‑bit engine RPM signal. Challenge: ensuring proper scaling and endianness across heterogeneous ECUs.
Software Component (SWC) – A modular unit of functionality defined in AUT… #
Related: Function Cluster, RTE. Example: an SWC that implements anti‑lock braking logic. Challenge: achieving reusability while satisfying project‑specific constraints.
Software Component Template (SWC Template) – Pre‑defined skeletons that h… #
Related: SWC. Example: a template for a sensor processing SWC. Challenge: customizing templates without breaking AUTOSAR compliance.
Static Configuration – Build‑time definition of system parameters (e #
g., task priorities, memory sections). Related: Dynamic Configuration. Example: assigning a static stack size to a diagnostic task. Challenge: balancing memory usage against performance guarantees.
System Description – ARXML file that captures the overall vehicle system,… #
Related: ECU Configuration Description. Example: a system description linking an engine ECU to a transmission ECU via CAN. Challenge: keeping the system description synchronized with hardware revisions.
Time‑Triggered Architecture (TTA) – A communication paradigm where messag… #
Related: FlexRay. Example: a time‑triggered slot for brake command messages. Challenge: managing schedule changes without disrupting deterministic behavior.
Traceability Matrix – Document that maps requirements to design elements,… #
Related: Requirement Management. Example: linking a safety requirement to the corresponding SWC implementation. Challenge: maintaining accuracy as the project evolves.
Transport Layer – BSW sub‑layer that provides segmentation and reassembly… #
g., CAN TP, FlexRay TP). Related: COM. Example: splitting a 200‑byte diagnostic request into multiple CAN frames. Challenge: handling timeouts and retransmissions reliably.
Vehicle Network – The collection of communication buses (CAN, LIN, FlexRa… #
Related: Network Management (NM). Example: a mixed CAN/FlexRay topology for a midsize sedan. Challenge: ensuring interoperability across different bus technologies.
Vehicle Signal – A conceptual representation of a physical parameter (e #
g., speed, temperature) that may be mapped to one or more network signals. Related: Signal. Example: mapping vehicle speed to a CAN signal with a scaling factor. Challenge: handling unit conversion and precision loss.
Virtual Function Bus (VFB) – Logical communication layer in AUTOSAR that… #
Related: RTE. Example: a VFB connection that routes a speed signal regardless of whether it travels over CAN or Ethernet. Challenge: keeping the VFB mappings consistent with the underlying network topology.
VFB Configuration – The set of ARXML entries that define how VFB signals… #
Related: Virtual Function Bus. Example: linking a VFB signal to a FlexRay frame in the configuration. Challenge: updating VFB configuration when the physical network changes.
Vehicle Dynamics – Domain that includes functions such as braking, steeri… #
Related: Function Cluster. Example: an SWC controlling electronic stability program (ESP). Challenge: meeting strict real‑time deadlines for safety‑critical calculations.
Watchdog – A hardware or software timer that resets the ECU if the softwa… #
Related: Safety Mechanism. Example: a watchdog that triggers a reset after 200 ms of inactivity. Challenge: configuring appropriate timeout values to avoid spurious resets.
Wiring Harness – Physical set of cables that interconnect ECUs in a vehic… #
Related: Vehicle Network. Example: a harness that routes CAN‑high and CAN‑low lines to multiple ECUs. Challenge: ensuring signal integrity and proper shielding in harsh automotive environments.
XML Schema – The definition of the structure and data types used in AUTOS… #
Related: ARXML. Example: an XSD file that validates a system description. Challenge: keeping schema versions aligned with AUTOSAR releases.
Yield – In cooperative scheduling, a task voluntarily relinquishes the CP… #
Related: Cooperative Scheduling. Example: a low‑priority diagnostic task yields after processing a small data chunk. Challenge: preventing starvation of higher‑priority tasks.
Zero‑Copy Communication – Technique where data is transferred between SWC… #
Related: RTE. Example: passing a sensor buffer directly to a perception SWC via shared memory. Challenge: managing memory ownership and synchronization safely.
Adaptive AUTOSAR Execution Management (AEX) – Service that controls the l… #
Related: Service‑Oriented Architecture. Example: AEX starting an object detection service on demand. Challenge: handling graceful shutdown during fault conditions.
Application Interface (API) – Functions exposed by a BSW module for use b… #
Related: RTE. Example: the Diagnostic Communication Manager API for sending diagnostic messages. Challenge: providing a stable API across multiple AUTOSAR releases.
Bootloader – Software that initializes hardware and loads the AUTOSAR OS… #
Related: Secure Boot. Example: a bootloader that verifies a digital signature before starting the OS. Challenge: ensuring reliable recovery if the boot image is corrupted.
CAN FD (Flexible Data‑rate) – Extension of CAN that allows larger payload… #
Related: CAN. Example: transmitting a diagnostic dump over CAN FD. Challenge: backward compatibility with legacy CAN nodes.
CANoe – Vector Informatik tool used for simulation, testing, and analysis… #
Related: Test Harness. Example: using CANoe to replay recorded CAN traffic during integration testing. Challenge: aligning virtual simulation with actual ECU timing.
CANoe Test Feature (CTF) – Integrated module within CANoe that enables au… #
Related: Test Automation. Example: a CTF script that validates signal mapping against the ARXML description. Challenge: maintaining test scripts as the AUTOSAR model evolves.
Configuration Tool – Software that assists engineers in creating and edit… #
Related: ARXML. Example: a tool that auto‑assigns task priorities based on timing analysis results. Challenge: avoiding manual edits that break schema compliance.
Diagnostic Event Manager (DEM) – BSW module that records fault codes, man… #
Related: Diagnostic Communication Manager (DCM). Example: DEM storing a cylinder misfire fault. Challenge: ensuring fault storage survives power‑on resets.
Diagnostic Communication Manager (DCM) – BSW module that implements diagn… #
g., UDS) and interfaces with DEM. Related: DEM. Example: DCM handling a diagnostic session request from a scan tool. Challenge: meeting stringent timing for service response.
Dynamic Configuration – Run‑time adjustments of system parameters such as… #
Related: Static Configuration. Example: changing a diagnostic task's period in response to a low‑power mode. Challenge: guaranteeing that dynamic changes do not violate safety constraints.
ECU Calibration – Process of tuning parameters (e #
g., fuel maps) to achieve desired performance. Related: Parameter Access. Example: adjusting ignition timing via a calibration interface. Challenge: ensuring calibrated values stay within safety limits.
ECU Diagnostic Interface (EDI) – Standardized connector and protocol for… #
Related: DCM. Example: a technician connecting a scan tool to the EDI to read fault codes. Challenge: protecting the interface from unauthorized access.
ECU Software Package (ESP) – Collection of AUTOSAR BSW, RTE, and OS binar… #
Related: IP. Example: an ESP containing a certified CAN driver and memory manager. Challenge: reconciling version differences among multiple ESPs.
ECU Test Harness – Framework that provides test cases, stubs, and drivers… #
Related: Integration Testing. Example: a harness that simulates sensor inputs while exercising the brake control SWC. Challenge: accurately modeling external influences without a full vehicle.
Event‑Driven Scheduling – Scheduling approach where tasks are activated b… #
g., interrupts) rather than by a fixed time base. Related: Pre‑emptive Scheduling. Example: a task that processes a CAN message as soon as it arrives. Challenge: ensuring bounded response time under high event load.
Extended AUTOSAR – Refers to additional specifications beyond the core AU… #
Related: GENERIC AUTOSAR. Example: the AUTOSAR Adaptive Platform Security Extension. Challenge: integrating extensions without increasing system complexity.
FlexRay Time‑Triggered Schedule (TTS) – Deterministic schedule that assig… #
Related: FlexRay. Example: a TTS slot for a 10 ms periodic brake command. Challenge: coordinating schedules across multiple ECUs to avoid collisions.
Functional Safety – Discipline that ensures systems operate without causi… #
Related: ASIL. Example: designing an SWC with redundancy to meet ASIL‑D requirements. Challenge: balancing safety mechanisms against performance and cost.
Hardware #
in-the-Loop (HIL) – Test method where real ECU hardware is connected to a simulated vehicle environment. Related: Integration Testing. Example: using a HIL rig to validate engine control algorithms under varying load conditions. Challenge: achieving high‑fidelity models that accurately reflect real‑world dynamics.
ISO‑26262 ASIL (Automotive Safety Integrity Level) – Classification (A to… #
Related: Functional Safety. Example: an airbag deployment function typically classified as ASIL‑D. Challenge: mapping AUTOSAR components to ASIL levels and tracing compliance.
JTAG – Debug interface used to program and debug microcontrollers during… #
Related: Debugging. Example: using JTAG to step through the AUTOSAR OS initialization code. Challenge: ensuring secure access in production vehicles.
Layered Architecture – The hierarchical organization of AUTOSAR into Appl… #
Related: AUTOSAR. Example: a diagram showing data flow from a sensor SWC through RTE to the CAN driver. Challenge: maintaining clear boundaries while allowing cross‑layer optimizations.
Linker Script – Configuration file that defines memory layout for the com… #
Related: Static Configuration. Example: placing the OS kernel in a protected flash region. Challenge: avoiding memory overlap when adding new BSW modules.
Memory Protection Unit (MPU) – Hardware feature that enforces access rest… #
Related: Safety Mechanism. Example: configuring the MPU to prevent a low‑priority task from writing to the OS stack. Challenge: configuring MPU entries without excessive overhead.
Microcontroller Unit (MCU) Clock – Timing source that drives the processo… #
Related: OS Scheduler. Example: a 80 MHz clock used for a high‑performance ECU. Challenge: handling clock drift and ensuring deterministic task timing.
Network Management (NM) – BSW module that controls the state of communica… #
g., wake‑up, sleep). Related: COM. Example: NM putting the CAN bus into sleep mode when the vehicle is off. Challenge: coordinating NM actions across multiple network types.
OS Application – A logical grouping of tasks, resources, and events that… #
Related: OS. Example: an OS application for powertrain control containing several periodic tasks. Challenge: allocating resources to avoid over‑commitment.
POSIX (Portable Operating System Interface) – Set of standards for Unix‑l… #
Related: Adaptive AUTOSAR. Example: using POSIX threads to implement a perception service. Challenge: mapping POSIX semantics onto real‑time automotive constraints.
Pre‑compile RTE – RTE generation mode where communication code is generat… #
Related: RTE. Example: a pre‑compiled RTE that directly calls a CAN driver function. Challenge: limited flexibility when runtime reconfiguration is needed.
Process Isolation – Technique used in Adaptive AUTOSAR to separate applic… #
Related: Security. Example: running the navigation service in its own process space. Challenge: managing inter‑process communication latency.
Project Configuration Management (PCM) – System that tracks versions of A… #
Related: Traceability Matrix. Example: using Git to manage AUTOSAR model revisions. Challenge: preventing divergent branches that cause integration errors.
RTE Generator – Tool that reads ARXML descriptions and produces C code fo… #
Related: RTE. Example: generating RTE code for a speed sensor SWC. Challenge: ensuring generated code meets performance and memory constraints.
Runtime Parameter Access (RPA) – Mechanism that allows parameters to be r… #
Related: Calibration. Example: reading the current fuel injection timing via a UDS request. Challenge: protecting critical parameters from unauthorized changes.
Safety Mechanism – Feature designed to detect and mitigate faults, such a… #
Related: Safe State. Example: a safety mechanism that disables torque output on sensor failure. Challenge: verifying that mechanisms activate reliably under all fault scenarios.
Scalable Vector Graphics (SVG) for AUTOSAR Diagrams – Format used to repr… #
Related: System Description. Example: an SVG showing the mapping of VFB signals to physical CAN messages. Challenge: keeping the diagram synchronized with the underlying ARXML model.
Secure Boot – Process that verifies the authenticity of AUTOSAR software… #
Related: Bootloader. Example: verifying the OS image signature during power‑up. Challenge: managing key distribution and revocation in the supply chain.
Software Component Instance (SWC Instance) – Specific occurrence of a SWC… #
Related: SWC. Example: two instances of a generic sensor processing SWC, each configured for a different sensor type. Challenge: avoiding name clashes and ensuring correct mapping in the RTE.
Software Package (SWP) – Bundle of AUTOSAR modules, including source code… #
Related: IP. Example: a SWP containing a certified CAN FD driver. Challenge: integrating multiple SWPs with differing configuration philosophies.
Static Timing Analysis (STA) – Method to verify that all tasks meet their… #
Related: OS Scheduler. Example: using a tool to confirm that an ABS control task finishes within 2 ms. Challenge: obtaining accurate WCET measurements for complex code.
System Integration Test (SIT) – Testing phase where all ECUs, networks, a… #
Related: HIL. Example: verifying that the driver assists correctly responds to brake pedal input across the vehicle. Challenge: reproducing real‑world driving scenarios in a controlled lab.
Task – Unit of execution defined in the AUTOSAR OS, which can be periodic… #
Related: OS Scheduler. Example: a 5 ms cyclic task that reads wheel speed sensors. Challenge: assigning priorities to avoid missed deadlines.
Test Case – Defined set of inputs, execution steps, and expected outcomes… #
Related: Traceability Matrix. Example: a test case that checks the correct handling of an over‑voltage condition. Challenge: achieving full coverage without excessive test duplication.
Test Harness – Framework that provides simulated inputs and captures outp… #
Related: Unit Testing. Example: a harness that feeds synthetic CAN frames to a diagnostics SWC. Challenge: ensuring the harness faithfully reproduces timing and concurrency aspects.
Time‑Triggered Communication (TTC) – Communication scheme where messages… #
Related: FlexRay. Example: a TTC slot for torque request messages. Challenge: re‑synchronizing schedules after a bus reset.
Traceability – The ability to link each requirement to its implementation… #
Related: Traceability Matrix. Example: tracing a safety requirement to the corresponding SWC code and test results. Challenge: maintaining traceability as the model evolves.
Transport Protocol (TP) – Layer that handles segmentation of large data u… #
Related: Transport Layer. Example: CAN TP splitting a 300‑byte diagnostic dump into multiple frames. Challenge: managing retransmission timers under high bus load.
UML (Unified Modeling Language) – Modeling language sometimes used to des… #
Related: System Description. Example: a UML diagram showing relationships among SWCs and BSW modules. Challenge: keeping UML models synchronized with ARXML files.
UDS (Unified Diagnostic Services) – Standard diagnostic protocol (ISO 142… #
Related: DCM. Example: a service to clear stored DTCs. Challenge: meeting the response time constraints defined by the standard.
Vehicle Dynamics Interface (VDI) – Set of signals and services that expos… #
Related: Virtual Function Bus. Example: providing yaw rate and lateral acceleration to a stability controller. Challenge: ensuring data freshness and synchronization across ECUs.
Virtual Function Bus (VFB) Mapping – Definition of how logical signals ar… #
Related: VFB Configuration. Example: mapping a VFB speed signal to a CAN message ID 0x120. Challenge: updating mappings when bus topology changes.
Watchdog Timer (WDT) – Hardware timer that forces a reset if software fai… #
Related: Safety Mechanism. Example: a WDT set to 100 ms for a safety‑critical ECU. Challenge: configuring the timeout long enough to avoid false resets but short enough to recover quickly.
XML Metadata – Additional information stored in ARXML files, such as vers… #
Related: XML Schema. Example: a metadata tag indicating the AUTOSAR release used for a particular component. Challenge: ensuring metadata is updated automatically by generation tools.
Zero‑Latency Path – Communication route in AUTOSAR where data is transfer… #
Related: Zero‑Copy Communication. Example: a sensor data path from an ADC driver directly to a control SWC. Challenge: preserving data integrity while bypassing standard marshaling.