WO2016124015A1 - 设备绑定方法和装置 - Google Patents

设备绑定方法和装置 Download PDF

Info

Publication number
WO2016124015A1
WO2016124015A1 PCT/CN2015/093205 CN2015093205W WO2016124015A1 WO 2016124015 A1 WO2016124015 A1 WO 2016124015A1 CN 2015093205 W CN2015093205 W CN 2015093205W WO 2016124015 A1 WO2016124015 A1 WO 2016124015A1
Authority
WO
WIPO (PCT)
Prior art keywords
binding
binding request
area network
local area
sent
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.)
Ceased
Application number
PCT/CN2015/093205
Other languages
English (en)
French (fr)
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.)
Xiaomi Inc
Original Assignee
Xiaomi Inc
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 Xiaomi Inc filed Critical Xiaomi Inc
Priority to RU2016116759A priority Critical patent/RU2644509C2/ru
Priority to JP2016572884A priority patent/JP6195685B2/ja
Priority to KR1020157036561A priority patent/KR101779484B1/ko
Priority to MX2016002216A priority patent/MX373351B/es
Publication of WO2016124015A1 publication Critical patent/WO2016124015A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1069—Session establishment or de-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/20—Network architectures or network communication protocols for network security for managing network security; network security policies in general
    • H04L63/205—Network architectures or network communication protocols for network security for managing network security; network security policies in general involving negotiation or determination of the one or more network security mechanisms to be used, e.g. by negotiation between the client and the server or between peers or by selection according to the capabilities of the entities involved
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H04L61/2503—Translation of Internet protocol [IP] addresses
    • H04L61/2517—Translation of Internet protocol [IP] addresses using port numbers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1073—Registration or de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/08—Access security
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/107—Network architectures or network communication protocols for network security for controlling access to devices or network resources wherein the security policies are location-dependent, e.g. entities privileges depend on current location or allowing specific operations only from locally connected terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/60—Context-dependent security
    • H04W12/63—Location-dependent; Proximity-dependent

Definitions

  • the present disclosure relates to the field of communications, and in particular, to a device binding method and apparatus.
  • the current practice is usually to use the device binding method to establish a binding relationship between the user and the smart device. Since the binding relationship is established, only the bound user has access and Controlling the permissions of the smart device, so in the process of establishing a binding relationship between the user and the smart device, it is bound to face higher security requirements.
  • the present disclosure provides a device binding method and apparatus.
  • a device binding method comprising:
  • the binding request carrying a user login ID of the local terminal
  • the binding request is sent from the local area network
  • the binding request is sent to the server, and the binding relationship between the user login ID and the device is established by the server.
  • the notification message that the binding is successfully sent by the server is received, and the notification message is forwarded to the local terminal.
  • the receiving the binding request sent by the local terminal includes:
  • the UDP port is intercepted, and a binding request sent by the local terminal in the local area network to the local device based on the port number of the UDP port is obtained.
  • the method further includes:
  • the binding request is issued from the external network, the binding request is discarded.
  • the determining whether the binding request is sent from a local area network includes:
  • a device binding method comprising:
  • the server to be bound And receiving, by the server to be bound, the binding request to be successfully sent by the server to be bound, where the binding message is sent to the server, and the server successfully establishes the user login by the server Issued after the binding relationship between the ID and the device to be bound.
  • the transport service in the local area network includes the UDP service
  • the sending the binding request to the device to be bound in the local local area network includes:
  • a device binding apparatus comprising:
  • a first receiving module configured to receive a binding request sent by the local terminal, where the binding request carries a user login ID of the local terminal;
  • a determining module configured to determine whether the binding request is sent from a local area network
  • a first sending module configured to send the binding request to a server when the binding request is sent from a local area network, where the server establishes a binding relationship between the user login ID and the local device;
  • a forwarding module configured to: after the establishment of the binding relationship is complete, receive an advertisement message that is successfully sent by the server, and forward the advertisement message to the local terminal.
  • the first receiving module includes:
  • a broadcast submodule configured to broadcast, in a local area network, a port number of a UDP port opened by the UDP service;
  • the obtaining sub-unit is configured to listen to the UDP port, and obtain a binding request sent by the local terminal in the local local area network to the local device based on the port number of the UDP port.
  • the device further includes:
  • a discarding module is configured to discard the binding request when the binding request is sent from the external network.
  • the determining module includes:
  • a determining submodule configured to determine whether the IP address in the binding request matches an IP network segment of the local local area network
  • a first determining submodule configured to: when the IP address in the binding request matches an IP network segment of the local local area network, determine that the binding request is sent from a local local area network;
  • the second determining submodule is configured to determine that the binding request is sent from the external network when the IP address in the binding request does not match the IP network segment of the local local area network.
  • a device binding apparatus comprising:
  • a second sending module configured to send a binding request to the device to be bound in the local area network, where the binding request carries a user login ID of the device;
  • a second receiving module configured to receive an advertisement message that is successfully bound by the device to be bound, where the notification message is sent to the server by the device to be bound, by the service
  • the terminal sends the binding relationship between the user login ID and the device to be bound.
  • the second sending module includes:
  • a first sending submodule configured to send a binding request to the to-be-bound device based on a locally preset port number of a UDP port opened by the UDP server;
  • a receiving submodule configured to receive a port number of the UDP port open by the UDP service broadcasted by the device to be bound in a local area network
  • the second sending submodule sends a binding request to the to-be-bound device based on the received port number.
  • a device binding apparatus including:
  • a memory for storing processor executable instructions
  • processor is configured to:
  • the binding request carrying a user login ID of the local terminal
  • the binding request is sent from the local area network
  • the binding request is sent to the server, and the binding relationship between the user login ID and the device is established by the server.
  • the notification message that the binding is successfully sent by the server is received, and the notification message is forwarded to the local terminal.
  • a device binding apparatus including:
  • a memory for storing processor executable instructions
  • processor is configured to:
  • the device to be bound is used to receive the bearer user login ID sent by the local terminal. Determining the request, and then determining whether the binding request is sent from the local area network.
  • the binding request is sent to the server, and the server establishes the user login ID and the to-be-tied Binding relationship between devices; the device to be bound only receives the binding request sent by the local terminal, and the binding relationship can be established only when the binding request is sent from the local local area network, so that the binding relationship cannot be established outside the local area network.
  • the terminal establishes a binding relationship, so that the error binding caused by the user login ID leakage can be avoided, thereby improving the security of the device itself.
  • FIG. 1 is a schematic flowchart diagram of a device binding method according to an exemplary embodiment
  • FIG. 2 is a schematic flowchart diagram of another device binding method according to an exemplary embodiment
  • FIG. 3 is a schematic flowchart diagram of another device binding method according to an exemplary embodiment
  • FIG. 4 is a schematic block diagram of a device binding apparatus according to an exemplary embodiment
  • FIG. 5 is a schematic block diagram of another device binding apparatus according to an exemplary embodiment
  • FIG. 6 is a schematic block diagram of another device binding apparatus according to an exemplary embodiment
  • FIG. 7 is a schematic block diagram of another device binding apparatus according to an exemplary embodiment.
  • FIG. 8 is a schematic block diagram of another device binding apparatus according to an exemplary embodiment
  • FIG. 9 is a schematic block diagram of another device binding apparatus according to an exemplary embodiment.
  • FIG. 10 is a schematic block diagram of another device binding apparatus according to an exemplary embodiment.
  • FIG. 11 is a schematic structural diagram of a device binding apparatus according to an exemplary embodiment.
  • first, second, third, etc. may be used in the present disclosure to describe various information, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
  • first information may also be referred to as second information without departing from the scope of the present disclosure.
  • second information may also be referred to as First information.
  • word "if” as used herein may be interpreted as "when” or “when” or “in response to a determination.”
  • the user can complete the registration by installing the client software of the smart device on the terminal, and then the login account (user login ID) after successful registration is passed through the corresponding server.
  • the smart device establishes a binding relationship to implement. After the binding relationship is established, the user already has the master authority of the smart device. After the subsequent user succeeds the client software of the smart device through the login account, the client software can interact with the smart device through the client software.
  • the smart device can perform operations such as accessing and controlling; for example, the smart device can be a smart home device, and after the user's login account establishes a binding relationship with the smart home device, the user can control through the client software of the smart home device. The opening and closing of the smart home.
  • the smart device in the local area network usually needs to access the Internet.
  • the smart device since the smart device usually has the characteristics of open interaction and operation, the user will log in to the account.
  • the server In the process of binding with the smart device, once the login account of the user is leaked, since the server establishes the legality of the binding user based on the login account only during the establishment of the binding relationship, other users use the login. The account can successfully complete the binding process with the smart device, thereby causing the wrong binding to make the smart device face a serious security risk.
  • the present disclosure proposes a device binding method, which receives a user login ID binding request sent by a local terminal through a device to be bound, and then determines whether the binding request is sent from a local local area network, when the binding request is made.
  • the binding request is sent to the server, and the binding relationship between the user login ID and the device to be bound is established by the server;
  • the binding request is made, and the binding relationship can be established only when the binding request is sent from the local local area network, so that the binding relationship cannot be established with the terminal outside the local local area network, so that the error binding caused by the user login account leakage can be avoided. Therefore, the security of the device itself can be improved.
  • FIG. 1 is a device binding method according to an exemplary embodiment.
  • the device binding method is used in a smart device, and includes the following steps:
  • step 101 a binding request sent by a local terminal is received; the binding request carries a user login ID of the local terminal;
  • step 102 it is determined whether the binding request is sent from a local area network
  • step 103 when the binding request is sent from the local area network, the binding request is sent to the server, and the binding relationship between the user login ID and the device is established by the server.
  • step 104 after the binding relationship is established, the notification message of the binding success sent by the server is received, and the notification message is forwarded to the local terminal.
  • the local local area network may be a WI-FI based wireless local area network
  • the smart device may be a smart device with a built-in WI-FI module.
  • the smart device can access the wireless local area network through the built-in WIFI module, and simultaneously The user may also access the terminal to the wireless local area network.
  • the smart device and the terminal are in the same local area network, and subsequent users can operate the terminal.
  • the client software of the smart device installed on the smart device initiates a binding operation with the smart device to obtain access and control rights of the smart device; for example, when implemented, an "initiation tie" may be provided on the client software.
  • the function switch of the user can initiate a binding operation with the smart device by turning on the function switch.
  • the client When the user binds to the smart device through the client software, the client sends a binding request carrying the login account of the user and the ID of the smart device to the server through the client software.
  • the authentication account After the authentication account is authenticated, if the smart device has not established a binding relationship with other users, the binding relationship between the login account and the smart device can be directly established locally. Because the server is authenticated based on the user login account during the establishment of the binding relationship, once the login account is compromised, the other illegal users may be successfully bound to the smart device, thereby facing a security risk.
  • the device that is in the same local area network as the smart device (that is, the local terminal) is generally a reliable device, in order to improve the security in the process of establishing a binding relationship between the user and the smart device, the error binding is avoided.
  • the problem is that in the binding process, the smart device can only accept the binding initiated by the device in the local wireless local area network, and the user of the non-local local area network cannot initiate the binding with the smart device, thereby minimizing the probability of error binding. .
  • the smart device can locally enable a local WLAN-oriented transport service, and after the transport service is enabled, the client software can send a binding request to the smart device based on the transport service, the smart The device may receive a binding request sent by the device in the local wireless local area network based on the transmission service, and then the smart device sends the received binding request to the server to complete the establishment of the binding relationship.
  • the binding request is no longer sent by the user directly to the server through the client software, but is sent by the smart device to be bound, it can be ensured that the binding request received by the server comes from The device in the local area network of the smart device limits the binding party when binding the smart device to a reliable device in the local area network of the smart device.
  • the transmission service for the local wireless local area network may be a UDP service.
  • the technical solution of the present disclosure is described below by taking the transmission service as a UDP service as an example.
  • a UDP port for the local wireless local area network may be opened by default in the background.
  • the port number of the UDP port is not specifically limited in this embodiment, for example, Is the non-famous port number or private network port number in the UDP port number.
  • the port number of the UDP port number can be configured in advance in the client software of the smart device. When the user initiates binding with the smart device by operating the client software, the client software can be advanced according to the The configured UDP port number sends a binding request to the UDP port, and the binding request may carry the login account of the user.
  • the binding request may also carry the ID of the smart device (for example, the hardware address of the smart device).
  • the smart device may also send a broadcast message in the local wireless local area network, and notify the port number of the enabled UDP port. For all clients in the local wireless LAN that receive the broadcast message software.
  • the smart device when receiving the binding request sent by the client software in the local wireless local area network, the smart device may monitor the UDP port in real time after the UDP port is enabled, once the UDP port is received from the local
  • the binding request can be obtained from the UDP port immediately, and the obtained binding request is sent from the local local area network, if the binding request is from the local local area network.
  • the binding request is sent to the server, and the binding relationship between the user login ID and the smart device in the binding request is established by the server.
  • the smart device determines whether the obtained binding request is sent from the local local area network, and can be implemented by determining whether the IP address in the binding request is an IP network segment of the local local area network. For example, the smart device can obtain the gateway IP address of the local wireless local area network and the subnet mask from the local gateway, determine the IP network segment of the local local area network according to the gateway IP address and the subnet mask, and then set the IP address in the binding request. Match with the IP network segment of the local area network. If it matches, then it can be determined that the binding request is sent from the local area network; on the contrary, if it does not match, the binding request may come from the external network at this time, for the external network. Binding requests are considered for security reasons and can be discarded directly by smart devices.
  • the server may first perform verification on the login account in the binding request, and if the verification succeeds, the server may also query the binding request. Whether the ID of the smart device in the local device has established a binding relationship with other users locally. If not, the server can directly establish the binding between the login account and the ID of the smart device in the binding request. relationship. After the binding relationship is successfully established, the server may send a binding success notification message to the smart device, and then the smart device forwards the notification message to the corresponding terminal in the local area network, and the subsequent user can successfully bind through the binding.
  • the login account is logged into the client software of the smart device to remotely access and control the smart device.
  • the local wireless local area network-based transmission service may have other implementations besides the UDP service, for example, the transmission service may also be an HTTP service.
  • the transmission service is an HTTP service
  • the smart setting may enable a private network IP address for the local wireless local area network, and the user may perform HTTP-based communication with the smart device based on the private network IP address through the client software on the terminal.
  • the smart device sends a binding request, which is not detailed in the embodiment.
  • the device to be bound receives the carrying user login ID binding request sent by the local terminal, and then determines whether the binding request is sent from the local local area network, and when the binding request is sent from the local local area network, The binding request is sent to the server, and the binding relationship between the user login ID and the device to be bound is established by the server; the device to be bound only receives the binding request sent by the local terminal, and only When the binding request is sent from the local area network, the binding relationship can be established, so that the binding relationship cannot be established with the terminal outside the local area network. Therefore, the error binding caused by the user login account leakage can be avoided, thereby improving the device itself. safety.
  • FIG. 2 is another device binding method according to an exemplary embodiment, where the method is used in a terminal, and the method includes the following steps:
  • step 201 a binding request is sent to the device to be bound in the local area network, where the binding request carries the user login ID of the device;
  • step 202 the notification message that the binding is successfully forwarded by the device to be bound is received, where the notification message is sent to the server by the device to be bound, and the server succeeds.
  • the binding relationship between the user login ID and the device to be bound is established.
  • the local local area network may be a WI-FI-based wireless local area network
  • the to-be-bound device may be a smart device with a built-in WI-FI module.
  • the smart device can access the wireless local area network through the built-in WIFI module, and the user can also access the wireless local area network after the smart device and the terminal are successfully accessed.
  • the smart device and the terminal are in the same local area network, and the subsequent user can initiate a binding operation with the smart device by operating the client software of the smart device installed on the terminal to obtain the smart device.
  • Access and control rights for example, when implemented, a function switch of "initiating binding" can be provided on the client software, and the user can initiate a binding operation with the smart device by turning on the function switch.
  • the client When the user binds to the smart device through the client software, the client sends a binding request carrying the login account of the user and the ID of the smart device to the server through the client software.
  • the authentication account After the authentication account is authenticated, if the smart device has not established a binding relationship with other users, the binding relationship between the login account and the smart device can be directly established locally. Because the server is authenticated based on the user login account during the establishment of the binding relationship, once the login account is compromised, the other illegal users may be successfully bound to the smart device, thereby facing a security risk.
  • the device that is in the same local area network as the smart device (that is, the local terminal) is generally a reliable device, in order to improve the security in the process of establishing a binding relationship between the user and the smart device, the error binding is avoided.
  • the problem is that in the binding process, the smart device can only accept the binding initiated by the device in the local wireless local area network, and the user of the non-local local area network cannot initiate the binding with the smart device, thereby minimizing the probability of error binding. .
  • the smart device can locally enable a local WLAN-oriented transport service, and after the transport service is enabled, the client software can send a binding request to the smart device based on the transport service, the smart The device may receive a binding request sent by the device in the local wireless local area network based on the transmission service, and then the smart device sends the received binding request to the server to complete the establishment of the binding relationship.
  • the binding request is no longer sent by the user directly to the server through the client software, but is sent by the smart device to be bound, it can be ensured that the binding request received by the server comes from The device in the local area network of the smart device limits the binding party when binding the smart device to a reliable device in the local area network of the smart device.
  • the transmission service for the local wireless local area network may be a UDP service.
  • the technical solution of the present disclosure is described below by taking the transmission service as a UDP service as an example.
  • a UDP port for the local wireless local area network may be opened by default in the background, where the port number of the UDP port is not limited in this embodiment. For example, it may be a non-famous port number or a private network port number in the UDP port number.
  • the port number of the UDP port number can be configured in advance in the client software of the smart device.
  • the client software can be advanced according to the The configured UDP port number sends a binding request to the UDP port, and the binding request may carry the login account of the user. If there are multiple smart devices in the local wireless local area network, in order to distinguish The binding request may also carry the ID of the smart device (for example, the hardware address of the smart device).
  • the smart device may also send a broadcast message in the local wireless local area network, and notify the port number of the enabled UDP port. Give all client software in the local wireless LAN that received the broadcast message.
  • the smart device when receiving the binding request sent by the client software in the local wireless local area network, the smart device may monitor the UDP port in real time after the UDP port is enabled, once the UDP port is received from the local
  • the binding request can be obtained from the UDP port immediately, and the obtained binding request is sent from the local local area network, if the binding request is from the local local area network.
  • the binding request is sent to the server, and the binding relationship between the user login ID and the smart device in the binding request is established by the server.
  • the smart device determines whether the obtained binding request is sent from the local local area network, and can be implemented by determining whether the IP address in the binding request is an IP network segment of the local local area network. For example, the smart device can obtain the gateway IP address of the local wireless local area network and the subnet mask from the local gateway, determine the IP network segment of the local local area network according to the gateway IP address and the subnet mask, and then set the IP address in the binding request. Match with the IP network segment of the local area network. If it matches, then it can be determined that the binding request is sent from the local area network; on the contrary, if it does not match, the binding request may come from the external network at this time, for the external network. Binding requests are considered for security reasons and can be discarded directly by smart devices.
  • the server may first perform verification on the login account in the binding request, and if the verification succeeds, the server may also query the binding request. Whether the ID of the smart device in the local device has established a binding relationship with other users locally. If not, the server can directly establish the binding between the login account and the ID of the smart device in the binding request. relationship. After the binding relationship is successfully established, the server may send a binding success notification message to the smart device, and then the smart device forwards the notification message to the corresponding terminal in the local area network, and the subsequent user can successfully bind through the binding.
  • the login account is logged into the client software of the smart device to remotely access and control the smart device.
  • the local wireless local area network-based transmission service may have other implementations besides the UDP service, for example, the transmission service may also be an HTTP service.
  • the transmission service is an HTTP service
  • the smart setting may enable a private network IP address for the local wireless local area network, and the user may perform HTTP-based communication with the smart device based on the private network IP address through the client software on the terminal.
  • the smart device sends a binding request, which is not detailed in the embodiment. .
  • the device to be bound is used to receive the carrying user login ID binding request sent by the local terminal, Then, it is determined whether the binding request is sent from the local area network.
  • the binding request is sent to the server, and the server establishes the user login ID and the device to be bound.
  • Binding relationship the device to be bound only receives the binding request sent by the local terminal, and can establish the binding relationship only when the binding request is sent from the local local area network, so that the device cannot be established with the terminal other than the local local area network.
  • the binding relationship can avoid the error binding caused by the user login account leakage, which can improve the security of the device itself.
  • FIG. 3 is another device binding method according to an exemplary embodiment, where the method includes the following steps:
  • step 301 the terminal sends a binding request to the device to be bound in the local area network, where the binding request carries the user login ID of the device;
  • step 302 the device to be bound receives the binding request sent by the local terminal.
  • step 303 the device to be bound determines whether the binding request is sent from a local area network.
  • step 304 when the binding request is sent from the local area network, the device to be bound sends the binding request to the server, and the server establishes the binding of the user login ID to the device. relationship;
  • step 305 after the binding relationship is established, the to-be-bound terminal receives the binding success message sent by the server, and forwards the notification message to the local terminal.
  • the local local area network may be a WI-FI-based wireless local area network
  • the to-be-bound device may be a smart device with a built-in WI-FI module.
  • the smart device can access the wireless local area network through the built-in WIFI module, and the user can also access the wireless local area network after the smart device and the terminal are successfully accessed.
  • the smart device and the terminal are in the same local area network, and the subsequent user can initiate a binding operation with the smart device by operating the client software of the smart device installed on the terminal to obtain the smart device.
  • Access and control rights for example, when implemented, a function switch of "initiating binding" can be provided on the client software, and the user can initiate a binding operation with the smart device by turning on the function switch.
  • the client When the user binds to the smart device through the client software, the client sends a binding request carrying the login account of the user and the ID of the smart device to the server through the client software.
  • the authentication account After the authentication account is authenticated, if the smart device has not established a binding relationship with other users, the binding relationship between the login account and the smart device can be directly established locally. Because the server is authenticated based on the user login account during the establishment of the binding relationship, once the login account is compromised, the other illegal users may be successfully bound to the smart device, thereby facing a security risk.
  • the device that is in the same local area network as the smart device (that is, the local interrupt) is usually a reliable device, in order to improve the security in the process of establishing a binding relationship between the user and the smart device, the error binding is avoided.
  • the problem is that in the binding process, the smart device can only accept the binding initiated by the device in the local wireless local area network, and the user of the non-local local area network cannot initiate the binding with the smart device, thereby minimizing the probability of error binding. .
  • the smart device can enable a local WLAN-oriented transport service locally, enabled After the transmission service, the client software may send a binding request to the smart device based on the transmission service, and the smart device may receive a binding request sent by a device in the local wireless local area network based on the transmission service, and then The smart device sends the received binding request to the server to complete the establishment of the binding relationship.
  • the binding request is no longer sent by the user directly to the server through the client software, but is sent by the smart device to be bound, it can be ensured that the binding request received by the server comes from The device in the local area network of the smart device limits the binding party when binding the smart device to a reliable device in the local area network of the smart device.
  • the transmission service for the local wireless local area network may be a UDP service.
  • the technical solution of the present disclosure is described below by taking the transmission service as a UDP service as an example.
  • a UDP port for the local wireless local area network may be opened by default in the background.
  • the port number of the UDP port is not specifically limited in this embodiment, for example, Is the non-famous port number or private network port number in the UDP port number.
  • the port number of the UDP port number can be configured in advance in the client software of the smart device.
  • the client software can be advanced according to the The configured UDP port number sends a binding request to the UDP port, and the binding request may carry the login account of the user. If there are multiple smart devices in the local wireless local area network, in order to distinguish The binding request may also carry the ID of the smart device (for example, the hardware address of the smart device).
  • the smart device may also send a broadcast message in the local wireless local area network, and notify the port number of the enabled UDP port. Give all client software in the local wireless LAN that received the broadcast message.
  • the smart device when receiving the binding request sent by the client software in the local wireless local area network, the smart device may monitor the UDP port in real time after the UDP port is enabled, once the UDP port is received from the local
  • the binding request can be obtained from the UDP port immediately, and the obtained binding request is sent from the local local area network, if the binding request is from the local local area network.
  • the binding request is sent to the server, and the binding relationship between the user login ID and the smart device in the binding request is established by the server.
  • the smart device determines whether the obtained binding request is sent from the local local area network, and can be implemented by determining whether the IP address in the binding request is an IP network segment of the local local area network. For example, the smart device can obtain the gateway IP address of the local wireless local area network and the subnet mask from the local gateway, determine the IP network segment of the local local area network according to the gateway IP address and the subnet mask, and then set the IP address in the binding request. Match with the IP network segment of the local area network. If it matches, then it can be determined that the binding request is sent from the local area network; on the contrary, if it does not match, the binding request may come from the external network at this time, for the external network. Binding requests are considered for security reasons and can be discarded directly by smart devices.
  • the server may first perform verification on the login account in the binding request, and if the verification succeeds, the server may also query the binding request. Smart device Whether the ID has already established a binding relationship with other users locally. If not, the server can directly establish the binding relationship between the login account and the ID of the smart device in the binding request. After the binding relationship is successfully established, the server may send a binding success notification message to the smart device, and then the smart device forwards the notification message to the corresponding terminal in the local area network, and the subsequent user can successfully bind through the binding.
  • the login account is logged into the client software of the smart device to remotely access and control the smart device.
  • the local wireless local area network-oriented transmission service may have other implementations in addition to the UDP service.
  • the transport service can also be an HTTP service.
  • the transmission service is an HTTP service
  • the smart setting may enable a private network IP address for the local wireless local area network, and the user may perform HTTP-based communication with the smart device based on the private network IP address through the client software on the terminal.
  • the smart device sends a binding request.
  • the user after the smart device is successfully bound to the login account of the user, the user usually has the requirement to remotely access and control the smart device, and the user remotely accesses and controls the smart device outside the coverage of the local wireless local area network.
  • the user accesses the packet through the NAT address translation of the IP address of the local wireless LAN router, the user can reach the smart device. It can be seen that during the remote access and control of the smart device, the NAT traversal exists. problem.
  • the most widely used and most effective way to traverse the NAT is to traverse the NAT by configuring the UDP port number. If the UDP port number enabled by the smart device is used to transmit the service with the smart device, the access packet can directly traverse the local wireless router. After the NAT firewall completes the IP address translation, it is transmitted to the smart device.
  • the implementation method of traversing the NAT by configuring the UDP port number can be referred to the description in the prior art by the technical personnel in the prior art.
  • the access packet wirelessly traverses the NAT firewall of the local wireless router to complete the IP address conversion.
  • a polling mechanism needs to be set for the smart device. Periodically requesting access packets from the server. In this way, users have a certain delay when accessing the smart device remotely.
  • the transmission service of the smart device to the local wireless local area network is a UDP service, which has an incomparable advantage.
  • the device to be bound receives the carrying user login ID binding request sent by the local terminal, and then determines whether the binding request is sent from the local local area network, and when the binding request is sent from the local local area network, The binding request is sent to the server, and the binding relationship between the user login ID and the device to be bound is established by the server; the device to be bound only receives the binding request sent by the local terminal, and only When the binding request is sent from the local area network, the binding relationship can be established, so that the binding relationship cannot be established with the terminal outside the local area network. Therefore, the error binding caused by the user login account leakage can be avoided, thereby improving the device itself. safety.
  • the present disclosure also provides an embodiment of an apparatus.
  • FIG. 4 is a schematic block diagram of a device binding apparatus according to an exemplary embodiment.
  • a device binding apparatus 400 includes: a first receiving mode Block 401, determining module 402, first sending module 403, and forwarding module 404; wherein:
  • the first receiving module 401 is configured to receive a binding request sent by the local terminal; the binding request carries a user login ID of the local terminal;
  • the determining module 402 is configured to determine whether the binding request is sent from a local area network
  • the first sending module 403 is configured to send the binding request to the server when the binding request is sent from the local area network, where the server establishes the user login ID and the device Binding relationship
  • the forwarding module 404 is configured to: after the binding relationship is established, receive an advertisement message that is successfully sent by the server, and forward the advertisement message to the local terminal.
  • the device to be bound receives the carrying user login ID binding request sent by the local terminal, and then determines whether the binding request is sent from the local local area network, and when the binding request is sent from the local local area network, The binding request is sent to the server, and the binding relationship between the user login ID and the device to be bound is established by the server; the device to be bound only receives the binding request sent by the local terminal, and only When the binding request is sent from the local area network, the binding relationship can be established, so that the binding relationship cannot be established with the terminal outside the local area network. Therefore, the error binding caused by the user login account leakage can be avoided, thereby improving the device itself. safety.
  • FIG. 5 is a block diagram of another apparatus according to an exemplary embodiment of the present disclosure.
  • the embodiment includes the user data of the local area network transmission service based on the foregoing embodiment shown in FIG.
  • the first receiving module 401 may include a broadcast submodule 401A and an obtaining submodule 401B;
  • the broadcast submodule 401A is configured to broadcast a port number of a UDP port opened by the UDP service in a local area network;
  • the obtaining sub-module 401B is configured to listen to the UDP port and obtain a binding request sent by the local terminal in the local local area network to the local device based on the port number of the UDP port.
  • FIG. 6 is a block diagram of another apparatus according to an exemplary embodiment of the present disclosure.
  • the apparatus 400 may further include a discarding module 405 on the basis of the foregoing embodiment shown in FIG. 4 . ;among them:
  • the discarding module 405 is configured to discard the binding request when the binding request is issued from an external network.
  • the structure of the discarding module 405 shown in the apparatus embodiment shown in FIG. 6 above may also be included in the foregoing apparatus embodiment of FIG. 5, and the disclosure is not limited thereto.
  • FIG. 7 is a block diagram of another apparatus according to an exemplary embodiment of the present disclosure.
  • the determining module 402 may include a determining submodule. 402A, a first determining submodule 402B and a second determining submodule 402C; wherein:
  • the determining sub-module 402A is configured to determine whether the IP address in the binding request matches an IP network segment of a local local area network;
  • the first determining submodule 402B is configured to match an IP address in the binding request to a local area network
  • the IP network segment determines that the binding request is sent from the local area network
  • the second determining sub-module 402C is configured to determine that the binding request is sent from the external network when the IP address in the binding request does not match the IP network segment of the local local area network.
  • the configurations of the determining submodule 402A, the first determining submodule 402B, and the second determining submodule 402C shown in the foregoing apparatus embodiment shown in FIG. 7 may also be included in the foregoing apparatus implementation of FIG. 5-6. In this example, the disclosure is not limited thereto.
  • FIG. 8 is a schematic block diagram of a device binding apparatus according to an exemplary embodiment.
  • a device binding apparatus 800 includes: a second sending module 801 and a second receiving module 802; wherein:
  • the second sending module 801 is configured to send a binding request to the device to be bound in the local area network, where the binding request carries the user login ID of the device;
  • the second receiving module 802 is configured to receive the binding success message forwarded by the device to be bound, where the notification message is sent by the device to be bound to the server. After the binding between the user login ID and the device to be bound is successfully established, the server sends the binding relationship.
  • the device to be bound receives the carrying user login ID binding request sent by the local terminal, and then determines whether the binding request is sent from the local local area network, and when the binding request is sent from the local local area network, The binding request is sent to the server, and the binding relationship between the user login ID and the device to be bound is established by the server; the device to be bound only receives the binding request sent by the local terminal, and only When the binding request is sent from the local area network, the binding relationship can be established, so that the binding relationship cannot be established with the terminal outside the local area network. Therefore, the error binding caused by the user login account leakage can be avoided, thereby improving the device itself. safety.
  • FIG. 9 is a block diagram of another apparatus according to an exemplary embodiment of the present disclosure, based on the foregoing embodiment shown in FIG. 8, when the transmission service in the local area network includes In the UDP service, the second sending module 801 can include a first sending submodule 801A;
  • the first sending submodule 801A is configured to send a binding request to the to-be-bound device based on a locally preset port number of a UDP port opened by the UDP server.
  • FIG. 10 is a block diagram of another apparatus according to an exemplary embodiment of the present disclosure, based on the foregoing embodiment shown in FIG. 8, when the transmission service in the local area network includes In the UDP service, the second sending module 801 may further include a receiving submodule 801B and a second sending submodule 801C; wherein:
  • the receiving submodule 801B is configured to receive a port number of the UDP port open by the UDP service broadcasted by the device to be bound in the local area network;
  • the second sending submodule 801C is configured to send a binding request to the to-be-bound device based on the received port number.
  • the device embodiment since it basically corresponds to the method embodiment, reference may be made to the partial description of the method embodiment.
  • the device embodiments described above are merely illustrative, wherein the modules or units described as separate components may or may not be physically separate, and the components displayed as modules or units may or may not be physical modules. Or units, which can be located in one place, or distributed to multiple network modules or units. Some or all of the modules or units may be selected according to actual needs to achieve the objectives of the disclosed embodiments. Those of ordinary skill in the art can understand and implement without any creative effort.
  • the present disclosure further provides a device binding device, the device comprising:
  • a memory for storing processor executable instructions
  • processor is configured to:
  • the binding request carrying a user login ID of the local terminal
  • the binding request is sent from the local area network
  • the binding request is sent to the server, and the binding relationship between the user login ID and the device is established by the server.
  • the notification message that the binding is successfully sent by the server is received, and the notification message is forwarded to the local terminal.
  • the present disclosure also provides a smart device, the smart device including a memory, and one or more programs, wherein one or more programs are stored in the memory and configured to be comprised by one or more processors Executing the one or more programs includes instructions for performing the following operations:
  • the binding request carrying a user login ID of the local terminal
  • the binding request is sent from the local area network
  • the binding request is sent to the server, and the binding relationship between the user login ID and the device is established by the server.
  • the notification message that the binding is successfully sent by the server is received, and the notification message is forwarded to the local terminal.
  • the present disclosure further provides a device binding device, the device comprising:
  • a memory for storing processor executable instructions
  • processor is configured to:
  • the present disclosure also provides a terminal, the terminal including a memory, and one or more programs, wherein one or more programs are stored in the memory and configured to be executed by one or more processors
  • the one or more programs include instructions for performing the following operations:
  • FIG. 11 is a schematic structural diagram of a device binding apparatus according to an exemplary embodiment.
  • a device binding apparatus 1100 is illustrated according to an exemplary embodiment, and the apparatus 1100 may be a smart home device, a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device. , medical equipment, fitness equipment, personal digital assistants, etc.
  • apparatus 1100 can include one or more of the following components: processing component 1101, memory 1102, power component 1103, multimedia component 1104, audio component 1105, input/output (I/O) interface 1106, sensor component 1107, And a communication component 1108.
  • Processing component 1101 typically controls the overall operation of device 1100, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations.
  • Processing component 1101 may include one or more processors 1109 to execute instructions to perform all or part of the steps of the above described methods.
  • processing component 1101 can include one or more modules to facilitate interaction between component 1101 and other components.
  • processing component 1101 can include a multimedia module to facilitate interaction between multimedia component 1104 and processing component 1101.
  • Memory 1102 is configured to store various types of data to support operation at device 1100. Examples of such data include instructions for any application or method operating on device 1100, contact data, phone book data, messages, pictures, videos, and the like.
  • the memory 1102 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.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read only memory
  • EPROM Programmable Read Only Memory
  • PROM Programmable Read Only Memory
  • ROM Read Only Memory
  • Magnetic Memory Flash Memory
  • Disk Disk or Optical Disk.
  • Power component 1103 provides power to various components of device 1100.
  • Power component 1103 can include power management The system, one or more power sources, and other components associated with generating, managing, and distributing power for the device 1100.
  • the multimedia component 1104 includes a screen between the device 1100 and a user that provides an output interface.
  • the screen can include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen can be implemented as a touch screen to receive input signals from the user.
  • the touch panel includes one or more touch sensors to sense touches, slides, and gestures on the touch panel. The touch sensor may sense not only the boundary of the touch or sliding action, but also the duration and pressure associated with the touch or slide operation.
  • the multimedia component 1104 includes a front camera and/or a rear camera. When the device 1100 is in an operation mode, such as a shooting mode or a video mode, the front camera and/or the rear camera can receive external multimedia data. Each front and rear camera can be a fixed optical lens system or have focal length and optical zoom capabilities.
  • the audio component 1105 is configured to output and/or input an audio signal.
  • the audio component 1105 includes a microphone (MIC) that is configured to receive an external audio signal when the device 1100 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode.
  • the received audio signal may be further stored in memory 1102 or transmitted via communication component 1108.
  • the audio component 1105 also includes a speaker for outputting an audio signal.
  • the I/O interface 1102 provides an interface between the processing component 1101 and a peripheral interface module, which may be a keyboard, a click wheel, a button, or the like. These buttons may include, but are not limited to, a home button, a volume button, a start button, and a lock button.
  • Sensor assembly 1107 includes one or more sensors for providing device 1100 with a status assessment of various aspects.
  • sensor assembly 1107 can detect an open/closed state of device 1100, relative positioning of components, such as the display and keypad of device 1100, and sensor component 1107 can also detect a change in position of one component of device 1100 or device 1100. The presence or absence of user contact with device 1100, device 1100 orientation or acceleration/deceleration and temperature change of device 1100.
  • Sensor assembly 1107 can include a proximity sensor configured to detect the presence of nearby objects without any physical contact.
  • Sensor assembly 1107 can also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
  • the sensor assembly 1107 can also include an acceleration sensor, a gyro sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
  • Communication component 1108 is configured to facilitate wired or wireless communication between device 1100 and other devices.
  • the device 1100 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof.
  • communication component 1108 receives broadcast signals or broadcast associated information from an external broadcast management system via a broadcast channel.
  • the communication component 1108 also includes a near field communication (NFC) module to facilitate short range communication.
  • NFC near field communication
  • 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.
  • RFID radio frequency identification
  • IrDA infrared data association
  • UWB ultra-wideband
  • Bluetooth Bluetooth
  • apparatus 1100 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 A gate array (FPGA), controller, microcontroller, microprocessor, or other electronic component implementation for performing the above methods.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGA field programmable A gate array
  • controller microcontroller, microprocessor, or other electronic component implementation for performing the above methods.
  • non-transitory computer readable storage medium comprising instructions, such as a memory 1102 comprising instructions executable by processor 1109 of apparatus 1100 to perform the above method.
  • 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, and an optical data storage device.
  • enabling the mobile terminal to perform a device binding method including:
  • the binding request carrying a user login ID of the local terminal
  • the binding request is sent from the local area network
  • the binding request is sent to the server, and the binding relationship between the user login ID and the device is established by the server.
  • the notification message that the binding is successfully sent by the server is received, and the notification message is forwarded to the local terminal.
  • the mobile terminal when the instructions in the storage medium are executed by a processor of the mobile terminal, the mobile terminal is further enabled to perform another device binding method, including:

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • General Business, Economics & Management (AREA)
  • Business, Economics & Management (AREA)
  • Multimedia (AREA)
  • Small-Scale Networks (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Communication Control (AREA)
  • Information Transfer Between Computers (AREA)
  • Telephonic Communication Services (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本公开提出一种设备绑定方法，所述方法包括：终端向本地局域网中的待绑定设备发送绑定请求，所述绑定请求携带本设备的用户登录ID；待绑定设备接收本地终端发送的绑定请求；待绑定设备判断所述绑定请求是否从本地局域网中发出；当所述绑定请求从本地局域网中发出时，待绑定设备将所述绑定请求发送至服务端，由所述服务端建立所述用户登录ID与本设备的绑定关系；当所述绑定关系建立完成后，待绑定终端接收所述服务端发送的绑定成功的通告消息，并将该通告消息转发至所述本地终端。本公开可以避免由于用户登录ID泄露而导致的错误绑定，从而可以提高设备自身的安全性。

Description

设备绑定方法和装置
本申请基于申请号为201510061349.0、申请日为2015/2/5的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本公开涉及通讯领域，尤其涉及设备绑定方法和装置。
背景技术
随着智能设备的发展，未来智能家居的组建逐渐成为目前业界关注的重点。然而，由于智能设备通常具有开放式的交互和操作的特点，智能设备在接入互联网以后，理论上所有接入互联网的设备都有可能访问和控制该智能设备，因此存在极大的安全隐患。
为了规定智能设备的私有属性和用户，目前的做法通常是采用设备绑定的方法，建立用户与智能设备之间的绑定关系，由于绑定关系一旦建立以后，只有绑定用户才具有访问和控制智能设备的权限，因此在建立用户与智能设备之间的绑定关系的过程中，势必也面临更高的安全性要求。
发明内容
为克服相关技术中存在的问题，本公开提供一种设备绑定方法和装置。
根据本公开实施例的第一方面，提供一种设备绑定方法，所述方法包括：
接收本地终端发送的绑定请求；所述绑定请求携带所述本地终端的用户登录ID；
判断所述绑定请求是否从本地局域网中发出；
当所述绑定请求从本地局域网中发出时，将所述绑定请求发送至服务端，由所述服务端建立所述用户登录ID与本设备的绑定关系；
当所述绑定关系建立完成后，接收所述服务端发送的绑定成功的通告消息，并将该通告消息转发至所述本地终端。
可选的，所述本地局域网的传输服务包括用户数据包协议UDP服务时，所述接收本地终端发送的绑定请求包括：
在本地局域网中广播由所述UDP服务开放的UDP端口的端口号；
监听所述UDP端口，获取本地局域网中的本地终端基于所述UDP端口的端口号向本设备发送的绑定请求。
可选的，所述方法还包括：
当所述绑定请求从外网中发出时，丢弃该绑定请求。
可选的，所述判断所述绑定请求是否从本地局域网中发出包括：
判断所述绑定请求中的IP地址是否匹配本地局域网的IP网段；
当所述绑定请求中的IP地址匹配本地局域网的IP网段时，确定所述绑定请求从本地局域网中发出；
当所述绑定请求中的IP地址不匹配本地局域网的IP网段时，确定所述绑定请求从外网中发出。
根据本公开实施例的第二方面，提供一种设备绑定方法，所述方法包括：
向本地局域网中的待绑定设备发送绑定请求，所述绑定请求携带本设备的用户登录ID；
接收所述待绑定设备转发的绑定成功的通告消息；其中所述通告消息在所述待绑定设备将所述绑定请求发送至服务端，由所述服务端成功建立所述用户登录ID与所述待绑定设备的绑定关系后发出。可选的，所述本地局域网中的传输服务包括UDP服务时，所述向本地局域网中的待绑定设备发送绑定请求包括：
基于本地预先设定的由所述UDP服务端开放的UDP端口的端口号向所述待绑定设备发送绑定请求；或
接收所述待绑定设备在本地局域网中广播的所述UDP服务开放的UDP端口的端口号；基于接收到的所述端口号向所述待绑定设备发送绑定请求。
根据本公开实施例的第三方面，提供一种设备绑定装置，所述装置包括：
第一接收模块，用于接收本地终端发送的绑定请求；所述绑定请求携带所述本地终端的用户登录ID；
判断模块，用于判断所述绑定请求是否从本地局域网中发出；
第一发送模块，用于在所述绑定请求从本地局域网中发出时，将所述绑定请求发送至服务端，由所述服务端建立所述用户登录ID与本设备的绑定关系；
转发模块，用于在所述绑定关系建立完成后，接收所述服务端发送的绑定成功的通告消息，并将该通告消息转发至所述本地终端。
可选的，所述本地局域网的传输服务包括用户数据包协议UDP服务时，所述第一接收模块包括：
广播子模块，用于在本地局域网中广播由所述UDP服务开放的UDP端口的端口号；
获取子单元，用于监听所述UDP端口，获取本地局域网中的本地终端基于所述UDP端口的端口号向本设备发送的绑定请求。
可选的，所述装置还包括：
丢弃模块，用于在所述绑定请求从外网中发出时，丢弃该绑定请求。
可选的，所述判断模块包括：
判断子模块，用于判断所述绑定请求中的IP地址是否匹配本地局域网的IP网段；
第一确定子模块，用于在所述绑定请求中的IP地址匹配本地局域网的IP网段时，确定所述绑定请求从本地局域网中发出；
第二确定子模块，用于在所述绑定请求中的IP地址不匹配本地局域网的IP网段时，确定所述绑定请求从外网中发出。
根据本公开实施例的第四方面，提供一种设备绑定装置，所述装置包括：
第二发送模块，用于向本地局域网中的待绑定设备发送绑定请求，所述绑定请求携带本设备的用户登录ID；
第二接收模块，用于接收所述待绑定设备转发的绑定成功的通告消息；其中所述通告消息在所述待绑定设备将所述绑定请求发送至服务端，由所述服务端成功建立所述用户登录ID与所述待绑定设备的绑定关系后发出。
可选的，所述本地局域网中的传输服务包括UDP服务时，所述第二发送模块包括：
第一发送子模块，用于基于本地预先设定的由所述UDP服务端开放的UDP端口的端口号向所述待绑定设备发送绑定请求；或
接收子模块，用于接收所述待绑定设备在本地局域网中广播的所述UDP服务开放的UDP端口的端口号；
第二发送子模块，基于接收到的所述端口号向所述待绑定设备发送绑定请求。
根据本公开实施例的第五方面，提供一种设备绑定装置，包括：
处理器；
用于存储处理器可执行指令的存储器；
其中，所述处理器被配置为：
接收本地终端发送的绑定请求；所述绑定请求携带所述本地终端的用户登录ID；
判断所述绑定请求是否从本地局域网中发出；
当所述绑定请求从本地局域网中发出时，将所述绑定请求发送至服务端，由所述服务端建立所述用户登录ID与本设备的绑定关系；
当所述绑定关系建立完成后，接收所述服务端发送的绑定成功的通告消息，并将该通告消息转发至所述本地终端。
根据本公开实施例的第六方面，提供一种设备绑定装置，包括：
处理器；
用于存储处理器可执行指令的存储器；
其中，所述处理器被配置为：
向本地局域网中的待绑定设备发送绑定请求，所述绑定请求携带本设备的用户登录ID；
接收所述待绑定设备转发的绑定成功的通告消息；其中所述通告消息在所述待绑定设备将所述绑定请求发送至服务端，由所述服务端成功建立所述用户登录ID与所述待绑定设备的绑定关系后发出。
本公开的实施例提供的技术方案可以包括以下有益效果：
本公开的以上实施例中，通过待绑定设备来接收本地终端发送的携带用户登录ID绑 定请求，然后判断该绑定请求是否从本地局域网发出，当该绑定请求从本地局域网发出时，将该绑定请求发送至服务端，由服务端建立所述用户登录ID与所述待绑定设备之间的绑定关系；由于待绑定设备只接收本地终端发送的绑定请求，并且只有在该绑定请求从本地局域网中发出时才可以建立绑定关系，从而无法与本地局域网以外的终端建立绑定关系，因此可以避免由于用户登录ID泄露而导致的错误绑定，从而可以提高设备自身的安全性。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不能限制本公开。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本公开的实施例，并与说明书一起用于解释本公开的原理。
图1是根据一示例性实施例示出的一种设备绑定方法的流程示意图；
图2是根据一示例性实施例示出的另一种设备绑定方法的流程示意图；
图3是根据一示例性实施例示出的另一种设备绑定方法的流程示意图；
图4是根据一示例性实施例示出的一种设备绑定装置的示意框图；
图5是根据一示例性实施例示出的另一种设备绑定装置的示意框图；
图6是根据一示例性实施例示出的另一种设备绑定装置的示意框图；
图7是根据一示例性实施例示出的另一种设备绑定装置的示意框图；
图8是根据一示例性实施例示出的另一种设备绑定装置的示意框图；
图9是根据一示例性实施例示出的另一种设备绑定装置的示意框图；
图10是根据一示例性实施例示出的另一种设备绑定装置的示意框图；
图11是根据一示例性实施例示出的一种用于所述设备绑定装置的一结构示意图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本公开相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本公开的一些方面相一致的装置和方法的例子。
在本公开使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本公开。在本公开和所附权利要求书中所使用的单数形式的“一种”、“所述”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本公开可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本公开范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为 第一信息。取决于语境，如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
目前，用户想要取得智能设备的访问和控制权限时，可以通过在终端上安装该智能设备的客户端软件完成注册，然后将注册成功后的登录账号(用户登录ID)通过对应的服务端与该智能设备建立绑定关系来实现。当绑定关系建立后，此时用户已经拥有该智能设备的主人权限，后续用户通过所述登录账号成功该智能设备的客户端软件后，可以通过该客户端软件与该智能设备进行交互，对该智能设备进行访问和控制等操作；例如，所述智能设备可以是智能家居设备，当用户的登录账号与该智能家居设备建立绑定关系后，用户可以通过该智能家居设备的客户端软件控制该智能家居的开启和关闭等。
在实际应用中，由于用户通常具有远程控制智能设备的需求，因此局域网中的智能设备通常也需要接入互联网，然而由于智能设备通常具有开放式的交互和操作的特点，因此用户在将登陆账号与智能设备进行绑定的过程中，一旦用户的登陆账号泄露，由于服务端在绑定关系建立的过程中，通常只基于登陆账号对绑定用户进行合法性验证，因此其它的用户使用该登陆账号能够顺利的完成与所述智能设备的绑定过程，从而造成错误绑定使得该智能设备面临严重的安全性风险。
有鉴于次，本公开提出一种设备绑定方法，通过待绑定设备来接收本地终端发送的携带用户登录ID绑定请求，然后判断该绑定请求是否从本地局域网发出，当该绑定请求从本地局域网发出时，将该绑定请求发送至服务端，由服务端建立所述用户登录ID与所述待绑定设备之间的绑定关系；由于待绑定设备只接收本地终端发送的绑定请求，并且只有在该绑定请求从本地局域网中发出时才可以建立绑定关系，从而无法与本地局域网以外的终端建立绑定关系，因此可以避免由于用户登录账户泄露而导致的错误绑定，从而可以提高设备自身的安全性。
如图1所示，图1是根据一示例性实施例示出的一种设备绑定方法，该设备绑定方法用于智能设备中，包括以下步骤：
在步骤101中，接收本地终端发送的绑定请求；所述绑定请求携带所述本地终端的用户登录ID；
在步骤102中，判断所述绑定请求是否从本地局域网中发出；
在步骤103中，当所述绑定请求从本地局域网中发出时，将所述绑定请求发送至服务端，由所述服务端建立所述用户登录ID与本设备的绑定关系；
在步骤104中，当所述绑定关系建立完成后，接收所述服务端发送的绑定成功的通告消息，并将该通告消息转发至所述本地终端。
在本实施例中，所述本地局域网可以是基于WI-FI的无线局域网，所述智能设备可以是内置了WI-FI模块的智能设备。
在初始状态下，智能设备可以通过内置的WIFI模块接入所述无线局域网，同时，用 户也可以将终端接入所述无线局域网，当所述智能设备和所述终端均接入成功后，此时所述智能设备和所述终端将处于同一个局域网中，后续用户可以通过操作终端上安装的该智能设备的客户端软件，发起与该智能设备的绑定操作来取得该智能设备的访问和控制权限；例如，在实现时，可以在所述客户端软件上提供一个“发起绑定”的功能开关，用户可以通过打开该功能开关发起与该智能设备的绑定操作。
其中，用户在通过所述客户端软件与所述智能设备进行绑定时，通常是通过客户端软件向服务端发送一个携带用户的登录账号以及所述智能设备的ID的绑定请求，服务端对该登录账号进行身份验证通过后，如果该智能设备尚未与其它用户建立绑定关系，那么可以直接在本地建立所述登录账号与该智能设备的绑定关系。由于在绑定关系的建立过程中，服务端是基于用户登录账号进行身份验证的，因此一旦登录账号泄露，则可能被其它的非法用户利用与该智能设备绑定成功，从而面临安全风险。
在本实施例中，由于与所述智能设备处于同一个局域网的设备(即本地终端)通常为可靠设备，因此为了提高用户与智能设备建立绑定关系过程中的安全性，避免错误绑定的问题，在绑定过程中，智能设备可以只接受本地无线局域网中的设备发起的绑定，非本地局域网的用户无法发起与所述智能设备的绑定，从而将错误绑定的概率降到了最低。
在实现时，智能设备可以在本地启用一个面向本地无线局域网的传输服务，在启用了该传输服务后，所述客户端软件可以基于该传输服务向所述智能设备发送绑定请求，所述智能设备可以基于该传输服务来接收本地无线局域网中的设备发送的绑定请求，然后由所述智能设备将接收到的绑定请求再发送至服务端完成绑定关系的建立。
在本实施例中，由于绑定请求不再是由用户通过客户端软件直接发送给服务端，而是由待绑定的智能设备来发送，因此可以保证服务端接收到的绑定请求均来自于所述智能设备本地局域网中的设备，将与所述智能设备进行绑定时的绑定方限制为所述智能设备本地局域网中的可靠设备。
其中，所述面向本地无线局域网的传输服务，可以是UDP服务，以下以所述传输服务为UDP服务为例对本公开的技术方案进行说明。
在初始状态下，当智能设备成功接入本地无线局域网后，可以在后台默认开放一个面向本地无线局域网的UDP端口，其中所述UDP端口的端口号在本实施例中不进行特别限定，例如可以是UDP端口号中的非著名端口号或私网端口号。与此同时，该智能设备的客户端软件中也可以提前配置该UDP端口号的端口号，当用户通过操作该客户端软件发起与该智能设备进行绑定时，所述客户端软件可以根据提前配置的所述UDP端口号向所述UDP端口发送绑定请求，此时该绑定请求中可以携带用户的登录账号，如果在本地无线局域网中存在多个智能设备，为了加以区分，此时该绑定请求中还可以携带智能设备的ID(例如智能设备的硬件地址)。当然，如果所述客户端软件中未提前配置所述UDP端口号，智能设备在所述UDP端口启用后，还可以在本地无线局域网中发送一个广播消息，将已启用的UDP端口的端口号通告给本地无线局域网中所有接收到该广播消息的客户端 软件。
在本实施例中，智能设备在接收本地无线局域网中的客户端软件发送的绑定请求时，可以在所述UDP端口启用后，就实时的监听该UDP端口，一旦该UDP端口收到来自本地无线局域网中的客户端软件发送的绑定请求时，可以立即从该UDP端口获取该绑定请求，同时判断获取到的绑定请求是否从本地局域网中发出，如果该绑定请求是从本地局域网中发出的，此时可以将该绑定请求发送至服务端，由服务端建立该绑定请求中的用户登录ID与所述智能设备的绑定关系。
其中，智能设备在判断获取到的绑定请求是否从本地局域网中发出，可以通过判断该绑定请求中的IP地址是否为本地局域网的IP网段来实现。例如，智能设备可以从本地网关获取本地无线局域网的网关IP地址以及子网掩码，根据网关IP地址和子网掩码来确定本地局域网的IP网段，然后将所述绑定请求中的IP地址与本地局域网的IP网段进行匹配，如果匹配的话，那么可以确定该绑定请求从本地局域网中发出；相反，如果不匹配的话，此时该绑定请求可能来自外网，对于来自外网的绑定请求，处于安全性考虑，智能设备可以直接丢弃。
在本实施例中，当服务端在收到所述智能设备转发的绑定请求后，首先可以对该绑定请求中的登录账号进行验证，如果验证通过，服务端还可以查询该绑定请求中的智能设备的ID是否已经在本地建立了与其它用户的绑定关系，如果没有，此时服务端可以直接在本地建立该绑定请求中的登录账号和智能设备的ID之间的绑定关系。当绑定关系成功建立后，服务端还可以向所述智能设备发送一个绑定成功的通告消息，然后由智能设备将该通告消息转发到本地局域网中的对应终端，后续用户可以通过绑定成功的登录账号登录所述智能设备的客户端软件来远程访问和控制所述智能设备。
值得说明的是，在实现时，所述面向本地无线局域网的传输服务除了所述UDP服务以外，还可以有其它实现方式，例如，所述传输服务还可以是HTTP服务。当所述传输服务为HTTP服务，智能设置可以启用一个面向本地无线局域网的私网IP地址，用户可以通过终端上的客户端软件基于该私网IP地址与该智能设备进行基于HTTP的通信，向该智能设备发送绑定请求，在实施例中不再进行一一详述。
在以上实施例中，通过待绑定设备来接收本地终端发送的携带用户登录ID绑定请求，然后判断该绑定请求是否从本地局域网发出，当该绑定请求从本地局域网发出时，将该绑定请求发送至服务端，由服务端建立所述用户登录ID与所述待绑定设备之间的绑定关系；由于待绑定设备只接收本地终端发送的绑定请求，并且只有在该绑定请求从本地局域网中发出时才可以建立绑定关系，从而无法与本地局域网以外的终端建立绑定关系，因此可以避免由于用户登录账户泄露而导致的错误绑定，从而可以提高设备自身的安全性。
如图2所示，图2是根据一示例性实施例示出的另一种设备绑定方法，该方法用于终端中，所述方法包括以下步骤：
在步骤201中，向本地局域网中的待绑定设备发送绑定请求，所述绑定请求携带本设备的用户登录ID；
在步骤202中，接收所述待绑定设备转发的绑定成功的通告消息；其中所述通告消息在所述待绑定设备将所述绑定请求发送至服务端，由所述服务端成功建立所述用户登录ID与所述待绑定设备的绑定关系后发出。
在本实施例中，所述本地局域网可以是基于WI-FI的无线局域网，所述待绑定设备可以是内置了WI-FI模块的智能设备。
在初始状态下，所述智能设备可以通过内置的WIFI模块接入所述无线局域网，同时，用户也可以将终端接入所述无线局域网，当所述智能设备和所述终端均接入成功后，此时所述智能设备和所述终端将处于同一个局域网中，后续用户可以通过操作终端上安装的该智能设备的客户端软件，发起与该智能设备的绑定操作来取得该智能设备的访问和控制权限；例如，在实现时，可以在所述客户端软件上提供一个“发起绑定”的功能开关，用户可以通过打开该功能开关发起与该智能设备的绑定操作。
其中，用户在通过所述客户端软件与所述智能设备进行绑定时，通常是通过客户端软件向服务端发送一个携带用户的登录账号以及所述智能设备的ID的绑定请求，服务端对该登录账号进行身份验证通过后，如果该智能设备尚未与其它用户建立绑定关系，那么可以直接在本地建立所述登录账号与该智能设备的绑定关系。由于在绑定关系的建立过程中，服务端是基于用户登录账号进行身份验证的，因此一旦登录账号泄露，则可能被其它的非法用户利用与该智能设备绑定成功，从而面临安全风险。
在本实施例中，由于与所述智能设备处于同一个局域网的设备(即本地终端)通常为可靠设备，因此为了提高用户与智能设备建立绑定关系过程中的安全性，避免错误绑定的问题，在绑定过程中，智能设备可以只接受本地无线局域网中的设备发起的绑定，非本地局域网的用户无法发起与所述智能设备的绑定，从而将错误绑定的概率降到了最低。
在实现时，智能设备可以在本地启用一个面向本地无线局域网的传输服务，在启用了该传输服务后，所述客户端软件可以基于该传输服务向所述智能设备发送绑定请求，所述智能设备可以基于该传输服务来接收本地无线局域网中的设备发送的绑定请求，然后由所述智能设备将接收到的绑定请求再发送至服务端完成绑定关系的建立。
在本实施例中，由于绑定请求不再是由用户通过客户端软件直接发送给服务端，而是由待绑定的智能设备来发送，因此可以保证服务端接收到的绑定请求均来自于所述智能设备本地局域网中的设备，将与所述智能设备进行绑定时的绑定方限制为所述智能设备本地局域网中的可靠设备。
其中，所述面向本地无线局域网的传输服务，可以是UDP服务，以下以所述传输服务为UDP服务为例对本公开的技术方案进行说明。
在初始状态下，当智能设备成功接入本地无线局域网后，可以在后台默认开放一个面向本地无线局域网的UDP端口，其中所述UDP端口的端口号在本实施例中不进行特别限 定，例如可以是UDP端口号中的非著名端口号或私网端口号。与此同时，该智能设备的客户端软件中也可以提前配置该UDP端口号的端口号，当用户通过操作该客户端软件发起与该智能设备进行绑定时，所述客户端软件可以根据提前配置的所述UDP端口号向所述UDP端口发送绑定请求，此时该绑定请求中可以携带用户的登录账号，如果在本地无线局域网中存在多个智能设备，为了加以区分，此时该绑定请求中还可以携带智能设备的ID(例如智能设备的硬件地址)。
当然，如果所述客户端软件中未提前配置所述UDP端口号，智能设备在所述UDP端口启用后，还可以在本地无线局域网中发送一个广播消息，将已启用的UDP端口的端口号通告给本地无线局域网中所有接收到该广播消息的客户端软件。
在本实施例中，智能设备在接收本地无线局域网中的客户端软件发送的绑定请求时，可以在所述UDP端口启用后，就实时的监听该UDP端口，一旦该UDP端口收到来自本地无线局域网中的客户端软件发送的绑定请求时，可以立即从该UDP端口获取该绑定请求，同时判断获取到的绑定请求是否从本地局域网中发出，如果该绑定请求是从本地局域网中发出的，此时可以将该绑定请求发送至服务端，由服务端建立该绑定请求中的用户登录ID与所述智能设备的绑定关系。
其中，智能设备在判断获取到的绑定请求是否从本地局域网中发出，可以通过判断该绑定请求中的IP地址是否为本地局域网的IP网段来实现。例如，智能设备可以从本地网关获取本地无线局域网的网关IP地址以及子网掩码，根据网关IP地址和子网掩码来确定本地局域网的IP网段，然后将所述绑定请求中的IP地址与本地局域网的IP网段进行匹配，如果匹配的话，那么可以确定该绑定请求从本地局域网中发出；相反，如果不匹配的话，此时该绑定请求可能来自外网，对于来自外网的绑定请求，处于安全性考虑，智能设备可以直接丢弃。
在本实施例中，当服务端在收到所述智能设备转发的绑定请求后，首先可以对该绑定请求中的登录账号进行验证，如果验证通过，服务端还可以查询该绑定请求中的智能设备的ID是否已经在本地建立了与其它用户的绑定关系，如果没有，此时服务端可以直接在本地建立该绑定请求中的登录账号和智能设备的ID之间的绑定关系。当绑定关系成功建立后，服务端还可以向所述智能设备发送一个绑定成功的通告消息，然后由智能设备将该通告消息转发到本地局域网中的对应终端，后续用户可以通过绑定成功的登录账号登录所述智能设备的客户端软件来远程访问和控制所述智能设备。
值得说明的是，在实现时，所述面向本地无线局域网的传输服务除了所述UDP服务以外，还可以有其它实现方式，例如，所述传输服务还可以是HTTP服务。当所述传输服务为HTTP服务，智能设置可以启用一个面向本地无线局域网的私网IP地址，用户可以通过终端上的客户端软件基于该私网IP地址与该智能设备进行基于HTTP的通信，向该智能设备发送绑定请求，在实施例中不再进行一一详述。。
在以上实施例中，通过待绑定设备来接收本地终端发送的携带用户登录ID绑定请求， 然后判断该绑定请求是否从本地局域网发出，当该绑定请求从本地局域网发出时，将该绑定请求发送至服务端，由服务端建立所述用户登录ID与所述待绑定设备之间的绑定关系；由于待绑定设备只接收本地终端发送的绑定请求，并且只有在该绑定请求从本地局域网中发出时才可以建立绑定关系，从而无法与本地局域网以外的终端建立绑定关系，因此可以避免由于用户登录账户泄露而导致的错误绑定，从而可以提高设备自身的安全性。
如图3所示，图3是根据一示例性实施例示出的另一种设备绑定方法，，所述方法包括以下步骤：
在步骤301中，终端向本地局域网中的待绑定设备发送绑定请求，所述绑定请求携带本设备的用户登录ID；
在步骤302中，待绑定设备接收本地终端发送的绑定请求；
在步骤303中，待绑定设备判断所述绑定请求是否从本地局域网中发出；
在步骤304中，当所述绑定请求从本地局域网中发出时，待绑定设备将所述绑定请求发送至服务端，由所述服务端建立所述用户登录ID与本设备的绑定关系；
在步骤305中，当所述绑定关系建立完成后，待绑定终端接收所述服务端发送的绑定成功的通告消息，并将该通告消息转发至所述本地终端。
在本实施例中，所述本地局域网可以是基于WI-FI的无线局域网，所述待绑定设备可以是内置了WI-FI模块的智能设备。
在初始状态下，所述智能设备可以通过内置的WIFI模块接入所述无线局域网，同时，用户也可以将终端接入所述无线局域网，当所述智能设备和所述终端均接入成功后，此时所述智能设备和所述终端将处于同一个局域网中，后续用户可以通过操作终端上安装的该智能设备的客户端软件，发起与该智能设备的绑定操作来取得该智能设备的访问和控制权限；例如，在实现时，可以在所述客户端软件上提供一个“发起绑定”的功能开关，用户可以通过打开该功能开关发起与该智能设备的绑定操作。
其中，用户在通过所述客户端软件与所述智能设备进行绑定时，通常是通过客户端软件向服务端发送一个携带用户的登录账号以及所述智能设备的ID的绑定请求，服务端对该登录账号进行身份验证通过后，如果该智能设备尚未与其它用户建立绑定关系，那么可以直接在本地建立所述登录账号与该智能设备的绑定关系。由于在绑定关系的建立过程中，服务端是基于用户登录账号进行身份验证的，因此一旦登录账号泄露，则可能被其它的非法用户利用与该智能设备绑定成功，从而面临安全风险。
在本实施例中，由于与所述智能设备处于同一个局域网的设备(即本地中断)通常为可靠设备，因此为了提高用户与智能设备建立绑定关系过程中的安全性，避免错误绑定的问题，在绑定过程中，智能设备可以只接受本地无线局域网中的设备发起的绑定，非本地局域网的用户无法发起与所述智能设备的绑定，从而将错误绑定的概率降到了最低。
在实现时，智能设备可以在本地启用一个面向本地无线局域网的传输服务，在启用了 该传输服务后，所述客户端软件可以基于该传输服务向所述智能设备发送绑定请求，所述智能设备可以基于该传输服务来接收本地无线局域网中的设备发送的绑定请求，然后由所述智能设备将接收到的绑定请求再发送至服务端完成绑定关系的建立。
在本实施例中，由于绑定请求不再是由用户通过客户端软件直接发送给服务端，而是由待绑定的智能设备来发送，因此可以保证服务端接收到的绑定请求均来自于所述智能设备本地局域网中的设备，将与所述智能设备进行绑定时的绑定方限制为所述智能设备本地局域网中的可靠设备。
其中，所述面向本地无线局域网的传输服务，可以是UDP服务，以下以所述传输服务为UDP服务为例对本公开的技术方案进行说明。
在初始状态下，当智能设备成功接入本地无线局域网后，可以在后台默认开放一个面向本地无线局域网的UDP端口，其中所述UDP端口的端口号在本实施例中不进行特别限定，例如可以是UDP端口号中的非著名端口号或私网端口号。与此同时，该智能设备的客户端软件中也可以提前配置该UDP端口号的端口号，当用户通过操作该客户端软件发起与该智能设备进行绑定时，所述客户端软件可以根据提前配置的所述UDP端口号向所述UDP端口发送绑定请求，此时该绑定请求中可以携带用户的登录账号，如果在本地无线局域网中存在多个智能设备，为了加以区分，此时该绑定请求中还可以携带智能设备的ID(例如智能设备的硬件地址)。
当然，如果所述客户端软件中未提前配置所述UDP端口号，智能设备在所述UDP端口启用后，还可以在本地无线局域网中发送一个广播消息，将已启用的UDP端口的端口号通告给本地无线局域网中所有接收到该广播消息的客户端软件。
在本实施例中，智能设备在接收本地无线局域网中的客户端软件发送的绑定请求时，可以在所述UDP端口启用后，就实时的监听该UDP端口，一旦该UDP端口收到来自本地无线局域网中的客户端软件发送的绑定请求时，可以立即从该UDP端口获取该绑定请求，同时判断获取到的绑定请求是否从本地局域网中发出，如果该绑定请求是从本地局域网中发出的，此时可以将该绑定请求发送至服务端，由服务端建立该绑定请求中的用户登录ID与所述智能设备的绑定关系。
其中，智能设备在判断获取到的绑定请求是否从本地局域网中发出，可以通过判断该绑定请求中的IP地址是否为本地局域网的IP网段来实现。例如，智能设备可以从本地网关获取本地无线局域网的网关IP地址以及子网掩码，根据网关IP地址和子网掩码来确定本地局域网的IP网段，然后将所述绑定请求中的IP地址与本地局域网的IP网段进行匹配，如果匹配的话，那么可以确定该绑定请求从本地局域网中发出；相反，如果不匹配的话，此时该绑定请求可能来自外网，对于来自外网的绑定请求，处于安全性考虑，智能设备可以直接丢弃。
在本实施例中，当服务端在收到所述智能设备转发的绑定请求后，首先可以对该绑定请求中的登录账号进行验证，如果验证通过，服务端还可以查询该绑定请求中的智能设备 的ID是否已经在本地建立了与其它用户的绑定关系，如果没有，此时服务端可以直接在本地建立该绑定请求中的登录账号和智能设备的ID之间的绑定关系。当绑定关系成功建立后，服务端还可以向所述智能设备发送一个绑定成功的通告消息，然后由智能设备将该通告消息转发到本地局域网中的对应终端，后续用户可以通过绑定成功的登录账号登录所述智能设备的客户端软件来远程访问和控制所述智能设备。
值得说明的是，在实现时，所述面向本地无线局域网的传输服务除了所述UDP服务以外，还可以有其它实现方式。例如，所述传输服务还可以是HTTP服务。当所述传输服务为HTTP服务，智能设置可以启用一个面向本地无线局域网的私网IP地址，用户可以通过终端上的客户端软件基于该私网IP地址与该智能设备进行基于HTTP的通信，向该智能设备发送绑定请求。
然而，由于智能设备与用户的登录账号绑定成功后，用户通常具有远程对该智能设备进行访问和控制的需求，当用户在本地无线局域网的覆盖范围之外对该智能设备进行远程访问和控制时，用户的访问报文需要经过本地无线局域网的路由器对IP地址进行NAT地址转换后，才可以到达智能设备，可见，用户在对该智能设备进行远程访问和控制的过程中，存在NAT穿越的问题。
而目前穿越NAT应用最广泛且最有效的方式，为通过配置UDP端口号来穿越NAT，如果用户通过智能设备启用的UDP端口号与智能设备进行传输服务，访问报文可以直接穿越本地无线路由器的NAT防火墙完成IP地址转换后，传输至所述智能设备。其中通过配置UDP端口号穿越NAT的实现方法本领域技术人员可以参考现有技术中的介绍，本实施例不再详述。
而如果用户通过智能设备启用的HTTP服务与该智能设备进行传输服务，访问报文无线直接穿越本地无线路由器的NAT防火墙完成IP地址转换，在这种情况下，需要为智能设备设置轮询机制，定期向服务端请求访问报文，通过这种方式用户远程访问智能设备时会存在一定的延迟。可见，智能设备面向本地无线局域网的传输服务为UDP服务，具有不可比拟的优势。
在以上实施例中，通过待绑定设备来接收本地终端发送的携带用户登录ID绑定请求，然后判断该绑定请求是否从本地局域网发出，当该绑定请求从本地局域网发出时，将该绑定请求发送至服务端，由服务端建立所述用户登录ID与所述待绑定设备之间的绑定关系；由于待绑定设备只接收本地终端发送的绑定请求，并且只有在该绑定请求从本地局域网中发出时才可以建立绑定关系，从而无法与本地局域网以外的终端建立绑定关系，因此可以避免由于用户登录账户泄露而导致的错误绑定，从而可以提高设备自身的安全性。
与前述设备绑定方法实施例相对应，本公开还提供了一种装置的实施例。
图4是根据一示例性实施例示出的一种设备绑定装置的示意框图。
如图4所示，根据一示例性实施例示出的一种设备绑定装置400，包括：第一接收模 块401、判断模块402、第一发送模块403和转发模块404；其中：
所述第一接收模块401被配置为，接收本地终端发送的绑定请求；所述绑定请求携带所述本地终端的用户登录ID；
所述判断模块402被配置为，判断所述绑定请求是否从本地局域网中发出；
所述第一发送模块403被配置为，在所述绑定请求从本地局域网中发出时，将所述绑定请求发送至服务端，由所述服务端建立所述用户登录ID与本设备的绑定关系；
所述转发模块404被配置为，在所述绑定关系建立完成后，接收所述服务端发送的绑定成功的通告消息，并将该通告消息转发至所述本地终端。
在以上实施例中，通过待绑定设备来接收本地终端发送的携带用户登录ID绑定请求，然后判断该绑定请求是否从本地局域网发出，当该绑定请求从本地局域网发出时，将该绑定请求发送至服务端，由服务端建立所述用户登录ID与所述待绑定设备之间的绑定关系；由于待绑定设备只接收本地终端发送的绑定请求，并且只有在该绑定请求从本地局域网中发出时才可以建立绑定关系，从而无法与本地局域网以外的终端建立绑定关系，因此可以避免由于用户登录账户泄露而导致的错误绑定，从而可以提高设备自身的安全性。
请参见图5，图5是本公开根据一示例性实施例示出的另一种装置的框图，该实施例在前述图4所示实施例的基础上，所述本地局域网的传输服务包括用户数据包协议UDP服务时，所述第一接收模块401可以包括广播子模块401A、获取子模块401B；其中：
所述广播子模块401A被配置为，在本地局域网中广播由所述UDP服务开放的UDP端口的端口号；
所述获取子模块401B被配置为，监听所述UDP端口，获取本地局域网中的本地终端基于所述UDP端口的端口号向本设备发送的绑定请求。
请参见图6，图6是本公开根据一示例性实施例示出的另一种装置的框图，该实施例在前述图4所示实施例的基础上，所述装置400还可以包括丢弃模块405；其中：
所述丢弃模块405被配置为，在所述绑定请求从外网中发出时，丢弃该绑定请求。
需要说明的是，上述图6所示的装置实施例中示出的丢弃模块405的结构也可以包含在前述图5的装置实施例中，对此本公开不进行限制。
请参见图7，图7是本公开根据一示例性实施例示出的另一种装置的框图，该实施例在前述图4所示实施例的基础上，所述判断模块402可以包括判断子模块402A、第一确定子模块402B和第二确定子模块402C；其中：
所述判断子模块402A被配置为，判断所述绑定请求中的IP地址是否匹配本地局域网的IP网段；
所述第一确定子模块402B被配置为，在所述绑定请求中的IP地址匹配本地局域网的 IP网段时，确定所述绑定请求从本地局域网中发出；
所述第二确定子模块402C被配置为，在所述绑定请求中的IP地址不匹配本地局域网的IP网段时，确定所述绑定请求从外网中发出。
需要说明的是，上述图7所示的装置实施例中示出的判断子模块402A、第一确定子模块402B和第二确定子模块402C的结构也可以包含在前述图5-6的装置实施例中，对此本公开不进行限制。
图8是根据一示例性实施例示出的一种设备绑定装置的示意框图。
如图8所示，根据一示例性实施例示出的一种设备绑定装置800，包括：第二发送模块801和第二接收模块802；其中：
所述第二发送模块801被配置为，向本地局域网中的待绑定设备发送绑定请求，所述绑定请求携带本设备的用户登录ID；
所述第二接收模块802被配置为，接收所述待绑定设备转发的绑定成功的通告消息；其中所述通告消息在所述待绑定设备将所述绑定请求发送至服务端，由所述服务端成功建立所述用户登录ID与所述待绑定设备的绑定关系后发出。
在以上实施例中，通过待绑定设备来接收本地终端发送的携带用户登录ID绑定请求，然后判断该绑定请求是否从本地局域网发出，当该绑定请求从本地局域网发出时，将该绑定请求发送至服务端，由服务端建立所述用户登录ID与所述待绑定设备之间的绑定关系；由于待绑定设备只接收本地终端发送的绑定请求，并且只有在该绑定请求从本地局域网中发出时才可以建立绑定关系，从而无法与本地局域网以外的终端建立绑定关系，因此可以避免由于用户登录账户泄露而导致的错误绑定，从而可以提高设备自身的安全性。
请参见图9，图9是本公开根据一示例性实施例示出的另一种装置的框图，该实施例在前述图8所示实施例的基础上，当所述本地局域网中的传输服务包括UDP服务时，所述第二发送模块801可以包括第一发送子模块801A；其中：
所述第一发送子模块801A被配置为，基于本地预先设定的由所述UDP服务端开放的UDP端口的端口号向所述待绑定设备发送绑定请求。
请参见图10，图10是本公开根据一示例性实施例示出的另一种装置的框图，该实施例在前述图8所示实施例的基础上，当所述本地局域网中的传输服务包括UDP服务时，所述第二发送模块801还可以包括接收子模块801B和第二发送子模块801C；其中：
所述接收子模块801B被配置为，接收所述待绑定设备在本地局域网中广播的所述UDP服务开放的UDP端口的端口号；
所述第二发送子模块801C被配置为，基于接收到的所述端口号向所述待绑定设备发送绑定请求。
需要说明的是，上述图10所示的装置实施例中示出的接收子模块801B和第二发送子模块801C的结构也可以包含在前述图9的装置实施例中，对此本公开不进行限制。
上述装置中各个模块或者单元的功能和作用的实现过程具体详见上述方法中对应步骤的实现过程，在此不再赘述。
对于装置实施例而言，由于其基本对应于方法实施例，所以相关之处参见方法实施例的部分说明即可。以上所描述的装置实施例仅仅是示意性的，其中所述作为分离部件说明的模块或者单元可以是或者也可以不是物理上分开的，作为模块或单元显示的部件可以是或者也可以不是物理模块或单元，即可以位于一个地方，或者也可以分布到多个网络模块或单元上。可以根据实际的需要选择其中的部分或者全部模块或单元来实现本公开方案的目的。本领域普通技术人员在不付出创造性劳动的情况下，即可以理解并实施。
相应的，本公开还提供一种设备绑定装置，所述装置包括：
处理器；
用于存储处理器可执行指令的存储器；
其中，所述处理器被配置为：
接收本地终端发送的绑定请求；所述绑定请求携带所述本地终端的用户登录ID；
判断所述绑定请求是否从本地局域网中发出；
当所述绑定请求从本地局域网中发出时，将所述绑定请求发送至服务端，由所述服务端建立所述用户登录ID与本设备的绑定关系；
当所述绑定关系建立完成后，接收所述服务端发送的绑定成功的通告消息，并将该通告消息转发至所述本地终端。
相应的，本公开还提供一种智能设备，所述智能设备包括有存储器，以及一个或者一个以上的程序，其中一个或者一个以上程序存储于存储器中，且经配置以由一个或者一个以上处理器执行所述一个或者一个以上程序包含用于进行以下操作的指令：
接收本地终端发送的绑定请求；所述绑定请求携带所述本地终端的用户登录ID；
判断所述绑定请求是否从本地局域网中发出；
当所述绑定请求从本地局域网中发出时，将所述绑定请求发送至服务端，由所述服务端建立所述用户登录ID与本设备的绑定关系；
当所述绑定关系建立完成后，接收所述服务端发送的绑定成功的通告消息，并将该通告消息转发至所述本地终端。
相应的，本公开还提供一种设备绑定装置，所述装置包括：
处理器；
用于存储处理器可执行指令的存储器；
其中，所述处理器被配置为：
向本地局域网中的待绑定设备发送绑定请求，所述绑定请求携带本设备的用户登录ID；
接收所述待绑定设备转发的绑定成功的通告消息；其中所述通告消息在所述待绑定设备将所述绑定请求发送至服务端，由所述服务端成功建立所述用户登录ID与所述待绑定设备的绑定关系后发出。
相应的，本公开还提供一种终端，所述终端包括有存储器，以及一个或者一个以上的程序，其中一个或者一个以上程序存储于存储器中，且经配置以由一个或者一个以上处理器执行所述一个或者一个以上程序包含用于进行以下操作的指令：
向本地局域网中的待绑定设备发送绑定请求，所述绑定请求携带本设备的用户登录ID；
接收所述待绑定设备转发的绑定成功的通告消息；其中所述通告消息在所述待绑定设备将所述绑定请求发送至服务端，由所述服务端成功建立所述用户登录ID与所述待绑定设备的绑定关系后发出。
图11是根据一示例性实施例示出的一种设备绑定装置的结构示意图。
如图11所示，根据一示例性实施例示出的一种设备绑定装置1100，该装置1100可以是智能家居设备、移动电话，计算机，数字广播终端，消息收发设备，游戏控制台，平板设备，医疗设备，健身设备，个人数字助理等。
参照图11，装置1100可以包括以下一个或多个组件：处理组件1101，存储器1102，电源组件1103，多媒体组件1104，音频组件1105，输入/输出(I/O)的接口1106，传感器组件1107，以及通信组件1108。
处理组件1101通常控制装置1100的整体操作，诸如与显示，电话呼叫，数据通信，相机操作和记录操作相关联的操作。处理组件1101可以包括一个或多个处理器1109来执行指令，以完成上述的方法的全部或部分步骤。此外，处理组件1101可以包括一个或多个模块，便于处理组件1101和其他组件之间的交互。例如，处理部件1101可以包括多媒体模块，以方便多媒体组件1104和处理组件1101之间的交互。
存储器1102被配置为存储各种类型的数据以支持在装置1100的操作。这些数据的示例包括用于在装置1100上操作的任何应用程序或方法的指令，联系人数据，电话簿数据，消息，图片，视频等。存储器1102可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
电源组件1103为装置1100的各种组件提供电力。电源组件1103可以包括电源管理 系统，一个或多个电源，及其他与为装置1100生成、管理和分配电力相关联的组件。
多媒体组件1104包括在所述装置1100和用户之间的提供一个输出接口的屏幕。在一些实施例中，屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板，屏幕可以被实现为触摸屏，以接收来自用户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸面板上的手势。所述触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与所述触摸或滑动操作相关的持续时间和压力。在一些实施例中，多媒体组件1104包括一个前置摄像头和/或后置摄像头。当装置1100处于操作模式，如拍摄模式或视频模式时，前置摄像头和/或后置摄像头可以接收外部的多媒体数据。每个前置摄像头和后置摄像头可以是一个固定的光学透镜系统或具有焦距和光学变焦能力。
音频组件1105被配置为输出和/或输入音频信号。例如，音频组件1105包括一个麦克风(MIC)，当装置1100处于操作模式，如呼叫模式、记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器1102或经由通信组件1108发送。在一些实施例中，音频组件1105还包括一个扬声器，用于输出音频信号。
I/O接口1102为处理组件1101和外围接口模块之间提供接口，上述外围接口模块可以是键盘，点击轮，按钮等。这些按钮可包括但不限于：主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件1107包括一个或多个传感器，用于为装置1100提供各个方面的状态评估。例如，传感器组件1107可以检测到装置1100的打开/关闭状态，组件的相对定位，例如所述组件为装置1100的显示器和小键盘，传感器组件1107还可以检测装置1100或装置1100一个组件的位置改变，用户与装置1100接触的存在或不存在，装置1100方位或加速/减速和装置1100的温度变化。传感器组件1107可以包括接近传感器，被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件1107还可以包括光传感器，如CMOS或CCD图像传感器，用于在成像应用中使用。在一些实施例中，该传感器组件1107还可以包括加速度传感器，陀螺仪传感器，磁传感器，压力传感器或温度传感器。
通信组件1108被配置为便于装置1100和其他设备之间有线或无线方式的通信。装置1100可以接入基于通信标准的无线网络，如WiFi，2G或3G，或它们的组合。在一个示例性实施例中，通信组件1108经由广播信道接收来自外部广播管理系统的广播信号或广播相关信息。在一个示例性实施例中，所述通信组件1108还包括近场通信(NFC)模块，以促进短程通信。例如，在NFC模块可基于射频识别(RFID)技术，红外数据协会(IrDA)技术，超宽带(UWB)技术，蓝牙(BT)技术和其他技术来实现。
在示例性实施例中，装置1100可以被一个或多个应用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现，用于执行上述方法。
在示例性实施例中，还提供了一种包括指令的非临时性计算机可读存储介质，例如包括指令的存储器1102，上述指令可由装置1100的处理器1109执行以完成上述方法。例如，所述非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
其中，当所述存储介质中的指令由移动终端的处理器执行时，使得移动终端能够执行一种设备绑定方法，包括：
接收本地终端发送的绑定请求；所述绑定请求携带所述本地终端的用户登录ID；
判断所述绑定请求是否从本地局域网中发出；
当所述绑定请求从本地局域网中发出时，将所述绑定请求发送至服务端，由所述服务端建立所述用户登录ID与本设备的绑定关系；
当所述绑定关系建立完成后，接收所述服务端发送的绑定成功的通告消息，并将该通告消息转发至所述本地终端。
其中，当所述存储介质中的指令由移动终端的处理器执行时，使得移动终端还能够执行另一种设备绑定方法，包括：
向本地局域网中的待绑定设备发送绑定请求，所述绑定请求携带本设备的用户登录ID；
接收所述待绑定设备转发的绑定成功的通告消息；其中所述通告消息在所述待绑定设备将所述绑定请求发送至服务端，由所述服务端成功建立所述用户登录ID与所述待绑定设备的绑定关系后发出。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本公开的其它实施方案。本申请旨在涵盖本公开的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本公开的真正范围和精神由下面的权利要求指出。
应当理解的是，本公开并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本公开的范围仅由所附的权利要求来限制。

Claims (14)

  1. 一种设备绑定方法，其特征在于，所述方法包括：
    接收本地终端发送的绑定请求；所述绑定请求携带所述本地终端的用户登录ID；
    判断所述绑定请求是否从本地局域网中发出；
    当所述绑定请求从本地局域网中发出时，将所述绑定请求发送至服务端，由所述服务端建立所述用户登录ID与本设备的绑定关系；
    当所述绑定关系建立完成后，接收所述服务端发送的绑定成功的通告消息，并将该通告消息转发至所述本地终端。
  2. 如权利要求1所述的方法，其特征在于，所述本地局域网的传输服务包括用户数据包协议UDP服务时，所述接收本地终端发送的绑定请求包括：
    在本地局域网中广播由所述UDP服务开放的UDP端口的端口号；
    监听所述UDP端口，获取本地局域网中的本地终端基于所述UDP端口的端口号向本设备发送的绑定请求。
  3. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    当所述绑定请求从外网中发出时，丢弃该绑定请求。
  4. 如权利要求1所述的方法，其特征在于，所述判断所述绑定请求是否从本地局域网中发出包括：
    判断所述绑定请求中的IP地址是否匹配本地局域网的IP网段；
    当所述绑定请求中的IP地址匹配本地局域网的IP网段时，确定所述绑定请求从本地局域网中发出；
    当所述绑定请求中的IP地址不匹配本地局域网的IP网段时，确定所述绑定请求从外网中发出。
  5. 一种设备绑定方法，其特征在于，所述方法包括：
    向本地局域网中的待绑定设备发送绑定请求，所述绑定请求携带本设备的用户登录ID；
    接收所述待绑定设备转发的绑定成功的通告消息；其中所述通告消息在所述待绑定设备将所述绑定请求发送至服务端，由所述服务端成功建立所述用户登录ID与所述待绑定设备的绑定关系后发出。
  6. 如权利要求5所述的方法，其特征在于，所述本地局域网中的传输服务包括UDP服务时，所述向本地局域网中的待绑定设备发送绑定请求包括：
    基于本地预先设定的由所述UDP服务端开放的UDP端口的端口号向所述待绑定设备发送绑定请求；或
    接收所述待绑定设备在本地局域网中广播的所述UDP服务开放的UDP端口的端口号；基于接收到的所述端口号向所述待绑定设备发送绑定请求。
  7. 一种设备绑定装置，其特征在于，所述装置包括：
    第一接收模块，用于接收本地终端发送的绑定请求；所述绑定请求携带所述本地终端的用户登录ID；
    判断模块，用于判断所述绑定请求是否从本地局域网中发出；
    第一发送模块，用于在所述绑定请求从本地局域网中发出时，将所述绑定请求发送至服务端，由所述服务端建立所述用户登录ID与本设备的绑定关系；
    转发模块，用于在所述绑定关系建立完成后，接收所述服务端发送的绑定成功的通告消息，并将该通告消息转发至所述本地终端。
  8. 如权利要求7所述的装置，其特征在于，所述本地局域网的传输服务包括用户数据包协议UDP服务时，所述第一接收模块包括：
    广播子模块，用于在本地局域网中广播由所述UDP服务开放的UDP端口的端口号；
    获取子单元，用于监听所述UDP端口，获取本地局域网中的本地终端基于所述UDP端口的端口号向本设备发送的绑定请求。
  9. 如权利要求7所述的装置，其特征在于，所述装置还包括：
    丢弃模块，用于在所述绑定请求从外网中发出时，丢弃该绑定请求。
  10. 如权利要求7所述的装置，其特征在于，所述判断模块包括：
    判断子模块，用于判断所述绑定请求中的IP地址是否匹配本地局域网的IP网段；
    第一确定子模块，用于在所述绑定请求中的IP地址匹配本地局域网的IP网段时，确定所述绑定请求从本地局域网中发出；
    第二确定子模块，用于在所述绑定请求中的IP地址不匹配本地局域网的IP网段时，确定所述绑定请求从外网中发出。
  11. 一种设备绑定装置，其特征在于，所述装置包括：
    第二发送模块，用于向本地局域网中的待绑定设备发送绑定请求，所述绑定请求携带本设备的用户登录ID；
    第二接收模块，用于接收所述待绑定设备转发的绑定成功的通告消息；其中所述通告消息在所述待绑定设备将所述绑定请求发送至服务端，由所述服务端成功建立所述用户登录ID与所述待绑定设备的绑定关系后发出。
  12. 如权利要求11所述的装置，其特征在于，所述本地局域网中的传输服务包括UDP服务时，所述第二发送模块包括：
    第一发送子模块，用于基于本地预先设定的由所述UDP服务端开放的UDP端口的端口号向所述待绑定设备发送绑定请求；或
    接收子模块，用于接收所述待绑定设备在本地局域网中广播的所述UDP服务开放的UDP端口的端口号；
    第二发送子模块，基于接收到的所述端口号向所述待绑定设备发送绑定请求。
  13. 一种设备绑定装置，其特征在于，包括：
    处理器；
    用于存储处理器可执行指令的存储器；
    其中，所述处理器被配置为：
    接收本地终端发送的绑定请求；所述绑定请求携带所述本地终端的用户登录ID；
    判断所述绑定请求是否从本地局域网中发出；
    当所述绑定请求从本地局域网中发出时，将所述绑定请求发送至服务端，由所述服务端建立所述用户登录ID与本设备的绑定关系；
    当所述绑定关系建立完成后，接收所述服务端发送的绑定成功的通告消息，并将该通告消息转发至所述本地终端。
  14. 一种设备绑定装置，其特征在于，包括：
    处理器；
    用于存储处理器可执行指令的存储器；
    其中，所述处理器被配置为：
    向本地局域网中的待绑定设备发送绑定请求，所述绑定请求携带本设备的用户登录ID；
    接收所述待绑定设备转发的绑定成功的通告消息；其中所述通告消息在所述待绑定设备将所述绑定请求发送至服务端，由所述服务端成功建立所述用户登录ID与所述待绑定设备的绑定关系后发出。
PCT/CN2015/093205 2015-02-05 2015-10-29 设备绑定方法和装置 Ceased WO2016124015A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
RU2016116759A RU2644509C2 (ru) 2015-02-05 2015-10-29 Способы и аппараты для связывания с устройством
JP2016572884A JP6195685B2 (ja) 2015-02-05 2015-10-29 機器バインディング方法、装置、プログラムおよび記録媒体
KR1020157036561A KR101779484B1 (ko) 2015-02-05 2015-10-29 기기 바인딩 방법, 장치, 프로그램 및 기록매체
MX2016002216A MX373351B (es) 2015-02-05 2015-10-29 Metodos y aparatos para vincularse con un dispositivo.

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510061349.0A CN104639549B (zh) 2015-02-05 2015-02-05 设备绑定方法和装置
CN201510061349.0 2015-02-05

Publications (1)

Publication Number Publication Date
WO2016124015A1 true WO2016124015A1 (zh) 2016-08-11

Family

ID=53217863

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/093205 Ceased WO2016124015A1 (zh) 2015-02-05 2015-10-29 设备绑定方法和装置

Country Status (8)

Country Link
US (1) US10560491B2 (zh)
EP (1) EP3054717B1 (zh)
JP (1) JP6195685B2 (zh)
KR (1) KR101779484B1 (zh)
CN (1) CN104639549B (zh)
MX (1) MX373351B (zh)
RU (1) RU2644509C2 (zh)
WO (1) WO2016124015A1 (zh)

Families Citing this family (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104639549B (zh) 2015-02-05 2018-09-04 小米科技有限责任公司 设备绑定方法和装置
CN104936304B (zh) * 2015-06-01 2018-09-18 小米科技有限责任公司 智能设备绑定方法、智能设备及服务器
CN105975359A (zh) * 2015-08-04 2016-09-28 乐视致新电子科技（天津）有限公司 一种对服务器进行数据清理的方法、装置及服务器
CN105372998A (zh) * 2015-09-29 2016-03-02 小米科技有限责任公司 绑定智能设备的方法及装置
CN105515923A (zh) * 2015-12-03 2016-04-20 小米科技有限责任公司 设备控制方法及装置
CN105847243B (zh) * 2016-03-18 2021-02-26 北京小米移动软件有限公司 访问智能摄像头的方法及装置
WO2017214763A1 (zh) * 2016-06-12 2017-12-21 北京小米移动软件有限公司 上传视频的方法、装置及摄像装置
CN106301785B (zh) * 2016-08-09 2020-09-22 Tcl科技集团股份有限公司 一种智能家居设备与智能终端的绑定方法及系统
CN107342994A (zh) * 2017-06-30 2017-11-10 歌尔科技有限公司 智能音响认证方法、智能音响、终端设备及系统
CN108401037B (zh) * 2018-01-23 2021-07-06 创新先进技术有限公司 用户终端和设备的绑定方法、装置和系统
CN109041038A (zh) * 2018-04-20 2018-12-18 珠海奔图电子有限公司 用于控制电子装置与指定用户绑定的方法和系统
CN109714769B (zh) * 2018-12-28 2020-01-14 北京深思数盾科技股份有限公司 信息绑定方法、装置、设备及存储介质
CN110012455B (zh) * 2019-01-25 2021-10-22 创新先进技术有限公司 一种账号信息的管理方法、装置及电子设备
CN109862012B (zh) * 2019-02-02 2022-03-25 青岛海信网络科技股份有限公司 一种设备接入的方法和设备
CN112118161B (zh) * 2019-06-19 2022-05-06 深圳Tcl新技术有限公司 一种基于Google智能助手的设备控制方法及系统
CN110505640B (zh) * 2019-08-23 2023-01-20 上海庆科信息技术有限公司 设备绑定的处理方法、装置及系统、待配网设备和终端
CN110601934A (zh) * 2019-09-18 2019-12-20 青岛海信智慧家居系统股份有限公司 一种绑定开关设备与开关设备建立绑定关系的方法及装置
CN110838959B (zh) * 2019-11-07 2021-12-21 深圳市欧瑞博科技股份有限公司 智能家居设备绑定方法、装置、电子设备及存储介质
CN111162981A (zh) * 2019-12-31 2020-05-15 青岛海尔科技有限公司 用于智能设备的绑定方法及装置、智能设备
CN111540457B (zh) * 2020-04-02 2023-07-25 出门问问信息科技有限公司 一种绑定方法和装置、电子设备和计算机存储介质
CN111651746B (zh) * 2020-06-01 2023-03-10 支付宝(杭州)信息技术有限公司 登录数据处理方法、装置、设备及系统
CN112468538B (zh) * 2020-11-04 2022-08-02 杭州萤石软件有限公司 一种物联网设备的操作方法及系统
CN112448873B (zh) * 2020-11-17 2023-07-25 深圳Tcl新技术有限公司 设备的绑定方法、装置及计算机可读存储介质
CN112804102B (zh) * 2021-01-12 2023-05-16 北京嘀嘀无限科技发展有限公司 设备绑定方法、装置和终端
CN113596838B (zh) * 2021-07-29 2024-12-03 北京小米移动软件有限公司 设备配网绑定方法、装置、设备及存储介质
CN115695586A (zh) * 2022-09-27 2023-02-03 海尔优家智能科技（北京）有限公司 一种登录的处理方法、设备及系统
CN115665167B (zh) * 2022-11-03 2025-09-23 深圳市欧瑞博科技股份有限公司 基于对等网络的智能物联网系统搭建方法及相关设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103699409A (zh) * 2013-12-19 2014-04-02 小米科技有限责任公司 一种电子设备切入唤醒状态的方法、装置和系统
US20140173049A1 (en) * 2012-12-18 2014-06-19 General Electric Company Binding an appliance to a network at point of purchase
CN104243482A (zh) * 2014-09-24 2014-12-24 海信集团有限公司 一种智能设备控制方法及设备
CN104270758A (zh) * 2014-10-10 2015-01-07 乐鑫信息科技（上海）有限公司 通过wifi与服务器安全建立连接并授权的方法
CN104639549A (zh) * 2015-02-05 2015-05-20 小米科技有限责任公司 设备绑定方法和装置

Family Cites Families (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100913869B1 (ko) * 2002-10-28 2009-08-26 삼성전자주식회사 무선단말장치 및 무선랜 접속정보를 자동으로 생성하고변경하는 방법
US7287077B2 (en) * 2003-08-07 2007-10-23 International Business Machines Corporation Reservation of TCP/UDP ports using UID, GID or process name
JP4622273B2 (ja) * 2004-03-10 2011-02-02 富士ゼロックス株式会社 情報処理端末
JP2008042262A (ja) * 2006-08-01 2008-02-21 Sharp Corp 被制御機器、遠隔制御システム、および、被制御機器の制御方法
US8239551B2 (en) * 2006-12-08 2012-08-07 Telefonaktiebolaget L M Ericsson (Publ) User device, control method thereof, and IMS user equipment
US8522019B2 (en) 2007-02-23 2013-08-27 Qualcomm Incorporated Method and apparatus to create trust domains based on proximity
CZ306790B6 (cs) * 2007-10-12 2017-07-07 Aducid S.R.O. Způsob navazování chráněné elektronické komunikace mezi různými elektronickými prostředky, zejména mezi elektronickými prostředky poskytovatelů elektronických služeb a elektronickými prostředky uživatelů elektronických služeb
US20100125652A1 (en) * 2008-11-14 2010-05-20 Olli Rantapuska Method, Apparatus, and Computer Program for Binding Local Devices to User Accounts
CN102264059A (zh) 2010-05-31 2011-11-30 华为技术有限公司 基于用户标识的通信方法、装置及系统
FI123551B (fi) * 2011-02-22 2013-07-15 Tosibox Oy Menetelmä ja laitejärjestely kiinteistöjen etähallinnan toteuttamiseksi
JP5405622B2 (ja) 2011-08-12 2014-02-05 シャープ株式会社 カメラモジュール
US8876324B2 (en) 2012-01-13 2014-11-04 Hansen International, Inc. Handrail with orientable illumination
US8880881B2 (en) * 2012-01-18 2014-11-04 Square, Inc. Secure communications between devices
US20140096180A1 (en) * 2012-09-28 2014-04-03 Ansuya Negi System, devices, and methods for proximity-based parental controls
CN103019197B (zh) * 2012-12-03 2014-10-29 海信集团有限公司 远程控制智能终端设备的方法及系统
US9374656B2 (en) * 2013-03-15 2016-06-21 Xerox Corporation Method and apparatus for automatically pairing a mobile endpoint device to an output device using a card swipe authentication
CN103209183A (zh) 2013-03-25 2013-07-17 中山大学 一种基于数字家庭网络中的设备注册的方法
CN203324759U (zh) 2013-04-23 2013-12-04 深圳先进技术研究院 基于无线手持终端的用电设备控制系统
CN104184668A (zh) 2014-07-29 2014-12-03 小米科技有限责任公司 物联网的联网方法、装置、路由器、以及第三方设备
CN104202224A (zh) 2014-09-11 2014-12-10 深圳市海派通讯科技有限公司 一种智能家电自动搜索控制方法、装置和系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140173049A1 (en) * 2012-12-18 2014-06-19 General Electric Company Binding an appliance to a network at point of purchase
CN103699409A (zh) * 2013-12-19 2014-04-02 小米科技有限责任公司 一种电子设备切入唤醒状态的方法、装置和系统
CN104243482A (zh) * 2014-09-24 2014-12-24 海信集团有限公司 一种智能设备控制方法及设备
CN104270758A (zh) * 2014-10-10 2015-01-07 乐鑫信息科技（上海）有限公司 通过wifi与服务器安全建立连接并授权的方法
CN104639549A (zh) * 2015-02-05 2015-05-20 小米科技有限责任公司 设备绑定方法和装置

Also Published As

Publication number Publication date
EP3054717A1 (en) 2016-08-10
MX2016002216A (es) 2016-10-06
KR101779484B1 (ko) 2017-10-10
MX373351B (es) 2020-07-06
JP6195685B2 (ja) 2017-09-13
RU2016116759A (ru) 2017-11-02
EP3054717B1 (en) 2020-09-30
JP2017507628A (ja) 2017-03-16
CN104639549B (zh) 2018-09-04
US10560491B2 (en) 2020-02-11
RU2644509C2 (ru) 2018-02-12
CN104639549A (zh) 2015-05-20
KR20160106006A (ko) 2016-09-09
US20160234260A1 (en) 2016-08-11

Similar Documents

Publication Publication Date Title
CN104639549B (zh) 设备绑定方法和装置
WO2016127667A1 (zh) 设备绑定方法和装置
WO2017092417A1 (zh) 基于智能终端设备的网络接入的方法和装置
WO2016145866A1 (zh) 设备绑定方法和装置
CN106452924B (zh) 同步无线网络配置的方法和装置
WO2017107470A1 (zh) 建立无线连接的方法及装置
WO2016155306A1 (zh) 网络接入方法及装置
CN106209800B (zh) 设备权限共享方法和装置
WO2017020413A1 (zh) 网络接入方法、设备及系统
WO2016134600A1 (zh) 智能设备检测方法和装置
WO2017166761A1 (zh) 终端之间的媒体数据共享方法及装置
WO2017071074A1 (zh) 建立连接的方法及装置
CN110891299A (zh) 配网方法及装置、电子设备及存储介质
CN106210797A (zh) 网络直播方法及装置
CN105472698A (zh) 无线网络接入方法及装置
CN106572112A (zh) 访问控制方法及装置
WO2019024053A1 (zh) 无人机控制方法及装置、无人机和遥控设备
WO2016050020A1 (zh) 消息传输方法及装置、电子设备
CN111132374A (zh) 建立无线网络连接的方法及装置
WO2021155702A1 (zh) 通信处理方法、装置、终端、服务器及存储介质
WO2024031730A1 (zh) 授权撤销方法及装置、存储介质
WO2017147780A1 (zh) 数据传输方法、设备及系统
JP6441481B2 (ja) 情報照会方法、装置、プログラム及び記録媒体
WO2016169208A1 (zh) 控制智能设备接入的方法和装置
CN106453073A (zh) 传输信息的方法及装置

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2016572884

Country of ref document: JP

Kind code of ref document: A

Ref document number: 20157036561

Country of ref document: KR

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: MX/A/2016/002216

Country of ref document: MX

ENP Entry into the national phase

Ref document number: 2016116759

Country of ref document: RU

Kind code of ref document: A

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112016009039

Country of ref document: BR

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15880957

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 112016009039

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20160422

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15880957

Country of ref document: EP

Kind code of ref document: A1