SOME/IP Protocol Stack
Self-developed SOME/IP protocol stack supporting service discovery, service invocation, event publish/subscribe, and access control, aligned with the AUTOSAR Adaptive standard.
>EV-Runner SOA Communication Middleware - End-to-end SOA middleware for cross-domain, in-domain and local communication in intelligent vehicles.
Core Features - End-to-end SOA communication middleware covering cross-domain, in-domain and local IPC
FDBus Intra-Domain Soft Bus
High-performance intra-domain communication bus supporting automatic fallback across IPC, VSOCK, and network IPC — the industry's first SOA communication framework to support VSOCK.
SOME/IP-FDBus Protocol Gateway
Bidirectional mapping between cross-domain SOME/IP services and intra-domain FDBus services, enabling a unified development and invocation model across vehicle-level and domain-level services.
IDL Interface Definition & Code Generation
Supports both ARXML and Protobuf interface definition formats, automatically generating cross-platform communication code and JavaBean classes to accelerate Android application integration.
Notification Center
System-level event distribution based on the FDBus publish/subscribe model, handling global notifications such as time changes, network status, and USB events, with topic identification and latest-value caching.
Access Control (IAM)
Built-in service access security policies with service-level permission control, ensuring critical vehicle services are protected from unauthorized invocation.
Features & Advantages - Designed for production, focused on performance, reliability and cross-platform compatibility
End-to-End SOA Communication
From IDL definition and code generation to service discovery and cross-domain gateway, a unified vehicle SOA communication system that eliminates cross-team interface collaboration barriers.
High Performance, Low Latency
Zero-copy communication and self-developed scheduling framework meet the high-bandwidth, low-latency demands of ADAS and cockpit applications.
Multi-Platform Support
Full support for QNX, Android, Generic Linux and Windows, covering cockpit, ADAS, TBox, gateway and zone controller nodes.
Production-Proven
Deployed in multiple mass-production models from leading OEMs with complete SOP validation and long-term operational stability.
Unified Development Model
Cross-domain, in-domain and local applications use the same interface definition and invocation pattern, reducing learning curves and improving team collaboration.
Self-Developed Full Stack
Core protocol stacks, software bus, code generation tools and integration capabilities are developed in-house for flexible customer platform adaptation.
Case Studies - Proven in production across smart cockpit and cockpit-driving fusion scenarios
Smart Cockpit
QNX + Android Cockpit SOA Platform
EV-Runner connects underlying vehicle capabilities with upper cockpit services. SOME/IP connects external Ethernet nodes, FDBus handles in-domain services and IPC, and Protocol Buffer IDL standardizes service interfaces. Upper-layer applications maintain stable invocation even when hardware or underlying implementations change.
Cockpit-Driving Fusion
More Case Studies
EV-Runner has been widely deployed and validated in numerous mass-production projects spanning autonomous driving, smart cockpit and TBox applications. As the core communication bus, it bridges intra-system, inter-VM, SoC-to-SoC and ECU-to-ECU communication, ensuring stable and reliable end-to-end SOA regardless of networking, interaction or architectural complexity.