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 display equipment. The display equipment comprises a display which is configured to perform page display; the at least one controller is connected with the display and is configured to receive a connection request initiated by an AIoT (artificial intelligence Internet of Things) client; under the condition that the request moment of the connection request exceeds the page display time limit corresponding to the connection request, controlling a display to display an authorized page; under the condition that the request moment of the connection request does not exceed the page display time limit corresponding to the connection request, controlling a display not to display an authorized page; and in response to a cancelling operation on the authorized page, counting continuous cancelling times, determining a page display time limit corresponding to the next connection request according to the continuous cancelling times, and prohibiting connection with the AIoT client. According to the method and the device, the operation cancelling times of the user can be reduced under the condition that multiple misoperation behaviors occur or hacker attacks occur.

Description

Technical Field

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

[0002] With the development of Artificial Intelligence of Things (AIoT), AIoT clients are increasingly applied to application fields such as smart home, environmental monitoring and security, and factory production line management.

[0003] During the use of an AIoT client, after the AIoT client is successfully authorized by a display device in an application scenario, the user can manage and control the display device through the AIoT client. The process of the display device authorizing the AIoT client is actually a process of establishing a connection between the AIoT client and the display device. If the connection is successful, the authorization is successful; if the connection fails, the authorization fails.

[0004] During the authorization process, the user can cancel the connection as needed on the display device. However, when the user makes misoperation behaviors of repeatedly initiating connection requests on the AIoT client or encounters a hacker attack, the user needs to frequently perform cancellation operations, which reduces the user experience. Summary of the Invention

[0005] The present application provides a display device and a page display method thereof to reduce the number of user cancellation operations in case of multiple misoperation behaviors or hacker attacks.

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

[0007] A display configured to perform page display;

[0008] At least one controller connected to the display and configured to:

[0009] Receive a connection request initiated by an Artificial Intelligence of Things (AIoT) client;

[0010] When the request time of the connection request exceeds the page display time limit corresponding to the current connection request, control the display to display an authorization page;

[0011] When the request time of the connection request does not exceed the page display time limit corresponding to the current connection request, control the display not to display an authorization page;

[0012] In response to a cancellation operation on the authorization page, the number of consecutive cancellations is counted, and the page display time limit corresponding to the next connection request is determined based on the number of consecutive cancellations, and establishing a connection with the AIoT client is prohibited; wherein, the length of the page display time limit corresponding to the next connection request is positively correlated with the number of consecutive cancellations.

[0013] In some embodiments, the controller can determine the page display time limit corresponding to the next connection request based on the number of consecutive cancellations obtained in this statistics. In this way, when the user initiates the next connection request to the display device on the AIoT client, the controller controls whether the display displays the authorization page based on the page display time limit corresponding to the next connection request. When the request time of the next connection request does not exceed the page display time limit corresponding to the next connection request, the controller controls the display not to display the authorization page, and the page display time limit corresponding to the next connection request is positively correlated with the number of consecutive cancellations obtained in this statistics. Whether it is multiple misoperations by the user or encountering hacker attacks, the user does not want the AIoT client to connect to the display device, and the above technical solution can increase the display time interval of the authorization page, that is, reduce the display frequency of the authorization page, reduce the number of times the user needs to manually cancel the operation, reduce the trouble caused to the user due to misoperation or hacker attacks, and thus improve the user experience.

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

[0015] Receive connection requests initiated by the artificial intelligence Internet of Things (AIoT) client;

[0016] When the request time of the connection request exceeds the page display time limit corresponding to the current connection request, controlling the display to display the authorization page;

[0017] When the request time of the connection request does not exceed the page display time limit corresponding to the current connection request, controlling the display not to display the authorization page;

[0018] In response to a cancellation operation on the authorization page, the number of consecutive cancellations is counted, and the page display time limit corresponding to the next connection request is determined based on the number of consecutive cancellations, and establishing a connection with the AIoT client is prohibited; wherein, the length of the page display time limit corresponding to the next connection request is positively correlated with the number of consecutive cancellations.

[0019] In some embodiments, the page display time limit corresponding to the next connection request can be determined based on the number of consecutive cancellations obtained in this statistics. In this way, when the user initiates the next connection request to the display device on the AIoT client, the display is controlled to display the authorization page based on the page display time limit corresponding to the next connection request. If the request time of the next connection request does not exceed the page display time limit corresponding to the next connection request, the authorization page is controlled not to be displayed, and the page display time limit corresponding to the next connection request is positively correlated with the number of consecutive cancellations obtained in this statistics. Whether it is multiple misoperations by the user or a hacker attack, the user does not want the AIoT client to connect to the display device, and the above technical solution can increase the display time interval of the authorization page, that is, reduce the display frequency of the authorization page, reduce the number of times the user needs to manually cancel the operation, reduce the trouble caused to the user by misoperation or hacker attack, and thus improve the user experience.

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

[0021] A request receiving module is used to receive a connection request initiated by an artificial intelligence Internet of Things (AIoT) client;

[0022] A first control module, configured to control the display to display an authorization page when the request time of the connection request exceeds the page display time limit corresponding to the current connection request;

[0023] A second control module, configured to control the display not to display the authorization page if the request time of the connection request does not exceed the page display time limit corresponding to the current connection request;

[0024] A time limit determination module is used to respond to a cancellation operation on the authorization page, count the number of consecutive cancellations, and determine the page display time limit corresponding to the next connection request based on the number of consecutive cancellations, and prohibit establishing a connection with the AIoT client; wherein the length of the page display time limit corresponding to the next connection request is positively correlated with the number of consecutive cancellations.

[0025] In some embodiments, the time limit determination module is introduced to determine the page display time limit corresponding to the next connection request based on the number of consecutive cancellations obtained in this statistics. In this way, when the user initiates the next connection request to the display device on the AIoT client, the display is controlled to display the authorization page based on the page display time limit corresponding to the next connection request. The second control module is introduced to control the display not to display the authorization page when the request time of the next connection request does not exceed the page display time limit corresponding to the next connection request, and the page display time limit corresponding to the next connection request is positively correlated with the number of consecutive cancellations obtained in this statistics. Whether it is multiple misoperations by the user or encountering hacker attacks, the user does not want the AIoT client to connect to the display device, and the above technical solution can increase the display time interval of the authorization page, that is, reduce the display frequency of the authorization page, reduce the number of times the user needs to manually cancel the operation, reduce the trouble caused to the user by misoperation or hacker attacks, and thus improve the user experience.

[0026] In a fourth aspect, some embodiments further provide a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, the steps of the method provided in some embodiments of the second aspect are implemented.

[0027] In the fifth aspect, some embodiments further provide a computer program product, including a computer program, which, when executed by a processor, implements the steps of the method provided in some embodiments of the second aspect. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0029] 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;

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

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

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

[0033] Figure 5ASchematic flowchart of a page display method provided by some embodiments of the present application;

[0034] Figure 5B Schematic diagram of an authorization page provided by some embodiments of the present application;

[0035] Figure 6A Schematic flowchart of another page display method provided by some embodiments of the present application;

[0036] Figure 6B Schematic flowchart of a blacklist update method provided by some embodiments of the present application;

[0037] Figure 6C Schematic flowchart of another blacklist update method provided by some embodiments of the present application;

[0038] Figure 6D Schematic flowchart of a whitelist update method provided by some embodiments of the present application;

[0039] Figure 7 Interaction schematic diagram between a display device and an AIoT client provided by some embodiments of the present application;

[0040] Figure 8 Schematic flowchart of an application switching method provided by some embodiments of the present application;

[0041] Figure 9 Block diagram of the structure of a page display device provided by some embodiments of the present application;

[0042] Figure 10 Internal structure diagram of a computer device in one embodiment. Detailed implementation manners

[0043] The embodiments will be described in detail below, and the examples are shown in the accompanying drawings. When the following description refers to the accompanying drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementation manners described in the following embodiments do not represent all implementation manners consistent with the present application. They are merely examples of systems and methods consistent with some aspects of the present application described in detail in the claims.

[0044] It should be noted that the brief description of the terms in the present application is only for the convenience of understanding the implementation manners described next, rather than intending to limit the implementation manners of the present application. Unless otherwise specified, these terms should be understood in their ordinary and common meanings.

[0045] In this application, terms such as "first", "second", "third", etc. in the description, claims and the above-mentioned drawings are used to distinguish similar or like objects or entities, and do not necessarily mean to limit a specific order or sequence, unless otherwise noted. It should be understood that such terms can be interchanged under appropriate circumstances.

[0046] The terms "comprising" and "having" and any variations thereof are intended to cover but not exclusively include. For example, a product or device comprising a series of components does not necessarily have to be limited to all the components clearly listed, but may include other components not clearly listed or inherent to these products or devices.

[0047] The term "module" refers to any known or later developed hardware, software, firmware, artificial intelligence, fuzzy logic or a combination of hardware and / or software code that can perform functions related to that element.

[0048] In this application, the display device 200 generally refers to a device with the ability to display images and process data. For example, the display device 200 includes but is not limited to smart TVs, mobile terminals, computers, monitors, advertising screens, wearable devices, virtual reality devices, augmented reality devices, etc.

[0049] Figure 1 It is a schematic diagram of the operation scenario between the display device and the control device provided for some embodiments of this application. As Figure 1 shown, the user can operate the display device 200 through touch operations, the mobile terminal 300 and the control device 100. For example, the control device 100 can be a remote control, a stylus, a handle, etc.

[0050] The mobile terminal 300 can be used as a control device to perform human-computer interaction between the user and the display device 200. The mobile terminal 300 can also be used as a communication device to establish a communication connection with the display device 200 for data interaction. In some embodiments, software applications can be installed on the mobile terminal 300 and the display device 200, and the connection communication can be achieved through network communication protocols to achieve the purpose of one-to-one control operation and data communication. For example, an AIoT client can be installed on the mobile terminal 300 to switch and control the installed applications on the display device 200. It is also possible to transmit the audio and video content displayed on the mobile terminal 300 to the display device 200 to achieve the synchronous display function.

[0051] As Figure 1It is also shown that the display device 200 also communicates with the server 400 for data communication through various communication methods. The display device 200 is allowed to communicate and connect through a local area network (LAN), a wireless local area network (WLAN), and other networks.

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

[0053] Figure 2 For some embodiments of the present application Figure 1 The hardware configuration block diagram of the display device 200 in

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

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

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

[0057] 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 may be provided with a plurality of communication devices 220 according to different supported communication methods. For example, when the display device 200 supports wireless network communication, the display device 200 may be provided with a communication device 220 including a WiFi (Wireless Fidelity) function. When the display device 200 supports Bluetooth connection communication, the display device 200 needs to be provided with a communication device 220 including a Bluetooth function.

[0058] The communication device 220 can enable the display device 200 to communicate with an external device or server 400 through a wireless or wired connection. Among them, the wired connection can connect the display device 200 to an external device through components such as a data cable and an interface. The wireless connection can connect the display device 200 to an external device through a wireless signal or a wireless network. The display device 200 can directly establish a connection relationship with an external device or indirectly establish a connection relationship through a gateway, a router, a connection device, etc.

[0059] In some embodiments, the controller 250 may include at least one of a central processing unit, a video processor, an audio processor, a graphics processor, and a power processor, and 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 the memory. The controller 250 controls the overall operation of the display device 200.

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

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

[0062] In some embodiments, the audio output device 270 may be a built-in speaker of the display device 200 or an external audio output device connected to the display device 200. Among them, for the external audio output device connected to the display device 200, the display device 200 may also be provided with an external audio output terminal, and the audio output device can be connected to the display device 200 through the external audio output terminal to output the sound of the display device 200.

[0063] In some embodiments, the memory 290 can be used to store various required data, such as the blacklist and whitelist mentioned below, so that the controller 250 can directly obtain the blacklist and whitelist from the memory 290, and further determine the AIoT client's status on the blacklist or whitelist.

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

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

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

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

[0068] The controller 110 includes a processor 112, a RAM (Random Access Memory) 113, a ROM (Read-Only Memory) 114, a communication interface 130, and a communication bus. The controller 110 is used to control the operation and operation of the control device 100, as well as the communication and cooperation between the internal components and the external and internal data processing functions.

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

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

[0071] In some embodiments, the control device 100 includes at least one of a communication interface 130 and an input / output interface 140. The communication interface 130 is configured in the control device 100, such as modules for WiFi, Bluetooth, NFC, etc., which can encode the user input instructions through the WiFi protocol, or the Bluetooth protocol, or the NFC protocol and send them to the display device 200.

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

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

[0074] In order to perform user interaction, in some embodiments, the display device 200 may run an operating system. The operating system is a computer program used to manage and control the hardware resources and software resources in the display device 200. The operating system can (control the display device) provide a user interface, allowing the user to interact with the display device 200 and supporting the running of various application programs.

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

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

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

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

[0079] As Figure 4 shown, in this application, the application framework layer includes a view system, managers, content providers, etc. Among them, the view system can design and implement the interfaces and interactions of applications. The view system includes lists, grids, text boxes, buttons, etc. The managers include at least one of the following modules: The activity manager is used to interact with all the activities running in the system; the location manager is used to provide access to the system location service for system services or applications; the package manager is used to retrieve various information related to the application packages currently installed on the device; the notification manager is used to control the display and clearing of notification messages; the window manager is used to manage the icons, windows, toolbars, wallpapers, and desktop widgets on the user interface.

[0080] In some embodiments, the activity manager is used to manage the life cycles of various applications and the usual navigation back functions, such as controlling the exit, opening, and backward movement of applications. 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 the changes of the display window. For example, shrinking the display window, jittering the display, distorting the display, etc.

[0081] 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 libraries included in the system runtime layer, such as C / C++ instruction libraries, to implement the functions that the framework layer needs to achieve.

[0082] 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. For example, as Figure 4As shown in the figure, hardware drivers can be configured in the kernel layer. The drivers included in the kernel layer can 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.

[0083] It should be noted that the above examples are only simple divisions of the functions of the operating system, and do not limit the specific form of the operating system of the display device 200 in this application. According to factors such as the functions of the display device and the type of the operating system, the number of levels and the specific level types included in the operating system can be in other forms.

[0084] In the scenario of controlling the display device 200 through the AIoT client, it is necessary to pre-grant the management permission to the AIoT client on the display device 200. During the authorization process, the display device 200 will respond to the connection request initiated by the AIoT client and display an authorization page for the user to perform connection confirmation or cancellation operations as needed. However, the following adverse effects may exist in the above process:

[0085] (1) When the user makes continuous incorrect operations on the AIoT client. For example, the user does not want the AIoT client to establish a connection with the display device 200, but makes an incorrect operation on the AIoT client, resulting in the AIoT client mistakenly initiating a connection request to the display device 200. For this reason, the user needs to perform a cancellation operation on the authorization page displayed by the display device 200. If multiple incorrect operations occur continuously, the display device 200 will display the authorization page multiple times. Correspondingly, the user needs to perform multiple cancellation operations associated in the display device 200.

[0086] (2) When the AIoT client is attacked by hackers. For example, when malicious code is implanted on the AIoT client, the AIoT client will continuously initiate connection requests to the display device 200, and the display device 200 continuously responds to the connection requests and displays the authorization page, causing the user to need to frequently perform cancellation operations on different authorization pages, which brings trouble to the user.

[0087] To solve the above problems, after the user performs a cancellation operation on the authorization page, the display 260 can be controlled to not display the authorization page within a certain period of time, so as to reduce the situation where the display 260 continuously displays the authorization page due to incorrect operations or being attacked by hackers, thereby reducing the trouble brought to the user by frequently dealing with the authorization page.

[0088] In some alternative embodiments, referring to Figure 5A , a page display method is provided, which is applied to the controller 250 in the display device 200 and includes:

[0089] S510, receiving a connection request initiated by an AIoT client.

[0090] Among them, the AIoT client is an application directly operated by a user in the artificial intelligence of things (AIoT) architecture. It can connect to Internet of Things devices and AI technology to achieve device management, data interaction, intelligent control, and scenario-based services. The AIoT client can be applied in scenarios such as smart home, smart city, industrial Internet of Things, and health care. In the smart home scenario, devices such as lights, curtains, and household appliances can be controlled through the AIoT client to achieve home automation. In the smart city scenario, public transportation and environmental monitoring data can be queried through the AIoT client, or urban governance can be participated in (such as reporting faults of public facilities). In the industrial Internet of Things scenario, the operation status of devices can be monitored, fault warnings can be received, and production processes can be optimized through the AIoT client. In the health care scenario, health data can be viewed, remote diagnoses can be made, or treatment plans can be adjusted through the AIoT client of wearable devices.

[0091] Among them, the carrier of the AIoT client can be terminal devices such as smartphones, smart speakers, and central control panels, which integrate hardware resources such as processors, sensors, and communication modules. For example, the AIoT client can be deployed on Figure 1 the mobile terminal 300.

[0092] In an actual scenario, when a user needs to manage and control the display device 200 through the AIoT client, the display device 200 needs to authorize the AIoT client first, that is, a connection needs to be established between the display device 200 and the AIoT client first. At this time, the AIoT client responds to the user operation and initiates a connection request to the display device 200; correspondingly, the controller 250 in the display device 200 receives and responds to the connection request.

[0093] It can be understood that after the AIoT client and the display device 200 successfully establish a connection, the user can manage and control the display device 200 through the AIoT client. For example, switch the installed applications on the display device 200.

[0094] S520, when the request time of the connection request exceeds the page display time limit corresponding to this connection request, display an authorization page.

[0095] Among them, the request time of the connection request refers to the time when the AIoT client initiates the connection request.

[0096] Exemplarily, when the request time of the current connection request exceeds the page display time limit corresponding to the current connection request, the controller 250 will control the display 260 to display an authorization page for the user to make an authorization response.

[0097] Among them, referring to Figure 5B , there can be multiple options on the authorization page: at least one of agreeing to connect, rejecting to connect, canceling the connection, etc. If it is detected that the user selects the option of canceling the connection, it is considered that the user has performed a cancellation operation. Based on at least one option on the authorization page, the user can make a selection as needed, so that the controller 250 can implement corresponding connection control management according to the user's selection.

[0098] Among them, there are multiple ways to display the authorization page. For example, in the form of a pop-up window, a floating page, a fade-in / fade-out method, a scrolling method, a method of directly using a specific display area of the display 260 as the authorization page to display each option, etc. Of course, there are other ways, which are not limited here.

[0099] Among them, the page display time limit corresponding to the connection request is used to characterize the display limit time of the authorization page corresponding to the connection request. That is, the authorization page cannot be displayed again within this display limit time.

[0100] Exemplarily, the time length of the page display time limit corresponding to the connection request can be determined based on the number of requests corresponding to the connection request, the authorization response duration of the user before this connection request, or the authorization response operation of the user before this connection request, etc.

[0101] Optionally, the page display time limit corresponding to the current connection request is determined by the number of consecutive cancellations corresponding to the previous connection request, and the page display time limit corresponding to the current connection request is positively correlated with the number of consecutive cancellations corresponding to the previous connection request. That is, the more the number of consecutive cancellations corresponding to the previous connection request, the longer the page display time limit corresponding to the current connection request, and the starting time of the page display time limit corresponding to the current connection request is the moment when the user selects the cancellation operation during the previous connection process.

[0102] Exemplarily, during the previous connection process, after the user selects the cancellation operation, the counted number of consecutive cancellations is 2 times, and the page display time limit corresponding to 2 times is 15 minutes. Therefore, the page display time limit corresponding to the current connection request is 15 minutes. At this time, taking the moment when the user selects the cancellation operation during the previous connection process as the starting time, when the duration between the request time of the current connection request and the above starting time exceeds 15 minutes, the controller 250 controls the display 260 to display the authorization page.

[0103] S530: When the request time of the connection request does not exceed the page display time limit corresponding to this connection request, the authorization page is not displayed.

[0104] When the request time of the connection request does not exceed the page display time limit corresponding to this connection request, the controller 250 controls the display 260 not to display the authorization page, that is, prohibits the display 260 from displaying the authorization page.

[0105] Exemplarily, in the previous connection process, after the user selects the cancel operation, the counted consecutive cancellation times are 3 times. Therefore, the page display time limit corresponding to this connection request is 30 minutes. Moreover, starting from the moment when the user selected the cancel operation in the previous connection process as the time origin, when the duration between the request time of this connection request and the time origin does not exceed 30 minutes, the controller 250 controls the display 260 not to display the authorization page. It can be seen that within 30 minutes after the moment when the user performs the cancel operation in the previous connection process, the display device 200 cannot display the authorization page, that is, the display time interval of the authorization page is increased, thereby reducing the number of times the user needs to manually perform the cancel operation, reducing the trouble brought to the user due to misoperation or hacker attack, and thus improving the user experience.

[0106] S540: In response to a cancel operation on the authorization page, count the consecutive cancellation times, determine the page display time limit corresponding to the next connection request according to the consecutive cancellation times, and prohibit establishing a connection with the AIoT client; wherein, the duration of the page display time limit corresponding to the next connection request is positively correlated with the consecutive cancellation times.

[0107] Exemplarily, the process of counting the consecutive cancellation times may include: presetting the consecutive cancellation times statistical parameter, and when the cancel operation appears for the first time, the parameter value of this statistical parameter is incremented by 1; when the cancel operation appears continuously, the statistical parameter continues to accumulate; after the cancel operation appears continuously, when a non-cancel operation appears, the parameter value of this statistical parameter is cleared to 0. Correspondingly, in response to a cancel operation on the authorization page, obtain the parameter value of this statistical parameter to determine the consecutive cancellation times.

[0108] Wherein, the duration of the page display time limit corresponding to the next connection request is positively correlated with the consecutive cancellation times obtained this time. The so-called positive correlation means that: the more consecutive cancellation times obtained this time, the greater the duration of the page display time limit corresponding to the next connection request. The relationship between the two can be a linear relationship or a non-linear relationship.

[0109] As an example of a linear relationship, if the number of consecutive cancellations obtained from this statistics is 1, then the page display time limit corresponding to the next connection request can be 5 minutes. If the number of consecutive cancellations obtained from this statistics is 2, then the page display time limit corresponding to the next connection request can be 10 minutes. If the number of consecutive cancellations obtained from this statistics is 3, then the page display time limit corresponding to the next connection request can be 15 minutes.

[0110] As an example of a non-linear relationship, if the number of consecutive cancellations obtained from this statistics is 1, then the page display time limit corresponding to the next connection request can be 5 minutes. If the number of consecutive cancellations obtained from this statistics is 2, then the page display time limit corresponding to the next connection request can be 15 minutes. If the number of consecutive cancellations obtained from this statistics is 3, then the page display time limit corresponding to the next connection request can be 30 minutes.

[0111] Since for this connection request, in the case where the user performs a cancellation operation, the controller 250 of the display device 200 will prohibit the display device 200 from establishing a connection with the AIoT client. Of course, in order for the user to clearly understand the result of this connection request, the controller 250 can control the display 260 to display a message reminder of connection failure.

[0112] It should be noted that the controller 250 prohibiting the display device 200 from establishing a connection with the AIoT client can be that the controller 250 prohibits the communication device 220 in the display device 200 from establishing a communication connection with the AIoT client. Similarly, the controller 250 controlling the display device 200 to establish a connection with the AIoT client can be that the controller 250 controls the communication device 220 in the display device 200 to establish a communication connection with the AIoT client.

[0113] In the above optional embodiment, the controller 250 can determine the page display time limit corresponding to the next connection request based on the number of consecutive cancellations obtained in this statistics. In this way, when the user initiates the next connection request to the display device 200 on the AIoT client, the controller 250 controls whether the display 260 displays the authorization page based on the page display time limit corresponding to the next connection request. When the request time of the next connection request does not exceed the page display time limit corresponding to the next connection request, the controller 250 controls the display 260 not to display the authorization page, and the page display time limit corresponding to the next connection request is positively correlated with the number of consecutive cancellations obtained in this statistics. Whether it is multiple misoperations of the user or encountering hacker attacks, the user does not want the AIoT client to connect to the display device, and the above technical solution can increase the display time interval of the authorization page, that is, reduce the display frequency of the authorization page, reduce the number of times the user needs to manually cancel the operation, reduce the trouble caused to the user due to misoperation or hacker attacks, and thus improve the user experience.

[0114] Based on the technical solutions of the above embodiments, in some embodiments, another page display method is provided. Figure 6A , the method comprising:

[0115] S610A, if no user operation is detected within a preset time after the authorization page is displayed, close the authorization page, and set the page display time limit corresponding to the next connection request to a first time limit, which is less than the page display time limit determined when canceling the operation.

[0116] Exemplarily, when no user operation is detected within a preset time after the controller 250 controls the display 260 to display the authorization page, the controller 250 controls the display 260 to close the authorization page, and the controller 250 sets the page display time limit corresponding to the next connection request to the first duration.

[0117] The preset time can be set as needed, for example, 60 seconds. As an example, if no user operation is detected within 60 seconds when the display 260 displays the authorization page, the controller 250 controls the display 260 to close the authorization page.

[0118] The page display time limit determined when the cancel operation is selected is, for example, the 5 minutes, 15 minutes, 30 minutes, 45 minutes, etc. mentioned above. The first time length is shorter than the page display time length when the user selects the cancel operation, for example, the first time length can be set to 1 minute, 2 minutes, 3 minutes, etc. The advantage of setting the first time length in this way is that it can reduce the impact on subsequent connection requests when the user does not have time to operate.

[0119] To further reduce the impact on subsequent connection requests, the first duration can be set to 0 minutes. In this way, if the user does not select any option on the authorization page during a connection process, the display 260 can immediately display the authorization page when the user makes a request to connect next time, thus having no impact on the next connection request.

[0120] In some embodiments, the foregoing determining the page display time limit corresponding to the next connection request according to the consecutive cancellation times may include: when the consecutive cancellation times are less than a preset number of times, determining the page display time limit corresponding to the next connection request according to the consecutive cancellation times.

[0121] Among them, the preset number of times can be set as needed. For example, it can be set to 3 times, 5 times, or 10 times.

[0122] It can be seen that this application allows users to have a small number of misoperations, which enables the display device 200 to have a certain fault tolerance. Moreover, since a small number of hacker attacks have little impact on security, the security is guaranteed to a certain extent.

[0123] It can be understood that when the consecutive cancellation times are less than the preset number of times, the controller 250 can determine the page display time limit corresponding to the next connection request according to the consecutive cancellation times. In this way, although the authorization page cannot be displayed again within a certain period of time, after a certain period of time, if the user does not stop the misoperation behavior on the AIoT client, or the AIoT client is still in the state of being attacked by hackers, the display 260 will still display the authorization page. In this case, the user still needs to perform a cancellation operation on the display device 200, which still causes trouble to the user, and there are security risks for too many hacker attacks.

[0124] To solve the above problems, in some embodiments, refer to Figure 6B , a method for updating the blacklist is further provided, including:

[0125] S610B, when the consecutive cancellation times are greater than or equal to the preset number of times, prohibit establishing a connection with the AIoT client and add the AIoT client to the blacklist.

[0126] If the number of consecutive cancellations is greater than or equal to the preset number, the controller 250 will add the AIoT client to the blacklist, so that the authorization page will not be displayed again after the AIoT client initiates a connection request again. That is, after the number of consecutive cancellations reaches a certain number, no matter how long it takes, even if the AIoT client initiates a connection request again, the display 260 will not display the authorization page again, so that the user does not have to cancel the operation on the authorization page, which reduces the trouble to the user, thereby improving the user experience, and at the same time can reduce the security risks caused by too many hacker attacks.

[0127] In some optional embodiments, in addition to prohibiting the display device 200 from establishing a connection with the AIoT client, the controller 250 may also control the display 260 to display a message indicating a connection failure.

[0128] In some embodiments, for an authorization page with a deny connection option, see Figure 6C , another blacklist update method is also provided, including:

[0129] S610C, in response to the connection rejection operation on the authorization page, prohibiting establishment of a connection with the AIoT client, and adding the AIoT client to a blacklist.

[0130] The operation of the user selecting any option on the authorization page of the display device 200 can be implemented through the control device 100. For example, the user selects the option of rejecting the connection on the authorization page of the display device 200 through a remote control or a handle.

[0131] It is worth noting that the "Reject Connection" option on the authorization page can be understood as a "Disagree to Connection" option, not only for the current connection request of the AIoT client, but for all the connection requests of the AIoT client this time and thereafter. The "Cancel" option on the authorization page is a "Cancel" option for the current connection request of the AIoT client. This is the difference between the two options.

[0132] It can be seen that if the user selects the "Reject Connection" option on the authorization page, the display device 200 will be prohibited from establishing a connection with the AIoT client for this connection request. At the same time, the AIoT client is added to the blacklist, so that the display device 200 will be prohibited from establishing a connection with the AIoT client for subsequent connection requests from the AIoT client. The AIoT client will no longer be troubled by misoperation or hacker attacks, and the security risks caused by hacker attacks on the AIoT client are also avoided.

[0133] Based on the above description, the formation methods of the blacklist include at least one of the following: the AIoT client is added to the blacklist due to the number of consecutive cancellations being greater than or equal to the preset number; the AIoT client is added to the blacklist because the user selects the reject connection option on the authorization page; the user adds the AIoT client to the blacklist on the display device 200 as needed. For example, if the user does not want a certain AIoT client to control the display device 200, the user can actively add the AIoT client to the blacklist. In addition to the self - addition operation, the user can also perform maintenance operations such as removing and renaming the AIoT clients in the blacklist.

[0134] Based on the above blacklist, when the request time of the connection request exceeds the page display time limit corresponding to the current connection request, the step of displaying the authorization page may include: when the request time of the connection request exceeds the page display time limit corresponding to the current connection request and the AIoT client does not belong to the blacklist, controlling the display to display the authorization page; when the AIoT client belongs to the blacklist, prohibiting the establishment of a connection with the AIoT client.

[0135] Exemplarily, after receiving the current connection request initiated by the AIoT client, the controller 250 can first determine whether the AIoT client belongs to the blacklist. Optionally, if it belongs to the blacklist, the establishment of a connection with the AIoT client is prohibited, or further, the controller 250 controls the display 260 to prompt a message reminder of connection failure. Or optionally, if it does not belong to the blacklist, the controller 250 can determine whether the request time of the current connection request exceeds the page display time limit corresponding to the current connection request. If it exceeds, the controller 250 controls the display 260 to display the authorization page. Further, if it does not exceed, the controller 250 controls the display 260 not to display the authorization page.

[0136] It can be seen that the AIoT clients in the blacklist are actually the AIoT clients that the display device 200 explicitly does not authorize. By using the blacklist to manage the AIoT clients that are explicitly not authorized, in the scenario where the AIoT client requests to connect to the display device 200, the AIoT clients that are explicitly not authorized can be quickly excluded.

[0137] In some embodiments, for the authorization page with an option to agree to connect, see Figure 6D , a method for updating the whitelist is also provided, including:

[0138] S610D, in response to the operation of agreeing to connect on the authorization page, establishing a connection with the AIoT client and adding the AIoT client to the whitelist.

[0139] Among them, the consent connection option on the authorization page refers to the option for the user to consent to all connection requests in this and subsequent times.

[0140] It can be understood that if the user selects the consent connection option, it means that the user consents to the connection request of the AIoT client to the display device 200. Therefore, the controller 250 controls the display device 200 to establish a connection with the AIoT client. Further, after the connection is successful, the controller 250 can also control the display 260 to prompt a message reminder of successful connection. Moreover, since the user selects the consent connection option, it indicates that the user grants the AIoT client the control and management permission for the display device 200. Therefore, the AIoT client can be added to the whitelist, so that for subsequent connection requests, it can be determined whether the AIoT client initiating the connection request has the control and management permission for the display device 200 based on the whitelist.

[0141] Based on the above whitelist, when the request time of the connection request exceeds the page display time limit corresponding to this connection request, the step of displaying the authorization page may include: when the request time of the connection request exceeds the page display time limit corresponding to this connection request and the AIoT client does not belong to the whitelist, controlling the display to display the authorization page; when the AIoT client belongs to the whitelist, establishing a connection with the AIoT client.

[0142] Exemplarily, after receiving the current connection request initiated by the AIoT client, the controller 250 can first determine whether the AIoT client belongs to the whitelist. Optionally, if it belongs to the whitelist, the controller 250 can control the display device 200 to establish a communication connection with the AIoT client. Further, after the connection is successful, the controller 250 can also control the display 260 to prompt a message reminder of successful connection. Or optionally, if it does not belong to the whitelist, the controller 250 can determine whether the request time of the current connection request exceeds the page display time limit corresponding to this connection request. If it exceeds, control the display 260 to display the authorization page. Further, if it does not exceed, the controller 250 controls the display 260 not to display the authorization page.

[0143] It can be seen that if an AIoT client belongs to the whitelist, when the AIoT client initiates a connection request, the display device 200 directly establishes a connection with the AIoT client, without the need to determine whether the request time of this connection request exceeds the page display time limit corresponding to this connection request. In other words, the AIoT clients in the whitelist are actually AIoT clients authorized by the display device 200. By implementing the management of the AIoT clients authorized by the display device 200 through the whitelist, in the scenario where the AIoT client requests to connect to the display device 200, the AIoT clients authorized by the display device 200 can quickly establish a connection with the display device 200.

[0144] In an actual scenario, both a whitelist and a blacklist may exist in the display device 200. At this time, after receiving the current connection request initiated by the AIoT client, the controller 250 can first determine whether the AIoT client belongs to the whitelist and the blacklist, and there are the following three situations:

[0145] (1) The AIoT client belongs to the whitelist, and the display device 200 will establish a connection with the AIoT client. After the connection is successful, the controller 250 can also control the display 260 to prompt a message indicating that the connection is successful;

[0146] (2) The AIoT client belongs to the blacklist, and the display device 200 is prohibited from establishing a connection with the AIoT client. Further, the controller 250 can also control the display 260 to prompt a message indicating that the connection fails;

[0147] (3) The AIoT client does not belong to the whitelist and does not belong to the blacklist. The controller 250 can determine whether the request time of this connection request exceeds the page display time limit corresponding to this connection request. If it exceeds, it controls the display 260 to display an authorization page. If it does not exceed, it controls the display 260 not to display an authorization page.

[0148] It can be seen that by implementing the management of the AIoT clients authorized by the display device 200 through the whitelist, and implementing the management of the AIoT clients that are clearly not authorized through the blacklist, in the scenario where the AIoT client requests to connect to the display device 200, the AIoT clients authorized by the display device 200 can quickly establish a connection with the display device 200, and the AIoT clients that are clearly not authorized can be quickly excluded.

[0149] In some embodiments, when the request time of the connection request exceeds the page display time limit corresponding to this connection request, the step of controlling the display to display the authorization page may include: when this connection request is not the first connection request initiated by the AIoT client, and the request time of the connection request exceeds the page display time limit corresponding to this connection request, controlling the display to display the authorization page; when this connection request is the first connection request initiated by the AIoT client, controlling the display to display the authorization page.

[0150] It can be seen that if this connection request is the first connection request initiated by the AIoT client, the controller 250 will control the display 260 to display the authorization page immediately. If this connection request is not the first connection request initiated by the AIoT client, the controller 250 will determine whether the request time of this connection request exceeds the page display time limit corresponding to this connection request. If it exceeds, the controller 250 controls the display 260 to display the authorization page; if it does not exceed, the controller 250 controls the display 260 not to display the authorization page. Therefore, whether it is a connection request initiated for the first time or a connection request not initiated for the first time, the method provided in this application can be used to determine whether to establish a connection between the AIoT client and the display device 200.

[0151] In actual scenarios, in addition to carrying the relevant identity of the AIoT client, the connection request initiated by the AIoT client may also carry a key, which is issued by the provider of the AIoT client. When the display device 200 receives the connection request, the controller 250 can verify whether the connection request carries a key. If it carries a key, the connection request is legal. Only for legal connection requests will it be decided whether to establish a connection between the display device 200 and the AIoT client based on S110~S140. For illegal connection requests, S110~S140 will not be executed. In this way, the security of the connection can be improved.

[0152] In some embodiments, see Figure 7 , explaining the interaction process between the display device and the AIoT client:

[0153] S710, the AIoT client initiates a connection request to the display device;

[0154] S720, the controller checks whether the AIoT client that initiates this connection request belongs to the whitelist and blacklist;

[0155] S720A, when the AIoT client initiating this connection request belongs to the whitelist, the controller controls to establish a connection with the AIoT client;

[0156] S720B. When the AIoT client that initiates this connection request is on the blacklist, the controller prohibits establishing a connection with the AIoT client.

[0157] S720C. When the AIoT client that initiates this connection request is neither on the whitelist nor on the blacklist, the controller determines whether the request time of this connection request exceeds the page display time limit corresponding to this connection request; then continue to execute S730A or S730B.

[0158] S730A. When the request time of this connection request does not exceed the page display time limit corresponding to this connection request, the controller controls the display to not show the authorization page.

[0159] S730B. When the request time of this connection request exceeds the page display time limit corresponding to this connection request, the controller controls the display to show the authorization page; then continue to execute S740A, S740B, S740C or S740D.

[0160] S740A. In response to a cancel operation on the authorization page, count the consecutive cancellation times; when the consecutive cancellation times are less than the preset times, determine the page display time limit corresponding to the next connection request according to the consecutive cancellation times, and prohibit establishing a connection with the AIoT client; when the consecutive cancellation times are greater than or equal to the preset times, prohibit establishing a connection with the AIoT client and add the AIoT client to the blacklist.

[0161] S740B. When no user operation is detected within the preset time after controlling the display to show the authorization page, the controller controls the display to close the authorization page and sets the page display time limit corresponding to the next connection request to the first duration, and the first duration is less than the page display time limit determined in the case of selecting the cancel operation.

[0162] S740C. In response to a reject connection operation on the authorization page, the controller prohibits the display device from establishing a connection with the AIoT client and adds the AIoT client to the blacklist.

[0163] S740D. In response to an accept connection operation on the authorization page, the controller controls the display device to establish a connection with the AIoT client and adds the AIoT client to the whitelist.

[0164] Based on the above process, whether it is due to multiple accidental operations by the user or a hacker attack, in the case where the user does not want to establish a connection between the display device and the AIoT client, by increasing the display time interval of the authorization page, that is, reducing the display frequency of the authorization page, the number of times the user needs to perform a manual cancellation operation is reduced, and the trouble brought to the user due to accidental operations or hacker attacks is reduced, thereby improving the user experience.

[0165] In some embodiments, after a successful connection is established between the AIoT client and the display device 200, the user can use the AIoT client to manage and control the display device 200. For example, perform a switching operation on the applications on the display device 200. Refer to Figure 8 , a method for the AIoT client to perform application switching on the display device, includes the following steps:

[0166] S810, after successfully connecting to the display device, provide a configuration page, and the configuration page has a package name configuration item for the application to be switched.

[0167] Among them, the English of the package name is Package Name, which is a string used to uniquely identify an application program, similar to an ID number, ensuring the uniqueness of each application in the system. The package name plays a crucial role in application development, release, and management.

[0168] Among them, the application to be switched refers to the application that the display device is to switch to.

[0169] In an actual scenario, the user can view the standard package name of the application to be switched in the applications in the settings menu of the display device 200. After learning the standard package name, the user can configure the package name of the application to be switched on the package name configuration item in the configuration page of the AIoT client.

[0170] S820, according to the package name, control the display device to switch to the application to be switched.

[0171] It can be seen that the AIoT client can control the display device 200 to switch to the application to be switched based on the package name, so that the display device 200 enters the page of the application to be switched.

[0172] It is understandable that the above steps S810 and S820 are both executed by the AIOT client.

[0173] In some embodiments, a blacklist may be set. The blacklist here is different from the blacklist of the AIoT client in the above text. The blacklist of the AIoT client in the above text may be referred to as the first blacklist, and the blacklist here may be referred to as the second blacklist. The second blacklist is used to store the blacklist of applications that are not desired to be switched through the AIoT client. For example, special applications such as the factory mode App (Application) and the mall mode App are stored in the second blacklist. The so-called factory mode App refers to an application that sets the factory information such as the language and country of the display device 200 at the time of factory shipment. The so-called mall mode App refers to an application that displays videos of goods in a mall. These two applications are used in abnormal scenarios. Therefore, in a normal home scenario, it is not desired to switch to these two applications through the AIoT client. Therefore, these two applications are added to the second blacklist.

[0174] In some embodiments, in the second blacklist, in addition to the factory mode App and the mall mode App, other applications that are not desired to be switched through the AIoT client may also be set. The second blacklist does not have to be prefabricated by the manufacturer of the display device 200. The user can set it by himself, that is, the user can perform maintenance operations such as adding applications, deleting applications, and editing names on the second blacklist.

[0175] Based on the above second blacklist, before executing S820, it can be checked whether the application to be switched belongs to the second blacklist. If it belongs to the second blacklist, the application cannot be switched, and information indicating that the switch cannot be performed can be prompted on the AIoT client, so as to prohibit special applications from being called and switched by the AIoT client. If it does not belong to the second blacklist, S820 will be executed, so that the display device 200 switches to the application to be switched.

[0176] Among them, since the package name is the unique identifier of the application, the package names of the applications are recorded in the second blacklist.

[0177] In some embodiments, the user only needs to configure the package name of the application to be switched to achieve the switching of the application on the display device 200 through the AIoT client. Since the package name can be queried and obtained on the display device 200, the package name is relatively easy to obtain. Furthermore, the application switching process is also easy to implement. Since the switching difficulty is reduced, ordinary users can achieve application switching. Moreover, except for the applications recorded in the second blacklist, other applications on the display device 200 can be used as the application to be switched. The other applications can be downloaded and installed by the user in the application store of the display device 200, or can be downloaded and installed by the user through other channels. The scope of applicable applications is relatively wide, and the user has more options and is not limited to certain fixed applications.

[0178] Based on the same inventive concept, in some embodiments, a page display device for implementing the above-mentioned page display method is also provided. The solution provided by this device for solving problems is similar to the solution described in the above method. Therefore, the specific limitations in one or more embodiments of the page display device provided below can refer to the limitations on the page display method in the foregoing text, and will not be elaborated here.

[0179] In an exemplary embodiment, as Figure 9 shown, a page display device is provided, including: a request receiving module 910, a first control module 920, a second control module 930, and a time limit determination module 940; wherein:

[0180] The request receiving module 910 is configured to receive a connection request initiated by an artificial intelligence Internet of Things (AIoT) client.

[0181] The first control module 920 is configured to control the display to display an authorization page when the request time of the connection request exceeds the page display time limit corresponding to the current connection request.

[0182] The second control module 930 is configured to control the display not to display an authorization page when the request time of the connection request does not exceed the page display time limit corresponding to the current connection request.

[0183] The time limit determination module 940 is configured to, in response to a cancellation operation on the authorization page, count the number of consecutive cancellations, and determine the page display time limit corresponding to the next connection request according to the number of consecutive cancellations, and prohibit establishing a connection with the AIoT client; wherein, the duration of the page display time limit corresponding to the next connection request is positively correlated with the number of consecutive cancellations.

[0184] In some embodiments, the device further includes: a third control module, configured to, when no user operation is detected within a preset time after controlling the display to display the authorization page, control the display to close the authorization page, and set the page display time limit corresponding to the next connection request to a first duration, and the first duration is less than the page display time limit determined in the case of selecting a cancellation operation.

[0185] In some embodiments, the first control module is specifically configured to: when the number of consecutive cancellations is less than a preset number, determine the page display time limit corresponding to the next connection request according to the number of consecutive cancellations.

[0186] In some embodiments, the device further includes: a first addition module, configured to, when the number of consecutive cancellations is greater than or equal to the preset number, prohibit establishing a connection with the AIoT client, and add the AIoT client to the blacklist.

[0187] In some embodiments, the device further includes: a second adding module, configured to prohibit establishing a connection with the AIoT client and add the AIoT client to a blacklist in response to a reject connection operation on the authorization page.

[0188] In some embodiments, the first control module is specifically configured to: control the display to display an authorization page when the request time of the connection request exceeds the page display time limit corresponding to the current connection request and the AIoT client does not belong to the blacklist; prohibit establishing a connection with the AIoT client when the AIoT client belongs to the blacklist.

[0189] In some embodiments, the device further includes: a third adding module, configured to establish a connection with the AIoT client and add the AIoT client to a whitelist in response to an accept connection operation on the authorization page.

[0190] In some embodiments, the first control module is specifically configured to: control the display to display an authorization page when the request time of the connection request exceeds the page display time limit corresponding to the current connection request and the AIoT client does not belong to the whitelist; establish a connection with the AIoT client when the AIoT client belongs to the whitelist.

[0191] In some embodiments, the first control module is specifically configured to: control the display to display an authorization page when the current connection request is a non-first connection request initiated by the AIoT client and the request time of the connection request exceeds the page display time limit corresponding to the current connection request; control the display to display an authorization page when the current connection request is a first connection request initiated by the AIoT client.

[0192] Each module in the above page display device can be implemented in whole or in part by software, hardware, and their combination. Each of the above modules can be embedded in or independent of a processor in a computer device in the form of hardware, or stored in a memory in the computer device in the form of software, so as to facilitate the processor to call and execute the operations corresponding to each of the above modules.

[0193] In an exemplary embodiment, a computer device is provided. The computer device may be a terminal, and its internal structural diagram may be as Figure 10As shown in the figure. The computer device includes a processor, a memory, an input / output interface, a communication interface, a display unit, and an input device. Among them, the processor, the memory, and the input / output interface are connected through a system bus, and the communication interface, the display unit, and the input device are connected to the system bus through the input / output interface. Among them, 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 computer programs. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and external devices. The communication interface of the computer device is used to communicate with external terminals 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, it implements a page display method. 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. The input device of the computer device can be a touch layer covered on the display screen, or a button, a trackball, or a touchpad set on the computer device housing, or an external keyboard, touchpad, or mouse, etc.

[0194] Those skilled in the art can understand that Figure 10 the structure shown in the figure is only a block diagram of some structures 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 those shown in the figure, or combine some components, or have different component arrangements.

[0195] In an alternative embodiment, Figure 10 the computer device shown in the figure may be the aforementioned display device, for example, a smart TV.

[0196] In an exemplary embodiment, a computer device is provided, including a memory and a processor. A computer program is stored in the memory, and when the processor executes the computer program, the steps in the above method embodiments are implemented. In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by the processor, the steps in the above method embodiments are implemented.

[0197] In one embodiment, a computer program product is provided, including a computer program, and when the computer program is executed by the processor, the steps in the above method embodiments are implemented.

[0198] 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 for analysis, stored data, displayed data, etc.) involved in this application are all information and data that have been authorized by the user or fully authorized by all parties, and the collection, use, and processing of relevant data need to comply with relevant regulations.

[0199] Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be completed by instructing relevant hardware through a computer program. 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 methods. Among them, any reference to a memory, database, or other medium used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. 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), etc. The databases involved in the embodiments provided in this application can include at least one of relational databases and non-relational databases. Non-relational databases can include distributed databases based on blockchain, etc., without limitation. The processors involved in the embodiments provided in this application can be general-purpose processors, central processors, graphics processors, digital signal processors, programmable logic devices, data processing logics based on quantum computing, artificial intelligence (AI) processors, etc., without limitation.

[0200] The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity of description, 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, it should be considered as the scope recorded in this application.

[0201] The above embodiments only represent several implementation manners of this application, and the description thereof is relatively specific and detailed. However, it should not be construed as a limitation on the patent scope of this application. It should be noted that for those of ordinary skill in the art, without departing from the concept of this application, several modifications and improvements can still be made, and these all belong to the protection scope of this application. Therefore, the protection scope of this application shall be subject to the appended claims.

Claims

1. A display device, characterized in that, Including: A display configured to perform page display; At least one controller connected to the display and configured to: Receive a connection request initiated by an Artificial Intelligence of Things (AIoT) client; When the request time of the connection request exceeds the page display time limit corresponding to the current connection request, control the display to show an authorization page; When the request time of the connection request does not exceed the page display time limit corresponding to the current connection request, control the display not to show the authorization page; In response to a cancellation operation on the authorization page, count the consecutive cancellation times, determine the page display time limit corresponding to the next connection request according to the consecutive cancellation times, and prohibit establishing a connection with the AIoT client; wherein the duration of the page display time limit corresponding to the next connection request is positively correlated with the consecutive cancellation times.

2. The display device according to claim 1, wherein The controller is further configured to: When no user operation is detected within a preset time after controlling the display to show the authorization page, control the display to close the authorization page and set the page display time limit corresponding to the next connection request to a first duration, and the first duration is less than the page display time limit determined in the case of selecting the cancellation operation.

3. The display device according to claim 1, characterized in that, When the controller executes to determine the page display time limit corresponding to the next connection request according to the consecutive cancellation times, it is configured to: When the consecutive cancellation times are less than a preset number of times, determine the page display time limit corresponding to the next connection request according to the consecutive cancellation times.

4. The display device according to claim 3, wherein The controller is further configured to: When the consecutive cancellation times are greater than or equal to the preset number of times, prohibit establishing a connection with the AIoT client and add the AIoT client to the blacklist.

5. The display device according to any one of claims 1-4, characterized in that, The controller is further configured to: In response to a reject connection operation on the authorization page, prohibit establishing a connection with the AIoT client and add the AIoT client to the blacklist.

6. The display device according to any one of claims 1-4, characterized in that, When the controller executes to control the display to show the authorization page when the request time of the connection request exceeds the page display time limit corresponding to the current connection request, it is configured to: When the request time of the connection request exceeds the page display time limit corresponding to the current connection request and the AIoT client does not belong to the blacklist, control the display to show the authorization page; When the AIoT client belongs to the blacklist, prohibit establishing a connection with the AIoT client.

7. The display device according to any one of claims 1-4, characterized in that The controller is further configured to: In response to an accept connection operation on the authorization page, establish a connection with the AIoT client and add the AIoT client to the whitelist.

8. The display device according to any one of claims 1-4, characterized in that, When the controller executes to control the display to show the authorization page when the request time of the connection request exceeds the page display time limit corresponding to the current connection request, it is configured to: When the request time of the connection request exceeds the page display time limit corresponding to the current connection request and the AIoT client does not belong to the whitelist, control the display to show the authorization page; When the AIoT client belongs to the whitelist, establish a connection with the AIoT client.

9. The display device according to claim 1, wherein When the controller controls the display to show an authorization page when the request time of the connection request exceeds the page display time limit corresponding to the current connection request, it is configured to: When the current connection request is a non-first connection request initiated by the AIoT client and the request time of the connection request exceeds the page display time limit corresponding to the current connection request, control the display to show an authorization page; When the current connection request is the first connection request initiated by the AIoT client, control the display to show an authorization page.

10. A page display method, characterized in that, It includes: Receive a connection request initiated by an artificial intelligence Internet of Things (AIoT) client; When the request time of the connection request exceeds the page display time limit corresponding to the current connection request, control the display to show an authorization page; When the request time of the connection request does not exceed the page display time limit corresponding to the current connection request, control the display not to show an authorization page; In response to a cancellation operation on the authorization page, count the consecutive cancellation times, determine the page display time limit corresponding to the next connection request according to the consecutive cancellation times, and prohibit establishing a connection with the AIoT client; wherein, the duration of the page display time limit corresponding to the next connection request is positively correlated with the consecutive cancellation times.

Images