The RAPIDSEA SOME/IP (Scalable Service-Oriented Middleware over IP) stack is an industry-grade communication protocol designed for the rigorous demands of modern automotive networks. Built to replace legacy signal-based communication (like CAN) with high-bandwidth, service-oriented architecture, it enables seamless data exchange between Electronic Control Units (ECUs) over Ethernet.
Whether you are developing ADAS systems, Infotainment clusters, or Telematics units, RAPIDSEA offers a versatile, royalty-free solution that supports dynamic service discovery, serialization, and remote procedure calls (RPC) ensuring your vehicle network is future-proof.

Designed to modernize in-vehicle connectivity, RAPIDSEA SOME/IP offers a robust suite of capabilities that simplify service management. Our stack ensures seamless interoperability while maintaining the strict reliability standards required for software-defined vehicles.
Contact sales to learn moreSOME/IP enables dynamic service detection across the network, allowing ECUs to find and utilize available functionality automatically without static configuration.
This approach allows ECUs to subscribe to specific services, receiving automatic updates whenever relevant data changes or specific events occur.
This pattern facilitates synchronous communication, enabling ECUs to send specific command requests to other units and receive immediate, direct responses.
Our stack uses efficient binary serialization to compact data, significantly reducing network traffic load while improving overall throughput and performance.
Headers contain service IDs, method IDs, and payload lengths, ensuring precise data routing, clear payload definition, and effective protocol management.
Embien offers ready-to-integrate SOME/IP protocol stacks to accelerate in-vehicle communication functionality. Our solution is designed for seamless adoption into your existing development environment.
Embien’s SOME/IP stack is implemented on top of standard transport layer protocols and the Internet Protocol (IP) stack, ensuring robustness and compatibility.
Our SOME/IP stack is successfully ported on the IMXRT developer kit, demonstrating immediate viability for high-performance microcontrollers.
The stack enables efficient communication between ECUs using a service-oriented approach, modernizing vehicle network architecture.

RAPIDSEA SOME/IP Stack implements all major SOME/IP Service Discovery entry types and message types, including:
| Type | TTL > 0 (Time to Live) | From | To | Description |
|---|---|---|---|---|
| 0x00 | Find Service | Client | Server | The Find Service entry type shall be used for finding service instances |
| 0x01 | Offer Service | Server | Client | The Offer Service entry type shall be used to offer a service to other communication partners |
| 0x02 | Subscribe Eventgroup | Client | Server | The Subscribe Eventgroup entry type shall be used to subscribe to an eventgroup. |
| 0x03 | Subscribe Eventgroup Ack | Server | Client | The Subscribe Eventgroup Acknowledgment entry type shall be used to indicate that Subscribe Eventgroup entry was accepted |
| Type | TTL = 0 (Time to Live) | From | To | Description |
|---|---|---|---|---|
| 0x01 | Stop Offer Service | Server | Client | The Stop Offer Service entry type shall be used to stop offering service instances. |
| 0x02 | Stop Subscribe Eventgroup | Client | Server | The Stop Subscribe Eventgroup entry type shall be used to stop subscribing to eventgroups. |
| 0x03 | Subscribe Eventgroup Nack | Server | Client | The Subscribe Eventgroup Negative Acknowledgment entry type shall be used to indicate that Subscribe Eventgroup entry was NOT accepted |
| Message type | Value | Description |
|---|---|---|
| 0x00 | REQUEST | A request expecting a response (even void) |
| 0x01 | REQUEST_NO_RETURN | A fire&forget request |
| 0x02 | NOTIFICATION | A request of a notification/event callback expecting no response |
| 0x80 | RESPONSE | The response message |
| 0x81 | ERROR | The response containing an error |
| 0x20 | TP_REQUEST | A TP request expecting a response (even void) |
| 0x21 | TP_REQUEST_NO_RETURN | A TP fire&forget request |
| 0x22 | TP_NOTIFICATION | A TP request of a notification/event call-back expecting no response |
| 0xa0 | TP_RESPONSE | The TP response message |
| 0xa1 | TP_ERROR | The TP response containing an error |
This ensures complete interoperability with AUTOSAR-based ECUs and Ethernet switches.
Modernize your vehicle architecture with a high-performance, cost-effective middleware designed for the future of software-defined mobility.
Legacy CAN buses cannot handle the data throughput of modern vehicles. RAPIDSEA enables a transition to Ethernet, reducing cabling weight & cost while increasing bandwidth by 100x.
SOME/IP’s event-oriented messaging mechanism transmits data only when changes occur, eliminating redundant cyclic broadcasts and significantly saving bandwidth for critical applications.
Unlike proprietary stacks tied to specific silicon, RAPIDSEA is tested on NXP (i.MX RT), Renesas, TI, and Microchip platforms. It adapts to your hardware choice, not the other way around.
Designed by architects with 20+ years of experience, the stack is lightweight enough to run on resource-constrained MCUs yet powerful enough for High-Performance Compute (HPC) units.

High-speed transmission of sensor data (Lidar, Radar) to fusion controllers using Publish-Subscribe mechanisms.
Seamless streaming of media metadata and navigation signals between head units and cluster displays.
Reliable transport of large firmware images to Gateway ECUs using the robust ISO-TP layer over Ethernet.
Bridging internal vehicle networks with external telematics units for vehicle-to-cloud data synchronization.
Yes, our stack allows interoperability with both AUTOSAR Classic and Adaptive platforms.