[Editor's Note] The proliferation of SDV in automobiles has led to an increase in software complexity, leading to a shift toward a structure that enables simplification, reusability, rapid development, and deployment. This, coupled with hardware-software separation and the introduction of standard interfaces, is expanding to cloud-based development environments. Consequently, bottlenecks are emerging in SDV development, and development software is increasingly requiring support for diverse software architectures and architectural integration. In this context, QNX is leveraging its cloud-based strategy to accelerate SDV development, enabling software development without hardware. This pre-verification in the cloud, followed by application to the SoC target, enables rapid development and sufficient testing. Accordingly, we met with QNX Vice President Minhee Ryu, who will present 'A Solution for Securing Competitiveness in an SDV-Centered Vehicle Development Environment' at the ' 2025 e4ds Tech Day ' on September 9th, and heard about QNX's next-generation technology and what will be presented at the Tech Day.



■ I am curious as to why the integration of automotive electrical architecture has recently emerged as an essential task, and what the biggest changes in development, management, and maintenance have been as the boundaries between hardware and software become blurred.

In the past, it would not be an exaggeration to say that automobiles were a collection of ECUs, but these days, the number of ECUs has been increasing, but it is actually showing a decreasing trend.

This is because improvements in hardware performance and advancements in software have enabled integrated operation of ECUs, leading to the pursuit of diverse user experiences.

The complexity is increasing from the SW level simply included in the ECU (HW) to a form of SW that can respond to various scenarios.

Therefore, SW has been pursuing SW-specific features that enable simplified, highly reusable, and faster development and deployment.

By separating HW and SW based on a standard interface, the SW development cycle was shortened and reusability was enabled, and this even made it possible to use it in a cloud development environment.

■ So how can the QNX platform contribute to achieving SDV goals? I wonder what your competitive edge is.

QNX's Foundational SW Products are RTOS and Hypervisor.

QNX can support any SW structure that customers seek through a hypervisor that supports virtualization, which is essential for architectural integration, and an RTOS that has been field-proven for many years, which can be considered the most basic SW.

Since the core of the OS, from the Kernel to the Hypervisor, has already obtained ISO26262 ASIL-D certification, customers can save time on certification and focus on creating stable products.

■ What are the main toolchains and frameworks provided by QNX to support rapid development cycles?

QNX, which collaborates with global OEMs and tiers, always strives to solve their challenges through dialogue with customers.

What we learned through our conversations is that the bottleneck in the development cycle is in HW, not SW.

As a solution, we applied the Cloud First development method and prepared an RTOS and Hypervisor called QNX Accelerate on AWS Cloud.

This made it possible to start SW development even when the HW was not ready, and to overcome changes in new personnel and regional limitations.

The developed SW can be pre-verified on the Cloud Target and applied as is once the SoC Target is ready, enabling faster development and sufficient testing.

Cloud Target will also help build more automated DevOps through CI/CD integration.

■ Next-generation technology I'm curious about QNX's roadmap for responding to these trends.

QNX continues to prepare for Cloud, Container, Cabin, and various future platforms based on its robust RTOS and Hypervisor solutions.

QNX is preparing a roadmap so that the most time-consuming and difficult parts of SW development can be handled by QNX, while customers can focus on developing middleware and applications that enhance the customer experience at higher layers.

For example, in construction, QNX is responsible for the invisible but important parts, such as the skeleton or plumbing of a building that will last 100 years, while OEMs or Tiers are responsible for the furniture and interior that will actually be used, thereby improving the customer experience.

■ I am curious about what kind of content will be presented at the 2025 e4ds Tech Day.

We would like to explain the reasons and direction of changes in SW development methods and how QNX is preparing for customers.

■ A word to readers

We hope that e4ds Tech Day will be a fun opportunity to gain a deeper understanding of SDV trends and obtain useful information.

Meanwhile, applications for ' 2025 e4ds Tech Day ' can be made on the official website ( https://www.e4ds.com/conference/techday/ ).