Domain services

Autonomous driving and cockpit domain control unit in China

Dublin, Sept. 05, 2022 (GLOBE NEWSWIRE) — The “Autonomous Driving Domain and Cockpit Control Unit (DCU) Industry Report, 2022 (I)” report has been added to from offer.

There are now mainly five modes of designing and producing domain controllers

Model 1: OEMs outsource domain controllers. This model is first introduced by Tesla, then adopted by emerging automakers like NIO and Xpeng Motors. Tesla designs domain controllers, and entrusts production to Quanta Computer and Pegatron. NIO seeks support from Wistron and Flex. In addition to the most basic hardware manufacturing, ODMs/OEMs are already beginning to set foot in software engineering covering the underlying domain controller core software and BSP driver.

Model 2: Tier 1 suppliers produce domain controllers for OEMs. This is the most common model of cooperation at the current stage. Tier 1 suppliers adopt the white box or gray box model; OEMs have the power to develop the application layer for autonomous driving or the intelligent cockpit. Chip vendors, Tier 1 suppliers and OEMs often form close partnerships. Chip vendors supply chips and develop software stacks and prototype design packages; Tier 1 vendors provide domain controller hardware production, middle 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 vendors born out of the trend toward separation of software and hardware focus their efforts on core domain controller software platforms. Upstream, they support OEMs to have independent system development authority and downstream integrate Tier 2 vendor resources such as chips and sensors. As the initiator of this mode, TTTech is currently valued at over $1 billion and features key shareholders like Audi, Samsung Electronics, Infineon, and Aptiv.

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

Meanwhile, Tier 1 suppliers also play the role of Tier 1.5. For example, in the area of ​​cockpit domain controllers, Bosch, which specializes in the underlying cockpit software systems, outsources hardware production and building ecosystems to its partner, AutoLink. For Tier 1 vendors, they are better able to keep up with the development trend of the market by providing a range of solutions such as software, hardware and integrated software and hardware solutions.

Model 4: Tier 0.5 suppliers were born out of OEM needs for complete self-development capabilities. Tier 0.5 suppliers closely related to OEMs will participate in the entire process of OEMs, from R&D, production and manufacturing to even later data management and exploitation. There are three types of Tier 0.5 providers:

(1) Some OEMs are separating 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 change to Tier 0.5 vendors. In the context of chip shortages, chip vendors have more of a say, and even OEMs have to bypass Tier 1 vendors to buy directly from them. Chip vendors no longer feel fulfilled in their role as Tier 2 vendors and are trying to develop a strong bond with OEMs. Chip suppliers participate in the development of OEM vehicle models from the start. For example, Mobileye and Geely have built strategic cooperation; after the acquisition of Veoneer, Qualcomm will work harder to deploy autonomous driving and cockpit cross-domain fusion computing platforms; The NVIDIA DRIVE Hyperion 8.1 platform is compatible with both autonomous driving and the cockpit, and the chip vendor is even trying to partner with OEMs on a self-driving business profit-sharing model.

Model 5: System integrators outsource domain controllers to ODMs/OEMs, especially providers of autonomous driving system solutions and smart cockpit software platforms. For example, Baidu’s ACU is produced by Flex, and Haomo AI also cooperates with Flex. Even many self-driving start-ups can adopt this model, that is, with ODM/OEM providing the extra automotive OEM hardware production capacity, they provide complete “Domain Controller” solutions. + ADAS integrated development” to OEMs, with the aim of being better able to compete with conventional Tier 1 suppliers.

In the era of software-defined vehicles, complete software system solutions will be the key to gaining competitive advantages for domain controller vendors.

In general, we believe that in the context of software and hardware separation, full-stack software system development capabilities will play a key role in the future competition. For domain controller vendors, the key to gaining competitive advantages lies in continuous efforts to enrich and build the underlying platforms (software-defined hardware, data services, information security, exploitation, etc.), middle layer platforms (middleware, AutoSAR, adaptation chip, etc.) and application layer platforms (human-computer interaction (HMI), algorithms, software stack, etc.) .

Main topics covered:

1 Evolution of automotive electronic and electrical architecture (EEE)
1.1 Four Dimensions of Automotive EEE Upgrade: Software Architecture, Hardware Architecture, Communication Architecture, and Power Architecture
1.2 Domain integration platform and vehicle computing platform in the evolution of automotive EEE
1.3 Evolution of the automotive EEA over the next decade
1.4 OEMs accelerate upgrade and mass production in the EEA (1)
1.5 OEMs accelerate upgrade and mass production in the EEA (2)
1.6 EEA and OEM Next Generation Domain Controller Layout (1)
1.7 EEA and OEM Next Generation Domain Controller Layout (2)
1.8 EEA and OEM Next Generation Domain Controller Layout (3)
1.9 EEA and OEM Next Generation Domain Controller Layout (4)

2 Evolution of domain controller software and hardware architectures and business models
2.1 Domain Controller Hardware Design
2.2 Domain Controller Software Design
2.3 Domain controller design and production models
2.4 Domain Controller ODM/OEM Production Model

3 Autonomous Driving Domain Controller Technology and Market Research
3.1 Evolution of autonomous driving and domain controller
3.2 L2+ Driving and Parking Integrated Domain Controller Solutions
3.3 L3/L4 Autonomous Driving Domain Controller Solutions
3.4 OEM Autonomous Driving Domain Controller Software and Hardware Solutions
3.5 Tier 1 Vendor Autonomous Driving Domain Controller Solutions
3.6 Autonomous Driving Domain Controller Software Vendor Solutions
3.7 Autonomous Driving Domain Controller SoC Solutions
3.8 Benchmarking of Autonomous Driving Domain Controller Technology
3.9 Autonomous Driving Domain Controllers End Markets: Passenger Cars
3.10 Autonomous Driving Domain Controllers End Markets: Commercial Vehicles
3.11 Autonomous Driving Domain Controller End Markets: Autonomous Delivery Vehicles

5 foreign domain controller providers
5.1 Bosch
5.1.1 Creation of the Cross-Domain Computing Solutions Division (XC Division)
5.1.2 Structure and presence of the XC division in China
5.1.3 Other Integrated ETAS Software Activities
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: Autosee 2.0 System Architecture
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 Benefits
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: Fusion Control Products System Architecture Roadmap
5.1.14 Autonomous Driving Domain Controllers: Product Development Trends
5.1.15 Autonomous driving domain controllers: evolution of DASy technology
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.3 Continental
5.4 Veoneer
5.6 Aptiva
5.7 Denso
5.8 Faurecia Clarion
5.9 Panasonic
5.10 Harmon
5.11 LG Electronics
5.12 Tesla
5.13 Marelli
5.14 TT Tech

For more information on this report, visit