Display device and page display method thereof

Abstract

The invention relates to display equipment and a page display method thereof, and relates to the technical field of page display. The display equipment comprises a display used for displaying pages; the controller is connected with the display and is configured to display a to-be-displayed page according to first cache data pre-cached in the display cache tree in response to a display operation on the to-be-displayed page in the target application; and acquiring real-time page data of the page to be displayed from an application server corresponding to the target application, and updating the real-time page data to the real-time cache tree, under the condition that the first cache data is the same as the real-time page data, display of the to-be-displayed page is kept; and when the first cache data is different from the real-time page data and the first interface element is invisible in the to-be-displayed page, the real-time page data is updated to the display cache tree to update the first cache data, so that a splash screen phenomenon caused by updating of the to-be-displayed page is avoided, and the influence on user experience is avoided.

Description

Technical Field

[0001] The present application relates to the field of page display, and in particular to a display device and a page display method thereof. Background Art

[0002] Currently, many application display contents in display devices obtain display data from the cloud through network requests, and then load the display data onto the page for display.

[0003] In traditional technology, after opening an application or jumping to a sub-page within the application, a loading block image or waiting effect can be displayed. After waiting for a few seconds or longer, the block image or waiting effect will be cancelled and the sub-page within the application will be displayed after the display data is successfully obtained from the cloud; the application can also display the cached data (local cache) or preset data of the last entry into the application, and request display data from the cloud at the same time. After waiting for the cloud to send the display data, the cached data is replaced with the display data, and the corresponding application sub-page is displayed.

[0004] However, the above method involves switching the display content of the same page, so the page flickers, which affects the user experience. Summary of the Invention

[0005] The present application provides a display device and a page display method thereof to reduce the inconvenience caused to users by page flickering.

[0006] In a first aspect, some embodiments provide a display device, including:

[0007] A display, used for displaying pages;

[0008] The controller, connected to the display, is configured to:

[0009] In response to a display operation on a page to be displayed in a target application, displaying the page to be displayed according to first cached data pre-cached in a display cache tree; wherein the page to be displayed includes at least one interface element; and

[0010] Obtain the real-time page data of the page to be displayed from the application server corresponding to the target application, and update the real-time page data to the real-time cache tree;

[0011] When the first cache data is identical to the real-time page data, maintaining display of the page to be displayed;

[0012] When the first cache data is different from the real-time page data and the first interface element is not visible in the page to be displayed, updating the real-time page data into the display cache tree to update the first cache data;

[0013] The first cache data is display data corresponding to the first interface element in the display cache tree.

[0014] In some embodiments, a display cache tree and a real-time cache tree are introduced, and a dual-cache data solution is adopted to store pre-cached data and real-time page data of the page to be displayed separately. The real-time page data is synchronized to the display cache tree at an appropriate time to achieve imperceptible refresh of the display page, thereby avoiding page flickering caused by frequent updates of the page to be displayed through real-time page data; that is, by comparing the consistency between the pre-cached data and the real-time page data, the first cache data will be updated according to the real-time page data only when the pre-cached data is inconsistent with the real-time page data and the first interface element in the page to be displayed is not visible. At this time, the update of the first cache data is performed when the first interface element is not visible, which will not affect the display of the page to be displayed, thereby avoiding the screen flickering phenomenon caused by the update of the page to be displayed, affecting the user experience.

[0015] In a second aspect, some embodiments further provide a page display method, including:

[0016] In response to a display operation on a page to be displayed in a target application, displaying the page to be displayed according to first cached data pre-cached in a display cache tree; wherein the page to be displayed includes at least one interface element; and

[0017] Obtain the real-time page data of the page to be displayed from the application server corresponding to the target application, and update the real-time page data to the real-time cache tree;

[0018] When the first cached data is identical to the real-time page data, maintaining display of the page to be displayed;

[0019] When the first cache data is different from the real-time page data and the first interface element is not visible in the page to be displayed, updating the real-time page data into the display cache tree to update the first cache data;

[0020] The first cache data is display data corresponding to the first interface element in the display cache tree.

[0021] In some embodiments, a display cache tree and a real-time cache tree are introduced, and a dual-cache data solution is adopted to store pre-cached data and real-time page data of the page to be displayed separately. The real-time page data is synchronized to the display cache tree at an appropriate time to achieve imperceptible refresh of the display page, thereby avoiding page flickering caused by frequent updates of the page to be displayed through real-time page data; that is, by comparing the consistency between the pre-cached data and the real-time page data, the first cache data will be updated according to the real-time page data only when the pre-cached data is inconsistent with the real-time page data and the first interface element in the page to be displayed is not visible. At this time, the update of the first cache data is performed when the first interface element is not visible, which will not affect the display of the page to be displayed, thereby avoiding the screen flickering phenomenon caused by the update of the page to be displayed, affecting the user experience.

[0022] In a third aspect, some embodiments further provide a page display device, including:

[0023] a display module configured to, in response to a display operation on a page to be displayed in a target application, display the page to be displayed according to first cached data pre-cached in a display cache tree; wherein the page to be displayed includes at least one interface element; and

[0024] The acquisition module is used to obtain the real-time page data of the page to be displayed from the application server corresponding to the target application, and update the real-time page data into the real-time cache tree;

[0025] The display module is further configured to maintain display of the page to be displayed when the first cached data is identical to the real-time page data;

[0026] an updating module, configured to update the real-time page data into the display cache tree to update the first cache data when the first cache data is different from the real-time page data and the first interface element is not visible in the page to be displayed;

[0027] The first cache data is display data corresponding to the first interface element in the display cache tree.

[0028] The page display device provided in the above embodiment introduces a display cache tree and a real-time cache tree, adopts a dual-cache data solution, stores the pre-cached data and the real-time page data of the page to be displayed separately, judges the appropriate time to synchronize the real-time page data to the display cache tree, realizes the imperceptible refresh of the display page, and avoids the page flickering phenomenon caused by frequent updates of the page to be displayed by the real-time page data; that is, by comparing the consistency between the pre-cached data and the real-time page data, the first cache data will be updated according to the real-time page data only when the pre-cached data is inconsistent with the real-time page data and the first interface element in the page to be displayed is not visible. At this time, the update of the first cache data is performed when the first interface element is not visible, which will not affect the display of the page to be displayed, avoiding the screen flickering phenomenon caused by the update of the page to be displayed, affecting the user experience.

[0029] In a fourth aspect, some embodiments further provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the following steps:

[0030] In response to a display operation on a page to be displayed in a target application, displaying the page to be displayed according to first cached data pre-cached in a display cache tree; wherein the page to be displayed includes at least one interface element; and

[0031] Obtain the real-time page data of the page to be displayed from the application server corresponding to the target application, and update the real-time page data to the real-time cache tree;

[0032] When the first cache data is identical to the real-time page data, maintaining display of the page to be displayed;

[0033] When the first cache data is different from the real-time page data and the first interface element is not visible in the page to be displayed, updating the real-time page data into the display cache tree to update the first cache data;

[0034] The first cache data is display data corresponding to the first interface element in the display cache tree.

[0035] The readable storage medium provided in the above embodiment and the computer program stored thereon, when executed by the processor, introduce a display cache tree and a real-time cache tree, adopt a dual cache data scheme, store the pre-cached data and the real-time page data of the page to be displayed separately, judge the appropriate time to synchronize the real-time page data to the display cache tree, realize the imperceptible refresh of the display page, and avoid the page flickering phenomenon caused by frequent updates of the page to be displayed by the real-time page data; that is, by comparing the consistency between the pre-cached data and the real-time page data, only when the pre-cached data and the real-time page data are inconsistent and the first interface element in the page to be displayed is not visible, will the first cache data be updated according to the real-time page data. At this time, the update of the first cache data is performed when the first interface element is not visible, which will not affect the display of the page to be displayed, avoiding the screen flickering phenomenon caused by the update of the page to be displayed, affecting the user experience.

[0036] In a fifth aspect, some embodiments further provide a computer program product, including a computer program, which, when executed by a processor, implements the following steps:

[0037] In response to a display operation on a page to be displayed in a target application, displaying the page to be displayed according to first cached data pre-cached in a display cache tree; wherein the page to be displayed includes at least one interface element; and

[0038] Obtain the real-time page data of the page to be displayed from the application server corresponding to the target application, and update the real-time page data to the real-time cache tree;

[0039] When the first cached data is identical to the real-time page data, maintaining display of the page to be displayed;

[0040] When the first cache data is different from the real-time page data and the first interface element is not visible in the page to be displayed, updating the real-time page data into the display cache tree to update the first cache data;

[0041] The first cache data is display data corresponding to the first interface element in the display cache tree.

[0042] The computer program provided in the above embodiment introduces a display cache tree and a real-time cache tree during the execution of the computer program, adopts a dual-cache data solution, stores the pre-cache data and the real-time page data of the page to be displayed separately, determines the appropriate time to synchronize the real-time page data to the display cache tree, realizes the imperceptible refresh of the display page, and avoids the page flickering phenomenon caused by frequent updates of the page to be displayed by the real-time page data; that is, by comparing the consistency between the pre-cache data and the real-time page data, the first cache data will be updated according to the real-time page data only when the pre-cache data and the real-time page data are inconsistent and the first interface element in the page to be displayed is not visible. At this time, the update of the first cache data is performed when the first interface element is not visible, which will not affect the display of the page to be displayed, avoiding the screen flickering phenomenon caused by the update of the page to be displayed, affecting the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

[0048] Figure 5 This is a schematic diagram of page switching in some embodiments of the present application;

[0049] Figure 6A A flowchart of a page display method provided in some embodiments of the present application;

[0050] Figure 6B A schematic diagram showing a cache tree is provided for some embodiments of the present application;

[0051] Figure 6C A schematic diagram showing a first type of first interface element display provided in some embodiments of the present application;

[0052] Figure 6D A schematic diagram of displaying a second first interface element provided in some embodiments of the present application;

[0053] Figure 7 A first cache data update step provided in some embodiments of the present application;

[0054] Figure 8 The first display cache tree update step provided in some embodiments of the present application;

[0055] Figure 9 A second display cache tree updating step provided in some embodiments of the present application;

[0056] Figure 10A A third display cache tree updating step provided in some embodiments of the present application;

[0057] Figure 10B A schematic diagram of a page to be displayed provided in some embodiments of the present application;

[0058] Figure 11 A flowchart of another page display method provided in some embodiments of the present application;

[0059] Figure 12 A structural block diagram of a page display device provided in some embodiments of the present application;

[0060] Figure 13 FIG. 1 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0061] The following embodiments are described in detail, with examples illustrated in the accompanying drawings. When the following description refers to the drawings, identical numbers in different figures represent identical or similar elements unless otherwise indicated. The embodiments described in the following embodiments are not intended to represent all possible implementations consistent with the present application. They are merely examples of systems and methods consistent with certain aspects of the present application, as detailed in the claims.

[0062] It should be noted that the brief descriptions of terms in this application are only for the purpose of facilitating the understanding of the embodiments described below, and are not intended to limit the embodiments of this application. Unless otherwise specified, these terms should be understood according to their ordinary and usual meanings.

[0063] In the specification and claims of this application and the accompanying drawings, the terms "first," "second," "third," etc. are used to distinguish similar or similar objects or entities, and are not necessarily intended to limit a particular order or sequence, unless otherwise noted. It should be understood that the terms used in this manner are interchangeable under appropriate circumstances.

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

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

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

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

[0068] The mobile terminal 300 can function as a control device for performing human-computer interaction between a user and the display device 200. The mobile terminal 300 can also function as a communication device for establishing a communication connection with the display device 200 and exchanging data. In some embodiments, the mobile terminal 300 can install software applications with the display device 200, enabling connection and communication via a network communication protocol, enabling one-to-one control operations and data communication. Audio and video content displayed on the mobile terminal 300 can also be transmitted to the display device 200 for synchronized display.

[0069] like Figure 1 As also shown in the figure, the display device 200 also communicates data with the external device 400 through various communication methods. The display device 200 can be allowed to communicate via a local area network (LAN), a wireless local area network (WLAN), and other networks. The external device 400 also includes an external video source device 410 and an external audio output device 420. Among them, the external video source device may include a digital video disc (DVD), a game console, a video capture card, a projection device, and a streaming device, etc. The external audio output device may include a speaker, a headset, an amplifier, an audio system device (Audio System Device), a multimedia console, and a digital mixing console, etc.

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

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

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

[0073] In some embodiments, detector 230 is used to collect signals from the external environment or external interactions. For example, detector 230 may include a light receiver, such as a sensor for collecting ambient light intensity; or, detector 230 may include an image collector, such as a camera, for collecting external environmental scenes, user attributes, or user interaction gestures; or, detector 230 may include a sound collector, such as a microphone, for receiving external sounds, such as user voice data.

[0074] In some embodiments, the display 260 includes a display component for presenting images and a driver component for driving image display. The display 260 is used to receive image signals output from the controller 250 for display. For example, the display 260 can be used to display video content, image content, and components of a menu control interface and a user control UI (User Interface).

[0075] In some embodiments, the communication device 220 is a component for communicating with an external device or server 400 according to various communication protocol types. The display device 200 can be provided with multiple communication devices 220 depending on the supported communication methods. For example, if the display device 200 supports wireless network communication, the display device 200 can be provided with a communication device 220 that includes WiFi (Wireless Fidelity) functionality. If the display device 200 supports Bluetooth connection communication, the display device 200 needs to be provided with a communication device 220 that includes Bluetooth functionality.

[0076] The communication device 220 can establish a communication connection between the display device 200 and an external device or server 400 via a wireless or wired connection. A wired connection can connect the display device 200 to an external device via a data cable, an interface, or other components. A wireless connection can connect the display device 200 to an external device via a wireless signal or wireless network. The display device 200 can establish a connection with an external device directly or indirectly through a gateway, router, or connection device.

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

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

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

[0080] In some embodiments, the audio output device 270 may be a local speaker of the display device 200, or an external audio output device connected to the display device 200. For the external audio output device connected to the display device 200, the display device 200 may further be provided with an external audio output terminal, through which the audio output device may be connected to the display device 200 to output the sound of the display device 200.

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

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

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

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

[0085] Controller 110 includes a processor 112, random access memory (RAM) 113, read-only memory (ROM) 114, a communication interface 130, and a communication bus. Controller 110 is used to control the operation and functionality of control device 100, as well as communication and coordination between internal components and external and internal data processing.

[0086] Under the control of the controller 110, the communication interface 130 communicates control signals and data signals with the display device 200. The communication interface 130 may include at least one of a WiFi chip 131, a Bluetooth module 132, an NFC (Near Field Communication) module 133, or other near field communication modules.

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

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

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

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

[0091] To facilitate user interaction, in some embodiments, the display device 200 may run an operating system. An operating system is a computer program used to manage and control the hardware and software resources of the display device 200. The operating system may provide a user interface (control the display device), allow the user to interact with the display device 200, and support the running of various application programs.

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

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

[0094] In some embodiments, the application layer provides services and interfaces for applications, enabling the display device 200 to run applications and interact with the user based on the applications. The application layer can host at least one application, which can include built-in window programs, system settings programs, clock programs, and the like, or applications developed by third-party developers. In specific implementations, the application packages in the application layer are not limited to the examples above.

[0095] The framework layer provides applications with an application programming interface (API) and programming framework. The application framework layer includes predefined functions. The application framework layer acts as a processing center, determining the actions taken by applications in the application layer. Through the API, applications can access system resources and services during execution.

[0096] like Figure 4As shown, in the embodiment of the present application, the application framework layer includes a view system, managers, content providers, etc., wherein the view system can design and implement the interface and interaction of the application, and the view system includes lists, grids, text boxes, buttons, etc. The manager includes at least one of the following modules: an activity manager for interacting with all activities running in the system; a location manager for providing system services or applications with access to the system location service; a package manager for retrieving various information related to the application packages currently installed on the device; a notification manager for controlling the display and clearing of notification messages; and a window manager for managing icons, windows, toolbars, wallpapers, and desktop widgets on the user interface.

[0097] In some embodiments, the activity manager is used to manage the lifecycle of each application and common navigation back functions, such as controlling application exit, opening, and back. The window manager is used to manage all window programs, such as obtaining the display screen size, determining whether there is a status bar, locking the screen, taking screenshots, and controlling changes in display windows, such as shrinking, shaking, or distorting the display window.

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

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

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

[0101] See also Figure 5 From the page switching diagram of the display device 200 shown, it can be seen that when the display device 200 needs to enter screen 2 from screen 1, since it is necessary to obtain the real-time page data of screen 2, the preset waiting page will be displayed first. After the real-time page data is obtained from the application server corresponding to screen 2, the screen 2 of the real-time page data will replace the waiting page. At this time, the replacement of the page content will cause the display device 200 to produce a brief screen flash phenomenon, which not only affects the user's visual experience, but also causes damage to the display device 200, affects the service life of the device, and reduces the user's usage experience.

[0102] In some alternative embodiments, see Figure 6A , provides a page display method, applied to the controller 250 in the display device 200, including:

[0103] S610 , in response to a display operation on a page to be displayed in a target application, display the page to be displayed according to first cache data pre-cached in a display cache tree.

[0104] The target application can be understood as the application to which the page to be displayed belongs on the display device 200. The page to be displayed can be understood as a page for displaying the application content of the target application, and the page to be displayed includes at least one interface element. An interface element can be understood as a visual element in the page to be displayed for user interaction.

[0105] The display cache tree (DisplayCachingTree) can be understood as a hierarchical data structure for storing pre-cached display data corresponding to each interface element. Page display can be performed based on the data stored in the display cache tree. The display cache tree can be bound to the user interface (UI) of the display device 200 through data binding technology. When the cached data in the display cache tree changes, the page displayed in the user interface will also be automatically refreshed.

[0106] For example, Figure 6BIn the display cache tree diagram shown, page 1 to be displayed includes at least one interface element (e.g., interface elements 1 to 3 in the diagram); each interface element includes at least one content category, and the display element corresponding to the content category (e.g., a list) can be displayed on page 2 to be displayed; each content category corresponds to at least one display object, which can be displayed on page 3 to be displayed. In response to a display operation on interface element 1 in page 1 to be displayed, page 2 to be displayed, which includes content category 1, content category 2, and content category 3, is displayed based on the display data corresponding to interface element 1; in response to a display operation on content category 1 in page 2 to be displayed, page 3 to be displayed, which includes display object 1, display object 2, and display object 3, is displayed based on the display data corresponding to content category 1.

[0107] The cache data can be understood as the display data corresponding to each interface element in the display cache tree. The first cache data can be understood as the display data corresponding to the first interface element in the display cache tree. The display data can be understood as the required data for displaying the interface elements.

[0108] Exemplarily, in response to a display operation on a page to be displayed in the target application, the controller 250 obtains pre-cached first cache data corresponding to the page to be displayed from the display cache tree; and displays the page to be displayed according to the first cache data.

[0109] S620: Obtain real-time page data of the page to be displayed from the application server corresponding to the target application, and update the real-time page data into the real-time cache tree.

[0110] The application server can be understood as the software platform used to run, deploy, and manage the target application. Real-time page data can be understood as the display data of the page to be displayed, obtained in real time from the application server. The real-time caching tree can be understood as a hierarchical data structure used to store the real-time page data obtained in real time from the application server.

[0111] In one optional implementation method, the controller 250 generates a real-time page data acquisition request corresponding to the page to be displayed in the target application, and sends the real-time page data acquisition request to the application server corresponding to the target application; the application server responds to the real-time page data acquisition request and sends the real-time page data of the page to be displayed in the target application to the controller 250; the controller 250 receives and acquires the real-time page data of the page to be displayed.

[0112] In another optional implementation, the controller 250 generates an intent request (Intent) when launching the target application's application interface and sends the intent request to the application server corresponding to the target application. In response to the request result fed back by the application server, the controller 250 obtains the real-time page data of the target application for the page to be displayed from the request result. For example, in the scenario of displaying the homepage of the target application, the obtained homepage data list (HomePageDataList) can be used as the real-time page data of the homepage.

[0113] Exemplarily, the method of updating the real-time page data to the real-time cache tree may include: obtaining the to-be-updated position of the to-be-displayed page in the real-time cache tree; updating the real-time page data to the corresponding to-be-updated position in the real-time cache tree to complete the update of the real-time cache tree.

[0114] It should be noted that, in this embodiment, S610 and S620 may be executed sequentially or simultaneously, and there is no limitation on the execution order of the two.

[0115] S630: When the first cache data is identical to the real-time page data, keep displaying the page to be displayed.

[0116] S640: When the first cache data is different from the real-time page data and the first interface element is not visible in the page to be displayed, update the real-time page data into the display cache tree to update the first cache data.

[0117] Exemplarily, a determination is made as to whether the first cached data and the real-time page data are identical. If the first cached data and the real-time page data are identical, then the data currently displayed on the to-be-displayed page is the latest data, and there is no need to update the to-be-displayed page; the to-be-displayed page can simply remain displayed. Furthermore, if the first cached data and the real-time page data contain an interface element whose display data differs, then that interface element is used as the first interface element. Based on the visibility of the first interface element on the to-be-displayed page, the real-time page data is updated as needed to the display cache tree to update the first cached data.

[0118] In some embodiments, as Figure 6CAs shown in the first interface element display diagram, for interface element 1, the first cache data (display data 1) corresponding to interface element 1 in the display cache tree is consistent with the real-time page data (display data 1) in the real-time cache tree, so the display of the page to be displayed can be maintained. Similarly, since the first cache data corresponding to interface element 2, interface element 3 and interface element 4 in the display cache tree are inconsistent with the real-time page data in the real-time cache tree, interface element 2, interface element 3 and interface element 4 can be used as the first interface element. Furthermore, based on the visibility of the first interface element in the page to be displayed, the real-time page data is updated to the display cache tree to update the first cache data.

[0119] In some embodiments, when the first cache data differs from the real-time page data, the visibility of the first interface element in the page to be displayed is determined; when the first cache data differs from the real-time page data and the first interface element is not visible in the page to be displayed, since the first interface element is not displayed on the display device 200 at this time, updating the display data corresponding to the first interface element does not affect the current display status of the display 260. At this time, the real-time page data can be updated to the display cache tree to update the first cache data. Accordingly, when the first interface element in the page to be displayed is redisplayed, the first interface element generated by the latest display data is presented.

[0120] Optionally, the method of determining the visibility of the first interface element in the page to be displayed can be: determining the visibility of the first interface element in the page to be displayed based on the element type of the first interface element; or determining the visibility of the first interface element based on the monitored movement of the central focus on the page (such as movement in the forward, backward, left and right directions).

[0121] In some embodiments, if the first interface element is of a list type, the visible area position list (visiblePositionList) of the visible area list in the page to be displayed is determined; if the first interface element is in the visible area position list, it indicates that the first interface element is in a visible state at this time; if the first interface element is not in the visible area position list, it indicates that the first interface element is in an invisible state at this time.

[0122] In other embodiments, if the first interface element is of a non-list type, the visible element interface of the visible interface element in the page to be displayed can be determined; if the first element interface of the first interface element matches the visible element interface, it indicates that the first interface element is in a visible state at this time; if the first element interface of the first interface element does not match the visible element interface, it indicates that the first interface element is in an invisible state at this time.

[0123] It should be noted that when the first cache data is different from the real-time page data and the first interface element is visible in the page to be displayed, the first interface element is kept displayed on the page to be displayed; when it is detected that the first interface element changes from a visible state to an invisible state, the real-time page data is directly updated to the display cache tree to update the first cache data.

[0124] For example, when the first interface element is in a visible state in the page to be displayed, updating the first cache data according to the real-time page data will cause the display 260 to produce a flickering phenomenon. Therefore, the first interface element can be kept displayed on the page to be displayed, and the visibility of the first interface element in the page to be displayed can be monitored at the same time; when it is monitored that the first interface element changes from a visible state to an invisible state, it proves that updating the display data corresponding to the first interface element at this time will not cause the display 260 to produce a flickering phenomenon. Therefore, the real-time page data can be updated to the display cache tree to update the first cache data without the user noticing.

[0125] For example, Figure 6C In the diagram showing the first interface element display, it is known that the first cached data corresponding to interface elements 2, 3, and 4 in the display cache tree is inconsistent with the real-time page data in the real-time cache tree. Interface element 2 is completely within the visible area, meaning it is visible. While interface element 3 has some content within the visible area, it is also visible to the user. Therefore, updating the first cached data corresponding to interface element 3 will still cause a screen flicker, and thus, interface element 3 is considered to be also visible. Therefore, for visible interface elements 2 and 3, the first cached data can only be updated after monitoring that interface elements 2 and 3 have changed from a visible state to an invisible state. However, interface element 4 is completely within the invisible area, meaning that updating interface element 4 will not cause a screen flicker on display 260. Therefore, the real-time page data corresponding to interface element 4 (display data 7) in the display cache tree can be directly updated to the corresponding first cached data in the display cache tree, causing the first cached data to change from display data 4 to display data 7. Once interface element 4 becomes visible, the latest content corresponding to display data 7 is directly displayed.

[0126] It should be noted that there is also a situation in this embodiment, that is, the first interface element is always in a visible state, and no operation in the page to be displayed can change the first interface element from a visible state to an invisible state. In this case, it is necessary to update the real-time page data to the display cache tree after exiting the page to be displayed to update the first cache data.

[0127] For example, Figure 6DThe first interface element display diagram shown is taken as an example where interface element 1 is always visible and interface element 2 is the first interface element. As shown in Figure (A), at this time, the focus of the page to be displayed is on interface element 2, and interface element 2 is still visible to the user. If the real-time page data is updated to the display cache tree, it will cause a screen flash phenomenon. Therefore, the first cache data cannot be updated. However, when the focus is monitored to slide from interface element 2 to interface element 3, as shown in Figure (B), at this time, interface element 2 is not on the screen, that is, it is in an invisible state. Then, updating the first cache data of interface element 2 will not cause a screen flash phenomenon. Therefore, the first cache data can be updated. For interface element 1 that is always visible, no matter how the focus is slid, a part of interface element 1 is visible. Therefore, the first cache data of interface element 1 can only be updated after completely exiting the current display page.

[0128] The above-mentioned page display method introduces a display cache tree and a real-time cache tree, adopts a dual-cache data solution, stores the pre-cached data and the real-time page data of the page to be displayed separately, judges the appropriate time to synchronize the real-time page data to the display cache tree, realizes the imperceptible refresh of the display page, and avoids the page flickering phenomenon caused by frequent updates of the page to be displayed by the real-time page data; that is, by comparing the consistency between the pre-cached data and the real-time page data, the first cache data will be updated according to the real-time page data only when the pre-cached data and the real-time page data are inconsistent and the first interface element in the page to be displayed is not visible. At this time, the update of the first cache data is performed when the first interface element is not visible, which will not affect the display of the page to be displayed, avoiding the screen flickering phenomenon caused by the update of the page to be displayed, affecting the user experience.

[0129] Based on the technical solutions of the above embodiments, in some embodiments, the step of updating the real-time page data into the display cache tree to update the first cache data is refined.

[0130] See also Figure 7 The step of updating the first cache data shown includes:

[0131] S710: Obtain location information of a first interface element.

[0132] The position information can be understood as the position identifier or position coordinates of the first interface element in the page to be displayed. The number of the first interface element is at least one.

[0133] Exemplarily, the controller 250 may obtain the position information of the first interface element in the page to be displayed from the memory of the display device 200 .

[0134] S720: Determine, based on the location information, a location to be updated in the real-time cache tree and the real-time page data corresponding to the location to be updated.

[0135] The position to be updated can be understood as the position information of the first interface element in the real-time cache tree and the position information of the first interface element in the display cache tree.

[0136] Exemplarily, the controller 250 searches the real-time cache tree for a location matching the location information of the first interface element in the page to be displayed, as the location to be updated; and obtains the real-time page data stored in the location to be updated.

[0137] S730: Update the real-time page data corresponding to the position to be updated in the real-time cache tree to the first cache data corresponding to the position to be updated in the display cache tree.

[0138] Exemplarily, the real-time page data corresponding to the position to be updated in the real-time cache tree overwrites the first cache data at the corresponding position to be updated in the display cache tree, so as to update the first cache data.

[0139] Optionally, the position to be updated of the to-be-displayed page in the display cache tree may be obtained; and the first cache data at the corresponding position to be updated in the display cache tree may be overwritten with the real-time page data to update the first cache data.

[0140] It should be noted that if the number of real-time page data corresponding to the position to be updated in the real-time cache tree is greater than the first cache data of the corresponding position to be updated in the display cache tree, the real-time page data exceeding the position to be updated will be changed from a replacement operation to an addition operation, and the exceeding real-time page data will be added to the corresponding position to be updated in the display cache tree, thereby realizing the content update of the cache data in the display cache tree.

[0141] For example, if the real-time page data corresponding to the position to be updated in the real-time cache tree includes display data 1 corresponding to position 1 and display data 2 corresponding to position 2, and the first cache data of the corresponding position to be updated in the display cache tree only includes display data 3 corresponding to position 1; it is obvious that the amount of real-time page data (2) is greater than the first cache data (1), then the display data 1 corresponding to position 1 will be used to replace the display data 3 corresponding to position 1 in the display cache tree, and the display data 2 corresponding to position 2 will be added to the display cache tree.

[0142] In the above embodiment, by determining the position information of the first interface element in the real-time cache tree and the display cache tree, the position to be updated in the real-time cache tree and the display cache tree can be accurately determined; only the real-time page data at the position to be updated is updated to the first cache data of the corresponding position to be updated in the display cache tree, avoiding updating the full data of the display cache tree, thereby improving the update efficiency of the first cache data.

[0143] Based on the technical solutions of the above embodiments, in some embodiments, in response to the display operation of the page to be displayed in the target application, the steps before displaying the page to be displayed according to the first cache data pre-cached in the display cache tree are refined to adapt to the scenario where the target application is installed for the first time.

[0144] See also Figure 8 The steps for updating the display cache tree shown include:

[0145] S810: When the target application is installed for the first time, a request is made to the application server of the target application for page data of the application home page.

[0146] The application homepage can be understood as the first page displayed after the target application is launched, and the page data can be understood as the data used to display the application homepage.

[0147] Specifically, when the target application is installed for the first time, the controller 250 reads metadata from the target application's corresponding installation application registry (AndroidManifest); generates an application homepage request based on the metadata; sends the application homepage request to the target application's application server, and obtains page data for the target application's corresponding application homepage from the application server; after obtaining the page data, changes the target application's installation status from downloading to opening. The metadata can be understood as data containing information such as the request uniform resource locator (URL) for the target application's corresponding application homepage and request parameters.

[0148] Exemplarily, the implementation method of generating the application homepage request based on the metadata may include: encapsulating the request uniform resource locator and request parameters in the metadata to obtain encapsulated metadata; and using the encapsulated metadata as the application homepage request.

[0149] It should be noted that the implementation method of determining that the first installation of the target application is completed in this embodiment may include: after the controller 250 monitors the download button trigger event for the target application, executing the download logic of the target application; after the target application is downloaded, starting to execute the installation operation of the target application, and only after receiving the reminder that the installation of the target application is completed, can it be determined that the first installation of the target application is completed.

[0150] S820, when an opening event of the target application is monitored, a request result of page data of the application homepage is obtained from the intent request generated in the process of pulling up the application interface of the target application.

[0151] Exemplarily, when the controller 250 listens to the trigger event of the open application button for the target application on the application page (such as the application details page of the application store or the my application page), it pulls up the application interface of the target application through the start activity (startActivity) technology, and at the same time, generates an intention request (Intent) to pull up the application interface; the intention request is sent to the application server of the target application; the application server receives the intention request and feeds back the page data corresponding to the intention request to the controller 250; the controller 250 obtains the page data of the application homepage from the intention request; if the corresponding field of the page data is empty, it indicates that the acquisition failed; if the corresponding field of the page data is not empty, it indicates that the acquisition was successful.

[0152] S830: If the acquisition is successful, the display data of each interface element in the application homepage in the request result is obtained, and the display cache tree is updated.

[0153] Specifically, if the acquisition is successful, the controller 250 acquires the page data in the request result; parses the page data to obtain the display data of each interface element in the application page; and adds the display data of each interface element to the display cache tree.

[0154] S840: If the acquisition fails, the preset data is acquired from the local database as display data of each interface element in the application homepage to update the display cache tree.

[0155] One optional implementation is: if the acquisition fails, the controller 250 acquires the preset data from the local database; uses the preset data as display data for each interface element in the application homepage; and adds the preset data to the display cache tree.

[0156] Another optional implementation method is: if the acquisition fails, the controller 250 reads the pre-configured home page data list (DBHomePageDataList) from the local database; since the target application is opened for the first time at this time and the page data of the application home page corresponding to the target application has not been obtained, the home page data list should be empty, that is, there is no cached page data locally, then the preset data can be obtained from the local database as the display data of each interface element in the application home page to update the display cache tree. At the same time, the child thread is started to execute the task of obtaining the page data of the application home page from the application server of the target application. Among them, the home page data list stores the page data of the application home page corresponding to the target application requested last time.

[0157] In this embodiment, when the target application is first installed, the page data of the application homepage is directly requested from the application server of the target application, instead of the traditional method of requesting the page data of the application homepage from the application server of the target application when the target application is opened. This actually advances the request for the page data and shortens the time of the data request. After the target application is opened and the request result for the page data of the application homepage is obtained, the page data associated with the target application still exists, and the page data is used as a degradation solution to display the page according to the page data, thus avoiding the problem of long waiting time when the user opens the target application for the first time, and further improving the user experience.

[0158] Based on the technical solutions of the above embodiments, in some embodiments, the updating steps of the display cache tree are refined to adapt to the scenario where the installed target application starts automatically at boot.

[0159] See also Figure 9 The steps for updating the display cache tree shown include:

[0160] S910 , when a display device having a target application installed is powered on and the target application is a startup application, obtain a network connection status of the display device.

[0161] For example, in order to ensure that the target application can obtain the latest page data, the startup broadcast will be statically registered for the target application in advance, and the target application will start automatically after receiving the TV startup broadcast; when the controller 250 determines that the display device on which the target application is installed is turned on and the target application is a startup self-starting application, it will dynamically monitor the changes in the network broadcast in the background; when the network broadcast changes, the network connection status of the display device is obtained.

[0162] S920, when the display device is in a network connection state, obtain the request result of the page data of the application homepage from the intention request generated in the process of pulling up the application interface of the target application, and obtain the display data of each interface element in the application homepage in the request result, and update the display cache tree.

[0163] In some embodiments, when the controller 250 detects that the display device 200 is in a network connection state, it indicates that the controller 250 can successfully communicate with the application server of the target application and obtain the latest page data from it. Therefore, the request result of the page data of the application homepage can be obtained from the intention request generated in the process of pulling up the application interface of the target application, and the display data of each interface element in the application homepage in the request result can be obtained to update the display cache tree.

[0164] It should be noted that the steps of obtaining the request result of the page data of the application homepage from the intention request generated during the process of pulling up the application interface of the target application, obtaining the display data of each interface element in the application homepage in the request result, and updating the display cache tree have been explained in detail in the above embodiment and will not be repeated here in this embodiment.

[0165] S930: When the display device is not in a network connection state, obtain the page data of the application homepage of the target application that was previously requested from the local database, and update the display cache tree.

[0166] In some embodiments, when the display device 200 is not in a network connection state, the control controller 250 cannot communicate with the application server of the target application. Therefore, the page data of the application homepage of the target application requested last can be obtained from the local database (such as the homepage data list), replacing the network side to obtain the page data of the application homepage, and the page data of the application homepage is updated to the display cache tree.

[0167] In this embodiment, the network connection status of the display device is detected. When the display device is not in a network connection state, the page data of the application homepage of the target application previously requested in the local database can be used to update the display cache tree as a backup, so that the application homepage of the target application previously requested can be displayed after the target application is opened. The target application homepage previously requested is used as a downgrade solution to avoid the problem that the user cannot open the target application homepage when the network is not connected, resulting in a long waiting time for the user, thereby further improving the user's usage experience.

[0168] Based on the technical solutions of the above embodiments, in some embodiments, the step of obtaining real-time page data of the page to be displayed from the application server corresponding to the target application is refined to adapt to the focus change in the currently displayed page.

[0169] See also Figure 10A The steps for updating the display cache tree shown include:

[0170] S1010 , during use of the target application, when a focus change in the current display page is monitored, obtain second cache data corresponding to a second interface element hit by the focus in the display cache tree.

[0171] The currently displayed page can be understood as the page displayed on display 260 before the page to be displayed is displayed. The second interface element can be understood as the interface element that is focused on in the currently displayed page. The second interface element generally indicates that the user intends to open the interface element. The second cache data can be understood as the display data corresponding to the second interface element in the display cache tree.

[0172] For example, during the use of the target application, if the controller 250 detects a change in the focus of the currently displayed page, the interface element hit by the focus is used as the second interface element; the position information of the second interface element in the display cache tree is determined; the position matching the position information is searched from the display cache tree as the position to be updated; and the second cache data stored in the position to be updated is obtained.

[0173] S1020, when the second cache data is consistent with the real-time page data corresponding to the second interface element in the real-time cache tree, request the real-time page data of the page to be displayed corresponding to the second interface element from the application server corresponding to the target application according to the second cache data.

[0174] In some optional embodiments, if the second cache data is consistent with the real-time page data corresponding to the second interface element in the real-time cache tree, indicating that the second interface element is still valid (i.e., has not been removed from the shelf or deleted), the controller 250 generates a real-time page data request based on the second cache data; sends the real-time page data request to the application server corresponding to the target application, and responds to the real-time page data corresponding to the real-time page data request fed back by the application server; and obtains the real-time page data of the page to be displayed. Accordingly, if the controller 250 monitors the trigger event for the second interface element, it directly displays the page to be displayed based on the real-time page data.

[0175] It is understandable that, in order to avoid the problem of users having to wait a long time when opening the page to be displayed, the operation of acquiring the real-time page data of the page to be displayed is executed when the focus change in the currently displayed page is monitored, instead of the traditional operation of acquiring the real-time page data of the page to be displayed only after the focus in the currently displayed page is triggered. In other words, the operation of acquiring the real-time page data of the page to be displayed is advanced to before the focus in the currently displayed page is triggered. Accordingly, when the controller 250 monitors the trigger event for the second interface element, the page to be displayed is directly displayed according to the latest real-time page data, thereby reducing the waiting time.

[0176] In some optional embodiments, if the second cache data is inconsistent with the real-time page data corresponding to the second interface element in the real-time cache tree, it is further possible to determine whether the content category of the second cache data is consistent with the content category of the real-time page data corresponding to the second interface element in the real-time cache tree; based on the consistency of the content category of the second cache data and the content category of the real-time page data, the real-time page data corresponding to the second interface element is obtained. The content category can be understood as representing the type of page content corresponding to the second interface element in the to-be-displayed page, and the content category can be configured and issued by the backend system.

[0177] In an optional embodiment, when the second cache data is inconsistent with the real-time page data corresponding to the second interface element in the real-time cache tree, and the content category of the second cache data is consistent with the content category of the real-time page data corresponding to the second interface element in the real-time cache tree, the real-time page data of the page to be displayed corresponding to the second interface element can be requested from the application server corresponding to the target application based on the real-time page data corresponding to the second interface element in the real-time cache tree; and the page to be displayed can be displayed based on the real-time page data of the page to be displayed corresponding to the second interface element.

[0178] For example, when the second cache data is inconsistent with the real-time page data corresponding to the second interface element in the real-time cache tree, and the content category of the second cache data is consistent with the content category of the real-time page data corresponding to the second interface element in the real-time cache tree, it indicates that the second interface element in the currently displayed page may have expired, but the second interface element corresponding to the page to be displayed has a similar content category to the second interface element in the currently displayed page. Therefore, when acquiring real-time page data, the real-time page data corresponding to the second interface element in the display cache tree can be replaced with the second cache data corresponding to the second interface element in the real-time cache tree to generate a real-time page data request for the page to be displayed; according to the real-time page data request, the real-time page data of the page to be displayed corresponding to the second interface element is requested from the application server corresponding to the target application; accordingly, the page to be displayed is displayed according to the real-time page data of the page to be displayed corresponding to the second interface element, thereby ensuring the accuracy of the acquired page data of the page to be displayed. It is worth noting that when or before requesting the real-time page data of the to-be-displayed page corresponding to the second interface element, the page where the second interface element is located is temporarily not updated. When or after displaying the to-be-displayed page corresponding to the second interface element, that is, the subordinate page of the second interface element, the interface element previously displayed in the page where the second interface element is located is converted from a visible state to an invisible state, and then the cached data at the corresponding position in the display cache tree is updated. In another optional embodiment, when the second cached data is inconsistent with the real-time page data corresponding to the second interface element in the real-time cache tree, and the content category of the second cached data is inconsistent with the content category of the real-time page data corresponding to the second interface element in the real-time cache tree, the cached data of the to-be-displayed page corresponding to the second interface element that was displayed last in the local database is obtained; and the to-be-displayed page is displayed according to the cached data of the to-be-displayed page.

[0179] For example, when the second cache data is inconsistent with the real-time page data corresponding to the second interface element in the real-time cache tree, and the content category of the second cache data is inconsistent with the content category of the real-time page data corresponding to the second interface element in the real-time cache tree, it indicates that the second interface element in the currently displayed page has expired, for example, a board replacement or deletion has occurred, and the page to be displayed cannot be displayed directly. Therefore, the cache data of the page to be displayed (that is, the lower-level page) corresponding to the second interface element displayed last time can be obtained in the local database; and the page to be displayed is displayed according to the cache data of the page to be displayed.

[0180] It should be noted that if there is no cached data in the local database for the page to be displayed corresponding to the previous display of the second interface element, empty content can be displayed and a reminder that the second interface element has gone offline can be output; preset data can also be obtained from the local database; and the page to be displayed can be displayed according to the preset data.

[0181] For example, Figure 10B As shown in the schematic diagram of the page to be displayed, for interface element 1, the second cache data of interface element 1 in the display cache tree is the same as the real-time page data in the real-time cache tree, proving that interface element 1 is valid. Based on display data 1 in the cache display tree, the real-time page data of the page to be displayed corresponding to the second interface element can be requested, and the page to be displayed can be displayed based on the requested data. For interface element 2, the second cache data (display data 2) of interface element 2 in the display cache tree is different from the real-time page data (display data 2′) in the real-time cache tree, but the content category of the second cache data (display data 2) and the real-time page data (display data 2′) are consistent. At this time, based on the real-time page data (display data 2′) corresponding to the second interface element in the real-time cache tree, the real-time page data of the page to be displayed corresponding to the second interface element can be requested from the application server corresponding to the target application; and based on the real-time page data of the page to be displayed corresponding to the second interface element, the page to be displayed can be displayed. For interface element 3, the second cache data (display data 3) of interface element 3 in the display cache tree is different from the real-time page data (display data 5) in the real-time cache tree, and the content categories of the second cache data (display data 3) and the real-time page data (display data 5) are also inconsistent. At this time, the cache data of the page to be displayed corresponding to the last display of the second interface element in the local database can be obtained; the page to be displayed is displayed according to the cache data of the page to be displayed.

[0182] In this embodiment, by comparing the consistency between the second cache data of the second interface element and the real-time page data, it is determined whether the second interface element is still valid; when it is determined that the second interface element is still valid, the latest page data corresponding to the second interface element is obtained in advance, so that when a trigger event for the second interface element is monitored, the page to be displayed is directly displayed according to the latest page data, avoiding the problem of users waiting for a long time when opening the page to be displayed, and further improving the user experience.

[0183] On the basis of the technical solutions of the above embodiments, in some optional embodiments, the page display process is described by taking a controller applied to a display device as an example.

[0184] See also Figure 11 The page display method shown includes:

[0185] S1101, start.

[0186] S1102: When the target application is installed for the first time, a request is made to the application server of the target application for page data of the application home page.

[0187] S1103, when an opening event of the target application is monitored, a request result of page data of the application home page is obtained from the intent request generated in the process of pulling up the application interface of the target application.

[0188] S1104: If the acquisition is successful, the display data of each interface element in the application homepage in the request result is obtained, and the display cache tree is updated.

[0189] S1105: If the acquisition fails, the preset data is acquired from the local database as the display data of each interface element in the application homepage to update the display cache tree.

[0190] S1106 , when the display device on which the target application is installed is powered on and the target application is a startup application, obtaining the network connection status of the display device.

[0191] S1107, when the display device is in a network connection state, obtain the request result of the page data of the application homepage from the intention request generated in the process of pulling up the application interface of the target application, and obtain the display data of each interface element in the application homepage in the request result, and update the display cache tree.

[0192] S1108 , when the display device is not in a network connection state, obtain the page data of the application homepage of the target application that was previously requested from the local database, and update the display cache tree.

[0193] S1109 , in response to a display operation on a page to be displayed in the target application, display the page to be displayed according to first cache data pre-cached in the display cache tree.

[0194] The page to be displayed includes at least one interface element, and the first cache data is the display data corresponding to the first interface element in the display cache tree.

[0195] S1110 , when the first cache data is identical to the real-time page data, keep displaying the page to be displayed.

[0196] S1111. Under the condition of situation A, obtain the position information of the first interface element.

[0197] S1112: Determine the location to be updated in the real-time cache tree and the real-time page data corresponding to the location to be updated according to the location information.

[0198] S1113, updating the real-time page data corresponding to the position to be updated in the real-time cache tree to the first cache data of the corresponding position to be updated in the display cache tree, and displaying the page to be displayed according to the first cache data of the page to be displayed.

[0199] S1114: When the condition B is met, keep displaying the first interface element on the page to be displayed.

[0200] S1115, when monitoring the first interface element changing from a visible state to an invisible state, directly update the real-time page data to the display cache tree to update the first cache data, and display the page to be displayed according to the first cache data of the page to be displayed.

[0201] S1116 , during the use of the target application, when a focus change in the current display page is monitored, obtain second cache data corresponding to the second interface element hit by the focus in the display cache tree.

[0202] S1117, when the second cache data is consistent with the real-time page data corresponding to the second interface element in the real-time cache tree, based on the second cache data, request the real-time page data of the page to be displayed corresponding to the second interface element from the application server corresponding to the target application, and update the real-time page data to the real-time cache tree.

[0203] S1118, when the condition C is met, based on the real-time page data corresponding to the second interface element in the real-time cache tree, request the real-time page data of the page to be displayed corresponding to the second interface element from the application server corresponding to the target application.

[0204] S1119 , displaying the page to be displayed according to the real-time page data of the page to be displayed corresponding to the second interface element, and updating the real-time page data into the real-time cache tree.

[0205] S1120: When the condition D is met, obtain cache data of the page to be displayed corresponding to the second interface element displayed last time in the local database.

[0206] S1121: Display the page to be displayed according to the cached data of the page to be displayed.

[0207] Based on the same inventive concept, embodiments of the present application also provide a page display device for implementing the aforementioned page display method. The solution provided by this device is similar to the solution described in the aforementioned method. Therefore, the specific limitations of one or more page display device embodiments provided below can be found in the above-described limitations of the page display method and will not be further elaborated here.

[0208] In an exemplary embodiment, Figure 12 As shown, a page display device is provided, including: a display module 1210, an acquisition module 1220 and an update module 1230.

[0209] The display module 1210 is configured to, in response to a display operation on a page to be displayed in a target application, display the page to be displayed according to first cached data pre-cached in the display cache tree; wherein the page to be displayed includes at least one interface element; and

[0210] The acquisition module 1220 is used to obtain the real-time page data of the page to be displayed from the application server corresponding to the target application, and update the real-time page data into the real-time cache tree;

[0211] The display module 1210 is further configured to maintain display of the page to be displayed when the first cached data is identical to the real-time page data;

[0212] Update module 1230 is used to update the real-time page data to the display cache tree to update the first cache data when the first cache data is different from the real-time page data and the first interface element is not visible in the page to be displayed; wherein the first cache data is the display data corresponding to the first interface element in the display cache tree.

[0213] In some embodiments, the display module is also used to keep the first interface element displayed on the page to be displayed when the first cache data is different from the real-time page data and the first interface element is visible in the page to be displayed; and when it is detected that the first interface element changes from a visible state to an invisible state, the real-time page data is directly updated to the display cache tree to update the first cache data.

[0214] In some embodiments, the update module 1230 is also used to obtain the location information of the first interface element; determine the location to be updated in the real-time cache tree and the real-time page data corresponding to the location to be updated based on the location information; and update the real-time page data corresponding to the location to be updated in the real-time cache tree to the first cache data of the corresponding location to be updated in the display cache tree.

[0215] In some embodiments, the page display device further includes:

[0216] The cache tree update module is used to request the page data of the application home page from the application server of the target application when the target application is installed for the first time; when monitoring the opening event of the target application, obtain the request result of the page data of the application home page from the intention request generated during the pulling-up process of the application interface of the target application; if the acquisition is successful, obtain the display data of each interface element in the application home page in the request result and update the display cache tree; if the acquisition fails, obtain the preset data from the local database as the display data of each interface element in the application home page to update the display cache tree.

[0217] In some embodiments, the cache tree update module is also used to obtain the network connection status of the display device when the display device on which the target application is installed is turned on and the target application is a self-starting application; when the display device is in a network connection state, the module obtains the request result of the page data of the application home page from the intention request generated during the process of pulling up the application interface of the target application, and obtains the display data of each interface element in the application home page in the request result, and updates the display cache tree; when the display device is not in a network connection state, the module obtains the page data of the application home page of the target application that was previously requested from the local database, and updates the display cache tree.

[0218] In some embodiments, the acquisition module is also used to, during the use of the target application, acquire the second cache data corresponding to the second interface element hit by the focus in the display cache tree when monitoring the focus change in the currently displayed page; when the second cache data is consistent with the real-time page data corresponding to the second interface element in the real-time cache tree, request the real-time page data of the page to be displayed under the second interface element from the application server corresponding to the target application based on the second cache data.

[0219] In some embodiments, the acquisition module is also used to request the real-time page data of the page to be displayed corresponding to the second interface element from the application server corresponding to the target application according to the real-time page data corresponding to the second interface element in the real-time cache tree; and display the page to be displayed according to the real-time page data of the page to be displayed corresponding to the second interface element when the second cache data is inconsistent with the real-time page data corresponding to the second interface element in the real-time cache tree, and the content category of the second cache data is consistent with the content category of the real-time page data corresponding to the second interface element in the real-time cache tree.

[0220] In some embodiments, the acquisition module is also used to obtain the cache data of the page to be displayed corresponding to the second interface element that was last displayed in the local database when the second cache data is inconsistent with the real-time page data corresponding to the second interface element in the real-time cache tree, and the content category of the second cache data is inconsistent with the content category of the real-time page data corresponding to the second interface element in the real-time cache tree; and display the page to be displayed according to the cache data of the page to be displayed.

[0221] Each module in the above-mentioned page display device can be implemented in whole or in part through software, hardware, or a combination thereof. Each module can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the corresponding operations of each module.

[0222] In an exemplary embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as shown in FIG. Figure 13As shown. The computer device includes a processor, a memory, an input / output interface, a communication interface, a display unit and an input device. The processor, the memory and the input / output interface are connected via a system bus, and the communication interface, the display unit and the input device are connected to the system bus via the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be implemented through WIFI, a mobile cellular network, near field communication (NFC) or other technologies. When the computer program is executed by the processor, an audio noise reduction method is implemented. The display unit of the computer device is used to form a visually visible picture, which can be a display screen, a projection device or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covering the display screen, or a button, trackball or touchpad set on the computer device casing, or an external keyboard, touchpad or mouse.

[0223] Those skilled in the art will understand that Figure 13 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0224] In an alternative embodiment, Figure 13 The computer device shown may be the aforementioned projection device, for example, a laser TV.

[0225] In one exemplary embodiment, a computer device is provided, comprising a memory and a processor. The memory stores a computer program, and when the processor executes the computer program, the steps of the above-described method embodiments are implemented. In another embodiment, a computer-readable storage medium is provided, storing the computer program, and when the processor executes the computer program, the steps of the above-described method embodiments are implemented.

[0226] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

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

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

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

[0230] The above embodiments merely illustrate several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present invention. It should be noted that a person skilled in the art may make various modifications and improvements without departing from the spirit of the present invention, all of which fall within the scope of protection of the present application. Therefore, the scope of protection of the present application shall be determined by the appended claims.

Claims

1. A display device, characterized in that: include: A display, used for displaying pages; A controller, connected to the display, is configured to: In response to a display operation on a page to be displayed in a target application, displaying the page to be displayed according to first cached data pre-cached in a display cache tree; wherein the page to be displayed includes at least one interface element; and Obtaining real-time page data of the to-be-displayed page from an application server corresponding to the target application, and updating the real-time page data into a real-time cache tree; When the first cache data is identical to the real-time page data, maintaining display of the page to be displayed; When the first cache data is different from the real-time page data and the first interface element is not visible in the page to be displayed, updating the real-time page data into the display cache tree to update the first cache data; The first cache data is display data corresponding to the first interface element in the display cache tree.

2. The display device according to claim 1, wherein The controller is further configured to: When the first cached data is different from the real-time page data and the first interface element is visible in the page to be displayed, keep displaying the first interface element on the page to be displayed; When it is detected that the first interface element changes from a visible state to an invisible state, the real-time page data is directly updated to the display cache tree to update the first cache data.

3. The display device according to claim 1 or 2, characterized in that When executing the updating of the real-time page data into the display cache tree to update the first cache data, the controller is configured to: Obtaining position information of the first interface element; Determining, based on the location information, a location to be updated in the real-time cache tree and real-time page data corresponding to the location to be updated; The real-time page data corresponding to the to-be-updated position in the real-time cache tree is updated to the first cache data at the corresponding to-be-updated position in the display cache tree.

4. The display device according to claim 1 or 2, characterized in that Before the controller performs the display operation on the page to be displayed in the target application and displays the page to be displayed according to the first cache data pre-cached in the display cache tree, the controller is further configured to: When the target application is installed for the first time, requesting page data of the application homepage from the application server of the target application; When an opening event of the target application is monitored, obtaining a request result for page data of the application homepage from an intent request generated during the process of pulling up the application interface of the target application; If the acquisition is successful, the display data of each interface element in the application homepage in the request result is obtained, and the display cache tree is updated; If the acquisition fails, the preset data is acquired from the local database as the display data of each interface element in the application homepage to update the display cache tree.

5. The display device according to claim 1 or 2, characterized in that: Before the controller performs the display operation on the page to be displayed in the target application and displays the page to be displayed according to the first cache data pre-cached in the display cache tree, the controller is further configured to: When a display device on which the target application is installed is powered on and the target application is a power-on auto-start application, obtaining a network connection status of the display device; When the display device is in a network connection state, obtaining a request result for page data of the application homepage from an intent request generated during the process of pulling up the application interface of the target application, and obtaining display data of each interface element in the application homepage from the request result, and updating the display cache tree; When the display device is not in a network connection state, page data of the application homepage of the target application requested last time in the local database is obtained, and the display cache tree is updated.

6. The display device according to claim 1 or 2, characterized in that When executing the step of acquiring the real-time page data of the to-be-displayed page from the application server corresponding to the target application, the controller is configured to: During use of the target application, when a focus change in a currently displayed page is monitored, obtaining second cache data corresponding to a second interface element hit by the focus in the display cache tree; When the second cache data is consistent with the real-time page data corresponding to the second interface element in the real-time cache tree, the real-time page data of the page to be displayed corresponding to the second interface element is requested from the application server corresponding to the target application according to the second cache data.

7. The display device according to claim 6, wherein: The controller is further configured to: If the second cache data is inconsistent with the real-time page data corresponding to the second interface element in the real-time cache tree, and the content category of the second cache data is consistent with the content category of the real-time page data corresponding to the second interface element in the real-time cache tree, requesting the real-time page data of the to-be-displayed page corresponding to the second interface element from the application server corresponding to the target application based on the real-time page data corresponding to the second interface element in the real-time cache tree; The page to be displayed is displayed according to the real-time page data of the page to be displayed corresponding to the second interface element.

8. The display device according to claim 6, wherein: The controller is further configured to: When the second cache data is inconsistent with the real-time page data corresponding to the second interface element in the real-time cache tree, and the content category of the second cache data is inconsistent with the content category of the real-time page data corresponding to the second interface element in the real-time cache tree, obtaining cache data of the to-be-displayed page corresponding to the second interface element that was previously displayed in the local database; The page to be displayed is displayed according to the cached data of the page to be displayed.

9. A page display method, characterized in that: include: In response to a display operation on a page to be displayed in a target application, displaying the page to be displayed according to first cached data pre-cached in a display cache tree; wherein the page to be displayed includes at least one interface element; and Obtaining real-time page data of the to-be-displayed page from an application server corresponding to the target application, and updating the real-time page data into a real-time cache tree; When the first cache data is identical to the real-time page data, maintaining display of the page to be displayed; When the first cache data is different from the real-time page data and the first interface element is not visible in the page to be displayed, updating the real-time page data into the display cache tree to update the first cache data; The first cache data is display data corresponding to the first interface element in the display cache tree.

10. A page display device, characterized in that: include: A display module, configured to, in response to a display operation on a page to be displayed in a target application, display the page to be displayed according to first cached data pre-cached in a display cache tree; wherein the page to be displayed includes at least one interface element; and An acquisition module, configured to acquire the real-time page data of the to-be-displayed page from the application server corresponding to the target application, and update the real-time page data into a real-time cache tree; The display module is further configured to maintain display of the page to be displayed when the first cache data is identical to the real-time page data; an updating module, configured to update the real-time page data into the display cache tree to update the first cache data when the first cache data is different from the real-time page data and the first interface element is not visible in the page to be displayed; The first cache data is display data corresponding to the first interface element in the display cache tree.

Images