The automotive & mobility industry is going through a change not seen for the past 100 years. And in the recent past we have seen the impact the CASE – Connected, Autonomous, Shared and Electric trend has had brought to the industry. As technology evolves and the software content in a vehicle increases dramatically the new trend of Software Defined Vehicles (SDV) is here
An SDV is envisioned as a vehicle that will be continuously connected to its environment enabling real time data exchange. This will enable feature and App enhancement in real time. Drivers will download and install the features as per their choice and requirements and the new features will be readily available to the users. For vehicle manufacturers this software defined approach means a change in the entire architecture of the vehicle for OEMs. This in turn means the development of an end-to-end scalable, updatable & modular architecture. Traditional distributed architectures with separate Electronic Control Units (ECUs) for each function are transitioning to more complex Central Computing Architectures
This article discusses how deploying Service Oriented Architecture (SOA) concept for Autonomous Driving (AD) development in the Central Computing Architecture environment for SDV proves is the right choice. Especially since many components like Fusion, Situation Analysis, Path planning etc. are reused across applications.
We will discuss 6 key aspects of deploying SOA for AD development in a Software Defined Vehicle environment/ program i.e.
The primary goal of SDV is to be configurable without impacting safety, security, and performance of the system. The Non-SDV AD system architecture was simple & decentralized which means the below challenges must be overcome in the SVD environment:
Figure 1: Complex Resource Sharing in Distributed Architecture
Deploying SOA with centralized architecture becomes a natural choice to ensure smooth functioning of the AD features and compliance to various Functional safety and Cybersecurity standards like ISO 26262, ISO 21434, SAE-J3061.
SOA is a software designed approach emphasizing on building applications which can be independently deployed and can communicate with each other through well-defined APIs. Architecture and the benefits are discussed in further sections.
The basic SOA architecture consists of:
Classification of Services are based on their functionality and accessibility. E.g., Method call which are initiated by other services, Events which are time synchronized or asynchronized , etc. There are different ways in which the services interact with each other such as Subscribe/Publish, Request/Respond, Fire & forget etc. Below Diagram is an example of Registry based service discovery with Request-Respond interface.
Figure 2: SOA Architecture
Transforming the classical SW to an SOA involves a few key challenges viz. SOA framework definition, grouping of functionalities, defining of services etc. The trick lies in understanding the data flow pipeline from a data driven perspective. The services are then tuned such that they work in synch to make the processed data reach its destination. The lifecycle of a service and its structure is defined based on various parameters such as standards and compliance policies. Target System-On-Chips (SOCs) Operating System may also influence the SOA architecture.
Below are two diagrams showing Classical and SOA based Lane Departure Warning (LDW) and Lane Keep Assist system (LKA)
Figure 3: High-level LDW/LKAS system in Signal based Architecture
Figure 4: High level SOA of LDW & LKAS
SOA based verification must have a different approach than traditional verification of AD-ADAS systems. The primary difference is that verification is not just done at application or feature level but also goes deeper to a level where the services interact with other services. Thus, the testing setup must have features which not only give it control access to the services but also has enough information (real time) on the SOA framework status.
SOA-based verification is particularly important for complex systems, such as Advanced Driver The verification process can also help to identify any potential performance bottlenecks and security vulnerabilities, allowing developers to address these issues before the system is deployed. By verifying the system in this way, the overall quality of the system can be improved, and the confidence of the end-users in the system can be increased.
SOA Test Framework:
Conventional Test framework cannot be easily adapted to test the SOA based system for many reasons. Conventional Test framework do not have flexibility to change their interfaces from signal-based verification to serviced based data driven verification.
The following must be considered whilst building a test framework for SOA based Autonomous system.:
Thus, the SOA Test framework would also be based on an SOA environment.
Further it should have additional capabilities for validation of below parameters:
Figure 5: SOA Verification Setup
In summary SOA is the clear and go to option for the advantages and ease it provides for smooth transitioning to SDV. This adaptation requires changes in various processes of development and verification. A robust test framework which can handle data driven services is the only key to successfully validating the AD-ADAS system. As the trend of SDV progresses it will bring up new challenges and solutions, it will be very interesting to see how engineers leverage SOA for the development of AD systems in this environment
Connect with us
KPIT Technologies is a global partner to the automotive and Mobility ecosystem for making software-defined vehicles a reality. It is a leading independent software development and integration partner helping mobility leapfrog towards a clean, smart, and safe future. With 11000+ automobelievers across the globe specializing in embedded software, AI, and digital solutions, KPIT accelerates its clients’ implementation of next-generation technologies for the future mobility roadmap. With engineering centers in Europe, the USA, Japan, China, Thailand, and India, KPIT works with leaders in automotive and Mobility and is present where the ecosystem is transforming.
Rajiv Gandhi Infotech Park,
Hinjawadi, Pune – 411057
Phone: +91 20 6770 6000
Frankfurter Ring 105b,80807
Phone: +49 89 3229 9660
Fax: +49 89 3229 9669 99
KPIT and KPIT logo are registered trademarks | © Copyright KPIT for 2018-2023
|cookielawinfo-checbox-analytics||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".|
|cookielawinfo-checbox-functional||11 months||The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".|
|cookielawinfo-checbox-others||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.|
|cookielawinfo-checkbox-necessary||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".|
|cookielawinfo-checkbox-performance||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".|