A binding method, apparatus and electronic device

Abstract

The present disclosure relates to the technical field of Internet of Things, and particularly relates to a binding method, device and electronic equipment, which are used for solving the problem of how to simplify the operation process of establishing the binding relationship between a mobile phone and a television. The method comprises the following steps: in response to a user operation of binding an electronic equipment, at least one electronic equipment that can be bound in a current environment is acquired; in response to a selection operation on a target equipment, a device identifier of the target equipment is acquired; based on the device identifier, login information of the target equipment is acquired from an Internet of Things server; based on multiple items in a second user account currently logged in, a first family identifier to which the second user account belongs, the device identifier and the login information, binding is performed, and a binding result is determined; based on the binding result, the target equipment is bound to a family page corresponding to a fusion identifier, and the target equipment is displayed in the family page.

Description

Technical Field

[0001] This disclosure relates to the field of Internet of Things (IoT) technology, and more particularly to a binding method, apparatus, and electronic device. Background Technology

[0002] Currently, users can control electronic devices (such as televisions) to perform corresponding operations (such as turning on / off, adjusting volume, etc.) through mobile terminals (such as mobile phones). In this process, it is necessary to establish a binding relationship between the mobile phone and the television. For the sake of user privacy and security, the same user account (such as mobile phone number) needs to be logged in on both the television and the mobile phone at the same time during the process of establishing the binding relationship between the mobile phone and the television.

[0003] However, when performing the above operations, users often encounter situations where the user account logged in on the mobile phone is different from the user account logged in on the TV, or the user account is not currently logged in on the TV. This forces users to switch the login status of their user account in order to complete the above operations, resulting in a poor user experience.

[0004] Therefore, simplifying the process of establishing a binding relationship between mobile phones and televisions has become an urgent problem to be solved. Summary of the Invention

[0005] To address the aforementioned technical problems, this disclosure provides a binding method, apparatus, and electronic device.

[0006] The technical solution disclosed herein is as follows:

[0007] In a first aspect, this disclosure provides a terminal device, comprising: a processor configured to, in response to a user operation of a bound electronic device, control a communicator to acquire at least one bindable electronic device in the current environment; the processor is further configured to, in response to a selection operation of a target device acquired by the communicator, control the communicator to acquire a device identifier of the target device; wherein, one target device corresponds to one device identifier, and the target device is any one of the electronic devices; the processor is further configured to, based on the device identifier acquired by the communicator, control the communicator to acquire login information of the target device from an Internet of Things server; wherein the login information includes a first login identifier for instructing the target device to use a pre-configured anonymous account, or the login information includes a second login identifier for instructing the target device to currently log in to a first user account; The processor is also configured to bind 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 obtained by the communicator, to determine the binding result. The binding result includes a converged identifier corresponding to both the first and second user accounts, where the converged identifier includes either the second family identifier corresponding to the first user account or the first family identifier corresponding to the second user account. The processor is also configured to bind the target device to the family page corresponding to the converged identifier based on the binding result and control the display to show the target device on the family page. Both the first and / or second user accounts can view the bound target device on the family page corresponding to the converged identifier and control the target device on the family page to perform physical network functions.

[0008] Secondly, this disclosure provides a binding method, comprising: in response to a user operation to bind an electronic device, obtaining at least one electronic device that can be bound in the current environment; in response to a selection operation of a target device, obtaining a device identifier of the target device; wherein, one target device corresponds to one device identifier, and the target device is any one of the electronic devices; based on the device identifier, obtaining login information of the target device from an IoT server; wherein the login information includes a first login identifier for instructing the target device to use a pre-configured anonymous account, or the login information includes a second login identifier for instructing the target device to currently log in to a first user account; binding 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 determining a binding result; wherein the binding result includes a fusion identifier corresponding to both the first user account and the second user account, the fusion identifier including a second family identifier corresponding to the first user account, or a first family identifier corresponding to the second user account; based on the binding result, binding the target device to the family page corresponding to the fusion identifier, and displaying the target device on the family page; wherein both the first user account and / or the second user account can view the target device already bound on the family page corresponding to the fusion identifier, and control the target device on the family page to perform IoT functions.

[0009] Thirdly, this disclosure provides an electronic device, including: a memory and a processor, the memory being used to store a computer program; the processor being used to cause the electronic device to implement the binding method as provided in any of the second aspects when executing the computer program.

[0010] Fourthly, the present invention provides a computer-readable storage medium comprising: storing a computer program on the computer-readable storage medium, the computer program being executed by a processor using a binding method as provided in any of the second aspects.

[0011] Fifthly, the present invention provides a computer program product that, when run on a computer, causes the computer to perform a binding method as provided in any of the second aspects.

[0012] It should be noted that the aforementioned computer instructions may be stored, in whole or in part, on the first computer-readable storage medium. The first computer-readable storage medium may be packaged together with the processor of the electronic device, or it may be packaged separately from the processor of the electronic device; this disclosure does not impose any limitations on this.

[0013] The descriptions of the second, third, fourth, and fifth aspects in this disclosure can be referenced to the detailed description of the first aspect; and the beneficial effects of the descriptions of the second, third, fourth, and fifth aspects can be referenced to the analysis of the beneficial effects of the first aspect, which will not be repeated here.

[0014] In this disclosure, the names of the aforementioned electronic devices do not limit the devices or functional modules themselves. In actual implementation, these devices or functional modules may appear under other names. As long as the functions of each device or functional module are similar to those of this disclosure, they fall within the scope of the claims of this disclosure and their equivalents.

[0015] These or other aspects of this disclosure will become more readily apparent in the following description.

[0016] The technical solution provided in this disclosure has the following advantages compared with the prior art:

[0017] The binding method disclosed herein allows users to control home devices via a terminal device. Users can select to bind an electronic device on the terminal device. The terminal device then responds to the user's action by obtaining at least one bindable electronic device in the current environment. This allows the user to see which electronic devices can be bound and select the desired device. In response to the selection of the target device, the terminal device obtains the target device's device identifier. Based on the device identifier, the terminal device retrieves the target device's login information from the IoT server. The terminal device binds the device 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, determining the binding result. Based on the binding result, the terminal device binds the target device to the family page corresponding to the converged identifier and displays the target device on the family page. Since both the first and / or second user accounts corresponding to the converged identifier can view the bound target devices on the family page corresponding to the converged identifier, users do not need to consider whether the currently logged-in first user account on the terminal device and the currently logged-in second user account on the target device are the same during the binding process, simplifying the process of establishing a binding relationship between the terminal device and the target device.

[0018] Furthermore, when the terminal device is a mobile phone and the target device is a television, the binding method provided in this disclosure eliminates the need to ensure that the first user account currently logged in on the mobile phone and the second user account currently logged in on the television are the same. This simplifies the process of establishing a binding relationship between the mobile phone and the television, thus resolving the problem of how to simplify the operational process for establishing the binding relationship between the two devices. Attached Figure Description

[0019] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure.

[0020] To more clearly illustrate the technical solutions in the embodiments of this disclosure or the prior art, the accompanying drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0021] Figure 1 A schematic diagram illustrating a scenario of the binding method provided in an embodiment of this application;

[0022] Figure 2 This is one of the structural schematic diagrams of the display device provided in the embodiments of this application;

[0023] Figure 3 This is a second schematic diagram of the structure of the display device provided in the embodiments of this application;

[0024] Figure 4 One of the flowcharts of the binding method provided in the embodiments of this application;

[0025] Figure 5 One of the scenario diagrams illustrating the binding method provided in the embodiments of this application;

[0026] Figure 6 A second schematic diagram illustrating a binding method provided in an embodiment of this application;

[0027] Figure 7 The third scenario diagram illustrating the binding method provided in the embodiments of this application;

[0028] Figure 8 The fourth scenario diagram illustrating the binding method provided in the embodiments of this application;

[0029] Figure 9 Fifth scenario illustration of the binding method provided in the embodiments of this application;

[0030] Figure 10 A schematic diagram of a scenario for the binding method provided in this application embodiment;

[0031] Figure 11 Seventh scenario illustration of the binding method provided in the embodiments of this application;

[0032] Figure 12 Eighth scenario illustration of the binding method provided in the embodiments of this application;

[0033] Figure 13 A schematic diagram of a scenario for the binding method provided in this application embodiment;

[0034] Figure 14 A schematic diagram of a scenario for the binding method provided in this application embodiment;

[0035] Figure 15 Scenario illustration eleven for the binding method provided in the embodiments of this application;

[0036] Figure 16 Scenario diagram 12 illustrating the binding method provided in this application embodiment;

[0037] Figure 17 A second schematic flowchart illustrating the binding method provided in this application embodiment;

[0038] Figure 18 The third flowchart illustrating the binding method provided in this application embodiment;

[0039] Figure 19 The fourth flowchart illustrating the binding method provided in this application embodiment;

[0040] Figure 20 Fifth flowchart illustrating the binding method provided in the embodiments of this application;

[0041] Figure 21 This is the sixth flowchart illustrating the binding method provided in the embodiments of this application. Detailed Implementation

[0042] To better understand the above-mentioned objectives, features, and advantages of this disclosure, the solutions disclosed herein will be further described below. It should be noted that, unless otherwise specified, the embodiments and features described herein can be combined with each other.

[0043] Numerous specific details are set forth in the following description in order to provide a full understanding of this disclosure, but this disclosure may also be implemented in other ways different from those described herein; obviously, the embodiments in the specification are only some, and not all, of the embodiments of this disclosure.

[0044] The display device provided in this application can have various implementation forms, such as a television, a smart television, a laser projection device, a monitor, an electronic bulletin board, an electronic table, etc. Figure 1 and Figure 2 This is one specific embodiment of the display device of this application.

[0045] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0046] Currently, when binding a TV to a mobile application (App), for user privacy and security reasons, the binding operation can only be performed if the user account currently logged in on the TV and the user account logged in on the mobile application (App) are the same. This process involves the following scenarios: Scenario 1: The user account currently logged in on the TV and the user account currently logged in on the mobile app are not the same account; Scenario 2: No user account is currently logged in on the TV.

[0047] In Scenario 1, since the user account currently logged in on the TV may have already purchased memberships or other benefits, directly guiding users to switch the user account currently logged in on the TV to the same user account currently logged in on the mobile app may lead to a large number of user complaints. If users are guided to log in to the user account currently logged in on the TV on the mobile app before binding, the process is also cumbersome, and users may not be able to successfully log in to the user account currently logged in on the TV on the mobile app, resulting in the termination of the actual binding process.

[0048] In scenario 2, there needs to be a quick operation method so that users can bind their accounts quickly, instead of manually controlling the TV with the TV remote to log in. Also, when users log in manually, there is a chance that the logged-in user account is not the user account currently logged into the App.

[0049] Therefore, simplifying the process of establishing a binding relationship between mobile phones and televisions has become an urgent problem to be solved.

[0050] To address the aforementioned issues, this disclosure provides a binding method. When a user needs to control home devices through a terminal device, the user can select to bind an electronic device on the terminal device. The terminal device then responds to the user's operation to bind an electronic device, obtaining at least one bindable electronic device in the current environment. This allows the user to see which electronic devices can be bound and select the desired device. In response to the selection of a target device, the terminal device obtains the target device's device identifier. Based on the device identifier, the terminal device retrieves the target device's login information from an IoT server. The terminal device binds the device 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, determining the binding result. Based on the binding result, the terminal device binds the target device to the family page corresponding to the converged identifier and displays the target device on the family page. Since both the first user account and / or the second user account corresponding to the converged identifier can view the bound target devices on the family page corresponding to the converged identifier, the user does not need to consider whether the currently logged-in first user account on the terminal device and the currently logged-in second user account on the target device are the same during the binding process, simplifying the process of establishing a binding relationship between the terminal device and the target device. The specific implementation process is as follows:

[0051] Figure 1 This is a schematic diagram illustrating an operational scenario between a home appliance and a control device according to one or more embodiments of this application, such as... Figure 1 As shown, a user can operate the home appliance 200 through the terminal device 300 and / or 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 home appliance 200. The user can input user commands through buttons on the remote control, voice input, control panel input, etc., to control the home appliance 200. In some embodiments, mobile terminals, tablet computers, computers, laptops, and other smart devices can also be used to control the home appliance 200.

[0052] In some embodiments, the terminal device provided in this application can be the aforementioned terminal device 300. When a user uses the home device 200, they can bind the home device 200 to a first application on the terminal device 300. This allows the user to control the home device 200 through the first application on the mobile terminal 300, such as viewing the current operating status of the home device 200, turning it on or off, etc. When a user needs to bind the home device 200 to the first application on the terminal device 300, the user can select to bind an electronic device on the first application of the terminal device 300. In response to the user's operation to bind an electronic device, the terminal device 300 obtains at least one bindable electronic device in the current environment. Then, the user can select the electronic device to bind from the at least one bindable electronic device displayed on the terminal device 300. At this time, in response to the selection operation of the target device, the terminal device 300 obtains the device identifier of the target device. Then, based on the device identifier, the terminal device 300 obtains the login information of the target device from the IoT server 400. Subsequently, the terminal device 300 binds the target device 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, to determine the binding result. Then, based on the binding result, the terminal device 300 binds the target device to the family page corresponding to the converged identifier and displays the target device on the family page. Both the first user account and / or the second user account can view the target device already bound on the family page corresponding to the converged identifier and control the target device on the family page to perform physical network functions.

[0053] As can be seen, using the binding method provided in this embodiment, when a user needs to control home devices through a first application of a terminal device, the user can select to bind an electronic device on the first application of the terminal device. Then, the first application, in response to the user's operation to bind the electronic device, obtains at least one bindable electronic device in the current environment. This allows the user to understand the bindable electronic devices in the current environment and select the desired device. At this time, the terminal device, in response to the selection operation of 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; the terminal device binds the device 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 terminal device binds the target device to the family page corresponding to the converged identifier and displays the target device on the family page. Since both the first user account and / or the second user account corresponding to the converged identifier can view the target devices already bound on the family page corresponding to the converged 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 binding process, simplifying the process of establishing the binding relationship between the terminal device and the target device.

[0054] Furthermore, when the terminal device is a mobile phone and the target device is a television, the binding method provided in this embodiment does not require that the first user account currently logged in on the mobile phone and the second user account currently logged in on the television be the same, thus establishing a communication connection between the mobile phone and the television. This simplifies the process of establishing a communication connection between the mobile phone and the television and solves the problem of how to simplify the operation process of establishing a binding relationship between the mobile phone and the television.

[0055] Figure 2 A hardware configuration block diagram of a terminal device 300 according to an exemplary embodiment is shown. For example... Figure 2 The terminal device 300 shown includes at least one of the following: a tuner / demodulator 210, a communicator 220, a detector 230, an external device interface 240, a controller 250, a display 260, an audio output interface 270, a memory, a power supply, and a user interface 280. The controller includes a central processing unit, a video processor, an audio processor, a graphics processor, RAM, ROM, and a first to nth interface for input / output. The display 260 may be a touch-enabled display, such as a touch screen display. The detector 230 is used to acquire signals from the external environment or for interaction with the external environment.

[0056] In some embodiments, the controller 250 controls the operation of the display device and responds to user operations via various software control programs stored in memory. The controller 250 controls the overall operation of the home appliance 200.

[0057] In some examples, taking a mobile phone 1 as the terminal device 300 in one or more embodiments of the application, and the operating system of the mobile phone 1 as the Android system, for example... Figure 3 As shown, mobile phone 1 can be logically divided into the Applications layer (referred to as "Application layer") 21, the Application Framework layer (referred to as "Framework layer") 22, the Android runtime and system library layer (referred to as "System runtime library layer") 23, and the kernel layer 24.

[0058] The application layer 21 includes one or more applications. These applications can be system applications or third-party applications. For example, application layer 21 may include a first application that provides control functions for home appliances 200. The framework layer 22 provides application programming interfaces (APIs) and programming frameworks for the applications in application layer 21. The system runtime library layer 23 provides support for the upper layer, i.e., the framework layer 22. When the framework layer 22 is used, the Android operating system runs the C / C++ libraries contained in the system runtime library layer 23 to implement the functions required by the framework layer 22. The kernel layer 24 acts as software middleware between the hardware layer and application layer 21, managing and controlling hardware and software resources.

[0059] In some examples, after mobile phone 1 is powered on, the first application starts. While using home device 200, the user can bind home device 200 to the first application on mobile phone 1. The user can then control home device 200 through the first application on mobile phone 1, such as checking the current operating status of home device 200, powering it on or off, etc. When the user needs to bind home device 200 to the first application on mobile phone 1, the user can select to bind an electronic device on the first application on mobile phone 1. At this time, the processing unit 201 of mobile phone 1 responds to the user's operation to bind an electronic device and controls the transceiver unit 202 to obtain at least one bindable electronic device in the current environment. Then, the user can select the electronic device to bind from the at least one bindable electronic device displayed on terminal device 300. At this time, the processing unit 201 of terminal device 300 responds to the selection operation of the target device obtained by transceiver unit 202 and controls transceiver unit 202 to obtain the device identifier of the target device. Then, based on the device identifier obtained by transceiver unit 202, the processing unit 201 of terminal device 300 controls transceiver unit 202 to obtain the login information of the target device from IoT server 400. Subsequently, the processing unit 201 of the terminal device 300 binds multiple factors based on 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 the binding result. Then, based on the binding result, the processing unit 201 of the terminal device 300 binds the target device to the family page corresponding to the converged identifier and controls the display unit 203 to display the target device on the family page.

[0060] Specifically, when the executing entity of the binding method provided in this embodiment is a mobile phone 1, the storage unit 204 of the mobile phone 1 is used to store data such as the program code of the binding method provided in this embodiment.

[0061] In the following embodiments, the execution subject of the binding method provided in this disclosure is the mobile phone 1 and the home device 200 is the television 1, to illustrate the method of this application embodiment.

[0062] This application provides a binding method, applied to mobile phone 1, such as... Figure 4 As shown, the binding method may include S11-S15.

[0063] S11. In response to a user operation on a bound electronic device, obtain at least one electronic device that can be bound in the current environment.

[0064] In some examples, when a user binds an electronic device to the first application on mobile phone 1, the first application on mobile phone 1 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 is successful can the electronic device be bound to the first application. To ensure that the system parameters are compatible with different development environments (development, testing, and production) and that the system parameters can be dynamically configured, the system parameters are sent offline by the IoT server.

[0065] In some examples, to ensure the normal operation of the first application, the system parameters are supported by backup data. Specifically, this is implemented as follows: When the first application starts, it sends a request to the IoT server 400's system parameter request interface. After receiving the request from the first application on mobile phone 1, the IoT server 400 sends the current system parameters to mobile phone 1. Mobile phone 1 receives the system parameters currently sent by the IoT server 400 and refreshes its memory data to update the system parameters in its memory to those currently sent by the IoT server 400.

[0066] In some examples, when mobile phone 1 obtains information about at least one electronic device that can be bound to the current environment (such as one or more of the following: refrigerator, television, washing machine, air conditioner, water heater, gas stove, and 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).

[0067] For example, after a user opens the first application on phone 1, the following is displayed: Figure 5 The first page 1 shown includes a control 1-1 for representing "My Home" and a control 1-2 for adding devices. Users can select control 1-1 to view the electronic devices already linked in "My Home". When a user needs to link an electronic device, they can select control 1-2. In response, phone 1 displays the following: Figure 6 The second page 2 is shown. The second page 2 includes a control 2-1 for acquiring nearby devices, a control 2-2 for adding devices via QR code scanning, and a control 2-3 for receiving added devices. In response to the selection of control 2-1, mobile phone 1 displays the following... Figure 7 The third page 3. The third page 3 includes at least one electronic device that can be bound to the current environment and controls for adding electronic devices, such as a TV (1d7f) and a corresponding control 3-1 for adding the TV (1d7f), an air conditioner (FCBD) and a control 3-2 for adding the air conditioner (FCBD).

[0068] S12. In response to the selection operation of the target device, obtain the device identifier of the target device. Each target device corresponds to one device identifier, and the target device can be any of the electronic devices.

[0069] In some examples, mobile phone 1 obtains the device identifier of the target device via DLNA. The device identifier can be an identifier such as a unique identifier code used to uniquely identify the target device.

[0070] In some examples, in conjunction 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. In response to the selection operation of the target device, mobile phone 1 obtains the device identifier of the TV (1d7f).

[0071] In some examples, the currently logged-in user account on the electronic device (e.g., account 1) is the administrator of that electronic device. When a user logs in to account 1 on the first application, they can create a family name for that electronic device, as well as delete and add electronic devices under that family name, and delete and add members (one member corresponds to one user account) within that family name. Each family name corresponds to one family identifier.

[0072] S13. Based on the device identifier, obtain the login information of the target device from the IoT server. The login information includes either a first login identifier indicating that the target device is using a pre-configured anonymous account, or a second login identifier indicating that the target device is currently logged into a first user account.

[0073] In some examples, when the target device logs into the first user account (the account registered by the user), the IoT server 400 will establish a binding relationship between the device identifier of the target device and the first user account.

[0074] In some examples, when the target device is 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.

[0075] In some examples, referring to the example given in S12 above, after obtaining the device identifier of the television (1d7f), mobile phone 1 sends query information carrying the device identifier (such as deviceid) to IoT server 400. Upon receiving the query information from mobile phone 1, IoT server 400 queries the database for the login information of the television (1d7f) based on the device identifier. For example, if IoT server 400 determines that the device identifier corresponds to an anonymous account, the login information includes a first login identifier used to instruct the television (1d7f) to use a pre-configured anonymous account. Alternatively, if IoT server 400 determines that the device identifier corresponds to a first user account, the login information includes a second login identifier used to indicate that the television (1d7f) is currently logged into the first user account.

[0076] In some examples, login information includes the target device's linked phone number (mobilePhone), the target device's nickname (nickName), the user account (customerId), and a login identifier (token). If the token is not empty, it indicates that the target device has already logged into the first user account, meaning the token is the second login identifier; if the token is empty, it indicates that the target device has already logged into an anonymous account, meaning the token is the first login identifier.

[0077] S14. Bind multiple items based on 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 to determine the binding result. The binding result includes a fusion identifier corresponding to both the first and second user accounts. The fusion identifier includes either the second family identifier corresponding to the first user account or the first family identifier corresponding to the second user account.

[0078] In some examples, when mobile phone 1 binds itself 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 login information, if the login information includes the first login identifier, the process proceeds to the unlogged-in binding process; if the login information includes the second login identifier and the first user account is the same as the second user account, the process proceeds to the same account binding process; if the login information includes the second login identifier and the first user account is different from the second user account, the process proceeds to the different account binding process.

[0079] For example, referring to the example given in S13 above, the target device is a television (1d7f). The non-login binding process includes: if the login information includes a first login identifier, mobile phone 1 displays as shown... Figure 8The device guidance binding page 4 includes an operation flow for performing a preset operation on the TV (1d7f) to display a login identifier. The guidance binding page 4 includes a control 4-1 for instructing selection of a login control at the top of the display page on the TV (1d7f), a control 4-2 for instructing the use of a 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 displayed content of controls 4-1 and 4-2, the user selects the login control at the top of the display page on the TV (1d7f), and the TV (1d7f)... In response to this selection operation, a login page containing a login QR code is displayed. Then, the user selects the QR code using the scan control 4-3 displayed on mobile phone 1. Mobile phone 1 then retrieves the login identifier (e.g., a login QR code) of the television (1d7f) in response to the user's action to obtain the login identifier. If the login identifier is valid (e.g., the login QR code must begin with the string in tvLoginQrLinks mentioned in the system parameter configuration instructions; the QR code may contain the application's short code to long code conversion rKey, deviceId, target device serial number serialno, and Universally Unique Identifier (uuid) fields, but must contain either the rKey or deviceId field to be considered a valid login identifier), mobile phone 1 displays the following... Figure 9 The login page 5 is shown. In response to selecting the login confirmation control 5-1 on login page 5, mobile phone 1 sends login information to the IoT server 400. This login information instructs the IoT server to send login information to the television (1d7f), and includes a second user account. Thus, the television (1d7f) can log in based on the second user account sent by the IoT server 400. Upon receiving login information from the IoT server 400 indicating that the target device has logged in with the second user account, mobile phone 1 sends first binding information to the IoT server 400, containing the second user account, the first family identifier, and the device identifier. This first binding information instructs the IoT server 400 to establish a binding relationship between the device identifier, the second user account, and the first family identifier. Mobile phone 1 receives feedback from the IoT server 400 confirming the established binding relationship between the device identifier, the second user account, and the first family identifier, determines the merged identifier in the binding result to be the first family identifier, and displays the result as shown below. Figure 10 The connection was successful on page 6.

[0080] The account binding process includes: If mobile phone 1's login information includes a second login identifier, and the first user account is the same as the second user account, then mobile phone 1 sends first binding information containing the second user account, the first family identifier, and the device identifier to the IoT server 400. This first binding information instructs 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. Mobile phone 1 receives feedback from the IoT server 400 indicating the established binding relationship between the device identifier, the second user account, and the first family identifier, confirms that the merged identifier in the binding result is the first family identifier, and displays the following... Figure 10 The connection was successful on page 6.

[0081] The process for binding different accounts includes two scenarios: Scenario 1 and Scenario 2. Scenario 1 is where the target device is currently logged into the first user account, and the first user account is not bound to a family identifier; Scenario 2 is where the target device is currently logged into the first user account, and the first user account is bound to a family identifier.

[0082] Scenario 1 includes: Referring to the example given in S13 above, when mobile phone 1's login information includes a second login identifier, and the first user account is different from the second user account, it sends second binding information carrying the first user account and device identifier to the IoT server 400. The second binding information instructs the IoT server 400 to create a preset family identifier (e.g., homeA) if the first user account is not bound to a second family identifier, and to establish a binding relationship between the first user account, device identifier, and homeA. Mobile phone 1 receives feedback information from the IoT server 400 carrying the binding relationship between the first user account, device identifier, and homeA. If the first family identifier (e.g., homeB) is different from the preset family identifier homeA, it displays... Figure 11 The application page 7 is shown. Application page 7 includes a preset pop-up window 7-1 indicating whether to join the preset family corresponding to homeA. In response to selecting the control 11 in the preset pop-up window 7-1 to apply for joining the preset family, mobile phone 1 sends an application request to the IoT server 400. This application request instructs the IoT server to send a request to join the preset family to the preset family (e.g., to the second user account corresponding to homeA (i.e., the first user account that initially created the preset family corresponding to homeA, such as account 1)). Afterwards, the IoT server 400 sends feedback information to mobile phone 1 indicating that the request information has been sent to the second user account. Upon receiving the feedback information from server 400 indicating that the request information has been sent to the second user account, mobile phone 1 displays the following... Figure 12The prompt page 8 shown is shown. Prompt page 8 includes a message 8-1 indicating that the user is "waiting for administrator approval of the second user account corresponding to homeA". Afterwards, other users can receive this request information in the first application logged into account 1. When allowed to join the preset family, the first application logged into account 1 can send feedback information allowing joining the preset family to the IoT server 400. The IoT server 400 then sends this feedback information to mobile phone 1. Mobile phone 1 receives the feedback information sent by the IoT server 400; the feedback information indicates that a request to join the preset family has been sent to account 1. Mobile phone 1 receives confirmation information from the IoT server 400 allowing joining the preset family (e.g., the confirmation information is a Message Queuing Telemetry Transport (MQTT) message), confirming that the fusion identifier in the binding result is homeA; where the second family identifier is equal to the preset family identifier. Mobile phone 1 displays as shown... Figure 13 The main page 9 is shown. Main page 9 includes a control 9-1 for representing all homes, a control 9-2 for representing my home, and a control 9-3 for representing preset homes. In response to the selection of control 9-1, the following is displayed: Figure 14 The selection page 10 includes a control 9-1 and a control 10-1 for representing preset families. When a user needs to view preset families, the user can select from the control 10-1. In response to this selection, the mobile phone 1 displays the following... Figure 15 The display page 11 shown is shown. Display page 11 includes at least one target device, such as a television (1d7f), that is bound to homeA. The user can then control the television 3 to perform IoT functions via the first application on mobile phone 1, such as turning the television (1d7f) on or off (1d7f). When the user needs to view a preset home, the user can select control 10-2. In response to the selection of control 10-2, mobile phone 1 displays the following... Figure 5 The first page 1 is shown. Additionally, users can access... Figure 13 On the main page 9 shown, selecting the control 9-2 used to represent my home will display the following... Figure 5 The first page 1 is shown. Alternatively, users can access it from, for example... Figure 13 On the main page 9 shown, selecting the control 9-3 used to represent my home will display the following... Figure 15 The page shown is page 11.

[0083] Scenario 2 includes: When mobile phone 1's login information includes a second login identifier, and the first user account is different from the second user account, it sends third binding information carrying the first user account and device identifier to IoT server 400. This third binding information instructs IoT server 400 to establish a binding relationship between the first user account, device identifier, and homeA, provided the first user account is already bound to a second home identifier (e.g., homeA). Mobile phone 1 receives feedback information from IoT server 400 carrying the binding relationship between the first user account, device identifier, and homeA. If the first home identifier (e.g., homeB) is the same as homeA, the merged identifier in the binding result is determined to be homeA. (Displayed as follows...) Figure 16 The aforementioned switching page 12 includes a pop-up window 12-1 indicating whether the television (1d7f) is bound and whether to switch to the preset home viewing television (1d7f). Pop-up window 12-1 includes a control 12-1-1 for confirming switching to the preset home viewing television (1d7f) and a control 12-1-2 for canceling switching to the preset home viewing television (1d7f). In response to the selection operation of control 12-1-1, mobile phone 1 displays as follows... Figure 15 The page shown is page 11.

[0084] S15. Based on the binding result, bind the target device to the home page corresponding to the converged identifier, and display the target device on the home page. Both the first user account and / or the second user account can view the target device bound to the home page corresponding to the converged identifier and control the target device on the home page to perform physical network functions.

[0085] In some examples, during the process of applying to join a preset family, if the first user account bound to the preset family is not a user account used by a family member, it can be quickly changed. For example, if a relative or friend binds the target device when visiting, the first user account bound to the target device can be changed. For instance, in response to the user operation of rebinding the target device, a prompt message can be generated to prompt the user to log out of the currently logged-in first user account on the target device and to re-execute the user operation of binding the electronic device.

[0086] For example, in conjunction with the example given in S14 above, such as Figure 11As shown, the application page 7 also includes a control 7-2 for instructing users to rebind devices. When a user needs to rebind the first user account of the TV (1d7f), they can select the control 7-2. In response to the selection of the control 7-2, the mobile phone 1 generates a prompt to log out of the currently logged-in first user account on the target device and re-executes the user operation of binding the electronic device (i.e., S11 above), thereby allowing the first user account of the TV (1d7f) to be rebound.

[0087] As can be seen, using the binding method provided in this embodiment, when a user needs to control a television through the first application of mobile phone 1, the user can select to bind the television on the first application of mobile phone 1. Then, the first application of mobile phone 1, in response to the user's operation of binding the television, 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 desired electronic device. At this time, mobile phone 1, in response to the selection operation of the television, obtains the television's device identifier; based on the device identifier, mobile phone 1 obtains the television's login information from the IoT server; mobile phone 1 binds the television 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, mobile phone 1 binds the television to the family page corresponding to the convergence identifier and displays the television on the family page. Since both the first user account and / or the second user account corresponding to the convergence identifier can view the target devices already bound on the family page corresponding to the convergence 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 binding process, simplifying the process of establishing a binding relationship between the terminal device and the target device.

[0088] In some feasible examples, combining Figure 4 ,like Figure 17 As shown, the above S14 can be specifically implemented through the following S140-S145.

[0089] S140. If the login information includes a first login identifier, display a device boot-up binding page. The device boot-up binding page includes an operation flow for performing preset operations on the target device to display the login identifier.

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

[0091] S142. If the login identifier is valid, display the login page.

[0092] S143. In response to the selection operation of the login control on the login page, send login information to the IoT server; wherein, the login information is used to instruct the IoT server to send login information to the target device, and the login information includes a second user account.

[0093] S144. Upon receiving login information from the IoT server indicating that the target device has logged into the second user account, send first binding information containing 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 between the device identifier, the second user account, and the first family identifier.

[0094] S145. Receive feedback results from the IoT server regarding the established binding relationship between the device identifier, the second user account, and the first family identifier, and determine that the fused identifier in the binding result is the first family identifier.

[0095] In some feasible examples, combining Figure 4 ,like Figure 18 As shown, the above S14 can be specifically implemented through the following S146 and S147.

[0096] S146. If the login information includes a second login identifier, and the first user account is the same as the second user account, then send first binding information containing the second user account, the first family identifier, and the device identifier to the IoT server. The first binding information instructs the IoT server to establish a binding relationship between the device identifier, the first family identifier, and the family identifier corresponding to the second user account.

[0097] S147. Receive feedback results from the IoT server regarding the established binding relationship between the device identifier, the second user account, and the first family identifier, and determine that the fused identifier in the binding result is the first family identifier.

[0098] In some feasible examples, combining Figure 4 ,like Figure 19 As shown, the above S14 can be specifically implemented through the following S148-S149-4.

[0099] S148. When the login information includes a 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 device identifier to the IoT server; wherein, the second binding information is used to instruct the IoT 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 between the first user account, the device identifier and the preset family identifier.

[0100] S149. Receive feedback information from the IoT server carrying the binding relationship between the first user account, device identifier, and preset family identifier.

[0101] S149-1. If the first family identifier is different from the preset family identifier, display the preset pop-up window for adding the preset family corresponding to the preset family identifier.

[0102] S149-2. In response to the selection operation of the control in the preset pop-up window to apply to join the preset family, an application request is sent to the IoT server. The application request instructs the IoT server to send the application to join the preset family request information to the preset family.

[0103] S149-3, Receive feedback information sent by the IoT server. The feedback information indicates that a request to join the preset household has been sent to the first user account.

[0104] S149-4. Receive confirmation information from the IoT server allowing the user to join a preset family, and confirm that the fusion identifier in the binding result is the preset family identifier. The second family identifier is equal to the preset family identifier.

[0105] In some feasible examples, combining Figure 4 ,like Figure 20 As shown, the above S14 can be specifically implemented through the following S149-5-S149-7.

[0106] S149-5. When the login information includes a second login identifier and the first user account is different from the second user account, send third binding information carrying the first user account and device identifier to the IoT server. The third binding information instructs the IoT server to establish a binding relationship between the first user account, the device identifier, and the second family identifier, provided that the first user account is already bound to the second family identifier.

[0107] S149-6 Receive feedback information sent by the IoT server carrying the binding relationship between the first user account, the device identifier, and the second family identifier.

[0108] S149-7. If the first family identifier and the second family identifier are the same, determine the fusion identifier in the binding result as the second family identifier.

[0109] In some feasible examples, combining Figure 4 ,like Figure 21 As shown, the binding method provided in this embodiment of the present disclosure further includes: S16.

[0110] S16. In response to the user operation of rebinding the target device, generate a first user account to prompt the user to log out of the current login on the target device, and re-execute the user operation prompt message for binding the electronic device.

[0111] The foregoing mainly describes the solutions provided by the embodiments of this application from a methodological perspective. To achieve the above functions, it includes corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0112] This application embodiment can divide the terminal device into functional modules according to the above method example. For example, each function can be divided into its own functional module, or two or more functions can be integrated into one processing unit. The integrated modules can be implemented in hardware or as software functional modules. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0113] An embodiment of this application provides a schematic diagram of the structure of a terminal device 300, including a processor 101, a communicator 102, and a display 103.

[0114] Processor 101 is configured to, in response to a user operation on a bound electronic device, control communicator 102 to acquire at least one bindable electronic device in the current environment; processor 101 is also configured to, in response to a selection operation on a target device acquired by communicator 102, control communicator 102 to acquire a device identifier of the target device; wherein, one target device corresponds to one device identifier, and the target device is any one of the electronic devices; processor 101 is further configured to, based on the device identifier acquired by communicator 102, control communicator 102 to acquire login information of the target device from an IoT server; wherein, the login information includes a first login identifier for instructing the target device to use a pre-configured anonymous account, or the login information includes a second login identifier for instructing the target device to currently log in to a first user account; processor 1 01 is also configured to bind multiple items based on 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 obtained by the communicator 102, and determine the binding result; wherein, the binding result includes a converged identifier corresponding to both the first user account and the second user account, and the converged identifier includes the second family identifier corresponding to the first user account, or the first family identifier corresponding to the second user account; the processor 101 is also configured to bind the target device to the family page corresponding to the converged identifier based on the binding result, and control the display 103 to display the target device on the family page; wherein, both the first user account and / or the second user account can view the target device already bound in the family page corresponding to the converged identifier, and control the target device in the family page to perform physical network functions.

[0115] In some implementable examples, processor 101 is further configured to control display 103 to display a device boot binding page when the login information acquired by communicator 102 includes a first login identifier; wherein the device boot binding page includes an operation flow for performing a preset operation on the target device to display the login identifier; processor 101 is further configured to control communicator 102 to acquire the login identifier of the target device in response to a user operation to acquire the login identifier; processor 101 is further configured to control display 103 to display a login page when the login identifier acquired by communicator 102 is a valid identifier; processor 101 is further configured to control communicator 102 to send login information to the IoT server in response to a selection operation of the login control in the login page displayed on display 103; wherein the login information... The information is used to instruct the IoT server to send login information to the target device, the login information including a second user account; the processor 101 is further configured to, when the communicator 102 receives login information sent by the IoT server indicating that the target device has logged in with the second user account, control the communicator 102 to send first binding information containing the second user account, a first family identifier, and a device identifier to the IoT server; wherein, the first binding information is used to instruct the IoT server to establish a binding relationship between the device identifier, the second user account, and the first family identifier; the processor 101 is further configured to, upon receiving feedback from the IoT server indicating that the binding relationship between the device identifier, the second user account, and the first family identifier has been established, determine that the fused identifier in the binding result is the first family identifier.

[0116] In some implementable examples, the processor 101 is further configured to, when the login information obtained by the communicator 102 includes a second login identifier and the first user account is the same as the second user account, control the communicator 102 to send first binding information containing 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 between the device identifier, the first family identifier, and the family identifier corresponding to the second user account;

[0117] The processor 101 is further configured such that the communicator 102 receives feedback results from the IoT server regarding the established binding relationship between the device identifier, the second user account, and the first family identifier, and determines the fused identifier in the binding result as the first family identifier.

[0118] In some implementable examples, processor 101 is further configured to, when the login information obtained by communicator 102 includes a second login identifier and the first user account is different from the second user account, control communicator 102 to send second binding information carrying the first user account and device identifier to the IoT server; wherein, the second binding information is used to instruct the IoT server to create a preset family identifier when the first user account is not bound to a second family identifier, and to establish a binding relationship between the first user account, device identifier, and preset family identifier; communicator 102 is further configured to receive feedback information sent by the IoT server carrying the binding relationship between the first user account, device identifier, and preset family identifier; processor 101 is further configured to, when the first family identifier is different from the preset family identifier obtained by communicator 102, ... The control display 103 displays a preset pop-up window for joining a preset family corresponding to a preset family identifier; the processor 101 is further configured to, in response to the selection operation of the control for applying to join a preset family in the preset pop-up window displayed on the display 103, control the communicator 102 to send an application request to the IoT server; wherein, the application request is used to instruct the IoT server to send application information for joining the preset family to the preset family; the communicator 102 is further configured to receive feedback information sent by the IoT server; wherein, the feedback information is used to indicate that the application information for joining the preset family has been sent to the first user account; the processor 101 is further configured to, upon receiving confirmation information from the IoT server that the communicator 102 is allowed to join the preset family, 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.

[0119] In some implementable examples, processor 101 is further configured to, when the login information obtained by communicator 102 includes a second login identifier and the first user account is different from the second user account, control communicator 102 to send third binding information carrying the first user account and device identifier to IoT server; wherein, the third binding information is used to instruct IoT server to establish a binding relationship between the first user account, device identifier and second family identifier when the first user account is already bound to the second family identifier; communicator 102 is further configured to receive feedback information sent by IoT server carrying the binding relationship between the first user account, device identifier and second family identifier; processor 101 is further configured to, when the first family identifier is the same as the second family identifier received by communicator 102, determine the fusion identifier in the binding result as the second family identifier.

[0120] In some implementable examples, processor 101 is also configured to generate a first user account prompting the user to log out of the current login on the target device in response to a user action to rebind the target device, and to re-execute the user action prompt message for binding the electronic device.

[0121] All relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and their functions will not be repeated here.

[0122] Of course, the terminal device 300 provided in this application embodiment includes, but is not limited to, the above-described modules. For example, the terminal device 300 may also include a memory 104. The memory 104 may be used to store the program code of the terminal device 300, and may also be used to store data generated by the terminal device 300 during operation, such as data in write requests.

[0123] As an example, combined Figure 3 The transceiver unit 202 in the terminal device 300 performs the same function as the communicator 102, the processing unit 201 performs the same function as the processor 101, the display unit 203 performs the same function as the display 103, and the storage unit 204 performs the same function as the memory 104.

[0124] This application also provides a chip system that can be applied to the terminal device 300 in the foregoing embodiments. The chip system includes at least one processor 1501 and at least one interface circuit 1502. The processor 1501 may be the processor in the terminal device 300. The processor 1501 and the interface circuit 1502 are interconnected via a line. The processor 1501 can receive and execute computer instructions from the memory of the terminal device 300 through the interface circuit 1502. When the computer instructions are executed by the processor 1501, the terminal device 300 can perform the various steps executed by the terminal device 300 in the foregoing embodiments. Of course, the chip system may also include other discrete devices, which are not specifically limited in this application.

[0125] This application also provides a computer-readable storage medium for storing computer instructions executed by the terminal device 300.

[0126] The above description is merely a specific embodiment of this disclosure, enabling those skilled in the art to understand or implement it. 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 this disclosure. Therefore, this disclosure is not to be limited to the embodiments described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A terminal device, characterized by comprising: Comprise: A processor configured to control a communicator to acquire at least one electronic device that can be bound in a current environment in response to a user operation of binding the electronic device; The processor is further configured to control the communicator to acquire a device identifier of a target device in response to a selection operation of the target device acquired by the communicator; wherein one target device corresponds to one device identifier, and the target device is any one of the electronic devices; The processor is further configured to control the communicator to acquire login information of the target device from an Internet of Things server based on the device identifier acquired by the communicator; wherein the login information includes a first login identifier indicating that the target device uses a pre-configured anonymous account, or the login information includes a second login identifier indicating that the target device is currently logged in a first user account; The processor is further configured to determine a binding result based on a plurality of items including a currently logged-in second user account, a first family identifier to which the second user account belongs, the device identifier, and the login information acquired by the communicator; wherein the binding result includes a fusion identifier corresponding to both the first user account and the second user account, and the fusion identifier includes a second family identifier corresponding to the first user account or a first family identifier corresponding to the second user account; The processor is further configured to bind the target device to a family page corresponding to the fusion identifier based on the binding result, and control a display to display the target device in the family page; wherein the first user account and / or the second user account can check the target devices bound in the family page corresponding to the fusion identifier, and control the target devices in the family page to perform physical network functions.

2. The terminal device according to claim 1, characterized by The processor is further configured to control the display to display a device guide binding page when the login information acquired by the communicator includes the first login identifier; wherein the device guide binding page includes an operation flow for performing a preset operation on the target device to display a login identifier; The processor is further configured to control the communicator to acquire the login identifier of the target device in response to a user operation of acquiring the login identifier; The processor is further configured to control the display to display a login page when the login identifier acquired by the communicator is a valid identifier; The processor is further configured to control the communicator to send login information to the Internet of Things server in response to a selection operation of a login control in the login page displayed by the display; 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. The processor is further configured to control the communicator to send, to the Internet of Things server, first binding information containing the second user account, the first family identifier and the device identifier, in a case where the communicator receives login information sent by the Internet of Things server and indicating that the target device has logged in the second user account; wherein the first binding information is used to instruct the Internet of Things server to establish a binding relationship among the device identifier, the second user account and the first family identifier. The processor is further configured to determine, in a case where the communicator receives feedback information sent by the Internet of Things server and indicating that the binding relationship among the device identifier, the second user account and the first family identifier has been established, that the fusion identifier in the binding result is the first family identifier.

3. The terminal device of claim 1, wherein, The processor is further configured to control the communicator to send, to the Internet of Things server, first binding information containing the second user account, the first family identifier and the device identifier, in a case where the login information obtained by the communicator contains the second login identifier and the first user account is the same as the second user account; wherein the first binding information is used to instruct the Internet of Things server to establish a binding relationship among the device identifier, the first family identifier and the family identifier corresponding to the second user account. The processor is further configured to determine, in a case where the communicator receives feedback information sent by the Internet of Things server and indicating that the binding relationship among the device identifier, the second user account and the first family identifier has been established, that the fusion identifier in the binding result is the first family identifier.

4. The terminal device according to claim 1, characterized by The processor is further configured to control the communicator to send, to the Internet of Things server, second binding information carrying the first user account and the device identifier, in a case where the login information obtained by the communicator contains the second login identifier and the first user account is different from the second user account; wherein the second binding information is used to instruct the Internet of Things server to create a preset family identifier in a case where the first user account is not bound to a second family identifier, and to establish a binding relationship among the first user account, the device identifier and the preset family identifier. The communicator is further configured to receive feedback information sent by the Internet of Things server and carrying a binding relationship among the first user account, the device identifier and the preset family identifier. The processor is further configured to control the display to display a preset pop-up window for joining a preset family corresponding to the preset family identifier, in a case where the first family identifier is different from the preset family identifier obtained by the communicator. The processor is further configured to, in response to a selection operation on the control for applying to join the preset family in the preset pop-up window displayed by the display, control the communicator to send 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; The communicator is further configured to receive feedback information sent by the Internet of Things server; wherein the feedback information is used to indicate that the request information for applying to join the preset family has been sent to the first user account; The processor is further configured to, in response to the communicator receiving confirmation information for allowing to join the preset family sent by the Internet of Things server, 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.

5. The terminal device according to claim 1, characterized by The processor is further configured to, in the case that the login information acquired by the communicator includes the second login identifier and the first user account is different from the second user account, control the communicator to send third binding information carrying the first user account and the device identifier 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 among the first user account, the device identifier and the second family identifier in the case that the first user account has been bound with the second family identifier; The communicator is further configured to receive feedback information sent by the Internet of Things server carrying the binding relationship among the first user account, the device identifier and the second family identifier; The processor is further configured to, in the case that the first family identifier is the same as the second family identifier received by the communicator, determine that the fusion identifier in the binding result is the second family identifier.

6. The terminal device of claim 1, wherein, The processor is further configured to, in response to a user operation of re-binding the target device, generate user operation prompt information for prompting to exit the first user account currently logged in the target device and re-perform the user operation of binding the electronic device.

7. A binding method, characterized by, Comprise: In response to a user operation of binding an electronic device, acquire at least one electronic device that can be bound in a current environment; In response to a selection operation on a target device, acquire a device identifier of the target device; wherein one target device corresponds to one device identifier, and the target device is any one of the electronic devices; Based on the device identifier, acquire login information of the target device from an Internet of Things server; wherein the login information includes a first login identifier used to indicate that the target device uses a pre-configured anonymous account, or the login information includes a second login identifier used to indicate that the target device is currently logged in a first user account; binding is performed based on the second user account currently logged in, the first family identifier to which the second user account belongs, the device identifier, and multiple items in the login information, and a binding result is determined; the binding result contains a fusion identifier corresponding to both the first user account and the second user account, and the fusion identifier includes a second family identifier corresponding to the first user account or a first family identifier corresponding to the second user account; based on the binding result, the target device is bound to a family page corresponding to the fusion identifier, and the target device is displayed in the family page; the first user account and / or the second user account can check the target device bound in the family page corresponding to the fusion identifier, and control the target device in the family page to perform a physical network function.

8. The binding method of claim 7, wherein, The binding is performed based on the second user account currently logged in, the family identifier to which the second user account belongs, the device identifier, and multiple items in the login information, and a binding result is determined, including: In the case that the login information includes the first login identifier, a device guide binding page is displayed; the device guide binding page includes an operation flow for performing a preset operation on the target device to display a login identifier; In response to a user operation of obtaining a login identifier, a login identifier of the target device is obtained; In the case that the login identifier is a valid identifier, a login page is displayed; In response to a selection operation on a login control in the login page, login information is sent to the Internet of Things server; 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; In the case that the login information sent by the Internet of Things server is received, indicating that the target device has logged in the second user account, first binding information containing the second user account, the first family identifier, and the device identifier is sent to the Internet of Things server; the first binding information is used to instruct the Internet of Things server to establish a binding relationship among the device identifier, the second user account, and the first family identifier; The feedback result of the Internet of Things server that the binding relationship among the device identifier, the second user account, and the first family identifier has been established is received, and the fusion identifier in the binding result is determined as the first family identifier.

9. The binding method of claim 7, wherein, The binding is performed based on the second user account currently logged in, the family identifier to which the second user account belongs, the device identifier, and multiple items in the login information, and a binding result is determined, including: In a case that the login information comprises the second login identifier, if the first user account is identical to the second user account, first binding information containing the second user account, the first home identifier and the device identifier is sent 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 among the device identifier, the first home identifier and the home identifier corresponding to the second user account. A feedback result of the Internet of Things server establishing a binding relationship among the device identifier, the second user account and the first home identifier is received, and a fusion identifier in a binding result is determined as the first home identifier.

10. A computer-readable storage medium, characterized in that, Comprise: The computer readable storage medium has stored thereon a computer program, which, when executed by a computing device, causes the computing device to implement the binding method of any one of claims 7-9.

Images