An application management method and display device

Abstract

This application discloses an application management method and a display device. The method includes: after detecting that the display device has completed power-on and is connected to the network, controlling the application manager to send a first instruction to the application corresponding to the application identifier information in the application list. The first instruction is used to instruct the application to maintain a background running mode after preloading the application process. In response to the operation of launching a target application, controlling the application manager to send a second instruction to the target application and a third instruction to non-target applications. The second instruction is used to instruct the application to switch to a foreground running mode, and the third instruction is used to instruct the application to terminate the background running mode. This application can improve the application startup speed and, while the target application is running in the foreground, terminate the background running mode of other non-target applications, reducing the controller's workload and ensuring that foreground applications can run normally and stably.

Description

Technical Field

[0001] This application relates to the field of display device technology, and in particular to an application management method and a display device. Background Technology

[0002] When a user launches an application installed on a display device, the device needs to load the application process and resources. Once loaded, the application interface is displayed. During the application loading process, the display device may show a pre-set loading prompt page or an advertisement that appears when the application launches. From the time the user clicks the application icon to the display of the application interface, it often takes several seconds or even tens of seconds, resulting in slow application startup speed and long waiting times for the user. Summary of the Invention

[0003] To address the aforementioned technical problems, embodiments of this application provide an application management method and a display device.

[0004] A first aspect embodiment provides a display device, comprising:

[0005] monitor;

[0006] The controller is configured to execute:

[0007] After detecting that the display device has been powered on and connected to the network, the control application manager sends a first instruction to the application corresponding to the application identification information in the application list. The first instruction is used to instruct the application to maintain background running mode after the application process has been preloaded.

[0008] In response to the operation of launching the target application, the control application manager sends a second instruction to the target application and a third instruction to the non-target application; wherein, the second instruction is used to instruct the target application to switch to foreground running mode, and the third instruction is used to instruct the non-target application to terminate background running mode;

[0009] Control the display to show the application interface of the target application.

[0010] In some embodiments, the controller is also configured to perform:

[0011] In response to the operation of closing the target application, the control application manager sends a fourth instruction to the target application and sends the first instruction to the non-target application; wherein, the fourth instruction is used to instruct the application to switch to background running mode;

[0012] Control the display to close the application interface of the target application.

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

[0014] Detect current memory usage;

[0015] If the memory usage rate is detected to be greater than the first threshold, query the first application, which includes at least one of the applications currently running in the background.

[0016] The control application manager sends the third instruction to the first application.

[0017] In some embodiments, after the controller executes the control application manager to send the third instruction to the first application, it is also configured to execute:

[0018] If the memory usage rate is detected to drop below a first threshold, the application manager is controlled to send the first instruction to the first application.

[0019] In some embodiments, the controller is also configured to perform:

[0020] In response to the operation of launching a second application, it is detected whether there is an application currently running in the foreground mode; wherein, the second application is the application launched by the controller when it receives a trigger command from a preset button sent by the control device;

[0021] If there is no application currently running in the foreground, the application manager sends the second instruction to the second application to control the display to show the application interface of the second application.

[0022] If there is an application currently running in the foreground, the application manager sends the first instruction to the second application.

[0023] In some embodiments, the controller is also configured to perform:

[0024] In response to the operation of launching the target application, the control application manager does not send the third instruction to the second application, so that the second application remains in background running mode; wherein, the second application is the application launched by the controller when it receives a preset button trigger instruction sent by the control device;

[0025] In response to launching the second application, the control application manager sends the fourth or fifth instruction to the target application; wherein the fifth instruction is used to instruct the target application to terminate the application process;

[0026] The control application manager sends the second instruction to the second application, controlling the display to show the application interface of the second application.

[0027] In some embodiments, the display device further includes a memory, and the controller is further configured to perform:

[0028] Receive background startup completion information reported by the application manager; wherein, the third application is the application that received the first instruction, and the background startup completion information is sent by the third application to the application manager after responding to the first instruction;

[0029] Save the application data of the third application that has been loaded in memory to the storage device;

[0030] If the memory usage rate is detected to be greater than the first threshold, the application manager is controlled to send the third instruction to the third application to keep the application data in the memory unchanged.

[0031] When the memory usage rate is detected to drop below a first threshold, the control application manager sends a sixth instruction to the third application; the sixth instruction is used to instruct the third application to read the application data stored in the memory into memory and then maintain the background running mode.

[0032] In some embodiments, the controller includes a plurality of CPU processors, and the controller is further configured to perform:

[0033] When the target application is detected to be running in the foreground, the number of processes running on multiple CPU processors is detected.

[0034] If the number of processes running on the target CPU processor is detected to be greater than the second threshold, the binding relationship between the non-target application and the target CPU processor is released, so that the target CPU processor is bound only to the target application; wherein, the binding relationship is used to allow the application to run only on the bound CPU processor;

[0035] In response to the operation of closing the target application, the binding relationship between the non-target application and the target CPU processor is re-established.

[0036] In some embodiments, the application list includes applications already installed on the local machine, or the application list includes applications with preloading permissions, which means allowing the application process to be preloaded and kept running in the background before the user launches the application.

[0037] A second aspect embodiment provides an application management method, the method comprising:

[0038] After detecting that the display device has been powered on and connected to the network, the control application manager sends a first instruction to the application corresponding to the application identification information in the application list. The first instruction is used to instruct the application to maintain background running mode after the application process has been preloaded.

[0039] In response to launching the target application, the control application manager sends a second instruction to the target application and a third instruction to the non-target application; wherein the second instruction is used to instruct the application to switch to foreground running mode, and the third instruction is used to instruct the application to terminate background running mode.

[0040] Other implementation methods for the second aspect are adaptable to the first aspect mentioned above, and will not be repeated here.

[0041] The application manager controls the running status of each application, which includes pre-loading application processes, background running mode, and foreground running mode. In foreground running mode, the user can perceive that the application has started, view the application page, and request the application's related business functions. In background running mode, the display device does not display the application page, and the user cannot request the application's related business functions. Pre-loading application processes refers to loading application data such as application processes and application page resources in the background in advance, so that when the user starts the application, there is no need to wait for the application to load. The display device directly switches the application to foreground running mode, which can skip loading prompt pages or advertisements displayed when the application starts and directly display the application interface. In this embodiment, due to the uncertainty of user operations, the display device cannot predict which application the user will launch. Therefore, the application manager can control all applications in the application list to preload their application processes. After loading, the application processes are kept in the background running mode. In this way, when the user launches any target application, the display device does not need to launch or load the application process again. Instead, it directly switches the target application from the background running mode to the foreground running mode, which improves the application launch speed. Furthermore, when the target application is running in the foreground, the background running mode of other non-target applications is terminated, reducing the operating load of the controller and ensuring that the foreground application can run normally and stably. Attached Figure Description

[0042] Figure 1 Some embodiments illustrate operational scenarios between the display device and the control device 100;

[0043] Figure 2 Hardware configuration block diagrams of the control device 100 in some embodiments are shown;

[0044] Figure 3 A hardware configuration block diagram of a display device 200 in some embodiments is shown;

[0045] Figure 4 A software configuration diagram of the display device 200 in some embodiments is shown;

[0046] Figure 5 A schematic diagram of the interface when an application is launched is shown in some embodiments;

[0047] Figure 6A schematic diagram of the interface when another application is launched is shown in some embodiments;

[0048] Figure 7 A schematic diagram of the application management page in some embodiments is shown;

[0049] Figure 8 The following diagram illustrates the variations of the application management page in some embodiments. Figure 1 ;

[0050] Figure 9 The following diagram illustrates the variations of the application management page in some embodiments. Figure 2 ;

[0051] Figure 10 The following are application management logic diagrams illustrating the display device after it is powered on and connected to the network in some embodiments;

[0052] Figure 11(a) illustrates the application management logic when a user launches a target application in some embodiments. Figure 1 ;

[0053] Figure 11(b) illustrates the application management logic when a user closes a target application in some embodiments. Figure 1 ;

[0054] Figure 12(a) illustrates the application management logic when a user launches a target application in some embodiments. Figure 2 ;

[0055] Figure 12(b) illustrates the application management logic when a user closes a target application in some embodiments. Figure 2 ;

[0056] Figure 13(a) shows an application management logic diagram for when memory is insufficient in some embodiments;

[0057] Figure 13(b) shows an application management logic diagram when memory is fully restored in some embodiments;

[0058] Figure 14(a) illustrates the application management logic when a user launches a target application in some embodiments. Figure 3 ;

[0059] Figure 14(b) illustrates the application management logic when a user launches a hotkey application in some embodiments. Figure 1 ;

[0060] Figure 14(c) illustrates the application management logic when a user closes a hotkey application in some embodiments. Figure 1 ;

[0061] Figure 15(a) illustrates the application management logic when a user launches a target application in some embodiments. Figure 4 ;

[0062] Figure 15(b) illustrates the application management logic when a user launches a hotkey application in some embodiments. Figure 2 ;

[0063] Figure 15(c) illustrates the application management logic when a user closes a target application in some embodiments. Figure 3 ;

[0064] Figure 15(d) shows the application management logic diagram when a user relaunches the hotkey application in some embodiments;

[0065] Figure 16(a) shows a schematic diagram of backup storage of application data for a third application in some embodiments;

[0066] Figure 16(b) illustrates the application management logic and memory storage state when memory is insufficient in some embodiments;

[0067] Figure 16(c) shows a schematic diagram of application management logic and memory loading data when memory is fully restored in some embodiments;

[0068] Figure 17 Schematic diagrams of the multi-core controller in some embodiments are shown;

[0069] Figure 18(a) shows a logic diagram of a multi-core controller controlling the CPU processor and application binding in some embodiments;

[0070] Figure 18(b) shows a logic diagram of the controller performing core processing when memory is insufficient in some embodiments;

[0071] Figure 18(c) shows a logic diagram of restoring the binding relationship between the CPU processor and the application when memory is sufficient in some embodiments;

[0072] Figure 19 The diagram shows the interface when the application is launched after the aforementioned application management is performed, as illustrated in some embodiments. Detailed Implementation

[0073] To make the objectives and implementation methods of this application clearer, the exemplary implementation methods of this application will be clearly and completely described below with reference to the accompanying drawings of the exemplary embodiments of this application. Obviously, the exemplary embodiments described are only some embodiments of this application, and not all embodiments.

[0074] 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.

[0075] The terms "first," "second," "third," "fourth," 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 can be used interchangeably where appropriate.

[0076] 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.

[0077] The display device provided in this application can have various implementation forms, such as a television, a smart television, a laser projection device, a monitor, an electronic bulletin board, an electronic table, etc. Figure 1 and Figure 2 This is one specific embodiment of the display device of this application.

[0078] Figure 1 This is a schematic diagram illustrating the operational scenario between the display device and the control unit 100 according to an embodiment. Figure 1 As shown, the user can operate the display device 200 through the smart device 300 or the control device 100.

[0079] In some embodiments, the control device 100 may be a remote control, and the communication between the remote control and the display device includes infrared protocol communication or Bluetooth protocol communication, as well as other short-range communication methods, to control the display device 200 wirelessly or via wired means. Users can control the display device 200 by inputting user commands through buttons on the remote control, voice input, control panel input, etc. Alternatively, the control device 100 may also be a mouse, which can be connected to the display device via wired or wireless means.

[0080] In some embodiments, a smart device 300 (such as a mobile terminal, tablet computer, computer, laptop computer, etc.) may also be used to control the display device 200. For example, an application running on the smart device may be used to control the display device 200.

[0081] In some embodiments, the display device may receive instructions not through the aforementioned smart devices or control devices, but through touch or gestures.

[0082] In some embodiments, the display device 200 also communicates with the server 400. The display device 200 may communicate via a local area network (LAN), wireless local area network (WLAN), and other networks. The server 400 may provide various content and interactive features to the display device 200. The server 400 may be a cluster or multiple clusters, and may include one or more types of servers.

[0083] Figure 2 The diagram shows a configuration block diagram of the control device 100 according to exemplary embodiments in some examples. For example... Figure 2 As shown, the control device 100 includes a controller 110, a communication interface 130, a user input / output interface 140, a memory, and a power supply. The control device 100 can 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.

[0084] In some embodiments, such as Figure 3 As shown, the display device 200 includes at least one of the following: a tuner 210, a communicator 220, a detector 230, an external device interface 240, a controller 250, a display 260, an audio output interface 270, a memory, a power supply, and a user interface.

[0085] In some embodiments, the controller includes a processor, a video processor, an audio processor, a graphics processor, RAM, ROM, and a first interface to an nth interface for input / output.

[0086] The display 260 includes a display screen assembly for presenting images, a driving assembly for driving image display, a component for receiving image signals from the controller output, and a user control UI interface for displaying video content, image content, menu control interface, and user control UI interface.

[0087] The display 260 may be a liquid crystal display 260, an OLED display 260, or a projection display 260, and may also be a projection device and a projection screen.

[0088] The communicator 220 is a component used to communicate with external devices or servers according to various communication protocol types. For example, the communicator may include at least one of the following: 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.

[0089] The user interface can be used to receive control signals from the control device 100 (such as an infrared remote control, mouse, etc.).

[0090] The external device interface 240 may include, but is not limited to, one or more of the following: High Definition Multimedia Interface (HDMI), analog or 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.

[0091] 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 monitor 260, the controller 250 can execute operations related to the object selected by the user command.

[0092] In some embodiments, the controller includes at least one of a central processing unit (CPU), a video processor, an audio processor, a graphics processing unit (GPU), RAM (random access memory), ROM (read-only memory), a first to an nth interface for input / output, a communication bus, etc.

[0093] Users can input commands through a graphical user interface (GUI) displayed on the monitor 260, and the user input interface receives the user input commands through the GUI. Alternatively, users can input commands by entering specific sounds or gestures, and the user input interface receives the user input commands by recognizing the sounds or gestures through sensors.

[0094] A "user interface" is the medium through which an application or operating system interacts and exchanges information with the user. It converts information from its internal form to a form that the user can accept. A common form of user interface is the graphical user interface (GUI), which refers to a user interface related to computer operation displayed graphically. It can be an icon, window, control, or other interface element displayed on the screen of an electronic device. Controls can include visual interface elements such as icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, and widgets.

[0095] In some embodiments, such as Figure 4 As shown, the display device system is divided into three layers, from top to bottom: the application layer, the middleware layer, and the hardware layer.

[0096] In some embodiments, the application layer mainly includes commonly used applications on the TV and an application framework. The commonly used applications are mainly applications developed based on browsers, such as HTML5 apps, and native apps.

[0097] In some embodiments, 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, etc., as well as the user interface for these functions (toolbar, status bar, menu, dialog box).

[0098] In some embodiments, native apps can support online or offline access, push notifications, or access to local resources.

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

[0100] In some embodiments, the hardware layer mainly includes a HAL interface, hardware, and drivers. The HAL interface is a unified interface for all TV chips, with the specific logic implemented by each chip. The drivers mainly include: audio drivers, display drivers, Bluetooth drivers, camera drivers, Wi-Fi drivers, USB drivers, HDMI drivers, sensor drivers (such as fingerprint sensors, temperature sensors, pressure sensors, etc.), and power drivers.

[0101] In some embodiments, for devices with the same or similar hardware and software structure as the aforementioned display device, the display device has an application installed, and the user can launch the target application by triggering the icon control of the target application through the home page or application center of the display device.

[0102] In some embodiments, when a display device launches a target application, it needs to initialize and load application data such as application processes and page resources in real time, such as... Figure 5 For example, in response to a user clicking the icon control of application A, the display device begins loading the process of application A. At this time, the user interface displays the default startup page or loading prompt page of application A. After the process of application A is loaded, the display device switches the user interface to the application interface of application A, such as displaying the default home page of application A.

[0103] In some embodiments, such as Figure 6As shown, when the display device loads the process of application A, it can also display the advertisement screen that application A displays when it starts up. The advertisement screen includes an advertisement image or video, as well as a skip control 61. If the user clicks the skip control 61, the display device skips the advertisement screen and goes directly to the home page of the target application. In addition, when launching certain applications, the display device can also first display the application's default launch page, and then seamlessly display the advertisement screen that is displayed when the application starts up.

[0104] Depend on Figure 5 and Figure 6 It is evident that it may take several seconds or even more than ten seconds from when a user clicks the application icon to when the application homepage is displayed, resulting in slow application startup speed and long waiting time for users to start the application. Furthermore, for display devices with built-in Linux systems, there is a lack of a unified application manager and its dynamic management mechanism, making it impossible to coordinate and manage applications based on factors such as application startup speed, memory, and CPU performance.

[0105] To solve the above-mentioned technical problems, in some embodiments, reference is made to Figure 3 The display device includes an application manager 251, which is controlled by a controller 250. The application manager 251 sends instruction information to each application to control its running state, which includes a pre-loading mode, a background running mode, and a foreground running mode. In the foreground running mode, the user can perceive that the application has started and can view the application page and request related business functions. In the background running mode, the display device does not display the application page, and the user cannot request related business functions. The pre-loading mode refers to pre-loading application data such as the application process and homepage resources in the background, and then keeping the application process running in the background. This way, after the user starts the application, there is no need to wait for the application to load; the display device directly switches the application to foreground running mode, skipping the preset startup page and the advertisements displayed when the application starts, and directly displaying the application homepage, thereby improving the application startup speed.

[0106] In some embodiments, the application manager 251 can record an application list, which includes application identifier information for all applications installed on the display device. The application manager 251 can manage the applications in the application list uniformly. The application list is not fixed; for example, when application B is newly installed on the display device, the identifier information of application B is added to the application list, and when application C is uninstalled on the display device, the identifier information of application C is removed from the application list. The display device can configure preloading permissions for all applications in the application list. The preloading permission means allowing the application process to be preloaded and kept in background running mode before the user launches the application.

[0107] In some embodiments, due to the limited memory of the display device, if multiple applications execute preloading mode simultaneously, it may lead to large memory consumption and cause problems such as display device lag. Therefore, preloading permissions can be set for some applications. If application A has preloading permissions, application manager 251 can control application A to execute preloading mode, so that when the user launches application A in the future, application A will be directly switched to foreground running mode, improving the startup speed of application A. If application B does not have preloading permissions, when the controller 250 receives the user's launch operation for application B, it controls application manager 251 to normal mode, that is, to load application data such as application process and homepage resources.

[0108] In some embodiments, the display device may add preloading permissions to applications according to preset rules. For example, applications may be sorted in descending order of usage frequency over a recent period, and preloading permissions may be set for the top N applications, where N represents a preset number. Alternatively, applications may be sorted in descending order of installation time, and preloading permissions may be set for the top N applications. The rules for setting preloading permissions are not limited to those described in this embodiment.

[0109] In some embodiments, users can access the system settings. Figure 7 The example application management page includes an authorized list 71 and a non-authorized list 72. The authorized list 71 contains the identifiers of applications with pre-loading permissions and their mapped revocation controls 711. The non-authorized list 72 contains the identifiers of applications without pre-loading permissions and their mapped authorization controls 721. (See reference...) Figure 8 For example, if application A is located in the authorized list 71, and the display device receives a click operation on the deauthorization control 711 mapped to application A, then the preloading permission for application A is revoked, and the identification information of application A is transferred to the unauthorized list 72. Then, the application manager 251 will no longer preload the process and application data of application A; for another example, refer to... Figure 9 In the example, application F is located in the unauthorized list 72. When the display device receives a click operation on the authorized control 721 mapped to application F, it adds preloading permissions to application F and transfers the identification information of application F to the authorized list 71. This embodiment allows users to set preloading permissions for applications as needed, improving the user experience.

[0110] In some embodiments, the application manager 251 can maintain an application list based on the authorization list 71 and add the application identification information contained in the authorization list 71 to the application list, so that the application list only contains the application identification information with preloading permissions.

[0111] In some embodiments, such as Figure 10As shown, after the controller 250 detects that the display device has been powered on and connected to the network, it controls the application manager 251 to send a first instruction to the application corresponding to each application identifier in the application list. The first instruction is used to instruct the application to start a preloading mode, that is, to instruct the application to preload the application process and maintain background running mode after the application process preloading is completed. After each application in the application list has completed the preloading mode, it can send background startup completion information to the application manager 251, so that the application manager 251 can determine that each application has completed background preloading. In this way, when the user launches any of the applications, there is no need to load the application process and homepage resources and other application data. Instead, the application is directly switched from background running mode to foreground running mode, so that the display skips the preset startup page and advertising screen and directly displays the application homepage, thereby improving the application startup speed.

[0112] In some embodiments, the application list may contain identification information of all applications installed on the display device. That is, the application list is equivalent to a combination of the authorized list 71 and the unauthorized list 72. The application manager 251 sets a first identifier for the identification information of applications with pre-loading permissions in the application list based on the authorized list 71. The first identifier indicates that the application has pre-loading permissions. Thus, the application manager 251 determines whether an application has pre-loading permissions by identifying whether its identification information contains the first identifier, and then decides whether to implement pre-loading mode or on-demand loading mode for each application. After detecting that the display device has completed power-on and is connected to the network, the controller 250 controls the application manager 251 to send a first instruction to the applications in the application list corresponding to the application identification information with the first identifier, and to receive background startup completion information returned by these applications. For applications without the first identifier, the on-demand loading mode is executed. The background startup completion information may contain the application's identification information.

[0113] In some embodiments, a user can launch the target application by clicking its icon control with a remote control or by inputting a command to launch the target application via voice. As shown in Figure 11(a), in response to the launch of the target application, the controller 250 controls the application manager 251 to send a second command to the target application and a third command to a non-target application. The second command instructs the application to switch to foreground mode, making the target application's homepage visible so that the user can request relevant business functions of the target application. The third command instructs the application to terminate background mode, causing the non-target application to end its application process and delete the resource data of the non-target application loaded in memory, thereby freeing up memory, reducing the operating load of the controller 250, ensuring that the target application in foreground mode can run normally and stably, and alleviating problems such as device lag.

[0114] In some embodiments, referring to FIG11(a), after the target application switches to the foreground running mode, the application manager 251 sends foreground running completion information; after a non-target application terminates its background running mode, it can send termination completion information to the application manager 251. Upon receiving the termination completion information, the application manager 251 determines that the non-target application has exited the background running mode. The termination completion information may include the identification information of the non-target application.

[0115] In some embodiments, as shown in FIG11(b), in response to the operation of closing the target application, the controller 250 controls the application manager 251 to send a fourth instruction to the target application. The fourth instruction is used to instruct the application to switch to background running mode. After the target application switches from foreground running mode to background running mode in response to the fourth instruction, it can send background switching completion information to the application manager 251. The background switching completion information may include the identification information of the target application.

[0116] In some embodiments, referring to FIG11(b), the controller 250 receives background startup completion information reported by the application manager 251. If it detects that there is no application currently in foreground running mode, it controls the application manager 251 to send the first instruction again to the non-target application that was previously terminated from background running. In response to the first instruction, the non-target application preloads the application process, maintains the background running mode after preloading is completed, and sends background startup completion information to the application manager 251.

[0117] In this embodiment, in response to the operation of closing the target application, the controller 250 does not directly terminate the target application process and release the memory occupied by the target application as in the conventional way. Instead, it switches the target application from foreground running mode to background running mode. This way, if the controller 250 detects that there is currently no foreground application, it does not need to control the application manager 251 to send a first instruction to the target application, thus avoiding the cumbersome process of first terminating the target application process and then reloading it, improving application management efficiency. The application manager 251 only needs to send a first instruction to non-target applications, causing them to preload their application processes and enter background running mode. At this time, all applications in the application list are in background running mode (equivalent to waiting to be launched in the foreground). In response to the user's operation to launch any of these applications, the controller 250 controls the application manager 251 to switch that application to foreground running mode, improving application launch speed.

[0118] In some embodiments, a user can launch multiple applications. For display devices that do not support split-screen display, only one application can run in the foreground, typically the most recently launched application. Other applications remain in the background. The user can switch the background application to the foreground using the application switcher on the display device. If the display device has split-screen display functionality, let the supported number of split screens be K. The controller 250 controls the display 260 to display K application windows on the user interface. Each application window displays one application page, thus allowing a maximum of K applications to run simultaneously in the foreground. For example, if the display device currently has K applications running in the foreground, in response to the operation of closing application S, the controller 250 controls the application manager 251 to send four instructions to application S, causing application S to switch to background running mode. The number of applications and application windows running in the foreground becomes K-1. In addition to the K-1 applications running in the foreground, other applications in the application list can maintain or terminate their background running mode.

[0119] In some embodiments, as shown in FIG12(a), in response to the operation of launching the target application, the controller 250 may also control the application manager 251 to send only the second instruction to the target application and not to send the third instruction to non-target applications. That is, when the target application is in the foreground running mode, the non-target application continues to maintain the background running mode. As shown in FIG12(b), in response to the operation of closing the target application, the controller 250 controls the application manager 251 to send a fourth instruction to the target application. The target application switches from the foreground running mode to the background running mode in response to the fourth instruction. Since the non-target application always maintains the background running mode, the application manager 251 does not send the first instruction to the non-target application. In this embodiment, when the display device has an application in the foreground running mode, keeping other applications in the background running mode simplifies the interaction between the application manager 251 and non-foreground applications. However, running multiple applications in the background will consume a lot of memory, especially for a single-core controller, which will lead to a high controller load, and thus cause problems such as lag in the display device and foreground applications.

[0120] In some embodiments, after the display device has been powered on and connected to the network, the controller 250 can monitor memory usage and compare it with a first threshold, wherein the first threshold can be set according to an upper limit of allowed memory consumption. If the memory usage is greater than the first threshold, it indicates that memory consumption is high, which can easily cause problems such as device lag.

[0121] In some embodiments, as shown in FIG13(a), if the controller 250 detects that the memory usage rate is greater than a first threshold, the controller 250 queries the first application, which includes at least one of the applications currently in background running mode (hereinafter referred to as background applications), and controls the application manager 251 to send a third instruction to the first application; the first application responds to the third instruction, terminates the background running mode, thereby ending the application process of the first application, releasing the memory consumed by the first application, and reducing the memory usage rate of the display device.

[0122] In some embodiments, let N represent the total number of background applications currently included in the display device, and M be the number of background applications included in the first application. If the first application includes all applications currently running in the background, i.e., M = N, then the application manager 251 sends a third instruction to the first application to close all background applications, thereby minimizing the memory usage of the display device and quickly releasing memory.

[0123] In some embodiments, if 1 ≤ M < N, the application manager 251 closes some background applications, while the other NM non-first applications remain in background operation mode. The display device can select which applications to classify as first applications and which to classify as non-first applications from the N background applications. For example, M applications can be randomly or arbitrarily selected as first applications from the N background applications; or, the first applications can be selected according to the order of the application list; or, according to the preset application priority, the M background applications with lower priority can be selected as first applications, and the other NM background applications with higher priority can be selected as non-first applications; or, the M background applications with lower usage frequency can be selected as first applications. The method of selecting the first application is not limited to this embodiment.

[0124] In some embodiments, if M is set to 1, the application manager 251 implements a debugging method that closes background applications one by one. For example, if the controller 125 detects that the memory usage is greater than a first threshold, it controls the application manager 251 to send a third instruction to background application X. After background application X terminates its background running mode, the memory usage will decrease. The controller 250 then compares the updated memory usage with the first threshold. If the updated memory usage is still greater than the first threshold, the controller 250 controls the application manager 251 to send a third instruction to background application Y, and so on, until the memory usage drops below the first threshold or all background applications are closed.

[0125] In some embodiments, the controller 250 can obtain the size of the memory to be released based on the difference between the memory usage rate and a first threshold, and automatically match the type and number of background applications that need to be closed by combining this with the memory consumed by each background application individually. For example, if the controller obtains that the memory to be released is 850MB, background application X consumes 300MB of memory, background application Y consumes 250MB of memory, and background application Z consumes 312MB of memory, then it can control the application manager 251 to send a third instruction to background applications X, Y, and Z, that is, the first application includes background applications X, Y, and Z, while other background applications remain in background running mode.

[0126] In some embodiments, as shown in FIG13(b), after the controller 250 controls the application manager 251 to close the first application, since memory usage is a dynamic parameter, if memory is sufficient, the controller 250 can also restore the first application to background running mode. Therefore, if the controller 250 detects that the memory usage has dropped below a first threshold, it controls the application manager 251 to send a first instruction to the first application; the first application responds to the first instruction, preloads application process and resource data, and after the preloading is completed, maintains background running mode.

[0127] In some embodiments, if the controller 250 detects that the memory usage rate has dropped below a first threshold, it can control the application manager 251 to implement a debug mode that restores background applications one by one to prevent the memory usage rate from exceeding the first threshold. For example, if the controller 125 detects that the memory usage rate is less than the first threshold, it controls the application manager 251 to send a first instruction to application A. After application A has finished preloading and entered background running mode, the memory usage rate will increase. The controller 250 then compares the updated memory usage rate with the first threshold. If the updated memory usage rate is still less than the first threshold, the controller 250 controls the application manager 251 to continue sending the first instruction to application B, and so on, until the memory usage rate rises to the first threshold, or all applications in the application list have started running (either in the foreground or in the background).

[0128] In some embodiments, the controller 250 can also obtain the available memory size based on the difference between the first threshold and the memory usage rate, and automatically match the types and number of applications that need to be preloaded in the background by combining the average memory consumption of applications running in the foreground and background. For example, if the controller 250 obtains that the available memory is 650MB, the average memory consumption of application C is 315MB, and the average memory consumption of application D is 256MB, then the controller 250 can control the application manager 251 to send a first instruction to application C and application D. After application C and application D have completed preloading and entered the background running mode, the memory usage rate will not exceed the first threshold.

[0129] In some embodiments, the display device may have a second application installed. This second application is an application that can be launched by a user by triggering a preset button on the control device 100, also known as a "hotkey application". The controller 250 receives operation instructions sent by the control device 100. If it recognizes that the key value contained in the operation instruction is mapped to a preset button (i.e., a hotkey), the controller 250 receives the operation to launch the second application.

[0130] In some embodiments, since the second application can be launched quickly with one click via the control device 100, the second application can be kept running in the background. As shown in FIG14(a), in response to the operation of launching the target application, the controller 250 controls the application manager 251 to send a second instruction to the target application. When sending a third instruction to a non-target application, the controller 250 does not send a third instruction to the second application, so that the second application keeps running in the background. Other non-target applications besides the second application can terminate the background running mode.

[0131] In some embodiments, as shown in FIG14(b), in response to the operation of launching the second application, the controller 250 controls the application manager 251 to send a second instruction to the second application to switch the second application from the background to the foreground, and controls the application manager 251 to send a fourth instruction or a fifth instruction to the target application to realize a quick switch from the target application to the second application after the hotkey is triggered. If the application manager 251 sends a fourth instruction to the target application, the target application ends the foreground running mode and enters the background running mode; if the application manager 251 sends a fifth instruction to the target application, the target application ends the foreground running mode and does not execute the background running mode, that is, the fifth instruction is used to make the target application terminate the application process, release the memory occupied by the target application, and send application termination information to the application manager 251.

[0132] In some embodiments, as shown in FIG14(c), in response to the operation of closing the second application, the controller 250 controls the application manager 251 to send a fourth instruction to the second application, causing the second application to exit the foreground running mode and switch to the background running mode. Figures 14(a) to 14(c) The provided embodiments enable hotkey applications to reside in the background. When a hotkey on the control device 100 is triggered, the display device switches the application running in the foreground to the hotkey application. Furthermore, it can skip the process of loading the hotkey application's process and resource data and directly display the hotkey application's homepage, thereby improving the startup speed of the hotkey application.

[0133] In some embodiments, as shown in FIG15(a), the controller 250 responds to the operation of launching the target application by controlling the application manager 251 to send a second instruction to the target application and a third instruction to non-target applications, including sending a third instruction to the second application, so that the second application and other non-target applications terminate the background running mode, ensuring that the target application can run stably in the foreground and alleviating problems such as device lag.

[0134] In some embodiments, as shown in FIG15(b), in response to the operation of launching a second application, the controller 250 detects that there is currently a target application running in the foreground mode, and controls the application manager 251 to send a first instruction to the second application. In response to the first instruction, the second application preloads application process and resource data, and then maintains the background running mode, waiting to be woken up by the foreground.

[0135] In this embodiment, in response to the operation of launching the second application, the controller 250 can detect whether there is currently an application in foreground running mode (hereinafter referred to as a foreground application). If there is currently no foreground application, that is, all applications in the application list are in background running mode and waiting to be woken up by the foreground, the controller 250 controls the application manager 251 to send a second instruction to the second application, thereby switching the second application to foreground running mode; if there is currently a foreground application, the display device may also temporarily not end the operation of the foreground application, and control the application manager to send a first instruction to the second application, so that the second application completes the preloading process in the background.

[0136] In some embodiments, as shown in FIG15(c), in response to the operation of closing the target application, the controller 250 controls the application manager 251 to send a fourth instruction to the target application, causing the target application to switch to background running mode. At this time, the controller 250 detects that there is no foreground application and controls the application manager 251 to send a first instruction to the non-target application. Since the second application is already in and remains in background running mode, the application manager 251 may no longer send the first instruction to the second application, or the second application may not respond to the first instruction sent by the application manager 251 again.

[0137] In some embodiments, as shown in FIG15(d), in response to the operation of restarting the second application, since there is currently no foreground application and the second application has completed preloading and is in background running mode, the controller 250 controls the application manager 251 to send a second instruction to the second application to switch the second application to foreground running mode, thereby improving the startup speed of the second application.

[0138] In some embodiments, the application receiving the first instruction from the application manager 251 is referred to as a "third application," as shown in Figure 16(a). In response to the first instruction, the third application preloads its own application process, maintains a background running mode after preloading, and sends background startup completion information to the application manager 251. Upon receiving the background startup completion information reported by the application manager 251, the controller 250 determines that all third applications have completed background preloading and saves the application data of the loaded third applications in memory to the storage device, thereby backing up the application data. The application data may include data related to the application process and homepage resources. When storing application data, the storage device can establish a mapping relationship between the application data and the third application.

[0139] In some embodiments, the controller 250 can monitor memory usage. As shown in Figure 16(b), if the controller 250 detects that the memory usage exceeds a first threshold, it controls the application manager 251 to send a third instruction to the third application, maintaining the storage state of the application data of the third application in the memory. In response to the third instruction, after the third application terminates its background running mode, the application data of the third application already loaded in memory is deleted to release the memory consumed by the third application during background operation and reduce memory usage. However, the application data stored in the memory remains unaffected.

[0140] In some embodiments, as shown in FIG16(c), when the controller 250 detects that the memory usage rate has dropped below a first threshold, it controls the application manager 251 to send a sixth instruction to the third application. In response to the sixth instruction, the third application reads the application data mapped to the third application stored in the memory into the memory and then maintains the background running mode. Figures 16(a) to 16(c) In the provided embodiment, after the third application completes background preloading, the controller backs up and stores the application data that has been loaded into memory. If the third application needs to resume background operation mode, it can copy the application data stored in the storage to memory, so that there is no need to request to load the application data again, thereby saving application loading process and resource time and improving application management efficiency.

[0141] In some embodiments, in response to the sixth instruction, the third application copies the application data mapped to the third application stored in the memory to the memory, maintains the background running mode, and sends background startup completion information to the application manager 251. The background startup completion information includes a target application identifier and a second identifier. The second identifier is used to indicate that the application data loaded into the memory by the third application comes from the memory, rather than being requested from the server.

[0142] In some embodiments, if the controller 250 receives background startup completion information reported by the application manager 251, it checks whether the background startup completion information contains a second identifier.

[0143] In some embodiments, if the background startup completion information does not contain a second identifier, indicating that the application data loaded in memory did not originate from the storage but was requested by the application from the server, the controller 250 checks whether the storage already contains application data mapped to the target application identifier. If the storage already contains application data mapped to the target application identifier, the controller 250 saves the target application data mapped to the target application identifier already loaded in memory to the storage and causes the storage to record the mapping relationship between the target application data and the target application identifier. If the storage already contains application data mapped to the target application identifier, the currently loaded target application data in memory replaces the previously loaded application data, thereby updating the application data in the storage.

[0144] In some embodiments, if the background startup completion information contains a second identifier, it indicates that the application data loaded in memory was not obtained by the application from the server, but came from the memory. It also indicates that the memory has previously stored the application data mapped to the target application identifier. Therefore, the controller 250 no longer controls the memory to repeatedly back up the application data.

[0145] In some embodiments, Figure 17 Example of a multi-core controller structure: controller 250 may include multiple CPU processors, let the number of CPU processors be Q, where Q is greater than 1. Controller 250 can schedule the Q CPU processors and control the binding of application processes to CPU processors, so that application processes can only run on CPU processors with binding relationships.

[0146] In some embodiments, as shown in FIG18(a), after the display device is powered on and connected to the network, the controller 250 sends a first instruction to each application corresponding to the application identifier information in the application list; in response to the first instruction, the application preloads the application process in the background and sends background startup completion information to the application manager 251; the controller 250 receives the background startup completion information reported by the application manager 251, and binds the application process mapped by the application identifier to Q CPU processors according to the application identifier contained in the background startup completion information, thereby establishing the binding relationship between the application and the Q CPU processors.

[0147] In some embodiments, as shown in FIG18(b), in response to the operation of launching the target application, the controller 250 controls the application manager 251 to send a second instruction to the target application, switching the target application to foreground running mode. Based on the high performance and core tuning characteristics of the multi-core controller, the controller 250 may not send a third instruction to non-target applications when controlling the application manager 251 to send the second instruction to the target application, allowing non-target applications to maintain background running mode.

[0148] In some embodiments, as shown in FIG18(b), the controller 250 can perform load monitoring on the Q CPU processors, for example, detecting the number of processes running on the Q CPU processors and comparing the number of processes running on the Q CPU processors with a second threshold. If the controller 250 finds a target CPU processor with a number of processes greater than the second threshold, for example, CPU processor 2 in FIG18(b) is the target CPU processor, it indicates that the target CPU processor is under high load (overload) and consumes a lot of processing resources when the target application is running in the foreground, which cannot guarantee the normal operation of the target application. Then the controller 250 can start the core tuning processing logic.

[0149] In some embodiments, as shown in FIG18(b), the core tuning processing logic can be configured such that the controller 250 unbinds the non-target application from the target CPU processor, so that the target CPU processor is bound only to the target application. In this way, the target CPU processor no longer runs non-target applications in the background, that is, it reduces the number of processes running on the target CPU processor, reduces its load, and thus provides sufficient processing resources for the target application running in the foreground, ensuring that the target application can run normally and stably.

[0150] In some embodiments, as shown in FIG18(c), in response to the operation of closing the target application, the controller 250 controls the application manager 251 to send a fourth instruction to the target application; in response to the fourth instruction, the target application exits the foreground, switches to background running mode, and sends background switching completion information to the application manager 251; when the controller 250 receives the background switching completion information reported by the application manager 251, the load of the target CPU processor decreases, and the controller 250 can control the application process of the non-target application to rebind with the target CPU processor, thereby restoring the binding relationship between the non-target application and the target CPU processor. Figures 18(a) to 18(c) The provided embodiments target multi-core controllers. By monitoring application running status and the load of Q CPUs, the operation and load of each CPU processor can be dynamically controlled through methods such as core binding and core tuning. This ensures the normal and stable operation of foreground applications and the entire machine, improving the efficiency and accuracy of application management and enhancing the user experience. The hardware and software configuration and application management logic of the multi-core controller are not limited to the embodiments of this application.

[0151] In some embodiments, such as when the controller includes CPU0, CPU1, CPU2, and CPU3, when application A is in foreground running mode, if the controller 250 detects that the number of processes running on CPU0 exceeds a second threshold, it determines CPU0 as the target CPU processor and controls the background application to unbind from CPU0, causing the background application to bind to CPU1, CPU2, and CPU3, while CPU0 only binds to application A. This reduces the load on CPU0, allowing it to have sufficient processing resources to maintain the normal operation of application A. In response to closing application A, the controller 250 can restore the binding relationship between the background application and CPU0.

[0152] This application embodiment utilizes the application configuration preloading capability to enable the display device to preload the application process and resources when the user has not launched the application, and then maintain a background running mode, waiting for the application to be woken up by the foreground. This way, when the user launches the application, compared to... Figure 5 and Figure 6 ,like Figure 19 As shown, the display device only needs to switch the application from background running mode to foreground running mode, skipping the process of loading application processes and resources, and directly displaying the application homepage, thus improving application startup speed. This application implements application management logic such as application startup, application running mode control, and application closure through control interaction between the controller 250, application manager 251, and the application, improving the efficiency of the application manager and precise control over applications, while also considering system memory and controller load. It provides an application management solution adapted to more application scenarios and display devices, especially for hotkey applications and multi-core controllers. The application startup page, application homepage, and application management page UI involved in this application are merely exemplary; the specific implementation should be based on the actual product and application. Those in the art can appropriately adjust and expand the application management logic of the embodiments of this application according to user scenarios, application characteristics, and display device performance configurations.

[0153] In some embodiments, this application also provides a computer storage medium that can store a program. When the computer storage medium is located in a display device, the program, when executed, can include program steps related to the application management method configured for the controller 250. The computer storage medium can be a magnetic disk, optical disk, read-only memory (ROM), or random access memory (RAM), etc.

[0154] 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.

[0155] For ease of explanation, the above description has been provided in conjunction with specific embodiments. However, the foregoing 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 made based on the foregoing teachings. The selection and description of the above embodiments are for the purpose of better explaining the contents of this disclosure, thereby enabling those skilled in the art to better utilize the described embodiments.

Claims

1. A display device, characterized by comprising: The application comprises: a display; a controller configured to perform: after detecting that the display device is powered on and has connected to a network, controlling the application manager to send a first instruction to an application corresponding to application identification information in an application list, the first instruction being used to instruct the application to enter and remain in a background running mode after completing preloading of an application process; the application list being pre-configured by a user in an application management page, the application management page comprising an authorized list and an unauthorized list, the authorized list comprising identification information of applications with preloading permissions and mapped de-authorization controls, and the unauthorized list comprising identification information of applications without preloading permissions and mapped authorization controls; in response to an operation of starting a target application, controlling the application manager to send a second instruction to the target application, wherein the second instruction is used to instruct the application to switch to a foreground running mode; detecting a current memory usage rate; if it is detected that the memory usage rate is greater than a first threshold, querying a first application in non-target applications, the first application comprising at least one of the applications currently in the background running mode; controlling the application manager to send a third instruction to the first application, wherein the third instruction is used to instruct the application to terminate the background running mode; controlling the display to display an application interface of the target application; in response to an operation of closing the target application, controlling the application manager to send a fourth instruction to the target application and the first instruction to the non-target applications; wherein the fourth instruction is used to instruct the application to switch to the background running mode; controlling the display to close the application interface of the target application.

2. The display device of claim 1, wherein, The controller, after controlling the application manager to send the third instruction to the first application, is further configured to: if it is detected that the memory usage rate decreases to less than the first threshold, controlling the application manager to send the first instruction to the first application.

3. The display device of claim 1, wherein, The controller is further configured to perform: in response to an operation of starting a second application, detecting whether there is currently an application in the foreground running mode; wherein the second application is an application started by the controller upon receiving a trigger instruction of a preset key sent by a control device; if there is currently no application in the foreground running mode, controlling the application manager to send the second instruction to the second application and controlling the display to display an application interface of the second application; if there is currently an application in the foreground running mode, controlling the application manager to send the first instruction to the second application.

4. The display device of claim 1, wherein, The controller is further configured to perform: in response to an operation of starting a target application, controlling the application manager not to send the third instruction to a second application, so as to make the second application remain in the background running mode; wherein the second application is an application started by the controller upon receiving a trigger instruction of a preset key sent by a control device; in response to an operation of starting the second application, controlling the application manager to send the fourth instruction or a fifth instruction to the target application; wherein the fifth instruction is used to instruct the target application to end the application process; controlling the application manager to send the second instruction to the second application and controlling the display to display an application interface of the second application.

5. The display device of claim 1, wherein, The display device further comprises a memory, and the controller is further configured to perform: receiving background start completion information reported by the application manager; the background start completion information is sent by a third application to the application manager in response to the first instruction, and the third application is the application that receives the first instruction; saving application data of the third application that has been loaded in the memory to the memory; if it is detected that the memory usage rate is greater than a first threshold value, controlling the application manager to send the third instruction to the third application, and keeping the storage state of the application data in the memory unchanged; when it is detected that the memory usage rate decreases to be less than the first threshold value, controlling the application manager to send a sixth instruction to the third application; the sixth instruction is used to instruct the third application to read the application data saved in the memory to the memory and keep the background running mode.

6. The display device of claim 1, wherein, The controller comprises a plurality of CPU processors, and the controller is further configured to perform: detecting the number of processes running on the plurality of CPU processors when it is detected that the target application is in the foreground running mode; if it is detected that the number of processes running on a target CPU processor is greater than a second threshold value, releasing a binding relationship between non-target applications and the target CPU processor, so that the target CPU processor is only bound to the target application; wherein the binding relationship is used to allow the application to run only in the bound CPU processor; in response to an operation of closing the target application, re-establishing the binding relationship between the non-target applications and the target CPU processor.

7. The display device of claim 1, wherein, The application list comprises native installed applications, or the application list comprises applications with preloading permissions, and the preloading permission refers to allowing an application process to be preloaded and kept in a background running mode before a user starts the application.

8. An application management method characterized by comprising: The method comprises: after it is detected that the display device is powered on and has connected to a network, controlling the application manager to send a first instruction to an application corresponding to application identification information in an application list; the first instruction is used to instruct the application to enter and keep a background running mode after a preloaded application process is completed; the application list is preconfigured by a user in an application management page; the application management page comprises an authorized list and a non-authorized list; the authorized list comprises identification information of applications with preloading permissions and mapped de-authorization controls; and the non-authorized list comprises identification information of applications without preloading permissions and mapped authorization controls; in response to an operation of starting a target application, controlling the application manager to send a second instruction to the target application; the second instruction is used to instruct the application to switch to a foreground running mode; detecting a current memory usage rate; if it is detected that the memory usage rate is greater than a first threshold value, querying a first application in non-target applications; the first application comprises at least one of the applications currently in the background running mode; controlling the application manager to send a third instruction to the first application; the third instruction is used to instruct the application to terminate the background running mode; In response to the operation of closing the target application, the application manager is controlled to send a fourth instruction to the target application and send the first instruction to the non-target application; wherein the fourth instruction is used to instruct the application to switch to a background running mode.

Images