Device network binding method, device, equipment and storage medium

By using the collaborative work between the first server and the second server in the intelligent device distribution network binding, a unified equipment distribution network process is achieved, and the complexity and compatibility problems of distribution network binding in the existing technology are solved, reducing the number of problems of distribution network binding in the existing technology. R&D costs and promote maintenance efficiency.

CN113596838BActive Publication Date: 2024-12-03BEIJING XIAOMI MOBILE SOFTWARE CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202110863845.3
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-07-29
Publication Date
2024-12-03
Estimated Expiration
2041-07-29

AI Technical Summary

Technical Problem

The binding process of existing smart device distribution network is complex and requires compatibility with different applications, which increases R&D costs and is not conducive to later maintenance.

Method used

The first server responds to the registration binding request of the device to be bound, sends it to the second server, and binds it after the binding is detected and sends notification information to the device to achieve a unified distribution network Binding the process to reduce the distinction between different applications.

Benefits of technology

It improves the compatibility of distribution network binding solutions, reduces the initial R&D cost of smart devices, and is conducive to later maintenance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113596838B_ABST
    Figure CN113596838B_ABST
Patent Text Reader

Abstract

The present disclosure is about a device network configuration binding method, apparatus, device and storage medium, the method is applied to a first server, the method includes: in response to receiving a registration binding request sent by a device to be bound, sending the registration binding request to a second server; in response to detecting that the second server has successfully bound the device to be bound, binding the device to be bound; in response to completing the binding of the device to be bound, sending a notification message to the device to be bound, the notification message is used to notify the device to be bound that the binding of the first server and the second server has been completed. The present disclosure can realize a unified device network configuration binding process, improve the compatibility of the network configuration binding solution for different applications, and thus reduce the initial research and development costs of smart devices, which is beneficial to later maintenance.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to the field of Internet technology, and in particular to a method, apparatus, device and storage medium for device network configuration binding. Background Art

[0002] With the development of terminal technology and Internet technology, the types and functions of smart devices on the market are becoming more and more diverse. When smart devices connect to the server through the Internet, they will involve the network binding process, which is one of the essential steps. In related technologies, it is possible to bind smart devices to the server based on different applications. However, the device network binding process based on different applications is relatively complicated, and different applications need to be compatible, which will not only increase the initial R&D cost of smart devices, but also be unfavorable for later maintenance. Summary of the invention

[0003] In order to overcome the problems existing in the related art, the embodiments of the present disclosure provide a device network configuration binding method, apparatus, device and storage medium to solve the defects in the related art.

[0004] According to a first aspect of an embodiment of the present disclosure, a device network configuration binding method is provided, which is applied to a first server, and the method includes:

[0005] In response to receiving a registration and binding request sent by the device to be bound, sending the registration and binding request to the second server;

[0006] In response to detecting that the second server successfully binds the device to be bound, binding the device to be bound;

[0007] In response to completing the binding of the device to be bound, sending notification information to the device to be bound, where the notification information is used to notify the device to be bound that the binding of the first server and the second server has been completed.

[0008] In one embodiment, the detecting that the second server successfully binds the to-be-bound device includes:

[0009] The preset information returned by the second server is received, where the preset information is used to indicate that the second server has completed binding with the device to be bound.

[0010] In one embodiment, the method further comprises:

[0011] Pre-establishing a long connection between the first server and the device to be bound;

[0012] Based on the long connection, the operation of sending notification information to the device to be bound is performed.

[0013] According to a second aspect of an embodiment of the present disclosure, a device network configuration binding method is provided, which is applied to a device to be bound, and the method includes:

[0014] In response to receiving the registration information sent by the application, networking is performed based on the registration information;

[0015] After completing the networking, sending a registration binding request to the first server;

[0016] In response to receiving the notification information sent by the first server, a binding result is returned to the application, wherein the notification information is used to notify the device to be bound that the binding of the first server and the second server has been completed.

[0017] In one embodiment, the method further comprises:

[0018] Pre-establishing a long connection between the first server and the device to be bound;

[0019] Based on the long connection, the operation of sending a registration binding request to the first server is performed.

[0020] In one embodiment, the method further comprises:

[0021] A Bluetooth connection between the application and the device to be bound is pre-established.

[0022] In one embodiment, the method further comprises:

[0023] Based on the Bluetooth connection, the registration information sent by the application is received.

[0024] In one embodiment, the method further comprises:

[0025] Based on the Bluetooth connection, the operation of returning the binding result to the application is performed.

[0026] According to a third aspect of an embodiment of the present disclosure, a device configuration network binding apparatus is provided, which is applied to a first server, and the apparatus includes:

[0027] A binding request sending module, configured to, in response to receiving a registration binding request sent by a to-be-bound device, send the registration binding request to a second server;

[0028] A binding device binding module, configured to bind the device to be bound in response to detecting that the second server successfully binds the device to be bound;

[0029] The notification information sending module is used to send notification information to the device to be bound in response to completing the binding of the device to be bound, wherein the notification information is used to notify the device to be bound that the binding of the first server and the second server has been completed.

[0030] In one embodiment, the detecting that the second server successfully binds the to-be-bound device includes:

[0031] The preset information returned by the second server is received, where the preset information is used to indicate that the second server has completed binding with the device to be bound.

[0032] In one embodiment, the device further comprises:

[0033] A first long connection building module, used to pre-build a long connection between the first server and the device to be bound;

[0034] The notification information sending module is further used to execute the operation of sending notification information to the device to be bound based on the long connection.

[0035] According to a fourth aspect of an embodiment of the present disclosure, a device network configuration binding apparatus is provided, which is applied to a device to be bound, and the apparatus includes:

[0036] A networking module, configured to connect to the network based on the registration information in response to receiving the registration information sent by the application;

[0037] A request sending module, used to send a registration binding request to the first server after completing networking;

[0038] The result returning module is used to return the binding result to the application in response to receiving the notification information sent by the first server, wherein the notification information is used to notify the device to be bound that the binding of the first server and the second server has been completed.

[0039] In one embodiment, the device further comprises:

[0040] A second long connection building module, used to pre-build a long connection between the first server and the device to be bound;

[0041] The request sending module is also used to execute the operation of sending a registration binding request to the first server based on the long connection.

[0042] In one embodiment, the device further comprises:

[0043] The Bluetooth connection building module is used to pre-build a Bluetooth connection between the application and the device to be bound.

[0044] In one embodiment, the device further comprises:

[0045] The registration information receiving module is used to receive the registration information sent by the application based on the Bluetooth connection.

[0046] In one embodiment, the result returning module is further used to execute the operation of returning the binding result to the application based on the Bluetooth connection.

[0047] According to a fifth aspect of an embodiment of the present disclosure, a device network configuration binding system is provided, the system comprising a device to be bound, a first server, and a second server;

[0048] The first server is used to execute any one of the above-mentioned device network configuration binding methods applied to the first server;

[0049] The device to be bound is used to execute any one of the above-mentioned device network configuration binding methods applied to the device to be bound.

[0050] According to a sixth aspect of an embodiment of the present disclosure, there is provided an electronic device, the device comprising:

[0051] a processor and a memory for storing a computer program;

[0052] Wherein, the processor is configured to implement, when executing the computer program:

[0053] In response to receiving the registration information sent by the application, networking is performed based on the registration information;

[0054] After completing the networking, sending a registration binding request to the first server;

[0055] In response to receiving the notification information sent by the first server, a binding result is returned to the application, wherein the notification information is used to notify the device to be bound that the binding of the first server and the second server has been completed.

[0056] According to a seventh aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided, on which a computer program is stored, and when the program is executed by a processor, the following is implemented:

[0057] In response to receiving the registration information sent by the application, networking is performed based on the registration information;

[0058] After completing the networking, sending a registration binding request to the first server;

[0059] In response to receiving the notification information sent by the first server, a binding result is returned to the application, wherein the notification information is used to notify the device to be bound that the binding of the first server and the second server has been completed.

[0060] The technical solution provided by the embodiments of the present disclosure may have the following beneficial effects:

[0061] The first server of the present invention responds to receiving a registration and binding request sent by the device to be bound, sends the registration and binding request to the second server, and in response to detecting that the second server has successfully bound the device to be bound, binds the device to be bound, and then in response to completing the binding of the device to be bound, sends a notification message to the device to be bound, and the notification message is used to notify the device to be bound that the binding of the first server and the second server has been completed, which can realize a unified device network configuration and binding process, improve the compatibility of the network configuration and binding solution for different applications, and thus reduce the initial research and development costs of smart devices, which is beneficial to later maintenance.

[0062] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0064] Figure 1 is a flow chart of a device network configuration binding method according to an exemplary embodiment of the present disclosure;

[0065] Figure 2 is a flowchart of another device network configuration binding method according to an exemplary embodiment of the present disclosure;

[0066] Figure 3 is a flow chart of a device network configuration binding method according to an exemplary embodiment of the present disclosure;

[0067] Figure 4 is a flowchart of another device network configuration binding method according to an exemplary embodiment of the present disclosure;

[0068] Figure 5 It is a schematic diagram of an application scenario of a device network configuration binding method according to an exemplary embodiment of the present disclosure;

[0069] Figure 6 It is a block diagram of a device network configuration binding apparatus according to an exemplary embodiment of the present disclosure;

[0070] Figure 7 is a block diagram of another device network configuration binding apparatus according to an exemplary embodiment of the present disclosure;

[0071] Figure 8It is a block diagram of a device network configuration binding apparatus according to an exemplary embodiment of the present disclosure;

[0072] Fig. 9 is a block diagram of another device configuration and binding apparatus according to an exemplary embodiment of the present disclosure;

[0073] Fig.10 It is a block diagram of an electronic device according to an exemplary embodiment of the present disclosure. DETAILED DESCRIPTION

[0074] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0075] Figure 1 It is a flow chart of a device network configuration binding method according to an exemplary embodiment; the method of this embodiment can be applied to a first server (eg, a server cluster consisting of one server or multiple servers).

[0076] like Figure 1 As shown, the method includes the following steps S101-S103:

[0077] In step S101, in response to receiving a registration and binding request sent by a device to be bound, the registration and binding request is sent to a second server.

[0078] In this embodiment, the first server may send the registration and binding request to the second server in response to receiving the registration and binding request sent by the device to be bound.

[0079] The first server may be a server for interconnecting the device to be bound with other devices, that is, by binding the device to be bound to the first server, the device to be bound can be interconnected with other devices in the current environment. For example, the device to be bound sends control instructions to other devices. The second server may be a server for updating the configuration information of the device to be bound.

[0080] For example, when a user needs to perform network binding on a device to be bound, the user can scan the device to be bound in the application pre-installed on the terminal device. After scanning the device to be bound, the option of binding the device to the network can be triggered, and then the application obtains the registration information from the first server. Then, the application can transparently transmit the above registration information to the device to be bound through a pre-built Bluetooth connection. After the device to be bound obtains the above information, it can connect to the network, and then initiate a registration and binding request to the device to be bound through a preset long connection (such as the ot_client channel) after connecting to the network. Furthermore, after receiving the above registration and binding request, the first server can synchronize the request to the second server to trigger the second server to bind the device to be bound, and detect whether the second server has successfully bound the device to be bound.

[0081] In step S102, in response to detecting that the second server successfully binds the device to be bound, the device to be bound is bound.

[0082] In this embodiment, after the first server sends the registration binding request to the second server, if it is detected that the second server has successfully bound the device to be bound, the device to be bound may be bound.

[0083] In one embodiment, the first server detects that the second server successfully binds the to-be-bound device, which may include:

[0084] The preset information returned by the second server is received, wherein the preset information can be used to indicate that the second server has completed binding with the device to be bound.

[0085] It is worth noting that the specific manner in which the first server binds the device to be bound can be found in the explanations and descriptions in the relevant technologies, and this embodiment does not limit this.

[0086] In step S103, in response to completion of binding of the device to be bound, notification information is sent to the device to be bound.

[0087] In this embodiment, after the binding of the device to be bound is completed, a notification message can be sent to the device to be bound, wherein the notification message can be used to notify the device to be bound that the binding of the first server and the second server has been completed. On this basis, the device to be bound can respond to receiving the passing message and notify the application of the binding result, so as to display the binding result to the user through the application.

[0088] From the above description, it can be seen that this embodiment sends the registration and binding request to the second server in response to receiving the registration and binding request sent by the device to be bound, and binds the device to be bound in response to detecting that the second server has successfully bound the device to be bound, and then in response to completing the binding of the device to be bound, sends a notification message to the device to be bound, and the notification message is used to notify the device to be bound that the binding of the first server and the second server has been completed. This can realize a unified device network configuration and binding process, improve the compatibility of the network configuration and binding solution for different applications, and thus reduce the initial research and development costs of smart devices, which is beneficial to later maintenance.

[0089] Figure 2 It is a flowchart of another device network configuration binding method according to an exemplary embodiment of the present disclosure; the method of this embodiment can be applied to a first server (eg, a server cluster consisting of one server or multiple servers).

[0090] like Figure 2 As shown, the method includes the following steps S201-S204:

[0091] In step S201, in response to receiving a registration and binding request sent by a device to be bound, the registration and binding request is sent to a second server.

[0092] In step S202, in response to detecting that the second server successfully binds the device to be bound, the device to be bound is bound.

[0093] In step S203, a long connection between the first server and the device to be bound is pre-established.

[0094] In this embodiment, in order to enable the first server to send notification information to the device to be bound based on the persistent connection after completing binding of the device to be bound, a persistent connection between the first server and the device to be bound may be pre-established.

[0095] It is worth noting that the type of the above-mentioned long connection can be set based on actual needs, and this embodiment does not limit this.

[0096] In one embodiment, the above-mentioned long connection can be an ot_client channel. It can be understood that the use of the ot_client channel for information transmission can ensure that the current network configuration binding solution no longer needs to distinguish different applications, compared with the messagingagent long connection used in the traditional solution, thereby improving the compatibility of the current network configuration binding process solution.

[0097] In step S204, in response to completing the binding of the device to be bound, notification information is sent to the device to be bound based on the persistent connection.

[0098] The explanations and instructions for steps S201-S202 and S204 can be found in the above Figure 1 Steps S101-S103 in the illustrated embodiment are not described in detail here.

[0099] From the above description, it can be seen that this embodiment pre-builds a long connection of the ot_client channel type between the first server and the device to be bound, so that after the binding of the device to be bound is completed, notification information is sent to the device to be bound based on the long connection. Compared with the messagingagent long connection used in the traditional solution, it can ensure that the current network configuration binding solution no longer needs to distinguish between different applications, thereby improving the compatibility of the current network configuration binding process solution.

[0100] Figure 3 It is a flowchart of a device network binding method according to an exemplary embodiment of the present disclosure; the method of this embodiment can be applied to devices to be bound (such as smart speakers, smart watches or wearable devices, etc.).

[0101] like Figure 3 As shown, the method includes the following steps S301-S303:

[0102] In step S301, in response to receiving registration information sent by an application, networking is performed based on the registration information.

[0103] In this embodiment, the device to be bound may connect to the network based on the registration information in response to receiving the registration information sent by the application.

[0104] For example, when a user needs to bind a device to be bound, the user can scan the device to be bound in the application pre-installed on the terminal device. After the device to be bound is scanned, the option of binding the device to the network can be triggered. Then the application can obtain the registration information from the first server, and then transparently transmit the registration information to the device to be bound through the pre-established Bluetooth connection. After the device to be bound obtains the above information, it can connect to the network.

[0105] It is worth noting that the process of the to-be-bound device connecting to the Internet based on the above-mentioned information obtained can refer to the explanations and descriptions in the relevant technologies, and this embodiment does not limit this.

[0106] In step S302, after completing networking, a registration binding request is sent to the first server.

[0107] In this embodiment, after the device to be bound completes networking, it may send a registration binding request to the first server based on the established network connection.

[0108] In step S303, in response to receiving the notification information sent by the first server, a binding result is returned to the application.

[0109] In this embodiment, after the device to be bound sends a registration binding request to the first server, the binding result can be returned to the application in response to receiving a notification message sent by the first server. The notification message can be used to notify the device to be bound that the binding of the first server and the second server has been completed.

[0110] For example, when the first server receives the above registration binding request, it can synchronize the request to the second server to trigger the second server to bind the device to be bound and wait for the second binding device to return the binding result. After the second server completes the binding, it can return the corresponding binding result to the first server, so that the first server can bind the device to be bound after receiving the above binding result returned by the second server, and then when the binding is completed, the final binding result can be sent to the device to be bound through a preset long connection (such as the ot_client channel), wherein the final binding result can be used to indicate that both the first server and the second server have completed the binding of the device to be bound. Furthermore, the device to be bound notifies the application of the binding result so as to display the binding result to the user through the application.

[0111] From the above description, it can be seen that the method of this embodiment responds to the registration information sent by the application, connects to the network based on the registration information, and after completing the networking, sends a registration binding request to the first server, and then responds to the notification information sent by the first server, returns the binding result to the application, which can realize a unified device network configuration and binding process, improve the compatibility of the network configuration and binding solution for different applications, and thus reduce the initial research and development costs of smart devices, which is beneficial to later maintenance.

[0112] Figure 4 It is a flowchart of another device network binding method according to an exemplary embodiment of the present disclosure; the method of this embodiment can be applied to devices to be bound (such as smart speakers, smart watches or wearable devices, etc.).

[0113] like Figure 4 As shown, the method includes the following steps S401-S403:

[0114] In step S401, in response to receiving registration information sent by the application, networking is performed based on the registration information.

[0115] In step S402, a long connection between the first server and the device to be bound is pre-established.

[0116] In this embodiment, in order to send a registration binding request to the first server based on the persistent connection after the device to be bound completes networking, a persistent connection between the first server and the device to be bound may be pre-established.

[0117] It is worth noting that the type of the above-mentioned long connection can be set based on actual needs, and this embodiment does not limit this.

[0118] In one embodiment, the above-mentioned long connection can be an ot_client channel. It can be understood that the use of the ot_client channel for information transmission can ensure that the current network configuration binding solution no longer needs to distinguish different applications, compared with the messagingagent long connection used in the traditional solution, thereby improving the compatibility of the current network configuration binding process solution.

[0119] In step S403, after completing networking, a registration binding request is sent to the first server based on the persistent connection.

[0120] In step S404, in response to receiving the notification information sent by the first server, a binding result is returned to the application.

[0121] The relevant explanations and descriptions of steps S401, S403-S404 can be found in the above embodiments and will not be elaborated here.

[0122] In one embodiment, a Bluetooth connection between the application and the device to be bound may also be pre-established. On this basis, the method of the above embodiment may also include any of the following:

[0123] Based on the Bluetooth connection, receiving the registration information sent by the application;

[0124] Based on the Bluetooth connection, the operation of returning the binding result to the application is performed.

[0125] From the above description, it can be seen that this embodiment pre-builds a long connection of the ot_client channel type between the first server and the device to be bound, so that the subsequent device to be bound can send a registration binding request to the first server based on the long connection after completing the networking. Compared with the messagingagent long connection used in the traditional solution, it can ensure that the current network configuration binding solution no longer needs to distinguish between different applications, thereby improving the compatibility of the current network configuration binding process solution.

[0126] Figure 5 is a schematic diagram of an application scenario of a device network configuration binding method according to an exemplary embodiment of the present disclosure; Figure 5 As shown, the application scenario mainly involves the first server (such as Mijia server), the second server (such as mico server), the device to be bound (such as smart speakers, etc.) and the application installed on the user's terminal device (such as smart phones, etc.). For example, when the user needs to perform network binding on the device to be bound, the device to be bound can be scanned in the application pre-installed on the terminal device. After the device to be bound is scanned, the option of binding the device to the network can be triggered to start the following steps S1 to S7 of the network binding process:

[0127] S1: Get encrypted information

[0128] The application obtains encrypted information such as bindkey (e.g., encrypted registration information) from the Mi Home server.

[0129] S2: Bluetooth transmission information

[0130] The application transparently transmits the above registration information to the smart speaker device to be bound through the pre-established Bluetooth connection.

[0131] S3: Uplink binding

[0132] After the smart speaker device obtains the above information, it can connect to the Internet, and then initiate a registration and binding request to the Mi Home server through a preset long connection (such as the ot_client channel) after connecting to the Internet.

[0133] S4: Binding Synchronization

[0134] After receiving the above registration and binding request, the Mi Home server can synchronize the request to the mico server to trigger the mico server to bind the smart speaker device and wait for the mico server to return the binding result.

[0135] S5: Return binding result

[0136] After the mico server completes the binding, the corresponding binding result can be returned to the Mi Home server.

[0137] S6: Downward instruction

[0138] After the Mi Home server receives the above binding result returned by the mico server, it can bind the smart speaker device. After the binding is completed, the final binding result can be sent to the smart speaker device through a preset long connection (such as the ot_client channel). The final binding result can be used to indicate that both the Mi Home server and the mico server have completed the binding of the smart speaker device.

[0139] S7: Binding results

[0140] The smart speaker device notifies the application of the binding result, so that the binding result is displayed to the user through the application.

[0141] Figure 6 It is a block diagram of a device network configuration binding apparatus according to an exemplary embodiment of the present disclosure; the apparatus of this embodiment can be applied to a first server (eg, a server cluster consisting of one server or multiple servers).

[0142] like Figure 6 As shown, the apparatus may include: a binding request sending module 110, a binding device binding module 120, and a notification information sending module 130, wherein:

[0143] The binding request sending module 110 is used to send the registration binding request to the second server in response to receiving the registration binding request sent by the device to be bound;

[0144] A binding device binding module 120, configured to bind the device to be bound in response to detecting that the second server successfully binds the device to be bound;

[0145] The notification information sending module 130 is used to send notification information to the device to be bound in response to completing the binding of the device to be bound, wherein the notification information is used to notify the device to be bound that the binding of the first server and the second server has been completed.

[0146] From the above description, it can be seen that the device of this embodiment sends the registration and binding request to the second server in response to receiving the registration and binding request sent by the device to be bound, and binds the device to be bound in response to detecting that the second server has successfully bound the device to be bound, and then sends a notification message to the device to be bound in response to completing the binding of the device to be bound. The notification message is used to notify the device to be bound that the binding of the first server and the second server has been completed. This can realize a unified device network configuration and binding process, improve the compatibility of the network configuration and binding solution for different applications, and thus reduce the initial research and development costs of smart devices, which is beneficial to later maintenance.

[0147] Figure 7 2 is a block diagram of another device configuration network binding device according to an exemplary embodiment of the present disclosure; the device of this embodiment can be applied to a first server (e.g., a server cluster composed of one server or multiple servers). Among them, the binding request sending module 210, the binding device binding module 220 and the notification information sending module 230 are similar to the aforementioned Figure 6The functions of the binding request sending module 110, the binding device binding module 120 and the notification information sending module 130 in the illustrated embodiment are the same and will not be described in detail herein.

[0148] In the above Figure 6 Based on the illustrated embodiment, detecting that the second server successfully binds the to-be-bound device may include:

[0149] The preset information returned by the second server is received, where the preset information is used to indicate that the second server has completed binding with the device to be bound.

[0150] like Figure 7 As shown, the above device also includes:

[0151] A first long connection building module 230, used to pre-build a long connection between the first server and the device to be bound;

[0152] On this basis, the notification information sending module 240 can also be used to execute the operation of sending the notification information to the device to be bound based on the long connection.

[0153] Figure 8 1 is a block diagram of a device network binding apparatus according to an exemplary embodiment of the present disclosure; the apparatus of this embodiment can be applied to a device to be bound (such as a smart speaker, a smart watch or a wearable device, etc.). Figure 8 The device may include: a networking module 310, a request sending module 320, and a result returning module 330, wherein:

[0154] A networking module 310, configured to connect to a network based on the registration information in response to receiving the registration information sent by the application;

[0155] The request sending module 320 is used to send a registration binding request to the first server after completing networking;

[0156] The result returning module 330 is used to return the binding result to the application in response to receiving the notification information sent by the first server, wherein the notification information is used to notify the device to be bound that the binding of the first server and the second server has been completed.

[0157] From the above description, it can be seen that the device of this embodiment responds to the registration information sent by the application, connects to the network based on the registration information, and after completing the networking, sends a registration binding request to the first server, and then responds to the notification information sent by the first server, and returns the binding result to the application. This can implement a unified device network configuration and binding process, improve the compatibility of the network configuration and binding solution for different applications, and thus reduce the initial research and development costs of smart devices, which is beneficial to later maintenance.

[0158] Fig. 9 4 is a block diagram of another device network binding device according to an exemplary embodiment of the present disclosure; the device of this embodiment can be applied to a device to be bound (such as a smart speaker, a smart watch or a wearable device, etc.). Among them, the networking module 410, the request sending module 420 and the result returning module 430 are the same as the aforementioned Figure 8 The functions of the networking module 310, the request sending module 320 and the result returning module 330 in the illustrated embodiment are the same and will not be described in detail herein.

[0159] like Figure 8 The above device may further include:

[0160] A second long connection building module 440 is used to pre-build a long connection between the first server and the device to be bound;

[0161] On this basis, the request sending module 420 may also be used to execute the operation of sending the registration binding request to the first server based on the long connection.

[0162] In one embodiment, the above device may further include:

[0163] The Bluetooth connection building module 450 is used to pre-build a Bluetooth connection between the application and the device to be bound.

[0164] In one embodiment, the above device may further include:

[0165] The registration information receiving module 460 is used to receive the registration information sent by the application based on the Bluetooth connection.

[0166] In one embodiment, the result returning module 430 may also be used to perform the operation of returning the binding result to the application based on the Bluetooth connection.

[0167] On the other hand, the embodiment of the present disclosure further provides a device network configuration binding system, which may include a device to be bound, a first server, and a second server;

[0168] The first server can be used to execute the above Figure 1 or Figure 2 The device network binding method shown;

[0169] The device to be bound can be used to perform the above Figure 3 or Figure 4 The device network binding method shown.

[0170] Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0171] Fig.10 900 is a block diagram of an electronic device according to an exemplary embodiment. For example, the device 900 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.

[0172] Reference Fig.10 , device 900 may include one or more of the following components: a processing component 902 , a memory 904 , a power component 906 , a multimedia component 908 , an audio component 910 , an input / output (I / O) interface 912 , a sensor component 914 , and a communication component 916 .

[0173] The processing component 902 generally controls the overall operation of the device 900, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. The processing component 902 may include one or more processors 920 to execute instructions to complete all or part of the steps of the above-mentioned method. In addition, the processing component 902 may include one or more modules to facilitate the interaction between the processing component 902 and other components. For example, the processing component 902 may include a multimedia module to facilitate the interaction between the multimedia component 908 and the processing component 902.

[0174] The memory 904 is configured to store various types of data to support operations on the device 900. Examples of such data include instructions for any application or method operating on the device 900, contact data, phone book data, messages, pictures, videos, etc. The memory 904 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0175] The power supply component 906 provides power to the various components of the device 900. The power supply component 906 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the device 900.

[0176] The multimedia component 908 includes a screen that provides an output interface between the device 900 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundaries of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 908 includes a front camera and / or a rear camera. When the device 900 is in an operating mode, such as a shooting mode or a video mode, the front camera and / or the rear camera may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.

[0177] The audio component 910 is configured to output and / or input audio signals. For example, the audio component 910 includes a microphone (MIC), and when the device 900 is in an operating mode, such as a call mode, a recording mode, and a speech recognition mode, the microphone is configured to receive an external audio signal. The received audio signal can be further stored in the memory 904 or sent via the communication component 916. In some embodiments, the audio component 910 also includes a speaker for outputting audio signals.

[0178] I / O interface 912 provides an interface between processing component 902 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include but are not limited to: a home button, a volume button, a start button, and a lock button.

[0179] The sensor assembly 914 includes one or more sensors for providing various aspects of status assessment for the device 900. For example, the sensor assembly 914 can detect the open / closed state of the device 900, the relative positioning of components, such as the display and keypad of the device 900, and the sensor assembly 914 can also detect the position change of the device 900 or a component of the device 900, the presence or absence of user contact with the device 900, the orientation or acceleration / deceleration of the device 900, and the temperature change of the device 900. The sensor assembly 914 can also include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor assembly 914 can also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 914 can also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0180] The communication component 916 is configured to facilitate wired or wireless communication between the device 900 and other devices. The device 900 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, 4G or 5G or a combination thereof. In an exemplary embodiment, the communication component 916 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 916 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

[0181] In an exemplary embodiment, the device 900 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the above methods.

[0182] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 904 including instructions, and the instructions can be executed by the processor 920 of the device 900 to perform the above method. For example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0183] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the disclosure disclosed herein. The present disclosure is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The description and examples are to be considered exemplary only, and the true scope and spirit of the present disclosure are indicated by the following claims.

[0184] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A device network configuration binding method, characterized in that: Applied to a first server, the first server is a server for interconnecting a device to be bound with other devices, the method comprising: In response to receiving the registration and binding request sent by the device to be bound, sending the registration and binding request to a second server, where the second server is a server for updating configuration information of the device to be bound; In response to detecting that the second server successfully binds the device to be bound, binding the device to be bound; In response to completing the binding of the device to be bound, sending notification information to the device to be bound, where the notification information is used to notify the device to be bound that the binding of the first server and the second server has been completed.

2. The method according to claim 1, characterized in that The detecting that the second server successfully binds the device to be bound includes: The preset information returned by the second server is received, where the preset information is used to indicate that the second server has completed binding with the device to be bound.

3. The method according to claim 1, characterized in that The method further comprises: Pre-establishing a long connection between the first server and the device to be bound; Based on the long connection, the operation of sending notification information to the device to be bound is performed.

4. A device network binding method, characterized in that: Applied to the device to be bound, the method includes: In response to receiving the registration information sent by the application, networking is performed based on the registration information; After completing networking, sending a registration binding request to a first server, where the first server is a server for interconnecting the device to be bound with other devices; In response to receiving the notification information sent by the first server, a binding result is returned to the application, wherein the notification information is used to notify the device to be bound that the binding of the first server and the second server has been completed, and the second server is a server used to update the configuration information of the device to be bound.

5. The method according to claim 4, characterized in that The method further comprises: Pre-establishing a long connection between the first server and the device to be bound; Based on the long connection, the operation of sending a registration binding request to the first server is performed.

6. The method according to claim 4, characterized in that The method further comprises: A Bluetooth connection between the application and the device to be bound is pre-established.

7. The method according to claim 6, characterized in that The method further comprises: Based on the Bluetooth connection, the registration information sent by the application is received.

8. The method according to claim 6, characterized in that The method further comprises: Based on the Bluetooth connection, the operation of returning the binding result to the application is performed.

9. A device for equipment network binding, characterized in that: Applied to a first server, the first server is a server for interconnecting a device to be bound with other devices, the device includes: a binding request sending module, configured to, in response to receiving a registration binding request sent by the device to be bound, send the registration binding request to a second server, where the second server is a server for updating configuration information of the device to be bound; A binding device binding module, configured to bind the device to be bound in response to detecting that the second server successfully binds the device to be bound; The notification information sending module is used to send notification information to the device to be bound in response to completing the binding of the device to be bound, wherein the notification information is used to notify the device to be bound that the binding of the first server and the second server has been completed.

10. A device for equipment network binding, characterized in that: Applied to a device to be bound, the device comprises: A networking module, configured to connect to the network based on the registration information in response to receiving the registration information sent by the application; A request sending module, used for sending a registration binding request to a first server after completing networking, wherein the first server is a server for interconnecting the device to be bound with other devices; A result returning module is used to return a binding result to the application in response to receiving a notification message sent by the first server, wherein the notification message is used to notify the device to be bound that the binding of the first server and the second server has been completed, and the second server is a server used to update the configuration information of the device to be bound.

11. A device network binding system, characterized in that: The system includes a device to be bound, a first server and a second server; The first server is used to execute the device network configuration binding method according to any one of claims 1 to 3 above; The device to be bound is used to execute the device network configuration binding method in any one of claims 4 to 8 above.

12. An electronic device, characterized in that: The device comprises: a processor and a memory for storing a computer program; Wherein, the processor is configured to execute the device network configuration binding method of any one of claims 1-3 or any one of claims 4-8 when executing the computer program.

13. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the device network configuration binding method described in any one of claims 1 to 3 or any one of claims 4 to 8 is implemented.