Service-oriented framework such as data distribution service (DDS) is enabling real-time, scalable software updates without disrupting the functionality of the vehicle. Software-defined vehicles (SDVs) must continuously flourish and on scale, they have to reflect the evolutionary trajectory of computers and internet. In the early days, computing was characterized by the ownership Silos, but it developed through adoption of middleware standards, integrated data models and interopeable APIs.
Similarly, the motor vehicle industry should embrace a change towards convergence – adopting integrated data models that originally integrates diverse programming languages, APIs, platforms and network architecture. This convergence is required to create a scalable, future-proof ecosystem where SDV can continuously operate, innovate and develop.
“We believe that the standard and future of dynamics is going to be ‘a car, a network’, with the network division of vital systems, such as engines and brakes are isolated from less significant systems such as infotainments for more secure and efficient cars, called” Amit Chadha, CEO and Managing Director, L&T Technology (LTTS).
Says Chadha, “The standardization of vehicle communication interface emerging as an Ethernet as a strong contender to change traditional protocols such as can, flax and lin will also increase the standardization of the interface. Ethernet’s standardization will also simplify software development, in addition to eliminating the need for gateway modules.”
He indicates that the new standard, such as 10 base T1, which provides a simple multidrop network at high speed, would also be a great option to change the final mile connectivity for the ED ECU (electronic control unit). “While 1000/100 BT will be used for upstream communication for zone between HPC/vehicle central computers, 10 base T1 will be used for zone connectivity for the edge.
Naveen Kalappa, Global Practice and Delivery Head – Embedded System, Tata Technologies, sheds light on the rise of collaborative alliances running SDV evolution. “Various consortiums such as SDV alliances- A cooperation of motor vehicle standards, including various consortium, Cosar, Kowsa, Eclipse SDV, and Sophie, are working to harmonize SDV development by taking advantage of open standards and technologies, including Open-SOS software and APIs.”
Service-oriented framework such as data distribution service (DDS) is enabling real-time, scalable software updates without disrupting the functionality of the vehicle. “This change spreads well beyond the vehicle. This connectivity is unlocking new price currents, from future maintenance and real-time diagnosis to data-making personalization, all are supported by all off-carnaments analytics platforms that learn from fleet-wide behavior,” Calappa says.
“We can expect a major open standard data model with a mixture of open sources and proprietary platforms, leading to an explosion of third-party apps and services,” Jeffrey Jacob-Partner and National Sector Leader for KPMG in India. This means, he shares that in the future, vehicles will become more modular, update and inter -oprable systems that will allow Tier 1 suppliers and tech companies to manufacture services that will work in many OEMs and there will be integrated data systems that enable real -time decisions. Initiatives like VW’s own Cariad platform, which is aimed at building, has a single integrated operating system in all its brands, and Android Automotive OS, which is being widely adopted by several OEMs to standardize in-vehicle infotainment and offer interoperability, highlighting this change and interaction.
A data model, silver Mahajan, partner and leader of the automotive sector, and atul gynez, partner, explaining the main idea of Deloite India, say, “This is about the supplier, stage, or the task to define, manage, and exchange data in all systems in a vehicle, making a single, an unified method to make a single, united method.”
They cite a European alliance for safe and standardized data exchanges as a notable initiative. It is a platform using end-to-end data chains with the entire (automotive) value chain. However, the two experts emphasize the need for regulatory push to innovate simultaneously and rapidly, or to find common ground between each other by focusing on the core for OEM and searching for an open source for non-core elements.
“Change towards a data model represents a fundamental step in enabling this intelligent dynamics ecosystem,” says Kalappa says that real-time vehicle telemetry, cloud-based user profiles and relevant environmental data can now be constantly interpreted, which enables personal, active vehicle experiences.
Like the universal serial bus (USB) standardized communication among the equipment in computing, “a data model will be a common language that unlocks scalable software development and continuous improvement in automotive value chains.”
Stating that the shift is expected to increase the development of advanced driver-help system (ADAS), autonomous driving, and other software-operated functional, Chadha expressed, “It is expected that OEMS will soon be a market for the common API for vehicle tasks for defined interfaces and can prepare the TIRE to choose the work of ISV. The day is not far away where API will part like any other items for RFQ.
From the language perspective, Chadha shared, “We will see the rust taking a center stage due to our memory management facilities and ability to secure the memory leaks. The compatibility of the rust with other languages allows for a spontaneous integration with the existing codebase, providing convenience of a gradual transition instead of a complete recurrence, which leads to an interruptions, which grows to interrupt their current development processes.
For the vehicle operating system (OS), Kalappa says it is becoming a central nervous system of modern mobility. “Unlike the Legacy OS platforms, which were tightly added with specific hardware, future vehicles are designed for flexibility and cloud-indesters adaptability. The new OS architecture is developed to support the modular and network environment.”
Given that future vehicles will add open-sources and proprietary elements to ensure strong security, real-time performance and spontaneous integration. “We will require strong firewalls, encryption, authentication, infiltration detection system (IDS), regular FOTA updates and fragmented networks to ensure security.”
Given that the future of the vehicle OS will probably be seen a mixture of ownership and open-source solutions, which ensure strong security, real-time performance, and uninterrupted integration with various vehicles and external systems, say chadha, “We will have challenges on security, we will also need to make a strong firewall, which is ready for an encryption and mutation and mutuality.”
Whether it is an electric vehicle (EV) is adjusting its performance based on the smart grid input, or an autonomous system that adapts its behavior based on the shore-specific landscapes, the ability to swallow and act on off-car data will be a defined facility. Vehicle OS will play an important role in this development.
Experts believe that future vehicles OS will not only manage the onboard system, but will also serve as a wide, node of real -time networks of connected equipment, infrastructure and cloud services. Open-sources platform core vehicle functions such as automotive grade linux (AGL) and Android Automotive OS will continue to expand beyond infotainment. Aligned heritage stack providers with autorus will face pressure due to high maintenance costs.
“Redhat has certified its Linux OS for functional security. This is an important step, and in the right direction. We hope that now many OEM will have the flexibility required to run the development of applications on the open-source OS,” the Chadha says.
