SDV(Software-Defined Vehicles) : SOA 및 미들웨어 산업(2025년)

Research on automotive SOA and middleware: Development towards global SOA, cross-domain communication middleware, AI middleware, etc.

With the implementation of centrally integrated EEAs, OEM software architectures are evolving towards global SOAs

In the context of software-defined vehicles, automotive architectures are evolving towards centralized EEAs, and SOA design has become the best choice for the next generation of automotive software architectures. Many OEMs continue to strengthen their layout in SOAs and their core middleware.

At the same time, automotive SOAs are spreading from domain controllers to centrally integrated vehicles. Global SOAs allow any application to call any service anywhere, achieving complete vertical and horizontal decoupling of systems.

The operating system layer of Changan SDA is based on SOA. On the integrated and high-real-time EEA with hardware and software, Changan SDA's middleware and application layers decouple software and hardware, and have implemented more than 3,000 vehicle-defined service buses, including more than 1,000 I/O abstract standardized software and hardware interfaces, more than 500 atomic services, more than 200 enhanced services, and more than 200 scenario services. It has also established a replicable and portable standard system, improving the efficiency of new function development by more than 30%.

In 2024, NIO released its full-stack self-developed SkyOS. Its self-developed SOA framework can best provide fast service discovery, reliable remote calls, high-bandwidth communication, precise access control and flexible deployment. SkyOS uses the self-developed SOA framework to abstract more than 1,600 atomic capabilities of the vehicle and call them in the form of APIs for different applications in different domains.

when designing the SOA framework, NIO defines a high-performance cross-domain communication protocol named TOX, which means Talks Over X, that is, it can be applied to all types of networks and all communication terminals.

Under the trend of cross-domain integration, the focus is on the deployment of unified middleware for the vehicle

As EEAs continue to develop towards central integration and cross-domain integration, automotive software can no longer effectively satisfy novel automotive architectures. Driven by the demand of OEMs, major suppliers have launched unified communications middleware that meets SOA requirements to enable cockpit-driving integrated product layout.

In order to deploy cross-domain integration better, Xpeng has built a unified communication middleware for the vehicle, including system security middleware, data security middleware, functional safety, vehicle OTA, vehicle SOA, middleware, etc. With such vehicle communication middleware, cockpit applications and autonomous driving applications are immune to differences or changes in hardware platforms, thus greatly improving research and development efficiency and speed. After the middleware is unified, the service-oriented or atomized capabilities will be further enhanced.

In February 2025, STEP released a cross-platform and cross-domain vehicle service communication framework dubbed VFB, which features unified multi-domain software technology, efficient cross-domain service collaboration, and rapid response to changing demand. Through centralized service governance, VFB achieves efficient collaboration and unified management between different functional domains (such as central gateway, intelligent driving, cockpit system, etc.), ensuring the consistency and efficiency of services, greatly improving system integration efficiency, reducing cross-domain communication friction, simplifying the construction of a vehicle SOA-based system, and greatly improving development efficiency. VFB can efficiently adapt to multiple models and multiple EEAs, facilitating the quick realization of the vehicle SOA platform.

In December 2024, Vector launched System Gateway, a system routing system adapted to third-party protocol stacks, to help customers apply different middleware products to cross-domain integration platforms. It enables communication between IP and ROS/DDS, between SOME/IP and Android, etc..

From the perspective of Vector's system design, there are many ecosystems and software on top of the SoC, and cross-ecosystem communication is done through "IPC" which can cross processes, chips or containers, depending on the specific project scenario. MICROSAR Adaptive is a general, automotive-grade solution that can be applied to most microprocessors. For third-party ecosystems, Vector achieves integration through System Gateway, which is in blue in the figure below.

The integration trend of AI foundation models and automotive middleware

With their application and penetration in the automotive industry, AI foundation models have improved the capabilities to automotive software systems and put forward new requirements for vehicle software systems. In 2025, automotive software is expected to see the integration of AI foundation models and middleware.

For vehicle software architectures, the software system middleware layer of AI foundation models has been fully upgraded. At the public library level, AI-related content such as security, RAG (retrieval-augmented generation ), vector databases, and reasoning engines have been added to build a unified reasoning framework, SDK (software development kit) and interface. The framework layer also incorporates many AI elements. For example, multimodal foundation model service knowledge bases, intelligent agent services, model management, edge-cloud collaborative services, distributed AI services, etc., provide all-round support for the development and operation of AI applications.

In October 2024, AUTOSEMO released the latest "China Automotive Basic Software Development Report 5.0", which proposed that with the help of AI foundation models, automotive basic software platforms will evolve to the open software architectures, which mainly consist of ASF middleware and standard middleware, of AI foundation models. In addition to cross-domain SOA middleware, ASF middleware also integrates middleware products such as AI foundation models/application frameworks to help in-depth development of AI models on vehicles.

In 2024, Changan Automobile added an AI service framework to the SDA software and actively integrated other architecture layers, including a new AI service layer, AI data services, AI scheduling, AI interface adaptation, and local model reasoning. The AI perception layer and AI actuation layer are integrated into the hardware layer to support computing and offer data collection and output services. The AI application layer is integrated into the vehicle function layer to provide AI application services. The hardware, data, framework, and algorithm layers are integrated into the cloud big data layer to offer massive AI data resources and train AI models.

In January 2025, Geely released the "Global Smart Car AI" technology system, which revolves around AI OS. Downward is the model layer and basic layer content contained in AI OS, and upward is terminal devices. For example, it is used for smart cars on the C-end, and serves R&D, production and other machine and enterprise management software on the B-end. It can be understood that AI OS is a platform that can flexibly adapt to various terminals, ensuring system security and user privacy while achieving efficient resource management and task scheduling.

At the same time, the AI OS scheduling engine enables the seamless cross-terminal flow of foundation model functions and services. In the entire product ecosystem, a unified all-causal intention understanding framework can integrate the needs and perception data of multiple devices such as vehicles, mobile phones, tablet PCs, wearable devices, smart homes, and other forms of embodied agents.

Table of Contents

1 Definition and Evolution of Automotive SOA

• 1.1 Definition
• Definition
• Main Features
• Main Technical Features
• Main Components
• Main Functional Modules
• Main Advantages
• 1.2 Differences between SOA and Signal-oriented Architecture
• Comparison
• Design Differences (1)
• Design Differences (2)
• Cockpit Software
• Examples of Differences
• 1.3 SOA and Middleware Evolution 1
• 1.4 SOA and Middleware Evolution 2
• 1.5 SOA and Middleware Evolution 3
• 1.6 SOA and Middleware Evolution 4
• 1.7 SOA and Middleware Evolution 5
• 1.8 SOA and Middleware Evolution 6
• 1.9 SOA and Middleware Evolution 7
• 1.10 SOA and Middleware Evolution 8
• 1.11 SOA and Middleware Evolution 9
• 1.12 SOA and Middleware Evolution 10
• 1.13 SOA and Middleware Evolution 11

2 OEM SOA and Middleware Supply Chain

• 2.1 Relationship between SOA and Middleware Supply Chain of Major OEMs
• Xpeng
• 2.2 SOA and Middleware Software Supply Models
• Suggestions on Industrial Division of Labor for SOA
• OEM SOA and Middleware Software Layout Methods
• Classification of Automotive Middleware Suppliers
• Main Automotive Middleware Business Models
• OEM Middleware Layout Methods
• Model 1:
• Model 2:

3 SOA and Middleware Layout of Major Suppliers

• 3.1 Evolution of SOA Software Layout
• Huawei
• Neusoft Reach
• 3.2 SOA Communication Middleware Layout
• Definition of Automotive SOA Middleware
• Classification of Automotive SOA Middleware
• Automotive SOA Communication Middleware
• Automotive Communication Middleware Protocol: SOME/IP&DDS
• Automotive Communication Middleware Protocol: MQTT
• Automotive Communication Middleware Protocol: Unified Communication Middleware
• Automotive SOA Communication Middleware
• Automotive Communication Middleware: DDS
• Automotive Communication Middleware: SOME/IP
• Automotive Middleware: MCAL
• 3.3 Automotive SOA Framework Middleware Layout
• Automotive SOA Framework Middleware
• 3.4 Automotive AI Foundation Model Middleware Layout
• Automotive AI Foundation Model Middleware
• 3.5 SOA-based Intelligent Driving Middleware
• Automotive Middleware: Autonomous Driving Middleware
• 3.6 SOA-based Vehicle Control and Other Functional Middleware Layout
• Vehicle Control Middleware
• 3.7 Automotive Basic Standard Middleware Layout
• AUTOSAR
• 3.8 Automotive Underlying Kernel Operating System Layout
• Automotive SOA Software Platform - Underlying Operating System Kernel (1)

4 Automotive SOA and Middleware Application Scenarios

• 4.1 SOA Development and Design Process
• Main Steps for OEMs to Implement SOA
• Main Capabilities That OEMs Need to Implement Automotive SOA
• Automotive SOA Development Methods
• SOA Development and Toolchain Based on CP AUTOSAR
• SOA Development and Toolchain Based on AP AUTOSAR
• Automotive Service-based Function Development Process
• Automotive Service-based Function Development Process
• Model-based SOA Development Methods
• Automotive SOA Connected Security Design
• Case (1)-(6)
• 4.2 Central Computing Platform Scenarios Based on SOA Design
• SOA-based Automotive Heterogeneous Central Computing Platform Software Design Solution (1)
• SOA-based Automotive Heterogeneous Central Computing Platform Software Design Solution (2)
• SOA-based Automotive Heterogeneous Central Computing Platform Software Design Solution (3)
• Case (1)-(6)
• 4.3 Intelligent Driving Scenarios Based on SOA Design
• Intelligent Driving System Solutions Based on SOA
• Cases......
• 4.4 Intelligent Cockpit Scenarios Based on SOA Design
• Cases......
• 4.5 Intelligent Vehicle Control Scenarios Based on SOA Design
• Cases......
• 4.6 Other Scenarios Based on SOA Design
• Geely Zeekr's SOA-based OTA Solution
• ABUP's Service-oriented OTA Solution
• Automotive Functional Safety Development Based on SOA
• SOA Communication Process

5 SOA and Middleware Application of Major OEMs

• 5.1 Xpeng
• SOA and Middleware Layout
• Evolution of SOA and Middleware Layout
• Vehicle-cloud SOA Middleware Platform
• Cross-domain Fusion Deployment of Vehicle Unified Middleware
• SOA Communication Middleware
• Hardware Sharing Cases under SOA
• SOA and SaaS
• SOA Application Software Development
• Left/Right ZCU SOA Evolution
• Left/Right ZCU SOA
• 5.2 NIO
• SOA and Middleware Layout
• Evolution of SOA and Middleware Layout
• SkyOS: A Global Operating System Based on SOA
• SkyOS Middleware
• Self-developed SOA Framework
• TOX Communication Protocol
• Software Development Toolchain
• Cockpit Subsystem Digital Architecture: SOA
• SkyOS-C atomization framework for cockpit subsystem
• Zone control software SOA
• SOA software for the latest EE architecture of NIO
• 5.3 Li Auto
• SOA and Middleware Layout
• Evolution of SOA and Middleware Layout
• Evolution of SOA and Middleware Layout
• 5.4 Leapmotor
• SOA and Middleware Layout
• Evolution of SOA and Middleware Layout
• SOA
• Vehicle OS
• Latest integrated EEA software architecture
• 5.5 Dongfeng Voyah
• Evolution of SOA and Middleware Layout
• "Tianyuan" centralized architecture design: SOA software architecture
• Vehicle OS
• "Tianyuan" centralized architecture design: SOA software architecture
• Created a developer platform
• Intelligent driving system based on SOA
• ICA service layering
• 5.6 Xiaomi Automobile
• SOA and Middleware Layout
• Evolution of SOA and Middleware Layout
• SOA Technology
• Automotive Central Computing Platform Based on SOA
• Communication Methods under Vehicle Control SOA
• SOA Technology
• Composition of HyperOS
• 5.7 SAIC
• SOA and Middleware Layout
• Evolution of SOA and Middleware Layout
• Supply Chain of Z-One "Galaxy" Cockpit-driving Integrated SOA Full-Stack Software and Hardware Solution
• Z-One "Galaxy" Cloud-link-edge Integrated SOA Software Platform
• Features of Cloud-link-edge Integrated SOA Software Platform of Z-One "Galaxy" Full-stack 3.0
• Z-One Cloud-link-edge Integrated SOA Software Platform
• Composition of Z-One Cloud-link-edge Integrated SOA Software Platform: Basic Middleware
• Composition of Z-One Cloud-link-edge Integrated SOA Software Platform: Functional Middleware
• Composition of Z-One Cloud-link-edge Integrated SOA Software Platform: Developer Platform
• Z-One "Galaxy" Cloud-link-edge Integrated SOA Software Platform
• Z-One "Galaxy" Intelligent Operating System: ZOS
• Z-One AI OS
• Z-One Explores Smart Cockpits Scenario Applications Based on Integration of SOA+LLM
• 5.8 GAC
• SOA and Middleware Layout
• Evolution of SOA and Middleware Layout
• Psi OS Based on SOA Cross-domain Service Engine
• Development Model of Psi OS
• SOA Software Platform of "X-Soul"
• 5.9 BYD
• SOA and Middleware Layout
• Evolution of SOA and Middleware Layout
• 5.10 FAW
• Hongqi's SOA and Middleware Layout
• Evolution of Hongqi's SOA and Middleware Layout
• SOA of HIS Based on Central Computing Platform
• Software Architecture of FAW.OS
• Hongqi Intelligent HIS Architecture Developer Platform
• SOA-based Cockpit Platform
• Vehicle SOA Platform Construction
• 5.11 Chery
• SOA and Middleware Layout
• Evolution of SOA and Middleware Layout
• EEA based on SOA Software Layered Design
• CHERY-OS Architecture
• Autonomous Driving Domain Controller SOA
• SOA Design Case
• 5.12 Great Wall Motor
• SOA and Middleware Layout
• Evolution of SOA and Middleware Layout
• EEA SOA Layout
• SOA of GEEP 4.0
• 100% SOA of GEEP 5.0
• Central Computing SOA
• Cockpit System Architecture
• 5.13 Changan Automobile
• SOA and Middleware Layout
• Evolution of SOA and Middleware Layout
• SDA Based on SOA
• Service-oriented Software Platform
• Service-oriented Intelligent Driving System
• Cockpit-driving Integration of SOA Services
• Service-oriented Communication (SOMEIP&DDS) Design
• Vehicle Control Software Development Practice Based on SOA
• 5.14 Geely
• SOA and Middleware Layout
• Evolution of SOA and Middleware Layout
• SOA-based OS - GeelyOS
• Full-domain AI OS
• Service Library Construction of SOA Ecosystem
• Full-stack Self-developed Basic Software Platform: GOS
• The Basic Software Platform Uses SOA to Decouple Software Services
• Communication Management Module Mechanism of GOS
• GOS - Multi-protocol Multi-OS Compatibility
• GOS - Developer Platform and Toolchain
• 5.15 ZEEKR
• Evolution of SOA and Middleware Layout
• Ark Operating System
• Ark Operating System Middleware
• Automotive Platform Shared by Multiple Models
• OTA Solution Based on SOA
• 5.16 BMW
• SOA Solution Design in the Next-generation EEA
• Zonal Controller Design in the Next-generation EEA
• Next-generation Software Architecture Based on the Latest EEA
• 5.17 Mercedes-Benz
• MB.OS
• STAR3 Service-oriented Communication Method
• 5.18 Volkswagen
• Key Technologies of SOA
• SOA Design
• Automotive Application Service Architecture of MEB Platform
• SOA Communication Method
• ICAS3 Intelligent Cockpit Domain, System Architecture
• Software Platform Development Plan
• China's Latest CEA Layout
• 5.19 Volvo
• SPA2 Introduces SOA (1)
• SPA2 Introduces SOA (2)
• SPA2 Introduces SOA (3)
• 5.20 Stellantis
• STLA Brain: Quasi-central EEA and Software Architecture

6 Chinese Automotive SOA Design and Middleware Suppliers

• 6.1 Huawei
• Evolution of Automotive Software (such as SOA and Middleware) Layout
• SOA-based Product: iDVP Intelligent Digital Base Software Framework
• SOA-based Product: Qiankun iDVP2.0 Intelligent Digital Base Software Framework
• iDVP Intelligent Digital Base Toolchain Products
• iDVP Intelligent Digital Base Supply Model
• Vehicle-level Basic SOA
• SOA: Core Concept Service-oriented Layered Decoupling
• Core Composition of SOA
• Development Model Features of SOA
• Intelligent Driving SOA and SaaS
• SOA Development Practice: Challenges
• SOA Development Practice: Solutions
• 6.2 Neusoft Reach
• Automotive SOA and Middleware Layout
• Iteration of NeuSAR
• SOA Solution
• NeuSAR OS
• NeuSAR Service Famework Middleware
• NeuSAR VMB
• NeuSAR AI Framework Middleware
• Basic Software Product: cCore
• Basic Software Product: aCore
• Lightweight Basic Software: NeuSAR CP-Lite
• openVOC Open Technology Framework
• Python+WebService Development Framework
• 6.3 Jingwei Hirain
• Evolution of Automotive Software (such as SOA and Middleware) Layout
• Vehicle OS
• Vehicle OS Toolchain
• Automotive SOA Technology Layout
• SOA Solution
• SOA Practice Based on AUTOSAR Technology
• Autonomous Vehicle Architecture Based on SOA
• MCAL Products
• AUTOSAR DDS
• 6.4 Thundersoft
• Evolution of Automotive Software (such as SOA and Middleware) Layout
• AquaDrive OS
• Ecological Cooperation of AquaDrive OS
• Cockpit-driving integration Design of AquaDrive OS
• Cross-domain Integration Promotes the Evolution of Automotive Operating System
• Software-defined Vehicle Business Layout
• Main Software Tools and Services for Software-defined Vehicle Business
• SOA Middleware
• 6.5 E-Planet Technologies (EPT)
• Evolution of Automotive Software (such as SOA and Middleware) Layout
• SOA Performance and Stability Automated Testing System
• SOA End-to-end Engineering Model
• SOA End-to-end Engineering Model Service Type
• SOA Design and Communication Solution
• SOA Software Solution
• Vehicle Control and Vehicle Equipment Middleware Solution
• SOME/IP Protocol Stack
• 6.6 UAES
• Evolution of Automotive Software (such as SOA and Middleware) Layout
• Evolution of USP
• USP 2.0
• USP Cores
• USP Tools
• Development Kit Based on MATLAB/Simulink
• USP Developer Verification Bench
• Vehicle-cloud Integrated Centralized Architecture Solution
• Automotive DDS Solution
• 6.7 EnjoyMove Technology
• Evolution of Automotive Software (such as SOA and Middleware) Layout
• Development and Evolution of EMOS
• EMOS
• XCG Gen 1
• TSN protocol stack
• 6.8 ArcherMind Technology
• Evolution of Automotive Software (such as SOA and Middleware) Layout
• Fusion OS
• Central Control Domain Software Platform: FusionWise3.0
• FusionWise Middleware
• SOA Framework Products
• AUTOSAR Product
• Fusion 3.0
• Intelligent Driving Domain Software Platform: FusionDrive2.0
• 6.9 Kotei
• Evolution of Automotive Software (such as SOA and Middleware) Layout
• Global Full-stack Solution for Automotive Software System
• Cross-domain SOA Middleware
• AI Enhanced Toolchain
• Distributed Communication Middleware
• Deep Cooperation with Customers
• Software R&D Model Evolution
• SDW 2.0
• 6.10 Megatronix
• Evolution of Automotive Software (such as SOA and Middleware) Layout
• Automotive Distributed Intelligent Operating System
• Business Model

7 Foreign Automotive SOA Design and Middleware Suppliers

• 7.1 Bosch ETAS
• Evolution of Automotive Software (such as SOA and Middleware) Layout
• End-to-end Vehicle Solution
• End-to-end Vehicle OS Solution
• ETAS Deterministic Middleware Solution (EDMS)
• TTS Deterministic Scheduling Middleware
• Edge Middleware
• End-to-end Vehicle OS Solution
• 7.2 Continental Elektrobit
• Evolution of Automotive Software (such as SOA and Middleware) Layout
• Automotive Basic Software Products
• SOA Middleware Solution
• Automotive Basic Software Products
• EB corbos Link
• EB zoneo
• EB zoneo GatewayCore
• Automotive HPC Software Architecture
• Software Platform for Next-generation Automotive Electronics Architecture: EB xelor
• "Software Functions and Products" for Body Domain and Actuators
• 7.3 Vector
• Automotive Operating System
• APP Cross-domain Fusion Deployment Tools
• Cross-domain Fusion Third-party Communication Middleware Fusion Solution
• System Routing Application Case
• SOA Design Based on PREEvision
• 7.4 Aptiv
• Evolution of Automotive Software (such as SOA and Middleware) Layout
• Automotive Software Technology
• Cloud Native Middleware and Development Products
• Middleware Composition
• Evolution of Intelligent Driving System Architecture Layout
• Evolution of Intelligent Driving System Architecture Layout
• Intelligent Driving System Software Middleware
• Trends of Scalable and Modular Intelligent Driving System Software
• Sixth-generation ADAS Platform Architecture
• SOA-based Zonal Controller Software Architecture
• 7.5 TTTech AUTO
• Evolution of Automotive Software (such as SOA and Middleware) Layout
• Motionwise Middleware Function Comparison
• SOA Software Solution
• MotionWise Schedule
• Main Components of MotionWise Schedule
• Development Process of MotionWise Schedule
• Zetta Auto
• Technology Framework of Zetta Auto
• Solution Framework of Zetta Auto
• Dynamics
• 7.6 GUARDKNOX
• Automotive SOA Products