Display devices, servers, program execution methods, and storage media

Abstract

This application relates to a display device, a server, a program execution method, and a storage medium. The display device includes: in response to a trigger operation on an NFC sensing area of ​​a smart device, acquiring an NFC identifier corresponding to the NFC sensing area and a target device identifier; sending an information acquisition request to a server, the information acquisition request being used to request the server to acquire a target WiFi identifier that has a device association relationship with the target device identifier; receiving the target WiFi identifier returned by the server; acquiring multiple WiFi identifiers corresponding to a target local area network connected to the display device; if the target WiFi identifier is included among the multiple WiFi identifiers, determining that the display device has control authority over the smart device; if the display device has control authority over the smart device, sending a program query request to the server; receiving target program parameters returned by the server; and controlling the smart device to execute the target program based on the program parameters.

Description

Technical Field

[0001] This application relates to terminal technology. More specifically, it relates to a display device, a server, a program execution method, and a storage medium. Background Technology

[0002] Currently, smart devices with an NFC sticker or a built-in NFC module (hereinafter referred to as having an NFC sensing area) have NFC tap functionality. To enable NFC tap functionality, a display device first taps its NFC sensing area against the smart device's NFC sensing area. The display device then uses a smart home application (APP) installed on it to configure, bind, and associate the smart device with a specific program. Once the program is successfully associated, tapping the display device's NFC sensing area again will automatically execute the associated program. Therefore, NFC tap functionality is widely promoted as a market selling point.

[0003] However, when a display device logged into the smart home APP through account A (hereinafter referred to as account A) taps the NFC sensing area of ​​a smart device to complete the network configuration, binding, and association procedures, if a display device logged into the smart home APP through account B (hereinafter referred to as account B) needs to use the NFC tap function of the smart device, it is necessary to first delete the smart device already bound under account A (i.e., unbind the smart device from account A), and then account B must re-perform the network configuration, binding, and association procedures for the smart device.

[0004] NFC tap-to-pay functionality is touted as a key selling point, and store staff frequently guide customers to download a smart home app so they can experience the feature using their own phones. However, due to high customer traffic, each time this is done, staff must first remove the smart device from their own account and then guide the customer to re-configure, bind, and associate the device using their own account before the customer can use the NFC tap-to-pay function. Furthermore, because of the high volume of customers, after each experience, staff must remind customers to remove the device from their account and reset the NFC program, which is time-consuming, labor-intensive, negatively impacts the customer experience, and wastes the staff's time promoting the product. Summary of the Invention

[0005] To solve the above-mentioned technical problems, or at least partially solve them, embodiments of this application provide a display device, a server, a program execution method, and a storage medium.

[0006] In a first aspect, embodiments of this application provide a display device, including: a controller configured to: in response to a trigger operation on an NFC sensing area on a smart device, acquire an NFC identifier and a target device identifier corresponding to the NFC sensing area, wherein the NFC identifier is used to indicate the NFC sensing area and the target device identifier is used to indicate the smart device; a communicator configured to: send an information acquisition request to a server, wherein the information acquisition request carries the target device identifier, the information acquisition request being used to request the server to acquire a target WiFi identifier that has a device association relationship with the target device identifier, the target WiFi identifier being used to indicate the WiFi module of the smart device; and receive the target WiFi identifier returned by the server; the controller is further configured to: acquire multiple WiFi identifiers corresponding to a target local area network connected to the display device, each WiFi identifier... The communicator is configured to: identify a device currently connected to the target local area network; determine if the target WiFi identifier is included among the multiple WiFi identifiers; and, if the display device has control over the smart device, determine that the display device has control over the smart device. The communicator is further configured to: send a program query request to the server when the display device has control over the smart device. The program query request carries the NFC identifier, the target device identifier, and the target WiFi identifier. The program query request requests target program parameters, which are program parameters associated with the NFC identifier, the target device identifier, and the target WiFi identifier, and are used to execute the target program associated with the NFC sensing area; and receive the target program parameters returned by the server. The controller is further configured to: control the smart device to execute the target program based on the program parameters.

[0007] Secondly, embodiments of this application provide a server method, including: a communicator configured to: receive an information acquisition request from a display device, the information acquisition request being generated by the display device in response to a tap-to-tap operation on an NFC sensing area affixed to a smart device, the information acquisition request carrying a target device identifier corresponding to the NFC sensing area; a controller configured to: acquire a target WiFi identifier that has a device association relationship with the target device identifier based on the information acquisition request, the target WiFi identifier being used to indicate the WiFi module of the smart device; the communicator is further configured to: return the target WiFi identifier to the display device, so that the display device determines whether it has control over the smart device based on the target WiFi identifier. The controller is further configured to: receive a program query request from the display device, the program query request carrying the target device identifier, the target WiFi identifier, and the NFC identifier corresponding to the NFC sensing area, the program query request being generated by the display device after determining that the display device has control authority over the smart device; the controller is further configured to: obtain target program parameters according to the program query request, the target program parameters being program parameters that have a program association relationship with the NFC identifier, the target device identifier, and the target WiFi identifier, and are used to execute the target program associated with the NFC sensing area; the communicator is further configured to: return the target program parameters to the display device, so that the display device controls the smart device to execute the target program based on the program parameters.

[0008] Thirdly, embodiments of this application provide a program execution method applied to a display device, comprising: responding to a tap-to-tap operation on an NFC sensing area affixed to a smart device, acquiring an NFC identifier and a target device identifier corresponding to the NFC sensing area, wherein the NFC identifier is used to indicate the NFC sensing area and the target device identifier is used to indicate the smart device; sending an information acquisition request to a server, the information acquisition request carrying the target device identifier, the information acquisition request being used to request the server to acquire a target WiFi identifier that has a device association relationship with the target device identifier, the target WiFi identifier being used to indicate the WiFi module of the smart device; receiving the target WiFi identifier returned by the server; and acquiring multiple WiFi identifiers corresponding to a target local area network connected to the display device, each WiFi identifier being... The Fi identifier is used to indicate a device currently connected to the target local area network; if the target WiFi identifier is included among the multiple WiFi identifiers, it is determined that the display device has control over the smart device; if the display device has control over the smart device, a program query request is sent to the server. The program query request carries the NFC identifier, the target device identifier, and the target WiFi identifier. The program query request is used to request target program parameters, which are program parameters that have a program association relationship with the NFC identifier, the target device identifier, and the target WiFi identifier, and are used to execute the target program associated with the NFC sensing area; the target program parameters returned by the server are received; based on the program parameters, the smart device is controlled to execute the target program.

[0009] Fourthly, embodiments of this application provide a program execution method applied to a server, comprising: receiving an information acquisition request from a display device, the information acquisition request being generated by the display device in response to a tap-to-tap operation on an NFC sensing area affixed to a smart device, the information acquisition request carrying a target device identifier corresponding to the NFC sensing area; based on the information acquisition request, acquiring a target WiFi identifier that has a device association relationship with the target device identifier, the target WiFi identifier being used to indicate the WiFi module of the smart device; and returning the target WiFi identifier to the display device, so that the display device determines whether it has control over the smart device based on the target WiFi identifier. The system receives a program query request from the display device. The program query request carries the target device identifier, the target WiFi identifier, and the NFC identifier corresponding to the NFC sensing area. The program query request is generated by the display device after determining that it has control authority over the smart device. Based on the program query request, the system obtains target program parameters. The target program parameters are program parameters that have a program association relationship with the NFC identifier, the target device identifier, and the target WiFi identifier, and are used to execute the target program associated with the NFC sensing area. The system returns the target program parameters to the display device so that the display device controls the smart device to execute the target program based on the program parameters.

[0010] Fifthly, embodiments of this application provide a computer-readable storage medium, including: storing a computer program on the computer-readable storage medium, wherein when the computer program is executed by a processor, it implements the program execution method as shown in the second aspect.

[0011] In a sixth aspect, embodiments of this application provide a computer program product, including: when the computer program product is run on a computer, causing the computer to implement the program execution method as shown in the second aspect.

[0012] Compared with the prior art, the technical solution provided in this application has the following advantages: In this application embodiment, in response to the triggering operation of the NFC sensing area on the smart device, the NFC identifier and the target device identifier corresponding to the NFC sensing area are obtained. The NFC identifier is used to indicate the NFC sensing area, and the target device identifier is used to indicate the smart device. The communicator is configured to: send an information acquisition request to the server, the information acquisition request carrying the target device identifier, the information acquisition request being used to request the server to acquire a target WiFi identifier that has a device association relationship with the target device identifier, the target WiFi identifier being used to indicate the WiFi module of the smart device; receive the target WiFi identifier returned by the server; the controller is further configured to: acquire multiple WiFi identifiers corresponding to the target local area network connected to the display device, each WiFi... The identifier is used to indicate a device currently connected to the target local area network; if the target WiFi identifier is included among the multiple WiFi identifiers, it is determined that the display device has control over the smart device; the communicator is further configured to: if the display device has control over the smart device, send a program query request to the server, the program query request carrying the NFC identifier, the target device identifier, and the target WiFi identifier, the program query request being used to request target program parameters, the target program parameters being program parameters that have a program association relationship with the NFC identifier, the target device identifier, and the target WiFi identifier, and are used to execute the target program associated with the NFC sensing area; receive the target program parameters returned by the server; the controller is further configured to: control the smart device to execute the target program based on the program parameters.In this solution, in response to a trigger operation on the NFC sensing area of ​​the smart device, the display device requests a target WiFi identifier that is associated with the target device identifier from the server. Then, by verifying that the target WiFi identifier is included among multiple WiFi identifiers corresponding to the target local area network currently connected to the display device, it determines that the display device has control over the smart device. Finally, it requests the server to obtain target program parameters that are associated with the NFC identifier, the target device identifier, and the target WiFi identifier, and are used to execute the target program associated with the NFC sensing area. Based on the target program parameters returned by the server, the display device controls the smart device to execute the target program. Thus, by verifying whether the display device is connected to the same local area network as the smart device, it determines whether the display device has control over the smart device. If the display device has control over the smart device, it obtains the target program associated with the NFC sensing area. The target program parameters control the smart device to execute the target program. Therefore, if a customer wants to experience the NFC tap-to-connect function, they only need to bring their display device close to the NFC tag. This verifies whether the display device is connected to the local area network of the smart device, thus determining whether the display device has control permissions over the smart device. This eliminates the need to remind customers to delete the device from their account and reset the NFC program (unbinding the smart device from account A so that a new customer's account can bind the smart device) after each experience, and to change the binding relationship between the smart device and different smart home APP accounts. It also eliminates the need to transfer permissions between accounts; simply verifying that the customer's device is connected to the same local area network as the smart device simplifies the process of verifying whether the display device has control permissions over the smart device and the process of the display device controlling the smart device to execute associated programs via the NFC tap-to-connect function, thus improving the customer experience. Attached Figure Description

[0013] To more clearly illustrate the implementation methods in the embodiments of this application or related technologies, the accompanying drawings used in the description of the embodiments or related technologies will be briefly introduced below. Obviously, the accompanying drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings.

[0014] Figure 1 An operational scenario between a display device and a control device according to some embodiments is illustrated;

[0015] Figure 2 A hardware configuration block diagram of a control device 100 according to some embodiments is shown;

[0016] Figure 3 A hardware configuration block diagram of a display device 200 according to some embodiments is shown;

[0017] Figure 4 One of the interface diagrams of a program execution method according to some embodiments is shown;

[0018] Figure 5 A second schematic diagram of an interface for a program execution method according to some embodiments is shown;

[0019] Figure 6 The third schematic diagram of the interface for a program execution method according to some embodiments is shown;

[0020] Figure 7 One of the flowcharts illustrating a program execution method according to some embodiments is shown;

[0021] Figure 8 A second flowchart illustrating a program execution method according to some embodiments is shown;

[0022] Figure 9 A third flowchart illustrating a program execution method according to some embodiments is shown;

[0023] Figure 10 A fourth flowchart illustrating a program execution method according to some embodiments is shown;

[0024] Figure 11 The fifth flowchart illustrates a program execution method according to some embodiments. Detailed Implementation

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

[0026] It should be noted that the brief descriptions of terms in this application are only for the convenience of understanding the embodiments described below, and are not intended to limit the embodiments of this application. Unless otherwise stated, these terms should be understood in their ordinary and common meaning.

[0027] The terms "first," "second," "third," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar or related objects or entities, and do not necessarily imply a specific order or sequence, unless otherwise specified. It should be understood that such terms are interchangeable where appropriate.

[0028] The terms “comprising” and “having”, and any variations thereof, are intended to cover but not exclude inclusion, for example, a product or device that includes a range of components is not necessarily limited to all of the components that are clearly listed, but may include other components that are not clearly listed or that are inherent to such product or device.

[0029] The display device provided in this application can have various implementation forms, such as a television, a smart television, a laser projection device, a monitor, an electronic bulletin board, an electronic table, a mobile phone, a tablet computer, a laptop computer, a handheld computer, an in-vehicle electronic device, etc.

[0030] Figure 1 This is a schematic diagram illustrating an operational scenario between a display device and a control device according to an embodiment, wherein the control device 100 includes any device capable of controlling the display device. For example... Figure 1 As shown, users can operate the display device 200 via mobile phone or remote control.

[0031] In some embodiments, the control device 100 may be a remote control. Communication between the remote control and the display device includes infrared protocol communication, Bluetooth protocol communication, and other short-range communication methods, controlling the display device 200 wirelessly or via wired means. Users can control the display device 200 by inputting user commands through buttons on the remote control, voice input, control panel input, etc.

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

[0033] In some embodiments, the display device 200 can also be controlled in a manner other than a control device. For example, it can be controlled by directly receiving user voice commands through a module configured inside the display device 200 for acquiring voice commands, or it can be controlled by receiving user voice commands through a voice control device set outside the display device 200.

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

[0035] Figure 2 An exemplary block diagram of the configuration of the control device 100 according to an exemplary embodiment is shown. Figure 2 As shown, the control device 100 includes a controller 110, a communication interface 130, a user input / output interface 140, an external memory, and a power supply. The control device 100 can receive user input operation commands and convert the operation commands into commands that the display device 200 can recognize and respond to, thus acting as an intermediary for interaction between the user and the display device 200.

[0036] like Figure 3 The display device 200 includes at least one of the following: a tuner 210, a communicator 220, a detector 230, an external device interface 240, a controller 250, a display 260, an audio output interface 270, a user interface 280, an external memory, and a power supply.

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

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

[0039] The display 260 can be an LCD display, an OLED display, or a projection display, and can also be a projection device and a projection screen.

[0040] The communicator 220 is a component used to communicate with external devices or servers according to various communication protocol types. For example, the communicator may include at least one of the following: a Wi-Fi module, a Bluetooth module, a wired Ethernet module, other network communication protocol chips or near-field communication protocol chips, and an infrared receiver. The display device 200 can establish the transmission and reception of control signals and data signals with the external control device 100 or the server 400 through the communicator 220.

[0041] User interface 280 can be used to receive control signals from control device 100 (such as an infrared remote control). It can also be used to directly receive user input operation commands and convert the operation commands into commands that the display device 200 can recognize and respond to; in this case, it can be called a user input interface.

[0042] Detector 230 is used to collect signals from the external environment or to interact with the external environment. For example, detector 230 includes a light receiver, a sensor for collecting ambient light intensity; or, detector 230 includes an image acquisition device, such as a camera, which can be used to collect external environmental scenes, user attributes, or user interaction gestures; or, detector 230 includes a sound acquisition device, such as a microphone, for receiving external sounds.

[0043] The external device interface 240 may include, but is not limited to, one or more of the following: High Definition Multimedia Interface (HDMI), analog or high-definition component input interface (component), composite video input interface (CVBS), USB input interface (USB), RGB port, etc. It may also be a composite input / output interface formed by multiple interfaces mentioned above.

[0044] The tuner / demodulator 210 receives broadcast television signals via wired or wireless means, and demodulates audio and video signals, such as EPG data signals, from multiple wireless or wired broadcast television signals.

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

[0046] The controller 250 controls the operation of the display device and responds to user operations through various software control programs stored in memory (internal or external memory). The controller 250 controls the overall operation of the display device 200. For example, in response to receiving a user command to select a UI object to display on the monitor 260, the controller 250 can perform operations related to the object selected by the user command.

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

[0048] RAM, also known as main memory, is an internal memory that directly exchanges data with the controller. It can be read and written at any time (except during refresh) and is very fast, typically serving as temporary data storage for the operating system or other running programs. Its biggest difference from ROM is data volatility; data stored in RAM is lost when power is off. RAM is used in computers and digital systems to temporarily store programs, data, and intermediate results. ROM operates in a non-destructive read-only manner; information can only be read, not written. Once information is written, it is fixed and will not be lost even if power is cut off; therefore, it is also called fixed-function memory.

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

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

[0051] The interactive system for the program execution method provided in this application embodiment consists of a server, at least one display device with a smart home APP installed, and at least one smart device. The server can be a cluster or multiple clusters, and can include one or more types of servers. The server can be a cloud server or an Internet of Things (IoT) cloud backend, used to store device association relationships, program association relationships, and parameter memory, etc. The display device can include televisions, smart TVs, laser projectors, monitors, electronic bulletin boards, electronic desktops, and devices such as refrigerators, air conditioners, speakers, range hoods, water heaters, and fans. The smart device has an NFC sticker or a built-in NFC module, supporting NFC tap-to-pay functionality. The smart home APP is used to bind the smart device and enable related functions to be executed by tapping the NFC sticker.

[0052] In this embodiment, in response to a triggering operation on the NFC sensing area of ​​a smart device, an NFC identifier and a target device identifier corresponding to the NFC sensing area are obtained. The NFC identifier indicates the NFC sensing area, and the target device identifier indicates the smart device. A communicator is configured to: send an information acquisition request to a server, the information acquisition request carrying the target device identifier, the information acquisition request requesting the server to acquire a target WiFi identifier associated with the target device identifier, the target WiFi identifier indicating the WiFi module of the smart device; and receive the target WiFi identifier returned by the server. The controller is further configured to: acquire multiple WiFi identifiers corresponding to the target local area network connected to the display device, each WiFi identifier indicating the current connection to the target local area network. A device on a domain network; if the target WiFi identifier is included among the multiple WiFi identifiers, the display device is determined to have control over the smart device; the communicator is further configured to: if the display device has control over the smart device, send a program query request to the server, the program query request carrying the NFC identifier, the target device identifier, and the target WiFi identifier, the program query request being used to request target program parameters, the target program parameters being program parameters that have a program association relationship with the NFC identifier, the target device identifier, and the target WiFi identifier, and are used to execute the target program associated with the NFC sensing area; receive the target program parameters returned by the server; the controller is further configured to: control the smart device to execute the target program based on the program parameters.In this solution, in response to a trigger operation on the NFC sensing area of ​​the smart device, the display device requests a target WiFi identifier that is associated with the target device identifier from the server. Then, by verifying that the target WiFi identifier is included among multiple WiFi identifiers corresponding to the target local area network currently connected to the display device, it determines that the display device has control over the smart device. Finally, it requests the server to obtain target program parameters that are associated with the NFC identifier, the target device identifier, and the target WiFi identifier, and are used to execute the target program associated with the NFC sensing area. Based on the target program parameters returned by the server, the display device controls the smart device to execute the target program. Thus, by verifying whether the display device is connected to the same local area network as the smart device, it determines whether the display device has control over the smart device. If the display device has control over the smart device, it obtains the target program associated with the NFC sensing area. The target program parameters control the smart device to execute the target program. Therefore, if a customer wants to experience the NFC tap-to-connect function, they only need to bring their display device close to the NFC tag. This verifies whether the display device is connected to the local area network of the smart device, thus determining whether the display device has control permissions over the smart device. This eliminates the need to remind customers to delete the device from their account and reset the NFC program (unbinding the smart device from account A so that a new customer's account can bind the smart device) after each experience, and to change the binding relationship between the smart device and different smart home APP accounts. It also eliminates the need to transfer permissions between accounts; simply verifying that the customer's device is connected to the same local area network as the smart device simplifies the process of verifying whether the display device has control permissions over the smart device and the process of the display device controlling the smart device to execute associated programs via the NFC tap-to-connect function, thus improving the customer experience.

[0053] For example, the NFC tap-to-wash function currently has the following application scenarios: Users can use a smart home app to connect to the washing machine's washing program. For example, they can customize and adjust the parameters of the washing program, such as the quick wash program, which allows adjusting time parameters such as 15 minutes, 20 minutes, and 25 minutes. They can set the washing program parameters and connect the washing program by opening the smart home app and controlling the buttons on the smart control page, thus enabling the NFC tap-to-wash function. Users can also use a smart home app to connect to the refrigerator's food management program. For example, they can customize the parameters of the food management program and set the parameters by opening the smart home app and controlling the buttons on the smart control page, thus enabling the NFC tap-to-food management function. The specific application can be determined according to the actual situation and is not limited here.

[0054] For example, taking the washing program of a washing machine associated with a smart home APP as an example, such as Figure 4As shown, the user selects the "Quick Clean" program to bind the device, and the following is displayed: Figure 5 The "Quick Clean" program's washing settings interface, as shown, allows users to set the washing parameters and then select the "OK" button. The interface will then display the desired result. Figure 6 The interface shown is "Quick Cleaning Program is about to start".

[0055] In some embodiments of this application, the display device includes: a controller configured to: in response to a trigger operation on an NFC sensing area on a smart device, acquire an NFC identifier and a target device identifier corresponding to the NFC sensing area, wherein the NFC identifier is used to indicate the NFC sensing area and the target device identifier is used to indicate the smart device; a communicator configured to: send an information acquisition request to a server, wherein the information acquisition request carries the target device identifier and is used to request the server to acquire a target WiFi identifier that has a device association relationship with the target device identifier, wherein the target WiFi identifier is used to indicate the WiFi module of the smart device; and receive the target WiFi identifier returned by the server; the controller is further configured to: acquire multiple WiFi identifiers corresponding to a target local area network connected to the display device, wherein each WiFi identifier is used to indicate The communicator is configured to: display a device currently connected to the target local area network; if the target WiFi identifier is included among the multiple WiFi identifiers, determine that the display device has control authority over the smart device; the communicator is further configured to: send a program query request to the server when the display device has control authority over the smart device, the program query request carrying the NFC identifier, the target device identifier, and the target WiFi identifier, the program query request being used to request target program parameters, the target program parameters being program parameters that have a program association relationship with the NFC identifier, the target device identifier, and the target WiFi identifier, and are used to execute the target program associated with the NFC sensing area; receive the target program parameters returned by the server; the controller is further configured to: control the smart device to execute the target program based on the program parameters.

[0056] Among them, smart devices are those with NFC stickers or built-in NFC modules, and the specifics can be determined according to the actual situation, which is not limited here.

[0057] The triggering operation for the NFC sensing area on the smart device can be an operation that occurs when the distance between the display device and the NFC sensing area (NFC tag or NFC module) is less than or equal to a distance threshold. This triggering operation on the NFC sensing area of ​​the smart device is then determined. The distance threshold can be determined based on the actual situation and is not limited here.

[0058] The NFC identifier is used to uniquely identify the NFC sensing area. If an NFC sticker is attached to the smart device, the NFC identifier is used to uniquely identify the NFC sticker. If the smart device has a built-in NFC module, the NFC identifier is used to uniquely identify the NFC module.

[0059] In this embodiment, if an NFC tag is affixed to a smart device, the NFC tag stores a pre-set NFC identifier and a smart device identifier (used to indicate the smart device with the NFC tag attached). Before the smart device leaves the factory, information is written into the NFC tag. This information includes the NFC identifier and the smart device identifier, and may also include a smart home app download address (for some operating systems, used to download the smart home app installation package and install the smart home app based on the downloaded package) or a smart home app package name (for other operating systems, used to install the smart home app). Other information may also be included, which can be determined based on the actual situation and is not limited here.

[0060] The server can store device association relationships, which can be used to indicate the association between the target device identifier and the target WiFi identifier. The device association relationships can also be used to indicate the association between the target device identifier and other information, such as the association between the target device identifier and the home identifier, the association between the target device identifier and the NFC identifier, etc. The specifics can be determined according to the actual situation and are not limited here.

[0061] The server can store multiple device associations. Each device association indicates the association between different device identifiers and different WiFi identifiers. When the server receives an information retrieval request, it searches for an association that matches the target device identifier from the multiple device associations. If the multiple device associations include a device association that matches the target device identifier, it is determined that a target WiFi identifier with a device association with the target device identifier has been found. If the multiple device associations do not include a device association that matches the target device identifier, it is determined that a WiFi identifier with a device association with the target device identifier cannot be found.

[0062] It is understood that in this embodiment of the application, the target device identifier is obtained from the NFC sensing area, the target WiFi identifier corresponding to the WiFi module of the smart device that is associated with the target device identifier is obtained from the cloud, and then the target WiFi identifier is verified among the multiple WiFi identifiers corresponding to the local area network connected to the display device to determine whether the display device and the smart device are connected to the same local area network. When the display device and the smart device are connected to the same local area network, it is determined that the display device has control over the smart device.

[0063] The program parameters can be cmdList, which includes program information and program parameter information. Specifically, cmdList includes cmdId, cmdCode, and commandInfo. cmdId is used to represent the program ID, cmdCode is used to represent the command code, and commandInfo is used to represent the program parameter information.

[0064] For example, assuming the target program is a quick wash program, the program parameter information represented by commandInfo may include setting the wash time to 15 minutes and the wash temperature to 40 degrees Celsius.

[0065] The server may store program association relationships, which are used to indicate the association between the NFC tag and the target device tag, the target WiFi tag and program parameters. The program association relationships can also be used to indicate the association between the NFC tag and other information, such as the association between the NFC tag and the home tag. The specific relationship can be determined according to the actual situation and is not limited here.

[0066] The server can store multiple program associations. Each program association indicates the association between different NFC identifiers, device identifiers, WiFi identifiers, and program parameters. When the server receives a program query request, it searches for an association that matches the NFC identifier, the target device identifier, and the target WiFi identifier from the multiple program associations. If the multiple program associations include a program association that matches the NFC identifier, the target device identifier, and the target WiFi identifier, it is determined that a program parameter with a program association with the NFC identifier, the target device identifier, and the target WiFi identifier has been found. If the multiple program associations do not include a program association that matches the NFC identifier, the target device identifier, and the target WiFi identifier, it is determined that a program parameter with a program association with the NFC identifier, the target device identifier, and the target WiFi identifier cannot be found.

[0067] In some embodiments of this application, the device identifier, WiFi identifier, and program parameters in the program association relationship can be treated as a whole, such as a data content structure that simultaneously includes the device identifier, WiFi identifier, and program parameters; the device identifier, WiFi identifier, and program parameters in the program association relationship can also be treated as separate data contents; the specific details can be determined according to the actual situation, and are not limited here.

[0068] Specifically, based on the program parameters, the smart device is controlled to execute the target program. This involves the display device sending control commands determined based on the program parameters to the smart device via a remote control channel, so that the smart device can execute the target program.

[0069] Example 1: Assume a smart device has an NFC tag attached. The smart device is identified by its deviceId, the NFC by its nfcId, and the Wi-Fi module by its target Wi-FiId. The server is a cloud server. When the display device taps the NFC tag, it retrieves the deviceId and nfcId stored in the NFC tag. Based on the deviceId, the display device calls the cloud server's interface to obtain the device association. If the smart device is already bound to another device via the NFC tag (assuming account A's display device is the bound smart device, and this device association is stored on the cloud server, allowing the Wi-FiId information to be obtained from the deviceId), then the cloud server stores the device association between the deviceId and the Wi-FiId. The display device then receives the target Wi-FiId returned by the cloud server. If the display device uses the same network as the smart device, and both are on the same local area network (LAN), the display device can discover LAN devices connected to the target LAN using the LAN discovery protocol. It can then obtain LAN data packets from that target LAN. These packets include the Wi-Fi IDs of each device on the target LAN, and may also include information such as Wi-Fi Type, depending on the specific requirements. The display device compares the Wi-Fi IDs in the LAN data packets with the target Wi-Fi ID obtained from the device association interface on the cloud server. If the comparison is successful (i.e., the target Wi-Fi ID is included in the Wi-Fi IDs in the LAN data packets), it indicates that the display device and the smart device are connected to the same LAN, and the display device is considered to have permission to control the smart device. This permission can include NFC tap functionality, or it can include both LAN control and NFC tap functionality.

[0070] In this embodiment, in response to a trigger operation on the NFC sensing area of ​​a smart device, the display device requests a target WiFi identifier associated with a target device identifier from a server. Then, by verifying that the target WiFi identifier is included among multiple WiFi identifiers corresponding to the target local area network currently connected to the display device, the display device determines that it has control over the smart device. Finally, it requests target program parameters from the server that are associated with the NFC identifier, the target device identifier, and the target WiFi identifier, and are used to execute the target program associated with the NFC sensing area. Based on the target program parameters returned by the server, the display device controls the smart device to execute the target program. Thus, by verifying whether the display device is connected to the same local area network as the smart device, it determines whether the display device has control over the smart device. If the display device has control over the smart device, it obtains the target program associated with the NFC sensing area. The target program parameters control the smart device to execute the target program. Therefore, if a customer wants to experience the NFC tap-to-play function, they only need to bring their display device close to the NFC tag. This verifies whether the display device is connected to the local area network of the smart device, thus determining whether the display device has control permissions over the smart device. This eliminates the need to remind customers to delete the device from their account and reset the NFC program (unbinding the smart device from account A so that a new customer's device account can be bound to the smart device) after each experience, and to change the binding relationship between the smart device and different smart home APP accounts. It also eliminates the need to transfer permissions between accounts; simply verifying that the customer's device is connected to the same local area network as the smart device simplifies the process of verifying whether the display device has control permissions over the smart device and simplifies the process of the display device controlling the smart device to execute associated programs via the NFC tap-to-play function, thus improving the customer experience.

[0071] In some embodiments of this application, the communicator is further configured to: send a smart control page retrieval request to the server when the display device has control authority over the smart device; the smart control page retrieval request carries a target account identifier and a target device identifier of the display device; the smart control page retrieval request is used to request the server to retrieve a target smart control page matching the display device; if at least one member account identifier associated with a family identifier that has a device association relationship with the target device identifier does not include the target account identifier, the target smart control page is used to display at least one local area network control function; if at least one member account identifier includes the target account identifier, the target smart control page includes the at least one remote control function; receive the target smart control page returned by the server; the display device further includes: a display, configured to: display the target smart control page.

[0072] The family identifier is used to indicate the family in which the smart device is located, and each member account identifier is used to indicate a member under that family.

[0073] If at least one member account identifier associated with a family identifier that is associated with the target device identifier does not include the target account identifier, it indicates that the displayed device is a guest, and the target smart control page is used to display at least one local area network control function, i.e., the target smart control page is a guest page; if at least one member account identifier includes the target account identifier, it indicates that the displayed device is an administrator, and the target smart control page includes the at least one remote control function, i.e., the target smart control page is an administrator page.

[0074] Among them, the local area network control function refers to the control function of the display device over the smart device when the display device must be connected to the same local area network as the smart device.

[0075] Among them, the remote control function refers to the ability of the display device to control the smart device regardless of whether it is connected to the same local area network as the smart device.

[0076] It is understood that, in this embodiment of the application, the display device can not only control the smart device to execute the target program associated with the NFC sensing area by triggering the NFC sensing area on the smart device, but also display the smart control page in the smart home APP of the display device.

[0077] The server also stores the association between the target device identifier and the home identifier. This association can be stored separately or in the device association relationship. In other words, the device association relationship is the association between the target device identifier, the target WiFi identifier, and the home identifier. The specific relationship can be determined based on the actual situation and is not limited here.

[0078] The member account identifier can be customerId, which is a unique identifier for the account. Each member account identifier corresponds one-to-one with the account in the smart app on the login display device.

[0079] Example 2, following Example 1 above, after the display device corresponding to account B has the permission to control smart devices, it will request the cloud server interface to obtain H5 page resources (i.e. smart control page) for display. When the display device corresponding to account B requests H5 page resources, the cloud server will verify the permissions of account B, that is, verify whether the account is an administrator (an account under the same family as account A) or a guest (an account under a different family than account A). The verification method is as follows: When account B requests H5 page resources, it uploads the deviceId and customerId obtained by tapping the NFC tag to the cloud. The cloud server retrieves the homeId from the database based on the deviceId and then checks if the customerId is included among the multiple member account identifiers associated with the homeId (i.e., the cloud server queries all member information under the homeId and compares whether it contains account B's customerId information). If the customerId is included among the multiple member account identifiers associated with the homeId, it means that account B belongs to the family and is considered an administrator; if the customerId is included among the multiple member account identifiers associated with the homeId, it means that account B does not belong to the family and is considered a guest. When account B is identified as a guest, the H5 page resources issued to the display device corresponding to account B are resources with guest permissions. When account B is identified as an administrator, the H5 page resources issued to the display device corresponding to account B are resources with administrator permissions. After the H5 page resources are sent to the display device corresponding to account B, the display device will automatically open the smart home APP and automatically display the H5 page.

[0080] In some embodiments of this application, the smart control page can be acquired and displayed simultaneously with acquiring program parameters and controlling the smart device to execute the target program; alternatively, the program can be acquired and the smart device can be controlled to execute the target program first, and then the smart control page can be acquired and displayed; alternatively, the smart control page can be acquired and displayed first, and then the program can be acquired and the smart device can be controlled to execute the target program. Other execution orders are also possible, which can be determined according to the actual situation and are not limited here.

[0081] In some embodiments of this application, the smart home APP of the display device will automatically open the H5 page and also automatically start controlling the smart device to execute the target program.

[0082] In some embodiments of this application, the aforementioned display device can be any display device, including a display device that logs into the smart home APP through account A (hereinafter referred to as account A, which is a display device that performs network configuration, binding, and program association by tapping the NFC sensing area of ​​the smart device), and a display device that logs into the smart home APP through a non-account A (such as account B, which is a display device other than the display device that performs network configuration, binding, and program association by tapping the NFC sensing area of ​​the smart device). The aforementioned display device can be any display device other than the display device corresponding to account A, that is, a display device that logs into the smart home APP through a non-account A. The specific device can be determined according to the actual situation and is not limited here.

[0083] In some embodiments of this application, since account A is the sovereign controller of the smart device, the display device corresponding to account A also has control permissions such as unbinding the device and changing the device name.

[0084] In some embodiments of this application, display devices other than the display device corresponding to account A (such as the display device corresponding to account B) can be set to not have control permissions such as unbinding device or changing device name; alternatively, display devices in the same household as the display device corresponding to account A can be set to have control permissions such as unbinding device or changing device name, while display devices not in the same household as the display device corresponding to account A cannot have control permissions such as unbinding device or changing device name; the specifics can be determined according to the actual situation and are not limited here.

[0085] In some embodiments of this application, a server is provided, including: a communicator configured to: receive an information acquisition request from a display device, the information acquisition request being generated by the display device in response to a tap-to-tap operation on an NFC sensing area affixed to a smart device, the information acquisition request carrying a target device identifier corresponding to the NFC sensing area; a controller configured to: acquire a target WiFi identifier that has a device association relationship with the target device identifier based on the information acquisition request, the target WiFi identifier being used to indicate the WiFi module of the smart device; the communicator is further configured to: return the target WiFi identifier to the display device, so that the display device can determine whether it has control authority over the smart device based on the target WiFi identifier; The controller receives a program query request from the display device. The program query request carries the target device identifier, the target WiFi identifier, and the NFC identifier corresponding to the NFC sensing area. The program query request is generated by the display device after determining that it has control authority over the smart device. The controller is further configured to: obtain target program parameters according to the program query request. The target program parameters are program parameters that have a program association relationship with the NFC identifier, the target device identifier, and the target WiFi identifier, and are used to execute the target program associated with the NFC sensing area. The communicator is further configured to: return the target program parameters to the display device so that the display device controls the smart device to execute the target program based on the program parameters.

[0086] In this embodiment of the application, the description of the server can be referred to the relevant description of the display device, and will not be repeated here.

[0087] In some embodiments of this application, the controller is specifically configured to: obtain, according to the program query request, associated program parameters, associated device identifier, and associated WiFi identifier that are associated with the NFC identifier; the associated program parameters are used to indicate the program parameters of the target program associated with the NFC sensing area; the associated device identifier is used to indicate the device identifier of the device of the target program associated with the NFC sensing area; and the associated WiFi identifier is used to indicate the WiFi module of the device of the target program associated with the NFC sensing area; if the associated device identifier matches the target device identifier and the associated WiFi identifier matches the target WiFi identifier, the associated program parameter is determined as the target program parameter.

[0088] In this embodiment of the application, the description of the server can be referred to the relevant description of the display device, and will not be repeated here.

[0089] In some embodiments of this application, the communicator is further configured to: receive a smart control page retrieval request from the display device, the smart control page retrieval request carrying a target account identifier and a target device identifier of the display device, the smart control page retrieval request being generated by the display device after determining that the display device has control permissions over the smart device; the controller is further configured to: based on the smart control page retrieval request, retrieve a family identifier that has a device association relationship with the target device identifier, the family identifier being used to indicate the family where the smart device is located, the smart control page retrieval request being used to request a target smart control page matching the display device; determine the family... Whether at least one member account identifier associated with the family identifier includes the target account identifier; if the at least one member account identifier does not include the target account identifier, the smart control page used to display at least one local area network control function is determined as the target smart control page, the family identifier is used to indicate the family where the smart device is located, and each member account identifier is used to indicate a member under the family; if the at least one member account identifier includes the target account identifier, the smart control page used to display the at least one remote control function is determined as the target smart control page; the communicator is also configured to: return the target smart control page to the display device.

[0090] In this embodiment of the application, the description of the server can be referred to the relevant description of the display device, and will not be repeated here.

[0091] In some embodiments of this application, the communicator is further configured to: receive a device binding request from a control device, the device binding request carrying the target device identifier, the device binding request being used to request the server to generate a device association relationship; the controller is further configured to: obtain the target WiFi identifier and the home identifier according to the device binding request; generate and save the device association relationship, the device association relationship being used to indicate the association relationship between the target device identifier and the target WiFi identifier and the home identifier.

[0092] Among them, the control device is a display device that performs network configuration, binding, and association programs by tapping the NFC sensing area of ​​the smart device, that is, the display device corresponding to account A.

[0093] The target WiFi identifier can be stored on the server or obtained by the server from the control device. The specific identifier can be determined according to the actual situation and is not limited here.

[0094] In some embodiments of this application, when using the NFC tap-to-connect function for the first time, the smart device needs to be bound to the home account first. After successful binding, the associated program can be used as needed.

[0095] Example 3, following Example 2 above, when the display device corresponding to account A uses the smart device NFC tap-to-connect function for the first time, it first enters the network configuration process. The display device taps the NFC tag and opens the smart home APP. The smart home APP reads the target device identifier (such as the device barcode, i.e., deviceId), device type (for example: air conditioner device type is 00d, washing machine device type is 00f), and NFC identifier (NFC tag serial number, i.e., NFCId) stored in the NFC tag. Based on the identified deviceId, NFCId, and device type, the corresponding device type's network configuration instruction page can be directly opened, guiding the user to perform the network configuration operation according to the prompts. After the network configuration process is completed, the smart home APP calls the cloud server interface to set NFC association data, associating the target device identifier with the target WiFi identifier to obtain the device association relationship, and stores the device association relationship on the cloud server. The device association relationship can also include the association relationship between the target device identifier and the home identifier.

[0096] In this embodiment of the application, the power distribution process can refer to relevant power distribution technologies, which will not be elaborated here.

[0097] In some embodiments of this application, the communicator is further configured to: receive a program binding request from a control device, the program binding request carrying the NFC identifier, the associated program parameters, the associated device identifier, and the associated WiFi identifier; the program binding request is generated by the control device in response to a received program binding operation; the controller is further configured to: generate and save a program association relationship based on the program binding request, the program association relationship being used to indicate the association relationship between the NFC identifier and the associated program parameters, the associated device identifier, and the associated WiFi identifier.

[0098] Example 4, following Example 3 above, after storing the device association relationship to the cloud server, will prompt the user to perform NFC program association. Taking a washing machine as an example, the interface will display a list of washing machine programs. The user can select the washing program to be associated. After selecting "Save", the smart home APP calls the cloud server interface to set NFC association data, associates the NFC ID with device information (deviceId, Wi-FiId) and command information (cmdList), generates program association relationship, and stores the program association relationship to the cloud server.

[0099] In this embodiment, by generating and storing device association relationships and program association relationships through a cloud server, a display device located on the same local area network as the smart device can obtain the device association relationship through the cloud server after tapping the NFC sensing area of ​​the smart device. This verifies that the display device and the smart device are on the same local area network and that the display device has control over the smart device. Furthermore, the display device can obtain the program parameters of the target program in the program association relationship through the cloud server and control the smart device to execute the target program based on the program parameters.

[0100] For example, when a smart home app successfully binds an NFC tag to a smart device for the first time, the user will be prompted to associate the tag with another app. During this process, the smart home app calls a cloud server interface to set up NFC association data. The cloud stores the association relationship. Specifically, when the display device requests the cloud server interface for app association, it needs to upload two important parameters: nfcId and dataContent (i.e., NFC association data). The dataContent must include at least deviceId, wifiId, and cmdList.

[0101] In some embodiments of this application, if the display device corresponding to account A binds the smart device to the family of the display device corresponding to account A, then the display device corresponding to account A can control the smart device to execute the target program associated with the NFC tag by tapping the NFC tag.

[0102] For example, once the display device corresponding to account A is associated with an NFC tag program, each time the smart device is used, the display device corresponding to account A only needs to tap the NFC tag to execute the program. The specific business logic is as follows: The smart home app installed on the display device corresponding to account A taps the NFC tag to read the information stored in the NFC tag. The smart home app then calls the cloud server interface to query the NFC associated program, retrieving the NFC association information from the cloud based on the NFCId stored in the NFC tag. The cloud queries the associated program under the NFCId and returns the query result to the smart home app. Based on the associated program sent by the cloud server, the smart home app obtains the program's cmdList parameters (such as cmdId, cmdCode, etc.), and then calls the cloud interface to execute the associated program.

[0103] In some embodiments of this application, if the display device corresponding to account A binds the smart device to the family of the display device corresponding to account A, then the display device corresponding to account A can control the smart device to execute the target program associated with the NFC tag by tapping the NFC tag.

[0104] In some embodiments of this application, the display device corresponding to account A is bound to an NFC device and associated with an executable program. When the display device corresponding to account B touches the NFC tag, if it is determined that the display device corresponding to account B and the smart device are on the same local area network, the smart device can be directly controlled without account A transferring permissions to account B.

[0105] In some embodiments of this application, after the display device corresponding to account A is bound to a smart device, it gains control over the smart device. Simultaneously, the display devices corresponding to account B or account C can also directly control the smart device when they are near the NFC sensing area of ​​the smart device. Considering the security scope of control, this application proposes a security verification mechanism to ensure that, except for administrators, other personnel can only control the device within the same network (same local area network). That is, in situations where they are not on the same network, visitors are not allowed to control the NFC device. This is to address the issue in high-traffic retail environments where someone could directly control the NFC device by tapping their phone against it. If they could still control the device after leaving the store, it would cause inconvenience to retail staff.

[0106] To illustrate this solution in more detail, the following will use examples to illustrate it. Figures 7 to 11 To explain, it is understandable that Figures 7 to 11 The steps involved may include more or fewer steps in actual implementation, and the order of these steps may also be different, depending on whether the program execution method provided in the embodiments of this application can be implemented.

[0107] Figure 7 The flowchart illustrates the steps of a program execution method according to one or more embodiments of this application. The program execution method may include:

[0108] 701. The display device responds to a tap operation on the NFC sensing area affixed to the smart device and obtains the NFC identifier corresponding to the NFC sensing area and the target device identifier.

[0109] The NFC identifier is used to indicate the NFC sensing area, and the target device identifier is used to indicate the smart device.

[0110] 702. The display device sends an information retrieval request to the server.

[0111] The information retrieval request carries the target device identifier and is used to request the server to obtain the target WiFi identifier that has a device association relationship with the target device identifier. The target WiFi identifier is used to indicate the WiFi module of the smart device.

[0112] 703. The server receives an information retrieval request from the display device.

[0113] The information acquisition request is generated by the display device in response to a tap-to-tap operation on the NFC sensing area attached to the smart device, and the information acquisition request carries the target device identifier corresponding to the NFC sensing area.

[0114] 704. Based on the information retrieval request, the server retrieves the target WiFi identifier that has a device association relationship with the target device identifier.

[0115] The target WiFi identifier is used to indicate the WiFi module of the smart device.

[0116] 705. The server returns the target WiFi identifier to the display device.

[0117] The target WiFi identifier is used by the display device to determine whether it has control over the smart device.

[0118] 706. The display device receives the target WiFi identifier returned by the server.

[0119] 707. The display device obtains multiple WiFi identifiers corresponding to the target local area network to which the display device is connected.

[0120] Each WiFi identifier is used to indicate a device currently connected to the target local area network.

[0121] 708. If the target WiFi identifier is included among the multiple WiFi identifiers, the display device determines that the display device has control over the smart device.

[0122] 709. When the display device has control over the smart device, the display device sends a program query request to the server.

[0123] The query request carries the NFC identifier, the target device identifier, and the target WiFi identifier. The query request is used to request target program parameters, which are program parameters that have a program association relationship with the NFC identifier, the target device identifier, and the target WiFi identifier, and are used to execute the target program associated with the NFC sensing area.

[0124] 710. The server receives a program query request from the display device.

[0125] The query request carries the target device identifier, the target WiFi identifier, and the NFC identifier corresponding to the NFC sensing area. The query request is generated by the display device after determining that the display device has control over the smart device.

[0126] 711. The server obtains the target program parameters based on the program's query request.

[0127] The target program parameter is a program parameter that has a program association relationship with the NFC identifier, the target device identifier, and the target WiFi identifier, and is used to execute the target program associated with the NFC sensing area.

[0128] 712. The server returns the target program parameters to the display device.

[0129] These program parameters are used by the display device to control the smart device to execute the target program.

[0130] 713. The display device receives the target program parameters returned by the server.

[0131] 714. The display device controls the smart device to execute the target program based on the program parameters.

[0132] In some embodiments of this application, after step 703 above, if the server fails to obtain a target WiFi identifier that has a device association relationship with the target device identifier based on the information acquisition request, that is, the server does not store the device association relationship corresponding to the target device identifier, the server returns a network configuration binding prompt message to the display device. The network configuration binding prompt message is used to prompt the display device to perform the network configuration binding process first.

[0133] In some embodiments of this application, after step 710 above, if the server does not obtain the target program parameters according to the program query request, that is, the server does not store program parameters that have a program association relationship with the NFC identifier, the target device identifier and the target WiFi identifier, the server returns a program binding prompt message to the display device. The program binding prompt message is used to prompt the display device to perform the program binding process first.

[0134] In some embodiments of this application, such as Figure 8 As shown, step 711 above can be implemented through steps 801 and 802 below.

[0135] 801. Based on the query request from the program, the server obtains the associated program parameters, associated device identifier, and associated WiFi identifier that are associated with the NFC identifier.

[0136] Among them, the associated program parameters are used to indicate the program parameters of the target program associated with the NFC sensing area, the associated device identifier is used to indicate the device identifier of the device of the target program associated with the NFC sensing area, and the associated WiFi identifier is used to indicate the WiFi module of the device of the target program associated with the NFC sensing area.

[0137] 802. If the associated device identifier matches the target device identifier, and the associated WiFi identifier matches the target WiFi identifier, then the associated program parameter is determined as the target program parameter.

[0138] In some embodiments of this application, combined with Figure 7 ,like Figure 9 As shown, after step 708 above, the program execution method provided in this application embodiment may further include steps 715 to 723 below.

[0139] 715. If the display device has control over the smart device, the display device sends a request to the server to obtain the smart control page.

[0140] The smart control page acquisition request carries the target account identifier and the target device identifier of the display device. The smart control page acquisition request is used to request the server to obtain the target smart control page that matches the display device. If at least one member account identifier associated with the family identifier that has a device association relationship with the target device identifier does not include the target account identifier, the target smart control page is used to display at least one local area network control function. If at least one member account identifier includes the target account identifier, the target smart control page includes the at least one remote control function. The family identifier is used to indicate the family where the smart device is located, and each member account identifier is used to indicate a member under the family.

[0141] 716. The server receives a request to retrieve the smart control page from the display device.

[0142] The smart control page acquisition request carries the target account identifier and the target device identifier of the display device. The smart control page acquisition request is generated by the display device when it is determined that the display device has control permissions over the smart device.

[0143] 717. Based on the request from the smart control page, the server obtains the family identifier that has a device association relationship with the target device identifier.

[0144] The home identifier is used to indicate the home where the smart device is located, and the smart control page retrieval request is used to request a target smart control page that matches the display device.

[0145] 718. The server determines whether at least one member account identifier associated with the family identifier includes the target account identifier.

[0146] 719. If the server determines the smart control page used to display at least one local area network control function as the target smart control page when the at least one member account identifier does not include the target account identifier.

[0147] The family identifier is used to indicate the family in which the smart device is located, and each member account identifier is used to indicate a member under that family.

[0148] 720. If the server determines the smart control page used to display the at least one remote control function as the target smart control page when the at least one member account identifier includes the target account identifier.

[0149] 721. The server returns the target smart control page to the display device.

[0150] 722. The display device receives the target intelligent control page returned by the server.

[0151] 723. The display device displays the target's intelligent control page.

[0152] In some embodiments of this application, such as Figure 10 As shown, prior to step 701 above, the program execution method provided in this application embodiment may further include steps 1001 to 1003 as described below.

[0153] 1001. The server receives a device binding request from the control device.

[0154] The device binding request carries the identifier of the target device and is used to request the server to generate a device association relationship.

[0155] 1002. The server obtains the target WiFi identifier and the home identifier based on the device binding request.

[0156] 1003. The server generates and saves device association relationships.

[0157] The device association is used to indicate the association between the target device identifier, the target WiFi identifier, and the home identifier.

[0158] In some embodiments of this application, combined with Figure 10 ,like Figure 11 As shown, after step 1003 above, the program execution method provided in this application embodiment may further include steps 1004 to 1002 below.

[0159] 1004. The server receives a program binding request from the control device.

[0160] The program binding request carries the NFC identifier, the associated program parameters, the associated device identifier, and the associated WiFi identifier; the program binding request is generated by the control device in response to the received program binding operation.

[0161] 1005. The server generates and saves the program association relationship based on the program binding request.

[0162] The program association relationship is used to indicate the association between the NFC identifier and the associated program parameters, the associated device identifier, and the associated WiFi identifier.

[0163] The present invention also provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it implements the various processes of the above-described program execution method and achieves the same technical effect. To avoid repetition, it will not be described again here.

[0164] The computer-readable storage medium can be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, etc.

[0165] The present invention provides a computer program product, comprising: when the computer program product is run on a computer, causing the computer to implement the above-described program execution method.

[0166] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

[0167] For ease of explanation, the above description has been provided in conjunction with specific embodiments. However, the above exemplary discussion is not intended to be exhaustive or to limit the embodiments to the specific forms disclosed above. Various modifications and variations can be obtained based on the above teachings. The selection and description of the above embodiments are for the purpose of better explaining the principles and practical applications, thereby enabling those skilled in the art to better utilize the described embodiments and various different variations of embodiments suitable for specific use considerations.

Claims

1. A display device, characterized in that, include: The controller is configured to: in response to a trigger operation on an NFC sensing area on a smart device, acquire an NFC identifier and a target device identifier corresponding to the NFC sensing area, wherein the NFC identifier is used to indicate the NFC sensing area and the target device identifier is used to indicate the smart device; The communicator is configured to send an information acquisition request to a server, the information acquisition request carrying the target device identifier, the information acquisition request being used to request the server to acquire a target WiFi identifier that has a device association relationship with the target device identifier, the target WiFi identifier being used to indicate the WiFi module of the smart device; Receive the target WiFi identifier returned by the server; The controller is further configured to: acquire multiple WiFi identifiers corresponding to the target local area network to which the display device is connected, each WiFi identifier being used to indicate a local area network device currently connected to the target local area network, the multiple WiFi identifiers being obtained from local area network data packets under the target local area network; If the target WiFi identifier is included among the plurality of WiFi identifiers, it is determined that the display device has control authority over the smart device; The communicator is further configured to: when the display device has control authority over the smart device, send a program query request to the server, the program query request carrying the NFC identifier, the target device identifier, and the target WiFi identifier, the program query request being used to request target program parameters, the target program parameters being program parameters that have a program association relationship with the NFC identifier, the target device identifier, and the target WiFi identifier, and are used to execute the target program associated with the NFC sensing area; Receive the target program parameters returned by the server; The controller is further configured to control the smart device to execute the target program based on the program parameters.

2. The display device according to claim 1, characterized in that, The communicator is also configured to: When the display device has control permissions over the smart device, it sends a smart control page retrieval request to the server. The smart control page retrieval request carries the target account identifier and the target device identifier of the display device. The smart control page retrieval request is used to request the server to retrieve the target smart control page that matches the display device. If at least one member account identifier associated with a family identifier that has a device association relationship with the target device identifier does not include the target account identifier, the target smart control page is used to display at least one local area network control function. If at least one member account identifier includes the target account identifier, the smart control page includes the at least one remote control function. The family identifier is used to indicate the family where the smart device is located, and each member account identifier is used to indicate a member under the family. Receive the target intelligent control page returned by the server; The display device further includes a display configured to display the target intelligent control page.

3. A server, characterized in that, include: The communicator is configured to receive an information acquisition request from a display device, the information acquisition request being generated by the display device in response to a tap-to-tap operation on an NFC sensing area attached to a smart device, the information acquisition request carrying a target device identifier corresponding to the NFC sensing area; The controller is configured to: based on the information acquisition request, acquire a target WiFi identifier that has a device association relationship with the target device identifier, wherein the target WiFi identifier is used to indicate the WiFi module of the smart device; The communicator is further configured to: return the target WiFi identifier to the display device, so that the display device can determine whether it has control over the smart device based on the target WiFi identifier; The display device receives a program query request, which carries the target device identifier, the target WiFi identifier, and the NFC identifier corresponding to the NFC sensing area. The program query request is generated by the display device based on multiple WiFi identifiers corresponding to the target local area network to which the display device is connected, including the target WiFi identifier, and the display device determines that it has control over the smart device. Each WiFi identifier is used to indicate a local area network device currently connected to the target local area network. The multiple WiFi identifiers are obtained from local area network data packets under the target local area network. The controller is further configured to: obtain target program parameters according to the program query request, wherein the target program parameters are program parameters that have a program association relationship with the NFC identifier, the target device identifier and the target WiFi identifier and are used to execute the target program associated with the NFC sensing area; The communicator is further configured to return the target program parameters to the display device, so that the display device controls the smart device to execute the target program based on the program parameters.

4. The server according to claim 3, characterized in that, The controller is specifically configured to: obtain, according to the program query request, associated program parameters, associated device identifier, and associated WiFi identifier that are associated with the NFC identifier; the associated program parameters are used to indicate the program parameters of the target program associated with the NFC sensing area; the associated device identifier is used to indicate the device identifier of the device of the target program associated with the NFC sensing area; and the associated WiFi identifier is used to indicate the WiFi module of the device of the target program associated with the NFC sensing area. If the associated device identifier matches the target device identifier, and the associated WiFi identifier matches the target WiFi identifier, then the associated program parameter is determined as the target program parameter.

5. The server according to claim 3, characterized in that, The communicator is further configured to: receive a smart control page acquisition request from the display device, the smart control page acquisition request carrying the target account identifier and the target device identifier of the display device, the smart control page acquisition request being generated by the display device when it is determined that the display device has control authority over the smart device; The controller is further configured to: based on the smart control page acquisition request, acquire a family identifier that has a device association relationship with the target device identifier, the family identifier being used to indicate the family where the smart device is located, and the smart control page acquisition request being used to request a target smart control page that matches the display device; Determine whether at least one member account identifier associated with the family identifier includes the target account identifier; In the case where the at least one member account identifier does not include the target account identifier, the smart control page used to display at least one local area network control function is determined as the target smart control page, the family identifier is used to indicate the family where the smart device is located, and each member account identifier is used to indicate a member under the family; If the at least one member account identifier includes the target account identifier, the smart control page used to display the at least one remote control function will be determined as the target smart control page; The communicator is also configured to return the target smart control page to the display device.

6. The server according to claim 5, characterized in that, The communicator is further configured to: receive a device binding request from a control device, the device binding request carrying the target device identifier, the device binding request being used to request the server to generate a device association relationship; The controller is further configured to: obtain the target WiFi identifier and the home identifier according to the device binding request; Generate and save device association relationships, which are used to indicate the association relationship between the target device identifier, the target WiFi identifier, and the home identifier.

7. The server according to any one of claims 3 to 6, characterized in that, The communicator is further configured to: receive a program binding request from a control device, the program binding request carrying the NFC identifier, associated program parameters, associated device identifier, and associated WiFi identifier; the program binding request is generated by the control device in response to a received program binding operation, the associated program parameters are used to indicate the program parameters of the target program associated with the NFC sensing area, the associated device identifier is used to indicate the device identifier of the device of the target program associated with the NFC sensing area, and the associated WiFi identifier is used to indicate the WiFi module of the device of the target program associated with the NFC sensing area; The controller is further configured to generate and save a program association relationship based on the program binding request, the program association relationship being used to indicate the association relationship between the NFC identifier and the associated program parameters, the associated device identifier, and the associated WiFi identifier.

8. A method for executing a program, characterized in that, Applied to display devices, including: In response to a tap-to-tap operation on an NFC sensing area attached to a smart device, the system obtains an NFC identifier and a target device identifier corresponding to the NFC sensing area. The NFC identifier is used to indicate the NFC sensing area, and the target device identifier is used to indicate the smart device. Send an information retrieval request to the server. The information retrieval request carries the target device identifier. The information retrieval request is used to request the server to retrieve a target WiFi identifier that has a device association relationship with the target device identifier. The target WiFi identifier is used to indicate the WiFi module of the smart device. Receive the target WiFi identifier returned by the server; The display device is connected to a target local area network (LAN) and multiple WiFi identifiers are obtained. Each WiFi identifier is used to indicate a LAN device currently connected to the target LAN. The multiple WiFi identifiers are obtained from LAN data packets under the target LAN. If the target WiFi identifier is included among the plurality of WiFi identifiers, it is determined that the display device has control authority over the smart device; When the display device has control over the smart device, it sends a program query request to the server. The program query request carries the NFC identifier, the target device identifier, and the target WiFi identifier. The program query request is used to request target program parameters. The target program parameters are program parameters that have a program association relationship with the NFC identifier, the target device identifier, and the target WiFi identifier, and are used to execute the target program associated with the NFC sensing area. Receive the target program parameters returned by the server; Based on the program parameters, the smart device is controlled to execute the target program.

9. A program execution method, characterized in that, Applied to servers, including: Receive an information acquisition request from the display device. The information acquisition request is generated by the display device in response to a tap operation on the NFC sensing area attached to the smart device. The information acquisition request carries the target device identifier corresponding to the NFC sensing area. Based on the information acquisition request, a target WiFi identifier that has a device association relationship with the target device identifier is acquired, and the target WiFi identifier is used to indicate the WiFi module of the smart device; The target WiFi identifier is returned to the display device so that the display device can determine whether it has control over the smart device based on the target WiFi identifier. The display device receives a program query request, which carries the target device identifier, the target WiFi identifier, and the NFC identifier corresponding to the NFC sensing area. The program query request is generated by the display device based on multiple WiFi identifiers corresponding to the target local area network to which the display device is connected, including the target WiFi identifier, and the display device determines that it has control over the smart device. Each WiFi identifier is used to indicate a local area network device currently connected to the target local area network. The multiple WiFi identifiers are obtained from local area network data packets under the target local area network. According to the program query request, the target program parameters are obtained. The target program parameters are program parameters that have a program association relationship with the NFC identifier, the target device identifier and the target WiFi identifier, and are used to execute the target program associated with the NFC sensing area. The target program parameters are returned to the display device so that the display device controls the smart device to execute the target program based on the program parameters.

10. A computer-readable storage medium, characterized in that, include: A computer program is stored on a computer-readable storage medium, and when executed by a processor, the computer program implements the program execution method as described in claim 8 or 9.

Images