Single-Engine Off-Screen Rendering for Multi-App 3D HMI
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In the automotive industry, multiple application functions in in-vehicle human machine interfaces (HMI) integrate individual engines for 3D rendering, leading to excessive system resource consumption and instability due to multiple engine instances.
Innovation Solution
A non-integrated single-engine background rendering method that uses a single engine to create an off-screen rendering buffer, provides rendering outputs for multiple views, isolates input click processing, and employs cross-process communication with a universal protocol and rendering service library, enabling one-click packaging and project generation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If each application integrates the engine individually, then each application can independently obtain 3D rendering capabilities, but system resource consumption becomes excessive
Solution Approach 1:
Multiple applications share a single engine instance through cross-process communication mechanisms, consolidating what were previously separate engine instances into one unified rendering engine that serves all applications, thereby reducing resource consumption while maintaining rendering capabilities
Solution Approach 2:
The single engine instance is designed to serve multiple applications universally, providing 3D rendering services to different applications through standardized communication interfaces, allowing one engine to perform the work of multiple engines across different application contexts
2Ease of operation
If multiple engine instances are used, then each application can run independently, but system stability is compromised
Solution Approach 1:
A cross-process communication mechanism acts as an intermediary between applications and the single engine instance, allowing applications to interact with the engine independently while the engine remains a single stable instance, thus maintaining both independence and stability
Solution Approach 2:
The system is segmented into independent application processes that communicate with a single engine instance through defined interfaces, isolating application logic from the engine while maintaining stable engine operation, so that application failures do not affect engine stability
3Ease of manufacture
If each application integrates the engine individually, then rendering can be performed locally, but device complexity increases
Solution Approach 1:
Instead of integrating the entire engine into each application, the patent creates virtual copies or representations of the engine's functionality through cross-process communication interfaces, allowing applications to access rendering capabilities without actually integrating the full engine, thereby reducing complexity
Data Source
Figure 1~2
Figure 3~4
Figure 5
AI summary
Provided is non-integrated single-engine background rendering method for multiple applications. The method includes that: a single engine provides creation of an off-screen rendering buffer and off-screen rendering, to enable the single engine to normally run an entire rendering process of the single engine and generate a rendered image without relying on an external on-screen rendering buffer; rendering outputs for multiple Views are is provided and processing of input clicks is isolated; a universal View component is abstracted; a cross-process communication mechanism is provided and a universal protocol is defined; a rendering service library is provided; and one-click packaging and project generation are performed.