Display method, intelligent cabin, vehicle, storage medium and computer program product

Abstract

The invention can be applied to the field of intelligent cabins, and particularly relates to a display method, an intelligent cabin, a vehicle, a storage medium and a computer program product. The display method comprises the following steps: acquiring instrument data to be displayed and central control data; performing rendering processing on the instrument data based on the first system service to obtain first rendering data; performing rendering processing on the central control data based on the second system service to obtain second rendering data; and performing data display on the same display screen based on the first rendering data and the second rendering data. According to the embodiment of the invention, the stability of the display screen for displaying the corresponding instrument data and central control data can be improved, and the safety of the vehicle where the display screen is located is improved.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to the field of intelligent cockpit, and in particular, to a display method, an intelligent cockpit, a vehicle, a storage medium and a computer program product. BACKGROUND

[0002] With the development of vehicle electrification, the vehicle intelligent cockpit integrates more and more screens. For example, an In-Vehicle Infotainment (IVI) screen, which is used as an entertainment screen, can be used for listening to music or navigation, etc.; and a vehicle instrument screen, which is used to display key information in the vehicle driving process, such as vehicle speed, engine state or airbag state, etc. In addition, the IVI content and the instrument content can also be displayed in the same screen. However, when the IVI content and the instrument content are displayed in the same screen at the same time, the stability of the IVI content and the instrument content displayed on the screen is poor. SUMMARY

[0003] To overcome the problems in the related art, the present disclosure provides a display method, an intelligent cockpit, a vehicle, a storage medium and a computer program product, which can improve the stability of the display screen in displaying corresponding instrument data and IVI data, and improve the safety of the vehicle where the display screen is located.

[0004] According to a first aspect of an embodiment of the present disclosure, a display method is provided, comprising at least:

[0005] obtaining instrument data and IVI data to be displayed;

[0006] rendering the instrument data based on a first system service to obtain first rendering data;

[0007] rendering the IVI data based on a second system service to obtain second rendering data;

[0008] performing data display on the same display screen based on the first rendering data and the second rendering data.

[0009] In some embodiments, the performing data display on the same display screen based on the first rendering data and the second rendering data comprises:

[0010] performing synthesis processing on the first rendering data and the second rendering data to obtain target rendering data;

[0011] displaying the target rendering data on the same display screen.

[0012] In some embodiments, the operating system of the first system service is a native system, and the rendering the instrument data based on the first system service to obtain first rendering data comprises:

[0013] render the instrument data based on a first rendering service of the native system to obtain the first rendering data; wherein a process executing the first rendering service is a native process.

[0014] In some embodiments, the rendering of the instrument data based on the first rendering service of the native system to obtain the first rendering data comprises:

[0015] rendering the instrument data based on the first rendering service supported by a graphic processing unit in the native system to obtain the first rendering data.

[0016] In some embodiments, the operating system of the second system service is a non-native system, and the rendering of the central control data based on the second system service to obtain the second rendering data comprises:

[0017] rendering the central control data based on a second rendering service of the non-native system to obtain the second rendering data; wherein a process executing the second rendering service is a non-native process.

[0018] In some embodiments, the non-native system is an Android system, and the rendering of the central control data based on the second rendering service of the non-native system to obtain the second rendering data comprises:

[0019] in response to the processing capability of a hardware compositor in the Android system satisfying a preset capability condition, rendering the central control data based on the second rendering service and obtaining the second rendering data based on the hardware compositor;

[0020] in response to the processing capability of the hardware compositor in the Android system not satisfying the preset capability condition, rendering the central control data based on the second rendering service of the non-native process and the first rendering service of a native process and obtaining the second rendering data based on the hardware compositor.

[0021] In some embodiments, the rendering of the central control data based on the second rendering service and the obtaining of the second rendering data based on the hardware compositor comprise:

[0022] converting the central control data into a plurality of layer data based on the second rendering service and rendering each of the layer data to obtain a plurality of rendered layers; wherein the different layer data correspond to different data contents.

[0023] compositing the plurality of rendered layers based on the hardware compositor to obtain the second rendering data.

[0024] In some embodiments, the central control data includes a first part of data and a second part of data. The rendering processing of the central control data based on the second rendering service (non-native process) and the first rendering service (native process) to obtain the second rendering data based on the hardware compositor includes:

[0025] The first part of the data is rendered based on the first rendering service to obtain the first part of the rendered data.

[0026] The second part of the data is rendered using the second rendering service to obtain the second part of the rendered data; wherein the rendering complexity of the first part of the data is greater than that of the second part of the data.

[0027] The hardware synthesizer is used to synthesize the first part of the rendering data and the second part of the rendering data to obtain the second rendering data.

[0028] According to a second aspect of the present disclosure, a smart cockpit is provided, comprising at least:

[0029] The acquisition module is configured to acquire instrument data and central control data to be displayed;

[0030] The first processing module is configured to render the instrument data based on the first system service to obtain first rendered data.

[0031] The second processing module is configured to perform rendering processing on the central control data based on the second system service to obtain second rendered data.

[0032] The display module is configured to display data on the same display screen based on the first rendering data and the second rendering data.

[0033] In some embodiments, the display module is specifically configured to: perform composite processing on the first rendering data and the second rendering data to obtain target rendering data; and display the target rendering data on the same display screen.

[0034] In some embodiments, the operating system of the first system service is a native system, and the first processing module is specifically configured to: perform rendering processing on the instrument data based on the first rendering service of the native system to obtain the first rendered data; wherein, the process executing the first rendering service is a native process.

[0035] In some embodiments, the first processing module is further configured to: perform rendering processing on the instrument data based on the first rendering service supported by the graphics processor in the native system to obtain the first rendered data.

[0036] In some embodiments, the operating system of the second system service is a non-native system, and the second processing module is specifically configured to: perform rendering processing on the central control data based on the second rendering service of the non-native system to obtain the second rendering data; wherein, the process executing the second rendering service is a non-native process.

[0037] In some embodiments, the non-native system is an Android system, and the second processing module is further configured to: in response to the processing capability of the hardware compositor in the Android system meeting a preset capability condition, perform rendering processing on the central control data based on the second rendering service, and obtain the second rendered data based on the hardware compositor; in response to the processing capability of the hardware compositor in the Android system not meeting the preset capability condition, perform rendering processing on the central control data based on the second rendering service of the non-native process and the first rendering service of the native process, and obtain the second rendered data based on the hardware compositor.

[0038] In some embodiments, the second processing module is further configured to: convert the central control data into multiple layer data based on the second rendering service, and perform rendering processing on each of the layer data respectively to obtain each rendered layer; wherein, the data content corresponding to different layer data is different; and perform compositing processing on each rendered layer based on the hardware compositor to obtain the second rendering data.

[0039] In some embodiments, the central control data includes a first part of data and a second part of data, and the second processing module is further configured to: perform rendering processing on the first part of data based on the first rendering service to obtain a first part of rendered data; perform rendering processing on the second part of data based on the second rendering service to obtain a second part of rendered data; wherein the rendering complexity of the first part of data is greater than the rendering complexity of the second part of data; and perform compositing processing on the first part of rendered data and the second part of rendered data based on the hardware compositor to obtain the second part of rendered data.

[0040] According to a third aspect of the present disclosure, a vehicle is provided, comprising at least:

[0041] processor;

[0042] Memory used to store computer programs or instructions;

[0043] The processor executes the computer program or instructions to implement the display method described in the first aspect.

[0044] According to a fourth aspect of the present disclosure, a non-transitory computer-readable storage medium is provided, the storage medium storing a computer program or instructions that, when executed by a processor, implement the steps of the display method described in the first aspect.

[0045] According to a fifth aspect of the present disclosure, a computer program product is provided, including a computer program or instructions, which, when executed by a processor, implement the steps of the display method described in the first aspect.

[0046] The technical solutions provided by the embodiments of this disclosure may include the following beneficial effects:

[0047] This disclosure provides a display method that uses a first system service to render instrument data to be displayed, obtaining first rendered data, and a second system service to render central control data to be displayed, obtaining second rendered data. The first and second rendered data are then displayed on the same screen. This ensures that the processing of instrument data by the first system service and the processing of central control data by the second system service do not interfere with each other, improving the stability of the display screen's display of the corresponding instrument and central control data and enhancing the user experience. Furthermore, due to the stable display of the instrument data on the screen, users can observe changes in the instrument data in real time, enabling them to take timely action in emergencies, thereby improving the safety of the vehicle where the display screen is located.

[0048] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0049] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure.

[0050] Figure 1 This is a flowchart illustrating a display method according to an exemplary embodiment. Figure 1 .

[0051] Figure 2a This is a schematic diagram of a display screen in a vehicle according to an exemplary embodiment. Figure 1 .

[0052] Figure 2b This is a schematic diagram two of a display screen in a vehicle according to an exemplary embodiment.

[0053] Figure 3 This is a system architecture diagram illustrating a display method according to an exemplary embodiment.

[0054] Figure 4 This is a flowchart illustrating a display method according to an exemplary embodiment.

[0055] Figure 5 This is a structural block diagram of an intelligent cockpit according to an exemplary embodiment.

[0056] Figure 6 This is a schematic diagram of the structure of a vehicle according to an exemplary embodiment. Detailed Implementation

[0057] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0058] The technical solutions provided by the embodiments of this disclosure are described in detail below with reference to the accompanying drawings.

[0059] In related technologies, a vehicle's intelligent cockpit can include a central control screen and an instrument panel screen; the central control screen is used as an entertainment screen and has low requirements for stability; the instrument panel screen is used to display key information during vehicle operation, such as vehicle speed, engine status, or airbag status, and has high requirements for stability.

[0060] Currently, there are three main approaches to setting up a central control screen and an instrument cluster screen in a vehicle's smart cockpit. The first approach involves all screens in the smart cockpit operating on a single System-on-Chip (SoC) platform. This utilizes a hypervisor virtual machine to create two independent operating systems: one for the central control screen and one for the instrument cluster screen. These two screens are hardware-independent. The second approach involves multiple SoCs operating on the same platform. The central control screen runs on one SoC, running an entertainment system like Android, while the instrument cluster screen runs on another SoC, running a different secure operating system, such as QNX. The third approach integrates the central control screen and the instrument cluster screen, with both displaying the same content rendered using a single system, such as Android.

[0061] However, this method of using the same system to render the central control content and instrument content displayed on the same screen leads to poor stability of the instrument content displayed on the same screen and poor accuracy of the corresponding instrument data.

[0062] In response, this disclosure provides a display method. Figure 1 This is a flowchart illustrating a display method according to an exemplary embodiment. Figure 1 ,like Figure 1 As shown, the display method provided in this embodiment includes at least the following steps:

[0063] S110: Obtain the instrument data and central control data to be displayed;

[0064] S120. Based on the first system service, the instrument data is rendered to obtain the first rendered data;

[0065] S130. Based on the second system service, the central control data is rendered to obtain the second rendering data;

[0066] S140. Display data on the same display screen based on the first rendering data and the second rendering data.

[0067] The display method provided in this disclosure can be applied to any vehicle with a display screen and at least two system services. In some embodiments, the above-described display method can also be applied to ships, aircraft, or head-up display (HUD) devices.

[0068] In steps S110-S130, the vehicle can render the instrument data to be displayed through the first system service to obtain the first rendered data; and the vehicle can render the central control data to be displayed through the second system service to obtain the second rendered data.

[0069] In some embodiments, such as Figure 2a and Figure 2b As shown, the vehicle's display screen L1 can include two display areas: the instrument cluster area L2 and the center console area L3. For example... Figure 2a As shown, a portion of the top area of ​​display screen L1 can be designated as instrument panel area L2, and the remaining area as central control area L3; for example... Figure 2b As shown, a portion of the left side of the display screen L1 can be designated as the instrument area L2, and the remaining area as the central control area L3.

[0070] Here, the instrument data to be displayed can be the instrument data that the vehicle needs to display in the instrument area of ​​the display screen; the central control data to be displayed can be the central control data that the vehicle needs to display in the central control area of ​​the display screen.

[0071] Taking the display method applied to a vehicle as an example, the instrument data to be displayed in this embodiment may include, but is not limited to: vehicle speed information, engine speed information, vehicle mileage information, remaining battery or fuel level information, coolant temperature information, warning information, and light status information. Warning information may include engine fault warning information, brake system fault warning information, and airbag system fault warning information. The central control data to be displayed may include, but is not limited to: navigation information, audio information, mobile phone connection status information, in-vehicle application software, monitoring information, and vehicle settings information. Vehicle settings information may include seat adjustment, air conditioning control, vehicle driving mode selection, and voice control settings.

[0072] In some embodiments, the first system service and the second system service may be different system services of the same operating system; or, the operating system of the first system service may be different from the operating system of the second system service, and this disclosure does not impose any restrictions.

[0073] In this embodiment of the disclosure, the operating system of the first system service can be the native system in the vehicle used to manage instrument data, such as an embedded operating system (e.g., QNX, RT-Linux, or VxWorks) or other real-time operating systems (RTOS); the first system service can be a native process in the native system. The operating system of the second system service can be a non-native system in the vehicle used to manage central control data, such as the Android system; the second system service can be a process in the Android system responsible for rendering processing.

[0074] It is understood that the rendering of instrument data based on the first system service to obtain the first rendered data may include, but is not limited to: rendering the instrument data based on the Open Graphics Library (OpenGL) rendering pipeline corresponding to the operating system of the first system service to obtain the first rendered data; or rendering the instrument data based on the Vulkan rendering pipeline corresponding to the operating system of the first system service to obtain the first rendered data.

[0075] OpenGL is a cross-platform graphics application programming interface (API) that specifies a standard software interface for 3D graphics processing hardware. Vulkan is also a cross-platform API for rendering 2D and 3D graphics, often referred to as "the next version of OpenGL." Vulkan offers better performance than OpenGL, and using the Vulkan rendering pipeline can bring advantages such as reduced rendering time per frame and improved smoothness.

[0076] Here, the rendering pipeline, also known as the rendering pipeline, pixel pipeline, or pixel pipeline, is a parallel processing unit within the display chip that processes image signals independently. The rendering pipeline is the process of converting a 3D scene model into the screen's pixel space for output. The image rendering process of the rendering pipeline can be abstracted into three stages: the application stage, which outputs rendered primitives; the geometry stage, which outputs vertex information in screen space; and the rasterization stage.

[0077] It should be noted that the first rendered data can be the data that can be displayed on the screen after the instrument data has been rendered.

[0078] It is understandable that the rendering of the central control data based on the second system service to obtain the second rendering data may include, but is not limited to: processes in the operating system of the second system service, such as Surfaceflinger, directly rendering the central control data to obtain the second rendering data; or, processes in the operating system of the second system service and the rendering pipeline corresponding to the operating system of the first system service, such as OpenGL or Vulkan rendering pipeline, together rendering the central control data to obtain the second rendering data.

[0079] SurfaceFlinger is a core component of the Android operating system, responsible for compositing and rendering content displayed on the screen. SurfaceFlinger provides the Hardware Composer (HWC) with a complete list of layers corresponding to applications in the system, allowing HWC to determine how to process these layers based on its hardware capabilities. HWC marks each layer with a compositing method: whether it's composited using the Graphics Processing Unit (GPU) or by HWC. All layers marked for GPU compositing can be rendered using the OpenGL rendering pipeline. SurfaceFlinger can then pass the layers rendered using the OpenGL pipeline, along with other layers marked for HWC compositing, to HWC, allowing HWC to complete the compositing and display of the remaining layers.

[0080] It should be noted that the second rendered data can be the data that can be displayed on the screen after rendering the central control data.

[0081] In this embodiment of the disclosure, instrument data and central control data are rendered separately by utilizing different first system services and second system services of two operating systems. This ensures that the first and second rendered data obtained after rendering will not affect each other due to a failure of one of the operating systems, thereby improving the stability of the data displayed on the screen.

[0082] In step S140, the vehicle can display data on the same display screen of the vehicle based on the first rendering data and the second rendering data, so as to realize the simultaneous display of instrument data and central control data on the same display screen.

[0083] It is understood that displaying data on the same display screen of the vehicle based on the first rendering data and the second rendering data may include, but is not limited to: displaying the corresponding instrument data in the instrument area of ​​the display screen based on the first rendering data, and displaying the corresponding central control data in the central control area of ​​the same display screen based on the second rendering data; or, firstly, synthesizing the first rendering data and the second rendering data to obtain the target rendering data, and then displaying the target rendering data on the same display screen.

[0084] In related technologies, as mentioned earlier, the central control screen and instrument panel are integrated in the vehicle's smart cockpit. The content displayed on the same screen, including both the central control and instrument panel information, is rendered using the same Android system. Due to various stability issues with the Android system, rendering the central control and instrument panel content together leads to poor stability of the displayed instrument panel content and inaccurate data. Consequently, users cannot observe accurate instrument panel data in real time, resulting in compromised driving safety.

[0085] In contrast, the display method provided in this embodiment can render the instrument data to be displayed through a first system service to obtain first rendered data, and render the central control data to be displayed through a second system service to obtain second rendered data. Then, the first and second rendered data are displayed on the same display screen. This ensures that the processing of instrument data by the first system service and the processing of central control data by the second system service do not interfere with each other, thereby improving the stability of the display screen displaying the corresponding instrument data and central control data and enhancing the user experience. Furthermore, due to the stable display of the instrument data on the display screen, users can observe the changes in the instrument data in real time, enabling them to take timely countermeasures in case of emergencies, thereby improving the safety of the vehicle where the display screen is located.

[0086] In some embodiments, step S140 may include:

[0087] The first and second rendering data are combined to obtain the target rendering data.

[0088] Display the target rendering data on the same screen.

[0089] In this embodiment of the present disclosure, the vehicle can first perform composite processing on the first rendering data and the second rendering data to obtain the target rendering data, and then display the target rendering data on the same display screen.

[0090] Here, the target rendering data can be rendering data that can display the corresponding instrument data and central control data on the display screen.

[0091] Understandably, based on the target rendering data, the corresponding instrument data can be displayed in the instrument area of ​​the display screen, and at the same time, based on the target rendering data, the corresponding central control data can be displayed in the central control area of ​​the same display screen, so as to realize the display of instrument data and central control data in different display areas of the same display screen of the vehicle.

[0092] It should be noted that after the vehicle combines the first and second rendering data into target rendering data, it outputs the data to the same display screen via a Clock and Timing Recovery Circuit (CRTC) shared by the first and second system services. The combined target rendering data can be stored in a frame buffer, and the CRTC is responsible for outputting the target rendering data from the frame buffer to the display screen according to a specified clock and timing sequence.

[0093] In this embodiment of the disclosure, target rendering data can be obtained by synthesizing the first rendering data and the second rendering data, and then the target rendering data can be displayed on the same display screen. This allows for better utilization of the two system services to display instrument data and central control data on the same display screen, thereby improving the stability of the display screen displaying the corresponding instrument data.

[0094] In some embodiments, the operating system served by the first system is a native system, and step S120 may include:

[0095] The instrument data is rendered using the first rendering service based on the native system to obtain the first rendered data; the process executing the first rendering service is the native process.

[0096] In this embodiment of the disclosure, the vehicle can render the instrument data according to the first rendering service of the native system to obtain the first rendered data; that is, the vehicle uses the native process of the native system to render the instrument data to obtain the first rendered data.

[0097] Here, the native system can be an operating system directly embedded in the vehicle, without relying on external device connections or projections. Native processes can be various programs or tasks running within the native system, and these processes can be directly managed and scheduled by the vehicle's native system.

[0098] The aforementioned first rendering service can be a service in the native system that can render instrument data; for example, the first rendering service can be the OpenGL rendering pipeline or the Vulkan rendering pipeline corresponding to the native system.

[0099] Understandably, the code in the native process of the native system can call the corresponding primary rendering service to render the instrument data and obtain the primary rendered data. For example, the vehicle's native process can call GPU APIs such as OpenGL or Vulkan to send rendering requests to the GPU. After receiving the request, the GPU executes the rendering operation on the instrument data to obtain the primary rendered data that can be displayed in the corresponding instrument area of ​​the screen.

[0100] In this embodiment of the disclosure, the instrument data can be rendered by the first rendering service of the native system to obtain the first rendered data, which is used to prepare for the subsequent display of the data on the same display screen. Furthermore, since the process executing the first rendering service is a native process, it will not affect the rendering of the instrument data by the native process of the native system when the other operating systems of the vehicle fail and affect the display of other data on the display screen, thereby improving the stability of the subsequent display of the corresponding instrument data.

[0101] In some embodiments, the instrument data is rendered based on the first rendering service of the native system to obtain first rendered data, including:

[0102] The instrument data is rendered using the first rendering service supported by the graphics processor in the native system to obtain the first rendered data.

[0103] In this embodiment of the present disclosure, the vehicle can render the instrument data according to the first rendering service supported by the graphics processor in the native system to obtain the first rendered data.

[0104] Here, the graphics processing unit (GPU) is also called a display chip. A GPU has a highly parallelized rendering pipeline (such as OpenGL or Vulkan). The rendering pipeline typically includes stages such as vertex shaders, geometry shaders, and fragment shaders, used to process instrument data. GPUs can reduce the reliance of graphics cards on the central processing unit (CPU).

[0105] Understandably, vehicles can call the GPU's rendering interface, such as APIs like OpenGL or Vulkan. This rendering interface can be used to transmit rendering instructions carrying instrument data to the GPU. After receiving the rendering instructions, the GPU can process the instrument data to obtain the first rendering data.

[0106] It should be noted that the vehicle may also include a Graphics System Library (GSL), which can provide wrappers or extensions for APIs such as OpenGL or Vulkan, making it easier to use the APIs for rendering on different operating systems. The vehicle may also include a Kernel Graphics System Layer (KGSL), which provides low-level support for GPU hardware drivers; for example, KGSL can be responsible for GPU driver initialization, configuration, and interaction with other system components.

[0107] In this embodiment, the instrument data can be rendered using a first rendering service supported by the graphics processor in the native system to obtain first rendered data, which is then used to prepare for subsequent data display on the same display screen. Since the first rendering service is supported by the graphics processor, it improves the rendering efficiency of the native system. Furthermore, by utilizing the first rendering service supported by the graphics processor, even if other operating systems in the vehicle malfunction and affect the display of other data on the screen, the rendering of the instrument data by the first rendering service supported by the graphics processor will not be affected, thereby improving the stability of the subsequent display of the corresponding instrument data.

[0108] In some embodiments, the operating system of the second system service is a non-native system, and step S130 may include:

[0109] The second rendering service based on the non-native system renders the central control data to obtain the second rendering data; the process executing the second rendering service is a non-native process.

[0110] In this embodiment of the disclosure, the vehicle can render the central control data according to the second rendering service of the non-native system to obtain the second rendering data; that is, the vehicle uses the non-native process of the non-native system to render the central control data to obtain the second rendering data.

[0111] Here, the non-native system can be an operating system used in the vehicle that is not originally installed in the vehicle, but is provided by a third-party or open-source platform. The non-native process can be various programs or tasks running in the vehicle's non-native system, and the non-native process can be directly managed and scheduled by the non-native system.

[0112] The aforementioned second rendering service can be a service in a non-native system that can perform rendering processing on the central control data; for example, the second rendering service can be a service in the Android system responsible for rendering processing, such as Surfaceflinger.

[0113] It is understood that the second rendering service can provide the layer list corresponding to the central control data to the hardware synthesizer. The vehicle can determine the rendering method for the central control data based on the processing capability of the hardware synthesizer in the non-native system. In this embodiment, there are two rendering methods for the central control data: the first method directly utilizes the second rendering service to render the central control data and obtains the second rendered data based on the hardware synthesizer; the second method uses both the second rendering service and the first rendering service of the native system to render the central control data together and obtains the second rendered data based on the hardware synthesizer.

[0114] For example, a vehicle can use SurfaceFlinger and HWC to render the central control data to obtain second rendered data; or, a vehicle can use SurfaceFlinger and HWC to render a portion of the central control data, and use the GPU's OpenGL or Vulkan rendering pipeline to render another portion of the central control data, together to obtain second rendered data.

[0115] In this embodiment, the central control data can be rendered using a second rendering service of a non-native system to obtain second rendered data, which is then used to prepare for subsequent data display on the same display screen. Furthermore, since the process executing the second rendering service is a non-native process that is distinct from the native process, it can avoid affecting the rendering of instrument data by the native process of the native system when the non-native system where the non-native process resides fails and affects the display of the central control data on the display screen. This improves the stability of the subsequent display of the corresponding instrument data on the display screen.

[0116] In some embodiments, the non-native system is an Android system. The central control data is rendered using a second rendering service based on the non-native system to obtain second rendered data, including:

[0117] In response to the fact that the processing capability of the hardware compositor in the Android system meets the preset capability conditions, the central control data is rendered based on the second rendering service, and the second rendering data is obtained based on the hardware compositor.

[0118] In response to the fact that the processing capability of the hardware compositor in the Android system does not meet the preset capability conditions, the central control data is rendered based on the second rendering service of the non-native process and the first rendering service of the native process, and the second rendering data is obtained based on the hardware compositor.

[0119] In this embodiment of the disclosure, the vehicle can determine the corresponding rendering method to render the central control data by judging whether the processing capability of the hardware synthesizer in the Android system meets the preset capability conditions, so as to obtain the second rendering data.

[0120] Here, the Hardware Composer (HWC) can be a component located in the Hardware Abstraction Layer (HAL) of the Android system. HWC can utilize the GPU and other hardware resources to composite multiple layers that can be displayed on the screen, reducing the burden on the CPU and GPU, improving display performance, and reducing power consumption.

[0121] It should be noted that the above-mentioned preset capability conditions can be set based on the performance of the hardware synthesizer, hardware specifications, or specific performance indicators, and this disclosure embodiment does not impose any restrictions.

[0122] Understandably, if the hardware compositor's processing power meets the preset requirements, the Android system can directly use the second rendering service to render the central control data and obtain the second rendered data based on the hardware compositor. If the hardware compositor's processing power does not meet the preset requirements, the Android system can use another rendering method, namely, combining the second rendering service (not native) and the first rendering service (native) to render the central control data together. After rendering, the data is then composited using the hardware compositor to obtain the second rendered data, enabling the Android system to achieve better rendering effects on low-performance hardware.

[0123] In this embodiment of the disclosure, the processing power of the hardware compositor in the Android system varies, allowing for consistent or acceptable rendering effects for central control data on Android systems with different performance levels. Furthermore, the rendering method for central control data can be dynamically adjusted based on the processing power of the hardware compositor. The Android system can ensure better rendering effects for central control data on high-performance hardware devices, while maintaining acceptable rendering effects on low-performance hardware devices, thereby improving the user experience.

[0124] In some embodiments, rendering processing of central control data is performed based on a second rendering service, and second rendering data is obtained based on a hardware compositor, including:

[0125] The central control data is converted into multiple layers of data based on the second rendering service, and each layer of data is rendered to obtain the rendered layers; the data content corresponding to different layers is different.

[0126] The hardware compositor is used to composite the rendered layers to obtain the second rendering data.

[0127] In this embodiment of the present disclosure, after the vehicle determines that the processing capability of the hardware synthesizer meets the preset capability conditions, it can first convert the central control data into multiple layers of data with different data contents according to the second rendering service, and then perform rendering processing on each layer of data to obtain each rendered layer. Then, the hardware synthesizer is used to synthesize each rendered layer to obtain the second rendering data.

[0128] Here, layer data can be all the data required to draw the visual elements corresponding to the central control data on the display screen. Each rendered layer can be the visualization result obtained after the layer data has been processed by the second rendering service, that is, the actual display of the layer data on the display screen, i.e., the display source of the display screen.

[0129] Understandably, the second system service receives central control data, which can include various types of information such as position, color, texture, or animation. The second system service can convert this central control data into multiple layer data, each layer representing an independent visual element or function, such as background, foreground elements, text, or icons. Furthermore, the second system service can perform rendering processing on each layer data, including but not limited to applying colors, textures, lighting effects, shadows, and animations. After rendering, each rendered layer is obtained, containing corresponding visual effects and attributes. Then, a hardware compositor can be used to composite all the rendered layers. Compositing involves stacking and blending the layers according to their position in the visual hierarchy, typically involving adjustments to parameters such as opacity and blending modes (e.g., overlay, multiplication, difference). After compositing, the final second rendering data is obtained, which can contain the complete visual effect of all layers combined.

[0130] For example, the SurfaceFlinger service in the Android system can receive central control data from multiple applications or services, and convert the received central control data into layer data that HWC can understand. Each layer data corresponds to a graphics buffer, and each graphics buffer stores the data content corresponding to each rendered layer. HWC receives the list of each rendered layer sent by the SurfaceFlinger service, and performs composite processing according to the hierarchical order of each rendered layer. The resulting second rendering data is output to a final output buffer so that it can be displayed on the screen.

[0131] In this embodiment of the disclosure, the central control data can be converted into multiple layer data through the second rendering service, and each layer data can be rendered to obtain each rendered layer. Then, the rendered layers can be composited by the hardware compositor to obtain the second rendering data. This allows the second rendering service of the Android system to better achieve the rendering effect of the central control data, thereby improving the performance and stability of the Android system.

[0132] In some embodiments, the central control data includes a first part of data and a second part of data. The central control data is rendered using a second rendering service (non-native process) and a first rendering service (native process), and the second rendering data is obtained based on a hardware compositor, including:

[0133] The first part of the data is rendered based on the first rendering service to obtain the first part of the rendered data.

[0134] The second part of the data is rendered using the second rendering service to obtain the second part of the rendered data; however, the rendering complexity of the first part of the data is greater than that of the second part of the data.

[0135] The first and second parts of the rendering data are combined using a hardware compositor to obtain the second rendering data.

[0136] In this embodiment of the disclosure, after the vehicle determines that the processing capability of the hardware synthesizer does not meet the preset capability conditions, it can use the first rendering service to render the first part of the central control data to obtain the first part of the rendered data, and use the second rendering service to render the second part of the central control data with a rendering complexity lower than that of the first part of the data to obtain the second part of the rendered data. Then, the hardware synthesizer is used to synthesize the first part of the rendered data and the second part of the rendered data to obtain the second rendered data.

[0137] Here, the first part of the data can be data from the central control data whose rendering complexity exceeds a preset threshold, that is, data from the central control data that corresponds to high rendering capabilities of the required rendering service. The first part of the rendering data can be the result obtained after rendering processing the first part of the data, which corresponds to the visualization result displayed on the screen.

[0138] The second part of the data mentioned above can be data from the central control data whose rendering complexity is less than or equal to a preset threshold, that is, data from the central control data with low rendering capabilities corresponding to the required rendering service. The second part of the rendering data can be obtained after rendering processing the second part of the data, and can correspond to the visualization results displayed on the screen.

[0139] It should be noted that the value of the preset threshold can be set according to the actual application situation, as long as it meets the processing capability of the hardware synthesizer in the Android system. This disclosed embodiment does not impose any restrictions.

[0140] Understandably, the vehicle can use a first rendering service, such as the GPU's OpenGL or Vulkan rendering pipeline, to render the first part of the data and obtain the first part of the rendered data; and use a second rendering service, such as the SurfaceFlinger service, to render the second part of the data and obtain the second part of the rendered data; then, a hardware compositor is used to composite the first part of the rendered data and the second part of the rendered data. The compositing process can include operations such as color mixing, transparency processing, image scaling, and rotation; after the compositing process, the hardware compositor outputs the second rendered data, which is the display data corresponding to the central control data, and can be used to display data on the screen.

[0141] For example, the SurfaceFlinger service can store the first portion of rendered data, processed using the OpenGL or Vulkan rendering pipeline, in a graphics buffer, and also store the second portion of rendered data, processed using its own rendering pipeline, in the graphics buffer. HWC receives the processed data from the SurfaceFlinger service and performs composite processing according to the hierarchical order of the first and second portions of rendered data. The resulting second portion of rendered data is output to a final output buffer for display on the screen.

[0142] In this embodiment of the disclosure, a first part of the data with high rendering complexity can be processed by a first rendering service to obtain a first part of the rendering data, and a second part of the data with lower rendering complexity than the first part of the data can be processed by a second rendering service to obtain a second part of the rendering data. Then, a hardware compositor is used to combine the first part of the rendering data and the second part of the rendering data to obtain the second part of the rendering data. This can effectively handle graphics rendering tasks with high rendering complexity, while improving the rendering efficiency and rendering effect for central control data.

[0143] Figure 3 This is a system architecture diagram illustrating a display method according to an exemplary embodiment. Figure 4 This is a flowchart illustrating a display method according to an exemplary embodiment, as shown in Figure 2. Figure 3 and Figure 4 As shown, the display methods provided in this disclosure are merely examples and not limitations, intended to help those skilled in the art better understand the technical solutions of this disclosure. See also Figure 4 The display method provided in this disclosure can be applied to vehicles, and may specifically include the following steps:

[0144] Step 401: Obtain the instrument data and central control data to be displayed.

[0145] Here, the instrument data to be displayed can be the instrument data that the vehicle needs to display in the instrument area of ​​the display screen; the central control data to be displayed can be the central control data that the vehicle needs to display in the central control area of ​​the display screen.

[0146] Step 402: Render the instrument data using the first rendering service supported by the graphics processor in the native system to obtain the first rendered data.

[0147] Here, the process executing the first rendering service is the native process of the native system.

[0148] For example, such as Figure 3As shown, the native processes 303 of the vehicle's native system 301, such as Wayland, Weston, or Flutter, can call the rendering interface 304 of the graphics processor 305, i.e., APIs such as OpenGL or Vulkan, and use the rendering interface 304 to transmit rendering instructions carrying instrument data to the graphics processor 305. After receiving the rendering instructions, the graphics processor 305 can perform rendering processing on the instrument data to obtain the first rendering data.

[0149] like Figure 3 As shown, the vehicle may also include a graphics software library 306, which can provide encapsulation or extension of APIs such as OpenGL or Vulkan, making it easier to use the APIs for rendering on different operating systems. The vehicle may also include a kernel graphics system layer 307, which can provide low-level support for the graphics processor 305 hardware driver; for example, the kernel graphics system layer 307 can be responsible for the initialization, configuration, and interaction with other system components of the graphics processor 305 driver.

[0150] Step 403: Determine whether the processing capability of the hardware synthesizer in the non-native system meets the preset capability conditions; if yes, proceed to step 404; if no, proceed to step 406.

[0151] Step 404: The second rendering service based on the non-native system converts the central control data into multiple layer data, and renders each layer data separately to obtain each rendered layer.

[0152] Here, the process executing the second rendering service can be a non-native process of a non-native system, and the non-native system can be the Android system.

[0153] Step 405: Perform composite processing on each rendered layer based on the hardware compositor to obtain the second rendering data.

[0154] For example, such as Figure 3 As shown, the SurfaceFlinger service 308 of the Android system 302 can receive central control data from multiple applications or services, and convert the received central control data into layer data that the hardware compositor 309 can understand. Each layer data corresponds to a graphics buffer, and each graphics buffer stores the data content corresponding to each rendered layer. The hardware compositor 309 receives the list of each rendered layer sent by the SurfaceFlinger service 308, and performs composite processing according to the hierarchical order of each rendered layer. The resulting second rendered data is output to a final output buffer so that it can be displayed on the display screen 318.

[0155] Step 406: Render the first part of the data in the central control data based on the first rendering service to obtain the first part of the rendered data.

[0156] Step 407: Render the second part of the data in the central control data based on the second rendering service to obtain the second part of the rendered data.

[0157] Here, the rendering complexity of the first part of the data is greater than that of the second part of the data.

[0158] Step 408: Combine the first part of the rendering data and the second part of the rendering data using a hardware compositor to obtain the second rendering data.

[0159] For example, such as Figure 3 As shown, the SurfaceFlinger service 308 is responsible for storing the first portion of rendered data, processed using the OpenGL or Vulkan rendering pipeline 304, in a graphics buffer, and also storing the second portion of rendered data, processed using its own rendering capabilities, in the graphics buffer. The hardware compositor 309 receives the rendered data from the SurfaceFlinger service 308 and performs composite processing according to the hierarchical order of the first and second portions of rendered data. The resulting second portion of rendered data is output to a final output buffer for display on the display screen 318.

[0160] Step 409: Combine the first rendering data and the second rendering data to obtain the target rendering data.

[0161] Step 410: Display the target rendering data on the same display screen.

[0162] Here, as Figure 3 As shown, after the vehicle uses the drive to synthesize the first rendering data and the second rendering data into target rendering data, the data is displayed on the same display screen 318 through the clock and data recovery circuit 317 shared by the operating systems of the first system and the second system.

[0163] For example, such as Figure 3 As shown, L4 identifies the User Interface (UI) functional module, L5 identifies the core layer functional module, L6 identifies the system-on-a-chip (SoC) functional module, and L7 identifies the device-level functional module. Among these, Figure 3Connectors 1 and 2 can connect to other displays in the vehicle that are different from those displaying instrument cluster data and central control data; connectors 313 and 316 can connect to the same display showing both instrument cluster data and central control data. The Hardware User Interface (HWUI) is a component in the Android system used to handle UI rendering operations for applications. libdrm 311 and 314 can be used to access and manage the Direct Rendering Manager (DRM) subsystem. The first graphics display framework 312 and the second graphics display framework 315 can respectively correspond to the collections of display hardware and software resources for processing central control data and instrument cluster data, and can each independently support an operating system.

[0164] The display method provided in this embodiment can render instrument data using a first rendering service supported by the graphics processor in the native system to obtain first rendered data, and render central control data using a second rendering service in a non-native system to obtain second rendered data. Since the non-native process executing the second rendering service is different from the native process executing the first rendering service, a failure in the non-native system affecting the display of central control data on the screen will not affect the rendering of instrument data by the native process in the native system. Similarly, a failure in the native system will not affect the rendering of non-native system data, thereby improving the stability of the subsequent display of corresponding instrument and central control data. Furthermore, due to the stable display of instrument data on the screen, users can observe changes in instrument data in real time, enabling them to take timely countermeasures in emergencies, thus improving the safety of the vehicle where the display is located.

[0165] At the same time, by taking advantage of the different processing capabilities of the hardware compositors in non-native systems, consistent or acceptable rendering effects for central control data can be achieved on non-native systems with different performance levels. In other words, the rendering method for central control data can be dynamically adjusted by the processing capabilities of the hardware compositors. Non-native systems can ensure better rendering effects for central control data on high-performance hardware devices, while maintaining acceptable rendering effects on low-performance hardware devices, thereby improving the user experience.

[0166] Figure 5 This is a structural block diagram of an intelligent cockpit according to an exemplary embodiment. See also... Figure 5 The intelligent cockpit 500 provided in this embodiment of the present disclosure is applied to a vehicle and may include: an acquisition module 510, a first processing module 520, a second processing module 530, and a display module 540.

[0167] The acquisition module 510 is configured to acquire instrument data and central control data to be displayed.

[0168] The first processing module 520 is configured to render instrument data based on the first system service to obtain first rendered data.

[0169] The second processing module 530 is configured to perform rendering processing on the central control data based on the second system service to obtain the second rendering data.

[0170] Display module 540 is configured to display data on the same display screen based on first rendering data and second rendering data.

[0171] The intelligent cockpit provided in this embodiment can render the instrument data to be displayed through a first system service to obtain first rendered data, and render the central control data to be displayed through a second system service to obtain second rendered data. The first and second rendered data are then displayed on the same screen, thereby ensuring that the processing of instrument data by the first system service and the processing of central control data by the second system service do not interfere with each other, thus improving the stability of the display screen displaying the corresponding instrument data and central control data and enhancing the user experience. Furthermore, due to the stable display of the instrument data on the screen, users can observe the changes in the instrument data in real time, enabling them to take timely measures in case of emergencies, thereby improving the safety of the vehicle where the display screen is located.

[0172] for Figure 5 In one possible implementation of the technical solution shown, the display module 540 is specifically configured to: perform composite processing on the first rendering data and the second rendering data to obtain target rendering data; and display the target rendering data on the same display screen.

[0173] for Figure 5 In one possible implementation of the technical solution shown, the operating system of the first system service is the native system, and the first processing module 520 is specifically configured to: render the instrument data based on the first rendering service of the native system to obtain the first rendering data; wherein, the process executing the first rendering service is the native process.

[0174] for Figure 5 In one possible implementation of the technical solution shown, the first processing module 520 is further configured to: render the instrument data based on the first rendering service supported by the graphics processor in the native system to obtain the first rendered data.

[0175] for Figure 5In one possible implementation of the technical solution shown, the operating system of the second system service is a non-native system, and the second processing module 530 is specifically configured as follows: the second rendering service based on the non-native system performs rendering processing on the central control data to obtain the second rendering data; wherein, the process executing the second rendering service is a non-native process.

[0176] for Figure 5 In one possible implementation of the technical solution shown, the non-native system is the Android system, and the second processing module 530 is further configured to: in response to the processing capability of the hardware compositor in the Android system meeting the preset capability conditions, perform rendering processing on the central control data based on the second rendering service, and obtain the second rendering data based on the hardware compositor; in response to the processing capability of the hardware compositor in the Android system not meeting the preset capability conditions, perform rendering processing on the central control data based on the second rendering service of the non-native process and the first rendering service of the native process, and obtain the second rendering data based on the hardware compositor.

[0177] for Figure 5 In one possible implementation of the technical solution shown, the second processing module 530 is further configured to: convert the central control data into multiple layer data based on the second rendering service, and render each layer data separately to obtain each rendered layer; wherein, the data content corresponding to different layer data is different; and perform compositing processing on each rendered layer based on the hardware compositor to obtain the second rendering data.

[0178] for Figure 5 In one possible implementation of the technical solution shown, the central control data includes a first part of data and a second part of data. The second processing module 530 is further configured to: perform rendering processing on the first part of data based on a first rendering service to obtain first part of rendered data; perform rendering processing on the second part of data based on a second rendering service to obtain second part of rendered data; wherein the rendering complexity of the first part of data is greater than the rendering complexity of the second part of data; and perform compositing processing on the first part of rendered data and the second part of rendered data based on a hardware compositor to obtain second rendered data.

[0179] It should be noted that the smart cockpit provided in this embodiment corresponds to the display method mentioned above. Related details can be found in the description of the display method above, and will not be repeated here.

[0180] Figure 6 This is a schematic diagram illustrating the structure of a vehicle according to an exemplary embodiment. (Refer to...) Figure 6The vehicle 600 may include one or more of the following components: processing component 602, memory 604, power supply component 606, multimedia component 608, audio component 610, input / output (I / O) interface 612, sensor component 614, and communication component 616.

[0181] Processing component 602 typically controls the overall operation of vehicle 600, such as operations associated with at least one of display, telephone call, data communication, camera operation, and recording. Processing component 602 may include one or more processors 620 to execute instructions to perform all or part of the steps of the methods described above. Furthermore, processing component 602 may include one or more modules to facilitate interaction between processing component 602 and other components. For example, processing component 602 may include a multimedia module to facilitate interaction between multimedia component 608 and processing component 602.

[0182] Memory 604 is configured to store various types of data to support operation of vehicle 600. Examples of such data include at least one of the following: instructions for any application or method operating on vehicle 600, contact data, phonebook data, messages, pictures, and videos. Memory 604 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as Static Random Access Memory (SRAM), Electrically Erasable Programmable Read Only Memory (EEPROM), Erasable Programmable Read-Only Memory (EPROM), Programmable Read Only Memory (PROM), Read-Only Memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0183] The power supply assembly 606 provides power to various components of the vehicle 600. The power supply assembly 606 may include at least one of the following: a power management system, one or more power sources, and other components associated with generating, managing, and distributing power to the vehicle 600.

[0184] The multimedia component 608 includes a screen that provides an output interface between the vehicle 600 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of touch or swipe actions but also the duration and pressure associated with the touch or swipe operation. In some embodiments, the multimedia component 608 includes a front-facing camera and / or a rear-facing camera. When the vehicle 600 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or the rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0185] Audio component 610 is configured to output and / or input audio signals. For example, audio component 610 includes a microphone (MIC) configured to receive external audio signals when vehicle 600 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 604 or transmitted via communication component 616. In some embodiments, audio component 610 also includes a speaker for outputting audio signals.

[0186] I / O interface 612 provides an interface between processing component 602 and peripheral interface modules, such as keyboards, click wheels, and buttons. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

[0187] Sensor assembly 614 includes one or more sensors for providing state assessments of various aspects of vehicle 600. For example, sensor assembly 614 may detect the on / off state of vehicle 600, the relative positioning of components such as the display and keypad of vehicle 600, changes in the position of vehicle 600 or one of its components, the presence or absence of user contact with vehicle 600, the orientation or acceleration / deceleration of vehicle 600, and temperature changes of vehicle 600. Sensor assembly 614 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 614 may also include an optical sensor, such as a complementary metal-oxide-semiconductor (CMOS) or charge-coupled device (CCD) image sensor, for use in imaging applications. In some embodiments, sensor assembly 614 may also include, but is not limited to, at least one of the following: an accelerometer, a gyroscope, a magnetometer, a pressure sensor, and a temperature sensor.

[0188] Communication component 616 is configured to facilitate wired or wireless communication between vehicle 600 and other devices. Vehicle 600 can access wireless networks based on communication standards, such as Wi-Fi, 4G, 5G, or combinations thereof. In one exemplary embodiment, communication component 616 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 616 also includes a Near Field Communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID), Infrared Data Association (IrDA), Ultra Wide Band (UWB), Bluetooth (BT), and other technologies.

[0189] In an exemplary embodiment, the vehicle 600 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components.

[0190] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory including executable instructions or a computer program that can be executed by a vehicle's processor to perform the display method. For example, the non-transitory computer-readable storage medium may be a ROM, random access memory (RAM), a compact disc read-only memory (CD-ROM), magnetic tape, floppy disk, and optical data storage device, etc.

[0191] A non-transitory computer-readable storage medium, when the instructions in the storage medium are executed by the vehicle's processor, enables the vehicle to perform any of the display methods described above. For example, the display method includes: acquiring instrument data and central control data to be displayed; rendering the instrument data based on a first system service to obtain first rendered data; rendering the central control data based on a second system service to obtain second rendered data; and displaying the data on the same display screen based on the first rendered data and the second rendered data.

[0192] This disclosure provides a computer program product comprising a computer program or executable instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer program or executable instructions from the computer-readable storage medium and executes the computer program or executable instructions, causing the computer device to perform any of the display methods described above.

[0193] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the claims.

[0194] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

Claims

1. A display method characterized by comprising: The method comprises: acquiring instrument data and central control data to be displayed; performing rendering processing on the instrument data based on a first system service to obtain first rendering data; performing rendering processing on the central control data based on a second system service to obtain second rendering data; performing data display on the same display screen based on the first rendering data and the second rendering data.

2. The method of claim 1, wherein, The data display on the same display screen based on the first rendering data and the second rendering data comprises: performing synthesis processing on the first rendering data and the second rendering data to obtain target rendering data; and displaying the target rendering data on the same display screen.

3. The method according to claim 1 or 2, characterized in that, The operating system of the first system service is a native system, and the rendering processing on the instrument data based on the first system service to obtain first rendering data comprises: performing rendering processing on the instrument data based on a first rendering service of the native system to obtain the first rendering data, wherein a process executing the first rendering service is a native process.

4. The method of claim 3, wherein, The rendering processing on the instrument data based on the first rendering service of the native system to obtain the first rendering data comprises: performing rendering processing on the instrument data based on the first rendering service supported by a graphic processing unit in the native system to obtain the first rendering data.

5. The method according to claim 1 or 2, characterized in that, The operating system of the second system service is a non-native system, and the rendering processing on the central control data based on the second system service to obtain second rendering data comprises: performing rendering processing on the central control data based on a second rendering service of the non-native system to obtain the second rendering data, wherein a process executing the second rendering service is a non-native process.

6. The method of claim 5, wherein, The non-native system is an Android system, and the rendering processing on the central control data based on the second rendering service of the non-native system to obtain the second rendering data comprises: in response to the processing capability of a hardware compositor in the Android system satisfying a preset capability condition, performing rendering processing on the central control data based on the second rendering service and obtaining the second rendering data based on the hardware compositor; in response to the processing capability of the hardware compositor in the Android system not satisfying the preset capability condition, performing rendering processing on the central control data based on the second rendering service of the non-native process and the first rendering service of a native process, and obtaining the second rendering data based on the hardware compositor.

7. The method of claim 6, wherein, The rendering processing on the central control data based on the second rendering service and obtaining the second rendering data based on the hardware compositor comprise: converting the central control data into a plurality of layer data based on the second rendering service, and performing rendering processing on each of the layer data to obtain each rendered layer, wherein different layer data correspond to different data contents; and performing synthesis processing on the each rendered layer based on the hardware compositor to obtain the second rendering data.

8. The method of claim 6, wherein, The middle control data includes first part data and second part data, the second rendering service based on the non-native process and the first rendering service of the native process are used for rendering processing of the middle control data, and the second rendering data is obtained based on the hardware synthesizer, including: The first part data is rendered based on the first rendering service to obtain first part rendering data; The second part data is rendered based on the second rendering service to obtain second part rendering data; wherein the rendering complexity of the first part data is greater than the rendering complexity of the second part data; The first part rendering data and the second part rendering data are synthesized based on the hardware synthesizer to obtain the second rendering data.

9. An intelligent cabin, characterized in that, Including: An acquisition module configured to acquire instrument data to be displayed and middle control data; A first processing module configured to render the instrument data based on a first system service to obtain first rendering data; A second processing module configured to render the middle control data based on a second system service to obtain second rendering data; A display module configured to display data on the same display screen based on the first rendering data and the second rendering data.

10. A vehicle characterized by comprising: Including: A processor; A memory for storing computer programs or instructions; Wherein the processor executes the computer programs or instructions to realize the steps of the display method in any one of claims 1 to 8.

11. A non-transitory computer-readable storage medium storing a computer program or instructions, wherein, When the computer programs or instructions in the storage medium are executed by the processor, the steps of the display method in any one of claims 1 to 8 are realized.

12. A computer program product comprising computer programs or instructions, characterized in that, The computer programs or instructions are executed by the processor to realize the steps of the display method in any one of claims 1 to 8.

Images