CN117043733A

CN117043733A - Control processing method and display device

Info

Publication number: CN117043733A
Application number: CN202280017552.6A
Authority: CN
Inventors: 王光强; 薛梅; 杨绍栋; 高斯太; 赖园园
Original assignee: Juhaokan Technology Co Ltd
Current assignee: Juhaokan Technology Co Ltd
Priority date: 2021-03-04
Filing date: 2022-04-29
Publication date: 2023-11-10
Also published as: CN115037970B; CN115022695B; CN114510170A; CN115037971A; WO2022237603A1; CN114510170B; CN115037971B; CN115022695A; CN115037970A

Abstract

When the first service Widget control is detected to be deleted, determining and displaying an icon of a second service (S1701), wherein the size of the second service Widget control corresponding to the second service is the same as that of the first service Widget control; receiving an input selection of an icon of a second service (S1702); and displaying a second service Widget control of a second service corresponding to the selected icon at a first position (S1703), wherein the first position is a display position of the first service Widget control. According to the method and the device, the recommended interface can be filled in the original position when the deleted control is replaced, display of other original controls is not affected, and user experience is good.

Description

Control processing method and display device

The application claims priority to national intellectual property office, application number 202110505212.5, national intellectual property office, application number 202111526619.2, national intellectual property office, application number 202111531851.5, national intellectual property office, application number 202210066285.3, 2021, 20, 2021, 12, 14, 12, 14, 20, and the disclosure of which is incorporated herein by reference in its entirety.

Technical Field

The present application relates to the field of device display technologies, and in particular, to a control processing method and a display device.

Background

A display device, such as a smart television, may provide a user with a play screen such as audio, video, pictures, etc. Today, a display device can provide not only live television program content received through data broadcasting but also various applications and service content such as network video programs, network games, and the like to a user.

In the smart tv, the function generally realizes opening of the function interface through a conventional TAB portal or a shortcut key on the remote controller, for example, when a recommended control of the TAB bar is selected in focus, the smart tv displays a recommended page, and if a user selects a fitness control of the TAB bar, the smart tv displays a fitness interface. Or, the smart television can display the setting page through the setting key on the remote controller.

For controlling the focus, in the existing interaction mode, in the operation process, a user needs to return the focus to the TAB control and/or the default control corresponding to the current interface by returning, and then move on the TAB bar by the focus so as to open the interface corresponding to the target TAB entrance. If the corresponding entrance of the interface is positioned on the first-level page or the second-level page, the target TAB is selected first, the target first-level page is displayed, then the entrance on the first-level page is selected, or after entering the second-level page, the entrance on the second-level page is selected.

Disclosure of Invention

In a first aspect, the present application provides a display apparatus comprising: the display is configured to display a desktop homepage presenting a Widget panel, wherein a plurality of service Widget controls for providing a service module starting entrance are displayed in the Widget panel; a controller coupled to the display, the controller configured to:

when the first service Widget control is detected to be deleted, determining and displaying an icon of a second service, wherein the size of the second service Widget control corresponding to the second service is the same as that of the first service Widget control;

receiving an input selection of an icon of the second service;

and displaying a second service Widget control of a second service corresponding to the selected icon at the first position, wherein the first position is a display position of the first service Widget control.

In a second aspect, the present application provides a display apparatus comprising: the display is configured to display a desktop homepage presenting a Widget panel, wherein a plurality of service Widget controls for providing a service module starting entrance are displayed in the Widget panel; a controller coupled to the display, the controller configured to:

Determining and displaying an icon of a second service when the first service Widget control is detected to be deleted, wherein the size of the second service Widget control corresponding to the second service is not larger than that of a first position, and the first position is a display position of the first service Widget control and a blank position adjacent to the display position of the first service Widget control;

receiving an input selection of an icon of the second service;

and displaying a second service Widget control of a second service corresponding to the selected icon at the first position.

The application also provides a control display method, which comprises the following steps:

receiving an input selection of an icon of the second service;

Drawings

FIG. 1 is a schematic diagram of an operation scenario between a smart control device and a control apparatus according to some embodiments of the present application;

FIG. 2 is a block diagram of the hardware configuration of a smart control device 200 in some embodiments of the application;

fig. 3 is a block diagram showing a hardware configuration of the control apparatus 100 according to some embodiments of the present application;

FIG. 4 is a diagram of the configuration of software in the intelligent control device 200 according to some embodiments of the present application;

FIG. 5 is a diagram of a desktop control architecture in some embodiments of the application;

FIG. 6 is a flow chart of a control processing method in some embodiments of the application;

FIG. 7 is a data flow diagram of a control processing method in some embodiments of the application;

FIG. 8 is a schematic diagram of a system home page in accordance with some embodiments of the application;

FIG. 9 is a diagram of a desktop homepage in accordance with some embodiments of the present application;

FIG. 10 is a diagram illustrating a Widget panel in a desktop homepage according to some embodiments of the present application;

fig. 11 is a schematic diagram showing a failure identifier on a service Widget control of a Widget panel according to some embodiments of the present application;

fig. 12 is a schematic diagram showing a failure identifier on a service Widget control for offloading a remote application according to some embodiments of the present application;

FIG. 13 is a schematic diagram of a failure notification interface according to some embodiments of the application;

FIG. 14 is a schematic diagram of a Widget panel that alternatively displays specified recommended Widget controls in some embodiments of the present application;

FIG. 15 is a schematic diagram of a Widget panel display space in some embodiments of the present application;

FIG. 16 is a schematic diagram of a control recommendation interface in some embodiments of the application;

FIG. 17 is a diagram illustrating a control display method according to some embodiments of the application;

FIG. 18 is a schematic diagram of an interface displaying an indication arrow when a control is deleted in some embodiments of the application;

FIG. 19 is a schematic diagram of an interface for displaying a delete prompt control when a control is deleted in some embodiments of the application;

FIG. 20 is a schematic diagram of an interface for displaying a delete prompt when a control is deleted in some embodiments of the application;

FIG. 21 is a schematic diagram of a display interface after a control is deleted in some embodiments of the application;

FIG. 22 is a schematic diagram of a display interface after the movement of the control is completed in some embodiments of the application;

FIG. 23 is a schematic diagram of a user interface shown in some embodiments of the application;

FIG. 24 is a television system home page under one possible "juvenile" theme shown in some embodiments of the present application;

FIG. 25 is a diagram of one possible juvenile mode system home page shown in some embodiments of the present application;

FIG. 26 is a user interface including a Widget panel in a globally locked state, shown in some embodiments of the application;

FIG. 27A is a diagram of one possible password entry interface shown in some embodiments of the application;

FIG. 27B is a user interface including a Widget panel after unlocking, according to some embodiments of the application;

FIG. 28 is a user interface including a Widget panel in a partially locked state, shown in some embodiments of the application;

FIG. 29 is a user interface displayed after unlocking an "application center" control, as shown in some embodiments of the application;

FIG. 30 is a display after unlocking an "application center" control, as shown in some embodiments of the application;

FIG. 31 is a user interface after expanding the "AI little finger" control as shown in some embodiments of the application;

FIG. 32 is a user interface after expanding an "application center" control, shown in some embodiments of the application;

FIG. 33 is a user interface after expanding the "signal source" control shown in some embodiments of the application;

FIG. 34 is a user interface after expanding the "set" control shown in some embodiments of the application;

FIG. 35 is a user interface after expanding the "sound mode" control shown in some embodiments of the application;

FIG. 36 is a flowchart of a Widget control display method illustrated in some embodiments of the present application;

FIG. 37 is a flow chart of a component display method in some embodiments of the application;

FIG. 38 is a schematic diagram of a desktop homepage in some embodiments of the present application;

FIG. 39 is a schematic diagram of a Widget panel according to some embodiments of the application;

fig. 40 is a schematic diagram of a player Widget data refresh in a Widget panel according to some embodiments of the present application;

FIG. 41 is a diagram illustrating a failure identifier on a Widget according to some embodiments of the present application;

FIG. 42 is a schematic diagram of another failure notification interface according to some embodiments of the application;

FIG. 43 is a schematic diagram of adding pages in some embodiments of the application;

FIG. 44 is another schematic diagram of an add page in some embodiments of the application;

FIG. 45 is a schematic illustration of a service menu in some embodiments of the application;

FIG. 46 is another schematic diagram of a service menu in some embodiments of the application;

FIG. 47 is a user interface including a Widget reminder that is one possibility, shown in some embodiments of the present application;

FIG. 48 is another possible user interface including a Widget reminder shown in some embodiments of the application;

FIG. 49 is another possible user interface including a Widget reminder shown in some embodiments of the application;

FIG. 50 is a user interface displayed after operation of a Widget reminder control, shown in some embodiments of the present application;

FIG. 51 is a diagram of one possible user interface including a Widget panel, shown in some embodiments of the application;

FIG. 52 is a user interface including a Widget panel in an edited state, shown in some embodiments of the application;

FIG. 53 is another user interface including a Widget panel shown in some embodiments of the application;

FIG. 54 is a user interface displayed after a "set" control is moved to the right as shown in some embodiments of the application;

FIG. 55 is a user interface displayed after the "set" control has been moved out of the Widget panel, shown in some embodiments of the present application;

FIG. 56 is a user interface displayed after deleting the "set" control shown in some embodiments of the application;

fig. 57 is a schematic diagram of a Widget control extension rule according to some embodiments of the present application;

FIG. 58 is a schematic diagram of another Widget control extension rule shown in some embodiments of the present application;

FIG. 59 is a schematic diagram of another Widget control extension rule shown in some embodiments of the present application;

FIG. 60 is a user interface including a Widget panel in an editing state, shown in some embodiments of the application;

FIG. 61 is a user interface including a Widget panel, shown in some embodiments of the present application;

FIG. 62 is another user interface including a Widget panel shown in some embodiments of the application;

FIG. 63 is another user interface including a Widget panel shown in some embodiments of the application;

FIG. 64 is a user interface including a delete acknowledgement box shown in some embodiments of the application;

FIG. 65 is a cross-screen system home page shown in some embodiments of the application;

FIG. 66 is a user interface including a rotating confirmation box shown in some embodiments of the application;

FIG. 67 is a home page of a vertical screen system shown in some embodiments of the application;

FIG. 68 is a user interface for a long press "KGege" control shown in some embodiments of the application;

FIG. 69 is a cross-screen system home page in an edited state as shown in some embodiments of the application;

FIG. 70 is a user interface including a delete confirmation box shown in some embodiments of the application;

fig. 71 is a schematic diagram of a Widget control seating rule in a touch mode according to some embodiments of the present application;

FIG. 72 is a user interface when dragging a "KSong" control, as shown in some embodiments of the application;

FIG. 73 is a user interface displayed after dragging a "KSong" control, as shown in some embodiments of the application;

FIG. 74 is a user interface displayed after an edit operation confirming a drag "KSong" control, shown in some embodiments of the application.

Detailed Description

For the purposes of making the objects and embodiments of the present application more apparent, an exemplary embodiment of the present application will be described in detail below with reference to the accompanying drawings in which exemplary embodiments of the present application are illustrated, it being apparent that the exemplary embodiments described are only some, but not all, of the embodiments of the present application.

When the intelligent control device is a display device, introduction is made based on the structure of the display device.

Fig. 1 is a use scenario of a smart control device according to some embodiments of the present application. As shown in fig. 1, the smart control device 200 is also in data communication with a server 400, and a user can operate the smart control device 200 through the smart device 300 or the control apparatus 100.

In some embodiments, the control apparatus 100 may be a remote controller, and the communication between the remote controller and the intelligent control device includes at least one of infrared protocol communication or bluetooth protocol communication, and other short-range communication modes, and the intelligent control device 200 is controlled by a wireless or wired mode. The user may control the intelligent control device 200 by inputting a user instruction through at least one of a key on a remote controller, a voice input, a control panel input, and the like.

In some embodiments, the smart device 300 may include any one of a mobile terminal, tablet, computer, notebook, AR/VR device, etc.

In some embodiments, the smart device 300 may also be used to control the smart control device 200. For example, the smart control device 200 is controlled using an application running on the smart device. In some embodiments, the communication of data may also be performed using the smart device 300 and the smart control device.

In some embodiments, the intelligent control device 200 may also perform control in a manner other than the control apparatus 100 and the intelligent device 300, for example, the module configured inside the intelligent control device 200 for obtaining the voice command may directly receive the voice command control of the user, or the voice command control of the user may also be received through the voice control apparatus set outside the intelligent control device 200.

In some embodiments, the intelligent control device 200 is also in data communication with the server 400. The intelligent control device 200 may be allowed to make communication connection through a Local Area Network (LAN), a Wireless Local Area Network (WLAN), and other networks. The server 400 may provide various contents and interactions to the intelligent control device 200.

Fig. 2 is a block diagram illustrating a hardware configuration of the control device 100 according to some embodiments of the present application. As shown in fig. 2, 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 apparatus 100 may receive an input operation instruction of a user and convert the operation instruction into an instruction recognizable and responsive to the smart control device 200, and may function as an interaction intermediary between the user and the smart control device 200.

In some embodiments, the communication interface 130 is configured to communicate with the outside, including at least one of a WIFI chip, a bluetooth module, NFC, or an alternative module. In some embodiments, the user input/output interface 140 includes at least one of a microphone, a touchpad, a sensor, keys, or an alternative module.

Fig. 3 is a block diagram of the hardware configuration of the intelligent control device 200 in some embodiments of the present application. Referring to fig. 3, in some embodiments, the intelligent control apparatus 200 includes at least one of a modem 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. In some embodiments, the controller includes a central processor, a video processor, an audio processor, a graphics processor, RAM, ROM, a first interface for input/output to an nth interface.

In some embodiments, the display 260 includes a display screen component for presenting a picture, and a driving component for driving an image display, for receiving an image signal from the controller output, for displaying video content, image content, and components of a menu manipulation interface, and a user manipulation UI interface, etc. In some embodiments, the display 260 may be at least one of a liquid crystal display, an OLED display, and a projection display, and may also be a projection device and a projection screen.

In some embodiments, the controller 250 and the modem 210 may be located in separate devices, i.e., the modem 210 may also be located in an external device to the main device in which the controller 250 is located, such as an external set-top box or the like. In some embodiments, the controller 250 controls the operation of the intelligent control device and responds to the user's operations by various software control programs stored on the memory. The controller 250 controls the overall operation of the intelligent control apparatus 200. For example: in response to receiving a user command to select a UI object to be displayed on the display 260, the controller 250 may perform an operation related to the object selected by the user command.

In some embodiments, the object may be any one of selectable objects, such as a hyperlink, an icon, or other operable control. The operations related to the selected object are: displaying an operation of connecting to a hyperlink page, a document, an image, or the like, or executing an operation of a program corresponding to the icon.

In some embodiments the controller includes at least one of a central processing unit (Central Processing Unit, CPU), video processor, audio processor, graphics processor (Graphics Processing Unit, GPU), RAM Random Access Memory, RAM), ROM (Read-Only Memory, ROM), first to nth interfaces for input/output, a communication Bus (Bus), and the like.

In some embodiments, a 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). Alternatively, the user may input the user command by inputting a specific sound or gesture, and the user input interface recognizes the sound or gesture through the sensor to receive the user input command.

Fig. 4 is a diagram of a software configuration of the intelligent control device 200 according to some embodiments of the present application. Referring to FIG. 4, in some embodiments, the system is divided into four layers, from top to bottom, an application layer (referred to as an "application layer"), an application framework layer (Application Framework layer) (referred to as a "framework layer"), a An Zhuoyun row (Android run) and a system library layer (referred to as a "system runtime layer"), and a kernel layer, respectively.

As shown in fig. 4, the application framework layer in some embodiments of the present application includes a manager (manager), a Provider (Content Provider), a network management system, etc., wherein the manager includes at least one of the following modules: an Activity Manager (Activity Manager) is used to interact with all activities that are running in the system; a Location Manager (Location Manager) is used to provide system services or applications with access to system Location services; a Package Manager (Package Manager) for retrieving various information about an application Package currently installed on the device; a notification manager (Notification Manager) for controlling the display and clearing of notification messages; a Window Manager (Window Manager) is used to manage icons, windows, toolbars, wallpaper, and desktop components on the user interface.

In some embodiments, to enhance the user experience of the display device, applications implementing different functions may be configured in the display device. Some applications may implement one function based on the application itself, while some applications may provide multiple services, and different services implement different functions, i.e., the application may implement multiple functions. For example, a desktop application is configured within the display device, the desktop application providing a plurality of business modules to implement different functions based on the business modules provided by the desktop application. To facilitate a user to launch a function, different components may be generated for presentation in the desktop homepage based on the different functions.

In some embodiments, since there are many service modules in the preset operating system application configured in the display device, in order to facilitate the user to quickly start the specified service module, a shortcut of the user's common service may be generated in the form of a Widget, where the Widget is used to provide a shortcut entry for the corresponding service module. Each Widget is displayed in a Widget panel, that is, a user can register a commonly used function into a data center (Widget service) to be added into the Widget panel, and a quick start entry is provided for the function under the preset operating system application through the Widget.

In some embodiments, when the display device installs the android system and the Widget panel is displayed in the desktop homepage, the current display device is usually implemented by using an android native desktop component framework, that is, a system component service, widgetService, works in the system frameworks hierarchy. Each component provider application provides a provider through which its component data is exposed to the desktop application. After the system is started, the system component service automatically gathers provider information of all component providers. And the desktop application uses WidgetHost to communicate with the system component service WidgetService to acquire provider information of each component application, and acquires component data through provider, and adds buttons or updates the displayed components. The component provider application comprises a third party application and a service module provided by a desktop application.

The component data contains information such as an Identification (ID) of the interface component and an operation (Action) of the interface component. The ID can be customized at the provider end; however, the Action can only use fixed less than 20 kinds, such as setting word size, word color, background diagram, click monitoring, etc. That is, the operation update of all the widgets is limited to less than 20 actions, which is difficult to expand and to realize complex interface effects.

The interface layout file for the component originates from the component provider application. In desktop applications, however, the resource consumption is relatively large because the context of the application needs to be created in order to be able to access the resource files within the component provider application. In addition, the layout file of the components cannot have custom components, otherwise, the custom components cannot be identified in the desktop application. Therefore, custom interface components cannot be used in the component layout file, and complex interface effects are difficult to achieve.

Therefore, the desktop component realized by the display device based on the android system is limited to the android system, and only a plurality of native components provided by the system can be used, so that the desktop component is difficult to expand or customize, and the display effect is relatively crude.

Therefore, in order to make the display device have no dependence on the android system when presenting the Widget panel, the application provides a brand-new desktop component frame, and any component (Widget) can be used based on the desktop component frame, and the component can be sourced from the inside of an application or from other applications. Component data sources can also be flexibly customized, and can be sourced from the inside of an application, or can be sourced from other applications. The size, layout, style (square, round and the like) and the like of each Widget presented in the Widget panel can be edited in a self-defined manner through the desktop component framework, multi-level Widget menu display and Widget classification can be performed, components under a certain classification can be added longitudinally, various attributes and the like of the components are modified, and the Widget panel with various effects is provided for users.

In some embodiments, to enable a desktop home page to be presented in the display device upon launching the display device to expose the application or installed business module of the system configuration, the desktop component framework may be run within the application layer in FIG. 4. A desktop application (illustratively: J application) is configured within the display device, the desktop application being an application of the application layer, the desktop application being made up of a desktop component framework for rendering a desktop home page upon startup of the display device.

Fig. 5 is a schematic diagram of a desktop assembly frame in accordance with some embodiments of the application. Referring to fig. 5, the desktop component architecture includes a business component management module (WidgetManager), a component presentation module (WidgetContainer), and a HostView, a data center module (WidgetService), and a component management module (WidgetServer).

The service component management modules (WidgetManager) are divided into service modules with service Identifications (IDs), and one service component management module corresponds to one service module and manages and maintains the components related to the respective service modules. And sending a request to a remote service module, receiving data of a data center module (WidgetService), and distributing the data to different components according to the service ID. The business component management module (WidgetManager) is used for managing component information, wherein the component information is used for recording basic information such as ID, length, width, clicking, expanding, refreshing interval and the like of a component; the component data and the Widget panel information are not limited at all, and can be flexibly expanded.

Component exposure module (WidgetContainer) and HostView: is responsible for adding, deleting, moving, information displaying and the like of the components. And the remote service module: the remote end relative to the desktop component module can be other business modules inside the desktop application or other applications. The component data is provided by a remote service module and is transmitted to the inside of the service component management module through a data center module WidgetService. In fig. 5, both the service module a and the application B are remote service modules.

The service module A is a service module provided by the desktop application, and the application B is an external application and is not a service application provided by the desktop application. Application B refers to a remote application installed in the software system of the display device and can be exposed in the desktop homepage, such as a third party application or an application preset by the system. When the application is displayed, an application management module in the software system acquires the installation information of the application from the system, and the application is displayed on a desktop homepage based on the installation information. If the application also provides the Widget display, the application management module registers the information of the application to WidgetService, and Widget components corresponding to the application are displayed in a Widget panel by the WidgetService.

The data center module (WidgetService) is equivalent to the system component service and is used for interfacing the service component management module and the remote service module, and the data sent by the remote service module is sent to WidgetService, widgetService for preliminary processing and then distributed to different service component management modules. The component management module (WidgetServer) is used for caching component information and component data.

In some embodiments, in order to ensure that the information such as the size, the layout, the style, and the like of each Widget displayed in the Widget panel is not limited by the system, the desktop component framework splits component information for presenting the widgets, where the component information includes component data and Widget panel information, and the component data refers to data required to be displayed on the Widget panel by a service module represented by a service ID, such as information such as ID, click operation, expansion, refresh interval, display content, and the like of the widgets; the Widget panel information refers to interface layout information displayed by the component, such as length, width and other size information of the Widget.

Splitting the component data and the Widget panel information: the component data uses the formats of character strings such as json, xml and the like with better compatibility, and the flexible data transmission limit is less; widget panel information can be stored at a desktop application end and also can be stored at other application ends. If the Widget panel information is stored in other applications, the desktop application may use cross-process loading techniques, such as plug-in loading. When the cross-process loading technology is used, the final Widget panel information is still loaded and run in the desktop application. The interface layout of the components is always loaded in the desktop application, so that resources, controls and the like in the desktop application can be used arbitrarily without being limited by a system. On this basis, more service forms can be derived, such as custom menus of components, multi-service combination components, and the like.

When the desktop component framework realizes the Widget panel, the information such as the size, the layout and the style of the Widget is not concerned, and the information such as the size, the layout and the style of the Widget can be customized. Because the sizes of the widgets can be different, the combined installation of the widgets in the Widget panel is not limited by the desktop component frame, but can be customized, and only the display of the Widget panel is required to be met.

In some embodiments, the desktop component framework manages widgets (components) according to service modules, one of which generates one Widget. The component data and the Widget panel information show one-to-one correspondence: the components of different business modules are not affected by each other, so that the independence and cohesiveness of the business and the components are ensured. According to the development of the service modules, more service modules can be laterally expanded, and more components can be expanded under the existing service modules.

In some embodiments, the implementation of the data channel of the desktop component framework is flexible: when a request is initiated to a remote service, the remote service in the desktop application can be directly called through an interface, and the remote service in other applications can send an IPC request (socket, IPC, file, etc.). The return data of the remote service can be realized in various ways.

In some embodiments, the desktop component framework may advantageously implement dynamic components: the remote service can actively inform the desktop application, add and delete some components according to the service requirement. Such as: and the contact application terminal adds/deletes one contact, and can actively inform the desktop application to add/delete one contact component. For another example: the application management component can actively inform the desktop application when the application is installed/uninstalled, and one application component is added/deleted.

In some embodiments, the desktop component framework may flexibly control component loading opportunities: for example, when the system is just started and the desktop application is just started, the system resources are relatively tense, and the registration of the components can be simply processed and suspended, so that the system resources are reduced from competing for robbing, and the operation of the main function is prevented from being blocked.

In some embodiments, the desktop application is an application installed at the application layer, and application B is an application installed at the application layer.

In some embodiments, the desktop application, upon launching, presents a desktop home page in the display device. The desktop homepage is provided with a plurality of service modules provided by a preset operating system, such as signal sources, networking states, children, education, fitness and other service modules. The user can register any one of the commonly used service modules into a data center module (WidgetService) and add the service modules into a Widget panel in a Widget mode, so that quick starting is realized. The service module belongs to the service in the desktop application, and in the display process of any service module, a user can call out the Widget panel through a preset operation to display the Widget panel in the desktop homepage.

In some embodiments, information of service modules such as signal sources, networking states, etc. is obtained from applications other than desktop applications.

In some embodiments, the Widget panel call-out instruction is not responded in the process of displaying other applications besides the desktop application. Applications outside the desktop application include remote applications installed by a user, such as third party applications including kiwi, cool, etc., when the remote applications are displayed in a user interface of the display device, the user triggers a preset operation, and the non-callable Widget panel is displayed in a desktop homepage.

In some embodiments, the desktop home page may be provided by a native system application or may be provided by a preset operating system application. In some embodiments, the desktop application may be a preset operating system application.

When a user needs to quickly start a certain function (such as a function realized by a certain service module) through the Widget panel, the Widget panel can be adjusted to be displayed in a desktop homepage based on a triggering operation, wherein the triggering operation refers to long-time pressing of a left key or other preset function keys of a remote controller by the user. If the user wants to start a certain function, a corresponding Widget control is triggered in the Widget panel to directly start the function, namely, a certain business module provided by the desktop application is started.

However, if the service module is disconnected, the corresponding service Widget control fails, but is not identified in the Widget panel, and when the corresponding service Widget control is triggered, the quick start of the designated service module cannot be realized. Therefore, when the user realizes the quick start of a certain service module based on the Widget panel, the user cannot timely acquire the invalid Widget control, so that the start of the certain service module fails, and the user experience is affected.

Wherein failure refers to unavailability. Failure of a business module refers to whether an application is available, e.g., if the application is offline or background is no longer maintained for policy reasons, although it is present in the display device, the business module is not available. In contrast, active refers to the available state.

Scene of service Widget control validity change: the validity of the service Widget control may be changed when the service state of the service module is changed. For example, if a business module with a Widget control is down-line for policy reasons, the corresponding business Widget control must be stale. Or a certain application B displayed on the desktop homepage is unloaded, the corresponding Widget control is certainly invalid, so that the Widget panel for receiving the service Widget control display needs to monitor the downlink broadcast of the service module or the unloading broadcast of the application, or the change of the service Widget control supported by the current service module is detected when the desktop application is started, the service Widget control which is already offline is set to be invalid, so that whether the control is valid or not can be updated in time, and further operations such as deletion and the like can be performed according to the wish of a user, and the user experience is improved.

Based on the above, in order to facilitate the user to timely acquire the validity of each service Widget control, the embodiment of the application provides a display device, which is used for realizing the detection of the validity of the control, triggering a query mechanism at a specific time point based on the self characteristics of the service module, namely, detecting the validity of the corresponding service Widget control by using two dimensions of application and service, detecting the invalid service module in real time, and adding an invalid identifier on the corresponding service Widget control in the Widget panel, so that the user can timely acquire the invalid service module, avoiding the situation that the corresponding service module cannot be started due to triggering of the service Widget control, and ensuring better user experience.

FIG. 6 is a flow chart of a control processing method in some embodiments of the application; FIG. 7 is a data flow diagram of a control processing method in some embodiments of the application. The display device provided by the embodiment of the application comprises: the display is configured to display a desktop homepage presenting a Widget panel, wherein a plurality of service Widget controls for providing a service module starting entrance are displayed in the Widget panel; a controller coupled to the display, the controller, when executing the control processing methods shown in fig. 6 and 7, configured to perform the steps of:

S1A, receiving preset operation generated based on a desktop homepage, and detecting whether the service state of each designated service module is changed, wherein the designated service module refers to a service module with a service Widget control displayed in a Widget panel, and the service state is used for representing whether the designated service module is available or not.

The scenario in which the display device starts the control validity query mechanism is started when a desktop homepage is presented in the display device, specifically, the controller detects whether a service state of each designated service module changes when performing receiving a preset operation generated based on the desktop homepage, and is further configured to perform the following steps:

step 111, receiving a start operation of a desktop application, and detecting whether a service state of each designated service module changes when a desktop homepage is presented in a user interface; or,

step 112, detecting whether the service state of each appointed service module changes or not when receiving the triggering operation of the appointed service module displayed in the desktop homepage; or,

step 113, when receiving a startup operation for starting the Widget panel generated based on the desktop homepage, detecting whether the service state of each designated service module changes.

The detection time of the validity of each service Widget control configured by the user is the time of starting the corresponding service module, the time of calling out the Widget panel or the time of starting the desktop application. The control validity query mechanism is synchronously triggered when the corresponding service module is started, or the control validity query mechanism is synchronously triggered when the Widget panel is started, or the control validity query mechanism is synchronously triggered when the desktop application is started, so that the service Widget control corresponding to the service module can be conveniently detected in real time. The designated business module that is started may be the business module that the desktop homepage displays, i.e., the source application of the shortcut.

In some embodiments, a display device is activated by a user, a system home page is presented in the display device, and a desktop application (J application) control icon is presented in the system home page. Triggering the desktop application control icon, presenting a desktop homepage in the display equipment, and synchronously triggering a control validity query mechanism.

And displaying each service module provided by the J application in the desktop homepage, wherein each service module can be added into a Widget panel in the form of a service Widget control based on user-defined settings of a user so as to provide a quick entry of the service module. In order to inquire the validity of each service Widget control in real time, when a user starts a certain service module, a control validity inquiry mechanism is synchronously triggered. The mode of the activated business module can be to trigger the business module control icon displayed in the desktop homepage.

In some embodiments, the executing actively queries whether the business state of each designated business module changes when the desktop application is launched. Since the user uses less of the overall display device hardware operating capacity at start-up, a full volume of queries can be made at this time for each designated business module. The method can be that the display equipment timely acquires and updates the change of the appointed service, so that the situation that the user does not change when the user inquires about the Widget control corresponding to the selected service is avoided.

In some embodiments, actively querying whether the service state of each designated service module changes when the Widget panel is started is performed. Because the user does not start to select the Widget control at this time, the user can perform one-time full-quantity query on each designated service module at this time, and update the state timely, so as to avoid the invariance caused by the fact that the user selects the Widget control corresponding to the service and then performs query.

After the application is started, a notification of a change in the service delivered by the server or other device may be received to update the status of the service.

FIG. 8 is a schematic diagram of a system home page in accordance with some embodiments of the application; FIG. 9 is a diagram of a desktop homepage in some embodiments of the application.

In some embodiments, referring to FIG. 8, when the display device starts and presents a system home page, the system home page presents user-installed third party application control icons in addition to desktop application (J application) control icons. If the user triggers a desktop application (J application) control icon, the desktop home page shown in FIG. 9 is displayed in a switch in the display device.

In some embodiments, the interface shown in FIG. 8 does not need to display a J application, and the display device defaults to a self-starting desktop application without additional triggers.

In some embodiments, as shown in fig. 9, the navigation bar of the user interface includes title controls such as "my", "wire treasures", "parent circles", "recommends", "VIP", "children", "movies", and the like, and the user can display the corresponding title interface by moving the focus to different title controls. For example, in fig. 9, when the focus is on the "recommendation" control, the displayed title interface is the "recommendation" interface, and the navigation bar in the "recommendation" interface includes multiple category controls such as "pick", "variety", "cartoon", "sports", "electronic contest", "cartoon", "knowledge", "all", "drama", and the like, so that the user can display the corresponding recommended content by moving the focus to different category controls. For example, in fig. A9, when the focus is on the "select" control, the content display area of the "recommend" interface displays select items recommended by the user, including icons, thumbnails, visual objects corresponding to the audiovisual content of movies, television shows, and so on. When the focus moves to the 'child', the 'child' title interface is displayed in the content display area, and the 'child' title interface mainly displays the child media. In some embodiments, the user may select a media resource to be played in the home page of the television system or open an application to be used, or may instruct to enter a next level interface by operating a control on the home page of the television system, and select the media resource to be played in the next level interface.

For example, if the designated business module that the user wants to activate is a "child" business module, the "child" business module icon presented in the desktop homepage shown in fig. 9 may be triggered directly, at which point the control validity query mechanism is triggered synchronously.

In some embodiments, a Widget panel refers to a panel control for centrally exposing Widget controls.

Fig. 10 is a schematic diagram illustrating a Widget panel in a desktop homepage according to some embodiments of the present application. When the desktop homepage is displayed in the display device, a triggering operation for starting the Widget panel is generated by a user, and a control validity query mechanism is synchronously triggered when the Widget panel is started, wherein the triggering operation refers to long-time pressing of a left key or other preset function keys of the remote controller by the user.

As shown in fig. 10, a Widget panel in a first state is displayed in a left content area of the user interface, where a plurality of Widget controls are displayed in the Widget panel, and the Widget controls are respectively "signal source", "application center", "Router", "setting", "player", "standard", "multi-screen interaction", "city service", "discovery", "contact", "device", "AI Camera"; the right content area of the user interface continues to display content in the standard mode home page.

Notably, in this example, subject to the size of the right content area, the items in the standard mode home page are displayed with the original layout parameters aligned to the left side edge of the right content area, and the display content in the standard mode home page beyond the right side edge of the user interface is hidden. The original layout parameters refer to the layout parameters of each item in fig. 9. That is, when the user presses the left key for a long time, the Widget panel is displayed in the left content area of the user interface, and each item in the standard mode homepage is entirely shifted to the right content area, and the displayed content beyond the right boundary of the user interface is hidden.

In some embodiments, when displaying the Widget panel as described above, the user may control to retract the Widget panel and return to the standard mode homepage by operating a return key on the remote control, or pressing a right key for a long time, to input a return instruction. After the Widget application receives the input return instruction, the foreground is exited, and the Widget panel is retracted. And the J application responds to the exiting of the Widget application from the foreground, is switched to the foreground operation, and displays the standard mode interface in a full screen mode.

In some embodiments, if the display device directly enters the broadcast television signal source when being started, such as directly playing a television program, at this time, the desktop application is not started, and the system homepage is not displayed in the display device, the desktop homepage cannot be entered, that is, the preset operation of starting the service module or the Widget panel cannot be generated, so that the control validity query mechanism is not triggered.

In some embodiments, when presenting a desktop home page in a display device, if a user wants to launch a different application, such as a third party cloud audiovisual application installed in a television, an interface is required to put the desktop application (J application) in a background/cancel thread and then launch the cloud audiovisual application. In the cloud audiovisual application display state, the Widget panel cannot be called out, and the Widget panel can be opened only after the Widget panel returns to the desktop homepage.

In some embodiments, the desktop home page may also present control icons for some remote applications (application B in fig. 5). At this time, the information of the remote application may be registered to the WidgetService, and then the registration information is acquired from the WidgetService through a service control management module (WidgetManager) to be displayed on the desktop homepage, where the user may start the corresponding remote application. At this time, the remote application may be used as a service module provided by the desktop application, or may be added to the Widget panel in the form of a service Widget control in the desktop homepage, so as to provide a quick start entry of the remote application.

When a certain service module or a Widget panel is started, a starting instruction is synchronously generated to trigger a control validity query mechanism, and whether the service state of the service module corresponding to each service Widget control displayed in the Widget panel is changed or not is detected. The parameters required for detecting whether the service state of the service module changes may be obtained from a data center (WidgetService).

In some embodiments, when a service module is started through other portals outside the Widget panel, whether the service module provides Widget control display may be judged first, and if the started service module does not provide service Widget control display, the service module may be started directly to display a service module homepage. If the started service module provides service Widget control display, the application is determined to be a designated service module, namely the designated service module refers to the service module with the service Widget control displayed in the Widget panel.

The method for judging whether the service module provides the service Widget control display can be judged by acquiring application information, and if the control identification exists in the application information, the service module is indicated to provide the Widget control display; and if the control identification does not exist in the application information, the service module is indicated to provide Widget control display.

In some embodiments, when the service modules are service modules preset by the system, the desktop application may directly obtain, through a service control management module (WidgetManager), application information generated when each service module is registered in the WidgetService, that is, call a data center (WidgetService) to query whether a control identifier exists in each service module. When the service module is a remote application installed in the software system, a service control management module (WidgetManager) can acquire application information generated by the remote application when the application management module of the system adds to a desktop homepage and registers to WidgetService.

In the scenario of starting the desktop application (J application), in order to determine the validity of the service Widget control corresponding to the designated service module in time, a control validity query mechanism can be triggered when the desktop application (J application) is started, the designated service module is started or the Widget panel is started, and whether the service state of each service module is changed is detected.

In some embodiments, the layer on which the display window of the desktop homepage is located is different from the layer on which the Widget panel is located.

In some embodiments, the layer on which the display window of the desktop homepage is located is the same as the layer on which the Widget panel is located, and when an instruction for calling the Widget panel is detected, the display position of the display window of the desktop homepage is adjusted so that the display window of the desktop homepage moves to one side, part of the display windows of the desktop homepage move out of the display interface of the display, and cannot be displayed, and part of the display windows of the desktop homepage do not move out of the display interface of the display, and can be displayed. And drawing a Widget panel at a position which is vacated after the display window of the desktop homepage moves. So as to realize the display of the two layers in the same layer.

In some embodiments, an isolator is provided on the side of the Widget panel that is adjacent to the display window of the desktop homepage. So that the user can distinguish the Widget panel and the display window of the desktop homepage as two different operation areas. After the Widget panel is presented, the focus is set in the Widget panel area by default, and the display window of the desktop homepage cannot acquire the focus. In this way, the switching of the focus between the two areas can be avoided in the process of moving the focus through the remote controller. The user exits the Widget panel by inputting instructions. The display window of the desktop homepage can be restored to the original display position.

In some embodiments, when the current interface of the desktop homepage invokes the Widget panel, a Widget requirement is triggered, typically based on the current interface of the desktop homepage.

In some embodiments, in response to selection of a service by a user, the interface in the display window of the desktop homepage is switched to the interface of the selected service only, and the display of the Widget panel is simultaneously canceled, so that full-screen display of the display window of the desktop homepage is restored.

In some embodiments, when the designated service module or the Widget panel is started, the controller, when executing the detection of whether the service status of each designated service module changes, is further configured to execute the following steps:

step 121, when the designated service module or the Widget panel is started, a service packet name and a service type of each designated service module are acquired, and whether the designated service module is available is detected based on the service packet name and the service type.

Step 122, if the specified service module is detected to be unavailable, determining that the service state of the specified service module is changed.

Step 123, if it is detected that the specified service module is available, it is determined that the service status of the specified service module is unchanged.

Because each service module provided by the desktop application (J application) can be displayed in the desktop homepage, and the third party application can be displayed in a self-defined adding mode, when judging whether the service state changes, judging whether the service state changes or not for the service module provided by the desktop application by judging the service change, namely judging by the service package name and the service type; for the remote application, whether the application state changes or not is judged by judging the change of the application, namely, judging by the application package name and the application information.

In some embodiments, whether the control validity query mechanism is triggered when the Widget panel is started or when the designated service module is started, whether the state of the corresponding application is changed or not can be judged through the service package name and the service type.

The service package name is used for checking whether a service module corresponding to the current package name exists in the current display equipment in the later period, namely, the service module is identified and designated, and the service type is used for identifying whether the corresponding service module is located in the validity period. If the service type of the appointed service module represents that the appointed service module is located in the validity period, the appointed service module is indicated to be available, and further the service state of the appointed service module is determined not to be changed; if the service type of the designated service module characterizes that the designated service module is not located in the validity period, the designated service module is not available, and further the service state of the designated service module is determined to be changed.

Based on the remote application, acquiring state parameters of the remote application based on the application package name, and if the state parameters represent the normal state, indicating that the remote application is available, thereby determining that the application state of the appointed application is unchanged; if the state parameter characterizes the abnormal state, the remote application is not available, and further the application state of the appointed application is determined to change.

For example, the desktop application provides two business modules A, B, the business types a, b of both business modules A, B characterize that the business module A, B is within the expiration date. If the service module a is down for policy or other reasons during the later use, the service module a is not available and the service module B is available.

In some embodiments, when the desktop application is started, the controller, when executing the detection of whether the traffic state of each specified traffic module changes, is further configured to execute the following steps:

and 131, when the desktop application is started, acquiring the total number of current service modules provided by the desktop application and the total number of historical service modules corresponding to the last starting.

And 132, if the total number of the current service modules is less than the total number of the historical service modules, determining that the service states of the designated service modules corresponding to the difference between the total number of the current service modules and the total number of the historical service modules are changed.

If the control validity query mechanism is triggered when the desktop application is started, judging whether the state of each service module provided by the desktop application is changed, and if so, acquiring the total number of current service modules provided by the desktop application and the total number of historical service modules corresponding to the last starting time when the desktop application is started, and comparing the difference of the total numbers of the service modules started twice. If the total number of service modules (one: B) corresponding to the current start is less than the total number of service modules (two: A and B) corresponding to the last start, the service modules provided by the desktop application are not available. At this time, the designated service modules may be screened out based on the difference between the total number of the current service modules and the total number of the historical service modules, and at the same time, it is determined that the service states of the designated service modules are changed.

In some embodiments, since a certain service module in the desktop application provides a service Widget control and is displayed in the Widget panel, validity detection needs to be performed on the service Widget control. And if a specific application provided in the desktop application does not provide the service Widget control, the validity detection process is not needed. Therefore, the service modules which provide the service Widget control and are displayed in the Widget panel are taken as designated service modules, and the service modules which do not provide the service Widget control are taken as common service modules. The service module provided by the desktop application comprises a designated service module and a common service module, wherein the designated service module can be started quickly through a service Widget control or restarted by triggering in a desktop homepage where the designated service module is positioned; and the starting of the common service module can be restarted only by triggering in the desktop homepage where the common service module is located.

If the service module which is unavailable in the desktop application provides the service Widget control to be displayed in the Widget panel, the service Widget control needs to be subjected to failure identification; if the unavailable service module in the desktop application does not provide service Widget control display, the subsequent failure identification display processing can be omitted. Therefore, in order to simplify the detection process of the validity of the control, when detecting whether the service state changes, only the service module which provides the Widget control and displays the Widget control in the Widget panel is used as a judging basis, and the common service module which does not provide the Widget control is not considered any more, namely, whether the service state changes is determined only by specifying whether the service module is available or not.

The judging basis of whether the service state of the designated service module changes or not can be based on the available condition of the designated service module displayed by the provided service Widget control, but not the available condition of the common service module displayed by the un-provided service Widget control.

If the service state of a certain appointed service module is detected to be unchanged, the control validity query mechanism is terminated, and the appointed service module can be directly started; if the service state of a certain designated service module is detected to change, the control validity query mechanism is continuously executed, and the target Widget control is further determined to display the failure identifier.

S2A, if the service state of any appointed application is changed, corresponding state change information is generated, and the state change information is used for determining a target service Widget control corresponding to the appointed service module with the state change.

When detecting that the service state of at least one designated service module changes, indicating that a service Widget control corresponding to the designated service module displayed in the Widget panel has a failure condition. Therefore, based on the state change information, the target Widget control corresponding to the designated service module with the state change can be determined, namely the service Widget control with the failure condition needs to be identified. The state change information comprises control identification, specified service module identification, state change identification and the like.

In some embodiments, when the Widget panel is started and the control validity query mechanism is triggered, the failure identifier can be directly displayed on the determined target service Widget control when the Widget panel is displayed.

In some embodiments, when the designated service module is started, a control validity query mechanism is triggered, or when the desktop application is started, the control validity query mechanism is triggered, after detecting that the currently started designated service module generates service state change, state change information is sent to the Widget panel, so that the Widget panel can update each control information displayed by the Widget panel based on a control validity detection result when the Widget panel is in subsequent display, and the state of the target service Widget control validity of the currently designated application can be updated in time.

S3A, receiving triggering operation for starting the Widget panel, displaying the Widget panel based on the service Widget control of each appointed service module, and displaying a failure identifier on the target service Widget control in the Widget panel, wherein the failure identifier is used for representing the failure of the target service Widget control corresponding to the appointed service module with state change.

And when the user starts the desktop application, starts any appointed application or starts the Widget panel based on the desktop homepage, the control validity is detected, and the generated state change information is sent to the Widget panel. When the user triggers the startup, the Widget panel timely displays the failure identifier on the corresponding target service Widget control based on the state change information so as to inform the user that the target service Widget control where the failure identifier is located is failed, and the startup of the corresponding service module cannot be realized through the target service Widget control.

When the user needs to use the Widget panel to realize the quick start of a certain service module, the user presses the left key of the remote controller for a long time, calls out the Widget panel and displays the Widget panel in a desktop homepage. Referring again to fig. 10, one possible way of displaying the widget panel is to pop up from the left side of the display, squeeze the desktop homepage to the right, at which time the right display content of the desktop homepage disappears from the display; if the display of the Widget panel is canceled, the desktop homepage moves to the left and is displayed in the state shown in FIG. 9.

And displaying all service Widget controls preset by the system or set by the user in the Widget panel, so that the Widget panel is displayed by acquiring total control information of all service Widget controls stored in the device, generating the Widget panel based on the total control information and displaying the Widget panel in a desktop homepage. The total control information is used for characterizing the name and icon of each service module, the effective parameters of the control show, the control identification, the control name, the source of the control icon service module (which service module the control is provided by), and the like.

In some embodiments, if the user starts the Widget panel for the first time, the obtained total control information is desktop control information preset by the system; if the user does not start the Widget target for the first time, the obtained total control information is the control information stored when the display equipment is closed last time. And the total control information is refreshed in real time each time based on the result of the control validity, and the reserved control information is valid.

Because the user generates the preset operation based on the desktop homepage each time before starting the Widget panel to display in the desktop homepage, the user can detect the validity of the control on each service module displayed on the desktop homepage. If the service state of a specific service module providing the Widget control is detected to change, the state change information is sent to the Widget panel. When the subsequent user calls the Widget panel to display, the Widget panel can add a failure identifier to the corresponding service Widget control based on the received service state change information corresponding to each designated service module, so that the user can timely acquire the validity state of each Widget control in the Widget panel, and accordingly process the failure Widget control, such as deleting or replacing the failure Widget control with other Widget controls.

And when the target service Widget control is searched, comparing the control identification with the total control information to determine the target service Widget control corresponding to the designated service module. And then, displaying the failure identifier on the target service Widget control in the Widget panel.

Fig. 11 is a schematic diagram showing a failure identifier on a service Widget control of a Widget panel according to some embodiments of the present application. Referring to fig. 11, when the detected desktop homepage designates the service module as "child", the "child" service module provides a service Widget control display. If the 'juvenile' business module is detected to be unavailable, a failure identifier is added on the 'juvenile' business Widget control, such as a 'failed' identifier in the figure.

In some embodiments, the reason why the service module is specified to generate the service state change may be that the service module is offline, and after the service module is offline, the corresponding service Widget control displayed in the Widget panel cannot be triggered to start the service module any more. Therefore, the service Widget control of the unloaded service module needs to be identified for failure.

Specifically, when there is a traffic module offline condition, the controller is further configured to: and responding to the instruction of canceling the provision of the specified service module, and displaying the failure identifier on a target service Widget control corresponding to the specified service module in the Widget panel when the Widget panel is started.

If a certain service module configured in the desktop application is offline, which means that the desktop application no longer provides the service module, the application management module of the display device will send an offline broadcast to the Widget panel, and the Widget panel determines whether the offloaded service module provides the Widget control display, where the determination manner may refer to the content of the foregoing embodiment, and is not described herein in detail.

And if the unloaded service module does not provide service Widget control display, not processing. And if the offloaded service module provides the Widget control display, taking the service module providing the service Widget control as a designated service module. Meanwhile, when a subsequent user starts the Widget panel to be displayed on a desktop homepage, comparison is performed based on the control identification and the total control information so as to determine a target service Widget control corresponding to the designated service module. And finally, displaying the failure identifier on the target service Widget control in the Widget panel.

In some embodiments, if a remote application displayed in a desktop homepage is offloaded by a user, an application management module of the display device sends an offload broadcast to a Widget panel, and when a subsequent user triggers the Widget panel to be displayed in the desktop homepage, a failure identifier is displayed on a service Widget control corresponding to the application.

Fig. 12 is a schematic diagram showing a failure identifier on a service Widget control for offloading a remote application in some embodiments of the present application. Referring to fig. 12, if the remote application unloaded by the user is a "kiwi" application, when the Widget panel is started, a failure identifier is displayed on a service Widget control of the "kiwi" application in the Widget panel, such as a "failed" identifier in the figure.

In some embodiments, when a desktop homepage is presented in the display device, if a user calls out and displays the Widget panel in the desktop homepage through a trigger operation, a control validity query mechanism is triggered, so that real-time validity detection is performed on the target service Widget control corresponding to each designated service module displayed in the Widget panel.

If the service state of a specific service module is detected not to change, the operation can be started normally, the corresponding target service Widget control is determined to be effective, and the specific service module is started directly. If the service state of a specific application is detected to change, adding a failure identifier on a target service Widget control corresponding to the specific service module. And simultaneously, a prompt box is popped up to inform the user that the designated service module is not available.

Because the Widget panel is called out and displayed at this time, the failure identifier can be directly added to the corresponding target service Widget control in the Widget panel, and the Widget panel starting action is not required to be executed.

In some embodiments, when a desktop homepage is presented in the display device, if a certain service module displayed in the desktop homepage is triggered, a control validity query mechanism is triggered, after the service module is judged to be provided with the Widget display, the service module is determined to be a designated service module, and real-time validity detection is continuously performed on a target service Widget control corresponding to the designated service module.

If a user detects that a certain service module is provided with Widget display and the service module is unavailable when starting the certain service module, namely, the service state is detected to change, state change information corresponding to the designated service module is sent to a Widget panel, so that the Widget panel can update the control information displayed by the Widget panel based on a control validity detection result when in subsequent display, namely, a failure identifier is displayed on a target service Widget control corresponding to the designated service module, and the state of the validity of each service Widget control displayed in the Widget panel is updated in time.

In some embodiments, when the system home page is presented in the display device, if the user triggers a desktop application presented in the system home page, the display of the desktop home page is switched in the display device. And triggering a control validity query mechanism when the desktop application is started so as to detect the service Widget control corresponding to each service module provided by the desktop application to carry out real-time validity detection.

If it is detected that a certain service module provides Widget display and the service module is unavailable, that is, a service state is detected to change, state change information corresponding to the specified service module is sent to a Widget panel, so that when the Widget panel displays in a subsequent mode, the control information displayed by the Widget panel can be updated based on a control validity detection result, that is, a failure identifier is displayed on a target service Widget control corresponding to the specified service module, and the state of the validity of each service Widget control displayed in the Widget panel can be updated in time.

In some embodiments, the method for providing the validity of the update service Widget control by the Widget panel is used for interacting with each service module provided by the desktop application, timely and synchronously designating the state of the target service Widget control provided by the service module, monitoring the installation (including update) of the service module of the whole machine, unloading and closing the broadcast, and if the unloaded service module provides the Widget control display function, displaying the corresponding service Widget control in time to be invalid.

Therefore, when the control validity is detected, the display device provided by the application can display the validity of the control according to two dimensions of service and application, and trigger a query mechanism at a specific time point, and if the Widget control is queried to be invalid, an invalid icon is displayed on the corresponding service Widget control in the Widget panel, so that a user can find the unusable service Widget control in time. Therefore, the control can be fed back at the first time when the control fails, so that a user can identify and replace the failed control in time.

In some embodiments, after the user calls the Widget panel to display on the desktop homepage through the triggering operation, if the user triggers the failure Widget control when the user sees that the service Widget control displaying the failure identifier exists in the Widget panel, the failure prompt interface is popped up in the current interface.

In some embodiments, after the focus moves to the Widget control, responding to a confirmation operation input by a user, triggering a failure prompt interface when the Widget control is a failure control, and displaying a secondary page corresponding to the Widget control or starting a function corresponding to the Widget control when the Widget control is not the failure control.

Specifically, upon triggering the Widget control with the failure identification, the controller is further configured to:

Step 41, responding to an instruction for triggering the target service Widget control with the failure identifier displayed in the Widget panel, not executing the starting process of the designated service module corresponding to the target service Widget control, and displaying a failure prompt interface with a deletion button in the desktop homepage.

And step 42, deleting the target service Widget control in the Widget panel in response to the instruction of triggering the deletion button.

When a user calls a Widget panel and triggers the target service Widget control with a failure identifier, the designated service module corresponding to the target service Widget control cannot be started. Therefore, when the service Widget control with the failure identifier in the Widget panel is triggered, the action of starting the corresponding appointed service module of the target service Widget control is not executed any more.

And if the specified service module corresponding to the current target service Widget control can not be started, a failure prompt interface is popped up in the desktop homepage.

FIG. 13 is a schematic diagram of a failure notification interface according to some embodiments of the application. Referring to fig. 11 and 13, when a user triggers a disabled "child" business Widget control, a disabling prompt interface is presented in the current interface. The invalidation prompt interface is provided with a deleting button, a cancelling button and a replacing control display area. The delete button is used for deleting the invalid Widget control, and the cancel button is used for closing the invalid prompting interface. The replacement control display area is used for displaying other Widget controls recommended by the system and capable of being displayed.

In some embodiments, the replacement control display displays an icon of the second service. In some embodiments, the icon of the second service may be a second service Widget control, or may be another type of control that characterizes the second service. This is because the replacement control display area is only used to display the service available for the user to select, so a scheme can be adopted as long as the effect of display is achieved.

If the icon of the second service is a Widget control of the second service, the floating layer is controlled by a Widget component display module in the desktop application, and icons with other formats can be displayed by modules different from the Widget component in the desktop application.

If the user clicks the delete button, the target service Widget control in the Widget panel may be deleted, i.e., the "child" service Widget control is deleted.

In some embodiments, if the system does not have a recommended Widget control that can be presented in a replacement, the replacement control display is not presented in the failure prompt interface.

In some embodiments, if a certain failed Widget control in the Widget panel is deleted, the home location of the Widget control will create a room. If the space is not refilled with other service widgets controls, space is wasted. If other service widgets in the Widget panel are reordered, the rearrangement can cause that the user cannot find the position of the previous control easily due to different sizes of the service widgets.

Therefore, in order to be convenient for not changing the original form of the Widget panel after deleting a certain invalid Widget control and fully utilizing the display space of the Widget panel, the application can recommend other service Widget controls which can be displayed alternatively for a user when deleting a certain invalid Widget control.

Specifically, when the service Widget control replacement presentation is performed, the controller is further configured to perform the following steps:

and 51, when triggering the target service Widget control with the failure identifier, generating a recommended Widget control based on attribute parameters of the target service Widget control, wherein the recommended Widget control is a control with the same characteristic as the target service Widget control.

And 52, displaying a replacement control display area in the failure prompt interface, and displaying the recommended Widget control in the replacement control display area.

And step 53, responding to an instruction for triggering the change of the specified recommended Widget control in the control display area, and displaying the specified recommended Widget control in the home position of the target service Widget control in the Widget panel.

The service Widget control which is recommended to the user and is replaced and displayed by the system can be synchronously displayed in the failure prompt interface when the user triggers the failure Widget control, so that when the user triggers the target service Widget control which is displayed with the failure identifier, the recommended Widget control which is recommended by the system is obtained and displayed in a replacement control display area of the failure prompt interface.

The recommended Widget control is generated based on the attribute parameters of the target service Widget control, wherein the attribute parameters are control (Widget) information. Because the user registers the service Widget control based on the service module, information such as an icon, a size, a service type, an application and the like generated when registering the service Widget control are stored in a data center (WidgetService). Thus, the attribute parameters of the target business Widget control may be obtained from a data center (Widget service). The attribute parameters include control size, service type, application to which they belong, etc. The recommended Widget control is a control with the same characteristic as the target service Widget control, and is used for replacing and displaying the home position of the deleted target Widget control based on the triggering of a user.

Referring again to fig. 13, the replacement control display area in the failure prompting interface may be displayed below the delete button, and the display position threshold that may be displayed in the replacement control display area may be 6, that is, the replacement control display area may display at most 6 recommended widgets controls.

If the user clicks a recommended certain service Widget control, deleting the user-triggered failure Widget control icon, and displaying the selected recommended Widget control in the home position of the failure Widget control.

In some embodiments, when the failure prompt interface shown in fig. 13 is displayed, if the user directly clicks the designated recommended Widget control in the replacement control display area, deleting the target service Widget control triggered by the user and having the failure identifier may be performed simultaneously, and displaying the selected designated recommended Widget control in the home position of the target service Widget control. Meanwhile, the invalidation prompt interface cancels display, and the appointed recommended Widget control is displayed in a replacement mode in the position where the invalidated Widget control is located in the Widget panel.

In some embodiments, the recommendation of the Widget control is by way of displaying an icon corresponding to the recommended service. In some embodiments, the icon may be a Widget control, or may be a presentation of other forms of controls.

Fig. 14 is a schematic diagram of a Widget panel that alternatively displays a specified recommended Widget control in some embodiments of the present application. Referring again to fig. 13, the recommended widgets controls presented in the replacement control display area include a time control, a clock control, a control center control, and a workout control. Referring to fig. 14, if the user directly triggers the fitness Widget control as the specified recommended Widget control, deleting the "child" service Widget control in the failed Widget panel, and displaying the fitness Widget control at the home position of the "child" service Widget control.

Fig. 15 is a schematic diagram of a Widget panel display space in some embodiments of the present application. In some embodiments, when the failure prompt interface shown in fig. 13 is displayed, if the user clicks the delete button, the target service Widget control (child Widget control) with the failure identifier may be directly deleted, and referring to fig. 15, the failure prompt interface cancels the display, and the home position of the deleted target service Widget control is a null position.

In order to display other service widgets on the vacancy again, the user can click the original position (the vacancy at this time) of the deleted target service Widget control again, and then a control recommendation interface is popped up and displayed on the upper layer of the desktop homepage.

FIG. 16 is a schematic diagram of a control recommendation interface in some embodiments of the application. Referring to fig. 16, the control recommendation interface presents a replacement control display area displaying a control recommended by the system and having the same characteristics as the target service Widget control. For example, recommended widgets displayed in the replacement control display area of the control recommendation interface include a time control, a clock control, a control center control and a fitness control. If the user triggers the exercise control as the specified recommended Widget control, the exercise control is displayed in the home position of the child business Widget control, and the replaced display effect diagram can be referred to again as the content shown in fig. 14.

In some embodiments, because the control sizes of different service widgets are different, in order to facilitate the system recommended service widgets to be displayed to the home position of the deleted target service Widget control, service widgets with the same size can be searched based on the size of the deleted service Widget control. But can be based on that the user can start the service Widget control with similar characteristic in the same position, can also be based on service characteristic or affiliated application as attribute parameter, recommend the Widget control that can replace the show for the user. That is, a recommended Widget control having the same characteristics as a target business Widget control refers to a control having at least one of the characteristics of the same control size, similar business attributes, the same belonging application, and the like.

The user actively deletes a certain service Widget control (whether invalid or not) or removes the control after the corresponding service Widget control is invalid because the service module is not available, the system actively recommends the control with similar form and service to the user according to the service type of the deleted Widget control, so as to recommend the control with similar function and same size to the user according to the size and service type of the current control, the user can conveniently add the control, the vacancy in the Widget panel is avoided, the vacancy is filled after the user is selected, and the user experience is improved.

In some embodiments, the control moving or deleting process may also be implemented by the user controlling the movement of the focus, as shown in fig. 18, for example, in some embodiments, after the focus moves to the "set" Widget control in fig. 10, service may be started through an input confirmation operation or other preset first operations, and meanwhile, the validity query is triggered. And when the received input is a preset second operation, starting the 'setting' Widget control to move or delete the thread.

After the move or delete thread is started, determining a position of the "set" Widget control in the panel, and if the target position in the first movement direction of the "set" Widget control is not the boundary of the panel (i.e., there is a position of a preset size as a movable position), drawing a first pointing arrow in the first movement direction of the "set" Widget control, the pointing direction of the arrow being the same as the first movement direction, the arrow being drawn in a floating layer above the panel. If the target position in the first movement direction of the "set" Widget control is the boundary of the panel (i.e., there is no position of a preset size as a movable position), then a delete prompt control is drawn in the first movement direction of the "set" Widget control to indicate that movement in that direction will result in deletion of the control.

Illustratively, on the interface shown in fig. 18, since none of the four movable-direction target positions of the "set" Widget control are boundaries of the Widget panel, pointing arrows are drawn in all four directions. To characterize the direction in which each of these four directions can be used as a direction of movement of the control.

In some embodiments, when the target positions of the four movable directions of the Widget control are not boundaries of the Widget panel, further judging the size of the Widget control at the target position, displaying the pointing arrow only when the length and width dimensions of the Widget control at the target position are the same as those of the Widget control at the set position, and not displaying the pointing arrow at the different times. In some embodiments, the controls with the same length and width dimensions can be replaced in position.

In some embodiments, the movement arrow may be displayed regardless of the size of the control at the target location.

In some embodiments, upon receiving a move operation, the "set" Widget control is displayed superimposed over the target location control without moving the target location control.

In some embodiments, as shown in fig. 19, on the interface shown in fig. 18, when an input instruction (for example, a right direction key instruction) for moving the control in the first direction is received, the "set" Widget control and the "router" Widget control position that is not operated are set to different layers, and then the "set" Widget control is superimposed on the "router" Widget control position on the right side thereof. Based on the position of the moved set Widget control, continuously judging whether the four movable directions of the set Widget control are boundaries of a Widget panel, wherein the target positions in the left moving direction and the downward moving direction are not boundaries of the Widget panel because the four movable directions of the set Widget control are upward moving directions, and pointing arrows are drawn in the three directions. The target position in the rightward movement direction is the boundary of the Widget panel, and no target position which can move exists, so that the deletion prompt control is drawn in the rightward movement direction of the setting Widget control to indicate that the rightward movement will perform deletion of the setting Widget control. Such a separate operation may be used to compare calls to control threads of other widgets controls to improve system performance before the user intent is determined.

In some embodiments, on the interface shown in fig. 18, an input instruction to move the control in the first direction (e.g., a right direction key instruction) is received, and the "set" Widget control may be interchanged with the "router" Widget control on the right side thereof, so that the user fully sees the control that is present on the current panel.

In some embodiments, a delete prompt interface, such as that shown in FIG. 20, is displayed in response to receiving an input instruction to move the control in a first direction (e.g., a right direction key instruction) based on the interface shown in FIG. 19, to allow the user to further confirm whether to delete the control.

In some embodiments, the information prompt window on the delete prompt interface does not hide the "set" Widget control to be deleted, so that the user knows the object to be deleted currently.

In some embodiments, deleting the information prompt window on the prompt interface includes determining a delete control and a cancel control. After the information prompt window is displayed, the focus on the panel is withdrawn, and the focus is displayed on a preset control on a default window of the information prompt window, so that the operation of a user is facilitated.

In some embodiments, determining to delete the control is responsive to a user operation. The delete information "sets" the Widget control. So that the initial position of the "set" Widget control is shown as empty, as shown in fig. 21. This is because, whether the "set" Widget control is an overlay "router" Widget control or an exchange of positions with "router" Widget control during movement, if the user determines that the control is to be moved, the "set" Widget control needs to be fixed in position after receiving the movement instruction on the final display effect (during movement, the control position may be moved multiple times, for example, after receiving the downward direction key instruction on the interface shown in fig. 19, the "set" Widget control may also be moved to the position of the "multi-screen interactive" Widget control.

In some embodiments, if the user chooses to cancel the deletion, the interface shown in FIG. 19 is returned.

In some embodiments, if the received input preset operation in the interface shown in fig. 19 cancels the move/delete thread, in the case where the "set" Widget control is an overlay "router" Widget control, the display of the "router" Widget control in its home position is canceled, and the "router" Widget control is displayed in its home position. If the "set" Widget control and the "router" Widget control exchange positions before canceling the move/delete thread, the current positions of the two are maintained. And at the same time, canceling the display of the arrow or the prompt in the floating layer. Both of the above means can achieve the effect shown in fig. 22.

In some embodiments, if the length and width dimensions of the control at the final target position in the moving process are inconsistent with those of the "set" Widget control, the "set" Widget control is now at the final target position in the moving process, and the position of the least other control is selected and adjusted according to the preset algorithm, so that the original interface is maintained to be displayed on the panel, and the number of the moved controls is the least.

In some embodiments, after cancelling the move/delete thread, focus is still displayed on the "set" Widget control to facilitate subsequent operations by the user.

In some embodiments, the typeface of the system home page in the drawing is a replacement for the image of the region prior to the change to simplify the drawing, which image may maintain the original display logic in the panel control logic.

Therefore, when the system generates the recommended Widget control, the control size corresponding to the target service Widget control with the failure identifier is acquired. When finding a Widget control which can be recommended, a service Widget control with the same size as the target service Widget control needs to be found. In addition, the control size and the service type can be used as the search basis at the same time, so that other service Widget controls with similar types with the invalid designated service module are recommended for the user.

In some embodiments, the controller, upon executing step 51, i.e., executing the attribute parameters based on the target service Widget control, generates a recommended Widget control, is further configured to perform the steps of:

step 511, obtaining the service type of the designated service module and the control size of the target service Widget control.

Step 512, based on the service type of the designated service module, searching the service Widget control with the same control size as the target service Widget control, wherein the service type of the service module corresponding to the first type control is the same as the service type of the designated service module.

And 513, if the number of the controls of the first type of controls meets the display bit threshold of the replacement control display area, taking the first type of controls as recommended widgets controls.

The system may generate the recommended Widget control at the time when the user triggers the target service Widget control with the failure identifier, or when the gap shown in the Widget panel is triggered. When the recommended Widget control is generated based on the vacancy, the recommended Widget control can be recommended based on the characteristics of the service Widget control originally displayed by the vacancy.

When the recommended Widget control is generated based on the target service Widget control which is invalid, the recommended strategy can be recommended according to the priority order, namely, firstly, the Widget control with the same characteristics (namely, the same service type) is searched based on the service type and the control size; finding Widget controls with the same characteristics (namely the same belonged application) based on the control sizes of other service modules provided by the desktop application; and finally searching Widget controls with the same characteristics (namely, the same control size) based on the control sizes of all the controls in the system.

In some embodiments, when the Widget control is displayed in the Widget panel, a plurality of grid networks with the same size and regular arrangement are arranged on the Widget panel. Because different widgets correspond to different control sizes, the number of grids occupied by the different widgets is different, for example, referring again to fig. 13, the "period weather" control occupies 3 grids in the transverse direction, and the corresponding control size is 3×1; the signal source control occupies 3 grids vertically, and the corresponding control size is 1 multiplied by 3; the control is set to occupy 2 transverse grids, and the corresponding control size is 2 multiplied by 1; the "juvenile" control occupies a grid and the corresponding control size is 1 x 1.

Thus, the control size may be represented by the number of grids, and the size of the empty space formed after the control is deleted is also represented by the number of grids, and the size requirements of the recommended Widget control that may be presented in replacement are also represented by the number of grids. For example, if the "period weather" control is deleted, a Widget control also having 3 grids in the lateral direction needs to be searched, and the corresponding required control size is 3×1; if the 'set' control is deleted, the Widget control which is also provided with 2 transverse grids is required to be searched, and the corresponding required control size is 2 multiplied by 1; if the child control is deleted, the Widget control which also has 1 grid structure needs to be searched, and the corresponding required control size is 1×1.

In order to enable a user to display the widgets with the same type at the same position after deleting one Widget, the user can search based on the service type. If the service Widget control deleted by the user is a "child" service Widget control, the service type of the service is educational and occupies a grid, then the service Widget control which is educational and occupies a grid is required to be searched as a first type control. At this time, the service type of the service module corresponding to the first type of control is the same as the service type of the designated service module, and the control size of the first type of control is the same as the control size of the target service Widget control corresponding to the designated service module.

After finding out the first type of control, judging whether the number of the control of the first type of control meets the display position threshold value of the display area of the replacement control, namely judging whether the first type of control can occupy each display area of the replacement control. If the number of the first type of controls meets the display bit threshold of the replacement control display area, the first type of controls can occupy all the display areas of the replacement control display area, and the first type of controls are not required to be inquired continuously, and the first type of controls are used as recommended widgets.

For example, the display bit threshold N is defined according to the application size. When the display bit threshold N is 6, if the display bit threshold N is 1 multiplied by 1, N is 6, namely 6 recommended Widget controls are displayed at most; if the control size is 2×2, N is 3, that is, at most 3 recommended widgets controls are displayed; in the case of a 3 x 2 control size, N is 2, i.e., a maximum of 2 recommended widgets controls are displayed.

When the display bit threshold value N is 6, if the number of the searched first type controls is 6, the searched first type controls can be directly used as recommended widgets and displayed in the replacement control display area in sequence. If the number of the searched controls of the first type is 3 and is smaller than the display bit threshold value N, the query is needed to be continued according to the next sequence. If the number of the searched controls of the first type is 8 and is larger than the display bit threshold value N, only the first 6 controls are used as recommended widgets.

In some embodiments, searching for a query sequence of recommended Widget controls, wherein the service type is a first priority sequence, and when the first type of control searched by the first priority sequence does not meet the condition, searching for the Widget controls according to a second priority sequence, wherein the second priority sequence is a sequence for searching for Widget controls corresponding to other service modules provided by an application to which a currently specified service module belongs. And when the second type of control found by the second priority order does not meet the conditions, continuing to search by a third priority order, wherein the third priority order is the order of searching based on all the controls provided by the system.

In some embodiments, if the first type of control found by the first priority does not meet the condition, and continues to find in the second priority order, the controller generates a recommended Widget control when executing the attribute parameter based on the target service Widget control, and is further configured to execute the following steps:

and step 514, if the number of the controls of the first type of controls does not meet the display bit threshold of the replacement control display area, searching the service Widget controls with the same control size as the target application Widget controls based on the service module provided by the desktop application to which the specified service module belongs as a second type of controls, wherein the application to which the second type of controls corresponds to the service module and the application to which the specified service belongs are desktop applications.

Step 515, if the total number of the first type of controls and the second type of controls meets the display bit threshold of the replacement control display area, the first type of controls and the second type of controls are used as recommended widgets.

And according to the first priority order, the system uses the service type and the control size as the searching basis, and if the number of the searched controls of the first control does not meet the display position threshold of the replacement control display area, the searching is needed to be continued based on the second priority order. At this time, the application (which is a desktop application) to which the specified service module belongs is acquired, and based on other service modules provided by the desktop application to which the specified service module belongs, the service Widget control with the same control size as the target service Widget control is searched for as the second class control. At this time, the application to which the second class control corresponds to the service module is the same as the application to which the specified service belongs, both are desktop applications, and the control size of the second class control is the same as the same control size of the target service Widget control corresponding to the specified service module.

For example, if the control with the failure identifier is a "child" service Widget control, the desktop application to which the service module belongs also provides service modules such as "parent circle", "television play", "movie", and the like, and the service modules all have the function of providing Widget control display.

If the control size of the "parent circle" service Widget control is 3×2, the control size of the "television play" service Widget control is 2×1, and the control size of the "movie" service Widget control is 1×1, then the Widget control having the same control size (1×1) as the "child" service Widget control is "movie", and therefore, the "movie" service Widget control may be used as the second type of control.

Based on the method, zero or more second type controls can be found, after the second priority order is found, the total control number of the first type controls and the second type controls is calculated, and the total control number is compared with the display bit threshold of the replacement control display area again.

If the total control quantity meets the display bit threshold of the replacement control display area, no subsequent inquiry is carried out, and the first type of control and the second type of control are used as recommended Widget controls and are displayed in the replacement control display area in sequence.

In some embodiments, in the system according to the first priority order and the second priority order, the service type, other service modules provided by the application and the control size are used as the searching basis, and if the total number of the searched first type of control and the searched second type of control does not meet the display bit threshold of the replacement control display area, searching is needed to be continued based on the third priority order. At this time, all widgets stored in the system are acquired, the service widgets with the same control size as the target service widgets are used as the third type of controls, and are sequentially recommended to the user according to the priority order and displayed in the replacement control display area. The total control quantity of the first type control, the second type control and the third type control meets the display position threshold value of the display area of the replacement control.

In some embodiments, in order to avoid repeatedly adding the same control to be displayed in the Widget panel when searching the recommended Widget control based on each priority order, the application only queries in the rest of service Widget controls which are not displayed in the Widget panel and meet the query conditions when querying. For example, when querying other service modules provided by the desktop application to which the "child" service module belongs, the "recommended" service Widget control is already displayed in the Widget panel, although the "recommended" service Widget control meets the search condition (the control size is the same as that of the desktop application to which the designated service module belongs), the "recommended" service Widget control is not used as the second type of control, that is, the "recommended" service Widget control is not repeatedly displayed.

In some embodiments, when the desktop application is started, each service module provided by the desktop application reports control information (control size, service type, application to which the control belongs, etc.) to the Widget panel, wherein the type of the control is equivalent to the service type of the corresponding service module. The Widget panel displays the desktop control according to the system preset or user-defined desktop control (the Widget panel starts the preset display control for the first time and the cached user-defined desktop control is started again).

If the user is about to delete the control, a control management module (WidgetServer) in the system will first query the application, service type and control size to which the control to be deleted currently belongs. The control management module firstly inquires three dimensions of the application size, the service type and the application to be deleted, sequentially reduces the dimensions, picks the Widget control application, sorts the Widget control application, and then displays the sorted Widget control recommendation sequence. If the system does not inquire the recommendation control meeting the condition, recommendation is not performed. If one of the recommended Widget controls is selected by the user, the new control is supplemented to the original position of the deleted control, and if the new control is not selected, the corresponding control is directly deleted.

In some embodiments, when the system recommends a control after deleting a certain service Widget control, taking the control recommendation based on a specified service module as an example, the priority order of the control recommendation is as follows: because the service control (Widget) can provide the control size (size), service type, belonging application and the like of the current service Widget when registering, when one control fails or is to be deleted, the system firstly inquires whether the corresponding service type of the service Widget which fails has the control with the same size, if so, the control is not displayed in the Widget panel (the addition of the control which is not displayed on the desktop is to prevent the repeated addition of the same control), and the control has the highest priority. And then querying the same size of other business controls in the desktop application which the user belongs to under the query, and the business controls are not added in the Widget panel as a second priority. If the total control number of the query is greater than N, the query is not performed; if the number of the total control conforming to the two priorities is smaller than N, querying all the controls under the condition that the control conforming to the size is used as the control of the third priority, and recommending the control to the user according to the order of the priorities.

When the control recommendation is carried out, the display device provided by the application firstly acquires whether the service type of the target service Widget control which is invalid has the Widget control with the same size based on the deleted target service Widget control, and recommends the Widget control to the user if the Widget control is present; if not, inquiring whether the service Widget controls with the same size exist in the desktop application to which the control belongs, if so, recommending, if not, inquiring all the controls under the control, and if so, recommending (preferentially showing that the control is not added to the desktop). The system recommends controls with similar functions and the same size to the user according to the size and the service type of the current control, so that the user can conveniently add the controls, gaps in the Widget panel are avoided, the gaps are filled after the user selects the controls, and the user experience is improved.

In some embodiments, as shown in fig. 17, there is provided a control display method, the method comprising:

and S1701, determining and displaying an icon of a second service when the first service Widget control is detected to be deleted, wherein the size of the second service Widget control corresponding to the second service is the same as that of the first service Widget control.

In some embodiments, determining and displaying the icon of the second service includes: acquiring a service type of a first service module corresponding to a first service Widget control and a control size of the first service Widget control; searching a target service with the same service type based on the service type, and determining a second service corresponding to a second service Widget control with the same control size of the first service Widget control in the target service; and displaying an icon corresponding to the second service. Through the identification of the service type, the service corresponding to the recommended control and the deleted control service are the same or similar, so that the deleted service of the user can be effectively replaced.

In some embodiments, when the deleted control is the deletion performed by the user when the control is not invalid, the control corresponding to the different types of services is recommended, and when the deleted control is the deletion performed by the user when the control is invalid, the control corresponding to the same types of services is recommended. This is because, in some embodiments, the user actively deleting a non-stale control may indicate that the user does not like the type of service much. And therefore recommends controls corresponding to different service types.

In some embodiments, determining and displaying the icon of the second service includes: acquiring a second service corresponding to a second service Widget control with the same control size as the first service Widget control; and displaying an icon corresponding to the second service.

In some embodiments, determining and displaying the icon of the second service includes: determining a plurality of second services and the use frequencies of the plurality of second services; and displaying icons corresponding to the plurality of second services according to the use frequencies of the plurality of second services, wherein the icons corresponding to the second services with high use frequencies are highlighted compared with the icons corresponding to the second services with low use frequencies. In this way, among the controls with the same size, the controls which are frequently used by the user and are not displayed in the panel can be selected for recommendation. Is beneficial to the quick use of users.

In some embodiments, highlighting may be prioritization, highlighting, or a large display.

In some embodiments, determining and displaying the icon of the second service includes: determining a plurality of second services and the service time of the plurality of second services; and displaying icons corresponding to the plurality of second services according to the using time of the plurality of second services, wherein the icons corresponding to the second services with small time difference between the using time and the current time are highlighted compared with the icons corresponding to the second services with large time difference between the using time and the current time. So that the controls that are most recently used by the user and are not displayed in the panel are recommended. Is beneficial to the quick use of users.

In some embodiments, determining and displaying the icon of the second service includes: determining update time of a plurality of second services; and displaying icons corresponding to the plurality of second services according to the update time of the plurality of second services, wherein the icons corresponding to the second services with small time difference between the update time and the current time are highlighted compared with the icons corresponding to the second services with large time difference between the update time and the current time. So that the controls that have been updated recently and are not displayed in the panel are recommended. Is beneficial to the quick use of users.

In some embodiments, determining and displaying the icon of the second service includes: acquiring a target service corresponding to a second service Widget control with the same control size as the first service Widget control; filtering a third service deleted by the user from the Widget control in the target service to determine a second service; and displaying an icon corresponding to the second service. So as to remove the deleted business of the user in the recommending process and avoid repeated recommendation.

In some embodiments, determining and displaying the icon of the second service includes: acquiring a service type corresponding to a system page and acquiring a control size of a first service Widget control, wherein the system page is a system page before a Widget panel is displayed; searching a target service with the same service type based on the service type, and determining a second service corresponding to a second service Widget control with the same control size of the first service Widget control in the target service; and displaying an icon corresponding to the second service. Since the user call-out of the panel amount requirement may be triggered based on the current system page, the user aims to find the business related to the current interface, and thus the recommendation is made with the control related to the system page business and not displayed in the panel when the user recommends. Is beneficial to the quick use of users.

S1702, receiving input selection of an icon of a second service;

in some embodiments, the icons of the second service are multiple, with focus being set by default on the highlighted icon (at which point focus in the Widget panel is deactivated). The user can view the icon of the second service that can be selected by moving the focus. If the user exits the selection of the icon of the second service, then a null is left at the first location. Step S1703 is performed if one of the icons is selected by the user.

And S1703, displaying a second service Widget control of a second service corresponding to the selected icon at a first position, wherein the first position is a display position of the first service Widget control.

In some embodiments, since the recommended business control is the same size as the deleted control, no adjustments to the positions of other controls are needed when supplementing the controls.

In some embodiments, some embodiments of the present application provide a control display method including: when the first service Widget control is detected to be deleted, determining and displaying an icon of a second service, wherein the size of the second service Widget control corresponding to the second service is not larger than that of a first position, and the first position is a display position of the first service Widget control and a blank position adjacent to the display position of the first service Widget control; receiving an input selection of an icon of a second service; and displaying a second service Widget control of a second service corresponding to the selected icon at the first position. In the application, when recommending, the deleted control and the blank positions (if any) of the adjacent positions are considered to recommend the control, and at the moment, the control can be the same as the deleted position in size or the whole blank position or any combination of the minimum position units of the whole blank position, thereby realizing diversified recommendation.

Illustratively, the first location includes a reserved blank location that existed prior to the delete action and a target location of the deleted control. The target position is 2×4 in size, the reserved blank position is 4*4, and the blank position left after deletion is 4*6 (or 6*4 in size), and icons of 6*4, 4*2, 2×4, 2×2, etc. in size can be recommended in the recommending process. Thus enlarging the number of screens that can be performed in size.

FIG. 6 is a flow chart of a control processing method in some embodiments of the application. Referring to fig. 6, a control processing method provided by an embodiment of the present application to detect validity of a control includes:

S1A, receiving preset operation generated based on a desktop homepage, and detecting whether a service state of each designated service module is changed, wherein the designated service module is a service module with a service Widget control displayed in a Widget panel, and the service state is used for representing whether the designated service module is available;

S2A, if the service state of any appointed service module is changed, corresponding state change information is generated, and the state change information is used for determining a target service Widget control corresponding to the appointed service module with the state change;

According to the control processing method and the display device, preset operation generated based on a desktop homepage is received, whether the service state of each designated service module changes or not is detected, and when the service state changes, a target service Widget control is determined based on state change information. When the Widget panel is started, a failure identifier is displayed on a target service Widget control in the Widget panel so as to represent that the target service Widget control corresponding to the designated service module with the state change fails. Therefore, when the method and the display device are used for realizing the control validity detection, the control validity can be displayed according to two dimensions of service and application, a query mechanism is triggered at a specific time point, and if the Widget control is queried to be invalid, the invalidation identification is displayed on the corresponding service Widget control in the Widget panel, so that a user can find the unavailable service Widget control in time, and the user experience is good.

FIG. 23 is a schematic diagram of a display device user interface of the present application shown in some exemplary embodiments. As shown in fig. 23, the user interface may include a plurality of view display areas, such as view display areas 501A, 502A, 503A, 504A shown in fig. 23. One or more items may be laid out in each view display area, where the items include visual interface elements such as icons, windows, controls, etc., where the controls may include icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, widgets, etc.

In some embodiments, the display device may be started up directly into a television system home page, which may be the home page of a preset video on demand program, such as a Convergence (J) application home page.

In some embodiments, the display device may operate in a standard mode, educational mode, or juvenile mode based on the J application. The standard mode is a basic working mode provided by the display equipment for users, the education mode is a working mode capable of specially providing small, primary and high education media for the users, and the child mode is a working mode capable of specially providing child media for the users. Illustratively, the interfaces that J applications may provide include a standard mode interface, a juvenile mode interface, and an educational mode interface, with different mode interfaces displaying user-accessible content in the respective modes.

In some embodiments, the different operation modes supported by the display device are respectively referred to as a first mode and a second mode, where the user interface displayed in the first mode is referred to as a first mode interface, and the user interface displayed in the second mode is referred to as a second mode interface. According to the difference of the functions of the first mode and the second mode, the first mode interface is used for displaying the content accessible by the first mode, and the second mode interface is used for displaying the content accessible by the second mode. It should be appreciated that the content accessible by the first and second modes is a different range of content provided by the content provider.

In some embodiments, the standard mode is a first mode, and the educational mode and/or the juvenile mode is a second mode. The standard mode interface is a first mode interface, and the educational mode or pediatric mode interface is a second mode interface. In these implementations, the content accessible by the first mode includes content accessible by the second mode and other content. That is, the content accessible by the standard mode includes educational and juvenile media assets, as well as other content.

It should be noted that, the user may select the operation mode of the display device during the power-on navigation when the display device is first powered on. The power-on navigation process refers to a series of initialization basic setting processes for the display device, including but not limited to selecting an operation interface language, initializing a connection network, logging in a cloud service account, selecting a working mode, and the like. The user may select an operating mode of the display device in a mode selection interface. The mode selection interface comprises a plurality of mode options such as a standard mode, an educational mode, a juvenile mode and the like. When the user selects the "education mode", the display device will operate in the education mode, such as displaying an education mode homepage, executing an interactive control strategy corresponding to the education mode, and the like. When the user selects the "standard mode", the display device will operate in the standard mode, such as displaying a standard mode homepage, executing an interactive control policy corresponding to the standard mode, and the like.

It should be noted that, the user may also control the display device to switch from the standard mode to the education mode or the juvenile mode in the interface including the mode switching button provided in the standard mode, and control the display device to switch from the education mode or the juvenile mode to the standard mode in the interface including the mode switching button provided in the education mode or the juvenile mode.

In some embodiments, during the display device operating system startup process, the J application is started. And after the J application is started, reading the mode attribute variable in the system attribute data. If the read mode attribute variable is a first value, a standard mode system home page is displayed. If the read mode attribute variable is not the first value, a juvenile mode system homepage or an educational mode system homepage is displayed. For example, if the read mode attribute variable is a second value, displaying a juvenile mode system home page; if the read mode attribute variable is a third value, an educational mode system homepage is displayed.

In some embodiments, the J application performs a mode switching process in response to a user operation. Specifically, the J application modifies the mode attribute variable in the system attribute data to a second value in response to a user operation indicating entry from the standard mode to the juvenile mode, while updating the currently displayed standard mode interface to the juvenile mode interface. The J application modifies the mode attribute variable in the system attribute data to a first value in response to a user operation indicating entry into the standard mode from the pediatric mode, while updating the currently displayed pediatric mode interface to the standard mode interface.

In some embodiments, the television system homepage provided by the J application at least comprises a navigation bar and a content area below the navigation bar, wherein the navigation bar comprises a plurality of title controls, and the content displayed in the content area changes along with the change of the selected title control in the navigation bar, so that a title interface corresponding to the selected title control is displayed.

In some embodiments, the programs in the application layer may be integrated in the J application, presented by one control of the navigation bar. When the application control in the navigation bar is selected, further displaying the page of the application.

In some embodiments, the applications on the display device include system applications and user applications, which may include widgets applications and other system applications. After the display device is powered on, user applications and other system applications may be registered with the display device operating system. The Widget application is used for reading application registration information of the operating system, integrating Widgets corresponding to the user application and other system applications according to the read application registration information, so that a user can operate other system applications and user applications in the Widget application, such as starting a certain user application or operating a certain functional module of a certain user application. In specific implementation, the Widget application may have an independent UI interaction interface, which may be referred to as a Widget panel, and is mainly used for displaying the Widget control. One Widget control corresponds to a certain user application or system application. The user operates the corresponding application by operating the Widget control on the Widget panel.

In some embodiments, the system homepage displayed after the display device is started is a Widget application interface, that is, the system homepage is a Widget panel including Widget controls arranged according to a preset sequence, and when a user clicks any one Widget control, an application corresponding to the Widget control is started and related content of the application is displayed.

In some embodiments, the view display area used to display the Widget panel may occupy the entire screen, or may occupy a portion of the screen, such as the left area of the screen.

In some embodiments, the user may start the Widget application and display the Widget panel by inputting a preset operation.

In some embodiments, the display device receives the input preset operation through the J application, and after the J application receives the preset operation, starts the Widget application. And the Widget application displays Widget panels in different states according to the different attributes of the current working modes. Specifically, if the current working mode is the standard mode, displaying a Widget panel in a first state, wherein all Widget controls displayed in the Widget panel in the first state are available; and if the current working mode is a child mode or an education mode, displaying a Widget panel in a second state, wherein at least one Widget control in the Widget panel in the second state is not available. Thus, in the standard mode, the user can open all widgets controls, while in the juvenile mode or the education mode, the user cannot directly open the widgets controls limited to the corresponding mode.

In some embodiments, after the Widget application is started, a mode attribute variable in the system attribute data is read, and the current working mode is judged according to the read mode attribute variable. Therefore, the Widget panels in different states are presented according to the different attributes of the current working modes. It can be seen that the system attribute data can be shared between the Widget application and the J application, and decoupling between the Widget application and the J application is realized by sharing the system attribute data.

For example, when displaying the J application standard mode interface (such as the standard mode homepage shown in fig. 9), the user may press the left direction key (hereinafter referred to as "left key") of the remote controller for a long time to trigger displaying the Widget panel. And after the J application receives the operation, pulling up the Widget application in an implicit starting mode of the Intent. After the Widget application is started, the mode attribute variable in the system attribute data is read, and the current working mode can be judged to be the standard mode according to the read mode attribute variable, so that a Widget panel in a first state is displayed, wherein the Widget panel in the first state comprises one or more Widget controls, and each Widget control is available. When the Widget panel in the first state is displayed, a user can start an application corresponding to the Widget by operating any Widget control on the Widget panel, and relevant content of the application is displayed.

Notably, after the J application pulls up the Widget application in response to the received preset operation, the J application switches to the background operation, and the Widget application operates in the foreground. Further, after the Widget application is started, the Widget control on the Widget panel can acquire the focus, and the J application cannot acquire the focus. The designated Widget on the Widget panel firstly acquires a focus, and a selector indicating the focus position is displayed on the designated Widget control by default. When the Widget panel is displayed, the user can move the position of the selector through corresponding operation so as to select different widgets controls. The specified Widget control may be, for example, a Widget control of a first order on a Widget panel.

In some embodiments, the J application moves content in the standard mode interface to the right content area of the display for display in a lateral right direction of the display while the Widget application is pulled up in response to the received preset operation. After the Widget application is started, a Widget panel is displayed in a left content area of the display. In this way, while the Widget panel is displayed, the content in the J application standard mode interface can be continuously displayed.

In some embodiments, the right side content area of the display is referred to as a first content area and the left side content area of the display is referred to as a second content area. It should be appreciated that the sizes of the first content area and the second content area may be preset according to the requirements.

In some implementations, the left-hand portion of the content in the standard mode interface is displayed in the right-hand content region at the original display size, with the other right-hand portion of the content hidden. Illustratively, first, a distance x=w1 of rightward movement is determined according to a width W1 of a preconfigured left content area; then, new display position coordinates (X0 + X, Y0) of each interface element in the standard mode interface are calculated according to the distance moved to the right, wherein (X0, Y0) is the original display position coordinates of each interface element. And finally, on the basis of keeping the original display size of each interface element unchanged, displaying each interface element at a new display position, and hiding the interface element beyond the right edge of the display window.

In other implementations, the entire content in the standard mode interface is displayed in the right content area in a compressed display size. Illustratively, the width w2=wmax-W1 of the right content area is first determined as the user interface maximum width according to the preconfigured width W1 of the left content area. The reduction ratio S, s=w2/Wmax is then calculated from the width of the right content area and the maximum width of the user interface. The new display size of each interface element in the standard mode interface is calculated according to the reduction ratio as (a0×s) × (b0×s), where a0×b0 is the original display size of a certain interface element. And finally, displaying all the contents in the standard mode interface in a right content area with a new display size.

In other embodiments, the Widget panel is displayed overlaid on the content of the J application Standard mode interface. The Widget panel may be configured to be semitransparent, so that the covered content in the interface may be displayed through the Widget panel.

In some embodiments, the user may control switching to the juvenile mode or educational mode interface through a designated control on the J-standard mode home page. The child mode or education mode interface can display child media assets or education media assets, so that the children in the family can be restricted from using functions irrelevant to the child or education, and the children can learn in a pure space and are not interfered by other factors.

Notably, the juvenile mode interface of the J application is different from the "juvenile" title interface nested in the standard mode home page. In one aspect, the child mode interface is self-contained, its display scheme being individually configurable, while the "child" title interface is nested in the standard mode home page, its display scheme being part of the standard mode home page display scheme; on the other hand, the child mode interface displays content that is different from the "child" title interface. In some embodiments, an "education" control may also be included in the TAB column of the standard mode home page, and when focus is on "education", an "education" title interface will be displayed in the lower content display area. It should be appreciated that the "educational" heading interface differs from the user interface in educational mode based on a similar theory to the "juvenile" heading interface, and will not be repeated here.

Illustratively, while displaying the J-mode home page as shown in FIG. 10, the user may move focus to the "child" control by manipulating it. When focus is on the "child" control, the displayed title interface changes to the "child" title interface. Fig. 24 illustrates one possible "pediatric" title interface. As shown in fig. 24, the interface includes functionality controls such as "pediatric mode", "parental center", etc., wherein the user may control entry into the pediatric mode by operating the "pediatric mode" control. And the J application displays a child mode homepage after receiving the operation of the user on the child mode control, and sets the mode attribute value in the local attribute data to be a second value.

FIG. 25 is a child mode home page, particularly a user interface that the user selects the "child mode" control and determines to enter when displaying the "child" title interface of FIG. 24, in accordance with some embodiments of the application. As shown in fig. 25, the child mode home page includes an "exit child mode" control thereon, wherein the user can trigger a switch to the standard mode by operating the "exit child mode" control.

In some embodiments, when displaying the child mode homepage, the user may trigger the start of the Widget application and the display of the Widget panel through a preset operation.

Illustratively, when displaying the child mode home page as shown in fig. 25, the user may press the left button of the remote control for a long time to trigger the display of the Widget panel. And the J application receives the preset operation and pulls up the Widget application in an implicit starting mode of the Intent. After the Widget application is started, the mode attribute variable in the system attribute data is read, and the current working mode can be judged to be the child mode according to the read mode attribute variable, so that the Widget panel in the second state is displayed. Unlike the first state Widget panel displayed in the standard mode, at least one Widget control is not available in the second state Widget panel displayed in the pediatric mode.

In some embodiments, the Widget panel in the second state includes a hidden Widget control and an unlock control for triggering the hidden Widget control to appear, i.e., the Widget panel in the second state does not display any Widget control, so that all Widget controls are not available by hiding all Widget controls. At this time, the user cannot view the Widget controls on the Widget panel, and cannot operate any Widget control.

Notably, after the J application pulls up the Widget application in response to the received preset operation, the J application switches to the background operation, and the Widget application operates in the foreground. Further, after the Widget application is started, the unlocking control on the Widget panel can acquire the focus, and the J application cannot acquire the focus. When the user operates the unlocking control, the Widget application responds to the operation (such as clicking operation) of the unlocking control, displays a password input interface, and receives the password input by the user in the password input interface. After the Widget application receives the password input by the user, verifying whether the input password is correct; and if the input password is verified to be correct, controlling the hidden Widget control to appear in the Widget panel, so that the locking state of the Widget panel is released.

In some embodiments, the unlocked Widget panel is the same as the Widget panel in the first state.

After unlocking the Widget panel, the user may move the selector position by a corresponding operation to select a different Widget control. The user can start the application corresponding to the Widget control and display the related content of the application by operating the selected Widget control.

In some embodiments, in addition to the unlock control, auxiliary information, such as time information, weather information, unlock prompt information, and the like, may be displayed on the Widget panel in the second state.

In some embodiments, the J application moves content in the pediatric mode interface to a right content area of the display for display in a lateral right direction of the display while the Widget application is pulled up in response to the received preset operation. And after the Widget application is started, displaying a Widget panel in a second state in a left content area of the display. In this way, the content in the child mode interface can continue to be displayed while the Widget panel is displayed.

In some implementations, a portion of the content to the left in the pediatric mode interface is displayed in the right content area at the original display size, with another portion of the content to the right hidden. Alternatively, the entire content in the pediatric mode interface is displayed in the right side content area in a compressed display size. For more specific implementation, refer to the content described above for the standard mode interface, which is not described herein.

In other embodiments, the Widget panel of the second state is displayed overlaid on the content of the pediatric mode interface. The layer of the Widget panel in the second state may be set to be semitransparent, so that the covered content in the interface may be displayed through the layer of the Widget panel.

Fig. 26 is a user interface shown in some embodiments of the application, specifically, a user interface displayed upon receiving a long-press left key operation when the child mode system home page shown in fig. 25 is displayed. As shown in fig. 26, a Widget panel is displayed in the left content area of the user interface, and an unlock control and auxiliary information are displayed on the Widget panel, where the auxiliary information specifically includes time information "12:34", greetings" good noon "and weather information" today-11-2 ℃, clear to cloudy ". The child mode system home page is continuously displayed in the right content area of the user interface. Notably, in this example, limited to the size of the right view display area, the items in the juvenile mode system homepage are displayed with the original layout parameters aligned with the left side boundary of the right view display area and the display in the juvenile mode system homepage beyond the right side boundary of the user interface is hidden. The original layout parameters refer to the layout parameters of each item in fig. 25.

Fig. 27A is a user interface, specifically a password input interface displayed after a user operates an unlock control in the Widget panel, according to some embodiments of the present application. As shown in fig. 27A, in the password input interface, operable numeric soft keys, delete keys, and a password input area are displayed. The user can select a number to be input by moving the focus, input the selected number by a confirmation operation, delete the number that has been input by operating the delete key. It should be appreciated that fig. 27A is only one example of a password entry interface. The password entry interface displayed in different products may be different. For example, in some embodiments, a 6-bit or 8-bit password may be entered in a password entry area in the password entry interface, letter and/or symbol soft keys may also be displayed, a clear key may also be displayed, and so forth.

FIG. 27B is an unlocked user interface, particularly a user interface that is displayed after a user has entered a correct password in a password entry interface, as shown in some embodiments of the present application. As shown in fig. 27B, an unlocked Widget panel is displayed in the left content area of the user interface, and a plurality of Widget controls are displayed on the Widget panel, which are respectively "signal source", "application center", "city service", "small classroom", "contact", "player", "fitness plan", "standard", "device", "smart camera". The items in the homepage of the child mode system are integrally translated to the right content area of the user interface, and the displayed content in the page beyond the right boundary of the user interface is hidden.

In some embodiments, if the Widget application verifies that the password entered by the user in the password input interface is correct, the mode attribute variable in the system attribute data is modified to a second value or a third value.

In some embodiments, the J application polls the mode attribute variables in the system attribute data and updates the currently displayed juvenile mode interface or educational mode interface to a standard mode interface when the mode attribute system is polled to change from the second value or the third value to the first value.

In other embodiments, when the J application switches from background to foreground operation, the J application reads the schema attribute variables in the system attribute data. And if the read mode attribute variable is a first value, displaying a standard mode interface. If the read mode attribute value is the second value or the third value, continuing to display the juvenile mode interface or the educational mode interface. In this way, when the user successfully unlocks the Widget panel in the juvenile mode or the education mode, and then controls the Widget application to exit through a return instruction, the Widget application exits the foreground, the J application is switched to the foreground, and the mode attribute value is read as a first value, so that the currently displayed juvenile mode or the education mode interface is updated to be a standard mode interface, namely, the juvenile mode or the education mode is switched to be the standard mode.

In some embodiments, in the Widget panel of the second state, the Widget control is normally displayed, wherein the designated Widget control is not available, and the designated Widget control refers to a Widget control limited to use in the child mode and/or the educational mode. When the Widget application is concretely realized, after being pulled up by the J application, the mode attribute of each Widget is determined according to the configuration information of each Widget, if the Widget application is in a child mode and/or an education mode, widget control icons containing unavailable identifiers are displayed, and the Widgets are configured into an unavailable state; and if the mode is the standard mode, displaying the Widget control icon which does not contain the unavailable identifier. In these embodiments, the user may view the Widget panel normally to learn all the widgets on the Widget panel, and the user may directly operate the available widgets and may not directly operate the unavailable widgets.

In some embodiments, when a user selects an unavailable Widget control and determines that the Widget application responds to the user operation, displays a password input interface as shown in fig. 27A, and receives a password input by the user at the password input interface.

In some implementations, if the Widget application verifies that the password input by the user in the password input interface is correct, the Widget application directly pulls up the application corresponding to the Widget control operated by the user. After the corresponding application is started, the related content of the application can be directly displayed in the left content area, and the interface of the application can be displayed in a full screen mode.

In other implementations, if the Widget application verifies that the password input by the user in the password input interface is correct, the Widget control operated by the user is activated to be in an available state, and the unavailable identifier on the icon is withdrawn. When the user operates the Widget control again, the party can open the application corresponding to the Widget control, namely, display the related content of the application.

FIG. 28 is a user interface, particularly a user interface displayed upon receipt of a long left-click operation while displaying a juvenile mode system home page, shown in some example embodiments of the present application. In the user interface shown in fig. 28, a Widget panel is displayed in a view display area on the left side of the user interface, and a plurality of Widget controls are displayed on the Widget panel, which are respectively "signal source", "application center", "city service", "small classroom", "contact", "player", "exercise program", "standard", "device", "smart camera". The signal source, the application center, the city service and the equipment are unavailable widgets, locking angle marks are displayed on the unavailable widgets, and other widgets are available widgets.

When the user interface shown in fig. 28 is displayed, if the user selects the unavailable "application center" control and confirms, the Widget application will respond to the operation of the user on the "application center", display the password input interface shown in fig. 27A, and receive the password input by the user in the password input interface. In some embodiments, if the Widget application verifies that the password entered by the user in the password input interface is correct, the application center application module is directly pulled up. After the application center application module is started, a plurality of application program icons, namely the first-level item content corresponding to the application center control, can be displayed in the left content area. Or after the application center application module is started, displaying the homepage of the application center application module in a full screen mode, and displaying a plurality of application program icons in the homepage. In other embodiments, if the Widget application verifies that the password entered by the user in the password entry interface is correct, then the lock corner key on the "application center" control is revoked. The user needs to operate the "application center" control again to expand a plurality of application icons corresponding to the "application center" control in the left content area.

Fig. 29 illustrates a user interface displayed after a correct unlock code is entered in the code entry interface. Unlike the user interface shown in fig. 28, in fig. 29, a plurality of application icons are displayed floating above the Widget panel.

In some embodiments, the unlocking passwords corresponding to different widgets controls are the same or different. After the Widget application receives the password input by the user through the password input interface, comparing the received password with the correct password corresponding to the Widget control selected by the user, so as to determine whether the password input by the user is correct, and if so, activating the Widget control selected by the user into an available Widget control.

In some embodiments, when a user selects a Widget control with a locking corner mark and inputs a correct unlocking password in a password input interface, all unusable widgets controls in the Widget panel may be activated as usable widgets controls.

Along the foregoing examples, if the user selects the "application center" control and confirms while displaying the user interface shown in fig. 28, the Widget application will respond to the user's operation on the "application center", display the password input interface shown in fig. 27A, and receive the password entered by the user in the password input interface. If the Widget application verifies that the password input by the user in the password input interface is correct, locking angle marks on all unavailable Widget controls in the Widget panel are cancelled, and then the user interface shown in FIG. 30 is displayed. In fig. 30, the lock angle labels on the "signal source", "application center", "city service", "device" controls all disappear, meaning that the "signal source", "application center", "city service", "device" controls are all activated as available widgets controls.

In some embodiments, when the Widget panel in the global lock state or the local lock state as described above is displayed, the user may control to retract the Widget panel and return to the standard mode homepage or continue to display the child mode homepage or the education mode homepage by operating a return key on the remote controller or pressing a right key for a long time to input a return instruction. Specifically, after the Widget application receives an input return instruction, the foreground is exited, and the Widget panel is retracted. And the J application responds to the exiting of the Widget application from the foreground, and is switched to the foreground operation to read the mode attribute variable in the system attribute data. And if the read mode attribute variable is a first value, updating the currently displayed standard mode interface or the juvenile mode interface to be the standard mode interface. If the read mode attribute value is the second value or the third value, continuing to display the juvenile mode interface or the educational mode interface.

In some embodiments, when the Widget panel in the first state or the unlocked Widget panel is displayed, the Widget control in the Widget panel may acquire the focus, and the user may select the target Widget control to operate by moving the focus position. When the focus is on the target Widget control, the user can click on the target Widget control by operating a 'confirm' button on the remote controller. After the Widget application receives the operation of the target Widget control, starting the application corresponding to the target Widget control, and displaying the related content of the application.

In some embodiments, after an application corresponding to a Widget control operated by a user is started, primary item content of the application may be displayed in a preset content area, for example, floating on a Widget panel and displayed in a left content area of a user interface. The primary page of the application, such as the application home page, may also be displayed full screen.

Fig. 31 is an exemplary user interface displayed upon user selection of the "AI little assistant" control in the Widget panel shown in fig. 10. As shown in fig. 31, the first-level item content corresponding to the "AI-little assistant" is displayed in the view display area on the left side of the user interface. Referring to fig. 31, the primary item contents corresponding to the "AI-assistant" include "weather", "information", "calendar" controls, and five-day weather change diagrams and schedule information. In FIG. 31, focus is left on the "weather" control by default. At this time, the user may select other controls to display different item contents by operating the moving focus, for example, when the focus selects the "calendar" control, the display of weather information may be canceled, the calendar details of the present month may be displayed, and when the focus selects the "information" control, the display of the calendar details of the present month may be canceled, and the information list may be displayed.

Fig. 32 is an exemplary user interface displayed upon user selection of the "application center" control in the Widget panel shown in fig. 10. As shown in fig. 32, the primary item content corresponding to the "application center" is expanded in the view display area on the left side of the user interface, specifically including a plurality of application icons. When displaying fig. 32, the focus is stopped on the first application icon by default, and the user can select and operate any one of the applications to start the application by operating to move the focus position.

Fig. 33 is an exemplary user interface displayed upon user selection of the "signal source" control in the Widget panel shown in fig. 10. As shown in fig. 33, a signal source list is displayed in the view display area on the left side of the user interface, the signal source list being formed by arranging a plurality of signal source options such as HDMI1, HDMI2, analog tv, terrestrial digital, and the like. In the interface shown in fig. 33, the user can move the signal source options hidden in the signal source list to the view display area to display by continuously moving the focus downwards. In fig. 33, the focus is stopped on HDMI1 by default, and the user can select and operate any one of the signal source options by operating to move the focus position.

In some embodiments, the user may trigger to display the secondary item content corresponding to the primary item content by operating the primary item content corresponding to the application of the Widget control.

Fig. 34 is an exemplary user interface displayed upon user selection of the "set" control in the Widget panel shown in fig. 10. As shown in fig. 34, a plurality of primary setting items such as "one-touch acceleration", "one-touch up", "play setting", "image mode", and "sound mode" are displayed in the view display area on the left side of the user interface, and the focus is stopped on the "one-touch acceleration" item by default. The user can select an item to be operated by moving the focus position, and trigger the display of the corresponding secondary item content by operating the selected primary setting item. For example, if the user selects the "sound mode" item and confirms, a secondary setting item corresponding to the "sound mode" item will be displayed. As shown in fig. 35, the secondary setting items corresponding to "sound modes" such as "AI sound quality", "cinema", "music", "sports", and the like are displayed in the view display area on the left side of the user interface, and the user can select a sound mode to be set by moving the focus position, or cancel the sound mode currently set.

It should be appreciated that the content and its hierarchy that a user triggers the display by clicking on the Widget control depends on the design of the corresponding application of the Widget control, and those skilled in the art can design the display logic of the relevant content of each application according to the user's needs.

Notably, in order to avoid user confusion in exploring the content of each hierarchical level of items, navigation icons are displayed in the view display area in which the content of the items is displayed. For example, when the content of a secondary item corresponding to a certain application is displayed, an icon indicating a return to the previous level is displayed in the corresponding view display area. If the currently displayed item contents further include the next level item contents, an icon indicating to enter the next level is displayed in the corresponding view display area.

The display device provided by the application can work in two modes, namely a first mode and a second mode, wherein the content accessible in the first mode comprises the content accessible in the second mode and other content, so that the user can only access the allowed content in a certain mode and can limit the access to other content by configuring the content accessible in different modes. For example, the first mode is a standard mode and the second mode is a juvenile mode or an educational mode. The user may access the juvenile, educational and other assets while the standard mode interface is displayed, and the user may only access the educational and/or juvenile assets while the juvenile mode interface or the educational mode interface is displayed.

In some embodiments, the user may call out the Widget control panel through a preset operation. When the display equipment receives the preset operation, firstly judging the attribute of the current mode; if the current mode is the first mode, displaying a Widget panel in a first state, wherein all Widget controls displayed in the Widget panel in the first state are available; and if the current mode is the second mode, displaying a Widget panel in a second state, wherein at least one Widget control in the Widget panel in the second state is unavailable. Thus, in the first mode, the user may open all of the widgets controls, while in the second mode, the user will not be able to directly open those widgets controls that are restricted to use in the second mode.

According to the display device provided by the embodiment, the embodiment of the application also provides a Widget control display method. As shown in fig. 36, the method may include the steps of:

S110A, when the system page in the first mode or the second mode is displayed, a preset operation for displaying the Widget control is received.

S120A, responding to the preset operation, and judging the current mode attribute. If the current mode is the first mode, S130A is performed, and if the current mode is the second mode, S140A is performed.

Wherein the content accessible in the first mode includes content accessible in the second mode and other content.

S130A, displaying a Widget panel in a first state, wherein all Widget controls displayed in the Widget panel in the first state are available.

Specifically, moving the content in the system page in the first mode to the first content area for continuous display, and displaying the Widget panel in the first state in the second content area.

S140A, a Widget panel in a second state is displayed, wherein at least one Widget control in the Widget panel in the second state is unavailable.

Specifically, moving the content in the system page in the second mode to the first content area for continuous display, and displaying the Widget panel in the second state in the second content area.

In a more specific implementation, the method comprises the following steps: displaying the left part of the content in the system homepage in the first mode or the second mode in the first content area in the original display size, and hiding the other right part of the content; alternatively, the entire contents of the system homepage in the first mode or the second mode are displayed in the first content area in the compressed display size.

In some embodiments, the Widget panel of the second state includes a hidden Widget control and an unlock control for triggering the hidden Widget control to appear. The display method provided by the application further comprises the following steps: responding to the confirmation operation of the unlocking control, and displaying a password input interface; and when the correct password input in the password input interface is received, controlling the hidden Widget control to appear in a Widget panel.

In some embodiments, a designated Widget control in the Widget panel of the second state is not available, the designated Widget control being a Widget control that restricts use in the second mode. The display method provided by the application further comprises the following steps: responding to the confirmation operation of the unavailable Widget control, and displaying a password input interface; when a correct password input in the password input interface is received, displaying the content corresponding to the Widget control of the operation; and responding to the confirmation operation of the available Widget control, and displaying the content corresponding to the Widget control operated.

In some embodiments, in response to an input indicating a switch from the second mode to the first mode, a mode attribute variable in the system attribute data is set to a first value; in response to an input indicating an operation to switch from the first mode to the second mode, a mode attribute variable in the system attribute data is set to other values.

In some embodiments, the current mode is determined according to the following steps: acquiring a mode attribute variable in system attribute data; if the mode attribute variable is a first value, determining that the current mode is a first mode; if the mode attribute variable is not the first value, it is determined that the current mode is the second mode.

In some embodiments, the mode attribute variable is set to a first value when a correct password entered in the password input interface is received. The corresponding Widget panel is also adjusted according to the changed mode attribute

In some embodiments, the content corresponding to the Widget control of the display operation includes: and starting the application corresponding to the Widget control, and displaying the primary item content corresponding to the application in the second content area through the application, or displaying the primary page corresponding to the application in a full screen mode. In some embodiments, the display method provided by the present application further includes: receiving an input return instruction when the Widget panel is displayed; acquiring a mode attribute variable in system attribute data; if the mode attribute variable is a first value, the Widget panel is withdrawn, and a system homepage in a first mode is displayed; and if the mode attribute variable is not the first value, the Widget panel is withdrawn, and a system homepage in a second mode is displayed.

In some embodiments, the display method provided by the present application further includes: receiving an input return instruction when displaying the content corresponding to the application; and responding to the return instruction, and controlling to return to a previous interface, wherein the previous interface is an interface before displaying the current content corresponding to the application.

In some embodiments, the icons of the unavailable widgets controls in the Widget panel in the second state have an unavailable identifier; and when the correct password input in the password input interface is received, the unavailable identification is revoked.

FIG. 37 is a flow chart of a method of component display in some embodiments of the application. An embodiment of the present application provides a display apparatus including: a display configured to present a user interface; a controller coupled to the display, the controller being configured to perform the following steps when performing the component presentation method shown in fig. 37:

S1B, receiving starting operation of the desktop application, acquiring service data of each service module provided by the desktop application, and displaying a desktop homepage in a user interface based on the service data of each service module.

FIG. 8 is a schematic diagram of a system home page in accordance with some embodiments of the application; FIG. 38 is a diagram of a desktop homepage in some embodiments of the application. Referring to fig. 8, a user activates a display device in which a system home page is presented in which desktop application (J application) control icons are presented. Referring to fig. 38, the desktop application control icon is triggered to perform a launch operation of the desktop application to present a desktop homepage in the display device.

When the desktop homepage is displayed, service data of each service module provided by the desktop application is acquired, the service data is used for realizing the functions of the service modules, the service data comprises service IDs, and the service IDs are used for representing the service modules. Based on the business data of each business module, displaying a desktop homepage in a user interface according to a preset homepage layout mode, wherein the desktop homepage displays the functional content of each business module.

In some embodiments, each business module provided by the J application is shown in the desktop homepage, and each business module can be added to the Widget panel in the form of a Widget based on user-defined settings to provide a quick entry of the business module.

The Widget panel is displayed in the desktop homepage, and the display mode of the Widget panel can synchronously display the Widget panel while displaying the desktop homepage in the user interface of the display device when the desktop application is started; or when the desktop application is started, the desktop homepage is preferentially displayed in the user interface of the display device, and when a preset operation is generated based on the desktop homepage, the Widget panel is called out again to be displayed in the desktop homepage.

In some embodiments, the Widget panel is usually hidden and displayed when the display device is running, and when a user needs to quickly start a certain function (such as a function implemented by a certain service module) through the Widget panel, the Widget panel can be adjusted to be displayed in a desktop homepage based on a preset operation, wherein the preset operation refers to that the user presses a left key or other preset function keys of the remote controller for a long time. If the user wants to start a certain function, triggering a corresponding Widget in the Widget panel to directly start the function, namely starting a certain service module provided by the desktop application.

In some embodiments, when a user starts a desktop application, the user may register a corresponding Widget for a certain service module at the same time. At this time, when the desktop application is started, the WidgetManagers of all the service modules are collected, the component information registration related to the service modules is triggered, and the component information registration is stored in the WidgetServer.

Specifically, upon registering the Widget for the service module, the controller is further configured to perform the steps of:

step 101, when registering widgets for service modules, service data of each remote service module is acquired, and the remote service module comprises a service module provided by a desktop application or a third party application.

Step 102, sending the service data of each remote service module to a data center module, where the data center module is configured to process the service data of each remote service module.

Step 103, after the service data is processed, a service component management module is respectively configured for each remote service module based on the service ID of each remote service module.

Step 104, calling a target service component management module, registering a corresponding Widget for the target remote service module, and storing component information generated by registering the Widget and a corresponding service ID into the component management module.

Referring again to the desktop component framework shown in fig. 5, when registering widgets for a service module, service data of at least one remote service module for performing component display may be obtained. The remote business modules include a desktop application provided business module (e.g., business module a in fig. 5) or a third party application (e.g., application B in fig. 5).

When the desktop application is started, a data center module (WidgetService) is synchronously pulled up to prepare for receiving service data of a remote service module. Therefore, when the Widget registration based on the new service module exists, the data center module receives the service data of the remote service module.

After the data center module simply processes the service data of the remote service module, a service component management module is respectively configured for each remote service module. A remote service module corresponds to a service ID, and thus, the corresponding service component management module (WidgetManager) may be represented by the service ID, and a service module corresponds to a service component management module.

In order to realize the registration of the widgets, the data center module sends the service data of the target remote service module to the corresponding target service component management module so that the target service component management module registers the corresponding widgets for the target remote service module. For example, the service data of the service module a is sent to the service component management module a for component registration, and the service data of the service module B is sent to the service component management module B for component registration.

When the target service component management module carries out component registration on the target service module, component data and Widget panel information can be synchronously generated to form the component information of the target service module. For example, the component information a of the service module a includes component data a and Widget panel information a, and the component information B of the service module B includes component data B and Widget panel information B.

After the target service component management module performs component registration on the target service module, the component information of the target service module needs to be further stored, and the module for storing the component information is a component management module (WidgetServer). Therefore, after the registration is completed, the target service component management module stores the component information generated by registering the widgets for the target service module and the corresponding service ID into the component management module (WidgetServer). The component management module stores the component information of the corresponding service module according to the service ID so as to distinguish and call the component information of different service modules.

The method for registering the widgets for the service module can be applied to the starting of the desktop application and the operation process of the desktop application, and can be used for realizing registration as long as the condition of registering the widgets for the service module exists.

S2B, when a Widget panel is displayed, a service component management module is called to acquire component information of a service module corresponding to each service ID from the component management module and send the component information to a component display module, wherein the component information refers to information generated when the service module provided by a desktop application registers the Widget, the component information comprises component data and Widget panel information, the component data refers to data required to be displayed on the Widget panel by the service module characterized by the service ID, and the Widget panel information refers to interface layout information displayed by the Widget.

After launching the desktop application, a desktop home page is presented in a user interface of the display device. In the desktop homepage display process, the Widget panel can be synchronously displayed, or the Widget panel is called out to be displayed in the desktop homepage based on preset operation. Then, when the Widget panel needs to be displayed, based on the desktop component framework shown in fig. 5, the service component management module is called to acquire the component information of the service module corresponding to each service ID from the component management module, and the component information is sent to the component display module for display.

The component management module stores the component information of all the service modules capable of carrying out component display, so that when the Widget panel needs to be presented, the component information of all the service modules needs to be displayed.

When the desktop application is started, if the component registration of the new service module is not performed, the service component management module corresponding to the different service modules acquires the historically added component information from the component management module. That is, based on each service ID added in history, the corresponding service component management module obtains the component information of the service module corresponding to the service ID from the component management module.

When the desktop application is started, if the component registration of the new service module is performed, the newly registered component information needs to be acquired from the component management module in addition to the component information added in the query history. That is, based on each service ID newly registered, the corresponding service component management module obtains the component information of the service module corresponding to the service ID from the component management module.

After the component information of all the service modules to be displayed is acquired, each service component management module sends the acquired component information of the service module to the component display module so that the component display module completes the display of the Widget panel based on the component information of each service module.

In some embodiments, when the user launches the desktop application and displays the Widget panel while presenting the desktop homepage in the display device, the display of the Widget panel may be delayed due to the fact that the generation of the desktop homepage and the generation of the acquired data by the Widget panel may be different. At this time, in order to ensure that the data can be displayed in the Widget panel, so as to avoid the error of interface display caused by the error of a user, the Widget panel can be displayed by using default data. For example, the default data includes default pictures and default characters, and the Widget panel is generated and timely displayed based on the default pictures and the default characters. After the cached component information is obtained from the component management module based on the desktop component framework, the component information of each service module is replaced and displayed in the Widget panel.

S3B, calling a component display module to generate a Widget panel based on the component data and Widget panel information corresponding to each service ID, and displaying the Widget panel in a desktop homepage, wherein the Widget panel is provided with a plurality of Widgets for providing starting inlets of the service modules.

After receiving the component information of the corresponding service module sent by each service component management module, the component display module can generate a Widget panel based on the component information of each service module and display the Widget panel in a desktop homepage. Each service module generates a corresponding Widget, and is distributed on a Widget panel, and a certain Widget is triggered, so that the quick starting of the service module corresponding to the Widget can be realized.

For this purpose, the controller generates the Widget panel based on the component data and the Widget panel information corresponding to each service ID when executing the calling component display module, and is further configured to execute the following steps:

step 31D, calling a component display module to generate a component display frame including a plurality of widgets based on the Widget panel information corresponding to each service ID, where one service ID corresponds to one Widget.

And step 32D, displaying the component data corresponding to each service ID on the corresponding Widget to form a Widget panel, wherein one Widget corresponds to one service module.

The Widget panel information in the component information is used for determining the layout and the size (length and width dimensions) of the Widget corresponding to each service module, so that when the Widget corresponding to each service module is displayed in the Widget panel, the layout and the ordering can be performed according to the dimensions of each Widget. The component data in the component information is used for determining information, such as names, icons, brief introduction content and the like, of corresponding service modules displayed on each Widget.

Therefore, when desktop Widget panel display is performed, the component display module determines the layout and the ordering of the Widgets corresponding to each service module based on the Widget panel information of the service module corresponding to each service ID. After the Widget layout and sequencing are completed, the component data of the service module corresponding to each service ID are respectively displayed on the corresponding Widget to form a Widget panel. The service IDs and the service modules are in one-to-one correspondence with the widgets.

And the component data of the service module also comprises triggering operations such as clicking and the like, if a user wants to quickly start a certain service module provided by the desktop application, the Widget corresponding to the service module is found in the Widget panel, and the Widget is triggered, so that the user can directly enter a homepage of the corresponding service module, and the quick start of the service module is realized.

In some embodiments, when the widgets are displayed in the Widget panel, a plurality of grid networks with the same size and regular arrangement are arranged on the Widget panel. Since different widgets correspond to different component sizes, the number of grids occupied by different widgets is different.

Fig. 39 is a schematic diagram of a Widget panel according to some embodiments of the present application. In order to simplify the drawing, the desktop homepage part in actual display is not shown, and it should be noted that the Widget panel and the desktop homepage are two independent display modules, and the Widget panel can be independently set with different display modes outside the desktop homepage. Referring to fig. 39, for example, the my home component occupies 3 grids in the lateral direction, the corresponding component size is 3×1 (i.e., 3 control units in the lateral direction, one control unit in the vertical direction, and the subsequent size expressions are not repeated); the "my applications" component occupies 2 grids in the lateral direction, then the corresponding component size is 2 x 1; the "shortcut setting" component occupies 1 grid, and the corresponding component size is 1×1; the "media center" component occupies a grid, and the corresponding component size is 1 x 1.

And splicing and sequencing the widgets according to the sizes of the components, so that the total number of grids transversely occupied by the plurality of spliced widgets is the same as the total number of transverse grids preset by the Widget panel, the number of vertical grids can be expanded in real time, namely the total number of transverse display grids of the Widget panel is unchanged, and the total number of longitudinal display grids is variable.

In some embodiments, if a Widget corresponding to a service module is newly added, a Widget is newly displayed on the basis of each Widget originally displayed in the Widget panel. If the component size of the Widget is larger and the Widget cannot be completely displayed transversely, one row of the Widget is automatically expanded downwards to be displayed. If a certain Widget displayed in the Widget panel is deleted, the Widget automatically contracts longitudinally.

In some embodiments, the determination of the position of the newly added component may be: acquiring the component size of the newly added Widget, determining whether the space in the rectangular area corresponding to the position of all the current controls can accommodate the component size of the newly added Widget, if so, placing the newly added Widget adjacent to the existing component, and if not, automatically expanding and placing one row below.

In some embodiments, determining a vacancy in a rectangular area corresponding to the current position of all the controls, determining a position combination which can be formed by the vacancy area, and determining whether the formed position combination contains the size of the component of the newly added Widget. The four vacancies of the exemplary field-font distribution may be partitioned into vacancies of the following size according to a vacancy partition technique: 1×1, 1×2, 2×1, 2×2. The vacancy segmentation technique may be implemented using existing techniques.

In some embodiments, a row is automatically expanded below, the height of an expanded row is determined according to the determined height of the newly added component of the Widget, and then the newly added component of the Widget is placed in the expanded new row. For example, if the height of the component of the newly added Widget is 2, a new row with a high level of 2 needs to be added; if the height of the component of the newly added Widget is 1, a newly added row with a high bit of 1 needs to be added.

In some embodiments, the Widget panel is always loaded in the desktop application, that is, the Widget panel is displayed at a certain area position in the desktop homepage, and the Widget panel cannot be started to be displayed on other pages.

In some embodiments, the desktop homepage may switch different TABs for different displays. The other pages are secondary pages corresponding to the arbitrary TAB controls from the left homepage, or tertiary pages of the non-desktop homepage which the secondary pages jump to.

In some embodiments, if the display device directly enters the broadcast television signal source when being started, for example, directly playing a television program, at this time, the display device does not display a system homepage, but cannot enter the desktop homepage, that is, cannot generate a preset operation of starting a service module or a Widget panel, that is, cannot call out the Widget panel for display.

In some embodiments, an instruction of a user to move the focus is received, when the focus moves to the left or right boundary of the page, whether the current page is a desktop homepage is determined in response to a specification of continuing to move the focus with the user, if so, the desktop homepage is moved in an opposite direction, and a Widget panel is displayed at a position vacated on the display interface.

Therefore, the display device provided by the application is provided with the desktop component frame, and the user-defined layout of each Widget displayed in the desktop Widget panel is realized through the desktop component frame, so that the display device is not limited by a system, can realize rich interface effects, and has good user experience.

In some embodiments, when a service module corresponding to a certain Widget displayed in the Widget panel changes data, the display content of the Widget may be refreshed. The data refreshing mode comprises that the business module with data change actively notifies the desktop application, and the Widget panel actively acquires the data change of each business module from the data center module according to a certain time interval.

In some embodiments, when the service module actively notifies the desktop application of the manner of data refresh, the controller is further configured to perform the steps of:

step 41D, when the target service module generates information update, the data center module is called to acquire new component information generated by the target service module, and based on the target service ID of the target service module, the new component information of the target service module is sent to the target service component management module corresponding to the target service ID.

And 42D, calling the target service component management module to send the new component information corresponding to the target service ID to the component display module.

Step 43D, calling a component display module to determine a corresponding target Widget in the Widget panel based on the target service ID, and updating information display of the target Widget based on new component information corresponding to the target service ID, so as to update display information in the Widget panel.

When the service module actively notifies the desktop application to refresh data, the target service module generating data change actively notifies the desktop application to refresh the display content of the corresponding Widget in the Widget panel, and at this time, the target service module generating data change sends the data change to a data center module (Widget service).

The data change which can be generated by the target service module comprises component data change or Widget panel information change, the component data change can comprise information to be displayed or trigger operation mode change, and the Widget panel information change comprises change of patterns, layout and the like. Thus, new component information can be generated based on the changed data of the target business module, and the new component information can be actively generated to the data center module.

And the data center module simply processes the new component information of the target service module and distributes the new component information of the target service module to the target service component management module corresponding to the target service module. At the time of distribution, a target service component management module (WidgetManager) for managing the target service module component information may be determined based on the target service ID of the target service module.

In order to realize the data refreshing of the Widget panel, the target service component management module is called to send new component information corresponding to the target service ID to the component display module, and the component display module updates the display content of the corresponding Widget in the Widget panel based on the new component information. Meanwhile, in order to update the cache data in the component management module in time, the target service component management module synchronously sends corresponding new component information to the component management module for storage based on the target service ID.

When the new component information characterizes that the target service module generates the data change of the component data, for example, the target service module is a contact application end, and if a user newly adds/deletes a contact at the application end, the changed component data is the contact information. After the contact information is transferred to the component display module based on the desktop component framework, the target service ID of the target service module determines the target Widget in the Widget panel as a 'contact' component. Therefore, the newly added contact information is updated to the display content of the contact component, or the deleted contact information is deleted from the contact component, so that the display information in the Widget panel is updated.

When the new component information characterizes that the target service module generates the data change, for example, the target service module is a contact application end, if the style of a 'contact' component is square, the component style is changed into a round, and then the changed Widget panel information is the component style. After the component style information is transferred to the component display module based on the desktop component frame, the target service ID of the target service module determines that the target Widget in the Widget panel is a contact component. Therefore, the component style of the contact component is updated from the original square to a round, and the update of the display information in the Widget panel is realized.

Therefore, when a certain service module provided in the desktop application generates data change, the service module actively informs the desktop application to update the display information in the Widget panel in real time, so that the dynamic assembly can be realized very conveniently, and the display effect of the Widget panel is better.

In some embodiments, when the Widget panel actively acquires the change data of the service module to perform data refreshing, the controller is further configured to perform the following steps:

51D, when the Widget panel display information is refreshed at intervals, calling a target service component management module to acquire new component information generated by the target service module from the data center module according to preset intervals, and transmitting the new component information generated by the target service module to the component display module;

and step 52D, calling a component display module to determine a corresponding target Widget in the Widget panel based on the target service ID, and updating information display of the target Widget based on new component information corresponding to the target service ID, so as to realize interval refreshing of display information in the Widget panel.

When the Widget panel is adopted to actively acquire the change data of the service module to refresh the data, the Widget panel actively requests the target service module to return the change data, at this time, the target service module receives the request and then sends the new component information generated by the target service module to the data center module, and after simple data processing, the service component management module corresponding to the target service module (target service ID) acquires the new component information generated by the target service module from the data center module.

In some embodiments, the preset interval of the Widget panel interval update information may be set to be 30 minutes, and then the preset interval of calling the target business component management module to actively acquire the new component information of the target module is also set to be 30 minutes. The preset interval may be other values, and is not particularly limited.

Fig. 40 is a schematic diagram of a player Widget data refresh in a Widget panel according to some embodiments of the present application. When the new component information characterizes that the target service module generates the data change, for example, the target service module is a player, and the corresponding target Widget in the Widget panel is a "player" component. Referring to fig. 40 (a), if the "player" component originally displays the song A, B, C, after a preset interval of 30 minutes, the target service component management module corresponding to the player actively requests the player to return the current playing information through the data center module. Referring to fig. 40 (b), if the current playing information is song A, B, C, D, E, the display content of the "player" component in the Widget panel is changed from "song A, B, C" to "song A, B, C, D, E", so as to automatically present the latest playing information of the player to the user, thereby realizing the interval refreshing of the display information in the Widget panel.

Therefore, the desktop application can actively acquire the data change generated by a certain service module, and the target service component management module corresponding to the service module actively acquires the new component information of the service module according to the preset interval, and updates the display information in the Widget panel at the active real-time interval, so that the dynamic component can be conveniently realized, and the display effect of the Widget panel is better.

In some embodiments, when implementing the dynamic component, the desktop application may further change an effective state of a corresponding Widget in the Widget panel according to a service state of each service module, where the effective state is used to characterize whether the corresponding Widget can be triggered by clicking. For example, if a certain service module is unloaded, in order to prompt the user that the service module cannot be started quickly through the widgets in the Widget panel, a failure identifier may be added to the corresponding widgets.

Specifically, when adding the failure identifier to the failed Widget, the controller is further configured to perform the following steps:

step 61D, when deleting the target service module, receiving a deletion operation for the target service module, and calling a corresponding target service component management module to send a service deletion instruction carrying the target service ID to the component display module based on the target service ID of the target service module.

Step 62D, calling a component display module, and adding a failure identifier to a target Widget corresponding to the target service ID in the Widget panel based on the service deletion instruction, where the failure identifier is used for characterizing the Widget failure corresponding to the target service module corresponding to the target service ID.

When a certain service module is deleted, the service state of the service module changes, so that the desktop application is actively notified to update the display information of the corresponding Widget in the Widget panel.

If a certain service module configured in the desktop application is deleted/offline, which means that the desktop application does not provide the service module any more, the application management module of the display device sends the deleted/offline broadcast to the Widget panel, and the failure identifier is displayed on the target Widget corresponding to the service module. When the application module is deleted, the failure identifier is displayed on the corresponding Widget in the Widget panel, so that the user is informed of the corresponding Widget failure in time, the corresponding service module is deleted, the corresponding service module cannot be started by triggering the Widget, and the user experience is good. Meanwhile, in order to update the cache data in the component management module in time, the target service component management module synchronously sends a corresponding service deleting instruction to the component management module based on the target service ID, so that the component management module deletes the component information of the deleted service module and updates the cache.

Failure refers to unavailability. Failure of a business module refers to whether an application is available, e.g., if the application is offline or background is no longer maintained for policy reasons, although it is present in the display device, the business module is not available. In contrast, active refers to the available state.

When the target service module is deleted, the service state of the target service module changes, and then new component information of the target service module represents that the component data changes, and at this time, the component data means that the target service module is unavailable, i.e. the triggering operation cannot be executed.

After the target service module generates new component information, the desktop application is actively notified, namely the new component information is sent to the data center module, and after the data center module simply processes the new component information of the target service module, the new component information of the target service module is distributed to the target service component management module corresponding to the target service module. At the time of distribution, a target service component management module (WidgetManager) for managing the target service module component information may be determined based on the target service ID of the target service module.

And calling a target service component management module corresponding to the target service ID to send a service deleting instruction carrying the target service ID to the component display module based on the new component information. In order to realize data refreshing of the Widget panel, based on a service deletion instruction, a component display module adds a failure identifier to a target Widget corresponding to a target service ID in the Widget panel, wherein the failure identifier is used for representing the failure of the Widget corresponding to the target service module corresponding to the target service ID.

Fig. 41 is a schematic diagram illustrating a failure identifier on a Widget according to some embodiments of the present application. Referring to fig. 41, if the service module offloaded by the user is a random listen, after a service deletion instruction of the media center is transferred to the component display module based on the desktop component frame, a target service ID of the target service module determines that a target Widget in the Widget panel is a "random listen" component. Finally, displaying the invalidation mark on the Widget control corresponding to the random listening service in the Widget panel, such as the mark which is invalid in the figure.

Therefore, when a certain service module provided in the desktop application is deleted, the service module actively informs the desktop application, and the display information in the Widget panel is updated in real time, so that a dynamic component can be conveniently realized, and the display effect of the Widget panel is better.

In some embodiments, after the Widget panel is displayed on the desktop homepage, when the user sees that the Widget with the failure identifier displayed in the Widget panel exists, if the user triggers the failure Widget, the user pops up the failure prompt interface in the current interface.

step 71D, receiving a triggering operation of the target Widget with the failure identifier displayed in the Widget panel, not executing the starting process of the target service module corresponding to the target Widget, and displaying a failure prompt interface with a delete button in the desktop homepage.

And step 72D, receiving triggering operation of a deleting button, and deleting the target Widget in the Widget panel.

When the user triggers the target Widget with the failure identifier displayed in the Widget panel, the target service module corresponding to the target Widget cannot be started. Therefore, when the target Widget with the failure identifier in the Widget panel is triggered, the action of starting the target service module corresponding to the target Widget is not executed.

And in order to inform the user that the target service module corresponding to the current target Widget cannot be started, a failure prompt interface is popped up in the desktop homepage.

FIG. 42 is a schematic diagram of another failure notification interface according to some embodiments of the application. Referring to fig. 42, when a user triggers a spent "media center" Widget, a spent hint interface is presented in the current user interface. The invalidation prompt interface is provided with a deleting button, a cancelling button and a replacing control display area. The delete button is used for deleting the invalid Widget, and the cancel button is used for closing the invalid prompting interface. The change control display area is used for displaying other widgets recommended by the system and capable of being displayed. If the user clicks the delete button, the target Widget in the Widget panel may be deleted, i.e., the "media center" Widget is deleted.

In some embodiments, the Widget panel is located in the desktop homepage, and when the target Widget that is disabled is triggered based on the Widget panel, the disabling prompt interface is provided by the Widget panel, that is, the component display module controls display. The popped failure prompt interface is displayed on the upper layer of the Widget panel, which is equivalent to the display of the failure prompt interface on the upper layer of the desktop homepage. The display of the failure prompt interface does not influence the original display structure of the desktop homepage, namely, each business originally displayed in the desktop homepage cannot adjust the position, and the failure prompt interface is displayed in a suspension mode.

In some embodiments, when the recommended Widget control recommended by the system is displayed in the control display area, the recommended Widget control is generated based on an attribute parameter of the target Widget control with the failure identifier, and the attribute parameter is control (Widget) information. Because the user registers the Widget based on the service application, the icon, the size, the service type, the application and other information generated when registering the service Widget control are all stored in the component management module (Widget server). Thus, the attribute parameters of the target Widget may be obtained from a component management module (Widget server). The attribute parameters include control size, service type, application to which they belong, etc. The recommended Widget control is a control with the same characteristic as the target Widget, and is used for replacing and displaying the position of the deleted target Widget control based on the triggering of a user.

The replacement control display area in the failure prompt interface can be displayed below the deletion button, if the threshold of the display positions which can be displayed by the replacement control display area can be 6, the replacement control display area can display 6 recommended widgets at most, the display positions which can be displayed by the replacement control display area can be other numbers, and the display positions can be adjusted according to actual application conditions.

Because the widgets have different control sizes, in order to facilitate the system recommended widgets to be displayed to the home position of the deleted target Widget, widgets with the same size can be searched based on the size of the deleted Widget. But can be based on the user can start the widgets with similar characteristics at the same position, and can also be based on the service type or the application as attribute parameters, and can recommend the widgets which can be alternatively displayed for the user. That is, a recommended Widget control having the same characteristics as a target Widget refers to a control having at least one of the characteristics of the same control size, similar service types, the same belonging application, and the like.

In some embodiments, the desktop component framework may implement multi-level menu expansion of a certain Widget in the Widget panel, and may classify each service module provided by the desktop application according to service requirements, divide services belonging to the same type into the same class, and configure a total Widget in the Widget panel for the class. When a certain service under the total Widget needs to be triggered, the total Widget can be triggered, a secondary service menu is popped up in a Widget panel, and menu items corresponding to the services belonging to one type are displayed in the secondary service menu. And triggering a menu item based on the secondary service menu, so that the corresponding service can be started quickly.

To this end, when the desktop component framework classifies based on the type of each business module, the controller is further configured to perform the steps of:

and 81D, when the Widget group is added in the Widget panel, receiving a trigger operation of an addition button displayed in the Widget panel, displaying a Widget group list and a component preview area in a user interface by switching the addition page, wherein the service types of service modules of the Widgets under the same Widget group are the same, and the component preview area displays the Widgets corresponding to the Widget group.

Step 82D, receiving a triggering operation on the target Widget packet in the Widget packet list, and displaying the Widget corresponding to the target Widget packet in the component preview area.

Step 83D, receiving a trigger operation for the target widgets in the component preview area, and adding the target widgets corresponding to the target Widget group into the Widget panel.

The user can add the Widget based on the Widget panel, at this time, an add button (as shown in fig. 39) is displayed at the bottommost part of the Widget panel, the add button is triggered, an add page is generated, and the display is switched in the user interface.

FIG. 43 is a schematic diagram of adding pages according to some embodiments of the application. Referring to fig. 43, a Widget packet list and a component preview area are displayed in an add page, wherein the Widget packet list displays names of a plurality of Widget packets, and one Widget packet includes widgets of service modules with the same service type, i.e. the service modules with the same service type are classified; the component preview area displays widgets of each service module corresponding to the Widget group, and the display content of the component preview area changes along with the change of the clicked target Widget group in the Widget group list.

In some embodiments, the add page and the Widget panel are generated by a component presentation module, and the desktop home page is generated by a system configured application management module. In the interface shown in fig. 8, the display window of the desktop application is located on the system homepage, and when the desktop application is triggered, the desktop homepage pops up and is displayed on the upper layer of the system homepage. When the Widget panel needs to be called out, the user presses the left key of the remote controller for a long time, and the Widget panel is called out and displayed in a desktop homepage. One possible display mode of the Widget panel is to pop up from the left side of the display, extrude the desktop homepage to the right as a whole, and leave a space on the left side of the desktop homepage for the Widget panel to display. At this time, the right display content of the desktop homepage disappears from the display, and is displayed in the state shown in fig. 38; if the display of the Widget panel is canceled, the desktop homepage integrally moves leftwards, and the original state is restored.

In some embodiments, the Widget panel is located in the desktop homepage, and then when the add button is triggered based on the Widget panel, the add page is provided by the Widget panel, i.e., controlled to be presented by the component presentation module. The popped added page is displayed on the upper layer of the Widget panel, which is equivalent to being displayed on the upper layer of the desktop homepage. The added page is displayed on the upper layer of the desktop homepage in a covering mode, so that the display of the added page does not influence the original display structure of the desktop homepage, namely, each business originally displayed in the desktop homepage cannot adjust the position.

In some embodiments, if the user triggers the target Widget group, such as the child private area, it may be determined that the service modules of the same service type corresponding to the target Widget group (child private area) may be "child mode", "small class", "study report", etc., and then widgets of each service module corresponding to the target Widget group, such as "child mode" Widget, "small class" Widget, "study report" Widget, etc., need to be displayed in the component preview area. Each service Widget may have a different component size, so that a user may select and add a Widget with a target component size to the Widget panel.

In some embodiments, when the add page is displayed, the service component management module obtains, from the component management module, component information and service type of each service module of the corresponding preregistered widgets based on each service ID, where the component information refers to information generated when the service module provided by the desktop application registers the widgets, the component information includes component data and Widget panel information, the component data refers to data required to be displayed on the Widget panel by the service module represented by the service ID, and the Widget panel information refers to interface layout information displayed by the widgets.

And grouping a plurality of service modules based on the service types, calling the module display module to generate a Widget grouping list for the service modules with the same service types, and displaying Widgets corresponding to each service module with the same service types in a module preview area. When triggering any target Widget group in the Widget group list, the user displays each Widget corresponding to the target Widget group in the component preview area; and when another target Widget group is triggered by switching, each Widget corresponding to the newly triggered target Widget group is displayed in the component preview area by switching.

In some embodiments, if a user has added at least one Widget to a Widget panel under a certain packet, when the added page is displayed, the service component management module counts the service types of the service modules added with the widgets to the Widget panel before, and calculates the number of the service modules added with the widgets to the Widget panel under the same service type based on the added service types. When the Widget grouping list is displayed, the added number is displayed on the display item where the Widget grouping corresponding to the service type is located, for example, the added number of widgets under the "media center" Widget grouping in fig. 43 is 1.

And when the user needs to display the widgets of each service module under the child special area group in the Widget panel, directly triggering the target widgets in the component preview area, and if the 'child mode' Widget is triggered, adding the 'child mode' Widget into the Widget panel.

At this time, in order to implement the addition of widgets of each service module under the target Widget group in the Widget panel, the triggered target Widget determines the target service ID, and invokes the target service component management module corresponding to the target service ID to store the component information of the target Widget into the component management module, so as to facilitate the subsequent component display.

FIG. 44 is another schematic diagram of adding pages in some embodiments of the application. Referring to fig. 44, when the user triggers the target Widget group in the add page to be "application", it may be determined that the service modules corresponding to the target Widget group (application specific area) are all services of application types, which may be "cloud audiovisual small television", "CIBN cool cat", "cloud audiovisual aurora", "guarantor" or the like. Then, the widgets of the fixed widgets of the target Widget group and the widgets of each service module corresponding to the target Widget group need to be displayed in the component preview area, for example, the fixed widgets are 'my application (1 x 1)' widgets, 'my application (2 x 2)' widgets; the widgets corresponding to the target Widget group can be a 'cloud audiovisual small television' Widget, a 'CIBN cool cat' Widget, a 'cloud audiovisual aurora' Widget, a 'Galaxy kiwi' Widget and the like.

The fixed widgets of the target Widget group (such as an application group) comprise different component sizes, the widgets of the different component sizes execute different triggering processes, for example, if the component size is 1x1, when the corresponding application group Widget is triggered, the user interface jumps to a my application page, the my application page displays various applications of the same application type, and the applications are displayed in a menu item form and are not displayed in a Widget form any more; if the component size is 2x1 or 2x2, when the corresponding "application" grouped widgets are triggered, a classification menu of "my application" is displayed at the upper layer of the current Widget panel, and each application which is installed in the system and is the same application type is displayed in the classification menu of "my application", and is not displayed in the form of the widgets any more.

In some embodiments, if the user wants to add the Widget packet corresponding to the same service type to the Widget panel, so as to view each service module (such as all applications) installed in the system through the Widget panel at the same time, the user may click on a fixed Widget of the target Widget packet in the component preview area, such as "my application (2 x 1)"; if the user wants to add the widgets of a certain service module to the Widget panel, so as to directly start a certain service module based on the Widget panel, the widgets of each service module in the component preview area, such as a 'cloud audiovisual small television' Widget, a 'CIBN cool cat' Widget, a 'cloud audiovisual aurora' Widget, a 'Galaxy kiwi' Widget, and the like, can be clicked.

Therefore, when the desktop assembly is displayed based on the desktop assembly frame, the display device provided by the application can customize the width and height, layout, style, click jump, multi-level expansion menu and the like of the assembly according to the service requirements of the user, and the display effect of the Widget panel is better, and the user experience is good.

In some embodiments, when the user triggers the target widgets corresponding to the target Widget group based on the Widget panel, the user may pop out the secondary classification menu in the current Widget panel to display all the service modules corresponding to the service types belonging to the target Widget group. To this end, the controller is further configured to perform the steps of:

and 9D1, when triggering the target Widget corresponding to the target Widget group, receiving a triggering operation of the target Widget corresponding to the target service module in the Widget panel, and if the component size of the target Widget meets the preset size, calling the target service component management module to acquire menu item information corresponding to each service module under the target Widget group from the component management module, and sending the menu item information to the component display module.

Step 92D, calling a component display module to generate a service menu based on the menu item information corresponding to each service module, displaying the service menu in the Widget panel, and displaying the service menu item corresponding to each service module under the target Widget group in the service menu.

When a user needs to trigger a target Widget corresponding to the target Widget group, judging whether the component size of the target Widget in the user trigger Widget panel meets a preset size, wherein the preset size is the component size of non-1 x 1. If the component size of the target Widget is 1x1, the preset size is not satisfied, and thus, the user interface jumps to the main page of the target Widget packet. For example, when triggering a target Widget corresponding to an "application", if the component size of the Widget is 1x1, the user interface jumps to my application page, where the my application page displays applications of the same application type, and the applications are displayed in the form of menu items and are not displayed in the form of widgets.

If the component size of the target Widget is 2x1 or 2x2, the preset size is satisfied, so that a classification menu corresponding to the target Widget group, namely a service menu, can be popped out from the Widget panel. At this time, the target service component management module corresponding to each service module in the target Widget packet is called, menu item information corresponding to each service module in the corresponding target Widget packet is obtained from the component management module, and the menu item information is sent to the component display module.

And when each service menu item under the classification of the target service module is displayed, generating a service menu by the component display module based on menu item information corresponding to each service module. The service menu is a two-level menu corresponding to each service module under the target Widget group, and the mode of generating the service menu can refer to the mode of generating the Widget panel based on the component information of each service module provided by the desktop application in the foregoing embodiment, which is not described herein.

For example, if the component size of the triggered "application" packet Widget is 2x1 or 2x2, a classification menu of "my application" is presented at the upper layer of the current Widget panel, and each application which is installed by the system and is the same application type is presented in the classification menu of "my application", and the application is presented in the form of menu item.

FIG. 45 is a schematic diagram of a service menu in some embodiments of the application. Referring to fig. 39 and 45, if the user triggers a "my application (2 x 1)" Widget corresponding to a target Widget group (my application) based on the Widget panel, a service menu is popped up in the current Widget panel, and menu items of all applications under the category of "my application" are displayed in the service menu, such as a "cloud audiovisual small television" menu item, a "CIBN cool cat" menu item, a "cloud audiovisual aurora" menu item, a "Galaxy kiwi" menu item, and the like. And the user triggers any menu item to directly start the corresponding application.

FIG. 46 is another schematic diagram of a service menu in some embodiments of the application. Referring to fig. 39 and 46, if the user triggers an "AI Camera" Widget corresponding to a target Widget group (AI Camera) based on the Widget panel, a service menu is popped up in the current Widget panel, and menu items of all applications under the category of "AI Camera" are displayed in the service menu, such as a "magic mirror" menu item, a "video call" menu item, an "AI fitness" menu item, a "small aggregation at home" menu item, and the like. And the user can directly start the corresponding service module by triggering any menu item, and switch and display the corresponding service homepage.

In some embodiments, the Widget panel is located in the desktop homepage, and then a service menu is popped up when the target Widget packet is triggered based on the Widget panel and displayed on the upper layer of the Widget panel, wherein the service menu is provided by the Widget panel, i.e. controlled and displayed by the component display module. The service menu is displayed on the upper layer of the Widget panel in a floating layer mode, so that the display of the service menu does not influence the original display structures of the Widget panel and the desktop homepage, namely, the positions of all the services displayed in the Widget panel and the desktop homepage are not adjusted.

In some embodiments, referring again to fig. 39, an edit button and an alignment button are also displayed in the Widget panel, and when the edit button is triggered, any Widget displayed in the Widget panel can be modified, such as modifying an attribute; and triggering an alignment button to align and arrange all widgets displayed in the Widget panel.

In some embodiments, in the process of displaying the Widget panel, no matter whether the target service module generates data change in any mode described above, when the Widget panel is required to refresh the interface display content, the change data of the target service module is returned, or when the target service module actively refreshes the data, the change data is sent to the data center module, and after the data center module receives and simply processes the change data, the change data is distributed to the corresponding target service component management module according to the target service ID. And after receiving the data, the target service component management module distributes the data to the corresponding widgets according to the target service ID. And after the component display module receives the data, displaying the change data on the target Widget to update the display information of the Widget panel.

Therefore, when the desktop assembly is displayed based on the desktop assembly frame, the display equipment provided by the application can classify each service module provided by the desktop application according to different types, and each service under the same classification belongs to the same type. Thus, a vast array of classifications can be expanded laterally indefinitely, each of which manages its own components.

FIG. 37 is a flow chart of a method of component display in some embodiments of the application. Referring to fig. 37, an embodiment of the present application provides a component display method, the method including:

S1B, receiving starting operation of a desktop application, acquiring service data of each service module provided by the desktop application, and displaying a desktop homepage in the user interface based on the service data of each service module;

S2B, when a Widget panel is displayed, a service component management module is called to acquire component information of a service module corresponding to each service ID from the component management module and send the component information to a component display module, wherein the component information is information generated when the service module provided by a desktop application registers the Widget, the component information comprises component data and Widget panel information, the component data is data which is required to be displayed on the Widget panel by the service module characterized by the service ID, and the Widget panel information is interface layout information displayed by the Widget;

S3B, calling the component display module to generate a Widget panel based on the component data and the Widget panel information corresponding to each service ID, displaying the Widget panel in a desktop homepage, wherein a plurality of widgets for providing starting inlets of each service module are displayed in the Widget panel.

The component display method and the display device provided by the embodiment of the invention display desktop homepages based on the service data of each service module when the desktop application is started. When a Widget panel is displayed in a desktop homepage, a service component management module is called to acquire component information of a service module corresponding to each service ID from a component management module and send the component information to a component display module, the component display module is called to generate the Widget panel based on the component data corresponding to each service ID and the Widget panel information, the Widget panel is displayed in the desktop homepage, and a plurality of widgets for providing starting inlets of the service modules are displayed in the Widget panel. Therefore, when the method and the display device are used for carrying out component display based on the desktop component framework, the method and the display device are not limited by a system, component information is split into component data and Widget panel information, and the layout, the style and the like of each Widget presented in the Widget panel can be edited in a self-defined manner, so that the Widget panel with various effects is provided for users.

In some embodiments, when the input signal source of the display device changes, the Widget reminder is displayed at the upper layer of the currently displayed interface. For example, when detecting that the signal input of one or more HDMI interfaces changes from none to none, determining that the input signal source changes, and displaying a Widget reminder at the upper layer of the currently displayed interface. And prompting the user that the signal source is changed through the Widget prompt, and/or displaying a Widget panel or a signal source selection interface through operation of the indication display device when the Widget prompt is displayed.

In some embodiments, the control for loading the Widget alert may not acquire focus. In these embodiments, when the Widget reminder is displayed, the focus may remain unchanged at the position after the last operation by the user.

In other embodiments, the control in which the Widget alert is located may acquire focus. In these embodiments, when the Widget reminder is displayed, the Widget reminder control preemptively takes the focus, i.e., the focus automatically falls on the Widget reminder control.

In some embodiments, after the display device is turned on, a page corresponding to a home page of the television system or other signal sources is displayed, where the home page of the television system may be a home page of a preset video on demand program, such as an application home page of a "gather-look" application, and the page corresponding to the other signal sources may be a live television home page or a page corresponding to an HDMI interface. It should be understood that when displaying a home page of a television system, the input signal source of the display device is a vod program, and other signal sources such as a live television interface, an HDMI interface, etc. may not have signal input. When the live television home page is displayed, other signal sources such as a video on demand program interface, an HDMI interface and the like can have no signal input.

When a homepage of a television system or pages corresponding to other signal sources are displayed, if the input signal sources are detected to change, if one signal source is added, one signal source is reduced or the signal sources are switched, a Widget reminder is displayed on the upper layer of the homepage of the system. When the Widget reminder is displayed, a user can instruct the display device to display the first-level item content corresponding to the Widget panel or the 'signal source' Widget control by pressing the left key for a long time.

FIG. 47 is a user interface, in particular a user interface displayed upon detecting a change in an input signal source when displaying a home page of the television system as shown in FIG. 7, in accordance with some exemplary embodiments of the present application. As shown in fig. 47, a Widget reminding control is displayed in the upper left corner area of the upper layer of the system homepage, and through the Widget reminding control, a user can know that the signal source change occurs currently. In addition, in the example shown in fig. 47, the Widget reminder control may not acquire focus.

For example, when displaying the user interface including the Widget alert control shown in fig. 47, if the user presses the left key for a long time, a Widget panel may be displayed, as shown in fig. 640, which is not described herein.

For another example, when the user interface including the Widget reminder control shown in fig. 47 is displayed, if the user presses the left key for a long time, the primary item content corresponding to the "signal source" control is displayed, as shown in fig. 18, which is not repeated herein.

In some embodiments, the Widget alert control may not acquire focus at the time of display when the desktop home page/non-full screen page is displayed. The display equipment receives an instruction of a user for moving the focus, when the focus moves to the left/right boundary of the display interface, whether a Widget reminding control is displayed currently is determined, if yes, a secondary panel corresponding to the signal source control is displayed in the control panel area, and signal source information is displayed; if not, the control panel area displays a default Widget panel. Wherein, the non-full screen playing page refers to other pages outside the full screen playing page.

In some embodiments, the default Widget panel is a main panel, and at least part of the components on the main panel correspond to secondary panels to display detailed information corresponding to the components. The Widget control panel is provided with a signal source component, and the secondary panel corresponding to the signal source control is displayed in the Widget control panel area after the signal source component is selected by a user.

In some embodiments, when the display device plays the video program in full screen, if the input signal source is detected to change, the widgets reminder is displayed at the upper layer of the video program screen while continuing to play the video program in full screen. At this time, the user may display the Widget panel or the signal source list by operating the indication display device.

In some embodiments, the Widget alert control displayed when a video program is played full screen may acquire focus.

In some embodiments, the Widget alert control may be displayed on the video program screen while the focus object is displayed on the Widget alert control. Or, when the display duration of the Widget reminding control on the video program picture reaches the first preset duration, displaying the focus object on the Widget reminding control.

In some embodiments, when focus is on the Widget alert control, the user may control the display of the Widget panel or signal source list through a confirmation operation.

In some embodiments, if a confirmation operation to the Widget reminder control is not received within a second preset time period after the Widget reminder control is displayed, the Widget reminder control is revoked.

In some embodiments, when the Widget reminding control is displayed on the video program screen, the user may deactivate the Widget reminding control by operating a return button or other designated buttons on the remote control.

In some embodiments, in a full screen play page, the Widget alert control may not acquire focus while displayed. The user can trigger the display device to set the focus on the Widget reminding control through a preset key, or the displayed Widget reminding control is configured to appear by default to obtain the focus at the moment, and the user can move the focus through the direction key to enable the focus to be located on the Widget reminding control or a full-screen playing window.

When the Widget reminding control is displayed on the full-screen playing page, responding to a confirmation instruction corresponding to a confirmation key on the remote control device, judging the current focus position/who obtains the focus currently, and displaying a Widget panel area or a secondary panel corresponding to the signal source control if the Widget reminding control obtains the focus; and if the full-screen playing window obtains the focus, controlling to pause the playing of the video.

In some embodiments, the Widget reminder control displayed on the full-screen play window is cancelled while the play of the video is paused.

In some embodiments, the Widget alert control obtains a focus, displays a Widget panel area or displays a secondary panel corresponding to the signal source control. The position of the full-screen playing window is moved, and a Widget panel area or a secondary panel corresponding to the signal source control is displayed in the vacated area. Or directly above the full-screen playing window, and displaying a Widget panel area or a secondary panel corresponding to the signal source control in a floating layer mode.

Fig. 48 is a user interface displayed upon detecting a change in signal source while a video program is being played full screen. As shown in fig. 48, in the user interface, a video program screen is displayed in full screen, and a Widget reminder control is displayed in the upper left corner area of the upper layer of the video program screen. At this time, the Widget reminding control does not display a focus object, i.e. does not acquire focus.

Fig. 49 is a user interface displayed after the display duration of the Widget reminder control in fig. 48 reaches a first preset duration (e.g., 3 s). The main difference from the interface shown in fig. 48 is that in the user interface shown in fig. 49, a focus object is displayed on the Widget alert control. At this time, the user may instruct to display the Widget panel or the signal source list by operating a confirm key on the remote controller.

Fig. 50 is an exemplary view showing a user interface for receiving a confirmation operation input by a user when the user interface shown in fig. 49 is displayed. As shown in fig. 50, while continuing to play the video program, a widgets panel or a signal source list is displayed at the upper layer of the video program screen.

In the example shown in fig. 48-23, playing of the video program may also be stopped if a confirmation operation entered by the user is received.

In some embodiments, a user may remove the Widget controls on the Widget panel by operating, and move the positions of the Widget controls on the Widget panel to change the layout among the Widget controls in the Widget panel.

Next, taking the Widget panel shown in fig. 7 as an example, user operation and interface change in the process of moving the Widget control position and deleting the Widget control are introduced.

In some embodiments, when the focus stays on any Widget control, the user may activate the editing state of the Widget panel by pressing the confirm key on the remote controller for a long time, and when the Widget panel is in the editing state, the user may move or delete the Widget control thereon.

In some embodiments, the Widget panel in the edit state is referred to as a Widget editing panel.

Fig. 51 is a user interface displaying a Widget panel in which focus is left on a "set" control. When the user presses the confirm key on the remote controller for a long time, the Widget panel enters an editing state, and further the Widget editing panel is displayed, as shown in fig. 52.

In some embodiments, the Widget panel has a control thereon for activating the editing state of the Widget panel, and the user can activate the editing state of the Widget panel by operating the control.

In some embodiments, after a user presses a certain Widget control for a long time to activate the editing state of the Widget panel, the Widget control is picked up according to the default in which the focus is located. For example, as shown in fig. 51, focus stays on the "set" control, and when the user presses the confirm key on the remote control for a long time, the Widget panel editing state is activated while the "set" control is automatically picked up (focus is placed on the "set" control). The setting operation is aroused when the user is in the Widget control, which means that the user performs editing operation on the Widget control, so that the Widget control is picked up by default, and compared with the method of picking up the preset control, the setting operation is simplified.

In some embodiments, the user may release the pick up of the "set" control by returning an instruction, then move the focus through the directional key, and pick up the target control by pressing the ok key when the focus is located at the target control.

In some embodiments, activation of the Widget panel may be canceled by a continuous instruction after the "set" control is automatically picked up.

In some embodiments, upon automatically picking up the "set" control, the location of the "set" control is determined, and the directional control is displayed for sides that are not adjacent to the boundary to indicate an inputtable directional instruction that does not delete the control. Displaying the delete control to the side adjacent to the boundary to characterize that a directional instruction entering the direction will delete the control.

In some embodiments, the automatic pick-up "setting" control may be located at a middle position, so that the four directions centered around the control display direction control, after receiving an input direction instruction for moving right, the control position is moved, the control pointed to the position (such as the "Router" control) may be covered, that is, the setting control is covered and displayed above the "Router" control, and the positions may also be exchanged, where the controller determines whether four sides of the "setting" control are adjacent to a panel boundary, and exemplarily, as shown in fig. 54, the right side of the setting control is adjacent to a right boundary of a display panel, and the other sides are not adjacent to the panel boundary, so that the other three sides respectively display the directional arrow control, and the right side displays the deletion hint control. By deleting the display of the control, the user may be prompted to continue pressing the side direction key (illustratively, the right side direction key) on the remote control device at this time, without moving the "set" control to the next row, but rather with a delete operation. On the one hand, complicated operation of entering the whole Widget panel into a control deleting/installing mode in control management logic in the prior art is avoided, and the deleted control can prompt a user to continuously input an operation executed by a direction key instruction, after the control is set to be moved to a nearby boundary position, before a further key instruction moving to the right is not received, obvious reminding is carried out, and the influence caused by operation habit that the user moves a focus to the next row or carries out active effect reminding cannot move after receiving a focus moving instruction in other equipment is relieved.

In some embodiments, whether the edge of the control is adjacent to the boundary of the panel may be determined by determining whether the control boundary and the Widget boundary are preset values, where the preset values characterize the distance between the control adjacent to the boundary and the Widget panel boundary, and the distance value may be determined according to the control display position and the Widget panel display position in the design process. In another mode, a boundary control bit is designated, and when the position of the control and the boundary control bit overlap, a boundary corresponding to the adjacent boundary control bit of the control is determined. In still another manner, by determining the coordinates of the control and the preset coordinates, for example, x=a is the boundary of the control position corresponding to the left boundary, and x=b is the boundary of the control position corresponding to the right boundary. When the x coordinates of the two vertical sides of the control are A, B respectively, if a is not equal to A and B is equal to B, determining that the control is adjacent to the right boundary of the panel, displaying a direction arrow on the left side, and displaying a deletion control on the right side. In some cases, the width of the control is 3, when a is equal to a and B is equal to B, the control is determined to be adjacent to the left boundary and the right boundary of the panel, the deletion control is displayed on the left side, the deletion control is also displayed on the right side, and the user triggers the control to delete through the left arrow and the right arrow.

In some embodiments, the overlay display may avoid repeated movement of the control, illustratively, a user selecting a move right "setup" control, which may overlay a first target control, such as a "Router" control, which may overlay a second target control, such as a "multi-screen interactive" control, if the user selects move down, the "Router" control resumes display and position avoidance, and if the user now enters an edit-complete operation, the "setup" control and the "multi-screen interactive" control are interchanged by updating coordinates, while the "Router" control is unaffected.

Illustratively, when displaying the user interface shown in fig. 640, the user may cause the controls laid out on the lower portion of the Widget panel to be displayed in the view display by moving the focus downward and sliding the Widget panel downward. Fig. 53 is a user interface displayed after the user slides the Widget panel down to the bottom, and in fig. 53, an edit control and an add control are displayed below the current functionality control. When the user operates the editing control, the Widget panel enters an editing state, and the Widget editing panel can be displayed; when the user operates the add control, the user will jump to the Widget store interface.

Referring to fig. 52, the Widget control on the Widget panel is reserved on the Widget editing panel, and a location frame is further displayed. The position frame is composed of a plurality of grids, and one grid is the minimum area unit occupied by the Widget control and is the minimum moving distance when the position of the Widget control is moved. One Widget control may be laid out on one or more grids. It should be appreciated that the larger the size of the Widget control, the greater the number of grids it occupies. In fig. 52, the "setting" control is in a pickup state, and at this time, an operation indication identifier is further displayed on the "setting" control, where the operation indication identifier indicates four moving directions, that is, up, down, left, and right, respectively, which indicates that the user can move the "setting" control up, down, left, and right.

When the Widget editing panel is displayed, a user can pick up the Widget control to be moved through operation, and can also move the picked up Widget control up, down, left or right, delete the Widget control by moving the Widget control out of the view display area, and put down the picked up Widget control. For example, when the focus stays on a certain Widget control, the user may operate a confirm key on the remote controller to pick up the Widget control, then, move the position of the Widget control by operating a direction key on the remote controller, and if the Widget control is moved out of the view display area, delete the Widget control; the user can put down the picked-up Widget control by operating a confirmation key on the remote controller.

Referring to fig. 52, in a state where the "set" control is picked up, if the user presses the right key on the remote controller, the "set" control will move rightward, wherein the "set" control moves rightward by one grid every time the right key is pressed. Of course, the user may also press the left, up, or down key on the remote control to move the "set" control to the left, up, and down.

When the display device receives a user operation to move the "set" control to the right, the user interface shown in fig. 54 is displayed. It can be seen that in relation to fig. 52, in fig. 54 the "set" control is moved one grid to the right, overlapping and displayed on top of the "Rouder" control, the operational indication identifier displayed on the "set" control indicates three directions of movement, up, down and left, respectively, indicating that the user can move the "set" control up, down and left. It is noted that the grid where the "set" control is currently located is located at the edge of the view display area, so that a deletion reminder is displayed on the right side of the "set" control to remind the user that the "set" control can be moved out of the view display area through right-key operation to delete the control.

When the user interface shown in fig. 54 is displayed, if the user presses the right key on the remote controller, a deletion confirmation box as shown in fig. 55 is displayed, and the deletion confirmation box includes a "determine deletion" control and a "cancel" control. If the user selects the "determine delete" control, that is, instructs the display device to delete the "set" control, the user interface shown in fig. 56 may be displayed at this time; if the user selects "cancel," return to the user interface shown in FIG. 54. In the user interface shown in FIG. 56, the "set" control disappears, the "Rouder" control appears, and focus remains on the "Rouder" control.

In some embodiments, if a gap is created around a Widget control that is adapted to its size, the Widget control is extended to the gap to complement the gap. And when the width of the Widget control is the same as the width of the gaps around the Widget control or the height of the Widget control is the same as the height of the gaps around the Widget control, the Widget control is considered to be matched with the sizes of the gaps around the Widget control. The slots refer to grids that are not occupied by widgets controls.

As shown in fig. 57, the change in vacancies is shown rather than indicating that the three states exist at the same physical interface. When a 1 x 1 space is created on the right side of the Widget control, the Widget control may extend one grid to the right, changing from display state 11 to display state 12. When the Widget control underside creates a 1 x 1 vacancy, the Widget control may extend downward one grid, changing from display state 11 to display state 13. It should be understood that the display state 11 is a state when the Widget control occupies 1×1 grids, the display state 12 is a state when the Widget control occupies 1×2 grids, and the display state 13 is a state when the Widget control occupies 2×1 grids.

As shown in fig. 58, the change in vacancies is shown rather than indicating that the three states exist at the same physical interface. When a 1 x 1 vacancy is created to the right of the Widget control in fig. 58, the Widget control may extend one grid to the right, changing from display state 21 to display state 22. When the Widget control has 1×2 slots on its underside, the Widget control may extend downward by one grid as a whole, changing from display state 21 to display state 23. It should be understood that the display state 21 is a state when the Widget control occupies 1×2 grids, the display state 22 is a state when the Widget control occupies 1×3 grids, and the display state 13 is a state when the Widget control occupies 2×2 grids.

As shown in fig. 59, the change in vacancies is shown rather than indicating that the three states exist at the same physical interface. When a 2 x 1 vacancy is created to the right of the Widget control in fig. 59, the Widget control may extend one grid to the right, thereby changing from the display state 31 to the display state 32. When the Widget control has 1×2 slots on its underside, the Widget control may extend downward by one grid as a whole, changing from display state 31 to display state 33. It should be understood that the display state 31 is a state when the Widget control occupies 2×2 grids, the display state 32 is a state when the Widget control occupies 2×3 grids, and the display state 33 is a state when the Widget control occupies 3×2 grids.

In some embodiments, the height of the Widget control with the highest height is taken as the height of the row where the Widget control is located. In addition, when there is a vacancy row between rows, the lower row is translated upward as a whole to complement the vacancy row. The widgets controls in each row are aligned to the left.

In some embodiments, after editing is complete, the location of the void is determined, then it is determined whether there is a control located to the left of it, if so, it is determined whether the height of the left control is the same as the height of the void, if so, the display area of the left control is enlarged to cover the void, if different, it is determined whether there is a control located to the right of it, if so, it is determined whether the height of the right control is the same as the height of the void, if so, the display area of the right control is enlarged to cover the void, if different, the void is not filled, or judgment logic of other dimensions is executed.

In some embodiments, after editing is complete, the location of the void is determined, then it is determined whether there is a control located on its upper side, if so, it is determined whether the width of the left control is the same as the width of the void, if so, the display area of the left control is enlarged to cover the void, if different, it is determined whether there is a control located on its lower side, if so, it is determined whether the width of the lower control is the same as the width of the void, if so, the display area of the lower control is enlarged to cover the void, if different, the void is not filled, or a judgment logic of other dimensions is executed.

In some embodiments, the determinations of the left and right directions and the determinations of the upper and lower sides may be combined in any order.

In some embodiments, the widgets in each row are arranged in a top-to-bottom followed by left-to-right order.

While displaying the user interface shown in FIG. 54, the user may operate the ok key on the remote control to drop the "set" control. According to the rules described above, when the user operates the ok key on the remote control to drop the "set" control, a user interface as shown in fig. 60 will be displayed. In fig. 60, the left side of the "set" control creates a grid of vacancies. The "Rouder" control moves to the next row and aligns to the left, with two empty grids on the left side. While displaying the diagram 60, the user may operate a back key on the remote control to exit the edit state. According to the above rule, when the user operates the return key on the remote controller, the user interface shown in fig. 61 will be displayed. In FIG. 61, the "set" control extends one grid to the left, complementing the space to the left; the "Rouder" control extends 2 grids to the right, complementing the space to the right.

While displaying the user interface shown in fig. 56, the user may operate a back key on the remote control to indicate exiting the edit status, displaying the user interface shown in fig. 62. In FIG. 62, the "Rouder" control icon extends one grid to the left to supplement the room created by deleting the "set" control.

It should be appreciated that while displaying the user interface shown in fig. 56, the user may also continue to move the focus position to select a control to move or delete, and pick up the selected control by a confirmation operation, and move the picked up control by operating the direction key. For example, the user may pick up the "Rouder" control by a confirmation operation. The user may then move the "Rouder" control one grid to the left by a left key operation. Alternatively, the user may remove the "Rouder" control from the view display area by right-key operation, thereby removing the "Rouder" control from the Widget panel.

In some embodiments, for a dead Widget control, when the Widget panel is displayed, a dead mark is displayed on a dead Widget control icon, so that a user is reminded that the Widget control has been dead through the dead mark. It should be appreciated that there are various reasons for the Widget control to fail, for example, if an application in the system is deleted, the Widget control corresponding to the application will fail.

As can be seen from fig. 63, the "find" control icon on the Widget panel displays a failure identifier "? "means that the" find "control is a dead Widget control.

In some embodiments, when the Widget panel is displayed, if the user picks up the failed Widget control by operating, a Widget failure prompt box may be displayed, where the Widget failure prompt box includes a control and a cancel control for deleting the failed Widget, and the user may operate the delete control to delete the picked up failed Widget control, or operate the cancel control, and return to the interface before the Widget failure prompt box is displayed.

In addition, a plurality of recommended Widget controls can be displayed in the Widget invalidation prompt box and used for replacing the picked up invalidation Widget controls. The user can select one recommended Widget control in the Widget invalidation prompt box to replace the invalidation Widget control picked up by the user with the selected recommended Widget control.

It should be noted that, the recommended Widget control is selected according to the picked up ineffective Widget control, and the recommended Widget control and the picked up ineffective Widget control have the same size.

For example, when the user interface shown in fig. 63 is displayed, the user first moves the focus to the "find" control, and then operates the confirm key on the remote controller to pick up the "find" control, and since the "find" control is a dead Widget control, when the display device receives a confirm operation on the "find" control, a Widget failure prompt box is displayed, as shown in fig. 64. Referring to fig. 64, in the Widget invalidation prompt box, a "delete invalidation Widget" control, a "cancel" control and a plurality of recommended widgets are displayed. When the Widget invalidation prompt box is displayed, if a user operates the 'delete invalidation Widget' control, deleting the 'discovery' control from the Widget panel and returning to the user interface containing the latest Widget panel. If the user operates the "cancel" control while the Widget invalidation prompt is displayed, the user interface shown at 44 will be returned. When the Widget invalidation prompt box is displayed, if a user selects a certain recommended Widget, the display device replaces a found control in the Widget panel with the recommended Widget selected by the user.

In some embodiments, before the Widget panel is displayed, detecting whether each Widget control is invalid, and if the invalid Widget control exists, deleting the invalid Widget control from the Widget panel data, so that the invalid Widget control is not displayed in the displayed Widget panel.

In some embodiments, when the display device is operating in the educational mode, the user may operate the display device through key inputs, touch inputs, and/or voice inputs.

In some embodiments, the display device displays the educational mode system home page after powering on in the educational mode.

In some embodiments, the educational mode system homepage may be displayed in the manner described in the following embodiments.

In some embodiments, a system homepage displayed after the display device is started is designed in a Widget mode, that is, the system homepage includes Widget controls arranged according to a preset sequence, and when a user clicks any one Widget control, the user interface jumps to a primary page corresponding to the Widget control or a main interface of a Widget program.

In some embodiments, the view display area used to display the Widget control may occupy the entire screen, or may occupy a portion of the screen, such as the left area of the screen.

In some embodiments, the user may set the local tile or system-provided background theme to the background of the system home page.

In one implementation, the display device may be a conventional display screen fixed setting, and the user may only view in a manner where the landscape screen width is greater than the portrait screen width. In some embodiments, the display screen of the display device is rotatable, the display device is provided with a supporting portion, and the display portion is connected with the supporting portion, the supporting portion can be placed on a platform wall surface or the like to support or fix the whole display device, the display portion can rotate relative to the supporting portion, a user can watch in a mode that the transverse screen width is larger than the vertical screen width in a transverse screen state, and the user can watch in a mode that the transverse screen width is smaller than the vertical screen width in a vertical screen state.

In some embodiments, the rotation angle of the display part of the display device is in the same quadrant, and the display part is changed from the horizontal screen state to the vertical screen state, and returns along the original rotation path when the vertical screen state is changed to the horizontal screen state.

In some embodiments, when the display device is started, if the current display is detected to be in a landscape state, a landscape system homepage is displayed. FIG. 65 is a user interface showing a cross-screen system home page designed in a Widget manner, in accordance with some embodiments of the application. As shown in fig. 65, the user interface includes a plurality of widgets controls such as "time", "setting", "calendar", "weather", "gathering, and" gathering. Notably, the widgets controls of the portrait application can be displayed on the landscape system home page.

In one embodiment, while the display is in the landscape state, the user may control the stationary component to rotate via key input, touch input, and/or voice input to cause the display to transition from the current landscape state to the portrait state and switch from the displayed landscape system home page to the portrait system home page.

In some embodiments, when displaying the home page of the landscape screen system, if the user clicks on the Widget control that can display the portrait screen application on the home page of the landscape screen system, a rotation confirmation interface is displayed, where the rotation confirmation interface includes a "determine rotation" control and a "cancel" control. When the user clicks the 'confirm rotation' control, the controller controls the display to rotate, and the vertical screen system homepage is displayed on the display. For example, when a cross-screen status system homepage as shown in fig. 65 is displayed, if the user clicks the "small video" control, a rotation confirmation interface as shown in fig. 66 is displayed. When the user clicks the 'confirm rotation' control in the rotation confirmation interface, the display rotates to a vertical screen state, and the display displays a homepage of the vertical screen system.

FIG. 67 is a user interface, which is a home page of a vertical screen system designed in a Widget manner, in accordance with some embodiments of the application. As shown in fig. 67, the user interface includes a plurality of widgets controls such as "time", "setting", "calendar", "weather", "polite", and the like. Notably, the widgets controls for the landscape application can be displayed on the portrait system home page.

It should be noted that, the widgets displayed in the home page of the horizontal screen system and the home page of the vertical screen system may be identical, not identical, or completely different.

In some embodiments, when displaying the home page of the horizontal screen system or the home page of the vertical screen system, the user may delete the Widget control on the home page or move the position of the Widget control in the home page through touch input to change the layout of the Widget control in the home page.

In some embodiments, in response to an operation to invoke the Widget panel with an input, a current rotation state of the display device is determined, and when the display device is in a landscape state, the desktop homepage is controlled to move, and the Widget panel is displayed in an vacated position. And when the display equipment is in a vertical screen state, the display of the vertical screen homepage is canceled, and the Widget panel is displayed in a full screen mode.

Next, taking a home page of a horizontal screen system as an example, a touch operation and a user interface change process when deleting the Widget control on the home page or moving the position of the Widget control in the home page are described.

In some embodiments, after the editing operation is input, the Widget panel may be displayed in situ, or the display of the desktop homepage may be canceled, and the Widget panel may be displayed in full screen.

In some embodiments, the display device is a touch-operable display device, and when displaying the home page of the flat screen system, the user may activate the page editing state by pressing any Widget control on the page for a long time. For example, as shown in fig. 68, when the user presses the "K song" control long, the page editing state is activated, displaying the system homepage in the editing state as shown in fig. 69.

In some embodiments, a control is selected and maintained in touch, the control can be dragged, after the dragging is completed, the position of the touch point is detected, when the position of the touch point after the movement is located on a first control position, whether the control position exists the existing control is determined, if yes, the existing control and the dragged control are controlled to exchange control positions, and if not, the dragged control is displayed on the first control position.

In some embodiments, if the touch point moves to the boundary of the display area, a hint is displayed as to whether to delete the dragged control.

As shown in fig. 69, the original Widget control is reserved on the system homepage in the editing state, a delete button is displayed on the upper right corner of each Widget control icon, and the user can delete the Widget control by clicking the delete button on the Widget control. As shown in fig. 69, when the user clicks the delete button on the "K song" control icon, a delete confirmation box as shown in fig. 70 is displayed, and when the "determine delete" control and the "cancel" control are displayed in the delete confirmation box, the user may click the "determine delete" control, instruct to delete the "K song" control, and click the "cancel" control to return to the user interface as shown in fig. 69.

In addition, as shown in fig. 69, a position frame is displayed in the system homepage in the editing state, where the position frame is composed of a plurality of grids, and one grid is the minimum area unit occupied by the Widget control, and is also the minimum moving distance when the Widget control is moved. One Widget control may be laid out on one or more grids. When the system homepage is in an editing state, the user can also move the position of any Widget control through a drag gesture.

In addition, referring to fig. 69, a "restore" control and a "confirm" control are displayed in the system homepage in the editing state, and the user may click on the "restore" control to indicate restoration to the system homepage before editing, may click on the "confirm" control to control the editing operation to take effect, and indicates exiting the editing state and displaying the system homepage after editing.

In some embodiments, when a user drags the target Widget control from the first position to the second position and releases the hand, determining one or more selectable areas according to a grid occupied by the target Widget control in the second position, wherein each selectable area comprises at least one grid occupied by the target Widget control partially or fully, and each selectable area has the same size as the target Widget control; calculating the overlapping area of the target Widget control and each optional area, and determining the optional area generating the largest overlapping area as a target area; and placing the target Widget control on the target area.

As shown in fig. 71, when the user drags the Widget control in fig. 71 from the first position to the second position and releases the hand, the grid occupied by the Widget control includes a grid 1-6, and the selectable area 1-3 can be determined according to the grid 1-6, wherein the selectable area 1 includes a grid 1-2, the selectable area 2 includes a grid 1-4, the selectable area 3 includes a grid 5-6, and the size of each selectable area is 2×2 as the size of the Widget control. Through calculation, the overlapping areas of the Widget control and the selectable areas 1-3 are determined to be S1, S2 and S3 respectively, and the Widget control is displayed on the selectable area 3 because S3 is greater than S2 and greater than S1. The selectable regions are formed from a combination of adjacent grids.

Referring to fig. 72, if the user drags the "K song" control from home position to the position shown in fig. 72 and releases his hand by dragging the gesture according to the above rule, the user interface shown in fig. 73 will be displayed. As can be seen from fig. 73, by the user dragging, the "K song" control moves down and to the right by one grid respectively, and is individually laid out in the second row, and the "gathering" control moves down by three cells as a whole, and is laid out in the third row, a vacancy row is generated between the second row and the first row, and vacancies are generated in the second row and the third row.

While displaying the user interface shown in fig. 80, if the user clicks the "ok" control, this means that the user confirms the editing operation, and thus exits the editing state, and the user interface shown in fig. 81 is displayed. In contrast to fig. 73, in fig. 74, the empty row between the second row and the first row is complemented, and the controls in the second row and the third row are aligned to the left. When the user interface shown in fig. 73 is displayed, if the user clicks the "restore" control, this indicates that the user cancels the editing operation, and thus returns to the interface before dragging the "K song" control.

Notably, the user may also confirm or cancel the editing operation that has been entered by key entry, thereby achieving the same effect as clicking on the "ok" control or the "cancel" control. Specifically, when the user interface shown in fig. 73 is displayed, the user may press a confirm key on the remote controller to confirm the input editing operation and exit the editing state, and further the user interface is displayed. The user can press the return key on the remote controller to cancel the input editing operation, and then return to the interface before dragging the Karaoke control.

In some embodiments, controls for activating the page editing state are also displayed in the horizontal screen system homepage and the vertical screen system homepage, and the user can activate the page editing state by clicking the controls. For example, when displaying the landscape screen system home page shown in fig. 71, the user can slide the editing control into the view display area by sliding the home page upward. When the user clicks the editing control, the page editing state is activated, and then the homepage of the horizontal screen system in the editing state is displayed.

In some embodiments, the display device presents a user interface corresponding to the touch mode in response to receiving the touch input. For example, when a system homepage is displayed as in fig. 71, in response to receiving a long press operation of the "K song" control by the user, the system homepage in an edit state corresponding to the touch mode as shown in fig. 76 is displayed.

In some embodiments, the position of the moved "K song" control is detected, when there are other controls that do not completely overlap in the position, the row in which the covered control is located is determined, all the controls in the row are moved down by the height of the row in which the covered control is located, and the "K song" control is displayed in the dragged position.

Illustratively, the dragged control occupies a partial position (2 x 2) in the fourth row grid and the fifth row grid. The covered controls comprise a child drawing board control, a family message control and a family album control. The row occupied by these controls is 4 rows (third row grid, fourth row grid, fifth row grid, sixth row grid), so other controls within the row except for the "K song" control are moved down by 4 grids. The "K Song" control shows a partial position (2×2) in the fourth row grid and the fifth row grid.

In some embodiments, the control moving downward will complement to the left to be visually displayed more smoothly.

In some embodiments, the controls may be padded up in rows such that a row of blank grids does not appear.

In some embodiments, the two above-described patches may be performed sequentially, or may be performed simultaneously.

The moving K song control occupies a third row of grids and a fourth row of grids, the original other controls occupy a fifth row of grids and a lower position, and the child drawing board control and the office whiteboard control are filled leftwards.

In some embodiments, the position of the moved "K song" control is detected, and the position is interchanged when the position is completely overlapped with other controls with the same size.

Although the application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: it is still possible to modify the foregoing embodiments or to make equivalent substitutions for some or all of the technical features thereof; such modifications and substitutions do not depart from the scope of the various embodiments of the application.

Claims

A display device, comprising:

The display is configured to display a desktop homepage presenting a Widget panel, wherein a plurality of service Widget controls for providing a service module starting entrance are displayed in the Widget panel;

a controller coupled to the display, the controller configured to:

when the first service Widget control is detected to be deleted, determining and displaying an icon of a second service, wherein the size of the second service Widget control corresponding to the second service is the same as that of the first service Widget control;

receiving an input selection of an icon of the second service;

and displaying a second service Widget control of a second service corresponding to the selected icon at the first position, wherein the first position is a display position of the first service Widget control.
The display device of claim 1, the controller, in performing the determining and displaying an icon of a second service, further configured to:

acquiring a service type of a first service module corresponding to the first service Widget control and a control size of the first service Widget control;

searching a target service with the same service type based on the service type, and determining a second service corresponding to a second service Widget control with the same control size of the first service Widget control in the target service;

And displaying an icon corresponding to the second service.
The display device of claim 1, the controller, in performing the determining and displaying an icon of a second service, further configured to:

acquiring a second service corresponding to a second service Widget control with the same control size as the first service Widget control;

and displaying an icon corresponding to the second service.
The display device of claim 1, the second service being a plurality, the controller, in performing the determining and displaying an icon of the second service, being further configured to:

determining a plurality of second services and the use frequencies of the second services;

and displaying a plurality of icons corresponding to the second services according to the use frequencies of the second services, wherein the icons corresponding to the second services with high use frequencies are highlighted compared with the icons corresponding to the second services with low use frequencies.
The display device of claim 1, the second service being a plurality, the controller, in performing the determining and displaying an icon of the second service, being further configured to:

determining a plurality of second services and the service time of the second services;

And displaying a plurality of icons corresponding to the second services according to the using time of the second services, wherein the icons corresponding to the second services with small time difference between the using time and the current time are highlighted compared with the icons corresponding to the second services with large time difference between the using time and the current time.
The display device of claim 1, the second service being a plurality, the controller, in performing the determining and displaying an icon of the second service, being further configured to:

determining a plurality of second services and updating time of the second services;

and displaying a plurality of icons corresponding to the second services according to the update time of the second services, wherein the icons corresponding to the second services with small time difference between the update time and the current time are highlighted compared with the icons corresponding to the second services with large time difference between the update time and the current time.
The display device of claim 1, the controller, in performing the determining and displaying an icon of a second service, further configured to:

acquiring a target service corresponding to a second service Widget control with the same control size as the first service Widget control;

Filtering a third service deleted by the user from the Widget control in the target service to determine a second service;

and displaying an icon corresponding to the second service.
The display device of claim 1, the controller, in performing the determining and displaying an icon of a second service, further configured to:

acquiring a service type corresponding to a system page and acquiring a control size of the first service Widget control, wherein the system page is a system page in front of a display Widget panel;

searching a target service with the same service type based on the service type, and determining a second service corresponding to a second service Widget control with the same control size of the first service Widget control in the target service;

and displaying an icon corresponding to the second service.
A display device, comprising:

the display is configured to display a desktop homepage presenting a Widget panel, wherein a plurality of service Widget controls for providing a service module starting entrance are displayed in the Widget panel;

a controller coupled to the display, the controller configured to:

determining and displaying an icon of a second service when the first service Widget control is detected to be deleted, wherein the size of the second service Widget control corresponding to the second service is not larger than that of a first position, and the first position is a display position of the first service Widget control and a blank position adjacent to the display position of the first service Widget control;

Receiving an input selection of an icon of the second service;

and displaying a second service Widget control of a second service corresponding to the selected icon at the first position.
A control processing method, comprising:

when the first service Widget control is detected to be deleted, determining and displaying an icon of a second service, wherein the size of the second service Widget control corresponding to the second service is the same as that of the first service Widget control;

receiving an input selection of an icon of the second service;

and displaying a second service Widget control of a second service corresponding to the selected icon at the first position, wherein the first position is a display position of the first service Widget control.