Dublin, May 05, 2025 (GLOBE NEWSWIRE) -- The "Software-Defined Vehicles in 2025: SOA and Middleware Industry Research Report" has been added to ResearchAndMarkets.com's offering.
The automotive software landscape is transforming with the shift towards Service-Oriented Architectures (SOA) and middleware innovation. As OEMs embrace centrally integrated Electrical and Electronic Architectures (EEAs), global SOAs promote seamless inter-application communication through complete system decoupling.
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.
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..
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 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.
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.
Key Topics Covered:
Definition and Evolution of Automotive SOA
- Main Features
- Main Technical Features
- Main Components
- Main Functional Modules
- Main Advantages
- Differences between SOA and Signal-oriented Architecture
- Comparison
- Design Differences
- Cockpit Software
- Examples of Differences
- SOA and Middleware Evolution
OEM SOA and Middleware Supply Chain
- Relationship between SOA and Middleware Supply Chain of Major OEMs
- Xpeng
- 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
SOA and Middleware Layout of Major Suppliers
- Evolution of SOA Software Layout
- Huawei
- Neusoft Reach
- 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
- Automotive SOA Framework Middleware Layout
- Automotive SOA Framework Middleware
- Automotive AI Foundation Model Middleware Layout
- Automotive AI Foundation Model Middleware
- SOA-based Intelligent Driving Middleware
- Automotive Middleware: Autonomous Driving Middleware
- SOA-based Vehicle Control and Other Functional Middleware Layout
- Vehicle Control Middleware
- Automotive Basic Standard Middleware Layout
- AUTOSAR
- Automotive Underlying Kernel Operating System Layout
- Automotive SOA Software Platform - Underlying Operating System Kernel
Automotive SOA and Middleware Application Scenarios
- SOA Development and Design Process
- Main Steps for OEMs to Implement SOA
- Model-based SOA Development Methods
- Intelligent System Scenarios Based on SOA Design
- Automotive Functional Safety Development Based on SOA
SOA and Middleware Application of Major OEMs
- Xpeng
- NIO
- Li Auto
- Leapmotor
- Dongfeng Voyah
- Xiaomi Automobile
- SAIC
- GAC
- BYD
- FAW
- Chery
- Great Wall Motor
- Changan Automobile
- Geely
- ZEEKR
- BMW
- Mercedes-Benz
- Volkswagen
- Volvo
- Stellantis
Chinese Automotive SOA Design and Middleware Suppliers
- Huawei
- Neusoft Reach
- Jingwei Hirain
- Thundersoft
- E-Planet Technologies (EPT)
- UAES
- EnjoyMove Technology
- ArcherMind Technology
- Kotei
- Megatronix
Foreign Automotive SOA Design and Middleware Suppliers
- Bosch ETAS
- Continental Elektrobit
- Vector
- Aptiv
- TTTech AUTO
- Zetta Auto
- GUARDKNOX
For more information about this report visit https://www.researchandmarkets.com/r/a7ryff
About ResearchAndMarkets.com
ResearchAndMarkets.com is the world's leading source for international market research reports and market data. We provide you with the latest data on international and regional markets, key industries, the top companies, new products and the latest trends.
