查看購物車
  • Simplified Chinese
  • English
  • Japanese
  • Korean
封面
市場調查報告書
商品編碼
1613804

中國的汽車雲端服務平台產業(2024年)

Automotive Cloud Service Platform Industry Report, 2024
出版日期: | 出版商: ResearchInChina | 英文 360 Pages | 商品交期: 最快1-2個工作天內

價格
簡介目錄

1. 基於人工智慧的模式和汽車 NOA 將擴大汽車雲端服務的需求

2024年，經歷價格競爭後，OEM成本降低成為焦點，業務雲化步伐放緩，雲端需求減少，但NOA的量產和基於雲端的AI基礎模型對汽車雲端服務的需求正在增加而不是隨著它們安裝在汽車中而減少。

安裝在汽車上的AI平台模型和NOA對雲端服務有以下要求。

1.硬體基礎設施硬體基礎設施：AI平台模型/NOA的運作需要大量的運算能力。除了對雲端伺服器的效能和數量要求越來越高之外，伺服器設備的網路效能也受到考驗。

2.軟體解決方案

AI平台模式：截至2024年9月，國內量產車款搭載的平台模式主要採用雲端部署。一些新興整車廠（如蔚來/小鵬汽車/理想汽車）採用端雲一體化部署，需要呼叫基於雲端的模型來完成複雜的功能模式。

基礎模型安裝在車輛上後，與使用者的互動頻率會增加，交互請求數會從每天幾次增加到數十次甚至數百次，雲端服務的需求也會增加。

NOA：NOA安裝數量大幅增加，使用頻率增加，導致處理和儲存的資料量增加，雲端服務需求增加，配套工具鏈增加。

2024年，阿里雲將為Momenta提供穩定、靈活的雲端原生運算資源，建構自動化的資料閉環。此方案支援端到端的技術框架，涵蓋視覺識別AI能力，可協助智慧駕駛解決方案的大規模部署與運用。 Momenta使用Spot的例子，基於阿里雲ESS&HPA機制的彈性，實現了高性價比。

同年，AWS與賓士、BMW等國際品牌合作，透過雲端平台工具鏈打造AI助手，提升業務效率。

2.雲端平台工具鏈深度整合

2024年，汽車雲端服務解決方案將實現從設計開發到生產管理、供應鏈優化、行銷推廣，甚至售後服務的全鏈條資料整合和智慧決策支援。雲端廠商的新解決方案體現了功能深度整合、工具鏈完整的特性。

2024年9月，百度推出智慧雲端3.0，專注於端到端智慧駕駛開發。特點如下。

可用於從車輛到雲端的全流程智慧駕駛訓練，包括建構虛擬模擬資料。

建構即時車路雲平台，提升雲端訓練效率，消除車路資料壁壘。平台提供壅塞路段提前避讓、超視距風險預警、紅綠燈提醒、遠端即時鳥瞰等服務。

我們為語意調度、內容生成、向量搜尋和跨模態等研發場景提供基於雲端的駕駛艙基礎設施模型。

2024年9月，華為發表L4級自動駕駛網路解決方案－星河AI自動駕駛網路。這使得網路數據分析、多場景模擬和雲端代理呼叫成為可能。

本報告提供中國的汽車雲端服務平台產業調查分析，提供國內外的雲端服務產業和各公司的平台相關資訊。

目錄

第1章 汽車雲端服務概要

  • 汽車雲端服務產業概覽
  • 汽車雲端服務的主要類型
  • 汽車雲端服務的競爭格局
  • 中國汽車雲商業模式
  • 汽車雲端應用場景

第2章 汽車雲端解決方案

  • 自動駕駛雲
  • 車聯網雲
  • V2X 雲
  • 數位轉型
  • 雲端資料閉環
  • 人工智慧+雲端服務
  • 雲端資訊安全
  • SOA雲端

第3章 雲端平台基礎設施

  • 汽車雲產業鏈
  • 資料中心
  • 雲端伺服器
  • 伺服器晶片
  • 雲端提供商晶片自主研發進展

第4章 汽車公共雲端平台

  • 亞馬遜雲 - AWS
  • 微軟的雲端 - Azure
  • Google雲
  • 華為汽車雲
  • 百度汽車雲
  • 阿里巴巴汽車雲
  • 騰訊汽車雲
  • 位元組跳動汽車雲
  • NVIDIA 雲端服務支持

第5章 OEM雲端平台的設計

  • OEM解決方案的比較(1)-(3)
  • Geely
  • Xpeng Motors
  • Li Auto
  • NIO
  • FAW
  • Changan
  • GWM
  • SAIC
  • GAC

第6章 摘要和趨勢

  • 雲端遷移對 OEM 的重要性
  • 雲端服務需求趨勢
  • 原始設備製造商與供應商之間的聯盟趨勢
  • 雲端運算架構的趨勢
  • 雲端原生將改變軟體開發方式
  • 終端與雲端集成
  • 雲端服務硬體基礎架構的趨勢
簡介目錄
Product Code: GX013

Automotive cloud services: AI foundation model and NOA expand cloud demand, deep integration of cloud platform tool chain

In 2024, as the penetration rate of intelligent connected vehicles continues to increase, the development of automotive cloud services will show the following trends:

AI foundation model and NOA installed in vehicles expand the demand for automotive cloud services

Deep integration of cloud platform tool chain

Cloud native further changes the way automotive software is developed

Terminal-cloud integration

Cloud infrastructure resources are further in short supply, and cloud vendors are increasing their investment costs

......

1. AI foundation model and NOA installed in vehicles expand the demand for automotive cloud services

In 2024, after experiencing a price war, OEMs' cost reduction has become a focus, the pace of business cloudification has slowed down, and the demand for cloud has declined; but with the mass production of NOA and the installation of cloud-based AI foundation models in vehicles, the demand for automotive cloud services has increased instead of decreased.

AI foundation model and NOA installed in vehicles have the following requirements for cloud services:

1.Hardware infrastructure: The operation of AI foundation model/NOA requires a lot of computing power. In addition to placing higher demands on the performance and number of cloud servers, it also tests the network performance of server facilities.

2.Software solution:

AI foundation model: As of September 2024, the foundation model installed in domestic mass-produced models mainly adopts cloud-based deployment. Some emerging OEMs (such as NIO/ Xpeng Motors/Li Auto) adopt terminal-cloud integration deployment, in which complex functional modes still need to call cloud-based models to complete.

After the foundation model was installed in vehicles, the frequency of user interactions increased, from a few interaction requests per day to dozens or even hundreds of interaction requests per day, which led to an increase in demand for cloud services.

NOA: NOA's installation volume has surged significantly, and the frequency of use has also increased, which has led to an increase in the amount of data processed and stored, an increase in the demand for cloud services, and an increase in the supporting tool chain.

In 2024, Alibaba Cloud provides Momenta with stable and flexible cloud-native computing resources to build automated closed-loop data. The solution supports an end-to-end technical framework, covers visual perception AI capabilities, and can promote large-scale deployment and application of intelligent driving solutions. Momenta uses Spot cases to achieve high cost- effectiveness based on the elasticity of Alibaba Cloud ESS&HPA mechanisms.

In the same year, AWS cooperates with international brands such as Mercedes-Benz and BMW to build AI assistants through cloud platform tool chain to improve operational efficiency.

2. Deep Integration of cloud platform tool chain

In 2024, automotive cloud service solutions will further develop in the direction of deep integration, realizing data integration and intelligent decision support for the entire chain from design and development to production management, supply chain optimization, marketing promotion and even after-sales service. New solutions of cloud vendors reflect characteristics of deep functional integration and perfect tool chain:

In September 2024, Baidu launched Intelligent Cloud 3.0, focusing on end-to-end intelligent driving development. Features include:

It can be used for full-process intelligent driving training from vehicle to cloud, including building virtual simulation data;

By improving training efficiency in the cloud and breaking down data barriers between the vehicle and the road, a real-time vehicle-road cloud platform is built; the platform provides services including early avoidance of congested sections, beyond-visual-range risk warnings, traffic light reminders, and remote live bird's-eye view.

Provides a cloud-based cockpit foundation model for R&D scenarios such as semantic understanding scheduling, content generation, vector search, and cross-modality.

In September 2024, Huawei launched the L4 autonomous driving network solution - Xinghe AI autonomous driving network, which implements network data analysis, multi - scenario simulation and Agent calling in the cloud:

3. Cloud native further changes the way automotive software is developed

As some OEMs/Tier1s begin to build a vehicle-cloud collaborative infrastructure and try to upload vehicle-side data to the cloud for analysis and processing, and send cloud-side commands to the vehicle to achieve simple vehicle-cloud interaction. Cloud native technology has begun to be applied to the cloud-vehicle collaborative development process in automotive industry.

Cloud native is a software approach to building and running scalable applications in new dynamic environments such as public clouds, private clouds, and hybrid clouds. The concept of "cloud native" was proposed before 2020, but its application in automobiles has been in the exploratory stage and has not been widely used. It is mainly concentrated in telematics and some intelligent cockpit functions. In 2024, with the application of multi-cloud environments and AI technologies, the application scenarios of cloud native will increase greatly, and begin to affect construction logic of PaaS/SaaS cloud service solutions in the automotive industry from underlying layer:

On the vehicle side, in addition to in-vehicle infotainment system, cloud native has been used for the development and optimization of related technologies for autonomous driving and intelligent cockpit. For example, through large-scale computing and training functions of cloud-based autonomous driving platform, more accurate models and more comprehensive algorithms are provided for autonomous driving system, improving the safety and reliability of autonomous driving.

In the cloud, OEMs use a more complete cloud platform to store, mine, analyze and process vehicle data, provide support for intelligent vehicle operations, and gradually apply cloud-native software development models to OEM supply chain management, production and manufacturing and other fields, achieving collaborative optimization of entire industry chain. For example, container orchestration technology (Kubernetes, etc.) has gradually become the core technology for OEMs to build cloud-vehicle software collaborative development platforms.

Taking the cooperation between AWS and Continental to develop cloud-based ECU as an example, Continental used AWS Graviton to simulate the hardware environment, then selected operating system and middleware to run on AWS EC2, and completed the creation of virtualized development environment through AWS EC2.

In 2024, cloud native applications will focus on:

1.Computing power management: The cloud-native platform can provide efficient computing power management technologies, including GPU computing power scheduling and distributed training, to meet the needs of AI algorithm training and real-time reasoning.

2.Optimization of service mesh and API gateway: Besides 5G communication, performance optimization of service mesh, collaboration with Kubernetes scheduler, flexible configuration and security protection of API gateway also have a great impact on cloud communication.

3.Data management and governance: Data management capabilities of Automotive Cloud Native Platform include data storage, backup, cleaning, labeling, and data security & compliance management. As OEMs increasingly value the circulation of data assets, efficient data circulation and sharing have become one of factors affecting the cloud native platform.

4.Cloud resource utilization: Some OEMs are beginning to pay attention to factors such as energy efficiency and resource utilization of cloud native technologies. Some energy-saving technologies and strategies reduce the energy consumption of cloud native platforms, while improving resource utilization efficiency and reducing operating costs.

NIO uses cloud-native technology to build a vehicle-cloud collaborative development platform

In order to solve problems such as scarce computing power, chaotic edge node management, and unstable cloud communications, NIO uses KubeEdge as the core of platform and builds a complete vehicle-cloud collaborative development platform with Kubernetes + KubeEdge as the technical base.

NIO's vehicle-cloud collaboration platform uses KubeEdge's cloud-edge communication mechanism to solve the tidal effect problem of node connections.

Typical application scenarios of this technology include:

1. New energy vehicle battery health and safety data analysis: In the algorithm development stage, use containerization to develop edge algorithms; in the engineering vehicle verification stage, deploy edge computing container applications in small batches; after verification, replace the corresponding mass production base image.

2. Build a vehicle-side software test management platform: After introducing cloud native capabilities, Virtual car, test benches, and real vehicles can be connected to K8s for unified monitoring and management, which can arrange test tasks more reasonably and improve the utilization of test resources.

Table of Contents

1 Overview of Automotive Cloud Services

  • 1.1 Overview of Automotive Cloud Service Industry
    • 1.1.1 Definition of Automotive Cloud
    • 1.1.2 China's Automotive Cloud Market Size
    • 1.1.3 Classification of Automotive Cloud Platforms
    • 1.1.4 Automotive Public Cloud Platforms in China
  • 1.2 Main Types of Automotive Cloud Services
  • 1.3 Competition Landscape of Automotive Cloud Services
  • 1.4 Automotive Cloud Business Models in China
  • 1.5 Application Scenarios of Automotive Cloud

2 Automotive Cloud Solutions

  • 2.1 Autonomous Driving Cloud
    • 2.1.1 Requirements of Autonomous Driving for Cloud: Cloud Services Support Autonomous Driving
    • 2.1.1 Requirements of Autonomous Driving for Cloud: Cloud Services Support Simulation Testing
    • 2.1.2 Application Scenarios of Autonomous Driving Cloud
    • 2.1.3 Cloud Service + End-to-End Intelligent Driving: Case 1
    • 2.1.3 Cloud Service + End-to-End Intelligent Driving: Case 2
    • 2.1.4 Autonomous Driving Cloud Platform: Realizing Three Types of Functions
    • 2.1.5 Example of Autonomous Driving Cloud Service Provider: AWS
    • 2.1.5 Example of Autonomous Driving Cloud Service Provider: Huawei Cloud
  • 2.2 Telematics Cloud
    • 2.2.1 Application Scenarios of Telematics Cloud
    • 2.2.2 Requirements of Telematics for Cloud: Monitoring, Early Warning, Diagnosis and Rescue
    • 2.2.2 Requirements of Telematics for Cloud: Facilitating OTA Process Management
    • 2.2.3 Example of Telematics Cloud Service Providers: Tencent Cloud
    • 2.2.3 Example of Telematics Cloud Service Providers: PATEO
  • 2.3 V2X Cloud
    • 2.3.1 Overview of V2X Cloud
    • 2.3.2 V2X Cloud Service Architecture: General Architecture
    • 2.3.2 V2X Cloud Service Architecture: Segmented Architecture
    • 2.3.3 In-vehicle Cloud Computing: Six Service Contents
    • 2.3.3 In-vehicle Cloud Computing: Pain Points and Solutions
    • 2.3.4 Example of V2X Cloud Service Providers: Baidu Cloud
    • 2.3.4 Example of V2X Cloud Service Providers: SenseAuto
  • 2.4 Digital Transformation
    • 2.4.1 Overview of Digital Transformation
    • 2.4.2 Requirements of Digital Transformation for Cloud
  • 2.5 Cloud Data Closed Loop
    • 2.5.1 Overview of Data Closed Loop
    • 2.5.2 The Role of Cloud Platform in Data Closed Loop: Promoting Data Migration to the Cloud
    • 2.5.2 The Role of Cloud Platform in Data Closed Loop: Reducing Costs and Increasing Efficiency
    • 2.5.2 The Role of Cloud Platform in Data Closed Loop: Computing Power Requirements
    • 2.5.3 Cloud Platform Data Closed Loop Case: AWS Cloud
    • 2.5.3 Cloud Platform Data Closed Loop Case: Baidu Cloud
    • 2.5.3 Cloud Platform Data Closed Loop Case: Volcano Engine
    • 2.5.3 Cloud Platform Data Closed Loop Case: Alibaba Cloud
    • 2.5.3 Cloud Platform Data Closed Loop Case: SAIC
  • 2.6 AI + Cloud Services
    • 2.6.1 Application Scenarios of AI + Cloud Service
    • 2.6.2 Reference Architecture of AI Intelligent Cloud
    • 2.6.3 Application of AI in IaaS, PaaS, and MaaS
    • 2.6.4 Integration of AI Cloud Computing and Intelligent Computing
    • 2.6.5 Cloud AI Accelerator
    • 2.6.6 Cooperative Deployment of AI Cloud and Devices
  • 2.7 Cloud Information Security
    • 2.7.1 Telematics Security Challenges
    • 2.7.2 Cloud Security Scenarios
    • 2.7.3 Cloud Information Threats
    • 2.7.4 Cloud Information Security Architecture
    • 2.7.5 Cloud Security Strategy: Cloud WAF
    • 2.7.5 Cloud Security Strategy: Container Security
    • 2.7.5 Cloud Security Strategy: Cloud Host Security
    • 2.7.5 Cloud Security Strategy: Cloud Identity Management
    • 2.7.5 Cloud Security Strategy: Micro-isolation
    • 2.7.6 Typical Case of Cloud Security: Qi An Xin Technology
    • 2.7.6 Typical Case of Cloud Security: Topsec
    • 2.7.6 Typical Case of Cloud Security: VecenTek
    • 2.7.6 Typical Case of Cloud Security: Infosec Technologies
  • 2.8 SOA Cloud
    • 2.8.1 Cloud Native in SOA
    • 2.8.2 SOA Cloud Case 1 (Continental)
    • 2.8.2 SOA Cloud Case 2 (Qualcomm)

3 Cloud Platform Infrastructure

  • 3.1 Automotive Cloud Industry Chain
  • 3.2 Data Centers
    • 3.2.1 Distribution of Data Centers in China
    • 3.2.2 Data Center Layout of Cloud Platform Companies
    • 3.2.3 Supercomputing Centers
  • 3.3 Cloud Servers
  • 3.4 Server Chips
    • 3.4.1 Server Chip Technology Route
    • 3.4.2 Server Chip Vendors
  • 3.5 Progress of Cloud Providers in Self-development of Chips
    • 3.5.1 AWS' Self-developed Chips
    • 3.5.2 Google's Self-developed Chips
    • 3.5.3 Alibaba's Self-developed Chips
    • 3.5.4 Baidu's Self-developed Chips: Architecture of Kunlunxin
    • 3.5.4 Baidu's Self-developed Chips: Cloud Scenario of Kunlunxin

4 Automotive Public Cloud Platforms

  • 4.1 Amazon Cloud - AWS
    • 4.1.1 Introduction
    • 4.1.2 Regional Distribution
    • 4.1.3 Automotive Industry Layout
    • 4.1.4 AWS for Automotive
    • 4.1.5 Software-Defined Vehicle Solutions
    • 4.1.6 Telematics Data Lake
    • 4.1.7 Autonomous Driving Data Lake
    • 4.1.8 Automotive Customers
    • 4.1.9 Supply Relationship (2024 Summary)
    • 4.1.10 Cooperation Case: Audi
    • 4.1.10 Cooperation Case: BMW
    • 4.1.10 Cooperation Case: Continental
    • 4.1.10 Cooperation Case: HERE
    • 4.1.10 Cooperation Case: ABUP
    • 4.1.10 Cooperation Case: ThunderSoft
    • 4.1.10 Cooperation Case: 51World
  • 4.2 Microsoft Cloud - Azure
    • 4.2.1 Azure Automotive Solutions
    • 4.2.2 Azure Telematics Cloud Platform
    • 4.2.3 Microsoft Connected Vehicle Platform (MCVP) Service: Business Model and Main Customers
    • 4.2.4 Microsoft Connected Vehicle Platform (MCVP) Service: Ecosystem Partners
    • 4.2.5 Cooperated with Ericsson Connected Vehicle Cloud (CVC)
    • 4.2.6 Ericsson CVC Solution
    • 4.2.7 NVIDIA AI Cloud Server Azure Solution
    • 4.2.8 Cooperative Auto Parts Suppliers
    • 4.2.9 Cooperative OEMs
  • 4.3 Google Cloud
    • 4.3.1 Google Cloud Platform (GCP)
    • 4.3.2 Latest Dynamics
  • 4.4 Huawei Automotive Cloud
    • 4.4.1 Introduction
    • 4.4.2 Automotive Solutions
    • 4.4.3 Telematics Solution
    • 4.4.4 Autonomous Driving Development Solution
    • 4.4.5 Autonomous Driving Cloud Service: Qiankun 3.0
    • 4.4.5 Autonomous Driving Cloud Service: Xinghe AI Cloud
    • 4.4.6 Foundation Model Solution
    • 4.4.7 Mobility Solution
    • 4.4.8 Automotive Simulation Solution
    • 4.4.9 Digital Intelligent Platform Solution
    • 4.4.10 Digital Marketing Solution
    • 4.4.11 Overseas Business Solutions
    • 4.4.12 Customers (1)
    • 4.4.12 Customers (2)
  • 4.5 Baidu Automotive Cloud
    • 4.5.1 Introduction
    • 4.5.2 3.0 Architecture
    • 4.5.3 Autonomous Driving Solution: Model Training Acceleration
    • 4.5.3 Autonomous Driving Solution: Simulation
    • 4.5.3 Autonomous Driving Solution: Intelligent Driving Data Platform
    • 4.5.4 Baidu Telematics Cloud
    • 4.5.5 Baidu V2X Cloud
    • 4.5.6 Data Closed-Loop Solution
    • 4.5.7 Data Annotation Solution
    • 4.5.8 Security System
  • 4.6 Alibaba Automotive Cloud
    • 4.6.1 Introduction
    • 4.6.2 Industry Capabilities
    • 4.6.3 Technical Bases: Apsara Platform
    • 4.6.3 Technical Bases: Apsara + CIPU
    • 4.6.3 Technical Bases: Intelligent Computing Platform
    • 4.6.3 Technical Bases: Intelligent Computing Center
    • 4.6.4 Main Customers: Momenta
    • 4.6.4 Main Customers: Xpeng Motors
    • 4.6.5 Telematics Security Solution: Cloud-Network-Terminal Integrated Defense
  • 4.7 Tencent Automotive Cloud
    • 4.7.1 Introduction
    • 4.7.2 Architecture: A New Generation of Data Closed Loop
    • 4.7.3 Autonomous Driving Cloud
    • 4.7.4 Intelligent Connected Cloud
    • 4.7.5 Capabilities
    • 4.7.6 Ecosystem
    • 4.7.7 Security Mechanism
    • 4.7.8 OEM Customers
  • 4.8 ByteDance Automotive Cloud
    • 4.8.1 Introduction
    • 4.8.2 System Architecture
    • 4.8.3 Ecosystem
    • 4.8.4 ByteDance's Cloud Computing Capabilities
    • 4.8.5 Volcano Engine Multi-Cloud Disaster Tolerance Architecture: Traffic Scheduling Solution
    • 4.8.5 Volcano Engine Multi-Cloud Disaster Tolerance Architecture: Traffic Scheduling Solutions for Access and Application Layers
  • 4.9 NVIDIA Cloud Service Supporting
    • 4.9.1 Omniverse Cloud
    • 4.9.2 Cooperation Case

5 OEM Cloud Platform Layout

  • OEM Solution Comparison (1) - (3)
  • 5.1 Geely
    • 5.1.1 Cloud Platform Strategy
    • 5.1.2 Digital Transformation Strategic Planning
    • 5.1.3 Corporate Cloud Platform
    • 5.1.4 Corporate Cloud Platform Solution and Planning
    • 5.1.5 Xingrui Intelligent Computing Center
    • 5.1.6 Intelligent Driving Cloud Data Factory
    • 5.1.7 Cooperation Case with Tencent Cloud
    • 5.1.8 Cooperation Case with Qiniu Cloud
    • 5.1.9 Cooperation Case with Huawei Cloud
    • 5.1.10 Cooperation Case between Zeekr and Alibaba Cloud
  • 5.2 Xpeng Motors
    • 5.2.1 Cloud Platform
    • 5.2.2 Fuyao Intelligent Computing Center
  • 5.3 Li Auto
    • 5.3.1 Cloud Platform Layout
    • 5.3.2 End-to-End Intelligent Driving Cloud World Model
    • 5.3.3 Telematics Cloud
    • 5.3.4 Data Storage Solution
  • 5.4 NIO
    • 5.4.1 Hybrid Cloud
    • 5.4.2 Energy Cloud
    • 5.4.3 Autonomous Driving Cloud
  • 5.5 FAW
    • 5.5.1 FAW Group's Cloud Platform Layout
    • 5.5.2 FAW Hongqi Intelligent Cloud
    • 5.5.3 FAW Group Local Data Center
    • 5.5.4 Cooperation Case between FAW and Huawei Cloud
    • 5.5.5 Cooperation Case between FAW and Alibaba Cloud
    • 5.5.6 Case Study of Cooperation between FAW and Baidu Cloud
    • 5.5.7 FAW Work Cloud Platform - Beidou Cloud
  • 5.6 Changan
    • 5.6.1 Digitalization Path: Cloud Stage
    • 5.6.1 Digitalization Path: Digital Management Stage
    • 5.6.1 Digitalization Path: Enlightenment Stage
    • 5.6.2 Cloud Platform Big Data
    • 5.6.3 Intelligent Vehicle Cloud Big Data Processing Architecture
    • 5.6.4 Telematics Cloud and R&D Cloud
    • 5.6.5 Terminal-Cloud Integrated SDA Architecture
    • 5.6.6 Terminal-Cloud Integrated Service Ecosystem
    • 5.6.7 Intelligent Vehicle Cloud Platform
    • 5.6.8 Cloud Platform Partners
    • 5.6.9 Changan and Tencent Cloud: Telematics Hybrid Cloud and Supercomputing Center
    • 5.6.9 Changan and Tencent Cloud: Cooperation History
    • 5.6.10 Changan and Huawei Cloud: Industrial Internet Cloud
  • 5.7 GWM
    • 5.7.1 Intelligent Cloud
    • 5.7.2 GWM & Huawei Cloud
  • 5.8 SAIC
    • 5.8.1 Cloud Business Layout
    • 5.8.2 Cloud Products and Services
    • 5.8.3 Cloud Platform: Overall Architecture
    • 5.8.4 Cloud Platform: Features and Advantages
    • 5.8.5 SAIC Autonomous Driving Cloud
    • 5.8.6 Data Flow of SAIL-Cloud Combined with Cloud Foundation Model
    • 5.8.7 Intelligent Connected Cloud of SAIL-Cloud
    • 5.8.8 Cooperation Case of SAIL-Cloud
    • 5.8.9 Cloud Product Technology and Security Route
    • 5.8.10 Overseas Cooperation with AWS
  • 5.9 GAC
    • 5.9.1 Cooperate with Tencent on Telematics Cloud
    • 5.9.2 Cooperate with Tencent on Intelligent Driving Cloud
    • 5.9.3 Cooperate with ByteDance on Digital Cloud

6 Summary and Trends

  • 6.1 Significance of OEMs' Migration to Cloud
    • 6.1.1 Cloud Platform Is the Foundation of Digitization of OEMs
    • 6.1.2 Significance of OEMs' Migration to Cloud (1)
    • 6.1.3 Significance of OEMs' Migration to Cloud (2)
    • 6.1.4 Significance of OEMs' Migration to Cloud (3)
    • 6.1.5 Significance of OEMs' Migration to Cloud (4)
  • 6.2 Cloud Service Demand Trends
    • 6.2.1 Development Path of Cloud Services in China
    • 6.2.2 Changes in Demand for Cloud Services: Characteristics
    • 6.2.2 Changes in Demand for Cloud Services: AI Foundation Model
    • 6.2.2 Changes in Demand for Cloud Services: Multi-Cloud Environment
    • 6.2.3 Summary of Cloud Capabilities Demanded by OEMs (1):
    • 6.2.3 Summary of Cloud Capabilities Demanded by OEMs (2):
    • 6.2.3 Summary of Cloud Capabilities Demanded by OEMs (3): Deep Integration of Cloud Platform Tool Chain
  • 6.3 OEM and Supplier Cooperation Trends
    • 6.3.1 Cloud Application of OEMs
    • 6.3.2 Automotive Cloud Business Model
    • 6.3.3 OEMs' Strategy for Selecting Cloud Service Providers
  • 6.4 Cloud Computing Architecture Trends
    • 6.4.1 Cloud Computing Architecture Moves Towards Software and Hardware Integration
    • 6.4.2 E/E Architecture of Automotive Cloud Computing
  • 6.5 Cloud Native Changes Software Development Methods
    • 6.5.1 Cloud Native Changes Software Development Methods: Vehicle-Cloud Collaboration
    • 6.5.1 Cloud Native Changes Software Development Methods: Main Technologies and Advantages
    • 6.5.1 Cloud Native Changes Software Development Methods: Application Scenarios
    • 6.5.2 Data Lake + Cloud Native to Build a New Storage and Computing System
    • 6.5.3 Cloud Native Security Evolution
    • 6.5.4 Supplier's Cloud Native Application Case: Alibaba Cloud
    • 6.5.4 Supplier's Cloud Native Application Case: Tencent Cloud
    • 6.5.4 Supplier's Cloud Native Application Case: Huawei Cloud
    • 6.5.5 OEM's Cloud Native Application Case: NIO (1)-(4)
    • 6.5.5 OEM's Cloud Native Application Case: GWM (1)-(8)
    • 6.5.5 OEM's Cloud Native Application Case: FAW
    • 6.5.5 OEM's Cloud Native Application Case: Xpeng Motors (1)-(2)
    • 6.5.5 OEM's Cloud Native Application Case: Li Auto
    • 6.5.6 OEM's Cloud Native Application Case: Summary
  • 6.6 Terminal-Cloud Integration
    • 6.6.1 Terminal-Cloud Integration (1)
    • 6.6.2 Terminal-Cloud Integration (2)
  • 6.7 Cloud Service Hardware Infrastructure Trends
    • 6.7.1 Cloud Service Hardware Infrastructure Trends (1)
    • 6.7.2 Cloud Service Hardware Infrastructure Trends (2)