세계 및 중국의 자동차용 OS 산업(2023-2024년)

Global and China Automotive Operating System (OS) Industry Report, 2023-2024

US $ 4,500 ￦ 6,508,000

Unprintable PDF (Single User License)

PDF 보고서를 1명만 이용할 수 있는 라이선스입니다. 인쇄 불가능하며, 텍스트의 Copy&Paste도 불가능합니다.

US $ 6,800 ￦ 9,834,000

Printable & Editable PDF (Enterprise-wide License)

PDF 보고서를 동일 기업의 모든 분이 이용할 수 있는 라이선스입니다. 인쇄 가능하며 인쇄물의 이용 범위는 PDF 이용 범위와 동일합니다.

한글목차

중국의 운영체제는 노력을 시작합니다.

2023년, 화웨이, 반마즈싱, 샤오미, NIO 등 중국 업체들이 OS 시장에 집중하여 경쟁 우위를 가진 다양한 버전을 출시하여 중국 칩 솔루션에 적응하고 OEM의 지정 프로젝트를 획득했습니다.

미들웨어에서 AUTOSAR는 여전히 차량 제어 및 자율주행을 위한 OEM의 선택 중 하나입니다. 그러나 AUTOSAR는 국산 칩에 완전히 적합하지 않고, 현장 통신 처리의 피드백 시간이 길고, 자동차 기업의 요구를 완전히 충족시킬 수 없기 때문에 일부 공급자와 OEM은 자체 마이크로 커널과 미들웨어를 연구하고 있습니다.2023년 5월, CAAM은 오픈소스 마이크로커널을 기반으로 한 독립적인 자동차 OS를 실현하고 2025년에 QNX를 점진적으로 대체할 계획인 중국 자동차 OS 오픈소스 계획의 첫 번째 마이크로커널 오픈소스 프로젝트를 정식으로 발표했습니다. 그 중 iSOFT는 Mulan Public License(버전 2)를 사용하여 오픈소스 마이크로 커널을 제공하고 SemiDrive Technology는 G9X 칩을 제공했습니다.

아이소프트가 제공하는 EasyAda 마이크로커널은 다양한 칩 플랫폼과 응용 시나리오에 대응하는 보안 커널을 제공할 수 있습니다. iSOFT는 자동차 분야를 위해 마이크로커널에 대응하는 실시간 개선 메커니즘을 구현하고 있습니다. 예를 들어, 자율주행의 대규모 계산을 위한 우선순위 기반 선점 메커니즘, 마이크로커널의 선점 스케줄링 전략, 통합 알고리즘, 인터럽트, 지연 메커니즘 및 기타 기술적 수단을 통해 마이크로커널을 개선하여 실시간 및 성능 요구사항을 돌파할 수 있습니다. 할 수 있습니다.

이 보고서는 세계 및 중국의 자동차용 OS 산업에 대해 조사 분석했으며, 산업 동향, OS 분류, OS 및 기업 프로파일 등의 정보를 제공합니다.

목차

제1장 자동차용 OS 동향

• 동향 1 : 기본 OS 경쟁 환경의 변화
  • 시장 구도
  • 기본 OS 시장 뉴스
  • WinCE, 공식적으로 시장 퇴출
  • Linux, 잠재적인 경쟁력 강화
  • 국내화 현황
• 동향 2 : 오픈소스 통합 단계로 향하는 운영체제
  • 중국의 자동차용 OS 오픈소스 계획
  • 오픈소스 통합의 열쇠
• 동향 3 : SOA 아키텍처 자동차용 OS
  • 자동차용 OS의 정의
  • 소프트웨어 계층 아키텍처
  • 자동차용 OS의 특징
  • 자동차용 OS 개발 모드의 진화
  • 자동차용 OS 비즈니스 모델의 진화
  • OEM 차량의 OS 레이아웃
  • 프로바이더 자동차용 OS 레이아웃
  • 자동차용 OS 크로스 도메인 스케줄링 : 알고리즘 콜/칩 어뎁테이션
  • 자동차용 OS와 AI 대형 모델의 통합
• 동향 4 : OEM 자사개발 OS
  • 장점과 리스크
  • 현황
  • 솔루션 비교
• 동향 5 : IVI 시스템
  • 지도 소프트 기능의 약체화
  • 주요 프로바이더의 시장 점유율 추이

제2장 자동차용 OS 개요

• 자동차용 OS의 서론
• 자동차용 OS의 분류
• 소프트웨어 아키텍처
• 비즈니스 모델
• 기본적인 자동차용 OS
• 커스터마이즈 자동차용 OS
• ROM 자동차용 OS
• 하이퍼바이저
• OSEK
• 오픈 조직 : Covesa
• 오픈 조직 : AUTOSAR
• 오픈 조직 : Autoware Foundation

제3장 기본 자동차용 OS

• QNX
• Linux&AGL
• Android
• VxWorks
• AliOS
• Harmony OS
• Cockpit HOS
• Ubuntu
• ROS
• webOS

제4장 하이퍼바이저

• 개요
• QNX 하이퍼바이저
• ACRN
• COQOS 하이퍼바이저
• PikeOS
• EB Corbos 하이퍼바이저
• Harman 디바이스 가상화
• VOSYS 모니터
• ZlingSmart 하이퍼바이저

제5장 광의 자동차용 OS와 기업

• Neusoft Reach NeuSAR
• ThunderSoft
• ETAS
• ArcherMind Technology
• EB
• AICC
• NVIDIA DRIVE OS
• Baidu DuerOS
• Apex.AI
• iSOFT Infrastructure Software
• ZlingSmart
• ZTE GoldenOS
• ECARX
• 기타

제6장 OEM 자동차용 OS

• Tesla OS
• NIO SkyOS
• Xiaomi Hyper OS
• Li Auto
• Xpeng Motor XsmartOS
• Leap Motor

제7장 기타 OEM OS

• Volkswagen VW.OS
• Toyota Arene OS
• BMW
• Mercedes-Benz MB OS
• FAW.OS
• SAIC Z-ONE Intelligent Vehicle Cloud-Management-End Full Stack Solution-SOA Software Platform
• GAC Psi OS
• Geely
• Great Wall Motor
• Changan RTDriveOS
• CHERY-OS
• Dongfeng
• BYD OS

LSH

영문 목차

영문목차

Chinese operating systems start to work hard

In 2023, Chinese providers such as Huawei, Banma Zhixing, Xiaomi, and NIO made efforts in operating system market, launched different versions with competitive advantages, adapting to Chinese chip solutions and obtaining designated projects from OEMs.

In middleware, AUTOSAR is still one of choices of most OEMs for vehicle control and autonomous driving. But it is not fully adapted to domestic chips, and feedback time of on-site communication processing is longer, which can't fully meet requirements of auto companies, resulting in partial providers and OEMs researching their own microkernel and middleware. In May 2023, China Association of Automobile Manufacturers (CAAM) formally released the first microkernel open-source project of China Automotive Operating System Open Source Plan, which plans to realize independent automotive OS based on open source microkernel and gradually replace QNX in 2025. Among them, iSOFT provided open source microkernel using the Mulan Public License (version 2); SemiDrive Technology provided G9X chip.

EasyAda microkernel provided by iSOFT can provide secure kernels for various chip platforms and application scenarios. For automotive field, iSOFT has implemented corresponding real-time improvement mechanisms for microkernel. For example, priority-based preemption mechanism for large-scale calculations of autonomous driving, preemption scheduling strategy of microkernel, as well as integrated algorithm, interrupt, delay mechanism and other technical means can improve microkernel to break through real-time and performance requirements.

OEMs: three methods to realize vehicle operating systems

As EE architecture evolves towards a centralized computing architecture, software systems begin to move towards an SOA architecture, where operating systems begin to progress from domain-type to vehicle-level.

SOA-based vehicle operating system integrates functions of cockpit OS, intelligent driving OS, and safety vehicle control OS via central computing platform to provide vehicle-level platform with a set of programming interfaces. Characterized by layered decoupling and unified architecture, it improves development efficiency of auto companies via providing unified interfaces. Vehicle operating system realizes functions scheduling and integration in various domains of the vehicle by centrally scheduling hardware resources and computing power.

According to ResearchInChina, there are three methods to implement vehicle operating system:

Method 1, Huawei:

In April 2023, Huawei launched iDVP Intelligent Digital Vehicle Platform (i.e., vehicle operating system), which is a digital base designed based on SOA architecture, integrating functions of Huawei's various domain operating systems (AOS, HOS, and VOS), and realizing decoupling of software and hardware through atomic service layer, thus realizing rapid adaptation for cross-model development.

In 2023, representative model were AITO M9 and Luxeed S7, whose Toulin chassis is developed based on iDVP and realizes centralized and collaborative control of vehicle driving, braking, steering, and suspension through native applications such as HUAWEI xMotion configured with iDVP. In 2024, iDVP platform is scheduled to launch seven vehicles.

Method 2, NIO:

In September 2023, NIO released vehicle operating system "SkyOS", using self-developed microkernel and Hypervisor to replace QNX kernel service. SkyOS is divided into four modules, of which SkyOS-M module is based on a self-developed microkernel and has strong real-time performance and security. Its microkernel architecture is equipped with Hypervisor system for cockpit-driving integration, which is installed on NIO NT 3.0 platform; SkyOS-L module uses a self-developed middleware platform to replace AUTOSAR solution.

During OS development, NIO has released a number of technologies, including those for realizing task scheduling on multi-core processing system and improving task scheduling efficiency. Among them, multi-layer scheduling model is adopted for scheduling target tasks on multi-core processing system. equipped with fair round robin algorithm/most idle priority algorithm, etc., the vehicle operating system is able to coordinate hardware resources (computing power, sensors) under different working conditions by means of perception function groups.

Linux, Harmony, SkyOS and other operating systems use different scheduling methods for multitasking, and evolved from initial unified scheduling to multi-layer scheduling, which improves processing efficiency, as well as security performance.

Method 3, Volkswagen:

Volkswagen VW.OS consists of SDK (Software Development Kit), reference applications, software components and configuration tools for embedded software and cloud connectivity. By working in conjunction with VW.AC and BigLoop, it forms a vehicle software development platform that realizes conversion of distributed to centralized processing methods and achieves a core architecture reduction to three in-vehicle central processors.

As of February 2023, some Porsche and Audi models already carry partial components of VW.OS 1.2 (including software updates, cloud-based data transfer, diagnosis, and data accumulation), and Volkswagen plans to roll out the full software platform as version 2.0 in 2025, with partners including BlackBerry and Microsoft.

Providers: building an OS ecosystem

OS large-scale application requires the support of a strong ecosystem. In 2023, while actively implementing vehicle operating systems, automotive OS providers will also increase expansion of OS ecosystem, including adapting to more domestic chips and establishing more upstream and downstream partners.

Upstream/downstream cooperation:

• ThunderSoft: worked closely with its subsidiary DISHUI Zhixing and Lingang section of Shanghai Pilot Free Trade Zone to set up a vehicle R&D base; in addition, ThunderSoft and Cariad, a subsidiary of Volkswagen, established Carthunder as a joint venture to cooperate in the fields of intelligent connectivity, intelligent cockpit, and operating system.

• ArcherMind Technology: established a strategic partnership with EB in AUTOSAR.

Chip:

• ThunderSoft: ThunderSoft is deeply bound to Qualcomm chips. For example, it has achieved stable operation of the LLaMA-2 13 billion parameter model on edge devices equipped with Qualcomm 8 series chip platforms, and improved competitiveness of vehicle platform products through AI large models.

• ArcherMind Technology: In 2023, ArcherMind Technology built a Hesper OS software platform solution for J5 and J6 based on Horizon TogetherROS.Auto platform. This solution adds SOA functions based on FusionDrive functions. In addition, ArcherMind Technology signed a cooperation agreement with NVIDIA to become its ecosystem software partner, providing intelligent driving vision solutions based on Orin and Xavier chips to intelligent driving-related companies.

• Build a developer ecosystem: Huawei, for example, launched HarmonyOS NEXT and provides middleware and tool chains for developers.

Table of Contents

1 Trends of Automotive OS

• 1.1 Trend 1: Changes in Underlying OS Competitive Landscape
  • 1.1.1 Market Status
  • 1.1.2 Underlying OS Market News
  • 1.1.3 WinCE Officially Exits the Market
  • 1.1.4 Linux Potential Competitiveness Strengthening
  • 1.1.5 Domestication Status
• 1.2 Trend 2: Operating System Toward Open Source Integration Stage
  • 1.2.1 China Automotive OS Open Source Plan
  • 1.2.2 Key to Open Source Integration
• 1.3 Trend 3: Vehicle OS under SOA Architecture
  • 1.3.1 Definition of Vehicle OS
  • 1.3.2 Software Layer Architecture
  • 1.3.3 Characteristics of Vehicle OS
  • 1.3.4 Evolution of Vehicle OS Development Modes
  • 1.3.5 Evolution of Vehicle OS Business Models
  • 1.3.6 Vehicle OS Layout of OEMs
  • 1.3.7 Vehicle OS Layout of Providers
  • 1.3.8 Vehicle OS Cross-domain Scheduling: Algorithm Call/Chip Adaptation
  • 1.3.9 Integration of Vehicle OS with AI Large Model
• 1.4 Trend 4: OEMs Self-developed OS
  • 1.4.1 Advantages and Risks
  • 1.4.2 Current Status
  • 1.4.3 Solution Comparison
• 1.5 Trend 5: IVI System
  • 1.5.1 Weakening of Mapping Software Function
  • 1.5.2 Changes in Market Share of Leading Providers

2 Overview of Automotive OS

• 2.1 Introduction of Automotive OS
  • 2.1.1 Definition of Automotive OS
  • 2.1.2 History of OS Installation
• 2.2 Automotive OS Classification
  • 2.2.1 Automotive OS Classification: Narrow-sense OS and Broad-sense OS
  • 2.2.2 Automotive OS Classification: Real-time and Non-real-time
  • 2.2.3 RTOS Suppliers and Product List
  • 2.2.4 Non-RTOS Suppliers and Product List
  • 2.2.5 Automotive OS Classification: Micro Kernel, Macro Kernel, and Hybrid Kernel
  • 2.2.6 Automotive OS Classification: Vehicle Control Operating System and In-vehicle Operating System
  • 2.2.7 In-vehicle OS Industry Map
  • 2.2.8 Automotive OS Market Size
• 2.3 Software Architecture
  • 2.3.1 Intelligent Vehicle Software Architecture
  • 2.3.2 Intelligent Vehicle Software Ecological Framework
  • 2.3.3 Kernel is the Core of Automotive Software Architecture
• 2.4 Business Model
  • 2.4.1 Business Model Types
  • 2.4.2 Business Models of Major Automotive Operating System Enterprises
  • 2.4.3 Automotive Operating System Development Trend and Business Model Exploration
  • 2.4.4 Basic Automotive Operating System and Business Model
  • 2.4.5 Automotive RTOS and Business Model
  • 2.4.6 Suppliers OS and Business Model
• 2.5 Basic Automotive OS
  • 2.5.1 Introduction
  • 2.5.2 Automotive Underlying OS Market Share
• 2.6 Customized Automotive OS
  • 2.6.1 Introduction
  • 2.6.2 Comparison
  • 2.6.3 Chip Vendors and Their Partners
• 2.7 ROM Automotive OS
• 2.8 Hypervisor
  • 2.8.1 Introduction
  • 2.8.2 Hypervisor Becomes an Inevitable Choice
  • 2.8.3 Comparison of Main Hypervisors
• 2.9 OSEK
  • 2.9.1 Introduction
  • 2.9.2 Architecture and Features
• 2.10 Open Organization: Covesa
  • 2.10.1 Profile
  • 2.10.2 Members
  • 2.10.3 Achievements
  • 2.10.4 Achievement Examples
  • 2.10.5 Role of Covesa
  • 2.10.6 Dynamics
• 2.11 Open Organization: AUTOSAR
  • 2.11.1 Profile
  • 2.11.2 Classification
  • 2.11.3 Members
  • 2.11.4 Classic AUTOSAR
  • 2.11.5 Adaptive AUTOSAR
  • 2.11.6 Comparison of Classic and Adaptive AUTOSAR
  • 2.11.7 Integration of Adaptive AUTOSAR and ROS
  • 2.11.8 Core of AUTOSAR
  • 2.11.9 Organization of AUTOSAR China Working Group
  • 2.11.10 Project Case of AUTOSAR China Working Group
  • 2.11.11 AUTOSAR Related Software Tool Supplier Business Model
  • 2.11.12 Vector AUTOSAR Solution Business Model
  • 2.11.13 EB AUTOSAR Solution Business Model
  • 2.11.14 Neusoft Reach AUTOSAR Solution Business Model
  • 2.11.15 Business Model of iSOFT AUTOSAR Solution
  • 2.11.16 Business Model of Jingwei HiRain AUTOSAR Solution
• 2.12 Open Organization: Autoware Foudation
  • 2.12.1 Profile
  • 2.12.2 Features of Autoware Core

3 Basic Automotive OS

• 3.1 QNX
  • 3.1.1 Profile
  • 3.1.2 Business
  • 3.1.3 QNX Real-time Operating System (Neutrino RTOS)
  • 3.1.4 QNX Neutrino RTOS Support Platform
  • 3.1.5 QNX Vehicle Application
  • 3.1.6 QNX Cockpit Software Platform Solution
  • 3.1.7 Platform for ADAS
  • 3.1.8 Safety Level
  • 3.1.9 OS for Safety
  • 3.1.10 Cockpit-driving Integrated Domain Controller
  • 3.1.11 Partners
  • 3.1.12 Dynamics
• 3.2 Linux&AGL
  • 3.2.1 Profile
  • 3.2.2 AGL Architecture
  • 3.2.3 Linux Architecture
  • 3.2.4 Iteration History
  • 3.2.5 OEM Partners
  • 3.2.6 RT-Linux
  • 3.2.7 Members
  • 3.2.8 Dynamics
• 3.3 Android
  • 3.3.1 Profile of Android & Android Automotive OS
  • 3.3.2 Android Automotive OS Features
  • 3.3.3 Underlying Architecture
  • 3.3.4 User Development
  • 3.3.5 Dynamic News
• 3.4 VxWorks
  • 3.4.1 Profile
  • 3.4.2 WindRiver Products: VxWorks
  • 3.4.2 WindRiver Products: WindRiver Linux and Wind River AUTOSAR Adaptive Software Platform
  • 3.4.2 WindRiver Products: Helix Virtualization Platform
  • 3.4.3 WindRiver VxWorks Microkernel Architecture
  • 3.4.4 Main Partners in Automotive Field
  • 3.4.5 Wind River's Dynamics in Automotive Field
  • 3.4.6 New Application: Aptiv Introduces Wind River Studio "Cloud Native" to Automotive Industry
• 3.5 AliOS
  • 3.5.1 Profile
  • 3.5.2 Architecture
  • 3.5.3 Application Layer
• 3.5.4Solutions
• 3.5.5 AliOS Drive
• 3.5.6 Cooperation between Banma Zhixing and AliOS Drive
• 3.5.7 AliOS Accessed to Large Model
• 3.5.8 Models Equipped
• 3.5.9 Dynamic News
• 3.6 Harmony OS
  • 3.6.1 Profile
  • 3.6.2 Development History
  • 3.6.3 Technical Features
  • 3.6.4 Cooperation Model with Automakers
• 3.6.5Cockpit HOS
• 3.6.6 Intelligent Driving OS: AOS
• 3.6.7 Intelligent Vehicle Control OS: VOS
• 3.6.8 Huawei Cross-domain Integrated Software Framework
• 3.6.9 CCA Architecture: VCU + 3-5 VIUs
• 3.6.9 CCA Architecture: System Framework and Full-stack Solution
• 3.6.10 Harmony Access to Large Models
• 3.6.11 Models Equipped
• 3.6.12 Dynamic News
• 3.7 Ubuntu
  • 3.7.1 Profile
  • 3.7.2 Historical Versions
  • 3.7.3 Application
  • 3.7.4 Cooperation in Automotive Field
• 3.8 ROS
  • 3.8.1 Profile
  • 3.8.2 Introduction to ROS 2.0
  • 3.8.3 ROS 2.0 Iteration
  • 3.8.4 ROS 2.0 Architecture
  • 3.8.5 Application Cases
• 3.9 webOS
  • 3.9.1 Development History
  • 3.9.2 OSE Components and Development Roadmap
  • 3.9.3 Integration with AGL
  • 3.9.4 Dynamics in Automotive Field

4 Hypervisor

• 4.1 Profile
  • 4.1.1 Definition
  • 4.1.2 Comparison of Main Hypervisors
  • 4.1.3 Status Quo of Hypervisor Industry
  • 4.1.4 Application of Intelligent Cockpit Hypervisors in China
  • 4.1.5 Prospects of Global Automotive Hypervisor Market
  • 4.1.6 Global Hypervisor Suppliers and Their Product Lists
  • 4.1.7 Chinese Hypervisor Suppliers and Their Product Lists
  • 4.1.8 Automotive Virtual Machine Management System Business Model
• 4.2 QNX Hypervisor
  • 4.2.1 Profile
  • 4.2.2 Architecture
  • 4.2.3 Solutions
• 4.3 ACRN
  • 4.3.1 Profile
  • 4.3.2 Composition
• 4.4 COQOS Hypervisor
  • 4.4.1 COQOS Hypervisor
  • 4.4.2 COQOS Hypervisor SDK
  • 4.4.3 Mixed VIRTIO / Non-VIRTIO Architectures
  • 4.4.4 "Next Gen COQOS" Heterogeneous Cores
• 4.5 PikeOS
• 4.6 EB Corbos Hypervisor
• 4.7 Harman Device Virtualization
• 4.8 VOSYSmonitor
• 4.9 ZlingSmart Hypervisor

5 Broad-sense Automotive OS and Enterprises

• 5.1 Neusoft Reach NeuSAR
  • 5.1.1 Intelligent Connected Vehicle Business Layout
  • 5.1.2 Introduction to NeuSAR
  • 5.1.3 Dynamics of NeuSAR
  • 5.1.4 Main Products
  • 5.1.5 Vehicle Operating System
  • 5.1.6 Neusoft Reach Domain Controller Software Development Platform: NeuSAR DS
  • 5.1.7 NeuSAR Security Levels
• 5.2 ThunderSoft
  • 5.2.1 Profile
  • 5.2.2 Business
  • 5.2.3 DISHUI OS
  • 5.2.4 Combination between Rubik Large Model and OS
  • 5.2.5 OS Projects
  • 5.2.6 SOA Middleware
• 5.3 ETAS
  • 5.3.1 Vehicle Solutions
  • 5.3.2 Cloud Native Software Platform
• 5.4 ArcherMind Technology
  • 5.4.1 Profile
  • 5.4.2 Main Products
  • 5.4.3 Subsidiary: Arraymo
  • 5.4.4 Operating System: FusionOS
  • 5.4.5 Cooperate with Horizon on Intelligent Driving Domain OS Platform
  • 5.4.6 Fusion Matrix
  • 5.4.7 FusionDrive: Some IP Products and Smart Gateways
  • 5.4.8 Architecture for Some IP Integration with TogetheROS.Auto
  • 5.4.9 J5-based SomeIP Fusion Architecture
  • 5.4.10 J5-based FusionDrive Diagnosis
  • 5.4.11 Partners
• 5.5 EB
  • 5.5.1 Profile and Products Introduction
  • 5.5.2 J5-based Intelligent Driving Domain OS
• 5.6 AICC
  • 5.6.1 Profile
  • 5.6.2 AICC Promotes the Automotive OS Standard
  • 5.6.3 ICVOS: Intelligent Connected Vehicle OS
  • 5.6.4 ICVOS: Software Architecture /Development Architecture /SDK Architecture
  • 5.6.5 ICVOS: Vehicle-cloud Collaboration
  • 5.6.6 ICVOS: Basic Information Security Platform
  • 5.6.7 ICVOS: Software Architecture Development Case with OEM
• 5.7 NVIDIA DRIVE OS
  • 5.7.1 Profile
  • 5.7.2 Drive OS SDK Architecture
• 5.8 Baidu DuerOS
  • 5.8.1 Profile
  • 5.8.2 Features
  • 5.8.3 Application Scenarios and Customers
  • 5.8.4 Software Architecture
  • 5.8.5 Baidu DuerOS Accesses to Large Model
  • 5.8.6 Baidu Vehicle OS Plan
• 5.9 Apex.AI
  • 5.9.1 Profile
  • 5.9.2 Dynamics
  • 5.9.3 Apex.OS Features
  • 5.9.4 Apex.OS Extension Kit
  • 5.9.5 Apex.OS Tool Architecture
• 5.10 iSOFT Infrastructure Software
  • 5.10.1 Profile
  • 5.10.2 Development Course
  • 5.10.3 Product and Service
  • 5.10.4 AUTOSAR CP+AP Integrated Solution
  • 5.10.5 OS Architecture
  • 5.10.6 Vehicle OS Architecture
  • 5.10.7 Orientais
  • 5.10.8 Open-source Microkernel
• 5.11 ZlingSmart
  • 5.11.1 Profile
  • 5.11.2 RAITE OS
• 5.12 ZTE GoldenOS
  • 5.12.1 Micro kernel and Macro kernel Technology Architecture
  • 5.12.2 Vehicle Control OS Solution
  • 5.12.3 Intelligent Cockpit OS Solution
  • 5.12.4 Intelligent Driving OS Solution
  • 5.12.5 Cooperation of Neusoft Reach + ZTE + SemiDrive Technology
  • 5.12.6 Introduction of NewStart OS
  • 5.12.7 Development History of NewStart
  • 5.12.8 NewStart's Intelligent Cockpit OS Solution
• 5.13 ECARX
  • 5.13.1 Product Introduction
  • 5.13.2 Ecological Cooperation
• 5.14 Others
  • 5.14.1 RT-Thread
  • 5.14.2 Enjoy Move Technology: EMOS
  • 5.14.3 KOTEI Information: Kcar-OS
  • 5.14.4 PATEO Qing OS
  • 5.14.5 STEP

6 Vehicle OS of OEMs

• 6.1 Tesla OS
  • 6.1.1 Introduction to Tesla OS
  • 6.1.2 Tesla: Cloud OS
• 6.2 NIO SkyOS
  • 6.2.1 Introduction
  • 6.2.2 SkyOS Architecture
  • 6.2.3 NIO Vehicle OS Scheduling Algorithm
  • 6.2.4 Adapted Chips
• 6.3 Xiaomi Hyper OS
  • 6.3.1 Introduction
  • 6.3.2 OS Development History
  • 6.3.3 Architecture Design
  • 6.3.5 Access to Large Model
  • 6.3.6 Adopting Nuttx Kernel
• 6.4 Li Auto
  • 6.4.1 Li OS Architecture
  • 6.4.2 Self-developed Chips Status
• 6.5 Xpeng Motor XsmartOS
  • 6.5.1 X-EEA2.0 Architecture
  • 6.5.2 X-EEA3.0 Key Technologies
  • 6.5.3 Next Steps
• 6.6 Leap Motor
  • 6.6.1 Four-domain Fusion Architecture
  • 6.6.2 Intelligent Driving OS

7 OS of Other OEMs

• 7.1 Volkswagen VW.OS
  • 7.1.1 Introduction
  • 7.1.2 Development History
  • 7.1.3 Features
  • 7.1.4 Overall Layout of Software
  • 7.1.5 Roadmap - Hardware, Software to be Unified
  • 7.1.6 E³ 2.0 EEA: CARIAD Software Platform
• 7.2 Toyota Arene OS
  • 7.2.1 Introduction
  • 7.2.2 Ecological Resources
  • 7.2.3 Functions
• 7.3 BMW
  • 7.3.1 Mass-produced EEA: Software System Development Evolution
  • 7.3.2 BMW iDrive
• 7.4 Mercedes-Benz MB OS
  • 7.4.1 Function Introduction
  • 7.4.2 Architecture
  • 7.4.3 Recent Developments
• 7.5 FAW.OS
  • 7.5.1 Architecture
  • 7.5.2 Features
• 7.6 SAIC Z-ONE Intelligent Vehicle Cloud-Management-End Full Stack Solution-SOA Software Platform
• 7.7 GAC Psi OS
  • 7.7.1 Architecture
  • 7.7.2 Application
• 7.8 Geely
  • 7.8.1 VolvoCars.OS
  • 7.8.2 Flyme OS
  • 7.8.3 SOA-based OS - GeelyOS
  • 7.8.4 ZEEKR OS
• 7.9 Great Wall Motor
  • 7.9.1 GEEP 4.0 Quasi-Central EEA: SOA Software Framework
  • 7.9.2 Coffee OS
  • 7.9.3 GEEP 5.0 Central Computing EEA
• 7.10 Changan RTDriveOS
  • 7.10.1 Architecture
  • 7.10.2 Next Steps
• 7.11 CHERY-OS
  • 7.11.1 Architecture
  • 7.11.2 Applications
• 7.12 Dongfeng
  • 7.12.1 Vehicle OS Architecture
  • 7.12.2 Vehicle OS Development Route
• 7.13 BYD OS

관련자료