A vehicle-mounted surround view quick display method and system, an electronic device, and a storage medium

Abstract

The application discloses a kind of vehicle-mounted look-around quick display method, system, electronic equipment and storage medium, belong to vehicle-mounted auxiliary driving technical field.The method comprises: in response to QNX real-time operating system starting instruction, asynchronous pre-initialization and background resource preheating are carried out to look-around function;Vehicle state is obtained, and look-around display is triggered when detecting reverse instruction;When look-around is closed, look-around picture rendering process controlled based on delay scheduling mechanism is triggered;System hibernation wake-up state is adaptively saved and recovery switching;Configuration mapping mode is used to manage functional events, interactive controls and communication messages;According to the gear state of vehicle, the look-around closing function is safety-locked.The application realizes look-around quick response by background asynchronous preheating, combined with delay scheduling, configuration mapping, hibernation wake-up adaptive control and gear safety locking, system power consumption, compatibility and reverse safety are considered, and the starting speed, running stability and user experience of system are improved.

Description

Technical Field

[0001] This application relates to the field of vehicle-mounted driver assistance technology, and in particular to a vehicle-mounted surround view rapid display method, a vehicle-mounted surround view rapid display system, electronic equipment, and storage medium. Background Technology

[0002] Modern smart car infotainment systems generally adopt a QNX+Android virtualization architecture. This architecture uses the QNX Hypervisor to achieve virtualization processing, separating and managing critical and non-critical services to form a clear layered system architecture. QNX, as a real-time operating system (RTOS), boasts a fast startup time of 2-5 seconds, while Android offers rich functionality but has a slower startup speed, typically requiring 10-20 seconds. The two systems achieve resource isolation and security through virtualization technology and seamless switching of system functions through hardware layer fusion. This architecture has become the mainstream choice for current automotive systems.

[0003] Currently, publicly available AVM (Around View Monitor) technical solutions based on the above architecture are mainly divided into three categories: First, the pure QNX architecture solution, which implements all AVM functions on the QNX side. Although it has the advantage of fast startup speed, it suffers from insufficient richness of the Android ecosystem and poor support for third-party applications, resulting in a user experience inferior to the Android system. Second, the Android startup waiting solution, which does not use FastAVM technology and requires waiting for the Android system to fully start before displaying the AVM surround view screen. The implementation method is relatively simple, but in the case of a cold start of the vehicle, users need to wait 10-20 seconds to see the surround view screen, resulting in a significant delay. Third, the pre-loaded image solution, which uses static images as placeholders before AVM startup, cannot display real-time video streams, and cannot meet the actual usage needs such as vehicle reversing.

[0004] Based on practical project development experience and in-depth analysis of existing technologies, it was found that the AVM system based on the QNX+Android virtualization architecture still has four major technical problems, which seriously affect system performance, user experience and driving safety.

[0005] Firstly, there is the issue of rapid response in cold start scenarios. When the vehicle is put into reverse gear, the user needs to check the road conditions behind immediately. However, the Android system has not yet fully started, and the AVM application cannot run normally. As a result, the user cannot see the surround view screen for 10-20 seconds after the cold start. Moreover, the existing solution uses a serial initialization method, which has a long startup delay and cannot meet the user's expectation of displaying the surround view screen within 500ms, which seriously affects driving safety.

[0006] Secondly, there is the issue of performance optimization under the limited resources on the QNX side. As a real-time operating system, QNX has different priorities in resource allocation. The implementation of FastAVM requires efficient use of hardware resources such as CPU and GPU. At the same time, the control of the rendering loop needs to take into account the overall system performance and avoid affecting critical service functions such as the dashboard.

[0007] Third, there's the issue of switching between STR (Stop To Resume) modes. When a vehicle enters STR power-saving mode, the QNX side needs to pause related applications. After the system wakes up, the normal display of FastAVM needs to be restored quickly. Furthermore, the STR interfaces of Kanzi 3.6 and Kanzi 3.9 differ, requiring targeted adaptation. At the same time, the state saving and restoration process must ensure integrity to prevent data loss. Fourth, there's the issue of code complexity for multi-vehicle adaptation. Different vehicle models have different screen sizes, functional modules, and UI layouts. Traditional conditional compilation methods result in high code duplication and maintenance difficulty. Adding a new vehicle model requires extensive code modifications, significantly reducing development efficiency. Summary of the Invention

[0008] In view of this, the purpose of the present invention is to provide a vehicle surround view fast display method, a vehicle surround view fast display system, electronic device and storage medium, which aims to solve one of the technical problems in the prior art, namely, the cold start fast response problem, the QNX side performance optimization problem, the STR mode switching problem and the multi-vehicle adaptation problem.

[0009] This invention provides the following solution:

[0010] According to one aspect of the present invention, a method for rapid display of vehicle surround view is provided, comprising the following steps:

[0011] In response to the QNX real-time operating system startup command, asynchronous pre-initialization and background resource warm-up are performed on the surround view function;

[0012] Obtain vehicle status and trigger surround view display when a reversing command is detected;

[0013] When surround view is off, the surround view rendering process is triggered based on a delay scheduling mechanism.

[0014] Adaptively save and restore the system's hibernation / wake-up state;

[0015] Functional events, interactive controls, and communication messages are managed using a configuration-based mapping approach.

[0016] The surround view function is locked for safety based on the vehicle's gear position.

[0017] Furthermore, asynchronous pre-initialization and background resource preheating are implemented so that after the rendering engine is loaded, the surround view video stream is started asynchronously through a background thread, the image acquisition device is initialized, and the rendering environment is prepared, while the main thread synchronously completes the vehicle signal monitoring.

[0018] Furthermore, a delay scheduling mechanism is implemented to start a preset delay when the surround view is turned off. During the delay, rendering continues to complete the screen refresh. After the delay expires, rendering is terminated to reduce system resource consumption.

[0019] Furthermore, the sleep / wake state adaptive saving and restoration switching allows for storing the view operation parameters through global state variables, adapting to the sleep and wake interfaces of different rendering engine versions.

[0020] Furthermore, the configurable mapping method allows for unified management of the relationships between functional events, interactive controls, and communication messages through a preset mapping table, and enables multi-vehicle compatibility through configuration-based replacement of conditional compilation.

[0021] Furthermore, gear position safety protection specifically includes: real-time acquisition of vehicle gear position signals, and disabling the surround view shutdown control when in reverse gear.

[0022] According to a second aspect of the present invention, an in-vehicle surround view rapid display system is provided, comprising:

[0023] Hardware support layer, virtualization management layer, real-time operating system side fast surround view unit, Android operating system side full-function surround view unit and vehicle communication and interaction unit;

[0024] The fast surround view unit integrates an asynchronous pre-initialization module, a rendering intelligent control module, a sleep / wake-up adaptation module, a configurable vehicle model adaptation module, and a gear safety protection module.

[0025] The hardware support layer provides the hardware acquisition, processing, and display foundation for the surround view function;

[0026] The virtualization management layer is used to achieve hardware resource isolation between the two systems and to forward display data;

[0027] The vehicle communication interaction unit is used to realize two-way interaction between the system and the vehicle status signals;

[0028] The full-featured surround view unit on the Android operating system side is used to provide complete surround view functionality services;

[0029] Real-time operating system side fast surround view unit integration: asynchronous pre-initialization module, rendering intelligent control module, sleep wake-up adaptation module, configurable vehicle model adaptation module, gear position safety protection module;

[0030] The asynchronous pre-initialization module is used to perform asynchronous loading and pre-start of the lookup resources in the background, improving the cold start response speed;

[0031] The rendering intelligent management module is used to manage the rendering process based on latency strategies, reducing system resource consumption and avoiding image residue.

[0032] The hibernation / wake-up adaptation module is used to save and restore the system's hibernation / wake-up state and adapt to multiple rendering engine versions;

[0033] The configurable vehicle adaptation module is used to achieve hardware and function compatibility across multiple vehicle models through configuration mapping, simplifying the adaptation process.

[0034] The gear position safety protection module is used to safely lock the surround view function according to the vehicle's gear position to prevent the function from being abnormally shut down when reversing.

[0035] Furthermore, the hardware support layer includes image acquisition equipment, vehicle status sensors, on-board computing chips, and display output devices.

[0036] Furthermore, the virtualization management layer completes the fusion and data pass-through of the display layers of the real-time operating system and the Android system through the hardware virtualization interface.

[0037] Furthermore, the asynchronous pre-initialization module independently executes the start-up of the surround view video stream, the initialization of the image acquisition device, and the preparation of the rendering environment through a background thread, while the main thread synchronously completes the monitoring of the vehicle status.

[0038] Furthermore, the rendering intelligent control module initiates a delayed rendering strategy when surround view is turned off, maintaining complete screen refresh during the delay period, and terminating rendering after the delay ends to release system resources.

[0039] Furthermore, the sleep / wake-up adaptation module stores the surrounding operating parameters through global state variables, making it compatible with the sleep and wake-up interfaces of different rendering engine versions, and achieving smooth recovery.

[0040] Furthermore, the configurable vehicle adaptation module manages function events, interactive controls, and communication messages in a unified manner through a preset mapping table, and achieves multi-vehicle adaptation by replacing conditional compilation in a configurable way.

[0041] Furthermore, the gear position safety protection module acquires the vehicle's gear position signal in real time, disables the surround view shutdown control when in reverse gear, and restores the control to be available when not in reverse gear.

[0042] Furthermore, the real-time operating system-side rapid surround view unit and the Android operating system-side full-function surround view unit achieve state synchronization and seamless function switching through the vehicle communication interaction unit.

[0043] According to three aspects of the present invention, an electronic device is provided, comprising: a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus;

[0044] The memory stores a computer program, which, when executed by the processor, causes the processor to perform the steps of a vehicle surround view fast display method.

[0045] According to four aspects of the present invention, a computer-readable storage medium is provided that stores a computer program executable by an electronic device, which, when run on the electronic device, causes the electronic device to perform the steps of a vehicle surround-view fast display method.

[0046] Compared with the prior art, the present invention has the following advantages:

[0047] This invention significantly improves the performance of vehicle AVM (Autonomous View Monitor) functionality, ensuring driving safety and optimizing the user experience. Specifically, FastAVM achieves millisecond-level cold start display time, enabling rapid response to startup commands and reducing driving safety hazards caused by startup delays, thus effectively enhancing driving safety. After the Android system boots, FastAVM on the QNX side can seamlessly switch to full AVM mode, with a smooth and imperceptible switching process, avoiding interference with user operations caused by switching lag and significantly improving the user experience. When FastAVM is turned off, the system employs a delayed stop mechanism, stopping the rendering loop while ensuring the last frame is fully refreshed, effectively reducing system resource consumption. This results in CPU and GPU utilization approaching 0% after FastAVM is turned off, minimizing system resource waste. Simultaneously, the system can achieve smooth STR (Stroke Array) switching without lag, further optimizing operational smoothness and enhancing the user experience.

[0048] This invention significantly improves code quality and reduces development and adaptation costs through architecture optimization and standardized management. It adopts a mapping table-driven architecture, completely eliminating numerous conditional compilation statements, simplifying code structure, greatly improving code reusability, reducing redundant code, and facilitating code maintenance and iteration. For adaptation requirements of new vehicle models, no modification to the core code is needed; only adjustments to relevant configurations are required, significantly reducing adaptation costs and shortening the adaptation cycle. Unified timer management effectively avoids resource leaks, ensuring stable system operation. The PPS subscription mapping table mechanism effectively avoids omissions or duplications during the subscription process, further improving the stability and reliability of system operation.

[0049] This invention is adaptable to different platforms and multiple vehicle models, reducing platform switching and product line expansion costs. The system simultaneously supports both Kanzi 3.6 and Kanzi 3.9 versions, adapting to different API interfaces through conditional compilation. This allows for platform switching without significant modifications to the core code, effectively reducing platform switching costs. It can run stably on multiple vehicle models under development, and when adding new models, no modifications to the core system code are required; only configuration adjustments are needed for adaptation. This significantly improves product line scalability and meets the needs of batch development of multiple vehicle models.

[0050] This invention further enhances driving safety and improves system robustness through multiple safety mechanisms. A special protection mechanism for the reverse gear (R) is designed for reversing scenarios. When the vehicle is in R (reverse), even if the FastAVM off button is accidentally pressed, the system will not unexpectedly disable the FastAVM function, ensuring continuous display during reversing and guaranteeing driving safety. A data verification mechanism is added to strictly verify the data received and processed by the system, while improving the outlier handling logic to effectively avoid display errors caused by data anomalies, thereby improving system robustness and ensuring stable and safe system operation. Attached Figure Description

[0051] To more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0052] Figure 1 This is a flowchart of a vehicle surround view rapid display method provided by one or more embodiments of the present invention.

[0053] Figure 2 This is a structural diagram of a vehicle surround view rapid display system provided by one or more embodiments of the present invention.

[0054] Figure 3 This is a functional logic diagram of a specific embodiment of the present invention.

[0055] Figure 4 This is a schematic diagram illustrating the FastAVM signal processing flow hierarchy in a specific embodiment of the present invention.

[0056] Figure 5 This is a flowchart illustrating the asynchronous initialization and background thread warm-up mechanism in a specific embodiment of the present invention.

[0057] Figure 6This is a schematic diagram of a mapping table-driven multi-vehicle adaptation architecture in a specific embodiment of the present invention.

[0058] Figure 7 This is a flowchart illustrating the FastAVM fast display in a cold start scenario according to a specific embodiment of the present invention.

[0059] Figure 8 This is a block diagram of an electronic device structure for a vehicle surround view rapid display method provided by one or more embodiments of the present invention. Detailed Implementation

[0060] The technical solution of the present invention will now be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0061] The terminology used in the embodiments of this application is for the purpose of describing particular embodiments only and is not intended to limit the application. The singular forms “a,” “said,” and “the” used in the embodiments of this application and the appended claims are also intended to include the plural forms, and “multiple” generally includes at least two unless the context clearly indicates otherwise.

[0062] It should be understood that the term "and / or" used in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0063] It should be understood that although the terms first, second, third, etc., may be used in the embodiments of this application, these descriptions should not be limited to these terms. These terms are only used to distinguish the descriptions. For example, first may also be referred to as second without departing from the scope of the embodiments of this application, and similarly, second may also be referred to as first.

[0064] Depending on the context, the words "if" or "if" as used here can be interpreted as "when," "when," "in response to determination," or "in response to detection." Similarly, depending on the context, the phrases "if determination" or "if detection (of the stated condition or event)" can be interpreted as "when determination," "in response to determination," "when detection (of the stated condition or event)," or "in response to detection (of the stated condition or event)."

[0065] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that an article or device that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such an article or device. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the article or device that includes said element.

[0066] Figure 1 This is a flowchart of a vehicle surround view rapid display method provided by one or more embodiments of the present invention.

[0067] like Figure 1 As shown, it includes the following steps:

[0068] Step S1: In response to the QNX real-time operating system startup command, perform asynchronous pre-initialization and background resource warm-up for the surround view function;

[0069] In one embodiment, asynchronous pre-initialization and background resource preheating are performed by a background thread asynchronously starting the surround view video stream, initializing the image acquisition device, and preparing the rendering environment after the rendering engine is loaded, while the main thread synchronously completes the vehicle signal monitoring.

[0070] Specifically, through the asynchronous pre-initialization and background thread warm-up mechanism under the QNX system, time-consuming operations such as starting the surround view video stream, initializing the camera equipment, and setting up the rendering environment are completed asynchronously in advance after the rendering engine is loaded. The main thread can listen to the vehicle signals synchronously without waiting. When the user puts the vehicle into reverse gear during a cold start, there is no need to reload resources, and the surround view can be output instantly, which greatly improves the display response speed in reversing scenarios and ensures driving safety.

[0071] Step S2: Obtain vehicle status and trigger surround view display when a reversing command is detected;

[0072] Step S3: When surround view is off, trigger the surround view rendering process based on the delay scheduling mechanism;

[0073] In one embodiment, a delay scheduling mechanism is also included, which starts a preset delay when the lookaround is turned off, continues rendering during the delay to complete the screen refresh, and terminates rendering after the delay expires to reduce system resource consumption.

[0074] Specifically, a delayed scheduling rendering mechanism is adopted. When surround view is turned off, a preset delay is started. During the delay, rendering continues to run to complete the full refresh of the double-buffered screen, which solves the problem of screen residue and ghosting on the performance-limited vehicle system platform from the root. After the delay expires, rendering is automatically terminated, which greatly reduces the invalid use of CPU and realizes intelligent management of system resources.

[0075] Step S4: Adaptively save and restore the system's hibernation / wake-up state;

[0076] Specifically, the adaptive saving and restoration switching of sleep and wake-up states is achieved by storing the view operation parameters through global state variables, and adapting the sleep and wake-up interface to different versions of rendering engines.

[0077] By saving the surround view operation parameters through global state variables, it can adaptively adapt to the sleep and wake-up interfaces of different rendering engine versions. After the system sleeps and wakes up, it can quickly restore the surround view working state without re-initialization. The switching process is smooth and stable, improving cross-platform compatibility and usage continuity.

[0078] Step S5: Use a configuration-based mapping method to manage functional events, interactive controls, and communication messages;

[0079] In one embodiment, the configurable mapping method manages the relationships between functional events, interactive controls, and communication messages through a preset mapping table, and achieves multi-vehicle compatibility by configuring replacement conditional compilation.

[0080] By adopting a configurable mapping table to uniformly manage the relationships between functional events, interactive controls, and communication messages, and replacing traditional conditional compilation code with a configurable approach, adding new car models only requires modifying the mapping table configuration, without changing the core business code. This eliminates code redundancy, reduces the probability of development errors, and significantly improves development efficiency and code reusability.

[0081] Step S6: Securely lock the surround view off function according to the vehicle's gear position.

[0082] Among them, the gear position safety protection specifically includes: real-time acquisition of vehicle gear position signals, and disabling the surround view shutdown control when in reverse gear.

[0083] Specifically, the surround view function is safely locked based on the vehicle's gear position. The surround view shutdown control is automatically disabled when the vehicle is in reverse gear to prevent users from accidentally turning off the surround view screen. This ensures that the road conditions are visible in real time during reversing and comprehensively improves the safety and reliability of the vehicle surround view system.

[0084] Figure 2 This is a structural diagram of a vehicle surround view rapid display system provided by one or more embodiments of the present invention.

[0085] like Figure 2 As shown, it includes:

[0086] Hardware support layer, virtualization management layer, real-time operating system side fast surround view unit, Android operating system side full-function surround view unit and vehicle communication and interaction unit;

[0087] The fast surround view unit integrates an asynchronous pre-initialization module, a rendering intelligent control module, a sleep / wake-up adaptation module, a configurable vehicle model adaptation module, and a gear safety protection module.

[0088] The hardware support layer provides the hardware acquisition, processing, and display foundation for the surround view function;

[0089] The virtualization management layer is used to achieve hardware resource isolation between the two systems and to forward display data;

[0090] The vehicle communication interaction unit is used to realize two-way interaction between the system and the vehicle status signals;

[0091] The full-featured surround view unit on the Android operating system side is used to provide complete surround view functionality services;

[0092] Real-time operating system side fast surround view unit integration: asynchronous pre-initialization module, rendering intelligent control module, sleep wake-up adaptation module, configurable vehicle model adaptation module, gear position safety protection module;

[0093] The asynchronous pre-initialization module is used to perform asynchronous loading and pre-start of the lookup resources in the background, improving the cold start response speed;

[0094] The rendering intelligent management module is used to manage the rendering process based on latency strategies, reducing system resource consumption and avoiding image residue.

[0095] The hibernation / wake-up adaptation module is used to save and restore the system's hibernation / wake-up state and adapt to multiple rendering engine versions;

[0096] The configurable vehicle adaptation module is used to achieve hardware and function compatibility across multiple vehicle models through configuration mapping, simplifying the adaptation process.

[0097] The gear position safety protection module is used to safely lock the surround view function according to the vehicle's gear position to prevent the function from being abnormally shut down when reversing.

[0098] In one embodiment, the hardware support layer includes an image acquisition device, a vehicle status sensor, an on-board computing chip, and a display output device.

[0099] In one embodiment, the virtualization management layer completes the fusion and data pass-through of the display layers of the real-time operating system and the Android system through the hardware virtualization interface.

[0100] In one embodiment, the asynchronous pre-initialization module independently executes the start-up of the surround-view video stream, the initialization of the image acquisition device, and the preparation of the rendering environment through a background thread, while the main thread synchronously completes the monitoring of the vehicle status.

[0101] In one embodiment, the rendering intelligent control module initiates a delayed rendering strategy when surround view is turned off, keeps the screen refreshed completely during the delay period, and terminates rendering after the delay ends to release system resources.

[0102] In one embodiment, the sleep / wake-up adaptation module stores the look-around operation parameters through a global state variable, is compatible with the sleep and wake-up interfaces of different versions of rendering engines, and achieves smooth recovery.

[0103] In one embodiment, the configurable vehicle model adaptation module manages function events, interactive controls, and communication messages in a unified manner through a preset mapping table, and achieves multi-vehicle model adaptation by replacing conditional compilation in a configurable way.

[0104] In one embodiment, the gear safety protection module acquires the vehicle's gear signal in real time, disables the surround view shutdown control when in reverse gear, and restores the control to an available state when not in reverse gear.

[0105] In one embodiment, the real-time operating system-side fast surround view unit and the Android operating system-side full-function surround view unit achieve state synchronization and seamless function switching through the vehicle communication interaction unit.

[0106] It is worth noting that although only some basic functional modules are disclosed in this embodiment, it does not mean that the composition of this system is limited to the above-mentioned basic functional modules. On the contrary, what this embodiment intends to express is that, based on the above-mentioned basic functional modules, those skilled in the art can arbitrarily add one or more functional modules in combination with existing technology to form an infinite number of embodiments or technical solutions. That is to say, this system is open rather than closed. The fact that this embodiment only discloses a few basic functional modules does not mean that the scope of protection of the claims of this invention is limited to the disclosed basic functional modules. At the same time, for the convenience of description, the above device is described separately according to its functions as various units and modules. Of course, in implementing this invention, the functions of each unit and module can be implemented in one or more software and / or hardware.

[0107] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0108] Figure 3 This is a functional logic diagram of a specific embodiment of the present invention.

[0109] This embodiment provides an in-vehicle panoramic imaging (AVM) system based on a QNX-Android dual-system virtualization architecture. The overall architecture, from top to bottom, includes a hardware layer, a QNX Hypervisor virtualization layer, a vehicle communication layer, a QNX-side FastAVM module, an Android-side full-version AVM module, and a display screen.

[0110] The hardware layer includes cameras, body sensors, an 8155 SoC main control chip, and an in-vehicle display screen. The cameras are positioned around the front, rear, left, and right sides of the vehicle to collect real-time video streams around the vehicle. The body sensors are used to collect vehicle perception signals such as vehicle speed, gear position, steering angle, and parking status. The 8155 SoC is the main control unit, providing computing power, video encoding and decoding, and hardware virtualization support. The hardware layer transmits the collected raw video streams and vehicle perception signals to the QNXHypervisor virtualization layer.

[0111] The QNX Hypervisor virtualization layer uses the VirtIO hardware isolation forwarding mechanism to virtualize and isolate the hardware resources of the 8155 SoC, allocating camera hardware paths to both the QNX and Android systems to avoid hardware resource contention between the two systems. It also handles the underlying forwarding of multiple camera video streams, ensuring low-latency video data transmission. The vehicle communication layer constructs a vehicle signal transmission link based on the CAN bus and PPS timing service. The CAN bus receives vehicle status signals such as gear position, speed, and steering angle from the vehicle controller, while the PPS service provides a high-precision clock synchronization signal. The vehicle communication layer synchronously sends these vehicle status signals to the FastAVM module on the QNX side and the full-version AVM module on the Android side.

[0112] On the QNX side, a FastAVM high-speed panoramic imaging module is deployed to achieve low-latency and rapid panoramic image output. Specifically, it performs the following functions: It enables an independent asynchronous thread to preload the camera video stream forwarded by the virtualization layer, completing video stream decoding and caching in advance; it uses a PPS mapping table to uniformly send and receive vehicle status signals, completing signal timing alignment and signal verification; it configures a dual-flag rendering loop with a start flag and a ready flag, starting basic image rendering upon power-on; it implements a 500ms delay pause to reduce load in low-speed reversing scenarios, appropriately reducing the rendering load; and it uses the Kanzi rendering engine to achieve high-speed panoramic image rendering, prioritizing the output of the rendered basic panoramic image to the display screen.

[0113] The full version of the AVM module is deployed on the Android side. This module starts silently in the background and takes over the panoramic image output after the system is ready. The full version of the AVM module implements full-function application logic such as 360° panoramic stitching, dynamic reversing trajectory, and blind spot warning. It provides rich UI interaction such as panoramic image zooming, perspective switching, and mode selection, and reserves interfaces to expand third-party functions such as parking assistance and driving recording.

[0114] The display receives the screen output from both systems and executes priority output logic: when the vehicle is powered on or in reverse gear, it prioritizes receiving the basic panoramic image output from the QNX side FastAVM to achieve ultra-fast image output; when the Android side full version AVM module is ready in the background, the display seamlessly switches to the full-featured panoramic image output from the Android side, completing a smooth transition from ultra-fast image output to full-featured interaction.

[0115] This embodiment utilizes a QNX-Android dual-system virtualization architecture, combining the fast, real-time boot capabilities of the QNX system with the full-featured expandability of the Android system. By employing VirtIO hardware isolation forwarding and PPS signal synchronization to ensure the stability of signal and video stream transmission, it effectively achieves millisecond-level ultra-fast image output for in-vehicle panoramic imaging. At the same time, it provides rich human-computer interaction and expansion functions, enhancing driving safety and user experience in reversing scenarios.

[0116] Figure 4 This is a schematic diagram illustrating the FastAVM signal processing flow hierarchy in a specific embodiment of the present invention.

[0117] like Figure 4 As shown, the signal processing flow of the QNX-side FastAVM high-speed panoramic imaging module in this invention is described in detail.

[0118] In this embodiment, the FastAVM module is divided into an input layer, a FastAVM core processing layer, and an output layer, realizing the full-link processing of multi-source signal reception, timing synchronization, security verification, status update, rendering scheduling, and screen output for the entire vehicle.

[0119] The input layer is used to receive the vehicle PPS signal and various vehicle interaction signals sent by the vehicle, including gear position signal, radar signal, door status signal, theme configuration signal, language configuration signal, STR steering signal, AVM display control signal, view switching signal, etc., providing all the external input data required for panoramic image rendering for the FastAVM module.

[0120] The FastAVM core processing layer sequentially executes signal distribution, data parsing and verification, global state update, and rendering loop scheduling: First, through the PPS mapping table unified distribution unit, a standardized signal mapping relationship is established based on the vehicle's PPS high-precision timing signal. This ensures timing alignment, classification, and unified distribution of various input signals, guaranteeing synchronous input from multiple sources and preventing signal timing errors. Next, through the data parsing and validity verification unit, protocol parsing, format verification, threshold verification, and validity judgment are performed on the distributed signals, filtering invalid signals and abnormal interference data to ensure the reliability of the input signals. Then, through the global state update unit, the verified valid signals are synchronously updated to the FastAVM global state machine, synchronizing the operating status in real time, including gear position, radar distance, door status, display theme, and display view. Finally, through the dual-flag rendering loop unit, based on the updated global state, a dual-state scheduling logic using a start flag and a ready flag continuously drives the rendering engine to execute basic panoramic image rendering, achieving stable rendering output with low latency and no black screen.

[0121] The output layer is used to display the panoramic image UI. Based on the rendering results of the core processing layer, it outputs the AVM panoramic main page, multi-view switching screen, radar distance prompt information, gear status indicator, and display interface matching the set theme on the vehicle display screen, thus completing the real-time visualization of the panoramic image.

[0122] This embodiment uses the vehicle PPS timing signal as the timing reference to achieve unified management and control of multi-source vehicle signals. It ensures data security and reliability through signal validity verification and achieves extremely fast and stable image output by relying on dual-flag rendering loop. It fully adapts to the low latency and high reliability characteristics of the QNX hard real-time system, effectively improving the startup speed and image stability of the vehicle panoramic image.

[0123] Figure 5 This is a flowchart illustrating an intelligent rendering scheduling mechanism based on a delay timer in a specific embodiment of the present invention.

[0124] This embodiment is applied to the FastAVM panoramic surround view start / stop control of the in-vehicle Kanzi cockpit system. It addresses the technical pain points of limited vehicle host performance and the image residue caused by Kanzi's dual-buffer refresh after AVM is turned off. It adopts a 500ms delay timer to achieve intelligent rendering scheduling, while being compatible with both Kanzi 3.6 and 3.9 versions, taking into account the integrity of the image display, CPU power consumption control, and smooth user interaction.

[0125] Includes the following steps:

[0126] Step 1: Receive the AVM shutdown command and perform basic hiding operations.

[0127] After the user clicks to close AVM, the system executes the basic hidden interface logic:

[0128] Set the ShowPage flag to false to hide the AVM panoramic view main page;

[0129] Simultaneously hide the AVM's accompanying view switching button and wheel control button to quickly hide the upper UI interface.

[0130] Step 2: Start the delay timer to ensure a complete refresh of the double-buffered screen.

[0131] The system calls the timer API adapted to the current Kanzi version (3.6 / 3.9) to start a 500ms delay timer;

[0132] The AVM rendering loop continues to run during the delay period without immediately terminating the rendering process;

[0133] For scenarios where vehicle infotainment system performance is limited and resources are insufficient, a 500ms delay buffer is used to fully execute the Kanzi double buffer refresh action, avoiding the problem of residual images and ghosting in the last frame caused by rendering stopping immediately.

[0134] Step 3: Two branch scheduling logics within the delay period

[0135] The system continuously monitors in real time whether the user triggers the AVM reopen command within a 500ms delay window, and executes the scheduling in two scenarios:

[0136] Scenario A: The user reopens AVM within 500ms.

[0137] The system immediately cancels the running 500ms delay timer;

[0138] Reset the ShowPage flag to true to quickly display the AVM page;

[0139] Completely remove the timer task and keep the original rendering loop running continuously;

[0140] It directly outputs a surround view image, enabling millisecond-level fast restart response and improving the user interaction experience in reversing and moving scenarios.

[0141] Scenario B: 500ms timer expires, no AVM restart command issued.

[0142] The system sets the global signal flag g_FlagSignal to Kanzi_AVM_CLOSE;

[0143] After verifying the status of the two flags, stop the AVM rendering loop and terminate the video stream rendering process;

[0144] By freeing up rendering computing resources, the CPU utilization of the AVM module drops from 20%-30% to near 0, avoiding power waste caused by invalid rendering.

[0145] Specifically, it addresses the issues of image ghosting and residual images after the AVM (Autonomous Visualization) is turned off on performance-constrained in-vehicle infotainment platforms, ensuring the integrity of the display effect; it promptly stops rendering after a timeout, effectively reducing unnecessary CPU power consumption; it supports rapid restart during the delay window period, adapting to high-frequency start-stop vehicle scenarios and improving user experience; and it is compatible with both versions of the Kanzi platform, offering strong versatility and reducing project development and maintenance costs.

[0146] Figure 6 This is a schematic diagram of a mapping table-driven multi-vehicle adaptation architecture in a specific embodiment of the present invention.

[0147] like Figure 6 As shown, this embodiment is applied to the Kanzi application layer development of the in-vehicle FastAVM panoramic surround view system. Based on the mapping table-driven architecture, it achieves rapid adaptation to multiple vehicle models and unified scheduling and processing of multiple types of events. The overall process combines application loading, mapping table initialization, PPS message subscription, multi-source event distribution, and interface refresh. The specific implementation steps are as follows:

[0148] When the vehicle system powers on, after the Kanzi application executes the onProjectLoaded callback (application loading complete), the system first loads three core mapping tables: the state mapping table, the button mapping table, and the PPS subscription mapping table. In this embodiment, the C++ standard container std::unordered_map is used to construct the above mapping relationships, establishing key-value mappings between event IDs, interface node IDs, and PPS message topics and their corresponding business processing functions. At the same time, the mapping table configuration for the corresponding vehicle model is selected during the compilation phase through macro definitions, eliminating a large amount of vehicle model conditional compilation branch code in traditional development.

[0149] After the mapping table is loaded, the system automatically completes the subscription operation for all required PPS messages based on the PPS subscription mapping table, and continuously listens for various PPS interaction events issued by the vehicle's infotainment system. When a PPS message arrives, the system automatically distributes it to the corresponding processing logic through the mapping table according to the message type, which is divided into four types of event execution branches:

[0150] State events: Invoke the processing function bound to the state mapping table to execute state control logic such as AVM perspective switching;

[0151] Button events: Call the handler function bound to the button map to respond to user interface button interactions;

[0152] Gear position event: Match the corresponding processing logic according to the mapping table, control the display state of the X button, and update the vehicle gear position information synchronously;

[0153] Radar event: Performs radar data parsing, data verification, and distance information update operations.

[0154] After the business logic processing of the four types of events is completed, the Kanzi interface is updated in a unified manner, and the processing results are synchronously rendered to the vehicle display terminal.

[0155] In this embodiment, when a new compatible vehicle model is added, developers only need to modify the configuration of the three major mapping tables, supplementing the corresponding vehicle model's event ID, node ID, PPS topic, and processing function mapping relationships. No changes to the AVM core business code are required, achieving centralized and unified management of event handling, view mapping, and PPS subscription. This architecture effectively improves code reusability, reduces code redundancy and potential defects caused by conditional compilation, lowers the development and maintenance costs of multi-vehicle adaptation, and significantly improves the efficiency of vehicle model iteration development.

[0156] Figure 7 This is a flowchart illustrating the FastAVM fast display in a cold start scenario according to a specific embodiment of the present invention.

[0157] like Figure 7 As shown, this embodiment is applied to a QNX+Android dual-system in-vehicle cockpit platform. Addressing scenarios where the Android system boots up slowly during cold starts and users need to quickly view the surround-view screen after shifting into reverse, it achieves millisecond-level output of the surround-view screen even when the Android system is not ready through asynchronous preheating of FastAVM on the QNX side, background thread preloading, and dual-system timing scheduling. The specific implementation process is as follows:

[0158] After the vehicle completes a cold start, the QNX system starts first, taking 2-5 seconds to complete the underlying system initialization. Once the QNX system is ready, it triggers the FastAVM application initialization, executes the onProjectLoaded callback, and then starts the FastAVM asynchronous initialization and background warm-up process. In this embodiment, an independent background thread is created to start the AVM core service. The background thread executes the following in sequence: calling startAVM() to wake up the AVM video stream, initializing the data acquisition from the vehicle camera, pre-setting the Kanzi rendering environment, and simultaneously subscribing to all PPS messages based on the PPS subscription mapping table ppsSubscriptionMap to achieve real-time monitoring of automotive-grade signals such as gear position, status, and radar. The main thread does not block while waiting for the background thread to execute, ensuring system scheduling efficiency.

[0159] When the user shifts into reverse (R) to check the road conditions behind, the gear detection module recognizes the R signal and sends the `AVM_SHOW = 1` command via the PPS protocol. Upon receiving the signal, FastAVM triggers the `avm_show_callback(Kanzi_AVM_OPEN)` callback function, which immediately calls `onAvm(kanzi_AVM_ShowPage, true)` to quickly wake up and display the FastAVM page. Simultaneously, `onAvmTimeOut_init()` is called to configure view parameters, remove the AVM shutdown delay timer, and set the global flag `g_FlagSignal = Kanzi_AVM_OPEN`. After the rendering loop verifies the status of both flags, real-time rendering begins, outputting the surround-view image in just 150-200ms, meeting the user's need to check road conditions immediately while reversing, without waiting for the Android system to boot.

[0160] During the continuous output of the surround view display by FastAVM, the system waits in parallel for the Android system to start (taking 10-20 seconds); it continuously monitors the Android system's readiness status, and once the Android system is fully ready, it automatically switches to the complete AVM service on the Android side to take over the surround view display. The entire cold start-surround view display-system switching process takes 800-1000ms, ensuring a safe reversing experience for users while achieving orderly collaborative scheduling between the QNX and Android dual systems.

[0161] This embodiment addresses the pain point of AVM's inability to quickly display when the Android system is not ready during the vehicle's cold start phase by prioritizing QNX-side startup and using an asynchronous background warm-up mechanism. It balances the real-time performance, security, and compatibility of the dual-system platform in the cold start scenario.

[0162] Figure 8 This is a block diagram of an electronic device structure for a vehicle surround view rapid display method provided by one or more embodiments of the present invention.

[0163] like Figure 8 As shown, this application provides an electronic device, including: a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus;

[0164] The memory stores a computer program that, when executed by the processor, causes the processor to perform the steps of a vehicle surround view fast display method.

[0165] This application also provides a computer-readable storage medium storing a computer program executable by an electronic device, which, when run on the electronic device, causes the electronic device to perform the steps of a vehicle surround view fast display method.

[0166] For the sake of simplicity, the method embodiments are described as a series of actions. However, those skilled in the art should understand that the embodiments of the present invention are not limited to the described order of actions, because according to the embodiments of the present invention, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions involved are not necessarily essential to the embodiments of the present invention.

[0167] As can be seen from the above description of the embodiments, those skilled in the art can clearly understand that this application can be implemented by means of software plus necessary general-purpose hardware platforms. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in various embodiments or some parts of the embodiments of this application.

[0168] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for rapid display of vehicle surround view, applied to a virtualized vehicle architecture including a real-time operating system and an Android system, characterized in that, include: In response to the QNX real-time operating system startup command, asynchronous pre-initialization and background resource warm-up are performed on the surround view function; Obtain vehicle status and trigger surround view display when a reversing command is detected; When surround view is off, the surround view rendering process is triggered based on a delay scheduling mechanism. Adaptively save and restore the system's hibernation / wake-up state; Functional events, interactive controls, and communication messages are managed using a configuration-based mapping approach. The surround view function is locked for safety based on the vehicle's gear position.

2. The vehicle surround view rapid display method according to claim 1, characterized in that, The asynchronous pre-initialization and background resource preheating are specifically as follows: after the rendering engine is loaded, the background thread asynchronously completes the startup of the surround view video stream, the initialization of the image acquisition device and the preparation of the rendering environment, while the main thread synchronously completes the monitoring of the whole vehicle signal.

3. The vehicle surround view rapid display method according to claim 1, characterized in that, The delay scheduling mechanism specifically involves starting a preset delay when the surround view is turned off, maintaining rendering during the delay to complete the screen refresh, and terminating rendering after the delay expires to reduce system resource consumption.

4. The vehicle surround view rapid display method according to claim 1, characterized in that, The adaptive saving and restoration switching of the hibernation and wake-up state is specifically achieved by storing the surrounding operation parameters through a global state variable, and adapting the hibernation and wake-up interface to different versions of the rendering engine.

5. The vehicle surround view rapid display method according to claim 1, characterized in that, The configurable mapping method specifically involves managing the relationships between functional events, interactive controls, and communication messages in a unified manner through a preset mapping table.

6. The vehicle surround view rapid display method according to claim 1, characterized in that, The gear safety protection specifically involves: acquiring the vehicle's gear signal in real time and disabling the surround view shutdown control when in reverse gear.

7. A vehicle-mounted surround-view rapid display system, applied to a virtualized vehicle architecture including a real-time operating system and an Android system, characterized in that, include: Hardware support layer, virtualization management layer, real-time operating system side fast surround view unit, Android operating system side full-function surround view unit and vehicle communication and interaction unit; The hardware support layer is used to provide the hardware acquisition, processing and display foundation for the surround view function; The virtualization management layer is used to achieve hardware resource isolation between the two systems and display data forwarding; The vehicle communication interaction unit is used to realize two-way interaction between the system and the vehicle status signals; The full-function surround view unit on the Android operating system side is used to provide complete surround view function services; The real-time operating system-side fast surround view unit integrates an asynchronous pre-initialization module, a rendering intelligent control module, a sleep / wake-up adaptation module, a configurable vehicle model adaptation module, and a gear safety protection module. The asynchronous pre-initialization module is used to perform asynchronous loading and pre-start of the surround view resources in the background, thereby improving the cold start response speed. The rendering intelligent management module is used to manage the rendering process based on a delay strategy, thereby reducing system resource consumption and avoiding image residue. The hibernation / wake-up adaptation module is used to save and restore the system's hibernation / wake-up state and adapt to multiple rendering engine versions. The configurable vehicle adaptation module is used to achieve hardware and function compatibility of multiple vehicle models through configuration mapping, simplifying the adaptation process. The gear safety protection module is used to lock the surround view function according to the vehicle's gear status to prevent the function from being abnormally shut down when reversing.

8. The vehicle-mounted surround-view rapid display system according to claim 7, characterized in that, The virtualization management layer completes the fusion of the display layers of the real-time operating system and the Android system and data pass-through through the hardware virtualization interface.

9. An electronic device, characterized in that, include: The processor, communication interface, memory, and communication bus are connected, with the processor, communication interface, and memory communicating with each other via the communication bus. The memory stores a computer program, which, when executed by the processor, causes the processor to perform the steps of the vehicle surround view fast display method according to any one of claims 1-6.

10. A computer-readable storage medium, characterized in that, It stores a computer program executable by an electronic device, which, when run on the electronic device, causes the electronic device to perform the steps of the vehicle surround view fast display method as described in any one of claims 1-6.

Images