Autonomous Driving and Cockpit Domain Control Unit (DCU) Industry Report, 2022 (I)

Search by Type

Report DataBase News

Abstract

Selected Charts

Related Reports

Related Companies

Domain Controller Research: Exploration of Five Business Models, Tier1, Tier0.5, Tier1.5 or ODM?

Automakers accelerate the mass production of new E/E architecture platforms, and the penetration rate of domain controllers surges.

In addition to emerging carmakers that adopt new domain controller architectures from the start, conventional automakers have also stepped up the pace of using domain controllers in vehicles. Typical architectures include Geely Sustainable Experience Architecture (SEA), GAC Protoss Architecture, Great Wall E/E Platform (GEEP), BYD E3.0 Platform, and Volkswagen E3 Architecture. Through the lens of development planning, having achieved mass production of domain controller centralized architectures during 2021-2022, most OEMs will produce cross-domain fusion architectures in quantities between 2022 and 2023, and are expected to spawn centralized architectures from 2024 to 2025.

域控1_副本.png

As OEMs accelerate mass production of new E/E architectures, domain controllers will be a big beneficiary. Taking autonomous driving domain controllers as an example, our statistics show that in 2021, at least 33 OEMs had over 50 production vehicle models equipped with autonomous driving domain controller products, and the number of such production models will surge in 2022.

According to ResearchInChina, China shipped 539,000 autonomous driving domain controllers for passenger cars in 2021, with a penetration rate of 2.7%, a figure expected to exceed 5% in 2022. It is conceivable that in 2025, the annual shipments will reach 4.523 million sets, and the penetration rate will jumped to 18.7%; the key driver will be the soaring shipments of L2+ driving and parking integrated domain controllers.

域控2_副本.png

At present, more than 18 suppliers have launched over 20 L2+ driving and parking integrated domain controllers. In 2022, NOA is to be mounted on vehicles on large scale. Also the lightweight driving and parking integrated solutions using TI TDA4 and Horizon J3 chips have lowered 30% to 50% costs compared with the NVIDIA Xavier-driven solutions, helping "NOA+ automated parking" solutions to fully cover passenger cars priced between RMB100,000 and RMB200,000. The increasing number of passenger cars will support L2+ driving assistance functions such as ramp-to-ramp highway pilot, automated parking and home-AVP.

The L3/L4 high computing power domain controllers with built-in high computing power chips, e.g., NVIDIA ORIN-X, Horizon J5, Huawei Ascend 610, EyeQ6, Qualcomm Ride (8540+9000) and Renesas V3U, support high-precision sensors like LiDAR, 4D radar and multiple 8MP cameras, enabling intelligent driving in all highway, urban and parking scenarios. Currently, they are already in the early phase of small-batch shipments, and largely mounted on over RMB300,000 high-end models.

Explore domain controller business models, Tier1, Tier0.5, Tier1.5 or ODM.

Domain controller, as a core component for intelligent connected vehicle platforms, upwardly supports development of application software, and downwardly links E/E architecture and various system components. Its importance is beyond doubt. The competition in the domain controller market tends to be white-hot as multiple business models coexist.

Automakers are of course pleased to see the current competitive landscape. Their partnerships and collaborations with multiple suppliers help them build full-stack self-development capabilities. For automakers, this is also a process of trial and error so as to create a business development model that ultimately suits them.

In short, there are now mainly five domain controller design and production modes:

域控3_副本.png

Model 1: OEMs outsource domain controllers. This model is firstly introduced by Tesla, and then adopted by emerging carmakers like NIO and Xpeng Motors. Tesla designs domain controllers, and entrusts the production to Quanta Computer and Pegatron. NIO seeks support from Wistron and Flex. As well as the most basic hardware manufacture, ODMs/OEMs already begin to set foot in software engineering covering domain controller underlying basic software, and BSP driver.

Model 2: Tier 1 suppliers provide domain controller production for OEMs. It is the most common model of cooperation in current stage. Tier 1 suppliers adopt the white box or gray box model; OEMs have the authority to develop the application layer for autonomous driving or intelligent cockpit. Chip vendors, Tier 1 suppliers, and OEMs often form close partnerships. Chip vendors provide chips and develop software stacks and prototype design packages; Tier 1 suppliers provide domain controller hardware production, intermediate layers, and chip solution integration. Typical cooperation cases of this model include Desay SV + NVIDIA + Xpeng Motors/Li Auto/IM Motors, and ZEEKR + Mobileye + iMotion.

Model 3: Tier 1.5 suppliers born in the trend towards software and hardware separation concentrate their efforts on domain controller basic software platforms. Upwardly, they prop up OEMs to hold the independent development authority of systems, and downwardly integrate Tier 2 suppliers’ resources such as chips and sensors. As the originator of this mode, TTTech is currently valued at more than USD1 billion, and introduces key shareholders like Audi, Samsung Electronics, Infineon and Aptiv.

TTTech provides the MotionWise software platform that includes tools and middleware. Technomous co-funded by TTTech and DIAS Automotive Electronic Systems (a company under SAIC) is SAIC’s major supplier of autonomous driving domain controllers. In China, Neusoft Reach, EnjoyMove Technology, ArcherMind Technology, Megatronix Technology, ThunderSoft and the like all tend to enter the domain controller supply chain from software.

Meanwhile, Tier 1 suppliers are also playing the role of the Tier 1.5. For instance, in the field of cockpit domain controllers, Bosch which specializes in underlying cockpit software systems outsources hardware production and ecosystem construction to its partner, AutoLink. For Tier 1 suppliers, they are best able to follow the market development trend by providing a range of solutions such as software, hardware, and software and hardware integrated solutions.

Model 4: Tier 0.5 suppliers are born of OEMs’ needs for full-stack self-development capabilities. Tier 0.5 suppliers tightly bound with OEMs will partake in the whole process of OEMs from R&D, production and manufacture to even later data management and operation. There are three types of Tier 0.5 suppliers:

(1) Some OEMs spin off their parts and components division for independent operation. Examples include DIAS Automotive Electronic Systems under SAIC, Nobo Automotive Technology and Haomo AI under Great Wall Motor, and ECARX under Geely;

(2) Some OEMs seek partnerships with Tier 1 suppliers to establish joint ventures, for example, Anhui Domain Compute co-founded by Hongjing Drive and JAC, and FulScience Automotive Electronics, a joint venture of Desay SV, FAWER Automotive Parts and FAW.

(3) Chip vendors transform into Tier 0.5 suppliers. In the context of chip shortage, chip vendors have a bigger say, and even OEMs have to bypass Tier 1 suppliers to purchase directly from them. Chip vendors no longer feel fulfilled in the role as Tier 2 suppliers, and are trying to develop a strong bond with OEMs. Chip vendors participate in OEMs’ vehicle model development at the very beginning. For example, Mobileye and Geely built strategic cooperation; after acquiring Veoneer, Qualcomm will work harder to roll out autonomous driving and cockpit cross-domain fusion computing platforms; NVIDIA DRIVE Hyperion 8.1 platform is compatible with both autonomous driving and cockpit, and the chip vendor even attempts to join hands with OEMs on an autonomous driving business profit sharing model.

Model 5: system integrators outsource domain controllers to ODMs/OEMs, especially providers of autonomous driving system solutions and intelligent cockpit software platforms. For instance, Baidu’s ACU is produced by Flex, and Haomo AI also cooperates with Flex. Even many autonomous driving start-ups may adopt this model, that is, with ODMs/OEMs providing the automotive OEM hardware production capacity supplement, they supply complete "domain controller + ADAS integrated development" solutions to OEMs, aiming to be better able to compete with conventional Tier 1 suppliers.

In the age of software-defined vehicles, full-stack software system solutions will be the key to gaining competitive edges for domain controller providers.

In general, we believe that against a background of software and hardware separation, the full-stack software system development capabilities will play a key part in the future contest. For domain controller providers, the key to gaining competitive edges is the continuous efforts to enrich and build underlying platforms (software-defined hardware, data services, information security, operating systems, etc.), middle-layer platforms (middleware, AutoSAR, chip adaptation, etc.), and application-layer platforms (human-machine interaction (HMI), algorithms, software stack, etc.).

域控4_副本.png

In terms of intelligent cockpit, in PATEO CONNECT+’s case, the company has five core technology platforms: Operating System, Intelligent Voice, Hardware, Map, and Cloud Platform. Based on SOA and software-defined vehicles, PATEO CONNECT+ provides software application development and operation for users in intelligent cockpit, intelligent driving, and body control domain.

The in-depth cooperation with large automakers such as FAW, Dongfeng Motor, BAIC, Geely and SAIC-GM-Wuling allows PATEO to rapidly expand its intelligent cockpit division based on its telematics business. Its solutions from domain controllers and operating systems to hardware, software and cloud three-end intelligent cockpit integrated solutions help automakers create personalized driving experience for users.

At the hardware end, PATEO’s intelligent cockpit domain controller hardware platforms cover Qualcomm 8295/8155, NXP i.MX8QM, MTK8666, and homemade X9H, among others. Its products are led by:

In April 2020, PATEO's i.MX8QM-based intelligent cockpit product was first mounted on production model BEIJING X7. The use of hardware isolation technology supports operation of Linux + Android dual operating systems on the same hardware.

In April 2022, PATEO Qinggan 8155 platform fitted on Voyah Dreamer was launched on market. This platform with QNX Hypervisor technology allows operation of QNX + Android dual operating systems on the same hardware. In June, the platform became available to NETA U, NETA Auto’s new flagship model. It enables the perfect integration of dashboard and entertainment system, and thus cuts much of the hardware and software cost of intelligent cockpit domain controllers.

PATEO CONNECT+ is designing and developing the next-generation Qualcomm 8295-based intelligent cockpit platform with higher levels of domain controller integration. The 8295 chip that supports three-domain fusion will favor a sharp reduction in the cost of the cockpit. Compared with the conventional modes of multiple domain controllers and multiple wire harnesses, the three-domain hardware integration based on the 8295 automotive chip platform takes on integrated control over multiple units such as streaming rearview mirror, central display, air conditioner, and lamps. This mode will save the cost of quite a few domain controllers and intelligent component control units. With this mode, PATEO will derive diverse lower-cost solutions from Qinggan 8295-based cockpit when cooperating with different partners, assisting automakers in slashing their cost. PATEO will expand cooperation and develop solutions in such fields as vehicle intelligence, intelligent vehicle connectivity, SOA, cockpit integration, and central controller-based multi-domain fusion. This new cockpit platform is expected to be rolled out on market with related vehicle models in 2023, providing leading immersive intelligent driving experience for automotive industry.

At the software end, with long-term efforts to develop intelligent cockpit domain controllers from cloud platform to terminal platform, PATEO has built end-to-end design and development capabilities. The cloud end involves technical solution platforms such as CP access, account management, data management, and FOTA. The terminal design and development range from cockpit operating systems to HMI.

域控5_副本.png

As for autonomous driving, taking Neusoft Reach as an example, it boasts the following autonomous driving domain controller products:

Neusoft Reach's new-generation central computing platform for autonomous driving based on Horizon Journey?5 chip supports the access to multi-channel LiDARs, 16-channel high-definition cameras, radars and ultrasonic radars, enabling 360° perception redundancy for the whole vehicle. The platform provides L3/L4 autonomous driving functions on the basis of open SOA, and NeuSAR, the basic software self-developed by Neusoft Reach;

Neusoft Reach’s driving and parking integrated domain controller for autonomous driving enables the access to 5-10 channels of high-definition cameras, 5-channel radars, and 12-channel ultrasonic radars, of which the cameras deliver up to 8 megapixels. The integration of parking and driving functions and sensor sharing render the enhanced perception capability for L2+ autonomous driving. Through the preset basic software and the autonomous driving-specific middleware, the SOA-based software architecture provides developers with a range of development tools;

Neusoft Reach’s X-Box3.0 domain controller enables mass production and application of L0-L3 autonomous driving for multiple scenarios, including multiple function combinations such as interior/exterior scenario, L2-L3 driving scenario, and L3+ parking scenario. This intelligent driving controller has been designated for several production models, and will be mass-produced and put on market in 2022.

In April 2022, Neusoft Reach introduced a software development platform for domain controllers - NeuSAR DS (Domain System). As a complete underlying software development platform, verification system and tool chain for domain controllers (central domain, cockpit domain and intelligent driving domain), NeuSAR DS is designed for OEMs and offers all general software functions between hardware and application layers. The platform provides a wealth of software development and debugging tools, virtualization validation systems, integrated systems, environment deployment services (e.g., IDE), commercial POSIX OS, and third-party OS integration, as well as chip BSP and secure boot solutions.

1 Evolution of Automotive Electronic and Electrical Architecture (EEA)
1.1 Four Dimensions of Automotive EEA Upgrade: Software Architecture, Hardware Architecture, Communication Architecture, and Power Architecture
1.2 Domain Integration Platform and Vehicle Computing Platform in the Evolution of Automotive EEA
1.3 Evolution of Automotive EEA in the Next Decade
1.4 OEMs Accelerate EEA Upgrade and Mass Production (1)
1.5 OEMs Accelerate EEA Upgrade and Mass Production (2)
1.6 New-generation EEA and Domain Controller Layout of OEMs (1)
1.7 New-generation EEA and Domain Controller Layout of OEMs (2)
1.8 New-generation EEA and Domain Controller Layout of OEMs (3)
1.9 New-generation EEA and Domain Controller Layout of OEMs (4)

2 Evolution of Domain Controller Software and Hardware Architectures and Business Models
2.1 Domain Controller Hardware Design
2.1.1 Domain Controller Hardware Architecture
2.1.2 Hardware Architecture Upgrade: ECU Hardware Architecture Upgrade
2.1.3 Communication Architecture Upgrade: Vehicle Backbone Network Evolves to Ethernet
2.1.4 Power Architecture Upgrade: The Power Topology Is Getting More Complex
2.1.5 Challenges in Domain Controller Hardware Design: Power Integrity (PI)
2.1.6 Challenges in Domain Controller Hardware Design: Signal Integrity (SI)
2.1.7 Challenges in Domain Controller Hardware Design: EMC
2.1.8 Challenges in Domain Controller Hardware Design: Power Consumption and Heat Dissipation
2.1.9 Challenges in Domain Controller Hardware Design: Designed Service Life
2.1.10 Challenges in Domain Controller Hardware Design: Testing and Verification
2.1.11 Challenges in Domain Controller Hardware Design: Higher Requirements for Process
2.2 Domain Controller Software Design
2.2.1 Domain Controller Software Architecture
2.2.2 Domain Controller Software Architecture Upgrade: Software Architecture Is Upgraded to Adaptive AutoSAR
2.2.3 "Full-stack Self-development" System Frameworks of OEMs and Tier 1 Suppliers (1)
2.2.4 "Full-stack Self-development" System Frameworks of OEMs and Tier 1 Suppliers (2)
2.2.5 "Full-stack Self-development" Cases of OEMs and Tier 1 Suppliers (1)
2.2.6 "Full-stack Self-development" Cases of OEMs and Tier 1 Suppliers (2)
2.3 Domain Controller Design and Production Models
2.3.1 Domain Controller Design and Production: Five Procurement Models (1)
2.3.2 Domain Controller Design and Production: Five Procurement Models (2)
2.3.3 Domain Controller Design and Production: Five Procurement Models (3)
2.3.4 Domain Controller Design and Production: Three Cooperative Development Models
2.3.5 Domain Controller Design and Production: Three Profit Sharing Models
2.4 Domain Controller ODM/OEM Production Model
2.4.1 Domain Controller ODM/OEM Production Model: Mode of Cooperation
2.4.2 Domain Controller ODM/OEM Production Model: Core Players
2.4.3 Domain Controller ODM/OEM Production Model: Typical Cooperation Cases

3 Research on Autonomous Driving Domain Controller Technology and Market
3.1 Evolution of Autonomous Driving and Domain Controller
3.1.1 Evolution Route of Autonomous Driving
3.1.2 Relationship between Autonomous Driving Domain Controllers and Automated Driving Levels
3.1.3 Phase 1: L0-L2 ADAS Distributed System Solutions
3.1.4 Phase 2: L2+ Domain Centralized Driving and Parking Integrated System Solutions - 5V5R
3.1.5 Phase 2: L2+ Domain Centralized Driving and Parking Integrated System Solutions - 5R12V or 5R11V
3.1.6 Phase 3: L3-L4 Domain Centralized System Solutions (All-scenario Full Self-Driving (FSD))
3.2 L2+ Driving and Parking Integrated Domain Controller Solutions
3.2.1 L2+ Driving and Parking Integrated Domain Controller Solutions
3.2.2 Benchmarking of L2+ Driving and Parking Integrated Systems and Domain Controller Products (1)
3.2.3 Benchmarking of L2+ Driving and Parking Integrated Systems and Domain Controller Products (2)
3.2.4 Benchmarking of L2+ Driving and Parking Integrated Systems and Domain Controller Products (3)
3.2.5 Benchmarking of L2+ Driving and Parking Integrated Systems and Domain Controller Products (4)
3.2.6 Benchmarking of L2+ Driving and Parking Integrated Systems and Domain Controller Products (5)
3.2.7 Benchmarking of L2+ Driving and Parking Integrated Systems and Domain Controller Products (6)
3.3 L3/L4 Autonomous Driving Domain Controller Solutions
3.3.1 Benchmarking of L3/L4 Autonomous Driving Domain Controller Solutions and Domain Controller Products (1)
3.3.2 Benchmarking of L3/L4 Autonomous Driving Domain Controller Solutions and Domain Controller Products (2)
3.3.3 Benchmarking of L3/L4 Autonomous Driving Domain Controller Solutions and Domain Controller Products (3)
3.3.4 Benchmarking of L3/L4 Autonomous Driving Domain Controller Solutions and Domain Controller Products (4)
3.3.5 Benchmarking of L3/L4 Autonomous Driving Domain Controller Solutions and Domain Controller Products (5)
3.3.6 Redundancy Policies for L3/L4 Autonomous Driving Domain Controllers (1): AURIX + TTTech Motionwise
3.3.7 Redundancy Policies for L3/L4 Autonomous Driving Domain Controllers (2): Dual-System Hybrid Architecture Solution
3.3.8 Redundancy Policies for L3/L4 Autonomous Driving Domain Controllers (3): Multi-Level Security Paths
3.4 Autonomous Driving Domain Controller Software and Hardware Solutions of OEMs
3.4.1 Summary of Autonomous Driving Domain Controller Configurations and Suppliers of 33 OEMs (1)
3.4.2 Summary of Autonomous Driving Domain Controller Configurations and Suppliers of 33 OEMs (2)
3.4.3 Summary of Autonomous Driving Domain Controller Configurations and Suppliers of 33 OEMs (3)
3.4.4 Summary of Autonomous Driving Domain Controller Configurations and Suppliers of 33 OEMs (4)
3.4.5 Summary of Autonomous Driving Domain Controller Configurations and Suppliers of 33 OEMs (5)
3.4.6 Summary of Autonomous Driving Domain Controller Configurations and Suppliers of 33 OEMs (6)
3.4.7 Summary of Autonomous Driving Domain Controller Configurations and Suppliers of 33 OEMs (7)
3.4.8 Summary of Autonomous Driving Domain Controller Configurations and Suppliers of 33 OEMs (8)
3.4.9 Summary of Autonomous Driving Domain Controller Configurations and Suppliers of 33 OEMs (9)
3.5 Autonomous Driving Domain Controller Solutions of Tier 1 Suppliers
3.5.1 Summary of Autonomous Driving Domain Controller Solutions of 28 Tier 1 Suppliers (1)
3.5.2 Summary of Autonomous Driving Domain Controller Solutions of 28 Tier 1 Suppliers (2)
3.5.3 Summary of Autonomous Driving Domain Controller Solutions of 28 Tier 1 Suppliers (3)
3.5.4 Summary of Autonomous Driving Domain Controller Solutions of 28 Tier 1 Suppliers (4)
3.5.5 Summary of Autonomous Driving Domain Controller Solutions of 28 Tier 1 Suppliers (5)
3.5.6 Summary of Autonomous Driving Domain Controller Solutions of 28 Tier 1 Suppliers (6)
3.5.7 Summary of Autonomous Driving Domain Controller Solutions of 28 Tier 1 Suppliers (7)
3.5.8 Summary of Autonomous Driving Domain Controller Solutions of 28 Tier 1 Suppliers (8)
3.6 Solutions of Autonomous Driving Domain Controller Software Suppliers
3.6.1 Tier 1.5 Suppliers (Domain Controller Middleware OS) and New Development Models in Computing Infrastructure Platform Will Appear
3.6.2 Middleware Is the Key to Future Software Value Growth
3.6.3 Application of Autonomous Driving Domain Controller Middleware
3.6.4 Solutions of Autonomous Driving Domain Controller Middleware Suppliers
3.6.5 Software Stack Solutions of Autonomous Driving SoC Vendors (1)
3.6.6 Software Stack Solutions of Autonomous Driving SoC Vendors (2)
3.7 Autonomous Driving Domain Controller SoC Solutions
3.7.1 Comparison of Product Performance Parameters between 14 Autonomous Driving Domain Controller SoC Vendors (1)
3.7.2 Comparison of Product Performance Parameters between 14 Autonomous Driving Domain Controller SoC Vendors (2)
3.7.3 Comparison of Product Performance Parameters between 14 Autonomous Driving Domain Controller SoC Vendors (3)
3.7.4 Comparison of Product Performance Parameters between 14 Autonomous Driving Domain Controller SoC Vendors (4)
3.7.5 Comparison of Product Performance Parameters between 14 Autonomous Driving Domain Controller SoC Vendors (5)
3.7.6 Comparison of Product Performance Parameters between 14 Autonomous Driving Domain Controller SoC Vendors (6)
3.7.7 Comparison of Product Performance Parameters between 14 Autonomous Driving Domain Controller SoC Vendors (7)
3.7.8 Comparison of Product Performance Parameters between 14 Autonomous Driving Domain Controller SoC Vendors (8)
3.7.9 Comparison of Product Performance Parameters between 14 Autonomous Driving Domain Controller SoC Vendors (9)
3.8 Autonomous Driving Domain Controller Technology Benchmarking
3.8.1 Technology Benchmarking of Autonomous Driving Domain Controller Products (1)
3.8.2 Technology Benchmarking of Autonomous Driving Domain Controller Products (2)
3.8.3 Technology Benchmarking of Autonomous Driving Domain Controller Products (3)
3.8.4 Technology Benchmarking of Autonomous Driving Domain Controller Products (4)
3.9 Autonomous Driving Domain Controller End Markets: Passenger Cars
3.9.1 Penetration Rate of Autonomous Driving in Passenger Cars in China, 2021-2025E
3.9.2 Shipments of Autonomous Driving Domain Controllers for Passenger Cars in China, 2021-2025E
3.9.3 China’s Passenger Car Autonomous Driving Domain Controller Market Size, 2021-2025E
3.9.4 Cost Prices of Autonomous Driving Domain Controllers: Prices of Products by Target Market
3.9.5 Competitive Landscape of Autonomous Driving Domain Controller Market: Estimated Market Shares of Vendors in 2021
3.9.6 Competitive Landscape of Autonomous Driving Domain Controller Market: Roles Four-Party Players Pursue
3.10 Autonomous Driving Domain Controller End Markets: Commercial Vehicles
3.10.1 Application of Domain Controllers in the End Market: China’s L3/L4 Commercial Vehicle Market
3.10.2 Application of Domain Controllers in the End Market: Commercial Vehicle Domain Controller Solutions
3.11 Autonomous Driving Domain Controller End Markets: Autonomous Delivery Vehicles
3.11.1 Application of Domain Controllers in the End Market: China’s Autonomous Delivery Vehicle Market (1)
3.11.2 Application of Domain Controllers in the End Market: China’s Autonomous Delivery Vehicle Market (2)
3.11.3 Application of Domain Controllers in the End Market: Autonomous Delivery Vehicle Domain Controller Solutions

5 Foreign Domain Controller Suppliers
5.1 Bosch
5.1.1 Established the Cross-Domain Computing Solutions Division (XC Division)
5.1.2 Structure and Presence of XC Division in China
5.1.3 Further Integrated ETAS Software Business
5.1.4 Cockpit Domain Controllers: Product Development Trends
5.1.5 Cockpit Domain Controller Platform: Autosee 2.0
5.1.6 Cockpit Domain Controller Platform: System Architecture of Autosee 2.0
5.1.7 Domain Controllers: Technical Solutions and Advantages (1)
5.1.8 Domain Controllers: Technical Solutions and Advantages (2)
5.1.9 Cockpit Domain Controller Platform: Innovations and Advantages
5.1.10 Cockpit Domain Controller Platform: Jointly Developed with Autolink
5.1.11 Intelligent Cockpit Cross-Domain Fusion: System Architecture of Fusion Control Products (1)
5.1.12 Intelligent Cockpit Cross-Domain Fusion: System Architecture of Fusion Control Products (2)
5.1.13 Intelligent Cockpit Cross-Domain Fusion: System Architecture Roadmap of Fusion Control Products
5.1.14 Autonomous Driving Domain Controllers: Product Development Trends
5.1.15 Autonomous Driving Domain Controllers: DASy Technology Evolution
5.1.16 Autonomous Driving Domain Controllers: L1-L4 Development Planning
5.1.17 Autonomous Driving Domain Controllers: Computing Power Development Planning
5.1.18 Autonomous Driving Middleware: Iceoryx
5.2 Visteon
5.2.1 Development Planning for Cockpit Electronics and Autonomous Driving (1)
5.2.2 Development Planning for Cockpit Electronics and Autonomous Driving (2)
5.2.3 Cockpit Domain Controllers: Development Trends
5.2.4 4th Generation SmartCore Cockpit Domain Controller
5.2.5 3rd Generation SmartCore Cockpit Domain Controller
5.2.6 SmartCore Cockpit Domain Controllers (1)
5.2.7 SmartCore Cockpit Domain Controllers (2)
5.2.8 SmartCore Cockpit Domain Controllers (3)
5.2.9 Typical Customer Groups of SmartCore
5.2.10 Autonomous Driving Domain Controllers: DriveCore Technology Upgraded in 2021
5.2.11 Autonomous Driving Domain Controllers: Advantages of DriveCore
5.2.12 Autonomous Driving Domain Controllers: Architecture of DriveCore
5.2.13 Autonomous Driving Domain Controllers: DriveCore Development Tools
5.3 Continental
5.3.1 Development Plan of Vehicle Computing Business Unit (HPC) (1)
5.3.2 Development Plan of Vehicle Computing Business Unit (HPC) (2)
5.3.3 Development Plan of Vehicle Computing Business Unit (HPC) (3)
5.3.4 SOP Timeline of High Performance Computers (HPC) in Different Domains
5.3.5 Software Platform for Next-Generation Automotive Electronics Architectures: EB xelor
5.3.6 Cockpit HPC: Development Trends of Cockpit Domain Products
5.3.7 Cockpit HPC: Integrated Interior Platform (IIP)
5.3.8 Cockpit HPC: Architecture with Software and Hardware Separation
5.3.9 Cockpit HPC: Providing Cockpit Domain Controller Products for BMW iX BEV
5.3.10 Autonomous Driving HPC: ADCU Computing Platform
5.3.11 Autonomous Driving HPC: AI Chip Layout
5.4 Veoneer
5.4.1 Qualcomm Acquired Veoneer for USD4.5 Billion: Using Arriver Vision Software Stack
5.4.2 The Cooperation between Qualcomm and Veoneer Started in 2021
5.4.3 Autonomous Driving Product Line Layout
5.4.4 Active Safety Platform Architecture
5.4.5 L2+ Hands-off System
5.4.6 ADAS SW (Software) Stack Roadmap: ASP1.0-ASP3.X
5.4.7 Mercedes-Benz L3 Autonomous Vehicles Carried Veoneer’s Stereo Vision Perception Solutions
5.4.8 ADAS ECU Products
5.4.9 ADAS/AD ECU: Zeus Computing Platform
5.4.10 ADAS/AD ECU: Functional Architecture
5.5 ZF
5.5.1 New Corporate Strategy: "See, Think, Act"
5.5.2 Autonomous Driving Domain Controllers: Product Development Trends
5.5.3 Autonomous Driving Domain Controllers: New Generation ProAI Architecture
5.5.4 Autonomous Driving Domain Controllers: 3rd Generation ProAI
5.5.5 coASSIST Level 2+ Automated Driving System Developed in Cooperation with Mobileye
5.5.6 Autonomous Driving Domain Controllers: Core Customers
5.5.7 Domain Controller Basic Software: Established a Global Software Center
5.5.8 Domain Controller Basic Software: Cooperated with KPIT
5.6 Aptiv
5.6.1 Aptiv’s Smart Vehicle Architecture (SVA)
5.6.2 Aptiv’s SVA(TM) Topology
5.6.3 Aptiv Acquired Wind River: To Promote Cockpit, Autonomous Driving and Domain Controller Businesses
5.6.4 Wind River VxWorks Microkernel Architecture (1)
5.6.5 Wind River VxWorks Microkernel Architecture (2)
5.6.6 Aptiv’s Intelligent Cockpit Controllers: Development Progress
5.6.7 Aptiv’s Integrated Cockpit Controllers (ICC): Features and Customers
5.6.8 Aptiv’s Integrated Cockpit Controllers (ICC): Development Plan
5.6.9 Aptiv’s Integrated Cockpit Controllers (ICC): System Architecture
5.6.10 Aptiv’s Integrated Cockpit Controllers (ICC): Application of In-cabin Sensing Platform
5.6.11 Aptiv’s Integrated Cockpit Controllers (ICC): Product Planning and Technology Roadmap
5.6.12 Aptiv’s Autonomous Driving Controllers: Development Progress
5.6.13 Aptiv’s Ultra PAD Autonomous Driving Domain Controller
5.6.14 BMW's EEA and Autonomous Driving Solutions
5.6.15 Aptiv's New-Generation ADAS Platform: A Satellite Architecture Platform for Autonomous Driving
5.6.16 Aptiv's New-Generation ADAS Platform: Three Levels of Configurations
5.6.17 Aptiv's New-Generation ADAS Platform: Supporting Multiple SVA Design Principles
5.6.18 Aptiv's New-Generation ADAS Platform: Software and Hardware Composition and Technical Characteristics (1)
5.6.19 Aptiv's New-Generation ADAS Platform: Software and Hardware Composition and Technical Characteristics (2)
5.6.20 Aptiv's New-Generation ADAS Platform: Software and Hardware Composition and Technical Characteristics (3)
5.7 Denso
5.7.1 Cockpit Control Unit (CCU): Product Development Trends
5.7.2 KOTEI Cockpit Domain Controller: Cooperated with SemiDrive Technology
5.7.3 Cockpit Control Unit (CCU): Application Cases (Subaru)
5.7.4 Cockpit Control Unit (CCU): Application Cases (Subaru)
5.7.5 Intelligent Cockpit Design: Technology Roadmap
5.7.6 Intelligent Cockpit Design: Integrated Control of Cockpit Systems
5.7.7 Intelligent Cockpit Design: Cockpit Integrated Control System Based on Virtualization Technology
5.7.8 Intelligent Cockpit Design: Service Oriented Architecture (SOA) Development
5.7.9 ADAS/AD Technology Framework
5.8 Faurecia Clarion
5.8.1 The Four Business Groups Focus on the Two Technology Strategies: The Cockpit of The Future and Sustainable Mobility
5.8.2 Acquired a Controlling 60% Stake in HELLA
5.8.3 The Merger with HELLA Will Empower Faurecia’s Driving Assistance Business
5.8.4 Cockpit Computing Platform: Development Trends of Cockpit Domain Products
5.8.5 Cockpit Intelligence Platform (CIP): Single-Processor Multi-Screen Integrated System
5.8.6 Cockpit Domain Controllers: Evolving and Integrating More Features
5.8.7 Cockpit Domain Controllers: Building Multi-screen Integrated Cockpit Systems
5.8.8 Cockpit Domain Controllers: Planning and Objectives
5.8.9 Cockpit Domain Controllers: Chip Partners (Horizon Robotics, Allwinner and Renesas)
5.8.10 Cockpit Domain Controllers: Hongqi H9 Intelligent Cockpit in Cooperation with FAW Hongqi
5.9 Panasonic
5.9.1 Cockpit SPYDR: Development Trends of Cockpit Controllers
5.9.2 Cockpit Domain Controller Solutions: SPYDR 2.0 and SPYDR 3.0
5.9.3 Cockpit Domain Controller Solutions: Key Features of SPYDR 2.0 and SPYDR 3.0
5.9.4 Cockpit Electronics Layout
5.9.5 Cockpit Electronics Computing Architecture
5.9.6 Cockpit System Software Architecture
5.9.7 Cockpit System Software Architecture: COQOS Software Operating System
5.9.8 Cockpit Domain Controller Chip: Sociconext Plans to Launch 5nm Automotive SOC
5.10 Harman
5.10.1 Profile
5.10.2 Digital Cockpit Product Lines
5.10.3 Vision of Next-Generation EEA: Harman Proposes A Modular and Combinable Mode of Cooperation in Cockpits
5.10.4 Vision of Next-Generation EEA: Multi-Domain Hybrid Architecture
5.10.5 Vision of Next-Generation EEA: Hardware Architecture
5.10.6 Vision of Next-Generation EEA: Software Architecture
5.10.7 Cockpit Domain Controllers: Technical Solutions
5.10.8 Cockpit Domain Controllers: Platform Solutions
5.10.9 Cockpit Domain Controllers: Application Case - ARCFOX αT
5.10.10 Intelligent Cockpit Platform: to Develop An Intelligent Cockpit Platform for Volkswagen ICAS 3.1
5.10.11 Multi-Domain Fusion Planning: Cockpit Platform Pre-integrates ADAS Functions
5.10.12 Multi-Domain Fusion Planning: Development Planning for Cockpit Platform and ADAS Function Integration
5.10.13 Multi-Domain Fusion Planning: Underlying Hardware Architecture of Cockpit Platform (1)
5.10.14 Multi-Domain Fusion Planning: Underlying Hardware Architecture of Cockpit Platform (2)
5.11 LG Electronics
5.11.1 Cockpit Controllers: Development Progress
5.11.2 Entertainment Domain Controllers: ICAS3
5.11.3 Volkswagen ID.3/ID.4 E3 Electronic Architecture
5.11.4 Entertainment Domain Controllers: ICAS3 (1)
5.11.5 Entertainment Domain Controllers: ICAS3 (2)
5.11.6 Entertainment Domain Controllers: ICAS3 (3)
5.11.7 LG Works to Build WebOS-based Automotive Platform Solutions
5.11.8 Development of Linux WebOS Platform
5.11.9 LG Electronics Joined ACRN (Hypervisor)
5.12 Tesla
5.12.1 Evolution of Autopilot System and Processors
5.12.2 Autopilot Hardware Development Route
5.12.3 Tesla Plans to Outsource the Production of HW 4.0 Autonomous Driving Chip to Samsung
5.12.4 Autopilot Function Upgrade Path: HW 1.0—HW 3.0 (1)
5.12.5 Autopilot Function Upgrade Path: HW 1.0—HW 3.0 (2)
5.12.6 Domain Controller AutoPilot 3.0: Features
5.12.7 Domain Controller AutoPilot 2.5: Features (1)
5.12.8 Domain Controller AutoPilot 2.5: Features (2)
5.12.9 Domain Controller AutoPilot 2.0: Features (1)
5.12.10 Domain Controller AutoPilot 2.0: Features (2)
5.13 Marelli
5.13.1 Marelli Automotive Electronics Set up China R&D Center
5.13.2 Marelli and BlackBerry Enhanced Their Partnership on QNX Neutrino Real Time Operating System (RTOS)
5.13.3 Marelli and GAC Enhanced Their Partnership on Cockpit Domain Controller Development
5.13.4 Intelligent Cockpit Domain Controllers
5.14 TTTech
5.14.1 Profile
5.14.2 Next Business Strategic Directions
5.14.3 Autonomous Driving Solutions
5.14.4 Technical Advantages of Autonomous Driving Controller Platform
5.14.5 Autonomous Driving Security Software Platform: MotionWise
5.14.6 Autonomous Driving Security Software Platform: MotionWise
5.14.7 TTTech MotionWise “Low-Cost Redundancy” Strategy in Cooperation with Infineon (1)
5.14.8 TTTech MotionWise “Low-Cost Redundancy” Strategy in Cooperation with Infineon (2)
5.14.9 TTTech Cooperated with SAIC: To Develop the Intelligent Driving Central Controller (iECU) for Intelligent Driving

Global and China Passenger Car T-Box Market Report, 2023

T-Box industry research: the market will be worth RMB10 billion and the integration trend is increasingly clear. ResearchInChina released "Global and China Passenger Car T-Box Market Report, 2023", w...

Analysis Report on Auto Shanghai 2023

Analysis on 75 Trends at Auto Shanghai 2023: Unprecedented Prosperity of Intelligent Cockpits and Intelligent Driving Ecology After analyzing the intelligent innovation trends at the Auto Shanghai 20...

Chinese Emerging Carmakers’ Telematics System and Entertainment Ecosystem Research Report, 2022-2023

Telematics service research (III): emerging carmakers work on UI design, interaction, and entertainment ecosystem to improve user cockpit experience. ResearchInChina released Chinese Emerging Carmake...

China Passenger Car Cockpit-Parking Industry Report, 2023

Cockpit-parking integration research: cockpit-parking vs. driving-parking, which one is the optimal solution for cockpit-driving integration?Cockpit-parking vs. driving-parking, which one is the optim...

Automotive Sensor Chip Industry Report, 2023

Sensor chip industry research: driven by the "more weight on perception" route, sensor chips are entering a new stage of rapid iterative evolution. At the Auto Shanghai 2023, "more weight on percepti...

Automotive Electronics OEM/ODM/EMS Industry Report, 2023

Automotive electronics OEM/ODM/EMS research: amid the disruption in the division of labor mode in the supply chain, which auto parts will be covered by OEM/ODM/EMS mode? Consumer electronic manu...

China Automotive Smart Glass Research Report, 2023

Smart glass research: the automotive smart dimming canopy market valued at RMB127 million in 2022 has a promising future.Smart dimming glass is a new type of special optoelectronic glass formed by com...

Automotive Ultrasonic Radar and OEM Parking Roadmap Development Research Report, 2023

Automotive Ultrasonic Radar Research: as a single vehicle is expected to carry 7 units in 2025, ultrasonic radars will evolve to the second generation. As a single vehicle is expec...

Autonomous Driving SoC Research Report, 2023

Research on autonomous driving SoC: driving-parking integration boosts the industry, and computing in memory (CIM) and chiplet bring technological disruption. “Autonomous Driving SoC Research ...

China ADAS Redundant System Strategy Research Report, 2023

Redundant System Research: The Last Line of Safety for Intelligent VehiclesRedundant design refers to a technology adding more than one set of functional channels, components or parts that enable the ...

Intelligent Steering Key Components Report, 2023

Research on intelligent steering key components: four development trends of intelligent steering The automotive chassis consists of four major systems: transmission system, steering system, driving ...

Automotive Digital Instrument Cluster Operating System Report, 2023

Digital Instrument Cluster Operating System Report: QNX commanded 71% of the Chinese intelligent vehicle cluster operating system market. Amid the trend for the integration of digital cluster and cen...

800V High Voltage Platform Research Report, 2023

How to realize the commercialization of 800V will play a crucial part in the strategy of OEMs. As new energy vehicles and battery technology boom, charging and battery swapping in the new energy vehi...

Automotive Intelligent Cockpit Platform Research Report, 2023

Intelligent cockpit platform research: the boundaries between vehicles and PCs are blurring, and there are several feasible paths for cockpit platforms. Automotive Intelligent Cockpit Platform Resea...

Global and China Automotive Wireless Communication Module Industry Report，2023

Vehicle communication module research: 5G R16+C-V2X module, smart SiP module and other new products spring up. In 2022, 4G modules swept 84.3% of the vehicle communication module market....

Intelligent Vehicle Cockpit-Driving Integration Research Report, 2023

Cockpit-Driving Integration Research: many companies are making layout and may implement it during 2024-2025. 1. What is the real cockpit-driving integration? At present, automotive electroni...

Chinese Joint Venture OEMs' Telematics System and Entertainment Ecosystem Research Report, 2022

Telematics System Research 2: Baidu Family Bucket, Huawei and Tencent Become the Mainstream Ecosystems ResearchInChina released Chinese Joint Venture OEMs' Telematics System and Entertainment Ecosyst...

China Automotive Digital Key Research Report, 2023

Automotive Digital Key Research: the pace of mobile phones replacing physical keys quickens amid the booming market "China Automotive Digital Key Research Report, 2023" released by ResearchInChina co...

Abstract

Table of Contents

Selected Charts

Related Reports

Related Companies