AUTOSAR

AUTomotive Open System ARchitecture (AUTOSAR) is a global development partnership of automotive interested parties founded in 2003. It pursues the objective to create and establish 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 whole product lifecycle.[1][2][3]

History

The AUTOSAR development partnership was formed in July 2003 by Bavarian Motor Works (BMW), Robert Bosch GmbH, Continental AG, Daimler AG (formerly Daimler-Benz, then DaimlerChrysler), Siemens VDO, and Volkswagen to develop and establish 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 of AUTOSAR.

Since 2003, AUTOSAR has provided four major releases of the standardized automotive software architecture for its Classic Platform and one release of Acceptance Tests. The work of AUTOSAR can be divided into three phases:

  • Phase I (2004–2006): Basic development of the standard (releases 1.0, 2.0, 2.1)
  • Phase II (2007–2009): Extension of the standard in architecture and methodology (releases 3.0, 3.1, 4.0)
  • Phase III (2010–2013): Maintenance and selected improvements (releases 3.2, 4.1, 4.2)[4]

In 2013, the AUTOSAR consortium 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[5] and release 18-03 in March 2018.[6] With release 18-10 in October 2018, the major development activities were finally published in a joint release of AUTOSAR Classic, Adaptive, and Foundation.[7]

Concept and goals

AUTOSAR provides a set of specifications that describes 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 and mastering the growing complexity of automotive electronic and software architectures.[4]

Based on this guiding principle, AUTOSAR has been devised to pave the way for innovative electronic systems that further improve performance, safety, and environmental friendliness and to facilitate the exchange and update of software and hardware over the service life of the vehicle. It aims to be prepared for the upcoming technologies and to improve cost-efficiency without compromising quality.[8][1]

Software architecture

AUTOSAR uses a three-layer architecture:[9]

  • Basic Software: standardized software modules (mostly) with no explicit automotive job, but offers services needed to run the functional part of the upper software layer.[10]
  • Runtime Environment (RTE): Middleware which abstracts from the network topology for the inter- and intra-ECU information exchange between the application software components and between the Basic Software and the applications.[11]
  • Application Layer: application software components that interact with the runtime environment.[12]

Methodology
  • System Configuration Description includes all system information and the information agreed between different ECUs (e.g. definition of bus signals).
  • ECU extract: contains the information from the System Configuration Description needed for a specific ECU (e.g. those signals where a specific ECU has access to).
  • ECU Configuration Description: contains all basic software configuration information that is local to a specific ECU. Use this information to build the executable software, the code of the basic software modules and the code of the software components out of it.[13]

Classic Platform

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

The AUTOSAR Classic Platform architecture distinguishes on the highest abstraction level 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
  • Electronic control unit (ECU) abstraction
  • Microcontroller abstraction

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 by using the Franca Interface Definition Language (Franca IDL).[14]

Adaptive Platform

New use-cases required the development of the Adaptive Platform. One prominent example is highly 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.

The Adaptive AUTOSAR is developed and written using the C++ which is an Object Oriented Programming language. The communication protocol used for the in-vehicle networking using the Adaptive platform is SOME/IP based on the Ethernet Communication Protocol.

For the Adaptive Platform 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:

  • Assemble functions of the Adaptive Platform
  • Define clustering of requirements specification
  • Describe behavior of software platform from application and network perspective
  • Do not constrain the final SW design of the architecture implementing the Adaptive Platform.

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:

  • Update and Configuration management
  • State Management
  • Network Management
  • Diagnostics

The AUTOSAR 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.[15][16] [17]

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.[18]

Acceptance Tests

In 2014, AUTOSAR 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.[19]

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.[20][21] 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:[22][23]

  • Core Partner
  • Strategic Partner
  • Premium Partner
  • Associate Partner
  • Development Partner
  • Attendee

Core Partners include the founding partners BMW, Bosch, Continental, Daimler AG, Ford, General Motors, PSA Peugeot Citroën, Toyota, and Volkswagen.[24] These companies are responsible for organization, administration and control of the AUTOSAR development partnership.[22] Within this core, the Executive Board defines the overall strategy and roadmap.[25] The Steering Committee manages day-to-day non-technical operations and admission of partners, public relations and contractual issues.[26] The Chairman and Deputy of Chairman, appointed for one year, represent the Steering Committee for that purpose.[27] The AUTOSAR Spokesperson takes over the communication with the outside world.[28][29]

Strategic Partners are appointed for a period of two years from the circle of Premium Partners and 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.[22][30] Associate partners are making use of the standard documents AUTOSAR has already released.[31] Attendees are currently participating with Academic collaboration and non-commercial projects.[32]

As of mid-2019, more than 270 companies participate in the AUTOSAR development partnership.[22]

gollark: Dream journal things, plausibly.
gollark: I don't think you can meaningfully do that. Atoms are smaller than the wavelength of visible light. It wouldn't make sense.
gollark: You don't use an adblocker?
gollark: Argument by analogy is mostly bad, actually.
gollark: Sounds like ecological fallacy.

References
  1. "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. "AUTOSAR: Shaping the future of a Global Standard" (PDF). Archived from the original (PDF) on 19 December 2015. Retrieved 11 December 2015.
  5. "Adaptive Platform_Release_17_10_EN" (PDF). AUTOSAR. 20 December 2017.
  6. "AUTOSAR_Release_18_03_EN" (PDF). AUTOSAR. 23 April 2018.
  7. "History". www.autosar.org. Retrieved 14 May 2018.
  8. "AUTOSAR: Motivation & Goals". Archived from the original on 19 December 2015. Retrieved 11 December 2015.
  9. "AUTOSAR: The worldwide automotive standard for e/e systems", ATZextra, Springer Fachmedien Wiesbaden, 18: 9–10, October 2013, ISSN 2195-1454
  10. "AUTOSAR: Basic Software". Archived from the original on 19 December 2015. Retrieved 11 December 2015.
  11. "AUTOSAR: Runtime Environment". Archived from the original on 19 December 2015. Retrieved 11 December 2015.
  12. "AUTOSAR: Software". Archived from the original on 19 December 2015. Retrieved 11 December 2015.
  13. "AUTOSAR: Methodology". Archived from the original on 19 December 2015. Retrieved 11 December 2015.
  14. "Classic Platform". www.autosar.org. Retrieved 2019-12-02.
  15. "Adaptive Platform". www.autosar.org. Retrieved 14 May 2018.
  16. "AUTOSAR for Intelligent Vehicles" (PDF). AUTOSAR. 29 November 2017.
  17. "AUTOSAR proofs to be THE automotive software platform for intelligent mobility" (PDF). AUTOSAR. 18 October 2017.
  18. "Foundation". www.autosar.org. Retrieved 14 May 2018.
  19. "Acceptance Test". Retrieved 14 May 2018.
  20. "AUTOSAR: Technical Overview". Archived from the original on 19 December 2015. Retrieved 11 December 2015.
  21. "Application Interface". Retrieved 14 May 2018.
  22. "AUTOSAR: Basic Information" (PDF). Archived from the original (PDF) on 19 December 2015. Retrieved 11 December 2015.
  23. "Current Partners". www.autosar.org. Retrieved 14 May 2018.
  24. "Core Partners". www.autosar.org. Retrieved 14 May 2018.
  25. "AUTOSAR: Executive Board". Archived from the original on 19 December 2015. Retrieved 11 December 2015.
  26. "AUTOSAR: Steering Committee". Archived from the original on 23 September 2015. Retrieved 11 December 2015.
  27. "Autopresse: Autonews". Retrieved 11 December 2015.
  28. "AUTOSAR: Spokesperson". Archived from the original on 19 December 2015. Retrieved 11 December 2015.
  29. "AUTOSAR Chairman handover Press Release" (PDF). AUTOSAR. 21 November 2017.
  30. "AUTOSAR: Project Leader Team". Archived from the original on 19 December 2015. Retrieved 11 December 2015.
  31. "Associate Partners". www.autosar.org. Retrieved 14 May 2018.
  32. "Attendees". www.autosar.org. Retrieved 14 May 2018.

Further reading
  • Scheid, Oliver (2015). AUTOSAR Compendium: Part 1: Application & RTE. p. 406. ISBN 978-1-50275-152-2.
  • Kindel, Olaf; Friedrich, Mario (2009). Software Development with AUTOSAR (Softwareentwicklung mit AUTOSAR). dpunkt.verlag. p. 300. ISBN 978-3-89864-563-8.
  • Autosar rev raises questions for auto design
  • GENIVI Alliance
  • ISO/IEC 15504, Software Process Improvement and Capability Determination (SPICE)
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.