Automotive Ethernet for OTA Updates & eSync | Excelfore

The Future of Vehicle Connectivity: How Automotive Ethernet Powers OTA Software and eSync Platforms

Modern vehicles are no longer defined only by mechanical design driven by horse power. They are characterized by electronics driven by connectivity. Every ECU, domain controller, and sensor now relies on a network robust enough to manage high data loads, facilitate real-time communication, and ensure secure OTA software updates.

This is where automotive Ethernet comes in. Unlike legacy CAN or LIN buses, Ethernet provides the bandwidth, economy and scalability required for a software-defined vehicle. And when combined with the Excelfore eSync OTA platform, it powers secure and efficient full-vehicle updates.

Let us explore!

Why automotive ethernet is the backbone of OTA?

Automotive Ethernet solves three fundamental problems in modern vehicle networks: bandwidth, standardization, and determinism.

• Bandwidth: Infotainment systems, ADAS, and high-resolution cameras generate massive data. Traditional CAN can’t handle this. Ethernet provides gigabit-level throughput to carry large software payloads.
• Scalability: Ethernet scales gracefully. Switch-based forwarding and auto-negotiation simplify adding ports and aggregating bandwidth without creating shared-bus bottlenecks.
• Standardization: Ethernet supports multiple protocols that unify communication across ECUs. Perhaps the most important among these is IP addressing.
• Determinism: The one advantage that CAN has held is deterministic timing.  When TSN (time-sensitive networking) is added to Automotive Ethernet, then priority traffic -- like control signals and safety-critical data -- arrives predictably, even when the network is busy.

This makes Ethernet the ideal highway for OTA software distribution across the entire vehicle.

Deeper look: SOME/IP and DoIP

Protocols such as SOME/IP and DoIP provide a crucial link in bringing the reach of IP addressing to devices on non-IP buses such as CAN and LIN. IP addressing can reach/diagnose/update devices on non-IP buses via standardized routing (DoIP) and service proxies (SOME/IP), preserving these buses while enabling scalable, secure, and discoverable access.

SOME/IP (Scalable service-Oriented Middleware over IP)

• SOME/IP enables service-oriented communication between ECUs.
• Instead of fixed message sets, ECUs can dynamically “discover” services, just like devices on an enterprise network.
• IP Addressing: A SOME/IP proxy/adapter on the gateway exposes services on behalf of CAN/LIN devices and translates requests/events to the local bus protocol. The proxy’s IP serves the non-IP device by “virtualizing” it as a service.
• This is crucial for software-defined vehicles, where features can be added or updated over time.

DoIP (Diagnostics over IP)

• DoIP standardizes remote diagnostics using IP-based communication.
• It allows service centers—or even OEM cloud servers—to run UDS diagnostics as if the vehicle were physically connected.
• This reduces workshop dependency and supports remote troubleshooting at scale.
• IP Addressing:  A CAN gateway on Ethernet can forward UDS frames to the target ECU on CAN and relay responses back—so the gateway’s IP address makes non-IP ECUs remotely reachable.
• UDS can also be used to reflash devices, the combination of DoIP and UDS provides a very practical set of tools to enable OTA installation of new software from the cloud.

Deeper look: Ethernet TSN (Time-Sensitive Networking)

• TSN introduces determinism to Ethernet, ensuring latency-sensitive data (like braking or steering commands) always meets deadlines.
• Without TSN, Ethernet traffic could delay critical control signals, potentially compromising system stability and integrity.
• With TSN, you can safely mix high-bandwidth traffic (like infotainment updates) with safety-critical traffic on the same backbone.

Together, SOME/IP, DoIP, and TSN provide Ethernet with the flexibility, reliability, and safety required for automotive networks, thereby establishing it as a foundation for full-vehicle OTA.

eSync: Making OTA scalable and secure

The Excelfore  eSync OTA platform uses this Ethernet backbone to manage OTA software updates across all ECUs and domains. It is more than just a delivery system—it’s a complete pipeline for updates, diagnostics, and telemetry.

Key features include:

• Bi-directional pipeline: Updates flow down, diagnostics flow up.
• Fault tolerance: Built-in retries, rollbacks, and resume functions ensure reliability.
• Security by design: Encrypted sessions, mutual authentication, and policy enforcement.
• Multi-ECU orchestration: Updates can target infotainment, ADAS, powertrain, active safety, passive safety, and/or chassis simultaneously, without conflicts.

For example, an OEM pushes an ADAS algorithm update. eSync delivers it through Ethernet to multiple ECUs, validates it, and applies it safely. If any step fails, rollback policies ensure the vehicle stays operational.

Delta compression: making updates practical

Full image updates can be too large and slow for today’s cellular networks. That’s why delta compression is essential. Instead of sending gigabytes of data, eSync calculates the differences between the current and target versions. Only the “delta” is transmitted, which can reduce payloads by up to 95%.

On the vehicle side, the ECU reconstructs the update from this smaller delta package. This reduces bandwidth consumption, minimizes download time, and lowers costs—especially for fleets of tens of thousands of vehicles. This means OEMs can deploy security patches, feature enhancements, and compliance updates frequently, without overwhelming networks or users.

Does it matter for OEMs?

Combining automotive Ethernet, eSync, and delta compression creates a future-proof architecture that OEMs can trust.

Advantages include:

• Efficiency: More immediate updates with smaller payloads.
• Scalability: Reaches dozens of ECUs across domains.
• Reliability: IP addressing native to automotive ethernet, with SOME/IP and DoIP extensions for devices on non-IP buses, ensures updates can reliably reach every programmable device in the vehicle.
• Diagnostics: DoIP enables remote monitoring and proactive maintenance.
• Flexibility: SOME/IP allows dynamic feature updates, unlocking Features-on-Demand revenue models.

The road ahead

The shift to a software-defined vehicle requires more than software—it requires the proper connectivity infrastructure. Automotive Ethernet provides the backbone. SOME/IP, DoIP, and TSN ensure flexibility and determinism. eSync manages updates and diagnostics at scale. Delta compression makes it efficient and cost-effective.

Concurrently, these technologies form the basis for connected mobility. They keep vehicles current, safe, and competitive—not just at launch, but throughout their entire lifecycle.

For OEMs, this isn’t just an advancement. It’s the roadmap to providing vehicles that are flexible, secure, and future-ready.

FAQ:

1. Why is automotive Ethernet essential for OTA software updates?

Automotive Ethernet provides the high bandwidth, scalability, and IP-based communication required to deliver large OTA software updates across multiple ECUs. Unlike CAN or LIN, Ethernet supports gigabit data rates and standardized protocols, making it the backbone for full-vehicle OTA updates in software-defined vehicles.

2. How do SOME/IP and DoIP enable OTA updates on non-IP ECUs?

SOME/IP and DoIP extend IP-based communication to ECUs running on CAN or LIN buses. Gateways expose these non-IP devices through IP addresses, allowing cloud systems to discover services, run diagnostics, and deliver OTA updates remotely—without redesigning existing in-vehicle networks.

3. What role does Ethernet TSN play in safe OTA updates?

Ethernet TSN (Time-Sensitive Networking) ensures deterministic delivery of safety-critical data even when the network is handling high-bandwidth OTA traffic. This allows OTA software downloads and infotainment updates to coexist safely with real-time control signals on the same automotive Ethernet backbone.

4. How does the eSync platform use automotive Ethernet for scalable OTA delivery?

Excelfore eSync uses automotive Ethernet as a high-speed backbone to orchestrate OTA updates across multiple ECUs and domains. Its bi-directional pipeline enables secure delivery, validation, rollback, and real-time diagnostics—ensuring reliable updates at fleet scale.

5. Why is delta compression important for Ethernet-based OTA updates?

Even with automotive Ethernet, transmitting full software images is inefficient over cellular links. Delta compression reduces OTA payload sizes by sending only software changes, cutting bandwidth usage and update time while allowing frequent, secure updates through platforms like eSync.