Display control method of cockpit display frame, computer equipment and storage medium

Abstract

The embodiment of the invention discloses a display control method of a cabin display frame. The method comprises the steps that a cache management assembly is controlled to distribute a plurality of cache regions for an application program, and the application program draws target image data into the occupied cache regions; and controlling the cache management component to transmit the display control information and the target image data of the to-be-sent-to-display cache region to a display device for display processing through the DRM driving component. According to the display control method provided by the embodiment of the invention, the display event can be processed by occupying less system resources on the basis of the concise and lightweight cabin display frame, and the picture can be displayed efficiently and quickly. Meanwhile, the cockpit display frame provided by the embodiment of the invention does not depend on or is attached to any open source display frame to process the display event, and the display event can be normally brushed and displayed only after the DRM driving component runs, so that the display efficiency is improved.

Description

Technical Field

[0001] The embodiments of the present application relate to the technical field of cockpit display, and in particular, to a display control method, a computer device, and a storage medium for a cockpit display framework. Background Art

[0002] The in-vehicle cockpit provided by the related art adopts an open-source display architecture, and the open-source display architecture can transmit image data to a display device for display. Such an open-source display architecture requires a relatively large amount of system resources to process image data, and requires a relatively long time to respond to and process image data, resulting in a relatively long image display time. Summary of the Invention

[0003] An object of the embodiments of the present application is to provide a display control method, a computer device, and a storage medium for a cockpit display framework, so as to solve the technical problem of relatively low display efficiency of the cockpit display architecture provided by the related art.

[0004] In a first aspect, the embodiments of the present application provide a display control method for a cockpit display framework. The cockpit display framework includes a display management component, a refresh rate component, and a cache management component. The display control method includes: responding to a cache allocation request sent by an application program to the cache management component, and controlling the cache management component to allocate a plurality of cache areas for the application program. The plurality of cache areas form a cache queue. Responding to an image drawing request sent by the application program to the cache management component, and controlling the cache management component to update an available cache area to an occupied cache area, so that the application program draws target image data into the occupied cache area. The available cache area is a cache area in the cache queue that can be used to draw image data. Responding to a drawing completion request sent by the application program to the cache management component, and controlling the cache management component to update the occupied cache area to a cache area to be sent for display. The drawing completion request is used to indicate that the application program has drawn all the target image data into the occupied cache area. Responding to a display control request sent by the application program to the display management component, and controlling the display management component to generate display control information. Responding to a cache sending request sent by the refresh rate component to the cache management component, and controlling the cache management component to transmit the display control information and the target image data of the cache area to be sent for display to a display device through a DRM driver component for display processing. The cache sending request is used to indicate that the refresh rate component has received an image sending signal sent by the DRM driver component.

[0005] The display control method provided by the embodiments of the present application is based on a simple and lightweight cockpit display framework, which can occupy less system resources to process display events and display the screen more efficiently and quickly. At the same time, the cockpit display framework provided by the embodiments of the present application does not depend on or attach to any open-source display framework to process display events. It only needs to be able to normally draw and display the screen after the DRM driver component runs. Therefore, the embodiments of the present application avoid the problem of low efficiency caused by running an open-source display architecture, and can normally draw and display the screen only through a simple and lightweight cockpit display framework, thereby improving the display efficiency.

[0006] Optionally, the cache management component is configured with a quantity setting interface and a cache application interface. The cache allocation request includes a quantity setting request and a cache application request. The cache management component includes a cache production component. In response to the cache allocation request sent by the application to the cache management component, it controls the cache management component to allocate multiple cache areas for the application, including: in response to the quantity setting request sent by the application calling the quantity setting interface to the cache production component, determining the cache quantity; in response to the cache application request sent by the application calling the cache application interface to the cache production component, controlling the cache production component to allocate multiple cache areas for the application according to the cache quantity.

[0007] The embodiments of the present application control the cache production component to allocate a cache queue for the application by sequentially calling the quantity setting interface and the cache application interface. Such a working mechanism is particularly important in a complex cache application environment and can ensure that the corresponding number of cache areas is reliably allocated to each application that needs to apply for a cache area.

[0008] Optionally, the cache management component is configured with an image drawing interface. The cache management component includes a cache production component. In response to the image drawing request sent by the application to the cache management component, it controls the cache management component to update the available cache area to an occupied cache area, so that the application can draw target image data to the occupied cache area, including: in response to the image drawing request sent by the application calling the image drawing interface to the cache production component, controlling the cache production component to select an available cache area that meets the preset drawing conditions in the cache queue as the occupied cache area, and controlling the cache production component to return the cache address of the occupied cache area to the application, so that the application can draw target image data to the occupied cache area based on the cache address.

[0009] The embodiments of the present application update the available cache area to an occupied cache area, so that the application exclusively occupies the occupied cache area, avoiding other applications from writing other image data to the occupied cache area where the target image data has been drawn and erasing the existing target image data in the occupied cache area, thereby avoiding the loss of target image data. At the same time, it avoids the problem of image data loss caused by the application competing with other applications for the same occupied cache area at the same time.

[0010] Optionally, each buffer is configured with a status flag. The constituent elements of the preset drawing condition include an available buffer with a status flag being an idle flag. In response to an image drawing request sent by an application to the buffer production component by calling an image drawing interface, controlling the buffer production component to select an available buffer that meets the preset drawing condition in the buffer queue as an occupied buffer, including: In response to an image drawing request sent by an application to the buffer production component by calling an image drawing interface, controlling the buffer production component to check whether there is an available buffer with a status flag being an idle flag in the buffer queue. If there is an available buffer with a status flag being an idle flag in the buffer queue, then controlling the buffer production component to update the available buffer to an occupied buffer.

[0011] Optionally, the buffer management component is configured with a to-be-displayed interface. The buffer management component includes a buffer production component. Each buffer is configured with a status flag. In response to a drawing completion request sent by an application to the buffer management component, controlling the buffer management component to update the occupied buffer to a to-be-displayed buffer, including: In response to a drawing completion request sent by an application to the buffer production component by calling the to-be-displayed interface, controlling the buffer production component to update the status flag of the occupied buffer to a to-be-displayed flag, and determining a buffer that meets the preset display condition among all the buffers with the to-be-displayed flag as the to-be-displayed buffer.

[0012] After the application in the embodiment of the present application has drawn all the target image data into the occupied buffer, it can automatically update the occupied buffer to a to-be-displayed buffer, so that the buffer management component can transmit the target image data to the display device through the DRM driver component for display processing.

[0013] Optionally, the constituent elements of the preset display condition include that the timestamp of the buffer with the to-be-displayed flag is the earliest timestamp in the buffer queue. Determining a buffer that meets the preset display condition among all the buffers with the to-be-displayed flag as the to-be-displayed buffer, including: determining the timestamp of each buffer with the to-be-displayed flag, finding out the earliest timestamp among all the timestamps, and determining the buffer corresponding to the earliest timestamp as the to-be-displayed buffer.

[0014] The embodiment of the present application can control each display screen to be displayed in sequence according to the time sequence, so as to ensure the continuity of the screen display and improve the user experience.

[0015] Optionally, the cache management component includes a cache consumption component. In response to the cache display request sent by the refresh rate component to the cache management component, it controls the cache management component to transmit the display control information and the target image data in the buffer area to be displayed to the display device through the DRM driver component for display processing, including: obtaining the cache display request sent by the refresh rate component to the cache consumption component, responding to the cache display request, controlling the cache consumption component to read the target image data in the buffer area to be displayed, and reading the display control information of the display management component, and controlling the cache consumption component to transmit the target image data and the display control information to the display device through the DRM driver component for display processing.

[0016] Optionally, the display management component is configured with an image display interface, and the display control information includes an image display identifier, and the image display identifier is used to instruct the display device to display a display screen corresponding to the target image data; and / or, the display management component is configured with an image hiding interface, and the display control information includes an image hiding identifier, and the image hiding identifier is used to instruct the display device to hide a display screen corresponding to the target image data; and / or, the display management component is configured with a transparency interface, and the display control information includes a transparency parameter, and the transparency parameter is used to instruct the display device to adjust the transparency of a display screen corresponding to the target image data; and / or, the display management component is configured with a window setting interface, and the display control information includes window setting parameters, and the window setting parameters are used to instruct the display device to control the window attributes of the target window, and the target window is the window for displaying a display screen corresponding to the target image data; and / or, the display management component is configured with an image cropping interface, and the display control information includes image cropping parameters, and the image cropping parameters are used to instruct the display device to crop a display screen corresponding to the target image data; and / or, the display management component is configured with a layer priority interface, and the display control information includes layer priority parameters, and the layer priority parameters are used to instruct the display management component to adjust the hierarchical relationship between each application layer.

[0017] The embodiments of the present application provide rich display APIs, and the application program can meet various image display requirements by calling various display APIs.

[0018] In a second aspect, the embodiments of the present application provide a computer device, including a memory and a processor, the memory is connected to the processor, and the processor is used to execute one or more computer programs stored in the memory. When the processor executes the one or more computer programs, the computer device implements the display control method of the cockpit display framework described above.

[0019] In a third aspect, the embodiments of the present application provide a computer-readable storage medium, and the computer-readable storage medium stores a computer program, and the computer program includes program instructions. When the program instructions are executed by the processor, the processor executes the display control method of the cockpit display framework described above. Brief Description of the Drawings

[0020] To more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for the description of the embodiments of the present application will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0021] Figure 1 Schematic diagram of a display architecture provided by the related art;

[0022] Figure 2 Schematic diagram of a cockpit display framework provided by the embodiments of the present application;

[0023] Figure 3 Schematic diagram of the interaction between the refresh rate component and the DRM driver component provided by the embodiments of the present application;

[0024] Figure 4 Schematic diagram of the architecture of a cache management component provided by the embodiments of the present application;

[0025] Figure 5 Schematic diagram of the flow of a display control method for a cockpit display framework provided by the embodiments of the present application;

[0026] Figure 6 Schematic diagram of the structure of a display control device for a cockpit display framework provided by the embodiments of the present application;

[0027] Figure 7 Schematic diagram of the structure of a computer device provided by the embodiments of the present application. Detailed Description of the Embodiments

[0028] In order to make the objectives, technical solutions and advantages of the present application clearer, the present application will be further described in detail below with reference to the drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present application without creative efforts belong to the scope of protection of the present application.

[0029] It should be noted that if there is no conflict, the various features in the embodiments of the present application can be combined with each other, and all are within the protection scope of the present application. In addition, although functional module division is carried out in the device schematic diagram and the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in a different order from the module division in the device or the flowchart. Furthermore, the terms "first", "second", "third", etc. adopted in the present application do not limit the data and execution order, but only distinguish the same items or similar items with basically the same functions and effects.

[0030] The working environments of the display architectures of in-vehicle cockpits and Windows systems are different, and the user requirements are different, which result in the following obvious differences between the two display architectures:

[0031] 1) Characteristics of the display architecture of in-vehicle cockpits:

[0032] 1.1 Safety first. The in-vehicle environment has extremely high requirements for safety. The display architecture needs to ensure stable and reliable operation in various complex driving scenarios, avoiding distractions or incorrect operations by the driver caused by display failures and leading to safety accidents. For example, in harsh conditions such as high temperature, low temperature, and vibration, the display system still needs to normally display key driving information, such as vehicle speed, fuel level, warning information, etc.

[0033] 1.2 Multi-screen interaction and collaboration. In-vehicle cockpits usually have multiple display screens, such as instrument panels, center control screens, and co-pilot entertainment screens. The display architecture needs to support information sharing and interaction between the above screens, providing a unified and smooth experience for drivers or passengers.

[0034] 1.3 High real-time requirements. For some key driving information, such as vehicle speed and braking status, it needs to be displayed in real time to ensure that the driver can obtain accurate information in a timely manner. The display architecture needs to have the characteristic of low latency to ensure real-time update of information.

[0035] 2) Characteristics of the display architecture of Windows systems:

[0036] 2.1 Generalization and compatibility. The display architecture of the Windows system aims to provide general display support for various types of application programs and is compatible with different hardware devices and software platforms.

[0037] 2.2 Multitasking. The display architecture of the Windows system supports running multiple application programs simultaneously and displaying content in different windows. The display architecture needs to have efficient window management and graphics composition capabilities to ensure that the interfaces of multiple application programs can be displayed simultaneously without interference.

[0038] The display architecture of the Windows system requires a lot of system resources and the processing process is quite cumbersome, leading industry insiders to choose relatively secure open-source display architectures. For example, such open-source display architectures include the Yocto Weston display architecture and the Android Surface Flinger architecture.

[0039] The Yocto Weston display architecture is built on the Yocto project and is a display system with Weston as the Wayland compositor. The Yocto Weston display architecture uses the Wayland protocol, which defines the communication mechanism between applications and the compositor (Weston). Applications establish connections with the Weston compositor through Wayland sockets and send drawing requests, window management requests, etc. to it.

[0040] The Weston compositor is responsible for receiving events from input devices (such as keyboards, mice, touchscreens) and passing the events to the corresponding applications. At the same time, the Weston compositor composes the graphics buffers of each application and then sends the composed image data to the display device for display through the DRM (Direct Rendering Manager) driver component of the Linux kernel.

[0041] When starting up, the Weston compositor needs to perform a series of initialization operations, such as creating windows, allocating resources, establishing connections with clients and hardware, etc., which is likely to increase the initialization time and reduce the display efficiency.

[0042] The Android SurfaceFlinger display framework is the core component in the Android system responsible for graphics display and composition, and plays a crucial role in achieving smooth and efficient graphics interface display.

[0043] As the compositor of the Android graphics display system, the main task of SurfaceFlinger is to integrate and process the graphics data generated by various applications in the system and finally display the composed image on the screen. In the Android system, each application window corresponds to one or more Surfaces, and a Surface can be regarded as an abstract graphics buffer management object. Applications write the drawn graphics data into the corresponding buffer through the Surface, and SurfaceFlinger is responsible for managing the buffer, including buffer allocation, recycling, and synchronization operations. SurfaceFlinger will regularly collect the graphics data in the Surfaces of each application for composition, and the composed graphics data is sent to the display device for display.

[0044] The Android SurfaceFlinger display framework has a high level of complexity and requires a relatively large amount of system resources to handle complex window management, buffer synchronization, hardware acceleration, and other issues.

[0045] Generally speaking, both the Yocto Weston display architecture and the Android Surface Flinger architecture require a relatively large amount of system resources for image processing, resulting in low image processing efficiency.

[0046] The inventors also found a display architecture provided by another related technology. Please refer to Figure 1 , where the display architecture 100 includes a display management unit 11 and a cache management unit 12.

[0047] The display management unit 11 only provides a simple image display interface (show interface) and an image hiding interface (hide interface), and does not support the setting of other display parameters. All other display parameters use default values.

[0048] The cache management unit 12 only supports rotation in a single buffer. For example, when drawing image data in a single buffer, when it needs to be displayed, the image data of this buffer is sent out, and then image data is drawn in this buffer again, resulting in low display efficiency.

[0049] When image display is required, the application layer 13 applies for a buffer from the cache management unit 12 and draws image data into this buffer. At the same time, the application layer 13 calls the image display interface or the image hiding interface of the display management unit 11 to obtain an image display identifier or an image hiding identifier. The cache management unit 12 packs the image data, the image display identifier, or the image hiding identifier, and transmits it to the DRM driver component 15 through the driver interface library 14 (libdrm.so). The DRM driver component 15 transmits the image data, the image display identifier, or the image hiding identifier to the display device for display processing.

[0050] From the above description, it can be seen that in the display architecture provided by the related technology, the display management unit 11 supports fewer API interfaces and cannot meet the diverse display needs of users. The cache management unit 12 only supports rotation in a single buffer, resulting in low display efficiency. In addition, such a display architecture does not support the processing of VSYNC signals (Vertical Synchronization Signals) and PageFlip events, and the refresh rate depends on the output of the application program, which is prone to tearing and abnormal phenomena.

[0051] The cockpit display framework provided in the embodiment of the present application includes a display management component, a refresh rate component and a cache management component. The architecture is relatively simple and lightweight, takes up less system resources to process display events, and displays the screen more efficiently and quickly. At the same time, the cockpit display framework provided in the embodiment of the present application does not rely on or attach to any open source display framework to process display events. It only needs to run the DRM driver component to refresh the image and display it normally. Therefore, the embodiment of the present application avoids the problem of inefficiency caused by the need to run the open source display architecture. It can refresh the image and display it normally only through the simple and lightweight cockpit display framework, thereby improving the display efficiency.

[0052] Hereinafter, the present application embodiment provides a cockpit display framework. Figure 2 The cockpit display framework 200 includes a display management component 21 , a refresh rate component 22 and a cache management component 23 .

[0053] The display management component 21 can provide a rich display application interface (display API). The display application interface may include: image display interface (show API), image hiding interface (hide API), transparency interface (Alpha API), window setting interface (Position API), image cropping interface (Crop API) and layer priority interface (Z-order API), etc.

[0054] When the application 24 calls the image display interface of the display management component 21, the display management component 21 generates an image display identifier, which is used to instruct the display device to display the display screen corresponding to the target image data. When the application 24 calls the image hiding interface of the display management component 21, the display management component 21 generates an image hiding identifier, which is used to instruct the display device to hide the display screen corresponding to the target image data.

[0055] The application 24 calls the transparency interface of the display management component 21, and the display management component 21 generates a transparency parameter, which is used to instruct the display device to adjust the transparency of the display screen corresponding to the target image data. The application 24 calls the window setting interface of the display management component 21, and the display management component 21 generates a window setting parameter, which is used to instruct the display device to control the window properties of the target window, the target window is a window that displays the display screen corresponding to the target image data, and the window properties include the position and size of the target window.

[0056] The application 24 calls the image cropping interface of the display management component 21, and the display management component 21 generates image cropping parameters, which are used to instruct the display device to crop the display screen corresponding to the target image data. The application 24 calls the layer priority interface of the display management component 21, and the display management component 21 generates layer priority parameters, which are used to instruct the display management component 21 to adjust the hierarchical relationship between each application layer.

[0057] Please refer to Figure 3 , the refresh rate component 22 supports the processing of VSYNC signals and PageFlip events, and improves the frame rate while ensuring that the output screen is tear-free.

[0058] The VSYNC signal is a periodic signal actively output by the display device, which is used to indicate that the display device has completed the refresh of one frame of the screen. When the display device displays an image, it scans the screen line by line from left to right and from top to bottom. Completing a full screen scan is called a frame of screen scan. After a frame of screen scan is completed, the display device outputs a VSYNC signal to notify other devices (such as the graphics card, graphics compositor, etc.) that they can start preparing to display the next frame of the screen.

[0059] The PageFlip event (page flip event) is a mechanism for managing and updating the display content. In the embodiments of the present application, multiple buffers are used to store image data. When the application finishes drawing the image data in the buffer, the DRM driver component 25 outputs a PageFlip event. When the PageFlip event occurs, the display framework switches from the currently displayed buffer (front buffer) to another buffer that has been prepared with new image data (back buffer), and displays the new screen to the user, thereby realizing the update of the screen.

[0060] Screen tearing refers to the phenomenon that the image seen on the display device appears misaligned, overlapped, or discontinuous. This phenomenon is mainly caused by the asynchronous refresh process of the display device and the rendering process of the GPU. The refresh rate of the display device refers to the number of times the display device refreshes the screen per second to display an image. For example, if the refresh rate is 60Hz, the display device refreshes the screen 60 times per second. The frame rate refers to the number of image frames rendered by the GPU per second. When the frame rate is higher than the refresh rate, for example, the refresh rate of the display device is 60Hz, and the frame rate of the GPU is 120fps, the GPU renders images faster than the display device refreshes the screen. Before the display device has completed the refresh of one frame, the GPU has already rendered a new image and started to overwrite the original buffer. In this way, the display device will display partial contents of the new and old frames simultaneously during the refresh process, resulting in screen tearing.

[0061] The embodiments of this application require the VSYNC signal and PageFlip event transmitted by the DRM driver component 25 to display the screen. In this way, not only can the phenomenon of screen tearing be avoided, but when the VSYNC signal is received but the PageFlip event is not received, multiple image data can be drawn in multiple buffers to the greatest extent, which is beneficial to improving the frame rate.

[0062] The cache management component 23 is used to manage the cache.

[0063] Please refer to Figure 4 , the cache management component 23 includes a cache production component 231 (Buffer Producer), a cache queue 232, and a cache consumption component 233 (Buffer Consumer). The cache production component 231 is used to allocate a cache area for the application 24 according to the requirements of the application 24, so that the application 24 can draw image data into the cache area. The cache queue 232 includes multiple cache areas, and the cache areas are used to store image data. The cache consumption component 233 is used to read the image data from the cache queue 232 and transmit the image data to the display device for display through the DRM driver component 25. The DRM driver component 25 manages the display hardware in the Linux kernel and can provide an interface for the application to directly access the display hardware.

[0064] The cache management component 23 supports the producer-consumer mode. The application draws the image data into the cache queue 232 through the cache production component 231, and the cache consumption component 233 reads the image data from the cache queue 232. In this way, it can ensure that the image data is produced and consumed normally in an orderly manner.

[0065] The cache management component 23 is configured with multiple types of cache APIs, including a quantity setting interface (Buffer count API), a cache application interface (Alloc buffer API), an image drawing interface (Dequeue buffer API), a to-be-displayed interface (Queue buffer API), and a cache release interface (Cancel buffer API).

[0066] When the application 24 calls the quantity setting interface of the cache management component 23, the cache management component 23 determines the cache quantity of the cache area that the application 24 needs to apply for. For example, the application 24 needs to apply for 2 or 3 or 4 cache areas, that is, the cache quantity is 2 or 3 or 4.

[0067] When the application 24 calls the cache application interface of the cache management component 23, the cache management component 23 allocates multiple cache areas consistent with the cache quantity for the application 24, and the multiple cache areas constitute the cache queue 232.

[0068] Each buffer is provided with a status flag, and the status flag includes an idle flag, a drawing flag, and a to-be-displayed flag. The idle flag is used to indicate that no image data is stored in the buffer. The drawing flag is used to indicate that the application is drawing image data into the buffer. The to-be-displayed flag is used to indicate that the application has completed drawing image data into the buffer.

[0069] In the embodiments of the present application, it is defined that: a buffer with an idle flag is an available buffer, a buffer with a drawing flag is an occupied buffer, and a buffer with a to-be-displayed flag is a to-be-displayed buffer.

[0070] Please combine Figure 4 , in the embodiments of the present application, "free" is used as the idle flag, "dequeued" is used as the drawing flag, and "queued" is used as the to-be-displayed flag. The status flag of the first buffer 41 is the drawing flag, indicating that the first buffer 41 is waiting to be drawn or is being drawn with image data, that is, the first buffer 41 is an occupied buffer. The status flag of the second buffer 42 is the to-be-displayed flag, indicating that the second buffer 42 has been drawn with image data by the application and is waiting for the cache consumption component 233 to take the image data from the second buffer 42 and send it to the display device for display, that is, the second buffer 42 is a to-be-displayed buffer. The status flags of the third buffer 43, the fourth buffer 44, and the fifth buffer 45 are the idle flags, indicating that the application can draw image data into the third buffer 43, the fourth buffer 44, or the fifth buffer 45, that is, the third buffer 43, the fourth buffer 44, and the fifth buffer 45 are available buffers.

[0071] When the application 24 calls the image drawing interface of the cache management component 23, it notifies the cache management component 23 to set the corresponding buffer as an occupied buffer and can draw image data on the occupied buffer.

[0072] When the application 24 calls the to-be-displayed interface of the cache management component 23, it notifies the cache management component 23 to set the occupied buffer as a to-be-displayed buffer.

[0073] In the embodiments of the present application, a multi-buffer approach is adopted. One or more buffers are set as to-be-displayed buffers, and another or other multiple buffers are set as occupied buffers. The to-be-displayed buffers are used for foreground buffering of image data, and the occupied buffers are used for background buffering of image data. After the image data in the to-be-displayed buffer is taken away and the display is completed, after obtaining the VSYNC signal and the PageFlip event, the embodiments of the present application can update the occupied buffer into a to-be-displayed buffer, that is: switch the background buffer to the foreground buffer for display, and at the same time start the next round of drawing of image data, so as to improve the display smoothness and avoid the screen from flickering.

[0074] Next, the embodiments of the present application provide a display control method for a cockpit display framework, and the cockpit display framework is the cockpit display framework described in the above various embodiments. Please refer to Figure 5 , and the display control method includes steps S51 to S55.

[0075] The embodiments of the present application execute step S51, in response to a cache allocation request sent by an application to the cache management component, control the cache management component to allocate multiple cache areas for the application, and the multiple cache areas form a cache queue.

[0076] There are many trigger events that trigger the application to send a cache allocation request to the cache management component. The trigger events include initialization events, physical button events, virtual button events, voice events, intermediate events, or third-party application trigger events, etc. An initialization event refers to an event when the cockpit display framework enters the initial state. A physical button event refers to an event when a physical button of the vehicle cockpit is pressed. A virtual button event refers to an event when a virtual button on the main interface of the application is pressed. A voice event refers to an event when the vehicle cockpit responds to voice data collected by the voice acquisition module and starts the application. An intermediate event refers to an event when the application needs to display a screen in a process. A third-party application trigger event refers to an event when a third-party application triggers the application to display a screen.

[0077] The cache allocation request is used to request the cache management component to allocate multiple cache areas for the application. The cache management component is configured with a quantity setting interface and a cache application interface. The cache allocation request includes a quantity setting request and a cache application request. The quantity setting request is used to determine the cache quantity required by the application, and the cache application request is used to request the cache management component to allocate multiple cache areas to the application according to the cache quantity.

[0078] The cache management component includes a cache production component. Responding to the cache allocation request sent by the application to the cache management component, controlling the cache management component to allocate multiple cache areas for the application includes the following steps: responding to the quantity setting request sent by the application calling the quantity setting interface to the cache production component, determining the cache quantity, and responding to the cache application request sent by the application calling the cache application interface to the cache production component, controlling the cache production component to allocate multiple cache areas to the application according to the cache quantity.

[0079] The quantity setting request carries the application identifier of the application and the cache quantity. The cache production component parses the quantity setting request to obtain the application identifier and the cache quantity, and establishes the correspondence between the application and the cache quantity based on the application identifier and the cache quantity. When the application sends a cache application request to the cache production component, the cache production component allocates a buffer area with a quantity consistent with the cache quantity to the application. It can be understood that the cache quantity is customized by the application according to requirements, and the cache quantity can be 1 or more than 2.

[0080] In the embodiment of the present application, by sequentially calling the quantity setting interface and the cache application interface, the cache production component is controlled to allocate a cache queue for the application. Such a working mechanism is particularly important in a complex cache application environment and can ensure that the corresponding quantity of buffer areas is reliably allocated to each application that needs to apply for a buffer area.

[0081] In the embodiment of the present application, step S52 is executed to respond to the image drawing request sent by the application to the cache management component, and control the cache management component to update the available buffer area to the occupied buffer area, so that the application can draw the target image data to the occupied buffer area. The available buffer area is the buffer area in the cache queue that can be used to draw image data.

[0082] When the cache management component successfully allocates a cache queue to the application, the cache management component sends a cache application success message to the application. The application responds to the cache application success message and sends an image drawing request to the cache management component.

[0083] Specifically, in the embodiment of the present application, in response to the image drawing request sent by the application to the cache production component by calling the image drawing interface, the cache production component is controlled to select an available buffer area that meets the preset drawing conditions in the cache queue as the occupied buffer area, and the cache production component is controlled to return the cache address of the occupied buffer area to the application, so that the application can draw the target image data to the occupied buffer area based on the cache address.

[0084] It can be understood that the cache queue may or may not have an available buffer area. For example, all buffer areas in the cache queue are buffer areas to be displayed or a combination of buffer areas to be displayed and occupied buffer areas.

[0085] Each buffer is configured with a status flag. The constituent elements of the preset drawing condition include an available buffer whose status flag is an idle flag. In the embodiment of the present application, in response to an image drawing request sent by an application program to the cache production component by calling an image drawing interface, it controls the cache production component to check whether there is an available buffer with a status flag of an idle flag in the cache queue. If there is an available buffer with a status flag of an idle flag in the cache queue, it controls the cache production component to update the available buffer to an occupied buffer. If there is no available buffer with a status flag of an idle flag in the cache queue, it is determined that there is no available buffer in the cache queue.

[0086] In the embodiment of the present application, the available buffer is updated to an occupied buffer, so that the application program exclusively occupies the occupied buffer, avoiding other application programs from writing other image data into the occupied buffer with target image data already drawn, thus erasing the existing target image data in the occupied buffer, and further avoiding the loss of target image data. At the same time, it avoids the problem of image data loss caused by the application program competing with other applications for the same occupied buffer.

[0087] Controlling the cache production component to update the available buffer to an occupied buffer includes the following steps: updating the status flag of the available buffer to a drawing flag, that is, the available buffer becomes an occupied buffer.

[0088] In some embodiments, when there is no available buffer in the cache queue, the cache production component performs a blocking operation to delay the operation of the application program to draw target image data into the cache queue, ensuring that the target image data will not be overwritten or lost.

[0089] The embodiment of the present application executes step S53. In response to a drawing completion request sent by an application program to the cache management component, it controls the cache management component to update the occupied buffer to a buffer to be displayed. The drawing completion request is used to indicate that the application program has drawn all the target image data in the occupied buffer.

[0090] The cache management component is configured with an interface to be displayed. In response to a drawing completion request sent by an application program to the cache management component, controlling the cache management component to update the occupied buffer to a buffer to be displayed includes the following steps: in response to the application program calling the interface to be displayed to send a drawing completion request to the cache production component, controlling the cache production component to update the status flag of the occupied buffer to a to-be-displayed flag, and determining the buffer that meets the preset display condition among all the buffers with the to-be-displayed flag as the buffer to be displayed.

[0091] After the application example of the present application completely draws the target image data into the occupied buffer, it can automatically update the occupied buffer to the buffer to be sent for display, so that the buffer management component can transmit the target image data to the display device through the DRM driver component for display processing.

[0092] The constituent elements of the preset display condition include that the timestamp of the buffer with the to-be-displayed identifier is the earliest timestamp in the buffer queue. Determining the buffer that meets the preset display condition as the buffer to be sent for display among all the buffers with the to-be-displayed identifier includes the following steps: determining the timestamp of each buffer with the to-be-displayed identifier, finding out the earliest timestamp among all the timestamps, and determining the buffer corresponding to the earliest timestamp as the buffer to be sent for display. In this way, the application example of the present application can control each display screen to be displayed in sequence according to the time sequence, thereby ensuring the continuity of the screen display and improving the user experience.

[0093] The application example of the present application executes step S54, responds to the display control request sent by the application to the display management component, and controls the display management component to generate display control information.

[0094] The display management component is configured with an image display interface, and the display control information includes an image display identifier, which is used to instruct the display device to display the display screen corresponding to the target image data. The display management component is configured with an image hiding interface, and the display control information includes an image hiding identifier, which is used to instruct the display device to hide the display screen corresponding to the target image data.

[0095] The display management component is configured with a transparency interface, and the display control information includes a transparency parameter, which is used to instruct the display device to adjust the transparency of the display screen corresponding to the target image data. The display management component is configured with a window setting interface, and the display control information includes window setting parameters, which are used to instruct the display device to control the window attributes of the target window, and the target window is the window for displaying the display screen corresponding to the target image data.

[0096] The display management component is configured with an image cropping interface, and the display control information includes image cropping parameters, which are used to instruct the display device to crop the display screen corresponding to the target image data. The display management component is configured with a layer priority interface, and the display control information includes layer priority parameters, which are used to instruct the display management component to adjust the superior-subordinate relationship between each application layer.

[0097] The application example of the present application provides rich display APIs, and the application can meet various image display requirements by calling various display APIs.

[0098] In the embodiment of the present application, step S55 is executed to control the cache management component to transmit the display control information and the target image data in the display buffer to the display device for display processing through the DRM driver component in response to the cache display request sent by the refresh rate component. The cache display request is used to indicate that the refresh rate component receives the image display signal sent by the DRM driver component.

[0099] The image display signal includes a VSYNC signal and / or a PageFlip signal corresponding to a PageFlip event. In the embodiment of the present application, the VSYNC signal and the PageFlip event that need to be transmitted by the DRM driver component are required to display the picture. In this way, not only can the phenomenon of picture tearing be avoided, but also when the VSYNC signal is received but the PageFlip event is not received, multiple image data can be drawn in multiple buffers to the greatest extent, which is beneficial to improving the frame rate.

[0100] The cache management component includes a cache consumption component. In the embodiment of the present application, the cache display request sent by the refresh rate component to the cache consumption component is obtained, and in response to the cache display request, the cache consumption component is controlled to respond to the cache display request to read the target image data in the display buffer and the display control information of the display management component, and the cache consumption component is controlled to transmit the target image data and the display control information to the display device for display processing through the DRM driver component.

[0101] The embodiment of the present application implements a producer-consumer cache management mode, which can ensure that image data is produced and consumed in an orderly and reliable manner, which is beneficial to improving the smoothness of image display.

[0102] If the display control information includes an image display identifier, the display device displays the display screen corresponding to the target image data based on the image display identifier. If the display control information includes an image hiding identifier, the display device hides the display screen corresponding to the target image data based on the image hiding identifier.

[0103] If the display control information includes a transparency parameter, the display device sets the transparency of the display screen corresponding to the target image data based on the transparency parameter. If the display control information includes window setting parameters, the display device sets the size and position of the window corresponding to the display screen based on the window setting parameters.

[0104] If the display control information includes image cropping parameters, the display device crops a partial screen corresponding to the image cropping parameters from the display screen corresponding to the target image data for display. If the display control information includes layer priority parameters, the display device adjusts the superior-subordinate relationship between the display screen corresponding to the target image data and the existing layers based on the layer priority parameters.

[0105] Generally speaking, the display control method provided by the embodiments of the present application is based on a simple and lightweight cockpit display framework, which can occupy less system resources to process display events and display the screen more efficiently and quickly. At the same time, the cockpit display framework provided by the embodiments of the present application does not depend on or attach to any open-source display framework to process display events. Only after the DRM driver component runs, it can normally draw and display the screen. Therefore, the embodiments of the present application avoid the problem of low efficiency caused by running an open-source display architecture, and can normally draw and display the screen only through a simple and lightweight cockpit display framework, thereby improving the display efficiency.

[0106] It should be noted that in the above various embodiments, there is not necessarily a certain order among the above steps. Those of ordinary skill in the art can understand according to the description of the embodiments of the present application that in different embodiments, the above steps can have different execution orders, that is, they can be executed in parallel, or they can be exchanged and executed, etc.

[0107] As another aspect of the embodiments of the present application, the embodiments of the present application provide a display control device for a cockpit display framework, which applies the cockpit display frameworks described in the above various embodiments. Among them, the display control device of the cockpit display framework can be a software module, and the software module includes several instructions, which are stored in a memory. The processor can access this memory and call the instructions for execution to complete the display control method of the cockpit display framework described in the above various embodiments.

[0108] In some embodiments, the display control device of the cockpit display framework can also be built by hardware devices. For example, the display control device of the cockpit display framework can be built by one or more than two chips, and each chip can work in coordination with each other to complete the display control method of the cockpit display framework described in the above various embodiments. For another example, the display control device of the cockpit display framework can also be built by various logic devices, such as built by a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), a single-chip microcomputer, an ARM (Acorn RISC Machine), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination of these components.

[0109] Please refer to Figure 6 , the display control device 600 of the cockpit display framework includes a cache application module 61, a data drawing module 62, a cache display sending module 63, a display control module 64, and a data transmission module 65.

[0110] The cache application module 61 is used to respond to a cache allocation request sent by an application to the cache management component, and control the cache management component to allocate multiple cache areas for the application. The multiple cache areas form a cache queue. The data drawing module 62 is used to respond to an image drawing request sent by the application to the cache management component, and control the cache management component to update the available cache area to an occupied cache area, so that the application can draw target image data into the occupied cache area. The available cache area is a cache area in the cache queue that can be used to draw image data. The cache display module 63 is used to respond to a drawing completion request sent by the application to the cache management component, and control the cache management component to update the occupied cache area to a cache area to be displayed. The drawing completion request is used to indicate that the application has completely drawn the target image data into the occupied cache area. The display control module 64 is used to respond to a display control request sent by the application to the display management component, and control the display management component to generate display control information. The data transmission module 65 is used to respond to a cache display request sent by the refresh rate component to the cache management component, and control the cache management component to transmit the display control information and the target image data of the cache area to be displayed to the display device through the DRM driver component for display processing. The cache display request is used to indicate that the refresh rate component has received an image display signal sent by the DRM driver component.

[0111] In some embodiments, the cache management component is configured with a quantity setting interface and a cache application interface. The cache allocation request includes a quantity setting request and a cache application request. The cache management component includes a cache production component. Specifically, the cache application module 61 is used to: respond to a quantity setting request sent by the application to the cache production component by calling the quantity setting interface, determine the cache quantity, and respond to a cache application request sent by the application to the cache production component by calling the cache application interface, and control the cache production component to allocate multiple cache areas for the application according to the cache quantity.

[0112] In some embodiments, the cache management component is configured with an image drawing interface. The cache management component includes a cache production component. Specifically, the data drawing module 62 is used to: respond to an image drawing request sent by the application to the cache production component by calling the image drawing interface, control the cache production component to select an available cache area that meets the preset drawing conditions in the cache queue as the occupied cache area, and control the cache production component to return the cache address of the occupied cache area to the application, so that the application can draw the target image data into the occupied cache area based on the cache address.

[0113] In some embodiments, each buffer is configured with a status flag. The constituent elements of the preset drawing condition include a buffer with a status flag being an idle flag. The data drawing module 62 is specifically configured to: in response to an image drawing request sent by an application program calling an image drawing interface to a buffer production component, control the buffer production component to check whether there is an available buffer with a status flag being an idle flag in the buffer queue. If there is an available buffer with a status flag being an idle flag in the buffer queue, control the buffer production component to update the available buffer to an occupied buffer.

[0114] In some embodiments, the buffer management component is configured with a to-be-displayed interface. The buffer management component includes a buffer production component. Each buffer is configured with a status flag. The buffer display module 63 is specifically configured to: in response to a drawing completion request sent by an application program calling the to-be-displayed interface to the buffer production component, control the buffer production component to update the status flag of the occupied buffer to a to-be-displayed flag. The drawing completion request is used to indicate that the application program has completed the drawing of target image data in the available buffer, and determine a buffer that meets the preset display condition among all the buffers with the to-be-displayed flag as the to-be-displayed buffer.

[0115] In some embodiments, the constituent elements of the preset display condition include that the timestamp of a buffer with the to-be-displayed flag is the earliest timestamp in the buffer queue. The buffer display module 63 is specifically configured to: determine the timestamp of each buffer with the to-be-displayed flag, find out the earliest timestamp among all the timestamps, and determine the buffer corresponding to the earliest timestamp as the to-be-displayed buffer.

[0116] In some embodiments, the buffer management component includes a buffer consumption component. The data transmission module 65 is specifically configured to: obtain a buffer display request sent by a refresh rate component to the buffer consumption component, in response to the buffer display request, control the buffer consumption component to read the target image data of the to-be-displayed buffer and the display control information of the display management component, and control the buffer consumption component to transmit the target image data and the display control information to a display device through a DRM driver component for display processing.

[0117] In some embodiments, the display management component is configured with an image display interface. The display control information includes an image display flag, and the image display flag is used to instruct the display device to display a display screen corresponding to the target image data.

[0118] In some embodiments, the display management component is configured with an image hiding interface. The display control information includes an image hiding flag, and the image hiding flag is used to instruct the display device to hide a display screen corresponding to the target image data.

[0119] In some embodiments, the display management component is configured with a transparency interface, and the display control information includes transparency parameters, which are used to instruct the display device to adjust the transparency of the display screen corresponding to the target image data.

[0120] In some embodiments, the display management component is configured with a window setting interface, and the display control information includes window setting parameters, which are used to instruct the display device to control the window attributes of the target window, where the target window is the window for displaying the display screen corresponding to the target image data.

[0121] In some embodiments, the display management component is configured with an image cropping interface, and the display control information includes image cropping parameters, which are used to instruct the display device to crop the display screen corresponding to the target image data.

[0122] In some embodiments, the display management component is configured with a layer priority interface, and the display control information includes layer priority parameters, which are used to instruct the display management component to adjust the hierarchical relationship between various application layers.

[0123] It should be noted that the display control device of the above cockpit display framework can execute the display control method of the cockpit display framework provided by the embodiments of the present application, and has the corresponding functional modules and beneficial effects for executing the method. For the technical details not described in detail in the embodiments of the display control device of the cockpit display framework, reference can be made to the display control method of the cockpit display framework provided by the embodiments of the present application.

[0124] See Figure 7 , Figure 7 is a schematic structural diagram of a computer device provided by an embodiment of the present application. The computer device 700 includes one or more processors 71 and a memory 72. The memory 72 is connected to one or more processors 71, for example, connected to the processor 71 through a bus.

[0125] The processor 71 is configured to support the computer device in performing the corresponding functions in the methods in the above method embodiments. The processor 71 may be a central processing unit (CPU), a network processor (NP), a hardware chip, or any combination thereof. The above hardware chip may be an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The above PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

[0126] The memory 72 is used to store program codes, etc. The memory 72 may include volatile memory (VM), such as random access memory (RAM); the memory may also include non-volatile memory (NVM), such as read-only memory (ROM), flash memory, a hard disk drive (HDD), or a solid-state drive (SSD); the memory may further include a combination of the above types of memory.

[0127] The memory 72 can be used to store non-volatile software programs, non-volatile computer executable programs, and modules, such as the program instructions / modules corresponding to the display control method of the cockpit display framework in the embodiments of the present application. By running the non-volatile software programs, instructions, and modules stored in the memory, the processor executes various functional applications and data processing of the display control method of the cockpit display framework and the display control device of the cockpit display framework, that is, implements the functions of each module or unit of the display control method of the cockpit display framework and the display control device of the cockpit display framework provided in the above method embodiments.

[0128] The memory 72 may include a program storage area and a data storage area. The program storage area may store an operating system and application programs required for at least one function. The data storage area may store data created according to the use of the display control device of the cockpit display framework, etc. In some embodiments, the memory may optionally include a memory remotely set relative to the processor, and these remote memories may be connected to the display control device of the cockpit display framework through a network. Examples of the above network include but are not limited to the Internet, intranet, local area network, mobile communication network, and combinations thereof.

[0129] The one or more modules are stored in the memory and, when executed by the one or more processors, execute the display control method of the cockpit display framework in any of the above method embodiments. For example, the method steps described in the above method embodiments are executed to implement the functions of the modules described in the above device embodiments.

[0130] An embodiment of the present application further provides a computer-readable storage medium storing a computer program, the computer program including program instructions, and the program instructions, when executed by a computer device, cause the computer to execute the method as described in the foregoing embodiments.

[0131] Those of ordinary skill in the art can understand that all or part of the processes in the above method embodiments can be completed by instructing relevant hardware through a computer program. The program can be stored in a computer-readable storage medium, and when executed, it may include the processes of the above method embodiments. Among them, the storage medium may be a magnetic disk, optical disk, read-only memory (ROM), or random access memory (RAM), etc.

[0132] The above disclosure is only for the preferred embodiments of the present application, and of course, it cannot be used to limit the scope of rights of the present application. Therefore, equivalent changes made according to the claims of the present application still fall within the scope covered by the present application.

Claims

1. A display control method for a cockpit display frame, characterized in that, The cockpit display framework includes a display management component, a refresh rate component, and a cache management component. The display control method includes: Responding to a cache allocation request sent by an application to the cache management component, controlling the cache management component to allocate multiple cache areas for the application, and the multiple cache areas form a cache queue; Responding to an image drawing request sent by the application to the cache management component, controlling the cache management component to update an available cache area to an occupied cache area, so that the application draws target image data to the occupied cache area, and the available cache area is a cache area in the cache queue that can be used to draw image data; Responding to a drawing completion request sent by the application to the cache management component, controlling the cache management component to update the occupied cache area to a cache area to be sent for display. The drawing completion request is used to indicate that the application has drawn all the target image data in the occupied cache area; Responding to a display control request sent by the application to the display management component, controlling the display management component to generate display control information; Responding to a cache sending request sent by the refresh rate component to the cache management component, controlling the cache management component to transmit the display control information and the target image data of the cache area to be sent for display to a display device through a DRM driver component for display processing. The cache sending request is used to indicate that the refresh rate component has received an image sending signal sent by the DRM driver component; 2. The display control method according to claim 1, wherein The cache management component is configured with a quantity setting interface and a cache application interface. The cache allocation request includes a quantity setting request and a cache application request. The cache management component includes a cache production component. Responding to a cache allocation request sent by an application to the cache management component, controlling the cache management component to allocate multiple cache areas for the application includes: Responding to a quantity setting request sent by the application to the cache production component by calling the quantity setting interface, determining the cache quantity; Responding to a cache application request sent by the application to the cache production component by calling the cache application interface, controlling the cache production component to allocate multiple cache areas for the application according to the cache quantity; 3. The display control method according to claim 1, wherein The cache management component is configured with an image drawing interface. The cache management component includes a cache production component. Responding to an image drawing request sent by the application to the cache management component, controlling the cache management component to update an available cache area to an occupied cache area, so that the application draws target image data to the occupied cache area, includes: Responding to an image drawing request sent by the application to the cache production component by calling the image drawing interface, controlling the cache production component to select an available cache area that meets a preset drawing condition in the cache queue as the occupied cache area; Controlling the cache production component to return the cache address of the occupied cache area to the application, so that the application draws target image data to the occupied cache area based on the cache address.

4. The display control method according to claim 3, wherein Each of the buffer areas is configured with a status identifier. The constituent elements of the preset drawing condition include an available buffer area with a status identifier being an idle identifier. Responding to the image drawing request sent by the application program to the buffer production component by invoking the image drawing interface, and controlling the buffer production component to select an available buffer area that meets the preset drawing condition in the buffer queue as the occupied buffer area includes: Responding to the image drawing request sent by the application program to the buffer production component by invoking the image drawing interface, and controlling the buffer production component to check whether there is an available buffer area with a status identifier being an idle identifier in the buffer queue; If there is an available buffer area with a status identifier being an idle identifier in the buffer queue, then controlling the buffer production component to update the available buffer area to an occupied buffer area.

5. The display control method according to claim 1, wherein The buffer management component is configured with a to-be-displayed interface. The buffer management component includes a buffer production component. Each of the buffer areas is configured with a status identifier. Responding to the drawing completion request sent by the application program to the buffer management component, and controlling the buffer management component to update the occupied buffer area to a to-be-displayed buffer area includes: Responding to the drawing completion request sent by the application program to the buffer production component by invoking the to-be-displayed interface, and controlling the buffer production component to update the status identifier of the occupied buffer area to a to-be-displayed identifier; Determining, among all the buffer areas with the to-be-displayed identifier, the buffer area that meets the preset display condition as the to-be-displayed buffer area.

6. The display control method according to claim 5, wherein The constituent elements of the preset display condition include that the time stamp of the buffer area with the to-be-displayed identifier is the earliest time stamp in the buffer queue. Determining, among all the buffer areas with the to-be-displayed identifier, the buffer area that meets the preset display condition as the to-be-displayed buffer area includes: Determining the time stamp of each buffer area with the to-be-displayed identifier; Finding out the earliest time stamp among all the time stamps; Determining the buffer area corresponding to the earliest time stamp as the to-be-displayed buffer area.

7. The display control method according to claim 1, characterized in that The buffer management component includes a buffer consumption component. Responding to the buffer display request sent by the refresh rate component to the buffer management component, and controlling the buffer management component to transmit the display control information and the target image data of the to-be-displayed buffer area to the display device through the DRM driver component for display processing includes: Obtaining the buffer display request sent by the refresh rate component to the buffer consumption component; Responding to the buffer display request, and controlling the buffer consumption component to read the target image data of the to-be-displayed buffer area and read the display control information of the display management component; Controlling the buffer consumption component to transmit the target image data and the display control information to the display device through the DRM driver component for display processing.

8. The display control method according to any one of claims 1 to 7, wherein The display management component is configured with an image display interface. The display control information includes an image display identifier, and the image display identifier is used to instruct the display device to display a display picture corresponding to the target image data; and / or, The display management component is configured with an image hiding interface, and the display control information includes an image hiding identifier for instructing the display device to hide the display screen corresponding to the target image data; and / or, The display management component is configured with a transparency interface, and the display control information includes transparency parameters for instructing the display device to adjust the transparency of the display screen corresponding to the target image data; and / or, The display management component is configured with a window setting interface, and the display control information includes window setting parameters for instructing the display device to control the window attributes of a target window, where the target window is the window for displaying the display screen corresponding to the target image data; and / or, The display management component is configured with an image cropping interface, and the display control information includes image cropping parameters for instructing the display device to crop the display screen corresponding to the target image data; and / or, The display management component is configured with a layer priority interface, and the display control information includes layer priority parameters for instructing the display management component to adjust the hierarchical relationship between various application layers.

9. A computer device, characterized in that, It includes a memory and a processor, the memory is connected to the processor, and the processor is configured to execute one or more computer programs stored in the memory. When the processor executes the one or more computer programs, the computer device implements the display control method of the cockpit display framework according to any one of claims 1-8.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, the computer program includes program instructions, and when the program instructions are executed by the processor, the processor is caused to execute the display control method of the cockpit display framework according to any one of claims 1-8.

Images