Terminal and device binding method

Abstract

The present invention relates to the technical field of display devices. Some embodiments of the present application illustrate a terminal and a device binding method. The method comprises: in response to a user inputting an instruction for adding a device, controlling a display to display a list of discovered devices; in response to the user inputting an instruction for selecting a first device control, if a first device is a display device, controlling the display to display a binding guide page, and obtaining the number of target controls in the list of discovered devices; if the number is greater than 1, sending a screenshot request to the first device; obtaining a screen picture from a server and displaying the screen picture on a screenshot display window; and when a binding confirmation operation input by the user is received, binding the first device to a user account.

Description

Terminal and device binding method

[0001] This application claims priority to Chinese patent applications with application number 202311019070.7 filed on August 14, 2023, application number 202410827395.6 filed on June 25, 2024, application number 202410009495.8 filed on January 3, 2024, and application number 202311642095.2 filed on December 1, 2023, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of terminal technology, and in particular to a terminal and device binding method. Background Art

[0003] In the AIoT (Artificial Intelligence & Internet of Things) system, the TV serves as the central manager of the home. Accessing the AIoT system requires high accuracy to enhance the user experience. When the TV and phone are connected to the same network, the mobile app can discover all TVs on the same local area network through the DLNA (Digital Living Network Alliance) service. The user can then select a target TV and bind it to the phone.

[0004] However, as people's living standards improve, many households have more than one TV, and TV stores and showrooms often feature multiple TVs. Mobile apps may also discover multiple TVs. Each TV is likely named with a default name, such as "Smart TV" or "Living Room TV." Even if multiple TVs have different names, users cannot intuitively match the TV name to the actual TV.

[0005] Summary of the Invention

[0006] Some embodiments of the present application provide a terminal and device binding method.

[0007] In a first aspect, some embodiments of the present application provide a terminal, including:

[0008] monitor;

[0009] The controller is configured as:

[0010] After logging into the user account, in response to the user inputting an instruction to add a device, the display is controlled to display a discovered device list, where the discovered device list includes at least one device control.

[0011] In response to a user input instruction to select a first device control among at least one device control, if the first device corresponding to the first device control is a display device, the display is controlled to display a binding guide page, and the number of target controls in the discovered device list is obtained, the binding guide page includes a screenshot display window, and the target control is a control of a display device corresponding to the device control.

[0012] If the number is greater than 1, a screenshot request is sent to the first device, so that the first device captures a screenshot based on the screenshot request and uploads the screenshot to the server.

[0013] Get the screen image from the server and display it in the screenshot display window.

[0014] If a confirmation binding operation input by the user is received, the first device is bound to the user account, so that the user can control the first device through the terminal.

[0015] In a second aspect, some embodiments of the present application provide a device binding method, including:

[0016] After logging into the user account, in response to the user inputting an instruction to add a device, the display is controlled to display a discovered device list, where the discovered device list includes at least one device control.

[0017] In response to a user input instruction to select a first device control among at least one device control, if the first device corresponding to the first device control is a display device, the display is controlled to display a binding guide page, and the number of target controls in the discovered device list is obtained, the binding guide page includes a screenshot display window, and the target control is a control of a display device corresponding to the device control.

[0018] If the number is greater than 1, a screenshot request is sent to the first device, so that the first device captures a screenshot based on the screenshot request and uploads the screenshot to the server.

[0019] Get the screen image from the server and display it in the screenshot display window.

[0020] If a confirmation binding operation input by the user is received, the first device is bound to the user account, so that the user can control the first device through the terminal.

[0021] It can be seen from the above content. After logging into the user account and receiving the user input instruction to add a device, the discovered device list is displayed, and the discovered device list includes at least one device control. The device control refers to the control corresponding to the terminal discovered device. After receiving the user input instruction to select the first device control in at least one device control, if the first device corresponding to the first device control is a display device, the binding guide page is displayed, and the number of display devices in the discovered device list is obtained. The binding guide page includes a screenshot display window; if the number of display devices is greater than 1, a screenshot request is sent to the first device, so that the first device takes a screenshot based on the screenshot request and uploads the screenshot to the server; the screenshot is obtained from the server and displayed in the screenshot display window; after receiving the confirmation binding operation input by the user after determining that he wants to bind the device based on the screen image, the first device is bound to the user account so that the user can control the first device through the terminal. The embodiment of the present application is applied to the scenario where the user account logged in by the terminal is bound to the device. After determining that the device selected by the user is a display device and the number of discovered display devices is greater than 1, a screenshot of the selected device is obtained and displayed to the user, so that the user can quickly and accurately find the target device and bind it, simplifying the operation process and saving user time. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] FIG1 shows a flow chart of a device binding method provided according to some embodiments of the present disclosure;

[0023] FIG2 shows a schematic diagram of displaying a list of discovered devices according to some embodiments of the present disclosure;

[0024] FIG3 shows a schematic diagram of a home page of an application provided according to some embodiments of the present disclosure;

[0025] FIG4 shows a schematic diagram of a discovered device list provided according to some embodiments of the present disclosure;

[0026] FIG5 shows a schematic diagram of a cross-network screenshot method provided according to some embodiments of the present disclosure;

[0027] FIG6 shows a schematic diagram of a method for taking screenshots on the same network according to some embodiments of the present disclosure;

[0028] FIG7 shows a schematic diagram of a user interface of a display device according to some embodiments of the present disclosure;

[0029] FIG8 shows a schematic diagram of another display device user interface provided according to some embodiments of the present disclosure;

[0030] FIG9 shows a schematic diagram of a binding pop-up reminder box provided according to some embodiments of the present disclosure;

[0031] FIG10 shows a schematic diagram of a screenshot animation provided according to some embodiments of the present disclosure;

[0032] FIG11 shows a timing diagram of a cross-network screenshot method provided according to some embodiments of the present disclosure;

[0033] FIG12 shows a timing diagram of a method for taking screenshots on the same network according to some embodiments of the present disclosure;

[0034] FIG13 shows a schematic diagram of a first binding guide page provided according to some embodiments of the present disclosure;

[0035] FIG14 shows a schematic diagram of a second binding guide page provided according to some embodiments of the present disclosure;

[0036] FIG15 shows a schematic diagram of a successful connection interface provided according to some embodiments of the present disclosure;

[0037] FIG16 shows a schematic diagram of a home page of another application provided according to some embodiments of the present disclosure;

[0038] FIG17 shows a schematic diagram of a third binding guide page provided according to some embodiments of the present disclosure;

[0039] FIG18 shows a schematic diagram of a fourth binding guide page provided according to some embodiments of the present disclosure;

[0040] FIG19 shows a schematic diagram of a fifth binding guide page provided according to some embodiments of the present disclosure;

[0041] FIG20 shows a timing diagram of a device binding method provided according to some embodiments of the present disclosure;

[0042] FIG21 shows a schematic diagram of a scene of a display method provided according to some embodiments of the present disclosure;

[0043] FIG22 shows a second structural schematic diagram of a display device according to some embodiments of the present disclosure;

[0044] FIG23 shows one of the flowcharts of the display method according to some embodiments of the present disclosure;

[0045] FIG24 shows one of the scene schematic diagrams of the display method provided according to some embodiments of the present disclosure;

[0046] FIG25 shows a second schematic diagram of a scene of a display method provided according to some embodiments of the present disclosure;

[0047] FIG26 shows a third schematic diagram of a scene of a display method provided according to some embodiments of the present disclosure;

[0048] FIG27 shows a fourth schematic diagram of a scene of a display method provided according to some embodiments of the present disclosure;

[0049] FIG28 shows a fifth schematic diagram of a scene of a display method provided according to some embodiments of the present disclosure;

[0050] FIG29 shows a second flow chart of a display method according to some embodiments of the present disclosure;

[0051] FIG30 shows a third flow chart of a display method according to some embodiments of the present disclosure;

[0052] FIG31 shows a fourth flow chart of a display method according to some embodiments of the present disclosure;

[0053] FIG32 shows a fifth flow chart of a display method according to some embodiments of the present disclosure;

[0054] FIG33 shows a sixth flowchart of a display method according to some embodiments of the present disclosure;

[0055] FIG34 shows a seventh flowchart of a display method according to some embodiments of the present disclosure;

[0056] FIG35 shows an eighth flowchart of a display method according to some embodiments of the present disclosure;

[0057] FIG36 shows a ninth flowchart of a display method according to some embodiments of the present disclosure;

[0058] FIG37 shows a flowchart of a method for determining member controls according to some embodiments of the present disclosure;

[0059] FIG38 shows a schematic diagram of a local device display frame according to some embodiments of the present disclosure;

[0060] FIG39 shows a schematic diagram of an application home page according to some embodiments of the present disclosure;

[0061] FIG40 shows a flowchart of a method for determining a target account according to some embodiments of the present disclosure;

[0062] FIG41 shows a schematic diagram of a living room TV details page according to some embodiments of the present disclosure;

[0063] FIG42 shows a schematic diagram of a membership renewal page provided according to some embodiments of the present disclosure;

[0064] FIG43 shows a schematic diagram of a membership activation page provided according to some embodiments of the present disclosure;

[0065] FIG44 shows a schematic diagram of a prompt page provided according to some embodiments of the present disclosure;

[0066] FIG45 shows a flowchart of a method for purchasing membership according to some embodiments of the present disclosure;

[0067] FIG46 shows a schematic diagram of a code scanning page provided according to some embodiments of the present disclosure;

[0068] FIG47 shows a flowchart of a device binding method according to some embodiments of the present disclosure;

[0069] FIG48 shows a timing diagram of a device binding method provided according to some embodiments of the present disclosure;

[0070] FIG49 shows a schematic diagram of a confirmation page provided according to some embodiments of the present disclosure;

[0071] FIG50 shows a timing diagram of another device binding method provided according to some embodiments of the present disclosure;

[0072] FIG51 shows a timing diagram of yet another device binding method provided according to some embodiments of the present disclosure;

[0073] FIG52 shows one of the flowcharts of the binding method provided according to some embodiments of the present disclosure;

[0074] FIG53 shows one of the scenario diagrams of the binding method provided according to some embodiments of the present disclosure;

[0075] FIG54 shows a second schematic diagram of a scenario of a binding method according to some embodiments of the present disclosure;

[0076] FIG55 shows a third scenario diagram of a binding method according to some embodiments of the present disclosure;

[0077] FIG56 shows a fourth scenario diagram of a binding method according to some embodiments of the present disclosure;

[0078] FIG57 shows a fifth scenario diagram of a binding method provided according to some embodiments of the present disclosure;

[0079] FIG58 shows a sixth scenario diagram of a binding method according to some embodiments of the present disclosure;

[0080] FIG59 shows a seventh schematic diagram of a scenario of a binding method according to some embodiments of the present disclosure;

[0081] FIG60 shows an eighth scenario diagram of a binding method according to some embodiments of the present disclosure;

[0082] FIG61 shows a ninth scenario diagram of a binding method according to some embodiments of the present disclosure;

[0083] FIG62 shows a tenth schematic diagram of a scenario of a binding method provided according to some embodiments of the present disclosure;

[0084] FIG63 shows an eleventh schematic diagram of a scenario of a binding method provided according to some embodiments of the present disclosure;

[0085] FIG64 shows a twelfth schematic diagram of a scenario of a binding method provided according to some embodiments of the present disclosure;

[0086] FIG65 shows a second flowchart of a binding method according to some embodiments of the present disclosure;

[0087] FIG66 shows a third flowchart of a binding method according to some embodiments of the present disclosure;

[0088] FIG67 shows a fourth flowchart of a binding method according to some embodiments of the present disclosure;

[0089] FIG68 shows a fifth flowchart of a binding method according to some embodiments of the present disclosure;

[0090] FIG69 shows a sixth flowchart of the binding method provided according to some embodiments of the present disclosure. DETAILED DESCRIPTION

[0091] In order to make the purpose and implementation of the present disclosure clearer, the exemplary implementation of the present disclosure will be clearly and completely described below in conjunction with the drawings in the exemplary implementation of the present disclosure. Obviously, the described exemplary implementation is only a part of the implementation of the present disclosure, rather than all the implementations.

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

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

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

[0095] The terminal provided in the embodiments of the present disclosure may have various implementation forms, for example, it may be a display device and a smart device, etc. Among them, the smart device includes a mobile terminal, a tablet computer, a computer, a laptop computer, etc.

[0096] The display device provided in the embodiments of the present disclosure may have various implementation forms, for example, it may be a television, a smart TV, a laser projection device, a monitor, an electronic bulletin board, an electronic table, etc.

[0097] In the AIoT (Artificial Intelligence & Internet of Things) system, the TV serves as the central manager of the home, and the operational procedures for accessing the AIoT system require high accuracy to improve the user experience. When the TV and mobile phone are connected to the same network, the mobile application can discover all TVs on the same local area network through the DLNA (Digital Living Network Alliance) service, and the user can select the target TV to bind to the mobile phone. However, as people's living standards improve, many families have more than one TV, and there are multiple TVs in TV stores or showrooms. The mobile application may also discover multiple TVs. The name of each TV is likely to use the default TV name, such as "Smart TV" or "Living Room TV". Even if the names of multiple TVs are different, users cannot intuitively match the TV name with the actual TV.

[0098] When a user finds a TV through a mobile phone application and wants to bind it, although the names of the TVs are different, the target TV cannot be correctly distinguished from the TV list displayed by the application. The user can use the remote control to control the target TV and enter the setting information to view the corresponding TV name, so that the user can select the target TV in the TV list. However, the query path is deep, the operation is not simple, and it takes time for the user. If the names displayed in the TV list are all the same, the user selects the TVs in the TV list one by one for home binding and determines whether to bind the target TV by checking whether the device card can control the target TV after the binding is completed. However, this process may involve repeated binding and unbinding of TV devices, and it is impossible to accurately bind the target TV. The operation is cumbersome and time-consuming.

[0099] In order to solve the above technical problems, the embodiments of the present disclosure further improve some functions of the terminal. The terminal in the embodiments of the present disclosure may refer to a mobile phone, and the mobile terminal 300 that appears in subsequent embodiments may also refer to a mobile phone, and the embodiments of the present disclosure are described based on the interaction between the mobile phone and the display device. It should be noted that describing the embodiments of the present disclosure with the mobile terminal 300 as a mobile phone does not limit the type of the terminal or mobile terminal 300 in the embodiments of the present disclosure. As shown in Figure 1, the controller performs the following steps:

[0100] Step 101: After the user account logs in, in response to the user inputting an instruction to add a device, the display is controlled to display a list of discovered devices, where the list of discovered devices includes at least one device control;

[0101] In some embodiments, the terminal may refer to a mobile phone. When the mobile phone receives an instruction from the user to open an application, it controls the display to display the home page of the application. The home page includes an add device control and an account display area.

[0102] If historical account login information or locally saved account login information is detected, the user account is logged in according to the account login information and the account information is displayed in the account display area. Receive the user input to select the add device control instruction and control the display to display the discovered device list.

[0103] If no historical account login information or saved account login information is detected, the account display area will display the information "Not logged in". After receiving the user input to select the add device control command, the display will be controlled to display the user login interface. After receiving the user input login information, such as account number and password, and verifying it successfully, the display will be controlled to display the list of discovered devices.

[0104] The Discovered Devices list displays all nearby white goods and display devices, such as LAN white goods, Bluetooth white goods, and LAN display devices. White goods (white appliances) refer to electrical products that can replace household chores, primarily including washing machines, some kitchen appliances, and those that improve living conditions and material living standards, such as air conditioners and refrigerators.

[0105] As shown in Figure 2, white goods can be discovered through the LAN private protocol and the Bluetooth private protocol. Display devices, such as TVs, can be discovered through the LAN DLNA protocol. After discovering a device, it is necessary to notify the update of the discovered device list, filter the bound devices, and then display the discovered device list. The displayed discovered device list may include "Living Room TV (1)", "Living Room TV (2)", "Living Room TV (3)", "Smart Air Conditioner (1)", and "Refrigerator (1)".

[0106] In some embodiments, the step of controlling the display to display the list of discovered devices includes:

[0107] Get the device ID of the discovered device and the device ID of the bound device.

[0108] The device ID is a unique identifier for each display device. The last eight digits of the device ID are the display device's wired MAC address (Media Access Control Address, also known as the physical address or hardware address) or wireless MAC address. For example, if the display device ID is 8610030090000370000007127d00a247, 7d00a247 is the corresponding MAC address.

[0109] The device information of the discovered device is obtained through the service and protocol used by the device discovery. The device information includes the device identifier. The bound device identifier can be obtained directly from the local computer or the server through the user account.

[0110] Determine whether the device ID of the discovered device is the same as the device ID of the bound device.

[0111] If the device identifier of the discovered device is different from the device identifier of the bound device, a device control corresponding to the discovered device is displayed in the discovered device list. The device control is named by combining the discovered device name with a field in the device identifier, such as the last four digits of the device identifier. In some embodiments, the device control is named "Smart TV" (a247).

[0112] If the device ID of the discovered device is the same as the device ID of the bound device, there is no need to display the device control corresponding to the discovered device in the discovered device list.

[0113] All discovered devices are screened to filter out bound devices to avoid invalid operations such as users repeatedly binding already bound devices.

[0114] In some embodiments, the home page of the application is shown in FIG3 . The home page includes an account display area 31 and a bound device area 32 . The bound device area includes an add device control 321 . The user account has bound devices. The bound device area 32 also includes a device card 322 corresponding to the bound device. The user can control the bound device through the device card. When the user account is logged in, the account display area 31 displays the logged in user account information. When the user account is not logged in, the account display area 31 displays the unlogged in information. FIG3 is the case of a logged in user account. When the user clicks the instruction to add a device control, the discovered device list shown in FIG4 is displayed. The discovered device list includes three living room TV controls: "Living Room TV (1)", "Living Room TV (2)", "Living Room TV (3)" and one smart air conditioner control: "Smart Air Conditioner (1)".

[0115] Step 102: Receive a user input instruction to select a first device control among at least one device control.

[0116] In some embodiments, in FIG4 , an instruction is received in which the user clicks on a first living room TV control.

[0117] Step 103: In response to a user input instruction to select a first device control among at least one device control, it is determined whether a first device corresponding to the first device control is a display device.

[0118] In some embodiments, the step of determining whether the first device corresponding to the first device control is a display device includes:

[0119] Obtain a device type identifier for the first device. Determine whether the device type identifier is a display device type identifier, for example, the display device type identifier may be DLNA. If the device type identifier is a display device type identifier, determine that the first device corresponding to the first device control is a display device. If the device type identifier is not a display device type identifier, determine that the first device corresponding to the first device control is not a display device.

[0120] In some embodiments, the step of determining whether the first device corresponding to the first device control is a display device includes:

[0121] Determine the service and protocol type used by the first device. Determine whether the service and protocol type are the service and protocol type used by a display device, wherein the protocol used by the display device is the DLNA protocol. If the service and protocol type are the service and protocol type used by the display device, determine that the first device corresponding to the first device control is a display device. If the service and protocol type are the service and protocol type used by the display device, determine that the first device corresponding to the first device control is not a display device.

[0122] It should be noted that the device information of the discovered device is obtained through the services and protocols used by the discovered device. The device information includes the device type, device identification, device name, device icon, device IP (Internet Protocol), device wired physical address and device wireless physical address, etc.

[0123] If the first device corresponding to the first device control is a display device, execute step 104: control the display to display a binding guide page, and obtain the number of target controls in the discovered device list.

[0124] The binding guide page includes a screenshot display window, which is used to display a screen image captured by a display device. The target control is a device control, and the device corresponding to the device control is a control of the display device.

[0125] In some embodiments, the screenshot display window is provided with a placeholder identifier. When the placeholder identifier of the screenshot display window is a preset value, for example, the placeholder identifier is 0, it indicates that the binding guide page does not display the screenshot display window. When the placeholder identifier of the screenshot display window is not a preset value, for example, the placeholder identifier is 1, it indicates that the binding guide page displays the screenshot display window.

[0126] In some embodiments, when displaying the discovered device list, the number of different device types is counted and saved locally. When a new device joins or a device exits the discovered device list, the number of device types is updated. The number of target controls (or display devices) in the discovered device list can be directly obtained locally.

[0127] In some embodiments, the step of obtaining the number of target controls in the discovered device list includes:

[0128] Traverse the device controls in the discovered device list. Determine whether the device corresponding to the device control is a display device. If so, increment the target control count by 1 and continue determining whether the device corresponding to the next device control is a display device. If not, continue determining whether the device corresponding to the next device control is a display device. After all device controls in the discovered device list have been determined, obtain the target control count.

[0129] Step 105: Determine whether the quantity is greater than 1.

[0130] If the number is greater than 1, execute step Step 106: send a screenshot request to the first device, so that the first device captures a screenshot based on the screenshot request and uploads the screenshot to the server.

[0131] In some embodiments, if the number is greater than 1, the placeholder flag of the screenshot display window is set to a non-preset value, for example, the placeholder flag is set to 1, so that the screenshot display window is displayed on the binding guide page.

[0132] In some embodiments, the screenshot request includes a picture identifier. After sending the screenshot request to the first device, the first device captures a screen image based on the screenshot request and uploads the screen image and the picture identifier to the server.

[0133] The image identifier has a corresponding or associated relationship with the screen image, or the image identifier is a random identification code that can identify the screen image. The terminal can subsequently obtain the corresponding, associated or identified screen image based on the image identifier.

[0134] In some embodiments, the image identifier is in the format of voice_remote+yyyyMMddHHmmss+random, i.e., it starts with voice_remote, concatenated with the current time in the format of yyyyMMddHHmmss, and then concatenated with a 6-digit decimal random number. In some embodiments, the image identifier may be voice_remote20230620170524636462.

[0135] In some embodiments, if the number is greater than 1, it is determined whether the second device corresponding to the second device control in at least one device control is the same as the IP address of the first device, that is, whether the device IP address corresponding to the device control in the discovered device list is the same as the IP address of the first device. The second device control refers to the device control in the discovered device list other than the first device control.

[0136] The device information of the discovered device is obtained by using the service and protocol used by the discovered device. The device information includes the device IP. The IP address of the second device is compared with the IP address of the first device to determine whether the IP address of the second device is the same as the IP address of the first device.

[0137] If the second device corresponding to the second device control in at least one device control has the same IP address as the first device, a cross-network screenshot operation is performed.

[0138] The steps for taking screenshots across networks include:

[0139] Send a screenshot request to the server so that the server sends the screenshot request to the first device based on the device identifier and receives the screenshot data uploaded by the first device after capturing the screen image based on the screenshot request. The screenshot request includes the device identifier and the image identifier, and the screenshot data includes the screen image and the image identifier.

[0140] In order to clarify the process of cross-network screenshot in the embodiment of the present disclosure, an embodiment is disclosed below:

[0141] Obtain a device identifier of the first device and generate an image identifier.

[0142] The device ID (deviceid) and image ID (pushdata) are added as request parameters to the screenshot request. The screenshot request also includes the specific action type (action) and the unique ID (uuid) of the request. The unique ID of the message is used to count the number of screenshot requests sent by the terminal and the number of screenshot requests received by the display device.

[0143] In some embodiments, the request parameters of the screenshot request are as follows:

[0144] "uuid":"288179e0-0f48-11ee-96ed-4b2ea44b9229",

[0145] "action":"com.xxx.smartimages.UPLOAD_CAPTURE",

[0146] "pushdata":"mobilekey":"voice_remote20230620170524636462",

[0147] "deviceid":"86100300900000400000008300ffbf33".

[0148] Among them, mobilekey represents the unique identifier corresponding to the current screen image, that is, the image identifier.

[0149] Send the screenshot request to the server through the cross-network interface, such as mobilemsg / push / v5.3 / remoteMonitor.

[0150] After receiving the screenshot request, the server sends a successful request message to the terminal and sends the screenshot request to the device corresponding to the device identifier in the screenshot request, that is, the first device. The screenshot request sent by the server may not include the device identifier, that is, only the image identifier, operation type, and unique identifier of the request are sent to the first device.

[0151] After receiving the screenshot request, the first device performs the operation corresponding to the operation type, that is, captures the current user interface and generates a screen image, and uploads the screen image and image identifier to the server. The unique identifier of the request can be saved locally to facilitate subsequent counting of the number of screenshots.

[0152] In some embodiments, the server and the display device communicate via MQTT (Message Queuing Telemetry Transport). As shown in Figure 5, the terminal sends a screenshot request to the MQTT server (MQTT Server) of the server. The screenshot request includes a device identifier, a picture identifier, and an operation type. The MQTT server pushes an MQTT message (screenshot request) to the device corresponding to the device identifier. The MQTT message includes a picture identifier and an operation type. After receiving the MQTT message, the MQTT client (MQTT Client) of the display device broadcasts the message. After receiving the broadcast message, the screenshot application in the display device executes the operation of capturing the current user interface and generating a screen image, and uploading the screen image and the picture identifier to the server.

[0153] The embodiment of the present disclosure takes into account the possibility that there may be a device with the same IP as the currently selected device in the discovered device list. In order to avoid sending screenshot instructions to non-currently selected devices via IP, a cross-network screenshot method is used to ensure the accuracy of the sent instructions.

[0154] If the IP addresses of the second device corresponding to the second device control in at least one device control are different from those of the first device, a same-network screenshot operation is performed.

[0155] The steps for taking screenshots on the same network include:

[0156] A screenshot request is sent to the first device based on the IP of the first device, so that the first device captures a screen image based on the screenshot request and uploads the screenshot data. The screenshot request includes a picture identifier, and the screenshot data includes a screen image and a picture identifier.

[0157] In order to clarify the process of taking screenshots on the same network in the embodiments of the present disclosure, an embodiment is disclosed below:

[0158] The terminal obtains the IP address of the first device and generates an image identifier.

[0159] The terminal adds the image identifier (pushdata) as a request parameter to the screenshot request. The screenshot request also includes the specific operation type (action) of this request and the unique identifier (uuid) of this request.

[0160] In some embodiments, the request parameters of the screenshot request are as follows:

[0161] "uuid":"288179e0-0f48-11ee-96ed-4b2ea44b9229",

[0162] "action":"com.xxx.smartimages.UPLOAD_CAPTURE",

[0163] "pushdata":"mobilekey":"voice_remote20230620170524636462".

[0164] The terminal requests a service through the local area network, for example, ip:port / ..commonstarttvapp, and sends a screenshot request to the first device.

[0165] After receiving the screenshot request, the first device performs an operation corresponding to the operation type, that is, captures the current user interface and generates a screen image, and uploads the screen image and the image identifier to the server.

[0166] In some embodiments, as shown in FIG6 , the terminal sends a screenshot request to the display device, wherein the screenshot request includes an image identifier and an operation type. After receiving the screenshot request, the display device notifies the screen casting service in the service, such as the micro-screen casting SDK (Software Development Kit). The screen casting service broadcasts the screenshot request. After receiving the broadcast screenshot request, the screenshot application in the display device executes the operation of capturing the current user interface and generating a screen image, and uploading the screen image and the image identifier to the server.

[0167] In the embodiment of the present disclosure, when it is found that there is no device with the same IP as the device selected for adding in the device list, a screenshot request can be sent directly through the local area network. The screenshot process link of the local area network is shorter than the cross-network screenshot process link, which achieves higher screenshot time efficiency and gives priority to using the same network screenshot.

[0168] In some embodiments, the screenshot request includes a preset instruction, which is used to instruct the first device to execute a preset operation corresponding to the preset instruction, and the preset operation is used to change the user interface of the display device.

[0169] New data content is added to the operation type (action) field of the screenshot request, and the data content is used to instruct the first device to execute a preset operation corresponding to the preset instruction.

[0170] In some embodiments, the preset operation includes displaying a binding pop-up reminder box or prompt text before performing a screenshot operation. Displaying a binding pop-up reminder box or prompt text before performing a screenshot operation can cause the screen image captured by the display device to include the binding pop-up reminder box or prompt text. In this case, a timer is started after displaying the binding pop-up reminder box, and when the timer expires, the binding pop-up reminder box or prompt text is canceled. In some embodiments, the user interface of the display device is shown in Figures 7 and 8.

[0171] In some embodiments, the binding pop-up reminder box includes an agree control and a disagree control for screenshots. If a user input is received to select an agree control, the operation of capturing the current user interface and generating a screen image, and uploading the screen image and the image identifier to the server is executed. If a user input is received to select a disagree control, the operation of capturing the current user interface and generating a screen image, and uploading the screen image and the image identifier to the server is not executed, and if the terminal does not obtain the screen image within a preset time, a prompt message indicating that the screen image has not been obtained can be displayed. In some embodiments, the binding pop-up reminder box is shown in Figure 9.

[0172] In some embodiments, the preset operation includes displaying a screenshot animation. Displaying a screenshot animation after performing a screenshot operation can help the user distinguish whether the device control selected in the discovered device list is the target display device when the user is close to the target display device or can directly view the target display device screen. Among them, the screenshot animation can be to gradually reduce the proportion of the screen image to a corner of the screen after the screenshot is captured. The screenshot animation can be to shake the screen image on the screen after the screenshot is captured. The screenshot animation can be to misplace the screen image after the screenshot is captured or to reduce it by a certain proportion and display it in the current user interface for a preset duration. In some embodiments, the user interface of the display device is shown in Figure 10.

[0173] In some embodiments, the preset operation includes playing a screenshot prompt sound. Playing the screenshot prompt sound when performing the screenshot operation can help the user distinguish whether the device control selected in the discovered device list is the target display device when the user is close to the target display device.

[0174] In some embodiments, the preset operation includes executing a screenshot operation again after executing the screenshot operation and displaying the screenshot animation. This method can cause the screenshot captured by the display device to include data from a specified frame or any frame in the screenshot animation, and upload the second screenshot and image identifier to the server, which can capture the user interface shown in Figure 10.

[0175] In order to solve the problem that when the images displayed by multiple display devices are exactly the same, it is impossible to quickly distinguish the selected device from the target device by taking a screenshot. The embodiment of the present disclosure adds a preset instruction in the screenshot request, so that a binding screenshot prompt that changes the current user interface is added before or after the display device takes a screenshot, which can effectively distinguish the screenshot operation in the binding process from the original simple screenshot or remote monitoring screenshot. The binding screenshot in the embodiment of the present disclosure is for the purpose of distinguishing display devices, rather than viewing the current user interface or execution result of the display device.

[0176] Step 107: Obtain the screen image from the server and display the screen image in the screenshot display window.

[0177] The steps to obtain the screen image from the server include:

[0178] Send an image request to the server, including an image ID. Receive the screen image sent by the server based on the image ID.

[0179] In order to clarify the process of taking screenshots on the same network in the embodiments of the present disclosure, an embodiment is disclosed below:

[0180] After sending a screenshot request to the server or first device, the terminal receives a message from the server or first device indicating a successful request. After receiving the successful request message, the terminal polls the screen image or screen image URL (uniform resource locator) based on the image identifier. The screen image can be obtained based on the screen image URL. Polling the screen image means sending an image request at a preset interval until the screen image is obtained and then stopping the polling.

[0181] When the terminal is polling, it uses the image ID in the screenshot request to obtain the specified screen image through the interface. For example, the interface is:

[0182] https: / / xxxxxx.com / v5 / image / imageurl / by / id?sessionID=voice_remote20230620170524636462&_=744987, where the value of sessionID is the image ID generated when the terminal sends a screenshot request.

[0183] In some embodiments, as shown in Figure 11, when the conditions for executing cross-network screenshots are met, the terminal application sends a screenshot request to the message subsystem of the server, and the screenshot request includes a device identifier and a picture identifier. After receiving the screenshot request, the message subsystem sends a message of successful request to the terminal and sends a screenshot request to the device (display device) corresponding to the device identifier, and the screenshot request includes a picture identifier. After receiving the screenshot request, the display device captures the user interface and generates a screen image, and uploads the picture identifier and the screen image to the AI ​​(Artificial Intelligence) data subsystem of the server. After receiving the data uploaded by the display device, the AI ​​data subsystem sends a message of successful upload to the display device. After receiving the message of successful request, the terminal starts to poll the screen image URL through the interface, and sends a picture request with a picture identifier until the server sends the screen image URL.

[0184] In some embodiments, as shown in FIG12 , when the conditions for executing a screenshot on the same network are met, the terminal application sends a screenshot request to the display device based on the display device IP, and the screenshot request includes a picture identifier. After receiving the screenshot request, the display device sends a message indicating a successful request to the terminal, captures the user interface, generates a screen image, and uploads the picture identifier and the screen image to the AI ​​data subsystem of the server. After receiving the data uploaded by the display device, the AI ​​data subsystem sends a message indicating a successful upload to the display device. After receiving the message indicating a successful request, the terminal begins to poll the screen image URL through the interface and sends a picture request with a picture identifier until the server sends the screen image URL.

[0185] In some embodiments, the screenshot display window further includes a refresh screen control. After receiving a user input instruction to select the refresh screen control, the screenshot request is sent to the first device again, so that the first device captures the screen image again based on the screenshot request and uploads the screen image and the image identifier to the server.

[0186] Step 108: Receive a confirmation binding operation from the user and bind the first device to the user account, allowing the user to control the first device through the terminal. Binding the first device to the user account allows the user to control the first device through the terminal logged into the user account. Control methods include turning the device on and off, adjusting the volume, and searching for media resources.

[0187] In some embodiments, if the first device corresponding to the first device control is a display device, it is detected whether the first device is logged in to a user account.

[0188] If it is detected that the first device has not logged in to the user account, a first guidance frame is displayed on the binding guidance page. The first guidance frame includes guidance information for guiding the user to log in to the user account logged in by the terminal on the first device. The user can log in to the user account on the first device according to the guidance information.

[0189] 13 , the binding guide page includes a screenshot display window 131 and a first guide frame 132 . The screenshot display window 131 includes a refresh screen control 1311 .

[0190] If a user account logged in to the first device is detected, determine whether the user account logged in to the first device is the same as the user account logged in to the terminal. If it is detected that the user account logged in to the first device is the same as the user account logged in to the terminal, display a bind control and a cancel control on the binding guide page. If a user input is received to select the bind control, bind the first device to the user account logged in to the terminal. If a user input is received to select the cancel control, control the display to display a list of discovered devices.

[0191] In some embodiments, in Figure 4, an instruction for the user to click on the first living room TV control is received, and a binding guide page is displayed. As shown in Figure 14, the binding guide page includes a screenshot display window 141, a binding control 142, and a cancel control 143. After the screenshot display window 141 displays the screen image, if the user determines that the currently displayed screen image is the same as the user interface of the target display device, the binding control 142 can be selected. The user input is received to select the binding control 142, the living room TV is bound to the user account logged in by the terminal, and a successful connection interface is displayed, as shown in Figure 15. In the successful connection interface, you can select the room to which the device belongs and change the device name. After the connection is successful, the device card for the living room TV is added to the binding device area of ​​the application home page, as shown in Figure 16. The living room TV can be controlled by selecting the device card.

[0192] If it is detected that the user account logged in by the first device is different from the user account logged in by the terminal, a second guide box is displayed on the binding guide page, and the second guide box includes adding home controls and rebinding controls.

[0193] If an instruction is received from the user to select to join the family control, the user account logged in the terminal is added to the family of the user account logged in the first device, so that the user account logged in the terminal establishes a connection relationship with the first device.

[0194] If user input is received to select rebinding the control, a first guide box is displayed on the binding guide page.

[0195] If the user account logged into the first device is different from the user account logged into the terminal, the first device is already bound to the user account logged into the first device. If you want to control the first device through the terminal, you can add the user account logged into the terminal to the same family as the user account logged into the first device. This will establish a connection between the user account logged into the terminal and the first device, allowing you to control the first device through the terminal. You can also unbind the first device from the user account logged into the first device, that is, log in the terminal user account on the first device to bind the terminal user account to the first device.

[0196] In some embodiments, as shown in FIG17 , the binding guide page includes a screenshot display window 171 and a second guide frame 172. The second guide frame includes a join family control 1721 and a rebind control 1722. If a user input is received to select the join family control 1721, the user account XX logged in by the terminal is added to the family of the user account AA logged in by the display device, and a successful connection interface is displayed, as shown in FIG15 . If a user input is received to select the rebind control 1722, the binding guide page is displayed, as shown in FIG18 . The binding guide page includes a screenshot display window 131 and a first guide frame 132. The first guide frame 132 includes the user account logged in by the display device.

[0197] If the number is equal to 1, the placeholder flag of the screenshot display window is set to a preset value, for example, to not display the screenshot display window on the binding guide page. In some embodiments, the binding guide page is shown in FIG19 .

[0198] In some embodiments, as shown in Figure 20, a terminal application discovers a device and sends the device information to the terminal's binding service layer. The binding service layer filters the bound devices and controls the display to display a list of discovered devices. After a user selects a device control in the discovered device list, the binding guidance page is displayed and a determination is made as to whether the number of displayed devices in the discovered device list is greater than one. If the number of displayed devices is greater than one, the display determines whether there is a device in the discovered device list with the same IP address as the selected device. If there is a device with the same IP address as the selected device, a screenshot request is sent to the server via a cross-network connection. If there is no device with the same IP address as the selected device, a screenshot request is sent to the display device via a local connection. After receiving the screenshot request, the display device captures the user interface, generates a screen image, and uploads the screen image to the server. After receiving a response from the server or display device, the binding service layer polls for the captured screen image, sends an image request to the server, and receives the screen image URL. The screen image is displayed on the binding guidance page. If the number of displayed devices is less than one, the display is controlled to display the binding guidance page without the screen image.

[0199] The Tab page in the embodiment of the present disclosure refers to an interface design similar to a tab page, which generally displays different content areas of the same page through a series of independent tabs at the top of the page.

[0200] FIG21 is a schematic diagram of an operation scenario between a household appliance and a control device according to one or more embodiments of the present disclosure. As shown in FIG21 , a user can operate a display device 200 through a mobile terminal 300 and / or a control device 100. The control device 100 can be a remote control, and communication between the remote control and the display device includes infrared protocol communication, Bluetooth protocol communication, wireless or other wired methods to control the display device 200. The user can control the display device 200 by inputting user commands through buttons on the remote control, voice input, control panel input, etc. In some embodiments, a tablet computer, computer, laptop computer, and other smart devices can also be used to control the display device 200.

[0201] In some embodiments, the terminal provided by the embodiments of the present disclosure may be the above-mentioned mobile terminal 300, such as a mobile phone. The user may control the display device 200 through the mobile phone while using the mobile phone. If the display device 200 has not established a binding relationship with the mobile phone, the user may open the first application on the mobile phone. In this case, the first application responds to the startup operation and obtains the electronic devices that can be added to the current environment through the target protocol. The target protocols include the local area network protocol, the Bluetooth protocol, and the Digital Living Network Alliance protocol. Afterwards, the first application generates a display list based on the electronic devices. The display list includes one or more electronic devices. When the first application determines that there are no other preset pop-up windows to display and the currently displayed page is the target page, the device list pop-up window is displayed on the target page according to the display list. In this way, the user can view the display device 200 that currently needs to be added in the device list pop-up window displayed on the target page, such as the homepage, and perform the corresponding addition operation.

[0202] It can be seen that by adopting the display method provided by the embodiment of the present disclosure, when the user needs to add an electronic device, the user only needs to open the first application installed on the terminal device, and can then check the electronic devices that can be added in the current environment on the target page. The user does not need to manually obtain the electronic devices that can currently be added, thereby avoiding the problem that different users have different proficiency levels in using terminal devices, which often causes users to be unable to find the electronic devices that can currently be added when adding electronic devices.

[0203] As shown in Figure 22, the mobile phone, server, and television can interact with each other. The mobile phone can send commands to the server or television, and receive commands from the server or television, via the processing unit 201, acquisition unit 202, display unit 203, and storage unit 204. The television can execute preset operations represented by various commands based on the application layer 21, framework layer 22, system runtime layer 23, and kernel layer 24, such as displaying an interactive interface. In some embodiments, a user can control the television through their mobile phone while using the phone. If the television and mobile phone are not bound, the user can open a first application on the phone. In response to the launch operation, the processing unit 201 of the first application controls the acquisition unit 202 to obtain electronic devices that can be added to the current environment using a target protocol. Target protocols include LAN protocol, Bluetooth protocol, and Digital Living Network Alliance protocol. The processing unit 201 of the first application then generates a display list based on the electronic devices obtained by the acquisition unit 202. The display list includes one or more electronic devices. Afterwards, if the processing unit 201 of the first application determines that no other preset pop-up windows are currently being displayed and the currently displayed page is the target page, it controls the display unit 203 to display the device list pop-up window according to the display list on the target page. In this way, the user can view the electronic devices that need to be added in the device list pop-up window displayed on the target page, such as viewing the television that needs to be added in the device list pop-up window displayed on the homepage, and perform the corresponding addition operation.

[0204] In some embodiments, when the execution subject of the display method provided by the embodiment of the present disclosure is a mobile phone, the storage unit 204 of the mobile phone is used to store data such as the program code of the display method provided by the embodiment of the present disclosure.

[0205] In the following embodiments, the method of the embodiment of the present disclosure is described by taking a mobile phone as an example of an execution subject of the display method provided by the embodiment of the present disclosure.

[0206] An embodiment of the present disclosure provides a display method applied to a television. As shown in FIG23 , the display method may include S11 - S13 .

[0207] S11. In response to the start operation, obtain electronic devices that can be added in the current environment through a target protocol, wherein the target protocol includes a local area network protocol, a Bluetooth protocol, and a Digital Living Network Alliance (DLNA) protocol.

[0208] In some embodiments, in response to a startup operation, the first application sends a broadcast message using a target protocol. After receiving the broadcast message sent by the first application, the electronic device reports configuration information to the first application. For example, when the target protocol is the Bluetooth protocol, the configuration information includes the Media Access Control Address (MAC) corresponding to the mobile hotspot module of the mobile phone and the Bluetooth identifier (code information of the Bluetooth module). When the target protocol is the LAN protocol, the configuration information includes the LAN identifier (code information of the Wi-Fi module).

[0209] In some embodiments, after the first application is started, the first application automatically discovers a first electronic device, such as a TV, a stereo, or a game console, that is in the same local area network as the terminal device on which the first application is currently installed through the DLNA service. The first application automatically discovers a second electronic device, such as a washing machine, a dryer, a dishwasher, etc., that is in the same local area network as the terminal device on which the first application is currently installed through the Bluetooth service and / or the local area network service.

[0210] It should be noted that the first application starts the DLNA service, Bluetooth service and LAN service immediately after the first application is started, and saves the new devices (such as the first electronic device and / or the second electronic device) discovered by the DLNA service, Bluetooth service and LAN service in the "device update subunit" of the first application. After waiting for the "upgrade detection subunit" and "boot detection subunit" to complete the detection, it will start to actively notify the outside of the changes in the device list pop-up window.

[0211] In some embodiments, the processing unit further includes a device update subunit, an upgrade detection subunit, a boot detection subunit, and a home page Tab manager.

[0212] After the first application is launched, the upgrade detection subunit detects version information, such as detection information containing the current version information sent by the first application to the IoT server 400. After receiving the detection information from the first application, the IoT server 400 determines whether new version information is available. If new version information is available, the IoT server 400 sends the upgrade information to the terminal device on which the first application is installed. After receiving the upgrade information from the IoT server 400, the upgrade detection subunit of the first application adds an upgrade pop-up window to the homepage tab manager. When the homepage tab manager determines that the upgrade pop-up window needs to be displayed, it initializes the PageStatus to the unstarted state. PageStatus includes pop-up label attributes (upgrade, guide) and the display status (not started, displaying, and completed). The upgrade pop-up window is then inserted into the pageList. The pageList is initialized to an empty list. The homepage tab manager determines that the current homepage is the target page (e.g., if the homepage identifier indicates that the current homepage is the homepage), displays the upgrade pop-up window on the target page, and simultaneously sends an indication to the upgrade detection subunit that the upgrade pop-up window has been displayed. Afterwards, the upgrade detection subunit responds to the closing operation of the upgrade pop-up window by sending an indication message of pop-up window closure to the home page Tab manager. The home page Tab manager takes out the corresponding PageStatus in the pageList and modifies the display status to "ended". Or when the home page display changes, or the home page identifier changes, or the device update subunit determines that the display list sends a change, the home page Tab manager determines that the current page is not the target page, and does not take any action. The home page Tab manager determines that the current page is the target page, and the display status of the pop-ups in the pageList are all "ended", and deviceListshowed is all false, and there is a display list that can be displayed, then it will be displayed in the device list pop-up window according to the display list. The home page Tab manager determines that the current page is the target page, and the display status of the pop-ups in the pageList is not all "ended", and there is a pop-up window being displayed, then it will continue to display the pop-up window. The home page Tab manager determines that the current page is the target page, and the display status of the pop-ups in the pageList is not all "ended", and there is a pop-up window being displayed, then it will remove the next display pop-up window in the pageList for display. If the Home Tab Manager determines that the current page is not the target page, no action will be taken. If the Home Tab Manager determines that the current page is the target page, and the display status of the pop-up windows in pageList are all "ended", and deviceListshowed is not all false, the Home Tab Manager notifies the device update sub-unit to continue obtaining the display list.

[0213] The Home Tab Manager determines that the current page is not the target page and does not take any action. The Home Tab Manager determines that the current page is the target page and the display status of the pop-up windows in pageList are all "ended", and deviceListshowed is all false, and there is no display list to display, so it continues to wait.

[0214] It should be noted that the process of guiding the detection sub-unit to display and close the user guidance pop-up window is similar to the process of upgrading the detection sub-unit to display and close the upgrade pop-up window, which will not be repeated here.

[0215] In some embodiments, since the Bluetooth service and the LAN service may discover the same electronic device, it is necessary to deduplicate the obtained electronic devices, such as: if the second electronic device has been networked (that is, the second electronic device can establish a communication connection with the LAN), then the second electronic device can be discovered not only through the Bluetooth protocol, but also through the LAN protocol. Therefore, the same electronic device can be discovered as two devices, one is an electronic device discovered by the LAN service, and the other is an electronic device discovered by the Bluetooth service. However, when actually displayed in the device list pop-up window, it is necessary to give priority to presenting the electronic devices discovered by the LAN service to the user and filter out the same electronic devices discovered by the Bluetooth service. Therefore, it involves the problem of deduplication of discovered devices.

[0216] In some embodiments, the content of the broadcast packet of the electronic device discovered by the local area network service or the electronic device discovered by the Bluetooth service is as shown in Table 2:

[0217] Among them, the wifiId definition rules of the wifi module are:

[0218] To distinguish product information, the Wi-Fi ID begins with the product model (featureCode) with the first target number of digits, for example, if the first target number of digits is 24. The Wi-Fi ID is then derived by appending the MAC address of the Wi-Fi module with the second target number of digits, for example, if the second target number of digits is 12. (If the first target number of digits is 24 and the second target number of digits is 12, the Wi-Fi ID is 36 bits long.)

[0219] For example, the wifiId is "86100c00fffe00600000004038640773889c", the featureCode is "86100c00fffe006000000040", and the MAC address is "38640773889c".

[0220] The local_name definition rules of the Bluetooth module are:

[0221] To distinguish devices from other manufacturers, the local_name begins with the target identifier, such as "HIS-." The target identifier is followed by the last N digits of the Wi-Fi module's wifiId. For example, if the Wi-FiId is "86100c00fffe00600000004038640773889c," where N is 4, the local_name is determined to be "HIS-889c."

[0222] S12: Generate a display list based on the electronic devices, wherein the display list includes one or more electronic devices.

[0223] In some embodiments, based on the actual identifier in the reported information reported by the electronic device, a query can be performed in the device category list to determine whether there is a theoretical identifier that is the same as the actual identifier, and the network identifier corresponding to the theoretical identifier that is the same as the actual identifier is used to indicate that the electronic device supports the Internet of Things function. Based on the configuration information of the electronic device corresponding to the actual identifier, when device model information is obtained, a display list is generated based on the device model information. The device model information includes at least a device icon, a device name, and a device model, and the display list includes the electronic device corresponding to each device model information.

[0224] In some embodiments, the actual identifier includes a local area network device identification code or a Bluetooth pairing device identification code.

[0225] In some embodiments, in response to a startup operation, the first application in the mobile phone calls the Bluetooth module of the mobile phone to obtain information reported by the electronic device in the current environment, such as the content of the Bluetooth broadcast packet, parses the content of the broadcast packet, and then connects to the Internet of Things server 400 to obtain device model information. In addition, after the first application successfully pairs the Bluetooth network with the electronic device, as long as the first application and the electronic device are in the same local area network, the local area network discovery protocol can be used to determine whether the electronic device is connected to the local area network.

[0226] In some embodiments, the correspondence between the theoretical identifier and the network identifier is pre-configured in the device category list, such as the network identifier is the netconfigStatus identifier (wherein, when the netconfigStatus identifier is 0, it indicates that the electronic device does not support the Internet of Things function. When the netconfigStatus identifier is 1, it indicates that the electronic device supports the Internet of Things function, and the theoretical identifier includes a local area network device identification code (deviceIdCode) or a Bluetooth network device identification code (deviceIdCodeBLE).

[0227] In some embodiments, deviceIdCodeBLE is obtained from the manufacturer data (Manufacturer Data) in the Bluetooth advertising packet.

[0228] In some embodiments, the reported information includes a Bluetooth broadcast packet. When a first application receives a Bluetooth broadcast packet reported by an electronic device in the current environment, the first application parses the Bluetooth broadcast packet and determines the actual identifier (e.g., deviceIdCodeBLE1). Then, based on deviceIdCodeBLE1, the first application searches the device category list to identify the theoretical identifier in the device category list that is identical to deviceIdCodeBLE1, as well as the network identifier corresponding to the theoretical identifier. If the network identifier indicates that the electronic device supports IoT functionality, the configuration information of the electronic device corresponding to deviceIdCodeBLE1 is sent to IoT server 400. After receiving the configuration information sent by the mobile phone, IoT server 400 queries the database based on the configuration information to obtain the device model information. IoT server 400 then sends the device model information to the mobile phone, allowing the mobile phone to display the device model information in the display list based on the device model information sent by the IoT service. Alternatively, if the network identifier indicates that the electronic device does not support IoT functionality, the electronic device corresponding to deviceIdCodeBLE1 is deleted. Alternatively, based on deviceIdCodeBLE1, a query is performed in the device category list to determine the theoretical identifier in the device category list that is the same as deviceIdCodeBLE1, as well as the network identifier corresponding to the theoretical identifier. If the network identifier is used to indicate that the electronic device supports the Internet of Things function, the configuration information of the electronic device corresponding to the deviceIdCodeBLE1 is sent to the Internet of Things server 400. After the Internet of Things server 400 receives the configuration information sent by the mobile phone, it queries the database based on the configuration information. If the device model information is not found, the Internet of Things server 400 sends the target information to the mobile phone to indicate that the device model information has not been obtained. After the mobile phone receives the target information sent by the Internet of Things server 400, it queries the device category list based on deviceIdCodeBLE1. When it is determined that the device category corresponding to the theoretical identifier corresponding to deviceIdCodeBLE1 has a corresponding device icon and device name, the device icon and device name corresponding to the device category are used as the device model information. In this way, the mobile phone can be displayed in the display list based on the device model information. Alternatively, based on deviceIdCodeBLE1, a query is performed in the device category list to determine the theoretical identifier in the device category list that is the same as deviceIdCodeBLE1, as well as the network identifier corresponding to the theoretical identifier. If the network identifier is used to indicate that the electronic device supports the Internet of Things function, the configuration information of the electronic device corresponding to deviceIdCodeBLE1 is sent to the Internet of Things server 400.After receiving the configuration information sent by the mobile phone, the IoT server 400 queries the database based on the configuration information. If the device model information is not found, the IoT server 400 sends target information to the mobile phone indicating that the device model information has not been obtained. After receiving the target information sent by the IoT server 400, the mobile phone queries the device category list based on deviceIdCodeBLE1. If it is determined that the device category corresponding to the theoretical identifier corresponding to deviceIdCodeBLE1 does not have a corresponding device icon and device name, it queries the mobile phone's database based on deviceIdCodeBLE1. If there is a pre-configured local icon and local name corresponding to the deviceIdCodeBLE1, the local icon and local name are used as the device model information. In this way, the mobile phone can display the device model information in the display list.

[0229] In some embodiments, the reported information includes an online package. When the first application receives the online package reported by the electronic device in the current environment, the first application parses the online package to determine the actual identifier (such as deviceIdCode 1). Afterwards, based on deviceIdCode 1, a query is performed in the device category list to determine the theoretical identifier that is the same as deviceIdCode 1 in the device category list, and the network identifier corresponding to the theoretical identifier. If the network identifier is used to indicate that the electronic device supports the Internet of Things function, the configuration information of the electronic device corresponding to the deviceIdCode 1 is sent to the Internet of Things server 400. After receiving the configuration information sent by the mobile phone, the Internet of Things server 400 queries the database based on the configuration information to obtain the device model information. Afterwards, the Internet of Things server 400 sends the device model information to the mobile phone, so that the mobile phone can display it in the display list based on the device model information sent by the Internet of Things service.

[0230] Alternatively, if the network identifier indicates that the electronic device does not support IoT functionality, the electronic device corresponding to deviceIdCode 1 is deleted. Alternatively, a query is performed in the device category list based on deviceIdCode 1 to determine the theoretical identifier in the device category list that is identical to deviceIdCode 1, as well as the network identifier corresponding to the theoretical identifier. If the network identifier indicates that the electronic device supports IoT functionality, configuration information for the electronic device corresponding to deviceIdCode 1 is sent to IoT server 400. After receiving the configuration information sent by the mobile phone, IoT server 400 queries the database based on the configuration information. If no device model information is found, IoT server 400 sends target information to the mobile phone indicating that the device model information was not obtained. After receiving the target information sent by IoT server 400, the mobile phone queries the device category list based on deviceIdCode 1. If a corresponding device icon and device name exist for the device category corresponding to the theoretical identifier corresponding to deviceIdCode 1, the device icon and device name corresponding to the device category are used as the device model information. This allows the mobile phone to display the device model information in the display list. Alternatively, a query is performed in the device category list based on deviceIdCode 1 to determine the theoretical identifier in the device category list that is identical to deviceIdCode 1, as well as the network identifier corresponding to the theoretical identifier. If the network identifier indicates that the electronic device supports IoT functionality, configuration information for the electronic device corresponding to deviceIdCode 1 is sent to IoT server 400. After receiving the configuration information sent by the mobile phone, IoT server 400 performs a query in the database based on the configuration information. If no device model information is found, IoT server 400 sends target information to the mobile phone indicating that the device model information was not obtained. After receiving the target information sent by IoT server 400, the mobile phone performs a query in the device category list based on deviceIdCode 1. If the device category corresponding to the theoretical identifier corresponding to deviceIdCode 1 does not have a corresponding device icon and device name, the mobile phone performs a query in the database based on deviceIdCode 1. If a pre-configured local icon and local name corresponding to deviceIdCode 1 exist, the local icon and local name are used as the device model information. In this way, mobile phones can be displayed in the display list based on device model information.

[0231] In some embodiments, when it is obtained through the target protocol that there is only one electronic device that can be added in the current environment, a display list is directly generated.

[0232] In some embodiments, when the number of electronic devices that can be added to the current environment obtained through the target protocol is greater than or equal to 2, it is necessary to perform deduplication on the addable electronic devices to obtain a display list. For example, when deduplication is performed on the electronic devices bound to the current account and at least two electronic devices that can be added to the current environment, since there is a problem of re-acquisition of electronic devices obtained through the Bluetooth protocol and the local area network protocol, the electronic devices obtained through the local area network protocol and the Bluetooth protocol can be deduplicated to obtain deduplicated electronic devices. Afterwards, the deduplicated electronic devices and the electronic devices obtained through the Digital Living Network Alliance protocol are merged to obtain a merged electronic device. Since there is an electronic device bound to the current account currently logged in by the first application in the merged electronic device, it is necessary to perform deduplication on the electronic devices bound to the current account and the merged electronic devices to obtain electronic devices that can be displayed. Afterwards, based on the electronic devices that can be displayed, a display list containing each electronic device that can be displayed is generated, such as deleting the electronic devices in the merged electronic devices that are identical to the electronic devices bound to the current account (such as the same device identification code used to uniquely identify the electronic device), thereby obtaining electronic devices that can be displayed.

[0233] S13. If no other preset pop-up window is currently displayed and the currently displayed page is the target page, a device list pop-up window is displayed in the target page according to the display list.

[0234] In some embodiments, the display conditions of the device list pop-up window include:

[0235] 1. The device list pop-up window is displayed only once during the lifecycle of the first app (after launch and before the background process is killed). For example, after the first app is launched, a display flag is recorded. For example, the default value of deviceListShowed is false. After the device list pop-up window is displayed on the target page, the default value of the display flag is set to true. The next time the target page is displayed again, the device list pop-up window will not be displayed.

[0236] 2. The first application loads successfully on the target page and is displayed on the top layer. If the target page fails to load, the device list pop-up window will not be displayed even if there are devices that can be displayed in the current device list pop-up window. The device list pop-up window will only be displayed when the currently displayed top layer page is the target page.

[0237] 3. There are currently electronic devices that can be added. When the number of electronic devices that can be added is greater than 1, the device list pop-up window will be displayed.

[0238] In some embodiments, the target page may be a home page.

[0239] In some embodiments, in response to a startup operation, the first application first displays a startup page as shown in FIG24 , and then enters a set homepage, such as the homepage. The first application includes at least one homepage, for example, the first application includes four homepages, namely, homepage 1a as shown in FIG25 , homepage 2a as shown in FIG26 , homepage 3a as shown in FIG27 , and homepage 4a as shown in FIG28 . When the user sets homepage 1a as the homepage, the first application first enters a startup page as shown in FIG24 , and then enters a homepage as shown in FIG25 , in response to a startup operation.

[0240] In some embodiments, a homepage corresponds to a tab page. The homepage is the first tab page of the homepage (i.e., the page displayed after the first application is launched and the startup page is displayed). Pop-ups may be displayed on the homepage, such as the upgrade pop-up window 3a-1, the user guidance pop-up window 4a-1, and the device list pop-up window 5a-1. Only one pop-up window can be displayed at a time.

[0241] In some embodiments, the display priority of the pop-up window includes the priority of the upgrade pop-up window being greater than the priority of the user guidance pop-up window, and the priority of the user guidance pop-up window being greater than the priority of the device list pop-up window.

[0242] In some embodiments, because the first application uses hybrid stack routing management, the tab pages include two forms: Flutter pages (such as homepage 1a, homepage 4a, etc.) and Native pages (such as startup page, homepage 2a, homepage 3a, etc.). If the pop-ups are displayed according to priority, it is necessary to ensure that the high-priority pop-ups do not exist or are closed before displaying the subsequent pop-ups. Therefore, when displaying the device list pop-up, it is necessary to ensure that the upgrade pop-up and the user guidance pop-up are closed.

[0243] From the above, it can be seen that by adopting the display method provided by the present invention, when a user needs to add an electronic device, the user only needs to open the first application installed on the terminal device, and can then check the electronic devices that can be added in the current environment on the target page. The user does not need to manually obtain the electronic devices that can currently be added, thereby avoiding the problem that different users have different proficiency in using terminal devices, which often causes users to be unable to find the electronic devices that can currently be added when adding electronic devices.

[0244] In some feasible examples, in combination with FIG. 23 , as shown in FIG. 29 , the above S12 can be specifically implemented through the following S120 - S122 .

[0245] S120 , performing deduplication processing on the electronic devices respectively obtained by the local area network protocol and the Bluetooth protocol to obtain deduplicated electronic devices.

[0246] S121 . Obtain a merged electronic device based on the deduplicated electronic devices and the electronic devices obtained through the Digital Living Network Alliance protocol.

[0247] S122: De-duplicate electronic devices bound to the current account and the merged electronic devices to generate a display list.

[0248] In some embodiments, for some scenarios where the accuracy of deduplication is not high, it is possible to determine whether the electronic device discovered by the Bluetooth service and the electronic device discovered by the local area network service are the same electronic device through local_name and wifiId. For example, in combination with the example given in S11 above, deduplication is performed using the last 4 digits of local_name and the last 4 digits of wifiId. If the last 4 digits of local_name and the last 4 digits of wifiId are equal, it means that the electronic device discovered by the Bluetooth service and the electronic device discovered by the local area network service are the same electronic device. At this time, the electronic device discovered by the local area network service is retained, the electronic device discovered by the Bluetooth service is deleted, and the retained electronic device discovered by the local area network service is used as the electronic device after deduplication.

[0249] In some embodiments, a 4-digit hexadecimal number can enumerate up to 65,536 devices. When determining whether the electronic device discovered by the Bluetooth service and the electronic device discovered by the local area network service are the same electronic device through local_name and wifi ID, the last 4 digits of local_name and wifiID may be the same, but the electronic device discovered by the Bluetooth service and the electronic device discovered through the local area network service are two different devices. This will incorrectly filter out the electronic device discovered through the Bluetooth service. To this end, the display method provided in the embodiment of the present disclosure deduplicates the electronic devices discovered by the Bluetooth service and the electronic devices discovered by the local area network service through one or more of the category information, media access control address, and network configuration information, thereby ensuring the accuracy of deduplication.

[0250] In some feasible examples, as shown in FIG30 in combination with FIG29 , the above S120 can be specifically implemented through the following S1200 and S1201 .

[0251] S1200: Acquire target information of the electronic device obtained by the local area network protocol and the Bluetooth protocol respectively.

[0252] S1201: Deduplication is performed on electronic devices obtained from the LAN protocol and the Bluetooth protocol based on target information to obtain deduplication electronic devices, wherein the target information includes any one of a media access control address or configuration information corresponding to the mobile hotspot module.

[0253] In some feasible examples, the target information includes a media access control address corresponding to the mobile hotspot module. In conjunction with FIG30 , as shown in FIG31 , the above S1201 can be specifically implemented through the following S12010 and S12011 .

[0254] S12010: Acquire Bluetooth information reported by each electronic device using a Bluetooth protocol, wherein the Bluetooth information includes information added to indicate a media access control address.

[0255] S12011: If the media access control address and Bluetooth information corresponding to the mobile hotspot module are identical, delete the electronic device obtained using the first protocol, retain the electronic device obtained using the second protocol, and use the retained electronic device obtained using the second protocol as the deduplicated electronic device. The first protocol includes any one of a local area network protocol and a Bluetooth protocol, and the second protocol includes any one of the local area network protocol and the Bluetooth protocol except the first protocol.

[0256] In some embodiments, the electronic device obtained by the retained second protocol is used as the deduplicated electronic device.

[0257] In some embodiments, for ease of understanding, assume that the electronic device discovered through the Bluetooth service (e.g., referred to as the Bluetooth device) is B_1, and the electronic device discovered through the LAN service (e.g., referred to as the LAN device) is W_1. The unique MAC identifier of the Wi-Fi module is used to verify that the electronic device discovered by the Bluetooth service and the electronic device discovered by the LAN service are the same electronic device. This solution relies on the MAC address of the Wi-Fi module reported by the Bluetooth device during broadcasting.

[0258] In some embodiments, in conjunction with the example given in Table 2, the process for a Bluetooth device to obtain the MAC address of a Wi-Fi module is as follows: When the first M bits of the manufacturer_data information in the advertising packet content reported by the Bluetooth device are ≥ 128 (e.g., M is equal to 2), the Bluetooth device is deleted and the local area network device is retained. When the first two bits of the manufacturer_data information in the advertising packet content reported by the Bluetooth device are less than 128, such as the "manufacturer_data" information in the advertising packet content of B_1 is "40007638640773889c", the first two bits "40" in "40007638640773889c" are converted to decimal 64. Since 64 < 128, it indicates that the electronic device supports MAC resolution. The MAC address length is then determined by comparing the first two bits of the "manufacturer_data" information in the broadcast packet with a preset threshold (e.g., 64). For example, if the first two bits of the "manufacturer_data" information in the broadcast packet are ≥ 64, the MAC address length is determined to be 12. If the first two bits of the "manufacturer_data" information in the broadcast packet are < 64, the MAC address length is determined to be 8. For example, if the "manufacturer_data" information in the broadcast packet is "40007638640773889c," the first two bits "40" in "40007638640773889c" are converted to decimal 64. Since 64=64, the MAC address length is 12. Then, based on the address length, characters of the address length are truncated from the "manufacturer_data" information in the broadcast packet content as the MAC (the characters after the address length in the "manufacturer_data" information in the broadcast packet content are taken). For example, if the "manufacturer_data" information in the broadcast packet content is "40007638640773889c", the characters starting from the last character "c" are truncated forward with a step length equal to the address length as the MAC, that is, the MAC is "8640773889c".

[0259] Afterwards, the LAN device obtains the Wi-Fi module's MAC address as follows: As shown in Table 2, the definition rules for Wi-FiId specify that the last 12 characters of Wi-FiId represent the Wi-Fi module's MAC address. Since the length of the Wi-Fi module's MAC address obtained by the Bluetooth device is dynamic, the length of the Wi-Fi module's MAC address obtained by the Bluetooth device is compared with 12. When the length of the Wi-Fi module's MAC address obtained by the Bluetooth device is greater than or equal to 12, characters are truncated from the last character of Wi-FiId forward by a step length equal to the length of the Wi-Fi module's MAC address obtained by the Bluetooth device as the MAC address. When the length of the Wi-Fi module's MAC address obtained by the Bluetooth device is less than 12, characters are truncated from the last character of Wi-FiId forward by a step length equal to the length of the Wi-Fi module's MAC address obtained by the Bluetooth device as the MAC address. In some embodiments, based on the above-given quantities, the length of the Wi-Fi module's MAC address obtained by B_1 is 12, and the length of the Wi-Fi module's MAC address obtained by W_1 is 12, with the minimum of these two values ​​being 12. Assume that W_1's Wi-FiId is "86100c00fffe00600000004038640773889c." Among them, the characters with a step length of 12 are intercepted from the last character c as the MAC, that is, the MAC is "8640773889c".

[0260] Afterwards, the MAC address of the Wi-Fi module obtained by the Bluetooth device is compared with the MAC address of the Wi-Fi module obtained by the LAN device. If the MAC address of the Wi-Fi module obtained by the Bluetooth device is the same as the MAC address of the Wi-Fi module obtained by the LAN device, it indicates that the Bluetooth device and the LAN device are the same device. The Bluetooth device can be deleted, the LAN device can be retained, and the retained LAN device can be used as the electronic device after deduplication. If the MAC address of the Wi-Fi module obtained by the Bluetooth device is different from the MAC address of the Wi-Fi module obtained by the LAN device, it indicates that the Bluetooth device and the LAN device are not the same device. Therefore, both need to be retained, that is, the retained Bluetooth device and LAN device can be used as the electronic device after deduplication.

[0261] In some feasible examples, the target information includes configuration information, and the configuration information includes category information of the electronic device. In conjunction with FIG30 , as shown in FIG32 , the above S1201 can be specifically implemented through the following S12012.

[0262] S12012. If electronic devices with the same category information exist, delete the electronic devices obtained using the third protocol, retain the electronic devices obtained using the fourth protocol, and use the retained electronic devices obtained using the fourth protocol as the deduplicated electronic devices. The third protocol includes any one of a local area network protocol and a Bluetooth protocol, and the fourth protocol includes any one of the local area network protocol and the Bluetooth protocol except the first protocol.

[0263] In some embodiments, the retained electronic devices obtained using the fourth protocol are used as deduplicated electronic devices.

[0264] In some embodiments, combined with the example given in S12011 above, the display method provided by the embodiments of the present disclosure can also perform deduplication using the category information to which the Bluetooth device belongs and the category information to which the local area network device belongs. For example, the category information corresponding to B_1 is a washing machine, and the category information corresponding to W_1 is an air conditioner. Since the category information of the two is different, it is necessary to retain both the Bluetooth device and the local area network device, that is, the retained Bluetooth device and the local area network device are used as the deduplicated electronic devices.

[0265] In some embodiments, when the first application is launched, it obtains the current category data and persists it to the memory of the terminal device. Each time the first application is launched, it needs to detect whether the locally stored category data needs to be updated. For example, the first application sends an update request to the IoT server 400, including the update date of the current category data. The IoT server 400 determines that there is no new category data after the update date and sends a non-update indication to the terminal device. Based on this indication, the terminal device will not update the category data for the current time. The category data includes category information, Bluetooth module code information, WiFi module code information, etc.

[0266] Assume that the electronic device is a "range hood" and the corresponding category code is "connector.device.type.greasepump." The Bluetooth module code is "23," and the Wi-Fi module code is "35." The Bluetooth module code or the Wi-Fi module code can be used to uniquely match the corresponding category code. For example, based on the example in Table 2 above, the "service_data" corresponding to B_1 is "0202040f000000," where each two bits correspond to a hexadecimal value. Take bits 3 and 4 of "service_data," for example, "02." Get the hType field corresponding to W_1, for example, "2." Pad the leading bits of hType to the target length. If the target length is 2, the Wi-Fi module code is "02." Then, search the category data for the Bluetooth module code "23" and find that the corresponding category code is "connector.device.type.fridge." The code information "02" of the WiFi module is queried in the category data, and the code information of the category information corresponding to the code information "02" of the WiFi module is obtained as "connector.device.type.fridge".

[0267] Afterwards, when the code information of the category information corresponding to the code information of the Bluetooth module is the same as the code information of the category information corresponding to the code information of the WiFi module, it means that the Bluetooth device and the LAN device are the same electronic device. Therefore, the Bluetooth device can be deleted, the LAN device can be retained, and the retained LAN device can be used as the deduplicated electronic device. When the code information of the category information corresponding to the code information of the Bluetooth module is different from the code information of the category information corresponding to the code information of the WiFi module, it means that the two are not the same electronic device. At this time, both need to be retained, that is, the retained Bluetooth device and LAN device will be used as the deduplicated electronic devices.

[0268] In some feasible examples, the target information includes configuration information, the configuration information includes network configuration information, and the network configuration information includes any one of configured network and unconfigured network. In conjunction with FIG30 , as shown in FIG33 , the above S1201 can be specifically implemented through the following S12013 and S12014.

[0269] S12013: When the network configuration information of the electronic device obtained through the Bluetooth protocol indicates that the electronic device is not network configured, retain the electronic device whose network configuration information indicates that the electronic device is not network configured, and use the retained electronic device whose network configuration information indicates that the electronic device is not network configured as the deduplicated electronic device.

[0270] S12014: When the network configuration information of the electronic device obtained through the Bluetooth protocol indicates that the electronic device has been configured, delete the electronic device whose network configuration information indicates that the electronic device has been configured.

[0271] In some embodiments, the electronic devices whose network configuration information is retained as unconfigured are used as the deduplicated electronic devices.

[0272] In some embodiments, combined with the example given in S12011 above, the display method provided by the embodiment of the present disclosure can use the network configuration information of the electronic device to determine whether the Bluetooth device and the local area network device are the same electronic device, because the electronic device cannot be discovered by the local area network service when it is not networked.

[0273] In some embodiments, the first application can determine network configuration information based on the "service_data" field in the broadcast packet reported by B_1. For example, if "service_data" is "0202040f000000," where each two bits correspond to a hexadecimal value, the first application extracts bits 5 and 6 of "service_data" and finds the value "01." The first application then converts "01" to an 8-bit binary value, "00000100," and extracts bits 4 through 6, "001," from "00000100."

[0274] Among them, "000" indicates that the network configuration information is not configured, and "001" indicates that the network configuration information is configured.

[0275] When the network configuration information is not configured, it means that the electronic device has not been connected to the network, so the Bluetooth device needs to be retained. When the network configuration information is configured, it means that the electronic device has been connected to the network, so the Bluetooth device can be deleted.

[0276] In some feasible examples, in combination with FIG. 29 , as shown in FIG. 34 , the above S122 can be specifically implemented through the following S1220 .

[0277] S1220: Delete the electronic devices bound to the current account from the merged electronic devices to obtain electronic devices that can be added.

[0278] In some embodiments, if a device is found that has already been bound to the current account, the device is removed from the homepage device list to avoid the user's home bound devices repeatedly popping up every time the user starts up the device, which affects the user experience.

[0279] In some feasible examples, the device list pop-up window also includes an ignore control for not displaying the device list within a preset time, and each electronic device corresponds to one ignore control. In conjunction with Figure 23, as shown in Figure 35, the display method provided by the embodiment of the present disclosure further includes: S14.

[0280] S14. In response to the selection operation of the ignore control, the electronic device corresponding to the ignore control is deleted from the device list pop-up window, and the electronic device corresponding to the ignore control is no longer displayed in the device list pop-up window displayed within a preset time.

[0281] In some embodiments, each time the first application is started, a pop-up window with a list of devices that meet the conditions will automatically pop up. If the electronic device found in the device list pop-up window is a neighbor's TV, or an electronic device that the user does not want to bind, the user experience will be affected if the electronic device continues to be displayed in the device list pop-up window each time the first application is started. Therefore, the display method provided in the embodiment of the present disclosure is to optimize this problem and provide the user with an entry to ignore the electronic device. The user can ignore all or ignore a single device with one click. The first application locally records the device ignore mark as a basis for whether the device is displayed in the device list next time.

[0282] In some embodiments, in conjunction with the homepage 5a shown in FIG28 , the user can select the electronic device to be added in the device list pop-up window 5a-1 displayed in the homepage 5a. For example, when the user needs to add the refrigerator RDDDEE-af(b888b), the user can select the add control 5a-1-1 corresponding to the refrigerator RDDDEE-af(b888b), thereby adding the refrigerator RDDDEE-af(b888b) to the AAA home. Alternatively, when the user no longer needs to display the refrigerator RDDDEE-af(b888b) in the device list pop-up window, the user can select the ignore control 5a-1-2 corresponding to the refrigerator RDDDEE-af(b888b), thereby no longer displaying the refrigerator RDDDEE-af(b888b) in the device list pop-up window.

[0283] In some embodiments, to prevent the user from ignoring an electronic device in the device list pop-up window and then needing to display the electronic device in the device list pop-up window again, the first application can periodically (e.g., once a month) prompt the user whether to display the electronic device in the device list pop-up window.

[0284] In some feasible examples, in combination with FIG. 23 , as shown in FIG. 36 , the above S13 can be specifically implemented through the following S130 - S132 .

[0285] S130: Obtain the priority of the category to which each addable electronic device belongs.

[0286] S131 , sorting the addable electronic devices in descending order of priority to obtain a display order.

[0287] S132: If no other preset pop-up window is currently displayed and the currently displayed page is the target page, the addable electronic devices are displayed in the device list pop-up window displayed on the target page in the order of display.

[0288] In some embodiments, since there are differences in the shipping quantities corresponding to different categories, in order to improve the user experience, the display method provided in the embodiments of the present disclosure sorts the categories to which the electronic devices displayed in the device list pop-up window belong based on the shipping quantities corresponding to different categories, thereby ensuring the order of display of the electronic devices displayed in the device list pop-up window.

[0289] In some embodiments, the priority of the first electronic device is greater than the priority of the second electronic device.

[0290] In some embodiments, electronic devices of the same priority are displayed in the device list pop-up window in ascending order of discovery time.

[0291] In the embodiments of the present disclosure, a terminal device generally refers to an electronic device with communication processing and control functions, including but not limited to mobile phones, computers, tablet computers, display devices, etc.

[0292] The terminal device includes at least one of a communication device, a detector, a device interface, a controller, a display, an audio output device, a memory, a power supply, and a user input interface.

[0293] In some embodiments, the display includes a display component for presenting an image and a driver component for driving the image display. The display is configured to receive image signals output from the controller for display. For example, the display can be configured to display video content, image content, menu control interface components, and user control UI interfaces.

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

[0295] In the embodiments of the present disclosure, a display device generally refers to a device capable of displaying images and processing data. For example, a display device includes but is not limited to smart TVs, mobile terminals, computers, monitors, advertising screens, wearable devices, virtual reality devices, augmented reality devices, etc.

[0296] In the IoT system, the TV serves as the central manager of the home and accounts for a high proportion of daily household use, leading to a corresponding demand for TV memberships. There are two ways to purchase TV memberships: 1) log in to your account on the TV and purchase a TV membership through the TV's membership purchase portal. 2) bind the TV to a household, allowing all family members to view the TV in their mobile device list and purchase a TV membership through the mobile portal.

[0297] However, using a mobile phone to purchase a TV membership only works if the TV is already associated with a household and the account logged in with the phone is associated with the same household. However, the device list often includes TVs discovered via the local area network and TVs that were logged out after being associated. These TVs may not be logged in to any account, or may be logged in but not in the household associated with the mobile phone account.

[0298] In some embodiments, if a TV is not logged into any account and you want to purchase a membership for that TV using your phone, you need to log in to your mobile account on the TV login screen and use the Add Device control on the mobile homepage to bind the TV to the household associated with your mobile account. A card corresponding to the TV will appear in the device list on your phone. Selecting the card will take you to the TV details page, which includes a Purchase Membership control. Selecting this control will allow you to purchase a membership for the TV.

[0299] In some embodiments, if a TV is already logged in to an account, and the account logged in to the phone is not in the same household as the TV, if you want to purchase a membership for the TV on your phone, you need to log out of the currently logged-in account on the TV and log in to the mobile account. After the TV successfully logs in to the mobile account, use the Add Device control on the mobile homepage to reassign the TV from the household of the original logged-in account to the household of the mobile account. A card corresponding to the TV will appear in the device list. By selecting the card corresponding to the TV, you will enter the TV details page, which includes a Purchase Membership control. After selecting the Purchase Membership control, you can purchase a membership for the TV.

[0300] Therefore, when the TV is not logged in to the account, or the TV is logged in to the account but the account logged in to the mobile phone is not in the same household as the TV, the membership purchase process is complicated and the mobile phone cannot quickly purchase a membership for the TV.

[0301] The present disclosure provides a terminal device including a display and a controller. As shown in FIG37 , the controller (at least one processor) runs an application program to cause the terminal device to perform the following steps:

[0302] Step S101: receiving a user input instruction for selecting a display device control, wherein the instruction for selecting a display device control is used to instruct the display of a device details page, which includes at least one member control.

[0303] The display device is equipped with a desktop application that provides multiple service modules to implement different functions based on the service modules provided by the desktop application. The desktop application provides access to signal sources and access to installed third-party applications (icons). It can directly play media data or call installed third-party applications to play media data.

[0304] Membership includes membership for desktop applications and third-party applications. Membership types include, but are not limited to, film and television membership, children's membership, education membership, and film and television single-point membership. It should be noted that when purchasing a membership for a display device through a terminal device, it is necessary to open a specific application and log in to the user account. In this disclosure, the first account is logged in. After the first account successfully logs in, a device list is displayed on the application homepage. The device list includes devices bound to the current home of the first account and devices discovered through the local area network.

[0305] After receiving the user's instruction to open a specific application, the DLNA (Digital Living Network Alliance) service can be used to discover all device collections on the same local area network. The bound devices are removed from the device collection to form a new device collection. Based on the new device collection, a local device display box pops up on the application home page. The local device display box includes at least one local device control. The user can choose to add the local device to the device list on the home page, or choose not to add the local device to the device list on the home page. Among them, the local device can only be displayed in the device list corresponding to the first account and cannot be shared with other members of the family.

[0306] As shown in Figure 38, the local device display box includes a living room TV control 21, an air conditioning control 22, an add control 23, and a close control 24. If the user selects the living room TV control 21 and clicks the add control 23, the living room TV corresponding to the living room TV control 21 can be added to the device list. As shown in Figure 39, the device list on the application homepage includes a central air conditioning control 31, a bedroom TV control 32, and a living room TV control 33. The TV corresponding to the bedroom TV control 32 is the TV bound to the first logged-in account, and the TV corresponding to the living room TV control 33 is the TV discovered via the local area network.

[0307] The device list on the home page of the application includes two types of devices. One is a local device. A local device refers to a device discovered through a local area network, and the device is added to the local cache of the terminal device. Among them, the local device does not verify the device login status, and only the user account itself can control the device, and it cannot be shared with other family members. The other is a bound device. Bound device means binding the device to the target family through methods such as scanning a code to bind, so that multiple family members can share it. It should be noted that the device must be logged in to the account when performing device binding, but the user may log out after the device is bound. After the device is added to the device list, the user can intelligently control the local device and the bound device through the terminal device.

[0308] In the embodiment of the present disclosure, the display device includes a display device discovered through a local area network and a bound display device.

[0309] In some embodiments, the step of receiving a user input instruction to select a display device control includes:

[0310] In response to a user input instruction to open an application, the display is controlled to display a home page, the home page includes a device list, and the device list includes at least one display device control.

[0311] Receive user input for selecting a display device control. In some embodiments, the step of receiving user input for selecting a display device control includes: in response to a user input for opening an application, controlling the display to display a home page, the home page including a personal information control. In response to a user input for selecting a personal information control, controlling the display to display a personal information page, the personal information page including a device management control. In response to a user input for selecting a device management control, controlling the display to display a device management page, the device management page including at least one display device control.

[0312] It should be noted that the device management page displays all device controls bound to all homes where the user account is located.

[0313] Receive a user input instruction to select a display device control. Step S102: Obtain device information of the display device corresponding to the display device control. The step of obtaining the device information of the display device corresponding to the display device control includes: obtaining a device ID of the display device.

[0314] After receiving the user input to open the application, the terminal device will send a request to obtain the bound device to the Internet of Things server 400 (AIoT subsystem), which includes the first account and the family selected by the first account (current family). The Internet of Things server 400 will issue the device information of the bound device based on the first account and all families. The device information of the bound device includes the device name and device identification. While sending the request to obtain the bound device, the terminal device will also obtain the basic device information of the local area network device from the cache. The basic device information of the local area network includes the device name and device identification. The device name is used to display in the device list, and the device identification is cached in the memory. The memory cache declaration period is during the startup of this application. After the application is killed, the contents of the memory cache are recycled by the system.

[0315] It should be noted that the basic device information for LAN devices is obtained using the Internet Protocol (IP) and port number after receiving a user input command to add the local display device to the device list on the home page. This basic device information for LAN devices is stored in the terminal device (persistent cache) and remains available until the application deletes it.

[0316] After receiving updated device information (i.e., a change message to the bound device list) pushed by the message server, the bound device list is updated based on the updated device information. The updated device information includes the device name and device ID. A device information request is sent to the business server (business subsystem), including the device ID. The business subsystem stores the basic device information of the display device and also uploads the login information of the display device to the business subsystem in real time. The device information issued by the business server based on the device ID is received.

[0317] Device information includes basic device information and login information. Basic device information includes the license plate, default alias, and API version. Login information includes the login account's mobile phone number, customer ID, nickname, and password.

[0318] If the display device is not logged in to an account, the service server will only send the basic device information of the display device and the customer ID of the logged in account as anonymous. If the display device is logged in to an account, the service server will send the basic device information and login information of the display device.

[0319] Step 103: Determine whether the login status is the account not logged in status. The step of determining whether the login status is the account not logged in status includes:

[0320] Determine whether the device information includes a password (Token). If the device information includes a password, determine that the login status is a logged-in account status.

[0321] If the device information does not include a password, the login status is determined to be the account not logged in state. If the login status is the account not logged in state, step S104 is executed: the target account is determined to be the first account. The first account is the account logged in by the terminal device. If the display device does not have an account logged in, the first account logged in by the terminal device application is the target account for the membership purchase. For example, if the first account is C2, the target account for the membership purchase is C2.

[0322] If the display device is not logged into an account, the purchase account identifier is set to a first preset value. In some embodiments, the purchase account identifier (isBuyForTVAccount) is set to false. The purchase account identifier is used to indicate whether the current purchase process is for the account currently logged into the display device. Setting the purchase account identifier to the first preset value indicates that the current purchase process is not for the account currently logged into the display device. When the purchase account identifier is false, it is used to confirm the user's purchase account information before payment.

[0323] If the login status is not "account not logged in," that is, "account logged in," step S105 is executed: determining that the target account is a second account. The second account is the account logged in by the display device. If the display device is logged in, the second account logged in by the display device is the target account for the membership purchase. For example, if the second account is C1, the target account for the membership purchase is C1.

[0324] If the display device is logged in to an account, the purchase account identifier is set to a second preset value. In some embodiments, the purchase account identifier is set to true. The purchase account identifier is used to indicate whether the current purchase process is for the account currently logged in to the display device. Setting the purchase account identifier to the second preset value indicates that the current purchase process is for the account currently logged in to the display device. When the purchase account identifier is true, there is no need to prompt the user for the purchase account information before payment.

[0325] As shown in Figure 40, after receiving the user input instruction to select the TV control, the mobile phone sends a TV information query request to the service server. The TV information request includes the device identification of the TV. The service server queries the device information corresponding to the device identification and sends the device information to the mobile phone. The device information includes the TV license plate, TV nickname, and TV version number. If the TV is not logged in to the account, the customer identification is anonymous. If the TV is logged in to the account, the device information also includes the TV login account mobile phone number, nickname, customer identification and password. The mobile phone determines whether the device information includes a password, that is, determines whether the display device is logged in to the account. If the device information includes a password, that is, the display device login account is displayed, then the target account is determined to be the TV login account. If the device information does not include a password, that is, the display device is not logged in to the account, then the target account is determined to be the mobile phone login account.

[0326] Step 106: Obtain the membership status corresponding to the target account. The steps of obtaining the membership status corresponding to the target account include:

[0327] The member type is determined based on the license information, and a member information request is sent to the server so that the server can feedback a list of activated members based on the target account, wherein the member information request includes the target account.

[0328] The display device can only be used by members who have purchased the corresponding license plate. For example, the display device with license plate XXX can only be used by members of type A. If the user account purchases a member of type B, it cannot be used on the display device with license plate XXX.

[0329] There's a fixed mapping between the license plate and the membership type (Resource ID) of a display device. Given a display device's license plate, the corresponding membership type can be determined based on this mapping. Membership types include third-party applications and desktop applications.

[0330] In some embodiments, after determining the membership type, the terminal device sends a membership information request to the membership server (membership subsystem). The membership information request includes the target account number. The membership server searches the corresponding membership activation list based on the target account number and sends a list of activated members to the terminal device. The activated member list includes the member type and the corresponding membership category under that member type. The activated member list also includes the member's expiration date.

[0331] In some embodiments, when there is only one type of membership, after receiving the activated membership list, the terminal device determines whether the determined membership type is in the activated membership list. If the determined membership type is in the activated membership list, the membership status is determined to be activated. If the determined membership type is not in the activated membership list, the membership status is determined to be unactivated.

[0332] In some embodiments, in the case where there are multiple types of membership, after receiving the activated membership list, the terminal device determines whether the determined membership type is in the activated membership list. If the determined membership type is in the activated membership list, it is determined whether the membership type selected by the user is the same as the membership type corresponding to the membership type. If the membership type selected by the user is the same as the membership type corresponding to the membership type, the membership status is determined to be activated. If the membership type selected by the user is different from the membership type corresponding to the membership type, the membership status is determined to be unactivated. If the determined membership type is not in the activated membership list, the membership status is determined to be unactivated.

[0333] In some embodiments, the activated membership list is shown in Table 3.

[0334] If the membership type is Type A and the membership category is Junior Membership, the membership status is determined to be activated. If the membership type is Type B and the membership category is Junior Membership, the membership status is determined to be unactivated. If the membership type is Type C and the membership category is Junior Membership, the membership status is determined to be unactivated.

[0335] In some embodiments, a membership activation status request is sent to a membership server. The membership activation status request includes the target account number, membership type, and membership category selected by the user. The membership server determines the member's activation status based on the target account number, membership type, and membership category, and sends the member's activation status to the terminal device. The member's activation status includes activated and unactivated.

[0336] When the membership status is activated, the membership ID corresponding to the membership status is set to a preset value, such as 1. When the membership status is unactivated, the membership ID corresponding to the membership status is set to a non-preset value, such as 0.

[0337] Step S107: Determine the display content of the member control in the device details page according to the member status.

[0338] Among them, the display content of the member control is different for different member statuses.

[0339] When the membership status is activated, the display content of the membership control is determined to be renewal content, and the renewal content includes the membership validity period and the renewal control. In particular, when the target account is the first account, that is, when the device is displayed as not logged in to the account, the renewal content also includes the login control.

[0340] When the member status is unactivated, the display content of the member control is determined to be activation content, and the activation content includes activation controls. Wherein, when the target account is the first account, that is, when the display device is in the account unlogged state, the activation content also includes a login control.

[0341] After receiving a user input instruction to select a display device control, the display device sends a details page data request to the server. The server sends the details page data based on the details page data request. The display device draws and displays the device details page based on the details page data. The device details page includes at least one member control.

[0342] In some embodiments, the membership control in the device details page is fixed content, that is, it does not display whether the current membership is activated or not activated, and can be directly obtained from the details page data.

[0343] In some embodiments, the member control on the device details page can determine the display content of the member control based on the member activation status, that is, display whether the current member is activated or not activated. The member control display content needs to be further determined based on the member activation status.

[0344] In some embodiments, in response to user input selecting an instruction to display a device control, the display content of the member control is determined and the details page data is obtained. After both data are determined, the device details page is drawn and displayed based on the display content of the member control and the details page data.

[0345] In some embodiments, in response to a user input selecting to display a device control, if details page data is first acquired, the device details page is drawn and displayed based on the details page data. The displayed content of the member control is either empty or fixed. After the display content of the member control is determined, the displayed content of the member control is updated.

[0346] In some embodiments, the membership control is an unselectable control, that is, you can only jump to the membership purchase page by selecting the renewal control and the activation control.

[0347] In some embodiments, the membership control is a selectable control, and after selecting the membership control, the user can jump to the membership purchase page.

[0348] In some embodiments, in Figure 39, a user selects the living room TV control 33 instruction, and in response to the instruction, the display displays the living room TV details page. As shown in Figure 41, the living room TV details page includes a film and television membership control 51 and a children's membership control 52. Since the film and television membership has been activated under this account, the corresponding display content of the film and television membership control 51 is renewal content, and the renewal content includes an immediate renewal control 511, an immediate login control 512, and a membership validity period 513. Figure 41 shows the situation where the display device is not logged into the account. If the display device logs in to the account, the immediate login control 512 is not displayed. Since the children's membership has not been activated under this account, the corresponding display content of the children's membership control 52 is activation content, and the activation content includes an immediate activation control 521.

[0349] In some embodiments, a user input instruction to select a membership control, a renewal control, or an activation control is received.

[0350] The user can click on the membership control, renewal control or activation control. For example, in Figure 41, if the user clicks on the movie membership control 51 or the immediate renewal control 511, an instruction is input to display the purchase page of the living room TV movie membership. If the user clicks on the children's membership control 52 or the immediate activation control 521, an instruction is input to display the purchase page of the living room TV children's membership.

[0351] In response to an instruction to select a membership control, renewal control, or activation control, the display is controlled to display a membership purchase page. The membership purchase page includes at least one purchase control. Different purchase controls correspond to different display contents, including the membership validity period and price.

[0352] In some embodiments, the step of controlling the display to display the member purchase page includes: obtaining member detail information corresponding to the member type.

[0353] The terminal device sends a membership details request to the e-commerce server (e-commerce subsystem). The membership details request includes the membership type and membership category. If there is only one membership category, the membership category does not need to be sent; the member can be locked by the membership type. The e-commerce server queries the membership details corresponding to the membership type and membership category and sends the membership details to the terminal device. The membership details are used to display the membership purchase page. The membership details include activation details and renewal details. The activation details are used to display the membership purchase page if the first account has not activated membership. The renewal details are used to display the membership renewal page if the first account has activated membership.

[0354] In some embodiments, the membership type is type A and the membership category is child membership. The e-commerce server may issue activation details and renewal details for type A child membership. A member purchase page is drawn based on the member details and the activated member list. A determination is made as to whether the member type is in the activated member list. If the member type is in the activated member list, a member renewal page is drawn based on the renewal details. If the member type is not in the activated member list, a member activation page is drawn based on the activation details. The display is controlled to display the member renewal page or the member activation page.

[0355] In some embodiments, the step of controlling the display to display the member purchase page includes:

[0356] Obtain the member details corresponding to the member type, including activation details and renewal details. Obtain the member ID corresponding to the member status. If the member ID is the preset value, determine that the member status is activated, draw the member renewal page based on the renewal details, and control the display to display the member renewal page. If the member ID is not the preset value, determine that the member status is unactivated, draw the member activation page based on the activation details, and control the display to display the member activation page. After receiving the user input to select the purchase control, purchase the membership corresponding to the purchase control for the target account.

[0357] In some embodiments, in FIG41 , if a user input is received to select the movie membership control 51, a membership renewal page is displayed, as shown in FIG42 . The membership renewal page includes a switch TV control 61, a monthly subscription control 62, a continuous monthly subscription control 63, an annual subscription control 64, and an immediate renewal control 65. The switch TV control 61 is used to switch the TV to which the subscription is purchased. After selecting the monthly subscription control 62 or the like, the immediate renewal control 65 can be selected to renew the movie membership for the TV.

[0358] In Figure 41, if the user inputs a command to select the children's membership control 52, the membership activation page is displayed, as shown in Figure 43. The membership activation page includes a switch TV control 71, a monthly subscription control 72, a continuous monthly subscription control 73, an annual subscription control 74, and an immediate activation control 75. After selecting the monthly subscription control 72, you can select the immediate activation control 75 to renew the children's TV membership.

[0359] In some embodiments, the membership purchase interface includes a device switching control. Upon receiving a user input selecting the device switching control, a device switching list is displayed, which displays the available display device controls. Upon receiving a user input selecting the display device control, device information for the switched display device is obtained, a target account is re-determined, and a membership is purchased for the target account.

[0360] In some embodiments, after receiving a user input command selecting a purchase control / immediate renewal control / immediate activation control, a detection is performed to determine whether the purchase account identifier is a first preset value. If the purchase account identifier is the first preset value, for example, the first preset value is false, the display is controlled to display a prompt page prompting the user to purchase a membership for the account currently logged in to the terminal device. If the purchase account identifier is not the first preset value, that is, the second preset value, for example, the second preset value is true, the display is not controlled to display the prompt page.

[0361] In some embodiments, as shown in Figure 44, the prompt page includes prompt information, a confirmation control 81, and a cancel control 82. After receiving the user input instruction to select the confirmation control 81, the TV membership is purchased for the first account.

[0362] As shown in Figure 45, after obtaining the display device license plate, the terminal device matches the member type based on the license plate and sends a member details request to the e-commerce server. The member details request includes the member type. The e-commerce server issues the member details corresponding to the member type. The member details include activation details and renewal details. The terminal device sends a member activation list request to the member server, including the target account. The member server issues a list of activated members based on the target account. The terminal device determines the member activation status based on the activated list. If the member is activated, the member renewal page is displayed based on the renewal details. If the member is not activated, the member activation page is displayed based on the activation details. After receiving the user's renewal / activation instruction, the terminal device determines whether the purchasing account flag is true. If the purchasing account flag is false, a prompt page is displayed. After the user confirms the purchasing account, the order process begins. If the purchasing account flag is true, the order process begins. The order process involves sending an order request to the payment server. The order request includes the target account and member information (the purchase control selected by the user). The payment server generates order information based on the order request and sends it to the terminal device. The terminal device opens the payment page based on the order information.

[0363] As shown in Figure 39, the home page also includes a current home control 34 and a scan control 35. Click the current home control 34 to switch the selected home control. A user account can join multiple families and can switch the current home to any joined family. The device list on the home page displays the devices bound to the current family and local devices. After the user selects the scan control 35, the scan code page is displayed, as shown in Figure 46. After scanning the identification code displayed on the display screen of the display device, the identification information can be determined and a binding request can be sent to the Internet of Things server 400. The binding request includes the target binding home and device identification. The target binding home is the current home where the terminal application login account is located. If the display device is not in the current home, the Internet of Things server 400 will rebind the display device to the current home. The original home binding relationship of the display device is destroyed, and the original family members' ability to intelligently control the display device cannot be guaranteed.

[0364] If the display device is not logged in, after successfully purchasing a membership for the target account, the terminal device will automatically jump to the code scanning page, where the identification code displayed on the display device's screen can be scanned. The identification code includes but is not limited to QR codes and barcodes. The identification code can be displayed on the display device's account login interface.

[0365] After scanning the identification code, the terminal device identifies the identification code and obtains identification information, which includes parameters such as the display device's UUID (Universally Unique Identifier) ​​and rKey.

[0366] The terminal device sends a login request to the account server. The login request includes parameters such as the display device's UUID and rKey, as well as the first account, password, and login method (scan code login). The account server can determine the device identifier of the display device based on the display device's UUID and rKey parameters, and instruct the display device corresponding to the device identifier to log in to the first account. After receiving a successful login message from the display device, the account server sends a successful login message to the terminal device.

[0367] After receiving the successful device login message, the terminal device sends a first binding request to IoT server 400. The first binding request includes the first account, the device ID of the display device, the target binding family, and the target owner (owner). The target binding family is empty, and the target owner is the first account. Compared to ordinary family members, the device owner has greater control over the device.

[0368] In some embodiments, after clicking the Scan control to enter the scanning page, the household designation flag is set to 1. A household designation flag of 1 indicates that the target household is not empty, that is, the target household is the household selected by the user (the current household). After successfully jumping to the scanning page after a membership purchase, the household designation flag is set to 0. A household designation flag of 0 indicates that the target household is empty, that is, no target household is specified.

[0369] The embodiment of the present disclosure provides a server, wherein the server is an Internet of Things server 400. As shown in FIG47 , the server performs the following steps:

[0370] Step S1101: Receive a first binding request.

[0371] The first binding request is sent after the terminal device purchases a membership for a display device that has not logged in to an account and logs in to the first account by scanning a code. The first binding request includes the target account, the device identifier of the display device, the target binding family and the target owner. The target binding family is empty and the target owner is the first account.

[0372] After receiving the first binding request, the IoT server 400 will first determine whether there is a target binding family. If there is a target binding family, the display device will be bound to the target binding family. Since the target binding family of the first binding request of the present disclosure is empty, step S1102 is executed.

[0373] Step S1102: query and display the bound family of the device based on the device identification.

[0374] Step S1103: Determine whether the bound family is empty.

[0375] If the bound family is not empty, step S1104 is executed: obtaining the bound family of the display device, that is, the first family.

[0376] Step S1105: Determine whether the first account is in the first family.

[0377] If the first account is in the first family, step S1106 is executed: the owner of the display device is changed to the first account.

[0378] It should be noted that the first family disclosed in this disclosure includes not only the family selected by the first account of the terminal device (current family), but also families not selected by the first account. If the first account is in the first family, the display device will not be bound to the family selected by the first account.

[0379] In some embodiments, the first account is bound to Family A, Family B, and Family C respectively. The family currently selected by the first account is Family A. The TV is bound to Family B. Usually, after the TV logs in to the first account by scanning the code, it is necessary to specify the target binding family as Family A selected by the first account when sending the binding request. If the TV is not in Family A selected by the current terminal device, the TV needs to be unbound from Family B and rebound to Family A. However, the binding request of the solution disclosed in the present invention does not specify the target binding family. When the TV and the first account are both in Family B, there is no need to rebind the TV to Family A.

[0380] In the embodiment of the present disclosure, after purchasing a membership for a display device, if the display device has not logged in to an account, the user needs to be guided to scan a code to log in. The login operation at this time is not triggered by the user's autonomous binding process. On the premise of ensuring that the account logged in to the display device is the device owner, the existing family binding relationship of the display device can be maintained to the maximum extent to ensure the intelligent control capabilities of the original family members.

[0381] If the first account is not in the first family, execute step S1107: determine whether the first account has selected a family. If the first account has selected a family, execute step S1108: obtain the family selected by the first account, that is, the second family, and bind the display device to the second family, and change the owner of the display device to the first account. If the bound family is empty, execute step S1109: create a second family, bind the display device to the second family, and change the owner of the display device to the first account. If the original owner of the display device is the first account, there is no need to change the owner of the display device. Send the binding result to the terminal device. The terminal device updates the family and device list page according to the binding result.

[0382] As shown in Figure 48, if the display device is not logged in, after successfully purchasing a membership for account C2, the terminal device displays the QR code scanning page, as shown in Figure 46. The scanned QR code is parsed to obtain identification information, and a confirmation page, as shown in Figure 49, is displayed. The identification information includes parameters such as the display device's UUID and rKey. After the user clicks the confirm login control, a login request is sent to the account server. The login request includes the identification information and account C2. The account server determines the device ID based on the identification information and logs the display device corresponding to the device ID into account C2. After detecting that the display device has successfully logged in, the account server sends a successful login message to the terminal device. The terminal device sends a binding request to IoT server 400. The binding request includes account C2, the device ID, the target binding family, and the target owner. If the target binding family is empty, the target owner is account C2. IoT server 400 queries the binding relationship between the display device and account C2. If both the display device and account C2 are in household 1, the owner of the display device is changed to account C2, maintaining the original binding relationship with account C2. If the display device is in Home 1, but account C2 is not in Home 1, query account C2's current home, which is Home 2, bind the display device to Home 2, and change the display device's owner to account C2. If the display device is not bound to a home, query account C2's current home, which is Home 2, bind the display device to Home 2, and change the display device's owner to account C2.

[0383] After device binding is complete, IoT server 400 sends the binding result to the terminal device. The terminal device updates its homepage based on the binding result. Updating the homepage includes updating the homepage and the device list. Updating the homepage displays the home of account C2 on the terminal device when creating a second home. Updating the device list displays the newly bound devices in addition to the original device list.

[0384] In some embodiments, after receiving a user input instruction to select a login control, the display is controlled to display a code scanning page. Identification information is determined based on the identification code. The identification information and the first account are sent to the account server, so that the account server instructs the display device to log in to the first account. A first binding request is sent to the IoT server 400. The first binding request includes the first account, the device identifier of the display device, the target binding family, and the target owner. The target binding family is empty, and the target owner is the first account. A first binding result is received from the IoT server 400 based on the first binding request. The homepage is updated based on the first binding result.

[0385] In some embodiments, as shown in FIG41 , after receiving an instruction from the user to select the login control 512 , a code scanning page is displayed, as shown in FIG46 .

[0386] In the embodiment of the present disclosure, when the TV is not logged in to the account and the terminal device login account has activated a membership, the process of directly entering the display device login terminal device account can be entered by selecting the login control, without specifying the target binding family, so as to maximize the maintenance of the existing family binding relationship of the display device to ensure the intelligent control capabilities of the original family members.

[0387] If the device displays no account logged in, after successfully purchasing a membership for the target account, the terminal device will automatically jump to the QR code scanning page. The user can choose to directly exit the QR code scanning page and enter the account and password on the account login interface of the device, or enter the account and verification code to log in.

[0388] The embodiment of the present disclosure provides a server, wherein the server is an Internet of Things server 400. The server performs the following steps:

[0389] Receive push messages from the account server. These push messages are sent by the account server after detecting a login from the first account. The push message includes the login device, login method, the first account, and the device identifier of the display device. Login devices include various types, such as display devices, air conditioners, refrigerators, and dishwashers. Login methods include QR code scanning (App Scan) and manual login.

[0390] When the user enters the account information, the display device sends the account information to the account server. The account server verifies the account information and, if successful, instructs the display device to log in to the first account and sends a push message to the IoT server 400.

[0391] Determine whether the login device is a display device. If the login device is a display device, determine whether the login method is scan code login. If the login method is not scan code login, query the bound family of the display device based on the device identifier. Determine whether the bound family is empty. If the bound family is not empty, obtain the bound family of the display device, that is, the first family. Determine whether the first account is in the first family. If the first account is in the first family, change the owner of the display device to the first account. If the first account is not in the first family, obtain the family of the first account, that is, the second family, and bind the display device to the second family, and change the owner of the display device to the first account. If the bound family is empty, execute the steps of obtaining the family of the first account and subsequent steps. If the login device is not a display device, discard the message and do not process it. If the login method is scan code login, discard the message and do not process it. Because the terminal device application scan code login process has already been initiated by the application, it will not be processed again at this time.

[0392] As shown in Figure 50, under the condition that the display device has not logged in to the account, after the terminal device successfully purchases a membership for account C2, the display device sends the login information manually entered by the user on the login interface to the account server. Among them, the login information includes account C2 and password. After successful verification, the account server executes the account login, that is, the display device logs in to account C2. The account server sends a push message to the Internet of Things server 400. The push message includes the login device, login method, account C2 and device identification. When the login device is not a display device or the login method is to scan the code to log in, the Internet of Things server 400 does not process the push message. When the login device is a display device and the login method is not to scan the code to log in, the binding relationship between the display device and account C2 is queried. The following process is the same as the process in Figure 48 and will not be repeated here.

[0393] After device binding is complete, an update message containing the newly bound device list and the newly created home is sent to the messaging server. The update message includes the bound home and updated device information. The messaging server pushes the updated device information to all members of the bound home. The end device updates the home and device list pages based on the updated device information.

[0394] Under the condition that the display device has logged in to the account, after the terminal device successfully purchases a membership for the second account, it sends a second binding request to the Internet of Things server 400. The second binding request includes the second account, the device identifier of the display device, the target binding family and the target owner. The target binding family is empty and the target owner is the second account.

[0395] The embodiment of the present disclosure provides a server, wherein the server is an Internet of Things server 400. The server performs the following steps:

[0396] Receive the second binding request. The second binding request is sent by the terminal device after purchasing a membership for the display device that has logged in the second account. The second binding request includes the second account, the device identification of the display device, the target binding family and the target owner. The target binding family is empty, and the target owner is the second account. After receiving the second binding request, the Internet of Things server 400 will first determine whether there is a target binding family. If there is a target binding family, the display device will be bound to the target binding family. Since the target binding family of the second binding request of the present disclosure is empty, the binding family of the display device is queried based on the device identification. Determine whether the binding family is empty. If the binding family is not empty, obtain the binding family of the display device, that is, the first family.

[0397] Determine whether the second account is in the first home. If the second account is in the first home, change the owner of the display device to the second account.

[0398] If the second account is not in the first household, the second account's household is obtained, i.e., the second household, and the display device is bound to the second household, and the owner of the display device is changed to the second account. If the bound household is empty, the second account's household is obtained and subsequent steps are performed. The terminal device receives the second binding result issued by the IoT server based on the second binding request.

[0399] As shown in Figure 51, after successfully purchasing a membership for account C1, the terminal device, displaying the device's login information, sends a binding request to IoT server 400. The binding request includes account C1, the device's identifier, the target binding family, and the target owner. The target binding family is empty, and the target owner is account C1. IoT server 400 queries the binding relationship between the display device and account C1. The following process is similar to that in Figure 12 and will not be repeated here.

[0400] The disclosed embodiments enable quick membership purchases for display devices in different login states. After purchasing a membership, users are guided to log in based on their login status and automatically bind to the display device based on its binding status, achieving shared intelligent control among family members and long-term user retention. While ensuring that the account logged into the display device is the device owner, the existing family binding relationship of the display device is maintained to the greatest extent possible, ensuring intelligent control capabilities for the original family members.

[0401] Some embodiments of the present disclosure provide a method for purchasing membership for a display device. The method is applicable to a terminal device, wherein the terminal device includes a display and a controller. The controller is configured to: after receiving an instruction input by a user to select a display device control, control the display to display a device details page, and obtain device information of the display device corresponding to the display device control. The display device control is set in a device list, and the device list is set in a homepage page. The device details page includes at least one membership control, and the device information includes a login status. If the login status is an account not logged in state, the target account is determined to be a first account, and the first account is the account logged in to the terminal device. If the login status is a logged in account state, the target account is determined to be a second account, and the second account is the account logged in to the display device. The membership status corresponding to the target account is obtained. The display content of the membership control is determined based on the membership status, wherein the display content of the membership control is different for different membership statuses. The embodiments of the present disclosure obtain the login status of the display device, and determine the target account that needs to purchase membership based on different login statuses, so as to achieve the purpose of quickly purchasing membership for display devices with different login statuses.

[0402] In some embodiments, the terminal device provided by the embodiments of the present disclosure may be the mobile phone described in the above embodiments. During use of a home appliance, a user can bind the home appliance to a first application on their mobile phone. This allows the user to control the home appliance 200 through the first application, such as viewing the current operating status of the home appliance, turning it on or off, and so on. When the user wishes to bind the home appliance 200 to the first application on their mobile phone, the user can select "bind electronic device" within the first application. In response to the user's action to bind an electronic device, the mobile phone retrieves at least one electronic device that can be bound to the current environment. The user can then select the electronic device to be bound from the at least one bindable electronic device displayed on the mobile phone. In response to the selection of the target device, the mobile phone retrieves the device identifier of the target device. Based on the device identifier, the mobile phone retrieves the login information of the target device from the IoT server 400. The mobile phone then performs a binding operation based on multiple factors including the currently logged-in second user account, the first family identifier to which the second user account belongs, the device identifier, and the login information, and determines the binding result. Based on the binding result, the mobile phone binds the target device to the family page corresponding to the fusion identifier and displays the target device on the family page. Among them, the first user account and / or the second user account can both check the bound target device in the home page corresponding to the fusion identifier, and control the target device in the home page to execute the physical network function.

[0403] As can be seen, using the binding method provided by the embodiments of the present disclosure, when a user needs to control a home device through the first application of a terminal device, the user can select to bind an electronic device on the first application of the terminal device. The first application then, in response to the user's operation to bind an electronic device, obtains at least one electronic device that can be bound in the current environment. This allows the user to understand the electronic devices that can be bound in the current environment and select the electronic device to be bound. At this point, the terminal device, in response to the operation to select the target device, obtains the device identifier of the target device. Based on the device identifier, the terminal device obtains the login information of the target device from the IoT server 400. The terminal device performs binding based on multiple items of the currently logged-in second user account, the first family identifier to which the second user account belongs, the device identifier, and the login information, and determines the binding result. Based on the binding result, the terminal device binds the target device to the home page corresponding to the fusion identifier and displays the target device on the home page. Since the first user account and / or the second user account corresponding to the fusion identifier can both view the bound target devices on the home page corresponding to the fusion identifier, the user does not need to consider whether the currently logged-in first user account of the terminal device and the currently logged-in second user account of the target device are the same during the electronic device binding process, simplifying the process of establishing the binding relationship between the terminal device and the target device.

[0404] In addition, when the terminal device is a mobile phone and the target device is a television, the binding method provided by the embodiment of the present disclosure can be used to establish a communication connection between the mobile phone and the television without having to ensure that the first user account currently logged in to the mobile phone and the second user account currently logged in to the television are the same. This simplifies the establishment of a communication connection between the mobile phone and the television and solves the problem of how to simplify the operational process of establishing a binding relationship between the mobile phone and the television.

[0405] In some embodiments, after the mobile phone is turned on, the first application is launched. While using a household appliance, the user can bind the household appliance to the first application on the mobile phone. This allows the user to control the household appliance through the first application on the mobile phone, such as viewing the current operating status of the household appliance, turning it on or off, and so on. When the user needs to bind the household appliance to the first application on the mobile phone, the user can select to bind an electronic device in the first application on the mobile phone. The processing unit 201 of the mobile phone, in response to the user's operation to bind the electronic device, controls the transceiver unit 202 to obtain at least one electronic device that can be bound in the current environment. The user can then select the electronic device to be bound from the at least one electronic device that can be bound displayed on the mobile phone. In response to the selection operation of the target device obtained by the transceiver unit 202, the processing unit 201 of the mobile phone controls the transceiver unit 202 to obtain the device identification of the target device. Based on the device identification obtained by the transceiver unit 202, the processing unit 201 of the terminal device 300 controls the transceiver unit 202 to obtain the login information of the target device from the IoT server 400. The mobile phone's processing unit 201 then performs binding based on multiple items including the currently logged-in second user account, the first family identifier to which the second user account belongs, the device identifier obtained by the transceiver unit 202, and the login information obtained by the transceiver unit 202, and determines a binding result. The mobile phone's processing unit 201 then binds the target device to the family page corresponding to the fusion identifier based on the binding result and controls the display unit 203 to display the target device on the family page.

[0406] In some embodiments, when the execution subject of the binding method provided by the embodiment of the present disclosure is a mobile phone, the storage unit 204 of the mobile phone is used to store data such as the program code of the binding method provided by the embodiment of the present disclosure.

[0407] In the following embodiments, the method of the embodiment of the present disclosure is described by taking the execution subject of the binding method provided by the embodiment of the present disclosure as the above-mentioned mobile phone and the home device 200 as a television as an example.

[0408] An embodiment of the present disclosure provides a binding method, which is applied to a mobile phone. As shown in FIG52 , the binding method may include S11 - S15.

[0409] S11. In response to a user operation of binding an electronic device, obtaining at least one electronic device that can be bound in the current environment.

[0410] In some embodiments, when a user binds an electronic device to a first application on a mobile phone, the first application on the mobile phone needs to verify the electronic device to be bound. For example, the first application can verify the system parameters obtained from the electronic device (e.g., determine whether the scanned content of the system parameters is a TV login code). Only when the verification passes can the electronic device be bound to the first application. In order to ensure that the system parameters are compatible with different development environments (development, testing, online) and enable dynamic configuration of the system parameters, the system parameters are sent offline by the Internet of Things server 400.

[0411] In some embodiments, to ensure the normal operation of the first application, the system parameters are supported by guaranteed data. This is specifically implemented as follows: When the first application is launched, it sends a request message to the system parameter request interface of the IoT server 400. After receiving the request message sent by the first application on the mobile phone, the IoT server 400 sends the current system parameters to the mobile phone. The mobile phone receives the system parameters currently issued by the IoT server 400 and refreshes the memory data to update the system parameters in the memory data to the system parameters currently issued by the IoT server 400.

[0412] In some embodiments, when a mobile phone obtains at least one electronic device that can be bound to the current environment (such as an electronic device including one or more of a refrigerator, a television, a washing machine, an air conditioner, a water heater, a gas stove, and a range hood), it can scan and discover at least one electronic device that can be bound to the current environment through the Digital Living Network Alliance (DLNA).

[0413] In some embodiments, after the user opens the first application on the mobile phone, the first page 1 shown in Figure 53 is displayed. The first page 1 includes a control 1-1 for indicating my home and a control 1-2 for adding devices. At this time, the user can select control 1-1 to view the electronic devices bound to "my home". When the user needs to bind an electronic device, he can select control 1-2. At this time, the mobile phone displays a second page 2 as shown in Figure 54 in response to the selection of control 1-2. Among them, the second page 2 includes a control 2-1 for obtaining nearby devices, a control 2-2 for scanning and adding, and a control 2-3 for receiving and adding. In response to the selection of control 2-1, the mobile phone displays a third page 3 as shown in Figure 55. Among them, the third page 3 includes at least one electronic device that can be bound to the current environment and a control for adding an electronic device, such as a TV (1d7f) and a control 3-1 for adding the corresponding TV (1d7f), an air conditioner (FCBD) and a control 3-2 for adding the air conditioner (FCBD).

[0414] S12: In response to the selection operation of the target device, obtain the device identification of the target device, wherein one target device corresponds to one device identification, and the target device is any electronic device.

[0415] In some embodiments, the mobile phone obtains the device identification of the target device through DLNA, wherein the device identification can be an identification code or other identification used to uniquely identify the target device.

[0416] In some embodiments, combined with the example given in S11 above, when the target device is a TV (1d7f), if the user needs to bind the TV (1d7f) to "My Home" (corresponding to the second user account currently logged in to the first application), the user can select the add control 3-1, and the mobile phone responds to the selection operation of the target device to obtain the device identification of the TV (1d7f).

[0417] In some embodiments, the user account currently logged into the electronic device (e.g., account 1) is the administrator of the electronic device. When the user logs in to account 1 on the first application, they can create a family name for the electronic device, delete and add electronic devices under the family name, and delete and add members of the family name (one member corresponds to one user account). One family name corresponds to one family identifier.

[0418] S13. Based on the device identifier, obtain login information of the target device from the IoT server 400. The login information includes a first login identifier for indicating that the target device uses a pre-configured anonymous account, or the login information includes a second login identifier for indicating that the target device is currently logged in to the first user account.

[0419] In some embodiments, when the target device logs in to the first user account (an account registered by the user), a binding relationship between the device identifier of the target device and the first user account is established in the IoT server 400 .

[0420] In some embodiments, when the target device has not logged into the first account, the IoT server 400 will configure a pre-configured anonymous account for the target device and establish a binding relationship between the device identifier of the target device and the anonymous account to ensure that the target device can be used normally.

[0421] In some embodiments, in combination with the example given in S12 above, after the mobile phone obtains the device identifier of the television (1d7f), the mobile phone sends a query message carrying the device identifier (such as deviceid) to the Internet of Things server 400. After receiving the query message sent by the mobile phone, the Internet of Things server 400 queries the database for the login information of the television (1d7f) based on the device identifier. For example: when the Internet of Things server 400 determines that the device identifier corresponds to an anonymous account, it determines that the login information includes a first login identifier for indicating that the television (1d7f) uses a pre-configured anonymous account. Alternatively, when the Internet of Things server 400 determines that the device identifier corresponds to a first user account, it determines that the login information includes a second login identifier for indicating that the television (1d7f) is currently logged in to the first user account.

[0422] In some embodiments, the login information includes the target device's bound mobile phone number (mobilePhone), the target device's nickname (nickName), the user account (customerId), and a login identifier (token). If token is not empty, it indicates that the target device has logged into the first user account, i.e., the token identifier is the second login identifier. If token is empty, it indicates that the target device has logged into an anonymous account, i.e., the token identifier is the first login identifier.

[0423] S14. Binding is performed based on multiple items of the currently logged-in second user account, the first family identifier to which the second user account belongs, the device identifier, and the login information, and a binding result is determined. The binding result includes fusion identifiers corresponding to the first user account and the second user account, and the fusion identifier includes the second family identifier corresponding to the first user account or the first family identifier corresponding to the second user account.

[0424] In some embodiments, when a mobile phone is bound based on multiple items of the currently logged-in second user account, the first family identifier to which the second user account belongs, the device identifier, and the login information, if the login information includes the first login identifier, the non-logged-in binding process is entered. If the login information includes the second login identifier, and the first and second user accounts are the same, the same-account binding process is entered. If the login information includes the second login identifier, and the first and second user accounts are different, the different-account binding process is entered.

[0425] In some embodiments, an example is given in combination with the above S13, and the target device is a TV (1d7f) for example. Among them, the non-logged in binding process includes: when the login information of the mobile phone includes the first login identifier, the device guide binding page 4 as shown in Figure 56 is displayed. Among them, the device guide binding page 4 includes an operation process for performing a preset operation on the TV (1d7f) to display the login identifier (wherein, the guide binding page 4 includes a control 4-1 for indicating the selection of the login control at the top of the display page displayed on the TV (1d7f), and a control 4-2 for indicating the use of the first application to scan the login QR code displayed on the TV (1d7f), and a scan control 4-3 for scanning the QR code. Based on the display content of the control 4-1 and the control 4-2, the user selects the login control at the top of the display page on the TV (1d7f), and the TV (1d7f) responds to the operation. Select the operation to display the login page containing the login QR code. After that, the user selects the scan control 4-3 displayed on the mobile phone, so that the mobile phone responds to the user operation of obtaining the login identifier and obtains the login identifier (such as the login QR code) of the TV (1d7f). When the login identifier of the mobile phone is a valid identifier (such as: the login QR code must start with the string in tvLoginQrLinks mentioned in the configuration instructions of the system parameters, the QR code may contain the rKey of the application instruction short code to long code, deviceId, serial number serialno of the target device, and universally unique identifier (Universally Unique Identifier, uuid) field, but must contain rKey or deviceId field, the login identifier is considered to be a valid identifier), and the login page 5 shown in Figure 57 is displayed. In response to the selection operation of the confirmation login control 5-1 in the login page 5, the mobile phone sends the login information to the Internet of Things server 400. Among them, the login information is used to instruct the Internet of Things server 400 to send the login information to the TV (1d7f), and the login information includes the second user account. In this way, the TV (1d7f) can log in based on the second user account sent by the Internet of Things server 400. After receiving the Internet of Things server When the target device receives login information sent by IoT server 400 indicating that the second user account has been logged into the target device, the mobile phone sends first binding information containing the second user account, the first family identifier, and the device identifier to IoT server 400. The first binding information instructs IoT server 400 to establish a binding relationship between the device identifier, the second user account, and the first family identifier. The mobile phone receives feedback from IoT server 400 indicating that the binding relationship between the device identifier, the second user account, and the first family identifier has been established, determines that the fusion identifier in the binding result is the first family identifier, and displays a successful connection page 6 as shown in Figure 58.

[0426] The same-account binding process includes: when the mobile phone's login information includes a second login identifier, and the first user account and the second user account are the same, the mobile phone sends first binding information containing the second user account, the first family identifier, and the device identifier to the IoT server 400. The first binding information is used to instruct the IoT server 400 to establish a binding relationship between the device identifier, the first family identifier, and the family identifier corresponding to the second user account. The mobile phone receives feedback from the IoT server 400 indicating that the binding relationship between the device identifier, the second user account, and the first family identifier has been established, determines that the fusion identifier in the binding result is the first family identifier, and displays a successful connection page 6 as shown in Figure 58.

[0427] The process for binding multiple accounts includes two scenarios: Scenario 1 and Scenario 2. Scenario 1 involves the target device being logged into the first user account, and the first user account is not bound to a family identifier. Scenario 2 involves the target device being logged into the first user account, and the first user account is bound to a family identifier.

[0428] Scenario 1 includes: In conjunction with the example given in S13 above, when the login information includes a second login identifier and the first user account is different from the second user account, the mobile phone sends a second binding information carrying the first user account and the device identifier to the Internet of Things server 400. The second binding information is used to instruct the Internet of Things server 400 to create a preset home identifier (such as homeA) when the first user account is not bound to the second home identifier, and to establish a binding relationship between the first user account, the device identifier, and homeA. The mobile phone receives feedback information sent by the Internet of Things server 400 carrying the binding relationship between the first user account, the device identifier, and homeA. When the first home identifier (such as homeB) is different from the preset home identifier homeA, the application page 7 shown in Figure 59 is displayed. The application page 7 includes a preset pop-up window 7-1 for indicating joining the preset home corresponding to homeA. In response to the selection operation of the control 11 for applying to join the preset home in the preset pop-up window 7-1, the mobile phone sends an application request to the Internet of Things server 400. Among them, the application request is used to instruct the Internet of Things server 400 to send a request information for applying to join the preset family to the preset family (such as sending a request information for joining the preset family to the second user account corresponding to homeA (that is, the first user account (such as account 1) that initially created the preset family corresponding to homeA). Afterwards, the Internet of Things server 400 sends feedback information to the mobile phone to indicate that the request information has been sent to the second user account. After receiving the feedback information sent by the server 400 to indicate that the request information has been sent to the second user account, the mobile phone displays a prompt page 8 as shown in Figure 60. Among them, the prompt page 8 includes a view 8-1 for prompting the user to "wait for the administrator review of the second user account corresponding to homeA". Afterwards, other users can receive the request information in the first application logged in with account 1. When allowed to join the preset family, the first application logged in with account 1 can send feedback information to the Internet of Things server 400 to allow joining the preset family). Afterwards, the Internet of Things server 400 will send the feedback information to the mobile phone. The mobile phone receives the feedback information sent by the Internet of Things server 400. Among them, the feedback information is used to indicate that the request information for applying to join the preset family has been sent to account 1. The mobile phone receives confirmation information (e.g., a Message Queuing Telemetry Transport (MQTT) message) from IoT server 400 allowing the user to join the preset home, and determines that the fusion identifier in the binding result is homeA. The second home identifier is equal to the preset home identifier. The mobile phone displays home page 9, as shown in FIG61 . Home page 9 includes a control 9-1 for displaying all homes, a control 9-2 for displaying my home, and a control 9-3 for displaying the preset home.In response to the selection of control 9-1, a selection page 10 as shown in FIG62 is displayed. The selection page 10 includes control 9-1 and a control 10-1 for representing a preset home. When the user needs to view the preset home, the user can select control 10-1. The mobile phone, in response to the selection of control 10-1, displays a display page 11 as shown in FIG63. Display page 11 includes at least one target device, such as a TV (1d7f), that has established a binding relationship with homeA. The user can then control the TV 3 through the first application on the mobile phone to perform the corresponding IoT function, such as turning on the TV (1d7f) or turning off the TV (1d7f). When the user needs to view the preset home, the user can select control 10-2. The mobile phone, in response to the selection of control 10-2, displays the first page 1 as shown in FIG53. Furthermore, the user can select control 9-2 for representing my home on the main page 9 as shown in FIG61 to display the first page 1 as shown in FIG53. Alternatively, the user may select the control 9-3 for representing my home in the main page 9 as shown in FIG. 61 to display the display page 11 as shown in FIG. 63 .

[0429] Scenario 2 includes: when the login information of the mobile phone includes the second login identifier and the first user account is different from the second user account, the mobile phone sends a third binding information carrying the first user account and the device identifier to the Internet of Things server 400. The third binding information is used to instruct the Internet of Things server 400 to establish a binding relationship between the first user account, the device identifier and homeA when the first user account has been bound to the second home identifier (such as homeA). The mobile phone receives feedback information sent by the Internet of Things server 400 that carries the binding relationship between the first user account, the device identifier and homeA. When the first home identifier (such as homeB) is the same as homeA, it is determined that the fusion identifier in the binding result is homeA. The switching page 12 as shown in Figure 64 is displayed. Switching page 12 includes a pop-up window 12-1 for indicating that the TV (1d7f) has been bound and whether to switch to the preset family viewing TV (1d7f). Pop-up window 12-1 includes a control 12-1-1 for confirming the switch to the preset family viewing TV (1d7f) and a control 12-1-2 for canceling the switch to the preset family viewing TV (1d7f). In response to the selection operation of control 12-1-1, the mobile phone displays display page 11 as shown in Figure 63.

[0430] S15. Based on the binding result, the target device is bound to the home page corresponding to the fusion identifier, and the target device is displayed on the home page. The first user account and / or the second user account can both access the bound target device on the home page corresponding to the fusion identifier and control the target device on the home page to execute the physical network function.

[0431] In some embodiments, during the application process to join a preset family, if the first user account bound to the preset family is not the user account used by a family member, a quick rebinding can be performed. For example, if a relative or friend binds the target device while visiting, the first user account bound to the target device can be rebinded. For example, in response to the user's operation to rebind the target device, a prompt message is generated to prompt the user to log out of the first user account currently logged in on the target device and to re-execute the user operation to bind the electronic device.

[0432] In some embodiments, in combination with the example given in S14 above, as shown in FIG59 , the application page 7 further includes a control 7-2 for instructing to rebind the device. When the user needs to rebind the first user account of the television (1d7f), the user can select the control 7-2. At this time, the mobile phone, in response to the selection of the control 7-2, generates a prompt message for prompting to exit the first user account currently logged in on the target device and re-execute the user operation of binding the electronic device (i.e., the above S11), thereby rebinding the first user account of the television (1d7f).

[0433] As can be seen, using the binding method provided by the embodiments of the present disclosure, when a user needs to control a television through a first application on a mobile phone, the user can select to bind the television on the first application on the mobile phone. The first application then responds to the user's request to bind the television and obtains at least one electronic device that can be bound to the current environment. This allows the user to understand the electronic devices that can be bound to the current environment and select the electronic device to be bound. In response to the selection of the television, the mobile phone obtains the device identifier of the television. Based on the device identifier, the mobile phone obtains the login information of the television from the IoT server 400. The mobile phone performs a binding based on multiple items of the currently logged-in second user account, the first family identifier to which the second user account belongs, the device identifier, and the login information, and determines the binding result. Based on the binding result, the mobile phone binds the television to the home page corresponding to the fusion identifier and displays the television on the home page. Since the first user account and / or the second user account corresponding to the fusion identifier can both access the bound target device on the home page corresponding to the fusion identifier, the user does not need to consider whether the currently logged-in first user account of the terminal device and the currently logged-in second user account of the target device are the same during the electronic device binding process, simplifying the process of establishing the binding relationship between the terminal device and the target device.

[0434] In some feasible examples, combined with FIG52 , as shown in FIG65 , the above S14 can be specifically implemented through the following S140 - S145 .

[0435] S140: If the login information includes the first login identifier, display a device boot binding page, wherein the device boot binding page includes an operation flow for performing a preset operation on the target device to display the login identifier.

[0436] S141. In response to a user operation of obtaining a login identifier, obtain a login identifier of a target device.

[0437] S142: If the login identifier is a valid identifier, display the login page.

[0438] S143: In response to the selection operation of the login control on the login page, send login information to the Internet of Things server 400. The login information is used to instruct the Internet of Things server 400 to send the login information to the target device, and the login information includes the second user account.

[0439] S144. Upon receiving the login information sent by the IoT server 400 indicating that the target device has logged into the second user account, first binding information including the second user account, the first family identifier, and the device identifier is sent to the IoT server 400. The first binding information is used to instruct the IoT server 400 to establish a binding relationship among the device identifier, the second user account, and the first family identifier.

[0440] S145: Receive feedback from the IoT server 400 indicating that a binding relationship has been established between the device identifier, the second user account, and the first family identifier, and determine that the fusion identifier in the binding result is the first family identifier.

[0441] In some feasible examples, combined with FIG52 , as shown in FIG66 , the above S14 can be specifically implemented through the following S146 and -S147.

[0442] S146: If the login information includes the second login identifier and the first user account is the same as the second user account, first binding information including the second user account, the first family identifier, and the device identifier is sent to the IoT server 400. The first binding information is used to instruct the IoT server 400 to establish a binding relationship between the device identifier, the first family identifier, and the family identifier corresponding to the second user account.

[0443] S147: Receive feedback from the IoT server 400 indicating that a binding relationship has been established between the device identifier, the second user account, and the first family identifier, and determine that the fusion identifier in the binding result is the first family identifier.

[0444] In some feasible examples, combined with FIG52 , as shown in FIG67 , the above S14 can be specifically implemented through the following S148 - S149 - 4.

[0445] S148. If the login information includes the second login identifier and the first user account is different from the second user account, send second binding information carrying the first user account and the device identifier to the IoT server 400. The second binding information is used to instruct the IoT server 400 to create a preset family identifier if the first user account is not bound to the second family identifier, and to establish a binding relationship among the first user account, the device identifier, and the preset family identifier.

[0446] S149: Receive feedback information sent by the Internet of Things server 400 that carries the binding relationship between the first user account, the device identifier, and the preset family identifier.

[0447] S149-1. When the first family ID is different from the preset family ID, a preset pop-up window for adding the preset family corresponding to the preset family ID is displayed.

[0448] S149-2: In response to the selection operation of the control for applying to join the preset family in the preset pop-up window, an application request is sent to the IoT server 400. The application request is used to instruct the IoT server 400 to send a request information for applying to join the preset family to the preset family.

[0449] S149-3. Receive feedback information sent by the Internet of Things server 400. The feedback information is used to indicate that a request to join the preset family has been sent to the first user account.

[0450] S149-4: Receive confirmation information from the IoT server 400 regarding permission to join the preset family, and determine that the fusion identifier in the binding result is the preset family identifier, wherein the second family identifier is equal to the preset family identifier.

[0451] In some feasible examples, combined with FIG52 , as shown in FIG68 , the above S14 can be specifically implemented through the following S149-5-S149-7.

[0452] S149-5. If the login information includes the second login identifier and the first user account is different from the second user account, third binding information carrying the first user account and the device identifier is sent to the IoT server 400. The third binding information is used to instruct the IoT server 400 to establish a binding relationship between the first user account, the device identifier, and the second family identifier, if the first user account is already bound to the second family identifier.

[0453] S149-6: Receive feedback information sent by the IoT server 400 that carries the binding relationship between the first user account, the device identifier, and the second family identifier.

[0454] S149-7. When the first family identifier and the second family identifier are the same, determine that the fusion identifier in the binding result is the second family identifier.

[0455] In some feasible examples, in combination with FIG. 52 , as shown in FIG. 69 , the binding method provided by the embodiment of the present disclosure also includes: S16.

[0456] S16 . In response to the user operation of rebinding the target device, generate prompt information for prompting the user to log out of the first user account currently logged in to the target device and re-execute the user operation of binding the electronic device.

[0457] The above mainly introduces the solution provided by the embodiment of the present disclosure from the perspective of method. In order to realize the above functions, it includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present disclosure can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in a hardware or computer software driven hardware manner depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present disclosure.

[0458] The disclosed embodiments can divide the terminal device into functional modules according to the above-described method examples. For example, each functional module can be divided into corresponding functional modules, or two or more functions can be integrated into a single processing unit. The integrated modules can be implemented in the form of hardware or software functional modules.

[0459] The foregoing description is intended only to provide specific embodiments of the present disclosure, intended to enable those skilled in the art to understand and implement the present disclosure. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure is not intended to be limited to the embodiments described herein, but rather to be construed in the broadest manner consistent with the principles and novel features disclosed herein.

Claims

1. A terminal, comprising: monitor; The controller is configured as: After the user account is logged in, in response to the user inputting an instruction to add a device, controlling the display to display a list of discovered devices, wherein the list of discovered devices includes at least one device control; In response to a user inputting an instruction to select a first device control among the at least one device control, if the first device corresponding to the first device control is a display device, controlling the display to display a binding guide page, and obtaining the number of target controls in the discovered device list; the binding guide page includes a screenshot display window, and the target control is a control of a device corresponding to the device control, which is a display device; In response to the number of the target controls being greater than 1, sending a screenshot request to the first device, so that the first device captures a screen image based on the screenshot request and uploads the screen image to a server; Acquire the screen image and display the screen image in the screenshot display window; If a confirmation binding operation input by the user is received, the first device is bound to the user account so as to control the first device through the terminal.

2. The terminal according to claim 1, wherein: The controller executes sending a screenshot request to the first device so that the first device captures a screen image based on the screenshot request and uploads the screen image to the server, and is further configured to: If the second device corresponding to the second device control in at least one device control has the same IP as the first device, a screenshot request is sent to the server, so that the server sends the screenshot request to the first device based on the device identifier and receives the screenshot data uploaded by the first device after capturing the screen image based on the screenshot request, the screenshot request includes the device identifier and the image identifier, and the screenshot data includes the screen image and the image identifier.

3. The terminal according to claim 1, wherein: The controller executes sending a screenshot request to the first device so that the first device captures a screen image based on the screenshot request and uploads the screen image to the server, and is further configured to: If the second device corresponding to the second device control in the at least one device control has an IP different from that of the first device, a screenshot request is sent to the first device based on the IP of the first device, so that the first device captures a screenshot image based on the screenshot request and uploads the screenshot data, the screenshot request includes an image identifier, and the screenshot data includes a screen image and an image identifier.

4. The terminal according to claim 2 or 3, wherein: The controller executes acquiring the screen image and is further configured to: Sending the picture request to the server, wherein the picture request includes a picture identifier; Receive the screen image sent by the server based on the image request.

5. The terminal according to claim 1, wherein: The controller is further configured to: In response to the number of the target controls being less than or equal to 1, the placeholder identifier of the screenshot display window is set to a preset value so that the screenshot display window is not displayed on the binding guide page. The terminal according to claim 1 , wherein: The screenshot request includes a preset instruction, where the preset instruction is used to instruct the first device to execute a preset operation corresponding to the preset instruction, and the preset operation is used to change the user interface of the display device.

7. The terminal according to claim 1, wherein: If the controller receives a confirmation binding operation from the user, the controller binds the first device to the user account, and is further configured to: If it is detected that the user account logged in by the first device is the same as the user account logged in by the terminal, displaying a binding control on the binding guide page; If an instruction of selecting the binding control is received from the user, the first device is bound to the user account logged in by the terminal.

8. The terminal according to claim 7, wherein: The controller is configured to: If it is detected that the first device has not logged in to the user account, a first guide frame is displayed on the binding guide page, the first guide frame includes guide information, and the guide information is used to guide the user to log in to the user account logged in by the terminal on the first device.

9. The terminal according to claim 7, wherein: The controller is configured to: If it is detected that the user account logged in by the first device is different from the user account logged in by the terminal, a second guide box is displayed on the binding guide page, and the second guide box includes adding a home control and rebinding a control; If an instruction is received from the user to select to join the family control, the user account logged in at the terminal is added to the family of the user account logged in at the first device, so that the user account logged in at the terminal establishes a connection relationship with the first device; If a user input is received to select rebinding the control, a first guide frame is displayed on the binding guide page.

10. The terminal according to claim 1, wherein: The controller executes, in response to a user input instruction to add a device, controlling the display to display a list of discovered devices, and is configured to: Acquire electronic devices that can be added to the current environment based on the target protocol; wherein the target protocol includes a local area network protocol, a Bluetooth protocol, and a Digital Living Network Alliance protocol; Based on the acquired electronic devices, a display list is generated; wherein the display list includes one or more electronic devices; If there is no other preset pop-up window to be displayed at present, and the currently displayed page is the target page, the display is controlled to display the device list pop-up window according to the display list in the target page. The terminal according to claim 10 , wherein: When the controller executes the target protocol to obtain the electronic devices that can be added in the current environment, it is configured as follows: Performing deduplication processing on the electronic devices respectively obtained based on the local area network protocol and the Bluetooth protocol to obtain deduplicated electronic devices; Obtaining a merged electronic device based on the deduplicated electronic device and the electronic device obtained through the Digital Living Network Alliance protocol; Deduplication is performed based on the electronic devices bound to the current account and the merged electronic devices to generate a display list.

12. The terminal according to claim 11, wherein: The controller performs deduplication processing on the electronic devices respectively obtained through the local area network protocol and the Bluetooth protocol to obtain the deduplicated electronic devices, and is configured as follows: Acquire target information of the electronic device based on the local area network protocol and the Bluetooth protocol respectively; wherein the target information includes a media access control address corresponding to a mobile hotspot module or any one of the configuration information; Based on the target information, deduplication processing is performed on the electronic devices respectively obtained through the local area network protocol and the Bluetooth protocol to obtain deduplication electronic devices.

13. The terminal according to claim 12, wherein: The target information includes a media access control address; the controller is further configured to: Acquiring Bluetooth information reported by the electronic device based on the Bluetooth protocol; wherein the Bluetooth information includes information added to represent a media access control address; When the media access control address and the acquired Bluetooth information are the same, the electronic device acquired based on the first protocol is deleted, the electronic device acquired based on the second protocol is retained, and the retained electronic device acquired based on the second protocol is used as the deduplicated electronic device; wherein the first protocol includes any one of the local area network protocol and the Bluetooth protocol, and the second protocol includes protocols among the local area network protocol and the Bluetooth protocol except the first protocol.

14. The terminal according to claim 13, wherein: The target information includes configuration information, and the configuration information includes category information to which the electronic device belongs; the controller is further configured to: In the case of electronic devices with the same category information, the electronic devices obtained based on the third protocol are deleted, and the electronic devices obtained based on the fourth protocol are retained, and the retained electronic devices obtained based on the fourth protocol are used as the deduplicated electronic devices; wherein the third protocol includes any one of the local area network protocol and the Bluetooth protocol, and the fourth protocol includes the local area network protocol and the Bluetooth protocol except the first protocol.

15. The terminal according to claim 13, wherein: The configuration information includes network configuration information, and the network configuration information includes any one of a configured network and an unconfigured network; the controller is further configured to: In the case that the network configuration information of the electronic device obtained based on the Bluetooth protocol is not network configured, retaining the electronic device whose network configuration information is not network configured, and using the retained electronic device whose network configuration information is not network configured as the deduplicated electronic device; In the case that the network configuration information of the electronic device obtained based on the Bluetooth protocol is already configured, the electronic device whose network configuration information is already configured is deleted.

16. The terminal according to claim 12, wherein: When the controller executes the target protocol to obtain the electronic devices that can be added in the current environment, it is configured as follows: The electronic devices bound to the current account are deleted from the merged electronic devices to obtain the electronic devices that can be added.

17. The terminal according to claim 10, wherein: The device list pop-up window also includes an ignore control for not displaying within a preset time, and one ignore control corresponds to one electronic device; the controller is further configured to: In response to a selection operation on the ignore control, the electronic device corresponding to the ignore control is deleted in the device list pop-up window, and the electronic device corresponding to the ignore control is no longer displayed in the device list pop-up window displayed within a preset time.

18. The terminal according to claim 1, wherein: The controller is configured to: After receiving an instruction input by a user for indicating to display a device details page, obtaining device information of a display device corresponding to the first device control, the device details page including at least one member control, and the device information including a login status; If the login status is a non-logged-in account status, determining that the target account is a first account, the first account is an account logged in by the terminal device; If the login status is a logged-in account status, determining that the target account is a second account, the second account is an account logged in by the display device; Obtain the membership status corresponding to the target account; The display content of the member control in the device details page is determined according to the member status, wherein the display content of the member control is different for different member statuses.

19. The terminal according to claim 1, wherein: The device information also includes license plate information, and the controller executes to obtain the membership status corresponding to the target account, and is further configured to: Determine the member type according to the license plate information, and send a member information request to the server so that the server can feedback a list of activated members based on the target account, wherein the member information request includes the target account; If the member type is in the activated member list, determining that the member status is activated; If the member type is not in the activated member list, it is determined that the member status is unactivated.

20. The terminal according to claim 19, wherein: The controller determines the display content of the member control in the device details page according to the member control, and is further configured to: When the membership status is in the activated status, it is determined that the display content of the membership control is renewal content, and the renewal content includes the membership validity period and the renewal control.

21. The terminal according to claim 19, wherein: The controller determines the display content of the member control in the device details page according to the member control, and is further configured to: When the member status is an unactivated state, it is determined that the display content of the member control is activated content, and the activation content includes an activation control.

22. The terminal according to claim 20 or 21, wherein: The controller is configured to: After receiving an instruction from a user to select a renewal control or an activation control, controlling the display to display a member purchase page, the member purchase page including at least one purchase control; After receiving an instruction input by the user to select the purchase control, the membership corresponding to the purchase control is purchased for the target account.

23. The terminal according to claim 22, wherein: The controller is configured to: After the target account is the first account and the membership corresponding to the purchase control is purchased for the target account, the display is controlled to display a code scanning page, where the code scanning page is used to scan the identification code on the display screen of the display device; determining identification information based on the identification code; Sending the identification information and the first account to an account server, so that the account server guides the display device to log in to the first account; Sending a first binding request to the Internet of Things server, wherein the first binding request includes the first account, the device identifier of the display device, the target binding family and the target owner, wherein the target binding family is empty and the target owner is the first account; Receiving a first binding result sent by the Internet of Things server based on the first binding request; The home page is updated based on the first binding result.

24. The terminal according to claim 20, wherein: When the target account is the first account, the renewal content further includes a login control, and the controller is configured to: After receiving an instruction input by a user to select the login control, controlling the display to display a code scanning page, the code scanning page being used to scan an identification code on a display screen of the display device; determining identification information based on the identification code; Sending the identification information and the first account to an account server, so that the account server instructs the display device to log in to the first account; Sending a first binding request to the Internet of Things server, wherein the first binding request includes the first account, the device identifier of the display device, the target binding family and the target owner, wherein the target binding family is empty and the target owner is the first account; Receiving a first binding result sent by the Internet of Things server based on the first binding request; The home page is updated based on the first binding result.

25. The terminal according to claim 1, wherein: The controller is also configured to: In response to a selection operation for selecting a target device to be bound, obtaining a device identification of the target device; wherein one target device corresponds to one device identification; Based on the acquired device identifier, acquiring login information of the target device from the Internet of Things server; wherein the login information includes a first login identifier for indicating that the target device uses a pre-configured anonymous account, or the login information includes a second login identifier for indicating that the target device is currently logged in to a first user account; Binding is performed based on multiple items of the currently logged-in second user account, the first family identifier to which the second user account belongs, the device identifier, and the login information, and a binding result is determined; wherein the binding result includes fusion identifiers corresponding to the first user account and the second user account, and the fusion identifier includes the second family identifier corresponding to the first user account, or the first family identifier corresponding to the second user account; Based on the binding result, the target device is bound to the home page corresponding to the fusion identifier, and the display is controlled to display the target device in the home page; wherein the first user account and / or the second user account can both view the bound target device in the home page corresponding to the fusion identifier, and control the target device in the home page to perform physical network functions.

26. The terminal according to claim 25, wherein: When the login information includes a first login identifier, the controller is configured to: Controlling the display to display a device boot binding page; wherein the device boot binding page includes an operation flow for performing a preset operation on the target device to display a login logo; When the login identifier is a valid identifier, controlling the display to display a login page; In response to a selection operation of a login control in the login page displayed on the display, sending login information to the Internet of Things server; wherein the login information is used to instruct the Internet of Things server to send the login information to the target device, and the login information includes the second user account; Upon receiving the login information sent by the IoT server indicating that the target device has logged in to the second user account, sending first binding information including the second user account, the first family identifier and the device identifier to the IoT server; wherein the first binding information is used to instruct the IoT server to establish a binding relationship among the device identifier, the second user account and the first family identifier; When receiving a feedback result sent by the Internet of Things server indicating that a binding relationship among the device identifier, the second user account and the first family identifier has been established, determining that the fusion identifier in the binding result is the first family identifier.

27. The terminal according to claim 25, wherein: When the login information includes a second login identifier and the first user account is the same as the second user account, the controller is configured to: Sending first binding information including the second user account, the first family identifier and the device identifier to the Internet of Things server; wherein the first binding information is used to instruct the Internet of Things server to establish a binding relationship between the device identifier, the first family identifier and the family identifier corresponding to the second user account; When receiving a feedback result sent by the Internet of Things server indicating that a binding relationship among the device identifier, the second user account and the first family identifier has been established, determining that the fusion identifier in the binding result is the first family identifier.

28. The terminal according to claim 25, wherein: The controller is configured to: When the login information includes the second login identifier and the first user account is different from the second user account, second binding information carrying the first user account and the device identifier is sent to the Internet of Things server; wherein the second binding information is used to instruct the Internet of Things server to create a preset family identifier when the first user account is not bound to the second family identifier, and to establish a binding relationship among the first user account, the device identifier and the preset family identifier; receiving feedback information sent by the Internet of Things server and carrying a binding relationship between the first user account, the device identifier, and the preset family identifier; When the first family identifier is different from the acquired preset family identifier, controlling the display to display a preset pop-up window for adding a preset family corresponding to the preset family identifier; In response to a selection operation of a control for applying to join the preset family in the preset pop-up window displayed on the display, sending an application request to the Internet of Things server; wherein the application request is used to instruct the Internet of Things server to send request information for applying to join the preset family to the preset family; Receiving feedback information sent by the Internet of Things server; wherein the feedback information is used to indicate that a request information for applying to join the preset family has been sent to the first user account; Upon receiving confirmation information sent by the Internet of Things server allowing the user to join the preset family, it is determined that the fusion identifier in the binding result is the preset family identifier; wherein the second family identifier is equal to the preset family identifier.

29. The terminal according to claim 25, wherein: The controller is configured to: When the login information includes the second login identifier and the first user account is different from the second user account, third binding information carrying the first user account and the device identifier is sent to the Internet of Things server; wherein the third binding information is used to instruct the Internet of Things server to establish a binding relationship between the first user account, the device identifier and the second family identifier when the first user account has been bound to the second family identifier; receiving feedback information sent by the Internet of Things server and carrying a binding relationship between the first user account, the device identifier, and the second family identifier; When the first family identifier is the same as the received second family identifier, it is determined that the fusion identifier in the binding result is the second family identifier.

30. The terminal according to claim 25, wherein: The controller is also configured to: In response to the user operation of rebinding the target device, prompt information for prompting to log out of the first user account currently logged in to the target device and to re-execute the user operation of the bound electronic device is generated.

31. A device binding method, comprising: After logging into the user account, in response to a user inputting an instruction to add a device, controlling the display to display a list of discovered devices, wherein the list of discovered devices includes at least one device control; In response to a user input of an instruction to select a first device control among the at least one device control, if the first device corresponding to the first device control is a display device, controlling the display to display a binding guide page, and obtaining the number of target controls in the discovered device list, the binding guide page including a screenshot display window, the target control being a control of a device corresponding to the device control being a display device; If the number is greater than 1, sending a screenshot request to the first device, so that the first device captures a screen image based on the screenshot request and uploads the screen image to a server; Acquire the screen image from the server and display the screen image in the screenshot display window; If a confirmation binding operation input by the user is received, the first device is bound to the user account so that the user can control the first device through the terminal.

Images