Vehicle-mounted operating system display method and device based on container, equipment and medium

Abstract

A container-based vehicle-mounted operating system display method, apparatus and device, and a medium, relating to the field of vehicle-mounted display, comprising: when a display server deployed on a host receives to-be-displayed layer data sent by a target display client deployed on a target operating system container, performing layer synthesis on the to-be-displayed layer data, generating target composite layer data; determining a first display port corresponding to the target operating system container based on a mapping relationship between the operating system container and the display port; and transmitting the target composite layer data to a first display port for display. According to the method and the device, the operation system container is not responsible for layer merging and only provides the display client, so that the purpose of container lightweight is achieved; and the display server sides in all the containers are uniformly combined to one display server side on the host machine, so that the overall process number of the system is reduced, the resource consumption and the memory demand are reduced, and the overall performance of the system is improved.

Description

Technical Field

[0001] The present application relates to the field of vehicle-mounted display technology, and in particular to a container-based vehicle-mounted operating system display method, device, equipment and medium. Background Art

[0002] In the evolution of in-vehicle operating systems, multi-system and cross-system data fusion is the current mainstream solution. Taking the cockpit as an example, it usually provides an instrument system that displays vehicle body signals (such as vehicle speed, gear position, etc.), a central control system that provides customers with entertainment information functions, and a co-pilot or rear-seat system that provides customers with special customized experiences (such as 3A gaming experience), etc.

[0003] The above-mentioned systems can run on different SOCs (System on Chip) (including SOC hard segmentation solutions), or they can run on the same SOC based on virtualization (such as Hypervisor virtual machine) or containers; among them, each system provides graphic display of the instrument, central control, and rear row respectively, and there may be a need for data fusion between systems, such as displaying the navigation data of the central control on the instrument.

[0004] Multiple systems running on different SOCs can control their own display devices for display respectively, and data fusion between systems can be transmitted through Ethernet and other methods. Although it has the advantage of simple system architecture, the hardware cost is high. The virtualization and container-based approach allows all systems to run on the same SOC. Although it can reduce hardware costs, the Hypervisor virtual machine and container need to use their internal complete graphics display services to implement functions such as window management and layer synthesis. That is, each container needs to deploy a client for processing tasks such as layer synthesis and its corresponding display server for display, resulting in high resource consumption and memory requirements. It can be seen that how to reduce the resource consumption and memory requirements of the vehicle operating system display is an urgent problem that needs to be solved. Summary of the invention

[0005] The present application provides a container-based in-vehicle operating system display method, device, equipment and medium, which can effectively reduce the resource consumption and memory requirements of the in-vehicle operating system display to achieve the purpose of lightweight.

[0006] In a first aspect, an embodiment of the present application provides a container-based vehicle operating system display method, the method is applied to a display server deployed on a host machine, and the method includes the following steps:

[0007] When receiving the to-be-displayed layer data sent by the target display client deployed on the target operating system container, performing layer synthesis on the to-be-displayed layer data to generate target synthesized layer data, wherein the target operating system container runs on the host machine;

[0008] Determine a first display port corresponding to the target operating system container based on a preset mapping relationship between the operating system container and the display port;

[0009] The target composite layer data is transmitted to the first display port for display.

[0010] In combination with the first aspect, in one implementation, the method further includes:

[0011] Performing layer synthesis on multiple to-be-fused layer data received from a target input port to obtain target fused layer data, wherein the multiple to-be-fused layer data are data sent to the target input port by different target display clients, and the different target display clients are deployed on different target operating system containers;

[0012] Determine a second display port corresponding to the target input port based on a preset mapping relationship between an input port and an operating system container and a mapping relationship between an operating system container and a display port;

[0013] The target fusion layer data is transmitted to the second display port for display.

[0014] In combination with the first aspect, in one implementation, the layer data to be fused is business data corresponding to a fixed service or business data corresponding to a dynamic service, the fixed service is a factory pre-configured service, and the dynamic service is a randomly configured service.

[0015] In combination with the first aspect, in one implementation, the display server is deployed on any operating system container.

[0016] In combination with the first aspect, in one implementation, the display server receives the layer data to be displayed through an input port corresponding to the target operating system container and interacts with the target display client based on a preset display service protocol.

[0017] In a second aspect, an embodiment of the present application provides a container-based vehicle operating system display device, wherein the container-based vehicle operating system display device includes a display server deployed on a host machine and a target operating system container running on the host machine, wherein the display server is used to:

[0018] When receiving the to-be-displayed layer data sent by the target display client deployed on the target operating system container, performing layer synthesis on the to-be-displayed layer data to generate target synthesized layer data;

[0019] Determine a first display port corresponding to the target operating system container based on a preset mapping relationship between the operating system container and the display port;

[0020] The target composite layer data is transmitted to the first display port for display.

[0021] In conjunction with the second aspect, in one implementation, the display server is further configured to:

[0022] Performing layer synthesis on multiple to-be-fused layer data received from a target input port to obtain target fused layer data, wherein the multiple to-be-fused layer data are data sent to the target input port by different target display clients, and the different target display clients are deployed on different target operating system containers;

[0023] Determine a second display port corresponding to the target input port based on a preset mapping relationship between an input port and an operating system container and a mapping relationship between an operating system container and a display port;

[0024] The target fusion layer data is transmitted to the second display port for display.

[0025] In combination with the second aspect, in one implementation, the layer data to be fused is business data corresponding to a fixed service or business data corresponding to a dynamic service, the fixed service is a factory pre-configured service, and the dynamic service is a randomly configured service.

[0026] In combination with the second aspect, in one implementation, the display server is deployed on any operating system container.

[0027] In combination with the second aspect, in one implementation, the display server receives the layer data to be displayed through an input port corresponding to the target operating system container and interacts with the target display client based on a preset display service protocol.

[0028] In a third aspect, an embodiment of the present application provides a container-based vehicle operating system display device, wherein the container-based vehicle operating system display device includes a processor, a memory, and a container-based vehicle operating system display program stored in the memory and executable by the processor, wherein when the container-based vehicle operating system display program is executed by the processor, the steps of the aforementioned container-based vehicle operating system display method are implemented.

[0029] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a container-based vehicle-mounted operating system display program is stored. When the container-based vehicle-mounted operating system display program is executed by a processor, the steps of the aforementioned container-based vehicle-mounted operating system display method are implemented.

[0030] The beneficial effects brought by the technical solution provided in the embodiments of the present application include:

[0031] All layer merging is completed by a display server deployed on the host machine, that is, the display server will perform layer synthesis on the layer data to be displayed obtained from each target display client deployed on the target operating system container to generate target synthesized layer data, and based on the preset mapping relationship between the operating system container and the display port, the target synthesized layer data is transmitted to the display port corresponding to the target operating system container for display, so as to realize the display of the vehicle operating system data; it can be seen that through this application, the operating system container is no longer responsible for the merging of layers but only provides a display client, thereby achieving the purpose of lightweight container; and all display servers in all containers are merged into one display server on the host machine, which can reduce the overall number of processes of the system to reduce resource consumption and memory requirements, thereby effectively improving the overall performance of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] Figure 1 This is a flow chart of an embodiment of a method for displaying a vehicle operating system based on a container of the present application;

[0033] Figure 2 This is a schematic diagram of the internal deployment of one of the host machines involved in the embodiment of the present application;

[0034] Figure 3 A schematic diagram of data fusion between different operating system containers involved in the embodiment of the present application;

[0035] Figure 4 This is a schematic diagram of another internal deployment of a host machine involved in the embodiment of the present application;

[0036] Figure 5 This is a schematic diagram of the hardware structure of a container-based vehicle operating system display device involved in the embodiment of the present application. DETAILED DESCRIPTION

[0037] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0038] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.

[0039] In a first aspect, an embodiment of the present application provides a container-based vehicle operating system display method.

[0040] In one embodiment, referring to Figure 1 , Figure 1 This is a flow chart of an embodiment of the container-based vehicle operating system display method of the present application. Figure 1 As shown, the container-based vehicle operating system display method is applied to a display server deployed on a host machine, and the method includes the following steps:

[0041] Step S10: When receiving the layer data to be displayed sent by the target display client deployed on the target operating system container, layer synthesis is performed on the layer data to be displayed to generate target synthesized layer data, and the target operating system container runs on the host machine.

[0042] For example, it should be understood that when all vehicle-mounted operating systems are implemented on the same SOC in a container-based manner, since the traditional container implements functions such as window management and layer synthesis through its internal complete graphics display service, that is, each container needs to deploy a client for processing tasks such as layer synthesis and a display server for sending and displaying, resulting in large resource consumption and memory requirements. In this embodiment, see Figure 2 As shown, the layer merging of all containers is completed by only one display server (i.e., dp-server) deployed on the host (i.e., Host), so that the container does not need to perform layer synthesis tasks, thereby reducing the resource consumption and memory requirements of the container, and there is no need to deploy the display server in each container, thereby effectively reducing the occupation of hardware resources.

[0043] It should be noted that the target operating system container refers to the container corresponding to the instrument system, central control system, co-pilot system, and rear system that have display requirements. For example, if the target operating system is the instrument system, the target operating system container is the instrument container; the target display client refers to the client deployed in the target operating system container, which is used to provide display services. Figure 2 As shown, multiple operating system containers Container1 to Container n are run on the host machine, and each operating system container has the need to be displayed independently on different screens; and only a display client dp-client providing display services is deployed in each operating system container, and the display clients include dp-client1 to dp-client n. It should be understood that the display service can be any one of the display technologies such as X11, wayland, xwayland, etc. It can be understood that, assuming that the instrument container is Container1 and the display client is dp-client1, if the target operating system is the instrument system, the target operating system container is Container1 and the target display client is dp-client1.

[0044] For any target operating system, when there is a display demand, the target display client in the corresponding target operating system container will send the layer data to be displayed to the display server, so that the display server can perform layer synthesis processing on the received layer data to be displayed, thereby generating target synthesized layer data.

[0045] Furthermore, in one embodiment, the display server receives the layer data to be displayed through an input port corresponding to the target operating system container and performs data exchange with the target display client based on a preset display service protocol.

[0046] Exemplarily, in this embodiment, a data transmission interface is configured for each target operating system container on the display server, that is, each target operating system container has an input port corresponding to it, that is, there is a mapping relationship between the target operating system container and the input port. When the target display client performs data transmission, it can be transmitted to the display server through the input port corresponding to the target operating system container in which it is located; it should be noted that the target display client can realize data transmission with the display server based on communication technologies such as socket.

[0047] It should be understood that the display client dp-client can exchange data with the display server dp-server through a display protocol corresponding to the display service, wherein the display protocol can be any one of protocols such as X11, wayland, xwayland, etc.

[0048] Step S20: determining a first display port corresponding to the target operating system container based on a preset mapping relationship between the operating system container and the display port.

[0049] Exemplarily, in this embodiment, each operating system has a display screen corresponding to it. For example, for an instrument system, the corresponding display screen is an instrument display screen. Based on this, the computer hardware Hardware configures a display port dp for each display screen for data transmission therewith. Since there is a corresponding relationship between the operating system and the operating system container, there is also a mapping relationship between the operating system container and the display port. For example, Figure 2 Container1 and dp1 in the diagram have a mapping relationship. It can be seen that Hardware provides display ports dp1 to dpn to realize the display of containers of different operating systems.

[0050] Therefore, the display port corresponding to the target operating system container (i.e., the first display port) can be found through the above mapping relationship to realize data transmission between the display server and the display screen. For example, if the target operating system container is Container1 and its corresponding display port is dp1, then the first display port is dp1.

[0051] Step S30: transmitting the target composite layer data to the first display port for display.

[0052] Exemplarily, in this embodiment, after determining the first display port, the display server will send the display based on the first display port, that is, transmit the target synthesis layer data to the display screen corresponding to the first display port for display, so as to realize the display of the vehicle operating system data. For example, assuming that the target operating system is an instrument system and its corresponding target operating system container is Container1, when the display server receives the layer data to be displayed sent by dp-client1 in Container1 and performs layer synthesis on it, it will send the target synthesis layer data to dp1 through the mapping relationship between Container and dp.

[0053] In summary, this embodiment enables the operating system container to no longer be responsible for layer merging but only provide a display client, thereby achieving the purpose of lightweight container; and all display server ends in all containers are unified and merged into one display server end on the host machine, which can reduce the overall number of processes in the system, thereby reducing resource consumption and memory requirements, thereby effectively improving the overall performance of the system.

[0054] Furthermore, in one embodiment, the method further includes:

[0055] Perform layer synthesis on multiple layer data to be fused received from the target input port to obtain target fused layer data, wherein the multiple layer data to be fused are data sent to the target input port by different target display clients, and the different target display clients are deployed on different target operating system containers; wherein the layer data to be fused are business data corresponding to a fixed business or business data corresponding to a dynamic business, wherein the fixed business is a factory pre-configured business, and the dynamic business is a randomly configured business;

[0056] Determine a second display port corresponding to the target input port based on a preset mapping relationship between an input port and an operating system container and a mapping relationship between an operating system container and a display port;

[0057] The target fusion layer data is transmitted to the second display port for display.

[0058] Exemplarily, it is understandable that a traditional container has a complete graphics display service for implementing functions such as window management and layer synthesis, and is displayed through the display driver of the host machine, so that when implementing process-level layer fusion between containers for on-demand multi-display services, there is a problem of complex fusion process. For example, taking navigation projection as an example, assuming that the navigation map of the entertainment system needs to be displayed on the instrument, the entertainment system container needs to first perform layer synthesis on the navigation data based on its internal client to obtain layer data 1, and the instrument system container needs to perform layer synthesis on its existing data based on its internal client 1 to obtain layer data 2; then the instrument system container obtains layer data 1 from the display server in the entertainment system container based on another internal client 2 through IPC (Inter-Process Communication), and at this time, client 1 and client 2 will respectively send layer data 1 and layer data 2 to the display server in the instrument system container for fusion before displaying; it can be seen that the fusion process is very complicated and troublesome.

[0059] In addition, traditional containers can only display and transfer fixed services predefined at the factory, but cannot perform dynamic layer fusion display, resulting in the problem of fixed fusion solutions. For example, the predefined instrument system at the factory can realize the fusion display of the navigation map in the entertainment system, so the instrument system can only perform the fusion display of the navigation system, but cannot perform the fusion display of other services.

[0060] In this embodiment, only a display server deployed on the host machine is used to synthesize and display the layers. That is, when there is a display fusion requirement between different operation containers, the display server dp-server will synthesize the layers from different containers and display them to the specified port, regardless of whether the layer data is the business data pre-configured at the factory. Therefore, this embodiment can simplify the display fusion process and realize the dynamic fusion of fixed and random services to improve the flexibility of fusion. It should be noted that the existence of display fusion requirements between different operation containers can be determined based on the number of data received by an input port being no less than 1; of course, other judgment conditions can also be set according to actual needs to determine whether there is a display fusion requirement between different operation containers, which is not limited here.

[0061] See also Figure 3 As shown in the figure, it is assumed that the target operating system container Container1 is configured to send the display to dp1, and the target operating system container Container2 is configured to send the display to dp2; at this time, if a target service in Container1 and Container2 needs to be merged and sent to dp1, the dp-server can merge the data sent by the target display client client specified in Container1 and Container2; specifically, dp-client1 in Container1 will send the to-be-fused layer data corresponding to the target service to the target input port corresponding to Container1, and at the same time, dp-client2 in Container2 will also send the to-be-fused layer data corresponding to the target service to the target input port; when dp-server When receiving the layer data to be fused sent by dp-client1 and dp-client2 from the target input port, since it receives two layer data to be fused, the synthesis module (i.e., composer) corresponding to Container1 in dp-server will perform layer synthesis on the two to obtain the target fused layer data, so as to realize process-level layer synthesis; then, dp-server will determine that the target operating system container corresponding to the target input port is Container1 according to the mapping relationship between the input port and the operating system container, and determine that the display port corresponding to Container1 is dp1 (i.e., the second display port) according to the mapping relationship between the operating system container and the display port, and then send the target fused layer data to dp1 for display, thereby completing the fused display between different operating system containers.

[0062] It should be noted that the service in Container2 that needs to be displayed in fusion with Container1 can be a fixed service predefined at the factory or any randomly specified dynamic service, and the display server supports layer synthesis of any display client.

[0063] In addition, see Figure 3 As shown in the figure, for Container2, the services that have been integrated with Container1 can still be sent to display from dp2, or they can be displayed only to dp1 without being output from dp2. The specific configuration can be made according to actual needs.

[0064] Furthermore, in one embodiment, the display server is deployed on any operating system container.

[0065] For example, in this embodiment, the display server can also be deployed in an operating system container, that is, an operating system container is randomly selected from all operating system containers for dp-server deployment, which can be more conducive to business deployment; for example, see Figure 4 As shown, dp-server is deployed to Container 1. It should be noted that, except that dp-server is deployed from the host machine to the operating system container, the other layer synthesis and display methods are the same as those explained in the previous steps, and will not be repeated here.

[0066] It can be seen that the container-based in-vehicle operating system display method provided in this embodiment can achieve a more flexible display mode to meet the needs of display of different operating systems and display fusion between operating systems.

[0067] In a second aspect, an embodiment of the present application also provides a container-based vehicle operating system display device.

[0068] In one embodiment, a container-based in-vehicle operating system display device includes a display server deployed on a host machine and a target operating system container running on the host machine, wherein the display server is used to:

[0069] When receiving the to-be-displayed layer data sent by the target display client deployed on the target operating system container, performing layer synthesis on the to-be-displayed layer data to generate target synthesized layer data;

[0070] Determine a first display port corresponding to the target operating system container based on a preset mapping relationship between the operating system container and the display port;

[0071] The target composite layer data is transmitted to the first display port for display.

[0072] Furthermore, in one embodiment, the display server is also used for:

[0073] Performing layer synthesis on multiple to-be-fused layer data received from a target input port to obtain target fused layer data, wherein the multiple to-be-fused layer data are data sent to the target input port by different target display clients, and the different target display clients are deployed on different target operating system containers;

[0074] Determine a second display port corresponding to the target input port based on a preset mapping relationship between an input port and an operating system container and a mapping relationship between an operating system container and a display port;

[0075] The target fusion layer data is transmitted to the second display port for display.

[0076] Furthermore, in one embodiment, the layer data to be fused is business data corresponding to a fixed business or business data corresponding to a dynamic business, the fixed business is a factory pre-configured business, and the dynamic business is a randomly configured business.

[0077] Furthermore, in one embodiment, the display server is deployed on any operating system container.

[0078] Furthermore, in one embodiment, the display server receives the layer data to be displayed through an input port corresponding to the target operating system container and performs data exchange with the target display client based on a preset display service protocol.

[0079] Among them, the functional implementation of each part in the above-mentioned container-based vehicle operating system display device corresponds to the various steps in the above-mentioned container-based vehicle operating system display method embodiment, and its functions and implementation processes are no longer repeated here one by one.

[0080] In a third aspect, an embodiment of the present application provides a container-based in-vehicle operating system display device. The container-based in-vehicle operating system display device may be a personal computer (PC), a laptop computer, a server, or other device with data processing capabilities.

[0081] Reference Figure 5 , Figure 5 The hardware structure diagram of the container-based vehicle operating system display device involved in the embodiment of the present application is shown in FIG. In the embodiment of the present application, the container-based vehicle operating system display device may include a processor, a memory, a communication interface, and a communication bus.

[0082] The communication bus may be of any type and is used to interconnect the processor, the memory, and the communication interface.

[0083] The communication interface includes an input / output (I / O) interface, a physical interface, and a logical interface, etc., which are used to realize the interconnection of devices inside the container-based vehicle operating system display device, and an interface for realizing the interconnection between the container-based vehicle operating system display device and other devices (such as other computing devices or user devices). The physical interface can be an Ethernet interface, a fiber optic interface, an ATM interface, etc.; the user device can be a display, a keyboard, etc.

[0084] The memory can be various types of storage media, such as random access memory (RAM), read-only memory (ROM), non-volatile RAM (NVRAM), flash memory, optical storage, hard disk, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), etc.

[0085] The processor may be a general-purpose processor, which may call the container-based vehicle operating system display program stored in the memory and execute the container-based vehicle operating system display method provided in the embodiment of the present application. For example, the general-purpose processor may be a central processing unit (CPU). The method executed when the container-based vehicle operating system display program is called may refer to the various embodiments of the container-based vehicle operating system display method of the present application, which will not be repeated here.

[0086] Those skilled in the art will understand that Figure 5 The hardware structure shown in the figure does not constitute a limitation on the present application, and may include more or less components than shown in the figure, or combine certain components, or arrange the components differently.

[0087] In a fourth aspect, an embodiment of the present application also provides a computer-readable storage medium.

[0088] The readable storage medium of the present application stores a container-based vehicle operating system display program, wherein when the container-based vehicle operating system display program is executed by a processor, the steps of the container-based vehicle operating system display method as described above are implemented.

[0089] Among them, the method implemented when the container-based vehicle operating system display program is executed can refer to the various embodiments of the container-based vehicle operating system display method of the present application, and will not be repeated here.

[0090] It should be noted that the serial numbers of the above-mentioned embodiments of the present application are only for description and do not represent the advantages or disadvantages of the embodiments.

[0091] The terms "including" and "having" and any variations thereof in the specification and claims of this application and the above-mentioned drawings are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally includes steps or units that are not listed, or optionally includes other steps or units inherent to these processes, methods, products or devices. The terms "first", "second" and "third" are used to distinguish different objects, etc., and do not represent a sequence, nor do they limit "first", "second" and "third" to different types.

[0092] In the description of the embodiments of the present application, "exemplary", "for example" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary", "for example" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary", "for example" or "for example" is intended to present related concepts in a specific way.

[0093] In the description of the embodiments of the present application, unless otherwise specified, “ / ” means or, for example, A / B can mean A or B; the “and / or” in the text is merely a description of the association relationship of associated objects, indicating that three relationships may exist, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, “multiple” refers to two or more than two.

[0094] In some processes described in the embodiments of the present application, multiple operations or steps that appear in a specific order are included, but it should be understood that these operations or steps may not be executed in the order in which they appear in the embodiments of the present application or in parallel, and the sequence number of the operation is only used to distinguish the different operations, and the sequence number itself does not represent any execution order. In addition, these processes may include more or fewer operations, and these operations or steps may be executed in sequence or in parallel, and these operations or steps may be combined.

[0095] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, disk, CD) as described above, and includes a number of instructions for a terminal device to execute the methods described in each embodiment of the present application.

[0096] The above are only preferred embodiments of the present application, and are not intended to limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A container-based vehicle operating system display method, characterized in that: The method is applied to a display server deployed on a host machine, and the method comprises the following steps: When receiving the to-be-displayed layer data sent by the target display client deployed on the target operating system container, performing layer synthesis on the to-be-displayed layer data to generate target synthesized layer data, wherein the target operating system container runs on the host machine; Determine a first display port corresponding to the target operating system container based on a preset mapping relationship between the operating system container and the display port; The target composite layer data is transmitted to the first display port for display.

2. The container-based vehicle operating system display method according to claim 1, characterized in that: The method further comprises: Performing layer synthesis on multiple to-be-fused layer data received from a target input port to obtain target fused layer data, wherein the multiple to-be-fused layer data are data sent to the target input port by different target display clients, and the different target display clients are deployed on different target operating system containers; Determine a second display port corresponding to the target input port based on a preset mapping relationship between an input port and an operating system container and a mapping relationship between an operating system container and a display port; The target fusion layer data is transmitted to the second display port for display.

3. The container-based vehicle operating system display method according to claim 2, characterized in that: The layer data to be fused is business data corresponding to a fixed business or business data corresponding to a dynamic business. The fixed business is a factory pre-configured business, and the dynamic business is a randomly configured business.

4. The container-based vehicle operating system display method according to claim 1, characterized in that: The display server is deployed on any operating system container.

5. The container-based vehicle operating system display method according to claim 1, characterized in that: The display server receives the layer data to be displayed through an input port corresponding to the target operating system container and performs data interaction with the target display client based on a preset display service protocol.

6. A container-based vehicle operating system display device, characterized in that: The container-based in-vehicle operating system display device includes a display server deployed on a host machine and a target operating system container running on the host machine, wherein the display server is used to: When receiving the to-be-displayed layer data sent by the target display client deployed on the target operating system container, performing layer synthesis on the to-be-displayed layer data to generate target synthesized layer data; Determine a first display port corresponding to the target operating system container based on a preset mapping relationship between the operating system container and the display port; The target composite layer data is transmitted to the first display port for display.

7. The container-based vehicle operating system display device according to claim 6, characterized in that: The display server is also used for: Performing layer synthesis on multiple to-be-fused layer data received from a target input port to obtain target fused layer data, wherein the multiple to-be-fused layer data are data sent to the target input port by different target display clients, and the different target display clients are deployed on different target operating system containers; Determine a second display port corresponding to the target input port based on a preset mapping relationship between an input port and an operating system container and a mapping relationship between an operating system container and a display port; The target fusion layer data is transmitted to the second display port for display.

8. The container-based vehicle operating system display device according to claim 7, characterized in that: The layer data to be fused is business data corresponding to a fixed business or business data corresponding to a dynamic business. The fixed business is a factory pre-configured business, and the dynamic business is a randomly configured business.

9. A container-based vehicle operating system display device, characterized in that: The container-based in-vehicle operating system display device includes a processor, a memory, and a container-based in-vehicle operating system display program stored in the memory and executable by the processor, wherein when the container-based in-vehicle operating system display program is executed by the processor, the steps of the container-based in-vehicle operating system display method as described in any one of claims 1 to 5 are implemented.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a container-based vehicle operating system display program, wherein when the container-based vehicle operating system display program is executed by a processor, the steps of the container-based vehicle operating system display method as described in any one of claims 1 to 5 are implemented.

Images