Equipment binding method, electronic equipment and storage medium

Abstract

The embodiment of the invention provides an equipment binding method, electronic equipment and a storage medium, and relates to the field of Internet of Things. The method comprises the following steps: receiving target equipment information, and displaying verification information, so that a user terminal sends a verification request to a cloud in response to scanning the verification information; receiving verification passing information which is sent by the cloud and contains the target activation code, and sending the target activation code to the to-be-activated equipment; the verification passing information is sent after the cloud determines that a target user identifier contained in the verification request passes verification, and a target activation code contained in the verification passing information is determined by the cloud according to a target equipment identifier; and receiving activation success information sent after the to-be-activated device is successfully activated according to the target activation code, and sending a binding request to the cloud, so that the cloud establishes a corresponding relationship between the target user identifier and the target device identifier according to the target user identifier passing the verification. According to the method and the device, the problems of tedious operation and poor convenience of binding the user terminal to the equipment are solved.

Description

Technical Field

[0001] The present application relates to the technical field of Internet of Things, and in particular to a device binding method, an electronic device and a storage medium. Background Art

[0002] Currently, in the activation process of smart devices, two activation methods are usually used: remote control activation and mini-program activation. The mini-program activation method can reduce the cost of purchasing and activating remote controls and is gradually being promoted.

[0003] Then, in the existing mini-program activation process, due to the lack of interaction with the user terminal, after the installer installs and activates the smart device, the user still needs to search and bind the smart device by himself. Therefore, there is a problem of cumbersome user operations and poor convenience during the binding process of the smart device. Summary of the invention

[0004] The embodiments of the present application provide a device binding method, an electronic device, and a storage medium, which are used to solve the technical problems of cumbersome user operations and poor convenience during the binding process of smart devices.

[0005] According to a first aspect of an embodiment of the present application, a device binding method is provided, which is applied to an activation terminal, and the method includes: receiving target device information of a device to be activated sent by a cloud, and displaying verification information so that the user terminal sends a verification request to the cloud in response to scanning the verification information; the target device information is sent after the cloud receives an activation request sent by the activation terminal and including a target device identifier of the device to be activated; Receive the verification pass information including the target activation code sent by the cloud, and send the target activation code to the device to be activated; the verification pass information is sent by the cloud after it determines that the target user identifier included in the verification request has been verified, and the target activation code included in the verification pass information is determined by the cloud according to the target device identifier; Receive activation success information sent by the device to be activated after successful activation according to the target activation code, and send a binding request containing the target device identifier to the cloud, so that the cloud can establish a corresponding relationship between the target user identifier and the target device identifier based on the target user identifier that has passed the verification.

[0006] The beneficial effects of the technical solution provided by the embodiment of the present application are: The device binding method for activating a terminal provided in an embodiment of the present application receives device information of the device to be activated sent by the cloud after sending an activation request to the cloud, and then displays verification information, so that the user terminal can send a verification request to the cloud by scanning the verification information. When the cloud determines that the target user identifier included in the verification request has been verified, the target activation code is determined according to the target device identifier. The activation terminal receives the verification pass information carrying the target activation code sent by the cloud, and then the activation terminal can send the target activation code to the device to be activated to activate the device to be activated. After the device to be activated is successfully activated according to the target activation code, the activation terminal receives the activation success information sent by the device to be activated, and then the activation terminal sends a binding request containing the target device identifier to the cloud, so that the target user identifier that has passed the aforementioned verification in the cloud is established, thereby The correspondence between the target user identifier and the target device identifier. During the process of initiating an activation request, the activation terminal displays verification information and allows the user terminal to scan the verification information so that the cloud can verify whether the user identifier corresponding to the user terminal meets the preset conditions. When the activation terminal receives the verification pass information containing the target activation code, it determines that the cloud has recorded the target user identifier that has passed the verification at this time. After subsequently receiving the activation success information, the activation terminal directly initiates a binding request, so that the user terminal does not need to re-search for the device to be activated and bind it, and the cloud can establish a binding relationship between the target device identifier and the target user identifier based on the corresponding relationship stored during verification, eliminating the step of users manually binding devices, greatly simplifying the process of binding user identifiers to devices to be activated, and improving the convenience of binding and user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in describing the embodiments of the present application are briefly introduced below.

[0008] Figure 1 A schematic diagram of a system architecture for implementing a device binding method provided in an embodiment of the present application; Figure 2 A schematic diagram of a flow chart of a device binding method for activating a terminal provided in an embodiment of the present application; Figure 3 A schematic diagram of a flow chart of a method for sending a binding request in a device binding method provided in an embodiment of the present application; Figure 4 A schematic diagram of a method for sending an activation request in a device binding method provided in an embodiment of the present application; Figure 5 A schematic diagram of a process flow of a device binding method applied to the cloud provided in an embodiment of the present application; Figure 6A schematic diagram of an interactive process of a device binding method provided in an embodiment of the present application; Figure 7 A schematic diagram of the structure of an activation terminal provided in an embodiment of the present application; Figure 8 A schematic diagram of a cloud structure provided in an embodiment of the present application; Fig. 9 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0009] The embodiments of the present application are described below in conjunction with the drawings in the present application. It should be understood that the implementation methods described below in conjunction with the drawings are exemplary descriptions for explaining the technical solutions of the embodiments of the present application and do not constitute a limitation on the technical solutions of the embodiments of the present application.

[0010] It will be understood by those skilled in the art that, unless specifically stated, the singular forms "one", "an" and "the" used herein may also include plural forms. It should be further understood that the terms "including" and "comprising" used in the embodiments of the present application refer to that the corresponding features can be implemented as the presented features, information, data, steps, operations, elements and / or components, but do not exclude the implementation as other features, information, data, steps, operations, elements, components and / or combinations thereof supported by the technical field. It should be understood that when we call an element "connected" or "coupled" to another element, the one element can be directly connected or coupled to the other element, or it can refer to that the one element and the other element establish a connection relationship through an intermediate element. In addition, the "connection" or "coupling" used here may include wireless connection or wireless coupling. The term "and / or" used here indicates at least one of the items defined by the term, for example, "A and / or B" can be implemented as "A", or as "B", or as "A and B".

[0011] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.

[0012] The following describes several exemplary embodiments to illustrate the technical solutions of the embodiments of the present application and the technical effects produced by the technical solutions of the present application. It should be noted that the following embodiments can refer to, draw on or combine with each other, and the same terms, similar features and similar implementation steps in different embodiments will not be described repeatedly.

[0013] Figure 1 A schematic diagram of a system architecture for implementing a device binding method provided in an embodiment of the present application, wherein the system architecture includes: a terminal 120, a cloud 140, and a device to be activated 160.

[0014] The terminal 120 installs and runs an application program having a device binding method, and the terminal 120 is used to activate and bind the device to be activated 160; The terminal 120 is connected to the cloud 140 via a wireless network or a wired network.

[0015] The cloud 140 includes at least one of a server, multiple servers, a cloud computing platform, and a virtualization center. Schematically, the cloud 140 includes a processor 144 and a memory 142, and the memory 142 includes a display module 1421, a control module 1422, and a receiving module 1423. The cloud 140 is used to provide background services for the application of the device binding method. Optionally, the cloud 140 undertakes the main computing work and the terminal 120 undertakes the secondary computing work; or, the cloud 140 undertakes the secondary computing work and the terminal 120 undertakes the main computing work; or, the cloud 140 and the terminal 120 adopt a distributed computing architecture for collaborative computing.

[0016] Optionally, the device types of the terminal include: at least one of a smart phone, a tablet computer, an e-book reader, a Moving Picture Experts Group Audio Layer III (MP3) player, a Moving Picture Experts Group Audio Layer IV (MP4) player, a laptop computer and a desktop computer.

[0017] Those skilled in the art will appreciate that the number of the above terminals may be more or less. For example, the above terminal may be only one, or the above terminals may be dozens or hundreds, or more. The embodiment of the present application does not limit the number of terminals and device types.

[0018] The present application provides a device binding method, which is applied to activate a terminal, such as Figure 2 As shown, the method includes: S101, receiving target device information of the device to be activated sent by the cloud, and displaying verification information.

[0019] In the embodiments of the present application, the device to be activated refers to a device that needs to complete the activation process before it can be used normally, and the device to be activated is a device that can interact with the activation terminal through line communication. The device to be activated can be a smart home device, such as a smart lock, a smart light, and a smart appliance; the device to be activated can also be a personal electronic device, such as a smart watch, a fitness device, an e-reader, etc.; the device to be activated can also be an industrial controller, such as a PLC control, an industrial robot, etc.; the device to be activated can also be other electronic devices that need to be activated remotely or locally.

[0020] In an embodiment of the present application, the activation terminal is a terminal operated by an installer. After installing the device to be activated, the installer activates the device to be activated through the activation terminal. For example, the device to be activated is a smart clothes dryer. After the installer installs the smart clothes dryer at home, if the installer wants to use the smart clothes dryer, the installer must activate the smart clothes dryer through the activation terminal he carries.

[0021] In the embodiment of the present application, the target device information is sent after the cloud receives an activation request including a target device identifier of the device to be activated sent by the activation terminal.

[0022] In an embodiment of the present application, the target device information is information related to the device to be activated, such as the model, function and other information of the device to be activated. The target device information is sent by the cloud to the device to be activated after the activation terminal sends an activation request containing the target device identifier of the device to be activated to the cloud, so that the activation terminal can determine whether the device information of the device to be activated is accurate.

[0023] In an embodiment of the present application, verification information is displayed so that the user terminal sends a verification request to the cloud in response to scanning the verification information.

[0024] In the embodiment of the present application, the activation terminal displays the verification information so that the user terminal can send a verification request to the cloud by scanning the verification information to verify whether the target user identifier corresponding to the user terminal currently has the authority to activate the device to be activated.

[0025] In an embodiment of the present application, the verification information may be a verification QR code, or an NFC tag embedded with a link, which the user terminal can scan to open the link that initiates the verification request, or a barcode containing link information.

[0026] In one example, the activation terminal displays a verification QR code and text information instructing the user terminal to scan the verification QR code on a visual interface. After the user terminal scans the verification QR code, the user terminal displays a verification login interface. The user terminal logs in or registers on the verification interface. After successful login or registration, the user terminal sends the input user ID along with the verification request to the cloud for the cloud to verify whether the user ID has the authority to activate the device to be activated.

[0027] S102, receiving verification pass information including a target activation code sent by the cloud, and sending the target activation code to the device to be activated.

[0028] In the embodiment of the present application, the verification pass information is sent after the cloud determines that the target user identifier included in the verification request has been verified, and the target activation code included in the verification pass information is determined by the cloud based on the target device identifier.

[0029] In an embodiment of the present application, after the cloud receives the verification request, it first verifies the target user identifier contained in the verification request. After determining that the target user identifier is verified, it determines the target activation code based on the target device identifier, and then sends verification information containing the target activation code to the activation terminal.

[0030] In the embodiment of the present application, after it is determined that the user identification verification is passed, the target user identification and the target device identification may be stored correspondingly in the first database, that is, a temporary corresponding relationship between the target user identification and the target device identification is established.

[0031] In the embodiment of the present application, the cloud can also store device identifications and activation codes through an activation library, and each device identification has a unique corresponding activation code.

[0032] In one example, the verification information is obtained in the following manner: after the cloud receives the verification request containing the target user ID, it determines whether the preset conditions are met based on the target user ID. If the preset conditions are met, it means that the target user ID has the activation authority for the device to be activated, and the target user ID is deemed to have passed the verification. Therefore, the target activation code corresponding to the target device ID is obtained from the activation library that stores the device ID and the activation code. At the same time, the cloud also stores the corresponding relationship between the target user ID and the target device ID in the first library. Finally, the cloud sends the verification information containing the target activation code to the activation terminal. Among them, the content stored in the first library will be cleared after a preset time period, that is, the first library stores temporary data.

[0033] In the embodiment of the present application, after the activation terminal receives the verification pass information including the target activation code sent by the cloud, the activation terminal has determined that the user terminal has the activation authority, so it sends the target activation code to the device to be activated to activate the device to be activated.

[0034] S103, receiving activation success information sent by the device to be activated after successful activation according to the target activation code, and sending a binding request including the target device identifier to the cloud.

[0035] In an embodiment of the present application, when the activation terminal receives the activation success information sent by the device to be activated, it indicates that the current device to be activated has been successfully activated according to the target activation code. Then, at this time, the device to be activated can be bound, so a binding request containing the target device identifier is sent to the cloud.

[0036] In the embodiment of the present application, a binding request is sent to the cloud so that the cloud establishes a correspondence between the target user identifier and the target device identifier according to the aforementioned verified target user identifier.

[0037] In the embodiment of the present application, since the cloud has clearly verified that the target user identifier has passed the verification before obtaining the target activation code, it means that the current target user identifier has the conditions to be bound to the device to be activated. Therefore, when the cloud receives the binding request, it can directly bind the target device identifier with the previously verified target user identifier to establish a corresponding relationship between the target user identifier and the target device identifier.

[0038] In one example, after sending a binding request to the cloud, the cloud can also establish a correspondence between the target device identifier and the target user identifier based on the first library for storing temporary data. Since the correspondence between the target device identifier and the target user identifier has been stored in the first library when it is determined that the target user identifier has been verified, the cloud can determine the corresponding target user identifier from the first library based on the target device identifier after receiving the binding request, thereby establishing a correspondence between the target user identifier and the target device identifier.

[0039] In the embodiment of the present application, the activation terminal sends a binding request to the cloud in order to allow the cloud to directly establish a corresponding relationship between the verified target user identifier and the target device identifier, thereby treating the device to be activated as a bound device of the target user identifier, so that the user terminal can directly connect to the device to be activated based on Bluetooth without having to re-search and bind the device to be activated, and then issue corresponding functional instructions to the device to be activated.

[0040] In the above scheme, during the process of initiating an activation request, the activation terminal displays verification information and allows the user terminal to scan the verification information so that the cloud can verify whether the user identification corresponding to the user terminal meets the preset conditions. When the activation terminal receives the verification success information including the target activation code, it determines that the cloud has stored the correspondence between the verified target device identification and the target user identification. Therefore, after receiving the subsequent activation success information, the activation terminal directly initiates a binding request, so that the user terminal does not need to re-search for the device to be activated and bind it. The cloud can establish a binding relationship between the target device identification and the target user identification based on the corresponding relationship stored during verification, eliminating the step of users manually binding the device, greatly simplifying the process of binding the user identification to the device to be activated, and improving the convenience of binding and the user experience.

[0041] Based on the above embodiments, as an optional embodiment, the method of sending the binding request is as follows: Figure 3 The specific contents are as follows: S201, sending a verification information acquisition request to the device to be activated; the verification information acquisition request is used to request to obtain device verification information; S202, receiving device verification information sent by the device to be activated, and sending a device verification request carrying the device verification information to the cloud; S203: If the device verification success information is received, a binding request including the target device identifier is sent to the cloud.

[0042] In S201 of the embodiment of the present application, the device verification information is the information required to verify whether the device to be activated meets the binding conditions. After the activation terminal determines that the device to be activated is successfully activated, it is necessary to bind the device to be activated to the user identification so that the terminal corresponding to the user identification can operate the device to be activated. In order to ensure the legitimacy of the device to be activated, that is, to determine whether the device to be activated meets the binding conditions, the activation terminal will send a verification information acquisition request to the device to be activated to obtain the device verification information of the device to be activated for verification.

[0043] In S202 of the embodiment of the present application, the device verification request is used to request the cloud to verify whether the device verification information meets the binding conditions. In order to determine whether the device to be activated can be bound to the user identifier, the activation terminal sends a device verification request containing the device verification information of the device to be activated to the cloud, requesting the cloud to determine whether the device verification information meets the binding conditions.

[0044] In S203 of the embodiment of the present application, the device verification success information is sent after the cloud verifies that the device verification information meets the binding conditions. When the activated terminal receives the device verification success information sent by the cloud, it means that the cloud has determined that the device verification information meets the binding conditions. Therefore, a binding request containing the target device identifier can be sent to the cloud, requesting the cloud to bind the target device identifier with the target user identifier.

[0045] In an embodiment of the present application, the device verification information may be the triplet information of the device. The triplet information of the device is assigned when the device to be activated is registered in the cloud. The information successfully registered in the cloud is information that has been verified for legality. After the cloud assigns the triplet information to the device to be activated, it will also store the triplet information corresponding to the device to be activated, so that when the activation terminal sends a device verification request containing the triplet information to the cloud, the cloud compares the triplet information stored locally with the triplet information contained in the device verification request. If the triplet information is consistent, it is considered that the triplet information meets the binding conditions, and thus a verification success message is sent to the activation terminal.

[0046] In the above scheme, before sending a binding request, it is necessary to send a verification information acquisition request to the device to be activated to obtain the device verification information of the device to be activated, and then send a device verification request carrying the device verification information to the cloud to request the cloud to verify whether the device to be activated meets the binding verification conditions. If it meets the binding conditions, it means that the device to be activated is legal. The activation terminal will send a binding request to the cloud only after receiving the verification success information. Before sending a binding request to the cloud, the legitimacy of the device to be activated is ensured by sending a device verification request to prevent unauthorized devices from illegally obtaining user information and affecting user safety. At the same time, it reduces problems and failures caused by unauthorized devices, and improves the overall experience and satisfaction of users using smart devices.

[0047] Based on the above embodiments, as an optional embodiment, after sending a binding request to the cloud, receiving a binding success message sent by the cloud after establishing a correspondence between the target user identifier and the target device identifier; sending a binding success message to the device to be activated; in response to the device status change success message sent by the device to be activated, the activation terminal displays an activation success page.

[0048] In the embodiment of the present application, the binding success information is sent so that the device to be activated changes the device state to the binding state. When the device to be activated is in the binding state, the user terminal corresponding to the target user identifier has the authority to connect to the device to be activated.

[0049] In an embodiment of the present application, after the activation terminal determines that the device to be activated is successfully bound, a binding success message is sent to the device to be activated to instruct the device to be activated to change its own device status to a bound status. The device to be activated in the bound status can only establish a wireless communication connection with the target user identifier that establishes a binding relationship, that is, only the bound target user identifier has the authority to connect to the device to be activated, so that other terminals will not scan and connect to the device to be activated during the device scanning process.

[0050] In an embodiment of the present application, after the activation terminal sends a binding request to the cloud, it waits for the cloud to return a binding success message. After receiving the binding success message, it indicates that the cloud has established a correspondence between the target user identifier and the target device identifier, and the target user identifier has the authority to operate the device to be activated. Therefore, the activation terminal needs to send a binding success message to the device to be activated, informing the device to be activated that a correspondence has been established with the target user identifier, and instructing the device to be activated to change the device status to a bound status. When the device to be activated is in offline binding, it can only establish a wireless communication connection with the user terminal corresponding to the target user identifier, and cannot be searched and bound by other user terminals and the activation terminal.

[0051] In the embodiment of the present application, after the device to be activated changes the device status to the bound status, it sends information about successful device status change to the activation terminal. The activation terminal that receives the information about successful device status change displays an activation success page.

[0052] In the above scheme, after receiving the binding success information sent by the cloud, the binding success information is sent to the device to be activated, informing that the device to be activated has been bound to the target user ID, and instructing the device to be activated to change the device status to the binding status, so that the activation terminal will no longer scan the device to be activated when scanning the device, and it is also ensured that the device to be activated is only connected to the user terminal corresponding to the bound target user ID. This avoids the subsequent activation terminal activating other devices to be activated and affecting the accurate selection of the device to be activated.

[0053] Based on the above embodiments, as an optional embodiment, the target device information of the device to be activated and the confirmation information control are displayed, and the confirmation information control is used to confirm that the device information of the device to be activated is accurate; in response to the confirmation information control being triggered, the verification information is displayed; In an embodiment of the present application, after receiving the target device information of the device to be activated sent by the cloud, the activation terminal will display the target device information and confirmation information controls on a visual interface for the installer to confirm whether the currently interacting device to be activated and the device to be activated actually to be activated are the same device to be activated. When the devices to be activated are consistent, the installer triggers the confirmation information control, and the activation terminal detects that the confirmation information control is triggered, and determines that the current target device information is correct. Therefore, the verification information is displayed to instruct the user terminal to scan the verification information, so that the user terminal sends a verification request to the cloud to further execute the activation process.

[0054] In the embodiment of the present application, the target device information includes at least one of the following: The device model of the device to be activated; Product image of the device to be activated.

[0055] In an embodiment of the present application, the device model of the device to be activated is used to distinguish different models of the same type of devices to be activated. For example, the smart clothes drying machine is divided into a basic version and an advanced version, and the corresponding device models are NYJ100 and NYJ200 respectively; the product picture of the device to be activated refers to a picture showing the appearance of the device to be activated, and the target device information is used to help the installer confirm whether the device to be activated is consistent with the device currently being activated.

[0056] In the above scheme, the target device information returned by the cloud is received, and the target device information includes information related to the device to be activated, so that the installer can confirm the device to be activated through the displayed target device information, and after confirming that the target device information is correct, the verification information is displayed to instruct the user terminal to perform user verification, so as to avoid the problem that the actually activated device does not match the planned activated device.

[0057] Based on the above embodiments, as an optional embodiment, the method of sending the activation request is as follows: Figure 4 As shown, the specific process includes: S301, display activation controls; S302, in response to the activation control being triggered, displaying the target device identifier of the device to be activated and the scanning control; S303, in response to the scanning control being triggered, scanning each device within a preset range, and acquiring broadcast information of each scanned device; S304, determining at least one device whose device status is in an inactive state according to the broadcast information of each device; S305, determining a device to be activated from at least one device, and establishing a wireless communication connection with the device to be activated; S306, sending a query instruction to the device to be activated via a wireless communication connection; S307: If the device identifier is consistent with the target device identifier and the displayed confirmation device control is triggered, an activation request including the target device identifier is sent to the cloud.

[0058] In S301 of the embodiment of the present application, the activation control is used to confirm the start of the activation process. After the installer successfully installs the device to be activated and powers on and operates normally, the installer enters the activation page of the device through the activation terminal. The activation page displays the activation control, waiting for the installer to confirm whether to start the activation process.

[0059] In S302 of the embodiment of the present application, after the device to be activated detects that the activation control is triggered, the activation process of the device to be activated is confirmed. First, the target device identification of the device to be activated is displayed. Since the installation and activation tasks of the installer are all assigned by the system, the target device identification of the device to be activated will be displayed on the installation and activation task received by the activation terminal; while displaying the target device identification, a scanning control will also be displayed. The scanning control is used to confirm the scanning of devices within a preset range. Since the current activation terminal has not yet established a connection with the device to be activated, the installer can scan the devices that can be connected around by triggering the displayed scanning control.

[0060] In S303 of the embodiment of the present application, the activation terminal detects that the activation control is triggered, and starts scanning the devices within a preset range to obtain the broadcast information of each device.

[0061] In S304 of the embodiment of the present application, since the broadcast information indicates whether the corresponding device is in an activated state, that is, by scanning the broadcast information of each device, the devices in the activated state and the inactivated state within the preset range can be determined, and thus all devices with an inactivated state can be determined based on the broadcast information of each device.

[0062] In S305 of the embodiment of the present application, after the activation terminal determines all devices in the unactivated state according to the device status, the unactivated devices will be displayed on the visual interface. The installer determines the devices to be activated through the activation terminal, and after determining the devices to be activated, establishes a wireless communication connection with the devices to be activated, thereby realizing information interaction with the devices to be activated.

[0063] In S306 of the embodiment of the present application, after the activation terminal establishes a wireless communication connection with the device to be activated, it sends a query instruction to the device to be activated, and the query instruction is used to instruct the device to be activated to broadcast a preset sound and return the device identification of the device to be activated. That is, the activation terminal sends a query instruction to make the device to be activated make a sound, so that the installer can determine that the current device to be activated is consistent with the device that actually interacts with information, and the purpose of letting the device to be activated return the device identification is to ensure the consistency of the device to be activated.

[0064] In S307 of the embodiment of the present application, when the received device identification is consistent with the target device identification, it means that the currently interacting device to be activated is consistent with the device to be activated indicated on the installation activation task. At the same time, a confirmation device control will also be displayed on the visual interface. That is, after the installer determines that the device to be activated is correct according to the preset sound broadcast by the device to be activated, the installer confirms that the current device to be activated is accurate by triggering the confirmation device control. After the activation terminal detects that the confirmation device control is triggered, it sends an activation request to the cloud to request the cloud to send the target device information of the device to be activated.

[0065] In the above scheme, after the activation control is triggered, the target device identification of the device to be activated is displayed, and the activation terminal formally enters the activation process. First, the device status of the device is determined based on the devices within the preset range scanned, and the devices in the unactivated state are displayed. Then, the device to be activated is selected for wireless communication connection. In order to actually build a wireless communication connection that is consistent with the device to be activated, a query instruction is sent to instruct the connected device to be activated to broadcast a preset sound and return a device identification. When the device to be activated emits a preset sound and the device identification is consistent with the target device identification, it means that the device to be activated is consistent with the currently connected device. After confirming that the device control is triggered, an activation request is sent to the target device identification. The above scheme ensures that the currently connected device to be activated and the device to be activated that needs to be activated are consistent during the activation process.

[0066] The present application provides a device binding method, which is applied to the cloud. Figure 5 As shown, the method includes: S401, receiving an activation request including a device identification of a device to be activated, and sending target device information of the device to be activated to an activation terminal.

[0067] In an embodiment of the present application, when the cloud receives an activation request sent by the activation terminal, it first obtains the device identification of the device to be activated from the activation request, and then obtains the target device information of the device to be activated from the device library that stores the device identification and the corresponding device information based on the device identification. The target device information is information related to the device to be activated.

[0068] In an embodiment of the present application, during the production process of the devices to be activated, the device identification of each device to be activated will be determined based on the production quantity and the device model. The finished product burning stage will burn the device identification, activation code and triplet information to the mainboard of each device to be activated in turn. After the burning is successfully verified, the device information, activation code and triplet information corresponding to each target device identification will be stored in the cloud.

[0069] In the embodiment of the present application, the cloud sends the target device information to the activation terminal so that the activation terminal can confirm that the device to be activated is correct based on the target device information, and then the activation terminal displays the verification information on the visual interface. The verification information is displayed so that the user terminal responds to the scanned verification information and sends a verification request to the cloud.

[0070] In one example, after receiving the activation request sent by the activation terminal, the cloud determines the target device information such as the device model and product image of the device to be activated according to the device identifier, and sends the target device information to the activation terminal.

[0071] S402: Receive a verification request including a target user identifier sent by a user terminal.

[0072] In an embodiment of the present application, the verification request is sent after the user terminal scans the verification information. Therefore, after the user terminal scans the verification information, the cloud receives the verification request containing the user identification sent by the user terminal. After the cloud receives the verification request, it will verify whether it has the authority to activate the device to be activated based on the target user identification.

[0073] S403, verifying the target user identification included in the verification request, and if it is determined that the target user identification is successfully verified, determining the corresponding target activation code according to the target device identification, and sending verification success information including the target activation code to the activation terminal.

[0074] In the embodiment of the present application, if the cloud determines that the target user identifier meets the preset conditions, it means that the current target user identifier has the authority to activate the device to be activated, that is, the target user identifier is verified successfully, and the corresponding target activation code is determined according to the target device identifier, and the verification pass information containing the target activation code is sent to the activation terminal.

[0075] In the embodiment of the present application, since the verification of the target user identification is passed, it means that the device to be activated can be activated at present, so the corresponding target activation code is determined from the activation library according to the target device identification. Then, the verification passing information including the target activation code is sent to the activation terminal, so that the activation terminal can activate the device to be activated according to the target activation code.

[0076] In an embodiment of the present application, each device to be activated will have a unique corresponding activation code, and the activation library is used to store each device identification and the activation code corresponding to each device identification, so that when the device to be activated needs to be activated, the corresponding activation code can be obtained in time for activation.

[0077] In an embodiment of the present application, after determining that the target user identifier has passed the verification, the target user identifier and the target device can also be stored correspondingly in the first library. The information in the first library is only stored for a preset time period, that is, the information in the first library will be cleared after the preset time period is exceeded. Therefore, it is equivalent to establishing a short-term correspondence between the target user identifier and the target device identifier.

[0078] S404: Receive a binding request including a target device identifier sent by the activation terminal, and establish a corresponding relationship between the target user identifier and the target device identifier according to the aforementioned verified target user identifier.

[0079] In the embodiment of the present application, the binding request is used to request the cloud to bind the activation device corresponding to the target device identifier with the user identifier to be verified, so that the device to be activated can be operated by the user terminal corresponding to the user identifier.

[0080] In an embodiment of the present application, after the cloud receives the binding request, since it determines that the target user identifier has been verified when verifying the user identifier, the cloud has already recorded the target user identifier and the target device identifier. For example, the corresponding relationship between the target user identifier and the target device identifier is stored in the first library. Therefore, after the device to be activated is successfully activated, as long as the binding request sent by the activation terminal is received, the corresponding target user identifier can be directly determined according to the target device identifier, thereby constructing the corresponding relationship between the user identifier and the target device identifier, and completing the binding of the device to be activated and the user identifier.

[0081] In one example, after obtaining the binding request sent by the activation terminal, the cloud determines the corresponding target device identifier from the first library based on the target device identifier, and then obtains the bound device list of the target device identifier, which is used to record the device identifiers of the devices to which the target device identifier has been bound, and then adds the target device identifier to the bound device list of the target device identifier, thereby completing the binding of the device to be activated and the target user identifier.

[0082] In the above scheme, when the cloud receives the activation request, the target device information is returned to the activation terminal. The cloud receives the verification request sent by the user terminal indicated by the activation terminal through the verification information, and verifies the target user identifier in the verification request. When the target user identifier is verified, it means that the device to be activated can be activated at present. Therefore, the verification pass information and the target activation code are sent to the activation terminal, so that the activation terminal sends the activation code to the device to be activated for device activation. When the binding request is received, the target device of the device to be activated is bound to the aforementioned target user identifier. Since the correspondence between the target user identifier and the target device identifier has been temporarily stored before the activation, at this time, it is only necessary to determine the corresponding target user identifier according to the target device identifier to establish the binding relationship. By verifying the user identifier and passing the user verification, the correspondence between the device identifier and the user identifier is temporarily stored, so that after the activation is successful, the user terminal does not need to re-search the clothes drying machine and bind it, and the activated device can be automatically bound to the user name, eliminating the customer's subsequent steps of manually binding the device, thereby improving the convenience and user experience of use.

[0083] Based on the above embodiments, as an optional embodiment, a device verification request carrying device verification information sent by an activation terminal is received; if the device verification information meets the binding condition, a device verification success message is sent to the activation terminal; a binding request containing a target device identifier is received from the activation terminal; In the embodiment of the present application, the device verification information is obtained from the device to be activated after the activation terminal determines that the device to be activated has been successfully activated, and the binding request is sent after the activation terminal receives the device verification success information. That is to say, after determining that the device to be activated has been successfully activated, the activation terminal will obtain the device verification information from the device to be activated, and then send a device verification request containing the device verification information to the cloud, requesting to verify whether the device to be activated meets the binding conditions. Therefore, in the embodiment of the present application, when the cloud receives the device verification request containing the device verification information sent by the activation terminal, it is determined that the current device to be activated has been successfully activated, and it is necessary to verify whether the device to be activated meets the binding conditions based on the device verification information, thereby starting to judge whether the device verification information meets the binding conditions. If it meets the binding conditions, it means that the device to be activated can be bound, so the device verification success information is sent to the activation terminal. Since the activation terminal receives the device verification success information sent by the cloud and determines that the device to be activated can be bound, it will send a binding request to the cloud. Therefore, the cloud will receive the binding request sent by the activation terminal.

[0084] In one example, the device verification information may be the device's triplet information, and the binding condition may be that the cloud stores the triplet information of the device to be activated. The triplet information of the device to be activated is assigned when the device to be activated is registered in the cloud. All devices to be activated that are successfully registered in the cloud are legal. Therefore, when the cloud receives a device verification request containing the device triplet information, it determines whether the above-mentioned device triplet information is stored. If the above-mentioned device triplet information is stored, it is considered that the binding condition is met, and therefore, a verification success message is sent to the activation terminal.

[0085] In the above scheme, the device verification information is used to verify whether the device to be activated meets the binding conditions, thereby ensuring the legitimacy of the device to be activated and preventing unauthorized devices from binding to user identities and obtaining user information, which may affect user security.

[0086] Based on the above embodiments, as an optional embodiment, user information is obtained from a user database according to a target user identifier; the number of devices that the target user identifier has been authorized to activate is determined according to the user information; if the number of devices that the target user identifier has been authorized to activate is less than a preset number threshold, it is determined that the target user identifier satisfies the preset conditions.

[0087] In an embodiment of the present application, the user library is used to store user identifiers and user information corresponding to each user identifier. The user information may be information about devices that the user has authorized to activate. Based on the information about devices that the user has authorized to activate, the number of devices that the current target user identifier has authorized to activate can be determined. When the number of devices that the same user identifier has authorized to activate is too large, there may be loopholes in service quality and security. Therefore, the cloud ensures the service and security of users during the use of the device by limiting the number of devices that the user identifier has authorized to activate during the activation phase.

[0088] In an embodiment of the present application, when the number of devices that the target user identifier has been authorized to activate is greater than a preset number threshold, it indicates that the current user identifier does not have the authority to activate the device to be activated. Therefore, when the cloud determines that the number of devices that the target user identifier has been authorized to activate is less than a preset number threshold, it determines that the target user identifier meets the preset conditions and has the authority to activate the device to be activated, thereby obtaining the target activation code corresponding to the device to be activated, so that the activation terminal can continue to activate the device to be activated.

[0089] In the above scheme, user information is obtained from the user database according to the target user ID, so as to determine the number of devices currently authorized to be activated by the user ID. When the number of devices authorized to be activated by the user is less than the preset number, it means that the current user still has the authority to activate the devices to be activated. Therefore, it is determined that the target user meets the preset conditions. By limiting the number of devices authorized to be activated by the user ID during the activation phase, the service quality of each customer account can be managed more effectively and the risk of security vulnerabilities can be reduced.

[0090] In an embodiment of the present application, after the activation terminal receives the information that the device status has been successfully changed returned by the device to be activated, the activation terminal will also send an activation success message to the cloud. After the cloud receives the activation success message, it sends the activation success message to the user terminal, so that the user terminal jumps to the evaluation page to evaluate this installation and activation. After the user evaluation is completed, the successfully bound device can be loaded in the display device list. When the user enters the page of the corresponding successfully bound device, the nearby devices will be automatically scanned via Bluetooth and the corresponding devices will be connected, so that the user can realize local control of the device through the user terminal. For the first successful connection, a window will automatically pop up on the user terminal to prompt the network configuration operation, thereby realizing remote control.

[0091] refer to Figure 6 As shown, it exemplarily shows an interactive flow chart of a device binding method, the specific contents are as follows: S501, the activation terminal determines the target device identifier of the device to be activated; S502, the activation terminal sends an activation request including a target device identifier to the cloud; S503, the cloud determines the target device information corresponding to the target device identifier according to the target device identifier; S504, the cloud sends target device information to the activation terminal; S505. When the activation terminal determines that the target device information is correct, the activation terminal displays verification information; S506, the user terminal scans the verification information, jumps to display the verification interface, and logs in to the verification interface in response to the input target user identifier; S507, the user terminal sends a verification request including the target user identifier to the cloud; S508: The cloud determines that a preset condition is met according to the target user identifier, stores the target user identifier and the target device identifier in the first database accordingly, and determines a corresponding target activation code according to the target device identifier; S509, the cloud sends verification pass information including the target activation code to the activation terminal; S510, the activation terminal sends a target activation code to the device to be activated; S511, the device to be activated is activated according to the target activation code; S512, the device to be activated sends activation success information to the activation terminal; S513, the activation terminal sends a verification information acquisition request to the device to be activated; S514, the device to be activated sends device verification information to the activation terminal; S515, the activation terminal sends a device verification request including device verification information to the cloud; S516. The cloud determines whether the device to be activated meets the binding conditions based on the device verification information; S517, when the binding conditions are met, the cloud sends a device verification success message to the activation terminal; S518, the activation terminal sends a binding request including the target device identifier to the cloud; S519: The cloud determines the corresponding target user identifier from the first database according to the target device identifier, and establishes a corresponding relationship between the target user identifier and the target device identifier.

[0092] S520, the cloud returns binding success information to the activation terminal; S521, the activation terminal sends a binding success message to the device to be activated; S522, the device to be activated changes the device state to a binding state; S523, the device to be activated returns information that the device status has been successfully changed to the activation terminal; S524. The activation terminal displays an activation success page.

[0093] The present application embodiment provides an activation terminal, such as Figure 7 As shown, the activation terminal 70 may include: a display module 701, a first sending module 702 and a second sending module 703, wherein: The display module 701 is used to receive the target device information of the device to be activated sent by the cloud, and display the verification information, so that the user terminal responds to scanning the verification information and sends a verification request to the cloud; the target device information is sent after the cloud receives the activation request sent by the activation terminal containing the target device identifier of the device to be activated; The first sending module 702 is used to receive the verification information including the target activation code sent by the cloud, and send the target activation code to the device to be activated; the verification information is sent by the cloud after determining that the target user identifier included in the verification request has been verified, and the target activation code included in the verification information is determined by the cloud according to the target device identifier; The second sending module 703 is used to receive the verification information including the target activation code sent by the cloud, and send the target activation code to the device to be activated; the verification information is sent by the cloud after determining that the target user identifier included in the verification request has been verified, and the target activation code included in the verification information is determined by the cloud according to the target device identifier; The device of the embodiments of the present application can execute the method provided by the embodiments of the present application, and the implementation principles are similar. The actions performed by each module in the device of each embodiment of the present application correspond to the steps in the method of each embodiment of the present application. For the detailed functional description of each module of the device, please refer to the description in the corresponding method shown in the previous text, which will not be repeated here.

[0094] The present application embodiment provides an activation terminal, such as Figure 8 As shown, the cloud 80 may include: a first receiving module 801, a second receiving module 802, a determining module 803 and an establishing module 804, wherein: The first receiving module 801 is used to receive an activation request including a device identification of a device to be activated, and send target device information of the device to be activated to the activation terminal so that the activation terminal displays verification information; The second receiving module 802 is used to receive a verification request including a target user identifier sent by a user terminal, where the verification request is sent by the user terminal after scanning the verification information; The determination module 803 is used to verify the target user identification included in the verification request, and if it is determined that the target user identification is verified successfully, determine the corresponding target activation code according to the target device identification, and send verification success information including the target activation code to the activation terminal; The establishing module 804 is used to receive a binding request including a target device identifier sent by the activation terminal, and to establish a corresponding relationship between the target user identifier and the target device identifier according to the aforementioned verified target user identifier.

[0095] The device of the embodiments of the present application can execute the method provided by the embodiments of the present application, and the implementation principles are similar. The actions performed by each module in the device of each embodiment of the present application correspond to the steps in the method of each embodiment of the present application. For the detailed functional description of each module of the device, please refer to the description in the corresponding method shown in the previous text, which will not be repeated here.

[0096] In an embodiment of the present application, an electronic device (computer device / equipment / system) is provided, including a memory, a processor, and a computer program stored in the memory. The processor executes the above-mentioned computer program to implement the steps of the device binding method. Compared with the related art, the following can be achieved: By displaying verification information and allowing the user terminal to scan the verification information, the cloud can verify whether the user identification corresponding to the user terminal meets the preset conditions. When the activation terminal receives the verification success information including the target activation code, it determines that the cloud has recorded the target user identification that has passed the verification. Therefore, after receiving the activation success information subsequently, the activation terminal directly initiates a binding request, so that the user terminal does not need to re-search for the device to be activated and bind it. The cloud can establish a binding relationship between the target device identification and the target user identification based on the corresponding relationship stored during verification, eliminating the step of users manually binding devices, greatly simplifying the process of binding user identification to devices to be activated, and improving the convenience of binding and user experience.

[0097] In an alternative embodiment, an electronic device is provided, such as Fig. 9 As shown, Fig. 9 The electronic device 4000 shown includes: a processor 4001 and a memory 4003. The processor 4001 and the memory 4003 are connected, such as through a bus 4002. Optionally, the electronic device 4000 may also include a transceiver 4004, which may be used for data interaction between the electronic device and other electronic devices, such as data transmission and / or data reception. It should be noted that in actual applications, the transceiver 4004 is not limited to one, and the structure of the electronic device 4000 does not constitute a limitation on the embodiments of the present application.

[0098] Processor 4001 may be a CPU (Central Processing Unit), a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It may implement or execute various exemplary logic blocks, modules and circuits described in conjunction with the disclosure of this application. Processor 4001 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0099] The bus 4002 may include a path to transmit information between the above components. The bus 4002 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus. The bus 4002 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig. 9 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0100] The memory 4003 may be a ROM (Read Only Memory) or other types of static storage devices that can store static information and instructions, a RAM (Random Access Memory) or other types of dynamic storage devices that can store information and instructions, or an EEPROM (Electrically Erasable Programmable Read Only Memory), a CD-ROM (Compact Disc Read Only Memory) or other optical disk storage, optical disk storage (including compressed optical disk, laser disk, optical disk, digital versatile disk, Blu-ray disk, etc.), magnetic disk storage media, other magnetic storage devices, or any other medium that can be used to carry or store computer programs and can be read by a computer, without limitation herein.

[0101] The memory 4003 is used to store the computer program for executing the embodiment of the present application, and the execution is controlled by the processor 4001. The processor 4001 is used to execute the computer program stored in the memory 4003 to implement the steps shown in the above method embodiment.

[0102] Among them, the electronic equipment package may include but is not limited to mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Fig. 9 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0103] The embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps and corresponding contents of the aforementioned method embodiment can be implemented. Compared with the prior art, the following can be implemented: By displaying verification information and allowing the user terminal to scan the verification information, the cloud can verify whether the user identification corresponding to the user terminal meets the preset conditions. When the activation terminal receives the verification success information including the target activation code, it determines that the cloud has recorded the target user identification that has passed the verification. Therefore, after receiving the activation success information subsequently, the activation terminal directly initiates a binding request, so that the user terminal does not need to re-search for the device to be activated and bind it. The cloud can establish a binding relationship between the target device identification and the target user identification based on the corresponding relationship stored during verification, eliminating the step of users manually binding devices, greatly simplifying the process of binding user identification to devices to be activated, and improving the convenience of binding and user experience.

[0104] It should be noted that the computer-readable medium mentioned above in the present disclosure may be a computer-readable signal medium or a computer-readable medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In the present disclosure, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer readable signal media may also be any computer readable medium other than computer readable storage media, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer readable medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

[0105] The present application also provides a computer program product, including a computer program, which can implement the steps and corresponding contents of the above method embodiments when executed by a processor. Compared with the prior art, it can achieve: By displaying verification information and allowing the user terminal to scan the verification information, the cloud can verify whether the user identification corresponding to the user terminal meets the preset conditions. When the activation terminal receives the verification success information including the target activation code, it determines that the cloud has recorded the target user identification that has passed the verification. Therefore, after receiving the activation success information subsequently, the activation terminal directly initiates a binding request, so that the user terminal does not need to re-search for the device to be activated and bind it. The cloud can establish a binding relationship between the target device identification and the target user identification based on the corresponding relationship stored during verification, eliminating the step of users manually binding devices, greatly simplifying the process of binding user identification to devices to be activated, and improving the convenience of binding and user experience.

[0106] The terms "first", "second", "third", "fourth", "1", "2", etc. (if any) in the specification and claims of this application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the numbers used in this way can be interchanged where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than that shown or described in the drawings.

[0107] It should be understood that, although each operation step is indicated by arrows in the flowchart of the embodiment of the present application, the implementation order of these steps is not limited to the order indicated by the arrows. Unless clearly stated herein, in some implementation scenarios of the embodiment of the present application, the implementation steps in each flowchart can be performed in other orders according to demand. In addition, some or all of the steps in each flowchart may include multiple sub-steps or multiple stages based on actual implementation scenarios. Some or all of these sub-steps or stages may be executed at the same time, and each sub-step or stage in these sub-steps or stages may also be executed at different times respectively. In different scenarios of execution time, the execution order of these sub-steps or stages may be flexibly configured according to demand, and the embodiment of the present application does not limit this.

[0108] The above are only optional implementation methods for some implementation scenarios of the present application. It should be pointed out that for ordinary technicians in this technical field, without departing from the technical concept of the scheme of the present application, other similar implementation methods based on the technical ideas of the present application are also within the protection scope of the embodiments of the present application.

Claims

1. A device binding method, characterized in that: Applied to activating a terminal, the method comprises: receiving target device information of the device to be activated sent by the cloud, and displaying verification information, so that the user terminal sends a verification request to the cloud in response to scanning the verification information; the target device information is sent by the cloud after receiving the activation request sent by the activation terminal and including the target device identifier of the device to be activated; receiving verification information including a target activation code sent by the cloud, and sending the target activation code to the device to be activated; the verification information is sent by the cloud after determining that the target user identifier included in the verification request has been verified, and the target activation code included in the verification information is determined by the cloud according to the target device identifier; Receive activation success information sent by the device to be activated after successful activation according to the target activation code, and send a binding request including the target device identifier to the cloud, so that the cloud establishes a correspondence between the target user identifier and the target device identifier according to the target user identifier that has passed the verification.

2. The method according to claim 1, characterized in that The sending a binding request including a target device identifier to the cloud comprises: Sending a verification information acquisition request to the device to be activated; the verification information acquisition request is used to request to obtain device verification information; the device verification information is information required to verify whether the device to be activated meets the binding conditions; receiving device verification information sent by the device to be activated, and sending a device verification request carrying the device verification information to the cloud, wherein the device verification request is used to request the cloud to verify whether the device verification information meets the binding condition; If the device verification success information is received, a binding request including the target device identifier is sent to the cloud; the device verification success information is sent after the cloud verifies that the device verification information meets the binding conditions.

3. The method according to claim 1, characterized in that The method further comprises: Receiving binding success information sent by the cloud after establishing a correspondence between the target user identifier and the target device identifier; Sending the binding success information to the device to be activated, so that the device to be activated changes the device state to the binding state; when the device to be activated is in the binding state, the user terminal corresponding to the target user identifier has the authority to connect to the device to be activated; In response to the information sent by the device to be activated indicating that the device status has been successfully changed, the activation terminal displays an activation success page.

4. The method according to claim 1, characterized in that: The receiving target device information of the device to be activated sent by the cloud and displaying the verification information includes: Display the target device information of the device to be activated and a confirmation information control, wherein the confirmation information control is used to confirm that the device information of the device to be activated is accurate; In response to the confirmation information control being triggered, displaying the verification information; The target device information includes at least one of the following: The device model of the device to be activated; Product image of the device to be activated.

5. The method according to claim 1, characterized in that The receiving target device information of the device to be activated sent by the cloud also includes: Displaying an activation control, wherein the activation control is used to confirm the start of the activation process; In response to the activation control being triggered, displaying the target device identification of the device to be activated and a scanning control, wherein the scanning control is used to confirm scanning of devices within a preset range; In response to the scanning control being triggered, scanning each device within a preset range, and acquiring broadcast information of each scanned device; the broadcast information indicates whether the corresponding device is in an activated state; Determine at least one device whose device status is in an inactive state according to the broadcast information of each device; Determine a device to be activated from the at least one device, and establish a wireless communication connection with the device to be activated; Sending a query instruction to the device to be activated via the wireless communication connection; the query instruction is used to instruct the device to be activated to broadcast a preset sound and return a device identification; If the device identifier is consistent with the target device identifier and the displayed confirmation device control is triggered, an activation request including the target device identifier is sent to the cloud, wherein the activation request is used to request the cloud to send the target device information of the device to be activated; the confirmation device control is used to confirm that the device to be activated is accurate.

6. A device binding method, characterized in that: Applied to the cloud, the method includes: receiving an activation request including a device identification of a device to be activated, and sending target device information of the device to be activated to an activation terminal so that the activation terminal displays verification information; Receiving a verification request including a target user identifier sent by a user terminal, wherein the verification request is sent by the user terminal after scanning the verification information; Verifying the target user identifier included in the verification request, and if it is determined that the target user identifier is verified successfully, determining the corresponding target activation code according to the target device identifier, and sending verification success information including the target activation code to the activation terminal; A binding request including a target device identifier is received from the activation terminal, and a corresponding relationship between the target user identifier and the target device identifier is established according to the target user identifier that has passed the verification.

7. The method according to claim 6, characterized in that The receiving a binding request including a target device identifier sent by the activation terminal includes: receiving a device verification request carrying device verification information sent by the activation terminal; the device verification information is obtained from the device to be activated after the activation terminal determines that the device to be activated is successfully activated; If the device verification information meets the binding condition, sending device verification success information to the activation terminal; A binding request including a target device identifier is received from the activation terminal; the binding request is sent by the activation terminal after receiving device verification success information.

8. The method according to claim 6, characterized in that The determining, according to the target user identifier, that a preset condition is satisfied includes: Obtaining user information from a user database according to the target user identifier; the user database is used to store user identifiers and user information corresponding to each user identifier; Determine the number of devices that the target user identifier has authorized to activate according to the user information; If the number of devices that the target user identification has authorized to activate is less than a preset number threshold, it is determined that the target user identification satisfies a preset condition.

9. An electronic device comprising a memory, a processor and a computer program stored in the memory, characterized in that: The processor executes the computer program to implement the steps of the method according to any one of claims 1 to 8.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 8 are implemented.

Images