Techday
This page was machine-translated and may differ from the original. View original

SDV Core: Value Creation through Continuous Software Updates

Google 우선 소스Published2023.08.31 12:22

Development of a service model where users download an app to receive services from an IT Backend service.
Powered by multiple cores, multi-threading, and virtual machines… Importance of HPC rises
Industry insiders have stated that the evolution toward Software Defined Vehicles (SDVs) is marking a paradigm shift from hardware-centric to software-centric vehicles, which will impact the business models of both OEMs and suppliers.

Kim Eui-yeol, Head of Vector Korea Business Division, gave a presentation on the topic of 'SDV Architecture Design' at Vector Tech Day 2023, held on the 30th at the Conrad Hotel in Yeouido under the concept of 'Driving the Future with SDV and E-Mobility,' explaining the changes and basic concepts that SDV will bring.

The core of SDV is value creation through continuous software updates, and the provision of services through this is expected to generate added value and revenue, as well as impact the business models of OEMs and suppliers.



SDVs, evolving beyond simple in-vehicle systems to include connectivity and autonomous driving, are being developed in a form where services are provided by downloading applications from IT-Backend services, etc.It is becoming a foot.

Providing services means that software complexity increases, and it must be processed quickly and accurately while maintaining precise control.

Software runs on multiple cores, multi-threading, and virtual machines, which increases the need for High Performance Computers (HPC).

In existing distributed architectures, various controllers had to cooperate to perform complex functions, but now the HPC, which acts as the brain of the vehicle, handles complex and fast calculations, while existing sensors or actuators handle only simple functions.

As development organizations integrate to design integrated functions, the mapping relationships assigned to hardware must also be clearly expressed and shared among organizations.

Because the previously developed processes differ from one another, large organizations face difficulties in integrating and collaborating, so work is needed to align and standardize them.

To standardize the development process, the AUTOSAR standard, an automotive standard specification, has been introduced, and a model-based design approach is adopted to ensure consistency between system specifications and development code.

Simple and optimized software uses the AUTOSAR Classic platform, while complex and continuously expandable functions use the AUTOSAR Adaptive platform and are managed by operating systems such as Linux and Android.

In the case of the network architecture, there is an HPC responsible for connectivity connected to the existing IT Backend, and they communicate with the IT Backend in the form of APIs.

Zonal Controllers can reduce weight by integrating physically close-range sensors, actuators, etc., thereby reducing wiring harnesses. There is an advantage to having.

"Korean OEMs plan to develop many in-vehicle functions in-house, but German companies that attempted a similar approach are facing failure," said Business Division Manager Kim Eui-yeol. "I expect that Korean OEMs will also find a way to coexist with their suppliers after going through various processes."
본 기사에 대한 정정·반론·추후보도 청구는 보도 청구 안내를, 그간 게재된 보도문은 정정·반론보도 모아보기를 참고해 주세요.
성유창 기자
성유창 기자