Table of Content

1 Introduction to AUTOSAR
1.1 Overview of AUTOSAR
1.1.1 Introduction to Background and Purposes of AUTOSAR (1)
1.1.2 Introduction to Background and Purposes of AUTOSAR (2)
1.1.3 AUTOSAR Architecture
1.1.4 AUTOSAR Interfaces
1.1.5 AUTOSAR Basic Software Layer (1)
1.1.6 AUTOSAR Basic Software Layer (2)
1.1.7 AUTOSAR Packages Basic Software Which Can Be Called by Upper-layer Applications through Standardized Interfaces
1.1.8 AUTOSAR Development Flow (1)
1.1.9 AUTOSAR Development Flow (2)

1.2 Classification of AUTOSAR
1.2.1 Types of AUTOSAR
1.2.2 Comparison between AUTOSAR Classic Platform (CP) and AUTOSAR Adaptive Platform (AP) (1)
1.2.3 Comparison between AUTOSAR Classic Platform (CP) and AUTOSAR Adaptive Platform (AP) (2)
1.2.4 Evolution of AUTOSAR Classic (CP)/AUTOSAR Adaptive (AP)
1.2.5 Execution Mode of AUTOSAR Classic (CP)/AUTOSAR Adaptive (AP)
1.3 AUTOSAR Adaptive
1.3.1 Architecture (1)
1.3.2 Architecture (2)
1.3.3 AUTOSAR Runtime for Adaptive (ARA)
1.3.4 Three Pillars
1.3.5 Methodology
1.3.6 AUTOSAR Adaptive Supports Address Space Virtualization
1.3.7 Boot Sequence
1.3.8 Development Flow
1.3.9 Tasks Undertaken by Providers in the Development Process
1.3.10 Tool Chain Business Models
1.4 AUTOSAR Partnership
1.4.1 Introduction
1.4.2 Organizational Structure
1.4.3 Working Groups
1.4.4 Groups, Boards and Task Forces
1.4.5 Members
1.4.6 Premium Partners of AUTOSAR China
1.4.7 Based on AUTOSAR Architecture, the Automotive Software Ecosystem Member Organization of China (AUTOSEMO) Was Established
1.5 AUTOSAR Standards Construction
1.5.1 AUTOSAR Standards
1.5.2 Standard Roadmap of AUTOSEMO
1.5.3 Key Achievements of AUTOSEMO
1.5.4 Standard Work of AUTOSEMO
1.5.5 Ecosystem Building Plan of AUTOSEMO
1.6 AUTOSAR Market Pattern
1.6.1 Major AUTOSAR Tool Providers
1.6.2 Status Quo and Pattern of AUTOSAR Inside and Outside China (Software Platform, Basic Software)
1.6.3 Product Layout of Chinese Providers in AUTOSAR (1)
1.6.4 Product Layout of Chinese Providers in AUTOSAR (2)
1.6.5 Progress of Chinese Providers in AUTOSAR Business
1.6.6 Software Providers Gain More Competitive Edges through Investments and Mergers & Acquisitions
1.6.7 Software Providers and Automakers Reshape Cooperation Models


2 AUTOSAR Adaptive Architecture and Development Roadmap
2.1 Impact of E/E Architecture Evolution on AUTOSAR
2.1.1 Application of AUTOSAR in E/E Architecture (1)
2.1.2 Application of AUTOSAR in E/E Architecture (2)
2.1.3 Application of AUTOSAR in E/E Architecture (3)
2.1.4 AUTOSAR Adaptive is an Indispensable Key Element to Centralized Architecture (1)
2.1.5 AUTOSAR Adaptive is an Indispensable Key Element to Centralized Architecture (2)
2.1.6 Central Computing Unit Based on AUTOSAR Adaptive (1)
2.1.7 Central Computing Unit Based on AUTOSAR Adaptive (2)
2.1.8 Upgrade of Automotive Software Architecture to AUTOSAR Adaptive
2.1.9 Upgrade of Domain Controller Software Architecture to AUTOSAR Adaptive (1)
2.1.10 Upgrade of Domain Controller Software Architecture to AUTOSAR Adaptive (2)
2.1.11 Trends of AUTOSAR Application in OEM E/E Architecture
2.2 AUTOSAR Adaptive is Service Oriented Architecture
2.2.1 The Development of SOA Promotes the Application of AUTOSAR Adaptive
2.2.2 AUTOSAR Adaptive Follows the Concept of "Service Oriented Architecture (SOA)" (1)
2.2.3 AUTOSAR Adaptive Follows the Concept of "Service Oriented Architecture (SOA)" (2)
2.2.4 AUTOSAR Adaptive Uses Service-oriented Inter-process Communication (1)
2.2.5 AUTOSAR Adaptive Uses Service-oriented Inter-process Communication (2)
2.3 Development Roadmap of AUTOSAR Adaptive
2.3.1 Challenges for Suppliers to Develop AUTOSAR Adaptive
2.3.2 Features to Be Added in AUTOSAR Adaptive in the Future
2.3.3 Technology Evolution Roadmap of AUTOSAR Adaptive
2.3.4 Development Plan for AUTOSAR Adaptive
2.4 AUTOSAR Promotes the Application of Automotive Ethernet
2.4.1 AUTOSAR Favors Wider Adoption of Ethernet in Vehicle Architecture
2.4.2 AUTOSAR Classic ECU Communication (1)
2.4.3 AUTOSAR Classic ECU Communication (2)
2.4.4 AUTOSAR Adaptive and Ethernet Communication (SOME/IP) Protocols


3 Application Cases of AUTOSAR Adaptive
3.1 Overview
3.1.1 AUTOSAR-based Layered Structure for ICV
3.1.2 AUTOSAR Adaptive Application
3.1.3 AUTOSAR Adaptive Application Scenarios
3.1.4 Progress of OEMs in Mass Production of AUTOSAR-based Software Platforms
3.1.5 Progress of Software Providers in Mass Production of AUTOSAR-based Software Platforms
3.1.6 Volkswagen’s AUTOSAR Adaptive-based Universal Software Architecture (1)
3.1.7 Volkswagen’s AUTOSAR Adaptive-based Universal Software Architecture (2)
3.1.8 Toyota Zonal Architecture Uses AUTOSAR-based SOA
3.1.9 Application of AUTOSAR in Visteon E/E Architecture
3.2 Application of AUTOSAR in OTA
3.2.1 OTA Update Flow
3.2.2 Standardized Functions Via OTA Updates
3.2.3 Advantages of AUTOSAR Adaptive Platform OTA
3.2.4 UCM Specially Designed by AUTOSAR Adaptive for OTA (1)
3.2.5 UCM Specially Designed by AUTOSAR Adaptive for OTA (2)
3.2.6 UCM Specially Designed by AUTOSAR Adaptive for OTA (3)
3.2.7 UCM Specially Designed by AUTOSAR Adaptive for OTA (4)
3.2.8 OTA Protection Mechanism in AUTOSAR Adaptive
3.2.9 "Vehicle Computer Network OTA Demonstration System" Developed by AUTOSAR User Group China
3.2.10 Neusoft Reach’s NeuSAR aCore for OTA
3.3 Application of AUTOSAR in ADAS
3.3.1 Impact of AUTOSAR on Autonomous Driving Characteristics
3.3.2 AUTOSAR Adaptive Promotes the Development of ADAS
3.3.3 AUTOSAR-based ADAS ECU Solutions
3.3.4 Foreign Companies Use AUTOSAR to Deploy ADAS/AD Domain Controllers
3.3.5 Chinese Companies Use AUTOSAR to Deploy ADAS/AD Domain Controllers
3.3.6 OEM’s Mass Production of Models with ADAS/AD Domain Controllers Based on AUTOSAR Platform
3.3.7 Aptiv’s AUTOSAR Standard-compliant ADAS Platform
3.3.8 Desay SV’s Autonomous Driving Domain Controller IPU03 Is Based on AUTOSAR with Safety Components
3.3.9 Neusoft Reach’s AUTOSAR-based Autonomous Driving Domain Controllers
3.4 Application of AUTOSAR in Cockpit
3.4.1 Requirements of Intelligent Cockpit for AUTOSAR in E/E Architecture Evolution
3.4.2 Requirements of Intelligent Cockpit Functions for AUTOSAR Adaptive
3.4.3 Application of AUTOSAR in Cockpit Domain Controllers of Chinese Suppliers (1)
3.4.4 Application of AUTOSAR in Cockpit Domain Controllers of Chinese Suppliers (2)
3.4.5 Bosch’s Cockpit Fusion and Domain Control Products Use AUTOSAR
3.4.6 Volkswagen’s Cockpit Domain Controller Uses AUTOSAR
3.4.7 Nobe Technology’s Cockpit Domain Controller Uses AUTOSAR
3.4.8 Wingtech Technology’s Intelligent Cockpit Domain Controller Integrates AUTOSAR
3.5 Application of AUTOSAR in Vehicle Control
3.5.1 Requirements of Autonomous Driving Vehicle Control Functions for AUTOSAR
3.5.2 AUTOSAR Solution for AERI New Energy Vehicle Control Unit (VCU)
3.5.3 Vehicle General Domain Controller Developed by Neusoft Reach Based on AUTOSAR
3.5.4 AUTOSAR in ENOVATE E/E Architecture
3.5.5 AUTOSAR in Volkswagen Body Control Domain
3.6 Application of AUTOSAR in SOA
3.6.1 SOA Basic Software Architecture
3.6.2 Features of SOA Software Architecture
3.6.3 SOA Architecture Design for Central Computing EEA Adopts AUTOSAR Framework Software
3.6.4 Challenges and Strategies of SOA Development and Application Models
3.6.5 Deployment of AUTOSAR-based SOA Automotive Software on Domain Controllers
3.6.6 Summary of Progresses of OEMs and Tier1s in SOA Software Platforms (1)
3.6.7 Summary of Progresses of OEMs and Tier1s in SOA Software Platforms (2)

4 Foreign AUTOSAR Software Companies
4.1 Wind River
4.1.1 Profile
4.1.2 AUTOSAR Adaptive Software Platform
4.1.3 AUTOSAR Adaptive Software Platform Structure
4.1.4 AUTOSAR Business Trends
4.2 Elektrobit
4.2.1 Profile
4.2.2 AUTOSAR Adaptive–based Solutions
4.2.3 HPC Software Architecture
4.2.4 AUTOSAR Adaptive Product Lines
4.2.5 EB tresos
4.2.6 EB tresos Studio
4.2.7 EB xelor Software Platform for Next Generation Vehicle Electronic Architectures
4.2.8 Application: Hardware Platform Based on EB tresos
4.2.9 Application: Major Customers and Partners
4.3 Vector
4.3.1 Profile
4.3.2 AUTOSAR Solution?MICROSAR
4.3.3 Features of AUTOSAR Solution
4.3.4 Adaptive MICROSAR Architecture
4.3.5 Advantages of Adaptive MICROSAR
4.3.6 AUTOSAR Classic Functional Safety Solution
4.3.7 AUTOSAR Adaptive Functional Safety Solution
4.3.8 Tool Chain for ECU Development
4.3.9 Adaptive MICROSAR Product Lines
4.4 ETAS
4.4.1 Profile
4.4.2 AUTOSAR Solutions (1)
4.4.3 AUTOSAR Solutions (2)
4.4.4 AUTOSAR Solutions (3)
4.4.5 AUTOSAR Tool Chain
4.5 KPIT
4.5.1 Profile
4.5.2 AUTOSAR Software Tool Products (1)
4.5.3 AUTOSAR Software Tool Products (2)
4.5.4 AUTOSAR Software Tool Product: K-SAR Editor
4.6 Tata Elxsi
4.6.1 Profile
4.6.2 AUTOSAR Products: AUTOSAR Classic
4.6.3 AUTOSAR Products: AUTOSAR Adaptive
4.6.4 AUTOSAR Compliant Configuration Tool: eZyconfig
4.6.5 AUTOSAR Services
4.6.6 Tata Elxsi and Green Hills Introduced the Latest AUTOSAR Compliant Platforms
4.6.7 Cases: AUTOSAR Adaptive and Classic Co-existence
4.6.8 Cases: AUTOSAR-based Cockpit Architecture
4.6.9 AUTOSAR Development
4.7 Autron
4.7.1 AUTOSAR Products (1)
4.7.2 AUTOSAR Products (2)
4.7.3 Related Dynamics
4.8 Mentor Graphics
4.8.1 Profile
4.8.2 AUTOSAR Products: Capital VSTAR
4.8.3 AUTOSAR Products: Capital VSTAR Embedded Software
4.8.4 AUTOSAR Products: Capital VSTAR MCAL
4.8.5 AUTOSAR Products: Capital VSTAR Tools
4.8.6 AUTOSAR Products: Capital VSTAR Virtualizer
4.8.7 Siemens Capital E/E System
4.8.8 Major Events
4.9 Apex.AI
4.9.1 Profile
4.9.2 Main Product: Apex.Middleware


5 Chinese AUTOSAR Companies
5.1 Neusoft Reach
5.1.1 Profile
5.1.2 Basic Automotive Software Platform: NeuSAR
5.1.3 Neusoft Reach Participated in Promoting the Construction of Automotive Software Ecosystem Member Organization of China (AUTOSEMO)
5.1.4 NeuSAR aCore Architecture
5.1.5 NeuSAR cCore Architecture
5.1.6 AUTOSAR Software Tool Products
5.1.7 SOA-oriented Software Framework
5.1.8 AUTOSAR-based Standardized Domain Controllers
5.2 Huawei
5.2.1 Tasks Undertaken in AUTOSAR
5.2.2 Self-developed AUTOSAR
5.2.3 Self-developed AUTOSAR CP and AP Architectures
5.2.4 Self-developed Operating Systems
5.2.5 AOS Architecture
5.2.6 VOS Architecture
5.2.7 Vehicle Basic Software and SOA Service Framework
5.2.8 MDC Autonomous Driving Computing Platform Uses AUTOSAR
5.2.9 Huawei MDC and Huanyu Zhixing Jointly Released Minibus Solution
5.3 iSoft Infrastructure Software
5.3.1 Profile
5.3.2 AUTOSAR Basic Software Platform Products and Technical Services (1)
5.3.3 AUTOSAR Basic Software Platform Products and Technical Services (2)
5.3.4 AUTOSAR Basic Software Platform Products and Technical Services (3)
5.3.5 AUTOSAR Basic Software Platform Products and Technical Services (4)
5.3.6 AUTOSAR Basic Software Platform Products and Technical Services (5)
5.3.7 Major Customers and Cooperation Dynamics
5.4 Jingwei HiRain
5.4.1 Profile
5.4.2 AUTOSAR Solutions
5.4.3 AUTOSAR Solutions: Embedded Standard Software
5.4.4 AUTOSAR Solutions: AUTOSAR Tool Chain
5.4.5 AUTOSAR Solutions: INTEWORK-EAS-CP
5.4.6 AUTOSAR Solutions: INTEWORK-EAS-AP
5.4.7 AP Pre-research Application Practices
5.4.8 AP Development Plan
5.4.9 AP Application Cases
5.5 HingeTech
5.5.1 Profile
5.5.2 AUTOSAR Solution: AUTOSAR Adaptive Solution
5.5.3 AUTOSAR Application Practice: Smart Antenna
5.6 Hangzhou SMR Technology
5.6.1 Profile
5.6.2 AUTOSAR Solutions
5.6.3 SmartSAR Studio Products
5.7 NOVAUTO
5.7.1 Profile
5.7.2 AUTOSAR Software Solutions
5.7.3 Partners
5.8 UAES
5.8.1 SOA Software Development
5.8.2 AUTOSAR-based Open Software Platform (1)
5.8.3 AUTOSAR-based Open Software Platform (2)
5.9 Others
5.9.1 China Intelligent and Connected Vehicles (Beijing) Research Institute Co., Ltd. (CICV) Led the Funding Round of Automotive Intelligence and Control of China Co., Ltd. (AICC)
5.9.2 DJI’s Self-developed Autonomous Driving Domain Controller Middleware is Compatible with AUTOSAR
5.9.3 Rockchip