Display device and control device connection method

Abstract

The invention relates to a display device and a control device connection method. The display device includes: a display configured to display a user interface; the communication device is configured to establish communication connection with a server; the lightweight equipment manager is configured to perform data management on the control equipment; the controller is configured to determine first control equipment corresponding to an equipment access notification under the condition that the communication device receives the equipment access notification sent by the lightweight equipment manager; interacting with a first equipment node corresponding to the first control equipment, wherein the first equipment node is configured as an interaction interface of the first control equipment; and accessing the first control equipment to the communication device under the condition that the first equipment node is determined to be capable of interacting. The display equipment can better adapt to a low-performance platform, and the success rate of accessing the low-performance platform to the control equipment is improved.

Description

Technical Field

[0001] The present application relates to the technical field of display devices, and in particular to a method for connecting a display device and a control device. Background Art

[0002] Cloud gaming is a gaming mode based on cloud computing technology, which allows players to stream game images and data through the Internet. The game images can be displayed through display devices, and players can interact with the game by operating the control devices.

[0003] In the related art, udev (a device manager) is usually used to control device management. The behavior of udev is controlled by a rule file, thereby ensuring that the access process of the control device is carried out in an orderly manner.

[0004] However, in some lower-performance platforms, the device manager supported by the kernel is edev (a lightweight device manager). Edev has no rule files for behavior control. In the process of accessing the control device, it is often the case that the control device cannot be used normally after the user connects the control device to the display device. Therefore, there is a problem of low success rate in accessing the control device on low-performance platforms. Summary of the invention

[0005] The present application provides a method for connecting a display device and a control device to solve the problem of low success rate of low-performance platforms accessing control devices.

[0006] In the first aspect, some embodiments provide a display device, including: a display, a communication device, a lightweight device manager, and a controller. The display is configured to display a user interface; the communication device is configured to establish a communication connection with a server; the lightweight device manager is configured to manage data for the control device; the controller is configured to: when the communication device receives a device access notification sent by the lightweight device manager, determine the first control device corresponding to the device access notification; interact with the first device node corresponding to the first control device, the first device node being configured as an interaction interface of the first control device; and when it is determined that the first device node can interact, connect the first control device to the communication device.

[0007] Technical effect: When the communication device receives the device access notification sent by the lightweight device manager, the first control device corresponding to the device access notification is determined, and the first device node corresponding to the first control device is first tried to interact. When it is determined that the first device node can interact, the first control device is connected to the communication device. In this way, even if the lightweight device manager supported by the low-performance platform notifies the communication device to access the device before the device node of the first control device is generated due to the lack of a rule file for behavior control, it can also ensure that when the first control device is connected to the communication device, the first device node has been generated and can interact, so that the first control device can be successfully connected to the communication device, avoiding the situation where the first control device fails to access the communication device because the communication device cannot interact with the device node after the first control device is connected to the communication device. That is, it can avoid the situation where the first control device cannot communicate with the server through the communication device after accessing the display device due to the failure of the first control device to access the communication device, thereby failing to control the cloud game. Therefore, the way in which the control device is connected to the display device in this application can better adapt to the low-performance platform and improve the success rate of the low-performance platform accessing the control device.

[0008] In some embodiments, the communication device stores a connected list and a to-be-connected list;

[0009] In the process of connecting the first control device to the communication apparatus, the controller is further configured to:

[0010] When it is detected that the current remaining capacity of the connected list is greater than a preset remaining capacity threshold, connecting the first control device to the communication apparatus and adding information of the first control device to the connected list;

[0011] When it is detected that the current remaining capacity of the connected list is less than or equal to a preset remaining capacity threshold, the information of the first control device is added to the to-be-connected list.

[0012] Technical effect: By maintaining a list to be connected, it is possible to avoid the situation where the first control device is connected and then removed when the connected list is full. Since the first control device has not been removed by the communication device, the first device node will not be deleted. In this way, when the user wants to use the first control device, it is only necessary to replace the control device on the connected list with the first device node on the list to be connected, without repeating a series of processes such as generating device nodes and connecting to the communication device, thereby effectively saving resources. The saved resources can be used for other functions of the display device, thereby improving the overall stability and fluency of the display device, which can also improve the user experience.

[0013] In some embodiments, the controller is further configured to:

[0014] When it is detected that any control device in the connected list is disconnected, selecting a second control device from the to-be-connected list;

[0015] The second control device is connected to the communication apparatus, and information of the second control device is added to the connected list.

[0016] Technical effect: After any control device in the connected list is disconnected, the second control device is automatically selected and reconnected from the list to be connected, thereby realizing automatic replacement of the connected control device. In this way, when any control device in the connected list is disconnected due to low battery or failure, the user only needs to put down the disconnected control device and pick up the second control device to continue the operation. The whole process almost does not require the user to pause the application interaction process. For example, if the user is currently in a cloud game, the user's game operation will hardly be affected, and only a control device needs to be changed, which effectively improves the smoothness of the user's operation, thereby improving the user experience.

[0017] In some embodiments, in the process of connecting the second control device to the communication apparatus and adding the information of the second control device to the connected list, the controller is further configured to:

[0018] Connecting the second control device to the communication device;

[0019] In the case where it is determined that the second control device is connected to the communication apparatus, the information of the second control device is added to the connected list, and the information of the second control device is deleted from the to-be-connected list.

[0020] Technical effect: By first determining that the second control device can access the communication device, and then adding the information of the second control device to the connected list, unnecessary writing and deleting operations caused by the inability of the second control device to connect back can be reduced, thereby effectively saving resources. The saved resources can be used for other functions of the display device, thereby improving the overall stability and smoothness of the display device, which can also improve the user experience.

[0021] In some embodiments, after connecting the second control device to the communication apparatus, the controller is further configured to:

[0022] When it is determined that the second control device is not connected to the communication apparatus, the information of the second control device is deleted from the to-be-connected list, and the process returns to the step of selecting the second control device from the to-be-connected list.

[0023] Technical effect: By immediately reselecting the second control device from the list to be connected when the reconnection fails, the time for switching control devices can be effectively shortened, the time the user pauses application interaction to wait for switching control devices can be shortened, and the user's operation fluency can be improved, which can also improve the user experience.

[0024] In some embodiments, after connecting the second control device to the communication apparatus, the controller is further configured to:

[0025] The connection reminder information is displayed through the second control device.

[0026] Technical effect: By displaying connection reminder information, when the control device is switched, the user can be instructed to accurately find the second control device after the switch, shortening the time the user spends searching for the control device after the control device is switched, thereby shortening the time the user pauses application interaction and waits for the control device to be switched, thereby improving the user's operation fluency and user experience.

[0027] In some embodiments, after the first device node corresponding to the first control device interacts, the controller is further configured to:

[0028] When it is determined that the first device node cannot interact, the step of interacting with the first device node corresponding to the first control device is executed repeatedly until it is determined that the first device node can interact, and the first control device is connected to the communication device.

[0029] Technical effect: Through a cyclic attempt, the communication device can promptly know the information that the first device node has generated, and thus promptly access the first control device. This can shorten the time it takes for the first control device to access the communication device as much as possible, and reduce the waiting time for the user from connecting the first control device to the display device to using the first control device. This can also improve the user experience.

[0030] In some embodiments, during the process of executing the step of cyclically executing the step of interacting with the first device node corresponding to the first control device, the controller is further configured to:

[0031] Get the current loop count;

[0032] When it is determined that the current number of cycles does not exceed the preset number of cycles threshold, the step of interacting with the first device node corresponding to the first control device is returned to be executed, and the current number of cycles is updated.

[0033] Technical effect: By setting a loop count threshold, you can avoid falling into an infinite loop, ensure the controllability of resource consumption, and maintain system stability.

[0034] In some embodiments, when it is determined that the current number of cycles does not exceed the preset number of cycles threshold, before returning to execute the step of interacting with the first device node corresponding to the first control device and updating the current number of cycles, the controller is further configured to:

[0035] Querying a historical connection time of the first control device and a target number of cycles corresponding to the historical connection time, wherein the target number of cycles is positively correlated with the historical connection time;

[0036] The target cycle number is determined as a preset cycle number threshold.

[0037] Technical effect: After determining for the first time that the first device node cannot interact, before performing a cyclic interaction, the preset cycle count threshold is adaptively adjusted based on the historical connection time of the first control device. On the one hand, when the first device node can be generated, smooth access to the first control device can be guaranteed. On the other hand, in the abnormal situation where the first device node cannot be generated, unnecessary resource consumption can be effectively reduced, and the user's waiting time in the abnormal situation can be shortened, which can also improve the user experience.

[0038] In a second aspect, some embodiments further provide a control device connection method, which is applied to the display device provided in the first aspect, the display device comprising: a display, a communication device, a lightweight device manager and a controller, and the method comprises:

[0039] When the communication device receives a device access notification sent by the lightweight device manager, determining a first control device corresponding to the device access notification;

[0040] interacting with a first device node corresponding to a first control device, the first device node being configured as an interaction interface of the first control device;

[0041] When it is determined that the first device node is capable of interacting, the first control device is connected to the communication apparatus.

[0042] Technical effect: When the communication device receives the device access notification sent by the lightweight device manager, the first control device corresponding to the device access notification is determined, and the first device node corresponding to the first control device is first tried to interact. When it is determined that the first device node can interact, the first control device is connected to the communication device. In this way, even if the lightweight device manager supported by the low-performance platform notifies the communication device to access the device before the device node of the first control device is generated due to the lack of a rule file for behavior control, it can also ensure that when the first control device is connected to the communication device, the first device node has been generated and can interact, so that the first control device can be successfully connected to the communication device, avoiding the situation where the first control device fails to access the communication device because the communication device cannot interact with the device node after the first control device is connected to the communication device. That is, it can avoid the situation where the first control device cannot communicate with the server through the communication device after accessing the display device due to the failure of the first control device to access the communication device, thereby failing to control the cloud game. Therefore, the way in which the control device is connected to the display device in this application can better adapt to the low-performance platform and improve the success rate of the low-performance platform accessing the control device. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0044] Figure 1 A schematic diagram of an operation scenario between a display device and a control device provided in some embodiments of the present application;

[0045] Figure 2 A schematic diagram of the hardware configuration of a display device provided in some embodiments of the present application;

[0046] Figure 3 A schematic diagram of the hardware configuration of a control device provided in some embodiments of the present application;

[0047] Figure 4 A schematic diagram of software configuration of a display device provided in some embodiments of the present application;

[0048] Figure 5 A timing diagram of a method for implementing a control device connection method provided in some embodiments of the present application;

[0049] Figure 6 A timing diagram of a method for implementing a control device connection method provided in some embodiments of the present application;

[0050] Figure 7 A flowchart of a method for implementing a control device connection method provided in some embodiments of the present application. DETAILED DESCRIPTION

[0051] The following embodiments are described in detail, and examples thereof are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementations described in the following embodiments do not represent all implementations consistent with the present application. They are only examples of systems and methods consistent with some aspects of the present application as detailed in the claims.

[0052] It should be noted that the brief description of terms in this application is only for the convenience of understanding the embodiments described below, and is not intended to limit the embodiments of this application. Unless otherwise specified, these terms should be understood according to their common and usual meanings.

[0053] The terms "first", "second", "third", etc. in the specification and claims of this application and the above drawings are used to distinguish similar or similar objects or entities, and do not necessarily mean to limit a specific order or sequence, unless otherwise noted. It should be understood that the terms used in this way can be interchangeable under appropriate circumstances.

[0054] The terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover but not exclude inclusion, for example, a product or device comprising a list of components is not necessarily limited to all the components expressly listed but may include other components not expressly listed or inherent to such product or device.

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

[0056] In the embodiment of the present application, the display device 200 generally refers to a device with image display and data processing capabilities. For example, the display device 200 includes but is not limited to a smart TV, a mobile terminal, a computer, a monitor, an advertising screen, a wearable device, a virtual reality device, an augmented reality device, etc.

[0057] Figure 1 This is a schematic diagram of an operation scenario between a display device and a control device provided in some embodiments of the present application. Figure 1 As shown in FIG. 1 , the user can operate the display device 200 through touch operation, the mobile terminal 300 and the control device 100. For example, the control device 100 can be a remote controller, a stylus pen, a handle, etc.

[0058] The mobile terminal 300 can be used as a control device for performing human-computer interaction between the user and the display device 200. The mobile terminal 300 can also be used as a communication device for establishing a communication connection with the display device 200 and performing data interaction. In some embodiments, the mobile terminal 300 can install software applications with the display device 200, and achieve connection and communication through a network communication protocol to achieve the purpose of one-to-one control operation and data communication. The audio and video content displayed on the mobile terminal 300 can also be transmitted to the display device 200 to achieve a synchronous display function.

[0059] like Figure 1 As also shown in FIG. 4 , the display device 200 also communicates data with the server 400 through various communication methods. The display device 200 may be allowed to communicate and connect through a local area network (LAN), a wireless local area network (WLAN) and other networks.

[0060] The display device 200 may provide a broadcast receiving television function, and may also additionally provide an intelligent network television function of a computer support function, including but not limited to network television, smart television, Internet Protocol television (IPTV), etc.

[0061] Figure 2 Some embodiments of the present application provide Figure 1 2 is a block diagram of the hardware configuration of the display device 200.

[0062] In some embodiments, the display device 200 may include at least one of a tuner 210, a communication device 220, a detector 230, a device interface 240, a controller 250, a display 260, an audio output device 270, a memory, a power supply, and a user input interface.

[0063] In some embodiments, the detector 230 is used to collect signals of the external environment or external interaction. For example, the detector 230 includes a light receiver, a sensor for collecting the intensity of ambient light; or, the detector 230 includes an image collector, such as a camera, which can be used to collect external environment scenes, user attributes or user interaction gestures; or, the detector 230 includes a sound collector, such as a microphone, etc., for receiving external sounds.

[0064] In some embodiments, the display 260 includes a display function component for presenting a picture, and a driving component for driving an image display. The display 260 is used to receive an image signal output from the controller 250 for display. For example, the display 260 can be used to display video content, image content, and components of a menu control interface and a user control UI interface.

[0065] In some embodiments, the communication device 220 is a component for communicating with the first control device or the server 400 according to various communication protocol types. The display device 200 may be provided with a plurality of communication devices 220 according to different supported communication modes. For example, when the display device 200 supports wireless network communication, the display device 200 may be provided with a communication device 220 including a WiFi function. When the display device 200 supports Bluetooth connection communication, the display device 200 needs to be provided with a communication device 220 including a Bluetooth function.

[0066] In some embodiments, the communication device may be a browser. In a cloud gaming scenario, the terminal may transmit data between the browser and the server.

[0067] The communication device 220 can communicate with the display device 200 and the first control device or the server 400 by wireless or wired connection. Among them, the wired connection can connect the display device 200 to the control device through components such as data cables and interfaces. The wireless connection can connect the display device 200 to the control device through wireless signals or wireless networks. The display device 200 can establish a connection relationship with the first control device directly, or indirectly establish a connection relationship through a gateway, a router, a connection device, etc.

[0068] In some embodiments, the controller 250 may include at least one of a central processing unit, a video processor, an audio processor, a graphics processor, and a power processor, and a first interface to an nth interface for input / output. The controller 250 controls the operation of the display device and responds to the user's operation through various software control programs stored in the memory. The controller 250 controls the overall operation of the display device 200.

[0069] In some embodiments, the controller 250 and the tuner-demodulator 210 may be located in different separate devices, that is, the tuner-demodulator 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.

[0070] In some embodiments, the user may input a user command through a graphical user interface (GUI) displayed on the display 260 , and the user input interface receives the user input command through the graphical user interface (GUI).

[0071] In some embodiments, the audio output device 270 may be a local speaker of the display device 200, or may be an external audio output device of the display device 200. In particular, for the external audio output device of the display device 200, the display device 200 may also be provided with an external audio output terminal, and the audio output device may be connected to the display device 200 through the external audio output terminal to output the sound of the display device 200.

[0072] In some embodiments, the user input interface 280 may be used to receive instructions from a user.

[0073] Figure 3 Some embodiments of the present application provide Figure 1 The hardware configuration diagram of the control device in the figure. Figure 3 As shown, the control device 100 may include: a controller 110, a communication interface 130, a user input / output interface, a memory, and a power supply.

[0074] The control device 100 is configured to control the display device 200 , and can receive user input operation instructions, and convert the operation instructions into instructions that the display device 200 can recognize and respond to, playing the role of an interactive intermediary between the user and the display device 200 .

[0075] In some embodiments, the control device 100 may be a smart device, for example, the control device 100 may be installed with various applications for controlling the display device 200 according to user requirements.

[0076] In some embodiments, Figure 1 As shown, the mobile terminal 300 or other intelligent electronic devices can play a similar function as the control device 100 after installing the application for controlling the display device 200 .

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

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

[0079] The user input / output interface 140 , wherein the input interface includes at least one of other input interfaces such as a microphone 141 , a touch panel 142 , a sensor 143 , and a button 144 .

[0080] 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 a communication interface 130, such as a WiFi, Bluetooth, NFC or other module, and can encode the user input command through the WiFi protocol, Bluetooth protocol, or NFC protocol and send it to the display device 200.

[0081] 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 store various control signal instructions input by the user.

[0082] The power supply 180 is used to provide operating power support for each component of the control device 100 under the control of the controller.

[0083] In order to perform user interaction, in some embodiments, the display device 200 may run an operating system. The operating system is a computer program for managing and controlling hardware resources and software resources in the display device 200. The operating system may (control the display device) provide a user interface, allow the user to interact with the display device 200, and support the running of various application programs.

[0084] It should be noted that the operating system can be a native operating system based on a specific operating platform, a third-party operating system deeply customized based on a specific operating platform, or an independent operating system specially developed for the display device.

[0085] The operating system can be divided into different modules or layers according to the functions implemented, such as Figure 4 As shown, in some embodiments, the system is divided into four layers, from top to bottom, namely, the application layer (Applications layer) (referred to as "application layer"), the application framework layer (Application Framework layer) (referred to as "framework layer"), the system library layer and the kernel layer.

[0086] In some embodiments, the application layer is used to provide services and interfaces for applications so that the display device 200 can run applications and interact with users based on applications. At least one application can be run in the application layer, and these applications can be window programs, system settings programs, clock programs, etc. that come with the operating system; they can also be applications developed by third-party developers. In specific implementations, the application packages in the application layer are not limited to the above examples.

[0087] The framework layer provides application programming interfaces (APIs) and programming frameworks for applications. The application framework layer includes some predefined functions. The application framework layer is equivalent to a processing center that determines the actions of applications in the application layer. Applications can access system resources and obtain system services during execution through the API interface.

[0088] like Figure 4As shown, in the embodiment of the present application, the application framework layer includes a view system, managers, content providers, etc., wherein the view system can design and implement the interface and interaction of the application, and the view system includes lists, grids, text boxes, buttons, etc. The manager includes at least one of the following modules: the device external manager is used to manage the control device related data such as device nodes and device events; the activity manager is used to interact with all activities running in the system; the location manager is used to provide system services or applications with access to the system location service; the package manager is used to retrieve various information related to the application package currently installed on the device; the notification manager is used to control the display and clearing of notification messages; the window manager is used to manage icons, windows, toolbars, wallpapers and desktop components on the user interface.

[0089] In some embodiments, the activity manager is used to manage the life cycle of each application and the usual navigation back function, such as controlling the exit, opening, and back of the application. The window manager is used to manage all window programs, such as obtaining the display screen size, determining whether there is a status bar, locking the screen, capturing the screen, and controlling the display window changes, for example, reducing the display window, shaking the display, distorting the display, etc.

[0090] In some embodiments, the system runtime layer can provide support for the framework layer. When the framework layer is used, the operating system will run the instruction library contained in the system runtime layer, such as the C / C++ instruction library, to implement the functions to be implemented by the framework layer.

[0091] In some embodiments, the kernel layer is a functional layer between the hardware and software of the display device 200. The kernel layer can implement functions such as hardware abstraction, multitasking, and memory management. Figure 4 As shown, the kernel layer may be configured with hardware drivers, and the drivers included in the kernel layer may be at least one of the following drivers: audio driver, display driver, Bluetooth driver, camera driver, WIFI driver, USB driver, HDMI driver, sensor driver (such as fingerprint sensor, temperature sensor, pressure sensor, etc.), and power driver, etc.

[0092] It should be noted that the above example is only a simple division of the operating system functions and does not constitute a limitation on the specific operating system form of the display device 200 in the embodiment of the present application. Depending on factors such as the function of the display device and the type of operating system, the number of levels and specific level types contained in the operating system may be expressed in other forms.

[0093] In some embodiments, reference Figure 5 , the device manager supported by the kernel in the display device is a lightweight device manager, such as edev, and the communication device that needs to add the control device can be a browser. When the user connects the new control device to the display device, the kernel's device driver will detect this event, notify edev, and process the data of the control device to generate a device node corresponding to the control device. After receiving the notification, edev will directly notify the browser to access the control device. When the browser receives the device access notification sent by edev, it will add and configure the control device. After the addition and configuration are completed, the configuration information of the control device will be verified by opening the device node and interacting with the device node. However, it takes a certain amount of time for the kernel to generate a device node, so it may happen that when the browser opens the device node, the device node has not been generated. In this case, the browser will determine that the verification fails, and automatically remove the control device. In this way, even if the device node is generated afterwards, the browser fails to add the control device, resulting in the control device being unable to communicate with the server, thereby causing the control device to be unable to be used normally. In this case, even if the user disconnects the control device from the display device and then reconnects it, the device node corresponding to the control device will be deleted synchronously after the disconnection. Therefore, when reconnecting, the device node still needs to be regenerated. Therefore, the above problem will still occur and the control device still cannot be used normally.

[0094] Based on this, a display device is provided, the display device comprising:

[0095] The display is configured to display a user interface.

[0096] The communication device is configured to establish a communication connection with the server.

[0097] The lightweight device manager is configured to perform data management on the control device.

[0098] Among them, a lightweight device manager can be a device manager that, after receiving an access notification of a new control device sent by the kernel, does not need to perform complex rule matching, but directly notifies the communication device to add the device, such as edev. The lightweight device manager has the characteristics of quick deployment, streamlined functions, low maintenance cost, and high performance, and is suitable for some lower-performance platforms.

[0099] In some embodiments, when the user connects the first control device to the display device, the kernel's device driver detects the event of the first control device being connected to the display device, and sends a device access notification to the lightweight device manager, the device access notification is used to notify the lightweight device manager to manage the data of the newly connected first control device, synchronously, the kernel processes the data of the first control device, and after the data processing is completed, the first device node corresponding to the first control device can be generated. After receiving the device access notification, the lightweight device manager sends a device access notification to the communication device, the device access notification is used to notify the communication device to access the first control device. That is, the process of the kernel processing the data of the first control device to generate the first device node is synchronized with the process of the communication device accessing the first control device.

[0100] The controller is configured to: when the communication device receives a device access notification sent by a lightweight device manager, determine the first control device corresponding to the device access notification; interact with the first device node corresponding to the first control device, the first device node is configured as an interaction interface of the first control device; and when it is determined that the first device node is capable of interacting, connect the first control device to the communication device.

[0101] The device node may be an abstract representation of the hardware device in the file system of the display device, and the user space program on the display device may interact with the hardware device by opening, reading, writing and closing the device node. The first device node may be an abstract representation of the first control device in the file system of the display device.

[0102] In some embodiments, when the communication device receives a device access notification sent by a lightweight device manager, it first extracts device identification information from the device access notification, and determines the newly connected first control device based on the device identification information; then, based on the mentioned device identification information, it queries the first device node corresponding to the newly connected first control device; then, it attempts to interact with the first device node, and when it is determined that the first device node is able to interact, it connects the first control device to the communication device.

[0103] Wherein, connecting the first control device to the communication apparatus may include adding and configuring the first control device in the communication apparatus.

[0104] The process of interacting with the first device node includes accessing the first device node; if information that the first device node cannot access is received, determining that the first device node cannot interact; if information that the first device node can access is received, determining that the first device node can interact.

[0105] In some feasible embodiments, after attempting to interact with the first device node corresponding to the first control device, if it is determined that the first device node cannot interact, the step of interacting with the first device node corresponding to the first control device can be returned immediately or after the timing reaches a preset interval time, and interaction with the first device node can be attempted again; if it is still determined that the first device node cannot interact, the interaction attempts can continue in a loop, or it can be determined that the connection between the first control device and the display terminal has failed, without executing the subsequent process of connecting the first control device to the communication device, and an abnormal prompt message that the first control device cannot be connected can also be fed back through the display device.

[0106] In some feasible embodiments, the delayed interaction time can be set in advance based on the time required for the kernel to generate a device node through experience or testing, so that after the communication device receives the device access notification sent by the lightweight device manager, or after determining the first control device corresponding to the device access notification, timing is performed, and when the timing reaches the preset delayed interaction time, the interaction with the first device node corresponding to the first control device is attempted; in this case, if it is determined that the first device node cannot interact, there is no need to wait or make cyclic attempts, and the connection between the first control device and the display terminal is determined to have failed. There is no need to perform the subsequent process of connecting the first control device to the communication device, and the display device can also feedback an abnormal prompt message that the first control device cannot be connected; or, the cyclic attempt to interact can be continued to avoid deviations in the estimated delayed interaction time, but the threshold value of the number of cycles of the cyclic attempt to interact can be set to a smaller value. By setting the delayed interaction time, the number of cyclic attempts to interact can be reduced, thereby saving communication resources.

[0107] In some feasible embodiments, if the interaction attempt is continued in a loop, the loop may be looped until it is determined that the first device node is capable of interacting, in which case the first control device is connected to the communication device; or the loop may be looped until the number of loops reaches a preset loop number threshold, in which case the loop is terminated without executing the subsequent process of connecting the first control device to the communication device, and an abnormal prompt message that the first control device cannot be connected may be fed back through a display device; or the loop may be looped until the time for attempting to interact reaches a preset interaction time threshold, in which case the loop is terminated without executing the subsequent process of connecting the first control device to the communication device, and an abnormal prompt message that the first control device cannot be connected may be fed back through a display device.

[0108] In some embodiments, reference Figure 6, the device manager supported by the kernel in the display device is a lightweight device manager, such as edev, and the communication device that needs to add the first control device can be a browser. When the user connects the first control device to the display device, the kernel's device driver will detect this event, notify edev, and process the data of the first control device to generate a first device node corresponding to the first control device. After receiving the notification, edev will directly notify the browser to access the first control device. When the browser receives the device access notification sent by edev, it first tries to open the first device node multiple times and interacts with the first device node. When it is determined that the first device node is opened successfully, it adds and configures the first control device. In this way, it can ensure the smooth progress of the configuration information verification process after the addition and configuration are completed, and avoid the situation where the first control device is removed by the browser due to the inability to open the first device node.

[0109] After the first control device is connected to the communication device, the communication device can verify the configuration information of the first control device by interacting with the first device node. If the communication device detects that the first device node cannot interact, it will be determined as a verification failure, so that the first control device will be removed, resulting in the first control device being unable to communicate with the server through the communication device. Therefore, this embodiment can ensure that the first device node has been generated and can interact before the communication device and the first device node perform interactive verification by trying to interact with the first control device corresponding to the first control device before connecting the first control device to the communication device. In this way, if the generation time of the first device node is later than the time of attempting to interact, it can be ensured that the verification after the first control device is connected will not fail due to the late generation time of the first device node by delaying the access; if the first device node cannot be generated, it can also save the resources occupied by the communication device to add and configure the first control device that cannot generate the first device node.

[0110] In this embodiment, when the communication device receives the device access notification sent by the lightweight device manager, the first control device corresponding to the device access notification is determined, and the first device node corresponding to the first control device is first tried to interact. When it is determined that the first device node can interact, the first control device is connected to the communication device. In this way, even if the lightweight device manager supported by the low-performance platform lacks a rule file for behavior control, before the device node of the first control device is generated, it notifies the communication device to access the device, it can also ensure that when the first control device accesses the communication device, the first device node has been generated and can interact, so that the first control device can smoothly access the communication device, avoiding the situation that the first control device fails to access the communication device because the communication device cannot interact with the device node after the first control device accesses the communication device, that is, it can avoid the situation that the first control device fails to access the communication device, and the first control device cannot communicate with the server through the communication device after accessing the display device, thereby failing to control the cloud game. Therefore, the way in which the control device is connected to the display device in this application can better adapt to the low-performance platform, improve the success rate of the low-performance platform accessing the control device, and can also improve the fluency of the low-performance platform control device access operation.

[0111] In some embodiments, after interacting with the first device node corresponding to the first control device, the controller is further configured to:

[0112] When it is determined that the first device node cannot interact, the step of interacting with the first device node corresponding to the first control device is executed repeatedly until it is determined that the first device node can interact, and the first control device is connected to the communication device.

[0113] In some embodiments, after attempting to interact with the first device node corresponding to the first control device, if it is determined that the first device node cannot interact, the steps of interacting with the first device node corresponding to the first control device can be looped, and the interaction with the first device node can be attempted again until it is determined that the first device node can interact, and the first control device is connected to the communication device; or until the number of loops reaches a preset loop number threshold, the loop is terminated without executing the subsequent process of connecting the first control device to the communication device, and an abnormal prompt message that the first control device cannot be connected can be fed back through the display device; or until the time of the attempted interaction reaches a preset interaction time threshold, the loop is terminated without executing the subsequent process of connecting the first control device to the communication device, and an abnormal prompt message that the first control device cannot be connected can be fed back through the display device.

[0114] In some feasible embodiments, the process of cyclically executing the step of interacting with the first device node corresponding to the first control device includes: when it is determined that the first device node cannot interact, starting timing, and after the timing reaches a preset interval time, returning to execute the step of interacting with the first device node corresponding to the first control device. In this way, compared with the continuous loop method, this embodiment can reduce the number of loops by delaying the loop, thereby reducing the resources required and consumed by the loop interaction.

[0115] In some feasible embodiments, the interval time can be a numerical value, an array, or an algorithm. In the case where the interval time of each cycle is the same, the interval time can be a numerical value. The interval time of each cycle can also be different. In this case, the interval time can be an array or an algorithm, and the interval time of each cycle can be negatively correlated with the number of cycles, that is, the more cycles there are, the shorter the preset interval time is. For example, if the number of cycles is 3, the cycle time interval can be (t1, t2, t3), t1 is greater than t2 and greater than t3, (t1, t2, t3) means that the time interval of the first cycle is t1, the time interval of the second cycle is t2, and the time interval of the third cycle is t3. In the case where the first device node can be generated, the more cycles there are, the closer it is to the generation time of the first device node, and the preset interval time is shortened, so that the generation of the first device node can be detected more timely. In the case where the first device node cannot be generated, in the later stage of the cycle, shortening the interval time can shorten the time to confirm that the first device node cannot be generated, thereby reminding the user as soon as possible to check whether there are other abnormalities.

[0116] In this embodiment, by means of a cyclic attempt, the communication device can promptly know the information that has been generated by the first device node, and thus promptly access the first control device. This can shorten the time it takes for the first control device to access the communication device as much as possible, and reduce the waiting time for the user from connecting the first control device to the display device to using the first control device. This can also improve the user experience.

[0117] In some embodiments, during the process of executing the step of cyclically executing the interaction with the first device node corresponding to the first control device, the controller is further configured to:

[0118] Get the current loop count;

[0119] When it is determined that the current number of cycles does not exceed the preset number of cycles threshold, the process returns to the step of interacting with the first device node corresponding to the first control device, and updates the current number of cycles.

[0120] The current number of loops may be the number of completed loop interactions. In the process of attempting to interact, loop interactions can be used to avoid the situation where the first device node has not been generated when attempting to interact, resulting in interaction failure. However, the process of loop interactions also requires the occupation and consumption of resources. Therefore, a loop number threshold can be set to avoid falling into an infinite loop, ensure the controllability of resource consumption, and maintain the stability of the system.

[0121] In some embodiments, after attempting to interact with the first device node corresponding to the first control device, if it is determined that the first device node cannot interact, the current cycle number can be obtained first, and the current cycle number can be compared with the numerical value of a preset cycle number threshold. If the current cycle number does not exceed the preset cycle number threshold, then immediately or after the timing reaches a preset interval time, return to the step of interacting with the first device node corresponding to the first control device, and try to interact with the first device node again until it is determined that the first device node can interact, and then connect the first control device to the communication device; if the current cycle number exceeds the preset cycle number threshold, the loop is terminated without executing the subsequent process of connecting the first control device to the communication device, and an abnormal prompt message that the first control device cannot be connected can also be fed back through the display device.

[0122] In this embodiment, by setting a loop count threshold, it is possible to avoid falling into an infinite loop, ensure the controllability of resource consumption, and maintain the stability of the system.

[0123] In some embodiments, when it is determined that the current number of cycles does not exceed the preset number of cycles threshold, before returning to the step of interacting with the first device node corresponding to the first control device and updating the current number of cycles, the controller is further configured to:

[0124] Query the historical connection time of the first control device and the target number of cycles corresponding to the historical connection time, where the target number of cycles is positively correlated with the historical connection time;

[0125] The target cycle number is determined as a preset cycle number threshold.

[0126] Among them, the historical connection time may refer to the average duration from the time the user initiates the connection between the first control device and the display device to the time the communication device successfully adds the first control device during the connection process of the first control device before the current connection to the display device; or it may refer to the maximum duration from the time the user initiates the connection between the first control device and the display device to the time the communication device successfully adds the first control device during the connection process of the first control device before the current connection to the display device; or it may refer to the average duration from the time the communication device receives the device access notification to the time the communication device successfully adds the first control device during the connection process of the first control device before the current connection to the display device; or it may refer to the maximum duration from the time the communication device receives the device access notification to the time the communication device successfully adds the first control device during the connection process of the first control device before the current connection to the display device; etc.

[0127] When the interval time of each cycle remains unchanged, the longer the historical connection time is, the more cycles are required to successfully interact with the first device node. Therefore, a larger cycle number threshold should be set; conversely, the longer the historical connection time is, the fewer cycles are required to successfully interact with the first device node. If interaction is not possible, it means that there is an abnormality in the generation of the first device node. Even if more cycles are performed, interaction will not be successful, which will result in a waste of resources. Therefore, only a smaller cycle number threshold needs to be set.

[0128] In some embodiments, after determining for the first time that the first device node cannot interact, before performing the cyclic interaction, the historical connection time corresponding to the first control device can be queried from the pre-stored historical connection time record based on the device identification information of the first control device. Then, the historical connection time can be brought into the preset cycle number algorithm to calculate the target cycle number corresponding to the historical connection time; or, the target cycle number corresponding to the historical connection time can be queried from the preset cycle number and connection time correspondence table. Then, the target cycle number determined based on the historical connection time is determined as the cycle number threshold of this cyclic interaction process.

[0129] In some feasible embodiments, after the historical connection time of the first control device is queried, the target interval time can be determined based on the historical connection time, wherein the interval time can be the time interval between two adjacent loop interactions, and the target interval time is positively correlated with the historical connection time, that is, the longer the historical connection time is, the longer the target interval time can be. The historical connection time can be brought into the preset interval time algorithm to calculate the target interval time corresponding to the historical connection time; or, the target interval time corresponding to the historical connection time can be queried from the preset correspondence table between the interval time and the connection time. Furthermore, the historical connection time and the target interval time can be brought into the preset cycle number algorithm to calculate the target cycle number; or, the target cycle number corresponding to the historical connection time and the target interval time can be queried from the preset correspondence table between the cycle number, the interval time and the connection time. Furthermore, the target cycle number determined based on the historical connection time and the target interval time is determined as the cycle number threshold of this loop interaction process.

[0130] In this embodiment, after determining for the first time that the first device node cannot interact, before performing a cyclic interaction, the preset cycle count threshold is adaptively adjusted based on the historical connection time of the first control device. On the one hand, when the first device node can be generated, smooth access to the first control device can be guaranteed. On the other hand, in the abnormal situation where the first device node cannot be generated, unnecessary resource consumption can be effectively reduced, and the waiting time of the user in the abnormal situation can be shortened, which can also improve the user experience.

[0131] In some embodiments, a connected list and a to-be-connected list are stored on the communication device; in the process of connecting the first control device to the communication device, the controller is further configured to:

[0132] When it is detected that the current remaining capacity of the connected list is greater than a preset remaining capacity threshold, connecting the first control device to the communication device and adding information of the first control device to the connected list;

[0133] When it is detected that the current remaining capacity of the connected list is less than or equal to the preset remaining capacity threshold, the information of the first control device is added to the to-be-connected list.

[0134] It should be noted that, at present, in order to ensure the response speed and stability of the control device connected to the display device, the communication device usually sets an upper limit on the number of connected devices. A connected list is usually maintained in the communication device for adding the information of the connected control device, and only the control device added to the connected list is allowed to interact with the application. The number of connected control devices is limited by the limited number of additions to the connected list. The common number of additions to the connected list is four, that is, the information of up to four control devices is stored, and up to four control devices are allowed to interact with the application at the same time. After the connected list is full, if there is another control device connected, even if the kernel can generate a device node, the communication device will remove the control device because the connected list cannot be added. After the communication device removes the control device, the kernel will also delete the corresponding device node synchronously. However, in this case, when the user wants to change the control device, even if the control device that was previously requested to be connected is connected again, a series of processes such as generating device nodes and interacting with device nodes must be repeated, resulting in unnecessary waste of resources.

[0135] The connected list may be a list for storing information of connected devices, and the connected devices may be control devices that have been connected to the communication device and can interact with the server through the communication device. The waiting list may be a list for storing information of devices to be connected, and the waiting device may be a control device that has requested to access the communication device but is temporarily unable to access the communication device due to the upper limit of the number of connected devices.

[0136] In some feasible embodiments, at least one of the connected list and the to-be-connected list may be displayed through a display device so that the user can know the connection status of the control device.

[0137] In some feasible embodiments, when at least one of the connected list and the list to be connected has information updated, at least one of the connected list and the list to be connected may be displayed through a display device so that the user can know the connection change of the control device. For example, when a control device in the connected list is disconnected and a control device in the list to be connected is added to the connected list, the updated connected list and the list to be connected may be displayed through a display device.

[0138] In some embodiments, when it is determined that the first device node is able to interact, the current remaining capacity of the connected list is further detected, and the current remaining capacity is compared with the numerical value of a preset remaining capacity threshold; if the current remaining capacity is greater than the preset remaining capacity threshold, it means that the number of connected control devices has not yet reached the upper limit of the number of connected devices, and therefore the first control device can be connected to the communication device, and the information of the first control device is added to the connected list; if the current remaining capacity is less than or equal to the preset remaining capacity threshold, it means that the number of connected control devices has reached the upper limit of the number of connected devices, and no new control devices can be connected, and therefore, the information of the first control device is added to the list to be connected.

[0139] In this embodiment, by maintaining a list to be connected, it is possible to avoid the situation where the first control device is connected and then removed when the connected list is full. Since the first control device has not been removed by the communication device, the first device node will not be deleted. In this way, when the user wants to use the first control device, it is only necessary to replace the control device on the connected list with the first device node on the list to be connected, without repeating a series of processes such as generating device nodes and connecting to the communication device, thereby effectively saving resources. The saved resources can be used for other functions of the display device, thereby improving the stability and fluency of the overall use of the display device, which can also improve the user experience.

[0140] In some embodiments, the controller is further configured to:

[0141] When it is detected that any control device in the connected list is disconnected, selecting a second control device from the list to be connected;

[0142] The second control device is connected to the communication apparatus, and information of the second control device is added to the connected list.

[0143] It should be noted that when the connected list is full, if the user wants to change the control device that interacts with the application for information, he needs to first control the control device on the connected list to disconnect, and then control the new control device to connect to the display device, so as to ensure that the connected display device can be added to the connected list, so as to interact with the application for information, which has poor flexibility.

[0144] In some embodiments, during the process of the user manipulating the control device to interact with the server, the user can connect the control device to the display device at any time that is convenient for operation. When the connected list is full, the newly connected control device will be added to the list to be connected in a preset order, wherein the preset order can be the time order of device node generation, or the time order of determining that the device node can interact, or the priority order set by the user, etc. Furthermore, when any control device in the connected list is too low in power, or the user performs a disconnection operation to disconnect any control device in the connected list from the display device, the control device is disconnected from the display device. In this case, the information of the disconnected control device can be removed from the connected list, and the control device with the highest priority order is obtained from the list to be connected in a preset order as the information of the second control device, and the second control device is reconnected based on the information of the second control device, and the second control device is connected to the communication device through the reconnection, and the information of the second control device is added to the connected list.

[0145] In this embodiment, after any control device in the connected list is disconnected, the second control device is automatically selected and reconnected from the to-be-connected list, thereby achieving automatic replacement of the connected control device. In this way, when any control device in the connected list is disconnected due to low battery or malfunction, the user only needs to put down the disconnected control device and pick up the second control device to continue the operation. The entire process requires almost no pause of the application interaction process by the user. For example, if the user is currently in a cloud game, the user's game operation will hardly be affected, and only a control device needs to be changed, which effectively improves the smoothness of the user's operation, thereby improving the user experience.

[0146] In some embodiments, in the process of connecting the second control device to the communication apparatus and adding the information of the second control device to the connected list, the controller is further configured to:

[0147] Connecting the second control device to the communication device;

[0148] When it is determined that the second control device is connected to the communication apparatus, the information of the second control device is added to the connected list, and the information of the second control device is deleted from the to-be-connected list.

[0149] In some embodiments, after selecting the second control device from the list to be connected, you can reconnect to the second control device based on the information of the second control device. Since the second control device in the list to be connected was connected to the display device some time ago, there may be a situation where the reconnection is unsuccessful. Therefore, you can first detect whether the second control device is successfully connected to the communication device. In the case where it is determined that the second control device has successfully connected to the communication device, the information of the second control device is added to the connected list, and the information of the second control device is deleted from the list to be connected to avoid interfering with the subsequent reconnection process. In the case where it is determined that the second control device cannot access the communication device, you can try to reconnect multiple times until the access is successful, or until the preset reconnection number threshold is reached, it is determined that the second control device has failed to reconnect, and the second control device is selected from the list to be connected again; alternatively, it can also be directly determined that the second control device has failed to reconnect, and the second control device is selected from the list to be connected again.

[0150] In this embodiment, by first determining that the second control device can access the communication device and then adding the information of the second control device to the connected list, unnecessary writing and deleting operations caused by the inability of the second control device to connect back can be reduced, thereby effectively saving resources. The saved resources can be used for other functions of the display device, thereby improving the stability and smoothness of the overall use of the display device, which can also improve the user experience.

[0151] In some embodiments, after the second control device is connected to the communication apparatus, the controller is further configured to:

[0152] When it is determined that the second control device is not connected to the communication apparatus, the information of the second control device is deleted from the to-be-connected list, and the process returns to the step of selecting the second control device from the to-be-connected list.

[0153] In some embodiments, since the second control device has been previously connected to the display device and its corresponding device node has also been generated, in this case, if it is determined that the second control device cannot access the communication device, it is usually not because the preparation of the device node has not been completed. In this case, it is usually impossible to establish a connection between the second control device and the display device by reconnecting, and it is necessary to re-initiate the connection between the second control device and the display device. In order to reduce the impact of the reconnection on the user's current operations, the information of the second control device can be deleted from the list to be connected, and the step of selecting the second control device from the list to be connected is returned to execute, and the second control device is reselected until a second control device that can successfully reconnect is selected.

[0154] In this embodiment, by immediately reselecting the second control device from the list to be connected when the reconnection fails, the time for switching the control device can be effectively shortened, the time for the user to suspend application interaction and wait for the control device to be switched can be shortened, the user's operation fluency can be improved, and the user experience can also be improved.

[0155] In some embodiments, after the second control device is connected to the communication apparatus, the controller is further configured to:

[0156] The connection reminder information is displayed through the second control device.

[0157] The connection reminder information may include audio, light, vibration, etc., which are used to remind the user of the newly connected communication device, which can be used to control the device to interact with the server. For example, a user has multiple devices to be connected and multiple connected devices. After the connected device is disconnected, the user is immersed in the game and suddenly finds that the control device in his hand cannot interact with the game. At this time, the second control device is newly connected to the communication device. The second control device can emit light, audio or vibration to remind the user to put down the disconnected control device in his hand, accurately pick up the second control device displaying the connection reminder information from the many devices to be connected, and continue the game.

[0158] In this embodiment, by displaying connection reminder information, the user can be instructed to accurately find the second control device after the switch when the control device is switched, thereby shortening the time the user takes to find the control device after the control device is switched, thereby shortening the time the user pauses application interaction and waits for the control device to be switched, thereby improving the user's operation fluency and user experience.

[0159] In some embodiments, a control device connection method is provided, such as Figure 7 As shown, the control device connection method can be implemented by a display device, the display device includes: a display, a communication device, a lightweight device manager and a controller; the control device connection method includes the following steps:

[0160] Step 702: when the communication device receives a device access notification sent by the lightweight device manager, determine a first control device corresponding to the device access notification;

[0161] Step 704, interacting with a first device node corresponding to the first control device, the first device node being configured as an interaction interface of the first control device;

[0162] Step 706: When it is determined that the first device node can interact, connect the first control device to the communication device.

[0163] In some embodiments, a connected list and a to-be-connected list are stored on the communication device; connecting the first control device to the communication device includes:

[0164] When it is detected that the current remaining capacity of the connected list is greater than a preset remaining capacity threshold, connecting the first control device to the communication device and adding information of the first control device to the connected list;

[0165] When it is detected that the current remaining capacity of the connected list is less than or equal to the preset remaining capacity threshold, the information of the first control device is added to the to-be-connected list.

[0166] In some embodiments, the method further comprises:

[0167] When it is detected that any control device in the connected list is disconnected, selecting a second control device from the list to be connected;

[0168] The second control device is connected to the communication apparatus, and information of the second control device is added to the connected list.

[0169] In some embodiments, connecting the second control device to the communication apparatus and adding information of the second control device to the connected list includes:

[0170] Connecting the second control device to the communication device;

[0171] When it is determined that the second control device is connected to the communication apparatus, the information of the second control device is added to the connected list, and the information of the second control device is deleted from the to-be-connected list.

[0172] In some embodiments, after connecting the second control device to the communication apparatus, the method further includes:

[0173] When it is determined that the second control device is not connected to the communication apparatus, the information of the second control device is deleted from the to-be-connected list, and the process returns to the step of selecting the second control device from the to-be-connected list.

[0174] In some embodiments, after connecting the second control device to the communication apparatus, the method further includes:

[0175] The connection reminder information is displayed through the second control device.

[0176] In some embodiments, after interacting with the first device node corresponding to the first control device, the method further includes:

[0177] When it is determined that the first device node cannot interact, the step of interacting with the first device node corresponding to the first control device is executed repeatedly until it is determined that the first device node can interact, and the first control device is connected to the communication device.

[0178] In some embodiments, the step of cyclically executing the interaction with the first device node corresponding to the first control device includes:

[0179] Get the current loop count;

[0180] When it is determined that the current number of cycles does not exceed the preset number of cycles threshold, the process returns to the step of interacting with the first device node corresponding to the first control device, and updates the current number of cycles.

[0181] In some embodiments, when it is determined that the current number of cycles does not exceed the preset number of cycles threshold, before returning to the step of interacting with the first device node corresponding to the first control device and updating the current number of cycles, the method further includes:

[0182] Query the historical connection time of the first control device and the target number of cycles corresponding to the historical connection time, where the target number of cycles is positively correlated with the historical connection time;

[0183] The target cycle number is determined as a preset cycle number threshold.

[0184] In this embodiment, when the communication device receives the device access notification sent by the lightweight device manager, the first control device corresponding to the device access notification is determined, and the first device node corresponding to the first control device is first tried to interact. When it is determined that the first device node can interact, the first control device is connected to the communication device. In this way, even if the lightweight device manager notifies the communication device to access the device before the device node of the first control device is generated due to the lack of a rule file for behavior control, it can also ensure that when the first control device accesses the communication device, the first device node has been generated and can interact, so that the first control device can smoothly access the communication device, avoiding the situation where the first control device fails to access the communication device because the communication device cannot interact with the device node after the first control device accesses the communication device, that is, it can avoid the situation where the first control device fails to access the communication device, resulting in the first control device being unable to communicate with the server through the communication device after accessing the display device, thereby failing to control the cloud game. Therefore, the method of connecting the control device to the display device in this application can better adapt to the low-performance platform, improve the success rate of the low-performance platform accessing the control device, and also improve the fluency of the low-performance platform control device access operation.

[0185] In an exemplary embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and the method of the above embodiment is implemented when the processor executes the computer program.

[0186] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the method of the above embodiment is implemented.

[0187] In one embodiment, a computer program product is provided, including a computer program, which implements the method of the above embodiment when executed by a processor.

[0188] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

[0189] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0190] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0191] The above embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A display device, characterized in that: include: a display configured to display a user interface; A communication device configured to establish a communication connection with a server; A lightweight device manager configured to perform data management on the control device; The controller is configured as: In a case where the communication device receives a device access notification sent by the lightweight device manager, determining a first control device corresponding to the device access notification; interacting with a first device node corresponding to the first control device, the first device node being configured as an interaction interface of the first control device; When it is determined that the first device node is capable of interacting, the first control device is connected to the communication apparatus.

2. The display device according to claim 1, characterized in that The communication device stores a connected list and a to-be-connected list; In the process of connecting the first control device to the communication apparatus, the controller is further configured to: When it is detected that the current remaining capacity of the connected list is greater than a preset remaining capacity threshold, connecting the first control device to the communication apparatus and adding information of the first control device to the connected list; When it is detected that the current remaining capacity of the connected list is less than or equal to a preset remaining capacity threshold, the information of the first control device is added to the to-be-connected list.

3. The display device according to claim 2, characterized in that The controller is further configured to: When it is detected that any control device in the connected list is disconnected, selecting a second control device from the to-be-connected list; The second control device is connected to the communication apparatus, and information of the second control device is added to the connected list.

4. The display device according to claim 3, characterized in that In the process of connecting the second control device to the communication apparatus and adding the information of the second control device to the connected list, the controller is further configured to: Connecting the second control device to the communication device; In the case where it is determined that the second control device is connected to the communication apparatus, the information of the second control device is added to the connected list, and the information of the second control device is deleted from the to-be-connected list.

5. The display device according to claim 4, characterized in that After the second control device is connected to the communication apparatus, the controller is further configured to: When it is determined that the second control device is not connected to the communication apparatus, the information of the second control device is deleted from the to-be-connected list, and the process returns to the step of selecting the second control device from the to-be-connected list.

6. The display device according to claim 3, characterized in that After the second control device is connected to the communication apparatus, the controller is further configured to: The connection reminder information is displayed through the second control device.

7. The display device according to any one of claims 1 to 6, characterized in that: After the first device node corresponding to the first control device interacts, the controller is further configured to: When it is determined that the first device node cannot interact, the step of interacting with the first device node corresponding to the first control device is executed repeatedly until it is determined that the first device node can interact, and the first control device is connected to the communication device.

8. The display device according to claim 7, characterized in that In the process of executing the step of cyclically executing the step of interacting with the first device node corresponding to the first control device, the controller is further configured to: Get the current loop count; When it is determined that the current number of cycles does not exceed the preset number of cycles threshold, the step of interacting with the first device node corresponding to the first control device is returned to be executed, and the current number of cycles is updated.

9. The display device according to claim 8, characterized in that In the case where it is determined that the current number of cycles does not exceed the preset number of cycles threshold, before returning to the step of interacting with the first device node corresponding to the first control device and updating the current number of cycles, the controller is further configured to: Querying a historical connection time of the first control device and a target number of cycles corresponding to the historical connection time, wherein the target number of cycles is positively correlated with the historical connection time; The target cycle number is determined as a preset cycle number threshold.

10. A control device connection method, characterized in that: The method is applied to the display device according to any one of claims 1 to 9, comprising: In a case where the communication device receives a device access notification sent by the lightweight device manager, determining a first control device corresponding to the device access notification; interacting with a first device node corresponding to the first control device, the first device node being configured as an interaction interface of the first control device; When it is determined that the first device node is capable of interacting, the first control device is connected to the communication apparatus.

Images