AUTOSAR

Last updated

AUTOSAR
Company typeDevelopment Partnership
IndustryAutomotive, E/E, Software, Semiconductor
Founded2003
HeadquartersMunich, Germany (Administration)
Key people
Michael Niklas-Höret
(Chairperson, 2024)
Members366 Companies (12/2023)
Website autosar.org

AUTomotive Open System ARchitecture (AUTOSAR) is a development partnership of automotive interested parties founded in 2003. It is focused on creating and establishing an open and standardized software architecture for automotive electronic control units (ECUs). Goals include the scalability to different vehicle and platform variants, transferability of software, the consideration of availability and safety requirements, a collaboration between various partners, sustainable use of natural resources, and maintainability during the product lifecycle. [1] [2] [3]

Contents

History

AUTOSAR was formed in July 2003 by Bavarian Motor Works (BMW), Robert Bosch GmbH, Continental AG, Mercedes-Benz Group AG (formerly Daimler-Benz, then DaimlerChrysler), Siemens VDO, and Volkswagen AG to promote an open industry standard for automotive electrical-electronic (E/E) architecture. In November 2003, Ford Motor Company joined as a core partner, and in December, Groupe PSA (formerly PSA Peugeot Citroën) and Toyota Motor Corporation joined. The following November, General Motors also became a core partner. After Siemens VDO was acquired by Continental in February 2008, it ceased being an independent core partner.

Since 2003, AUTOSAR provided four major releases of the automotive software architecture for its classic platform and one release of acceptance tests. The work can be divided into three phases:

In 2013, AUTOSAR entered a continuous working mode for its classic Platform to maintain the standard and provide selected improvements, including releases R4.2, and 1.0 of acceptance tests.

In 2016, work on the Adaptive Platform began. A first release (17-03) was published in early 2017, followed by release 17–10 in October 2017 [7] and release 18–03 in March 2018. [8] With release 18–10 in October 2018, major development activities were published. [9]

In December 2023, AUTOSAR R23-11 was virtually released. [10]

Concept and goals

AUTOSAR provides specifications of basic software modules, defines application interfaces and builds a common development methodology based on standardized exchange format. Basic software modules made available by the AUTOSAR layered software architecture can be used in vehicles of different manufacturers and electronic components of different suppliers, thereby reducing expenditures for research and development. [6]

Based on this principle, AUTOSAR aims to prepare for upcoming technologies. [11] [1]

Software architecture

AUTOSAR uses a three-layer architecture: [12]

Methodology

Classic Platform

The AUTOSAR classic platform is the standard for embedded real-time ECUs based on OSEK. Its main deliverable is specifications.

The architecture distinguishes between three software layers that run on a microcontroller: application, runtime environment (RTE) and basic software (BSW). The application software layer is mostly hardware independent. Communication between software components and access to BSW happens via RTE, which represents the full interface for applications.

The BSW is divided in three major layers and complex drivers:

Services are divided further, into functional groups representing the infrastructure for system, memory and communication services.

One essential concept of the Classic Platform is the Virtual Functional Bus (VFB). This virtual bus is an abstract set of RTEs that are not yet deployed to specific ECUs and decouples the applications from the infrastructure. It communicates via dedicated ports, which means that the communication interfaces of the application software must be mapped to these ports. The VFB handles communication within the individual ECU and between ECUs. From an application point of view, no detailed knowledge of lower-level technologies or dependencies is required. This supports hardware-independent development and usage of application software.

The Classic Platform also enables the integration of non-AUTOSAR systems such as GENIVI, now renamed COVESA, by using the Franca Interface Definition Language (Franca IDL). [18]

Adaptive platform

New use-cases required the development of the adaptive platform. One example is automated driving, in the context of which the driver temporarily and/or partially transfers responsibility for driving to the vehicle. This can require communication with traffic infrastructure (e.g. traffic signs and -lights), cloud servers (e.g. to access the latest traffic information or map data), or the use of microprocessors and high-performance computing hardware for parallel processing, e.g., graphics processing units (GPUs).

Further, Car-2-X applications require interaction to vehicles and off-board systems. That means that the system has to provide secure on-board communication, support of cross-domain computing platforms, smartphone integration, integration of non-AUTOSAR systems, and so on. Also, cloud-based services will require dedicated means for security, such as secure cloud interaction and emergency vehicle preemption. They will enable remote and distributed services, such as remote diagnostics, over the air (OTA) update, repair, and exchange handling.

To support dynamic deployment of customer applications and to provide an environment for applications that require high-end computing power AUTOSAR is currently standardizing the AUTOSAR Adaptive Platform. Its core is an operating system based on the POSIX standard. The operating system can be used from the application via a subset of the POSIX according to IEEE1003.13 (namely PSE51). One of the key features of the Adaptive Platform is service-oriented communication since the Platform is based on the Service - Oriented Architecture. [19]

Adaptive AUTOSAR is developed and written using C++ which is an object-oriented programming language. The communication protocol used for the in-vehicle networking is SOME/IP, based on Ethernet. Two types of interfaces are available: services and application programming interfaces (APIs). The platform consists of functional clusters which are grouped in services and the AUTOSAR adaptive platform foundation.

Functional clusters:

Functional clusters in AUTOSAR Adaptive Platform have to have at least one instance per (virtual) machine while services may be distributed in the in-car network.

Adaptive platform services include:

The adaptive platform contains both specification and code. In comparison to the Classic Platform, AUTOSAR develops an implementation to shorten the validation cycle and illustrate the underlying concepts. This implementation is available to all AUTOSAR partners. [20] [21] [22] [19] [23]

Foundation

The purpose of the foundation standard is to enforce interoperability between the AUTOSAR platforms. The foundation contains common requirements and technical specifications (for example protocols) shared between the AUTOSAR platforms, and the common methodology. [24] [25]

Acceptance tests

In 2014, acceptance tests were introduced to minimize test efforts and costs. Acceptance test Specifications are system test specifications using the specified interfaces of the respective Platform. Also, they are considering the specified behavior on the bus. They can be seen as a black box test case for a given platform function. The specification of standard acceptance tests contributes to these objectives. [26] [27]

Standardized application interfaces

Standardization of functional interfaces across manufacturers and suppliers and standardization of the interfaces between the different software layers is seen as a basis for achieving the technical goals of AUTOSAR. [28] [29] Only by standardizing concrete interface contents in their physical and temporal representation allows achieving the needed integration compatibility.

Organization

AUTOSAR defined six different levels of membership. The contribution of partners varies depending on the type of partnership: [30] [31]

Core Partners include the founding partners Bavarian Motor Works (BMW), Robert Bosch AG, Continental AG, Mercedes-Benz Group AG, Ford Motor Company, General Motors Holding LLC, Peugeot Citroën Automobiles S.A., Toyota Motor Corporation, and Volkswagen AG. [32] These companies are responsible for organization, administration and control of the AUTOSAR development partnership. [30] Within this core, the executive board defines the overall strategy and roadmap. [33] The Steering Committee manages day-to-day non-technical operations and admission of partners, public relations and contractual issues. [34] The chairman and Deputy of chairman, appointed for one year, represent the Steering Committee for that purpose. [35] The AUTOSAR Spokesperson takes over the communication with the outside world. [36] [37]

Premium Partner Plus companies support the project leader team in the various technical, organizational and everyday processes. They also give new strategic inputs to the project leader round.

Premium and Development members contribute to work packages coordinated and monitored by the Project Leader Team established by the Core Partners. [30] [38] Associate partners are making use of the standard documents AUTOSAR has already released. [39] Attendees are currently participating with Academic collaboration and non-commercial projects. [40]

Vendors

Selection of vendors, including RTOS, BSW, design tools, compiler, etc. [41]

Vendors which provide related tools and software, e.g. for testing, diagnostics, development, etc.

See also

Related Research Articles

<span class="mw-page-title-main">OSI model</span> Model of communication of seven abstraction layers

The Open Systems Interconnection model is a reference model from the International Organization for Standardization (ISO) that "provides a common basis for the coordination of standards development for the purpose of systems interconnection." In the OSI reference model, the communications between systems are split into seven different abstraction layers: Physical, Data Link, Network, Transport, Session, Presentation, and Application.

OSEK is a standards body that has produced specifications for an embedded operating system, a communications stack, and a network management protocol for automotive embedded systems. It has produced related specifications, namely AUTOSAR. OSEK was designed to provide a reliable standard software architecture for the various electronic control units (ECUs) throughout a car.

OpenMAX, often shortened as "OMX", is a non-proprietary and royalty-free cross-platform set of C-language programming interfaces. It provides abstractions for routines that are especially useful for processing of audio, video, and still images. It is intended for low power and embedded system devices that need to efficiently process large amounts of multimedia data in predictable ways, such as video codecs, graphics libraries, and other functions for video, image, audio, voice and speech.

<span class="mw-page-title-main">Automatic test equipment</span> Apparatus used in hardware testing that carries out a series of tests automatically

Automatic test equipment or automated test equipment (ATE) is any apparatus that performs tests on a device, known as the device under test (DUT), equipment under test (EUT) or unit under test (UUT), using automation to quickly perform measurements and evaluate the test results. An ATE can be a simple computer-controlled digital multimeter, or a complicated system containing dozens of complex test instruments capable of automatically testing and diagnosing faults in sophisticated electronic packaged parts or on wafer testing, including system on chips and integrated circuits.

MISRA C is a set of software development guidelines for the C programming language developed by The MISRA Consortium. Its aims are to facilitate code safety, security, portability and reliability in the context of embedded systems, specifically those systems programmed in ISO C / C90 / C99.

EAST-ADL is an Architecture Description Language (ADL) for automotive embedded systems, developed in several European research projects. It is designed to complement AUTOSAR with descriptions at higher level of abstractions. Aspects covered by EAST-ADL include vehicle features, functions, requirements, variability, software components, hardware components and communication. Currently, it is maintained by the EAST-ADL Association in cooperation with the European FP7 MAENAD project.

Association for Standardization of Automation and Measuring Systems or ASAM is an incorporated association under German law. Its members are primarily international car manufacturers, suppliers and engineering service providers from the automotive industry. The association coordinates the development of technical standards, which are developed by working groups composed of experts from its member companies. ASAM pursues the vision that the tools of a development process chain can be freely interconnected and allow a seamless exchange of data. The standards define protocols, data models, file formats and application programming interfaces (APIs) for the use in the development and testing of automotive electronic control units. A large amount of popular tools in the areas of simulation, measurement, calibration and test automation are compliant to ASAM standards. Compliance shall guarantee interoperability of tools from different vendors, allow data exchange without the need for converters, and facilitate the exchange of unambiguous specification between customers and suppliers.

<span class="mw-page-title-main">Vector Informatik</span>

Vector Informatik develops software tools and components for networking of electronic systems based on the serial bus systems CAN, LIN, FlexRay, MOST, Ethernet, AFDX, ARINC 429, and SAE J1708 as well as on CAN-based protocols such as SAE J1939, SAE J1587, ISO 11783, NMEA 2000, ARINC 825, CANaerospace, CANopen and more. The headquarters of the company Vector Informatik GmbH is in Stuttgart, Germany. Subsidiaries include Braunschweig, Munich, Hamburg, Regensburg along with international subsidiaries in Brazil, China, France, Italy, England, India, Japan, South Korea, Austria, Sweden, and the USA. Vector Informatik also includes Vector Consulting Services GmbH, a consultation firm specializing in optimization of technical product development. Altogether, these companies are referred to as the Vector Group.

ISO 26262, titled "Road vehicles – Functional safety", is an international standard for functional safety of electrical and/or electronic systems that are installed in serial production road vehicles, defined by the International Organization for Standardization (ISO) in 2011, and revised in 2018.

<span class="mw-page-title-main">CANape</span> Software tool by Vector Informatik

CANape is a software tool from Vector Informatik. This development software, widely used by OEMs and ECU suppliers of automotive industries is used to calibrate algorithms in ECUs at runtime.

The ETAS Group is a German company which designs tools for the development of embedded systems for the automotive industry and other sectors of the embedded industry. ETAS is 100-percent subsidiary of Robert Bosch GmbH.

The Functional Mock-up Interface defines a standardized interface to be used in computer simulations to develop complex cyber-physical systems.

<span class="mw-page-title-main">RT-RK</span> Serbian R&D company

RT-RK is a Serbian R&D company and national research institute that delivers development services and own products in the arena of real time embedded systems, with focus on consumer electronics and automotive industry. Headquartered in Novi Sad, with offices in Belgrade, Banja Luka and Osijek (Croatia) with over 550 engineers, RT-RK is one of the biggest development houses in Southeast Europe.

MODELISAR was an ITEA 2 European project aiming to improve the design of systems and of embedded software in vehicles. The MODELISAR goals were to:

dSPACE GmbH, located in Paderborn, Germany, is one of the world's leading providers of tools for developing electronic control units.

<span class="mw-page-title-main">OPEN Alliance SIG</span>

The OPEN Alliance is a non-profit, special interest group (SIG) of mainly automotive industry and technology providers collaborating to encourage wide scale adoption of Ethernet-based communication as the standard in automotive networking applications.

<span class="mw-page-title-main">Enterprise Architect (software)</span> Visual modeling and design tool

Sparx Systems Enterprise Architect is a visual modeling and design tool based on the OMG UML. The platform supports: the design and construction of software systems; modeling business processes; and modeling industry based domains. It is used by businesses and organizations to not only model the architecture of their systems, but to process the implementation of these models across the full application development life-cycle.

Unified Diagnostic Services (UDS) is a diagnostic communication protocol used in electronic control units (ECUs) within automotive electronics, which is specified in the ISO 14229-1. It is derived from ISO 14230-3 (KWP2000) and the now obsolete ISO 15765-3. 'Unified' in this context means that it is an international and not a company-specific standard. By now this communication protocol is used in all new ECUs made by Tier 1 suppliers of Original Equipment Manufacturer (OEM), and is incorporated into other standards, such as AUTOSAR. The ECUs in modern vehicles control nearly all functions, including electronic fuel injection (EFI), engine control, the transmission, anti-lock braking system, door locks, braking, window operation, and more.

<span class="mw-page-title-main">CANpie</span>

CANpie is an open source project and pursues the objective of creating and establishing an open and standardized software API for access to the CAN bus.

<span class="mw-page-title-main">Link Motion</span>

Link Motion is an automotive software and hardware company developing embedded automotive systems that have been used in the Lamborghini Huracán. Their main product is the Motion T carputer which can implement a connected vehicle gateway as a separate unit or as a part of the cockpit solution (eCockpit). The Motion T carputer runs on NXP's i.MX8 multi-OS platform, supports four in-car HD displays and hosts connectivity features on Microsoft’s connected vehicle platform, a set of services built on the Microsoft Azure cloud, such as over-the-air software and firmware updates, telemetry and diagnostics data and secure remote access.

References

  1. 1 2 "Elektrobit Automotive: AUTOSAR" . Retrieved 11 December 2015.
  2. ↑ "AUTOSAR official website". AUTOSAR. 5 June 2018.
  3. ↑ Scheid, Oliver (2015). AUTOSAR Compendium - Part 1: Application & RTE. Bruchsal: CreateSpace Independent Publishing Platform.
  4. ↑ Fennel, H.; Helmut, S.; Bielefeld, J.; et al. (2006). "Achievements and exploitation of the AUTOSAR development partnership" . Convergence 2006: 10.
  5. ↑ "AUTOSAR — The Worldwide Automotive Standard for E/E Systems". ATZextra Worldwide. 18 (9): 5–12. October 2013. doi:10.1007/s40111-013-0003-5. ISSN   2195-1470.
  6. 1 2 "AUTOSAR: Shaping the future of a Global Standard" (PDF). Archived from the original (PDF) on 19 December 2015. Retrieved 11 December 2015.
  7. ↑ "Adaptive Platform_Release_17_10_EN" (PDF). AUTOSAR. 20 December 2017. Archived from the original (PDF) on 31 December 2021. Retrieved 5 June 2018.
  8. ↑ "AUTOSAR_Release_18_03_EN" (PDF). AUTOSAR. 23 April 2018.
  9. ↑ "History". www.autosar.org. Retrieved 14 May 2018.
  10. ↑ cooperation, AUTOSAR development. "AUTOSAR R20-11 Release Event". www.autosar.org. Archived from the original on 16 April 2021. Retrieved 9 December 2020.
  11. ↑ "AUTOSAR: Motivation & Goals". Archived from the original on 19 December 2015. Retrieved 11 December 2015.
  12. ↑ "AUTOSAR: The worldwide automotive standard for e/e systems", ATZextra, Springer Fachmedien Wiesbaden, 18: 9–10, October 2013, ISSN   2195-1454
  13. ↑ "AUTOSAR: Basic Software". Archived from the original on 19 December 2015. Retrieved 11 December 2015.
  14. ↑ "AUTOSAR: Runtime Environment". Archived from the original on 19 December 2015. Retrieved 11 December 2015.
  15. ↑ "AUTOSAR: Software". Archived from the original on 19 December 2015. Retrieved 11 December 2015.
  16. ↑ "AUTOSAR: Methodology". Archived from the original on 19 December 2015. Retrieved 11 December 2015.
  17. ↑ Chaaban, Khaled; Leserf, Patrick; Saudrais, Sebastien (September 2009). "Steer-By-Wire system development using AUTOSAR methodology". 2009 IEEE Conference on Emerging Technologies & Factory Automation. Mallorca: IEEE. pp. 1–8. doi:10.1109/ETFA.2009.5347123. ISBN   978-1-4244-2727-7. S2CID   16258656.
  18. ↑ "Classic Platform". www.autosar.org. Retrieved 2 December 2019.
  19. 1 2 Furst, Simon; Bechter, Markus (June 2016). "AUTOSAR for Connected and Autonomous Vehicles: The AUTOSAR Adaptive Platform". 2016 46th Annual IEEE/IFIP International Conference on Dependable Systems and Networks Workshop (DSN-W). Toulouse, France: IEEE. pp. 215–217. doi:10.1109/DSN-W.2016.24. ISBN   978-1-5090-3688-2. S2CID   1133757.
  20. ↑ "Adaptive Platform". www.autosar.org. Retrieved 14 May 2018.
  21. ↑ "AUTOSAR for Intelligent Vehicles" (PDF). AUTOSAR. 29 November 2017.
  22. ↑ "AUTOSAR proofs to be THE automotive software platform for intelligent mobility" (PDF). AUTOSAR. 18 October 2017.
  23. ↑ Reichart, Günter; Asmus, Rinat (2021). Bertram, Torsten (ed.). "Progress on the AUTOSAR Adaptive Platform for Intelligent Vehicles". Automatisiertes Fahren 2020. Proceedings (in German). Wiesbaden: Springer Fachmedien: 67–75. doi:10.1007/978-3-658-34752-9_6. ISBN   978-3-658-34752-9. S2CID   240964305.
  24. ↑ "Foundation". www.autosar.org. Retrieved 14 May 2018.
  25. ↑ Stepanovic, Mia; Bjelica, Milan; Kastelan, Ivan; Velikic, Gordana (January 2020). "Scalable approach to extending automotive software using AUTOSAR adaptive stack". 2020 IEEE International Conference on Consumer Electronics (ICCE). Las Vegas, NV, USA: IEEE. pp. 1–2. doi:10.1109/ICCE46568.2020.9212328. ISBN   978-1-7281-5186-1. S2CID   222221057.
  26. ↑ "Acceptance Test". Archived from the original on 14 May 2018. Retrieved 14 May 2018.
  27. ↑ Rüping, Thomas; Fürst, Simon; Bechter, Markus (1 September 2015). "Zukunft von Autosar Weiter- und Neuentwicklung". ATZelektronik (in German). 10 (7): 24–29. doi:10.1007/s35658-015-0571-4. ISSN   2192-8878. S2CID   194286395.
  28. ↑ "AUTOSAR: Technical Overview". Archived from the original on 19 December 2015. Retrieved 11 December 2015.
  29. ↑ "Application Interface" . Retrieved 14 May 2018.
  30. 1 2 3 "AUTOSAR: Basic Information" (PDF). Archived from the original (PDF) on 19 December 2015. Retrieved 11 December 2015.
  31. ↑ "Current Partners". www.autosar.org. Retrieved 14 May 2018.
  32. ↑ "Core Partners". www.autosar.org. Retrieved 14 May 2018.
  33. ↑ "AUTOSAR: Executive Board". Archived from the original on 19 December 2015. Retrieved 11 December 2015.
  34. ↑ "AUTOSAR: Steering Committee". Archived from the original on 23 September 2015. Retrieved 11 December 2015.
  35. ↑ "Autopresse: Autonews" . Retrieved 11 December 2015.
  36. ↑ "AUTOSAR: Spokesperson". Archived from the original on 19 December 2015. Retrieved 11 December 2015.
  37. ↑ "AUTOSAR Chairman handover Press Release" (PDF). AUTOSAR. 21 November 2017.
  38. ↑ "AUTOSAR: Project Leader Team". Archived from the original on 19 December 2015. Retrieved 11 December 2015.
  39. ↑ "Associate Partners". www.autosar.org. Archived from the original on 28 November 2020. Retrieved 14 May 2018.
  40. ↑ "Attendees". www.autosar.org. Archived from the original on 28 November 2020. Retrieved 14 May 2018.
  41. ↑ cooperation, AUTOSAR development. "Vendor IDs". www.autosar.org. Retrieved 25 February 2021.
  42. ↑ "Generating ARXML and C code". www.ibm.com. 17 October 2017. Retrieved 10 April 2021.

Further reading

This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.