AUTOSAR Software Industry Report 2020: In the Era of Software Defined Vehicles (SDV), Will an OEM Acquire an AUTOSAR Software Firm? - ResearchAndMarkets.com

DUBLIN--(BUSINESS WIRE)--The "AUTOSAR Software Industry Report, 2020" report has been added to ResearchAndMarkets.com's offering.

Software defined vehicle (SDV) and architecture defined vehicle are hotly debated among insiders recently. Yet, the technical standard - AUTOSAR are essential for them.

AUTomotive Open System ARchitecture (AUTOSAR) is a worldwide development partnership of vehicle manufacturers, suppliers, service providers and companies from the automotive electronics, semiconductor and software industry. Since 2003, they have been working on the development and introduction of several open, standardized software platforms for the automotive industry. The 'Core Partners' of AUTOSAR are the BMW Group, Bosch, Continental, Daimler, Ford, General Motors, the PSA Group, Toyota and the Volkswagen Group.

As of May 2020, AUTOSAR has accommodated 284 members, including some Chinese companies, like Great Wall Motor, FAW, Dongfeng Motor, HiRain Technologies, iSoft Infrastructure Software, SAIC and Neusoft Reach.

It seems that not many Chinese companies are on the AUTOSAR member list. Nevertheless, the Automotive Software Ecosystem Member Organization of China (AUTOSEMO), founded in July 2020, involves 9 automakers (FAW, SAIC, GAC, NIO, Geely, Great Wall Motor, Dongfeng Motor, FAW Jiefang and Xiaopeng Motors) and 6 suppliers (Neusoft Reach, HiRain Technologies, Shanghai Nasn Automotive Electronics, Shenzhen VMAX Power, Shanghai Re-Fire Technology and Horizon Robotics).

Based on AUTOSAR, AUTOSEMO is striving to develop basic software architecture standards and an industrial ecosystem that are led by Chinese companies. AUTOSEMO will temporarily not include the AUTOSAR's application programming interface API standards (body, transmission, power, chassis, passive safety, HMI, multimedia and telematics) already under development in the business scope of its standard working groups. System software and testing standards of AUTOSEMO are consistent with AUTOSAR.

Key Topics Covered:

1 AUTOSAR

1.1 Introduction to AUTOSAR

1.1.1 Briefing of AUTOSAR

1.1.2 Organization of AUTOSAR

1.1.3 Working Groups of AUTOSAR

1.1.4 AUTOSAR Groups, Boards and Task Forces

1.1.5 Members of AUTOSAR

1.1.6 History of AUTOSAR (2003-2020)

1.2 AUTOSAR Overview

1.2.1 Briefing of AUTOSAR System Architecture

1.2.2 AUTOSAR Types

1.2.3 AP/CP Comparison

1.2.4 CP/AP Evolution

1.2.5 Adaptive AUTOSAR ARA

1.2.6 AP/CP Actuation Mode

1.2.7 Adaptive AUTOSAR Platform and Classic AUTOSAR Gateway Connection

1.2.8 Classic AUTOSAR Software Layer Structure

2 Adaptive AUTOSAR and Development Roadmap

2.1 Adaptive AUTOSAR

2.1.1 Adaptive AUTOSAR

2.1.2 Illustration of Adaptive AUTOSAR

2.1.3 Three Pillars of Adaptive AUTOSAR

2.1.4 AP Methodology

2.1.5 Addressing Space Virtualization

2.2 AP Applied AA and Interfaces

2.2.1 Adaptive Application AA and IPC

2.2.2 Proceeding in OS

2.2.3 AP Is Further to Operating System (OS)

2.2.4 AP Uses Different Operating Systems for Varied Level of Safety and Real Time

2.2.5 AP Can Build Time Partition Architecture

2.3 AP as the Service-oriented Architecture

2.3.1 The Architecture Following Service-oriented Idea, SOA

2.3.2 Relation between SOA and SOME/IP

2.3.3 Service-oriented IPC (InterProcess Communication)

2.3.4 Service-oriented Architecture (SOA) Communication

2.4 AP Development Tools and Workflow

2.4.1 Starting Sequence of AP

2.4.2 Toolchain Role of Adaptive AUTOSAR

2.4.3 AP Development Tools and Workflow

2.4.4 Generation of RTE Interface

2.5 Development Route of Adaptive AUTOSAR

2.5.1 Feature (I) to Be Added to AP in Future

2.5.2 Feature (II) to Be Added to AP in Future

2.5.3 AP Roadmap

2.5.4 Development Planning of Adaptive AUTOSAR

3 Adaptive AUTOSAR Cases

3.1 Overview

3.1.1 Typical Scenarios of Adaptive AUTOSAR

3.1.2 150 AP Projects under Way

3.1.3 Volkswagen MEB: Ethernet and Adaptive AUTOSAR as the Crucial Elements

3.1.3 Volkswagen MEB: ICAS Software Reference Architecture

3.1.4 Bosch Automotive Software Architecture

3.2 Adaptive AUTOSAR and Vehicle E/E Architecture

3.2.1 AP Is an Indispensible Element to Centralized and Zonal Architectures

3.2.2 AP and Vehicle E/E Architecture Design

3.2.3 AUTOSAR Adaptive Development Process in PREEvision

3.2.4 AUTOSAR Adaptive Design Content in PREEvision

3.2.5 PREEvision in Tandem with Microsar

3.3 Adaptive AUTOSAR and OTA

3.3.1 UCM Specially Designed by Adaptive AUTOSAR for OTA

3.3.2 UCM Diagnosis

3.3.3 UCM Global State Machine

3.3.4 Software Cluster State Machine

3.3.5 UCM Master Architecture

3.3.6 UCM Software Package

3.3.7 UCM Software Package Division of Labor

3.3.8 UCM Software Package Development Process

3.3.9 OTA Update Process

3.4 Adaptive AUTOSAR and ADAS

3.4.1 Adaptive AUTOSAR Facilitates the Development of ADAS

3.4.2 Foreign Companies' Layout in ADAS/AD Domain Controllers via Use of AP

3.4.3 Chinese Companies' Layout ADAS/AD Domain Controllers via Use of AP

3.4.4 Production Plan of Vehicle Models Using Adaptive AUTOSARADAS/AD Domain Controllers

3.4.5 Bosch Automotive AI Processor Fit for AP Architecture

3.4.6 Desay SV IPU03 Based on AUTOSAR Containing Safety Components

3.4.7 Applied Case: ARA Actuation Management

3.4.7 Applied Case: ARA Communication Management

3.4.7 Applied Case: Addition of ACC Capability

4 AUTOSAR Software Developers

4.1 WindRiver

4.2 Continental Elektrobit (EB)

4.3 Vector

4.4 ETAS

4.5 KPIT

4.6 iSoft Infrastructure Software

4.7 Neusoft Reach

4.8 HiRain Technologies

4.9 TaTa Elxsi

4.10 HingeTech

4.11 Autron

4.12 Mentor Graphics

4.13 Hangzhou SMR Technology

For more information about this report visit https://www.researchandmarkets.com/r/orifm9