AUTOSAR

AUTOSAR
legal form	Development partnership
founding	2003
Seat	Munich (Administration)
Branch	Automotive industry
Website	www.autosar.org

AUTOSAR (AUTomotive Open System ARchitecture) is a global development partnership founded in 2003 between automobile manufacturers , suppliers and other companies in the electronics, semiconductor and software industries. Its purpose is to develop and establish an open and standardized software architecture for electronic control units (ECUs).

The goals are scalability to different vehicle and platform variants, transferability of software, consideration of availability and security requirements, cooperation between different partners, sustainable use of natural resources and maintainability over the entire " product life cycle ".

history

The AUTOSAR development partnership was founded in July 2003 by BMW , Bosch , Continental , DaimlerChrysler , Siemens VDO and Volkswagen to develop and establish an open industry standard for the automotive E / E architecture. In November 2003 Ford Motor Company joined as a core partner, and in December Peugeot Citroën Automobiles SA and Toyota Motor Corporation joined. The following November, General Motors also became a core partner. After Siemens VDO was taken over by Continental in February 2008, it is no longer an independent core partner of AUTOSAR.

Since 2003 AUTOSAR has made four main versions of the standardized automotive software architecture available for its Classic Platform and one version of Acceptance Tests. The work on the AUTOSAR Classic Platform can be divided into three phases:

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

In 2013 the AUTOSAR consortium introduced a continuous working mode for the Classic platform in order to maintain the standard and provide selected improvements (including version R4.2 and version 1.0 of the acceptance tests).

Work on the Adaptive Platform began in 2016. A first release (17-03) was published in early 2017, followed by Release 17-10 in October 2017 and Release 18-03 in March 2018. With Release 18-10 in October 2018, the most important development activities were finally in a joint version of AUTOSAR Classic, Adaptive and Foundation published together in October 2018. In the next steps, further joint publications of the three AUTOSAR platforms are to be published annually.

Concept and goals

AUTOSAR provides a number of specifications that describe basic software modules, define application interfaces and create a common development methodology based on a standardized exchange format. Basic software modules made available by the AUTOSAR Layered Software Architecture can be used in vehicles from different manufacturers and electronic components from different suppliers, which reduces research and development costs and the increasing complexity of automotive electronics and software architectures.

Software architecture

Classification

AUTOSAR uses a three-layer architecture:

• Basic software: standardized software modules (mostly) without a functional task, which offer services that are necessary to operate the functional part of the upper software level.
• Runtime environment (runtime environment RTE): middleware that abstracts from the network topology for the inter- and intra-ECU exchange of information between application software components and between the base software and applications.
• Application layer: application software components that interact with the runtime environment.

The AUTOSAR method

• The system configuration description contains all system information and information agreed between the various control units (ECU) (e.g. definition of bus signals).
• ECU extract: contains the information from the description of the system configuration that is required for a specific control unit (e.g. those signals to which a specific control unit has access).
• ECU configuration description: contains all of the basic software configuration information that is local to a specific ECU. This information is used to create the executable software, the code of the basic software modules and the code of the software components from it.

Classic platform

The AUTOSAR Classic Platform is the standard for embedded real-time ECUs based on OSEK . The most important result is the specifications.

The AUTOSAR Classic platform architecture distinguishes between three software layers at the highest level of abstraction that run on a microcontroller: application, runtime environment (RTE) and basic software (BSW). The application software layer is largely hardware-independent. Communication between software components and access to BSW takes place via RTE, which represents the complete interface for applications.

The BSW is divided into three main layers and complex drivers:

• Services,
• ECU (electronic control unit) abstraction and
• Microcontroller abstraction.

The services are also divided into functional groups that represent the infrastructure for system, storage and communication services.

The Virtual Functional Bus (VFB) is an essential concept of the Classic platform. This virtual bus is an abstract set of RTEs that have not yet been made available for specific control units and decouples the applications from the infrastructure. Communication takes place via dedicated ports, i. H. the communication interfaces of the application software must be mapped to these ports. The VFB takes over the communication within the individual control units and between the control units. From an application perspective, no detailed knowledge of technologies or lower-level dependencies is required. This supports the hardware-independent development and use of application software.

The Classic platform also enables the integration of non-AUTOSAR systems such as GENIVI using the Franca Interface Description Language (IDL).

Adaptive platform

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

In addition, Car-2-X applications require interaction with vehicles and off-board systems. This means that the system must provide secure on-board communication, support for cross-domain computing platforms, smartphone integration, integration of non-AUTOSAR systems, etc. Cloud-based services also require dedicated security measures such as secure cloud interaction and right of way for emergency vehicles. They enable remote controlled and distributed services, e.g. B. Remote diagnostics, over-the-air (OTA) updates, repairs and replacements.

To support the dynamic provision of customer applications and to provide framework conditions for those 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 by the application via a subset of POSIX according to IEEE1003.13 (namely PSE51). One of the main features of the Adaptive Platform is service-oriented communication.

Two types of interfaces are available for the Adaptive Platform: services and application programming interfaces (APIs). The platform consists of functional clusters that are grouped into services and the AUTOSAR Adaptive Platform Basis.

Functional clusters:

• Compilation of functionalities of the adaptive platform
• Definition of the clustering of requirements specifications
• Description of the behavior of the software platform from the application and network perspective
• However, it does not limit the final software design of the architecture that implements the Adaptive Platform.

Functional clusters in the AUTOSAR Adaptive Platform must be at least one instance above a (virtual) machine, while the services can be distributed in the vehicle-internal network.

Adaptive platform services include:

• Update and configuration management
• Status management
• Network management
• diagnosis

The AUTOSAR Adaptive Platform contains both specification and code. Compared to the Classic Platform, AUTOSAR is developing an implementation to shorten the validation cycle and to illustrate the underlying concepts. This implementation is available to all AUTOSAR partners.

Foundation

The purpose of the foundation is to guarantee interoperability between the AUTOSAR platforms. The Foundation contains common requirements and technical specifications (e.g. protocols) for the AUTOSAR platforms as well as the common methodology.

Acceptance tests

AUTOSAR acceptance tests were introduced in 2014 in order to minimize test effort and costs. Acceptance test specifications are system test specifications using the specified interfaces of the respective platform. They also take into account the specified behavior on the bus. They can be viewed as a black box test case for a specific platform function. The specification of standard acceptance tests for your objectives.

Standardized application interfaces

The standardization of functional interfaces between manufacturers and suppliers and the standardization of the interfaces between the various software layers is seen as the basis for achieving the technical goals of AUTOSAR. Only by standardizing specific interface contents with regard to their physical and temporal representation can the necessary integration be achieved.

organization

AUTOSAR defined six different types of membership. The partners' contribution varies depending on the type of partnership:

• Core partner
• Strategic partner
• premium partner
• Associate partner
• Development partner
• Attendees

Core partners are the founding partners BMW, Bosch, Continental, Daimler AG, Ford, General Motors, PSA Peugeot Citroën, Toyota and Volkswagen. These companies are responsible for the organization, administration and control of the AUTOSAR development partnership. In this core, the board defines the overall strategy and the timetable. The steering committee administers everyday non-technical processes and the approval of partners, public relations and contractual matters. The chairman and the deputy chairman, who are appointed for one year, represent the steering committee for this purpose. The AUTOSAR spokesperson takes over communication with the outside world.

Strategic partners are appointed from among the premium partners for a period of two years and support the project manager team in the various technical, organizational and everyday processes. They also give new strategic input to the project manager group.

Premium and development partners contribute to work packages that are coordinated and monitored by the project management team set up by the core partners. Associate partners use the standard documents that AUTOSAR has already published. Attendees are currently participating in academic collaborations and non-commercial projects.

In mid-2019, more than 270 companies are taking part in the AUTOSAR development partnership.

literature

• Oliver Scheid: AUTOSAR Compendium - Part 1: Application & RTE . 2015, ISBN 978-1-5027-5152-2 .
• Olaf Kindel, Mario Friedrich: Software development with AUTOSAR. Basics, engineering, management for practice . dpunkt.verlag, 2009, ISBN 978-3-89864-563-8 .
• Werner Zimmermann, Ralf Schmidgall: Bus systems in vehicle technology - protocols, standards and software architecture . 5th edition. Springer Vieweg, 2014, ISBN 978-3-658-02418-5 .
• Jörg Schäuffele, Thomas Zurawka: Automotive Software Engineering: Using basics, processes, methods and tools efficiently . 5th edition. Springer Vieweg, 2013, ISBN 978-3-8348-2469-1 .

See also

• OSEK / VDX - standardization body that participates in the AUTOSAR standardization process
• Association for Standardization of Automation and Measuring Systems (ASAM) and Manufacturer Supplier Relationship (MSR) - standardization in the field of exchange formats, tool interfaces
• Spice (Norm) (ISO / IEC 15504) - an evaluation scheme for software development
• Automotive SPICE - Application of Spice to the automotive sector
• Capability Maturity Model Integration - another evaluation scheme for software development

Web links

• Website for the book "AUTOSAR Compendium - Part 1: Application & RTE"
• Website of the AUTOSAR development partnership
• AUTOSAR - The Standardized Software Architecture in the IT dictionary of the GI
• Technical article about the exchange formats defined in AUTOSAR in electronics automotive
• Technical article about typical change scenarios in the development of AUTOSAR control unit software in electronics automotive
• free e-learning learning module AUTOSAR
• Free AUTOSAR poster and glossary from Vector Informatik GmbH

Individual evidence

1. ↑ Elektrobit Automotive: AUTOSAR. Retrieved November 17, 2015 . 
2. ↑ AUTOSAR. Retrieved February 24, 2020 . 
3. ↑ ^{a b} AUTOSAR: History. Retrieved February 24, 2020 . 
4. ↑ AUTOSAR - The worldwide automotive standard for e / e systems . In: ATZextra . October 2013, p. 7 .
5. ↑ AUTOSAR: FAQ. Retrieved February 24, 2020 . 
6. ↑ AUTOSAR - The worldwide automotive standard for e / e systems . In: ATZextra . October 2013, p. 9-10 .
7. ↑ AUTOSAR: Basic Software. (No longer available online.) Archived from the original on December 19, 2015 ; accessed on November 17, 2015 . Info: The archive link was inserted automatically and has not yet been checked. Please check the original and archive link according to the instructions and then remove this notice.  
8. ↑ AUTOSAR: Runtime Environment. (No longer available online.) Archived from the original on December 19, 2015 ; accessed on November 17, 2015 . Info: The archive link was inserted automatically and has not yet been checked. Please check the original and archive link according to the instructions and then remove this notice.  
9. ↑ AUTOSAR: software. (No longer available online.) Archived from the original on December 19, 2015 ; accessed on November 17, 2015 . Info: The archive link was inserted automatically and has not yet been checked. Please check the original and archive link according to the instructions and then remove this notice.  
10. ^ AUTOSAR: Methodology. (No longer available online.) Archived from the original on December 19, 2015 ; accessed on November 17, 2015 . Info: The archive link was inserted automatically and has not yet been checked. Please check the original and archive link according to the instructions and then remove this notice.  
11. ↑ AUTOSAR: Adaptive Platform. Retrieved February 24, 2020 . 
12. ↑ AUTOSAR: Foundation. Retrieved February 24, 2020 . 
13. ↑ AUTOSAR: Acceptance Test. Retrieved February 24, 2020 . 
14. ↑ AUTOSAR: Technical Overview. (No longer available online.) Archived from the original on December 19, 2015 ; accessed on November 17, 2015 . Info: The archive link was inserted automatically and has not yet been checked. Please check the original and archive link according to the instructions and then remove this notice.  
15. ↑ AUTOSAR: Application Interface. Retrieved February 24, 2020 . 
16. ↑ ^{a b c d} AUTOSAR: Basic Information. (PDF) (No longer available online.) Archived from the original on December 19, 2015 ; accessed on November 17, 2015 . Info: The archive link was inserted automatically and has not yet been checked. Please check the original and archive link according to the instructions and then remove this notice.  
17. ↑ AUTOSAR: Core Partners. (No longer available online.) Archived from the original on December 19, 2015 ; accessed on November 17, 2015 . Info: The archive link was inserted automatically and has not yet been checked. Please check the original and archive link according to the instructions and then remove this notice.  
18. ↑ AUTOSAR: Executive Board. (No longer available online.) Archived from the original on December 19, 2015 ; accessed on November 17, 2015 . Info: The archive link was inserted automatically and has not yet been checked. Please check the original and archive link according to the instructions and then remove this notice.  
19. ↑ Rüping regularly new spokesman at AUTOSAR. In: auto-presse.de. Retrieved November 17, 2015 . 
20. ^ AUTOSAR: Spokesperson. (No longer available online.) Archived from the original on December 19, 2015 ; accessed on November 17, 2015 . Info: The archive link was inserted automatically and has not yet been checked. Please check the original and archive link according to the instructions and then remove this notice.  
21. ↑ AUTOSAR - The worldwide automotive standard for e / e systems . In: ATZextra . October 2013, p. 6-7 .
22. ↑ AUTOSAR: Project Leader Team. (No longer available online.) Archived from the original on December 19, 2015 ; accessed on November 17, 2015 . Info: The archive link was inserted automatically and has not yet been checked. Please check the original and archive link according to the instructions and then remove this notice.