Passenger cabin multi-screen display method, device and equipment based on cloud mobile phone and medium

By creating multiple containers in the terminal of the bus cabin and using docker container technology to achieve independent operation of multiple screens, the problem that existing smart screen systems cannot meet personalized entertainment needs is solved, reducing hardware costs and improving equipment utilization.

CN119645332APending Publication Date: 2025-03-18BEIJING AOSI TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411654492.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-11-19
Publication Date
2025-03-18

AI Technical Summary

Technical Problem

The smart screen system in the existing bus cabin mainly uses a centralized entertainment system, which cannot meet the needs of personalized entertainment. The personalized entertainment system has limited applications due to its high cost and complexity.

Method used

By creating multiple containers in the terminal, docker container technology is used to realize independent operation of multiple screens, sharing resources to reduce hardware costs and improve device utilization.

Benefits of technology

It realizes independent operation of multi-cabin screens, reduces hardware costs, improves equipment utilization, and solves the problem of multiple users sharing the same hardware host.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119645332A_ABST
    Figure CN119645332A_ABST
Patent Text Reader

Abstract

The invention discloses a passenger cabin multi-screen display method and device based on a cloud mobile phone, equipment and a medium. The method is applied to a terminal supporting a docker container technology, a container corresponding to each screen is created in the terminal, a system instance corresponding to an operating system of the terminal runs in the container, and an inter-process communication node corresponding to the operating system is mirrored in each container. A preset operation executed by a user on a target screen of the multiple screens is obtained, and the target container is a container which is created in the terminal and corresponds to the target screen; determining whether the preset operation needs to access an inter-process communication node of the terminal; and when it is determined that the preset operation needs to access the inter-process communication node of the terminal, accessing a terminal service corresponding to the preset operation through the mirrored inter-process communication node in the target container, processing graphic data corresponding to the preset operation by the terminal service, and transmitting the processed graphic data to a target screen for display.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments of the present application relate to the fields of container technology and operating system technology, and in particular to a method, device, equipment and medium for displaying multiple screens in a cabin based on a cloud phone. Background Art

[0002] With the development of the bus industry, passengers' requirements for travel experience are gradually increasing. In traditional buses, passengers can only obtain limited information through simple broadcasts or paper advertisements, which can no longer meet passengers' needs for interactivity and information.

[0003] As a new type of interactive device, smart screens can provide passengers with rich entertainment content, real-time itinerary information and advertising services, thus improving passengers' travel experience. At the same time, smart screens also provide operators with a new business model, realizing value-added services through precise advertising and information release. Smart screen systems in bus cabins are generally divided into two types: centralized entertainment systems and personalized entertainment systems. Centralized entertainment systems are the most common, with all passengers sharing the same set of entertainment content, such as movies, TV shows and music. In contrast, personalized entertainment systems allow each passenger to independently select and watch different programs or content to meet their personal entertainment needs. Passengers can control the screen through a simple operating interface.

[0004] At present, most bus companies use centralized entertainment systems to provide entertainment services for passengers in the cabin. The architecture and management of this system are relatively simple, suitable for most bus compartment configurations, and have low costs.

[0005] Although personalized entertainment systems can provide a more personalized experience, their application in bus cabins is relatively limited due to their complexity and high cost. Personalized entertainment systems are usually used in high-end tourist buses or luxury buses to provide more luxurious and customized services to meet the needs of high-end passengers. This method requires a complete set of hardware for each on-board screen to work properly, and the hardware cost is relatively high. Summary of the invention

[0006] The embodiment of the present application provides a method, device, equipment and medium for displaying multiple screens in a cabin based on a cloud phone, which can be used to realize independent operation of multiple screens through container technology, effectively reduce hardware costs, and improve equipment utilization by sharing resources. The technical solution is as follows:

[0007] On the one hand, an embodiment of the present application provides a method for displaying multiple screens in a cabin based on a cloud phone, which is applied to a terminal supporting docker container technology, wherein a container corresponding to each screen is created in the terminal, a system instance corresponding to an operating system of the terminal is run in the container, and an inter-process communication node corresponding to the operating system is mirrored in each container, and the method includes:

[0008] Calling a system instance in a target container to obtain a preset operation performed by a user on a target screen of the multi-screen, wherein the target container is a container created in the terminal and corresponding to the target screen;

[0009] Determining whether the preset operation requires access to an inter-process communication node of the terminal;

[0010] When it is determined that the preset operation requires access to the inter-process communication node of the terminal, the terminal service corresponding to the preset operation is accessed through the inter-process communication node of the image in the target container, so that the terminal service processes the graphic data corresponding to the preset operation and transmits the processed graphic data to the target screen for display.

[0011] On the other hand, an embodiment of the present application provides a multi-screen display device in a cabin based on a cloud phone, which is applied to a terminal supporting docker container technology, wherein a container corresponding to each screen is created in the terminal, a system instance corresponding to the operating system of the terminal is run in the container, and an inter-process communication node corresponding to the operating system is mirrored in each of the containers, and the device includes:

[0012] A preset operation acquisition module, used to call a system instance in a target container to acquire a preset operation performed by a user on a target screen of the multi-screen, wherein the target container is a container created in the terminal and corresponding to the target screen;

[0013] A preset operation determination module, used to determine whether the preset operation requires access to an inter-process communication node of the terminal;

[0014] A terminal service access module is used to access the terminal service corresponding to the preset operation through the inter-process communication node of the image in the target container when it is determined that the preset operation needs to access the inter-process communication node of the terminal, so that the terminal service processes the graphic data corresponding to the preset operation and transmits the processed graphic data to the target screen for display.

[0015] On the other hand, an embodiment of the present application provides an electronic device, comprising a processor and a memory, wherein the memory stores at least one instruction, at least one program, a code set or an instruction set, and the at least one instruction, the at least one program, the code set or the instruction set is loaded and executed by the processor to implement the method described in the above aspects.

[0016] On the other hand, an embodiment of the present application provides a computer-readable storage medium, in which at least one instruction, at least one program, a code set or an instruction set is stored, and the at least one instruction, the at least one program, the code set or the instruction set is loaded and executed by a processor to implement the method described in the above aspects.

[0017] On the other hand, an embodiment of the present application provides a computer program product, which, when executed, is used to execute the method described in the above aspects.

[0018] In the technical solution provided in the embodiment of the present application, multiple containers are created in the terminal and container technology is used to control multiple screens. The problem of multiple cabin screens being connected to an Android host at the same time is solved, and the operation of each cabin screen is independent. This solves the problem of multiple users using multiple cabin screens connected to the same hardware host device and using them at the same time, and can effectively reduce hardware costs and improve device utilization by sharing resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1 A flowchart of a method for displaying multiple screens in a cabin based on a cloud phone provided in an embodiment of the present application;

[0020] Figure 2 A block diagram of an Android system infrastructure provided in an embodiment of the present application;

[0021] Figure 3 A block diagram of accessing a host binder node in a container provided in an embodiment of the present application;

[0022] Figure 4 A timing diagram of a Guest Android container accessing a Host Android binder node provided in an embodiment of the present application;

[0023] Figure 5 A timing diagram of a Guest Android container accessing a binder node in a container provided in an embodiment of the present application;

[0024] Figure 6 A schematic diagram of the structure of a multi-screen display device in a cabin based on a cloud phone provided in an embodiment of the present application;

[0025] Figure 7 A structural block diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0026] The implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.

[0027] Reference Figure 1 , shows a flow chart of the steps of a method for displaying multiple screens in a cabin based on a cloud phone provided in an embodiment of the present application. Figure 1 As shown, the cabin multi-screen display method based on cloud phone may include: step 101, step 102 and step 103.

[0028] Step 101: calling a system instance in a target container to obtain a preset operation performed by a user on a target screen of the multi-screen, wherein the target container is a container created in the terminal and corresponding to the target screen.

[0029] The embodiment of the present application can be applied to a terminal supporting docker container technology, in which a container corresponding to each screen is created in the terminal, a system instance corresponding to the operating system of the terminal is run in the container, and an inter-process communication node corresponding to the operating system is mirrored in each container. Multiple screens are connected to the terminal.

[0030] A Docker container is a "container" run by a program written in the Go language, which uses Linux kernel features (such as namespaces and control groups) to provide isolation and resource management. Each Docker container is an independent, repeatable, and deployable unit with its own file system, network, and process space, and can be quickly started, stopped, and migrated.

[0031] The operating system of the terminal may be an Android system, an iOS system, a Hongmeng system, etc. The specific type of the operating system of the terminal may be determined according to business requirements, and this embodiment does not impose any restrictions on this.

[0032] On a terminal that supports Docker container technology, an independent Docker container is created for each screen. These containers are isolated from each other to ensure that the operating system instances or application environments on each screen do not interfere with each other.

[0033] In each created container, a system instance corresponding to the terminal operating system is run. These system instances can be complete operating systems or lightweight operating system images. Specifically, it can be determined according to actual needs, and this embodiment does not limit this.

[0034] Each container has an inter-process communication node corresponding to the terminal operating system. For example, the operating system takes the Android system as an example. Android Binder is a very important inter-process communication (IPC) mechanism in the Android system. It allows efficient and secure data exchange between different processes and supports cross-process calls, so that various components in the Android system can work together. Binder is the basis for implementing communication between most services (such as Activity Manager, Window Manager, etc.) and application processes in the Android system.

[0035] Docker provides a lightweight virtualization method, which mainly implements application isolation through containers. Unlike traditional virtual machines, Docker containers share the host's operating system kernel, but can still provide a relatively independent environment to ensure mutual isolation between different containers. There are mainly Namespace isolation, Cgroups isolation, UnionFS, and network isolation. Namespace is a mechanism provided by the Linux kernel, which can isolate system resources (such as processes, networks, file systems, etc.) into different containers, making each container look like an independent system. In this way, the Android container can only access the processes and services in the container, and cannot access the processes and nodes of the host (i.e., the terminal). Therefore, if the container wants to communicate with the host system and call the service interface of the host system, it needs to be able to access the host's binder node (i.e., the inter-process communication node in the Android system).

[0036] In the specific implementation, you can use the -v mapping mode to map the / dev / hwbinder node (i.e., inter-process communication node) of the host system to the container to create a Guest Android container. In this way, the container has the basis for accessing the host hwbinder node (the inter-process communication node of the terminal), and the container has its own / dev / hwbinder node (the inter-process communication node of the container), which does not affect the Guest Android (i.e., the Android system instance in the container) to communicate with internal services through binder communication.

[0037] For this infrastructure, Figure 2 As shown in the figure (taking Android system as an example), Android (Host) is the Android main system of the terminal. The control of graphic display output is all carried out in the main system, and each Guest system ( Figure 2The graphic data of Guest1, Guest2, Guest3) (i.e., the Android system instance in the container) is decrypted and rendered and then output to different screen devices to achieve independent display output of each Guest system.

[0038] After completing the above operations, the user on the multi-screen side can perform the preset operation. Specifically, the system instance in the target container can be called to obtain the preset operation performed by the user on the target screen of the multi-screen. In a specific implementation, a monitoring tool or script can be run in the target container to capture the preset operation performed by the user on the target screen. The monitoring tool or script needs to convert the captured operation into a format that can be recognized by the system instance.

[0039] The target container is a container corresponding to the target screen among the multiple containers created in the terminal. The preset operation may be an operation of opening an application, an operation of opening a file, or an operation of opening a multimedia file (such as an audio file, a video file, etc.). This embodiment does not limit the specific operation type of the preset operation.

[0040] After the system instance in the target container is called to obtain the preset operation performed by the user on the target screen, step 102 is executed.

[0041] Step 102: Determine whether the preset operation requires access to an inter-process communication node of the terminal.

[0042] After the system instance in the target container is called to obtain the preset operation performed by the user on the target screen, it can be determined whether the preset operation requires access to the inter-process communication node of the terminal.

[0043] In this embodiment, whether the inter-process communication node of the terminal needs to be accessed can be customized, that is, a variable parameter of whether the inter-process communication node of the terminal needs to be accessed can be set in each container. If the variable parameter of accessing the inter-process communication node of the terminal is true, it means that the inter-process communication node of the terminal needs to be accessed. If the variable parameter is false, it means that the inter-process communication node in the container needs to be accessed.

[0044] Of course, when it is necessary to access the digital rights management (i.e., Digital Rights Management, DRM) service of the system layer of the terminal's operating system, it is possible to first determine whether the graphic data corresponding to the preset operation needs to be processed by the digital rights management service to obtain a determination result. And based on the determination result, it is determined whether the preset operation needs to access the inter-process communication node of the terminal. For example, when the preset operation is to open a certain video file, the video file can be a paid video file of a certain multimedia platform. At this time, it is necessary to perform the processing operation of the video file through the terminal's DRM service, and then it is necessary to access the terminal's digital rights management service, etc.

[0045] In specific implementation, digital rights management (DRM) is a technology used to protect the copyright of digital content. It uses a series of technical means, such as encryption, permission control, digital watermarking, etc., to ensure that digital content is used within the specified authorized scope and prevent illegal copying and distribution.

[0046] DRM technology first establishes a digital program authorization center to encrypt digital content and protect it with keys. The encrypted digital content header stores the KeyID and URL of the program authorization center. When users play on demand, they can obtain the relevant key decryption after verification and authorization by the digital program authorization center based on the KeyID and URL (Uniform Resource Locator) information in the program header, and the program can be played. Even if the content is downloaded, it cannot be played without the key of the authorization center, thus protecting the copyright of the program.

[0047] Widevine DRM is a digital rights management (DRM) technology provided by Google that is used to protect streaming content and digital files from unauthorized access and copying. Widevine DRM is widely used on various platforms, including Android devices, Chrome browsers, and other supported browsers.

[0048] Widevine DRM has three security levels: L1, L2 and L3, of which L1 is the highest level of security protection and is usually used to protect high-definition video content. The L1 level content decryption and rendering process is completed entirely in a trusted execution environment at the hardware level, which can provide the highest level of security. For Android devices, the Widevine DRM client is usually built into the device to decrypt protected video content. The main functions of the Widevine client include authenticating with the Widevine server, obtaining the decryption key, and downloading videos from the content server for decrypted playback.

[0049] Since Widevine in TZ (TrustZone, a hardware-based security technology) only supports one Client and does not support multiple L1-level clients, in this embodiment, the system-level DRM module is only run in the host system (Host), and the system-level DRM module is not run in multiple Docker-based guest systems (Guest). This design is to ensure the security isolation of Widevine DRM in TrustZone, while avoiding conflicts or security issues between multiple clients. Figure 2 As shown, Guest1, Guest2, and Guest3 all disable the DRM module and run the DRM module in the Android main system.

[0050] When it is determined that the preset operation does not need to access the inter-process communication node of the terminal, the container client of the system instance in the target container can be called to obtain the variable parameter of the inter-process communication node of the access terminal. In the case where the variable parameter is an inaccessible parameter, the container service corresponding to the preset operation is accessed through the container inter-process communication node pre-created in the target container, so that the container service processes the graphic data corresponding to the preset operation, and transmits the processed graphic data to the target screen for display.

[0051] The timing for the Guest Android container to access the binder node in the container can be as follows Figure 5 As shown. When creating a container, you can map the / dev / hwbinder node of the host system to / lxc / hwbinder in the container (the directory path for storing inter-process communication nodes). And set global variables through the client service (client access) in the container. In actual use, you can get global variables through libhwbinder (an important library for inter-process communication in the Android system). If libhwbinder gets the global variable as false, use the / dev / hwbinder node created in the container in advance. The / dev / hwbinder node in the container can access the service corresponding to the preset operation, and the service processes the graphic data corresponding to the preset operation, and transmits the processed graphic data to the target screen for display.

[0052] After determining that the preset operation requires access to the inter-process communication node of the terminal, step 103 is executed.

[0053] Step 103: When it is determined that the preset operation requires access to the inter-process communication node of the terminal, the terminal service corresponding to the preset operation is accessed through the inter-process communication node of the image in the target container, so that the terminal service processes the graphic data corresponding to the preset operation and transmits the processed graphic data to the target screen for display.

[0054] When it is determined that the preset operation requires access to the inter-process communication node of the terminal, the terminal service corresponding to the preset operation can be accessed through the inter-process communication node of the image in the target container, so that the terminal service can process the graphic data corresponding to the preset operation and transmit the processed graphic data to the target screen for display.

[0055] The embodiment of the present application enables the container to have the ability to access the inter-process communication node of the main system by mirroring the inter-process communication node of the terminal in each container, and the container has its own inter-process communication node, which does not affect the system instance in the container to communicate with the internal service through the inter-process communication node.

[0056] When using the terminal service to process graphic data, the variable parameters of the inter-process communication node for accessing the terminal can be set first, and then the terminal service can be accessed through the inter-process communication node of the image in the container. The implementation process can be described in detail in conjunction with the following specific implementation method.

[0057] In a specific implementation of the present application, the above step 103 may include:

[0058] Sub-step S1: when it is determined that the preset operation needs to access the inter-process communication node of the terminal, call the container client of the system instance in the target container to set the variable parameter of accessing the inter-process communication node of the terminal as an accessible parameter.

[0059] In this embodiment, when it is determined that the preset operation requires access to the inter-process communication node of the terminal, the container client of the system instance in the target container is called to set the variable parameter of the inter-process communication node of the access terminal to an accessible parameter (true).

[0060] It can be understood that within the container, the variable parameters of the inter-process communication node that accesses the terminal are inaccessible parameters (false) by default. When the inter-process communication node of the terminal needs to be accessed, the variable parameters can be set through the client service in the target container, that is, the variable parameters of the inter-process communication node that accesses the terminal are set to accessible parameters (true).

[0061] Sub-step S2: accessing the terminal service corresponding to the preset operation through the inter-process communication node of the image in the target container.

[0062] Then, the terminal service corresponding to the preset operation can be accessed through the inter-process communication node of the image in the target container. For example, when the preset operation is to open the camera application, the service of the camera application can be accessed through the inter-process communication node of the image in the target container to process the graphic data of the camera application and send it to the target screen for display.

[0063] It can be understood that the above examples are merely examples listed for a better understanding of the technical solutions of the embodiments of the present application, and are not intended to be the sole limitation to the embodiments.

[0064] The embodiment of the present application uses the inter-process communication node of the mirror terminal in the container to enable services inside and outside the container to access each other through the inter-process communication node without destroying the Docker container isolation solution.

[0065] When processing encrypted multimedia files, the processing may be performed by accessing the digital rights management service of the terminal, and the implementation process may be described in detail in conjunction with the following specific implementation manner.

[0066] In a specific implementation of the present application, the above step 103 may include:

[0067] Sub-step M1: calling the system instance in the target container to obtain the multimedia file corresponding to the preset operation.

[0068] In this embodiment, when the preset operation is to open a multimedia file (such as an audio file, a video file, a specified word file, etc.), the system instance in the target container can be called to obtain the multimedia file corresponding to the preset operation.

[0069] Sub-step M2: Access the digital rights management service through the inter-process communication node of the image in the target container, send the multimedia file to the digital rights management service, so that the digital rights management service decodes the multimedia file to obtain decoded graphic data, and transmits the decoded graphic data to the target screen for display.

[0070] Furthermore, the inter-process communication node of the image in the target container can be called to access the digital rights management service, and the multimedia file can be sent to the digital rights management service, so that the digital rights management service can decode the multimedia file, obtain the decoded graphic data, and transmit the decoded graphic data to the target screen for display. For example, the user on the target screen needs to open a video file that comes from a video platform and needs to be watched by a member. At this time, it is necessary to access the DRM service in the terminal, and the video file can be decrypted by the DRM service before it can be transmitted to the external target screen for display.

[0071] It can be understood that the above examples are merely examples listed for a better understanding of the technical solutions of the embodiments of the present application, and are not intended to be the sole limitation to the embodiments.

[0072] The timing for the Guest Android container to access the Host Android binder node can be as follows Figure 4 As shown. When creating a container, you can map the / dev / hwbinder node of the host system to / lxc / hwbinder in the container. And set global variables through the client service (client access) in the container. In actual use, you can get global variables through libhwbinder in the container. If libhwbinder gets the global variable as true, use / lxc / hwbinder, which is / dev / hwbinder of the host. At this time, you can access the DRM service of the host, and the DRM service processes the graphic data. The DRM service accesses the external screen and transmits the processed graphic data to the external screen for display.

[0073] The above process takes a Guest Android container calling process as an example, which is applicable to multiple Guest Android systems for container-host communication, and outputs the display data of different containers to different external screens.

[0074] The process for the container to access its own inter-process communication node (taking Android binder as an example) and the terminal's inter-process communication node can be as follows: Figure 3 shown.

[0075] 1. The client service in the container uses the host binder node to access the host service.

[0076] If the client program wants to access the host's hwbinder node, it needs to select the / lxc / hwbinder node when opening the binder driver. As described in the figure above, if the host DRM service and interface are accessed in the Guest android1 container, the client sets the global variable to true, and libhwbinder obtains the global variable to true (through Figure 3 Step 3: The client initiates a service call request, and through the servicemanager, goes to libhwbinder to open the binder device node to query the service. Step 4: You need to access the host device node and set the global variable to true. Step 5: libhwbinder queries the specified global variable (false by default) before opening the hwbinder node.

[0077] If the global variable is true, the host hwbinder is marked for use, and then the DRM service and interface of the host system are accessed to send the image display to the external screen 1 (after steps 7 to 11). That is, step 7: the query result is true, and the host hwbinder is marked for use. Steps 8 and 9: Access the node / lxc / hwbinder--> / dev / hwbinder mapped in the Guest android1 container through the docker service. Step 10: Access the host DRM service and interface for image processing. Step 11: Output the processed graphic data to the external screen.

[0078] 2. The client service in the container uses the binder node in the container to access the service in the container

[0079] If the Guest android1 container accesses its own services and interfaces, the client does not set the global variable (the global variable defaults to false), libhwbinder obtains the global variable as false, and accesses its own / dev / hwbinder node (through Figure 3 Step 3: The client initiates a service call request, and goes to libhwbinder through the servicemanager to open the binder device node to query the service. Step 5: Before opening the hwbinder node, libhwbinder queries the specified global variable (false by default). Step 6: Since the client does not set the global variable, the return result is false, marking the use of the hwbinder in the container.

[0080] The cloud phone-based cabin multi-screen display method provided in the embodiment of the present application creates multiple containers in the terminal and adopts container technology to control the multiple screens. The problem of multiple cabin screens being connected to an Android host at the same time is solved, and the operation of each cabin screen is independent. This solves the problem of multiple users using multiple cabin screens connected to the same hardware host device and using them at the same time, and can effectively reduce hardware costs and improve equipment utilization by sharing resources.

[0081] The following is an embodiment of the device of the present application, which can be used to execute the embodiment of the method of the present application. For details not disclosed in the embodiment of the device of the present application, please refer to the embodiment of the method of the present application.

[0082] Reference Figure 6, shows a schematic diagram of the structure of a multi-screen display device for a cabin based on a cloud phone provided by an embodiment of the present application. The multi-screen display device for a cabin based on a cloud phone can be applied to a terminal supporting docker container technology. A container corresponding to each screen is created in the terminal, and a system instance corresponding to the operating system of the terminal is run in the container. An inter-process communication node corresponding to the operating system is mirrored in each container. Figure 6 As shown, the cabin multi-screen display device 600 based on cloud phone may include the following modules:

[0083] A preset operation acquisition module 610 is used to call a system instance in a target container to acquire a preset operation performed by a user on a target screen of the multi-screen, wherein the target container is a container created in the terminal and corresponding to the target screen;

[0084] A preset operation determination module 620, used to determine whether the preset operation requires access to an inter-process communication node of the terminal;

[0085] The terminal service access module 630 is used to access the terminal service corresponding to the preset operation through the inter-process communication node of the image in the target container when it is determined that the preset operation needs to access the inter-process communication node of the terminal, so that the terminal service can process the graphic data corresponding to the preset operation and transmit the processed graphic data to the target screen for display.

[0086] Optionally, the terminal service access module includes:

[0087] a variable parameter setting unit, configured to, when determining that the preset operation requires access to an inter-process communication node of the terminal, call a container client of the system instance in the target container to set a variable parameter of the inter-process communication node accessing the terminal as an accessible parameter;

[0088] The terminal service access unit is used to access the terminal service corresponding to the preset operation through the inter-process communication node of the image in the target container.

[0089] Optionally, the device further comprises:

[0090] a variable parameter acquisition module, configured to, when it is determined that the preset operation does not require access to the inter-process communication node of the terminal, call the container client of the system instance in the target container to acquire the variable parameters for accessing the inter-process communication node of the terminal;

[0091] A container service access module is used to access the container service corresponding to the preset operation through a container inter-process communication node pre-created in the target container when the variable parameter is an inaccessible parameter, so that the container service processes the graphic data corresponding to the preset operation and transmits the processed graphic data to the target screen for display.

[0092] Optionally, the digital rights management service of the system layer of the operating system is not running in any of the multiple containers in the terminal.

[0093] The preset operation determination module includes:

[0094] A judgment result obtaining unit, used to judge whether the graphic data corresponding to the preset operation needs to be processed by the digital rights management service, and obtain a judgment result;

[0095] The preset operation determining unit is used to determine whether the preset operation needs to access the inter-process communication node of the terminal according to the judgment result.

[0096] Optionally, the terminal service access module includes:

[0097] A multimedia file acquisition unit, used for calling the system instance in the target container to acquire the multimedia file corresponding to the preset operation;

[0098] A management service access unit is used to access the digital rights management service through the inter-process communication node of the image in the target container, send the multimedia file to the digital rights management service, so that the digital rights management service decodes the multimedia file to obtain decoded graphic data, and transmit the decoded graphic data to the target screen for display.

[0099] Optionally, the device further comprises:

[0100] A closing operation monitoring module, used for calling the system instance in the target container to monitor the closing operation of the graphic data on the target screen;

[0101] The access connection disconnection module is used to disconnect the inter-process communication node access connection with the image in the target container in response to a closing operation on the graphic data.

[0102] The cloud phone-based cabin multi-screen display device provided in the embodiment of the present application creates multiple containers in the terminal and adopts container technology to control the multiple screens. The problem of multiple cabin screens being simultaneously connected to an Android host is solved, and the operation of each cabin screen is independent. This solves the problem of multiple users using multiple cabin screens connected to the same hardware host device and using them at the same time, and can effectively reduce hardware costs and improve equipment utilization by sharing resources.

[0103] It should be noted that the device provided in the above embodiment, when implementing its functions, is only illustrated by the division of the above functional modules. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the device and method embodiments provided in the above embodiment belong to the same concept, and the specific implementation process is detailed in the method embodiment, which will not be repeated here.

[0104] In an exemplary embodiment, an electronic device is also provided, the electronic device comprising a processor and a memory, wherein the memory stores at least one instruction, at least one program, code set or instruction set. The at least one instruction, at least one program, code set or instruction set is configured to be executed by one or more processors to implement the above-mentioned cloud phone-based cabin multi-screen display method.

[0105] Please refer to Figure 7 , which shows a structural block diagram of an electronic device provided by an embodiment of the present application. The electronic device can be used to implement the cabin multi-screen display method based on cloud mobile phone provided in the above embodiment. The electronic device can be a PC or a server, or other devices with data processing and storage capabilities. Specifically:

[0106] The electronic device 700 includes a central processing unit (CPU) 701, a system memory 704 including a random access memory (RAM) 702 and a read-only memory (ROM) 703, and a system bus 705 connecting the system memory 704 and the central processing unit 701. The electronic device 700 also includes a basic input / output system (I / O system) 706 that helps to transfer information between various components in the computer, and a large-capacity storage device 707 for storing an operating system 713, application programs 714, and other program modules 715.

[0107] The basic input / output system 706 includes a display 708 for displaying information and an input device 709 such as a mouse and a keyboard for user inputting information. The display 708 and the input device 709 are connected to the central processing unit 701 through an input / output controller 710 connected to the system bus 705. The basic input / output system 1006 may also include an input / output controller 710 for receiving and processing inputs from a plurality of other devices such as a keyboard, a mouse, or an electronic stylus. Similarly, the input / output controller 710 also provides output to a display screen, a printer, or other types of output devices.

[0108] The mass storage device 707 is connected to the central processing unit 701 through a mass storage controller (not shown) connected to the system bus 705. The mass storage device 707 and its associated computer-readable medium provide non-volatile storage for the electronic device 700. That is, the mass storage device 707 may include a computer-readable medium (not shown) such as a hard disk or a CD-ROM drive.

[0109] Without loss of generality, the computer readable medium may include computer storage media and communication media. Computer storage media include volatile and non-volatile, removable and non-removable media implemented by any method or technology for storing information such as computer readable instructions, data structures, program modules or other data. Computer storage media include RAM, ROM, EPROM, EEPROM, flash memory or other solid-state memory technology, CD-ROM, DVD or other optical storage, tape cassettes, magnetic tapes, disk storage or other magnetic storage devices. Of course, those skilled in the art will appreciate that the computer storage media is not limited to the above. The above-mentioned system memory 704 and mass storage device 707 can be collectively referred to as memory.

[0110] According to various embodiments of the present application, the electronic device 700 can also be connected to a remote computer on the network through a network such as the Internet. That is, the electronic device 700 can be connected to the network 712 through the network interface unit 711 connected to the system bus 705, or the network interface unit 711 can also be used to connect to other types of networks or remote computer systems (not shown).

[0111] The memory further includes one or more programs, which are stored in the memory and configured to be executed by one or more processors. The one or more programs include instructions for executing the above-mentioned cloud phone-based cabin multi-screen display method.

[0112] In an exemplary embodiment, a computer-readable storage medium is also provided, in which at least one instruction, at least one program, a code set or an instruction set is stored. When the at least one instruction, the at least one program, the code set or the instruction set is executed by a processor of an electronic device, the at least one instruction, the at least one program, the code set or the instruction set implements the above-mentioned cloud phone-based cabin multi-screen display method.

[0113] Optionally, the computer-readable storage medium may be a ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.

[0114] In an exemplary embodiment, a computer program product is also provided. When the computer program product is executed, it is used to implement the above-mentioned cloud phone-based cabin multi-screen display method.

[0115] It should be understood that the "plurality" mentioned in this article refers to two or more. "And / or" describes the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects are in an "or" relationship.

[0116] The above description is only an exemplary embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the protection scope of the present application.

Claims

1. A method for displaying multiple screens in a cabin based on a cloud phone, characterized in that: Applied to a terminal supporting docker container technology, a container corresponding to each screen is created in the terminal, a system instance corresponding to the operating system of the terminal is run in the container, and an inter-process communication node corresponding to the operating system is mirrored in each container, the method includes: Calling a system instance in a target container to obtain a preset operation performed by a user on a target screen of the multi-screen, wherein the target container is a container created in the terminal and corresponding to the target screen; Determining whether the preset operation requires access to an inter-process communication node of the terminal; When it is determined that the preset operation requires access to the inter-process communication node of the terminal, the terminal service corresponding to the preset operation is accessed through the inter-process communication node of the image in the target container, so that the terminal service processes the graphic data corresponding to the preset operation and transmits the processed graphic data to the target screen for display.

2. The method according to claim 1, characterized in that In the case where it is determined that the preset operation needs to access the inter-process communication node of the terminal, accessing the terminal service corresponding to the preset operation through the inter-process communication node of the image in the target container includes: In a case where it is determined that the preset operation requires access to an inter-process communication node of the terminal, calling a container client of the system instance in the target container to set a variable parameter for accessing the inter-process communication node of the terminal as an accessible parameter; The terminal service corresponding to the preset operation is accessed through the inter-process communication node of the image in the target container.

3. The method according to claim 1, characterized in that After determining whether the preset operation requires access to the inter-process communication node of the terminal, the method further includes: In a case where it is determined that the preset operation does not need to access the inter-process communication node of the terminal, calling a container client of the system instance in the target container to obtain variable parameters for accessing the inter-process communication node of the terminal; When the variable parameter is an inaccessible parameter, the container service corresponding to the preset operation is accessed through the container inter-process communication node pre-created in the target container, so that the container service processes the graphic data corresponding to the preset operation and transmits the processed graphic data to the target screen for display.

4. The method according to claim 1, characterized in that: The digital rights management service of the system layer of the operating system is not running in any of the multiple containers in the terminal. The determining whether the preset operation requires access to an inter-process communication node of the terminal includes: Determine whether the graphic data corresponding to the preset operation needs to be processed by a digital rights management service, and obtain a determination result; According to the judgment result, it is determined whether the preset operation requires access to an inter-process communication node of the terminal.

5. The method according to claim 4, characterized in that The accessing of the terminal service corresponding to the preset operation through the inter-process communication node mirrored in the target container, so that the terminal service processes the graphic data corresponding to the preset operation, and transmits the processed graphic data to the target screen for display, includes: Calling the system instance in the target container to obtain the multimedia file corresponding to the preset operation; The digital rights management service is accessed through an inter-process communication node of the image in the target container, and the multimedia file is sent to the digital rights management service, so that the digital rights management service decodes the multimedia file to obtain decoded graphic data, and transmits the decoded graphic data to the target screen for display.

6. The method according to claim 1, characterized in that After accessing the terminal service corresponding to the preset operation through the inter-process communication node of the image in the target container, the method further includes: Calling the system instance in the target container to monitor a closing operation of the graphic data on the target screen; In response to a closing operation on the graphic data, an inter-process communication node access connection with the image in the target container is disconnected.

7. A multi-screen display device in a cabin based on a cloud phone, characterized in that: Applied to a terminal supporting docker container technology, a container corresponding to each screen is created in the terminal, a system instance corresponding to the operating system of the terminal is run in the container, and an inter-process communication node corresponding to the operating system is mirrored in each container. The device includes: A preset operation acquisition module, used to call a system instance in a target container to acquire a preset operation performed by a user on a target screen of the multi-screen, wherein the target container is a container created in the terminal and corresponding to the target screen; A preset operation determination module, used to determine whether the preset operation requires access to an inter-process communication node of the terminal; A terminal service access module is used to access the terminal service corresponding to the preset operation through the inter-process communication node of the image in the target container when it is determined that the preset operation needs to access the inter-process communication node of the terminal, so that the terminal service processes the graphic data corresponding to the preset operation and transmits the processed graphic data to the target screen for display.

8. A computer program product, characterized in that When the computer program product is executed, it is used to perform the method according to any one of claims 1 to 6.

9. An electronic device, characterized in that: The electronic device includes a processor and a memory, wherein the memory stores at least one instruction, at least one program, a code set or an instruction set, and the at least one instruction, the at least one program, the code set or the instruction set is loaded and executed by the processor to implement the method according to any one of claims 1 to 6.

10. A computer-readable storage medium, characterized in that: The storage medium stores at least one instruction, at least one program, a code set or an instruction set, and the at least one instruction, the at least one program, the code set or the instruction set is loaded and executed by the processor to implement the method according to any one of claims 1 to 6.