A display device and a dual-system control method

Abstract

This application provides a display device and a dual-system control method. When the user interface includes a second system interface, the method, in response to a startup command from a first system interface, detects a first display area of ​​the first system interface and sets a first touch marker value for the pixels in the first display area. When the user interface includes the first system interface, in response to a startup command from a second system interface, it detects a second display area of ​​the second system interface and sets a second touch marker value for the pixels in the second display area. The first touch marker value indicates the display area where the touch permissions of the first system are active, and the second touch marker value indicates the display area where the touch permissions of the second system are active. This method can control the touch permissions of the dual systems on the display device according to the display area of ​​the system interface, enabling the touch permissions of the two systems to coexist without conflict, thus improving the convenience and accuracy of user operation.

Description

Technical Field

[0001] This application relates to the field of display device technology, and in particular to a display device and a dual-system control method. Background Technology

[0002] Display devices refer to terminal devices capable of outputting specific display images, such as smart TVs, communication terminals, smart advertising screens, and projectors. Taking smart TVs as an example, smart TVs are television products based on Internet application technology, possessing open operating systems and chips, and having open application platforms. They enable two-way human-computer interaction and integrate multiple functions such as audio-visual, entertainment, and data to meet diverse and personalized user needs.

[0003] The display device supports dual systems, allowing two operating systems to be integrated into the device. For example, an Android touchscreen can be paired with a Windows system, enabling touch operations on both systems. To ensure that touch permissions for both systems coexist without conflict, touch permissions for the second system can be enabled or disabled based on whether the first system's interface is overlaid on the second system's signal source display channel.

[0004] However, in actual use, touch permission conflicts still exist in some scenarios. For example, when the sidebars at both ends of the Android touchscreen are expanded, the touch permissions of the running Windows system are disabled. When the Android sidebar collapses into arrows, the touch permissions of the Windows system are enabled, but clicking the arrows will still trigger a touch response in the corresponding area of ​​the Windows system. Another example is that Android's on-screen display (OSD) supports dragging. During OSD menu dragging, a dragging trajectory is visible in the corresponding area of ​​the Windows system. Although the Android system can detect OSD menu presses and disable Windows touch permissions, thus blocking some dragging data, the Windows system can still receive the pressed touch actions. Summary of the Invention

[0005] This application provides a display device and a dual-system control method to solve the problem of conflicting touch permissions in dual systems.

[0006] In a first aspect, some embodiments of this application provide a display device, including a display and a first controller. The display is configured to display a user interface, and is connected to a touch interaction module for receiving touch commands input by a user. The first controller is used to run a first system to control the display to display a first system interface. The first controller is connected to a second controller, which runs a second system to control the display to display a second system interface. The first controller is configured to execute the following program steps:

[0007] When the user interface includes a second system interface, in response to the start command of the first system interface, the first display area of ​​the first system interface is detected;

[0008] A first touch marker value is set for the pixels in the first display area, and the first touch marker value is used to indicate the display area where the touch permission of the first system is applied;

[0009] When the user interface includes a first system interface, in response to the start command of the second system interface, the second display area of ​​the second system interface is detected;

[0010] A second touch marker value is set for the pixels of the second display area. The second touch marker value is used to indicate the display area where the touch permission of the second system is applied.

[0011] Secondly, this application also provides a dual-system control method applied to the above-mentioned display device, comprising:

[0012] When the user interface includes a second system interface, in response to the start command of the first system interface, the first display area of ​​the first system interface is detected;

[0013] A first touch marker value is set for the pixels in the first display area, and the first touch marker value is used to indicate the display area where the touch permission of the first system is applied;

[0014] When the user interface includes a first system interface, in response to the start command of the second system interface, the second display area of ​​the second system interface is detected, and the second system interface is a window interface based on the second system.

[0015] A second touch marker value is set for the pixels of the second display area. The second touch marker value is used to indicate the display area where the touch permission of the second system is applied.

[0016] As can be seen from the above technical solutions, this application provides a display device and a dual-system control method. When the user interface includes a second system interface, the method, in response to a startup command from the first system interface, detects a first display area of ​​the first system interface and sets a first touch marker value for the pixels in the first display area. When the user interface includes the first system interface, in response to a startup command from the second system interface, it detects a second display area of ​​the second system interface and sets a second touch marker value for the pixels in the second display area. The first touch marker value indicates the display area where the touch permissions of the first system are active, and the second touch marker value indicates the display area where the touch permissions of the second system are active. This method can control the touch permissions of the dual systems on the display device according to the display area of ​​the system interface, achieving coexistence and non-conflict of touch permissions between the two systems, thus improving the convenience and accuracy of user operation. Attached Figure Description

[0017] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 A schematic diagram illustrating the usage scenarios of the display device provided in some embodiments of this application;

[0019] Figure 2 This is a schematic diagram of the hardware configuration of a display device provided in some embodiments of this application;

[0020] Figure 3 This is a schematic diagram illustrating the connection relationship of external terminal devices provided in some embodiments of this application;

[0021] Figure 4 This is a schematic diagram of the hardware configuration of the control device provided in some embodiments of this application;

[0022] Figure 5 This is a schematic diagram of the software configuration of a display device provided in some embodiments of this application;

[0023] Figure 6 This is a hierarchical diagram of a dual system provided for some embodiments of this application;

[0024] Figure 7 A schematic diagram of the sidebar expansion interface in a dual system provided in some embodiments of this application;

[0025] Figure 8 A schematic diagram of an interface in a dual system provided by some embodiments of this application, showing the sidebar collapsing into an arrow;

[0026] Figure 9 A schematic diagram of a menu dragging interface in a dual-system provided for some embodiments of this application;

[0027] Figure 10 A schematic diagram of the touch control flow of the first system interface under the second system provided in some embodiments of this application;

[0028] Figure 11 A schematic diagram of the interface of the first system launched under the second system provided in some embodiments of this application;

[0029] Figure 12 A schematic diagram illustrating the simultaneous startup of multiple first system interfaces under a second system, provided for some embodiments of this application;

[0030] Figure 13 A flowchart illustrating the execution of touch commands provided for some embodiments of this application;

[0031] Figure 14 A schematic diagram of the touch control flow of the second system interface under the first system provided in some embodiments of this application;

[0032] Figure 15 A schematic diagram of the second system interface launched under the first system provided in some embodiments of this application;

[0033] Figure 16 The diagram shows an interface diagram in which the first system interface and the second system interface overlap in some embodiments of this application. Detailed Implementation

[0034] The embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described below do not represent all embodiments consistent with this application. They are merely examples of systems and methods consistent with some aspects of this application as detailed in the claims.

[0035] It should be noted that the brief descriptions of terms in this application are only for the convenience of understanding the embodiments described below, and are not intended to limit the embodiments of this application. Unless otherwise stated, these terms should be understood in their ordinary and common meaning.

[0036] The terms "first," "second," "third," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar or related objects or entities, and do not necessarily imply a specific order or sequence, unless otherwise specified. It should be understood that such terms are interchangeable where appropriate.

[0037] The terms “comprising” and “having”, and any variations thereof, are intended to cover but not exclude inclusion, for example, a product or device that includes a range of components is not necessarily limited to all of the components that are clearly listed, but may include other components that are not clearly listed or that are inherent to such product or device.

[0038] The term "module" refers to any known or subsequently developed hardware, software, firmware, artificial intelligence, fuzzy logic, or combination of hardware and / or software code that is capable of performing the functions associated with that element.

[0039] Figure 1 This is a schematic diagram illustrating an operational scenario between a display device and a control device provided in some embodiments of this application. For example... Figure 1 As shown, the user can operate the display device 200 through the mobile terminal 300 and the control device 100.

[0040] In some embodiments, the mobile terminal 300 may install software applications with the display device 200 to establish a connection and communication via a network communication protocol, thereby achieving one-to-one control operation and data communication. Alternatively, audio and video content displayed on the mobile terminal 300 can be transmitted to the display device 200 to achieve synchronous display.

[0041] like Figure 1 The diagram also shows that the display device 200 communicates with the server 400 via various communication methods. This allows the display device 200 to communicate via a local area network (LAN), a wireless local area network (WLAN), and other networks.

[0042] In addition to providing broadcast television reception functions, the display device 200 can also be equipped with intelligent network television functions that provide computer support, including but not limited to network television, smart television, Internet Protocol television (IPTV), etc.

[0043] Figure 2 Provided for some embodiments of this application Figure 1 Hardware configuration block diagram of display device 200.

[0044] In some embodiments, the display device 200 includes at least one of a tuner 210, a communicator 220, a detector 230, a device interface 240, a controller 250, a display 260, an audio output interface 270, a memory, a power supply, and a communication device interface 280.

[0045] In some embodiments, detector 230 is used to acquire signals from the external environment or to interact with the outside world. For example, detector 230 includes a light receiver, a sensor for acquiring ambient light intensity; or, detector 230 includes an image acquisition device, such as a camera, which can be used to acquire external environmental scenes, user attributes, or user interaction gestures; or, detector 230 includes a sound acquisition device, such as a microphone, for receiving external sounds.

[0046] In some embodiments, the display 260 includes a display screen component for presenting an image, a driving component for driving image display, a component for receiving image signals output from a controller, and a user control UI interface, etc.

[0047] The display 260 can be an LCD display, an OLED display, or a projection display, and can also be a projection device and a projection screen.

[0048] In some embodiments, the display device 200 may also support touch interaction, that is, a touch interaction module may be provided on the display device 200, which may be a built-in module or an external module. For example, to realize touch interaction operation, the display 260 of the display device 200 may be provided with a touch panel (TP), which can receive touch signals input from fingers, touch points, styluses, etc., and execute touch interaction responses according to a pre-set interaction strategy. Of course, the display device 200 may also be a touch-screen integrated display.

[0049] In some embodiments, the communicator 220 is a component used to communicate with external devices or the server 400 according to various communication protocol types. For example, the communicator may include at least one of a Wi-Fi module, a Bluetooth module, a wired Ethernet module, other network communication protocol chips or near-field communication protocol chips, and an infrared receiver. The display device 200 can establish the transmission and reception of control signals and data signals with the control device 100 or the server 400 through the communicator 220.

[0050] In some embodiments, the controller 250 includes a processor, a video processor, an audio processor, a graphics processor, RAM, ROM, and a first to an nth interface for input / output. The controller 250 controls the operation of the display device and responds to user operations through various software control programs stored in the memory. The controller 250 controls the overall operation of the display device 200. For example, in response to receiving a user command to select a UI object to display on the display 260, the controller 250 can perform operations related to the object selected by the user command.

[0051] In some embodiments, detector 230 is used to acquire signals from the external environment or to interact with the outside world. For example, detector 230 includes a light receiver, a sensor for acquiring ambient light intensity; or, detector 230 includes an image acquisition device, such as a camera, which can be used to acquire external environmental scenes, user attributes, or user interaction gestures; or, detector 230 includes a sound acquisition device, such as a microphone, for receiving external sounds.

[0052] In some embodiments, the device interface 240 may include, but is not limited to, one or more interfaces such as: High Definition Multimedia Interface (HDMI), analog or data high-definition component input interface (component), composite video input interface (CVBS), USB input interface (USB), RGB port, etc. It may also be a composite input / output interface formed by multiple interfaces mentioned above.

[0053] For example, to enrich the display types of display device 200, the HDMI interface can connect to devices with video and audio input / output functions, and implement the corresponding audio and video output / input functions through the HDMI driver in the hardware layer. The USB interface can connect to devices with signal and data transmission functions and interactive functions, and, based on the USB driver in the hardware layer, access signals, transmit data, and perform specific interactive actions.

[0054] In some embodiments, the display device 200 can support multiple interface connections and perform corresponding functions according to the specific device type connected. For example, the display device 200 can connect to another monitor or terminal device 500 via an HDMI interface to form dual-screen, split-screen, screen sharing, conferencing, whiteboard, NFC, and other display functions. The display device 200 can also connect to the terminal device 500 via a USB interface and activate the Open Pluggable Specification (OPS) channel to connect the external terminal device 500. When connecting the terminal device 500 via the OPS channel, since the display device 200 has an independent operating system (System A) and the terminal device 500 can also have an independent operating system (System B), a dual-system mode can be formed.

[0055] In some embodiments, both the display device 200 and / or the connected terminal device 500 can support touch interaction. When both the display device 200 and the connected terminal device 500 support touch interaction, a data transmission and conversion module can be set in the display device 200 to transmit and convert the touch data generated during the touch interaction process, thereby achieving channel reverse control, that is, controlling the display device 200 through the touch-interactive terminal device 500. For example, as... Figure 3As shown, a switch module can be set up in the touch interaction system. The TP module with touch functionality can be connected to the main control system (system A) of the display device 200 via a USB interface, and can also be connected to the terminal device 500 (system B), an external host, and a type-C device. In this way, the OPS channel formed by the HDMI interface can transmit display content data, and the switch module and USB interface can transmit touch data.

[0056] In some embodiments, the tuner 210 receives broadcast television signals via wired or wireless reception and demodulates audio and video signals, such as EPG data signals, from a plurality of wireless or wired broadcast television signals.

[0057] In some embodiments, the controller 250 and the tuner 210 may be located in different separate devices, that is, the tuner 210 may also be located in an external device of the main device where the controller 250 is located, such as an external set-top box.

[0058] In some embodiments, the user can input user commands through a graphical user interface (GUI) displayed on the display 260, and the user input interface receives the user input commands through the graphical user interface (GUI). Alternatively, the user can input user commands by inputting specific sounds or gestures, and the user input interface receives the user input commands by recognizing the sounds or gestures through sensors.

[0059] In some embodiments, the communication device interface 280 is an interface that can be used to receive control input.

[0060] Figure 4 Provided for some embodiments of this application Figure 1 Hardware configuration block diagram of the central control device. (Example) Figure 4 As shown, the control device 100 includes a controller 110, a communication interface 130, a user input / output interface, a memory 190, and a power supply 180.

[0061] The control device 100 is configured to control the display device 200, and to receive user input operation commands and convert the operation commands into commands that the display device 200 can recognize and respond to, thus acting as an intermediary for interaction between the user and the display device 200.

[0062] In some embodiments, the control device 100 may be an intelligent device. For example, the control device 100 may be equipped with various applications for controlling the display device 200 according to user needs.

[0063] In some embodiments, such as Figure 1As shown, the mobile terminal 300 or other smart electronic devices can perform similar functions to the control device 100 after installing the application of the control display device 200.

[0064] The controller 110 includes a processor 112, RAM 113, ROM 114, a communication interface 130, and a communication bus. The controller 110 is used to control the operation of the control device 100, as well as the communication and cooperation between internal components and the external and internal data processing functions.

[0065] Under the control of the controller 110, the communication interface 130 enables communication of control signals and data signals with the display device 200. The communication interface 130 may include at least one of other near-field communication modules such as WiFi chip 131, Bluetooth module 132, and NFC module 133.

[0066] User input / output interface 140, wherein the input interface includes at least one of other input interfaces such as microphone 141, touchpad 142, sensor 143, button 144, etc.

[0067] In some embodiments, the control device 100 includes at least one of a communication interface 130 and an input / output interface 140. The control device 100 is configured with the communication interface 130, such as a WiFi, Bluetooth, or NFC module, which can encode user input commands via WiFi, Bluetooth, or NFC protocols and send them to the display device 200.

[0068] The memory 190 is used to store various operating programs, data, and applications for driving and controlling the control device 100 under the control of the controller. The memory 190 can also store various control signal instructions input by the user.

[0069] The power supply 180 is used to provide operating power support for the various components of the control device 100 under the control of the controller.

[0070] Figure 5 Provided for some embodiments of this application Figure 1 The diagram shows the software configuration of the display device. In some embodiments, the system of the display device 200 can be divided into three layers, from top to bottom: the application layer, the middleware layer, and the hardware layer.

[0071] The application layer mainly includes commonly used applications on TVs, as well as the application framework. The commonly used applications are mainly browser-based applications, such as HTML5 apps, and native apps.

[0072] An application framework is a complete program model that has all the basic functions required by standard application software, such as file access, data exchange, and the user interface for these functions (toolbar, status bar, menu, dialog box).

[0073] Native apps can support online or offline access, push notifications, or access to local resources.

[0074] The middleware layer includes various television protocols, multimedia protocols, and system components. Middleware can use the basic services (functions) provided by system software to connect different parts of application systems or different applications on the network, achieving resource sharing and function sharing.

[0075] The hardware layer mainly includes the Hardware Abstraction Layer (HAL) interface, hardware, and drivers. The HAL interface serves as a unified interface for all TV chips, with the specific logic implemented by each individual chip. Drivers primarily include: audio drivers, display drivers, Bluetooth drivers, camera drivers, Wi-Fi drivers, USB drivers, HDMI drivers, sensor drivers (such as fingerprint sensors, temperature sensors, and pressure sensors), and power drivers.

[0076] The aforementioned display device 200 can run two operating systems to form a dual-system configuration. For example, an Android touchscreen can run a Windows system. The touchscreen can also run other operating systems, such as HarmonyOS, and the Windows system can be a different system. The Windows system can be an OPS module built into the touchscreen or an external computer module connected via a cable that supports touch data transmission.

[0077] In some embodiments, such as Figure 6 The diagram shown is a hierarchical diagram of the dual system provided in this application embodiment. In the dual system of the display device 200, the first system is at the level of the second system. To ensure that the touch permissions of the two systems coexist and do not conflict with each other, when the display device 200 controls the touch permissions of the dual systems, it can control the on / off state of the touch permissions of the second system based on whether the interface of the first system is superimposed on the upper layer of the second system and the signal source display channel of the second system.

[0078] For example, display device 200 is a touchscreen display running Android, with a Windows system running on top, forming a dual-system setup. The Windows system is the OPS module inside the touchscreen display, input through the OPS signal source channel and displayed on the touchscreen display. If the Windows system signal is displayed under the OPS signal source channel and there is no Android system OSD interface covering it, then the touch permission of the OPS module is enabled, allowing the user to perform touch operations on the Windows system interface. Otherwise, the touch permission of the OPS module is disabled, and touch operations are performed on the Android system interface above it, thus solving the problem of simultaneous touch response from both systems and reducing accidental operations.

[0079] In other words, the method of distributing touch data in the second system at the bottom layer of the display device 200 is controlled by the signal source access of the second system and whether the interface of the first system is superimposed on the upper layer of the second system. When the signal source of the second system is connected to the display device 200, if the interface of the first system is not superimposed on the upper layer of the second system, the touch permission of the second system is enabled, and the second system responds to the user's touch operations in the user interface. If the interface of the first system is superimposed on the upper layer of the second system, the touch permission of the second system is disabled, and the first system responds to the user's touch operations in the user interface.

[0080] Understandably, when a user inputs a touch command through the touch interaction module of the display device 200, the touch interaction module receives the touch data generated by the touch command. This touch data is then passed up the hardware layer of the display device 200 to the application layer, and the application layer executes the touch interaction response based on the pre-set interaction strategy according to the operating system. Finally, the user interface obtained in response to the touch command is presented to the user.

[0081] For a dual-system setup, where a first system and a second system are integrated on the display device 200, the controller 250 of the display device 200 acts as the first controller, running the first system. An external controller acts as the second controller, running the second system. To ensure that the touch permissions of the first and second systems coexist without conflict, their touch permissions need to be configured. Since the first and second systems are integrated on the display device 200, touch data is transmitted sequentially upwards from the hardware layer of the display device 200, each sent to the first and second systems through its respective data channels. To disable the touch permissions of a particular system, its corresponding data channel is closed. For example, an Android touchscreen display may integrate a Windows system, forming a dual-system setup. The Windows system is the OPS module within the touchscreen display. Disabling the touch permissions of the Windows system disables the touch data distribution through the interface channel of the OPS module, preventing the Android touchscreen display from sending data to the OPS module.

[0082] However, the aforementioned dual-system touch control method still suffers from touch permission conflicts in some scenarios during actual use. For example, ... Figure 7 , 8 As shown, Figure 7 This is a schematic diagram of the sidebar expanded in the dual-system provided in the application embodiment. Figure 8 This is a schematic diagram of an interface where the sidebars are collapsed into arrows in a dual-system configuration provided in the application embodiment. Taking the aforementioned display device 200 as an example of a dual-system configuration consisting of an Android touchscreen display and a Windows system running on it. When the sidebars at both ends of the touchscreen display are expanded, touch data distribution of the OPS module inside the touchscreen display is disabled. After the sidebars at both ends of the touchscreen display are collapsed into arrows, touch data distribution of the OPS module is enabled. At this time, if the user clicks on the arrow portion through a specific interactive action, the corresponding location in the Windows system will also respond to the touch, causing a touch conflict.

[0083] If the arrows on the Android system's touchscreen were replaced with larger OSD menus, the touchscreen would affect a larger area of ​​the Windows system.

[0084] For example, such as Figure 9The diagram illustrates the menu dragging interface in the dual-system configuration provided in the application embodiment. The Android system's on-screen display (OSD) supports dragging. When a user drags the OSD menu using specific actions, the Windows system also receives the dragging action, resulting in a dragging trajectory at the corresponding position on the Windows system during the OSD menu dragging process. Therefore, the Android system can detect OSD menu press actions, and when a press action is detected, the Windows system's touch permissions are disabled. This method can block some dragging data, but the Windows system can still receive press touch actions.

[0085] To address the conflicting touch permissions in dual systems, some embodiments of this application also provide a dual-system control method applied to a display device 200. This method controls the touch permissions of the dual systems mounted on the display device 200, enabling the touch permissions of the two systems to coexist without conflict. The display device 200, to which the dual-system control method can be applied, includes a display 260, a first controller, and a second controller. The display 260 is configured to display a user interface and is connected to a touch interaction module. The touch interaction module receives touch commands input by the user. The first controller can be the display device 200's own controller 250, used to run the first system to control the display 260 to display the first system interface. The second controller can be an external controller of the display device 200, connected to the first controller. The second controller runs the second system to control the display 260 to display the second system interface; the first controller is configured to execute the aforementioned dual-system control method.

[0086] To achieve coexistence and non-conflict of touch permissions in both systems, the dual-system control method provided in this application includes touch permission control of the first system interface under the second system and touch permission control of the second system interface under the first system. For touch permission control of the first system interface under the second system, touch permissions for the corresponding area of ​​the second system can be disabled based on the display area of ​​the first system interface at startup. For touch permission control of the second system interface under the first system, touch permissions for the corresponding area of ​​the second system can be enabled based on the display area of ​​the second system interface at startup.

[0087] The system consists of two interfaces: a first system interface (windows based on the first system) and a second system interface (windows based on the second system). This means that touch permissions for both systems are controlled in separate zones. When the first system interface is launched from the top layer of the second system, touch permissions for the display area of ​​the first system interface from the second system are disabled. Conversely, when the second system interface is launched from the top layer of the first system, touch permissions for the display area of ​​the second system interface from the second system are enabled, allowing touch permissions to coexist without conflict between the two systems.

[0088] To enable and disable touch permissions for different display areas, attribute values ​​representing touch permissions can be assigned to pixels within those areas. For display areas representing the first system's touch permission, a first touch marker value can be set for the pixels within that area. For display areas representing the second system's touch permission, a second touch marker value can be set for the pixels within that area. When a user inputs a touch command, the display device 200 can detect the touch location and, based on the touch permission attribute value of the area where the touch location is located, execute the corresponding system's touch operation.

[0089] The first controller of the display device 200 can respond to touch commands input by the user, detect the touch point position of the touch command, and if the pixel at the touch point position is a first touch marker value, control the first system to execute the touch command. If the pixel at the touch point position is a second touch marker value, send a touch command to the second controller so that the second controller controls the second system to execute the touch command.

[0090] It is understood that the embodiments of this application do not specifically limit the first touch mark value and the second touch mark value, and can be set according to actual needs. For example, the first touch mark value can be represented by the number "0", and the second touch mark value can be represented by the number "1".

[0091] like Figure 10 As shown, Figure 10 This is a schematic diagram of the touch control flow of the first system interface under the second system in this application embodiment, which specifically includes the following:

[0092] S101: When the user interface includes a second system interface, in response to the startup command of the first system interface, the first display area of ​​the first system interface is detected.

[0093] S102: Set the first touch marker value for the pixels in the first display area.

[0094] The first touch marker value is used to indicate the area where the touch permissions of the first system are effective. When the interface of the first system is launched under the second system, the display device 200 can obtain the first display area of ​​the first system interface and set the first touch marker value for the pixels of the first display area, indicating that the first display area is the display area where the touch permissions of the first system are effective, so that the first display area can only perform touch operations of the first system and cannot perform touch operations of the second system.

[0095] For example, such as Figure 11 The diagram shown is a schematic of the first system interface launched under the second system provided in this application embodiment. The display device 200 is a touch screen display of the Android system, on which a Windows system is installed to form a dual system. Under the Windows system, the first system interface A is launched. The first display area corresponding to the first system interface A is obtained, the pixels of the first display area are traversed, and the first touch mark value "0" is set for the pixels of the first display area, indicating that the first display area is the display area under the touch permission of the Android system, so that the first system interface A can only perform touch operations of the Android system, while other display areas not covered by the first system interface A can still perform touch operations of the Windows system.

[0096] In some embodiments, the display device 200 can detect a first interface state of a first system interface. The first interface state includes a full-screen state and a non-full-screen state. If the first interface state is full-screen and there is no second system interface above the first system interface, the data channel between the first controller and the second controller is closed, preventing the first controller from sending data to the second controller. If the first interface state is non-full-screen, the step of detecting a first display area of ​​the first system interface is performed.

[0097] In other words, if the window interface launched by the first system is full-screen and no window interface of the second system is displayed, then the touch permissions of the second system are disabled. If the window interface launched by the first system is not full-screen, then the display area of ​​the window interface is detected, and only the touch permissions of the second system for that display area are disabled.

[0098] For example, an Android touchscreen display can be equipped with a Windows system, forming a dual-system setup. The Windows system is the OPS module inside the touchscreen display. When the first system's window is full-screen and no second system window is displayed, the touch data distribution through the OPS module's interface channel is directly shut down, and no data is sent to the OPS module.

[0099] In some embodiments, multiple first system interfaces may be launched simultaneously. In such cases, the display device 200 may, in response to the launch command of the multiple first system interfaces, detect the first display areas of the multiple first system interfaces. A union operation is performed on the multiple first display areas to obtain a union region of all the first display areas. A first touch marker value is set for the pixels in the union region.

[0100] For example, such as Figure 12 The diagram illustrates the simultaneous launch of multiple first system interfaces under a second system provided in this embodiment. The display device 200 is a touchscreen display of an Android system, running a Windows system to form a dual system. Under the Windows system, first system interface A and first system interface B are launched simultaneously. The first display area corresponding to first system interface A is area A, and the first display area corresponding to first system interface B is area B. The union of areas A and B is taken, and the pixels of this union area are set to the first touch marker value "0" to indicate that this first display area is the display area subject to touch permissions of the Android system.

[0101] In some embodiments, since the first system in the display device 200 can support the simultaneous launch of multiple applications, or the launch of multiple interfaces of the same application, the display device 200 can create a disabled touch list to store the disabled areas, i.e., the display areas where the touch permissions of the second system are applied, in order to facilitate the recording of the display areas affected by the touch permissions of different systems.

[0102] Therefore, the display device 200 can respond to a startup command from the first system interface, detect the first display area of ​​the first system interface, and add the first display area to the disabled touch list. It can also respond to a shutdown command from the first system interface and remove the first display area from the disabled touch list.

[0103] To differentiate the disabled areas of different applications or interfaces, a tagging method can be used to assign a unique identifier to each application or interface. Each identifier corresponds to a display area of ​​the first system interface. When the first system interface is exited, the touch disabling of the corresponding identifier's display area can be canceled, and the corresponding identifier's display area can be removed from the disabled touch list.

[0104] Therefore, the display device 200 can obtain a first identifier of the first system interface. When the first system interface starts, a first display area is marked based on the first identifier, and the first display area marked with the first identifier is added to the disabled touch list. When the first system interface closes, the first display area marked with the first identifier is removed from the disabled touch list.

[0105] like Figure 13The diagram shown is a flowchart illustrating the execution of touch commands according to an embodiment of this application. When a user inputs a touch command through a specific touch interaction, the display device 200 responds to the user's input touch command by detecting the touch point position. It then retrieves a disabled touch list and reads the disabled areas within that list. If the touch point position is within the disabled area, the first system is controlled to execute the touch command. If the touch point position is not within the disabled area, a touch command is sent to a second controller, causing the second controller to control the second system to execute the touch command.

[0106] Understandably, this application includes a touch interaction module in the data transmission link from the hardware layer of the display device 200. This module judges the touch data transmitted from the hardware layer to determine whether it is within a restricted area. If the touch point in the touch data is within the restricted area, the touch data is not sent to the second system, and the first system responds to the touch data. If the touch point in the touch data is not within the restricted area, the touch data is not sent to the first system, but to the second system, which then responds to the touch data.

[0107] For example, with Figure 12 Taking the user interface as an example, in a Windows system, when the first system interface A is launched, the first display area corresponding to the first system interface A is area A. Then, when the first system interface B is launched, the first display area corresponding to the first system interface B is area B. Area A is marked with the identifier "A", and area B is marked with the identifier "B". The marked areas A and B are added to the disabled touch list for storage. When the user inputs a touch command at a certain touch position... Figure 12 When the p-point is shown, the display device 200 will detect that the p-point falls within area B or area A, that is, the p-point is located in the disabled area. In this case, the touch data will not be distributed to the Windows system, and only the touch operation of the Android system will be executed.

[0108] When exiting the first system interface B, the identifier "B" of the first system interface B can be obtained, and the area marked with the identifier "B" in the disabled touch list can be removed from the disabled touch list. At this time, area A still exists in the disabled touch list. When the user input touch position is detected as point p, the touch of the corresponding area A in the Windows system is still in a disabled state, and the touch operation of the Android system is still executed.

[0109] If the touch location input by the user is detected to be point k, the display device 200 will detect that point k falls outside area A, that is, point k is not located in the disabled area, and then distribute the touch data to the Windows system to execute the touch operation of the Windows system.

[0110] like Figure 14 As shown, Figure 14 This is a schematic diagram of the touch control flow of the second system interface under the first system in the embodiments of this application, which specifically includes the following:

[0111] S201: When the user interface includes the first system interface, in response to the start command of the second system interface, the second display area of ​​the second system interface is detected.

[0112] S202: Set a second touch marker value for the pixels in the second display area.

[0113] The second touch marker value is used to indicate the display area where the touch permissions of the second system are applied. When the second system interface is launched under the first system, the display device 200 can obtain the second display area of ​​the second system interface and set the second touch marker value for the pixels of the second display area, indicating that the second display area is the display area where the touch permissions of the second system are applied, so that the second display area can only perform touch operations of the second system and cannot perform touch operations of the first system.

[0114] For example, such as Figure 15 The diagram shows the second system interface launched under the first system provided in this application embodiment. The display device 200 is a touch screen of Android system, with a Windows system running on it to form a dual system. The running Windows system is the OPS module inside the touch screen. Under the Android system, the whiteboard application is launched, and the window interface of the whiteboard application is displayed in full screen. At this time, the touch permission of the OPS module is off. The OPS module is launched on the upper layer of the whiteboard application to perform windowed display of the second system interface C. The second display area corresponding to the second system interface C is obtained, the pixels of the second display area are traversed, and the second touch flag value "1" is set for the pixels of the second display area, indicating that the second display area is the display area where the touch permission of the Windows system is applied, so that the second system interface C can only perform touch operations of the Windows system, while other display areas not covered by the second system interface C can still perform touch operations of the Android system.

[0115] In some embodiments, the display device 200 can detect the second interface state of the second system interface. The second interface state includes a full-screen state and a non-full-screen state. If the second interface state is full-screen and the first system interface does not exist above the second system interface, a data channel between the first controller and the second controller is opened, allowing the first controller to send data to the second controller. If the second interface state is non-full-screen, the step of detecting the second display area of ​​the second system interface is performed.

[0116] In other words, if the second system launches a full-screen window and the first system's window is not displayed, then touch permissions for the second system are enabled. If the second system launches a non-full-screen window, then the display area of ​​the window is detected, and touch permissions for the second system are only enabled for that display area.

[0117] In some embodiments, the dual-system display device 200 includes a scenario where the second system is displayed within the first system in the form of a window. For example, as... Figure 15 The second system interface C shown is a preview window of the second system OPS module displayed in the whiteboard application of the first system in the display device 200. For the preview window, due to the change of window touch data, it does not support the second system to perform corresponding touch operations.

[0118] Therefore, to solve the above problems, when the window of the second system is not displayed in full-screen mode, the display device 200 can perform corresponding window data coordinate transformation on the window touch data. When the display device 200 detects that the second interface state of the second system interface is in a non-full-screen state, it obtains the full-screen coordinates and maps the full-screen coordinates to the window coordinates according to the second display area of ​​the second system interface. Here, the full-screen coordinates are the position coordinates of the window touch data in the full-screen state of the second system interface. The window coordinates are the position coordinates of the window touch data in the current non-full-screen state of the second system interface.

[0119] The window touch data refers to the interface elements in the second system interface used to respond to user touch actions, such as icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, and navigation bars. When the second system interface is displayed in full-screen mode, it can interact with the window touch data corresponding to the touch position in the user's input touch command. When the second system interface is displayed in windowed mode, the position coordinates of the window touch data in the full-screen state can be mapped to the position coordinates of the window touch data in the current non-full-screen state, thereby enabling touch operations in the non-full-screen state of the second system interface.

[0120] In some embodiments, when the first display area of ​​the first system interface and the second display area of ​​the second system interface overlap, an intersection operation can be performed on the first display area and the second display area to obtain the intersection area. Then, the display levels of the first system interface and the second system interface are compared. If the display level of the first system interface is higher than that of the second system interface, a first touch marker value is set for the pixels in the intersection area.

[0121] For example, with Figure 15 Taking the interface shown as an example, in the Android system, the whiteboard application is launched, and its window is displayed in full screen. Within the whiteboard application, the OPS module is launched, and the second system interface C is displayed in a window. For example... Figure 16 As shown, the second display area corresponding to the second system interface C is area C. The position coordinates of the window touch data in the full-screen state of the second system interface C are mapped to the position coordinates of the window touch data in area C, so as to realize the touch operation when the second system interface C is not in the full-screen state.

[0122] At this time, the first system interface D of the Android system is launched on top of the second system interface C. The first display area corresponding to the first system interface D is area D. The display device 200 can perform an intersection operation on areas C and D, and take the intersection area of ​​areas C and D, that is... Figure 16 As shown in region E, a first touch marker value is set for the pixels in region E, indicating that region E is the display area subject to Android system touch permissions. This allows the unobstructed areas in region C to perform touch operations under Windows systems, while other areas can perform touch operations under Android systems.

[0123] In this embodiment, a method combining touchable and non-touchable areas is used to partition and control the touch permissions of the second system. The display area of ​​the first system above the touchable area of ​​the second system is set as a disabled area, resulting in the touchable area that the second system can operate on, while the disabled area can be used for touch operations of the first system. This achieves coexistence and non-conflict of touch permissions under both systems, improving the convenience and accuracy of user operation.

[0124] Based on the above dual-system control method, a display device 200 is also provided in some embodiments of this application, including: a display 260, a first controller, and a second controller. The display 260 is configured to display a user interface; the display 260 is connected to a touch interaction module, which receives touch commands input by the user. The first controller can be the display device 200's own controller 250, used to run the first system to control the display 260 to display the first system interface. The second controller can be an external controller of the display device 200, connected to the first controller. The second controller runs the second system to control the display 260 to display the second system interface. The first controller is configured to execute the following program steps:

[0125] When the user interface includes a second system interface, in response to the startup command of the first system interface, the first display area of ​​the first system interface is detected.

[0126] Set the first touch marker value for the pixels in the first display area.

[0127] The first touch marker value is used to indicate the display area where the touch permission of the first system is applied.

[0128] When the user interface includes the first system interface, in response to the startup command of the second system interface, the second display area of ​​the second system interface is detected.

[0129] Set a second touch marker value for the pixels in the second display area.

[0130] The second touch marker value is used to indicate the display area where the touch permission of the second system is applied.

[0131] As can be seen from the above technical solutions, the display device and dual-system control method provided in the above embodiments, when the user interface includes a second system interface, responds to the start command of the first system interface, detects the first display area of ​​the first system interface, and sets a first touch marker value for the pixels of the first display area. When the user interface includes the first system interface, responds to the start command of the second system interface, detects the second display area of ​​the second system interface, and sets a second touch marker value for the pixels of the second display area. The first touch marker value is used to represent the display area where the touch permissions of the first system are active, and the second touch marker value is used to represent the display area where the touch permissions of the second system are active. The method can control the touch permissions of the dual systems mounted on the display device according to the display area of ​​the system interface, realizing the coexistence and non-conflict of touch permissions of the two systems, improving the convenience and accuracy of user operation.

[0132] Those skilled in the art will clearly understand that the techniques in the embodiments of the present invention can be implemented using software plus necessary general-purpose hardware platforms. Based on this understanding, the technical solutions in the embodiments of the present invention, or the parts that contribute to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods of various embodiments or certain parts of the embodiments of the present invention.

[0133] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

[0134] For ease of explanation, the above description has been provided in conjunction with specific embodiments. However, the above exemplary discussion is not intended to be exhaustive or to limit the embodiments to the specific forms disclosed above. Various modifications and variations can be obtained based on the above teachings. The selection and description of the above embodiments are for the purpose of better explaining the principles and practical applications, thereby enabling those skilled in the art to better utilize the described embodiments and various different variations of embodiments suitable for specific use considerations.

Claims

1. A display device, characterized in that, include: A display is configured to display a user interface, the display being connected to a touch interaction module, the touch interaction module being used to receive touch commands input by the user; A first controller is configured to run a first system to control the display to show the interface of the first system. The first controller is connected to the second controller, which is used to run the second system to control the display to show the interface of the second system; The first controller is configured as follows: When the user interface includes a second system interface, in response to the start command of the first system interface, the first display area of ​​the first system interface is detected; A first touch marker value is set for the pixels in the first display area, and the first touch marker value is used to indicate the display area where the touch permission of the first system is applied; When the user interface includes a first system interface, in response to the start command of the second system interface, the second display area of ​​the second system interface is detected; A second touch marker value is set for the pixels of the second display area. The second touch marker value is used to indicate the display area where the touch permission of the second system is applied.

2. The display device according to claim 1, characterized in that, The first controller is also configured to: In response to a user-input touch command, the position of the touch point of the touch command is detected; If the pixel at the touch point location is a first touch marker value, control the first system to execute the touch command; If the pixel at the touch point location is a second touch marker value, the touch command is sent to the second controller so that the second controller controls the second system to execute the touch command.

3. The display device according to claim 1, characterized in that, The first controller is also configured to: In response to a plurality of startup commands from the first system interfaces, the first display areas of the plurality of the first system interfaces are detected; Perform a union operation on multiple of the first display areas to obtain a union region; Set a first touch marker value for the pixels in the union region.

4. The display device according to claim 1, characterized in that, The first controller is also configured to: Create a list of disabled touch controls; In response to the start command of the first system interface, the first display area is added to the disabled touch list; In response to the shutdown command of the first system interface, the first display area is removed from the disabled touch list.

5. The display device according to claim 4, characterized in that, The first controller is also configured to: In response to a user-input touch command, the position of the touch point of the touch command is detected; Retrieve the disabled touch list and read the disabled area of ​​the disabled touch list; If the touch point is located within the disabled area, the first system is controlled to execute the touch command. If the touch point is not located within the disabled area, the touch command is sent to the second controller so that the second controller controls the second system to execute the touch command.

6. The display device according to claim 4, characterized in that, The first controller is also configured to: Obtain the first identifier of the first system interface; When the first system interface is started, the first display area is marked based on the first identifier, and the first display area marked with the first identifier is added to the disabled touch list; When the first system interface is closed, the first display area marked with the first identifier is removed from the disabled touch list.

7. The display device according to claim 1, characterized in that, The first controller is also configured to: Detect the state of the first interface of the first system interface, which includes full-screen state and non-full-screen state. If the first interface is in full-screen mode and the second system interface does not exist above the first system interface, close the data channel between the first controller and the second controller. If the first interface is in a non-full-screen state, the step of detecting the first display area of ​​the first system interface is executed.

8. The display device according to claim 1, characterized in that, The first controller is also configured to: Detect the state of the second interface of the second system interface, which includes full-screen state and non-full-screen state; If the second interface state is a non-fullscreen state, obtain the fullscreen coordinates, which are the position coordinates of the window touch data in the fullscreen state of the second system interface; The full-screen coordinates are mapped to window coordinates based on the second display area, where the window coordinates are the position coordinates of the window touch data in the current non-full-screen state of the second system interface.

9. The display device according to claim 1, characterized in that, The first controller is also configured to: When the first display area and the second display area overlap, an intersection operation is performed on the first display area and the second display area to obtain the intersection area; Compare the display hierarchy of the first system interface and the second system interface; If the display level of the first system interface is higher than that of the second system interface, a first touch marker value is set for the pixels in the intersection area.

10. A dual-system control method, characterized in that, The invention is applied to a display device, which includes a display, a first controller, and a second controller; the first controller is used to run a first system to control the display to show the interface of the first system. The first controller is connected to a second controller, which runs a second system to control the display to show the interface of the second system; the method includes: When the user interface of the display includes a second system interface, in response to the start command of the first system interface, the first display area of ​​the first system interface is detected; A first touch marker value is set for the pixels in the first display area, and the first touch marker value is used to indicate the display area where the touch permission of the first system is applied; When the user interface of the display includes a first system interface, in response to the start command of the second system interface, the second display area of ​​the second system interface is detected, and the second system interface is a window interface based on the second system. A second touch marker value is set for the pixels of the second display area. The second touch marker value is used to indicate the display area where the touch permission of the second system is applied.

Images