In an exclusive interview with ELE Times, Shrikant Acharya, CTO and Co-founder of Excelfore, outlines how vehicles are evolving from simple update-driven systems to intelligent, data-centric platforms. He explains the distinction between OTA updates and data aggregation within a unified lifecycle pipeline, while highlighting innovations such as adaptive delta compression and distributed architectures. Acharya also explores the growing role of Ethernet, AI, and scalable system design in shaping software-defined vehicles, positioning India as a key market in this transformation.
ELE Times: Could you elaborate on OTA updates and how they differ from in-vehicle data-related processes? Also, what differentiates your OTA solution in this evolving landscape?
Excelfore:
It is important to distinguish between OTA updates and data aggregation. OTA primarily refers to a one-way process—delivering updates from infrastructure to the device. In contrast, extracting data from the device back to the infrastructure is better described as data aggregation. When viewed as a unified pipeline, both functions contribute to lifecycle management. Updates are deployed to improve or fix device functionality, while data is retrieved to evaluate performance, detect issues, and validate those updates through analytics.
From a technical standpoint, OTA updates are asynchronous, involving large data transfers—often several gigabytes —owing to their bulk, especially in systems like Android-based infotainment. Conversely, data retrieval is typically synchronous or near-real-time, requiring smaller, segmented packets to ensure continuity and responsiveness, thereby maintaining the real-time nature of the aggregation. In essence, while both operate within the same pipeline, OTA updates and data aggregation serve fundamentally different purposes—one enables corrective action, while the other supports monitoring and analysis.
OTA has evolved significantly—from early implementations in industrial systems to its adoption in automotive environments. Initial solutions, such as those derived from mobile update frameworks, were primarily suited for infotainment systems and can be considered first-generation approaches. At the same time, our solution represents a more advanced, third-generation architecture. A key innovation lies in its plug-and-play capability. Devices entering the network authenticate themselves through certificates and register dynamically. The client system acts as a generic dispatcher without embedded knowledge of the vehicle or environment, enabling deployment across diverse ecosystems.
Another major advancement is the distributed architecture. Complexity is intentionally removed from the communication pipeline and instead distributed between the server and device. This approach ensures scalability, simplifies integration, and allows seamless accommodation of legacy systems. OEMs can retain existing device management frameworks while selectively adopting newer capabilities.
Agents within devices handle updates, ensuring structured execution while maintaining flexibility. This modular and distributed design is central to our differentiation, which also helps OEMs to preserve legacy.
ELE Times: Could you explain the concept and significance of adaptive delta compression? How does this approach optimize bandwidth and system performance?
Excelfore:
Traditionally, software updates required transmitting the entire payload. Delta compression improves efficiency by sending only the differences between software versions, significantly reducing bandwidth usage and update time. However, managing these differential files over time creates a substantial IT burden for OEMs. Our approach shifts this responsibility to the server-client system. The server dynamically determines when and how to generate and transmit delta updates, eliminating the need for OEMs to manage them manually.
Also, if one doesn’t want to use the main channel to send these large files, you only give them a reference to the URL for that payload, and then the agent sets up an independent connection and puts it down. Also, the “adaptive” aspect introduces intelligence into this process. The system evaluates multiple parameters—such as device memory, processing capability, network interface (CAN, LIN, Ethernet), and connection speed—to determine the most efficient compression strategy.
Additionally, large payloads are handled via separate channels, ensuring that the primary communication pipeline remains responsive for critical operations such as authentication and command execution.
Regarding optimization, it is achieved by tailoring data packets to device constraints. For instance, if a device has limited cache capacity, the system ensures that data units fit precisely within that space. This avoids inefficiencies caused by partial data processing and repeated memory access. Beyond cache considerations, factors such as network speed and interface type are also evaluated. The system assigns weighted parameters to these variables and generates an optimal data transfer strategy, ensuring efficient utilization of bandwidth while maintaining system performance.
ELE Times: With the rise of SDVs and advanced features, how do you see networking technologies evolving?
Excelfore:
Ethernet has emerged as the dominant in-vehicle networking standard due to its scalability, cost efficiency, and high bandwidth capabilities. Earlier technologies like FlexRay served as transitional solutions but have largely been superseded.
While legacy systems such as CAN will continue to exist due to installed base constraints, advancements like 10 Mbps multi-drop Ethernet are increasingly capable of replacing them.
Time-Sensitive Networking (TSN) plays a crucial role, particularly in time synchronization and deterministic data transmission. Combined with Quality of Service (QoS) mechanisms, it enables efficient bandwidth utilization—often achieving up to 85–90% channel efficiency compared to significantly lower utilization without traffic management.
ELE Times: How are SDVs reshaping vehicle architecture and OEM strategies? How do you view the evolution of SDVs and connected vehicles in India?
Excelfore:
The term SDV is often used loosely, but its true definition involves a standardized hardware platform whose functionality can be dynamically reconfigured through software.
Architecturally, the industry has evolved from domain-based systems to zonal architectures with centralized computing. Zonal controllers process localized data, which is then transmitted to central compute units for decision-making.
This shift introduces challenges, particularly in thermal management, as high-performance compute systems generate significant heat. Cooling solutions have thus become a critical component of system design.
For India, it presents a unique opportunity, having bypassed several legacy stages of technological evolution. This allows for a more forward-looking approach, with fewer constraints from outdated systems. There is a strong willingness to adopt advanced technologies based on value and functionality. This mindset, similar to what was observed in China during its rapid technological growth phase, creates a favorable environment for innovation.
For technology providers, this openness enables deeper collaboration and the deployment of cutting-edge solutions, positioning India as a promising market for SDVs and connected vehicle ecosystems.
ELE Times: What role do you see AI playing in OTA and SDV ecosystems?
Excelfore:
AI adoption in vehicles is constrained by cost and computational limitations. As a result, the focus is shifting toward domain-specific, lightweight models rather than large, generalized AI systems.
While generative AI will primarily reside in the cloud, vehicles will utilize smaller models tailored to specific functions—such as diagnostics or object detection. One practical application is the digitization of vehicle manuals, enabling intelligent interpretation of diagnostic codes and user-friendly outputs.
However, monetization will be a key factor. Advanced AI-driven features are unlikely to be offered free of cost and will likely be delivered as subscription-based services.
ELE Times: How do you ensure safety and integrity in OTA updates, especially for critical systems?
Excelfore:
Data integrity is ensured through mechanisms such as SHA-256 hashing, which verifies that transmitted data remains unaltered. If discrepancies are detected, updates are rejected.
Authentication is enforced באמצעות digital certificates, establishing both device identity and software origin. Additionally, encryption ensures that only the intended device can decode and execute the update.
A critical vulnerability lies in key management during manufacturing. Protecting private keys is essential, as any compromise at this stage can undermine the entire security framework.
