Automotive software, SDVs, and AIDVs

Automakers, Tier1 and Tier2 suppliers, and IT/Cloud vendors

The architecture of the automotive software market is expected to largely converge into "zonal" models by 2028.
Cloud vendors, who previously had a limited presence, are expected to gradually increase their efforts in the area of software-defined vehicles (SDVs), centered around telematics control units (TCUs), central processing units (CPUs), and information-oriented operating systems, such as Android Automotive OS (AAOS).
This report examines trends in the traditional automotive software market and explores potential future scenarios through 2035. It considers how the growing presence of cloud vendors will impact the market after 2028, based on discussions with OEMs, Tier 1 and Tier 2 suppliers, and cloud vendors themselves.

I. General Overview

1. Market Changes Surrounding the Automotive Industry
   1.1. Recent Trends in the Global Automotive Market
   1.2. Recent Trends Among Domestic Original Equipment Manufacturers (OEMs)
   1.3. Functions and Services Expected of Vehicles
2. Overview of Automotive Systems to Date
   2.1. Overview of Automotive Systems
        2.1.1. Automotive Control Systems
        2.1.2. Information Systems
   2.2. Past Developments Concerning Automotive Software
3. Market Environment and Architectural Evolution in Automotive Software
   3.1. Market Environment and Architectural Hypotheses Prior to 2018
        3.1.1. Market Environment
        3.1.2. Architectural Hypotheses for Automotive Software
   3.2. Market Environment and Architectural Hypotheses for 2025
        3.2.1. Market Environment
        3.2.2. Architectural Hypotheses for Automotive Software
   3.2. Market Environment Forecast and Architectural Hypotheses Around 2028
        3.3.1. Market Environment Forecast
        3.3.2. Architectural Forecast for Automotive Software
   3.4. Market Environment Forecast and Architectural Hypotheses Around 2030
        3.4.1. Market Environment Forecast
        3.4.2. Automotive Software Architecture Forecast
   3.5. What is an AI-Defined Vehicle (AIDV), the Next Step After a Software-Defined Vehicle (SDV)?
        3.5.1. Overview of AI-Defined Vehicles (AIDVs): Blurring the Boundaries Between In-Car and Out-Car
        3.5.2. Specific Examples
4. Key Technologies Supporting Architecture Trends 
   4.1. Control System Software 
        4.1.1. AUTOSAR Classic/Adaptive 
        4.1.2. QNX 
        4.1.3. Automotive Grade Linux (AGL) 
   4.2. Vehicle OS 
        4.2.1. Fierce Global Competition in Vehicle OS Development
        4.2.2. Toyota Motor Corporation's Trial and Error in Developing Arene OS
        4.2.3. Nissan Motor Company's "Nissan Scalable Open Software Platform"
   4.3. Platforms
        4.3.1. SOAFEE
        4.3.2. AGL SoDeV Architecture
        4.3.3. Alloy Kore
        4.3.4. Snapdragon (Snapdragon Digital Chassis)
   4.4. SoC (System on a Chip)
        4.4.1. Overview of SoC
        4.4.2. Trends Toward In-House Development of Automotive SoCs
   4.5. Abstraction Technology – VirtIO
        4.5.1. Overview of VirtIO
        4.5.2. Relationship with Hypervisors
   4.6. Two APIs
        4.6.1. Traditional API
        4.6.2. Moves to Utilize Loose APIs for AI Agent Implementation
5.  Mobility Services.
   5.1. Tesla Shock
   5.2. Mobility Services
        5.2.1. Overview
        5.2.2. Primary Constraints
   5.3. Initial Launch Focuses on B2B Business
   5.4. B2C Business Initially Challenging: Expectations for Level 3 and Beyond
        5.4.1. Overview
        5.4.2. Current Environment is Unfavorable for the Application Business
        5.4.3. The Real Competition Begins After Level 3+ Autonomous Driving is Established
6. Comparison of Three Domestic OEMs
   6.1. Toyota Motor Corporation vs. Nissan Motor Co., Ltd. and Honda Motor Co., Ltd.
        6.1.1. Each Company Develops Its Own In-Vehicle Software Architecture
        6.1.2. Collaboration Between Nissan Motor and Honda Motor Significantly Changes the Three-Way Standoff
   6.2. Stance on OTA and Challenges for Implementation
        6.2.1. Positioning: Is OTA Seen as a Business Opportunity or Not?
        6.2.2. Implementing OTA is Not Simple
   6.3. Key Challenges to Overcome
        6.3.1. Challenge 1: Development Aspect: "Unique to Vehicles" and "Cross-Domain"
        6.3.2. Challenge 2: Organizational Aspect: Shifting from Silos to Cross-Functional Collaboration
        6.3.3. Challenge 3: Human Resources Aspect: Balancing In-House Development and Outsourcing
7. Market Size Transition and Forecasts for Various Automotive Software Segments (2021–2030)
   7.1. Market Size Transition and Forecasts for Automotive Software by Control System, In-Vehicle IT System, SDV, and AIDV
   7.2. Line Chart of SDV/AIDV Composition Ratio (2021–2030)
   7.3. Market Size Transition and Forecasts for SDV- and AIDV-Related Software by OEM, Tier 1, and Tier 2
   7.4. Market Size Calculation Methodology
8. Outlook for the Mobility Industry in 2035
   8.1. Changes Expected by 2030
        8.1.1. Vehicles will Consist of Both Automotive Edge Computing and Mobility Services
        8.1.2. Changes in Automotive Edge Computing
        8.1.3. Changes in Mobility Services
   8.2. Bold Predictions for Changes Starting Around 2035

II. Data Section

1. Automotive Software Market Size for OEMs
   1.1. Breakdown of Control Systems, Automotive IT Systems, SDVs, and AIDVs by OEM
   1.2. Automotive Software Market Size Transition, Forecasts, and Share by OEM
2. Automotive Software Market Size for Suppliers, etc.
   2.1. Breakdown of Control Systems, Automotive IT Systems, SDVs, and AIDVs by Supplier
   2.2. Automotive Software Market Size Transition, Forecasts, and Share by Supplier

III. Trends of the Three Major Domestic OEMs

1. Toyota Motor Corporation
2. Nissan Motor Co., Ltd.
3. Honda Motor Co., Ltd.
4. Mazda Motor Corporation

IV. Trends of Suppliers and IT Vendors

1. ASTEMO
2. Amazon Web Services
3. Elektrobit Nippon
4. Sapphire Stream
5. Snowflake
6. NEUSOFT Japan
7. Panasonic Automotive Systems
8. BlackBerry(QNX)
9. Vector Japan
10. Micware
11. Linaro (SOAFEE)