Software-defined vehicles (SDVs) use software to govern operations, incorporate new features and facilitate the integration of novel functionalities. This concept marks an advancement in the automotive industry, laying the foundation for autonomous driving and vehicle connectivity technologies.
The evolution of SDVs entails separating software and hardware development, such as smartphones. Original equipment manufacturers are establishing “walled gardens” for applications. This shift encompasses continuous agile software development, heightened computing requirements for data processing, a modular service-oriented architecture and fortified security measures against cyber threats.
The automotive industry is rapidly advancing toward SDVs, with the promise of improved comfort, safety and customization. As collaborations between OEMs and tech companies flourish, SDVs present additional challenges, such as cybersecurity risks and design intricacy.
The transition from domain to centralized architecture is also progressing, converting vehicles into mobile data centers. In this transformative journey, standards, collaborations and digital twin technology stand out as critical components, promising a future where software dictates the driving experience.
To delve deeper into this transformation, S&P Global Mobility initiated discussions with leading players in the SDV market, including Iflytek. Iflytek is an intelligent voice and artificial intelligence company in the Asia-Pacific region. They specialize in providing intelligent solutions for the automotive industry, including intelligent cockpits, sound effects, driving systems and services for automotive companies. As of March 2024, their automotive intelligent products and technologies have been embedded and accumulated in 57 million vehicles, with 10 billion online interactions and 25 million monthly active users. To learn more about this business and SDVs, we spoke to Lei Qin Hui, Iflytek Intelligent Auto Chief Technology Officer.
Key takeaways:
- Distributed and centralized architectures have pros and cons, with distributed architectures offering lower component maintenance costs and centralized architectures providing flexibility and the ability to integrate new functions.
- Communication speeds have increased from Kbit/s to Gbps due to high-resolution cameras, with high-speed communication required in the entertainment domain and real-time data communication and low latency needed for vehicle communication and automated driving.
- SDVs are built on vehicle hardware, with the cockpit domain transformed by mobile internet advancements, enabling intelligent features and turning the vehicle into a versatile space.
- Software development in the automotive industry follows standards, such as Automotive ASPICE and IATF 16949, with different software demands for each domain and complex software architecture in the central computer.
- Law enforcement and traceability are crucial for the safety and security of connected cars, with software protection for the network and gateway playing a key role in preventing unauthorized access and malicious attacks.
- In traditional partnerships, co-creation and co-development are necessary due to uncertain software specifications, and effective software development requires partnerships, frameworks and integration of different software modules. Natural Language Understanding (NLU) and Large Language Models (LLMs) improve user experience, while automated driving involves training algorithms and LLMs facilitate vehicle design and generate visuals. Manufacturing planning optimizes production processes, and LLMs are used in sales and marketing. Vehicle manuals provide maintenance guidance, and human salespeople establish emotional connections with clients.
The following is an edited transcript of the conversation.
S&P Global Mobility: Could you discuss the architectural transformations that SDVs are undergoing, specifically the shift from domain architectures to centralized electronic control units (ECUs), and the potential impact on vehicle operations?
Lei Qin Hui: Both distributed and centralized architectures have their pros and cons. Distributed architectures offer lower component maintenance costs but have higher overall vehicle costs and complex hardware management. Centralized architectures provide flexibility and the ability to integrate new functions but come with software complexity and higher maintenance costs for key components like the central computer.
The distributed architecture offers the advantage of combining multiple ECUs together, which extends its capabilities and results in lower maintenance fees. However, it also leads to higher total vehicle costs and complexity in terms of hardware and vehicle configuration.
With the rise of intelligent vehicles, there is a growing demand from our customers for entertainment and highly automated driving. As a result, the architecture is shifting toward domain-based and centralized architecture, where the software can control the vehicle sensors. This approach allows for flexibility in adding new functions to new vehicles, reduces the cost of hardware procurement, but increases software complexity and maintenance fees for the components.
Communication speeds have increased from Kbit/s to Gbps due to the use of high-resolution cameras. The entertainment domain requires high-speed communication, while vehicle communication and automated driving require real-time data communication and low latency. This complexity is further amplified by the high communication speed and low latency requirements of automakers' sliding functions.
As mechanical vehicles transition to electric and intelligent vehicles, we are witnessing a shift toward domain-based architecture, such as the vehicle control domain, cockpit domain controller and advanced driver assistance system (ADAS) domain controller. However, in the next one or two years, we can expect to see the emergence of central compute as a mega trend in the industry.
Both distributed and centralized architectures have their pros and cons. Distributed architectures offer lower component maintenance costs but have higher overall vehicle costs and complex hardware management. On the other hand, centralized architectures provide flexibility and the ability to integrate new functions but come with software complexity and higher maintenance costs for key components like the central computer. The distributed architecture offers the advantage of combining multiple ECUs, extending its capabilities and resulting in lower maintenance fees. However, it also leads to higher total vehicle costs and complexity in terms of hardware and vehicle configuration.
We are interested in how SDVs are reshaping the in-vehicle experience. Could you elaborate on the opportunities and challenges this presents for customization, infotainment and user interaction?
The first point emphasizes the importance of a solid foundation for SDVs. Currently, we have high-performance hardware in vehicles, which provides a strong base for SDVs.
The second point focuses on the intelligence and customer increasing demand of new features, particularly in the Greater Chinese market where there is a mobile internet industry. In the vehicle domain, this represents cockpit domain intelligence. As highly automated driving becomes more prevalent, the cockpit and rest of the cabin will transform into a multifunctional space resembling an office, meeting room, or smart home. It will no longer be solely a transportation space but also a place where you can work, be entertained, or relax. Therefore, the increasing demands of customers are a key driver for the development of new software features.
In relation to the other points, software-defined vehicles are essential for achieving highly automated driving. This requires a car with a wide range of features and software complexity. Additionally, there is a need for numerous software-defined vehicle chassis options. This is because software can be used to modify the performance of the vehicle chassis, opening up a multitude of possibilities for software customization in vehicles. Another important aspect is the ability to update the software regularly over time, even without software-defined vehicles.
What challenges have you encountered in SDV design, including system architecture, security, safety and failure prevention? How are these challenges being tackled?
Software development in the automotive industry faces challenges due to the sheer volume of code involved. To overcome these challenges, robust software development practices are essential. Different domains within the automotive industry have varying software requirements. For instance, infotainment software focuses on user-friendly interfaces, while software for highly automated driving prioritizes safety standards.
The central computer in vehicles exhibits complex software architecture. To protect data, safety and artificial intelligence (AI) in cars adhere to ISO 21434 standards. Algorithms and data are stored within the vehicle's mechanisms. Automated driving necessitates backup systems, low latency and multiple software layers. Control software ensures driving safety, stable design and robustness.
Extensive testing is conducted to verify and ensure the reliability of the software. Standards, such as Automotive ASPICE and IATF 16949, are followed in software development in the automotive industry to ensure quality and compliance with industry standards. These practices and standards play a crucial role in the development of software for the automotive industry, enabling the creation of safe, reliable and efficient systems.
How do you perceive the automotive industry's response to the increased risks of safety-related software crashes and remote cyber threats in SDVs?
Law enforcement and traceability are critical for ensuring the safety and security of connected cars. While no network can guarantee complete safety, those who attempt to attack a connected car will face consequences. To protect the vehicle network, it is essential to have software protection for the network and gateway. These components play a crucial role in preventing unauthorized access and malicious attacks. Timely response is vital for addressing software issues and fixing bugs. Regular updates and patches are necessary to maintain software security and reliability.
Although there are laws in place to provide coverage for cars under attack, it is important to note that no network can provide 100% safety and protection for the car. Similar to the banking system, which can also be vulnerable to attacks over time, software can be utilized to check the system and identify attackers, enabling them to be held accountable for their actions.
The second point emphasizes the importance of a vehicle network gateway, which serves as the entrance to the vehicle communication network. This unit is crucial in ensuring the security and protection of the vehicle network from potential attacks. Establishing requirements and protocols to safeguard the dedicated software of the vehicle is necessary to protect it from unauthorized access or breaches. The gateway acts as a barrier, preventing unauthorized access to the vehicle's internal systems and data, thereby enhancing the overall security of the connected car.
The third point highlights the significance of a quick response when software detects a problem or potential attack. Immediate software updates are crucial to address the issue and ensure the security and functionality of the system. Rapid response and effective bug fixing minimize the impact of potential attacks and maintain the safety and reliability of the connected car. Regular software updates and patches are necessary to address vulnerabilities and enhance the overall security posture of the vehicle network.
Could you provide some insight into the division of software development between the OEM and suppliers?
In traditional partnerships, the OEM defines specifications while the supplier develops and delivers the software. However, due to uncertain software specifications, co-creation and co-development are now necessary. Different software layers are involved, including standard capabilities like Iflytek AI, voice recognition, navigation, and music. Automakers can dominate by co-creating SDKs for various vehicle scenarios. Effective software development requires a software architecture similar to the E/E Architecture and powertrain, along with partnerships and frameworks to integrate different software modules. Without these, software development can be challenging.
Specifically, let us first address the partnership model. In the traditional model, known as the turnkey approach, the product is purchased from a supplier who then delivers it to the automakers. However, with software-defined vehicles, the requirements for software features have become more uncertain. This uncertainty necessitates a shift towards co-creation and co-development between automakers and software providers.
The second point highlights the different layers involved in software development. For instance, Iflytek utilizes AI technology for voice recognition and text-to-speech functionalities, among others. There are also standardized capabilities, such as navigation and music applications. Additionally, there are upper layers that focus on user experience. To achieve optimal results, there needs to be a co-creation process between software providers and automakers. This allows automakers to define the dominant software development and choose an integrator to integrate and develop the system. Partnerships play a crucial role in this process, as they involve not only delivering software applications to automakers but also co-creating software development to create user-friendly applications tailored to different vehicle scenarios.
The final point addresses the software framework, which is similar to the powertrain architecture's e-architecture. In software-defined vehicles, automakers have their own software architecture. This allows them to choose different software providers to offer various software modules that align with the same software architecture. This is crucial because it prevents the software management process from becoming overly complex. By following this framework, automakers can effectively manage and integrate different software components from multiple providers within their software architecture.
How do you see large language models transforming the automotive industry and its business models? What potential applications could we anticipate in the automotive sector?
User experience in cars is enhanced through NLU, transitioning from rule-based systems to LLMs that integrate extensive information. LLMs act as personal assistants, answering queries and controlling functions.
Automated driving involves training algorithms with data to handle corner cases and enhance driving performance. LLMs facilitate vehicle 3D design and generate visuals, while manufacturing planning optimizes production processes and resources.
LLMs are also utilized in sales and marketing for product introductions and demonstrations. Vehicles and robots are employed for advertising and explaining functionalities. Vehicle manuals provide maintenance guidance, while human salespeople establish emotional connections with clients.
These various applications of LLMs contribute to an improved user experience in cars, providing assistance, enhancing driving performance, aiding in design and manufacturing, and supporting sales and marketing efforts. The combination of technology and human interaction creates a holistic experience for car users.
