Will 2024 be the key window period for cabin-driving integration?

A practical problem is how to meet the differentiated needs of the smart driving domain and the cockpit domain on one chip during the cabin-driving integration process. At present, due to the close coupling relationship between intelligent driving and driving safety, the requirements for safety, stability, reliability, and response speed in the intelligent driving domain are significantly higher than those in the cockpit domain. In comparison, the cockpit domain focuses more on user interaction experience and the optimization and upgrading of in-vehicle entertainment systems. Therefore, it has higher requirements for the diversification and continuous iteration of system functions.

In this case, how to fully meet the different requirements of the two domains for security, real-time, etc., how to isolate different functional security levels, resource scheduling, cross-domain adaptation, and reasonable power consumption and cost during the integration process Control, rapid test verification and engineering implementation are all topics that cannot be avoided.

Even if One Board or even One Chip is realized, given the current industry's inconsistent standards in terms of definition and division of related functions, as well as the high cost of high-performance SoC chips, it is still a long way to go before cabin-driving integration can be truly popularized on a large scale. A long way to go.

“Not only that, for the integration of cabin and driving, even the entire industry will face new requirements such as organizational reconstruction, personnel capacity training, process design, and technology iteration.” The above-mentioned person in charge of Desay SV pointed out.

In the current organizational structure system, the intelligent driving and intelligent cockpit R&D functions of many OEMs and Tier 1 are usually divided into two independent business units. To effectively promote the process of cabin-driving integration, it is necessary to strengthen cross-department collaboration, even break down the original departmental barriers, and achieve deep integration at the organizational structure level. This process not only places high demands on the company's internal coordination mechanism, but is also a very challenging strategic organizational restructuring task, which itself has many difficulties.

This is just within the company. From the perspective of the entire industry, the integrated development of cabin driving will even bring about the reshaping of the industrial chain pattern, including new division of labor and cooperation between upstream and downstream enterprises, as well as the reform of existing development systems and models. Reconstruction, this change has begun to take shape in the evolution of the vehicle E/E architecture from traditional distributed to domain-centralized architecture.

"The current new OEM cooperation has changed from the vertical model in the past to the current mesh model, that is, with the OEM as the center, electronic system Tier1, software system Tier1, semiconductor supplier Tier2 and ICT companies collaborate with each other." Talking about cabin driving Hu Xiaoli, deputy general manager of Jiefa Technology, once said about the impact of integration on the industrial chain cooperation model.

Next, with the deeper integration of the smart driving domain and the smart cabin domain and further evolution towards a central computing architecture, it will further promote the reshaping of the industrial chain pattern.

Especially this year, the price war in the auto market is still continuing. Under the multiple pressures of cost reduction, efficiency improvement and in-depth intelligentization and electrification transformation, a more intense competitive reshuffle and in-depth integration is quietly coming.