封面
市場調查報告書
商品編碼
1513725

在集中式EEA架構中網域控制器的開發

Development of Domain Controllers in Centralized EEA Architecture

出版日期: | 出版商: MIC - Market Intelligence & Consulting Institute | 英文 23 Pages | 訂單完成後即時交付

價格

汽車電氣和電子架構(EEA)朝向集中式域結構發展。基於功能的集中與劃分,國際各大品牌將汽車電子控制系統劃分為五個網域的架構。 ADAS(高級駕駛輔助系統)和座艙域率先採用網域控制器,大幅提高了運算效率,培育了業界新的合作模式。

本報告詳細分析了集中式EEA架構下各網域的發展趨勢,考察了各大公司的域控制器產品,並探討了供應鏈中的新合作模式。

目錄

第1章 EEA 核心驅動因素與功能網域的趨勢

  • 整合進度緩慢的網域控制器:動力總成/底盤/車身
    • 動力總成網域:整合ECU基本功能的子控制器
    • 底盤網域:ECU目前主流
    • 主體網域:網關和基本 ADAS 功能的集成
  • 首選整合式網域控制器:智慧座艙/ADAS
    • 智慧座艙網域
    • ADAS網域

第2章 網域控制器產品開發分析

  • Bosch
  • Apiv
  • Continental
  • Desay

第3章 網域控制站供應模式

  • 模式(1):汽車製造商內部開發與外包生產
  • 模式(2):傳統一級供應商提供三類服務
  • 模式(3):第三方服務提供者的出現

第4章 MIC 的觀點

  • 延遲實施包含 ADAS 和駕駛艙優先網域的網域集中式架構
  • 駕駛停車一體化成為標準配置
  • 多樣化的網域控制器供應模式為 IT OEM 創造了機會

附錄

  • 公司名單
Product Code: NARPT24071001

The vehicle electrical and electronic architecture (EEA) is evolving towards a centralized domain structure. Based on functional centralization and partitioning, leading international brands have divided automotive electronic control systems into a five-domain framework. The advanced driver assistance systems (ADAS) and cockpit domains are the first to adopt domain controllers, significantly enhancing computational efficiency and fostering new cooperation models within the industry. This report provides an in-depth analysis of the development trends within each domain under the centralized EEA architecture, examines the domain controller products of leading companies, and explores new cooperation models within the supply chain.

Table of Contents

1. EEA's Core Drivers and Functional Domain Trends

  • 1.1 Domain Controller with Slow Integration Progress: Powertrain / Chassis / Body
    • 1.1.1 Powertrain domain: Sub-controllers integrating basic ECU functions
    • 1.1.2 Chassis domain: Currently dominated by ECUs
    • 1.1.3 Body domain: Integrating gateway and basic ADAS functions
  • 1.2 Domain Controllers with Priority Integration: Smart Cockpit / ADAS
    • 1.2.1 Smart Cockpit Domain
    • 1.2.2 ADAS Domain

2. Domain Controller Product Development Analysis

  • 2.1 Bosch
  • 2.2 Apiv
  • 2.3 Continental
  • 2.4 Desay

3. Domain Controller Supply Models

  • 3.1 Model 1: Carmakers Developing In-House and Outsourcing Production
  • 3.2 Model 2: Traditional Tier-1 Suppliers Providing Three Types of Services
  • 3.3 Model 3: Emergence of Third-Party Service Providers

4. MIC Perspective

  • 4.1 Slow Adoption of Domain-Centralized Architecture with ADAS and Cockpit as Priority Domains
  • 4.2 Driving and Parking Integration Becomes Standard Configuration
  • 4.3 Diverse Domain Controller Supply Models Create Opportunities for IT OEMs

Appendix

  • List of Companies

List of Figures

  • Figure 1: Desay's IPU ADAS Domain Controller Software and Hardware Architecture and Division of Labor Logic
  • Figure 2: Domain Controller Suppliers and Their Relationships
  • Figure 3: Automakers Develop In-House and Outsource Production
  • Figure 4: Tier-1 Supplier Supply Model
  • Figure 5: Third-Party Service Provider Supply Model