CN113596838A - Equipment distribution network binding method, device, equipment and storage medium - Google Patents

Equipment distribution network binding method, device, equipment and storage medium Download PDF

Info

Publication number
CN113596838A
CN113596838A CN202110863845.3A CN202110863845A CN113596838A CN 113596838 A CN113596838 A CN 113596838A CN 202110863845 A CN202110863845 A CN 202110863845A CN 113596838 A CN113596838 A CN 113596838A
Authority
CN
China
Prior art keywords
binding
bound
server
service end
distribution network
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202110863845.3A
Other languages
Chinese (zh)
Inventor
蔡纯兴
徐吉轩
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Xiaomi Mobile Software Co Ltd
Original Assignee
Beijing Xiaomi Mobile Software Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Xiaomi Mobile Software Co Ltd filed Critical Beijing Xiaomi Mobile Software Co Ltd
Priority to CN202110863845.3A priority Critical patent/CN113596838A/en
Publication of CN113596838A publication Critical patent/CN113596838A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/40—Security arrangements using identity modules
    • H04W12/48—Security arrangements using identity modules using secure binding, e.g. securely binding identity modules to devices, services or applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/50—Secure pairing of devices

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

The disclosure relates to a device distribution network binding method, a device and a storage medium, wherein the method is applied to a first service end, and the method comprises the following steps: responding to a received registration binding request sent by a device to be bound, and sending the registration binding request to a second server; binding the device to be bound in response to detecting that the second server is successfully bound to the device to be bound; and in response to the completion of the binding of the device to be bound, sending notification information to the device to be bound, wherein the notification information is used for notifying the device to be bound that the binding of the first service end and the second service end is completed. The method and the device for binding the distribution network can realize a unified equipment distribution network binding process, improve the compatibility of a distribution network binding scheme to different application programs, further reduce the early-stage research and development cost of the intelligent equipment, and are favorable for later maintenance.

Description

Equipment distribution network binding method, device, equipment and storage medium
Technical Field
The present disclosure relates to the field of internet technologies, and in particular, to a device and network binding method, apparatus, device, and storage medium.
Background
With the development of terminal technology and internet technology, the types and functions of smart devices on the market are more and more diversified. The intelligent equipment is connected with the server through the Internet, and all the intelligent equipment relate to a distribution network binding process, which is one of indispensable steps. The binding of the intelligent device distribution network to the server side based on different application programs can be realized in the related technology. However, the device distribution network binding process based on different application programs is complex, and different application programs need to be compatible, so that the early-stage research and development cost of the intelligent device can be increased, and the later-stage maintenance is not facilitated.
Disclosure of Invention
In order to overcome the problems in the related art, embodiments of the present disclosure provide a method, an apparatus, a device, and a storage medium for binding a device distribution network, so as to solve the defects in the related art.
According to a first aspect of the embodiments of the present disclosure, a device distribution network binding method is provided, which is applied to a first service end, and the method includes:
responding to a received registration binding request sent by a device to be bound, and sending the registration binding request to a second server;
binding the device to be bound in response to detecting that the second server is successfully bound to the device to be bound;
and in response to the completion of the binding of the device to be bound, sending notification information to the device to be bound, wherein the notification information is used for notifying the device to be bound that the binding of the first service end and the second service end is completed.
In an embodiment, the detecting that the second server successfully binds to the device to be bound includes:
and receiving preset information returned by the second server, wherein the preset information is used for representing that the second server finishes binding the equipment to be bound.
In an embodiment, the method further comprises:
pre-constructing a long connection between the first service terminal and the equipment to be bound;
and executing the operation of sending the notification information to the device to be bound based on the long connection.
According to a second aspect of the embodiments of the present disclosure, there is provided a device distribution network binding method, applied to a device to be bound, the method including:
responding to the received registration information sent by the application program, and networking based on the registration information;
after networking is completed, a registration binding request is sent to a first server;
and in response to receiving notification information sent by the first service end, returning a binding result to the application program, wherein the notification information is used for notifying the device to be bound that the binding of the first service end and the second service end is completed.
In an embodiment, the method further comprises:
pre-constructing a long connection between the first service terminal and the equipment to be bound;
and executing the operation of sending the registration binding request to the first service terminal based on the long connection.
In an embodiment, the method further comprises:
and pre-constructing the Bluetooth connection between the application program and the device to be bound.
In an embodiment, the method further comprises:
and receiving the registration information sent by the application program based on the Bluetooth connection.
In an embodiment, the method further comprises:
and executing the operation of returning the binding result to the application program based on the Bluetooth connection.
According to a third aspect of the embodiments of the present disclosure, an apparatus for binding a device distribution network is provided, which is applied to a first service end, and the apparatus includes:
the binding request sending module is used for responding to a received registration binding request sent by the equipment to be bound and sending the registration binding request to the second server;
the binding device binding module is used for binding the device to be bound in response to the detection that the second server is successfully bound to the device to be bound;
and the notification information sending module is used for responding to the completion of the binding of the device to be bound and sending notification information to the device to be bound, wherein the notification information is used for notifying the device to be bound that the binding of the first service end and the second service end is completed.
In an embodiment, the detecting that the second server successfully binds to the device to be bound includes:
and receiving preset information returned by the second server, wherein the preset information is used for representing that the second server finishes binding the equipment to be bound.
In one embodiment, the apparatus further comprises:
the first long connection construction module is used for constructing a long connection between the first service end and the equipment to be bound in advance;
the notification information sending module is further configured to execute the operation of sending the notification information to the device to be bound based on the long connection.
According to a fourth aspect of the embodiments of the present disclosure, there is provided an apparatus for binding a device distribution network, which is applied to a device to be bound, the apparatus including:
the networking module is used for responding to the received registration information sent by the application program and networking based on the registration information;
the request sending module is used for sending a registration binding request to the first server after networking is finished;
and the result returning module is used for returning a binding result to the application program in response to receiving notification information sent by the first service end, wherein the notification information is used for notifying the device to be bound that the binding of the first service end and the second service end is completed.
In one embodiment, the apparatus further comprises:
the second long connection construction module is used for constructing a long connection between the first service end and the equipment to be bound in advance;
the request sending module is further configured to execute the operation of sending the registration binding request to the first service end based on the long connection.
In one embodiment, the apparatus further comprises:
and the Bluetooth connection construction module is used for constructing the Bluetooth connection between the application program and the device to be bound in advance.
In one embodiment, the apparatus further comprises:
and the registration information receiving module is used for receiving the registration information sent by the application program based on the Bluetooth connection.
In an embodiment, the result returning module is further configured to perform the operation of returning the binding result to the application program based on the bluetooth connection.
According to a fifth aspect of the embodiments of the present disclosure, a device distribution network binding system is provided, where the system includes a device to be bound, a first service end, and a second service end;
the first server is used for executing any one of the above equipment distribution network binding methods applied to the first server;
the device to be bound is used for executing the device distribution network binding method applied to the device to be bound.
According to a sixth aspect of embodiments of the present disclosure, there is provided an electronic apparatus, the apparatus comprising:
a processor and a memory for storing a computer program;
wherein the processor is configured to, when executing the computer program, implement:
responding to the received registration information sent by the application program, and networking based on the registration information;
after networking is completed, a registration binding request is sent to a first server;
and in response to receiving notification information sent by the first service end, returning a binding result to the application program, wherein the notification information is used for notifying the device to be bound that the binding of the first service end and the second service end is completed.
According to a seventh aspect of embodiments of the present disclosure, there is provided a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements:
responding to the received registration information sent by the application program, and networking based on the registration information;
after networking is completed, a registration binding request is sent to a first server;
and in response to receiving notification information sent by the first service end, returning a binding result to the application program, wherein the notification information is used for notifying the device to be bound that the binding of the first service end and the second service end is completed.
The technical scheme provided by the embodiment of the disclosure can have the following beneficial effects:
according to the method, the first server sends the registration binding request to the second server in response to receiving the registration binding request sent by the device to be bound, binds the device to be bound in response to detecting that the second server successfully binds the device to be bound, and sends notification information to the device to be bound in response to finishing binding the device to be bound, wherein the notification information is used for notifying the device to be bound that the binding of the first server and the second server is finished, so that a unified device distribution network binding process can be realized, the compatibility of a distribution network binding scheme to different application programs is improved, the early-stage research and development cost of the intelligent device can be reduced, and the later-stage maintenance is facilitated.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
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 disclosure.
Fig. 1 is a flowchart illustrating a method for binding a device distribution network according to an exemplary embodiment of the present disclosure;
fig. 2 is a flowchart illustrating another method for binding a device distribution network according to an exemplary embodiment of the disclosure;
fig. 3 is a flowchart illustrating a method for binding a device distribution network according to an exemplary embodiment of the present disclosure;
fig. 4 is a flowchart illustrating another method for binding a device distribution network according to an exemplary embodiment of the disclosure;
fig. 5 is a schematic view of an application scenario of a device distribution network binding method according to an exemplary embodiment of the present disclosure;
fig. 6 is a block diagram illustrating an apparatus for binding a device distribution network according to an exemplary embodiment of the disclosure;
fig. 7 is a block diagram illustrating yet another device distribution network binding apparatus according to an exemplary embodiment of the disclosure;
fig. 8 is a block diagram illustrating an apparatus for binding a device distribution network according to an exemplary embodiment of the disclosure;
fig. 9 is a block diagram illustrating yet another device distribution network binding apparatus according to an exemplary embodiment of the disclosure;
fig. 10 is a block diagram illustrating an electronic device according to an exemplary embodiment of the present disclosure.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like 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. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.
Fig. 1 is a flow chart illustrating a method for binding a device distribution network according to an exemplary embodiment; the method of this embodiment may be applied to a first service end (e.g., a server or a server cluster composed of multiple servers).
As shown in fig. 1, the method comprises the following steps S101-S103:
in step S101, in response to receiving a registration binding request sent by a device to be bound, the registration binding request is sent to a second server.
In this embodiment, the first server may send, in response to receiving a registration binding request sent by the device to be bound, the registration binding request to the second server.
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 with the first server, the device to be bound may be interconnected with other devices in the current environment. For example, the device to be bound sends a control instruction to other devices. And the second server may be a server for updating the configuration information of the device to be bound.
For example, when a user needs to perform distribution network binding on a device to be bound, the device to be bound may be scanned in an application program pre-installed on a terminal device, and after the device to be bound is scanned, an option for binding the device to the distribution network may be triggered, so that the application program obtains registration information from the first server. Then, the application program can transmit the registration information to the device to be bound through the pre-constructed Bluetooth connection. And after obtaining the information, the device to be bound can perform networking, and then initiate a registration binding request to the device to be bound through a preset long connection (such as an ot _ client channel) after networking. Further, after receiving the registration binding request, the first service end may synchronize the request to the second service end, so as to trigger the second service end to bind the device to be bound, and detect whether the second service end successfully binds the device to be bound.
In step S102, in response to detecting that the second server successfully binds the device to be bound, binding the device to be bound.
In this embodiment, after the first server sends the registration binding request to the second server, if it is detected that the second server successfully binds the device to be bound, the device to be bound may be bound.
In an embodiment, the detecting, by the first service end, that the second service end successfully binds to the device to be bound may include:
and receiving preset information returned by the second server, wherein the preset information can be used for representing that the second server finishes binding the device to be bound.
It should be noted that, for a specific manner of binding the device to be bound by the first service end, reference may be made to explanation and description in the related art, which is not limited in this embodiment.
In step S103, in response to completion of binding the device to be bound, notification information is sent to the device to be bound.
In this embodiment, after the binding of the device to be bound is completed, notification information may be sent to the device to be bound, where the notification information may be used to notify that the device to be bound has completed the binding of the first service end and the second service end. On the basis, the device to be bound can inform the application program of the binding result corresponding to the received passing information, so that the binding result can be shown to the user through the application program.
As can be seen from the above description, in this embodiment, in response to receiving a registration binding request sent by a device to be bound, the registration binding request is sent to a second server, and in response to detecting that the second server binds the device to be bound successfully, the device to be bound is bound, and then in response to completing the binding of the device to be bound, notification information is sent to the device to be bound, where the notification information is used to notify that the device to be bound has completed the binding of the first server and the second server, so that a unified device distribution network binding process can be implemented, compatibility of a distribution network binding scheme with different application programs is improved, and further early-stage development cost of an intelligent device can be reduced, which is beneficial to later maintenance.
Fig. 2 is a flowchart illustrating another method for binding a device distribution network according to an exemplary embodiment of the disclosure; the method of this embodiment may be applied to a first service end (e.g., a server or a server cluster composed of multiple servers).
As shown in fig. 2, the method comprises the following steps S201-S204:
in step S201, in response to receiving a registration binding request sent by a device to be bound, the registration binding request is sent to a second server.
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.
In step S203, a long connection between the first service end and the device to be bound is constructed in advance.
In this embodiment, in order to implement that, after the first server completes the binding of the device to be bound, notification information is sent to the device to be bound based on the long connection, the long connection between the first server and the device to be bound may be pre-constructed.
It should be noted that the type of the long connection may be set based on actual needs, and this embodiment is not limited to this.
In one embodiment, the long connection may be an ot _ client channel. It can be understood that the ot _ client channel is used for information transmission, and compared with the messagingagent long connection adopted in the traditional scheme, the current distribution network binding scheme can be ensured not to distinguish different application programs, and the compatibility of the current distribution network binding flow scheme can be improved.
In step S204, in response to completion of binding the device to be bound, notification information is sent to the device to be bound based on the long connection.
The relevant explanations and explanations of steps S201 to S202 and S204 may refer to steps S101 to S103 in the embodiment shown in fig. 1, which are not repeated herein.
As can be seen from the above description, in this embodiment, by pre-constructing the ot _ client channel type long connection between the first server and the device to be bound, after the device to be bound is bound, notification information is sent to the device to be bound based on the long connection, and compared with the messagingent long connection adopted in the conventional scheme, it can be ensured that different application programs are no longer required to be distinguished in the current distribution network binding scheme, and thus the compatibility of the current distribution network binding flow scheme can be improved.
Fig. 3 is a flowchart illustrating a method for binding a device distribution network according to an exemplary embodiment of the present disclosure; the method of the embodiment can be applied to a device to be bound (e.g., a smart speaker, a smart watch, a wearable device, or the like).
As shown in fig. 3, the method comprises the following steps S301-S303:
in step S301, in response to receiving registration information sent by an application, networking is performed based on the registration information.
In this embodiment, the device to be bound may perform networking based on the registration information in response to receiving the registration information sent by the application program.
For example, when a user needs to perform distribution network binding on a device to be bound, the device to be bound may be scanned in an application program pre-installed on a terminal device, and after the device to be bound is scanned, an option of binding the device to the distribution network may be triggered. And the application program can acquire the registration information from the first service terminal and then transmit the registration information to the device to be bound through the pre-established Bluetooth connection. And after the equipment to be bound acquires the information, networking can be performed.
It should be noted that, for the process of networking the device to be bound based on the obtained information, reference may be made to explanation and description in the related art, which is not limited in this embodiment.
In step S302, after networking is completed, a registration binding request is sent to the first server.
In this embodiment, after the device to be bound completes networking, a registration binding request may be sent to the first server based on the established network connection.
In step S303, in response to receiving the notification information sent by the first service end, a binding result is returned to the application program.
In this embodiment, after the device to be bound sends a registration binding request to the first server, a binding result may be returned to the application program in response to receiving the notification information sent by the first server. The notification information may be used to notify that the device to be bound has completed binding between the first server and the second server.
For example, after receiving the registration binding request, the first service end may synchronize the request to the second service end to trigger the second service end to bind the device to be bound, and wait for the second binding device to return a binding result. After the second server finishes binding, a corresponding binding result can be returned to the first server, so that the first server can bind the device to be bound after receiving the binding result returned by the second server, and further can send a final binding result to the device to be bound through a preset long connection (such as an ot _ client channel) after binding is finished, wherein the final binding result can be used for representing that the first server and the second server finish binding the device to be bound. Further, the device to be bound notifies the binding result to the application program, so that the binding result is shown to the user through the application program.
As can be seen from the above description, in the method of this embodiment, by responding to the received registration information sent by the application, performing networking based on the registration information, and after the networking is completed, sending a registration binding request to the first server, and then responding to the received notification information sent by the first server, and returning a binding result to the application, a unified device-to-distribution network binding process can be implemented, the compatibility of a distribution network binding scheme with different applications is improved, and then the early-stage development cost of the intelligent device can be reduced, which is beneficial to later maintenance.
Fig. 4 is a flowchart illustrating another method for binding a device distribution network according to an exemplary embodiment of the disclosure; the method of the embodiment can be applied to a device to be bound (e.g., a smart speaker, a smart watch, a wearable device, or the like).
As shown in fig. 4, the method comprises the following steps S401-S403:
in step S401, in response to receiving registration information sent by an application, networking is performed based on the registration information.
In step S402, a long connection between the first service end and the device to be bound is pre-constructed.
In this embodiment, in order to send a registration binding request to the first server based on the long connection after the device to be bound completes networking, the long connection between the first server and the device to be bound may be pre-constructed.
It should be noted that the type of the long connection may be set based on actual needs, and this embodiment is not limited to this.
In one embodiment, the long connection may be an ot _ client channel. It can be understood that the ot _ client channel is used for information transmission, and compared with the messagingagent long connection adopted in the traditional scheme, the current distribution network binding scheme can be ensured not to distinguish different application programs, and the compatibility of the current distribution network binding flow scheme can be improved.
In step S403, after the networking is completed, a registration binding request is sent to the first server based on the long connection.
In step S404, in response to receiving the notification information sent by the first service end, a binding result is returned to the application program.
For the explanation and description of steps S401 and S403-S404, reference may be made to the above embodiments, which are not repeated herein.
In an embodiment, a bluetooth connection between the application program and the device to be bound may also be pre-constructed. On this basis, the method of the above embodiment may further include any one of:
receiving the registration information sent by the application program based on the Bluetooth connection;
and executing the operation of returning the binding result to the application program based on the Bluetooth connection.
As can be seen from the above description, in this embodiment, by pre-constructing the ot _ client channel type long connection between the first server and the device to be bound, it can be achieved that after the subsequent device to be bound completes networking, a registration binding request is sent to the first server based on the long connection, and compared with the messagingent long connection adopted in the conventional scheme, it can be ensured that the current distribution network binding scheme does not need to distinguish different application programs, and thus the compatibility of the current distribution network binding flow scheme can be improved.
Fig. 5 is a schematic view of an application scenario of a device distribution network binding method according to an exemplary embodiment of the present disclosure; as shown in fig. 5, the application scenario mainly involves a first service end (e.g., mijia server), a second service end (e.g., mico service end), a device to be bound (e.g., smart speaker, etc.), and an application installed on a terminal device (e.g., smart phone, etc.) of a user. For example, when the user needs to perform distribution network binding on the device to be bound, the device to be bound may be scanned in an application program pre-installed on the terminal device, and after the device to be bound is scanned, an option of binding the device to the distribution network may be triggered, so as to start the distribution network binding process of steps S1 to S7:
s1: obtaining encrypted information
The application program acquires encryption information such as bind key (e.g., encrypted registration information) from the mike server.
S2: bluetooth transmission information
And the application program transmits the registration information to the intelligent loudspeaker box equipment to be bound through the pre-established Bluetooth connection.
S3: upstream binding
After the smart sound box device acquires the information, networking can be performed, and then a registration binding request is initiated to the mike server through a preset long connection (such as an ot _ client channel) after networking.
S4: binding synchronization
After receiving the registration binding request, the mikey server can synchronize the request to the micro server to trigger the micro server to bind the intelligent loudspeaker box device, and wait for the micro server to return a binding result.
S5: returning binding results
After the binding of the micro server is completed, the corresponding binding result can be returned to the Mijia server.
S6: down instruction
After receiving the binding result returned by the micro server, the mikey server can bind the intelligent loudspeaker box device, and then after binding is completed, the mikey server can send a final binding result to the intelligent loudspeaker box device through a preset long connection (such as an ot _ client channel), wherein the final binding result can be used for representing that the mikey server and the micro server have both completed binding the intelligent loudspeaker box device.
S7: binding results
And the intelligent sound box device informs the binding result to the application program so as to show the binding result to the user through the application program.
Fig. 6 is a block diagram illustrating an apparatus for binding a device distribution network according to an exemplary embodiment of the disclosure; the apparatus of this embodiment may be applied to a first service end (e.g., a server or a server cluster composed of multiple servers).
As shown in fig. 6, the apparatus may include: a binding request sending module 110, a binding device binding module 120, and a notification information sending module 130, wherein:
a binding request sending module 110, configured to, in response to receiving a registration binding request sent by a device to be bound, send the registration binding request to a second server;
a 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;
a notification information sending module 130, configured to send, in response to completion of binding the device to be bound, notification information to the device to be bound, where the notification information is used to notify that the device to be bound has completed binding between the first service end and the second service end.
As can be seen from the above description, the apparatus of this embodiment sends, in response to receiving a registration binding request sent by a device to be bound, the registration binding request to a second server, and in response to detecting that the second server binds the device to be bound successfully, binds the device to be bound, and further in response to completing the binding of the device to be bound, sends notification information to the device to be bound, where the notification information is used to notify that the device to be bound has completed the binding of the first server and the second server, so that a unified device-to-device network binding process can be implemented, compatibility of a network binding scheme with different application programs is improved, and further early-stage development cost of an intelligent device can be reduced, and later maintenance is facilitated.
Fig. 7 is a block diagram illustrating yet another device distribution network binding apparatus according to an exemplary embodiment of the disclosure; the apparatus of this embodiment may be applied to a first service end (e.g., a server or a server cluster composed of multiple servers). The binding request sending module 210, the binding device binding module 220, and the notification information sending module 230 have the same functions as the binding request sending module 110, the binding device binding module 120, and the notification information sending module 130 in the embodiment shown in fig. 6, and are not described herein again.
On the basis of the embodiment shown in fig. 6, detecting that the second server successfully binds to the device to be bound may include:
and receiving preset information returned by the second server, wherein the preset information is used for representing that the second server finishes binding the equipment to be bound.
As shown in fig. 7, the above apparatus further includes:
a first long connection construction module 230, configured to construct a long connection between the first service end and the device to be bound in advance;
on this basis, the notification information sending module 240 may be further configured to perform the operation of sending the notification information to the device to be bound based on the long connection.
Fig. 8 is a block diagram illustrating an apparatus for binding a device distribution network according to an exemplary embodiment of the disclosure; the apparatus of this embodiment may be applied to a device to be bound (e.g., a smart speaker, a smart watch, or a wearable device, etc.). As illustrated in fig. 8, the apparatus may include: a networking module 310, a request sending module 320, and a result returning module 330, wherein:
a networking module 310, configured to, in response to receiving registration information sent by an application program, perform networking based on the registration information;
a request sending module 320, configured to send a registration binding request to the first server after networking is completed;
a result returning module 330, configured to return a binding result to the application program in response to receiving notification information sent by the first server, where the notification information is used to notify that the device to be bound has completed binding between the first server and the second server.
As can be seen from the above description, the device of this embodiment performs networking based on the registration information in response to the received registration information sent by the application program, sends a registration binding request to the first server after completing networking, and returns a binding result to the application program in response to receiving the notification information sent by the first server, so that a unified device-to-distribution network binding process can be implemented, the compatibility of a distribution network binding scheme with different application programs is improved, the early-stage development cost of the intelligent device can be reduced, and the later-stage maintenance is facilitated.
Fig. 9 is a block diagram illustrating yet another device distribution network binding apparatus according to an exemplary embodiment of the disclosure; the apparatus of this embodiment may be applied to a device to be bound (e.g., a smart speaker, a smart watch, or a wearable device, etc.). The networking module 410, the request sending module 420 and the result returning module 430 have the same functions as the networking module 310, the request sending module 320 and the result returning module 330 in the embodiment shown in fig. 8, and are not described herein again.
As shown in fig. 8, the apparatus may further include:
a second long connection construction module 440, configured to construct a long connection between the first service end and the device to be bound in advance;
on this basis, the request sending module 420 may be further configured to perform the operation of sending the registration binding request to the first service end based on the long connection.
In an embodiment, the apparatus may further include:
a bluetooth connection constructing module 450, configured to construct a bluetooth connection between the application program and the device to be bound in advance.
In an embodiment, the apparatus may further include:
a registration information receiving module 460, configured to receive the registration information sent by the application program based on the bluetooth connection.
In an embodiment, the result returning module 430 may be further configured to perform the operation of returning the binding result to the application program based on the bluetooth connection.
On the other hand, the embodiment of the disclosure also provides a device distribution network binding system, which may include a device to be bound, a first service end and a second service end;
the first server may be configured to execute the device distribution network binding method shown in fig. 1 or fig. 2;
and the device to be bound may be configured to perform the device network binding method shown in fig. 3 or fig. 4.
With regard to the apparatus in the above-described embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.
FIG. 10 is a block diagram illustrating an electronic device in accordance with an example 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, an exercise device, a personal digital assistant, and so forth.
Referring to fig. 10, device 900 may include one or more of the following components: processing component 902, memory 904, power component 906, multimedia component 908, audio component 910, input/output (I/O) interface 912, sensor component 914, and communication component 916.
The processing component 902 generally controls the overall operation of the device 900, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. Processing component 902 may include one or more processors 920 to execute instructions to perform all or a portion of the steps of the methods described above. Further, processing component 902 can include one or more modules that facilitate interaction between processing component 902 and other components. For example, the processing component 902 can include a multimedia module to facilitate interaction between the multimedia component 908 and the processing component 902.
The memory 904 is configured to store various types of data to support operation at the device 900. Examples of such data include instructions for any application or method operating on device 900, contact data, phonebook data, messages, pictures, videos, and so forth. The memory 904 may be implemented by any type or combination of volatile or non-volatile memory devices 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 or optical disks.
The power component 906 provides power to the various components of the device 900. The power components 906 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device 900.
The multimedia components 908 include a screen that provides an output interface between the device 900 and a 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 an input signal from a 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 boundary of a 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 facing camera and/or a rear facing camera. The front-facing camera and/or the rear-facing camera may receive external multimedia data when the device 900 is in an operating mode, such as a shooting mode or a video mode. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.
The audio component 910 is configured to output and/or input audio signals. For example, audio component 910 includes a Microphone (MIC) configured to receive external audio signals when device 900 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals may further be stored in the memory 904 or transmitted via the communication component 916. In some embodiments, audio component 910 also includes a speaker for outputting audio signals.
I/O interface 912 provides an interface between processing component 902 and peripheral interface modules, which may be 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.
The sensor component 914 includes one or more sensors for providing status assessment of various aspects of the device 900. For example, the sensor component 914 may detect an open/closed state of the device 900, the relative positioning of components, such as a display and keypad of the device 900, the sensor component 914 may also detect a change in the position of the device 900 or a component of the device 900, the presence or absence of user contact with the device 900, orientation or acceleration/deceleration of the device 900, and a change in the temperature of the device 900. The sensor assembly 914 may also include a proximity sensor configured to detect the presence of a nearby object in the absence of any physical contact. The sensor assembly 914 may 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 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
The communication component 916 is configured to facilitate communications between the device 900 and other devices in a wired or wireless manner. The device 900 may 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 associated information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 916 further includes a Near Field Communication (NFC) module to facilitate short-range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.
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, micro-controllers, microprocessors or other electronic components for performing the above-described methods.
In an exemplary embodiment, a non-transitory computer readable storage medium comprising instructions, such as the memory 904 comprising instructions, executable by the processor 920 of the device 900 to perform the above-described method is also provided. For example, the non-transitory computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It will be understood that the present disclosure is not limited to the precise arrangements 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 (13)

1. A device distribution network binding method is applied to a first service end, and comprises the following steps:
responding to a received registration binding request sent by a device to be bound, and sending the registration binding request to a second server;
binding the device to be bound in response to detecting that the second server is successfully bound to the device to be bound;
and in response to the completion of the binding of the device to be bound, sending notification information to the device to be bound, wherein the notification information is used for notifying the device to be bound that the binding of the first service end and the second service end is completed.
2. The method of claim 1, wherein the detecting that the second server successfully binds to the device to be bound comprises:
and receiving preset information returned by the second server, wherein the preset information is used for representing that the second server finishes binding the equipment to be bound.
3. The method of claim 1, further comprising:
pre-constructing a long connection between the first service terminal and the equipment to be bound;
and executing the operation of sending the notification information to the device to be bound based on the long connection.
4. A device distribution network binding method is applied to a device to be bound, and comprises the following steps:
responding to the received registration information sent by the application program, and networking based on the registration information;
after networking is completed, a registration binding request is sent to a first server;
and in response to receiving notification information sent by the first service end, returning a binding result to the application program, wherein the notification information is used for notifying the device to be bound that the binding of the first service end and the second service end is completed.
5. The method of claim 4, further comprising:
pre-constructing a long connection between the first service terminal and the equipment to be bound;
and executing the operation of sending the registration binding request to the first service terminal based on the long connection.
6. The method of claim 4, further comprising:
and pre-constructing the Bluetooth connection between the application program and the device to be bound.
7. The method of claim 6, further comprising:
and receiving the registration information sent by the application program based on the Bluetooth connection.
8. The method of claim 6, further comprising:
and executing the operation of returning the binding result to the application program based on the Bluetooth connection.
9. An apparatus for binding a distribution network of a device, applied to a first service end, the apparatus comprising:
the binding request sending module is used for responding to a received registration binding request sent by the equipment to be bound and sending the registration binding request to the second server;
the binding device binding module is used for binding the device to be bound in response to the detection that the second server is successfully bound to the device to be bound;
and the notification information sending module is used for responding to the completion of the binding of the device to be bound and sending notification information to the device to be bound, wherein the notification information is used for notifying the device to be bound that the binding of the first service end and the second service end is completed.
10. The device distribution network binding device is applied to a device to be bound, and comprises:
the networking module is used for responding to the received registration information sent by the application program and networking based on the registration information;
the request sending module is used for sending a registration binding request to the first server after networking is finished;
and the result returning module is used for returning a binding result to the application program in response to receiving notification information sent by the first service end, wherein the notification information is used for notifying the device to be bound that the binding of the first service end and the second service end is completed.
11. The equipment distribution network binding system is characterized by comprising equipment to be bound, a first service end and a second service end;
the first server is used for executing the device distribution network binding method in any one of the claims 1 to 3;
the device to be bound is used for executing the device distribution network binding method of any one of the claims 4 to 8.
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 perform the device network binding method of any of the above claims 1-3 or any of the above claims 4-8 when executing the computer program.
13. A computer-readable storage medium, on which a computer program is stored, which program, when being executed by a processor, is adapted to carry out the device-network-binding method of any one of the preceding claims 1 to 3 or of any one of the preceding claims 4 to 8.
CN202110863845.3A 2021-07-29 2021-07-29 Equipment distribution network binding method, device, equipment and storage medium Pending CN113596838A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110863845.3A CN113596838A (en) 2021-07-29 2021-07-29 Equipment distribution network binding method, device, equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110863845.3A CN113596838A (en) 2021-07-29 2021-07-29 Equipment distribution network binding method, device, equipment and storage medium

Publications (1)

Publication Number Publication Date
CN113596838A true CN113596838A (en) 2021-11-02

Family

ID=78251831

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110863845.3A Pending CN113596838A (en) 2021-07-29 2021-07-29 Equipment distribution network binding method, device, equipment and storage medium

Country Status (1)

Country Link
CN (1) CN113596838A (en)

Citations (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104580265A (en) * 2015-02-13 2015-04-29 小米科技有限责任公司 Equipment binding method and equipment binding device
CN104660618A (en) * 2015-03-24 2015-05-27 联想(北京)有限公司 Binding method and binding equipment
US20160234260A1 (en) * 2015-02-05 2016-08-11 Xiaomi Inc. Methods and apparaturses for binding with device
US20160269527A1 (en) * 2015-03-13 2016-09-15 Xiaomi Inc. Methods and apparatuses for binding with device
CN106302762A (en) * 2016-08-19 2017-01-04 北京小米移动软件有限公司 Smart machine binding method and device
CN107548059A (en) * 2016-06-28 2018-01-05 中兴通讯股份有限公司 A kind of authentication method and system
CN109040122A (en) * 2018-09-14 2018-12-18 小雅智能平台（深圳）有限公司 The method, apparatus and related accessory of a kind of new user's registration and binding service equipment
CN109361771A (en) * 2018-12-11 2019-02-19 湖北科技学院 Registration, certification, the connection method of a kind of Internet of things system and its equipment
CN109714769A (en) * 2018-12-28 2019-05-03 北京深思数盾科技股份有限公司 Information binding method, device, equipment and storage medium
CN110971495A (en) * 2019-10-24 2020-04-07 青岛海尔科技有限公司 Equipment binding method and device of intelligent household system and storage medium
CN111031522A (en) * 2019-11-18 2020-04-17 北京小米移动软件有限公司 Device binding method, device binding apparatus, and computer-readable storage medium
CN111988781A (en) * 2020-08-31 2020-11-24 上海上实龙创智能科技股份有限公司 Verification method and system for safe access of Internet of things equipment
CN112073115A (en) * 2020-09-02 2020-12-11 东方红卫星移动通信有限公司 Lora-based low-orbit satellite Internet of things registration security verification method, Internet of things terminal, network server and user server
US20210075636A1 (en) * 2017-08-28 2021-03-11 Hefei Midea Intelligent Technologies Co., Ltd. Smart refrigerator-based networking and control method and system, and smart refrigerator
CN112511653A (en) * 2021-02-03 2021-03-16 武汉慧联无限科技有限公司 Service authority activation method, configuration method and registration method of Internet of things equipment
CN113038434A (en) * 2019-12-09 2021-06-25 华为技术有限公司 Device registration method and device, mobile terminal and storage medium
CN113098976A (en) * 2021-04-20 2021-07-09 深圳市康冠科技股份有限公司 IOT equipment network distribution method and device and computer storage medium
CN113132185A (en) * 2019-12-30 2021-07-16 深圳Tcl新技术有限公司 Equipment distribution network binding method and system, mobile terminal and storage medium

Patent Citations (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160234260A1 (en) * 2015-02-05 2016-08-11 Xiaomi Inc. Methods and apparaturses for binding with device
CN104580265A (en) * 2015-02-13 2015-04-29 小米科技有限责任公司 Equipment binding method and equipment binding device
US20160269527A1 (en) * 2015-03-13 2016-09-15 Xiaomi Inc. Methods and apparatuses for binding with device
CN104660618A (en) * 2015-03-24 2015-05-27 联想(北京)有限公司 Binding method and binding equipment
CN107548059A (en) * 2016-06-28 2018-01-05 中兴通讯股份有限公司 A kind of authentication method and system
CN106302762A (en) * 2016-08-19 2017-01-04 北京小米移动软件有限公司 Smart machine binding method and device
US20210075636A1 (en) * 2017-08-28 2021-03-11 Hefei Midea Intelligent Technologies Co., Ltd. Smart refrigerator-based networking and control method and system, and smart refrigerator
CN109040122A (en) * 2018-09-14 2018-12-18 小雅智能平台（深圳）有限公司 The method, apparatus and related accessory of a kind of new user's registration and binding service equipment
CN109361771A (en) * 2018-12-11 2019-02-19 湖北科技学院 Registration, certification, the connection method of a kind of Internet of things system and its equipment
CN109714769A (en) * 2018-12-28 2019-05-03 北京深思数盾科技股份有限公司 Information binding method, device, equipment and storage medium
CN110971495A (en) * 2019-10-24 2020-04-07 青岛海尔科技有限公司 Equipment binding method and device of intelligent household system and storage medium
CN111031522A (en) * 2019-11-18 2020-04-17 北京小米移动软件有限公司 Device binding method, device binding apparatus, and computer-readable storage medium
CN113038434A (en) * 2019-12-09 2021-06-25 华为技术有限公司 Device registration method and device, mobile terminal and storage medium
CN113132185A (en) * 2019-12-30 2021-07-16 深圳Tcl新技术有限公司 Equipment distribution network binding method and system, mobile terminal and storage medium
CN111988781A (en) * 2020-08-31 2020-11-24 上海上实龙创智能科技股份有限公司 Verification method and system for safe access of Internet of things equipment
CN112073115A (en) * 2020-09-02 2020-12-11 东方红卫星移动通信有限公司 Lora-based low-orbit satellite Internet of things registration security verification method, Internet of things terminal, network server and user server
CN112511653A (en) * 2021-02-03 2021-03-16 武汉慧联无限科技有限公司 Service authority activation method, configuration method and registration method of Internet of things equipment
CN113098976A (en) * 2021-04-20 2021-07-09 深圳市康冠科技股份有限公司 IOT equipment network distribution method and device and computer storage medium

Similar Documents

Publication Publication Date Title
EP3038397B1 (en) Method and device for p2p wifi connection
CN105516183B (en) Equipment connection method and device
EP3226432B1 (en) Method and devices for sharing media data between terminals
CN109274510B (en) Message processing method, device, client, server and storage medium
EP3062487A1 (en) Method and apparatus for detecting smart device
CN109582400B (en) Program calling method and device
EP3223147A2 (en) Method for accessing virtual desktop and mobile terminal
CN107635074B (en) Method, apparatus and computer-readable storage medium for controlling alarm
CN105100074A (en) Data operation processing method, device and terminal equipment
JP2017513416A (en) Data transmission method, apparatus, facility, program, and recording medium
CN111010721A (en) Wireless network distribution method, wireless network distribution device and computer readable storage medium
CN105578391B (en) Information processing method, device and system and terminal equipment
CN111541922B (en) Method, device and storage medium for displaying interface input information
CN110121148B (en) Interphone team method and device
CN109245992B (en) Request processing method and device, electronic equipment and storage medium
CN107277422B (en) Video call method, device and system
CN112954596B (en) Data sharing method, device, equipment and storage medium
CN105159181A (en) Control method and device for intelligent equipment
CN105530594A (en) Communication method and device based remote control
WO2022047804A1 (en) Time gap request method and apparatus, and time gap configuration method and apparatus
CN114615647A (en) Call control method, device and storage medium
CN113596838A (en) Equipment distribution network binding method, device, equipment and storage medium
CN113726905A (en) Data acquisition method, device and equipment based on home terminal equipment
CN109194639B (en) Message receiving and processing method, device, terminal and readable storage medium
CN107734072B (en) Processing method and device for push information

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination