WO2016145866A1 - 设备绑定方法和装置 - Google Patents
设备绑定方法和装置 Download PDFInfo
- Publication number
- WO2016145866A1 WO2016145866A1 PCT/CN2015/093225 CN2015093225W WO2016145866A1 WO 2016145866 A1 WO2016145866 A1 WO 2016145866A1 CN 2015093225 W CN2015093225 W CN 2015093225W WO 2016145866 A1 WO2016145866 A1 WO 2016145866A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- bound
- binding
- preset duration
- wireless network
- user
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
- H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
- H04M1/72409—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by interfacing with external accessories
- H04M1/72412—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by interfacing with external accessories using two-way short-range wireless interfaces
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/06—Authentication
- H04W12/068—Authentication using credential vaults, e.g. password manager applications or one time password [OTP] applications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/08—Access security
- H04W12/084—Access security using delegated authorisation, e.g. open authorisation [OAuth] protocol
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
- H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
- H04W8/20—Transfer of user or subscriber data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/141—Setup of application sessions
Definitions
- the present disclosure relates to the field of communications, and in particular, to a device binding method and apparatus.
- WIFI smart device For a WIFI smart device, it is usually necessary to successfully access the router to receive a control command sent by the user from the mobile phone to perform a response action. At the same time, for security reasons, some WIFI smart devices also provide a binding mechanism to establish a binding relationship between the WIFI smart device and the user login account. Only the user login account that establishes the binding relationship is the owner of the WIFI smart device. Only, have the right to use and control the device.
- the present disclosure provides a device binding method and apparatus.
- a device binding method comprising:
- the binding request carries a user login account, and is used to trigger the server to start the binding process within a preset duration, so that the server receives the to-be-bound device within the preset duration.
- the binding confirmation message is sent, the binding relationship between the user login account and the device to be bound is established.
- the method before the determining whether the device to be bound successfully accesses the specified wireless network, the method further includes:
- the name and password of the wireless network are pushed to the device to be bound.
- determining whether the device to be bound successfully accesses the specified wireless network includes:
- the method further includes:
- the prompt message prompting the user to press the binding confirmation button within the preset time period is output; wherein, after the binding confirmation button is pressed, the The device to be bound is triggered to send the binding confirmation message to the server.
- the method further includes:
- the user After receiving the notification message that the user login account sent by the server is successfully bound to the device to be bound, the user outputs a prompt message indicating that the binding is successful;
- the location output corresponding to the device to be bound is used in the preset device list interface.
- a user option prompting the user to re-bind with the device to be bound.
- a device binding method comprising:
- the terminal And receiving, by the terminal, a binding request that is bound to the device to be bound;
- the binding request carries a user login account, and is used to trigger the device to start the binding process within a preset duration;
- the binding relationship between the user login account and the device to be bound is established.
- the binding request carries the unique identifier of the device to be bound
- the determining whether the binding confirmation message sent by the device to be bound is received within the preset duration includes:
- the binding acknowledgement message carries a unique identifier of the device
- the binding acknowledgement message is the same as the unique identifier in the binding request, it is determined that the binding acknowledgement message sent by the to-be-bound device is received within the preset duration.
- the method further includes:
- the notification message that the user login account and the device to be bound fails to be bound is sent to the terminal.
- a device binding apparatus comprising:
- the first determining module is configured to determine whether the device to be bound successfully accesses the designated wireless network
- a sending module configured to send, to the server, a binding request that is bound to the to-be-bound device, when the device to be bound successfully accesses the specified wireless network
- the binding request carries a user login account, and is used to trigger the server to start the binding process within a preset duration, so that the server receives the to-be-bound device within the preset duration.
- the binding confirmation message is sent, the binding relationship between the user login account and the device to be bound is established.
- the device further includes:
- a specifying module configured to: before the determining module determines whether the device to be bound is successfully connected to the specified wireless network, specify a wireless network for the to-be-bound device according to the user configuration;
- a pushing module configured to push the name and password of the wireless network to the device to be bound when receiving an instruction to establish a connection with the wireless network.
- the first determining module includes:
- a first determining sub-module configured to determine whether an announcement message sent by the device to be bound successfully connected to the specified wireless network is received
- a second determining submodule configured to determine that the device to be bound successfully accesses the designated wireless network when receiving the advertisement message successfully connected to the specified wireless network sent by the device to be bound.
- the device further includes:
- a first output module configured to: when the device to be bound successfully accesses the specified wireless network, output a prompt message prompting the user to press the binding confirmation button within the preset duration; wherein the binding confirmation After the button is pressed, the device to be bound is triggered to send the binding confirmation message to the server.
- the device further includes:
- a second output module configured to output a prompt message of successful binding to the user after receiving the notification message that the user login account and the device to be bound are successfully bound by the server;
- a third output module configured to: after receiving the notification message that the user login account and the device to be bound are failed to be bound, the device is to be tied in the preset device list interface. The location corresponding to the device output is used to prompt the user to re-bind the user with the device to be bound.
- a device binding apparatus comprising:
- the receiving module is configured to receive a binding request that is sent by the terminal to be bound to the device to be bound; the binding request carries a user login account, and is used to trigger the device to start the binding process within a preset duration;
- a second determining module configured to determine whether a binding confirmation message sent by the device to be bound is received within the preset duration
- a establishing module configured to establish a binding relationship between the user login account and the device to be bound, when the binding confirmation message sent by the device to be bound is received within the preset duration.
- the binding request carries the unique identifier of the device to be bound
- the second determining module includes:
- a receiving submodule configured to receive a binding acknowledgement message sent by the device within the preset duration; the binding acknowledgement message carries a unique identifier of the device;
- a second determining sub-module configured to determine whether the unique identifier in the binding acknowledgement message is the same as the unique identifier in the binding request
- a second determining submodule configured to: when the unique identifier in the binding acknowledgement message is the same as the unique identifier in the binding request, determine that the device to be bound is sent within the preset duration Bind the confirmation message.
- the device further includes:
- the first sending module is configured to send the user login account to the device to be bound successfully after receiving the binding confirmation message sent by the device to be bound within the preset duration. Announcement message;
- a second sending module configured to send, to the terminal, the user login account to be bound to the device to be bound, when the binding confirmation message sent by the device to be bound is not received within the preset duration Failed announcement message.
- a device binding apparatus including:
- a memory for storing processor executable instructions
- processor is configured to:
- the binding request carries a user login account, and is used to trigger the server to start the binding process within a preset duration, so that the server receives the to-be-bound device within the preset duration.
- the binding confirmation message is sent, the binding relationship between the user login account and the device to be bound is established.
- a device binding apparatus including:
- a memory for storing processor executable instructions
- processor is configured to:
- the terminal And receiving, by the terminal, a binding request that is bound to the device to be bound;
- the binding request carries a user login account, and is used to trigger the device to start the binding process within a preset duration;
- the binding relationship between the user login account and the device to be bound is established.
- the server by determining whether the device to be bound successfully accesses the specified wireless network, and when the device to be bound successfully accesses the specified wireless network, sending the device to the server to be bound a binding request, where the binding request carries a user login account, which is used to trigger the server to start the binding process within a preset duration, and the server receives the to-be-bounded within the preset duration.
- the binding confirmation message sent by the device After the binding confirmation message sent by the device, the binding relationship between the user login account and the device to be bound is established.
- 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 an interface diagram of a smart home APP according to an exemplary embodiment
- FIG. 5 is an interface diagram of another smart home APP according to an exemplary embodiment
- FIG. 6 is an interface diagram of another smart home APP according to an exemplary embodiment
- FIG. 7 is an interface diagram of another smart home APP according to an exemplary embodiment
- FIG. 8 is a schematic block diagram of a 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 block diagram of another device binding apparatus according to an exemplary embodiment.
- FIG. 12 is a schematic block diagram of another device binding apparatus according to an exemplary embodiment
- FIG. 13 is a schematic block diagram of another device binding apparatus according to an exemplary embodiment
- FIG. 14 is a schematic block diagram of another device binding apparatus according to an exemplary embodiment
- FIG. 15 is a schematic block diagram of another device binding apparatus according to an exemplary embodiment
- FIG. 16 is a schematic structural diagram of a device binding apparatus according to an exemplary embodiment
- FIG. 17 is a schematic structural diagram of another apparatus for binding a device 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 present disclosure provides a device binding method, which determines whether a device to be bound successfully accesses a specified wireless network.
- the binding request is performed to be bound to the device to be bound to the server, where the binding request carries the user login account, which is used to trigger the server.
- the binding process is started within a preset duration, and after the server receives the binding confirmation message sent by the device to be bound within the preset duration, the user login account and the device to be bound are established. Binding relationship.
- the binding process can be simplified and the error binding can be avoided, thereby improving the security in the device binding process.
- FIG. 1 is a device binding method according to an exemplary embodiment.
- the device binding method is used in a terminal, and includes the following steps:
- step 101 it is determined whether the device to be bound successfully accesses the designated wireless network
- step 102 when the device to be bound successfully accesses the specified wireless network, send a binding request to the server to be bound to the device to be bound; wherein the binding request carries the user login An account, configured to trigger the server to start the binding process within a preset duration, so that the server receives the binding confirmation message sent by the device to be bound within the preset duration, and then establishes a The binding relationship between the user login account and the device to be bound.
- the terminal may be a smart terminal, such as a smart phone;
- the server may be a server, a server cluster, or a cloud platform; and the device to be bound may be a smart device, such as a smart home device;
- the wireless network can be a WIFI network.
- the smart device is used to control the smart device, the user can usually complete the client software installed on the smart terminal; for example, when implemented, the client software can be a “smart home” APP, and the user passes the The app can centrally manage and control various smart devices in a home environment.
- smart home devices In a smart home environment, a number of smart home devices can be generally included.
- smart home devices such as smart cameras, smart sockets, and smart air purifiers, can be included in a smart home environment.
- the user can log in to the smart home APP through the user login account, and establish a binding relationship with the smart device in the home environment to determine the usage rights.
- the built-in WIFI module can usually send a WIFI broadcast message carrying the device name to the surrounding, and the smart home APP can scan the surrounding smart device by receiving the WIFI broadcast message, and The name of the scanned smart device is generated in the APP interface to facilitate a centralized management of the smart device in the home environment.
- the smart home APP can also be implemented by the built-in Bluetooth module when scanning the smart device; for example, when the smart device is powered on, the Bluetooth signal can be broadcasted to the surrounding through the built-in Bluetooth module, when the smart home The APP can scan surrounding smart devices by detecting the Bluetooth signal sent by the smart device.
- the smart device For the smart device that is scanned, the smart device is not yet connected to the network. Therefore, the user can configure the smart device by using the smart home APP to specify that the smart device is to access the WIFI network.
- the smart home APP when the smart home APP scans a newly added smart device for the first time, it can output a user prompt box of “discover a smart device and click to quickly connect the new device” in the APP interface, when the user clicks the prompt.
- a user prompt box of “discover a smart device and click to quickly connect the new device” in the APP interface, when the user clicks the prompt.
- the OK button in the box is displayed, you can jump to the device connection interface.
- a drop-down list of the WIFI network accessible by the smart device and a connection button can be provided, and the user can specify the WIFI network to be accessed (ie, the routed SSID) for the smart device in the drop-down list.
- the connection process of the smart home and the designated WIFI network may be initiated by clicking the connection button.
- an instruction to establish a connection with the specified WIFI network may be triggered to be sent to the background.
- the smart home APP receives the instruction in the background, the name of the designated WIFI network may be immediately The password is pushed to the smart device, and the smart device can connect to the designated WIFI network according to the name and password of the received WIFI network.
- the implementation manner of the smart home APP pushing the WIFI name and the password to the smart device is not specifically limited in this embodiment; for example, in an implementation manner, the terminal that installs the smart home APP can pass the built-in WIFI module. To scan the surrounding smart device, and then establish a WIFI connection with the scanned smart device. After the WIFI connection is successfully established, the name and password of the WIFI network can be sent to the scanned smart device based on the WIFI connection.
- the terminal that installs the smart home APP may encrypt the name and password of the WIFI network according to a preset algorithm, and perform subcontracting and encrypting the encrypted name and password of the WIFI network. Multiple WIFI broadcast messages are sent to surrounding smart devices.
- the WIFI name and password when the WIFI name and password are pushed to the smart device, it may be completed by a wireless router corresponding to the designated WIFI network, in addition to being completed by the terminal on which the smart home APP is installed.
- the smart home APP can respond to an announcement message that successfully accesses the specified WIFI network. After receiving the notification message, the smart home APP can determine the smart message. The device has successfully accessed the network. After the smart device is successfully connected to the network, the user can initiate a binding with the smart device by operating the smart home APP to obtain the control authority of the smart device.
- the smart home APP when the smart home APP initiates binding to the smart device, the smart home APP may set a preset duration, for example, 30 seconds, in order to simplify the binding process and improve the security of the binding.
- the user is required to press the binding confirmation button (such as the switch key) on the smart device for the binding confirmation within a preset duration. If the user completes the binding confirmation within the preset duration, the binding relationship with the smart device is established.
- the smart home APP can immediately send a binding request to the server to bind to the smart device; the binding request can carry the user.
- the smart home APP After the smart home APP sends a binding request to the server, it may also output a prompting interface for the user to prompt the user to press the specified binding confirmation button within a preset time period. For example, if the preset duration is 30 seconds, the binding confirmation button is the key of the smart device, and the smart home APP can output a “Please press the key to complete the connection within 30 seconds”. Tip box.
- the user When the user presses the binding confirmation button within the preset duration, the user may be triggered to send a binding confirmation message to the server for the binding; the binding confirmation message is A unique identifier of the smart device can be carried.
- the server can start timing and start the binding process for the smart device. After the binding process for the smart device is enabled, the server can start receiving the binding confirmation message sent by the smart device.
- the server may compare the unique identifier in the binding acknowledgement message with the unique identifier in the binding request, if the unique identifier in the received binding acknowledgement message is tied to the binding identifier If the unique identifier in the request is the same, indicating that the server successfully receives the binding confirmation message of the smart device response associated with the current binding process, the smart device and the user login in the binding request may be directly established locally. Corresponding relationship between the accounts, and sending a notification message of successful binding to the smart home APP.
- the user login account has obtained the control authority of the smart device, and the user can log in to the smart home APP to control and operate the smart device through the user login account, and once the binding is successful, the smart device If the device is reset, it no longer needs to be re-bound. The smart device still appears directly in the device list in the smart home APP interface after reset.
- the unique identifier in the binding acknowledgement message received by the server in the preset duration is different from the unique identifier in the binding request, the local binding may be considered as failed, and the server may return a smart home APP. Bind the failed notification message.
- the smart home APP may output a prompt message indicating successful binding to the user in the APP interface; when the smart home APP receives the binding failure sent by the server After the message is advertised, a user option for prompting the user to re-bind the smart device may be outputted in the device list generated in the APP interface, for example, the smart device may be in the device list. After the name, a "reconnect" user option is output, so that the user can re-initiate the binding with the smart device through the smart home app.
- the device to be bound is successfully connected to the specified wireless network.
- the device When the device to be bound successfully accesses the specified wireless network, the device is configured to be bound to the device to be bound.
- a binding request where the binding request carries a user login account, which is used to trigger the server to start the binding process within a preset duration, and the server sends the to-be-bound device to send the device to be bound within the preset duration.
- the binding relationship between the user login account and the device to be bound is established.
- the present disclosure introduces a binding confirmation mechanism, and introduces a concept of binding confirmation time limit. If the binding confirmation is completed within the binding confirmation time limit, the binding is successful, and the binding failure is not completed after the binding confirmation is completed within the binding confirmation time limit.
- the complicated binding verification process is omitted, so that the binding process can be simplified, and since the binding confirmation is triggered by the user manually pressing the binding confirmation button, the error binding can be effectively avoided, thereby improving the device binding. The security of the process.
- FIG. 2 is a device binding method according to an exemplary embodiment.
- the device binding method is used in a server, and includes the following steps:
- step 201 the binding request sent by the terminal to be bound to the device to be bound is received; the binding request carries The user login account is used to trigger the device to start the binding process within the preset time period.
- step 202 it is determined whether a binding confirmation message sent by the device to be bound is received within the preset duration
- step 203 when the binding confirmation message sent by the device to be bound is received within the preset duration, the binding relationship between the user login account and the device to be bound is established.
- the terminal may be a smart terminal, such as a smart phone;
- the server may be a server, a server cluster, or a cloud platform; and the device to be bound may be a smart device, such as a smart home device;
- the wireless network can be a WIFI network.
- the smart device is used to control the smart device, the user can usually complete the client software installed on the smart terminal; for example, when implemented, the client software can be a “smart home” APP, and the user passes the The app can centrally manage and control various smart devices in a home environment.
- smart home devices In a smart home environment, a number of smart home devices can be generally included.
- smart home devices such as smart cameras, smart sockets, and smart air purifiers, can be included in a smart home environment.
- the user can log in to the smart home APP through the user login account, and establish a binding relationship with the smart device in the home environment to determine the usage rights.
- the built-in WIFI module can usually send a WIFI broadcast message carrying the device name to the surrounding, and the smart home APP can scan the surrounding smart device by receiving the WIFI broadcast message, and The name of the scanned smart device is generated in the APP interface to facilitate a centralized management of the smart device in the home environment.
- the smart home APP can also be implemented by the built-in Bluetooth module when scanning the smart device; for example, when the smart device is powered on, the Bluetooth signal can be broadcasted to the surrounding through the built-in Bluetooth module, when the smart home The APP can scan surrounding smart devices by detecting the Bluetooth signal sent by the smart device.
- the smart device For the smart device that is scanned, the smart device is not yet connected to the network. Therefore, the user can configure the smart device by using the smart home APP to specify that the smart device is to access the WIFI network.
- the smart home APP when the smart home APP scans a newly added smart device for the first time, it can output a user prompt box of “discover a smart device and click to quickly connect the new device” in the APP interface, when the user clicks the prompt.
- a user prompt box of “discover a smart device and click to quickly connect the new device” in the APP interface, when the user clicks the prompt.
- the OK button in the box is displayed, you can jump to the device connection interface.
- a drop-down list of the WIFI network accessible by the smart device and a connection button can be provided, and the user can specify the WIFI network to be accessed (ie, the routed SSID) for the smart device in the drop-down list.
- the connection process of the smart home and the designated WIFI network may be initiated by clicking the connection button.
- an instruction to establish a connection with the specified WIFI network may be triggered to be sent to the background.
- the smart home APP receives the instruction in the background, the name of the designated WIFI network may be immediately The password is pushed to the smart device, and the smart device can connect to the designated WIFI network according to the name and password of the received WIFI network.
- the implementation manner of the smart home APP pushing the WIFI name and the password to the smart device is not specifically limited in this embodiment; for example, in an implementation manner, the terminal that installs the smart home APP can pass the built-in WIFI module. To scan the surrounding smart device, and then establish a WIFI connection with the scanned smart device. After the WIFI connection is successfully established, the name and password of the WIFI network can be sent to the scanned smart device based on the WIFI connection.
- the terminal that installs the smart home APP may encrypt the name and password of the WIFI network according to a preset algorithm, and perform subcontracting and encrypting the encrypted name and password of the WIFI network. Multiple WIFI broadcast messages are sent to surrounding smart devices.
- the WIFI name and password when the WIFI name and password are pushed to the smart device, it may be completed by a wireless router corresponding to the designated WIFI network, in addition to being completed by the terminal on which the smart home APP is installed.
- the smart home APP can respond to an announcement message that successfully accesses the specified WIFI network. After receiving the notification message, the smart home APP can determine the smart message. The device has successfully accessed the network. After the smart device is successfully connected to the network, the user can initiate a binding with the smart device by operating the smart home APP to obtain the control authority of the smart device.
- the smart home APP when the smart home APP initiates binding to the smart device, the smart home APP may set a preset duration, for example, 30 seconds, in order to simplify the binding process and improve the security of the binding.
- the user is required to press the binding confirmation button (such as the switch key) on the smart device for the binding confirmation within a preset duration. If the user completes the binding confirmation within the preset duration, the binding relationship with the smart device is established.
- the smart home APP can immediately send a binding request to the server to bind to the smart device; the binding request can carry the user.
- the smart home APP After the smart home APP sends a binding request to the server, it may also output a prompting interface for the user to prompt the user to press the specified binding confirmation button within a preset time period. For example, if the preset duration is 30 seconds, the binding confirmation button is the key of the smart device, and the smart home APP can output a “Please press the key to complete the connection within 30 seconds”. Tip box.
- the user When the user presses the binding confirmation button within the preset duration, the user may be triggered to send a binding confirmation message to the server for the binding; the binding confirmation message is A unique identifier of the smart device can be carried.
- the server can start timing and start the binding process for the smart device. After the binding process for the smart device is enabled, the server can start receiving the binding confirmation message sent by the smart device.
- the server may bind the unique identifier in the binding confirmation message to the binding The unique identifier in the request is compared. If the unique identifier in the binding confirmation message is the same as the unique identifier in the binding request, the server successfully receives the binding of the smart device response associated with the binding process. If the confirmation message is determined, the correspondence between the smart device and the user login account in the binding request may be directly established locally, and a binding success notification message is sent to the smart home APP.
- the user login account has obtained the control authority of the smart device, and the user can log in to the smart home APP to control and operate the smart device through the user login account, and once the binding is successful, the smart device If the device is reset, it no longer needs to be re-bound. The smart device still appears directly in the device list in the smart home APP interface after reset.
- the unique identifier in the binding acknowledgement message received by the server in the preset duration is different from the unique identifier in the binding request, the local binding may be considered as failed, and the server may return a smart home APP. Bind the failed notification message.
- the smart home APP may output a prompt message indicating successful binding to the user in the APP interface; when the smart home APP receives the binding failure sent by the server After the message is advertised, a user option for prompting the user to re-bind the smart device may be outputted in the device list generated in the APP interface, for example, the smart device may be in the device list. After the name, a "reconnect" user option is output, so that the user can re-initiate the binding with the smart device through the smart home app.
- the device to be bound is successfully connected to the specified wireless network.
- the device When the device to be bound successfully accesses the specified wireless network, the device is configured to be bound to the device to be bound.
- a binding request where the binding request carries a user login account, which is used to trigger the server to start the binding process within a preset duration, and the server sends the to-be-bound device to send the device to be bound within the preset duration.
- the binding relationship between the user login account and the device to be bound is established.
- the present disclosure introduces a binding confirmation mechanism, and introduces a concept of binding confirmation time limit. If the binding confirmation is completed within the binding confirmation time limit, the binding is successful, and the binding failure is not completed after the binding confirmation is completed within the binding confirmation time limit.
- the complicated binding verification process is omitted, so that the binding process can be simplified, and since the binding confirmation is triggered by the user manually pressing the binding confirmation button, the error binding can be effectively avoided, thereby improving the device binding. The security of the process.
- FIG. 3 is a device binding method according to an exemplary embodiment, including the following steps:
- step 301 the terminal determines whether the device to be bound successfully accesses the designated wireless network.
- step 302 when the device to be bound successfully accesses the specified wireless network, the terminal sends a binding request to the server to be bound to the device to be bound; wherein the binding request carries the user.
- the login account is used to trigger the server to start the binding process within a preset duration;
- step 303 the server starts the binding process, and determines whether the binding confirmation message sent by the device to be bound is received within the preset duration.
- step 304 when the binding confirmation message sent by the to-be-bound device is received within the preset duration, the server establishes a binding relationship between the user login account and the device to be bound.
- the terminal may be a smart terminal, such as a smart phone;
- the server may be a server, The server cluster or the cloud platform;
- the device to be bound may be a smart device, such as a smart home device;
- the wireless network may be a WIFI network.
- the smart device is used to control the smart device, the user can usually complete the client software installed on the smart terminal; for example, when implemented, the client software can be a “smart home” APP, and the user passes the The app can centrally manage and control various smart devices in a home environment.
- smart home devices In a smart home environment, a number of smart home devices can be generally included.
- smart home devices such as smart cameras, smart sockets, and smart air purifiers, can be included in a smart home environment.
- the user can log in to the smart home APP through the user login account, and establish a binding relationship with the smart device in the home environment to determine the usage rights.
- the built-in WIFI module can usually send a WIFI broadcast message carrying the device name to the surrounding, and the smart home APP can scan the surrounding smart device by receiving the WIFI broadcast message, and The name of the scanned smart device is generated in the APP interface to facilitate a centralized management of the smart device in the home environment.
- the smart home APP can also be implemented by the built-in Bluetooth module when scanning the smart device; for example, when the smart device is powered on, the Bluetooth signal can be broadcasted to the surrounding through the built-in Bluetooth module, the smart home APP.
- the surrounding smart devices can be scanned by detecting the Bluetooth signal sent by the smart device.
- the smart device For the smart device that is scanned, the smart device is not yet connected to the network. Therefore, the user can configure the smart device by using the smart home APP to specify that the smart device is to access the WIFI network.
- the smart home APP when the smart home APP scans a newly added smart device (such as an air purifier) for the first time, it can output a “discover a smart device and click to quickly connect the new device” in the APP interface.
- the user prompt box when the user clicks the OK button in the prompt box, the user can jump to the device connection interface.
- a drop-down list of a WIFI network accessible by the smart device (such as an air purifier) and a connection button can be provided in the device connection interface, and the user can specify the smart device in the drop-down list.
- the connection process of the smart home and the designated WIFI network may be initiated by clicking the connection button.
- an instruction to establish a connection with the specified WIFI network may be triggered to be sent to the background.
- the smart home APP receives the instruction in the background, the name of the designated WIFI network may be immediately The password is pushed to the smart device, and the smart device can connect to the designated WIFI network according to the name and password of the received WIFI network.
- the implementation manner of the smart home APP pushing the WIFI name and the password to the smart device is not specifically limited in this embodiment; for example, in an implementation manner, the terminal that installs the smart home APP can pass the built-in WIFI module. To scan the surrounding smart device, and then establish a WIFI connection with the scanned smart device. After the WIFI connection is successfully established, the name and password of the WIFI network can be sent to the scanned smart device based on the WIFI connection.
- the terminal that installs the smart home APP may use the WIFI network according to a preset algorithm.
- the name and password of the network are encrypted, and the encrypted name and password of the WIFI network are sub-packaged and carried in multiple WIFI broadcast messages and sent to surrounding smart devices.
- the WIFI name and password when the WIFI name and password are pushed to the smart device, it may be completed by a wireless router corresponding to the designated WIFI network, in addition to being completed by the terminal on which the smart home APP is installed.
- the smart home APP can respond to an announcement message that successfully accesses the specified WIFI network. After receiving the notification message, the smart home APP can determine the smart message. The device has successfully accessed the network. After the smart device is successfully connected to the network, a prompt interface may be output to the user in the smart home APP interface to prompt the user; for example, refer to FIG. 6 , where the smart device is an air purifier, which can be intelligent. In the home APP interface, a prompt interface for "congratulations, successful connection of the air purifier" is output to the user.
- the user can initiate a binding with the smart device by operating the smart home APP to obtain the control authority of the smart device.
- the smart home APP when the smart home APP initiates binding to the smart device, the smart home APP may set a preset duration, for example, 30 seconds, in order to simplify the binding process and improve the security of the binding.
- the user is required to press the binding confirmation button (such as the switch key) on the smart device for the binding confirmation within a preset duration. If the user completes the binding confirmation within the preset duration, the binding relationship with the smart device is established.
- the smart home APP can immediately send a binding request to the server to bind to the smart device; the binding request can carry the user.
- the smart home APP may also output a prompting interface for the user to prompt the user to press the specified binding confirmation button within a preset time period. For example, referring to FIG. 7 , if the preset duration is 30 seconds, the binding confirmation button is the key of the smart device, and the smart home APP can output a message to the user, “Please press within 30 seconds. The prompt to open the key to complete the connection.
- the user When the user presses the binding confirmation button within the preset duration, the user may be triggered to send a binding confirmation message to the server for the binding; the binding confirmation message is A unique identifier of the smart device can be carried.
- the server can start timing and start the binding process for the smart device. After the binding process for the smart device is enabled, the server can start receiving the binding confirmation message sent by the smart device.
- the server may compare the unique identifier in the binding acknowledgement message with the unique identifier in the binding request, if the unique identifier in the received binding acknowledgement message is tied to the binding identifier In the request.
- the unique identifier is the same, indicating that the server successfully receives the binding confirmation message of the smart device response associated with the current binding process, and then directly establishes between the smart device and the user login account in the binding request locally.
- Corresponding to the relationship and sending a notification message of successful binding to the smart home APP.
- the user login account has obtained the control authority of the smart device, and the user can log in to the smart home APP to control and operate the smart device through the user login account, and once the binding is successful, the smart device If the device is reset, it no longer needs to be re-bound. The smart device still appears directly in the device list in the smart home APP interface after reset.
- the local binding may be considered as failed, and the server may return a smart home APP. Bind the failed notification message.
- the smart home APP may output a prompt message indicating successful binding to the user in the APP interface; when the smart home APP receives the binding failure sent by the server After the message is advertised, a user option for prompting the user to re-bind the smart device may be outputted in the device list generated in the APP interface, for example, the smart device may be in the device list. After the name, a "reconnect" user option is output, so that the user can re-initiate the binding with the smart device through the smart home app.
- the device to be bound is successfully connected to the specified wireless network.
- the device When the device to be bound successfully accesses the specified wireless network, the device is configured to be bound to the device to be bound.
- a binding request where the binding request carries a user login account, which is used to trigger the server to start the binding process within a preset duration, and the server sends the to-be-bound device to send the device to be bound within the preset duration.
- the binding relationship between the user login account and the device to be bound is established.
- the present disclosure introduces a binding confirmation mechanism, and introduces a concept of binding confirmation time limit. If the binding confirmation is completed within the binding confirmation time limit, the binding is successful, and the binding failure is not completed after the binding confirmation is completed within the binding confirmation time limit.
- the complicated binding verification process is omitted, so that the binding process can be simplified, and since the binding confirmation is triggered by the user manually pressing the binding confirmation button, the error binding can be effectively avoided, thereby improving the device binding. The security of the process.
- the present disclosure also provides an embodiment of an apparatus.
- FIG. 8 is a schematic block diagram of a device binding apparatus according to an exemplary embodiment.
- a device binding apparatus 800 includes: a first judging module 801 and a sending module 802; wherein:
- the first determining module 801 is configured to determine whether the device to be bound successfully accesses the designated wireless network
- the sending module 802 is configured to: when the device to be bound successfully accesses the specified wireless network, send a binding request to the server to be bound to the device to be bound; wherein the binding The requesting to carry the user login account is used to trigger the server to start the binding process within the preset duration, so that the server receives the binding confirmation message sent by the to-be-bound device within the preset duration. Then, the binding relationship between the user login account and the device to be bound is established.
- the device to be bound is successfully connected to the specified wireless network.
- the device When the device to be bound successfully accesses the specified wireless network, the device is configured to be bound to the device to be bound.
- a binding request where the binding request carries a user login account, which is used to trigger the server to start the binding process within a preset duration, and the server sends the to-be-bound device to send the device to be bound within the preset duration.
- the binding relationship between the user login account and the device to be bound is established.
- FIG. 9 is a block diagram of another apparatus according to an exemplary embodiment of the present disclosure.
- the apparatus 800 may further include a designation module 803 on the basis of the foregoing embodiment shown in FIG. 8 .
- And pushing module 804 ; wherein:
- the specifying module 803 is configured to: before the determining module determines whether the device to be bound is successfully connected to the designated wireless network, specify a wireless network for the to-be-bound device according to the user configuration;
- the push module 804 is configured to, when receiving an instruction to establish a connection with the wireless network, push the name and password of the wireless network to the device to be bound.
- FIG. 10 is a block diagram of another apparatus according to an exemplary embodiment of the present disclosure.
- the first determining module 801 may include a judging submodule 801A and a first determining submodule 801B; wherein:
- the first determining sub-module 801A is configured to determine whether an announcement message sent by the device to be bound successfully connected to the designated wireless network is received;
- the first determining sub-module 801B is configured to: when receiving the advertisement message that is successfully connected to the specified wireless network and sent by the device to be bound, determine that the device to be bound successfully accesses the specified Wireless network.
- first determining submodule 801A and the first determining submodule 801B shown in the foregoing apparatus embodiment shown in FIG. 10 may also be included in the foregoing apparatus embodiment of FIG. No restrictions are imposed.
- FIG. 11 is a block diagram of another apparatus according to an exemplary embodiment of the present disclosure.
- the apparatus 800 may further include a first output according to the foregoing embodiment shown in FIG. 8 .
- Module 805 ; wherein:
- the first output module 805 is configured to: when the device to be bound successfully accesses the specified wireless network, output a prompt message prompting the user to press the binding confirmation button within the preset duration; After the binding confirmation button is pressed, the device to be bound is triggered to send the binding confirmation message to the server.
- first output module 805 shown in the foregoing apparatus embodiment shown in FIG. 11 may also be included in the foregoing apparatus embodiment of FIG. 9-10, and the disclosure is not limited thereto.
- FIG. 12 is a block diagram of another apparatus according to an exemplary embodiment of the present disclosure.
- the apparatus 800 may further include a second output according to the foregoing embodiment shown in FIG. Module 806 and third output module 807; wherein:
- the second output module 806 is configured to output a prompt message of successful binding to the user after receiving the notification message that the user login account and the device to be bound are successfully bound by the server;
- the third output module 807 is configured to: when receiving the user login account sent by the server After the notification message of the device to be bound is failed to be bound, the user corresponding to the device to be bound is output in the preset device list interface to prompt the user to re-bind the device with the device to be bound.
- the notification message of the device to be bound is failed to be bound
- the user corresponding to the device to be bound is output in the preset device list interface to prompt the user to re-bind the device with the device to be bound.
- FIG. 13 is a schematic block diagram of a device binding apparatus according to an exemplary embodiment.
- a device binding apparatus 1300 includes: a receiving module 1301, a second determining module 1302, and an establishing module 1303; wherein:
- the receiving module 1301 is configured to: receive a binding request that is sent by the terminal to be bound to the device to be bound; the binding request carries a user login account, and is used to trigger the device to start the binding process within a preset duration. ;
- the second determining module 1302 is configured to: determine whether a binding confirmation message sent by the device to be bound is received within the preset duration;
- the establishing module 1303 is configured to establish a binding relationship between the user login account and the device to be bound when the binding confirmation message sent by the device to be bound is received within the preset duration.
- the device to be bound is successfully connected to the specified wireless network.
- the device When the device to be bound successfully accesses the specified wireless network, the device is configured to be bound to the device to be bound.
- a binding request where the binding request carries a user login account, which is used to trigger the server to start the binding process within a preset duration, and the server sends the to-be-bound device to send the device to be bound within the preset duration.
- the binding relationship between the user login account and the device to be bound is established.
- FIG. 14 is a block diagram of another apparatus according to an exemplary embodiment of the present disclosure, which is carried in the binding request according to the foregoing embodiment shown in FIG.
- the second determining module 1302 may include a receiving submodule 1302A, a second determining submodule 1302B, and a second determining submodule 1302C; wherein:
- the receiving sub-module 1302A is configured to receive a binding confirmation message sent by the device within the preset duration; the binding confirmation message carries a unique identifier of the device;
- the second determining sub-module 1302B is configured to determine whether the unique identifier in the binding acknowledgement message is the same as the unique identifier in the binding request.
- the second determining sub-module 1302C is configured to: when the unique identifier in the binding confirmation message is the same as the unique identifier in the binding request, determine to receive the to-be-bounded within the preset duration A binding confirmation message sent by the device.
- FIG. 15 is a block diagram of another apparatus according to an exemplary embodiment of the present disclosure. Based on the foregoing embodiment shown in FIG. 13, the apparatus 1300 may further include a first sending. Module 1304 and second sending module 1305; wherein:
- the first sending module 1304 is configured to: when the binding confirmation message sent by the device to be bound is received within the preset duration, send the user login account to the terminal to be bound Notification of device binding success interest;
- the second sending module 1305 is configured to send the user login account and the to-be-tied to the terminal when the binding confirmation message sent by the device to be bound is not received within the preset duration The notification message that the device binding failed.
- first sending module 1304 and the second sending module 1305 shown in the foregoing device embodiment shown in FIG. 15 may also be included in the foregoing device embodiment of FIG. 14, and the present disclosure does not limit.
- 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 described as separate components may or may not be physically separate, and the components displayed as modules may or may not be physical modules, ie may be located A place, or it can be distributed to multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the objectives of the present disclosure. 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 carries a user login account, and is used to trigger the server to start the binding process within a preset duration, so that the server receives the to-be-bound device within the preset duration.
- the binding confirmation message is sent, the binding relationship between the user login account and the device to be bound is established.
- 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:
- the binding request carries a user login account, and is used to trigger the server to start the binding process within a preset duration, so that the server receives the to-be-bound device within the preset duration.
- the binding confirmation message is sent, the binding relationship between the user login account and the device to be bound is established.
- the present disclosure further provides a device binding device, the device comprising:
- a memory for storing processor executable instructions
- processor is configured to:
- the terminal And receiving, by the terminal, a binding request that is bound to the device to be bound;
- the binding request carries a user login account, and is used to trigger the device to start the binding process within a preset duration;
- the binding relationship between the user login account and the device to be bound is established.
- the present disclosure also provides a server, the server 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:
- the terminal And receiving, by the terminal, a binding request that is bound to the device to be bound;
- the binding request carries a user login account, and is used to trigger the device to start the binding process within a preset duration;
- the binding relationship between the user login account and the device to be bound is established.
- FIG. 16 is a schematic structural diagram of a device binding apparatus according to an exemplary embodiment.
- a device binding device 1600 which may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, according to an exemplary embodiment, is shown.
- apparatus 1600 can include one or more of the following components: processing component 1601, memory 1602, power component 1603, multimedia component 1604, audio component 1605, input/output (I/O) interface 1606, sensor component 1607, And a communication component 1608.
- Processing component 1601 typically controls the overall operation of device 1600, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations.
- Processing component 1601 can include one or more processors 1609 to execute instructions to perform all or part of the steps of the above described methods.
- processing component 1601 can include one or more modules to facilitate interaction between component 1601 and other components.
- processing component 1601 can include a multimedia module to facilitate interaction between multimedia component 1604 and processing component 1601.
- Memory 1602 is configured to store various types of data to support operation at device 1600. Examples of such data include instructions for any application or method operating on device 1600, contact data, phone book data, messages, pictures, videos, and the like.
- the memory 1602 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 Electrically erasable programmable read only memory
- PROM Programmable Read Only Memory
- ROM Read Only Memory
- Magnetic Memory Flash Memory
- Disk Disk or Optical Disk.
- Power component 1603 provides power to various components of device 1600.
- Power component 1603 can include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for device 1600.
- Multimedia component 1604 includes a screen between the device 1600 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 1604 includes a front camera and/or a rear camera. When the device 1600 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 1605 is configured to output and/or input an audio signal.
- audio component 1605 includes a microphone (MIC) that is configured to receive an external audio signal when device 1600 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 1602 or transmitted via communication component 1608.
- audio component 1605 also includes a speaker for outputting an audio signal.
- the I/O interface 1602 provides an interface between the processing component 1601 and the 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 1607 includes one or more sensors for providing state assessment of various aspects to device 1600.
- sensor assembly 1607 can detect an open/closed state of device 1600, relative positioning of components, such as the display and keypad of device 1600, and sensor component 1607 can also detect a change in position of one component of device 1600 or device 1600. The presence or absence of contact by the user with the device 1600, the orientation or acceleration/deceleration of the device 1600 and the temperature change of the device 1600.
- Sensor assembly 1607 can include a proximity sensor configured to detect the presence of nearby objects without any physical contact.
- Sensor assembly 1607 can also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
- the sensor assembly 1607 can also include an acceleration sensor, a gyro sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
- Communication component 1608 is configured to facilitate wired or wireless communication between device 1600 and other devices.
- the device 1600 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof.
- communication component 1608 receives broadcast signals or broadcast associated information from an external broadcast management system via a broadcast channel.
- the communication component 1608 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
- device 1600 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 package
- a memory 1602 of instructions is executable by processor 1609 of device 1600 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 carries a user login account, and is used to trigger the server to start the binding process within a preset duration, so that the server receives the to-be-bound device within the preset duration.
- the binding confirmation message is sent, the binding relationship between the user login account and the device to be bound is established.
- the present disclosure further provides a device binding device, the device comprising:
- a memory for storing processor executable instructions
- processor is configured to:
- the terminal And receiving, by the terminal, a binding request that is bound to the device to be bound;
- the binding request carries a user login account, and is used to trigger the device to start the binding process within a preset duration;
- the binding relationship between the user login account and the device to be bound is established.
- FIG. 17 is a block diagram of a device binding device 1700, according to an exemplary embodiment.
- device 1700 can be provided as a server.
- apparatus 1700 includes a processing component 1722 that further includes one or more processors, and memory resources represented by memory 1732 for storing instructions executable by processing component 1722, such as an application.
- the application stored in memory 1732 can include one or more modules each corresponding to a set of instructions.
- processing component 1722 is configured to execute instructions to perform the device binding method described above.
- Apparatus 1700 can also include a power supply component 1726 configured to perform power management of apparatus 1700, a wired or wireless network interface 1750 configured to connect apparatus 1700 to the network, and an input/output (I/O) interface 1758.
- the device 1700 can operate based on an operating system stored in the memory 1732, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM or the like.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Human Computer Interaction (AREA)
- Databases & Information Systems (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephonic Communication Services (AREA)
- Telephone Function (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Selective Calling Equipment (AREA)
Abstract
Description
Claims (18)
- 一种设备绑定方法,其特征在于,所述方法包括:判断待绑定设备是否成功接入指定的无线网络;当所述待绑定设备成功接入指定的无线网络时,向服务端发送与所述待绑定设备进行绑定的绑定请求;其中,所述绑定请求携带用户登录账号,用于触发所述服务端在预设时长内开启绑定进程,以使得所述服务端在所述预设时长内收到所述待绑定设备发送的绑定确认消息后,建立所述用户登录账号与所述待绑定设备的绑定关系。
- 如权利要求1所述的方法,其特征在于,所述判断待绑定设备是否成功接入指定的无线网络之前,还包括:根据用户配置为所述待绑定设备指定无线网络;当接收到与所述无线网络建立连接的指令时,将所述无线网络的名称和密码推送给所述待绑定设备。
- 如权利要求1所述的方法,其特征在于,所述判断待绑定设备是否成功接入指定的无线网络包括:判断是否接收到所述待绑定设备发送的成功连接到所述指定的无线网络的通告消息;当接收到所述待绑定设备发送的成功连接到所述指定的无线网络的通告消息时,确定所述待绑定设备成功接入所述指定的无线网络。
- 如权利要求1所述的方法,其特征在于,所述方法还包括:当所述待绑定设备成功接入指定的无线网络时,输出提示用户在所述预设时长内按动绑定确认按钮的提示消息;其中,所述绑定确认按钮被按动后,会触发所述待绑定设备向所述服务端发送所述绑定确认消息。
- 如权利要求1所述的方法,其特征在于,所述方法还包括:当接收到所述服务端发送的所述用户登录账号与所述待绑定设备绑定成功的通告消息后,向用户输出绑定成功的提示消息;当接收到所述服务端发送的所述用户登录账号与所述待绑定设备绑定失败的通告消息后,在预设的设备列表界面中与所述待绑定设备对应的位置输出用于提示用户与所述待绑定设备进行重新绑定的用户选项。
- 一种设备绑定方法,其特征在于,所述方法包括:接收终端发送的与待绑定设备进行绑定的绑定请求;所述绑定请求携带用户登录账号,用于触发本设备在预设时长内开启绑定进程;判断在所述预设时长内是否接收到所述待绑定设备发送的绑定确认消息;当在所述预设时长内收到所述待绑定设备发送的绑定确认消息时,建立所述用户登录账号与所述待绑定设备的绑定关系。
- 如权利要求6所述的方法,其特征在于,所述绑定请求中携带所述待绑定设备的 唯一标识;所述判断在所述预设时长内是否收到所述待绑定设备发送的绑定确认消息包括:在所述预设时长内接收设备发送的绑定确认消息;所述绑定确认消息携带所述设备的唯一标识;判断所述绑定确认消息中的唯一标识与所述绑定请求中的唯一标识是否相同;如果所述绑定确认消息中的唯一标识与所述绑定请求中的唯一标识相同,则确定在所述预设时长内接收到所述待绑定设备发送的绑定确认消息。
- 如权利要求6所述的方法,其特征在于,所述方法还包括:当在所述预设时长内收到所述待绑定设备发送的绑定确认消息时,向所述终端发送所述用户登录账号与所述待绑定设备绑定成功的通告消息;当在所述预设时长内未收到所述待绑定设备发送的绑定确认消息时,向所述终端发送所述用户登录账号与所述待绑定设备绑定失败的通告消息。
- 一种设备绑定装置,其特征在于,所述装置包括:第一判断模块,用于判断待绑定设备是否成功接入指定的无线网络;发送模块,用于在所述待绑定设备成功接入指定的无线网络时,向服务端发送与所述待绑定设备进行绑定的绑定请求;其中,所述绑定请求携带用户登录账号,用于触发所述服务端在预设时长内开启绑定进程,以使得所述服务端在所述预设时长内收到所述待绑定设备发送的绑定确认消息后,建立所述用户登录账号与所述待绑定设备的绑定关系。
- 如权利要求9所述的装置,其特征在于,所述装置还包括:指定模块,用于在所述判断模块判断待绑定设备是否成功接入指定的无线网络之前,根据用户配置为所述待绑定设备指定无线网络;推送模块,用于在接收到与所述无线网络建立连接的指令时,将所述无线网络的名称和密码推送给所述待绑定设备。
- 如权利要求9所述的装置,其特征在于,所述第一判断模块包括:第一判断子模块,用于判断是否接收到所述待绑定设备发送的成功连接到所述指定的无线网络的通告消息;第二确定子模块,用于在接收到所述待绑定设备发送的成功连接到所述指定的无线网络的通告消息时,确定所述待绑定设备成功接入所述指定的无线网络。
- 如权利要求9所述的装置,其特征在于,所述装置还包括:第一输出模块,用于在所述待绑定设备成功接入指定的无线网络时,输出提示用户在所述预设时长内按动绑定确认按钮的提示消息;其中,所述绑定确认按钮被按动后,会触发所述待绑定设备向所述服务端发送所述绑定确认消息。
- 如权利要求9所述的装置,其特征在于,所述装置还包括:第二输出模块,用于在接收到所述服务端发送的所述用户登录账号与所述待绑定设备 绑定成功的通告消息后,向用户输出绑定成功的提示消息;第三输出模块,用于在当接收到所述服务端发送的所述用户登录账号与所述待绑定设备绑定失败的通告消息后,在预设的设备列表界面中与所述待绑定设备对应的位置输出用于提示用户与所述待绑定设备进行重新绑定的用户选项。
- 一种设备绑定装置,其特征在于,所述装置包括:接收模块,用于接收终端发送的与待绑定设备进行绑定的绑定请求;所述绑定请求携带用户登录账号,用于触发本设备在预设时长内开启绑定进程;第二判断模块,用于判断在所述预设时长内是否接收到所述待绑定设备发送的绑定确认消息;建立模块,用于在所述预设时长内收到所述待绑定设备发送的绑定确认消息时,建立所述用户登录账号与所述待绑定设备的绑定关系。
- 如权利要求14所述的装置,其特征在于,所述绑定请求中携带所述待绑定设备的唯一标识;所述第二判断模块包括:接收子模块,用于在所述预设时长内接收设备发送的绑定确认消息;所述绑定确认消息携带所述设备的唯一标识;第二判断子模块,用于判断所述绑定确认消息中的唯一标识与所述绑定请求中的唯一标识是否相同;第二确定子模块,用于在所述绑定确认消息中的唯一标识与所述绑定请求中的唯一标识相同时,确定在所述预设时长内接收到所述待绑定设备发送的绑定确认消息。
- 如权利要求14所述的装置,其特征在于,所述装置还包括:第一发送模块,用于在所述预设时长内收到所述待绑定设备发送的绑定确认消息时,向所述终端发送所述用户登录账号与所述待绑定设备绑定成功的通告消息;第二发送模块,用于在所述预设时长内未收到所述待绑定设备发送的绑定确认消息时,向所述终端发送所述用户登录账号与所述待绑定设备绑定失败的通告消息。
- 一种设备绑定装置,其特征在于,包括:处理器;用于存储处理器可执行指令的存储器;其中,所述处理器被配置为:判断待绑定设备是否成功接入指定的无线网络;当所述待绑定设备成功接入指定的无线网络时,向服务端发送与所述待绑定设备进行绑定的绑定请求;其中,所述绑定请求携带用户登录账号,用于触发所述服务端在预设时长内开启绑定进程,以使得所述服务端在所述预设时长内收到所述待绑定设备发送的绑定确认消息后,建立所述用户登录账号与所述待绑定设备的绑定关系。
- 一种设备绑定装置,其特征在于,包括:处理器;用于存储处理器可执行指令的存储器;其中,所述处理器被配置为:接收终端发送的与待绑定设备进行绑定的绑定请求;所述绑定请求携带用户登录账号,用于触发本设备在预设时长内开启绑定进程;判断在所述预设时长内是否接收到所述待绑定设备发送的绑定确认消息;当在所述预设时长内收到所述待绑定设备发送的绑定确认消息时,建立所述用户登录账号与所述待绑定设备的绑定关系。
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
BR112016006057A BR112016006057A2 (pt) | 2015-03-13 | 2015-10-29 | métodos e aparelhos para a ligação com um dispositivo |
KR1020157036252A KR101851147B1 (ko) | 2015-03-13 | 2015-10-29 | 기기 바인딩 방법, 장치, 프로그램 및 기록매체 |
JP2017505704A JP6301007B2 (ja) | 2015-03-13 | 2015-10-29 | 機器バインディング方法、装置、プログラム及び記録媒体 |
MX2016001549A MX357512B (es) | 2015-03-13 | 2015-10-29 | Metodo y aparato para enlace con dispositivo. |
RU2016111615A RU2628323C1 (ru) | 2015-03-13 | 2015-10-29 | Способы и аппаратура для привязки к устройству |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201510112726.9A CN104780154B (zh) | 2015-03-13 | 2015-03-13 | 设备绑定方法和装置 |
CN201510112726.9 | 2015-03-13 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2016145866A1 true WO2016145866A1 (zh) | 2016-09-22 |
Family
ID=53621398
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2015/093225 WO2016145866A1 (zh) | 2015-03-13 | 2015-10-29 | 设备绑定方法和装置 |
Country Status (9)
Country | Link |
---|---|
US (1) | US10178214B2 (zh) |
EP (1) | EP3068155B1 (zh) |
JP (1) | JP6301007B2 (zh) |
KR (1) | KR101851147B1 (zh) |
CN (1) | CN104780154B (zh) |
BR (1) | BR112016006057A2 (zh) |
MX (1) | MX357512B (zh) |
RU (1) | RU2628323C1 (zh) |
WO (1) | WO2016145866A1 (zh) |
Families Citing this family (50)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104780154B (zh) | 2015-03-13 | 2018-06-19 | 小米科技有限责任公司 | 设备绑定方法和装置 |
CN105159523A (zh) * | 2015-07-31 | 2015-12-16 | 小米科技有限责任公司 | 目标功能的开启方法、装置及系统 |
CN106487767B (zh) * | 2015-08-31 | 2020-01-21 | 阿里巴巴集团控股有限公司 | 验证信息的更新方法及装置 |
CN105187433B (zh) * | 2015-09-22 | 2019-02-19 | 小米科技有限责任公司 | 设备接入方法及装置 |
CN105372998A (zh) * | 2015-09-29 | 2016-03-02 | 小米科技有限责任公司 | 绑定智能设备的方法及装置 |
CN105306264A (zh) * | 2015-10-09 | 2016-02-03 | 四川长虹电器股份有限公司 | 智能家电设备的网络配置和远程注册绑定的方法及系统 |
CN105703984B (zh) * | 2015-11-11 | 2019-07-16 | 四川长虹电器股份有限公司 | 一种连接方法及移动终端 |
CN105357629A (zh) * | 2015-11-20 | 2016-02-24 | 青岛海尔股份有限公司 | 移动终端与智能家电的绑定方法及装置 |
CN105487392A (zh) * | 2015-11-26 | 2016-04-13 | 小米科技有限责任公司 | 设备展示方法及装置 |
CN105530683A (zh) * | 2015-12-21 | 2016-04-27 | 小米科技有限责任公司 | 网络连接方法和装置 |
CN106911642A (zh) * | 2015-12-23 | 2017-06-30 | 北京奇虎科技有限公司 | 一种智能设备绑定方法及装置 |
CN105979522A (zh) * | 2016-05-16 | 2016-09-28 | 北京小米移动软件有限公司 | 设备绑定方法及装置 |
CN106713418B (zh) * | 2016-11-28 | 2019-10-11 | 北京小米移动软件有限公司 | 重置结果确认方法、装置、服务器和移动终端 |
US11038882B2 (en) * | 2017-04-03 | 2021-06-15 | Panasonic Intellectual Property Management Co., Ltd. | Remote control system, server device, terminal device, electrical apparatus registration method, and program |
CN109309653A (zh) * | 2017-07-28 | 2019-02-05 | 阿里巴巴集团控股有限公司 | 信息绑定方法、设备及系统 |
CN109308647B (zh) * | 2017-07-28 | 2022-05-24 | 阿里巴巴集团控股有限公司 | 实现商品信息绑定、商品下单的方法、设备和系统 |
CN107679392B (zh) * | 2017-09-01 | 2021-07-16 | 台州市吉吉知识产权运营有限公司 | 一种智能硬件的控制方法、装置和系统 |
CN108134718B (zh) | 2017-11-16 | 2019-07-23 | 百度在线网络技术(北京)有限公司 | 发现设备的方法、装置、设备和计算机存储介质 |
CN108282767B (zh) * | 2017-12-29 | 2020-11-17 | 歌尔科技有限公司 | 一种配对方法、装置和系统 |
CN108306938B (zh) * | 2017-12-29 | 2021-08-24 | 青岛海尔科技有限公司 | 一种物联产品自动入网的方法、装置及网关 |
CN108846279A (zh) * | 2018-06-22 | 2018-11-20 | 偶忆科技(深圳)有限公司 | 智能无线系统的权限管理方法、系统及现场装置及终端 |
CN108834226A (zh) * | 2018-06-25 | 2018-11-16 | 深圳市智能体科技有限公司 | 一种智能设备绑定的方法及系统 |
CN109144971B (zh) * | 2018-08-06 | 2019-07-23 | 珠海格力电器股份有限公司 | 设备绑定方法及匹配系统 |
CN109660432B (zh) * | 2018-10-31 | 2021-12-21 | 无锡小天鹅电器有限公司 | 家用电器及其控制系统和绑定方法 |
CN109474595B (zh) * | 2018-11-13 | 2022-09-20 | 京东方科技集团股份有限公司 | 一种电子设备绑定方法、电子设备、移动终端和服务器 |
CN109587016B (zh) * | 2018-11-20 | 2021-08-13 | 广东美的制冷设备有限公司 | 家电绑定系统、方法、移动终端、服务器、家电及介质 |
CN109714769B (zh) * | 2018-12-28 | 2020-01-14 | 北京深思数盾科技股份有限公司 | 信息绑定方法、装置、设备及存储介质 |
CN109889596A (zh) * | 2018-12-29 | 2019-06-14 | 珠海汇金科技股份有限公司 | 智能锁绑定方法、智能锁及智能锁绑定系统 |
CN110278291B (zh) * | 2019-03-19 | 2022-02-11 | 新华三技术有限公司 | 无线设备命名方法、存储介质及系统 |
CN110300117B (zh) * | 2019-07-05 | 2021-03-02 | 杭州博联智能科技股份有限公司 | Iot设备与用户绑定的认证方法、设备及介质 |
CN112443867B (zh) * | 2019-08-29 | 2022-11-29 | 宁波方太厨具有限公司 | 楼宇集中式排烟系统中室内吸油烟机遥控终端绑定方法 |
CN113099511B (zh) * | 2020-01-09 | 2023-02-17 | 阿里巴巴集团控股有限公司 | 网络配置方法、装置、设备和系统 |
CN111246439A (zh) * | 2020-01-09 | 2020-06-05 | 广东小天才科技有限公司 | 一种绑定手表的方法及终端 |
CN111246597B (zh) * | 2020-01-10 | 2021-07-16 | 宁波方太厨具有限公司 | 无线自组网系统 |
CN111787517A (zh) * | 2020-02-21 | 2020-10-16 | 北京沃东天骏信息技术有限公司 | 智能设备激活绑定的方法和装置 |
CN111490916B (zh) * | 2020-04-15 | 2022-03-11 | 公牛集团股份有限公司 | 紫蜂ZigBee子设备的绑定方法、系统、装置及介质 |
CN111478816B (zh) * | 2020-04-15 | 2023-04-07 | 公牛集团股份有限公司 | 紫蜂ZigBee子设备的配置方法、系统、装置及介质 |
CN111565137A (zh) * | 2020-04-28 | 2020-08-21 | 北京芯创睿胜科技有限公司 | 实现WiFi配网与设备绑定的系统及方法 |
CN111554399B (zh) * | 2020-05-25 | 2023-07-25 | 出门问问信息科技有限公司 | 一种重置方法和装置、电子设备和计算机存储介质 |
CN113784456A (zh) * | 2020-06-29 | 2021-12-10 | 北京沃东天骏信息技术有限公司 | 设备连接方法、装置及存储介质 |
CN113872782A (zh) * | 2020-06-30 | 2021-12-31 | 漳州立达信光电子科技有限公司 | 一种设备组网方法、控制设备和物联网系统 |
CN111885594B (zh) * | 2020-06-30 | 2024-03-22 | 海尔优家智能科技(北京)有限公司 | 设备绑定方法及装置 |
CN111711698A (zh) * | 2020-07-01 | 2020-09-25 | 青岛亿联客信息技术有限公司 | 一种智能设备入网方法、装置及智能设备控制系统、方法 |
CN111885144B (zh) * | 2020-07-20 | 2022-09-16 | 青岛易来智能科技股份有限公司 | 一种设备绑定方法及装置 |
CN112039739B (zh) * | 2020-08-31 | 2022-05-10 | 海信(山东)空调有限公司 | 控制家电配网绑定的方法和家电 |
CN114125837A (zh) * | 2020-08-31 | 2022-03-01 | Oppo广东移动通信有限公司 | 设备配网方法、装置、智能台灯及存储介质 |
CN112448873B (zh) * | 2020-11-17 | 2023-07-25 | 深圳Tcl新技术有限公司 | 设备的绑定方法、装置及计算机可读存储介质 |
CN113596838A (zh) * | 2021-07-29 | 2021-11-02 | 北京小米移动软件有限公司 | 设备配网绑定方法、装置、设备及存储介质 |
CN114422216B (zh) * | 2021-12-31 | 2024-01-09 | 杭州华橙软件技术有限公司 | 一种物联网设备绑定方法、装置和存储介质 |
CN115297463B (zh) * | 2022-06-22 | 2024-04-19 | 青岛海尔科技有限公司 | 设备绑定方法和装置、存储介质及电子装置 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060288227A1 (en) * | 2005-06-15 | 2006-12-21 | Nokia Corporation | Management of access control in wireless networks |
CN102332127A (zh) * | 2011-09-15 | 2012-01-25 | 深圳市酷开网络科技有限公司 | 基于网络电视在线支付业务的账户绑定方法和支付方法 |
CN104202306A (zh) * | 2014-08-15 | 2014-12-10 | 小米科技有限责任公司 | 访问认证方法、装置及系统 |
CN104780154A (zh) * | 2015-03-13 | 2015-07-15 | 小米科技有限责任公司 | 设备绑定方法和装置 |
Family Cites Families (23)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030097443A1 (en) | 2001-11-21 | 2003-05-22 | Richard Gillett | Systems and methods for delivering content over a network |
US20060021017A1 (en) | 2004-07-21 | 2006-01-26 | International Business Machines Corporation | Method and system for establishing federation relationships through imported configuration files |
US7913084B2 (en) * | 2006-05-26 | 2011-03-22 | Microsoft Corporation | Policy driven, credential delegation for single sign on and secure access to network resources |
US8106742B2 (en) * | 2006-08-04 | 2012-01-31 | Tegic Communications, Inc. | Remotely controlling one or more client devices detected over a wireless network using a mobile device |
EP2224668B1 (en) * | 2009-02-27 | 2014-05-14 | BlackBerry Limited | System and method for enabling encrypted voice communications between an external device and telephony devices associated with an enterprise network |
CN201421160Y (zh) * | 2009-05-18 | 2010-03-10 | 江苏技术师范学院 | 基于ZigBee技术的远程空调智能控制装置 |
US8190129B2 (en) | 2009-06-22 | 2012-05-29 | Mourad Ben Ayed | Systems for three factor authentication |
US8498618B2 (en) | 2009-06-22 | 2013-07-30 | Mourad Ben Ayed | Systems for intelligent authentication based on proximity |
CN101944996B (zh) | 2010-07-09 | 2012-11-21 | 北京海泰方圆科技有限公司 | 一种按键型智能密码钥匙及为其预制证书的方法 |
JP2012080482A (ja) * | 2010-10-06 | 2012-04-19 | Panasonic Corp | サーバ、端末、機器およびそれらの紐付け方法、紐付けプログラム |
CN103179636A (zh) * | 2011-12-21 | 2013-06-26 | 株式会社Ntt都科摩 | 一种移动互联网接入点、系统及其伙伴发现方法 |
WO2013138532A1 (en) * | 2012-03-14 | 2013-09-19 | Headwater Partners I Llc | Mobile device activation via dynamically selected access network |
CN103840953B (zh) * | 2012-11-21 | 2017-10-31 | 中兴通讯股份有限公司 | 远程日志实时获取方法及系统 |
CN104079543B (zh) | 2013-03-29 | 2017-06-06 | 珠海格力电器股份有限公司 | 智能家居系统监控权限的获取方法、装置和系统 |
CN103176468B (zh) | 2013-04-07 | 2015-01-21 | 深圳市闪联信息技术有限公司 | 基于定时绑定机制的智能家电认证方法 |
JP2015002543A (ja) * | 2013-06-18 | 2015-01-05 | キヤノン株式会社 | 機器管理装置および通信機器およびそれらの制御方法およびプログラム |
CN103399530B (zh) | 2013-07-01 | 2017-03-15 | 惠州Tcl家电集团有限公司 | 智能家电统一控制的方法、系统和管控平台以及控制终端 |
JP2015033085A (ja) * | 2013-08-06 | 2015-02-16 | キヤノン株式会社 | 通信装置、通信装置の制御方法、プログラム |
JP2015050752A (ja) * | 2013-09-04 | 2015-03-16 | シャープ株式会社 | 遠隔操作システムにおける登録支援システム |
CN103686674A (zh) | 2013-09-30 | 2014-03-26 | 深圳市通力科技开发有限公司 | 网络接入方法、智能终端以及wifi接入设备 |
CN103914040A (zh) * | 2013-12-31 | 2014-07-09 | 海尔集团公司 | 家电设备的控制系统及控制方法 |
US9532225B2 (en) * | 2014-06-12 | 2016-12-27 | General Electric Company | Secure pairing of end user devices with instruments |
CN104243576A (zh) * | 2014-09-11 | 2014-12-24 | 深圳万物新生科技有限公司 | 智能家居系统及其绑定用户终端与设备终端的方法 |
-
2015
- 2015-03-13 CN CN201510112726.9A patent/CN104780154B/zh active Active
- 2015-10-29 JP JP2017505704A patent/JP6301007B2/ja active Active
- 2015-10-29 MX MX2016001549A patent/MX357512B/es active IP Right Grant
- 2015-10-29 RU RU2016111615A patent/RU2628323C1/ru active
- 2015-10-29 KR KR1020157036252A patent/KR101851147B1/ko active IP Right Grant
- 2015-10-29 BR BR112016006057A patent/BR112016006057A2/pt not_active IP Right Cessation
- 2015-10-29 WO PCT/CN2015/093225 patent/WO2016145866A1/zh active Application Filing
-
2016
- 2016-03-09 EP EP16159503.8A patent/EP3068155B1/en active Active
- 2016-03-10 US US15/066,808 patent/US10178214B2/en active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060288227A1 (en) * | 2005-06-15 | 2006-12-21 | Nokia Corporation | Management of access control in wireless networks |
CN102332127A (zh) * | 2011-09-15 | 2012-01-25 | 深圳市酷开网络科技有限公司 | 基于网络电视在线支付业务的账户绑定方法和支付方法 |
CN104202306A (zh) * | 2014-08-15 | 2014-12-10 | 小米科技有限责任公司 | 访问认证方法、装置及系统 |
CN104780154A (zh) * | 2015-03-13 | 2015-07-15 | 小米科技有限责任公司 | 设备绑定方法和装置 |
Also Published As
Publication number | Publication date |
---|---|
KR20160121376A (ko) | 2016-10-19 |
MX2016001549A (es) | 2017-01-05 |
US20160269527A1 (en) | 2016-09-15 |
KR101851147B1 (ko) | 2018-04-24 |
EP3068155B1 (en) | 2017-12-20 |
US10178214B2 (en) | 2019-01-08 |
CN104780154B (zh) | 2018-06-19 |
CN104780154A (zh) | 2015-07-15 |
EP3068155A1 (en) | 2016-09-14 |
JP6301007B2 (ja) | 2018-03-28 |
RU2628323C1 (ru) | 2017-08-15 |
JP2017521968A (ja) | 2017-08-03 |
BR112016006057A2 (pt) | 2017-08-01 |
MX357512B (es) | 2018-07-12 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2016145866A1 (zh) | 设备绑定方法和装置 | |
US10104599B2 (en) | Device binding methods and apparatuses | |
WO2017092417A1 (zh) | 基于智能终端设备的网络接入的方法和装置 | |
JP6272552B2 (ja) | デバイスバインディング方法、装置、プログラム及び記録媒体 | |
WO2016183992A1 (zh) | 对账户与设备的控制关系进行管理的方法、装置和系统 | |
WO2017143729A1 (zh) | 遥控器绑定的处理方法、装置和设备 | |
WO2017113842A1 (zh) | 控制智能设备的方法及装置 | |
WO2016206293A1 (zh) | 运营商网络的接入方法和装置 | |
JP6374517B2 (ja) | 権限検証方法および装置 | |
KR102377724B1 (ko) | 기기의 네트워크 구성 방법, 장치 및 매체 | |
WO2016155306A1 (zh) | 网络接入方法及装置 | |
WO2017036039A1 (zh) | 远程协助方法和客户端 | |
WO2017035988A1 (zh) | 确定用户设备控制权限的方法、装置及终端设备 | |
WO2017071074A1 (zh) | 建立连接的方法及装置 | |
JP2017510861A (ja) | デバイスバインドの方法および装置 | |
JP6422997B2 (ja) | ビジネスプロセス実行方法、装置、システム、プログラム及び記録媒体 | |
KR101684814B1 (ko) | Wi-fi 네트워크 접속 방법, 장치, 프로그램 및 기록매체 | |
WO2015196665A1 (zh) | 绑定账号与令牌密钥的方法、装置 | |
WO2017008394A1 (zh) | 一种下载控制程序的方法及装置 | |
US9667424B2 (en) | Methods and apparatuses for binding token key to account | |
CN106331780B (zh) | 授权直播方法、装置、设备及系统 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
ENP | Entry into the national phase |
Ref document number: 20157036252 Country of ref document: KR Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 2017505704 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: MX/A/2016/001549 Country of ref document: MX |
|
ENP | Entry into the national phase |
Ref document number: 2016111615 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: 112016006057 Country of ref document: BR |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 15885236 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 112016006057 Country of ref document: BR Kind code of ref document: A2 Effective date: 20160318 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 15885236 Country of ref document: EP Kind code of ref document: A1 |