Automotive Software Providers and Business Models Research Report, 2022

Automotive Software Providers and Business Models Research Report, 2022

Research on software business models: four business forms and charging models of automotive software providers.

In an age of software-defined vehicles, automotive software booms, and providers step up their efforts to deploy various layers of software for a place in the software market. From the current layout of automotive software products and solutions, it can be seen that intelligent vehicle software business models include IP, solutions and technical services, and charging models are led by non-recurring engineering (NRE), software authorization/license, and royalty.

Through the lens of the product and solution layout of automotive software providers, currently their typical business forms are custom software development and design, technical services, software license/authorization, and system integration, varying slightly in charging models.

As software and hardware tend to be decoupled and layered, software becomes an independent core component product, and the automotive software industry chain is reshaped. The boundaries between Tier 1 and Tier 2 suppliers thus become ever more blurred, and even OEMs will develop their own hardware and software. Automotive software providers are transforming from Tier 2 into Tier 1 or even Tier 0.5 suppliers, with an increasingly high position in the industry chain.

The supply relationships between suppliers and automakers are changing as well. The conventional automotive supply chain has been broken, and the original chain-type ""supply"" model turns into a flat ""cooperation"" model. Players that have the ability to develop and integrate software and hardware are expected to become super suppliers, driving innovations and technology upgrades in the automotive industry.

Basic software layer: in the trend for modularization, standardization and platformization, suppliers and OEMs build closer relationships and more flexible cooperation models.

In service-oriented architecture (SOA), automotive basic software is an embedded software platform used to enable decoupling of software and hardware for automotive systems, and providing software and hardware support for automotive system services. It is the key to realization of vehicle intelligence.

In addition to chip and hardware, basic software is the most basic underlying capability in the entire industry chain. Major suppliers double down on development and innovation of automotive basic software products such as operating system and middleware. As well as large foreign providers such as Vector, ETAS and EB, quite a few local software providers in China like Neusoft Reach, ThunderSoft, Jingwei Hirain, and iSoft Infrastructure Software under China Electronics Technology Group Corporation are also working to deploy automotive basic software products, especially middleware products, most of which are AUTOSAR standard-compliant products, and hybrid platform software solutions based on CP and AP architectures.

To meet the market demand in the trend for SDVs, iSoft Infrastructure Software provides AUTOSAR CP+AP integrated solution for the two scenarios, security domain and high-performance computing domain, and combines it with iSoft Cloud System to enable landing of intelligent connectivity. This solution is applicable to intelligent cockpit domain, vehicle control system domain and ADAS/AD domain. By standardizing the interfaces and architectures of different operating systems, underlying hardware, protocol software, etc., it enables service-oriented architecture. Meanwhile, for intelligent cockpit and ADAS/AD domains, iSoft Infrastructure Software is developing corresponding operating system kernels for a comprehensive layout of automotive basic software platform.

As concerns business model, iSoft Infrastructure Software positions itself as a Tier 2 supplier that adopts a model similar to VECTOR and concentrates on developing and applying basic software and tool chains. The ""neutral"" position allows the company to focus more on the R&D and application of vehicle basic software technology.

In 2018, Neusoft Reach introduced NeuSAR, China’s first self-developed automotive basic software platform product which complies with the latest AUTOSAR release. NeuSAR not only supports conventional ECU development but provides a wealth of basic software, middleware and development tools for software development based on domain control systems in new-generation E/E architectures. It is widely used in domain control systems such as autonomous driving, intelligent driving, chassis power, and body control in new-generation architectures, providing underlying software support for more personalized and intelligent application of the next-generation intelligent vehicles.

NeuSAR is composed of NeuSAR cCore, NeuSAR aCore, NeuSAR middleware, NeuSAR DS and NeuSAR tool chain. NeuSAR cCore subject to the latest AutoSAR Classic standard finds broad application in mass-produced ECUs of OEMs and many Tier 1 suppliers; NeuSAR aCore, the world's first commercialized AutoSAR Adaptive product, has been spawned and used in multiple autonomous driving domain controllers. The high compliance with the existing standards and the stability built through wide application make NeuSAR the preferred local AutoSAR product in the industry.

In 2020, under the guidance of Ministry of Industry and Information Technology, Neusoft Reach led the establishment of China Automotive Basic Software Ecosystem Committee (AUTOSEMO), aiming to help to create an independent controllable automotive basic software ecosystem.

In the trend for ""software-defined vehicles"", automotive software industry will usher in layering and modularization, and a number of professional middleware module suppliers will be born. It is hard for automakers to complete R&D of full-chain software modules. OEMs will purchase software and hardware separately, and select hardware (chips) according to vehicle model position and price planning. They will also partner with basic software companies, mainly operating system and middleware providers, to build software architecture and adapt to chips.

Application software layer: to answer differentiated and individualized needs, conventional suppliers transform the development model from turnkey solution into bilateral in-depth cooperation.

Based on SOA (service-oriented architecture), the business model of SaaS (Software as a Service) is introduced. On the one hand, it provides users with an immersive entertainment space to meet their needs for emotional, personalized scenes and multimodal interaction. On the other hand, it offers self-development space to OEMs, creating infinite possibilities.

First of all, before mass production, automotive software revenue largely comes from non-recurring engineering project development fee and software license fee. Non-recurring engineering project development fee is that charged during development process from the special software design and custom development according to requirements of Tier 1 suppliers or OEMs to the final delivery of development results to customers. Software license fee is charged for the use of software products (systems or development tools) developed by software companies.

After mass production, the software charging model will turn into ""royalty fees"", ""technical service fees"" and FOTA-based software upgrade fees. Wherein, the royalty fees are the single vehicle copyright fees charged according to the number of functional module IPs used by customers, and the shipments.

For automotive software companies, they can also charge fees sustainably just like infrastructure services such as water and electricity. One example is the SaaS model.

In the case of acoustic software OEM market, conventional automakers often choose products and toning services of acoustic components suppliers or electro-acoustic brands, while intelligent vehicle manufacturers tend to purchase products and services from acoustic components suppliers for the purpose of cost control, rapid iteration and standardized modular production, that is, a model that leaves automakers using their own or third-party toning modes for overall audio debugging

For example, in February 2022, Harman announced Software-Enabled Branded Audio, an on-demand software platform that offers consumers a user-friendly, affordable way to upgrade existing unbranded car audio experience with no additional hardware required.

Vehicle-cloud platform layer: under the new-generation infrastructures, enable the innovative model of vehicle-cloud co-construction and coordination.

As underlying infrastructures get improved, new-generation vehicle E/E architectures evolve, SOA-based design concept becomes widespread, cloud infrastructures are far more perfect, and cloud computing power becomes stronger, cloud computing has become a crucial productivity in the automotive industry. The vehicle-cloud integrated data drive will play a key role in the competition in the automotive industry.

Vehicle cloud is a digital ecosystem platform for automakers to empower vehicle mobility and related intelligent services. Its service forms are divided into three types: IaaS, PaaS and SaaS. The IaaS layer is responsible for providing infrastructures related to computing, storage, network, CDN, security, disaster recovery and so forth in design, production and supply chain links; vehicle cloud services in the PaaS layer cover cloud platform architecture needed by after-sale links (such as call center, OTA, autonomous driving and telematics) and production design links (including analog, simulation, etc.); the SaaS layer involves sales and consumption of various function applications paid according to service time or amount of infrastructure.

At present, vehicle cloud service providers mainly include: public cloud providers that offer IaaS and Paas layers, such as Baidu Cloud, Tencent Cloud and Alibaba Cloud; those that cooperates with cloud platform service providers and provides SaaS services, including telematics service providers like PATEO and FutureMove Automotive. The former ones charge according to goods and services provided; the latter charge for services.

Cloud will be an effective supplement to vehicle, so specialized cloud solutions and digital platform tools will be gradually introduced. The complete layout of vehicle and cloud products will empower ""vehicle-cloud integration"" in the automotive industry. Whether from cost reduction and efficiency improvement or safety and reliability, OEMs will fail to meet the needs just by independent construction. They will be bound to forge closer partnerships with cloud service providers to open up new scene maps together and thus realize co-construction and enabling, a two-way process in which OEMs and cloud service providers walk and grow in the same pace in achieving development goals.

Neusoft Reach’s vehicle-cloud integrated platform is a self-developed intelligent software product for next-generation new E/E architectures. It is mainly composed of a vehicle-cloud integrated tool platform, a vehicle-cloud integrated core computing platform, and a vehicle-cloud integrated software ecosystem service platform, fully covering SOA-based design and development environment and runtime environment. The connection of in-vehicle capabilities and the reintegration of cloud big data and ecosystem service capabilities will quickly enable massive intelligent scene applications with a high degree of vehicle-cloud cooperation.

Neusoft Reach’s vehicle-cloud integrated product builds vehicle-cloud integrated intelligent vehicle digital bases based on the SOA design idea, and provides OEMs with full-stack SDV products and services, thereby improving brand value in the aspects of ""uniqueness"", ""added value"", and ""evolvability"".

Please Note: PDF E-mail from Publisher purchase option allows up to 10 users and does not allow printing or editing. This functionality will require a Global Site License.


1 Analysis of Automotive Software Business Model
1.1 Overview of Intelligent Vehicle Software Industry Chain
1.1.1 Intelligent Vehicle Software Architecture
1.1.2 Automotive Software Architecture Step Towards Service-Oriented (SOA) From Signal-Oriented
1.1.3 Transformation of Automobile Software Development Mode of OEMs
1.1.4 Types of Intelligent Vehicle Software
1.1.5 Automotive Software Supplier Categories
1.1.6 Software Empowers Automakers to Realize Value
1.2 Summary of Business Models of Intelligent Vehicle Software Related Suppliers
1.2.1 Main Business Types of Software Suppliers
1.2.2 Main Charging Models of Software Suppliers
1.2.3 Single Vehicle Software License Fee of Some Software Modules for Intelligent Vehicles
1.2.4 Automotive Software Sales Model
1.2.5 Summary of Business Models of Major Automotive Software Suppliers by Product (1)
1.2.6 Summary of Business Models of Major Automotive Software Suppliers by Product (2)
1.2.7 Summary of Business Models of Major Automotive Software Suppliers by Product (3)
1.2.8 Summary of Business Models of Major Automotive Software Suppliers by Product (4)
1.2.9 Summary of Business Models of Major Automotive Software Suppliers by Product (5)
1.2.10 Business Models of Major Automotive Software Products
1.2.11 Business Models of Major Automotive Software Suppliers
1.2.12 Evolution Trend of Role of Software Suppliers under SVD Trend
1.3 Development Trend of Smart Vehicle Software Business Model
1.3.1 Change of Role of Software Suppliers under SVD Trend
1.3.2 Automotive Software Market Size
1.3.3 Ecological Trend of Flattening and Joint Development of Automotive Supply
1.3.4 Software Suppliers Ecological Cooperation, Deep Binding with Upstream Partners
1.3.5 Exploration of Software Suppliers Cooperation Model
1.3.6 Charging Strategy of Software Suppliers
1.3.7 Exploration of Charging Model of Software Suppliers (1)
1.3.8 Exploration of Charging Model of Software Suppliers (2)
1.3.9 Exploration of Future Development Trends and Business Models of Automotive Software Product (1)
1.3.10 Exploration of Future Development Trends and Business Models of Automotive Software Product (2)
2 Analysis of Automotive Basic Software Layer Suppliers and Business Models
2.1 Development Status and Trend of Basic Software Business Model
2.1.1 Composition of Automotive Basic Software
2.1.2 Business Model of Each Module of Automotive Basic Software
2.1.3 Automotive Basic Software Module BSP Business Model
2.1.4 Evolution of Role of Automotive Basic Software Suppliers
2.1.5 Development Trend of Automotive Basic Software
2.1.6 Development Trend and Business Model Exploration of Automotive Basic Software Technology
2.2 Intelligent Vehicle Operating System
2.2.1 Types
2.2.2 Business Model Types
2.2.3 Business Models of Major Automotive Operating System Enterprises
2.2.4 Smart Cockpit OS Business Model
2.2.5 Autonomous Driving OS Supplier Business Model
2.2.6 Automotive Operating System Development Trend and Business Model Exploration
2.2.7 Basic Automotive Operating System and Business Model
2.2.8 Automotive RTOS Operating System and Business Model (1)
2.2.9 Automotive RTOS Operating System and Business Model (2)
2.2.10 Automotive Operating System and Business Model (1)
2.2.11 Automotive Operating Systems and Business Model (2)
2.2.12 Automotive Operating Systems and Business Model (3)
2.2.13 Automotive Operating Systems and Business Model (4)
2.3 Hypervisor Virtual Machine Management System
2.3.1 Automotive Virtual Machine Management System Business Model
2.3.2 Hypervisor and Business Model (1)
2.3.3 Hypervisors and Business Model (2)
2.3.4 Hypervisors and Business Model (3)
2.3.5 Hypervisors and Business Model (4)
2.4 Middleware
2.4.1 Types
2.4.2 Middleware Supplier Business Model
2.4.3 Middleware Supplier Business Model
2.4.4 ROS Middleware Products and Business Models
2.4.5 DDS Middleware Products and Business Model (1)
2.4.6 DDS Middleware Products and Business Model (2)
2.4.7 DDS Middleware Products and Business Model (3)
2.4.8 MCAL Middleware Products and Business Model (1)
2.4.9 MCAL Middleware Products and Business Model (2)
2.4.10 Autonomous Driving Middleware Products and Business Model (1)
2.4.11 Autonomous Driving Middleware Products and Business Model (2)
2.4.12 Autonomous Driving Middleware Products and Business Model (3)
2.4.13 Autonomous Driving Middleware Products and Business Model (4)
2.4.14 Autonomous Driving Middleware Products and Business Model (5)
2.4.15 Other Middleware Products and Business Model (1)
2.4.16 Other Middleware Products and Business Model (2)
2.4.17 Business Model of TTTech Autonomous Driving Middleware Solutions
2.5 AutoSAR
2.5.1 AutoSAR Industry Chain
2.5.2 AutoSAR Related Software Tool Supplier Business Model (1)
2.5.3 AutoSAR Related Software Tool Supplier Business Model (2)
2.5.4 AutoSAR Related Software Tool Supplier Business Model (3)
2.5.5 AutoSAR Related Software Tool Supplier Business Model (4)
2.5.6 AutoSAR Related Software Tool Supplier Business Model (5)
2.5.7 AutoSAR Related Software Tool Supplier Business Model (6)
2.5.8 AutoSAR Related Software Tool Supplier Business Model (7)
2.5.9 Vector AutoSAR Solution Business Model
2.5.10 EB AutoSAR Solution Business Model
2.5.11 Business Model of i-Soft AutoSAR Solution
2.5.12 Business Model of Jingwei HiRain AutoSAR Solution
3 Automotive Application Software Layer Suppliers and Business Models
3.1 Status Quo and Trend
3.1.1 Automotive Application Software Layer Industry Chain
3.1.2 Main Application Software Module Business Model
3.1.3 Trends of Main Application Software Module Business Model
3.2 Smart Cockpit Software System
3.2.1 Business Model of Smart Cockpit Software Platform Suppliers (1)
3.2.2 Business Model of Smart Cockpit Software Platform Suppliers (2)
3.2.3 Business Model of Smart Cockpit Software Platform Suppliers (3)
3.3 HMI software
3.3.1 HMI Software Business Model
3.3.2 Business Model of HMI Design Software Suppliers (1)
3.3.3 Business Model of HMI Design Software Suppliers (2)
3.3.4 Business Model of HMI Design Software Suppliers (3)
3.3.5 Business Model of HMI Design Software Suppliers (4)
3.4 Voice Interaction
3.4.1 Voice Software Suppliers Business Model (1)
3.4.2 Voice Software Suppliers Business Model (2)
3.4.3 Voice Software Suppliers Business Model (3)
3.4.4 Voice Software Suppliers Business Model (4)
3.4.5 Business Model of iFLYTEK Software Products
3.4.6 Business Model of Baidu Software Products
3.4.7 Business Model of AISpeech Software Products
3.4.8 Business Model of Cerence Software Products
3.5 HUD Software
3.5.1 HUD Software Suppliers Business Model (1)
3.5.2 HUD Software Suppliers Business Model (2)
3.5.3 HUD Software Suppliers Business Model (3)
3.5.4 Business Model of Some Products of Raythink
3.6 Autonomous Driving Software System
3.6.1 Autonomous Driving Supply Chain Model
3.6.2 Commercial Landing Scenarios of Autonomous Driving and Business Models
3.6.3 Exploration of Business Model of autonomous Robotaxi
3.6.4 Business Model of Autonomous Driving System Suppliers (1)
3.6.5 Business Model of Autonomous Driving System Suppliers (2)
3.6.6 Business Model of Autonomous Driving System Suppliers (3)
3.6.7 Business Model of Autonomous Driving System Suppliers (4)
3.6.8 ADAS System Aftermarket Supplier Business Model
3.7 HD Map
3.7.1 Industry Chain
3.7.2 Business Models
3.7.3 Cooperation Mode between HD Map Suppliers and OEMs
3.7.4 Monetization
3.7.5 HD Map Suppliers Business Model (1)
3.7.6 HD Map Suppliers Business Model (2)
3.7.7 HD Map Suppliers Business Model (3)
3.7.8 HD Map Suppliers Business Model (4)
3.7.9 HD Map Suppliers Business Model (5)
3.7.10 Business Model of Momenta Software Products
3.7.11 Business Model of Here Software Products
3.8 Parking Software
3.8.1 Parking Software Suppliers Business Model (1)
3.8.2 Parking Software Suppliers Business Model (2)
3.8.3 Parking Software Suppliers Business Model (3)
3.8.4 Business Model of Some Software Products of Zongmu Technology (1)
3.8.5 Business Model of Some Software Products of Zongmu Technology (2)
3.9 DMS Software
3.9.1 DMS Industry Chain
3.9.2 DMS Vision Perception Algorithm Suppliers and Business Models (1)
3.9.3 DMS Vision Perception Algorithm Suppliers and Business Models (2)
3.9.4 DMS Vision Perception Algorithm Suppliers and Business Models (3)
3.9.5 Business Model of Some Software Products of ArcSoft Technology
3.9.6 Business Model of Some Software Products of Seeing machines (1)
3.9.7 Business Model of Some Software Products ofSeeing machines (2)
3.10 Acoustic Software
3.10.1 Summary of Acoustic Software Vendors Business Model
3.10.2 Status Quo of Acoustic Software Business Models
3.10.3 Evolution of Acoustic Software Procurement Model of Automakers
3.10.4 Exploration of Acoustic Software Business Model
3.10.5 Acoustic Software Vendors Business Model (1)
3.10.6 Acoustic Software Vendors Business Model (2)
3.10.7 Acoustic Software Vendors Business Model (3)
3.10.8 Business Model of HARMAN Software Products
3.10.9 Business Model of DSP Concepts Software Products
3.11 Simulation Software
3.11.1 Simulation Tool Supplier Business Model (1)
3.11.2 Simulation Tool Supplier Business Model (2)
3.11.3 Simulation Tool Vendor Business Model (3)
3.11.4 Simulation Tool Vendor Business Model (4)
3.11.5 Simulation Tool Vendor Business Model (5)
3.11.6 Simulation Tool Vendor Business Model (6)
3.11.7 Simulation Tool Vendor Business Model (7)
3.11.8 Simulation Tool Vendor Business Model (8)
3.11.9 Simulation Tool Vendor Business Model (9)
3.11.10 Simulation Tool Vendor Business Model (10)
3.11.11 Simulation Tool Vendor Business Model (11)
3.11.12 Simulation Tool Vendor Business Model (12)
3.11.13 ANSYS Simulation Product Business Model
3.11.14 51WORLD Simulation Product Business Model
4 Automotive Cloud Platform Layer Supplier and Business Model Analysis
4.1 Status Quo and Trends of Business Models of Cloud Platform Layer-related Software
4.1.1 Business Models of Corresponding Module of Cloud Platform Layer
4.1.2 Vehicle to Everything Business Model
4.1.3 Exploration of V2X Payment Model
4.1.4 Cloud Platform Service Provider and OEM Cooperation Model
4.1.5 Cloud Platform Service Form and Charging Model
4.1.6 Service Forms of Major Cloud Platform Providers
4.1.7 Development Trend of Automotive Cloud as a Service
4.1.8 Future Vehicle Cloud as a Service Business Model Exploration
4.2 Cloud as a Service Platform
4.2.1 Cloud Platform Providers and Business Models (1)
4.2.2 Cloud Platform Providers and Business Models (2)
4.2.3 Cloud Platform Providers and Business Models (3)
4.2.4 Cloud Platform Providers and Business Models (4)
4.2.5 OEM Cloud Platform Layout and Business Model (1)
4.2.6 OEM Cloud Platform Layout and Business Model (2)
4.2.7 Huawei Cloud as a Service Software Product Business Model
4.2.8 Business Model of Some PATEO Software Products
4.3 OTA
4.3.1 OTA Industry Chain
4.3.2 OTA Business Model
4.3.3 OTA Operating Business Model
4.3.4 OTA-related Suppliers Business Model (1)
4.3.5 OTA-related Suppliers Business Model (2)
4.3.6 OTA-related Suppliers Business Model (3)
4.3.7 Business Model of CAROTA Software Products
4.3.8 Business Model of ABUP Software Products
4.4 Vehicles to Everything Safety Solutions
4.4.1 Information Security Software Business Model
4.4.2 Encryption Algorithm Business Model (1)
4.4.3 Encryption Algorithm Business Mode (2)
4.4.4 Cyber Security Testing Technology Business Model (1)
4.4.5 Business Model of Vecentek Software Products
5 Research on Business Model of Typical Automotive Software Suppliers
5.1 Neusoft Intelligent Vehicle Connection
5.1.1 Profile
5.1.2 Software Development Capabilities based on SOA Architecture
5.1.3 Business Model of C (5) HMI Platform
5.1.4 Business Model of Intelligent Cockpit Domain Control Platform
5.1.5 Business Model of AR-HUD
5.1.6 Business Model of Global Navigation OneCoreGo 3.0
5.1.7 Business Model of Vehicle to Everything Information Security Solution
5.1.8 CVIS Platform Business
5.1.9 CVIS Test Products
5.1.10 Business Model of CVIS Platform
5.1.11 Neusoft Reach
5.1.12 NeuSAR, Next-generation ICV Basic Software Platform
5.1.13 Neusoft Reach Autonomous Driving Solution
5.1.14 Neusoft Reach Vehicle-Cloud Integrated Product
5.2 i-Soft
5.2.1 Profile
5.2.2 CP AUTOSAR and Tool Chain Products
5.2.3 AP AUTOSAR and Tool Chain Products
5.2.4 AUTOSAR CP + AP Integrated Solution
5.2.5 Cloud System Solution
5.2.6 Vehicle Basic Software Ecosystem
5.2.7 Business Model
5.2.8 Partners
5.3 ThunderSoft
5.3.1 Profile
5.3.2 Intelligent Cockpit Products and Business Models
5.3.3 Software Products
5.3.4 Software Products Business Model (1)
5.3.5 Software Products Business Model (2)
5.3.6 Intelligent Driving Business
5.3.7 Business Model
5.3.8 Revenue by Business Model
5.3.9 Supplier Cooperation Model
5.4 Jingwei HiRain
5.4.1 Profile
5.4.2 Automotive Electronic Products Business
5.4.3 R & D Services and Solution Services
5.4.4 Advanced Driving Solutions
5.4.5 Business Model
5.4.6 Partners
5.5 Kotei
5.5.1 Profile
5.5.2 Intelligent Cockpit Solutions and Business Models
5.5.3 Intelligent Connection Test Solution and Business Model (1)
5.5.4 Intelligent Connection Test Solution and Business Model (2)
5.5.5 Business Model
5.5.6 Revenue by Business Model
5.5.7 Sales Model and Major Customers
5.5.8 Deeply Cooperation with Customers
5.5.9 Cooperation with Suppliers
5.5.10 Change from Tier2 to Tier0.5
5.5.11 Builds Software Factory
5.6 E-Planet
5.6.1 Products and Services
5.6.2 EEA Related Products and Business Models
5.6.3 HMI Related Products and Business Models
5.6.4 Tests Related Products and Business Models
5.6.5 Ethernet Protocol Stack Related Products and Business Models
5.6.6 Partners and Major Customers
5.7 Megatronix Technology
5.7.1 Profile
5.7.2 Product Line
5.7.3 SmartMega ® OS + Vehicle Distributed Intelligent Operating System
5.7.4 Business Model

Download our eBook: How to Succeed Using Market Research

Learn how to effectively navigate the market research process to help guide your organization on the journey to success.

Download eBook
Cookie Settings