For Software-Defined Vehicles (SDVs) to thrive and scale sustainably, they must mirror the evolutionary trajectory of computers and the internet. In the early days, computing was characterised by proprietary silos, but it evolved through the adoption of middleware standards, unified data models, and interoperable APIs.
Similarly, the automotive industry must embrace a shift towards convergence – adopting unified data models that seamlessly integrate diverse programming languages, APIs, platforms, and network architectures. This convergence is essential to create a scalable, future-proof ecosystem where SDVs can operate, innovate, and evolve continuously.
“We believe that the standard and future of mobility is going to be ‘ONE CAR, ONE NETWORK’, with network segmentation of critical systems, such as those controlling the engine and brakes, being isolated from less critical systems like infotainment for more safer and efficient cars,” says Amit Chadha, CEO and Managing Director, L&T Technology Services (LTTS).
Chadha adds, “There will also be increasing standardisation of vehicle communication interfaces, with Ethernet emerging as a strong contender to replace traditional protocols like CAN, FlexRay, and LIN. The standardisation of Ethernet will also simplify the software development, besides eliminating the need for Gateway modules.”
He reflects that the new standards, such as 10 BASE T1S, which provides a simple multidrop network at higher speeds, will also be a great option to replace last mile connectivity for edge ECU’s (Electronic Control Unit). “While 1000/100B T will be used for upstream communication between HPC’s/vehicle central computers to the zones, the 10 BASE T1S will be used for edge to zones connectivity. This is expected to save significant wiring costs as well as simplify the FOTA (Firmware Over-The-Air) upgrades.”
Naveen Kalappa, Global Practice & Delivery Head – Embedded Systems, Tata Technologies, highlights the rise of collaborative alliances driving SDV evolution. “Various consortiums like The SDV Alliance – a collaboration of automotive standards organisations including AUTOSAR, COVESA, Eclipse SDV, and SOAFEE- are working to harmonise SDV development by leveraging open standards and technologies, including open-source software and APIs.”
Service-oriented frameworks like the Data Distribution Service (DDS) are enabling real-time, scalable software updates without disrupting vehicle functionality. “The transformation extends well beyond the vehicle. This connectedness is unlocking new value streams, from predictive maintenance and real-time diagnostics to data-driven personalisation, all supported by off-car analytics platforms that learn from fleet-wide behaviour,” says Kalappa.
“We can expect a dominant open standard data model along with a mix of open source and proprietary platforms, leading to an explosion of third-party apps and services,” Jeffry Jacob- Partner and National Sector Leader for Automotive, KPMG in India. This means, he shares, that in the future, vehicles will become more modular, updatable and have interoperable systems which will allow Tier 1 suppliers and tech companies to build services which will work across multiple OEMs and have unified data systems that enable real time decision-making. Initiatives like VW’s own CARIAD platform, which aims to build have a single unified operating system across all its brands, and Android Automotive OS, which is being widely adopted by several OEMs to standardise in-vehicle infotainment and offer interoperability, highlight this shift towards standardisation and interoperability.
Explaining the core idea of One Data Model, Rajat Mahajan, Partner and Automotive Sector Leader, and Atul Jairaj, Partner, Deloitte India, say, “It’s about creating a single, unified way to define, manage, and exchange data across all systems in a vehicle, regardless of the supplier, platform, or function.”
They cite Catena-X, a European alliance for secure and standardised data exchange, as a noteworthy initiative. It is a platform for building, operating and collaboratively using end-to-end data chains along the entire (automotive) value chain. However, both experts emphasise on the need for regulatory push to innovate together and faster, or for OEMs to find common ground amongst each other by focusing on core and exploring open source for non-core elements.
“The shift towards a One Data Model represents a foundational step in enabling this intelligent mobility ecosystem,” says Kalappa, adding that real-time vehicle telemetry, cloud-based user profiles, and contextual environmental data can now be interpreted consistently, enabling personalised, proactive vehicle experiences.
Much like how the Universal Serial Bus (USB) standardised communication between devices in computing, “the One Data Model will be the common language that unlocks scalable software development and continuous improvement across the automotive value chain.”
Highlighting that the shift is expected to enhance the development of advanced driver-assistance systems (ADAS), autonomous driving, and other software-driven functionalities, Chadha expresses, “It is expected that OEMs will have soon have a marketplace for common APIs for vehicle functions with defined interfaces and standardized protocols forcing ISV’s and Tier Ones to adopt to the One Data Model. The OEMs can the choose the best optimised vehicle functions. In fact, the day is not far where APIs would be part for RFQ’s like any other commodities.”
From the language perspective, Chadha shares, “we will see RUST taking centre stage due to its memory management features and ability for securing against memory leaks. RUST’s compatibility with other languages allows for a seamless integration with existing codebases, facilitating a gradual transition rather than a complete rewrite, making it easier for automotive companies to adopt RUST without disrupting their current development processes.
As for the vehicle Operating System (OS), Kalappa says it is becoming the central nervous system of modern mobility. “Unlike legacy OS platforms that were tightly coupled with specific hardware, the future vehicle OS is designed for flexibility and cloud-native adaptability. The new OS architecture is evolving to support open, modular, and networked environments.”
Noting that the future vehicle OS will combine open-source and proprietary elements to ensure robust security, real-time performance, and seamless integration. “We’ll need stronger firewalls, encryption, authentication, Intrusion Detection Systems (IDS), regular FOTA updates, and segmented networks to ensure security.”
Noting that the future of vehicle OS will likely see a blend of proprietary and open-source solutions, ensuring robust security, real-time performance, and seamless integration with various in-vehicle and external systems, Chadha says, “We will have challenges on security, we will also need to have a robust firewall that is equipped for Encryption and Authentication, Intrusion Detection Systems (IDS), Regular Software Updates via FOTA to update security patches, and Network Segmentation.”
Whether it’s an electric vehicle (EV) adjusting its performance based on smart grid input, or an autonomous system optimising its behaviour based on edge-learned scenarios, the ability to ingest and act on off-car data will be a defining feature. The vehicle OS will play an instrumental role in this evolution.
Experts believe the future vehicle OS will not only manage onboard systems but also act as a node in a broader, real-time network of connected devices, infrastructure, and cloud services. Open-source platforms like Automotive Grade Linux (AGL) and Android Automotive OS will continue expanding beyond infotainment into core vehicle functions. Legacy stack providers aligned with AUTOSAR will face pressure due to high maintenance costs.
“REDHAT has certified its Linux OS for functional safety. This is significant step, and in the right direction. We expect that many OEMs now will have the necessary flexibility to drive the development of applications on open-source OS,” points Chadha.
