PUBLISHER: ResearchInChina | PRODUCT CODE: 1534983
PUBLISHER: ResearchInChina | PRODUCT CODE: 1534983
Intelligent Vehicle Multi-Domain Computing Industry Report, 2024
Multi-Domain Computing Research: A Summary of Several Ideas and Product Strategies for Cross-Domain Integration
1. Several ideas and strategies for cross-domain integration of OEMs
With the increasingly stringent requirements for advanced autonomous driving in terms of computing power, communication bandwidth, software, and security, automotive electronic and electrical architecture (EEA) has gradually evolved from a domain-centralized architecture to a multi-domain integration, and then to a central computing architecture. At present, the main integration ideas for automotive multi-domain computing are as follows:
The central control domain integrates body, chassis, power, gateway, etc.;
Digital chassis integrates intelligent driving, cockpit, etc.;
Cockpit-driving integration computing platform;
Quasi-central computing platform (One Box, multi-board, multi-core);
Central computing platform (One Box, mostly single board, equipped with single or multiple high-performance chips, using board-level interconnection technology).
At present, Leapmotor and Voyah have evolved into a central computing platform, Xpeng has entered a quasi-central computing platform, and most players have also entered the stage of domain integration, among which the development of cockpit-driving integration computing platform is relatively booming.
With the development of autonomous driving, cross-domain integration is imperative, and OEMs are accelerating the implementation of cross-domain integration models.
NIO central computing platform ADAM
The ADAM cross-domain solution of NIO's central computing platform integrates two chips on the same circuit board. The central computing platform ADAM can eliminate the need for encoding and decoding between different domains in the car, eliminating the need for encoding and decoding chips, power supplies, heat dissipation, wiring harnesses, etc. It directly replaces Gigabit Ethernet through etching circuits on the circuit board, and the cross-domain data bandwidth between intelligent driving and cockpit is greatly increased from Gigabit to 16Gbps, achieving a transmission rate increase of more than 10 times.
In addition, through cross-domain computing power sharing, each large computing power demand can be more rationally allocated, allowing intelligent driving chip NVIDIA Orin X and intelligent cockpit chip 8295 to solve their respective tasks.
Neta Haozhi Supercomputer XPC-S32G
In June 2024, Neta, NXP, HiRain, and Wind River jointly released the first integrated gateway domain control product--Haozhi Supercomputer XPC-S32G, which will be launched in 2024H2 with the new Neta S model.
Haozhi supercomputer XPC-S32G is based on the growing EEI architecture of Neta Shanhai Platform:
Equipped with NXP's high-performance S32G3 automotive network processor based on Arm Cortex-M7 and Cortex-A53;
Equipped with Wind River's advanced RT-Linux operating system solution;
Equipped with a SOA software architecture based on a powerful integrated development environment.
Neta plans to use Haozhi Supercomputer XPC-S32G as the basis for the vehicle network backbone system and service-oriented SOA architecture. The system can be understood as the "hub" of in-vehicle communication backbone network, with nine functions of central gateway, vehicle thermal management, battery energy management, power torque management, remote diagnosis, calibration, full data collection, SOA-type service gateway, edge computing and OTA Master, which can realize the interconnection of high-security cross-domain functional data, as well as automotive cyber security defense, and is responsible for vehicle control management, ensuring information output with extremely low delay, and has future-oriented vehicle function iteration capabilities.
2. Cross-domain integration products of Tier1 suppliers: from cockpit-driving integration platform, central cross-domain platform, quasi-central computing platform, central computing platform and other dimensions
Product development direction (1): cockpit-driving domain + functional domain (gateway, network connection, body, chassis, etc.) integration
Since 2024, OEMs have successively implemented the cross-domain integration architecture and gradually iterated to the central computing platform. In the process of cross-domain integration, "cockpit-driving integration" and "cockpit-driving + other domains" concentrate the computing power of the whole vehicle, closer to the central computing platform, and are currently one of the mainstream directions of cross-domain integration. Judging from the current supply layout, most of the solutions for cockpit + cockpit-driving integration are done.
In order to meet the mainstream development trend, Tier1s has also increased its cross-domain Product R&D, such as ECarx, JoyNext, AutoLink, PATEO, Continental, Desay SV and other suppliers, have launched relevant cross-domain integration solutions.
ECarx's cross-domain integration solutions are divided into two types: "cockpit-parking" and "cockpit-driving". The single-chip "cockpit-parking integration" solution based on "Longying No. 1" chip has been installed in mass production model of Galaxy E5, realizing the integration of intelligent cockpit and automatic parking functions.
The cockpit-driving integration solution is planned for mass production on the model in 2025 and is divided into two series:
One is a cost-effective solution for basic "cockpit-driving-parking" functions, such as "Car Brain (R) Antola Series", which adopts cockpit SoC Longying No. 1 with strong AI computing power. On the basis of original cockpit capability, an additional 2MP binocular camera can support development of "cockpit-driving-parking" functions, including HWA (highway assistance), ALC (automatic lane change assistance), APA (automatic parking assistance), RPA (remote control parking), as well as DMS (driver monitoring system), full scene voice interaction, HMI (human-machine interface) and other functions.
The second is a high-performance solution for high-order "cockpit-driving-parking" functions, such as "Car Brain Series". Through the single-board integration of two high-performance SoCs of intelligent cockpit + intelligent driving, cockpit-driving is realized. Through Ecarx Yunshan cross-domain software platform, the computing power can be reasonably allocated to each demand module. PCIe high-speed data transmission is used, and the transmission efficiency is more than 10 times higher than that of the traditional. With the high computing power of the two SoCs, it supports high-order autonomous driving functions of L2 + and above to match the demand of the mainstream market for high-order autonomous driving. At the same time, the scalable design of the overall architecture also provides better flexibility for the future chip computing power allocation. The integrated software and hardware greatly improve development efficiency and significantly reduce BOM cost of the solution.
Product development direction (2): body electronics extend to central control, integrating digital chassis, power, new energy systems, etc
Traditional body electronics are gradually developing cross-domain central controller products, which are further integrated with chassis, power, and new energy systems.
Taking UAES as an example, in order to meet the hardware and software needs of customers in the new EEA of future automobiles, UAES established Cross-Domain Control Business Unit (Advanced Connection Business Unit) in April 2021, which was integrated from the former Electronic Controller Business Unit and the Body Electronics Business Unit. Beginning in 2024, the organizational structure will be further integrated, and all low-voltage controller businesses will also be merged into the Cross-Domain Control Business Unit.
The Cross-Domain Control Business Unit launched hardware products such as in-vehicle computing platform (VCP), zonal controller (ZECU), body domain controller and smart grid management module (PNG), as well as service-based software architecture (SOA) and USP software development platform.
In 2023, UAES has acquired and synchronized the development of "central computing + zonal controller + SOA" platform on the new architecture for 8 customers, and realized the mass production of the first zonal controller product in Chinese market in June 2023. Through zonal architecture, nearly 20 independent ECUs can be integrated, and the communication rate can be increased from 2M to up to 1000M.
3. Cross-domain integration software platform: a foundation for enabling cross-domain computing
Single-chip fusion deployment of multiple function sets will make software complexity increase significantly, which brings new concerns for OEMs, but also an urgent need to solve the problem,ECARX, NESINEXT, ThunderSoft, ArcherMind Technology and others have launched relevant cross-domain software solutions.
ECARX Cloudpeak Cross-Domain Software Platform
In response to the development trend of cross-domain integration, central computing, and the actual mass production needs of global delivery, ECARX has launched ECARX Cloudpeak cross-domain software platform for the global smart car market, which is designed with SOA concept to ensure standardization and modularization of components, covering the underlying system software (Cloudpeak Virtualization), multi-operating systems, middleware, upper-layer application modules, and global application ecosystems. It can be combined with its different computing platforms to form a complete solution, easily realizing cross-domain functionality. It has been deployed on multiple mass-produced models.
In the Lynk & Co Z10 smart cockpit solution to be released, thanks to ECARX Cloupeak's interconnection of cockpit and intelligent driving systems, the image information sensed by sensors associated with intelligent driving is processed and presented on the central control screen in real time. At the same time, it integrates the lane-level navigation of cockpit domain and NOA function of intelligent driving domain, perfectly presenting a "human-computer co-driving" interface, realizing an immersive interactive experience that restores the real physical world.
NESINEXT CoreFusion cockpit-driving integration software open API
NESINEXT and Black Sesame Intelligent jointly create the open API of cockpit-driving integrated software, which is developed based on Wudang C1296 chip, which can solve the difficulties and pain points of single SoC cross-domain fusion function deployment, and can provide OEMs and ecological partners with full-stack, efficient, and low-cost development of operating system-level software bases, power builder chains, and ecosystems.
JoyNext has a mature tool chain, creating an intelligent cockpit framework, intelligent driving AP/CP middleware and automation adaptation tools that can support C1200 series chip platform. JoyNext and Black Sesame Intelligence have cooperated for many years, and have carried out in-depth cooperation in the fields of cockpit-driving integration operating system-level software base, power builder chain and complete ecosystem.
Under the trend of central computing architecture, the in-vehicle operating system has begun to evolve from a domain operating system to a vehicle operating system. By integrating the functions of cockpit operating system, intelligent driving operating system, and safety vehicle control operating system through central computing platform, the development efficiency of OEMs can be improved.
NIO global operating system Tianshu SkyOS
NIO intelligent electric vehicle global operating system Tianshu SkyOS is the underlying operating system of NIO vehicle, establishing a comprehensive and three-dimensional technical system for vehicle R&D, so that various devices can be organically integrated to achieve efficient collaboration.
SkyOS has built a "1 + 4 + N" technology cluster, covering multiple fields such as vehicle control, intelligent driving, cockpit, mobile Internet, etc., and has become a comprehensive and leading intelligent digital technology base. The NIO full stack has developed four sub-core systems, including "SkyOS-M", "SkyOS-L", "SkyOS-R" and "SkyOS-C".
SkyOS-L: The first domestic alternative to AutoSAR and a large-scale commercial real-time operating system. In comparison with AUTOSAR, SkyOS-L can execute stably whether it is a high-priority, medium-priority or low-priority instruction. AUTOSAR is not as accurate as SkyOS-L in medium-priority and low-priority instructions.
SkyOS-M: It is a micro-kernel architecture, running in the central brain, mainly controlling the body, chassis, suspension, etc. The kernel is more stable than the traditional Linux, and the service isolation is better. At the same time, on the basis of security isolation, there are four layers of monitoring and three layers of recovery security mechanism.
SkyOS-C: A deeply customized operating system based on Android, carrying the functions of a smart cockpit, self-developed TOX protocol stack, more stable data transmission, and AI intelligent experience including NOMI.
SkyOS-R: Increase the load capacity of the system.
Intelligent Vehicle Multi-Domain Computing Industry Report, 2024 mainly studies following:
Typical multi-domain computing architecture ideas, including Tier 1's cross-domain computing product layout and ideas, OEMs' cross-domain product layout and ideas, etc.
Multi-domain computing platform, including central control domain, digital chassis +intelligent driving + cockpit integration domain, cockpit-driving integration domain, quasi-central computing platform, central computing platform and other products;
Research on the impact of multi-domain computing on automotive software, MCU, VCU, and ECU;
Research on the layout, mass production, and cooperation of OEMs in multi-domain computing;
Research on the development, the latest technology layout, and product dynamics of Tier1s in multi-domain computing at home and abroad.
Table of Contents
1 Typical Multi-Domain Computing Architecture Ideas
- 1.1 Multi-domain Fusion Computing Development Ideas
- 1.1.1 Multi-domain Fusion Development Trend: Horizontal Integration, Computing Power Concentration (1)
- 1.1.2 Multi-domain Fusion Development Trend: Horizontal Integration, Computing Power Concentration (2)
- 1.1.3 Common Evolution Logic of Multi-domain Computing
- 1.1.4 Multi-domain Computing Development Path
- 1.1.5 Five Design Ideas of Multi-domain Computing
- 1.1.6 Multi-domain Fusion Requires "Integrated" Development
- 1.1.7 Development and Management Challenges of Cross-domain Fusion
- 1.1.8 Cross-domain Fusion Brings more Practical Application Services: Predictive Battery Thermal Management
- 1.2 Cross-domain Computing Products and Ideas (from the perspective of Tier 1s)
- 1.2.1 Multi-domain Computing Products and Ideas Summary of Domestic Tier1s (1)
- 1.2.2 Multi-domain Computing Products and Ideas Summary of Domestic Tier1s (2)
- 1.2.3 Multi-domain Computing Products and Ideas Summary of Domestic Tier1s (3)
- 1.2.4 Multi-domain Computing Products and Ideas Summary of Domestic Tier1s (4)
- 1.2.5 Multi-domain Computing Products and Ideas Summary of Domestic Tier1s (5)
- 1.2.6 Multi-domain Computing Products and Ideas Summary of Domestic Tier1s (6)
- 1.2.7 Multi-domain Computing Solutions of Overseas Tier 1 Suppliers (1)
- 1.2.8 Multi-domain Computing Solutions of Overseas Tier 1 Suppliers (2)
- 1.3 Cross-domain computing products and ideas (from the perspective of OEMs)
- 1.3.1 2024 is the First Year of Cross-domain (Central Computing + Zonal Controller)
- 1.3.2 Multi-domain Fusion can Enhance OEM Competitiveness
- 1.3.3 Multi-domain Fusion Evolution
- 1.3.4 OEM Multi-domain Fusion Layout and Views (1)
- 1.3.5 OEM Multi-domain Fusion Layout and Views (2)
- 1.3.6 Summary of Cross-domain Fusion Production Models (1)
- 1.3.7 Summary of Cross-domain Fusion Production Models (2)
- 1.3.8 Summary of Cross-domain Fusion Production Models (3)
2 Multi-domain Computing Platform
- 2.1 Central Control Domain (Body, Chassis, Power, Gateway)
- 2.1.1 Central Control Domain (Body, Chassis, Power, Gateway) Product Selection Summary of Tier 1s (1)
- 2.1.2 Central Control Domain (Body, Chassis, Power, Gateway) Product Selection Summary of Tier 1s (2)
- 2.1.3 Central Control Domain (body, chassis, power, gateway) Product Applications of OEMs
- 2.1.4 Central Control Domain (based on NXP's latest generation of Heterogeneous SOC): HiRain CCP
- 2.1.5 Central Control Domain: VCU8.6
- 2.1.6 Central Control Domain (based on NXP S32G)
- 2.1.7 Central Control Domain (based on NXP S32G399)
- 2.1.8 Central Control Domain: BYD Tianxuan Cross-domain Computing Platform
- 2.1.9 Central Control Domain (based on NXP S32G): GAC Xingling Architecture Central Computer
- 2.1.10 Central Control Domain: ZEEKR
- 2.1.11 Central Control Domain: ZEEKR Software Feature Deployment
- 2.1.12 Central Control Domain: Zonal Controller
- 2.1.13 Central Control Domain (based on Renesas RCAR-M3)
- 2.2 Multi-domain Fusion of Digital Chassis + Intelligent Driving + Cockpit
- 2.2.1 Three Routes of Chassis Domain Integration
- 2.2.2 Smart Chassis Eventually Goes to Cross-Domain Fusion of Software/Hardware Separation (1)
- 2.2.3 Smart Chassis Eventually Goes to Cross-Domain Fusion of Software/Hardware Separation (2)
- 2.2.4 Smart Chassis Cross-domain Fusion in 2.0
- 2.2.5 Tier 1 Chassis Domain + Intelligent Driving Domain Cross-domain Fusion Loading Status
- 2.2.6 Tier 1 Chassis Domain + Intelligent Driving Domain Cross-domain Fusion Loading Status
- 2.2.7 Digital Chassis + Smart Driving + Cockpit Multi-domain Fusion (1)
- 2.2.8 Digital Chassis + Smart Driving + Cockpit Multi-domain Fusion (2)
- 2.2.9 Digital Chassis + Smart Driving + Cockpit Multi-domain Fusion (3)
- 2.3 Cockpit-Driving Integration Computing Platform
- 2.3.1 Cockpit-Driving Integration will be Diverse
- 2.3.2 Cockpit-Driving Integration Market Evolves from Driving-Parking Integration/Cockpit-Parking Integration to Cockpit-Driving Integration
- 2.3.3 Technology Evolution Route of Cockpit-Driving Integration
- 2.3.4 Cockpit-Driving Integration Computing Platform Development Status and Trend: Cockpit-parking Integration Solution
- 2.3.5 Cockpit-Driving Integration Computing Platform Development Status and Trends: Cockpit-Driving-Parking Integration
- 2.3.6 Cockpit-driving Integration Computing Platform Development Status and Trends: Cockpit-Driving Integration
- 2.3.7 Main Forms of Cockpit-Driving Integration
- 2.3.8 Cockpit-Driving Integration Computing Platform Models of Domestic Suppliers (1)
- 2.3.9 Cockpit-Driving Integration Computing Platform Models of Domestic Suppliers (2)
- 2.3.10 Cockpit-Driving Integration Computing Platform Models of Domestic Suppliers (3)
- 2.3.11 Cockpit-Driving Integration Computing Platform Models of Domestic Suppliers (4)
- 2.3.12 Cockpit-Driving Integration Computing Platform Models of Domestic Suppliers (5)
- 2.3.13 Cockpit-Driving Integration Computing Platform Models of Domestic Suppliers (6)
- 2.3.14 Cockpit-Driving Integration Computing Platform Models of Domestic Suppliers (7)
- 2.3.15 Cockpit-Driving Integration Computing Platform Models of Foreign Suppliers (1)
- 2.3.16 Cockpit-Driving Integration Computing Platform Models of Foreign Suppliers (2)
- 2.3.17 Cockpit-Driving Integration Computing Platform Architecture (1)
- 2.3.18 Cockpit-Driving Integration Computing Platform Architecture (2)
- 2.3.19 Cockpit-Driving Integration Computing Platform Architecture (3)
- 2.3.20 Cockpit-Driving Integration Computing Platform Architecture (4)
- 2.3.21 Cockpit-Driving Integration Computing Platform (based on SemiDrive X9SP): Banma Integrated Domain Controller
- 2.3.22 Cockpit-Driving Integration Computing Platform (based on Qualcomm SA8295+NXPS32G): Z-One Cross-domain Fusion Central Brain ZXD1
- 2.3.23 Cockpit-Driving Integration Computing Platform (based on NXP S32G): Neta Cockpit-Driving Integrated Domain
- 2.3.24 Cockpit-Driving Integration Computing Platform (based on Qualcomm SA8775) (1)
- 2.3.25 Cockpit-Driving Integration Computing Platform (based on Qualcomm SA8775) (2)
- 2.3.26 Cockpit-Driving Integration Computing Platform (based on Qualcomm SA8775) (3)
- 2.3.27 Cockpit-Driving Integration Computing Platform (Qualcomm 8155+Horizon J3): PATEO + Zongmu "Cockpit-Driving-Parking Integration" Domain Control
- 2.3.28 Cockpit-Driving Integration Computing Platform (based on Qualcomm SA8775) (4)
- 2.3.29 Cockpit-Driving Integration Computing Platform (based on Qualcomm SA8775) (5)
- 2.3.30 Cockpit-Driving Integration Computing Platform (based on SemiDrive X9U+Horizon J5): G-Pulse MADC 3.5
- 2.4 Quasi-Central Computing Platform (Cockpit, Body, Gateway, 5G, VCU, etc.) Platform
- 2.4.1 Quasi-Computing Platform (Cockpit, Body, Gateway, 5G, VCU, etc.) Models of Tier 1s (1)
- 2.4.2 Quasi-Computing Platform (Cockpit, Body, Gateway, 5G, VCU, etc.) Models of Tier 1s (2)
- 2.4.3 Quasi-Central Computing platform (based on Qualcomm SA8295+Horizon J5)
- 2.4.4 Quasi-Central Computing platform (based on Qualcomm SA8295 + NXPS32G)
- 2.4.5 Quasi-Central Computing Platform (based on NVIDIA Orin + Qualcomm SA8295 + Black Sesame A1000)
- 2.5 One Chip Central Computing Platform
- 2.5.1 Central Computing Platform: One Chip Product Selection
- 2.5.2 One Chip Cross-domain Computing Platform (based on Black Sesame Wudang C1296): Technical Route of JoyNext Central Computing Unit
- 2.5.3 One chip Cross-domain Computing Platform (based on Black Sesame Wudang C1296): JoyNext's SOA-based Human-machine Co-driving System Design
- 2.5.4 One Chip Cross-domain Computing Platform (based on SemiDrive X9 series): Neusoft Reach X-Center 2.0
- 2.5.5 One Chip Central Computing SoC Selection (1)
- 2.5.6 One Chip Central Computing SoC Selection (2)
- 2.5.7 One Chip Central Computing SoC Selection (3)
- 2.5.8 One Chip Central Computing SoC: ThorCentral Computing Solution Layout
- 2.5.9 One Chip Central Computing SoC: SemiDriveX9 Series
- 2.5.10 One Chip Central Computing SoC: Multi-core heterogeneous X9CC for Central Computing
- 2.5.11 One Chip Central Computing SoC: Central Computing Architecture Solution Based on X9 Series
3 Multi-domain Computing Platform Supply Chain
- 3.1 Impact of Multi-domain Computing on Software: OEMs' Perspective
- 3.1.1 Cross-domain Fusion Computing Facilitates Hardware and Software Decoupling (1)
- 3.1.2 Cross-domain Fusion Computing Facilitates Hardware and Software Decoupling (2)
- 3.1.3 Cross-domain Fusion Computing Requires a Unified Software Architecture Platform (ARMSOAFEE architecture as an example)
- 3.1.4 Software Architecture Upgrade
- 3.1.5 Core Software Layer of Vehicle OS
- 3.1.6 Main OEMs' Layout of Vehicle OS
- 3.1.7 Main Limiting Factors of OEMs Self-developed Vehicle OS
- 3.1.8 OEMs Cross-domain Software Summary: OS System
- 3.1.9 OEMs Cross-domain OS (based on Qualcomm 3rd Gen Snapdragon Cockpit Platform): Galaxy OS
- 3.1.10 Typical Case of OEM OS Layout Model (1)
- 3.1.11 Typical Case of OEM OS Layout Model (2)
- 3.1.12 Typical Case of OEM OS Layout Model (3)
- 3.1.13 Typical Case of OEM OS Layout Model (4)
- 3.1.14 Typical Case of OEM OS Layout Model (5)
- 3.1.15 Typical Case of OEM OS Layout Model: NIO Self-developed Global OS
- 3.1.16 Typical Case of OEM OS Layout Model: Mercedes-Benz MB. OS
- 3.2 Impact of Multi-domain Computing on Software: Tier1's Perspective
- 3.2.1 Cross-domain Fusion Software Development Technologies: Virtualization, Cloud Native Development, Containerization
- 3.2.2 Cross-domain Fusion Software Development Platform: USP Platform
- 3.2.3 Cross-domain Software Development Trend: Evolution to Vehicle OS
- 3.2.4 Evolution of Vehicle OS Development Model
- 3.2.5 Vehicle OS Market Opportunities for Suppliers
- 3.2.6 Automotive OS Software Suppliers Role Evolution
- 3.2.7 Evolution of Business Model under Vehicle OS Trend
- 3.2.8 Vehicle OS Business Model Market Changes: Software OS Suppliers and Hardware Chip Vendors Bind, Deep Cooperation
- 3.2.9 Cross-domain Software Summary of Tier 1s: Vehicle OS System
- 3.2.10 Cross-domain OS (based on Qualcomm SA8775): ThunderSoft Aqua Drive OS (1)
- 3.2.11 Cross-domain OS (based on Qualcomm SA8775): ThunderSoft Aqua Drive OS (2)
- 3.2.12 Cross-domain OS (based on Qualcomm SA8775): ArcherMind Technology Fusion OS (1)
- 3.2.13 Cross-domain OS (based on Qualcomm SA8775): ArcherMind Technology Fusion OS (2)
- 3.2.14 Cross-domain OS: Banma Alios Develops Towards Vehicle OS
- 3.2.15 Cross-domain OS: Banma Vehicle OS Business Model
- 3.2.16 Cross-domain OS: Deep Cooperation Model between Banma and IM
- 3.2.17 Cross-domain OS: End-to-end Vehicle OS Solution of ETAS
- 3.2.18 Cross-domain OS: KOTEI Kcar-OS
- 3.2.19 Cross-domain Software Summary of Tier 1s: Software Platforms
- 3.2.20 Cross-domain Software Platform: ECARX Cloudpeak (1)
- 3.2.21 Cross-domain Software Platform: ECARX Cloudpeak (2)
- 3.2.22 Cross-domain Software Platform: JoyNext CoreFusion
- 3.2.23 Cross-domain Software Platform: Neusoft Reach NeuSAR 4.0
- 3.2.24 Cross-domain Software Platform: Huawei iDVP
- 3.3 Impact of Multi-domain Computing on MCUs
- 3.3.1 Use of MCUs in Traditional Architectures
- 3.3.2 Cross-domain Fusion Layout can Save some MCUs
- 3.3.3 Flexible Deployment of MCU Applications under Cross-domain Fusion Architecture
- 3.3.4 Cross-domain High Speed MCU Product Summary (1)
- 3.3.5 Cross-domain High Speed MCU Product Summary (2)
- 3.3.6 Cross-domain High Speed MCU Product Summary (3)
- 3.3.7 Cross-domain High Speed MCU Product Summary (4)
- 3.3.8 Cross-domain MCU: SemiDrive Body + Chassis + Power Cross-domain Fusion Chip E3650
- 3.3.9 Cross-domain MCU: SemiDrive Gateway Chip Product for Next-Generation Cross-domain Architecture G9H (1)
- 3.3.10 Cross-domain MCU: SemiDrive Gateway chip product for Next-generation Cross-domain Architecture G9H (2)
- 3.3.11 Cross-domain MCU: NXP S32N55
- 3.3.12 Cross-domain MCU: NXP S32G399
- 3.3.13 Cross-Domain MCU: Texas Instruments Zonal EEA Gateway Chip Jacinto (TM) DRA821
- 3.4 Impact of Multi-domain Computing on VCU
- 3.4.1 Structure of Independent VCU under Traditional Architecture (1)
- 3.4.2 Structure of Independent VCU under Traditional Architecture (2)
- 3.4.3 Integration Direction of VCU under the Trend of Cross-domain Computing (1)
- 3.4.4 Integration direction of VCU under the Trend of Cross-domain Computing (2)
- 3.4.5 VCU is integrated into Domain Controller
- 3.4.6 VCU integrated into Vehicle Control Domain
- 3.4.7 VCU Market Changes under Cross-domain Fusion trend
- 3.5 Impact of Multi-domain Computing on ECUs
- 3.5.1 ECUs are widely Distributed under Traditional Architecture
- 3.5.2 A large Number of ECUs will be integrated into HPC or Cross-domain Computing Platform Along with Multi-domain Computing Trend
- 3.5.3 OEMs' Planning of Integrated ECUs
4 Multi-domain Computing Technology Layout of OEMs
- 4.1 Geely
- 4.1.1 ZEEKR Central Super Computing Platform Architecture
- 4.1.2 ZEEKR Cross-domain Communication Standard
- 4.1.3 Multi-domain Computing Software Layout: ZEEKR EE 3.0 Central Computing Platform
- 4.1.4 Multi-domain Computing Software Layout: SOA Software Service Architecture
- 4.1.5 Multi-domain Computing Software Layout: Geely Galaxy OS Cross-domain Fusion Operating System
- 4.2 SAIC
- 4.2.1 Multi-domain Fusion Computing System Summary: 1st Gen
- 4.2.2 Multi-domain Fusion Computing System Summary: 2nd Gen
- 4.2.3 Multi-domain Computing Layout: All-domain Motion Control Platform (VMC) (1)
- 4.2.4 Multi-domain Computing Layout: All-domain Motion Control Platform (VMC) (2)
- 4.2.5 Z-one's Multi-domain Computing Layout: SOA Software Platform (1)
- 4.2.6 Z-one's Multi-domain Computing Layout: SOA Software Platform (2)
- 4.2.7 Multi-domain Computing Layout: Z-One Central Brain ZXD1
- 4.2.8 Multi-domain Computing Layout: Z-One Central Brain ZXD2
- 4.2.9 Multi-domain Computing Layout: IM L6 Cockpit-driving Integration Computing Platform
- 4.3 GAC
- 4.3.1 Multi-domain Fusion Computing System Summary
- 4.3.2 Multi-domain Computing Layout: X-Soul Architecture in GA3.0
- 4.3.3 Multi-domain Computing Layout: SOA Software Platform
- 4.4 Great Wall Motor
- 4.4.1 Multi-domain Fusion Computing System Summary
- 4.4.2 Multi-domain Computing Layout:Cockpit-driving Integration Central Computing+SOA Software Topology
- 4.4.3 GEEP 4.0 Quasi Central Multi-domain Computing Layout
- 4.4.4 GEEP 5.0 Central Computing Platform
- 4.5 FAW Hongqi
- 4.5.1 Multi-domain Fusion Computing System Summary
- 4.5.2 Multi-domain Computing Layout: Central Computing Platform-based HIS Architecture
- 4.5.3 Multi-domain Computing Layout: Vehicle Control Platform mass Production in 2025
- 4.5.4 Multi-domain Computing Layout: TSN Ethernet Multi-domain Controller
- 4.6 BYD
- 4.6.1 Multi-domain Fusion Computing System Summary
- 4.6.2 Cross-domain Computing Platform: Tianxuan
- 4.6.3 Multi-domain Computing Layout: Yisifang System
- 4.7 Changan Automobile
- 4.7.1 Multi-domain Fusion Computing System Summary
- 4.7.2 Advantages of Multi-domain Fusion Architecture
- 4.7.3 CIIA 2.0 Multi-domain Computing Layout: Software-Driven Architecture (SDA)
- 4.8 Li Auto
- 4.8.1 Multi-domain Fusion Computing System Summary: Function Module of LEEA2.0 & LEEA3.0 and Supply Chain
- 4.8.2 Iteration of Multi-domain Fusion Computing to Centralized Architecture
- 4.8.3 LEEA 2.0 Multi-domain Computing Layout: Central Domain Controller (XCU)
- 4.8.4 LEEA 3.0 Centralized Computing Layout
- 4.8.5 LEEA 3.0 Centralized Computing Layout: Communication Network Architecture
- 4.9 Xpeng Motors
- 4.9.1 Multi-domain Fusion Computing System and Supply Chain Summary: XEEA3.5 (1)
- 4.9.2 Multi-domain Fusion Computing System and Supply Chain Summary: XEEA3.5 (2)
- 4.9.3 Multi-domain Computing Layout: Building a Cross-domain Fusion Smart Base
- 4.9.4 Build Cross-domain Fusion Smart Base: Decoupling Hardware and Software, Optimal Allocation of Hardware Resources
- 4.9.5 Multi-domain Computing Layout: Central Computing Architecture
- 4.9.6 Multi-domain Computing Layout: Central Supercomputing Platform Architecture
- 4.9.7 Multi-domain Computing Layout: Central Computing Domain and Smart Driving Domain Software Architecture
- 4.9.8 Multi-domain Computing Layout: Vehicle Communication Middleware
- 4.9.9 Multi-domain Computing Layout: Virtualization Technology
- 4.9.10 Multi-domain Computing Case: Smart Driving Camera and Cockpit Camera Sharing
- 4.10 NIO
- 4.10.1 Multi-domain Fusion Computing System: Function Modules of NT2.0 & NT3.0 and Supply Chain (1)
- 4.10.2 Multi-domain Fusion Computing System: Function Modules of NT2.0 & NT3.0 and Supply Chain (2)
- 4.10.3 Cross-domain Solution Realizes Cost Reduction
- 4.10.4 NIO to Achieve Cross-domain Computing Power Fusion
- 4.10.5 NIO Brings NOMI GPT through Cross-domain Computing Power Sharing
- 4.10.6 Multi-domain Computing Layout: Central Computing Platform ADAM
- 4.10.7 Multi-domain Computing Layout: Interconnected Central Gateway LION Integrate Body Domain
- 4.10.8 Multi-domain Computing Layout: Intelligent Chassis Domain Controller ICC and Intelligent Driving Domain Cross-domain Fusion
- 4.10.9 Multi-domain Computing Layout:SKY OS
- 4.11 Neta Auto
- 4.11.1 Multi-domain Fusion Computing System Summary
- 4.11.2 Multi-domain Computing Layout: the First Fusion Domain Control Haozhi Super Computing XPC-S32G (1)
- 4.11.3 Multi-domain Computing Layout: the First Fusion Domain Control Haozhi Super Computing XPC-S32G (2)
- 4.11.4 Multi-domain Computing Layout: Shanhai Platform (Gen.2 EEI) Central Super Computing System
- 4.11.5 Multi-domain Computing Layout: Evolve to Multi-domain Fusion and Central Computing
- 4.11.6 Multi-domain Computing Layout: Self-developed Central Computing Platform
- 4.11.7 Multi-domain Computing Layout: Qualcomm SA8255P and Qualcomm SA8775P-based Cockpit-driving Integration Solution
- 4.12 Leapmotor
- 4.12.1 Multi-domain Fusion Computing System Summary
- 4.12.2 Multi-domain Computing Layout: Four-domain Fusion with Two Chips (1)
- 4.12.3 Multi-domain Computing Layout: Four-domain Fusion with Two Chips (2)
- 4.12.4 Central Integrated E/E Architecture Enables Self-development and Self-manufacturing Capabilities to Share 70% of Vehicle Cost
- 4.13 Volkswagen
- 4.13.1 Multi-domain Fusion Computing System Summary
- 4.13.2 Adopt XPeng Super Computing Platform+ Zonal Control Architecture
- 4.13.3 Multi-domain Computing Layout: System Architecture of ICAS3 Cabin Domain Controller
- 4.13.4 Multi-domain Computing Layout: Domain Extension and Domain Fusion of ICAS3 Cabin Domain Controller
- 4.13.5 Multi-domain Computing Layout: Safety Mechanism of VW ICAS3 Cabin Domain Controller Cross-domain Communication
- 4.13.6 Multi-domain Computing Layout: ICAS1 Network Architecture
- 4.14 Voyah
- 4.14.1 Multi-domain Fusion Computing System Summary
- 4.14.2 Tianyuan Multi-domain Computing Layout: Central Controller OIB
- 4.15 Tesla
- 4.15.1 Central Computing Module
- 4.16 Multi-domain Computing Summary of OEMs
- 4.16.1 Cross-domain Fusion Path of Leapmotor
- 4.16.2 Cross-domain Fusion Path of XPeng
- 4.16.3 Cross-domain Fusion Path of NIO
- 4.16.4 Cross-domain Fusion Path of Li Auto
- 4.16.5 Cross-domain Fusion Path of Neta
- 4.16.6 Cross-domain Fusion Path of Voyah
- 4.16.7 Cross-domain Fusion Path of SAIC
5 Multi-domain Computing Technology Layout of Chinese Tier 1 Suppliers
- 5.1 ECarx
- 5.1.1 Multi-domain Computing Product Layout
- 5.1.2 Cross-domain Layout (Chip): Longying No.1
- 5.1.3 Cross-domain Layout (Chip): Longying No.1 VS. Qualcomm8155
- 5.1.4 Cross-domain Layout (Cockpit-driving Integration Computing Platform): Qualcomm SA8295P-based Pikes Platform
- 5.1.5 Cross-domain Layout (Cockpit-driving Integration Computing Platform): Longying No.1 and A1000-based ECARX Super Brain (1)
- 5.1.6 Cross-domain Layout (Cockpit-driving Integration Computing Platform): Longying No.1 and A1000-based ECARX Super Brain (2)
- 5.1.7 Cross-domain Layout(Cockpit-driving Integration Computing Platform): Qualcomm SA8255P -based Atlas Platform
- 5.1.8 Cross-domain Layout(Cockpit-driving Integration Computing Platform: Antora Series
- 5.1.9 Cross-domain Layout(Cockpit-driving Integration Computing Platform): SiEngine Longying No.1 based Antora 1000 (1)
- 5.1.10 Cross-domain Layout(Cockpit-driving Integration Computing Platform): SiEngine Longying No.1 based Antora 1000 (2)
- 5.1.11 Cross-domain Layout (Cockpit-driving Integration Computing Platform): SiEngine Longying No.1 based Antora 1000 Pro
- 5.1.12 Cross-domain Layout (Software): Cloudpeak Cross-domain Software Platform to mass produce Volvo EX30
- 5.1.13 Cross-domain Layout (Software): Cockpit-driving Integration Large Model Architecture
- 5.2 Neusoft Reach
- 5.2.1 Intelligent Cockpit Evolves to Multi-domain Computing
- 5.2.2 Multi-domain Computing Product Layout
- 5.2.3 Cross-domain Layout (Cockpit-driving Integration Computing Platform): SemiDrive X9CC-based X-Center 2.0
- 5.2.4 Cross-domain Layout (Cockpit-Body-Gateway Integration): Qualcomm 8295, NXP S32G-based C5 HMI Platform (1)
- 5.2.5 Cross-domain Layout (Cockpit-Body-Gateway Integration): Qualcomm 8295, NXP S32G-based C5 HMI Platform (2)
- 5.2.6 Cross-domain Layout (Cockpit-Body-Gateway Integration): Qualcomm 8295, NXP S32G-based C5 HMI Platform (3)
- 5.2.7 Cross-domain Layout (Software): Cross-domain Fusion Software Platform NeuSAR (1)
- 5.2.8 Cross-domain Layout (Software): Cross-domain Fusion Software Platform NeuSAR (2)
- 5.2.9 Cross-domain Layout (Software): Cross-domain Fusion Middleware NeuSAR SF (1)
- 5.2.10 Cross-domain Layout (Software): Cross-domain Fusion Middleware NeuSAR SF (2)
- 5.2.11 Cross-domain Layout (Software): Multi-domain Fusion Era-oriented openVOC Framework
- 5.2.12 Cross-domain Layout (Software): Software First Development Mode
- 5.3 Desay SV
- 5.3.1 Multi-domain Computing Product Layout
- 5.3.2 Multi-domain Computing Layout: Evolution to Central Computing Platform
- 5.3.3 Cross-domain Layout(Cockpit-driving Integration Computing Platform): Qualcomm SA8775 -based ICPS01E Central Computing Platform
- 5.3.4 Cross-domain Layout (Cockpit-driving Integration Computing Platform): 1st GEN ICP (Aurora)
- 5.3.5 Cross-domain Layout (Cockpit-driving Integration Computing Platform): Design Ideas of 1st GEN ICP (Aurora) (1)
- 5.3.6 Cross-domain Layout (Cockpit-driving Integration Computing Platform): Design Ideas of 1st GEN ICP (Aurora) (2)
- 5.3.7 Cross-domain Layout (Cockpit-driving Integration Computing Platform): Software Architecture of 1st GEN ICP (Aurora)
- 5.3.8 Cross-domain Layout (Cockpit-driving Fusion Computing Platform): Key Features of ICP (Aurora) Intelligent Computing Platform
- 5.3.9 Cross-domain Layout (Cockpit-driving Integration Computing Platform)" 1st GEN ICP (Aurora) Storage-Computing Integration
- 5.3.10 Cross-domain Layout (Cockpit-driving Integration Computing Platform):Qualcomm SA8295P-based G9PH
- 5.3.11 Joint with INVIDIA and HYPER to Promote Cockpit-driving Integration and Central Computing Platform
- 5.4 PATEO CONNECT+
- 5.4.1 Multi-domain Fusion Layout: Walking on Two Legs
- 5.4.2 Multi-domain Computing Product Layout
- 5.4.3 Cross-domain Layout (Central Computing Platform): Qualcomm 8295, Horizon J5-based CCM
- 5.4.4 Cross-domain Layout (Cockpit-driving Integration Computing Platform): Qualcomm SA8295P-based Cockpit-driving Integration Domain Control
- 5.4.5 Cross-domain Layout (Cockpit-driving Integration Computing Platform): Qualcomm 8155+Horizon J3-based Cockpit-Driving-Parking Integration Domain Control (1)
- 5.4.6 Cross-domain Layout (Cockpit-driving Integration Computing Platform): Qualcomm 8155+Horizon J3-based Cockpit-Driving-Parking Integration Domain Control (2)
- 5.5 UAES
- 5.5.1 Product Supply Model
- 5.5.2 Cross-domain Fusion: Application Service Innovation
- 5.5.3 Multi-domain Computing Product Layout
- 5.5.4 Cross-domain Layout:NXP S32G-based Computing Platform VCP 1.0
- 5.5.5 Cross-domain Layout:Next Generation Vehicle Motion Fusion Control Platform VCU8.6
- 5.5.6 Cross-domain Layout: Vehicle Motion Fusion Control Platform - VCU8.5 (1)
- 5.5.7 Cross-domain Layout: Vehicle Motion Fusion Control Platform - VCU8.5 (2)
- 5.5.8 Cross-domain Layout: Vehicle Motion Fusion Control Platform - VCU8.5 (3)
- 5.5.9 Cross-domain Layout: Vehicle Motion Fusion Control Platform - VCU8.5 (4)
- 5.5.10 Cross-domain Layout:VCU8.5 Four-wheel Drive Control Function Architecture
- 5.5.11 Cross-domain Layout:VCU8.5 Automatically Restore Drivable State after Reset
- 5.5.12 Cross-domain Layout:VCU8.5 Charging Control Software Architecture
- 5.5.13 Cross-domain Layout:VCU8.5 Thermal Management Requirements
- 5.6 Jingwei Hirain
- 5.6.1 Multi-domain Fusion Layout
- 5.6.2 Multi-domain Computing Product Layout
- 5.6.3 Cross-domain Layout (Central Computing Platform): NXP S32G based Central Computing Platform
- 5.6.4 Multi-domain Computing Products: SOA-based Vehicle Test
- 5.7 ThunderSoft
- 5.7.1 Multi-domain Fusion Layout: Plan Mass-production of Cockpit-driving Integrated Platforms in 2024
- 5.7.2 Multi-domain Fusion Layout:ThunderX Auto Develops from Driving-parking Integration to Cockpit-driving Integration
- 5.7.3 Multi-domain Computing Product Layout
- 5.7.4 Cross-domain Fusion Layout(Cockpit-driving Integration Platform)
- 5.7.5 Cross-domain Fusion Layout(Software): Central Computing Platform Software Architecture
- 5.7.6 Cross-domain Fusion Layout (Software): Qualcomm 8255-based Aqua Drive OS
- 5.7.7 Cross-domain Fusion Layout (Software): SOA Middleware Platform
- 5.8 EnjoyMove Technology
- 5.8.1 Multi-domain Computing Product Layout
- 5.8.2 Cross-domain Fusion Layout(Cockpit-driving Integration Computing Platform)
- 5.8.3 Cross-domain Fusion Layout (Software):EMOS Platform
- 5.8.7 Cross-domain Fusion Layout (Software):TSN Protocol Stack
- 5.8.8 7 Cross-domain Fusion Layout (Tool): Central Computing Development Kit
- 5.9 Autolink
- 5.9.1 Cross-domain Fusion Planning
- 5.9.2 Multi-domain Computing Product Layout
- 5.9.3 Cross-domain Layout(Cockpit-driving Integration Computing Platform)
- 5.10 Hangsheng Electronics
- 5.10.1 Multi-domain Computing Product Layout
- 5.10.2 Cross-domain Layout (Cockpit-driving Integration Computing Platform)
- 5.11 JoyNext
- 5.11.1 Multi-domain Computing Product Layout
- 5.11.2 Cross-domain Layout(Cockpit-driving Integration Computing Platform)
- 5.11.3 Cross-domain Layout (Software): Black Sesame C1200 Based CoreFusion Cockpit-driving Integration Software Open Platform
- 5.12 Nobo Automotive Technology
- 5.12.1 Multi-domain Computing Product Layout
- 5.12.2 Cross-domain Layout(Cockpit-driving Integration Computing Platform)
- 5.13 ADAYO
- 5.13.1 Multi-domain Computing Product Layout
- 5.13.2 Cross-domain Layout(Cockpit-driving Integration Computing Unit)
- 5.14 Yuanfeng Technology
- 5.14.1 Multi-domain Computing Product Layout
- 5.14.2 Cross-domain Layout
- 5.15 BDStar Intelligent & Connected Vehicle Technology (BICV)
- 5.15.1 Multi-domain Computing Product Layout
- 5.15.2 Cross-domain Layout
- 5.16 Megatronix
- 5.16.1 Multi-domain Computing Product Layout
- 5.16.2 Cross-domain Layout
- 5.17 ArcherMind Technology
- 5.17.1 Cross-domain Layout (Software): Vehicle Fusion OS
- 5.17.2 Cross-domain Layout (Software): Central Control Domain Software Platform FusionWise3.0
- 5.17.3 Cross-domain Layout (Software): Cross-domain Fusion Vehicle Software Computing Platform
- 5.18 Bebest
- 5.18.1 Cross-domain Layout(Intelligent Chassis Cross-domain): Build Complete Technology Solution
- 5.18.2 Cross-domain Layout(Intelligent Chassis Cross-domain): Cross-domain Fusion Integrated Chassis-by-Wire Architecture
- 5.19 Baidu
- 5.19.1 Cockpit-driving Integration Software-Chip Integrated Computing Platform
- 5.19.2 Vehicle OS Integrated Supply
6 Multi-domain Computing Technology Layout of Overseas Tier 1 Suppliers
- 6.1 Bosch
- 6.1.1 Multi-domain Fusion Computing Layout: Evolution to Cockpit-driving Integrated Platform
- 6.1.2 Multi-domain Fusion Computing Layout: R&D Route of Cockpit-driving Integrated Products (1)
- 6.1.3 Multi-domain Fusion Computing Layout: R&D Route of Cockpit-driving Integrated Products (2)
- 6.1.4 Multi-domain Computing Product Layout
- 6.1.5 Cross-domain Layout
- 6.2 Continental
- 6.2.1 Multi-domain Fusion Computing Layout: Evolve to Four-domain Integrated HPC
- 6.2.2 Multi-domain Computing Product Layout
- 6.2.3 Cross-domain Layout
- 6.3 ZF
- 6.3.1 Multi-domain Fusion Computing Layout
- 6.3.2 Cross-domain Layout
- 6.4 Aptiv
- 6.4.1 Multi-domain Computing Product Layout
- 6.4.2 Cross-domain Layout
- 6.4.8 Multi-domain Fusion Computing Products
- 6.5 Harman
- 6.5.1 Cross-domain Layout: Cockpit-driving Integration Development Plan
- 6.5.2 Cross-domain Layout: Launch Multi-domain Hybrid Architecture in 2024
- 6.5.3 Cross-domain Layout: Cockpit-driving Integration
- 6.5.4 Cross-domain Layout: Cockpit-driving Integrated Underlying Hardware Architecture
- 6.6 Visteon
- 6.6.1 Multi-domain Computing Product Layout
- 6.6.2 Cross-domain Layout
- 6.7 LG Electronics
- 6.7.1 Cross-domainLayout: Partner with Magna to Launch Cross-domain Platform
- 6.8 Forvia
- 6.8.1 Multi-domain Computing Product Layout
- 6.8.2 Cross-domain Layout: Cockpit-parking Integration Domain Control Integrated with Qualcomm 8295
