Cross-system picture display method and device, equipment and medium

Abstract

The invention relates to a cross-system picture display method and device, equipment and a medium. The first domain system performs picture display on a first physical display device according to the first display data, and / or sends the first display data to a second domain system through a virtualization channel, and the second domain system performs picture display on a second physical display device according to the first display data; and the first domain system receives second display data sent by the second domain system through the virtualization channel, and performs picture display on the first physical display equipment according to the second display data. Through the embodiment of the invention, two-way synchronous picture display of different systems can be realized, and the interestingness of a product is improved, so that the increasing requirements of users are met.

Description

Technical Field

[0001] This invention relates to the technical field of screen display, and more specifically to a cross-system screen display method, apparatus, device, and medium. Background Technology

[0002] As user demands continue to increase, the number of screens in vehicles is growing; different screens may correspond to different systems; in practical applications, a single system can control a single screen and display only content specific to that system. This display method is becoming increasingly difficult to meet user needs as cockpit requirements continue to grow. Summary of the Invention

[0003] In view of the above problems, a cross-system screen display method, apparatus, device, and medium are proposed to overcome or at least partially solve the above problems, including:

[0004] A cross-system screen display method is applied to a central control system, the central control system including a first domain system and a second domain system. The first domain system is equipped with at least one first physical display device, and the second domain system is equipped with at least one second physical display device. A virtualization channel is provided between the first domain system and the second domain system. A display fusion module is provided in the first domain system. The display fusion module is used to receive display data and / or touch data sent by the second domain system through the virtualization channel, and to send display data and / or touch data to the second domain system through the virtualization channel. The method includes:

[0005] The first domain system displays the image on the first physical display device according to the first display data, and / or sends the first display data to the second domain system through the virtualization channel, and the second domain system displays the image on the second physical display device according to the first display data;

[0006] The first domain system receives the second display data sent by the second domain system through the virtualization channel, and displays the image on the first physical display device according to the second display data.

[0007] Optionally, the step of displaying the image on the first physical display device according to the second display data includes:

[0008] Determine the first layer of the second display data on the first physical display device;

[0009] The second display data is displayed on the first layer of the first physical display device.

[0010] Optionally, the method further includes:

[0011] Determine the priority of the display data corresponding to each layer of the first physical display device;

[0012] Enable the layer corresponding to the highest priority data display and disable other layers.

[0013] Optionally, the first physical display device includes multiple devices, the virtualization channel includes multiple channels, and there is a correspondence between the first physical display device and the virtualization channel; the step of displaying the image on the first physical display device according to the second display data includes:

[0014] Determine the target virtualization channel corresponding to the second displayed data;

[0015] Based on the target virtualization channel corresponding to the second display data, a target first physical display device is determined, and the second display data is displayed on the target first physical display device.

[0016] Optionally, the method further includes:

[0017] Receive the first touch data and determine the target application corresponding to the first touch data;

[0018] The first touch data is sent to the target application, which is used to control the display of the target physical display device corresponding to the first touch data based on the first touch data.

[0019] Optionally, determining the target application corresponding to the first touch data includes:

[0020] Determine the second layer of the first touch data on the first physical display device;

[0021] Based on the second layer, determine the target application corresponding to the first touch data.

[0022] Optionally, the first physical display device includes multiple display areas, and the step of displaying the image on the first physical display device according to the first display data includes:

[0023] The first display data is split to obtain a first sub-display data and a second sub-display data;

[0024] The first sub-display data corresponds to a display area on the first physical display device, and the second sub-display data corresponds to a display area on the first physical display device;

[0025] Based on the first sub-display data and the second sub-display data, the screen is displayed in different display areas on the first physical display device.

[0026] Optionally, the second domain system is configured to send the second display data to the first domain system for display through the virtualization channel when it is determined that the second display data belongs to a virtualization device; and to display the image on the second physical display device according to the second display data when it is determined that the second display data does not belong to a virtualization device.

[0027] Optionally, the second domain system is used to display a screen on the second physical display device according to the third display data; the second display data and the third display data are different parts of the same display data.

[0028] This invention also provides a cross-system screen display device applied to a central control system. The central control system includes a first domain system and a second domain system. The first domain system is equipped with at least one first physical display device, and the second domain system is equipped with at least one second physical display device. A virtualization channel is provided between the first domain system and the second domain system. A display fusion module is provided in the first domain system. The display fusion module is used to receive display data and / or touch data sent by the second domain system through the virtualization channel, and to send display data and / or touch data to the second domain system through the virtualization channel. The device includes:

[0029] A display module is configured to display a screen on the first physical display device according to the first display data, and / or send the first display data to the second domain system through the virtualization channel, wherein the second domain system displays a screen on the second physical display device according to the first display data;

[0030] The receiving and display module is used to receive second display data sent by the second domain system through the virtualization channel, and to display the image on the first physical display device according to the second display data.

[0031] The present invention also provides an electronic device, including a processor, a memory, and a computer program stored in the memory and capable of running on the processor, wherein the computer program, when executed by the processor, implements the cross-system screen display method described above.

[0032] The present invention also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the above-described cross-system screen display method.

[0033] The beneficial effects of this invention are:

[0034] In the embodiments of this invention, a first domain system displays the image on a first physical display device based on first display data, and / or sends the first display data to a second domain system via a virtualization channel. The second domain system then displays the image on the second physical display device based on the first display data. The first domain system receives second display data sent by the second domain system via the virtualization channel and displays the image on the first physical display device based on the second display data. Through these embodiments, bidirectional synchronous image display between different systems can be achieved, enhancing the product's appeal and thus better meeting the increasing demands of users. Attached Figure Description

[0035] Figure 1 This is a flowchart illustrating the steps of a cross-system screen display method according to an embodiment of the present invention;

[0036] Figure 2 This is a flowchart of another cross-system screen display method according to an embodiment of the present invention;

[0037] Figure 3 This is a flowchart of another cross-system screen display method according to an embodiment of the present invention;

[0038] Figure 4 This is a schematic diagram of the structure of a central control system according to an embodiment of the present invention;

[0039] Figure 5 This is a schematic diagram of cross-system data interaction according to an embodiment of the present invention;

[0040] Figure 6 This is a schematic diagram of a scenario according to an embodiment of the present invention;

[0041] Figure 7 This is a schematic diagram of the structure of a cross-system screen display device according to an embodiment of the present invention. Detailed Implementation

[0042] To make the above-mentioned objects, features, and advantages of the present invention more apparent and understandable, the present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without inventive effort are within the scope of protection of the present invention.

[0043] Reference Figure 1 The diagram illustrates a flowchart of a cross-system screen display method according to an embodiment of the present invention, which may include the following steps:

[0044] Step 101: The first domain system displays the image on the first physical display device according to the first display data, and / or sends the first display data to the second domain system through a virtualization channel. The second domain system displays the image on the second physical display device according to the first display data.

[0045] In one embodiment of the present invention, the above method can be applied to a central control system, which includes a first domain system and a second domain system. The first domain system is provided with at least one first physical display device, and the second domain system is provided with at least one second physical display device. A virtualization channel is provided between the first domain system and the second domain system. A display fusion module is provided in the first domain system. The display fusion module is used to receive display data and / or touch data sent by the second domain system through the virtualization channel, and to send display data and / or touch data to the second domain system through the virtualization channel.

[0046] The central control system can be the central control system in a vehicle, which can include at least a first domain system and a second domain system based on virtualization isolation; it can also include a third domain system and a fourth domain system. The specific number is not limited in the embodiments of the present invention.

[0047] For example, the first domain system can be the cockpit domain IVI (In-Vehicle Infotainment), also known as GuestOS (IVI); the cockpit domain IVI business emphasizes interactive experience and a rich application ecosystem, and the most suitable operating system is Android.

[0048] The second domain system can be an Instrument Cluster (IC), also known as a HostOS (IC). Instrument panels have real-time and reliability requirements, and the operating system tends to be RTLinux (Real-Time Linux) or RTOS (Real-Time Operating System), etc. This embodiment of the invention does not limit this.

[0049] In a first domain system, at least one first physical display device can be controlled; for example, the first physical display device may include one or more. In a second domain system, at least one second physical display device can also be controlled; for example, the second physical display device may include one or more. The embodiments of the present invention do not impose specific limitations on the number of first physical display devices and second physical display devices.

[0050] The first physical display device can be a display screen, such as an instrument panel screen, a secondary instrument panel screen, or a passenger-side screen in a vehicle.

[0051] The second physical display device can also be a display screen, such as an instrument panel screen, IVI screen, secondary instrument panel screen, or passenger-side screen in a vehicle. In this embodiment of the invention, the specific display screens referred to by the first and second physical display devices are not limited, and can be set according to actual needs.

[0052] Multiple virtualization channels based on the virtio protocol can be established between the first domain system and the second domain system to meet the display device requirements of different services.

[0053] The first domain system can be equipped with a display fusion module, which can be composed of virtio-display (virtualized output device), virtio-input (virtualized output device), and virtio-gpu (virtualized graphics processor). The display fusion module can be used for interactive display data between the first domain system and the second domain system, and can also be used for interactive touch data between the first domain system and the second domain system, thereby realizing the fusion interaction of display data and touch data.

[0054] In some feasible embodiments, in order to achieve cross-system screen display, after receiving the first display data, the first domain system can first determine the display device to which the first display data is to be displayed. The first display data can be display data sent to the first domain system by the application program.

[0055] If the first display data needs to be displayed on the first physical display device, the first domain system can directly display the screen on the first physical display device according to the first display data to display the screen corresponding to the first display data.

[0056] If the first display data needs to be displayed on the second physical display device, the first domain system can send the first display data to the second domain system through a virtualization channel; after receiving the first display data, the second domain system can display the image on the second physical display device according to the first display data, so as to display the image corresponding to the first display data on the second physical display device.

[0057] If the first display data needs to be displayed on both a first physical display device and a second physical display device, the first domain system can directly display the image on the first physical display device based on the first display data to display the image corresponding to the first display data; and it can also send the first display data to the second domain system through a virtualization channel. After receiving the first display data, the second domain system can display the image on the second physical display device based on the first display data to display the image corresponding to the first display data on the second physical display device.

[0058] Step 102: The first domain system receives the second display data sent by the second domain system through the virtualization channel, and displays the image on the first physical display device according to the second display data.

[0059] In some feasible embodiments, after receiving the second display data, the second domain system can first determine the display device to which the second display data is to be displayed. The second display data can be display data sent to the second domain system by an application.

[0060] If the second display data needs to be displayed on the second physical display device, the second domain system can directly display the screen on the second physical display device according to the second display data to display the screen corresponding to the second display data.

[0061] If the second display data needs to be displayed on the first physical display device, the second domain system can send the second display data to the first domain system through a virtualization channel. After receiving the second display data, the first domain system can display the image on the first physical display device according to the second display data, so as to display the image corresponding to the second display data on the first physical display device.

[0062] If the second display data needs to be displayed on both the first and second physical display devices, the second domain system can directly display the image on the second physical display device according to the second display data to display the image corresponding to the second display data; and it can also send the second display data to the first domain system through a virtualization channel. After receiving the second display data, the first domain system can display the image on the first physical display device according to the second display data to display the image corresponding to the second display data on the first physical display device.

[0063] In one embodiment of the present invention, the second domain system is used to send the second display data to the first domain system for display through a virtualization channel when it is determined that the second display data belongs to a virtualization device; and to display the image on the second physical display device according to the second display data when it is determined that the second display data does not belong to a virtualization device.

[0064] In some feasible embodiments, the first physical display device can be a virtualized device for the second domain system; when the second domain system determines that the second display data belongs to the data to be displayed by the virtualized device, it can send the second display data to the first domain system for display through the virtualization channel.

[0065] Conversely, if the second domain system determines that the second display data does not belong to the data that the virtualization device is going to display, then the screen can be displayed directly on the second physical display device based on the second display data.

[0066] In one embodiment of the present invention, a second domain system is used to display a screen on a second physical display device according to third display data; the second display data and the third display data are different parts of the same display data.

[0067] In some feasible embodiments, the first domain system and the second domain system can synchronously display different parts of a pattern, for example, cooperating to display a power-on pattern; for example, when the second domain system sends the second display data to the first domain system for display, it can display the image on the second physical display device based on the third display data, which is a different part of the same display data as the second display data, that is, display the image corresponding to the third display data on the second physical display device; thus, a part of the content of a pattern can be displayed on the first physical display device, and another part of the content of the pattern can be displayed on the second physical display device.

[0068] In some feasible embodiments, the first display data and the second display data can be the same display data, different display data, or different parts of the same display data; through bidirectional synchronization, the boot animation can be displayed synchronously on all display devices, and an animation can be split into several parts and displayed synchronously on multiple display devices.

[0069] In this embodiment of the invention, a first domain system displays a screen on a first physical display device based on first display data, and / or sends the first display data to a second domain system via a virtualization channel. The second domain system then displays a screen on the second physical display device based on the first display data. The first domain system receives second display data sent by the second domain system via the virtualization channel and displays a screen on the first physical display device based on the second display data. This embodiment of the invention enables bidirectional synchronous screen display across different systems, enhancing the product's appeal and thus better meeting the increasing demands of users.

[0070] Reference Figure 2 The diagram illustrates a flowchart of another cross-system screen display method according to an embodiment of the present invention, which may include the following steps:

[0071] Step 201: The first domain system displays the image on the first physical display device according to the first display data, and / or sends the first display data to the second domain system through a virtualization channel.

[0072] Multiple virtualization channels based on the virtio protocol can be established between the first domain system and the second domain system to meet the display device requirements of different services.

[0073] In some feasible embodiments, in order to achieve cross-system screen display, after receiving the first display data, the first domain system can first determine the display device to which the first display data is to be displayed.

[0074] If the first display data needs to be displayed on the first physical display device, the first domain system can directly display the screen on the first physical display device according to the first display data to display the screen corresponding to the first display data.

[0075] If the first display data needs to be displayed on the second physical display device, the first domain system can send the first display data to the second domain system through a virtualization channel; after receiving the first display data, the second domain system can display the image on the second physical display device according to the first display data, so as to display the image corresponding to the first display data on the second physical display device.

[0076] If the first display data needs to be displayed on both a first physical display device and a second physical display device, the first domain system can directly display the image on the first physical display device based on the first display data to display the image corresponding to the first display data; and it can also send the first display data to the second domain system through a virtualization channel. After receiving the first display data, the second domain system can display the image on the second physical display device based on the first display data to display the image corresponding to the first display data on the second physical display device.

[0077] Step 202: The first domain system receives the second display data sent by the second domain system through the virtualization channel.

[0078] In some feasible embodiments, after receiving the second display data, the second domain system can first determine the display device to which the second display data is to be displayed.

[0079] If the second display data needs to be displayed on the second physical display device, the second domain system can directly display the screen on the second physical display device according to the second display data to display the screen corresponding to the second display data.

[0080] If the second display data needs to be displayed on the first physical display device, the second domain system can send the second display data to the first domain system through a virtualization channel. After receiving the second display data, the first domain system can display the image on the first physical display device according to the second display data, so as to display the image corresponding to the second display data on the first physical display device.

[0081] If the second display data needs to be displayed on both the first and second physical display devices, the second domain system can directly display the image on the second physical display device according to the second display data to display the image corresponding to the second display data; and it can also send the second display data to the first domain system through a virtualization channel. After receiving the second display data, the first domain system can display the image on the first physical display device according to the second display data to display the image corresponding to the second display data on the first physical display device.

[0082] Step 203: Determine the first layer of the second display data on the first physical display device.

[0083] In some feasible embodiments, since cross-system display may involve multiple screens, in order to effectively manage these multiple screens, a first layer of the second display data on the first physical display device can be determined before displaying the second display data on the first physical display device. For example, virtualization channels may include multiple channels, and layers can be associated with virtualization channels.

[0084] After receiving the second display data, the first domain system can first determine its corresponding virtualization channel; then determine the first layer corresponding to that virtualization channel.

[0085] Step 204: Display the second display data on the first layer of the first physical display device.

[0086] After determining the first layer, the first domain system can display the second display data on the first layer of the first physical display device; in addition, for other display data, the first domain system can also display them on the corresponding layer of the first physical display device.

[0087] In this embodiment of the invention, a first domain system displays the image on a first physical display device based on first display data, and / or sends the first display data to a second domain system via a virtualization channel; the first domain system receives second display data sent by the second domain system via the virtualization channel; determines a first layer of the second display data on the first physical display device; and displays the second display data on the first layer of the first physical display device. Through this embodiment of the invention, bidirectional synchronous image display between different systems can be achieved, enhancing the product's appeal and thus better meeting the increasing demands of users.

[0088] Reference Figure 3 The diagram illustrates a flowchart of another cross-system screen display method according to an embodiment of the present invention, which may include the following steps:

[0089] Step 301: The first physical display device includes multiple display areas. The first domain system splits the first display data to obtain first sub-display data and second sub-display data.

[0090] In some feasible embodiments, the first physical display device can be a large physical screen that can display multiple independent images; the first display data can be the data to be displayed corresponding to the large physical screen, which may include first sub-display data and second sub-display data. The first sub-display data and the second sub-display data can be patterns that are related to each other, or they can be patterns that are not related to each other, and the embodiments of the present invention do not limit this.

[0091] After obtaining the first display data, the first domain system can first split the first display data to obtain the first sub-display data and the second sub-display data.

[0092] Step 302: Determine a display area on the first physical display device corresponding to the first sub-display data, and a display area on the first physical display device corresponding to the second sub-display data.

[0093] After obtaining the first sub-display data and the second sub-display data, the first domain system can determine that the first sub-display data corresponds to a display area on the first physical display device, and the second sub-display data corresponds to a display area on the first physical display device.

[0094] Step 303: Display images on different display areas of the first physical display device according to the first sub-display data and the second sub-display data.

[0095] After determining that the first sub-display data corresponds to a display area on the first physical display device, and the second sub-display data corresponds to a display area on the first physical display device, the first domain system can display images on different display areas of the first physical display device according to the first sub-display data and the second sub-display data, respectively. For example, the pattern corresponding to the first sub-display data can be displayed in one display area of ​​the first physical display device, and the pattern corresponding to the second sub-display data can be displayed in another display area of ​​the first physical display device. This embodiment of the invention does not limit this.

[0096] Step 304: Send the first display data to the second domain system through the virtualization channel.

[0097] If the first display data needs to be displayed on the second physical display device, the first domain system can send the first display data to the second domain system through a virtualization channel; after receiving the first display data, the second domain system can display the image on the second physical display device according to the first display data, so as to display the image corresponding to the first display data on the second physical display device.

[0098] Step 305: The first domain system receives the second display data sent by the second domain system through the virtualization channel.

[0099] In some feasible embodiments, after receiving the second display data, the second domain system can first determine the display device to which the second display data is to be displayed.

[0100] If the second display data needs to be displayed on the second physical display device, the second domain system can directly display the screen on the second physical display device according to the second display data to display the screen corresponding to the second display data.

[0101] If the second display data needs to be displayed on the first physical display device, the second domain system can send the second display data to the first domain system through a virtualization channel.

[0102] Step 306: Determine the first layer of the second display data on the first physical display device.

[0103] After receiving the second display data, the first domain system can first determine its corresponding virtualization channel; then determine the first layer corresponding to that virtualization channel.

[0104] Step 307: Display the second display data on the first layer of the first physical display device.

[0105] After determining the first layer, the first domain system can display the second display data on the first layer of the first physical display device; in addition, for other display data, the first domain system can also display them on the corresponding layer of the first physical display device.

[0106] In one embodiment of the present invention, a plurality of first physical display devices and a plurality of virtualization channels are included, and there is a correspondence between the first physical display devices and the virtualization channels. When displaying the image on the first physical display device according to the second display data, this can be achieved through the following steps:

[0107] Determine the target virtualization channel corresponding to the second display data; based on the target virtualization channel corresponding to the second display data, determine the target first physical display device, and display the second display data on the target first physical display device.

[0108] In some feasible embodiments, the first physical display device may include multiple devices, and the virtualization channel may include multiple channels. There is a correspondence between the first physical display device and the virtualization channel, and this correspondence can be one-to-one. This embodiment of the present invention does not limit this.

[0109] Based on this, after obtaining the second display data, the first domain system can determine the target virtualization channel corresponding to the second display data; then, it can determine the first physical display device corresponding to the target virtualization channel (hereinafter referred to as the target first physical display device).

[0110] After identifying the target first physical display device, the first domain system can display the second display data on the target first physical display device.

[0111] In one embodiment of the present invention, the above method may further include the following steps:

[0112] Receive first touch data and determine the target application corresponding to the first touch data; send the first touch data to the target application, which is used to control the display of the target physical display device corresponding to the first touch data according to the first touch data.

[0113] In some feasible embodiments, cross-screen operation can also be achieved for touch data; for example, after receiving the first touch data, the first domain system can determine the source of the first touch data and determine the target application corresponding to the source.

[0114] Then, the first touch data can be sent to the target application so that the target application can control the target physical display device corresponding to the first touch data based on the first touch data; the target physical display device is the display device controlled by the first touch data.

[0115] For example, the first domain system can directly send the first touch data to the target application; or it can first pass it through to the second domain system, and then the second domain system sends it to the target application. This embodiment of the invention does not limit this.

[0116] For example, the first domain system can also send the display data corresponding to the source of the first touch data to the target application; the target application can perform display control on the target physical display device corresponding to the first touch data based on the display data and the first touch data.

[0117] In one embodiment of the present invention, the target application can be determined in the following manner:

[0118] Determine the second layer of the first touch data on the first physical display device; based on the second layer, determine the target application corresponding to the first touch data.

[0119] For example, the source of the first touch data can be determined as its layer on the first physical display device (hereinafter referred to as the second layer).

[0120] In this embodiment of the invention, different layers can correspond to different applications; based on this, the application corresponding to the second layer can be determined and used as the target application corresponding to the first touch data.

[0121] In this embodiment of the invention, the first physical display device includes multiple display areas. A first domain system splits the first display data to obtain first sub-display data and second sub-display data. It determines that the first sub-display data corresponds to a display area on the first physical display device, and the second sub-display data corresponds to a display area on the first physical display device. Based on the first and second sub-display data, the system displays images on different display areas of the first physical display device. The first display data is sent to a second domain system via a virtualization channel. The first domain system receives the second display data sent by the second domain system via the virtualization channel. The system determines a first layer of the second display data on the first physical display device. The second display data is then displayed on the first layer of the first physical display device. Through this embodiment of the invention, bidirectional synchronous image display between different systems can be achieved, enhancing the product's appeal and thus better meeting the increasing demands of users.

[0122] The following, combined with Figure 4 , Figure 5 and Figure 6 The above-mentioned cross-system screen display method is further explained as follows:

[0123] To simplify the discussion, the central control system is divided into two domains (in reality, there can be three or more): the cockpit domain IVI (called GuestOS) and the instrument cluster domain IC (also called HostOS). Each domain focuses on different functionalities.

[0124] like Figure 4 The diagram shows a schematic representation of a central control system according to an embodiment of the present invention:

[0125] Note:

[0126] 1. irq (Interrupt Request) and hycall (Hypervisor Call): The communication mechanism between the hypervisor and HostOs and GuestOs. HostOs and GuestOs send data to the hypervisor via hycall, and the hypervisor notifies HostOs and GuestOs to read the data via irq.

[0127] 2. DRM (Direct Rendering Manager) driver: The display driver provides an interface to LIBDRM and directly drives the hardware device (i.e., the display device) to display the image. The hostOS side driver is a conventional driver, while the guestOS side uses a macro control compatible virtualization interface.

[0128] 3. LIBDRM (Direct Rendering Manager Library): A Linux system display screen call library file interface that provides an interface for upper-layer application code to call the underlying driver code.

[0129] 4. Input driver: The touchscreen driver provides an interface and device node to LIBINPUT to read data; it directly drives the touchscreen hardware to obtain touch coordinates. The two systems function identically. Touch data originates from the underlying hardware, is sent upwards via the input driver, and finally reaches the app.

[0130] 5. LIBINPUT (Input Device Handling Library): The input device library file of the Linux system input subsystem, which provides an interface for upper-layer application code to call the underlying driver code.

[0131] 6. GFX: Graphics Framework eXtension, a 2D / 3D graphics rendering library that provides graphics processing interfaces. It includes the Weston module interface.

[0132] 7. EVENT SUBSYSTEM: Event message processing logic in the Linux system's input subsystem.

[0133] 8. virtio-input: Virtualized input event-driven code. On the HostOS side, it provides an interface to connect to GFX (specifically the Weston module) to parse touch data, converting it into a format identical to the touch driver, and forwarding it across systems to the GuestOS-side virtio-input. On the GuestOS side, the virtio-input driver creates a virtualized device node to receive data from the HostOS side and stores the data in the device node's cache for Weston to read the touch data.

[0134] 9. virtio-display: HostOS-side display data forwarding module. Sending stream: Display data originates from the APP. After the Weston module in GFX determines whether data needs to be sent to the GuestOS side, it is forwarded to the GuestOS-side virtio-gpu driver via the virtio-display virtualization interface. Receiving stream: virtio-display can receive display data sent from the GuestOS-side virtio-gpu driver, processing it frame by frame. Depending on the rendering method supported by the SoC, it selects either software rendering or hardware rendering. Ultimately, all data is sent to the local DRM driver and then to the display device for display.

[0135] 10. virtio-gpu driver: GuestOS-side virtualized display module interface. Receive stream: Used to receive data sent from the HostOS-side virtio-display. It typically processes data frame by frame, checking if the destination device exists. If it does, it forwards the data to the GuestOS-side DRM driver, and then displays it on the hardware screen. Send stream: The virtio-gpu driver can receive data sent from the local system app to the GFX. Upon receiving data from the GFX interface, it determines (Weston processes according to the configuration file) the display device to which the data belongs. If it's a virtualized device, it forwards it directly to the HostOS virtio-display module. If the display device is not a virtualized device, it sends the data directly to the local DRM driver, and then to the display device for display.

[0136] Figure 4 The solid line represents the path for display data transmission, while the dashed line represents the path for touch data transmission.

[0137] Backend driver implementation: This part resides in the HostOS and its main function is to build the system HWM (Hardware Monitor, display fusion module) for accessing display device drivers. It obtains raw data (display data, touch data) through the virtio-display and virtio-input channels and sends it to the Weston module on the OS side. The entire virtio-display, virtio-input, and virtio-gpu module works together to form an HWM module.

[0138] 1) The display fusion module reads the HostOS virtualized display device configuration file, which is used to configure the number and parameters (such as hardware interface name and screen resolution) of each output channel and input channel of the IC-side display device. This configuration file determines which display device each output display of the IC side should be sent to, and determines the window level (i.e., layer) of each output display of the IC side on the display device.

[0139] 2) The virtio-gpu driver receives display data from the IVI side and sends it to the DRM driver or Weston module on the OS side (located in GFX).

[0140] 3) Obtain the touch parameters of the display device on the IC side through the libinput library. Compare the touch parameters with the display device parameters to bind the physical touch screen and the display device together. Establish a one-to-one correspondence. If the parameters meet the expectations, place the display device and the physical touch screen in an array, assign values ​​to the corresponding structures in the array, and access the corresponding display screen and touch screen through the array index.

[0141] 4) The HWM determines the source of the touch data and distributes the data to the input channels (i.e., virtualized channels, which are used for bidirectional interactive display data) corresponding to different output channels (i.e., virtualized channels, which are used for bidirectional interactive touch data) on the IVI side. Typically, the output channels on the IVI side correspond to a screen display buffer (virtio drm), while the input channels correspond to the touch data.

[0142] Typically, the output channel on the IVI side corresponds to the display buffer of a display device, while the input channel corresponds to touch data. After the physical touchscreen driver loads normally, it creates the ` / dev / input / eventX` node, where X represents a numerical value. The first touchscreen starts from 0 and increments sequentially. By reading the ` / dev / input / event0` node, parameters such as the touchscreen hardware name, resolution, and ID can be obtained. Between the touchscreen driver and the display driver, the one loaded first is assigned to the array mentioned in 3), while the one loaded later is grouped by comparing the ID, resolution, and other parameters of existing devices in the array.

[0143] HWM typically doesn't acquire the raw touchscreen data, but rather the touch data of the focus layer after processing by the HostOS's weston module. This data format differs from the [type code value] format reported by the physical screen. After acquiring the touch data, it sends the data to the designated OS system app based on the prior mapping between the touchscreen and the display screen.

[0144] 5) Implement the separation of display data and touch data. When two independent screens (instrument screen and IVI screen) are displayed through a physical large screen, the display data (or touch data) needs to be separated into two. In HWM, the origin of the separated data is reset and matched with the display area. The data is then forwarded to the app of the specified domain system through the virtio-input and virtio-gpu interfaces.

[0145] 6) Provides partial interface strategies, through which layer properties can be set, such as the `output windowvisible` property, which can enable and disable layers for specified channels. If two systems need to display their application's images simultaneously on a display device, they need to be differentiated by priority. This interface can be called to disable a layer, or they can be displayed in parallel, provided that the boundary of one image does not completely cover the boundary of another image.

[0146] Front-end driver implementation: This part of the code corresponds to the back-end driver and is divided into two parts: display and touch.

[0147] The display section includes a virtio-gpu, used to send display data to the backend driver. The display data stream on each output of the IVI is fused by the IVI's Weston and then sent across the system to the HWM on the IC side via DMABUF zero-copy. The HWM then determines which output on the IC should be sent to (subsequent outputs are output channels). The HWM then uses Weston's capabilities to send the different output data from the IVI to the corresponding output on the IC.

[0148] The touch component includes virtio-input, which is used to send touch data from the IC side to the corresponding app on the display device.

[0149] Given the differences between high and low configurations in actual vehicle models, some display devices will pass through to the IVI side. In order to enable operation of each screen, the multi-domain system has made some customizations to the virtio-gpu, such as compatibility with the DRM driver interface. This allows the display data from the IVI side to be forwarded to the IC side, and also allows the display data from the IC side to be received and forwarded to the local DRM driver for direct display.

[0150] The driver implementation mainly consists of the following steps:

[0151] 1) The virtio-gpu driver recognizes the Weston configuration file on the GustOS side. The main function of this configuration file is to instruct the virtio-gpu driver to create several virtio queues, each corresponding to one output channel. The number of output channels can be flexibly configured by modifying this file. This file also records parameters such as the name and resolution of the physical screen corresponding to each channel, allowing two output channels to specify the same physical screen.

[0152] The input channel is used to transmit touch data. It uses a separate buffer in a queue, and `virtio-input` is used to create the input channel. `virtio-input` calls the virtio queue API to create the buffer. The number of output channels can be flexibly configured by modifying this file. This file also records the name, resolution, and other parameters of the physical screen corresponding to each channel, allowing two output channels to be assigned to the same display device.

[0153] 2) The virtio-gpu driver mainly handles the reception and forwarding of display data on this side. It receives display data from the Weston module through the libdrm library and forwards the data to the IVI side through the virtio-queue memory and queue.

[0154] When a display device passes through to the IVI side, the GuestOS-side virtio-gpu driver receives the display data from the IC side and forwards it to the GuestOS-side drm driver. Other main tasks include requesting display buffers and mapping them to the application layer. The virtio-gpu driver provides an ioctl interface for the application layer to call, used to set resolution, refresh rate, power status, switch display frames, and composite multi-layer data.

[0155] The Weston module reads the Weston configuration of this system and sends the device parameters to the virtio-gpu driver. It mainly matches the display output channels to be created on the IC side with the virtio-queue, and each output is merged into a layer and sent to the IC side.

[0156] 3) Create a virtio-input driver device node ( / dev / virtio-input0). This device node is used to receive touch data sent from the HWM on the IC side, forward it to the Weston module, and then the Weston module reads the configuration file, associates the touch screen with the display device, and then feeds back to the specified app.

[0157] 4) For devices that pass through to the IVI side, it is compatible with the display / touch framework of a single-core OS. The virtio-gpu driver code on the IVI side has backward compatibility and retains the interface for calling the DRM driver. It can receive display data from the IC side and send it directly to the DRM driver to drive the display device to display the screen.

[0158] The implementation principle involves configuring the display device's ID in the configuration file. This ID consists of two parts: a major device number and a minor device number. The major device number is typically the first screen on this system, and numbers increment sequentially. The minor device number represents the display device's order among all display devices in a multi-domain system. For example... Figure 3 As shown, when displaying the system startup animation, to display the entire fish swimming animation, it is necessary to display each screen according to the minor device number and block the major device number.

[0159] like Figure 5 The four display devices are the instrument cluster screen, the IVI screen, the secondary instrument cluster screen, and the passenger-side screen. The instrument cluster screen and the IVI screen can be combined into one large screen, each displaying two images, located on the IC side. The dashed lines represent the transmission paths for touch data, and the solid lines represent the transmission paths for display data.

[0160] From the IC side, there are only 4 outputs (1, 2, 3, and 4 under DRM in the IC) and 4 inputs (1, 2, 3, and 4 under InputSystem in the IC).

[0161] For the IVI side, the HWM virtualization solution virtualizes 5 outputs (1, 2, 3, 4, and 5 under VRITIO DRM in IVI) and 5 inputs (1, 2, 3, 4, and 5 under Input System in IVI) through configuration files; that is, the virtualization channels mentioned in the aforementioned embodiments.

[0162] For Westone on the IC, the output and input devices on the IC correspond to the instrument panel screen, IVI screen, secondary instrument panel screen, and passenger screen in sequence.

[0163] For Weston's IVI, the IVI output and input correspond to the window layers on different display devices. Output1 / Input1 and Output5 / Input5 correspond to the IVI-1 and IVI-5 layers on the instrument screen, respectively. Other output / input channels correspond one-to-one according to their sequence numbers.

[0164] Display data stream: The display data stream on each output of the IVI, after being fused by the IVI's Weston, is sent across cores to the HWM via DMABUF zero-copy. The HWM then determines which output on the IC should be sent to, and uses Weston's capabilities to send the different output data from the IVI to the corresponding output on the IC. For example... Figure 5 As shown: both output1 and output5 are sent to the instrument screen by HWM, and HWM initializes windows of different levels for them to meet the needs of a sandwich-like scenario (ivi-ic-ivi).

[0165] Similarly, for other screens, HWM has the ability to send data bidirectionally to meet the needs of device pass-through scenarios.

[0166] Touch Data Flow: Assuming the instrument's physical screen receives touch data, it sends it to Weston via the input system. Weston in the IC, by judging the current display client layers, sends the coordinate data to the top-level window that needs the coordinates. If any window in the Weston module captures the coordinates, it will transmit the coordinates to the corresponding input in the IVI via the HWM. In this assumption, if Window1, virtualized by the HWM, receives the coordinate data, it will pass the corresponding touch data to Input1 in the IVI. Since Weston in the IVI links Input1 and Output1 together, Output1 in the IVI successfully receives the touch data.

[0167] If touch data from Window5 on the instrument panel screen is required, the strategy provider needs to actively hide the instrument panel within the IC and call the HWM interface to hide the Window1 layer. In real-world scenarios, layers are overlaid, rather than simply hiding the instrument panel within the IC. For example, AR / MR displays are shown within a square in the center of the screen, and in this case, the instrument panel layer is not hidden.

[0168] The same applies to other screens.

[0169] Each output from the IVI is merged into a single layer and sent to the IC side.

[0170] The output and input are in one-to-one correspondence, satisfying the requirement that the display and touch events are in one-to-one correspondence.

[0171] Both IVIoutput1 and output5 are sent to the IC, with one window level higher than the other.

[0172] like Figure 6The diagram illustrates a scenario where the boot animation is output from five channels on the IVI side: the boot animation can be four different screens, or four parts of one large screen. A single large screen can also achieve the effect of synchronously displaying the boot animation on all screens. For example... Figure 6 As shown, the startup animation can show a fish swimming continuously across four display devices (i.e., the instrument panel screen, the IVI screen, the secondary instrument panel screen, and the passenger-side screen).

[0173] HWM sets the window type from IVI output1 to a higher level than that of the IC instrument application, while setting the other outputs to a general level. Since outputs 1-4 are all continuous, a large buffer for the continuous coordinate system can be requested without any modifications to Weston, and then HWM sends it to different display devices.

[0174] Since the actual touch data from the display device is captured by the HWM and then sent to the corresponding output input, the touch data from output1 is sent to input1, while the touch data from output5 is sent to input5 by the HWM. Because a large buffer covering the entire screen is allocated and touch data is configured, cross-screen dragging and copying become possible; these are all operations on the display buffer. The display and touch operations of each output are independent and decoupled. Therefore, there is no special processing logic for the IVI Weston.

[0175] After the boot animation, hide the first layer of the animation (i.e., Figure 6 (The fish tail in the middle), the instrument screen can display the content of the instrument application. If the instrument interface has reserved AR / MR-5 space at this time, the instrument application + AR / MR scene can be realized. This screen is the sandwich scene.

[0176] This invention achieves new highlights in the cockpit system by virtualizing the kernel display subsystem. It combines the IVI-side virtio-gpu driver and HWM module to enable diverse display functions, including cross-system multi-screen synchronous boot animation display and the ability to overlay multiple windows on any screen. The fusion of touch data enables multi-screen interaction within the cockpit, allowing for drag-and-drop and copying across any interface. While maintaining compatibility with the single-core OS display / touch framework, it also solves diverse display scenarios across cores and screens. This reduces hardware investment, lowers system failure rates, and the HWM virtualization fusion solution meets current business needs and possesses excellent scalability.

[0177] In this embodiment of the invention, multiple virtualization channels based on the virtio protocol are established between multiple systems to meet the display device requirements of different services, while reducing the development difficulty of the display driver on the GuestOS side, making it no different from normal display driver development. For example, the display service in the basic services of the GuestOS system is needed by both OSes, and there are situations where both need to access the same physical display device, but there is only one hardware interface, requiring cross-system communication. In addition, in this embodiment of the invention, multiple apps can access one or more display devices in parallel, projecting the image onto one screen or different layers of multiple screens. Through flexible software configuration, a multi-layer overlay parallel display effect on a single screen can be achieved, creating a sandwich scene.

[0178] This invention integrates touchscreen data and display screen data for bidirectional transmission, enabling screen operation and cross-screen interaction, allowing users to freely drag and drop a display image between two screens.

[0179] This invention can save hardware costs and improve system stability. The solution supports large screens (also called long screens). This type of screen can be simply understood as combining two physical screens into one larger physical screen. Because one physical device is eliminated, the system failure rate is reduced, the cost is reduced, and the user experience is improved after the screen becomes larger. It is used as two independent screens, but the hardware is a single device. The splitting and merging of data is completed by virtio-input and virtio-display.

[0180] The embodiments of the present invention have good compatibility. When a display device is passed through to the IVI domain, no changes to the driver file are required, and the display device on the IVI domain side can be normally compatible.

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

[0182] Reference Figure 7This diagram illustrates a cross-system screen display device according to an embodiment of the present invention, applied to a central control system. The central control system includes a first domain system and a second domain system. The first domain system is equipped with at least one first physical display device, and the second domain system is equipped with at least one second physical display device. A virtualization channel is provided between the first domain system and the second domain system. A display fusion module is provided in the first domain system. The display fusion module is used to receive display data and / or touch data sent by the second domain system through the virtualization channel, and to send display data and / or touch data to the second domain system through the virtualization channel. The device may include the following modules:

[0183] The display module 701 is used to display the image on the first physical display device according to the first display data, and / or send the first display data to the second domain system through a virtualization channel, wherein the second domain system displays the image on the second physical display device according to the first display data.

[0184] The receiving and display module 702 is used to receive the second display data sent by the second domain system through the virtualization channel, and to display the image on the first physical display device according to the second display data.

[0185] In one embodiment of the present invention, a receiving display module 702 is used to determine a first layer of second display data on a first physical display device; and to display the second display data on the first layer of the first physical display device.

[0186] In one embodiment of the present invention, the apparatus further includes:

[0187] The layer display module is used to determine the priority of the display data corresponding to each layer of the first physical display device; to enable the layer corresponding to the display data with the highest priority, and to disable other layers.

[0188] In one embodiment of the present invention, a first physical display device includes multiple virtualization channels, and a correspondence exists between the first physical display device and the virtualization channel; a receiving display module 702 is used to determine the target virtualization channel corresponding to the second display data; based on the target virtualization channel corresponding to the second display data, a target first physical display device is determined, and the second display data is displayed on the target first physical display device.

[0189] In one embodiment of the present invention, the apparatus further includes:

[0190] The touch module is used to receive first touch data and determine the target application corresponding to the first touch data; send the first touch data to the target application, and the target application is used to control the display of the target physical display device corresponding to the first touch data according to the first touch data.

[0191] In one embodiment of the present invention, a touch module is used to determine a second layer of first touch data on a first physical display device; and to determine a target application corresponding to the first touch data based on the second layer.

[0192] In one embodiment of the present invention, the first physical display device includes multiple display areas. A display sending module 701 is used to split the first display data to obtain first sub-display data and second sub-display data; determine that the first sub-display data corresponds to a display area on the first physical display device, and that the second sub-display data corresponds to a display area on the first physical display device; and display images on different display areas on the first physical display device according to the first sub-display data and the second sub-display data.

[0193] In one embodiment of the present invention, the second domain system is used to send the second display data to the first domain system for display through a virtualization channel when it is determined that the second display data belongs to a virtualization device; and to display the image on the second physical display device according to the second display data when it is determined that the second display data does not belong to a virtualization device.

[0194] In one embodiment of the present invention, a second domain system is used to display a screen on a second physical display device according to third display data; the second display data and the third display data are different parts of the same display data.

[0195] In this embodiment of the invention, a first domain system displays a screen on a first physical display device based on first display data, and / or sends the first display data to a second domain system via a virtualization channel. The second domain system then displays a screen on the second physical display device based on the first display data. The first domain system receives second display data sent by the second domain system via the virtualization channel and displays a screen on the first physical display device based on the second display data. This embodiment of the invention enables bidirectional synchronous screen display across different systems, enhancing the product's appeal and thus better meeting the increasing demands of users.

[0196] This invention also provides an electronic device that may include a processor, a memory, and a computer program stored in the memory and capable of running on the processor. When the computer program is executed by the processor, it implements the cross-system screen display method described above.

[0197] This invention also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the cross-system screen display method described above.

[0198] As the apparatus embodiment is basically similar to the method embodiment, it is described in a relatively simple manner. For relevant details, please refer to the description of the method embodiment.

[0199] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. The same or similar parts between the various embodiments can be referred to each other.

[0200] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, apparatus, or computer program products. Therefore, embodiments of the present invention can take the form of entirely hardware embodiments, entirely software embodiments, or embodiments combining software and hardware aspects. Furthermore, embodiments of the present invention can take the form of computer program products implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0201] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing terminal device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal device, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0202] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing terminal device to operate in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0203] These computer program instructions can also be loaded onto a computer or other programmable data processing terminal equipment, causing a series of operational steps to be performed on the computer or other programmable terminal equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable terminal equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0204] Although preferred embodiments of the present invention have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of the embodiments of the present invention.

[0205] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or terminal device that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or terminal device. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or terminal device that includes said element.

[0206] The foregoing has provided a detailed description of a cross-system screen display method, apparatus, device, and medium. Specific examples have been used to illustrate the principles and implementation methods of the present invention. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of the present invention. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of the present invention. Therefore, the content of this specification should not be construed as a limitation of the present invention.

Claims

1. A cross-system screen display method, characterized in that, The method is applied to a central control system, which includes a first domain system and a second domain system. The first domain system has at least one first physical display device, and the second domain system has at least one second physical display device. A virtualization channel is provided between the first domain system and the second domain system. The first domain system has a display fusion module, which is used to receive display data and / or touch data sent by the second domain system through the virtualization channel, and to send display data and / or touch data to the second domain system through the virtualization channel. The method includes: The first domain system displays the image on the first physical display device according to the first display data, and / or sends the first display data to the second domain system through the virtualization channel, and the second domain system displays the image on the second physical display device according to the first display data; The first domain system receives the second display data sent by the second domain system through the virtualization channel, and displays the image on the first physical display device according to the second display data.

2. The method according to claim 1, characterized in that, The step of displaying the image on the first physical display device according to the second display data includes: Determine the first layer of the second display data on the first physical display device; The second display data is displayed on the first layer of the first physical display device.

3. The method according to claim 2, characterized in that, The method further includes: Determine the priority of the display data corresponding to each layer of the first physical display device; Enable the layer corresponding to the highest priority data display and disable other layers.

4. The method according to claim 1, characterized in that, The first physical display device includes multiple devices, and the virtualization channel includes multiple channels; there is a correspondence between the first physical display device and the virtualization channel; the step of displaying the image on the first physical display device according to the second display data includes: Determine the target virtualization channel corresponding to the second displayed data; Based on the target virtualization channel corresponding to the second display data, a target first physical display device is determined, and the second display data is displayed on the target first physical display device.

5. The method according to claim 1, characterized in that, The method further includes: Receive the first touch data and determine the target application corresponding to the first touch data; The first touch data is sent to the target application, which is used to control the display of the target physical display device corresponding to the first touch data based on the first touch data.

6. The method according to claim 5, characterized in that, Determining the target application corresponding to the first touch data includes: Determine the second layer of the first touch data on the first physical display device; Based on the second layer, determine the target application corresponding to the first touch data.

7. The method according to claim 1, characterized in that, The first physical display device includes multiple display areas, and the step of displaying the image on the first physical display device according to the first display data includes: The first display data is split to obtain a first sub-display data and a second sub-display data; The first sub-display data corresponds to a display area on the first physical display device, and the second sub-display data corresponds to a display area on the first physical display device; Based on the first sub-display data and the second sub-display data, the screen is displayed in different display areas on the first physical display device.

8. The method according to claim 1, characterized in that, The second domain system is used to send the second display data to the first domain system for display through the virtualization channel when it is determined that the second display data belongs to a virtualization device; and to display the image on the second physical display device according to the second display data when it is determined that the second display data does not belong to a virtualization device.

9. The method according to claim 1, characterized in that, The second domain system is used to display a screen on the second physical display device according to the third display data; the second display data and the third display data are different parts of the same display data.

10. A cross-system screen display device, characterized in that, An application is made in a central control system, the central control system comprising a first domain system and a second domain system. The first domain system is equipped with at least one first physical display device, and the second domain system is equipped with at least one second physical display device. A virtualization channel is provided between the first domain system and the second domain system. The first domain system is equipped with a display fusion module, which is used to receive display data and / or touch data sent by the second domain system through the virtualization channel, and to send display data and / or touch data to the second domain system through the virtualization channel. The device includes: A display module is configured to display a screen on the first physical display device according to the first display data, and / or send the first display data to the second domain system through the virtualization channel, wherein the second domain system displays a screen on the second physical display device according to the first display data; The receiving and display module is used to receive second display data sent by the second domain system through the virtualization channel, and to display the image on the first physical display device according to the second display data.

11. An electronic device, characterized in that, It includes a processor, a memory, and a computer program stored in the memory and capable of running on the processor, wherein the computer program, when executed by the processor, implements the cross-system screen display method as described in any one of claims 1 to 9.

12. A computer-readable storage medium, characterized in that, A computer program is stored on the computer-readable storage medium, which, when executed by a processor, implements the cross-system screen display method as described in any one of claims 1 to 9.

Images