Device registration method, hub device, and apparatus

Abstract

The application is suitable for the field of Internet of Things, and provides a device registration method, a hub device and an apparatus. In the device registration method provided by the application, the hub device can register a target device to the hub device with the assistance of a first user device. In addition, the hub device can register the hub device to a server with the assistance of a second user device. Then, the hub device can automatically register the registered devices (i.e. the target devices registered to the hub device) to the server. That is to say, after the first user device registers each registered device to the hub device in advance, the second user device only needs to register the hub device to the server, and the hub device can automatically register each registered device to the server, without the need for the second user device to register each target device to the server one by one, thereby greatly reducing the operations that a user using the second user device needs to perform, and having strong ease of use and practicality.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of Internet of Things, and in particular to a device registration method, a hub device and an apparatus. BACKGROUND

[0002] In an account-based smart home solution, a smart home device can register under a specified user account (or establish a binding relationship with the specified user account) by communicating with a smart home platform in the cloud. Thus, a user can conveniently use a user device (such as a mobile phone, a tablet computer, etc.) logged into the specified user account to manage multiple smart home devices under the specified user account.

[0003] However, in some scenarios, a smart home device cannot communicate with a smart home platform in the cloud, and / or it is not determined to which user account it should be registered. At this time, the installation and maintenance personnel responsible for installing the smart home device cannot help the household complete the registration process, and the household needs to register each smart home device under the specified user account after the smart home device can communicate with the smart home platform in the cloud and the specified user account is determined, which is cumbersome and has a poor user experience. SUMMARY

[0004] Embodiments of the present application provide a device registration method, a hub device and an apparatus, which can solve the problem that existing smart home solutions require the household to register each smart home device.

[0005] In a first aspect, embodiments of the present application provide a device registration method applied to a hub device, comprising:

[0006] In response to a first registration request sent by a first user device, sending a first registration code to the first user device;

[0007] After receiving the first registration code sent by a target device, registering the target device to the hub device;

[0008] Receiving a second registration code sent by a second user device; wherein the second user device and the first user device are the same user device or different user devices;

[0009] According to the second registration code, registering the hub device to a server;

[0010] After the hub device is registered to the server, registering a registered device to the server; wherein the registered device includes the target device that has been registered to the hub device.

[0011] It should be noted that in the scenario that the smart home device cannot communicate with the server, and / or the user has not determined which user account the smart home device should be registered under, if the user wants to manage the smart home devices in an overall manner, the user can register the smart home devices to the hub device as an edge server.

[0012] Specifically, the user can perform a device registration operation on the first user device. In response to the device registration operation of the user, the first user device can determine a target device to be registered, and send a first registration request to the hub device.

[0013] The hub device can send a first registration code to the first user device in response to the first registration request.

[0014] The first user device can forward the first registration code to the target device after receiving the first registration code.

[0015] The target device can send the first registration code to the hub device after receiving the first registration code forwarded by the first user device.

[0016] The hub device can register the target device to the hub device after receiving the first registration code sent by the target device.

[0017] The process of registering the target device to the hub device by the first user device can be understood as the process of granting the operation permission of the target device to the hub device by the first user device. The registration of the target device to the hub device by the hub device can be understood as the registration of the operation permission of the target device on the hub device.

[0018] Therefore, after the first user device assists the hub device to register the target devices to the hub device, the hub device can obtain the operation permission of the registered devices, and the user can manage the registered devices in an overall manner through the hub device.

[0019] Exemplarily, in the front-loading scenario (i.e., the application scenario that some smart home devices are installed in the decoration stage before the house is delivered to the occupant), the home area has not been connected to the Internet line, and the maintenance personnel also cannot know the user account of the occupant. In this case, the maintenance personnel can use the above method to register the smart home devices to the hub device using their own user device.

[0020] Then, the maintenance personnel or other users can manage the smart home devices registered to the hub device in an overall manner through the hub device.

[0021] In addition, after the smart home device can communicate with the server and the specified user account is determined, the user can want to register the hub device and the registered device on the server. The above-mentioned server can be understood as a smart home platform in the cloud.

[0022] At this time, the user can perform a device delivery operation on the second user device logged in the first user account. The second user device can send a second registration request to the server in response to the device delivery operation of the user.

[0023] The server can send a second registration code to the second user device after receiving the second registration request.

[0024] The second user device forwards the second registration code to the hub device after receiving the second registration code.

[0025] The hub device can send the second registration code to the server after receiving the second registration code.

[0026] The server can register the hub device to the server after receiving the second registration code sent by the hub device.

[0027] After the hub device is registered to the server, the hub device can send a third registration request to the server to register the registered device to the server through the third registration request.

[0028] The hub device registers the hub device and the registered device to the server can be understood as that the hub device registers the operation permissions of the hub device and the registered device under the first user account of the server. The first user account is the user account currently logged in by the second user device.

[0029] After the hub device and the registered device are registered to the server, the first user account has the operation permissions of the hub device and the registered device, and the second user device or other user devices logged in the first user account can control the hub device and the registered device through the first user account.

[0030] The above-mentioned first user device and second user device can be the same user device or different user devices.

[0031] When the first user device and the second user device are different user devices, the user using the second user device only needs to register the hub device on the server, and the hub device can automatically register the registered device on the server, without the user using the second user device needing to register each target device on the server one by one, greatly reducing the operations needed to be performed by the user, and effectively improving the user experience, having strong ease of use and practicality.

[0032] Exemplarily, in the front-loaded scenario, the first user device can be a user device of a maintenance personnel, and the second user device can be a user device of a householder.

[0033] Before the house is delivered, the maintenance personnel can use the first user device to help the householder register the various smart home devices loaded in the front to the hub device.

[0034] After the house is delivered, the householder can use the second user device of his own to register the hub device to the server.

[0035] After the hub device is registered to the server, the hub device can automatically register the registered devices to the server, without the householder registering each registered device one by one, greatly reducing the workload of the householder, thereby effectively improving the use experience of the householder.

[0036] In a possible implementation of the first aspect, the method further includes:

[0037] After the state recovery instruction is acquired, the server is instructed to cancel the registration relationship between the hub device and the server, and / or the registration relationship between the registered device and the server.

[0038] It should be noted that when the hub device registers the hub device and the registered device to the server, the server binds the hub device and the registered device to the first user account.

[0039] Therefore, the registration relationship between the hub device and the server can be understood as the binding relationship between the hub device and the first user account, and the registration relationship between the registered device and the server can be understood as the binding relationship between the registered device and the first user account.

[0040] When the user wants to cancel the registration relationship between the hub device and / or the registered device and the server, the user device can directly operate the hub device to trigger the state recovery instruction, or the user can also send the state recovery instruction to the hub device through the user device of his own.

[0041] After the hub device acquires the state recovery instruction, the hub device can instruct the server to cancel the registration relationship between the hub device and the server, and / or the registration relationship between the registered device and the server.

[0042] In a possible implementation of the first aspect, the instruction to the server to cancel the registration relationship between the hub device and the server, and / or the registration relationship between the registered device and the server includes:

[0043] A first unbinding instruction is sent to the server, and the first unbinding instruction is used to instruct the server to cancel the registration relationship between the registered device and the server.

[0044] After the registration relationship between the server and the registration device is released, a second unbinding instruction is sent to the server, where the second unbinding instruction is used to instruct the server to release the registration relationship between the hub device and the server.

[0045] It should be noted that, in addition to being able to proxy the registration device to register, the hub device can also proxy the registration device to release the registration relationship.

[0046] After the hub device obtains the state recovery instruction, the hub device can send a first unbinding instruction to the server.

[0047] After the server receives the first unbinding instruction, the server can release the registration relationship between the registration device and the server.

[0048] After the registration relationship between the registration device and the server is released, the hub device can send a second unbinding instruction to the server.

[0049] After the server receives the second unbinding instruction, the server can release the registration relationship between the hub device and the server.

[0050] That is, when the user wants to release the registration relationship between each registration device and the server, the user only needs to issue a state recovery instruction to the hub device, and the hub device can automatically release the registration relationship between the hub device and the registration device and the server, without the user needing to release the registration relationship between the hub device and the registration device and the server one by one, greatly reducing the operations that the user needs to perform and effectively improving the user experience.

[0051] In a possible implementation manner of the first aspect, after the first unbinding instruction is sent to the server, the method further includes:

[0052] The registration relationship between the hub device and the registration device is restored.

[0053] It should be noted that, in the process of registering the target device to the hub device, the hub device is not set with a user account. Therefore, after the target device is registered to the hub device, the registration relationship between the hub device and the registration device (i.e., the target device that has been registered to the hub device) can be understood as a master-slave relationship between the hub device and the registration device, where the hub device is the master device and the registration device is the slave device of the hub device, and the hub device has the operation permission of the registration device.

[0054] In some embodiments, the registration device can only maintain one registration relationship.

[0055] In this scenario, when the registration device is registered to the server, the registration relationship between the hub device and the registration device is released.

[0056] Therefore, the hub device can restore the registration relationship between the hub device and the registered device after the registration relationship between the registered device and the server is released.

[0057] Then, the user can conveniently register the hub device and the registered device to another user account of the server as a whole through the above device registration method, reduce the user's operation of re-registering the hub device and the registered device, and improve the user's use experience.

[0058] For example, when a house owner wants to rent the house to a tenant, the house owner needs to transfer the operation authority of the hub device and the registered device to the tenant.

[0059] At this time, the house owner can issue a state recovery instruction to the hub device. The hub device can release the registration relationship between the registered device and the hub device and the server according to the state recovery instruction, and restore the registration relationship between the hub device and the registered device.

[0060] After that, the tenant can use his own user device to register the hub device on the server, and bind the hub device to the user account of the tenant.

[0061] After the hub device is registered to the user account of the tenant, the hub device can automatically register the registered device to the user account of the tenant.

[0062] That is to say, through the above method, the house owner and the tenant can conveniently migrate the operation authority of the hub device and the registered device to another user account as a whole, without the tenant registering the hub device and the registered device one by one, greatly reducing the operation of the tenant and improving the use experience of the tenant.

[0063] In a possible implementation manner of the first aspect, after the target device is registered to the hub device, the method further includes:

[0064] Receiving control information sent by a third user device, the control information including a device identifier of a registered device to be controlled and a control instruction;

[0065] Forwarding the control instruction to the registered device corresponding to the device identifier.

[0066] It should be noted that after the registered device is registered to the hub device, the user can directly send control information to the hub device through his own user device, and control each registered device through the hub device.

[0067] At this time, the user can perform a control operation on the third user device. The third user device can determine the registered device to be controlled and the control instruction in response to the control operation. The control instruction is used to instruct the registered device to be controlled to perform the operation specified by the user.

[0068] Then, the third user device can send control information to the hub device, the control information can include the device identification of the registered device to be controlled and the control instruction.

[0069] After the hub device receives the control information, the hub device can forward the control instruction to the registered device corresponding to the device identification.

[0070] After the registered device to be controlled receives the control instruction, the registered device to be controlled can execute the operation corresponding to the control instruction.

[0071] In a possible implementation of the first aspect, after the target device is registered to the hub device, the method further includes:

[0072] In response to the control operation of the user, the registered device to be controlled and the control instruction are determined.

[0073] The control instruction is sent to the registered device to be controlled.

[0074] It should be noted that after the registered device is registered to the hub device, the user can directly control each registered device through the hub device.

[0075] At this time, the user can directly perform a control operation on the hub device. The hub device can determine the registered device to be controlled and the control instruction in response to the control operation.

[0076] Then, the hub device can send the control instruction to the registered device to be controlled.

[0077] After the registered device to be controlled receives the control instruction, the registered device to be controlled can execute the operation corresponding to the control instruction.

[0078] In a second aspect, an embodiment of the present application provides a device registration method, the method includes:

[0079] With the assistance of the first user device, the hub device registers a target device to the hub device.

[0080] With the assistance of the second user device, the hub device registers the hub device to a server; wherein the second user device and the first user device are the same user device or different user devices.

[0081] After the hub device registers the hub device to the server, the hub device registers a registered device to the server; wherein the registered device includes the target device that has been registered to the hub device.

[0082] It should be noted that in the case that the smart home device cannot communicate with the server, and / or the user has not determined which user account the smart home device should be registered under, if the user wants to manage the smart home devices collectively, the user can register the smart home devices to the hub device as an edge server.

[0083] Specifically, the hub device can register the target device to the hub device with the assistance of the first user device.

[0084] In addition, the hub device can register the hub device to the server with the assistance of the second user device.

[0085] After the hub device is registered to the server, the hub device can register the registered device to the server on behalf of the registered device.

[0086] The first user device and the second user device described above can be the same user device or different user devices.

[0087] When the first user device and the second user device are different user devices, the user using the second user device only needs to register the hub device to the server, and the hub device can automatically register the registered device to the server, without the user using the second user device having to register each target device to the server one by one, greatly reducing the operations the user needs to perform, and effectively improving the user's experience, having strong ease of use and practicality.

[0088] In a possible implementation of the second aspect, the method further includes:

[0089] After obtaining the state recovery instruction, the hub device instructs the server to cancel the registration relationship between the hub device and the server, and / or the registration relationship between the registered device and the server.

[0090] It should be noted that when the user wants to cancel the registration relationship between the hub device and / or the registered device and the server, the user device can directly operate the hub device to trigger the state recovery instruction, or the user can also send the state recovery instruction to the hub device through the user's own user device.

[0091] After the hub device obtains the state recovery instruction, the hub device can instruct the server to cancel the registration relationship between the hub device and the server, and / or the registration relationship between the registered device and the server.

[0092] In a possible implementation of the second aspect, the hub device registers the target device to the hub device with the assistance of the first user device, specifically including:

[0093] The first user device determines the target device to be registered in response to a device registration operation of a user, and sends a first registration request to the hub device;

[0094] The hub device sends a first registration code to the first user device in response to the first registration request, and the first user device sends the first registration code to the target device.

[0095] The target device sends the first registration code to the hub device, and the hub device registers the target device in response to receiving the first registration code.

[0096] It should be noted that in the process of registering the target device to the hub device, the user can perform a device registration operation on the first user device. In response to the device registration operation of the user, the first user device can determine the target device to be registered, and send a first registration request to the hub device.

[0097] The hub device can send a first registration code to the first user device in response to the first registration request.

[0098] The first user device can forward the first registration code to the target device after receiving the first registration code.

[0099] The target device can send the first registration code to the hub device after receiving the first registration code forwarded by the first user device.

[0100] The hub device can register the target device to the hub device after receiving the first registration code sent by the target device.

[0101] The process of registering the target device to the hub device by the first user device can be understood as the process of granting the operation permission of the target device to the hub device by the first user device. The process of registering the target device to the hub device by the hub device can be understood as the process of registering the operation permission of the target device on the hub device.

[0102] Therefore, after the first user device assists the hub device to register each target device to the hub device, the hub device can obtain the operation permission of each registered device, and the user can manage each registered device through the hub device.

[0103] For example, in the front-end scenario (application scenario of installing some smart home devices in the decoration stage before the house is delivered to the residents), the home area has not been connected to the Internet line, and the maintenance personnel also cannot know the user account of the residents. In this scenario, the maintenance personnel can use their own user device to register each smart home device to the hub device by using the above method.

[0104] After that, the installation and maintenance personnel or other users can manage all the smart home devices registered to the hub device through the hub device.

[0105] In a possible implementation of the second aspect, the hub device registers the hub device to the server with the assistance of the second user device, specifically including:

[0106] The second user device sends a second registration request to the server in response to a device delivery operation of a user;

[0107] The server sends a second registration code to the second user device in response to the second registration request, and the second user device sends the second registration code to the hub device;

[0108] The hub device registers the hub device to the server in response to receiving the second registration code.

[0109] It should be noted that in the process of registering the hub device to the server, the user can perform a device delivery operation on the second user device logged in the first user account. The second user device can send a second registration request to the server in response to the device delivery operation of the user.

[0110] The server can send a second registration code to the second user device after receiving the second registration request.

[0111] The second user device forwards the second registration code to the hub device after receiving the second registration code.

[0112] The hub device can send the second registration code to the server after receiving the second registration code.

[0113] The server can register the hub device to the server after receiving the second registration code sent by the hub device.

[0114] In a possible implementation of the second aspect, after obtaining the state recovery instruction, the hub device instructs the server to cancel the registration relationship between the hub device and the server, and / or the registration relationship between the registered device and the server, specifically including:

[0115] The hub device sends a first unbinding instruction to the server after obtaining the state recovery instruction.

[0116] The server cancels the registration relationship between the registered device and the server in response to the first unbinding instruction.

[0117] After canceling the registration relationship between the registered device and the server, the hub device sends a second unbinding instruction to the server.

[0118] In response to the second unbinding instruction, the server unbinds the hub device from the server.

[0119] It should be noted that the hub device can not only proxy the registration device to register, but also proxy the registration device to unbind.

[0120] After the hub device obtains the state recovery instruction, the hub device can send a first unbinding instruction to the server.

[0121] After the server receives the first unbinding instruction, the server can unbind the registration device from the server.

[0122] After the registration device is unbound from the server, the hub device can send a second unbinding instruction to the server.

[0123] After the server receives the second unbinding instruction, the server can unbind the hub device from the server.

[0124] That is, when the user wants to unbind the registration device from the server, the user only needs to issue a state recovery instruction to the hub device, and the hub device can automatically unbind the hub device and the registration device from the server, without the user needing to unbind the hub device and the registration device from the server one by one, greatly reducing the operations that the user needs to perform, and effectively improving the user experience.

[0125] In a possible implementation of the second aspect, after the first unbinding instruction is sent to the server, the method further includes:

[0126] The hub device restores the registration relationship between the hub device and the registration device.

[0127] It should be noted that in some embodiments, the registration device can only maintain one registration relationship.

[0128] In this scenario, when the registration device registers with the server, the registration relationship between the hub device and the registration device is unbound.

[0129] Therefore, the hub device can restore the registration relationship between the hub device and the registration device after the registration device is unbound from the server.

[0130] Then, the user can conveniently register the hub device and the registration device to another user account of the server through the above device registration method, reduce the operation of the user to re-register the hub device and the registration device, and improve the user experience.

[0131] In a possible implementation of the second aspect, after the hub device registers the target device to the hub device, the method further includes:

[0132] The third user device determines the registered device to be controlled and a control instruction in response to a control operation of a user;

[0133] The third user device sends control information to the hub device, where the control information includes a device identifier of the registered device to be controlled and the control instruction;

[0134] In response to receiving the control information, the hub device forwards the control instruction to the registered device corresponding to the device identifier.

[0135] It should be noted that, after the registered devices are registered to the hub device, the user can directly send control information to the hub device through the user device of the user, and control the registered devices through the hub device.

[0136] In another possible implementation of the second aspect, after the hub device registers the target device to the hub device, the method further includes:

[0137] The hub device determines the registered device to be controlled and a control instruction in response to a control operation of a user;

[0138] The hub device sends the control instruction to the registered device to be controlled.

[0139] It should be noted that, after the registered devices are registered to the hub device, the user can also directly perform a control operation on the hub device, and control the registered devices through the hub device.

[0140] In a third aspect, an embodiment of the present application provides a device registration apparatus applied to a hub device, and includes:

[0141] A first sending module configured to send a first registration code to a first user device in response to a first registration request sent by the first user device;

[0142] A first registration module configured to register a target device to the hub device after receiving the first registration code sent by the target device;

[0143] A second receiving module configured to receive a second registration code sent by a second user device; where the second user device and the first user device are the same user device or different user devices;

[0144] A second registration module configured to register the hub device to a server according to the second registration code;

[0145] The third registration module is configured to register a registration device to the server after the hub device is registered to the server, wherein the registration device comprises the target device that has been registered to the hub device.

[0146] In a possible implementation of the third aspect, the apparatus further includes:

[0147] The registration cancellation module is configured to instruct the server to cancel the registration relationship between the hub device and the server and / or the registration relationship between the registration device and the server after the state recovery instruction is acquired.

[0148] In a possible implementation of the third aspect, the registration cancellation module includes:

[0149] The first unbinding sub-module is configured to send a first unbinding instruction to the server, wherein the first unbinding instruction is used to instruct the server to cancel the registration relationship between the registration device and the server.

[0150] The second unbinding sub-module is configured to send a second unbinding instruction to the server after the registration relationship between the registration device and the server is cancelled, wherein the second unbinding instruction is used to instruct the server to cancel the registration relationship between the hub device and the server.

[0151] In a possible implementation of the third aspect, the apparatus further includes:

[0152] The registration recovery module is configured to recover the registration relationship between the hub device and the registration device.

[0153] In a possible implementation of the third aspect, the apparatus further includes:

[0154] The control receiving module is configured to receive control information sent by a third user device, wherein the control information comprises a device identifier of a registration device to be controlled and a control instruction.

[0155] The relay control module is configured to forward the control instruction to the registration device corresponding to the device identifier.

[0156] In another possible implementation of the third aspect, the apparatus further includes:

[0157] The control response module is configured to determine the registration device to be controlled and the control instruction in response to a control operation of a user.

[0158] The direct control module is configured to send the control instruction to the registration device to be controlled.

[0159] In a fourth aspect, an embodiment of the present application provides a device registration system, the system comprising a hub device, a first user device, a second user device and a target device, the hub device being configured to perform:

[0160] registering the target device to the hub device with assistance of the first user device;

[0161] registering the hub device to a server with assistance of the second user device; wherein the second user device is the same user device as the first user device or is a different user device;

[0162] after the hub device registers the hub device to the server, registering a registered device to the server; wherein the registered device comprises the target device that has been registered to the hub device.

[0163] In a possible implementation of the fourth aspect, the hub device is further configured to perform:

[0164] after obtaining a state recovery instruction, instructing the server to cancel a registration relationship between the hub device and the server, and / or a registration relationship between the registered device and the server.

[0165] In a possible implementation of the fourth aspect, in the process of registering the target device to the hub device with assistance of the first user device performed by the hub device:

[0166] the first user device is configured to determine the target device to be registered in response to a device registration operation of a user, and send a first registration request to the hub device;

[0167] the hub device is configured to send a first registration code to the first user device in response to the first registration request;

[0168] the first user device is further configured to send the first registration code to the target device;

[0169] the target device is configured to send the first registration code to the hub device;

[0170] the hub device is further configured to register the target device to the hub device in response to receiving the first registration code.

[0171] In a possible implementation of the fourth aspect, in the process of registering the hub device to the server with assistance of the second user device performed by the hub device:

[0172] the second user device is configured to send a second registration request to the server in response to a device delivery operation of a user;

[0173] The server is configured to send a second registration code to the second user equipment in response to the second registration request;

[0174] The second user equipment is further configured to send the second registration code to the central device;

[0175] The central device is configured to register itself with the server in response to receiving the second registration code.

[0176] In one possible implementation of the fourth aspect, during the process of the central device instructing the server to release the registration relationship between the central device and the server after receiving the state recovery instruction, and / or during the registration relationship between the registered device and the server:

[0177] The central device is used to send a first unbinding instruction to the server after receiving the status recovery instruction;

[0178] The server is configured to, in response to the first unbinding instruction, terminate the registration relationship between the registered device and the server;

[0179] The central device is also used to send a second unbinding command to the server after the registration relationship between the registration device and the server is terminated;

[0180] The server is also configured to, in response to the second unbinding command, remove the registration relationship between the central device and the server.

[0181] In one possible implementation of the fourth aspect, the central device is further configured to restore the registration relationship between the central device and the registration device.

[0182] In one possible implementation of the fourth aspect, the system further includes a third user equipment;

[0183] The third user equipment is used to determine the registered device to be controlled and the control command in response to the user's control operation;

[0184] The third user equipment is also used to send control information to the central equipment, the control information including the device identifier of the registered device to be controlled and the control command;

[0185] The central device is also configured to, in response to receiving the control information, forward the control command to the registered device corresponding to the device identifier.

[0186] In one possible implementation of the fourth aspect, the central device is further configured to perform:

[0187] determining a registered device to be controlled and a control instruction in response to a control operation of a user;

[0188] sending the control instruction to the registered device to be controlled.

[0189] In a fifth aspect, an embodiment of the present application provides a hub device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, the hub device being configured to implement the method in any of the possible implementation manners of the first aspect when the computer program is executed.

[0190] In a sixth aspect, an embodiment of the present application provides a computer readable storage medium configured to store a computer program, wherein the computer program is executable by a processor to implement the method in any of the possible implementation manners of the first aspect.

[0191] In a seventh aspect, an embodiment of the present application provides a computer program product configured to, when running on a hub device, cause the hub device to implement the method in any of the possible implementation manners of the first aspect.

[0192] In an eighth aspect, an embodiment of the present application provides a chip system, including a memory and a processor, the processor being configured to execute a computer program stored in the memory to implement the method in any of the possible implementation manners of the first aspect.

[0193] Compared with the prior art, the embodiments of the present application have the following beneficial effects:

[0194] In the device registration method of the present application, the hub device can register the target device to the hub device with the assistance of the first user device. And the hub device can register the hub device to the server with the assistance of the second user device. After the hub device is registered to the server, the hub device can automatically register the registered device (i.e. the target device registered to the hub device) to the server on behalf of the registered device.

[0195] That is to say, after the first user device registers the registered device to the hub device, the second user device only needs to register the hub device to the server, and the hub device can automatically register the registered device to the server, without the need for the second user device to register each target device to the server one by one, greatly reducing the operations that the user using the second user device needs to perform, and effectively improving the user's use experience, having strong ease of use and practicality. BRIEF DESCRIPTION OF DRAWINGS

[0196] Figure 1A system architecture diagram of a device registration system provided for an embodiment of the present application;

[0197] Figure 2 A structural schematic diagram of an electronic device provided for an embodiment of the present application;

[0198] Figure 3 A scene schematic diagram provided for an embodiment of the present application;

[0199] Figure 4 Another scene schematic diagram provided for an embodiment of the present application;

[0200] Figure 5 A system architecture diagram of another device registration system provided for an embodiment of the present application;

[0201] Figure 6 A device interaction diagram provided for an embodiment of the present application;

[0202] Figure 7 Another scene schematic diagram provided for an embodiment of the present application;

[0203] Figure 8 Another scene schematic diagram provided for an embodiment of the present application;

[0204] Figure 9 Another scene schematic diagram provided for an embodiment of the present application;

[0205] Figure 10 Another scene schematic diagram provided for an embodiment of the present application;

[0206] Figure 11 Another scene schematic diagram provided for an embodiment of the present application;

[0207] Figure 12 Another scene schematic diagram provided for an embodiment of the present application;

[0208] Figure 13 Another scene schematic diagram provided for an embodiment of the present application;

[0209] Figure 14 A system architecture diagram of another device registration system provided for an embodiment of the present application;

[0210] Figure 15 Another scene schematic diagram provided for an embodiment of the present application;

[0211] Figure 16 Another device interaction diagram provided for an embodiment of the present application;

[0212] Figure 17 Another scene schematic diagram provided for an embodiment of the present application;

[0213] Figure 18 This is another scenario illustration provided for an embodiment of this application;

[0214] Figure 19 Another device interaction diagram provided for an embodiment of this application;

[0215] Figure 20 This is another scenario illustration provided for an embodiment of this application;

[0216] Figure 21 A schematic flowchart illustrating a device registration method provided in an embodiment of this application;

[0217] Figure 22 A schematic flowchart illustrating another device registration method provided in this application embodiment;

[0218] Figure 23 This is a schematic diagram of the structure of a device registration apparatus provided in an embodiment of this application;

[0219] Figure 24 This is a system architecture diagram of another device registration system provided in an embodiment of this application. Detailed Implementation

[0220] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods have been omitted so as not to obscure the description of this application with unnecessary detail.

[0221] It should be understood that, when used in this application specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or a collection thereof.

[0222] It should also be understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0223] As used in the specification and the appended claims, the term “if’ can be interpreted as meaning “when” or “upon” or “in response to determining” or “in response to detecting” depending on the context. Similarly, the phrase “if it is determined” or “if [the described condition or event] is detected” can be interpreted as meaning “upon determining” or “in response to determining” or “upon detecting [the described condition or event]” or “in response to detecting [the described condition or event]” depending on the context.

[0224] In addition, in the description of the present application and the appended claims, the terms “first”, “second”, “third”, etc. are used only to distinguish descriptions, and cannot be understood as indicating or implying relative importance.

[0225] Reference in the specification to “one embodiment” or “some embodiments” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the application. The appearances of the phrase “in one embodiment” or “in some embodiments” in various places in the specification are not necessarily all referring to the same embodiment, although it can. The terms “including,” “containing,” “having,” and variations thereof are meant to encompass the terms “including but not limited to” unless otherwise indicated.

[0226] In the current smart home solution, many smart home devices support registration functions. These smart home devices can interact with the cloud-based smart home platform in a networked state, and register under a designated user account.

[0227] At this time, if the user device (such as a mobile phone, tablet computer, etc.) is logged into the designated user account, the user can manage the multiple smart home devices under the designated user account through the user device.

[0228] For example, assume that the user device is a mobile phone, and multiple smart home devices are registered under the designated user account.

[0229] At this time, if the mobile phone is logged into the designated user account, the user can directly manage each smart home device under the designated user account through the mobile phone, without the mobile phone establishing a connection with each smart home device one by one.

[0230] In the process of registering the smart home device, the smart home device needs to communicate with the smart home platform in the cloud. Since most of the current smart home devices do not support cellular networks, the smart home device needs to access the electronic device (hereinafter referred to as a routing device) in the home that is already connected to the network and has routing function, so as to realize communication with the smart home platform in the cloud.

[0231] However, in the application scenario (hereinafter referred to as the pre-installation scenario) that some smart home devices are installed in the decoration stage before the house is delivered to the user, since the house has not been delivered to the user, the user usually does not open the Internet line, so that the routing device cannot connect to the Internet through the Internet line, and thus the smart home device cannot access the smart home platform and cannot be registered.

[0232] In addition, in the pre-installation scenario, the installation and maintenance personnel responsible for installing the smart home device also cannot know the user account of the user, and cannot determine which user account the pre-installed smart home device should be registered to.

[0233] Therefore, in the case that the smart home device cannot communicate with the smart home platform in the cloud and / or it is not determined which user account it should be registered to, the installation and maintenance personnel cannot help the user to complete the registration process in advance, and the user needs to register each smart home device to the specified user account one by one after opening the Internet line of the home and determining the specified user account.

[0234] Since the number of smart home devices in the home is large, the user needs to perform more operations when registering the smart home devices by himself, which greatly affects the user experience.

[0235] Therefore, the embodiments of the present application provide a device registration method, in the case that the smart home device cannot access the Internet and the user account of the user has not been determined, the user device can register the smart home device to the hub device, so that the user can manage each smart home device through the hub device.

[0236] The embodiments of the present application also provide a device registration method, when the smart home device can access the Internet and it is determined to be registered to a specified user account, the user can conveniently register the smart home device previously registered to the hub device to the specified user account (or establish a binding relationship with the specified user account), without the user registering one by one, reducing the operations to be performed by the user and improving the user experience.

[0237] This application also provides a device registration method. When it is necessary to unbind a specified user account from a smart home device, the smart home device that has been registered on the cloud-based smart home platform can be reverted to a state where it is only registered to the central device. This allows the user to easily transfer the operation permissions of the smart home device and the central device to other users, while retaining the information configured when the smart home device was previously managed in a unified manner, such as retaining various smart scenes.

[0238] The above description uses a pre-installed scenario as an example to illustrate the applicable scenarios of the solutions provided in this application. However, it should be understood that this does not constitute a limitation on the applicable scenarios, the technical problems that can be solved, or the scope of coverage of the solutions provided in this application. The solutions provided in this application can also be applied to any other suitable scenario to solve the corresponding technical problems.

[0239] First, please refer to Figure 1 . Figure 1 An exemplary device registration system applicable to embodiments of this application is shown, which can be set up in a home area.

[0240] like Figure 1 As shown, the device registration system may include: one or more smart home devices 101 ( Figure 1 Only 3 are shown in the image), one or more central devices 102 ( Figure 1 (Only one is shown in the image), and user equipment 103.

[0241] The aforementioned smart home device 101 refers to Internet of Things (IoT) devices in a home area. These smart home devices may include one or more of the following types of electronic devices: desktop computers, laptops, tablets, smart TVs, smart screens, smart speakers, smart air conditioners, robot vacuums, dishwashers, smart lights, smart door locks, smart curtains, routers, LiDAR, millimeter-wave radar, smart door locks, video doorbells, etc.

[0242] Among them, the smart home device 101 with routing function (hereinafter referred to as the routing device) can create a local area network. Other smart home devices 101 can connect to the local area network, or they can choose not to connect to the local area network.

[0243] The central device 102 refers to an electronic device that can control the smart home device 101. The central device 102 can be a home control electronic device specially used for controlling the smart home device 101 in the whole house; or the central device 102 can also be a smart home device 101 installed with a home central software, which can enable the existing smart home device 101 (such as a router, a smart large screen, etc.) in the home to control and make intelligent decisions on the smart home device 101 in the whole house on the basis of the existing functions.

[0244] For example, in some scenarios, the central device 102 can be a control screen, and the user can control the smart home device 101 through the control screen; in other scenarios, the central device 102 can be a smart large screen installed with a home central software, and the user can control other smart home devices 101 through the smart large screen; in other scenarios, the central device 102 can be a smart speaker installed with a home central software, and the user can control other smart home devices 101 through the smart speaker.

[0245] In actual application scenarios, the central device 102 can access the local area network and control the smart home device 101 in the local area network.

[0246] The user device 103 refers to a personal device of the user, which can be understood as a mobile phone, a smart wearable device, or other non-shared electronic devices. Of course, if the user device 103 is used as a smart home device 101 by the user, the user device 103 can also be understood as a smart home device 101.

[0247] It should be understood that the embodiments of the present application do not particularly limit a certain device to be a smart home device 101, a central device 102, or a user device 103, and the role of a certain device in a certain stage should be defined according to the function and role of the device in different stages of the registration system.

[0248] The smart home device 101, the central device 102, and the user device 103 can communicate with each other through one or more of Wi-Fi connection, Bluetooth connection, universal serial bus (USB) connection, registered jack 45 (RJ45) connection, power line communication (PLC) connection, etc.

[0249] In some possible application scenarios, the device registration system can be applied to a front-end scenario. Specifically, the front-end scenario can refer to a scenario in which various smart home devices are pre-installed and configured in a house by a smart home solution provider or a maintenance personnel of a real estate developer before the house is delivered to a user.

[0250] Generally, the user will go to a broadband service provider to open a home network after taking possession of the house. Therefore, in the front-end stage, the smart home devices are in a state of being unable to connect to the Internet and are unable to be registered to a cloud-based smart home platform. In the existing smart home solution, the maintenance personnel cannot help the user complete the registration process in advance in this scenario, and the maintenance personnel cannot implement unified management of the smart home devices in this scenario.

[0251] When the device registration method provided in the embodiments of the present application is applied, the maintenance personnel can register various smart home devices to the hub device in the front-end scenario. The hub device can be understood as an edge cloud (also referred to as an edge server). Therefore, in the front-end stage, the maintenance personnel can perform unified management of the smart home devices through the hub device.

[0252] In addition, after the front-end is completed and the house is delivered to the user, the user can register the hub device to the user's own user account by using a user device logged in to the user's own user account, and after the hub device is registered, the hub device can register other smart home devices registered to the hub device to the user's user account, so that the user does not need to register each smart home device one by one, reducing the user's operation and improving the user's experience.

[0253] Reference Figure 2 , Figure 2 An example shows a structural schematic diagram of an electronic device 200 provided by the embodiments of the present application. The electronic device 200 can be the smart home device 101, the hub device 102, or the user device 103.

[0254] The electronic device 200 can include a processor 210, an external memory interface 220, an internal memory 221, a universal serial bus (USB) interface 230, a charging management module 240, a power management module 241, a battery 242, an antenna 1, an antenna 2, a mobile communication module 250, a wireless communication module 260, an audio module 270, a speaker 270A, a receiver 270B, a microphone 270C, a headset jack 270D, a sensor module 280, a key 290, a motor 291, an indicator 292, a camera 293, a display screen 294, and a subscriber identification module (SIM) card interface 295, etc. The sensor module 280 can include a pressure sensor 280A, a gyro sensor 280B, a barometric sensor 280C, a magnetic sensor 280D, an acceleration sensor 280E, a distance sensor 280F, a proximity light sensor 280G, a fingerprint sensor 280H, a temperature sensor 280J, a touch sensor 280K, an ambient light sensor 280L, a bone conduction sensor 280M, etc.

[0255] The processor 210 can include one or more processing units, for example: the processor 210 can include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Different processing units can be independent devices, or can be integrated in one or more processors.

[0256] The controller can generate operation control signals according to instruction operation codes and timing signals, and complete the control of fetching and executing instructions.

[0257] The memory in the processor 210 can also be provided for storing instructions and data. In some embodiments, the memory in the processor 210 is a cache memory. The memory can save instructions or data that have just been used or are repeatedly used by the processor 210. If the processor 210 needs to use the instructions or data again, it can be directly called from the memory. This avoids repeated access and reduces the waiting time of the processor 210, thereby improving the efficiency of the system.

[0258] In some embodiments, the processor 210 can include one or more interfaces. The interfaces can include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0259] The I2C interface is a bidirectional synchronous serial bus, including a serial data line (SDA) and a serial clock line (SCL). In some embodiments, the processor 210 can include multiple sets of I2C buses. The processor 210 can be coupled to the touch sensor 280K, the charger, the flash, the camera 293, etc. through different I2C bus interfaces, respectively. For example, the processor 210 can be coupled to the touch sensor 280K through an I2C interface, so that the processor 210 and the touch sensor 280K communicate through the I2C bus interface, and the touch function of the electronic device 200 is realized.

[0260] The I2S interface can be used for audio communication. In some embodiments, the processor 210 can include multiple sets of I2S buses. The processor 210 can be coupled to the audio module 270 through the I2S bus, and communication between the processor 210 and the audio module 270 is realized. In some embodiments, the audio module 270 can deliver audio signals to the wireless communication module 260 through the I2S interface, and the function of answering a phone through a Bluetooth headset is realized.

[0261] The PCM interface can also be used for audio communication, which samples, quantizes and encodes analog signals. In some embodiments, the audio module 270 and the wireless communication module 260 can be coupled through the PCM bus interface. In some embodiments, the audio module 270 can also deliver audio signals to the wireless communication module 260 through the PCM interface, and the function of answering a phone through a Bluetooth headset is realized. Both the I2S interface and the PCM interface can be used for audio communication.

[0262] The UART interface is a universal serial bus for asynchronous communication. The bus can be a bidirectional communication bus. It converts data to be transmitted between serial communication and parallel communication. In some embodiments, the UART interface is usually used to connect the processor 210 and the wireless communication module 260. For example, the processor 210 communicates with the Bluetooth module in the wireless communication module 260 through the UART interface to realize the Bluetooth function. In some embodiments, the audio module 270 can transmit audio signals to the wireless communication module 260 through the UART interface to realize the function of playing music through the Bluetooth headset.

[0263] The MIPI interface can be used to connect the processor 210 and peripheral devices such as the display screen 294 and the camera 293. The MIPI interface includes a camera serial interface (CSI), a display serial interface (DSI), etc. In some embodiments, the processor 210 and the camera 293 communicate through the CSI interface to realize the shooting function of the electronic device 200. The processor 210 and the display screen 294 communicate through the DSI interface to realize the display function of the electronic device 200.

[0264] The GPIO interface can be configured by software. The GPIO interface can be configured as a control signal or as a data signal. In some embodiments, the GPIO interface can be used to connect the processor 210 and the camera 293, the display screen 294, the wireless communication module 260, the audio module 270, the sensor module 280, etc. The GPIO interface can also be configured as an I2C interface, an I2S interface, a UART interface, a MIPI interface, etc.

[0265] The USB interface 230 is an interface that meets the USB standard specification, which can be a Mini USB interface, a Micro USB interface, a USB Type C interface, etc. The USB interface 230 can be used to connect a charger to charge the electronic device 200, or to transmit data between the electronic device 200 and a peripheral device. It can also be used to connect a headset to play audio through the headset. The interface can also be used to connect other electronic devices, such as AR devices, etc.

[0266] It can be understood that the interface connection relationship between the modules shown in the embodiments of the present application is only illustrative and does not constitute a structural limitation of the electronic device 200. In some other embodiments of the present application, the electronic device 200 can also use different interface connection methods or combinations of multiple interface connection methods in the above embodiments.

[0267] The charging management module 240 is configured to receive charging input from a charger. The charger can be a wireless charger or a wired charger. In some embodiments with wired charging, the charging management module 240 can receive charging input from a wired charger through the USB interface 230. In some embodiments with wireless charging, the charging management module 240 can receive wireless charging input through a wireless charging coil of the electronic device 200. The charging management module 240 can supply power to the electronic device while charging the battery 242.

[0268] The power management module 241 is configured to connect the battery 242, the charging management module 240, and the processor 210. The power management module 241 receives input from the battery 242 and / or the charging management module 240 to supply power to the processor 210, the internal memory 221, the display screen 294, the camera 293, and the wireless communication module 260. The power management module 241 can also be configured to monitor parameters such as battery capacity, battery cycle count, battery health status (leakage, impedance), and the like. In some other embodiments, the power management module 241 can also be disposed in the processor 210. In some other embodiments, the power management module 241 and the charging management module 240 can also be disposed in the same device.

[0269] The wireless communication function of the electronic device 200 can be implemented through the antenna 1, the antenna 2, the mobile communication module 250, the wireless communication module 260, the modem processor, and the baseband processor, and the like.

[0270] The antenna 1 and the antenna 2 are configured to transmit and receive electromagnetic wave signals. Each antenna in the electronic device 200 can be configured to cover a single or multiple communication frequency bands. Different antennas can also be multiplexed to improve the utilization of the antennas. For example, the antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in combination with a tuning switch.

[0271] The mobile communication module 250 can provide a solution for wireless communication including 2G / 3G / 4G / 5G, etc. applied to the electronic device 200. The mobile communication module 250 can include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The mobile communication module 250 can receive electromagnetic waves by the antenna 1, and perform filtering, amplification, etc. on the received electromagnetic waves, and transfer the same to the modem processor for demodulation. The mobile communication module 250 can also amplify the signal modulated by the modem processor, and radiate the same as electromagnetic waves through the antenna 1. In some embodiments, at least part of the functional modules of the mobile communication module 250 can be disposed in the processor 210. In some embodiments, at least part of the functional modules of the mobile communication module 250 can be disposed in the same device as at least part of the modules of the processor 210.

[0272] The modem processor can include a modulator and a demodulator. The modulator is configured to modulate a low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is configured to demodulate a received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. The low-frequency baseband signal processed by the baseband processor is transmitted to the application processor. The application processor outputs a sound signal through an audio device (not limited to the speaker 270A, the microphone 270B, etc.), or displays an image or a video through the display screen 294. In some embodiments, the modem processor can be a separate device. In other embodiments, the modem processor can be independent of the processor 210, and disposed in the same device as the mobile communication module 250 or other functional modules.

[0273] The wireless communication module 260 can provide a solution for wireless communication, including wireless local area networks (WLAN) (e.g., wireless fidelity (Wi-Fi) network), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR) technology, etc., which are applied to the electronic device 200. The wireless communication module 260 can be one or more devices that integrate at least one communication processing module. The wireless communication module 260 receives electromagnetic waves via the antenna 2, frequency-modulates and filters the electromagnetic wave signals, and transmits the processed signals to the processor 210. The wireless communication module 260 can also receive signals to be transmitted from the processor 210, frequency-modulate them, amplify them, and radiate them as electromagnetic waves via the antenna 2.

[0274] In some embodiments, antenna 1 and mobile communication module 250 of electronic device 200 are coupled, and antenna 2 and wireless communication module 260 are coupled, so that electronic device 200 can communicate with a network and other devices through wireless communication technology. The wireless communication technology can include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technology, etc. The GNSS can include a global positioning system (GPS), a global navigation satellite system (GLONASS), a beidu navigation satellite system (BDS), a quasi-zenith satellite system (QZSS), and / or a satellite based augmentation systems (SBAS).

[0275] Electronic device 200 implements a display function through a GPU, display screen 294, and an application processor, etc. The GPU is a microprocessor for image processing, which is connected to display screen 294 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 210 can include one or more GPUs, which execute program instructions to generate or change display information.

[0276] The display screen 294 is configured to display images, videos, and the like. The display screen 294 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flex light-emitting diode (FLED), a Miniled, a MicroLed, a Micro-oLed, a quantum dot light emitting diodes (QLED), or the like. In some embodiments, the electronic device 200 can include one or N display screens 294, where N is a positive integer greater than 1.

[0277] The electronic device 200 can implement a photographing function through an ISP, the camera 293, a video codec, a GPU, the display screen 294, and an application processor, and the like.

[0278] The ISP is configured to process data fed back by the camera 293. For example, when taking a photo, the shutter is opened, light is transmitted to the camera photosensitive element through the lens, the light signal is converted into an electrical signal, and the camera photosensitive element transmits the electrical signal to the ISP for processing to convert it into an image visible to the naked eye. The ISP can also perform algorithm optimization on the noise, brightness, and skin color of the image. The ISP can also optimize the exposure, color temperature, and other parameters of the shooting scene. In some embodiments, the ISP can be disposed in the camera 293.

[0279] The camera 293 is configured to capture still images or videos. An object generates an optical image through a lens and projects it onto a photosensitive element. The photosensitive element can be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, which is then transmitted to the ISP to convert it into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV, or the like format. In some embodiments, the electronic device 200 can include one or N cameras 293, where N is a positive integer greater than 1.

[0280] The digital signal processor is used to process digital signals, in addition to being able to process digital image signals, it can also process other digital signals. For example, when the electronic device 200 is in frequency point selection, the digital signal processor is used to perform Fourier transform on the frequency point energy, etc.

[0281] The video codec is used to compress or decompress digital video. The electronic device 200 can support one or more video codecs. In this way, the electronic device 200 can play or record videos in multiple encoding formats, such as: moving picture experts group (MPEG) 1, MPEG 2, MPEG 3, MPEG 4, etc.

[0282] The NPU is a neural-network (NN) calculation processor, which can quickly process input information by drawing on the structure of a biological neural network, such as the transmission mode between human brain neurons, and can also continuously self-learn. Through the NPU, the electronic device 200 can realize intelligent cognition applications such as image recognition, face recognition, voice recognition, text understanding, etc.

[0283] The external memory interface 220 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 200. The external memory card communicates with the processor 210 through the external memory interface 220 to realize data storage functions. For example, music, video, etc. Files are saved in the external memory card.

[0284] The internal memory 221 can be used to store computer executable program codes, which include instructions. The internal memory 221 can include a program storage area and a data storage area. The program storage area can store an operating system, at least one application program required by a function (such as a sound playing function, an image playing function, etc.), etc. The data storage area can store data created during the use of the electronic device 200 (such as audio data, a phonebook, etc.), etc. In addition, the internal memory 221 can include a high-speed random access memory, and can also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, a universal flash storage (UFS), etc. The processor 210 executes various function applications and data processing of the electronic device 200 by running instructions stored in the internal memory 221 and / or instructions stored in the memory provided in the processor.

[0285] The electronic device 200 can realize audio functions through the audio module 270, the speaker 270A, the receiver 270B, the microphone 270C, the earphone interface 270D, and the application processor, etc. For example, music playing, recording, etc.

[0286] The audio module 270 is configured to convert digital audio information into an analog audio signal output, and to convert an analog audio input into a digital audio signal. The audio module 270 can also be configured to encode and decode audio signals. In some embodiments, the audio module 270 can be disposed in the processor 210, or some functional modules of the audio module 270 can be disposed in the processor 210.

[0287] The speaker 270A, also referred to as a “loudspeaker”, is configured to convert an audio electrical signal into a sound signal. The electronic device 200 can listen to music or listen to a hands-free call through the speaker 270A.

[0288] The receiver 270B, also referred to as a “earpiece”, is configured to convert an audio electrical signal into a sound signal. When the electronic device 200 receives a call or a voice message, the user can listen to the voice by holding the receiver 270B close to the ear.

[0289] The microphone 270C, also referred to as a “microphone”, “transducer”, is configured to convert a sound signal into an electrical signal. When making a call or sending a voice message, the user can make a sound by holding the mouth close to the microphone 270C, and input the sound signal into the microphone 270C. The electronic device 200 can be provided with at least one microphone 270C. In other embodiments, the electronic device 200 can be provided with two microphones 270C, in addition to collecting sound signals, the noise reduction function can also be realized. In other embodiments, the electronic device 200 can also be provided with three, four or more microphones 270C, in addition to collecting sound signals, noise reduction, it can also identify the source of the sound, realize the function of directional recording, etc.

[0290] The earphone interface 270D is configured to connect a wired earphone. The earphone interface 270D can be a USB interface 230, or a 3.5mm open mobile terminal platform (OMTP) standard interface, a cellular telecommunications industry association of the USA (CTIA) standard interface.

[0291] The pressure sensor 280A is configured to sense a pressure signal and convert the pressure signal into an electrical signal. In some embodiments, the pressure sensor 280A can be disposed on the display screen 294. The pressure sensor 280A can be of various types, such as a resistive pressure sensor, an inductive pressure sensor, a capacitive pressure sensor, etc. The capacitive pressure sensor can include at least two parallel plates of conductive material. When a force is applied to the pressure sensor 280A, the capacitance between the electrodes changes. The electronic device 200 determines the intensity of the pressure based on the change in capacitance. When a touch operation is applied to the display screen 294, the electronic device 200 detects the intensity of the touch operation based on the pressure sensor 280A. The electronic device 200 can also calculate the position of the touch based on the detection signal of the pressure sensor 280A. In some embodiments, touch operations applied to the same touch position but with different touch operation intensities can correspond to different operation instructions. For example, when a touch operation with a touch operation intensity less than a first pressure threshold is applied to a short message application icon, an instruction to view short messages is executed. When a touch operation with a touch operation intensity greater than or equal to the first pressure threshold is applied to the short message application icon, an instruction to create a new short message is executed.

[0292] The gyroscope sensor 280B can be configured to determine the motion attitude of the electronic device 200. In some embodiments, the angular velocity of the electronic device 200 around three axes (i.e., x, y, and z axes) can be determined by the gyroscope sensor 280B. The gyroscope sensor 280B can be used for anti-shake photography. For example, when the shutter is pressed, the gyroscope sensor 280B detects the angle of shaking of the electronic device 200, calculates the distance that the lens module needs to compensate based on the angle, and lets the lens offset the shaking of the electronic device 200 by reverse movement to achieve anti-shake. The gyroscope sensor 280B can also be used for navigation and motion sensing game scenarios.

[0293] The barometric pressure sensor 280C is configured to measure air pressure. In some embodiments, the electronic device 200 calculates the altitude, assists positioning and navigation based on the air pressure value measured by the barometric pressure sensor 280C.

[0294] The magnetic sensor 280D includes a Hall sensor. The electronic device 200 can detect the opening and closing of a flip cover by using the magnetic sensor 280D. In some embodiments, when the electronic device 200 is a flip phone, the electronic device 200 can detect the opening and closing of the flip cover based on the magnetic sensor 280D. Further, based on the detected opening and closing state of the cover or the flip cover, the electronic device 200 can set a feature such as automatic unlocking of the flip cover.

[0295] The acceleration sensor 280E can detect the magnitude of acceleration of the electronic device 200 in various directions (typically three axes). When the electronic device 200 is stationary, the acceleration sensor 280E can detect the magnitude and direction of gravity. The acceleration sensor 280E can also be used to identify the attitude of the electronic device, and can be applied to landscape / portrait screen switching and pedometer applications.

[0296] Distance sensor 280F is configured to measure distance. Electronic device 200 can measure distance by infrared or laser. In some embodiments, electronic device 200 can utilize distance sensor 280F to measure distance to achieve fast focus when taking a picture.

[0297] Proximity light sensor 280G can include, for example, a light emitting diode (LED) and a light detector, such as a photodiode. The light emitting diode can be an infrared light emitting diode. Electronic device 200 emits infrared light outwardly through the light emitting diode. Electronic device 200 detects infrared reflected light from nearby objects using the photodiode. When sufficient reflected light is detected, electronic device 200 can determine that there is an object near electronic device 200. When insufficient reflected light is detected, electronic device 200 can determine that there is no object near electronic device 200. Electronic device 200 can utilize proximity light sensor 280G to detect that a user is holding electronic device 200 close to the ear for a phone call, so as to automatically turn off the screen to save power. Proximity light sensor 280G can also be used for automatic unlocking and locking of the screen in a holster mode or a pocket mode.

[0298] Ambient light sensor 280L is configured to sense ambient light brightness. Electronic device 200 can adaptively adjust the brightness of display 294 according to the sensed ambient light brightness. Ambient light sensor 280L can also be used to automatically adjust white balance when taking a picture. Ambient light sensor 280L can also cooperate with proximity light sensor 280G to detect whether electronic device 200 is in a pocket to prevent accidental touch.

[0299] Fingerprint sensor 280H is configured to collect a fingerprint. Electronic device 200 can utilize the collected fingerprint characteristics to implement fingerprint unlocking, access application lock, fingerprint picture taking, fingerprint call answering, and the like.

[0300] Temperature sensor 280J is configured to detect temperature. In some embodiments, electronic device 200 utilizes the temperature detected by temperature sensor 280J to implement temperature handling strategies. For example, when the temperature reported by temperature sensor 280J exceeds a threshold, electronic device 200 implements performance reduction of a processor located near temperature sensor 280J to reduce power consumption and implement thermal protection. In other embodiments, when the temperature is lower than another threshold, electronic device 200 heats battery 242 to avoid abnormal shutdown of electronic device 200 caused by low temperature. In other embodiments, when the temperature is lower than yet another threshold, electronic device 200 implements voltage boosting of the output voltage of battery 242 to avoid abnormal shutdown caused by low temperature.

[0301] Touch sensor 280K, also referred to as "touch device". Touch sensor 280K can be disposed on display screen 294, and touch sensor 280K and display screen 294 form a touch screen, also referred to as "touch panel". Touch sensor 280K is configured to detect touch operations applied to or near the touch sensor 280K. The touch sensor can transmit the detected touch operation to the application processor to determine the touch event type. Visual output related to the touch operation can be provided through display screen 294. In other embodiments, touch sensor 280K can also be disposed on the surface of electronic device 200, which is different from the position where display screen 294 is located.

[0302] Bone conduction sensor 280M can obtain vibration signals. In some embodiments, bone conduction sensor 280M can obtain vibration signals of the human body's vocal vibration bone block. Bone conduction sensor 280M can also contact the human body pulse to receive blood pressure pulsation signals. In some embodiments, bone conduction sensor 280M can also be disposed in a headset to form a bone conduction headset. Audio module 270 can analyze voice signals based on the vibration signals of the vocal vibration bone block obtained by the bone conduction sensor 280M to realize voice functions. The application processor can analyze heart rate information based on the blood pressure pulsation signals obtained by the bone conduction sensor 280M to realize heart rate detection functions.

[0303] Keys 290 include power on / off keys, volume keys, and the like. Keys 290 can be mechanical keys. They can also be touch keys. Electronic device 200 can receive key input and generate key signal input related to user settings and function control of electronic device 200.

[0304] Motor 291 can generate vibration prompts. Motor 291 can be used for incoming call vibration prompts and also for touch vibration feedback. For example, touch operations applied to different applications (such as taking pictures, playing audio, etc.) can correspond to different vibration feedback effects. Touch operations applied to different regions of display screen 294 can also correspond to different vibration feedback effects of motor 291. Different application scenarios (such as time reminders, received messages, alarms, games, etc.) can also correspond to different vibration feedback effects. Touch vibration feedback effects can also be customizable.

[0305] Indicator 292 can be an indicator light, which can be used to indicate charging status, power changes, and also to indicate messages, missed calls, notifications, and the like.

[0306] The SIM card interface 295 is configured to connect a SIM card. The SIM card can be inserted into or pulled out of the SIM card interface 295 to realize contact and separation with the electronic device 200. The electronic device 200 can support one or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 295 can support a Nano SIM card, a Micro SIM card, a SIM card, or the like. Multiple cards can be inserted into the same SIM card interface 295 at the same time. The types of the multiple cards can be the same or different. The SIM card interface 295 can be compatible with different types of SIM cards. The SIM card interface 295 can also be compatible with external storage cards. The electronic device 200 interacts with a network through the SIM card to realize functions such as call and data communication. In some embodiments, the electronic device 200 uses an eSIM, that is, an embedded SIM card. The eSIM card can be embedded in the electronic device 200 and cannot be separated from the electronic device 200.

[0307] It can be understood that the structure illustrated in the embodiments of the present application does not constitute a specific limitation on the electronic device 200. In other embodiments of the present application, the electronic device 200 can include more or fewer components than those illustrated, or combine certain components, or split certain components, or different arrangement of components. The illustrated components can be implemented in hardware, software, or a combination of software and hardware.

[0308] In the following, Figure 1 the device registration system shown in Figure 2 the electronic device shown in and in combination with a specific application scenario, the device registration method provided by the embodiments of the present application will be described in detail.

[0309] 1. Access to a local area network.

[0310] As described above, the user device can be a personal device of the user, and the user usually carries the user device with him / her. Therefore, the user device can enter or leave the home area with the movement of the user.

[0311] When the user device enters the home area, the user device can discover the local area network provided by the routing device.

[0312] At this time, if the user device has never accessed the local area network, the user device can acquire the local area network connection information in response to a connection operation of the user, and access the local area network according to the local area network connection information.

[0313] If the user device has accessed the local area network, the user device can automatically access the local area network according to the local area network connection information recorded by the device.

[0314] Exemplarily, it is assumed that the user equipment is a mobile phone, and a local area network is arranged in the home area, and the service set identifier (SSID) of the local area network is "H123".

[0315] As shown in (a) of FIG. 1, when the user first carries the mobile phone into the home area, the mobile phone can discover the local area network, and display the SSID of the local area network in a wireless local area network (WLAN) search interface 11. Figure 3

[0316] As shown in (b) of FIG. 1, after the user clicks the option of "H123" in the WLAN search interface 11, the mobile phone can enter a WLAN connection interface 12. The WLAN connection interface 12 includes a password input box 13, a "cancel" control 14 and a "connect" control 15. Figure 3

[0317] When the user inputs the connection password "123456" in the password input box 13 and clicks the "connect" control 15, the mobile phone can access the local area network "H123" according to the connection password, and the mobile phone can record the SSID and the connection password of the local area network.

[0318] After that, if the user carries the mobile phone into the home area again, the mobile phone can automatically access the local area network "H123" according to the locally recorded connection password "123456" after discovering the local area network "H123".

[0319] 2, log in to the hub device.

[0320] When the home area has not been opened up for an online line, the smart home devices in the home area cannot access the Internet and cannot communicate with the cloud smart home platform. At this time, the user equipment cannot register the smart home devices in the home area, and cannot centrally manage the smart home devices in the home area.

[0321] Therefore, when the home area has not been opened up for an online line, the user equipment can log in to the hub device as an edge server after accessing the local area network, register the smart home devices to the hub device, and control the smart home devices registered to the hub device through the hub device.

[0322] The manner in which the user equipment logs in to the hub device can be set according to actual needs.

[0323] For example, in some possible implementation manners, an administrator account and an administrator password for login are pre-set on the hub device.

[0324] ​​The administrator account and the administrator password can be set according to actual needs. For example, the administrator account can be set as "000001", and the administrator password can be set as "123456".

[0325] At this time, as shown in (a) of FIG. 6, after the user equipment accesses the local area network, the user can open an application (for example, a "decoration and maintenance application") for managing smart home equipment, and enter a login interface. Then, the user can input the administrator account "000001" and the administrator password "123456" on the login interface. Figure 4

[0326] The user equipment can log in the hub device according to the administrator account "000001" and the administrator password "123456" in response to the input operation of the user.

[0327] In some possible implementation manners, the hub device can be provided with a display screen, and the network protocol (Internet Protocol, IP) address of the hub device in the local area network and a randomly generated verification code can be displayed on the display screen.

[0328] For example, it is assumed that the IP address displayed on the display screen of the hub device is "126.1.1.1", and the randomly generated verification code is "Ksdyzc". At this time, as shown in (b) of FIG. 6, after the user views the IP address and the verification code displayed on the display screen of the hub device, the user can input the IP address "126.1.1.1" of the hub device and the verification code "Ksdyzc" on the login interface of the user equipment. Figure 4

[0329] The user equipment can log in the hub device according to the IP address "126.1.1.1" and the verification code "Ksdyzc" in response to the input operation of the user.

[0330] In some possible implementation manners, the user equipment can also log in the hub device by using face recognition, fingerprint recognition, gesture recognition, or other manners. The embodiments of the present application do not limit the manner in which the user equipment logs in the hub device.

[0331] It should be noted that the user can include one or more of a decoration and maintenance personnel, a householder, and the like. The embodiments of the present application do not limit the type of the user.

[0332] For example, in a front installation scenario, before the house is delivered, the decoration and maintenance personnel can log in the hub device by using a decoration and maintenance device (for example, a mobile phone or a notebook computer of the decoration and maintenance personnel); after the house is delivered, the householder can log in the hub device by using his personal device (for example, a mobile phone of the householder). The decoration and maintenance personnel and the householder can be understood as the user. ​​

[0333] 3. Device registration.

[0334] After the user device logs in the hub device, if the user device detects a device registration operation of the user, the user device can register the selected smart home device (hereinafter referred to as a target device) to the hub device.

[0335] Specifically, the user can perform a device registration operation on the user device. The user device can determine the target device in response to the device registration operation, and send a first registration request to the hub device.

[0336] After receiving the first registration request, the hub device can return a first registration parameter to the user device. The first registration parameter can include a first registration code.

[0337] Optionally, the first registration parameter can also include a first device identifier. After the target device registration is passed, the first device identifier can serve as the identity of the target device.

[0338] After receiving the first registration parameter, the user device can establish a connection with the target device, and send first registration information to the target device. The first registration information can include the identity of the hub device and the first registration parameter.

[0339] The identity of the hub device is used to find the hub device. The identity of the hub device can include one or more of the IP address of the hub device, the physical (Media Access Control, MAC) address of the hub device, the product serial number (Serial Number, SN) of the hub device, etc.

[0340] Optionally, the first registration information can also include local area network connection information. The local area network connection information can include the SSID and connection password of the local area network. In some embodiments, the local area network connection information can be stored on the user device; in other embodiments, the local area network connection information can also be input by the user during the device registration operation.

[0341] When the target device receives the first registration information, if the target device has not yet accessed the local area network, the target device can access the local area network according to the local area network connection information.

[0342] If the target device has accessed the local area network, the target device can find the hub device according to the identity information of the hub device, and establish a connection with the hub device.

[0343] After that, the target device can send the first registration code to the hub device.

[0344] When the hub device receives the first registration code, the hub device can check the received first registration code with the issued first registration code.

[0345] If the received first registration code is consistent with the issued first registration code, it means that the check is passed, and the hub device can register the target device on the device and send the first credential information to the target device, completing the registration process.

[0346] If the received first registration code is inconsistent with the issued first registration code, it means that the check fails, and the hub device can refuse to register the target device on the device.

[0347] Exemplarily, as shown in FIG. 21, it is assumed that the device registration system includes a central control screen 21, a mobile phone 22, and a smart speaker 23. Figure 5

[0348] In this example, the central control screen 21 can be understood as a hub device, the mobile phone 22 can be understood as a user device, and the smart speaker 23 can be understood as a smart home device that has not been registered. Moreover, the central control screen 21 and the mobile phone 22 are connected to a local area network of a home area, the mobile phone 22 is logged in the central control screen 21, and the smart speaker 23 has not been connected to the local area network of the home area.

[0349] Figure 6 Exemplarily, a device interaction diagram of an implementation manner of registering the smart speaker 23 on the central control screen 21 through the mobile phone 22 in the scenario shown in FIG. 21 is shown. Figure 5

[0350] At the first time, the user wants to register the smart speaker 23 on the central control screen 21. At this time, as shown in FIG. 22, the user can perform a preset operation on the smart speaker 23, for example, long-pressing a volume key. The smart speaker 23 can enter an AP mode and share a hotspot externally in response to the preset operation of the user, as shown in step S601. Figure 7 Figure 6 In some embodiments, as shown in (a) of FIG. 23, the user can also open a smart home management software (for example, a Jiasu application) on the mobile phone 22 to enter a device management interface 221. The device management interface 221 can include an “add” control 222, a “find” control 223, and a control 224 for managing the central control screen 21.

[0351] In some embodiments, the mobile phone 22 has logged in the central control screen 21, and therefore the control 224 can be displayed in the device management interface 221; in other embodiments, the mobile phone 22 has not logged in the central control screen 21, and therefore the control 224 can not be displayed in the device management interface 221. Figure 8

[0352] In some embodiments, the mobile phone 22 has logged in the central control screen 21, and therefore the control 224 can be displayed in the device management interface 221; in other embodiments, the mobile phone 22 has not logged in the central control screen 21, and therefore the control 224 can not be displayed in the device management interface 221.

[0353] ​​​​The user can click the "add" control 222 in the device management interface 221. As shown in (b) of FIG. 2B, the mobile phone 22 can enter a scanning interface 225 and perform a scanning operation in response to the user's operation, to scan for electronic devices in an AP mode (i.e., sharing a hotspot) around the mobile phone 22. Figure 8

[0354] During the scanning, the mobile phone 22 discovers the hotspot shared by the smart speaker 23, i.e., the mobile phone 22 scans the smart speaker 23, as shown in step S602 of FIG. 2C. Figure 6 Figure 8 Therefore, as shown in (c) of FIG. 2C, the mobile phone 22 can display a device list 226, in which an option of "smart speaker" is displayed.

[0355] After viewing the device list 226, the user can click the option of "smart speaker". At this time, as shown in FIG. 2D, the mobile phone 22 can determine the smart speaker 23 as a target device in response to the user's operation, and send a first registration request to the central screen 21, as shown in step S603 of FIG. 2D. Figure 9 Figure 6

[0356] After receiving the first registration request, the central screen 21 can generate a first registration parameter and return the first registration parameter to the mobile phone 22, as shown in step S604 of FIG. 2E. Optionally, the central screen 21 can also set a timer. Figure 6

[0357] In some embodiments, the above-mentioned first registration parameter can include a first registration code, which is used by the central screen 21 to verify the smart speaker 23. Optionally, the above-mentioned first registration parameter can also include a first device identifier, which can be used as an identity of the smart speaker 23 after registration.

[0358] The timing duration of the above-mentioned timer is the validity duration of the above-mentioned first registration parameter, which can be set according to actual needs. For example, in the present example, the timing duration can be set to 5 minutes (min), and the first registration parameter is valid within 5 min and invalid after 5 min. The timing start time point of the above-mentioned timer can be the time point at which the central screen 21 generates the first registration parameter, or the time point at which the central screen 21 sends the first registration parameter to the mobile phone 22, or other time points, which are not limited in the embodiments of the present application.

[0359] After receiving the first registration parameter, the mobile phone 22 can disconnect the connection with the local area network, access the hotspot shared by the smart speaker 23, and send a first registration information to the smart speaker 23.

[0360] ​​​​​In some embodiments, the first registration information can include the first registration parameter and the identifier of the central control screen 21. The identifier of the central control screen 21 is used to find the central control screen 21. The identifier of the central control screen 21 can include one or more of the local area network IP address of the central control screen 21, the MAC address of the central control screen 21, the SN code of the central control screen 21, etc. In this example, the identifier of the central control screen 21 can include the local area network IP address of the central control screen 21.

[0361] Optionally, the first registration parameter can further include the local area network connection information of the local area network. The local area network connection information can include the SSID and the connection password of the local area network.

[0362] In some embodiments, since the first registration information is sensitive, in order to prevent malicious listening by others and improve communication security, the mobile phone 22 can negotiate a first session key with the smart speaker 23 before transmitting the first registration information, and establish a first secure connection through the first session key. The mobile phone 22 can send the first registration information to the smart speaker 23 through the first secure connection, as shown in steps S604 and S605. Figure 6

[0363] The generation method of the session key can be selected according to actual needs. For example, the generation method of the session key can include any one or more of the encryption algorithms such as RSA encryption algorithm, elliptic curve cryptography (ECC), Diffie-Hellman Key Exchange (DH), etc. The specific generation method of the session key is not limited in the embodiments of the present application.

[0364] After the smart speaker 23 receives the first registration information, it can stop sharing the hotspot and enter a station (STA) mode, as shown in step S607. Figure 6 The mobile phone 22 can re-enter the local area network and restore the connection with the hub device, as shown in step S608. Figure 6

[0365] After entering the STA mode, the smart speaker 23 can access the local area network according to the local area network connection information, and access the central control screen 21 according to the local area network IP address.

[0366] In some embodiments, in order to improve communication security, the smart speaker 23 can negotiate a second session key with the central control screen 21 through the first registration code, and establish a second secure connection, as shown in step S609. Figure 6

[0367] ​​​The smart speaker 23 can send the first registration code to the central control screen 21 through the second secure connection described above, such as Figure 6 As shown in step S610.

[0368] After the central control screen 21 receives the first registration code sent by the smart speaker 23, the central control screen 21 can verify the received first registration code according to the first registration code issued by the central control screen 21 in step S604, such as Figure 6 As shown in step S611. The above verification can include: the central control screen 21 judges whether the first registration code received by the central control screen 21 in step S610 is the same as the first registration code generated by the central control screen 21 in step S604. Through the above verification process, it can be ensured that the smart home device registered by the central control screen 21 is the target device that the user wants to register, avoiding the case of malicious registration of other electronic devices, and improving the security of device registration.

[0369] In some embodiments, if the central control screen 21 sets a timer corresponding to the first registration code, the central control screen 21 first judges whether the first registration code is valid according to the timer after receiving the first registration code in step S610, and then verifies the first registration code in the case that the first registration code is valid. Of course, the process of judging whether the first registration code is valid can also be understood as part of the above "verification" process. Since it takes a certain amount of time to crack the first verification code, judging whether the first registration code is valid through the timer can reduce the possibility of malicious cracking and use of the first registration code by others, and improve the security of device registration.

[0370] When the first registration code received by the central control screen 21 in step S610 is the same as the first registration code generated by the central control screen 21 in step S604, it means that the verification is passed, and the central control screen 21 can generate the first credential information and return it to the smart speaker 23, such as Figure 6 As shown in step S612.

[0371] In some embodiments, the central control screen 21 can also send a registration success notification to the mobile phone 22, such as Figure 6 As shown in step S613. In some embodiments, as shown in (a) of Figure 10 After receiving the above registration success notification, the mobile phone 22 can add a control 227 for managing the smart speaker 23 in the device management interface 221, and display the state of the smart speaker 23 as offline on the control 227. In some embodiments, when the smart speaker 23 is in an offline state, the user cannot control the smart speaker 23 through the mobile phone 22, and the mobile phone 22 cannot obtain the device state information of the smart speaker 23, such as the remaining power of the smart speaker 23, the volume, etc.

[0372] In some embodiments, after receiving the first credential information, the smart speaker 23 can negotiate a third session key with the central control screen 21 according to the first credential information, establish a third secure connection, and the third secure connection can be used for subsequent communication between the smart speaker 23 and the central control screen 21, as shown in step S613. Figure 6 At this point, the smart speaker 23 completes the registration process to the central control screen 21.

[0373] In some embodiments, after establishing the third secure connection, the central control screen 21 can send an online notification to the mobile phone 22, as shown in step S615. Figure 6 When the mobile phone 22 receives the online notification, the mobile phone 22 can modify the state of the smart speaker 23 in the control 227 to an online state, as shown in (b) of step S616. Figure 10 In some embodiments, when the smart speaker 23 is in the online state, the user can control the smart speaker 23 and view the device state information of the smart speaker 23 through the mobile phone 22.

[0374] It can be understood that in the implementation shown in Figure 6 not all steps are optional steps, and some steps can be omitted or replaced by other steps. For example, steps S613 and S615 are optional steps, and step S605 can be replaced by establishing a non-encrypted connection, and the like.

[0375] In addition, the size of the serial number of each step shown in Figure 6 does not mean the order of execution, and the execution order of each step should be determined by its function and internal logic. For example, the execution order between step S607 and step S608 is not limited, step S607 can be implemented before step S608, or step S607 can be implemented after step S608.

[0376] As can be seen from the above examples, when the local area network cannot connect to the Internet, the user device cannot register the target device to the specified user account, but the user device can register the target device to the hub device in the local area network as an edge server.

[0377] At this time, the hub device is equivalent to an anonymous account not associated with any user, and the user can control each registered device (i.e., the target device registered to the hub device) through the hub device, effectively improving the user's experience.

[0378] In the front-loaded scenario, before the house is delivered, various smart home devices in the house cannot connect to the Internet, cannot communicate with the smart home platform in the cloud, and the installation and maintenance personnel do not know the user account of the future occupant. At this time, by using the device registration method provided in the embodiments of the present application, the installation and maintenance personnel can use the installation and maintenance device (for example, the mobile phone of the installation and maintenance personnel) to register various smart home devices (for example, lighting, smart door lock, smart curtain, alarm) in the house on the hub device. Thus, the installation and maintenance personnel can complete the installation, configuration and overall management of the smart home device by operating the hub device or operating the installation and maintenance device. For example, configure the lighting installed in the living room with the position tag "living room" and the device capability tag "lighting". For another example, configure some initialization scenes and device linkage, such as configuring the alarm to be turned on and the smart door lock to enter the alert state in the "away mode", configuring the main lighting in the living room to be turned off and the auxiliary lighting in the living room to be turned on at low brightness in the "theater mode", and the like.

[0379] When the house is delivered, the occupant can directly manage the above-mentioned smart home devices and use the above-mentioned configured content, without the need to perform the above-mentioned registration and configuration processes by himself.

[0380] 4. Device control.

[0381] When the user wants to control the registered device, the user can directly control the registered device through the hub device; or, after the user device logs in the hub device, the user can indirectly control the registered device on the user device through the relay function of the hub device.

[0382] Specifically, in some embodiments, the user can directly perform a control operation on the hub device.

[0383] At this time, the hub device can determine the controlled device and the control instruction in response to the control operation of the user. The above-mentioned controlled device refers to the registered device that the user wants to control, and can also be understood as the registered device selected by the user. The above-mentioned control instruction is used to indicate the operation that the user wants to perform, and can also be understood as indicating the operation selected by the user.

[0384] Then, the hub device can send the control instruction to the controlled device.

[0385] When the controlled device receives the control instruction, the controlled device can perform the operation corresponding to the control instruction.

[0386] Optionally, after performing the operation corresponding to the control instruction, the controlled device can also return the execution result to the hub device.

[0387] After receiving the execution result, the hub device can display the execution result so that the user can understand the execution progress.

[0388] For example,Figure 11 As shown in the example, the smart speaker 31 can be understood as a hub device, and the smart TV 32 can be understood as a registered device.

[0389] After the user comes back home in the evening, the user wants to turn on the smart TV 32 to watch a program. At this time, the user can perform a control operation on the smart speaker, for example, the user can say to the smart speaker 31: “Xiaoyi, turn on the smart TV”.

[0390] The smart speaker 31 can receive the voice signal issued by the user, and identify the voice signal to determine that the controlled device is the smart TV 32 and the control instruction is the power-on instruction. After determining the controlled device and the control instruction, the smart speaker 31 can send the power-on instruction to the smart TV 32.

[0391] When the smart TV 32 receives the power-on instruction, the smart TV 32 can enter a working state and play a program.

[0392] In some embodiments, the smart TV 32 can return a power-on notification to the smart speaker 31 after entering the working state.

[0393] In some embodiments, when the smart speaker 31 receives the power-on notification, the smart speaker 31 can voice broadcast “the smart TV has been turned on”.

[0394] As known from the above example, since the registered device has been registered to the hub device, when the user wants to control the registered device, the user can directly perform a control operation on the hub device.

[0395] At this time, the hub device can determine the controlled device and the control instruction according to the control operation of the user, and control the controlled device to perform an operation corresponding to the control instruction.

[0396] In addition, since the hub device has established a connection with the registered device, the user does not need to repeatedly perform a connection operation in the process of operating the hub device, which can effectively reduce the operation steps of the user and improve the user experience.

[0397] In other embodiments, the user can also perform a control operation on the user device after the user device logs in the hub device.

[0398] At this time, the user device can determine the controlled device and the control instruction in response to the control operation, and send control information to the hub device, the control information can include the control instruction and the first device identifier corresponding to the controlled device.

[0399] After receiving the control information, the hub device can determine the controlled device according to the first device identifier corresponding to the controlled device, and forward the control instruction to the controlled device.

[0400] When the controlled device receives the control instruction, the controlled device can perform an operation corresponding to the control instruction.

[0401] Optionally, after performing the operation corresponding to the control instruction, the controlled device can return an execution result to the hub device.

[0402] After the hub device receives the execution result, the hub device can forward the execution result to the user device.

[0403] After the user device receives the execution result, the user device can display the execution result so that the user can know the execution progress.

[0404] For example, as shown in Figure 12 In this example, the home server 41 can be understood as the hub device, the mobile phone 42 can be understood as the user device, and the smart air conditioner 43 and the smart large screen 44 can be understood as the registered devices.

[0405] In some embodiments, after the user returns home in the evening, the mobile phone 42 can automatically access the local area network according to the historical local area network connection information.

[0406] Then, the user opens the smart home management software (for example, the decoration and maintenance application). In some embodiments, after the mobile phone 42 starts the smart home management software, the mobile phone 42 can automatically log in to the home server 41 according to the historical administrator account and administrator password.

[0407] At this time, as shown in (a) of Figure 13 , the mobile phone 42 can display the device management interface 421 to the user. The device management interface 421 can include the control 422 for managing the home server 41, the control 423 for managing the smart air conditioner 43, and the control 424 for managing the smart large screen 44.

[0408] When the user clicks the control 423, the mobile phone 42 can determine that the controlled device is the smart air conditioner 43 in response to the operation of the user. And since the smart air conditioner 43 is in the shutdown state, the mobile phone 42 can determine that the control instruction is the power-on instruction.

[0409] After determining the controlled device and the control instruction, the mobile phone 42 can send control information to the home server 41. The control information includes the first device identifier corresponding to the smart air conditioner 43 and the power-on instruction.

[0410] When the home server 41 receives the control information, the home server 41 can determine that the smart air conditioner 43 is the controlled device according to the first device identifier in the control information. At this time, the home server 41 can forward the power-on instruction in the control information to the smart air conditioner 43.

[0411] After the smart air conditioner 43 receives the above power-on instruction, the smart air conditioner 43 can enter the power-on state.

[0412] In some embodiments, the smart air conditioner 43 can also return a start-up notification to the home hub 41 after entering the start-up state.

[0413] After the home hub 41 receives the start-up notification, the home hub 41 can forward the start-up notification to the mobile phone 42.

[0414] In some embodiments, when the mobile phone 42 receives the start-up notification, the mobile phone can change the device state of the smart air conditioner 43 in the control 423 to the start-up state, as shown in (b) of FIG. 4B. Figure 13

[0415] As can be seen from the above examples, when a user wants to control a registered device, the user can also log in the hub device with the user device to obtain the operation permission of the registered device.

[0416] Then, the user device can determine the controlled device and the control instruction according to the control operation of the user, and control the controlled device to perform the operation corresponding to the control instruction through the relay function of the hub device.

[0417] Through the above control mode, the user device only needs to log in the hub device to control each registered device, and does not need to establish a connection with each registered device one by one, which can effectively reduce the operation steps of the user and improve the user experience.

[0418] Exemplarily, in the front-end scene, before the house is delivered, the installation and maintenance personnel can log in the hub device with the installation and maintenance device to obtain the operation permission of each registered device. Then, the installation and maintenance personnel can control each registered device through the installation and maintenance device or the hub device to debug the performance of each registered device and configure the information of each registered device. After the house is delivered, before the householder opens the home Internet line, the householder can log in the hub device with his own personal device (for example, the householder's mobile phone) to obtain the operation permission of each registered device. Then, the householder can control each registered device through his own personal device or the hub device.

[0419] 5. Proxy registration.

[0420] When the routing device accesses the Internet line, the electronic devices in the local area network can access the Internet through the routing device.

[0421] At this time, the user can perform a device delivery operation on the user device to register the hub device and the registered device to the smart home platform.

[0422] The above device delivery operation can be understood as an operation of registering the whole-house smart home device to the user account of the householder after the house is delivered.

[0423] ​Specifically, when the user equipment detects the device delivery operation of the user, the user equipment can perform a multicast operation in the local area network, and scan the unregistered electronic device.

[0424] The specific form of the device delivery operation described above can be set according to actual needs. For example, in some embodiments, the device delivery operation described above can be that the user equipment starts a specific application (APP); in other embodiments, the device delivery operation described above can be that the user equipment scans a specific two-dimensional code and reads specific device information from the two-dimensional code; in other embodiments, the device delivery operation described above can be that the user equipment contacts a specific device NFC tag and reads specific device information from the NFC tag; in other embodiments, the device delivery operation described above can also take other forms. The embodiments of the present application do not limit the specific form of the device delivery operation described above.

[0425] In the process of multicast scanning of the user equipment, since the registered device has been registered to the hub device, the registered device can not respond to the multicast operation of the user equipment.

[0426] The hub device and the unregistered smart home device (hereinafter collectively referred to as the to-be-registered device) have not been registered, so the to-be-registered device can send the device information of the device to the user equipment in response to the multicast scanning operation of the user equipment.

[0427] The content of the device information described above can be set according to actual needs. For example, the device information described above can include one or more of product identification (prodId), SN code, MAC address and the like.

[0428] After receiving the device information of the to-be-registered device, the user equipment can determine the to-be-registered device according to the device information described above, send a second registration request to the smart home platform, and receive the second registration parameter returned by the smart home platform. The second registration parameter can include a second registration code.

[0429] Optionally, the second registration parameter described above can also include a second device identifier. After the registration of the to-be-registered device is passed, the second device identifier described above can serve as the identity of the to-be-registered device.

[0430] Among them, one to-be-registered device corresponds to one second device identifier and one second registration code.

[0431] Then, the user equipment can issue the second registration parameter and the platform identifier of the smart home platform to each of the to-be-registered devices. The platform identifier is used to find the smart home platform, and the content contained therein can be set according to actual needs. For example, in some embodiments, the platform identifier can include the uniform resource locator (URL) of the smart home platform.

[0432] When the to-be-registered device receives the second registration parameter and the platform identifier, the to-be-registered device can access the smart home platform according to the platform identifier, and send the second registration code to the smart home platform.

[0433] When the smart home platform receives the second registration code, the smart home platform can verify the received second registration code according to the issued second registration code.

[0434] If the issued second registration code is consistent with the received second registration code, it means that the verification is passed, and the smart home platform can bind the to-be-registered device to the first user account currently logged in by the user equipment, and send the second credential information to the to-be-registered device, thereby completing the registration process.

[0435] If the issued second registration code is inconsistent with the received second registration code, it means that the verification is not passed, and the smart home platform can refuse to register the to-be-registered device.

[0436] In some embodiments, after the hub device is registered to the smart home platform, the hub device can further send a third registration request to the smart home platform to register the registered devices.

[0437] After the smart home platform receives the third registration request, the smart home platform can bind the registered devices to the first user account, and issue the third device identifier and the third credential information corresponding to the registered devices to the hub device. One registered device corresponds to one third device identifier and one third credential information.

[0438] After the hub device receives the third device identifier and the third credential information corresponding to the registered devices, the hub device can issue the third device identifier and the third credential information to the corresponding registered devices, and update the locally stored first device identifier and the first credential information with the third device identifier and the third credential information.

[0439] When the registered device receives the third device identifier and the third credential information, the registered device can update the locally stored first device identifier and the first credential information with the third device identifier and the third credential information.

[0440] Exemplarily, as Figure 14As shown, it is assumed that the device registration system includes a home hub 51, a mobile phone 52, and a smart home device 53.

[0441] In this example, the home hub 51 can be understood as a hub device, and the mobile phone 52 can be understood as a user device. Both the home hub 51 and the mobile phone 52 are provided with a Near Field Communication (NFC) function. The mobile phone 52 and the home hub 51 are in the same local area network, and the smart home device 53 in the local area network has been registered to the home hub 51.

[0442] After the routing device accesses the online line, the local area network can access the Internet. As shown, Figure 15 If a user wants to register the home hub 51 and the smart home device 53 to a first user account, the user can perform a device delivery operation on the mobile phone 52, for example, by tapping the NFC tag of the home hub 51 with the mobile phone 52. The first user account is the user account currently logged in by the mobile phone 52.

[0443] During the contact between the home hub 51 and the mobile phone 52, the home hub 51 and the mobile phone 52 can discover each other and establish an NFC connection.

[0444] In some embodiments, the home hub 51 can send a product identification (prodId) and a device number to the mobile phone 52 through the NFC connection. In some embodiments, the device number can be composed of the SN code and / or the MAC address of the home hub 51.

[0445] After receiving the prodId and the device number, the mobile phone 52 can identify the device type corresponding to the prodId.

[0446] In some embodiments, when the mobile phone 52 identifies that the device type corresponding to the prodId is a “home hub”, the mobile phone 52 can detect whether the home hub 51 has been registered to the first user account according to the device number.

[0447] Specifically, the prodId can be a code used to identify the product model of an electronic device. Therefore, the mobile phone 52 can query the device type to be a “home hub” according to the obtained prodId. The mobile phone 52 is pre-configured with a registration process for devices of the “home hub” type. Therefore, the mobile phone 52 can execute the registration process in response to obtaining the prodId of the home hub 51. In the registration process, the mobile phone 52 can first detect whether the home hub 51 has been registered to the first user account according to the device number of the home hub 51.

[0448] If the home hub 51 has been registered under the first user account, the mobile phone 52 can directly open the whole house control interface corresponding to the home hub 51.

[0449] If the home hub 51 has not been registered under the first user account, the mobile phone 52 can enter the handover process.

[0450] Suppose the home hub 51 has not been registered. At this time, the mobile phone 52 detects that the home hub 51 has not been registered under the first user account, and the mobile phone 52 can enter the handover process.

[0451] Figure 16 An exemplary device interaction diagram of an implementation of the mobile phone 52 registering the home hub 51 and the smart home device 53 to the smart home platform 54 in the cloud is shown. Figure 14 In the scenario shown, a device interaction diagram of an implementation of the mobile phone 52 registering the home hub 51 and the smart home device 53 to the smart home platform 54 in the cloud is shown.

[0452] In the handover process, the mobile phone 52 can multicast scan unregistered electronic devices in the local area network, such as the home hub 51 and the smart home device 53. Figure 16 As shown in step S1601.

[0453] Since the smart home device 53 has been registered under the home hub 51, the smart home device 53 can not respond to the multicast operation of the mobile phone 52, as shown in step S1602. Figure 16

[0454] Since the home hub 51 has not been registered, the home hub 51 can send registration response information to the mobile phone 52, as shown in step S1603. In some embodiments, the registration response information can include device information of the home hub 51. Figure 16

[0455] After receiving the registration response information, the mobile phone 52 can determine the home hub 51 as a to-be-registered device according to the device information of the home hub 51. Then, the mobile phone 52 can send a second registration request to the smart home platform 54, as shown in step S1604. Figure 16

[0456] After receiving the second registration request, the smart home platform 54 can generate a second registration parameter and return the second registration parameter to the mobile phone 52, as shown in step S1605. In some embodiments, the second registration parameter can include a second registration code. Figure 16

[0457] Optionally, the second registration parameter can also include a second device identifier. When the home hub 51 is registered, the second device identifier can serve as an identity identifier of the home hub 51.

[0458] ​​​​The mobile phone 52 can transmit second registration information to the home hub 51 after receiving the second registration parameter, such as Figure 16 As shown in step S1606.

[0459] The second registration information can include the second registration parameter and a platform identifier of the smart home platform 54. In some embodiments, the platform identifier of the smart home platform 54 can include a URL of the smart home platform 54.

[0460] After the home hub 51 receives the second registration information, the home hub 51 can access the smart home platform 54 according to the second registration information (e.g., the URL).

[0461] In some embodiments, in order to improve the security of communication, the home hub 51 can negotiate a fourth session key with the smart home platform 54 according to the second registration code, and establish a fourth secure connection, such as Figure 16 As shown in step S1607.

[0462] Then, the home hub 51 can send the second registration code to the smart home platform 54 through the fourth secure connection, such as Figure 16 As shown in step S1608.

[0463] After the smart home platform 54 receives the second registration code sent by the home hub 51, the smart home platform 54 can verify the received second registration code according to the second registration code issued, such as Figure 16 As shown in step S1609. The verification can include: the smart home platform 54 judges whether the second registration code received by the smart home platform 54 in step S1608 is the same as the second registration code generated by the smart home platform 54 in step S1605. Through the above verification process, it can be ensured that the electronic device registered to the smart home platform 54 is the home hub 51, avoiding the situation that other electronic devices are maliciously registered, and improving the security of device registration.

[0464] When the second registration code received by the smart home platform 54 in step S1608 is the same as the second registration code generated by the smart home platform 54 in step S1605, it means that the verification is passed, and the smart home platform 54 can bind the home hub 51 to the first user account, and issue second credential information to the home hub 51, such as Figure 16 As shown in step S1610.

[0465] At this point, by executing steps S1601-S1610, the process of registering the home hub 51 to the smart home platform 54 can be completed. Next, the process of registering the smart home device 53 to the smart home platform 54 is performed.

[0466] In some embodiments, after receiving the second credential information, the home host 51 can negotiate a fifth session key with the smart home platform 54 according to the second credential information, establish a fifth secure connection, and send a third registration request to the smart home platform 54 through the fifth secure connection, as shown in Figure 16 In step S1611.

[0467] In some embodiments, the home host 51 can also send a third registration request to the smart home platform 54, and the third registration request is used to register the smart home device 53. Figure 16 In step S1612.

[0468] The content contained in the third registration request can be set according to actual needs. In some embodiments, the third registration request can include the number information of the smart home device 53. For example, assuming that there are three smart home devices 53 to be registered, the home host 51 can add the number information to the third registration request, and set the data information to 3. After receiving the third registration request, the smart home platform 54 can determine that there are three smart home devices 53 to be registered according to the number information in the third registration request.

[0469] In other embodiments, the third registration request can also include the device information of the smart home device 53, which can include one or more of the prodId, SN code, and MAC address information. For example, assuming that there are three smart home devices 53 to be registered, the home host 51 can add the device information of the three smart home devices 53 in the third registration request. After receiving the third registration request, the smart home platform 54 can determine that there are three smart home devices 53 to be registered according to the device information in the third registration request.

[0470] In other embodiments, the third registration request can also include other information. The embodiments of the present application do not limit the content contained in the third registration request.

[0471] In some embodiments, the home host 51 can send the third registration request to the smart home platform 54 through the fifth secure connection.

[0472] When the smart home platform 54 receives the third registration request, the smart home platform 54 can bind the above-mentioned smart home device 53 to the above-mentioned first user account, and return the third device identifier and the third credential information to the home host 51, as shown in Figure 16 In step S1613.

[0473] Among them, one smart home device 53 corresponds to one third device identifier and one third credential information.

[0474] The smart home platform 54 binding the smart home device 53 to the first user account can refer to the smart home platform 54 associating the third device identifier and the third credential information corresponding to the smart home device 53 to the first user account.

[0475] After receiving the third device identifier and the third credential information, the home hub 51 can update the first device identifier and the first credential information corresponding to the smart home device 53 using the third device identifier and the third credential information, and issue the corresponding third device identifier and the third credential information to each smart home device 53, as shown in Figure 16 The steps S1614 and S1615 are shown in the middle.

[0476] The update can refer to the home hub 51 modifying the locally recorded device identifier corresponding to the smart home device 53 from the first device identifier to the third device identifier, and modifying the locally recorded credential information corresponding to the smart home device 53 from the first credential information to the third credential information.

[0477] In some embodiments, the home hub 51 can also backup the first device identifier and the first credential information as a rollback file before updating the first device identifier and the first credential information corresponding to the smart home device 53. When needed, the home hub 51 can rollback the device identifier and the credential information corresponding to the smart home device 53 to the first device identifier and the first credential information according to the rollback file.

[0478] After receiving the third device identifier and the third credential information, the smart home device 53 can update the locally stored first device identifier and the first credential information according to the third device identifier and the third credential information, as shown in Figure 16 The step S1616 is shown in the middle.

[0479] It should be noted that in the above described steps S1613 to S1616, when there are multiple smart home devices 53 to be registered, the home hub 51 and the smart home platform 54 can register each smart home device 53 one by one, or the home hub 51 and the smart home platform 54 can also register multiple smart home devices 53 at a time.

[0480] For example, it is assumed that there are five smart home devices 53 such as smart speakers and smart large screens to be registered.

[0481] In some embodiments, after the home hub 51 sends the third registration request to the smart home platform 54, the smart home platform 54 can return a third device identifier and a third credential information, and bind the third device identifier and the third credential information to the first user account.

[0482] The home host 51 can update the first device identifier and the first credential information of the smart speaker with the third device identifier and the third credential information, and distribute the third device identifier and the third credential information to the smart speaker.

[0483] Then, the home host 51 can send a second third registration request, and the smart home platform 54 can return a second third device identifier and a second third credential information after receiving the second third registration request.

[0484] The home host 51 can update the first device identifier and the first credential information of the smart screen with the second third device identifier and the second third credential information, and distribute the second third device identifier and the second third credential information to the smart screen.

[0485] By analogy, the home host 51 and the smart home platform 54 can repeat the above steps to register each smart home device 53 one by one until all the smart home devices 53 are registered on the smart home platform 54.

[0486] In other embodiments, the third registration request sent by the home host 51 to the smart home platform 54 can include the device information of the five smart home devices 53.

[0487] After receiving the third registration request, the smart home platform 54 can determine the number of smart home devices 53 to be 5 according to the device information in the third registration request. At this time, the smart home platform can return 5 third device identifiers and 5 third credential information to the home host, and inform the third device identifier and the third credential information corresponding to each device information. Among them, the device information of one smart home device 53 corresponds to one third device identifier and one third credential information.

[0488] After receiving the multiple third device identifiers and the third credential information, the home host 51 can update the first device identifier and the first credential information of each smart home device 53 to its corresponding third device identifier and third credential information, and distribute its corresponding third device identifier and third credential information to the smart home device 53.

[0489] In some embodiments, since the above-mentioned third secure connection is established based on the first credential information, after the credential information of the smart home device 53 is changed to the third credential information, the smart home device 53 and the home host 51 may not be able to communicate through the above-mentioned third secure connection. Therefore, the smart home device 53 can negotiate a sixth session key with the home host 51 according to the third credential information, establish a sixth secure connection, and restore trusted communication with the home host 51, as shown in step S1617 of Figure 16

[0490] ​In some embodiments, after the home hub 51 and the smart home device 53 are registered to the first user account, the smart home platform 54 can send a registration success notification to the mobile phone 52, as shown in Figure 16 In step S1618.

[0491] In some embodiments, after receiving the registration success notification, the mobile phone 52 can add a control of the home hub 51 and a control of the smart home device 53 in the whole-house control interface 521, as shown in Figure 16

[0492] After that, the user can control the home hub 51 and the smart home device 53 by operating the controls 522 and 523.

[0493] It should be noted that in the case where the smart home device 53 is registered to the home hub 51, the user can only control the mobile phone 52 to access the local area network and log in to the home hub 51 to obtain the operation permission of the smart home device 53 in the home area.

[0494] However, in the case where the home hub 51 and the smart home device 53 are both registered to the first user account, if the mobile phone 52 is logged in to the first user account, the user can control the home hub 51 and the smart home device 53 in the local area network through the mobile phone 52 after the mobile phone 52 accesses the local area network; or the user can also access the smart home platform 54 through the mobile phone 52 when the mobile phone 52 does not access the local area network, and control the home hub 51 and the smart home device 53 through the smart home platform 54.

[0495] That is to say, in the case where the home hub 51 and the smart home device 53 are both registered to the first user account, the user can control the home hub 51 and the smart home device 53 in the home area in close range, or the user can also control the home hub 51 and the smart home device 53 remotely outside the home area.

[0496] As can be seen from the above example, when the local area network can access the Internet, the user device can register the unregistered device in the local area network to the smart home platform in response to the device delivery operation of the user.

[0497] The unregistered device includes the hub device. After being registered to the smart home platform, the hub device can automatically perform proxy registration to register the registered device to the smart home platform.

[0498] Through the above method, the user only needs to perform the device delivery operation once to register the hub device and the registered device to the smart home platform, without the need to register the hub device and the registered device one by one, which is simple to operate and can effectively improve the user experience. ​

[0499] Exemplarily, in the pre-installation stage, before the house is delivered, the installation and maintenance personnel can use the installation and maintenance equipment (for example, the mobile phone of the installation and maintenance personnel) to register various smart home devices (for example, lighting lamps, smart door locks, smart curtains, alarms) in the house to the hub device.

[0500] After the house is delivered, if the householder opens a home Internet line, the householder can perform a device delivery operation on the personal device (for example, the mobile phone of the householder) of the householder. At this time, the personal device of the householder can register the hub device and other unregistered smart home devices in the local area network to the smart home platform, and bind the hub device and other unregistered smart home devices to the first user account currently logged in by the personal device of the householder.

[0501] After the hub device is registered to the first user account, the hub device can automatically register various registered devices to the first user account on behalf of the various registered devices.

[0502] That is, through the device registration method provided in the embodiments of the present application, the installation and maintenance personnel can register various smart home devices to the hub device one by one, and help the user to complete most of the device registration operations in advance. After the householder opens a home Internet line, the householder only needs to perform a device delivery operation once, so as to register the hub device and the registered devices to the first user account, without the householder registering the hub device and the registered devices one by one, which greatly simplifies the registration operation of the householder, can effectively improve the use experience of the householder, and has strong ease of use and practicality.

[0503] 6. Cancel registration.

[0504] When the user needs to change the first user account bound by the hub device and the registered devices, the user can send a state recovery instruction to the hub device through the user device, or the user can directly input the state recovery instruction on the hub device.

[0505] When the hub device obtains the state recovery instruction, the hub device can send a first unbinding instruction to the smart home platform. The first unbinding instruction can include a third device identifier of the registered device, and the first unbinding instruction is used to instruct the smart home platform to unbind the registered device from the first user account.

[0506] When the smart home platform receives the first unbinding instruction, the smart home platform can determine the registered device that needs to be unbound according to the third device identifier, and unbind the registered device from the first user account.

[0507] And the central device can delete the third device identifier and the third credential information issued by the smart home platform, fall back to the first device identifier and the first credential information, and issue the first device identifier and the first credential information to the registered device.

[0508] After the registered device receives the first device identifier and the first credential information, the registered device can update the locally stored third device identifier and the third credential information with the first device identifier and the first credential information.

[0509] In some embodiments, the central device can further send a second unbinding instruction to the smart home platform. The second unbinding instruction includes a second device identifier of the central device, and the second unbinding instruction is used to instruct the smart home platform to unbind the central device from the first user account.

[0510] When the smart home platform receives the second unbinding instruction, the smart home platform can determine the central device that needs to be unbound according to the second device identifier, and unbind the central device from the first user account.

[0511] Then, the central device can clear the information related to the first user account and fall back to the state before registration.

[0512] After that, if the user wants to bind the central device and the registered device to other user accounts, the user can change the user account and register the central device and the registered device to the other user accounts according to the content described in Section 3.

[0513] For example, referring to the previous example, assume that the user wants to rent the house to a tenant, but the home hub 51 and the smart home device 53 in the house are registered to the first user account of the user and can only be used by the first user account.

[0514] At this time, in order to transfer the control right of the home hub 51 and the smart home device 53, the user can operate the mobile phone 52 to enter the whole-house control interface 521 as shown in Figure 17

[0515] As shown in Figure 17 , the user can long press the control of the home hub 522. In some embodiments, the mobile phone 52 can display a “remove” option above the control 522 in response to the operation of the user.

[0516] After the user clicks the “remove” option, the mobile phone 52 can enter the unbinding process in response to the operation of the user.

[0517] Figure 18 For example, it is shown that in Figure 19 ​A device interaction diagram of one implementation of the scenario in which the mobile phone 52 unbinds the home hub 51 and the smart home device 53 from the first user account.

[0518] In the unbinding process, the mobile phone 52 can send a state recovery instruction to the home hub 51, as shown in step S1901 in FIG. 19. Figure 14

[0519] When the home hub 51 receives the state recovery instruction, the home hub 51 can send a first unbinding instruction to the smart home platform 54, as shown in step S1902 in FIG. 19. The first unbinding instruction includes the third device identifier of each smart home device 53. Figure 19

[0520] After the smart home platform 54 receives the first unbinding instruction, the smart home platform 54 can unbind each smart home device 53 from the first user account, as shown in step S1903 in FIG. 19. Figure 19

[0521] Then, the home hub 51 can delete the locally stored third device identifier and third credential information, restore the first device identifier and the first credential information, and issue the corresponding first device identifier and first credential information to each smart home device 53, as shown in steps S1904 and S1905 in FIG. 19. Figure 19

[0522] After the smart home device 53 receives the first device identifier and the first credential information, the smart home device 53 updates the locally stored third device identifier and third credential information according to the first device identifier and the first credential information, as shown in step S1906 in FIG. 19. Figure 19

[0523] In some embodiments, the smart home device 53 can establish a seventh secure connection with the home hub 51 according to the first credential information, as shown in step S1907 in FIG. 19. Figure 19

[0524] At this point, the process of unbinding the smart home device 53 from the first user account is completed.

[0525] In some embodiments, next, the process of unbinding the home hub 51 from the first user account can also be further performed.

[0526] In some embodiments, the home hub 51 can also send a second unbinding instruction to the smart home platform 54 and delete the locally stored second device identifier and second credential information, as shown in steps S1908 and S1909 in FIG. 19. The second unbinding instruction can include the second device identifier of the home hub 51. Figure 19

[0527] ​​​​​​​After the smart home platform 54 receives the second unbinding instruction, the home hub 51 can be unbound from the first user account, as shown in FIG. 9. Figure 19 As shown in step S1910.

[0528] At this time, the home hub 51 and the smart home device 53 are restored to the state before the handover process.

[0529] As shown in FIG. 10, after the tenant moves in, if the tenant wants to register the home hub 51 and the smart home device 53 under the second user account, the tenant can perform a device handover operation on the mobile phone 55, for example, tap the mobile phone 55 with the home hub 51. The mobile phone 55 is the user device of the tenant, and the second user account is the user account currently logged in by the mobile phone 55. Figure 19

[0530] At this time, the mobile phone 55 can register the home hub 51 and the smart home device 53 in the second user account according to the process described in the previous example.

[0531] As can be seen from the above examples, when the user wants to unbind the hub device and the registered device from the first user account, the hub device can proxy the unbinding of each registered device, without the user having to operate each registered device one by one, simplifying the unbinding process of the registered device, reducing the operation steps of the user, and improving the user experience.

[0532] In summary, in the device registration method of the embodiments of the present application, when the smart home device cannot access the Internet, the user device can register the smart home device to the hub device as an edge server.

[0533] After that, the user can directly or indirectly operate the hub device to manage each registered device, reducing the difficulty of device management and improving the user experience.

[0534] Moreover, after the hub device and the smart home device can access the Internet, the user can perform a device handover operation. At this time, the hub device can proxy the registration of the registered device and automatically register each registered device to the smart home platform, without the user having to register each registered device one by one, greatly reducing the process steps of device registration.

[0535] In addition, when the user wants to unbind the hub device and the registered device from the first user account, the hub device can proxy the unbinding of each registered device, which is simple to operate and does not require the user to unbind each registered device one by one, greatly reducing the process steps of device deregistration.

[0536] ​Further, the hub device can re-register each registered device to the hub device in the process of unbinding. After that, the user can continue to manage each registered device through the hub device, or the hub device and the registered device can be quickly registered to another user account through the above house delivery process.

[0537] It should be understood that the size of the serial number of each step in the above embodiment does not mean the order of execution, and the execution order of each process should be determined according to its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0538] Further, the steps described in the above embodiments are not all necessary steps. In actual application scenarios, the device registration method can have more or fewer steps than the above embodiments, or implement part of the steps described above.

[0539] For example, in some embodiments, the hub device can not set an identity verification link, and any user device can directly access the hub device without logging in; in other embodiments, the hub device and the smart home platform can directly use the registration code as the credential information in the registration process, without generating and issuing the credential information after verification; in other embodiments, the electronic device can not negotiate a session key in the process of establishing a connection, and directly perform data interaction through an unencrypted connection; in other embodiments, the above electronic device can also add corresponding step processes according to new functions.

[0540] In addition, in the above embodiments, the user devices described in each chapter can be the same user device, and / or can also be different user devices. For example, in some scenarios, the user devices described in each chapter above can all be user devices of installers; in other scenarios, the installer can register the smart home device to the hub device through the method described in section 3, and after the homeowner moves in, the homeowner can implement the methods described in sections 4, 5, and 6 through his own user device. In this scenario, the user devices described in each chapter above are not the same user device.

[0541] Another device registration method provided by the embodiments of the present application will be described in detail from the perspective of the hub device. Please refer to Figure 20 The device registration method provided by the present embodiment includes:

[0542] S2101, in response to the first registration request sent by the first user device, sending a first registration code to the above first user device.

[0543] It should be noted that in the case that the smart home device cannot communicate with the server, and / or the user has not determined which user account the smart home device should be registered under, if the user wants to manage the smart home devices collectively, the user can register the smart home device to the hub device as an edge server.

[0544] Specifically, the user can perform a device registration operation on the first user device. In response to the device registration operation of the user, the first user device can determine the target device to be registered, and send a first registration request to the hub device.

[0545] The hub device can send a first registration code to the first user device in response to the first registration request.

[0546] S2102, after receiving the first registration code sent by the target device, the target device is registered to the hub device.

[0547] It should be noted that the first user device can forward the first registration code to the target device after receiving the first registration code.

[0548] The target device can send the first registration code to the hub device after receiving the first registration code forwarded by the first user device.

[0549] The hub device can register the target device to the hub device after receiving the first registration code sent by the target device.

[0550] The process of the first user device registering the target device to the hub device can be understood as the process of the first user device granting the operation permission of the target device to the hub device. The hub device registering the target device to the hub device can be understood as the hub device registering the operation permission of the target device on the hub device.

[0551] Therefore, after the first user device assists the hub device to register each target device to the hub device, the hub device can obtain the operation permission of each registered device, and the user can manage each registered device through the hub device.

[0552] Exemplarily, in the front-end scenario (i.e. the application scenario of installing some smart home devices in the decoration stage before the house is delivered to the occupant), the home area has not been connected to the Internet line, and the maintenance personnel also cannot know the user account of the occupant. In this case, the maintenance personnel can use their own user device to register each smart home device to the hub device through the above method.

[0553] Then, the maintenance personnel or other users can manage each smart home device registered to the hub device through the hub device.

[0554] S2103, receiving a second registration code sent by a second user equipment; wherein the second user equipment is the same user equipment as the first user equipment or is a different user equipment.

[0555] It should be noted that after the smart home device can communicate with the server and the specified user account is determined, the user can want to register the hub device and the registered device to the server.

[0556] At this time, the user can perform a device delivery operation on the second user equipment logged in the first user account. The second user equipment can send a second registration request to the server in response to the device delivery operation of the user.

[0557] The server can send a second registration code to the second user equipment after receiving the second registration request.

[0558] The second user equipment receives the second registration code and forwards the second registration code to the hub device.

[0559] S2104, according to the second registration code, registering the hub device to the server.

[0560] It should be noted that the hub device can register the hub device to the server after receiving the second registration code.

[0561] Specifically, the hub device can send the second registration code to the server after receiving the second registration code.

[0562] The server can register the hub device to the server after receiving the second registration code sent by the hub device.

[0563] S2105, after the hub device is registered to the server, registering the registered device to the server; wherein the registered device includes the target device that has been registered to the hub device.

[0564] It should be noted that after the hub device is registered to the server, the hub device can also register the registered device to the server.

[0565] Specifically, the hub device can send a third registration request to the server to register the registered device to the server through the third registration request.

[0566] Wherein, the hub device registers the hub device and the registered device to the server, which can be understood as that the hub device registers the operation permission of the hub device and the registered device under the first user account of the server. The first user account is the user account currently logged in by the second user equipment.

[0567] After the central device and the registered device are registered to the server, the first user account has the operation authority of the central device and the registered device, and the second user device or other user device logged in the first user account can control the central device and the registered device through the first user account.

[0568] The first user device and the second user device can be the same user device or different user devices.

[0569] When the first user device and the second user device are different user devices, the user using the second user device only needs to register the central device to the server, and the central device can automatically register the registered device to the server, without the user using the second user device registering each registered device to the server one by one, greatly reducing the operation that the user needs to perform, and effectively improving the user experience, having strong ease of use and practicality.

[0570] Exemplarily, in the pre-installation scenario, the first user device can be a user device of an installation and maintenance personnel, and the second user device can be a user device of a householder.

[0571] Before the house is delivered, the installation and maintenance personnel can use the first user device to help the householder register each smart home device of the pre-installation to the central device.

[0572] After the house is delivered, the householder can use the second user device of his own to register the central device to the server.

[0573] After the central device is registered to the server, the central device can automatically register the registered device to the server, without the householder registering each registered device one by one, greatly reducing the workload of the householder, thereby effectively improving the user experience of the householder.

[0574] Optionally, the method further comprises:

[0575] After the state recovery instruction is acquired, the server is instructed to cancel the registration relationship between the central device and the server, and / or the registration relationship between the registered device and the server.

[0576] It should be noted that when the user wants to cancel the registration relationship between the central device and / or the registered device and the server, the user device can directly operate the central device to trigger the state recovery instruction, or the user can also send the state recovery instruction to the central device through the user device of his own.

[0577] After the central device acquires the state recovery instruction, the central device can instruct the server to cancel the registration relationship between the central device and the server, and / or the registration relationship between the registered device and the server.

[0578] Optionally, the indication to the server to cancel the registration relationship between the hub device and the server, and / or the registration relationship between the registered device and the server comprises:

[0579] sending a first unbinding instruction to the server, the first unbinding instruction being used to instruct the server to cancel the registration relationship between the registered device and the server;

[0580] after the registration relationship between the registered device and the server is cancelled, sending a second unbinding instruction to the server, the second unbinding instruction being used to instruct the server to cancel the registration relationship between the hub device and the server.

[0581] It should be noted that, in addition to being able to proxy the registered device to register, the hub device can also proxy the registered device to cancel the registration relationship.

[0582] After the hub device obtains the state recovery instruction, the hub device can send a first unbinding instruction to the server.

[0583] After the server receives the first unbinding instruction, the server can cancel the registration relationship between the registered device and the server.

[0584] After the registration relationship between the registered device and the server is cancelled, the hub device can send a second unbinding instruction to the server.

[0585] After the server receives the second unbinding instruction, the server can cancel the registration relationship between the hub device and the server.

[0586] That is to say, when the user wants to cancel the registration relationship between each registered device and the server, the user only needs to issue a state recovery instruction to the hub device, and the hub device can automatically cancel the registration relationship between the hub device and the registered device and the server, without the user needing to cancel the registration relationship between the hub device and the registered device and the server one by one, greatly reducing the operations that the user needs to perform and effectively improving the user's use experience.

[0587] Optionally, after the first unbinding instruction is sent to the server, the method further comprises:

[0588] recovering the registration relationship between the hub device and the registered device.

[0589] It should be noted that, in some embodiments, the registered device can only maintain one registration relationship.

[0590] In this scenario, when the registered device registers with the server, the registration relationship between the hub device and the registered device is cancelled.

[0591] Therefore, the hub device can restore the registration relationship between the hub device and the registered device after the registration relationship between the registered device and the server is released.

[0592] Then, the user can conveniently register the hub device and the registered device to another user account of the server as a whole through the above device registration method, reduce the user's operation of re-registering the hub device and the registered device, and improve the user's experience.

[0593] For example, when a house owner wants to rent the house to a tenant, the house owner needs to transfer the operation authority of the hub device and the registered device to the tenant.

[0594] At this time, the house owner can issue a state recovery instruction to the hub device. The hub device can release the registration relationship between the registered device and the hub device and the server according to the state recovery instruction, and restore the registration relationship between the hub device and the registered device.

[0595] After that, the tenant can use his own user device to register the hub device on the server, and bind the hub device to the user account of the tenant.

[0596] After the hub device is registered to the user account of the tenant, the hub device can automatically register the registered device to the user account of the tenant.

[0597] That is to say, through the above method, the house owner and the tenant can conveniently migrate the operation authority of the hub device and the registered device to another user account as a whole, without the tenant registering the hub device and the registered device one by one, greatly reducing the operation of the tenant and improving the experience of the tenant.

[0598] Optionally, after the above-mentioned target device is registered to the above-mentioned hub device, the method further comprises:

[0599] Receiving control information sent by a third user device, the control information comprising a device identifier of a registered device to be controlled and a control instruction;

[0600] Forwarding the control instruction to the registered device corresponding to the device identifier.

[0601] It should be noted that after the registered device is registered to the hub device, the user can directly send control information to the hub device through his own user device to control each registered device through the hub device.

[0602] At this time, the user can perform a control operation on the third user device. The third user device determines the registered device to be controlled and the control instruction in response to the control operation. The control instruction is used to instruct the registered device to be controlled to perform the operation specified by the user.

[0603] Then, the third user device can send control information to the hub device, the control information can include the device identification of the registered device to be controlled and the control instruction.

[0604] After the hub device receives the control information, the hub device can forward the control instruction to the registered device corresponding to the device identification.

[0605] After the registered device to be controlled receives the control instruction, the registered device to be controlled can execute the operation corresponding to the control instruction.

[0606] Optionally, after the target device is registered to the hub device, the method further includes:

[0607] In response to the control operation of the user, determining the registered device to be controlled and the control instruction;

[0608] Sending the control instruction to the registered device to be controlled.

[0609] It should be noted that after the registered device is registered to the hub device, the user can also directly control each registered device through the hub device.

[0610] At this time, the user can directly perform a control operation on the hub device. The hub device determines the registered device to be controlled and the control instruction in response to the control operation.

[0611] Then, the hub device can send the control instruction to the registered device to be controlled.

[0612] After the registered device to be controlled receives the control instruction, the registered device to be controlled can execute the operation corresponding to the control instruction.

[0613] It should be understood that the size of the serial number of each step in the above embodiment does not mean the order of execution, and the execution order of each process should be determined according to its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0614] Another device registration method provided by the embodiments of the present application will be described in detail from the perspective of a device registration system. Please refer to Figure 21 The device registration method provided by the embodiments of the present application includes:

[0615] S2201, with the assistance of the first user device, the hub device registers the target device to the hub device;

[0616] It should be noted that in the scenario where the smart home device cannot communicate with the server and / or the user has not determined which user account the smart home device should be registered to, if the user wants to manage each smart home device in an overall manner, the user can register the smart home device to the hub device as an edge server.

[0617] At this time, the hub device can register the target device to the hub device with the assistance of the first user device.

[0618] S2202, the hub device registers the hub device to the server with the assistance of the second user device; wherein the second user device and the first user device are the same user device or different user devices;

[0619] It should be noted that the smart home device can communicate with the server, and after the user determines the first user account, the hub device can register the hub device to the server with the assistance of the second user device.

[0620] The first user account is a user account specified by the user, and can also be understood as the user account currently logged in by the second user device.

[0621] S2203, after the hub device registers the hub device to the server, the hub device registers the registered device to the server; wherein the registered device includes the target device that has been registered to the hub device.

[0622] It should be noted that after the hub device is registered to the server, the hub device can register the registered device to the server by proxying the registered device.

[0623] The first user device and the second user device can be the same user device or different user devices.

[0624] When the first user device and the second user device are different user devices, the user using the second user device only needs to register the hub device to the server, and the hub device can automatically register the registered device to the server, without the user using the second user device registering each registered device to the server one by one, greatly reducing the operation that the user needs to perform, and can effectively improve the user's use experience, has strong ease of use and practicality.

[0625] Optionally, the method further comprises:

[0626] After the hub device obtains the state recovery instruction, the hub device instructs the server to cancel the registration relationship between the hub device and the server, and / or the registration relationship between the registered device and the server.

[0627] It should be noted that when the user wants to cancel the registration relationship between the hub device and / or the registered device and the server, the user device can directly operate the hub device to trigger the state recovery instruction, or the user can also send the state recovery instruction to the hub device through the user device.

[0628] After the hub device obtains the state recovery instruction, the hub device can instruct the server to cancel the registration relationship between the hub device and the server, and / or register the device and the server.

[0629] Optionally, in the process of registering the target device to the hub device with the assistance of the first user device, the hub device specifically comprises the following steps:

[0630] The first user device determines the target device to be registered in response to the device registration operation of the user, and sends a first registration request to the hub device.

[0631] The hub device sends a first registration code to the first user device in response to the first registration request, and the first user device sends the first registration code to the target device.

[0632] The target device sends the first registration code to the hub device, and the hub device registers the target device to the hub device in response to receiving the first registration code.

[0633] It should be noted that in the process of registering the target device to the hub device, the user can perform a device registration operation on the first user device. In response to the device registration operation of the user, the first user device can determine the target device to be registered and send a first registration request to the hub device.

[0634] The hub device can send a first registration code to the first user device in response to the first registration request.

[0635] The first user device can forward the first registration code to the target device after receiving the first registration code.

[0636] The target device can send the first registration code to the hub device after receiving the first registration code forwarded by the first user device.

[0637] The hub device can register the target device to the hub device after receiving the first registration code sent by the target device.

[0638] The process of registering the target device to the hub device by the first user device can be understood as the process of granting the operation permission of the target device to the hub device by the first user device. The process of registering the target device to the hub device by the hub device can be understood as the process of registering the operation permission of the target device on the hub device.

[0639] Therefore, after the first user device assists the hub device to register each target device to the hub device, the hub device can obtain the operation permission of each registered device, and the user can manage each registered device through the hub device.

[0640] Exemplarily, in a front-loaded scenario (a scenario in which some smart home devices are installed in a house before it is delivered to a user, i.e., in a decoration stage), the home area has not been connected to an online line, and it is difficult for a maintenance personnel to know the user account of the user. In this scenario, the maintenance personnel can register the smart home devices to the hub device using the user device of the maintenance personnel by using the above method.

[0641] Subsequently, the maintenance personnel or other users can manage the smart home devices registered to the hub device through the hub device.

[0642] Optionally, the hub device is registered to the server by the hub device and the second user device, and the registration of the hub device to the server by the hub device and the second user device specifically includes:

[0643] The second user device sends a second registration request to the server in response to a device delivery operation of the user;

[0644] The server sends a second registration code to the second user device in response to the second registration request, and the second user device sends the second registration code to the hub device;

[0645] The hub device registers the hub device to the server in response to receiving the second registration code.

[0646] It should be noted that, in the process of registering the hub device to the server, the user can perform a device delivery operation on the second user device logged in the first user account. The second user device can send a second registration request to the server in response to the device delivery operation of the user.

[0647] The server can send a second registration code to the second user device after receiving the second registration request.

[0648] The second user device forwards the second registration code to the hub device after receiving the second registration code.

[0649] The hub device can send the second registration code to the server after receiving the second registration code.

[0650] The server can register the hub device to the server after receiving the second registration code sent by the hub device.

[0651] Optionally, after obtaining the state recovery instruction, the hub device instructs the server to cancel the registration relationship between the hub device and the server, and / or the registration relationship between the registered device and the server, and the cancellation of the registration relationship between the hub device and the server by the hub device and the server specifically includes:

[0652] The central device sends a first unbinding instruction to the server after obtaining the state recovery instruction.

[0653] The server cancels the registration relationship between the registered device and the server in response to the first unbinding instruction.

[0654] The central device sends a second unbinding instruction to the server after canceling the registration relationship between the registered device and the server.

[0655] The server cancels the registration relationship between the central device and the server in response to the second unbinding instruction.

[0656] It should be noted that the central device can not only proxy the registered device to register, but also proxy the registered device to cancel the registration relationship.

[0657] The central device can send a first unbinding instruction to the server after obtaining the state recovery instruction.

[0658] The server can cancel the registration relationship between the registered device and the server after receiving the first unbinding instruction.

[0659] The central device can send a second unbinding instruction to the server after canceling the registration relationship between the registered device and the server.

[0660] The server can cancel the registration relationship between the central device and the server after receiving the second unbinding instruction.

[0661] That is to say, when the user wants to cancel the registration relationship between each registered device and the server, the user only needs to issue a state recovery instruction to the central device, and the central device can automatically cancel the registration relationship between the central device and the registered device and the server, without the user canceling the registration relationship between the central device and the registered device and the server one by one, greatly reducing the operation that the user needs to perform, and effectively improving the user experience.

[0662] Optionally, after the first unbinding instruction is sent to the server, the method further includes:

[0663] The central device restores the registration relationship between the central device and the registered device.

[0664] It should be noted that in some embodiments, the registered device can only maintain one registration relationship.

[0665] In this scenario, when the registered device registers with the server, the registration relationship between the central device and the registered device is canceled.

[0666] Therefore, the hub device can restore the registration relationship between the hub device and the registered device after the registration relationship between the registered device and the server is released.

[0667] Then, the user can conveniently register the hub device and the registered device as a whole to another user account of the server through the above device registration method, reduce the user's operation of re-registering the hub device and the registered device, and improve the user's use experience.

[0668] Optionally, after the hub device registers the target device to the hub device, the method further includes:

[0669] The third user device determines the registered device to be controlled and a control instruction in response to a control operation of the user;

[0670] The third user device sends control information to the hub device, and the control information includes the device identifier of the registered device to be controlled and the control instruction;

[0671] In response to receiving the control information, the hub device forwards the control instruction to the registered device corresponding to the device identifier.

[0672] It should be noted that after the registered device is registered to the hub device, the user can directly send control information to the hub device through the user's own user device to control each registered device through the hub device.

[0673] Optionally, after the hub device registers the target device to the hub device, the method further includes:

[0674] The hub device determines the registered device to be controlled and a control instruction in response to a control operation of the user;

[0675] The hub device sends the control instruction to the registered device to be controlled.

[0676] It should be noted that after the registered device is registered to the hub device, the user can also directly perform a control operation on the hub device to control each registered device through the hub device.

[0677] It should be understood that the size of the serial number of each step in the above embodiments does not mean the order of execution, and the execution order of each process should be determined according to its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0678] Corresponding to the device registration method described in the above embodiments, Figure 22 A structure block diagram of a device registration apparatus provided by an embodiment of the present application is shown, and only parts related to the embodiments of the present application are shown for ease of description.

[0679] The device can be applied to a hub device, referring to Figure 23 The device comprises:

[0680] The first sending module 2301 is configured to send a first registration code to the first user equipment in response to a first registration request sent by the first user equipment.

[0681] The first registration module 2302 is configured to register a target device to the hub device after receiving the first registration code sent by the target device.

[0682] The second receiving module 2303 is configured to receive a second registration code sent by a second user equipment; wherein the second user equipment and the first user equipment are the same user equipment or different user equipments.

[0683] The second registration module 2304 is configured to register the hub device to a server according to the second registration code.

[0684] The third registration module 2305 is configured to register a registration device to the server after the hub device is registered to the server; wherein the registration device comprises the target device which has been registered to the hub device.

[0685] Optionally, the device further comprises:

[0686] The registration cancellation module is configured to instruct the server to cancel the registration relationship between the hub device and the server, and / or the registration relationship between the registration device and the server after obtaining a state recovery instruction.

[0687] Optionally, the registration cancellation module comprises:

[0688] The first unbinding sub-module is configured to send a first unbinding instruction to the server, wherein the first unbinding instruction is used to instruct the server to cancel the registration relationship between the registration device and the server.

[0689] The second unbinding sub-module is configured to send a second unbinding instruction to the server after the registration relationship between the registration device and the server is cancelled, wherein the second unbinding instruction is used to instruct the server to cancel the registration relationship between the hub device and the server.

[0690] Optionally, the device further comprises:

[0691] The registration recovery module is configured to recover the registration relationship between the hub device and the registration device.

[0692] Optionally, the device further comprises:

[0693] The control receiving module is configured to receive control information sent by the third user equipment, wherein the control information comprises a device identifier of the registration device to be controlled and a control instruction.

[0694] The relay control module is configured to forward the control instruction to the registration device corresponding to the device identifier.

[0695] Optionally, the apparatus further comprises:

[0696] The control response module is configured to determine the registration device to be controlled and the control instruction in response to a control operation of the user.

[0697] The direct control module is configured to send the control instruction to the registration device to be controlled.

[0698] Those skilled in the art can clearly understand that, for the convenience and brevity of description, only the division of the above functional units and modules is exemplified, and in actual application, the above functions can be completed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated in one processing unit, or each unit can exist physically, or two or more units can be integrated in one unit, and the integrated unit can be realized in the form of hardware or in the form of software functional unit. In addition, the specific names of the functional units and modules are only for the convenience of mutual distinction, and do not limit the protection scope of the present application. The specific working process of the units and modules in the apparatus can refer to the corresponding process in the foregoing method embodiments, which will not be described here.

[0699] Corresponding to the device registration method described in the above embodiments, Figure 23 A system architecture diagram of another device registration system provided by the embodiments of the present application is shown, and only the parts related to the embodiments of the present application are shown for the convenience of description.

[0700] As Figure 24 Figure 24 shown, the system comprises a hub device 2401, a first user equipment 2402, a second user equipment 2403 and a target device 2404, and the hub device 2401 is configured to perform:

[0701] register the target device 2404 to the hub device 2401 with the assistance of the first user equipment 2402;

[0702] register the hub device 2401 to the server with the assistance of the second user equipment 2403; wherein the second user equipment 2403 and the first user equipment 2402 are the same user equipment or different user equipments;

[0703] After the central device 2401 registers the central device 2401 to the server, the registered device is registered to the server; wherein the registered device includes the target device 2404 that has been registered to the central device 2401.

[0704] Optionally, the central device 2401 is further configured to perform:

[0705] After obtaining the state recovery instruction, the server is instructed to cancel the registration relationship between the central device 2401 and the server, and / or the registration relationship between the registered device and the server.

[0706] Optionally, in the process of registering the target device 2404 to the central device 2401 with the assistance of the first user device 2402, the central device 2401 is configured to perform:

[0707] The first user device 2402 is configured to determine the target device 2404 to be registered in response to a device registration operation of a user, and send a first registration request to the central device 2401.

[0708] The central device 2401 is configured to send a first registration code to the first user device 2402 in response to the first registration request.

[0709] The first user device 2402 is further configured to send the first registration code to the target device 2404.

[0710] The target device 2404 is configured to send the first registration code to the central device 2401.

[0711] The central device 2401 is further configured to register the target device 2404 to the central device 2401 in response to receiving the first registration code.

[0712] Optionally, in the process of registering the central device 2401 to the server with the assistance of the second user device 2403, the central device 2401 is configured to perform:

[0713] The second user device 2403 is configured to send a second registration request to the server in response to a device delivery operation of a user.

[0714] The server is configured to send a second registration code to the second user device 2403 in response to the second registration request.

[0715] The second user device 2403 is further configured to send the second registration code to the central device 2401.

[0716] The hub device 2401 is configured to register the hub device 2401 to the server in response to receiving the second registration code.

[0717] Optionally, the hub device 2401 is configured to instruct the server to deregister the hub device 2401 from the server and / or the registration device from the server in the process of deregistering the registration device from the server after the hub device 2401 obtains the state recovery instruction.

[0718] The hub device 2401 is configured to send a first unbinding instruction to the server after obtaining the state recovery instruction.

[0719] The server is configured to deregister the registration device from the server in response to the first unbinding instruction.

[0720] The hub device 2401 is further configured to send a second unbinding instruction to the server after deregistering the registration device from the server.

[0721] The server is further configured to deregister the hub device 2401 from the server in response to the second unbinding instruction.

[0722] Optionally, the hub device 2401 is further configured to restore the registration relationship between the hub device 2401 and the registration device.

[0723] Optionally, the system further comprises a third user device.

[0724] The third user device is configured to determine a registration device to be controlled and a control instruction in response to a control operation of a user.

[0725] The third user device is further configured to send control information to the hub device 2401, the control information comprising a device identifier of the registration device to be controlled and the control instruction.

[0726] The hub device 2401 is further configured to forward the control instruction to the registration device corresponding to the device identifier in response to receiving the control information.

[0727] Optionally, the hub device 2401 is further configured to perform:

[0728] determine a registration device to be controlled and a control instruction in response to a control operation of a user;

[0729] send the control instruction to the registration device to be controlled.

[0730] Those skilled in the art can understand that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be realized by electronic hardware or a combination of computer software and electronic hardware. Whether the functions are realized in hardware or software 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 the present application.

[0731] In the embodiments provided by the present application, it should be understood that the disclosed apparatus / equipment and method can be implemented in other ways. For example, the apparatus / equipment embodiments described above are merely schematic. For example, the division of the modules or units is merely a logical function division. There can be another division manner in actual implementation. For example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed coupling or direct coupling or communication connection between the units can be indirect coupling or communication connection through some interfaces, devices or units, and can be electrical, mechanical or in other forms.

[0732] The units described as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, i.e. they can be located in one place, or distributed on a plurality of network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiments.

[0733] In addition, each functional unit in each embodiment of the present application can be integrated into a processing unit, or each unit can exist physically independently, or two or more units can be integrated into one unit. The integrated unit can be realized in the form of hardware or in the form of a software functional unit.

[0734] The integrated module / unit, if implemented in the form of a software functional unit and sold or used as an independent product, can be stored in a computer readable storage medium. Based on such understanding, all or part of the processes in the above-mentioned embodiment methods can also be completed by a computer program instructing related hardware, and the computer program can be stored in a computer readable storage medium. When the computer program is executed by a processor, the steps of the above-mentioned various method embodiments can be implemented. The computer program includes computer program code, which can be in the form of source code, object code, executable files or some intermediate forms. The computer readable storage medium can include any entity or device capable of carrying the computer program code, recording medium, U disk, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signal, telecommunication signal and software distribution medium, etc. It should be noted that the content included in the computer readable storage medium can be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction, for example, in some jurisdictions, according to legislation and patent practice, the computer readable storage medium does not include electrical carrier signals and telecommunication signals.

[0735] Finally, it should be noted that the above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto, any change or replacement within the technical scope disclosed in the present application should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A device registration method, applied to central devices, characterized in that, The method includes: In response to the first registration request sent by the first user equipment, a first registration code is sent to the first user equipment; After receiving the first registration code sent by the target device, the target device is registered to the central device, so that when the first user device is on the same local area network as the target device, the first user device can control the target device through the central device. Receive a second registration code sent by a second user equipment; wherein the second user equipment is the same user equipment as the first user equipment or is a different user equipment; Register the central device to the server according to the second registration code; After the central device registers with the server, the registered device is also registered with the server, so that the second user device can control the registered device through the server even if it is not on the same local area network as the registered device; wherein, the registered device includes the target device that has been registered with the central device.

2. The method according to claim 1, characterized in that, The method further includes: After receiving the status recovery instruction, the server is instructed to remove the registration relationship between the central device and the server, and / or the registration relationship between the registered device and the server.

3. The method according to claim 2, characterized in that, The instruction to the server to remove the registration relationship between the central device and the server, and / or, the registration relationship between the registered device and the server includes: Send a first unbinding instruction to the server, the first unbinding instruction being used to instruct the server to unbind the registration relationship between the registered device and the server; After the registration relationship between the registered device and the server is terminated, a second unbinding instruction is sent to the server, which instructs the server to terminate the registration relationship between the central device and the server.

4. The method according to claim 3, characterized in that, After sending the first unbinding command to the server, the method further includes: Restore the registration relationship between the central device and the registered device.

5. The method according to any one of claims 1 to 4, characterized in that, After registering the target device to the central device, the method further includes: Receive control information sent by a third user equipment, the control information including the device identifier and control instructions of the registered device to be controlled; The control command is forwarded to the registered device corresponding to the device identifier.

6. The method according to any one of claims 1 to 4, characterized in that, After registering the target device to the central device, the method further includes: In response to the user's control operation, determine the registered device to be controlled and the control command; The control command is sent to the registered device to be controlled.

7. The method according to any one of claims 1 to 4, characterized in that, Registering the central device to the server includes: The central device is bound to the first user account currently logged into by the second user device, and the first user account is used by the second user device to access the server; The step of registering the device to the server includes: Bind the registered device to the first user account.

8. A method for registering a device, characterized in that, The method includes: With the assistance of the first user equipment, the central device registers the target device to the central device, so that when the first user equipment is on the same local area network as the target device, the first user equipment can control the target device through the central device. With the assistance of the second user equipment, the central device registers itself with the server; wherein the second user equipment and the first user equipment are either the same user equipment or different user equipment. After the central device registers itself with the server, the central device registers a registered device with the server, enabling the second user device to control the registered device through the server even when it is not on the same local area network as the registered device; wherein, the registered device includes the target device that has been registered with the central device.

9. The method according to claim 8, characterized in that, The method further includes: After receiving the status recovery instruction, the central device instructs the server to terminate the registration relationship between the central device and the server, and / or the registration relationship between the registered device and the server.

10. The method according to claim 8 or 9, characterized in that, With the assistance of the first user equipment, the central device registers the target device with the central device, specifically including: In response to the user's device registration operation, the first user equipment determines the target device to be registered and sends a first registration request to the central device; In response to the first registration request, the central device sends a first registration code to the first user device, and then the first user device sends the first registration code to the target device. The target device sends the first registration code to the central device, and the central device, in response to receiving the first registration code, registers the target device to the central device.

11. The method according to claim 8 or 9, characterized in that, With the assistance of the second user equipment, the central device registers itself with the server, specifically including: In response to the user's device delivery operation, the second user equipment sends a second registration request to the server; In response to the second registration request, the server sends a second registration code to the second user equipment, and then the second user equipment sends the second registration code to the central device; In response to receiving the second registration code, the central device registers itself with the server.

12. The method according to claim 9, characterized in that, After receiving the status recovery command, the central device instructs the server to terminate the registration relationship between the central device and the server, and / or the registration relationship between the registered device and the server, specifically including: After receiving the status recovery instruction, the central device sends a first unbinding instruction to the server. In response to the first unbinding command, the server terminates the registration relationship between the registered device and the server; After the registration relationship between the registered device and the server is terminated, the central device sends a second unbinding command to the server; In response to the second unbinding command, the server removes the registration relationship between the central device and the server.

13. The method according to claim 12, characterized in that, After sending the first unbinding command to the server, the method further includes: The central device restores the registration relationship between the central device and the registration device.

14. The method according to any one of claims 8-9 and 12-13, characterized in that, After the central device registers the target device with the central device, the process further includes: The third user equipment responds to the user's control operation by determining the registered device to be controlled and the control command; The third user equipment sends control information to the central equipment, the control information including the device identifier of the registered device to be controlled and the control command; In response to receiving the control information, the central device forwards the control command to the registered device corresponding to the device identifier.

15. The method according to claim 10, characterized in that, After the central device registers the target device with the central device, the process further includes: The third user equipment responds to the user's control operation by determining the registered device to be controlled and the control command; The third user equipment sends control information to the central equipment, the control information including the device identifier of the registered device to be controlled and the control command; In response to receiving the control information, the central device forwards the control command to the registered device corresponding to the device identifier.

16. The method according to claim 11, characterized in that, After the central device registers the target device with the central device, the process further includes: The third user equipment responds to the user's control operation by determining the registered device to be controlled and the control command; The third user equipment sends control information to the central equipment, the control information including the device identifier of the registered device to be controlled and the control command; In response to receiving the control information, the central device forwards the control command to the registered device corresponding to the device identifier.

17. The method according to any one of claims 8-9 and 12-13, characterized in that, After the central device registers the target device with the central device, the process further includes: The central device responds to the user's control operation by determining the registered device to be controlled and the control command; The central device sends the control command to the registered device to be controlled.

18. The method according to claim 10, characterized in that, After the central device registers the target device with the central device, the process further includes: The central device responds to the user's control operation by determining the registered device to be controlled and the control command; The central device sends the control command to the registered device to be controlled.

19. The method according to claim 11, characterized in that, After the central device registers the target device with the central device, the process further includes: The central device responds to the user's control operation by determining the registered device to be controlled and the control command; The central device sends the control command to the registered device to be controlled.

20. The method according to claim 8, characterized in that, Registering the central device to the server includes: The central device is bound to the first user account currently logged into by the second user device, and the first user account is used by the second user device to access the server; The step of registering the device to the server includes: Bind the registered device to the first user account.

21. A central device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, The central device is configured to implement the method as described in any one of claims 1 to 7 when executing the computer program.

22. A computer-readable storage medium configured to store a computer program, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1 to 7.

23. A computer program product, characterized in that, The computer program product is configured to run on a central device, causing the central device to perform the method as described in any one of claims 1 to 7.

24. A chip system, characterized in that, The chip system includes a memory and a processor, the processor being configured to execute a computer program stored in the memory to implement the method as described in any one of claims 1 to 7.

Images