중국의 지능형 차량용 콕핏-드라이빙 통합(콕핏-드라이빙-파킹) 산업(2024-2025년)

Cockpit-driving integration is gaining momentum, and single-chip solutions are on the horizon

The Intelligent Vehicle Cockpit-driving Integration (Cockpit-driving-parking) Industry Report, 2024-2025 released by ResearchInChina combs through and summarizes the advantages and disadvantages of driving-parking integration, cockpit-parking integration and cockpit-driving integration (cockpit-driving-parking), their implementation modes, business models, used chips, market application and distribution, OEMs' planning and layout, competitive landscape, and suppliers, and analyzes and predicts the market size of cockpit-driving integration (cockpit-driving-parking).

1. The installations of driving-parking integration domain controllers soared by 61.9% year on year, and the overall penetration rate exceeded 10%.

In the current general trend towards EEA centralization and OEMs' cost reduction needs, driving-parking integration, cockpit-parking integration and cockpit-driving integration (cockpit-driving-parking) domain controllers have come into being. Compared with cockpit-parking integration and cockpit-driving integration, driving-parking integration is implemented earlier and develops relatively maturely. Driving-parking integration began to be applied in 2021, and went into mass production in 2022. In the first three quarters of 2024, nearly 1.651 million vehicles installed with driving-parking integration domain controllers were sold, a like-on-like spike of 61.9%.

In the first three quarters of 2024, the penetration rate of driving-parking integration domain controllers was 10.7%, up 3.8 percentage points from the prior-year period and 3.6 percentage points versus 2023.

In the first three quarters of 2024, driving-parking integration domain controllers were largely installed on battery electric and extended-range passenger cars, which took a combined 95.1% share. Wherein, the installation rate in battery electric cars was 23.2%, mainly Tesla; the installation rate in the extended-range cars was as high as 77.3%, led by Li Auto and Harmony Intelligent Mobility Alliance (HIMA).

Driving-parking integration domain controller suppliers: Desay SV is far ahead, alone commanding over 30% of the market.

At present, some OEMs design driving-parking integration domain controllers by themselves, and outsource production to third-party suppliers, for example, Tesla (Quanta/Pegatron) and NIO (Flex); some large strong OEMs like Great Wall Motor (Haomo.ai) and BYD (BYD Research Institute) self-develop and self-produce the controllers; Li Auto, HIMA, Zeekr, Xiaomi, IM Motors, and Xpeng among others choose to cooperate with third-party suppliers.

Among the driving-parking integration domain controller suppliers, Desay SV holds a safe lead, alone taking a 30% share in the market. It has formed partnerships with Li Auto, Xiaomi, Zeekr, and Xpeng. Its best-selling products include IPU03 (Horizon J5/NVIDIA Xavier) and IPU04 (NVIDIA Orin X).

The share of single-chip solutions for driving-parking integration domain controllers reached 41%.

Driving-parking integration domain controllers generally adopt multi-chip solutions, but single-chip solutions have already taken a favorable market share (41%), and are expected to prevail in the market soon in the general trend for reducing costs and improving efficiency.

Driving-parking Integration Chip Solution

In the first three quarters of 2024, driving-parking integration domain controllers for passenger cars used a total of 2.68 million chips. Only Tesla (self-use), NVIDIA, and Huawei HiSilicon (mainly for HIMA) together sweep 76% of the market, showing a high market concentration. As concerns chip compute and process, the mainstream chips Tesla's second-generation FSD, Nvidia Orin-X, and Huawei HiSilicon Ascend 610 all boast higher than 100 TOPS and 7nm process.

2. 2024 is the first year for mass production of cockpit-parking integration.

Cockpit-parking integration solutions lower costs and improve efficiency mainly by saving a parking chip and exploiting the compute redundancy of the cockpit chip. For mainly processing image display and audio functions, the cockpit chip has relatively high GPU compute, but limited NPU compute. It is more suitable for integrating basic parking functions and targets vehicle models priced below RMB200,000. The two cockpit-parking integration models launched in August 2024 are both priced within RMB150,000:

The full range of Geely Galaxy E5, launched in early August, uses ECARX's cockpit domain controllers with 1 SiEngine Longying No.1 chip. Only the top-end starship edition adopts a cockpit-parking integration solution, with the manufacturer's suggested retail price (MSRP) of RMB145,800.

Xpeng MONA M03, launched in late August, uses Desay SV's cockpit domain control hardware and AutoAI's software, and packs Qualcomm Snapdragon 8155P. This model has three editions: Long-range Edition with MSRP of RMB119,800, Ultra-long-range Edition with MSRP of RMB129,800, and Ultra-long-range MAX Edition with MSRP of RMB155,800.

Among them the long-range and the ultra-long-range editions adopt a cockpit-parking integration solution, and the driving chip is Mobileye EyeQ4H. The Ultra-long-range MAX Edition with a price of higher than RMB150,000 adopts a driving-parking integration solution, and the driving chip is 2*NVIDIA Orin-X.

It is reported that the above two models have been available on market for only more than three months, but the cumulative delivery has been about 80,000 units, successfully bringing cockpit-parking integration into the mass production stage. In addition, quite a few OEMs such as Dongfeng Forthing, FAW Hongqi, GAC, NIO, Changan, BAIC Arcfox and Neta have already planned to use cockpit-parking integration, and the related suppliers have also introduced multiple cockpit-parking integration domain controllers, including ECARX Antora 1000/Antora 1000 Pro, Desay SV's Gen4 Series, Yuanfeng Technology's Cockpit-parking Integration Controller 1.0/2.0, AutoLink AL-N1/AL-C2, and Foryou Cockpit Platform 3.0.

3. Cockpit-driving integration develops better than expected, skyrocketing by 1071.9% year on year.

As an advanced form of cross-domain integration, cockpit-driving integration is the focus of the layout by players. It was put into use in 2023, ahead of cockpit-parking integration. In April 2023, Voyah Passion, the first model packing a cockpit-driving integration domain controller, was rolled off on market. In just one and a half years, models that actually apply cockpit-driving integration function have numbered up to 17.

In the first three quarters of 2024, cockpit-driving integration domain controllers were installed in 246,600 cars, soaring by 1071.9% on a like-on-like basis. Of course, cockpit-driving integration products are in the introduction stage, and the installation in 246,600 cars suffices to show that cockpit-driving integration has officially entered the mass production and application stage.

In the first three quarters of 2024, the penetration rate of cockpit-driving integration domain controllers was only 1.6%. Yet seen from the application layout of cockpit-driving integration by many OEMs, suppliers, and chip companies, most of them plan volume production and application of it in 2025. We hence speculate that 2025-2027 will be a boom period for cockpit-driving integration, and its penetration rate is expected to reach between 15% and 25% in 2027.

There is a huge market space for cockpit-driving integration suppliers in the future.

From the supplier side, in current stage cockpit-driving integration domain controllers are primarily developed and designed by OEMs, and produced by third parties. Voyah, a subsidiary of the traditional OEM Dongfeng, however adopts the cooperative product of the third-party suppliers Neusoft Reach and Megatronix. Geely, Changan, BAIC and GAC, which plan to set foot in the market in 2025, have established relations with different suppliers on R&D of cockpit-driving integration. There is still huge market space left for suppliers in the future.

Desay SV signed cooperation agreements with GAC Hyper and Chery in April and October 2024, respectively, on cockpit-driving integration domain controllers. In October, it also brought related products to Geely to exchange and share technological innovation and application.

Single-chip solutions for cockpit-driving integration are expected to land in 2025.

Among the current cockpit-driving integration models, except for the low-end edition (within RMB200,000) of Leapmotor C Series, all other models have adopted a multi-chip solution, with a typical configuration of mainstream intelligent cockpit chip (Qualcomm 8155/8295) + mainstream intelligent driving chip (Nvidia Orin-X). Regarding single-chip solutions, multiple OEMs and suppliers prefer Nvidia Thor and Qualcomm Ride Flex SA8775P chips, both of which are scheduled to come into mass production in 2025.

Table of Contents

1 Overview of Cockpit-driving Integration and EEA

• 1.1 Definition of Driving-parking Integration, Cockpit-parking Integration and Cockpit-driving Integration
• 1.2 Comparison between Driving-parking Integration, Cockpit-parking Integration and Cockpit-driving Integration
• 1.3 EEA Evolution Promotes Domain Controller Integration
• 1.4 Automotive EEA Evolution in the Next Decade
• 1.5 Summary of EEA Concentration of Mainstream OEMs (Domain Concentration)
• 1.6 Summary of EEA Concentration of Mainstream OEMs (Domain Fusion + Central Computing Architecture)

2 Overview of Driving-parking Integration

• 2.1 Comparison between Driving-parking Separation and Driving-parking Integration
• 2.2 Four Forms of Driving-parking Integration
• 2.3 Comparison between Multi-chip and Single-chip Driving-parking Integration Solutions
• 2.4 Comparison between Lightweight and High-level Driving-parking Integration Solutions
• 2.5 Driving-parking Integration Chips
  • 2.5.1 What Are the Requirements of Driving-parking Integration for Chips?
  • 2.5.2 How Do Chip Vendors Help OEMs Implement Driving-parking Integration Solutions?
  • 2.5.3 Competitive Landscape in the Field of Driving-parking Integration Chips
  • 2.5.4 Summary of Relationships between Chips, Driving-parking Integration Domain Controllers, and Vehicle Supply Chain
• 2.6 Driving-parking Integration Business Models
  • 2.6.1 How Does the Cooperation Model of the Driving-parking Integration Industry Chain Change?
  • 2.6.2 Driving-parking Integration Industry Chain Cooperation Model 1: OEM-led Development
  • 2.6.3 Driving-parking Integration Industry Chain Cooperation Model 2: Supplier Development Model
  • 2.6.4 Driving-parking Integration Industry Chain Cooperation Model 3: Chip Vendors Participate in Development
• 2.7 How to Transition from Driving-parking Integration to Cockpit-driving Integration?
• 2.8 Main Players in Driving-parking Integration

3 Application of Driving-parking Integration

• 3.1 Installations and Installation Rate of Driving-parking Integration in China
• 3.2 Distribution of Installations of Driving-parking Integration in China: Intelligent Driving Level
• 3.3 Distribution of Installations of Driving-parking Integration in China: EEA
• 3.4 Distribution of Installations of Driving-parking Integration in China: Chip Solution, Computing Power Level
• 3.5 Distribution of Installations of Driving-parking Integration in China: Intelligent Driving Sensor Solution
• 3.6 Distribution of Installations of Driving-parking Integration in China: Independent/Joint Venture OEMs
• 3.7 Distribution of Installations of Driving-parking Integration in China: Vehicle Model Price
• 3.8 Distribution of Installations of Driving-parking Integration in China: Power Type
• 3.9 TOP10 Brands and Models in China by Installations of Driving-parking Integration

4 Driving-parking Integration Suppliers

• 4.1 Competitive Landscape of Driving-parking Integration Domain Controller Suppliers in China
• 4.2 Quarterly Installations of Driving-parking Integration Domain Controller Suppliers in China
• 4.3 Summary of Mass-produced Products of Driving-parking Integration Domain Controller Suppliers in China
• 4.4 Desay SV
  • 4.4.1 Profile
  • 4.4.2 Core Businesses and New Customer Designation Projects in 2023
  • 4.4.3 Overview of Operation, 2023
  • 4.4.4 Overview of Operation, 2024H1
  • 4.4.5 Overview of R&D Investment, 2023
  • 4.4.6 Supply Chain Distribution and Core Customers
  • 4.4.7 Cockpit-driving-parking Business Layout
  • 4.4.8 Driving-parking Integration Domain Control Products (1)
  • 4.4.9 Driving-parking Integration Domain Control Products (2)
  • 4.4.10 Driving-parking Integration Domain Control Products (3)
• 4.5 Huawei
  • 4.5.1 Automotive BU Business Layout and Profile
  • 4.5.2 Revenue from Automotive BU
  • 4.5.3 Three Business Models That Huawei Automotive BU Promoted in the Past
  • 4.5.4 Change in Smart Car Business Model: Smart Car Selection Model Is Upgraded to Harmony Intelligent Mobility Alliance (HIMA)
  • 4.5.5 Main New Cooperative Models of HIMA
  • 4.5.6 Driving-parking Integration Domain Control Products (1)
  • 4.5.7 Driving-parking Integration Domain Control Products (2)
  • 4.5.8 Driving-parking Integration Domain Control Products (3)
• 4.6 iMotion
  • 4.6.1 Profile
  • 4.6.2 Milestones
  • 4.6.3 Revenue (Annual)
  • 4.6.4 Overview of Operation, 2023
  • 4.6.5 Business Model
  • 4.6.6 Product Strategic Roadmap
  • 4.6.7 Driving-parking Integration Domain Control Products (1)
  • 4.6.8 Driving-parking Integration Domain Control Products (2)
  • 4.6.9 Driving-parking Integration Domain Control Products (3)
  • 4.6.10 Core Driving-parking Integration Technology
  • 4.6.11 Expand the Team and Deploy Driving-parking Integration Domain Controllers Based on Horizon J6E
  • 4.6.12 New Dynamics in Driving-parking Integration
• 4.7 Hong Jing Drive
  • 4.7.1 Profile
  • 4.7.2 Development History and Hot Production Models
  • 4.7.3 Business Layout
  • 4.7.4 Business Model
  • 4.7.5 Product Roadmap
  • 4.7.6 Core Autonomous Driving Technology
  • 4.7.7 Driving-parking Integration Domain Control Products
  • 4.7.8 Driving-parking Integration Domain Control: Hyperware 2.5
• 4.8 Technomous
  • 4.8.1 Profile
  • 4.8.2 Driving-parking Integration Domain Control Products
  • 4.8.3 Driving-parking Integration Domain Controllers (1)
  • 4.8.4 Driving-parking Integration Domain Controllers (2)
  • 4.8.5 Driving-parking Integration Domain Controllers (3)
  • 4.8.6 Driving-parking Integration Domain Controller Software Platform
• 4.9 Freetech
  • 4.9.1 Profile
  • 4.9.2 Core Intelligent Driving Capabilities (1)
  • 4.9.2 Core Intelligent Driving Capabilities (2)
  • 4.9.3 Intelligent Driving Solution Roadmap
  • 4.9.4 Driving-parking Integration Domain Control Products (1)
  • 4.9.5 Driving-parking Integration Domain Control Products (2)
  • 4.9.6 Driving-parking Integration Domain Control Products (3)
  • 4.9.7 Driving-parking Integration Domain Control Products (4)
  • 4.9.8 Driving-parking Integration Domain Control Products (6)
  • 4.9.9 Driving-parking Integration Domain Control Products (6)
  • 4.9.10 Intelligent Driving Partners
  • 4.9.11 Recent Dynamics and Designated Mass Production
• 4.10 Baidu Apollo
  • 4.10.1 Profile
  • 4.10.2 Baidu's Strategic Layout in Intelligent Driving
  • 4.10.3 Intelligent Product Matrix
  • 4.10.4 Business Model
  • 4.10.5 Driving-parking Integration Domain Control Products
  • 4.10.6 Iteration Process of Driving-parking Integration Solutions
  • 4.10.7 Driving-parking Integration Solutions (1)
  • 4.10.8 Driving-parking Integration Solutions (2)
  • 4.10.9 Driving-parking Integration Solutions (3)
• 4.11 Zhuoyu Technology (DJI Automotive)
  • 4.11.1 Profile
  • 4.11.2 Development History
  • 4.11.3 R&D and Production
  • 4.11.4 Product Layout
  • 4.11.5 Intelligent Driving Business Development Strategy
  • 4.11.6 Driving-parking Integration Domain Control Products
  • 4.11.7 Driving-parking Integration Domain Control Products: D Series
  • 4.11.8 Driving-parking Integration Solutions: Lingxi Intelligent Driving System
  • 4.11.9 Driving-parking Integration Solutions: Lingxi Intelligent Driving System 2.0
  • 4.11.10 Driving-parking Integration Solutions: Chengxing Platform of Lingxi Intelligent Driving System 2.0
• 4.12 ECARX
  • 4.12.1 Profile
  • 4.12.2 Business Evolution
  • 4.12.3 Strategic Orientation
  • 4.12.4 Revenue
  • 4.12.5 Release of 2024Q2 Performance Report
  • 4.12.6 Ecosystem Companies
  • 4.12.7 Intelligent Vehicle Product Layout
  • 4.12.8 Computing Platform Products
  • 4.12.9 Driving-parking Integration Domain Control Products
• 4.13 MINIEYE
  • 4.13.1 Profile
  • 4.13.2 Revenue (Annual)
  • 4.13.3 Intelligent Driving Product Layout
  • 4.13.4 Technical Capabilities and Solutions
  • 4.13.5 Platformization and Software-Hardware Integration Capabilities
  • 4.13.6 Technology Route
  • 4.13.7 Driving-parking Integration Domain Control Products (1)
  • 4.13.8 Driving-parking Integration Domain Control Products (2)
  • 4.13.9 Driving-parking Integration Domain Control Products (3)
  • 4.13.10 Driving-parking Integration Domain Control Products (4)
  • 4.13.11 Driving-parking Integration Domain Control Products (5)
  • 4.13.12 Driving-parking Integration Domain Control Products (6)
  • 4.13.13 Dynamics, Customers and Development Directions, 2023-2024
• 4.14 Yihang.ai
  • 4.14.1 Profile
  • 4.14.2 Factory Construction
  • 4.14.3 Business Model
  • 4.14.4 Solutions
  • 4.14.5 Driving-parking Integration Domain Control Products
  • 4.14.6 Driving-parking Integration Domain Control Products: Single-chip Lite Version
  • 4.14.7 Driving-parking Integration Domain Control Products: Dual-chip Flagship Version
  • 4.14.8 Driving-parking Integration Domain Control Products: All-scenario Solution
• 4.15 Neusoft Reach
  • 4.15.1 Profile
  • 4.15.2 Autonomous Driving Product Matrix
  • 4.15.3 Driving-parking Integration Domain Control Products (1)
  • 4.15.4 Driving-parking Integration Domain Control Products (2)
  • 4.15.5 Intelligent Driving Partners
• 4.16 EnjoyMove Technology
  • 4.16.1 Profile
  • 4.16.2 Main Products
  • 4.16.3 Driving-parking Integration Domain Control Products (1)
  • 4.16.4 Driving-parking Integration Domain Control Products (2)
  • 4.16.5 Driving-parking Integration Domain Control Products (3)
• 4.17 Idriverplus
  • 4.17.1 Profile
  • 4.17.2 Core Technology
  • 4.17.3 Driving-parking Integration Domain Control Products
  • 4.17.4 Driving-parking Integration Solutions (1)
  • 4.17.5 Driving-parking Integration Solutions (2)
• 4.18 AutoBrain
  • 4.18.1 Profile
  • 4.18.2 Driving-parking Integration Domain Control Products: Single-chip Version
  • 4.18.3 Benefits of Driving-parking Integration Domain Control Products
• 4.19 Zongmu Technology
  • 4.19.1 Profile
  • 4.19.2 Organizational Structure
  • 4.19.3 Financing History
  • 4.19.4 Operation in 2023
  • 4.19.5 Strategic Layout
  • 4.19.6 Intelligent Driving Product and Solution Layout
  • 4.19.7 Driving-parking Integration Domain Control Products (1)
  • 4.19.8 Driving-parking Integration Domain Control Products (2)
  • 4.19.9 Driving-parking Integration Domain Control Products (3)

5 Overview of Cockpit-parking Integration

• 5.1 Definition and Scope of Application of Cockpit-parking Integration
• 5.2 Comparison of Advantages and Disadvantages between Cockpit-parking Integration and Driving-parking Integration
• 5.3 Factors Driving the Development of Cockpit-parking Integration and Challenges
• 5.4 Requirements of Cockpit-parking Integration for Chips
• 5.5 Application and Layout of Mainstream Chips in Cockpit-parking Integration

6 Application of Cockpit-parking Integration

• 6.1 Cockpit-parking Integration Application Layout of OEMs (1)
• 6.1 Cockpit-parking Integration Application Layout of OEMs (2)
• 6.1 Cockpit-parking Integration Application Layout of OEMs (3)
• 6.2 Cockpit-parking Integration Models Launched on Market
  • 6.2.1 Cockpit-parking Integration Models Launched on Market: Geely Galaxy E5 Starship Edition
  • 6.2.2 Cockpit-parking Integration Models Launched on Market: Xpeng MONA M03

7 Cockpit-parking Integration Suppliers

• 7.1 Summary of Products of Cockpit-parking Integration Suppliers (1)
• 7.1 Summary of Products of Cockpit-parking Integration Suppliers (2)
• 7.1 Summary of Products of Cockpit-parking Integration Suppliers (3)
• 7.1 Summary of Products of Cockpit-parking Integration Suppliers (4)
• 7.2 Ecarx
  • 7.2.1 Evolution of Cockpit Computing Platform Products
  • 7.2.2 Cockpit-parking Integration Domain Control Products
• 7.3 Desay SV
  • 7.3.1 Evolution of Intelligent Cockpit Platforms
  • 7.3.2 Intelligent Cockpit Platform Layout Trend
  • 7.3.3 Cockpit-parking Integration Domain Control Products (1)
  • 7.3.4 Cockpit-parking Integration Domain Control Products (2)
  • 7.3.5 Cockpit-parking Integration Domain Control Products (3)
  • 7.3.6 Cockpit-parking Integration Domain Control Products (4)
• 7.4 NavInfo
  • 7.4.1 Profile
  • 7.4.2 Operation
  • 7.4.3 Application Service Capabilities
  • 7.4.4 Evolution of Intelligent Cockpit Platform Products
  • 7.4.5 Cockpit-parking Integration Domain Control Products (1)
  • 7.4.6 Cockpit-parking Integration solutions (2)
  • 7.4.7 Ecosystem Partners
• 7.5 Yuanfeng Technology
  • 7.5.1 Profile
  • 7.5.2 Business Distribution
  • 7.5.3 R&D Investment
  • 7.5.4 Core Personnel
  • 7.5.5 Overall Vehicle Solutions
  • 7.5.6 Cooperation Model of Intelligent Cockpit Domain Controller Business
  • 7.5.7 Intelligent Cockpit Product Line
  • 7.5.8 "Multi-domain Integration" Technical Architecture for Intelligent Cockpit Domain Controllers
  • 7.5.9 Development Route of Cockpit-driving-parking Integration Products
  • 7.5.10 Cockpit-parking Integration Domain Control Products
  • 7.5.11 Cockpit-parking Integration Domain Control Products: Configuration
  • 7.5.12 Cockpit-parking Integration Domain Control Products: Cockpit-parking Integration Domain Controller 1.0
  • 7.5.13 Cockpit-parking Integration Domain Control Products: Cockpit-parking Integration Domain Controller 2.0
  • 7.5.14 Application Scenarios of Cockpit-parking Integration Solutions
  • 7.5.15 Cockpit-parking Integration Controllers: Customer Base
• 7.6 Autolink
  • 7.6.1 Profile
  • 7.6.2 Operation
  • 7.6.3 Cockpit Cross-domain Integration Planning
  • 7.6.4 Cockpit-parking Integration Domain Control Products (1)
  • 7.6.5 Cockpit-parking Integration Domain Control Products (2)
  • 7.6.6 Cockpit-parking Integration Domain Control Products (3)
  • 7.6.7 Cockpit-parking Integration Domain Control Products (4)
  • 7.6.8 Models Installed with Autolink's Cockpit Domain Controllers
• 7.7 Foryou Corporation
  • 7.7.1 Profile
  • 7.7.2 Intelligent Cockpit Domain Product Layout
  • 7.7.3 Evolution of Intelligent Cockpit Domain Control Platforms
  • 7.7.4 Features of Cockpit Domain Controllers Based on AAOP
  • 7.7.5 Intelligent Cockpit Multi-Level Solution
  • 7.7.6 Cockpit-parking Integration Domain Control Products
• 7.8 BICV
  • 7.8.1 Profile
  • 7.8.2 Cockpit-driving-parking Business Layout
  • 7.8.3 Cockpit-parking Integration Domain Control Products
  • 7.8.4 Cockpit-parking Integration Domain Control Products (1)
  • 7.8.5 Cockpit-parking Integration Domain Control Products (2)
  • 7.8.6 Cockpit-parking Integration Domain Control Products (3)
• 7.9 Megatronix
  • 7.9.1 Profile
  • 7.9.2 Intelligent Cockpit Customization and Cooperation Model
  • 7.9.3 Cockpit-parking Integration Domain Control Products
• 7.10 Visteon
  • 7.10.1 Profile
  • 7.10.2 Revenue
  • 7.10.3 Cockpit Domain Controllers
  • 7.10.4 Cockpit-parking Integration Domain Control Products
  • 7.10.5 Cockpit-parking Integration Domain Control Products
• 7.11 Aptiv
  • 7.11.1 Profile
  • 7.11.2 Revenue
  • 7.11.3 SVA Hardware Platform
  • 7.11.4 Wind River Software Platform
  • 7.11.5 Cockpit-parking Integration Domain Control Products
• 7.12 Bosch
  • 7.12.1 Profile of Bosch Mobility
  • 7.12.2 Revenue
  • 7.12.3 Status Quo of Intelligent Cockpit Domain Controller Business
  • 7.12.4 Development Path of Cockpit-driving-parking Integration
  • 7.12.5 Cockpit-parking Integration Domain Control Products
  • 7.12.6 Cockpit-parking Integration Domain Control Products: Hardware Solutions and Parking Capabilities
  • 7.12.7 Benefits of Cockpit-parking Integration Domain Control Products
  • 7.12.8 Open Cooperation Model for China's Local Cockpits

8 Overview of Cockpit-driving Integration

• 8.1 Cockpit-driving Integration Technology System Architecture
• 8.2 Cockpit-driving Integration Implementation Modes
  • 8.2.1 Three Cockpit-driving Integration Implementation Modes
  • 8.2.2 Cockpit-driving Integration Implementation Modes: One Domain Controller, One PCB, Multiple Chips
  • 8.2.3 Cockpit-driving Integration Implementation Modes: One Domain Controller, One PCB, Single Chip
• 8.3 Advantages of Cockpit-driving Integration
• 8.4 Disadvantages of Cockpit-driving Integration and Development Challenges
• 8.5 Cockpit-driving Integration's Requirements for Vehicle Software Architecture
• 8.6 Supply Chain Changes Brought by Cockpit-driving Integration
• 8.7 Cockpit-driving Integration Chips
  • 8.7.1 Cockpit-driving Integration's Requirements for Chips
  • 8.7.2 Chips for Single-chip Solutions for Cockpit-driving Integration: NVIDIA Thor, Qualcomm Snapdragon Ride(TM) Flex SA8775P
  • 8.7.3 Chips for Single-chip Solutions for Cockpit-driving Integration: Black Sesame Wudang C1296, SemiDrive X9CC, Renesas R-Car X5

9 Application of Cockpit-driving Integration

• 9.1 Application of Cockpit-driving Integration in Passenger Cars in China: Installations by Brand, Installation Rate, EEA Type, Domain Controller Suppliers
• 9.2 Application of Cockpit-driving Integration in Passenger Cars in China: Installations by Model, Installation Rate, Price, Sensing Solution, Domain Control Chip
• 9.3 Five-Year Forecast for Installations and Penetration Rate of Cockpit-driving Integration in Passenger Cars in China
• 9.4 Five-Year Forecast for Passenger Car Cockpit-driving Integration Domain Controller Market Size in China
• 9.5 Distribution of Cockpit-driving Integration Installations in Passenger Cars in China, Q1-Q3 2024
  • 9.5.1 Distribution of Cockpit-driving Integration Installations in Passenger Cars in China, Q1-Q3 2024: Energy Type, EEA Type
  • 9.5.2 Distribution of Cockpit-driving Integration Installations in Passenger Cars in China, Q1-Q3 2024: Intelligent Driving Level, ADAS Perception Solution
  • 9.5.3 Distribution of Cockpit-driving Integration Installations in Passenger Cars in China, Q1-Q3 2024: Chip Solution and Computing Power
  • 9.5.4 Distribution of Cockpit-driving Integration Installations in Passenger Cars in China, Q1-Q3 2024: Model Price, Model Class
• 9.6 Typical Passenger Car Models with Cockpit-driving Integration in China
  • 9.6.1 Typical Passenger Car Models with Cockpit-driving Integration in China: Features of Selected Models
  • 9.6.2 Typical Passenger Car Models with Cockpit-driving Integration in China: Voyah Passion
  • 9.6.3 Typical Passenger Car Models with Cockpit-driving Integration in China: 2024 NIO ES6
  • 9.6.4 Typical Passenger Car Models with Cockpit-driving Integration in China: ONVO L60
  • 9.6.5 Typical Passenger Car Models with Cockpit-driving Integration in China: Leapmotor C10
  • 9.6.6 Typical Passenger Car Models with Cockpit-driving Integration in China: Xpeng G6
• 9.7 Chinese Passenger Car OEMs' Application Layout and Planning of Cockpit-driving Integration

10 Cockpit-driving Integration Suppliers

• 10.1 Summary of Products of Cockpit-driving Integration Suppliers (1)
• 10.1 Summary of Products of Cockpit-driving Integration Suppliers (2)
• 10.1 Summary of Products of Cockpit-driving Integration Suppliers (3)
• 10.1 Summary of Products of Cockpit-driving Integration Suppliers (4)
• 10.1 Summary of Products of Cockpit-driving Integration Suppliers (5)
• 10.2 Neusoft Reach
  • 10.2.1 Cockpit-driving Integration Domain Control Products (1)
  • 10.2.2 Cockpit-driving Integration Domain Control Products (2)
  • 10.2.3 Cockpit-driving Integration Domain Control Products (3)
  • 10.2.4 Cockpit-driving Integration Domain Control Products (4)
  • 10.2.5 Cockpit-driving Integration Domain Control Products (6)
• 10.3 Megatronix
  • 10.3.1 Cockpit-driving Integration Domain Control Products
• 10.4 Desay SV
  • 10.4.1 Cockpit-driving Integration Domain Control Products (1)
  • 10.4.2 Cockpit-driving Integration Domain Control Products (2)
  • 10.4.3 Cockpit-driving Integration Domain Control Products (3)
  • 10.4.4 Cockpit-driving Integration Domain Control Products (4)
  • 10.4.5 New Dynamics in Cockpit-driving Integration Domain Control Products: Desay SV Entered Geely with Cutting-edge Products and Technology
• 10.5 Yuanfeng Technology
  • 10.5.1 Cockpit-driving Integration Domain Control Products
  • 10.5.2 Cockpit-driving Integration Domain Control Products: Configuration and Functions
  • 10.5.3 Cockpit-driving Integration Domain Control Products:Application Scenarios
• 10.6 ECARX
  • 10.6.1 Cockpit-driving Integration Domain Control Products (1)
  • 10.6.2 Cockpit-driving Integration Domain Control Products (2)
  • 10.6.3 Cockpit-driving Integration Domain Control Products (3)
  • 10.6.4 Cockpit-driving Integration Domain Control Products (4)
  • 10.6.5 Cockpit-driving Integration Domain Control Products (6)
  • 10.6.6 Cloudpeak Cross-domain Capability Base
• 10.7 AutoLink
  • 10.7.1 Cockpit-driving Integration Domain Control Products
• 10.8 BICV
  • 10.8.1 Cockpit-driving Integration Domain Control Products
  • 10.8.2 Cockpit-driving Integration Domain Control Products (1)
  • 10.8.3 Cockpit-driving Integration Domain Control Products (2)
  • 10.8.4 New Dynamics in Cockpit-driving Integration: Baidu's Former Head of Cockpit-driving Integration Zhou Peng Joins
• 10.9 NavInfo
  • 10.9.1 Cockpit-driving Integration Domain Control Products
  • 10.9.2 Cockpit-driving Integration Domain Control Products (1)
  • 10.9.3 Cockpit-driving Integration Domain Control Products (2)
• 10.10 PATEO CONNECT+
  • 10.10.1 Profile
  • 10.10.2 Main Business and Products
  • 10.10.3 Revenue
  • 10.10.4 Intelligent Cockpit Platform Development Route
  • 10.10.5 Cockpit-driving Integration Domain Control Products
  • 10.10.6 Cockpit-driving Integration Domain Control Products (1)
  • 10.10.7 Cockpit-driving Integration Domain Control Products (2)
  • 10.10.8 Cockpit-driving Integration Domain Control Products (3)
  • 10.10.9 Main Customers
• 10.11 Neusoft Corporation
  • 10.11.1 Revenue (Annual)
  • 10.11.2 Cockpit-driving Integration Domain Control Products (1)
  • 10.11.2 Cockpit-driving Integration Domain Control Products (2)
• 10.12 Bosch
  • 10.12.1 Cockpit-driving Integration Domain Control Products
  • 10.12.2 Cockpit-driving Integration Domain Control Products: Hardware Architecture
  • 10.12.3 Cockpit-driving Integration Domain Control Products: Software Architecture
• 10.13 Aptiv
  • 10.13.1 Cockpit-driving Integration Domain Control Products: Cross-domain Integration Computing Platform (1)
  • 10.13.2 Cockpit-driving Integration Domain Control Products: Cross-domain Integration Computing Platform (2)
• 10.14 Others
  • 10.14.1 NESINEXT's Cockpit-driving Integration Domain Control Products
  • 10.14.2 Zongmu Technology's Cockpit-driving Integration Domain Control Products
  • 10.14.3 Baidu Apollo's Cockpit-driving Integration Domain Control Products