SOME/IP Protocol

SOME/IP (Scalable Service-Oriented Middleware over IP), which stands for "scalable service-oriented middleware running over IP", is an in-vehicle network communication protocol spearheaded and developed by BMW Group in 2011, and subsequently standardised by the AUTOSAR consortium. Operating at the application layer of the OSI seven-layer model over TCP/UDP transport, it serves as a cornerstone technology underpinning the Service-Oriented Architecture (SOA) and Automotive Ethernet communication in next-generation intelligent vehicles.

Core Philosophy: From "Signal-Oriented" to "Service-Oriented"

To understand SOME/IP, one must first appreciate how it fundamentally differs from legacy in-vehicle communication buses such as CAN and LIN. Conventional bus systems are Signal-Oriented , where ECUs broadcast data cyclically or upon changes regardless of whether other ECUs actually require it, inevitably causing heavy bus loads.

In contrast, SOME/IP is Service-Oriented , operating strictly on a demand-driven basis. The server ECU transmits data only when a client ECU explicitly requests or subscribes to a service. This significantly cuts down bus loading while delivering a far more flexible communication architecture that allows software features to iterate and scale with ease.

To put it simply: a traditional CAN bus functions like a public PA loudspeaker, continuously broadcasting announcements whether anyone is listening or not; SOME/IP works like a dedicated phone line, establishing a direct connection and transmitting targeted data only when needed.

Core Functions

As an automotive middleware, SOME/IP provides a comprehensive suite of capabilities to ensure seamless inter-service communication:

• Serialisation: Converts data structures across disparate operating systems and hardware platforms (such as AUTOSAR, Linux, QNX, and Android) into a unified, standardised network transmission format, ensuring complete interoperability across heterogeneous devices.

• Remote Procedure Call (RPC): Enables an ECU (client) to remotely invoke methods or routines on another ECU (server) as if calling a local function. This represents the primary mechanism for executing service calls.

• Service Discovery (SD): Acts as the dynamic connection management mechanism for SOME/IP. Servers broadcast available services via SD, while clients use SD to locate required services. Both endpoints complete dynamic service discovery and subscription through an "Offer/Find" handshake.

• Publish/Subscribe: Clients subscribe to specific events or fields hosted by a server. Whenever an event is triggered or a field value updates, the server automatically pushes the changes to all subscribed clients, eliminating the overhead of repeated client polling.

Communication Patterns

SOME/IP primarily supports four communication patterns that make up its complete service interaction framework:

• Request/Response (Two-way Method): The client sends a request and the server returns a response. This is the standard "request-and-reply" pattern, widely used for reading status data or executing one-off actions.

• Fire&Forget (One-way Method): The client transmits a one-way request without expecting an acknowledgement or response from the server. Ideal for telemetry, logging, and general notifications.

• Event (Event Notification): Once a client subscribes to an eventgroup via SD, the server proactively pushes notifications to the client whenever a specific event triggers (such as detecting a speed limit road sign).

• Fields: Remotely accessible "attributes". Clients can read values using a Getter method and modify them via a Setter method. Furthermore, any change in a field's value can automatically notify subscribed clients, behaving similarly to an Event.

Technical Positioning and Industry Outlook

SOME/IP does not operate in isolation; it works in close tandem with the Automotive Ethernet physical layer and TSN (Time-Sensitive Networking) to form the unified communication backbone of modern smart vehicles. Research indicates that architectures integrating SOME/IP with TSN can constrain the average jitter of service-oriented traffic to within 17.12 microseconds, making it viable for mission-critical, ultra-low-latency applications like autonomous driving.

Today, SOME/IP is an integral part of the AUTOSAR standard and is widely deployed across in-vehicle operating environments like Android Automotive OS, enabling standardised communication across diverse ECUs. As the automotive industry accelerates towards Software-Defined Vehicles (SDVs), SOME/IP's position as the core enabler of Service-Oriented Architecture will only grow in prominence.