[Editor's Note] e4ds News and Vector Korea held a webinar on the 8th with the theme of 'Latest Trends in SDV Architecture'. In this webinar, we were able to learn about the changes in trends due to the automotive industry, which has a significant impact on the manufacturing industry, shifting to software-centered, as well as the definition and characteristics of SDV. Kim Eui-yeol, head of the business division at Vector Korea, who took the stage as a presenter, emphasized once again that partnerships between Tier companies and OEMs, where they learn from each other and establish new roles in the changing roles, are key success factors for the SDV trend, and that close collaboration between domestic companies is necessary to narrow the gap with global companies. Kim Eui-yeol, head of the Vector Korea business division, provided written answers to viewers' questions that could not be answered due to time constraints after the webinar.
■ I am curious about the most successful cases of SDV currently in use and the direction in which SDV will develop in the future. As explained in the webinar, SDV development is still in progress, so it is safe to say that no OEM or Tier has successfully completed it yet.
However, the OEM that appears to be doing the best is Mercedes Benz.
They not only develop MB.OS, but also have a clear understanding of what kind of business to create through SDV, and are communicating with various industries such as Tier, Tool Vendor, Chip Vendor, IT Company, and Cloud Company to create their SW, and are building their SW Layer and SW Factory.
Mercedes' insight into MB.OS, announced in February, was so detailed and well-organized that it garnered attention from the entire automotive industry, from the motivation to the future business model.
In the future, SDV will be developed while facing various technical limitations and overcoming or bypassing them.
One thing is certain: we will experience unprecedented services in our vehicles.
The most important thing in these experiences is the development of autonomous driving technology, and the level of services that can be provided will vary depending on how much autonomous driving technology develops.
■ Safety is the key I have a question about performance in terms of quality control, such as what efforts are needed in case of safety issues arising from software defects or hardware problems.
As always, safety is a top priority in vehicles, and even with the successful launch of SDV, safety concerns will continue to be a top priority.
However, the Vehicle EDGE Layer + IT Backend explained in the webinar will only have functions up to the maximum 'B' level among the ASIL levels of ISO26262, and the existing Onboard Layer will have functions up to the ASIL 'D' level as before.
When designing HPC, since many functions are concentrated, there is a high possibility of HW duplication to maintain redundancy, and when a safety issue occurs due to a HW problem and cannot be handled even with redundant HW, it is important to design it so that partial function processing is possible using the Degrade Function.
From a quality control perspective, it is necessary to create and verify Test Cases that may cause problems in multi-command situations.
For this reason, OEMs and Tiers are developing environments to virtualize and validate vehicles.
■ Questions about performance, bandwidth, and network hardware infrastructure upgrades HPC performance is expected to utilize CPUs at the level of 150 to 200 KDMIPS to integrate the SW of tens to hundreds of existing controllers, and communications are expected to send and receive data at a communication speed of 1 Gbps to 10 Gbps.
The last question is about the network outside the vehicle.As for questions about hardware, there has been discussion about introducing V2X to pilot infrastructure such as smart cities, but there has been no progress in applying it to actual infrastructure, so it is difficult to answer at this point.
■ What are the challenges to legal regulation and regulatory framework or market entry standards? Currently in Europe, there are regulations and standards such as UNECE WP29 and ISO 21434 that manufacturers are required to comply with.
Accordingly, domestic OEMs are trying to comply with laws and standards by creating CSMS (Cybersecurity Management System) and SUMS (Software Update Management System).
Since IT-based technologies have only recently been introduced into vehicles, these laws and standards are often unfamiliar and unclear about what needs to be done.
However, just like the existing functional safety, we expect that this will gradually be accepted naturally over time and reflected in the design.
■ If there is a framework that can be used for SDV development, please introduce it. Frameworks available for use in IT Backend include Amazon (AWS) and Microsoft (Azure), and OEMs are also developing their own frameworks for services that cannot be shared with external networks due to security issues.
■ I want to know about Vector's SDV support solutions and application casesg>
Since Vector is a company specializing in vehicle SW, it can be seen that general vehicle development SW also supports SDV.
Among them, tools specialized in service design include PREEvision, a tool for designing SDV architecture and systems, DaVinci, which can design adaptive SW and generate code, and CANoe, which can verify SOA.
As an application example, you can see that more than half of OEMs around the world are jointly developing the Vector Contribution area, which is highlighted in red in the figure below.
.png)
.jpg)
