Some/IP and DoIP: Bringing Service oriented communications to non IP networks and buses

 

The current automobile is more than just a vehicle—it’s a software-powered system of connected devices on wheels. As we move toward the era of the SDV (software-defined vehicle), the systems inside cars must also grow to communicate with the cloud.

 

Traditionally, most automotive communications have happened through protocols created for restricted data sharing, such as CAN or LIN. However, as elements such as OTA automotive services, real-time navigation, and advanced driver assistance become the norm, the need for service-oriented communication becomes increasingly critical.

 

That’s where Some/IP and DoIP step in.

Let’s break down what these two protocols are, how they work, and why they’re essential to future-ready vehicles—especially when adapting to non-IP networks like legacy CAN buses.

 

Understanding Service-Oriented Architecture in Vehicles

Before diving into Some/IP and DoIP, it’s helpful to understand why service-oriented communication matters.

 

In older vehicle architectures, messages were often predefined, static, and tied to specific ECUs (electronic control units). That worked when vehicles had fewer features. But today’s vehicles are dynamic, constantly updating, and expected to handle new applications during their lifetime—thanks to over-the-air updates and features on demand.

 

A service-oriented approach enables vehicle components to request and provide services, much like how apps interact on your smartphone. This dynamic communication is what enables features like predictive maintenance, vehicle diagnostics, and third-party app integration.

 

What is Some/IP?

Some/IP stands for Scalable Service-Oriented Middleware over IP. It is designed to provide flexible, service-based communication within automotive Ethernet networks.

 

Here’s why Some/IP matters:

●      It allows ECUs to offer and request services dynamically

●      It supports multicast and unicast communication

●      It’s scalable across different vehicle types and networks

●      It helps streamline connected automotive solutions across systems

In simple terms, Some/IP helps systems inside a vehicle communicate with each other in an innovative, structured manner, using familiar IT-style protocols over Ethernet TSN or traditional automotive buses.

 

What is DoIP?

DoIP, or Diagnostics over IP, is another crucial player in modern vehicle communication. It enables diagnostic services—such as reading fault codes or performing software updates—to be executed remotely over a standard IP connection.

 

Why is DoIP important?

●      It supports remote diagnostics via standard TCP/IP protocols

●      It works over Ethernet connections

●      It’s compatible with existing OTA automotive systems

●      It reduces the need for proprietary tools and connectors

In the world of vehicle diagnostics, DoIP simplifies everything. Technicians or OEMs can access vehicle health data, run tests, and apply over-the-air updates without physically plugging into the car.

 

Comparing Some/IP and DoIP

While both Some/IP and DoIP run on IP-based networks, they serve different purposes.

 

Main Purpose

●      Some/IP: Enables in-vehicle service communication between ECUs.

●      DoIP: Facilitates remote diagnostics over IP networks.

Based On

●      Some/IP: Uses TCP/UDP over IP.

●      DoIP: Uses TCP/IP and UDP specifically for diagnostics.

Focus

●      Some/IP: Designed for dynamic service requests, messaging, and event communication.

●      DoIP: Tailored for diagnostic communication (UDS-based services).

Data Type Handled

●      Some/IP: Handles various data types—infotainment, ADAS, control systems, etc.

●      DoIP: Primarily diagnostic messages (e.g., fault codes, ECU info).

Common Use Cases

●      Some/IP: Zonal architectures, infotainment systems, real-time ADAS features.

●      DoIP: ECU fault detection, remote diagnostics, workshop or OEM-level servicing.

So, while Some/IP focuses on allowing systems in the vehicle to interact fluidly, DoIP ensures that those same systems can be checked, maintained, and updated by the manufacturer—often without requiring a visit to a service center.

 

The Role of TCP/IP Protocols in Connected Vehicles

Modern connected vehicles are only as good as the networks behind them. At the heart of all this is the TCP/IP stack.

 

Why TCP/IP?

●      It’s the global standard for Internet and cloud-based communication

●      It supports secure and reliable data exchange between ECUs and cloud services

●      It enables true interoperability between vehicle systems and external diagnostics tools

●      It powers both DoIP and Some/IP to deliver smarter, more flexible communication

Think of TCP/IP as the universal language of connected vehicles. Without it, technologies like automotive Ethernet, automotive OTA, or cloud-based vehicle diagnostic tools wouldn’t be possible.

 

Extending These Protocols to Non-IP Networks

Here’s the real challenge: many vehicles still operate with a mix of non-IP networks (like CAN, LIN, or FlexRay) alongside IP-based systems. Some/IP and DoIP can be adapted or bridged to work in these environments.

 

How?

By using middleware and gateway solutions that translate between traditional buses and Ethernet networks. This allows OEMs to introduce connected automotive solutions in existing vehicle platforms without redesigning the entire electrical architecture.

That’s a game-changer—because it allows the gradual adoption of SDV principles while still leveraging current platforms.

 

Why This Matters for the Future

As vehicles become more intelligent and more connected, they also become more complex. The ability to:

●      Update software remotely

●      Diagnose issues before breakdowns

●      Scale across different hardware platforms

It illustrates a competitive edge in the automotive space.

With protocols like Some/IP and DoIP, automakers and suppliers can produce vehicles that are flexible, update-ready, and more effortless to maintain—while meeting the rising expectations of current customers.

 

Final Thoughts

Fetching service-oriented communication to non-IP networks isn’t just a technical advancement—it’s a foundational action toward creating the next age of smart mobility.

 

With Some/IP and DoIP, manufacturers can bridge legacy systems with cutting-edge elements, all while allowing OTA automotive updates, real-time vehicle diagnostics, and scalable connected automotive solutions.

 

In a world rapidly moving toward SDVs, getting the network architecture right is no longer optional—it’s critical.

 

Ready to Future-Proof Your Vehicle Network?

 

At Excelfore, we help you build the backbone of your SDV strategy—with secure, scalable, and standards-based solutions tailored for today's and tomorrow's mobility.

 

Contact us now.