WO2023273458A1 - 设备控制方法及装置 - Google Patents

设备控制方法及装置 Download PDF

Info

Publication number
WO2023273458A1
WO2023273458A1 PCT/CN2022/084073 CN2022084073W WO2023273458A1 WO 2023273458 A1 WO2023273458 A1 WO 2023273458A1 CN 2022084073 W CN2022084073 W CN 2022084073W WO 2023273458 A1 WO2023273458 A1 WO 2023273458A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
information
control
speaker
control key
Prior art date
Application number
PCT/CN2022/084073
Other languages
English (en)
French (fr)
Inventor
甘璐
时锐
潘适然
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP22831289.8A priority Critical patent/EP4336801A1/en
Publication of WO2023273458A1 publication Critical patent/WO2023273458A1/zh

Links

Images

Classifications

    • 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/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2803—Home automation networks
    • H04L12/2816—Controlling appliance services of a home automation network by calling their functionalities
    • 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
    • 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/06—Network architectures or network communication protocols for network security for supporting key management in a packet data network
    • H04L63/062—Network architectures or network communication protocols for network security for supporting key management in a packet data network for key distribution, e.g. centrally by trusted party
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • 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/72415—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 for remote control of appliances
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/04—Key management, e.g. using generic bootstrapping architecture [GBA]
    • H04W12/043—Key management, e.g. using generic bootstrapping architecture [GBA] using a trusted network node as an anchor
    • H04W12/0431—Key distribution or pre-distribution; Key agreement
    • 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
    • H04W12/55—Secure pairing of devices involving three or more devices, e.g. group pairing
    • 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/72469—User interfaces specially adapted for cordless or mobile telephones for operating the device by selecting functions from two or more displayed items, e.g. menus or icons

Definitions

  • the present application relates to the field of the Internet of Things, and in particular to a device control method and device.
  • IoT Internet of things
  • a certain device such as the first terminal
  • it may request the cloud to distribute a corresponding key (such as the first key), so that the first terminal uses the first key to control the IoT device.
  • the first terminal wants to authorize the control right of the IoT device to other devices, such as a second terminal whose cloud account is different from that of the first terminal
  • the first terminal can request the cloud to assign a corresponding key to the second terminal (such as the second key), so that the second terminal can use the second key to control the IoT device, thereby realizing the authorization of the control right.
  • the IoT device when the IoT device is connected to the second terminal but not connected to other devices (such as the first terminal or the cloud), if the first terminal cancels the authorization, that is, the second terminal no longer has the right to control the IoT device, but the second terminal However, if the connection with the IoT device is not disconnected, the IoT device will be hijacked by the second terminal.
  • other devices such as the first terminal or the cloud
  • Embodiments of the present application provide a device control method and device, so as to prevent the IoT device from being hijacked by the second terminal when the second terminal does not have the right to control the IoT device.
  • a device control method includes: the first device sends first information to the second device, and then, if the first device determines that the second device has not obtained the first control key, disconnecting from the second device. Wherein, the first device has been bound to the third device, and the first information is used to notify the second device to obtain the first control key, and the first control key is used for the second device to establish a session with the first device.
  • the first device may initiate a control right check to the second device, that is, send the first information to instruct the second device to obtain the latest control key ( as the first control key).
  • the first device may disconnect from the second device, so as to prevent the first device from being hijacked by the second device.
  • the method described in the first aspect may further include: the first device receives the second information from the third device, and thus according to the second Information, bind the third device.
  • the second information may be used to indicate that the first device needs to bind the third device. In this way, the first device can accurately bind the device to be bound, such as the third device, according to the second information, so as to avoid wrong binding.
  • the binding of the third device by the first device according to the second information may include: the first device determines, according to the second information, that no corresponding relationship with the first device has been established, so as to establish the first device and the third device.
  • the third device is bound.
  • the third device is the first device bound to the first device, that is, the first device that has the control right (or master control right) of the first device.
  • the first device can initiate a control verification to other devices based on the master control rights of the third device instead of initiating a control verification to the third device , so as to avoid mischecking.
  • the second information may include: the identifier of the first device, the identifier of the first user, and the second control key, where the first user is the user corresponding to the third device, and the correspondence relationship of the first device is the first The corresponding relationship between the device ID and the user ID, the first corresponding relationship is the corresponding relationship between the first device ID and the first user ID, and the second control key is used for the third device to establish a session with the first device.
  • the binding of the first device to the third device is the identification of the first user corresponding to the third device (such as the account of the first user). In this case, if the first user uses different devices to log in to the same account, he can still control the first device through the binding relationship of the first user, without the need for the first user to re-register and re-bind, which can improve user experience experience.
  • the method according to the first aspect may further include: the first device receives third information from the second device. Wherein, the third information is used for the second device to request to control the first device.
  • the third information may include: an identifier of the second user and an identifier of the first device, and the second user is a user corresponding to the second device.
  • the first device may determine that the identifier of the second user corresponding to the identifier of the first device in the third information is different from the identifier of the first user corresponding to the identifier of the first device in the first correspondence, thereby determining that the second device is not
  • the first device that has the control right of the first device, and then determines to initiate a control right check to the second device (such as sending the first information to the second device), instead of initiating a control right check to other devices, so that mistakes can be avoided. check.
  • the first information may include: a check value, and the check value may be used to determine the first control key.
  • the first control key is determined according to the check value, the second control key, and the identity of the second user.
  • the second control key is used by the third device to establish a session with the first device, and the second user is a user corresponding to the second device. It can be seen that since the second control key is stored locally on the first device, and the first device does not send the second control key to the second device, the second device cannot determine the first control key by itself, thereby avoiding In the case that the second device has no control right, the first device is hijacked by determining the first control key by itself.
  • a device control method includes: the second device receives first information from the first device, and sends fourth information to a fourth device.
  • the first information is used to notify the second device to obtain the first control key
  • the first control key is used by the second device to establish a session with the first device.
  • the fourth information is used to request the fourth device to determine the first control key.
  • the second device since the second device cannot determine the first control key by itself, it can only request the fourth device to determine the first control key, thereby avoiding hijack the first device by self-determining the first control key without authorization.
  • the first information may include: a check value, where the check value is used by the fourth device to determine the first control key.
  • the fourth information may include: an identifier of the first device, an identifier of the second user, and a check value.
  • the second user is a user corresponding to the second device. It should be understood that, in combination with the second aspect and the method described in the following fourth aspect, it can be known that, in the case where the fourth device saves the above-mentioned first correspondence, the fourth device can determine that the identifier of the first device in the fourth information corresponds to The identifier of the second user is different from the identifier of the first user corresponding to the identifier of the first device in the first correspondence, so that it is determined that the second user is not the first device that has the control right of the first device.
  • the fourth device can further determine whether the second user has the control right of the first device, or whether the first user cancels the authorization of the control right of the first device, so as to determine whether to generate the second control key, so as to avoid generating the second control key by mistake, for example, if the first device cancels authorization, the second control key is still generated.
  • the method described in the second aspect may further include: the second device receives the first control key from the fourth device, and sends the first control key to the first device The first control key is used to realize that the second device can continue to control the first device when it has the control right of the first device.
  • the second device before the second device receives the first information from the first device, the second device sends the third information to the first device.
  • the third information is used for the second device to request to control the first device.
  • the third information may include: an identifier of the second user and an identifier of the first device, and the second user is a user corresponding to the second device.
  • a device control method includes: the third device determines a second control key to send second information to the first device, wherein the second control key is used by the third device to establish a session with the first device, and is also used by the second A device determines a first control key, and the first control key is used by devices other than the third device to establish a session with the first device.
  • the second information includes the second control key, and the second information is used to instruct the first device to bind the third device.
  • the second information instructs the first device to bind the third device, so that the third device can become the first device to be bound to the first device, and also the first device to own the first device.
  • the device that controls the device.
  • the first device can initiate a control verification to the second device according to the binding relationship between the first device and the third device, that is, notify
  • the second device acquires the latest control key (such as the first control key).
  • the first device can use the first control key to verify whether the second device has obtained the first control key, thereby determining the second control key. Whether the device still has the control right of the first device. In this way, if the first device determines that the second device does not have the control right of the first device, it disconnects the connection with the second device, thereby avoiding being hijacked by the second device.
  • the second information may further include: an identifier of the third device and an identifier of the first user.
  • the method described in the third aspect may further include: the third device sends fifth information to the fourth device.
  • the fifth information is used to instruct the third device to authorize the control right to the second device, and the control right is the control right of the first device, so that the fourth device can subsequently determine the second device, or the second device corresponding to the second device.
  • the user the device having the control right of the first device, determines the first control key for the second device, so that the second device can continue to control the first device when it has the control right of the first device.
  • the method described in the third aspect may further include: the third device sends sixth information to the fourth device.
  • the sixth information is used to instruct the third device to cancel authorization of the control right of the first device to the second device.
  • the fourth device can subsequently determine that the second device does not have the right to control the first device based on the sixth information, and thus does not determine the first control key for the second device, so that the second device cannot continue to control the first device, avoiding the second device.
  • the second device hijacks the first device.
  • a device control method may include: the fourth device receives fourth information from the second device, thereby parsing the fourth information. Wherein, the fourth information is used to request the fourth device to determine the first control key, the first control key is used by the second device to establish a session with the first device, and the first device has been bound to the third device.
  • the method described in the fourth aspect may further include: if the fourth device determines that the second device has the control right of the first device, then according to the fourth information , determine the first control key, and send the first control key to the second device.
  • the fourth information may include the identifier of the first device, the identifier of the second user, and a check value
  • the first control key is determined according to the check value, the second control key, and the identifier of the second user
  • the second The second control key is used by the third device to establish a session with the first device, and the second user is a user corresponding to the second device.
  • the second device having the control right of the first device may refer to: the first device has been bound to the second device.
  • the method in the fourth aspect may further include: the fourth device receives fifth information from the third device, and according to the fifth information, Bind the first device with the second device.
  • the fifth information is used to instruct the third device to authorize the control right of the first device to the second device.
  • the binding of the first device and the second device by the fourth device according to the fifth information may include: the fourth device determines the second corresponding relationship between the first device and the second device according to the fifth information.
  • the second correspondence is used to indicate that the identifier of the first device corresponds to the identifier of the second user.
  • the binding of the first device to the second device is the identification of the first user corresponding to the second device (such as the account of the second user). In this case, if the second user uses a different device to log in to the same account, he can still control the first device through the binding relationship of the second user without re-authorization by the first user, thereby improving the user experience.
  • the method described in the fourth aspect may further include: if the fourth device determines that the second device does not have the control right of the first device, sending the second device Send the seventh message.
  • the seventh information is used to indicate that the second device does not have the control right of the first device.
  • the fact that the second device does not have the control right of the first device may refer to: the first device is not bound to the second device.
  • the method described in the fourth aspect may further include: the fourth device receives sixth information from the third device, and according to the sixth information to unbind the first device from the second device.
  • the sixth information is used to instruct the third device to cancel authorization of the control right of the first device to the second device.
  • the unbinding of the first device and the second device by the fourth device according to the sixth information may include: the fourth device deletes the second corresponding relationship between the first device and the second device according to the sixth information.
  • the second correspondence is used to indicate that the identifier of the first device corresponds to the identifier of the second user, and the second user is the user corresponding to the second device.
  • an electronic device in a fifth aspect, includes: one or more processors, a memory, and a communication module. Wherein, one or more computer programs are stored in the memory, and the one or more computer programs include instructions. When the instructions are executed by the electronic device, the electronic device executes the method described in any one of the first to fourth aspects above. method.
  • an Internet of Things system includes one or more electronic devices.
  • the electronic device is configured to execute the method described in any one of the above-mentioned first aspect to the fourth aspect.
  • a computer-readable storage medium including: a computer program or an instruction; when the computer program or instruction is run on a computer, the computer is made to execute any one of the above-mentioned first to fourth aspects. described method.
  • a computer program product including a computer program or an instruction, and when the computer program or instruction is run on a computer, the computer executes the method described in any one of the first to fourth aspects above .
  • a chip system is provided.
  • the chip system is applied to an electronic device including a memory and a communication module;
  • the chip system includes one or more interface circuits and one or more processors;
  • the interface circuit and the processor are interconnected through lines;
  • the interface circuit is used to receive data from the memory of the electronic device Signals, and send signals to the processor, the signals include computer instructions stored in the memory; when the processor executes the computer instructions, the electronic device executes the method described in any one of the first to fourth aspects above.
  • FIG. 1 is a schematic diagram of the architecture of the Internet of Things system provided by the embodiment of the present application.
  • FIG. 2 is a schematic structural diagram of a terminal device (such as a mobile phone) provided by an embodiment of the present application;
  • FIG. 3 is a schematic structural diagram of an IoT device (such as a speaker) provided in an embodiment of the present application;
  • FIG. 4 is an application scenario diagram of a device control method provided in an embodiment of the present application.
  • FIG. 5 is the first interactive interface diagram provided by the embodiment of the present application.
  • Figure 6A is the second interactive interface diagram provided by the embodiment of the present application.
  • Figure 6B is the third interactive interface provided by the embodiment of the present application.
  • Figure 6C is the fourth interactive interface provided by the embodiment of the present application.
  • FIG. 7 is the fifth interactive interface diagram provided by the embodiment of the present application.
  • Figure 8 is the sixth interactive interface provided by the embodiment of the present application.
  • FIG. 9 is the seventh interactive interface diagram provided by the embodiment of the present application.
  • FIG. 10 is the eighth interactive interface provided by the embodiment of the present application.
  • Fig. 11 is the interactive interface Fig. 9 provided by the embodiment of the present application.
  • Figure 12 is the tenth interactive interface diagram provided by the embodiment of the present application.
  • FIG. 13 is a first schematic flowchart of a device control method provided in an embodiment of the present application.
  • FIG. 14 is the second schematic flow diagram of the device control method provided by the embodiment of the present application.
  • FIG. 15 is a schematic structural diagram of an electronic device provided by an embodiment of the present application.
  • a physical network system may generally include: a first terminal, a second terminal, an IoT device, and a cloud.
  • the first terminal can be bound to the IoT device and request the cloud to distribute the corresponding key (such as the first key), so that the first terminal can use the first key to establish A session between the first terminal and the IoT device, so as to control the IoT device through the session.
  • the corresponding key such as the first key
  • the first terminal wants to authorize the control right of the IoT device to other devices, for example, to a second terminal logged in with a cloud account different from the cloud account of the first terminal
  • the first terminal can instruct the second terminal to Bind the IoT device, and request the cloud or the first terminal to assign the corresponding key (such as the second key) to the second terminal directly, so that the second terminal can use the second key to establish a connection between the second terminal and the IoT device. Session to control the IoT device through the session, so as to realize the authorization of the control right.
  • the second terminal After the second terminal is authorized to control the IoT device, the second terminal can connect to and control the IoT device. However, if the IoT device is connected to the second terminal and controlled by the second device, if the first terminal wants to cancel the authorization, because the IoT device is only connected to the second terminal (for example, the IoT device is a Bluetooth device and does not have The ability to communicate directly with the cloud), the IoT device can only communicate with the second terminal, and can only receive the control commands of the second terminal, which will cause the first terminal to fail to instruct the IoT device to disconnect from the second terminal, then the second The second terminal can always maintain the connection with the IoT device and control the IoT device, thus causing the IoT device to be hijacked by the second terminal.
  • the IoT device is a Bluetooth device and does not have The ability to communicate directly with the cloud
  • the only way to disconnect the IoT device from the second terminal is through manual notification.
  • the user of the first terminal manually notifies (sends a text message, makes a phone call, or informs in person, etc.) the user of the second terminal to disconnect the second terminal from the IoT device, so that the user of the second terminal executes disconnection of the second terminal.
  • the hijacking of the IoT device can only be released by a user operation of connecting to the IoT device, or by performing a user operation of deleting the IoT device from its own device list by the user of the second terminal.
  • the IoT device will still be hijacked by the second terminal.
  • whether the first terminal can successfully cancel the authorization of the control right of the IoT device depends on the second terminal. There is still no method for the first terminal to actively "take back" the control right of the IoT device.
  • Scenario 1 the smart door lock is hijacked by the tenant.
  • the first terminal is the landlord's mobile phone
  • the second terminal is the tenant's mobile phone
  • the IoT device is the smart door lock of the rental house.
  • the landlord can authorize the control of the smart door lock to the tenant through the mobile phone during the tenant's living in the rented house, so that the tenant can control the opening and closing of the smart door lock through the mobile phone to enter the rental house.
  • the tenant's residence period expires, the tenant can still control the opening and closing of the smart door lock through the mobile phone because the landlord cannot cancel the smart door lock control right authorized to the tenant through the mobile phone, so that the tenant can still enter the rental house freely. This will cause inconvenience to the landlord's life, and even bring potential safety hazards.
  • the first terminal is the mobile phone of user 1
  • the second terminal is the mobile phone of user 2
  • the IoT device is the headset of user 1.
  • user 1 can authorize the control right of the headset to user 2 through the mobile phone, so that user 2 can use the headset.
  • the headset of user 1 can only be controlled by the mobile phone of user 2, then user 1 cannot cancel the authorization through the mobile phone at this time Give user 2 the right to control the headset so that user 2 can continue to use the headset, thereby causing inconvenience to user 1.
  • the embodiments of the present application provide a device control method, system, electronic device, and device, which can enable the first terminal in the above scenario to actively "take back" the control right to the IoT device, effectively avoiding the hijacking of the IoT device.
  • FIG. 1 is a schematic diagram of an architecture of an Internet of Things system 100 in an embodiment of the present application.
  • the device control method provided in the embodiment of the present application can be applied to the Internet of Things system 100 shown in FIG. 1 .
  • the IoT system 100 may include: one or more electronic devices, such as a first device 101 , a second device 102 , a third device 103 and a fourth device 104 .
  • the first device 101, the second device 102, and the third device 103 can be terminal devices, and the terminal devices can specifically be mobile phones, tablet computers, TVs (also called smart screens, large-screen devices, etc.), notebook computers, Ultra-mobile personal computer (ultra-mobile personal computer, UMPC), handheld computer, netbook, personal digital assistant (personal digital assistant, PDA), wearable electronic equipment, vehicle-mounted equipment (also called car machine), augmented reality (augmented reality (AR) devices, virtual reality (VR) devices, etc.; or, IoT devices such as headphones, TVs, speakers, door locks, refrigerators, ovens, microwave ovens, air conditioners, sweeping robots, smart lights, cameras etc. There is no limit to this.
  • the fourth device 104 can be a network device, or a cloud device or a cloud platform (hereinafter referred to as a cloud platform), specifically a server (server), such as a database server (database server), an application server (application server), etc., and can It is not limited to a single server or a cluster of servers.
  • the first device 101 is an IoT device
  • the second device 102 and the third device 103 are terminal devices
  • the fourth device 104 is a cloud platform.
  • Communication with the second device 102 and the third device 103 may be in a wired manner, such as using a universal serial bus (universal serial bus, USB) to establish a wired connection, or may also communicate in a wireless manner, such as through a cellular Communication, Bluetooth low energy (bluetooth low energy, BLE), wireless fidelity (wireless fidelity, Wi-Fi), near field communication (near field communication, NFC), voice over Internet protocol (voice over Internet protocol, VoIP) ), support network slicing architecture communication protocols to establish wireless connections.
  • a wired manner such as using a universal serial bus (universal serial bus, USB) to establish a wired connection
  • USB universal serial bus
  • wireless manner such as through a cellular Communication, Bluetooth low energy (bluetooth low energy, BLE), wireless fidelity (wireless fidelity, Wi-Fi), near field communication (near field communication, NFC), voice over Internet protocol (voice over Internet protocol, VoIP) ), support network slicing architecture communication protocols to establish wireless connections.
  • BLE Bluetooth low
  • a wired or wireless communication connection may be established between the first device 101 and the fourth device 104, or a wired or wireless communication connection may not be established, which is not limited;
  • the device control method is especially applicable to the scenario where no wired or wireless communication connection is established between the first device 101 and the fourth device 104; A scenario in which a wired or wireless communication connection is established between devices 104 .
  • the third device 103 wants to control the first device 101, and the first device 101 is not currently bound to other devices, or is not controlled by other devices, then the third device 103, In other words, the first user (that is, the first user corresponding to the third device 103, such as the user of the third device 103) can be bound with the first device 101 to have the control right of the first device 101, thereby controlling the first device 101, such as controlling speakers to play audio, TV to play video, smart door locks to open and close, and so on.
  • the third device 103 can be the first device bound to the first device 101, that is, as the first device 101 the main control device.
  • the control right of the first device 101 owned by the third device 103 can be the main control right, that is, the third device 103 can not only control the first device 101, but also authorize the control right of the first device 101 to other devices, so that Other devices can also control the first device 101 .
  • the third device may authorize the control right of the first device 101 to the second device 102, or the second user (that is, the user corresponding to the second device 102, such as the user of the second device 102) through the cloud platform 104.
  • the second device 102 can also be bound with the first device 101 to have the right to control the first device 101 , thereby controlling the first device 101 .
  • the account of the second device 102 (such as the account on the cloud platform) is different from the account of the third device 103 (such as the account on the cloud platform).
  • the second device 102 can be used as the first device that is not the first bound device of the first device 101, that is, as the first device 101 to be bound.
  • the control right of the first device 101 owned by the second device 102 may be a slave control right, that is, the second device 102 can control the first device 101, but cannot authorize the control right of the first device 101 to other devices.
  • the second device 102 controls the first device 101, since the first device 101 determines that the second device 102 has the slave control right, not the master control right, it can periodically initiate a control right check to the second device 102 , such as instructing the second device 102 to obtain the latest control key.
  • the third device 103 does not cancel the authorization
  • the second device 102 can complete the verification of the control right through the cloud platform 104 , such as obtaining the latest control key from the cloud platform 104, so as to continue to control the second device 102 using the latest control key.
  • the third device 103 cancels the authorization, such as canceling the authorization of the control right of the first device 101 to the second device 102 on the cloud platform 104
  • the second device 102 cannot complete the verification of the control right through the cloud platform 104, such as Unable to obtain the latest control key from the cloud platform 104 .
  • the first device 101 will disconnect the communication connection with the second device 102 because the second device 102 has not obtained the latest control key, thereby preventing the first device 101 from being hijacked by the second device 102 .
  • the above-mentioned first device 101 is bound to the third device 103, which may be bound to the first user corresponding to the third device 103, such as establishing the identity of the first device 101 and the identity of the first user, or the first Correspondence between user accounts.
  • the above-mentioned third device 103 has the control right of the first device 101 , which can be considered as the first user has the control right of the first device 101 .
  • the first user logs in to the same account using different devices, he can still control the first device through the binding relationship of the first user, without the need for the first user to re-register and re-select the binding, which can improve the user's security. Use experience.
  • the above-mentioned first device 101 is bound to the second device 102, or it can be bound to the second user corresponding to the second device 102, such as establishing the identity of the first device 101 and the identity of the second user, or the second Correspondence between user accounts.
  • the above-mentioned second device 102 has the control right of the first device 101 , and it can also be considered that the second user has the control right of the first device 101 .
  • the second user uses a different device to log in to the same account, he can still control the first device through the binding relationship of the second user without re-authorization by the first user, thereby improving user experience.
  • the user with the master control right (such as the first user) can be unique, if there is only one, but the user with the slave control right (such as the second user) can have multiple For example, there can be one or more, so that the user with the master control right can conduct unified management of the control rights of the user with the slave control right, such as authorization and deauthorization, so that management efficiency can be improved.
  • FIG. 2 is a schematic structural diagram of a terminal device (such as a mobile phone) provided by an embodiment of the present application.
  • the second device 102 may include: a processor 210, an external memory interface 220, an internal memory 221, a universal serial bus (universal serial bus, USB) interface 230, an antenna 1, an antenna 2, and a mobile communication module 250 , wireless communication module 260, audio module 270, speaker 270A, receiver 270B, microphone 270C, earphone interface 270D, sensor module 280, etc.
  • the processor 210 may include: one or more processing units, for example, the processor 210 may include: an application processor (application processor, AP), a modem processor, a graphics processing unit (graphics processing unit, GPU), an image signal Processor (image signal processor, ISP), controller, memory, video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural network processor (neural-network processing unit, NPU) and so on. Wherein, different processing units may be independent devices, or may be integrated in one or more processors.
  • an application processor application processor, AP
  • modem processor graphics processing unit
  • graphics processing unit graphics processing unit
  • ISP image signal Processor
  • controller memory
  • video codec digital signal processor
  • DSP digital signal processor
  • baseband processor baseband processor
  • neural network processor neural-network processing unit
  • a memory may also be provided in the processor 210 for storing instructions and data.
  • the memory in processor 210 is a cache memory.
  • the memory may hold instructions or data that the processor 210 has just used or recycled. If the processor 210 needs to use the instruction or data again, it can be called directly from the memory. Repeated access is avoided, and the waiting time of the processor 210 is reduced, thereby improving the efficiency of the system.
  • the wireless communication function of the terminal device can be realized by the antenna 1, the antenna 2, the mobile communication module 250, the wireless communication module 260, the modem processor and the baseband processor.
  • Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals.
  • Each antenna in an end device can be used to cover single or multiple communication frequency bands. Different antennas can also be multiplexed to improve the utilization of the antennas.
  • Antenna 1 can be multiplexed as a diversity antenna of a wireless local area network.
  • the antenna may be used in conjunction with a tuning switch.
  • the mobile communication module 250 can provide wireless communication solutions including 2G/3G/4G/5G applied on terminal equipment.
  • the mobile communication module 250 may include: at least one filter, a switch, a power amplifier, a low noise amplifier (low noise amplifier, LNA) and the like.
  • the mobile communication module 250 can receive electromagnetic waves through the antenna 1, filter and amplify the received electromagnetic waves, and send them to the modem processor for demodulation.
  • the mobile communication module 250 can also amplify the signal modulated by the modem processor, convert it into electromagnetic wave and radiate it through the antenna 1 .
  • at least part of the functional modules of the mobile communication module 250 may be set in the processor 210 .
  • at least part of the functional modules of the mobile communication module 250 and at least part of the modules of the processor 210 may be set in the same device.
  • the wireless communication module 260 can provide applications on the terminal device including: wireless local area network (wireless local area networks, WLAN), such as Wi-Fi network, BLE, global navigation satellite system (global navigation satellite system, GNSS), frequency modulation (frequency modulation) , FM), NFC, infrared technology (infrared, IR) and other wireless communication solutions.
  • the wireless communication module 260 may be one or more devices integrating at least one communication processing module.
  • the wireless communication module 260 receives electromagnetic waves via the antenna 2 , frequency-modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 210 .
  • the wireless communication module 260 can also receive the signal to be sent from the processor 210 , frequency-modulate it, amplify it, and convert it into electromagnetic waves through the antenna 2 to radiate out.
  • the antenna 1 of the terminal device is coupled to the mobile communication module 250, and the antenna 2 is coupled to the wireless communication module 260, so that the terminal device can communicate with the network and other devices through wireless communication technology.
  • the wireless communication technology may include: GSM, GPRS, CDMA, WCDMA, TD-SCDMA, LTE, BT, GNSS, WLAN, NFC, FM, and/or IR technology, etc.
  • the GNSS may include: global positioning system (global positioning system, GPS), global navigation satellite system (global navigation satellite system, GLONASS), Beidou satellite navigation system (beidou navigation satellite system, BDS), quasi-zenith satellite system (quasi -zenith satellite system (QZSS) and/or satellite based augmentation systems (SBAS).
  • global positioning system global positioning system, GPS
  • global navigation satellite system global navigation satellite system
  • GLONASS global navigation satellite system
  • Beidou satellite navigation system beidou navigation satellite system
  • BDS Beidou navigation satellite system
  • QZSS quasi-zenith satellite system
  • SBAS satellite based augmentation systems
  • the terminal device realizes the display function through the GPU, the display screen 294, and the application processor.
  • the GPU is a microprocessor for image processing, and is connected to the display screen 294 and the application processor. GPUs are used to perform mathematical and geometric calculations for graphics rendering.
  • Processor 210 may include one or more GPUs that execute program instructions to generate or change display information.
  • the display screen 294 is used to display images, videos and the like.
  • the display screen 294 includes: a display panel.
  • the display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active matrix organic light emitting diode or an active matrix organic light emitting diode (active-matrix organic light emitting diode, AMOLED), flexible light-emitting diode (flex light-emitting diode, FLED), Miniled, MicroLed, Micro-oLed, quantum dot light emitting diodes (quantum dot light emitting diodes, QLED), etc.
  • the terminal device may include: 1 or N display screens 194, where N is a positive integer greater than 1.
  • the terminal device can realize the shooting function through ISP, camera 293 , video codec, GPU, display screen 294 and application processor.
  • the ISP is used for processing the data fed back by the camera 293 .
  • the light is transmitted to the photosensitive element of the camera through the lens, and the light signal is converted into an electrical signal, and the photosensitive element of the camera transmits the electrical signal to the ISP for processing, and converts it into an image visible to the naked eye.
  • ISP can also perform algorithm optimization on image noise, brightness, and skin color.
  • ISP can also optimize the exposure, color temperature and other parameters of the shooting scene.
  • the ISP may be located in the camera 293 .
  • Camera 293 is used to capture still images or video.
  • the object generates an optical image through the lens and projects it to the photosensitive element.
  • the photosensitive element may be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor.
  • CMOS complementary metal-oxide-semiconductor
  • the photosensitive element converts the light signal into an electrical signal, and then transmits the electrical signal to the ISP to convert it into a digital image signal.
  • the ISP outputs the digital image signal to the DSP for processing.
  • DSP converts digital image signals into standard RGB, YUV and other image signals.
  • the terminal device may include: 1 or N cameras 293, where N is a positive integer greater than 1.
  • Digital signal processors are used to process digital signals. In addition to digital image signals, they can also process other digital signals. For example, when the terminal device is selecting a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy.
  • Video codecs are used to compress or decompress digital video.
  • An end device can support one or more video codecs.
  • the terminal device can play or record video in various encoding formats, for example: moving picture experts group (moving picture experts group, MPEG) 1, MPEG2, MPEG3, MPEG4, etc.
  • the external memory interface 220 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the terminal device.
  • the external memory card communicates with the processor 210 through the external memory interface 220 to implement a data storage function. Such as saving music, video and other files in the external memory card.
  • the internal memory 221 may be used to store computer-executable program codes including instructions.
  • the processor 210 executes various functional applications and data processing of the terminal device by executing instructions stored in the internal memory 221 .
  • the internal memory 221 may include: a program storage area and a data storage area.
  • the storage program area can store an operating system, at least one application program required by a function (such as a sound playing function, an image playing function, etc.) and the like.
  • the storage data area can store data (such as audio data, phone book, etc.) created during the use of the terminal device.
  • the internal memory 221 may include: a high-speed random access memory, and may also include: a non-volatile memory, such as at least one magnetic disk storage device, flash memory device, universal flash memory (universal flash storage, UFS) and the like.
  • a non-volatile memory such as at least one magnetic disk storage device, flash memory device, universal flash memory (universal flash storage, UFS) and the like.
  • the terminal device can realize the audio function through the audio module 270, the speaker 270A, the receiver 270B, the microphone 270C, the earphone interface 270D, and the application processor. Such as music playback, recording, etc.
  • the audio module 270 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signal.
  • the audio module 270 may also be used to encode and decode audio signals.
  • the audio module 270 can be set in the processor 210 , or some functional modules of the audio module 270 can be set in the processor 210 .
  • Speaker 270A also referred to as a "horn" is used to convert audio electrical signals into sound signals.
  • the terminal device can listen to music through the speaker 270A, or listen to hands-free calls.
  • Receiver 270B also called “earpiece” is used to convert audio electrical signals into audio signals.
  • the terminal device answers a call or voice information, it can listen to the voice by bringing the receiver 270B close to the human ear.
  • the microphone 270C also called “microphone” or “microphone” is used to convert sound signals into electrical signals.
  • the user can make a sound by approaching the microphone 270C with a human mouth, and input the sound signal to the microphone 270C.
  • the terminal device may be provided with at least one microphone 270C.
  • the terminal device can be provided with two microphones 270C, which can also implement a noise reduction function in addition to collecting sound signals.
  • the terminal device can also be provided with three, four or more microphones 270C to realize the collection of sound signals, noise reduction, identification of sound sources, and realization of directional recording functions, etc.
  • the earphone interface 270D is used for connecting wired earphones.
  • the earphone interface 270D can be a USB interface 230, or a 3.5mm open mobile terminal platform (OMTP) standard interface, or a cellular telecommunications industry association of the USA (CTIA) standard interface.
  • OMTP open mobile terminal platform
  • CTIA cellular telecommunications industry association of the USA
  • the sensor module 280 may include: a pressure sensor, a gyroscope sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a distance sensor, a proximity light sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, and the like.
  • the terminal device may also include: a charging management module, a power management module, a battery, buttons, an indicator, and one or more SIM card interfaces, etc., which are not limited in this embodiment of the present application.
  • the structure shown in the embodiment of the present invention does not constitute a specific limitation on the terminal device.
  • the terminal device may include more or fewer components than shown in the figure, or combine certain components, or separate certain components, or arrange different components.
  • the illustrated components can be realized in hardware, software or a combination of software and hardware.
  • the connection of the devices described in the embodiments of the present application may be a direct connection, or may also be an indirect connection, such as a connection relayed by other devices, which is not limited.
  • the sending described in this embodiment of the present application may be direct sending, or may also be indirect sending, such as sending forwarded by other devices, which is not limited thereto.
  • FIG. 3 is a schematic structural diagram of an IoT device (such as a speaker) provided by an embodiment of the present application.
  • the IoT device may include: a processor 310 , a memory 320 , a wireless communication module 330 and a power supply 340 .
  • the memory 320 may be used to store application program codes, such as application program codes used for pairing and connection between the IoT device and the aforementioned mobile phone.
  • the processor 310 may control and execute the above-mentioned application program code, so as to realize the function of checking the control right in the embodiment of the present application.
  • An address for uniquely identifying the IoT device may also be stored in the memory 320 .
  • the memory 320 may also store connection data of devices that have been successfully paired with the IoT device before.
  • the connection data may be an address of a device that has been successfully paired with the IoT device. Based on the connection data, the IoT device can be automatically paired with the device without having to configure the connection with it, such as performing legality verification.
  • the foregoing address may be a media access control (media access control, MAC) address.
  • the wireless communication module 330 is used to support short-distance data exchange between the IoT device and various devices, such as the above-mentioned mobile phone.
  • the wireless communication module 340 can be a transceiver.
  • the IoT device can establish a wireless connection with the above-mentioned mobile phone through the transceiver, such as Bluetooth, Wi-Fi, NFC connection, etc., to realize short-distance data exchange between the two.
  • the power supply 340 may be used to supply power to various components included in the IoT device.
  • the power source 340 may be a battery, such as a rechargeable battery.
  • the structure shown in the embodiment of the present application does not constitute a specific limitation on the IoT device.
  • the IoT device is a different type of device, it may have more or fewer components than shown in FIG. 3 , may combine two or more components, or may have a different configuration of components.
  • the IoT device is a speaker
  • the IoT device can also include: speakers, microphones, etc.
  • the IoT device is a TV
  • the IoT device can also include: display screens, speakers, etc.
  • the IoT device is an air conditioner
  • the IoT device can also include: compression Machines, condenser tubes, etc., are not limited to this.
  • the various components shown in Figure 3 may be implemented in hardware, software, or a combination of hardware and software including one or more signal processing or application specific integrated circuits.
  • FIG. 4 is a schematic diagram of an application scenario of a device control method provided in an embodiment of the present application.
  • Fig. 5-Fig. 12 are interactive interface diagrams provided by the embodiment of the present application.
  • the device control method provided by the embodiment of the present application will be described in detail below.
  • the user corresponding to mobile phone 1, or the user of mobile phone 1, is called “user A”
  • the user corresponding to mobile phone 2, or the user of mobile phone 2 is called “user B”.
  • the speaker 3 It is a new device, such as a device that user A has not controlled before, user A needs to bind speaker 3 through mobile phone 1 first, such as establishing user A's identity (identity document, ID), such as account ID, and the identity of speaker 3 corresponding relationship to obtain the control right of speaker 3.
  • the account identifier of user A may be an identifier assigned by the cloud platform to the registered account of user A after user A registers to the cloud platform.
  • the identifier of the speaker 3 may be an identifier assigned to the speaker 3 by the cloud platform when the speaker 3 is registered to the cloud platform. In this way, when user A is bound to speaker 3, user A can authorize the control right of speaker 3 to user B through mobile phone 1, so that user B can also control speaker 3 through mobile phone 2, which will be described in detail below.
  • the mobile phone 1 may display a main interface 501 .
  • the main interface 501 may be an interface displayed after the mobile phone 1 is turned on, but it is not limited thereto, and may also be other interfaces, such as a background interface, such as a negative screen.
  • the main interface 501 may include various applications (Applications, APPs) installed on the mobile phone 1, for example, may include the icons of the APPs carried by the mobile phone 1, such as clock, calendar, gallery, memo, application store, settings, music player, Calculator, sports and health, camera, phone, information, address book, smart life 502, etc.
  • it can also include third-party apps, such as WeChat, QQ, Alipay, online games, etc.
  • user A can click on the smart life 502 in the main interface 501 .
  • the mobile phone 1 can jump from the main interface 501 to the APP interface 503 of the smart life 502 (shown in (b) in FIG. 5 ).
  • "2 devices" can be used to indicate that user A has bound 2 devices, such as TV 4 and TV 5, and the icons of TV 4 and TV 5 can be displayed near “2 devices", as shown below, So that user A knows the specific type of the bound device.
  • Both "+” 504 and “User A's Home” 505 can be used to bind new devices and authorize the control rights of the bound devices to other devices, but the difference is that "+” 504 is implemented at the granularity of devices
  • "User A's Home” 505 implements the above functions at the granularity of groups, which will be introduced separately below.
  • the mobile phone 1 may display a secondary menu 601 near "+” 504 (shown in FIG. 6A ).
  • the secondary menu 601 may include: add device 602, authorize device and so on.
  • the adding device 602 can be used to bind a new device, and the authorizing device can be used to authorize the control right of the bound device to other users (for specific implementation, please refer to the related introductions in FIG. 9 and FIG. 10 below).
  • secondary menu 601 is only an exemplary implementation manner, and is not intended as a limitation.
  • mobile phone 1 can jump to a new interface from APP interface 503 in response to the operation of clicking "+" 504, such as the device addition/authorization interface, and the device addition/authorization interface also includes: the above-mentioned adding device 602, authorization devices, etc., in order to realize the functions of binding devices and authorizing control rights mentioned above.
  • mobile phone 1 can jump from APP interface 603 to device search interface 604 (shown in FIG. 6B ), on the other hand, mobile phone 1 can search nearby , if the speaker 3 is found, the icon 605 of the speaker 3 is displayed on the device search interface 604 .
  • mobile phone 1 can establish a binding relationship between user A and speaker 3, such as establishing a corresponding relationship between user A's logo and the logo of speaker 3, and on the other hand
  • the mobile phone 1 can jump back to the APP interface 606 from the device search interface 604 (as shown in FIG.
  • the icon in the APP interface 606 can be changed from the previous "2 devices” to "3 devices" to indicate that user A has bound 3 devices, such as the speaker 3.
  • TV 4 and TV 5 and the icon of speaker 3 can be newly displayed near the "3 devices, as shown below, so that user A can know the specific type of the newly bound device.
  • the mobile phone 1 can jump from the APP interface 503 to the group management interface 701 (shown in (a) in FIG. 7 ).
  • the group management interface 701 may include icons of each group, such as individual, living room 702, and bedroom.
  • the icon of each group can also display the number of devices in the group, such as 0 devices for individuals, 1 device for living room 702, and 1 device for bedrooms, so as to facilitate user management.
  • the living room management interface 703 may include: icons of devices in the living room 702, such as the TV 4, and may also include: newly added devices 704 and authorized devices.
  • the newly added device 602 can be used to bind a new device in the living room 702, and the authorized device can be used to authorize the control right of the bound device in the living room 702, such as the TV 4, to other users (for specific implementation, please refer to the following Please refer to the related introduction of Fig. 9 and Fig. 10).
  • the mobile phone 1 can jump from the living room management interface 703 to the device search interface 801 (shown in (a) in FIG. 8 ), and on the other hand on the mobile phone 1 can search for nearby devices, for example, the speaker 3 is found, so that the icon 802 of the speaker 3 is displayed on the device search interface 801 .
  • mobile phone 1 can establish a binding relationship between user A and speaker 3, such as the corresponding relationship between user A's logo and speaker 3 logo, and mobile phone 1 can also be accessed from The device search interface 801 jumps back to the APP interface 803 (as shown in (b) in FIG. 8 ).
  • the icon in the APP interface 803 can be changed from the previous "2 devices” to "3 devices" to indicate that user A has bound 3 devices, such as the living room Speaker 3 and TV 4 in the home, TV 5 in the bedroom, and the icon of speaker 3 can be added and displayed near “3 devices", as shown below, so that user A can know the specific type of the newly bound device.
  • the bound speaker 3 is an independent bound device. Does not belong to a certain group. If the speaker 3 is bound with the group as the granularity, the bound speaker 3 can belong to the corresponding group, such as the living room. In other words, users can choose a corresponding binding method according to actual needs.
  • the above-mentioned device granularity binding method can be used; if the user wants to control a certain group, such as group sharing, group playback, etc., the above-mentioned group granularity binding method can be used. set the way.
  • the cloud platform can determine that user A has the master control right of speaker 3 according to the binding relationship between user A and speaker 3, so as to assign the control key of speaker 3 to mobile phone 1, such as key 1.
  • the mobile phone 1 can send the key 1 and the binding relationship between user A and the speaker 3 to the speaker 3 .
  • the speaker 3 may determine that the user A has the control right of the speaker 3 according to the binding relationship between the user A and the speaker 3 .
  • the speaker 3 and the mobile phone 1 can use the key 1 to establish a session, so as to perform encrypted communication through the session, so as to realize encrypted control, so as to ensure the security of the control and avoid the theft of the control right.
  • the cloud platform can assign different control keys to different devices of the same user, so that the control keys used by each device are different from those used by other devices, so as not to interfere with each other, so as to further improve the security of encrypted communication. safety.
  • the cloud platform distributes key 1 to user A's mobile phone 1, and distributes key X to other devices of user A, such as mobile phone 3 (not shown in FIG. 4 ), and key 1 and key X are different.
  • the mobile phone 1 and the speaker 3 can use the key 1 to establish a session
  • the mobile phone 3 and the speaker 3 can use the key X to establish a session.
  • user A after user A is bound to the speaker 3, he can authorize the bound device, such as the control right of the speaker 3, to other users, such as user B.
  • the bound device such as the control right of the speaker 3
  • user B can grant the control right at the granularity of the device, or grant the control right at the granularity of the group, which will be introduced respectively below.
  • the device is authorized to control at a granular level:
  • the mobile phone 1 can display a secondary menu 901 near "+" 607 (shown in (a) in FIG. 9 ). Then, user A can click on the authorization device 902, and in response to this operation, the mobile phone 1 can jump from the APP interface 903 to the device authorization interface 904 (shown in (b) in FIG. 9 ).
  • the device authorization interface 904 may include icons of all bound devices of user A, such as the TV 4 in the living room, the TV 5 in the bedroom, and the ungrouped speakers 3 .
  • user A can select the corresponding device in the device authorization interface 904, such as selecting the corresponding device by long pressing or clicking.
  • a check mark can be displayed near the selected device, so that user A can cancel the selection to modify the wrongly selected device.
  • the icon of the selected device may also be displayed in a manner such as highlighting or shaking to show a difference.
  • user A may select a certain device, such as selecting the speaker 3 , or may select multiple devices, such as selecting the speaker 3 , the TV 4 and the TV 5 .
  • user A can click confirm authorization 905, and in response to this operation, mobile phone 1 can jump from device authorization interface 904 to user selection interface 1001 (shown in (a) in FIG. 10 ).
  • user A wants to cancel the authorization he can also click cancel authorization 907 , and in response to this operation, the mobile phone 1 can return from the device authorization interface 904 to the APP interface 903 .
  • the user selection interface 1001 may include icons of previously authorized users, such as the icon 1002 of user B, the icon of user C, and so on.
  • icons of previously authorized users such as the icon 1002 of user B, the icon of user C, and so on.
  • user A wants to authorize the control right of speaker 3 to user B, he can directly click on the icon 1002 of user B to realize the control right more conveniently, such as authorizing the control right of speaker 3 to a user who has been authorized before , such as user B.
  • the icons of users who have been authorized can also be sorted by authorization frequency, such as in order of authorization frequency from high to low, from top to bottom, so that user A can more conveniently select frequently authorized users to further improve user experience.
  • the user selection interface 1001 may further include a user input box 1003, so that user A can authorize the control right to an unauthorized user.
  • user A wants to authorize the control right of speaker 3 to an unauthorized user, such as user D, he can input the account number of user D in user input box 1003, and then click authorization 1004 to realize the control of speaker 3. Control is delegated to user D.
  • mobile phone 1 may directly authorize the control right of speaker 3 to the user corresponding to the mobile phone currently connected to mobile phone 1 .
  • the mobile phone 1 can directly authorize the control right of the speaker 3 to the user B.
  • the mobile phone 1 can display a prompt message of successful authorization on the current interface, such as the user selection interface 1001, such as that the speaker 3 has been authorized to user B, so that the user can know in time that the authorization of the control right is successful, so as to provide Subsequent cancellation of authorization by the user provides a basis for decision-making.
  • the mobile phone 1 can also jump from the user selection interface 1001 to the authorization management interface 1005 (shown in (b) in FIG. 10 ).
  • the authorization management interface 1005 may include: an icon of the user B, an icon of the device authorized to control, such as the icon of the speaker 3 , and deauthorization 1006 .
  • the mobile phone 1 can display a prompt message of the authorization failure on the current interface, such as the user selection interface 1001, such as the speaker 3 is not authorized successfully, so that the user can know in time and re-authorize.
  • the mobile phone 1 can jump from the group management interface 1101 to the living room management interface 1103 (shown in (b) in FIG. 11 ). Further, user A can select the icon of the corresponding device in the living room management interface 1103, such as selecting the corresponding device by long pressing the icon. Wherein, a check mark can be displayed near the selected device, so that user A can cancel the selection to modify the wrongly selected device. Alternatively, the icon of the selected device may also be displayed in a manner such as highlighting or shaking to show a difference.
  • user A may select a certain device, such as selecting the speaker 3 , or may select multiple devices, such as selecting the speaker 3 and the TV 4 .
  • a certain device such as selecting the speaker 3
  • multiple devices such as selecting the speaker 3 and the TV 4 .
  • user A can click on the authorized device 1104, and in response to this operation, the mobile phone 1 can jump from the living room management interface 1103 to the user selection interface 1201 (shown in (a) in FIG. 12 ).
  • the user selection interface 1201 may include icons of all users in the user group corresponding to "user A's home", such as the icon 1202 of user B, the icon of user C, and so on.
  • user A wants to authorize the control right of speaker 3 to user B, he can directly click the icon 1202 of user B to conveniently authorize the control right, such as the control right of speaker 3, to users in the user group, such as User B.
  • the icons of all users in the user group can also be sorted by authorization frequency, for example, in the order of authorization frequency from high to low, and from top to bottom, so that user A can more conveniently authorize the control right to frequent users in the user group.
  • the user selection interface 1201 may also include a user input box 1203, so that user A can authorize the control right to users who are not in the user group. For example, if user D is not in the user group, user A can input user D's account number in user input box 1203, and then click authorize 1204, so as to authorize the control right of speaker 3 to user D.
  • the foregoing authorization methods are only examples, not limitations.
  • user A can directly select a certain group, such as long pressing to select the living room 1102 .
  • the mobile phone 1 can determine that all devices in the selected group need to be authorized to control, such as the TV 4 and the sound box 3, so that it can directly jump from the group management interface 1101 to the user selection interface 1201, in order to Reduce the number of interface jumps, thereby improving user experience.
  • the mobile phone 1 can directly authorize the control right of the speaker 3 to the user in the user group who is currently connected to the mobile phone 1, so as to reduce the user's operations and improve the user experience.
  • the users in the user group include: user B and user C, and mobile phone 1 is currently connected to user B's mobile phone through Bluetooth, NFC or Wi-Fi, then mobile phone 1 can directly authorize user B to control the speaker 3.
  • the mobile phone 1 can display a prompt message of successful authorization on the current interface, such as the user selection interface 1201, such as that the speaker 3 has been authorized to user B, so that the user can know in time that the authorization of the control right is successful, so as to provide Subsequent cancellation of authorization by the user provides a basis for decision-making.
  • the mobile phone 1 can also jump from the user selection interface 1201 to the authorization management interface 1205 (shown in (b) in FIG. 12 ).
  • the authorization management interface 1205 may include: the icon of user B, the device authorized to control, such as the icon of the speaker 3 (living room), and deauthorization 1206 .
  • the mobile phone 1 can display a prompt message of the authorization failure on the current interface, such as the user selection interface 1201, such as the speaker 3 is not authorized successfully, so that the user can know in time and re-authorize.
  • mobile phone 1 may send the identification of user B and the identification of speaker 3 to the cloud platform.
  • the cloud platform since the cloud platform has determined that user A has the master control right of speaker 3, the cloud platform can determine that user B has the slave control right of speaker 3 according to the identity of user B and the identity of speaker 3, so that Send the identification of the speaker 3 to the mobile phone 2.
  • the mobile phone 2 can send the identifier of the speaker 3 and the identifier of the user B to the speaker 3 to initiate control of the speaker 3 .
  • speaker 3 since speaker 3 locally records the binding relationship between user A and speaker 3, speaker 3 can determine that the user who initiated the control is not user A according to the identifier of user B and the identifier of speaker 3, Therefore, it is determined that user B has the slave control right of speaker 3 . In this way, the speaker 3 can periodically initiate a control verification to the user B, so as to avoid being hijacked by the user B. For example, for a certain period, the speaker 3 may randomly generate a check value, such as check value 1. Then, on the one hand, the speaker 3 can determine the latest control key, such as the key 3, according to the verification value 1, the key 1, and the identification of user B; on the other hand, the speaker 3 can notify the mobile phone 2 to obtain the latest control key.
  • the speaker 3 may randomly generate a check value, such as check value 1.
  • the speaker 3 can determine the latest control key, such as the key 3, according to the verification value 1, the key 1, and the identification of user B; on the other hand, the speaker 3 can notify the mobile phone 2 to obtain the latest control key
  • the key such as sending the verification value 1 to the mobile phone 2, so that the mobile phone 2 forwards the verification value 1 to the cloud platform.
  • user A does not cancel the control authorization of user B on the cloud platform
  • the mobile phone 1 can cancel the control right authorization of the user B on the cloud platform, so that the cloud platform no longer determines the key 3 according to the verification value 1, the key 1 and the identity of the user B. In this way, the mobile phone 2 cannot obtain the same control key as the sound box 3, so that the sound box 3 cannot be continued to be controlled, so as to prevent the mobile phone 2 from hijacking the sound box 3.
  • the overall flow of the device control method provided in the embodiment of the present application may include: the mobile phone 1 can control the speaker 3 Register to the cloud platform so that the cloud platform can bind speaker 3 and mobile phone 1 (or bind speaker 3 and user A). Then, mobile phone 1 can notify speaker 3 to bind user A.
  • user A since user A is the first user to bind speaker 3, user A has the master control right of speaker 3, so that user A can authorize the control right of speaker 3 to user B on the cloud platform, so that the cloud platform can bind the speaker 3 with user B.
  • the user B since the user B is not the first user to bind the speaker 3, the user B has the slave control right of the speaker 3. In this way, user B can initiate control of the speaker 3 through the mobile phone 2 .
  • the speaker 3 can determine, according to the binding relationship between the speaker 3 and the user A, that the user currently initiating control is not the user with the main control right, that is, user A, so that the control right check can be periodically initiated to the user B. For example, for a certain period, the speaker 3 can notify the mobile phone 2 to obtain the latest control key. After the mobile phone 2 receives the notification from the speaker 3 requesting the mobile phone 2 to obtain the latest control key, the mobile phone 2 can request the cloud platform to determine the latest control key for the mobile phone 2 .
  • the cloud platform determines that user B has the slave control right of speaker 3, thus The cloud platform determines the latest control key and sends the latest control key to the mobile phone 2, so that user B can continue to use the mobile phone 2 to control the speaker 3.
  • the cloud platform determines that user B does not have the secondary control right of speaker 3, so the cloud platform Not sure about the latest control key, cell phone 2 cannot get the latest control key.
  • the speaker 3 can determine that the mobile phone 2 has not obtained the latest control key, for example, the speaker 3 has not received the latest control key from the mobile phone 2 after a timeout, so the speaker 3 is disconnected from the mobile phone 2 .
  • the speaker 3 will periodically initiate a control verification to the mobile phone 2 (or user B) to determine whether the mobile phone 2 still has the control right of the speaker 3 If the speaker 3 determines that the mobile phone 2 no longer has control over the speaker 3, the speaker 3 will actively disconnect from the mobile phone 2 to avoid being hijacked by the mobile phone 2.
  • the speaker 3 initiates the verification of the control right by notifying the mobile phone 2 to obtain the latest control key
  • the latest control key can be determined devices, including speaker 3 and cloud platform, but not mobile phone 2, so that if mobile phone 2 wants to obtain the latest control key, it needs to request the latest control key from the cloud platform, and cannot confirm the latest control key by itself. key.
  • user A of mobile phone 1 cancels the authorization of the control right of speaker 3 to user B, it will be notified to the cloud platform synchronously, so that the cloud platform can obtain information on whether current user B still has the control right of speaker 3 in time.
  • the cloud platform determines that user B no longer has control over the speaker 3, even if the cloud platform receives a message from the mobile phone 2 requesting the latest control key, the cloud platform will not update the latest control key sent to the mobile phone 2, or the cloud platform will not perform the step of determining the latest control key. Therefore, the mobile phone 2 cannot obtain the latest control key, and the speaker 3 determines that the verification of the control right of the mobile phone 2 fails, and the speaker 3 actively disconnects from the mobile phone 2 to avoid being hijacked by the mobile phone 2.
  • FIG. 13 is a first schematic flow diagram of the device control method provided by the embodiment of the present application. As shown in FIG. 13 , the specific flow of the device control method may include:
  • the mobile phone 1 can scan, for example, scan through Bluetooth, Wi-Fi, or NFC, to discover the speaker 3, thereby obtaining the device information of the speaker 3.
  • the device information can include at least one of the following: device type, device model, device The version, or device manufacturer, etc., are not limited in this embodiment of the present application.
  • the mobile phone 1 registers the speaker 3 to the cloud platform.
  • the registration of the speaker 3 to the cloud platform may be that the cloud platform records the speaker 3, assigns a corresponding identifier to the speaker 3, and determines the control key of the mobile phone 1, such as the key 1 (or the second control key).
  • the key 1 can be used to establish a session (such as a control session) between the mobile phone 1 and the speaker 3, so that the mobile phone 1 can control the speaker 3 through the session.
  • the key 1 can be used for the cloud platform to determine other control keys, such as the key 3 (or the first control key), which is used for other devices (such as the mobile phone 2) to establish a session with the speaker 3 except the mobile phone 1,
  • the specific implementation can refer to the following S1313, which will not be repeated here.
  • the mobile phone 1 can send the device information of the speaker 3 to the cloud platform, as well as the identification of the above-mentioned user A, such as an account identification.
  • the cloud platform can determine that the speaker 3 is an unregistered device according to the device information of the speaker 3, and then assign the speaker 3 identifier and the above-mentioned key 1 to the speaker 3 to complete the registration of the speaker 3.
  • the cloud platform can establish a binding relationship between user A and speaker 3, such as the corresponding relationship between user A's logo and speaker 3's logo, so as to determine that user A has the master control right of speaker 3.
  • the cloud platform can send to the mobile phone 1, such as packaged or separately sent the identification of the speaker 3, and the key 1, so that the mobile phone 1 can also establish a binding relationship between user A and the speaker 3.
  • the mobile phone 1 notifies the speaker 3 to bind the user A.
  • the mobile phone 1 may also notify the speaker 3 to bind the user A when the registration is completed. For example, mobile phone 1 sends the logo of user A, the logo of speaker 3 and the key 1 (which can be carried in the second information) to speaker 3, so that speaker 3 can be accurately bound according to the logo of user A and the logo of speaker 3
  • the user who needs to be bound is to establish a binding relationship between user A and speaker 3, such as the corresponding relationship between the identity of user A and the identity of speaker 3, so as to avoid wrong binding.
  • user A is the first user who binds the speaker 3, that is, the first user who has the control right (or master control right) of the speaker 3.
  • the speaker 3 can initiate a control right verification to other users according to user A's master control right, without initiating a control right verification to user A, so that Avoid false verification; that is, the speaker 3 may not initiate a control right verification to the user who has the main control right.
  • the mobile phone 1 sends a session negotiation request to the speaker 3, and the speaker 3 receives the session negotiation request from the mobile phone 1.
  • the session negotiation request can be used to request the speaker 3 to cooperate with the mobile phone 1 to establish a control session (session), such as a control session between the mobile phone 1 and the speaker 3, so that the mobile phone 1 can subsequently control the speaker 3 through the control session.
  • the session negotiation request may include: an identifier of user A, and a random number (random number, RN), such as RN1.
  • RN1 can be randomly generated by mobile phone 1, and is used for speaker 3 to generate a session key for controlling the session, such as key 2.
  • RN1 can be randomly generated by mobile phone 1, and is used for speaker 3 to generate a session key for controlling the session, such as key 2.
  • RN1 can be randomly generated by mobile phone 1, and is used for speaker 3 to generate a session key for controlling the session, such as key 2.
  • the speaker 3 determines the session key.
  • speaker 3 After speaker 3 receives the session negotiation request, it can determine the identity of user A who currently requests to establish a control session based on the identity of user A in the session negotiation request and the established binding relationship between user A and speaker 3, that is, the owner of the speaker 3 users with master control rights. In this way, speaker 3 can determine a session key, such as key 2, according to key 1, RN1 in the session negotiation request, and RN2. Among them, RN2 may be randomly generated by speaker 3 .
  • the speaker 3 sends a session negotiation response to the mobile phone 1, and the mobile phone 1 receives the session negotiation response from the speaker 3.
  • the session negotiation response can be used to indicate that the speaker 3 has accepted the request of the mobile phone 1, and the speaker 3 can cooperate with the mobile phone 1 to establish a control session.
  • the session negotiation response may include RN2.
  • the speaker 3 determines the session key, and the execution order of sending the session negotiation response is not limited.
  • the mobile phone 1 determines the session key.
  • the mobile phone 1 After receiving the session negotiation response, the mobile phone 1 can determine the session key, such as key 2, according to the key 1, RN1, and RN2 in the session negotiation response. In this way, the mobile phone 1 and the speaker 3 have the same session key, so it can be considered that the control session is established. After that, the mobile phone 1 and the speaker 3 can use the key 2 for encrypted communication, so that the speaker 3 can respond to the control of the mobile phone 1 and perform corresponding operations, such as playing audio, adjusting the playback volume, and so on.
  • the session key such as key 2
  • the mobile phone 1 and the speaker 3 can use the key 2 for encrypted communication, so that the speaker 3 can respond to the control of the mobile phone 1 and perform corresponding operations, such as playing audio, adjusting the playback volume, and so on.
  • S1304-S1307 is an exemplary manner of establishing a control session, and is not intended to be a limitation, and other manners of establishing a control session may also be applicable to this embodiment of the present application.
  • the mobile phone 1 and the speaker 3 can also establish a control session using a secure remote password (secure remote password, SRP) protocol.
  • SRP secure remote password
  • the above-mentioned key 1 can be considered as a password in the SRP protocol, so that the mobile phone 1 can determine RN3, and according to RN3 and the password, determine a public-private key pair, such as public-private (publickey) 1 and private key (privatekey) 1.
  • speaker 3 can determine RN4, and determine a public-private key pair, such as public-private 2 and private key 2, according to RN4 and the password. In this way, the mobile phone 1 and the speaker 3 can exchange their respective public keys, thereby completing the establishment of the control session.
  • S1304-S1307 are optional steps. For example, after the mobile phone 1 is bound to the speaker 3, if it is necessary to control the speaker 3, or to transmit data to the speaker 3, then S1304-S1307 can be executed; otherwise, S1304-S1307 can not be executed. S1307.
  • the mobile phone 1 sends authorization information to the cloud platform, and the cloud platform receives the authorization information from the mobile phone 1.
  • the authorization information may be used to instruct the mobile phone 1 to authorize the control right of the speaker 3 to the user B, and may include: an identifier of the user B, such as an account identifier, and an identifier of the speaker 3 .
  • the identifier of user B may be an identifier stored in advance by mobile phone 1, or may be an identifier obtained by mobile phone 1 in real time, for example, user A inputs user B's identifier.
  • the mobile phone 1 may send the identification of the user B and the identification of the speaker 3 to indicate that user B is authorized to control the speaker 3 .
  • step S1308 is triggered by user operations (such as user A's operations) shown in FIGS. 5-12 above.
  • the cloud platform determines that the user B has the slave control right of the speaker 3.
  • the cloud platform After the cloud platform receives the authorization information, it can judge whether user B has the master control right of the speaker 3 or the slave control right according to the identifier of the user B in the authorization information and the identifier of the speaker 3 . Among them, since the cloud platform records the binding relationship (or master binding relationship) between speaker 3 and user A, that is, user A has the master control right of speaker 3, then the cloud platform can determine that user B has the slave control right of speaker 3 , and establish a binding relationship (or secondary binding relationship) between user B (such as the user B identifier) and speaker 3 (such as the speaker 3 identifier).
  • the cloud platform sends the first notification information to the mobile phone 2, and the mobile phone 2 receives the first notification information from the cloud platform.
  • the first notification information may be used to indicate that the device to be controlled by the mobile phone 2 is the speaker 3 , and may include the identifier of the speaker 3 .
  • the cloud platform may directly send the first notification information to the mobile phone 2, or may send the first notification information to the mobile phone 2 when the mobile phone 2 is online, such as logging in to the cloud platform, which is not limited.
  • the mobile phone 2 sends a control request to the speaker 3, and the speaker 3 receives the control request from the mobile phone 2.
  • control request (or the third information) may be used to request to control the speaker 3, and may include: the identifier of the user B, and the identifier of the speaker 3.
  • the speaker 3 determines that user B has the slave control right.
  • the speaker 3 can judge whether the user B has the master control right or the slave control right of the speaker 3 according to the identification of the user B in the control request.
  • the speaker 3 since the speaker 3 has recorded the binding relationship between the speaker 3 and the user A, that is, the user A has the master control right of the speaker 3, the speaker 3 can determine that the user who initiates the control is not the user who has the master control right of the speaker 3, namely Make sure that user B has slave control of speaker 3.
  • speaker 3 needs to periodically initiate the control verification for user B to verify whether user B currently still has the slave control right of speaker 3, so as to avoid being hijacked by user B.
  • the specific implementation Reference may be made to related introductions in the following S1313-S1324, which will not be repeated here.
  • the speaker 3 determines the latest control key.
  • the speaker 3 can generate a check value, such as randomly generating a check value 1, so that the speaker 3 can generate a check value according to the key 1, the user
  • the identification of B and the verification value 1 determine the latest control key, such as key 3, so that the speaker 3 can determine whether the mobile phone 2 can obtain the same key according to the key 3, so as to realize the control of user B. check.
  • the speaker 3 sends the first verification information to the mobile phone 2, and the mobile phone 2 receives the first verification information from the speaker 3.
  • the speaker 3 sends the first verification information (or first information) to the mobile phone 2 to notify the mobile phone 2 Get the latest control key, such as key 3.
  • the first check information may also include the above check value 1.
  • first preset time point and the second preset time point may be the same or different, which is not limited thereto.
  • the mobile phone 2 sends the first verification request to the cloud platform, and the cloud platform receives the first verification request from the mobile phone 2.
  • the first verification request (or fourth information) may be used to request the cloud platform to determine the latest control key for the mobile phone 2 .
  • the first verification request may include: the verification value 1, the identification of the speaker 3, and the identification of the user B.
  • the first verification request may be generated by the mobile phone 2 according to the first verification information.
  • the cloud platform determines that the user B has the slave control right of the speaker 3.
  • the cloud platform After receiving the first verification request, the cloud platform can determine whether user B has the slave control right of the speaker 3 according to the identification of user B in the first verification request. Among them, since user A has not canceled the control right authorization of user B on the cloud platform at this time, that is, the cloud platform still records the binding relationship between user B and speaker 3, then the cloud platform determines that user B has the secondary control right of speaker 3, Therefore, the latest control key, such as key 3, can be determined according to key 1, the identity of user B, and the check value 1.
  • the cloud platform sends the latest control key to the mobile phone 2, and the mobile phone 2 receives the latest control key from the cloud platform.
  • the sending time point of S1317 should be before the start of the first cycle. That is to say, in addition, the time interval between the above-mentioned second preset time point and the start of the first cycle needs to satisfy that S1317 is executed before the start of the first cycle.
  • the mobile phone 2 and the speaker 3 establish a control session in the first cycle according to the latest control key.
  • the mobile phone 1 sends authorization cancellation information to the cloud platform, and the cloud platform receives the authorization cancellation information from the mobile phone 1.
  • the authorization cancellation information may be used to indicate that user A needs to cancel the authorization of the control right of user B, and may include the identification of user A, the identification of user B, and the identification of speaker 3 .
  • the authorization cancellation information may indicate that user A needs to cancel the authorization of the control right of user B's speaker 3 through the identifier of user A, the identifier of user B, and the identifier of speaker 3 .
  • the cloud platform can delete the binding relationship between user B and speaker 3 according to the authorization cancellation information, or determine that user B no longer has the control right of speaker 3 .
  • step S1319 is triggered by the user operation (such as the user A's operation) shown in (b) in FIG. 10 or (b) in FIG. 12 .
  • the speaker 3 can continue to generate the check value, such as randomly generating the check value 2, so as to update the control key according to the key 1, the identification of user B and the verification value 2, such as updating the key 3 to key 4, so that the speaker 3 can determine whether the mobile phone 2 can obtain the key according to the key 4 The same key, so as to continue to verify the control of user B.
  • the check value such as randomly generating the check value 2
  • the verification value such as updating the key 3 to key 4
  • the speaker 3 can determine whether the mobile phone 2 can obtain the key according to the key 4 The same key, so as to continue to verify the control of user B.
  • the speaker 3 sends the second verification information to the mobile phone 2, and the mobile phone 2 receives the second verification information from the speaker 3.
  • the speaker 3 can also send the second verification information to the mobile phone 2 (or the first A message) is used to notify the mobile phone 2 that it needs to obtain the latest control key, such as the key 4.
  • the second check information may also include the above check value 2.
  • the third preset time point may be the same as or different from the fourth preset time point, which is not limited thereto.
  • the mobile phone 2 sends a second verification request to the cloud platform, and the cloud platform receives the second verification request from the mobile phone 2 .
  • the second verification request (or fourth information) may be used to request the cloud platform to determine the latest control key for the mobile phone 2 .
  • the second verification request may further include: the verification value 2, the identification of the speaker 3, and the identification of the user B.
  • the second verification request may be generated by the mobile phone 2 according to the second verification information.
  • S1319 and S1320-S1322 are not limited. That is to say, S1319 may occur before S1323, that is, before the cloud platform determines the latest control key, the authorization of the control right of user B may be canceled.
  • the cloud platform determines that the user B does not have the slave control right of the speaker 3.
  • the cloud platform can judge whether user B still has the slave control right of the speaker 3 according to the identification of user B in the second verification request.
  • the cloud platform can determine that user B does not have speaker 3 of control.
  • the cloud platform determines that user B does not have the right to control the speaker 3, it will not generate the latest control key (such as key 4), so as to avoid generating the latest control key by mistake, such as in the case of user A canceling the authorization , still generating the latest control key.
  • the cloud platform sends the second notification information to the mobile phone 2, and the mobile phone 2 receives the second notification information from the cloud platform.
  • the second notification information may be used to notify that user B does not have the slave control right of speaker 3 .
  • S1324 is an optional step, that is, the cloud platform can actively notify user B that he does not have the slave control right of speaker 3; After receiving the control key from the cloud platform, it is determined that user B does not have the slave control right of speaker 3.
  • the speaker 3 determines that the mobile phone 2 has not obtained the key 4, if the key 4 of the mobile phone 2 has not been received at the beginning of the second cycle, then it is determined that the user B does not have the slave control right of the speaker 3, so that user B can actively Disconnect from phone 2 to cooperate with phone 1 deauthorization.
  • the mobile phone 2 may also actively disconnect from the speaker 3, such as disconnecting from the mobile phone 2 according to the second notification information.
  • the method for the speaker 3 and the cloud platform to determine the latest control key may be different from the method exemplarily shown in the embodiment of FIG. 13 . That is, key 3 may not be determined based on key 1, user B's identity, and check value 1, and key 4 may not be determined based on key 1, user B's identity, and check value 2. Key 3 and Key 4 may also be determined according to a method different from the exemplary method shown in the embodiment shown in Figure 13, and this embodiment of the present application does not limit the way of determining Key 3 and Key 4. Any method of determining the control key that can be determined by the speaker 3 and the cloud platform but not by the mobile phone 1 does not exceed the scope covered by the embodiment of the present application.
  • Fig. 14 is the second schematic flow diagram of the device control method provided by the embodiment of the present application.
  • the specific process may include:
  • the third device determines a second control key.
  • the above-mentioned second control key is used for the third device to establish a session (such as a control session) with the first device, so that the third device can control the first device through the session.
  • the second control key is also used by the first device to determine the first control key
  • the first control key is used by devices other than the third device to establish sessions with the first device, so that the devices other than the third device can The first device is controlled through the session.
  • the third device may receive the second control key from the fourth device, or the third device may determine the second control key by itself, which is not limited.
  • the third device sends second information to the first device, and the first device receives the second information from the third device.
  • the second information includes the second control key
  • the second information is used to instruct the first device to bind the third device.
  • the first device can bind the third device according to the second information. For example, if the first device determines according to the second information that no corresponding relationship with the first device has been established, that is, the first device is not currently bound to other devices, then establish the first corresponding relationship between the first device and the third device, that is, bind third device.
  • the third device is the first device bound to the first device, that is, the first device that has the control right (or master control right) of the first device. In this way, if other devices subsequently want to control the first device, the first device can initiate a control verification to other devices based on the master control right of the third device instead of initiating a control verification to the third device. verification, so as to avoid false verification.
  • the second information may further include: an identifier of the third device and an identifier of the first user.
  • the first device can accurately bind the device it needs to bind according to the second information, such as establishing a first correspondence between the identity of the third device and the user corresponding to the third device, such as the identity of the first user, to avoid wrong binding.
  • binding the first device to the third device is binding the identifier of the first user corresponding to the third device (such as the account of the first user). In this case, if the first user uses different devices to log in to the same account, he can still control the first device through the binding relationship of the first user, without the need for the first user to re-register and re-bind, which can improve user experience experience.
  • the third device may further send fifth information to the fourth device.
  • the fifth information is used to instruct the third device to authorize the control right of the first device to the second device.
  • the fourth device may bind the first device and the second device according to the fifth information, so as to determine that the second device has the control right of the first device.
  • the fourth device may determine the second corresponding relationship between the first device and the second device according to the fifth information.
  • the second corresponding relationship may be used to indicate that the identifier of the first device corresponds to the identifier of the second user.
  • the binding of the first device to the second device is to bind the identity of the first user (such as the account of the second user) corresponding to the second device. In this case, if the second user uses a different device to log in to the same account, he can still control the first device through the binding relationship of the second user without re-authorization by the first user, thereby improving the user experience.
  • the fourth device can also notify the second device, so that the second device can send the third information to the first device.
  • the third information may be used by the second device to request to control the first device, and may include: an identifier of the second user and an identifier of the first device, and the second user may be a user corresponding to the second device.
  • the first device sends the first information to the second device, and the second device receives the first information from the first device.
  • the first information is used for notifying the second device to obtain the first control key, or used for the first device to initiate verification of the control right of the second device.
  • the first information may include a check value, which may be used to determine the first control key.
  • the first device can determine the identity of the second user corresponding to the identity of the first device in the third information , is different from the identity of the first user corresponding to the identity of the first device in the first correspondence, so it is determined that the second device is not the first device that has the control right of the first device, and then it is determined to initiate a control right check to the second device , instead of initiating a control right check to other devices, so that false checks can be avoided.
  • the second device sends fourth information to the fourth device, and the fourth device receives the fourth information from the third device.
  • the fourth information is used to request the fourth device to determine the first control key.
  • the fourth information may include: an identifier of the first device, an identifier of the second user, and a verification value.
  • the fourth device parses the fourth information.
  • the fourth device may determine whether the second device has the control right of the first device according to the fourth information.
  • the fourth device may determine that the identity of the second user corresponding to the identity of the first device in the fourth information is the same as that of the first device in the first correspondence.
  • the identifiers of the first user corresponding to the identifiers are different, so that it is determined that the second user is not the first device that has the control right of the first device.
  • the fourth device can further determine whether the second user has the control right of the first device, or whether the first user cancels the authorization of the control right of the first device, so as to determine whether to generate the second control key, so as to avoid generating the second control key by mistake, for example, if the first device cancels authorization, the second control key is still generated.
  • the second device receives the sixth information from the first device before determining whether the second user has the control right of the first device.
  • the sixth information may be used to instruct the third device to cancel authorization of the control right of the first device to the second device.
  • the fourth device may cancel the binding between the first device and the second device according to the sixth information, such as deleting the second corresponding relationship between the first device and the second device.
  • the second device when the second device is determining whether the second user has the right to control the first device, it can be determined that the second device does not have the right to control the first device based on the fact that the first device is not bound to the second device, so that it is not determined for the second device
  • the first controls the key so that the second device cannot continue to control the first device, preventing the second device from hijacking the first device.
  • the fourth device may send seventh information to the second device, to indicate that the second device does not have the control right of the first device.
  • the foregoing S1405-S1406 is an example in which the second device does not have the control right of the first device, but it is not limited thereto.
  • the fourth device determines that the second device has the control right of the first device, that is, The first device has been bound to the second device, so as to determine the first control key, such as determining the first control key according to the check value, the second control key, and the identifier of the second user. In this way, the fourth device may send the first control key to the second device, so that the second device forwards the first control key to the first device.
  • the first device may also determine the first control key according to the check value, the second control key, and the identifier of the second user. In this way, the first device can determine the first control key from the second device, which is the same as the first control key determined by itself, thereby determining that the second device obtains the first control key, and then maintains the connection with the second device, In order to realize that the second device can continue to control the first device when it has the control right of the first device.
  • the second device since the second control key is stored locally in the first device and the fourth device, and neither the first device nor the fourth device sends the second control key to the second device, the second device cannot determine the first control key, thereby preventing the first device from being hijacked by determining the first control key by itself when the second device has no control rights.
  • the device control method described in Figure 14 it can be known that when an IoT device (such as the first device) has been bound to a certain device (such as the third device), that is, the third device already has the control right of the first device. If another device, such as the second device, wants to continue to control the first device, the first device can initiate a control verification to the second device, that is, send the first information to instruct the second device to obtain the latest A control key (such as a first control key). In this way, if the second device does not obtain the first control key, that is, it does not have the control right of the first device, the first device may disconnect from the second device, so as to prevent the first device from being hijacked by the second device.
  • a control verification to the second device that is, send the first information to instruct the second device to obtain the latest A control key (such as a first control key).
  • the second device does not obtain the first control key, that is, it does not have the control right of the first device, the first device may disconnect from the second device, so
  • the embodiment of the present application discloses an electronic device, such as the mobile phone 1 , the mobile phone 2 or the speaker 3 in the above embodiments.
  • the electronic device may specifically include: a display screen 1507; one or more processors 1502; a memory 1503; a communication module 1508; one or more application programs (not shown); Connections may be via one or more communication buses 1505 .
  • the one or more computer programs 1504 are stored in the above-mentioned memory 1503 and configured to be executed by the one or more processors 1502, the one or more computer programs 1504 include instructions, and the instructions can be used to perform the above-mentioned Relevant steps performed by the mobile phone in the embodiment.
  • the electronic device may also include a touch sensor 1506 (the touch sensor 1506 and the display screen 1507 may be integrated into a touch screen 1501 ), a mouse and other input devices.
  • the embodiment of the present application discloses a chip system.
  • the chip system is applied to an electronic device including a memory and a communication module; the chip system includes one or more interface circuits and one or more processors; the interface circuit and the processor are interconnected through lines; the interface circuit is used to receive data from the memory of the electronic device Signals are sent to the processor, the signals include computer instructions stored in the memory; when the processor executes the computer instructions, the electronic device executes the above-mentioned device control method.
  • At least one means one or more, and “multiple” means two or more.
  • At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items.
  • at least one item (piece) of a, b, or c can represent: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, c can be single or multiple .
  • sequence numbers of the above-mentioned processes do not mean the order of execution, and the execution order of the processes should be determined by their functions and internal logic, and should not be used in the embodiments of the present application.
  • the implementation process constitutes any limitation.
  • Each functional unit in each embodiment of the embodiment of the present application may be integrated into one processing unit, or each unit may physically exist separately, or two or more units may be integrated into one unit.
  • the above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.
  • the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage
  • the medium includes several instructions to enable a computer device (which may be a personal computer, server, or network device, etc.) or a processor to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: flash memory, mobile hard disk, read-only memory, random access memory, magnetic disk or optical disk, and other various media capable of storing program codes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Automation & Control Theory (AREA)
  • Human Computer Interaction (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Health & Medical Sciences (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请提供一种设备控制方法及装置，以实现在第二终端没有IoT设备的控制权的情况下，IoT设备不会被第二终端劫持，属于终端技术领域。方法包括：第一设备向第二设备发送第一信息，之后，若第一设备确定第二设备未获取第一控制密钥，则断开与第二设备的连接。其中，第一设备已绑定第三设备，第一信息用于通知第二设备获取第一控制密钥，第一控制密钥用于第二设备与第一设备建立会话。

Description

设备控制方法及装置
本申请要求于2021年06月30日提交国家知识产权局、申请号为202110736672.9、申请名称为“设备控制方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及物联网领域，尤其涉及一种设备控制方法及装置。
背景技术
随着物联网(internet of thing，IoT)技术的发展，越来越多的IoT设备，如空调、电视、音箱等，支持与其他设备，如手机、电脑等连接，以实现通过设备联动控制这些IoT设备。
具体而言，当某个设备，如第一终端需要控制IoT设备，可以请求云端分配对应的密钥，(如第一密钥)，以便第一终端使用第一密钥控制该IoT设备。此时，如果第一终端想要把IoT设备的控制权授权给其他设备，如与第一终端的云端账号不同的第二终端，则第一终端可以请求云端为第二终端分配对应的密钥(如第二密钥)，以便第二终端可以使用第二密钥控制该IoT设备，从而实现控制权的授权。
然而，在IoT设备与第二终端连接，但未与其他设备(如第一终端或云端)连接时，若第一终端取消授权，即第二终端已没有IoT设备的控制权，但第二终端却不断开与IoT设备的连接，则导致IoT设备被第二终端劫持。
发明内容
本申请实施例提供一种设备控制方法及装置，以实现在第二终端没有IoT设备的控制权的情况下，IoT设备不会被第二终端劫持。
第一方面，提供一种设备控制方法。该方法包括：第一设备向第二设备发送第一信息，之后，若第一设备确定第二设备未获取第一控制密钥，则断开与第二设备的连接。其中，第一设备已绑定第三设备，第一信息用于通知第二设备获取第一控制密钥，第一控制密钥用于第二设备与第一设备建立会话。
基于第一方面所述的方法可知，在某个IoT设备(如第一设备)已绑定某个设备(如第三设备)，即第三设备已拥有第一设备的控制权的情况，如果另一个设备，如第二设备想要继续控制第一设备，则第一设备可以向第二设备发起控制权校验，即发送第一信息，用以指示第二设备获取最新的控制密钥(如第一控制密钥)。如此一来，如果第二设备未获取第一控制密钥，即没有第一设备的控制权，则第一设备可以断开与第二设备的连接，以避免第一设备被第二设备劫持。
一种可能的设计方案中，在第一设备向第二设备发送第一信息之前，第一方面所述的方法还可以包括：第一设备接收来自第三设备的第二信息，从而根据第二信息，绑定第三设备。其中，第二信息可以用于指示第一设备需要绑定第三设备。如此，第一设备可以根据第二信息，准确绑定其需要绑定的设备，如第三设备，以避免误绑定。
可选地，第一设备根据第二信息，绑定第三设备，可以包括：第一设备根据第二信息，确定未建立第一设备的对应关系，从而建立第一设备与第三设备的第一对应关系。可以看出，如果第一设备当前没有绑定其他设备，则绑定第三设备。换言之，第三设备是首个绑定第一设备的设备，也即首个拥有第一设备的控制权(或者说主控制权)的设备。如此一来，如果后续有其他设备想要控制第一设备，则第一设备可以根据第三设备拥有主控制权，向其他设备发起控制权校验，而不是向第三设备发起控制权校验，从而避免误校验。
进一步地，第二信息可以包括：第一设备的标识、第一用户的标识、以及第二控制密钥，其中，第一用户为第三设备对应的用户，第一设备的对应关系为第一设备的标识与用户的标识的对应关系，第一对应关系为第一设备的标识与第一用户的标识的对应关系，第二控制密钥用于第三设备与第一设备建立会话。换言之，第一设备绑定第三设备为绑定该第三设备对应的第一用户的标识(如第一用户的账号)。这种情况下，如果第一用户使用不同设备登录同一账号，则其仍然可以通过第一用户的绑定关系控制第一设备，无需第一用户重新注册和重新绑定，从而可以提高用户的使用体验。
一种可能的设计方案中，在第一设备向第二设备发送第一信息之前，第一方面所述方法还可以包括：第一设备接收来自第二设备的第三信息。其中，第三信息用于第二设备请求控制第一设备。
可选地，第三信息可以包括：第二用户的标识和第一设备的标识，第二用户为第二设备对应的用户。如此，第一设备可确定第三信息中第一设备的标识对应的第二用户的标识，与第一对应关系中第一设备的标识对应的第一用户的标识不同，从而确定第二设备不是首个拥有第一设备的控制权的设备，进而确定向第二设备发起控制权校验(如向第二设备发送第一信息)，而不是向其他设备发起控制权校验，从而可以避免误校验。
一种可能的设计方案中，第一信息可以包括：校验值，校验值可以用于确定第一控制密钥。
可选地，第一控制密钥为根据校验值、第二控制密钥以及第二用户的标识确定。其中，第二控制密钥用于第三设备与第一设备建立会话，第二用户为第二设备对应的用户。可以看出，由于第二控制密钥保存在第一设备本地，且第一设备未向第二设备发送第二控制密钥，使得第二设备无法自行确定第一控制密钥，从而可以避免在第二设备没有控制权的情况下，通过自行确定第一控制密钥而劫持第一设备。
第二方面，提供一种设备控制方法。该方法包括：第二设备接收来自第一设备的第一信息，并向第四设备发送第四信息。其中，第一信息用于通知第二设备获取第一控制密钥，第一控制密钥用于第二设备与第一设备建立会话。第四信息用于请求第四设备确定第一控制密钥。
结合第一方面和第二方面所述的方法可知，由于第二设备无法自行确定第一控制密钥，而只能请求第四设备确定第一控制密钥，从而可以避免在第二设备没有控制权的情况下，通过自行确定第一控制密钥而劫持第一设备。
一种可能的设计方案中，第一信息可以包括：校验值，校验值用于第四设备确定第一控制密钥。
可选地，第四信息可以包括：第一设备的标识、第二用户的标识以及校验值。其中，第二用户为第二设备对应的用户。应理解，结合第二方面和下述第四方面所述的方法可知，在第四设备保存有上述第一对应关系的情况下，第四设备可确定第四信息中第一设备的标识对应的第二用户的标识，与第一对应关系中第一设备的标识对应的第一用户的标识不同，从而确定第二用户不是首个拥有第一设备的控制权的设备。如此，第四设备可以进一步确定第二用户是否有第一设备的控制权，或者说第一用户是否取消第一设备的控制权授权，从而根据第一设备是否取消授权，确定是否生成第二控制密钥，以避免误生成第二控制密钥，如在第一设备取消授的情况下，仍生成第二控制密钥。
可选地，在第二设备向第四设备发送第四信息之后，第二方面所述的方法还可以包括：第二设备接收来自第四设备的第一控制密钥，从而向第一设备发送第一控制密钥，以实现第二设备在拥有第一设备的控制权的情况下，可以继续控制第一设备。
一种可能的设计方案中，在第二设备接收来自第一设备的第一信息之前，第二设备向第一设备发送的第三信息。其中，第三信息用于第二设备请求控制第一设备。
可选地，第三信息可以包括：第二用户的标识和第一设备的标识，第二用户为第二设备对应的用户。
此外，第二方面所述的方法的其他技术效果可以参考上述第一方面所述方法的技术效果，在此不再赘述。
第三方面，提供一种设备控制方法。该方法包括：第三设备确定第二控制密钥，从而向第一设备发送第二信息，其中，其中，第二控制密钥用于第三设备与第一设备建立会话，以及还用于第一设备确定第一控制密钥，第一控制密钥用于除第三设备外的设备第三设备与第一设备建立会话。第二信息包括第二控制密钥，且第二信息用于指示第一设备绑定第三设备。
结合第一方面和第三方面所述的方法可知，通过第二信息指示第一设备绑定第三设备，可以使得第三设备成为第一设备首个绑定的设备，也是首个拥有第一设备的控制权的设备。如此，如果后续有其他设备(如第二设备)想要控制第一设备，第一设备便可以根据第一设备与第三设备的绑定关系，向第二设备发起控制权校验，即通知第二设备获取最新的控制密钥(如第一控制密钥)。此时，由于第一设备可以根据第二控制密钥确定第一控制密钥，则第一设备可以使用第一控制密钥，校验第二设备是否获取第一控制密钥，从而确定第二设备是否还拥有第一设备的控制权。如此，若第一设备确定第二设备没有第一设备的控制权，则断开与第二设备的连接，从而避免被第二设备劫持。
一种可能的设计方案中，第二信息还可以包括：第三设备的标识和第一用户的标识。
一种可能的设计方案中，在第三设备向第一设备发送第二信息之后，第三方面所述的方法还可以包括：第三设备向第四设备发送第五信息。其中，第五信息用于指示第三设备将控制权授权给第二设备，控制权为第一设备的控制权，以便第四设备后续可以确定第二设备，或者说第二设备对应的第二用户，拥有第一设备的控制权的设备，从而为第二设备确定第一控制密钥，以实现第二设备在拥有第一设备的控制权的情况 下，可以继续控制第一设备。
可选地，在第三设备向第四设备发送第五信息之后，第三方面所述的方法还可以包括：第三设备向第四设备发送第六信息。其中，第六信息用于指示第三设备取消将第一设备的控制权授权给第二设备。如此，第四设备后续可以根据第六信息，确定第二设备没有第一设备的控制权，从而不为第二设备确定第一控制密钥，以便第二设备无法继续控制第一设备，避免第二设备劫持第一设备。
此外，第三方面所述的方法的其他技术效果还可以参考上述第一方面以及第二方面所述方法的技术效果，在此不再赘述。
第四方面，提供一种设备控制方法。该方法可以包括：第四设备接收来自第二设备的第四信息，从而解析第四信息。其中，第四信息用于请求第四设备确定第一控制密钥，第一控制密钥用于第二设备与第一设备建立会话，第一设备已绑定第三设备。
一种可能的设计方案中，在第四设备解析第四信息之后，第四方面所述的方法还可以包括：若第四设备确定第二设备有第一设备的控制权，则根据第四信息，确定第一控制密钥，从而向第二设备发送第一控制密钥。
可选地，第四信息可以包括第一设备的标识、第二用户的标识以及校验值，第一控制密钥为根据校验值、第二控制密钥以及第二用户的标识确定，第二控制密钥用于第三设备与第一设备建立会话，第二用户为第二设备对应的用户。
可选地，第二设备有第一设备的控制权可以指：第一设备已绑定第二设备。
可选地，在第四设备确定第二设备有第一设备的控制权之前，第四方面所述方法还可以包括：第四设备接收来自第三设备的第五信息，以根据第五信息，将第一设备与第二设备绑定。其中，第五信息用于指示第三设备将第一设备的控制权授权给第二设备。
进一步地，第四设备根据第五信息将第一设备与第二设备绑定，可以包括：第四设备根据第五信息，确定第一设备与第二设备的第二对应关系。其中，第二对应关系用于指示第一设备的标识与第二用户的标识对应。换言之，第一设备绑定第二设备为绑定该第二设备对应的第一用户的标识(如第二用户的账号)。这种情况下，如果第二用户使用不同设备登录同一账号，则其仍然可以通过第二用户的绑定关系控制第一设备，无需第一用户重新授权，从而可以提高用户的使用体验。
一种可能的设计方案中，在第四设备解析第四信息之后，第四方面所述的方法还可以包括：若第四设备确定第二设备没有第一设备的控制权，则向第二设备发送第七信息。其中，第七信息用于指示第二设备没有第一设备的控制权。
可选地，第二设备没有第一设备的控制权可以指：第一设备未绑定第二设备。
可选地，在第四设备确定第二设备没有第一设备的控制权之前，第四方面所述的方法还可以包括：第四设备接收来自第三设备的第六信息，以根据第六信息，将第一设备与第二设备取消绑定。其中，第六信息用于指示第三设备取消将第一设备的控制权授权给第二设备。
进一步地，第四设备根据第六信息，将第一设备与第二设备取消绑定，可以包括：第四设备根据第六信息，删除第一设备与第二设备的第二对应关系。其中，第二对应关系用于指示第一设备的标识与第二用户的标识对应，第二用户为第二设备对应的用 户。
此外，第四方面所述的方法的其他技术效果可以参考上述第一方面至第三方面所述方法的技术效果，在此不再赘述。
第五方面，提供一种电子设备。该电子设备包括：一个或多个处理器、存储器、通信模块。其中，存储器中存储有一个或多个计算机程序，一个或多个计算机程序包括指令，当指令被电子设备执行时，使得电子设备执行如上述第一方面至第四方面中任一方面所述的方法。
第六方面，提供一种物联网系统。该通话系统包括一个或多个电子设备。其中，该电子设备用于执行如上述第一方面至第四方面中任一方面所述的方法。
第七方面，提供一种计算机可读存储介质，包括：计算机程序或指令；当该计算机程序或指令在计算机上运行时，使得该计算机执行如上述第一方面至第四方面中任一方面所述的方法。
第八方面，提供一种计算机程序产品，包括计算机程序或指令，当该计算机程序或指令在计算机上运行时，使得该计算机执行如上述第一方面至第四方面中任一方面所述的方法。
第九方面，提供一种芯片系统。该芯片系统应用于包括存储器和通信模块的电子设备；芯片系统包括一个或多个接口电路和一个或多个处理器；接口电路和处理器通过线路互联；接口电路用于从电子设备的存储器接收信号，并向处理器发送信号，信号包括存储器中存储的计算机指令；当处理器执行计算机指令时，电子设备执行上述第一方面至第四方面中任一方面所述的方法。
附图说明
图1为本申请实施例提供的物联网系统的架构示意图；
图2为本申请实施例提供的终端设备(例如手机)的结构示意图；
图3为本申请实施例提供的IoT设备(例如音箱)的结构示意图；
图4为本申请实施例提供的设备控制方法的应用场景图；
图5为本申请实施例提供的交互界面图一；
图6A为本申请实施例提供的交互界面图二；
图6B为本申请实施例提供的交互界面图三；
图6C为本申请实施例提供的交互界面图四；
图7为本申请实施例提供的交互界面图五；
图8为本申请实施例提供的交互界面图六；
图9为本申请实施例提供的交互界面图七；
图10为本申请实施例提供的交互界面图八；
图11为本申请实施例提供的交互界面图九；
图12为本申请实施例提供的交互界面图十；
图13为本申请实施例提供的设备控制方法的流程示意图一；
图14为本申请实施例提供的设备控制方法的流程示意图二；
图15为本申请实施例提供的电子设备的结构示意图。
具体实施方式
下面先介绍现有技术中的物理网系统。
现有技术中，物理网系统通常可以包括：第一终端、第二终端、IoT设备以及云端。
其中，如果第一终端想要控制IoT设备，则第一终端可以与IoT设备绑定，并请求云端分配对应的密钥(如第一密钥)，以便第一终端使用第一密钥，建立第一终端与IoT设备的会话，以通过会话控制IoT设备。此时，如果第一终端想要把IoT设备的控制权授权给其他设备，如授权给登录有与第一终端的云端账号不同的云端账号的第二终端，则第一终端可以指示第二终端绑定IoT设备，并请求云端或者直接由第一终端为第二终端分配对应的密钥(如第二密钥)，以便第二终端可以使用第二密钥，建立第二终端与IoT设备的会话，以通过会话控制IoT设备，从而实现控制权的授权。
在第二终端获得对IoT设备的控制权授权后，第二终端可以连接并控制该IoT设备。然而，在IoT设备与第二终端连接、受第二设备控制的情况下，如果第一终端想要取消授权，却因IoT设备只与第二终端连接(如该IoT设备是蓝牙设备，不具备直接与云端进行通信的能力)，IoT设备只能够与第二终端通信、只能接收第二终端的控制指令，将会导致第一终端无法指示IoT设备断开与第二终端的连接，那么第二终端可以始终保持与IoT设备的连接，并控制IoT设备，从而导致IoT设备被第二终端劫持。
目前，为了解决IoT设备被第二终端劫持的问题，让IoT设备断开与第二终端的连接，只能是通过手动通知的方式。例如，第一终端的用户手动通知(发短信、打电话或当面告知等)第二终端的用户，请断开第二终端与IoT设备的连接，从而第二终端的用户执行断开第二终端与IoT设备的连接的用户操作，或者第二终端的用户执行将该IoT设备从自己的设备列表中删除的用户操作，才可以解除IoT设备的劫持。该过程中，如果第二终端的用户不同意断开连接、不执行上述用户操作，则IoT设备仍会处于被第二终端劫持的状态。目前，第一终端能否成功取消该IoT设备的控制权授权，是取决于第二终端的。尚没有一种方法，能够让第一终端主动“夺回”该IoT设备的控制权。
为便于理解，下面通过两个具体场景进行介绍。
场景1，智能门锁被租客劫持。
第一终端为房东的手机，第二终端为租客的手机，IoT设备为租房的智能门锁。这种情况下，租客在租房的居住期间，房东可以通过手机，将智能门锁的控制权授权给租客，以便租客可通过手机控制智能门锁的开闭，从而进出租房。但是，当租客的居住到期后，由于房东无法通过手机取消授权给租客的智能门锁控制权，租客仍可以通过手机控制智能门锁的开闭，从而仍可自由进出租房，进而给房东生活造成不便，甚至会带来安全隐患。
场景2，耳机被其他用户劫持。
第一终端为用户1的手机，第二终端为用户2的手机，IoT设备为用户1的耳机。这种情况下，如果用户2想要使用耳机，用户1可以通过手机，将耳机的控制权授权给用户2，以便用户2可以使用耳机。但是，当用户1想要使用耳机时，若此时用户2的手机仍旧与用户1的耳机连接，用户1的耳机只能受用户2的手机的控制，则此时用户1无法通过手机取消授权给用户2的耳机控制权，使得用户2仍可以继续使用耳 机，从而给用户1的使用造成不便。
有鉴于此，本申请实施例提供一种设备控制方法、系统、电子设备及装置，能够使得上述场景中的第一终端主动“夺回”对IoT设备的控制权，有效避免IoT设备的劫持。
下面将结合附图，对本申请中的技术方案进行描述。
图1为本申请实施例中的物联网系统100的架构示意图，本申请实施例提供的设备控制方法，可应用于图1所示的物联网系统100中。如图1所示，该物联网系统100可以包括：一个或多个电子设备，如第一设备101、第二设备102、第三设备103以及第四设备104。
其中，该第一设备101、第二设备102、第三设备103可以为终端设备，终端设备具体可以为手机、平板电脑、电视(也可称为智慧屏、大屏设备等)、笔记本电脑、超级移动个人计算机(ultra-mobile personal computer，UMPC)、手持计算机、上网本、个人数字助理(personal digital assistant，PDA)、可穿戴电子设备、车载设备(也可称为车机)、增强现实(augmented reality，AR)设备、虚拟现实(virtual reality，VR)设备等；或者，还可以为IoT设备，如耳机、电视、音箱、门锁、冰箱、烤箱、微波炉、空调、扫地机器人、智能灯、摄像头等，对此不限定。第四设备104可以是网络设备，或者说云端设备或云平台(以下称为云平台)，具体可以为服务器(server)，如数据库服务器(database server)、应用服务器(application server)等，且可以是单个服务器或者服务器集群，对此不限定。在一种典型场景中，第一设备101为IoT设备，第二设备102、第三设备103为终端设备，第四设备104为云平台。
其中，第一设备101分别与第二设备102和第三设备103之间，第二设备102与第一设备101之间，第三设备103与第一设备101之间，以及第四设备104分别与第二设备102和第三设备103之间，可以通过有线的方式通信，如使用通用串行总线(universal serial bus，USB)建立有线连接，或者，也可以通过无线的方式通信，如通过蜂窝通信、蓝牙低功耗(bluetooth low energy，BLE)、无线保真(wireless fidelity，Wi-Fi)、近场通信(near field communication，NFC)、基于互联网协议的语音通话(voice over Internet protocol，VoIP)、支持网络切片架构的通信协议建立无线连接。此外，可选地，第一设备101与第四设备104之间，可以建立有线或无线通信连接，或者也可以不建立有线或无线通信连接，对此不限定；其中，本申请实施例提供的设备控制方法，尤其适用于第一设备101与第四设备104之间不建立有线或无线通信连接的场景；当然，本申请实施例提供的设备控制方法也可以适用于第一设备101与第四设备104之间建立有线或无线通信连接的场景。
示例性地，物联网系统100中，如果第三设备103想要控制第一设备101，且第一设备101当前未绑定其他设备，或者说未受控于其他设备，则第三设备103，或者说第一用户(即第三设备103对应的第一用户，如第三设备103的使用者)可以与第一设备101绑定，以拥有第一设备101的控制权，从而控制第一设备101，如控制音箱播放音频、电视播放视频、智能门锁开闭锁等等。并且，由于第三设备103与第一设备101绑定时，第一设备101未绑定其他设备，则第三设备103可作为第一设备101首个绑定的设备，即作为第一设备101的主控设备。如此，第三设备103拥有的第一 设备101的控制权可以为主控制权，即第三设备103不仅可以控制第一设备101，也可以将第一设备101的控制权授权给其他设备，以便其他设备也可以控制第一设备101。比如，第三设备可以通过云平台104，将第一设备101的控制权授权给第二设备102，或者说第二用户(即第二设备102对应的用户，如第二设备102的使用者)，以便第二设备102也可以与第一设备101绑定，以拥有第一设备101的控制权，从而控制第一设备101。其中，第二设备102的账号(如云平台上的账号)与第三设备103的账号(如云平台上的账号)不同。并且，由于第二设备102与第一设备101绑定时，第一设备101已绑定第三设备103，则第二设备102可作为第一设备101非首个绑定的设备，即作为第一设备101的从控设备。如此，第二设备102拥有的第一设备101的控制权可以为从控制权，即第二设备102可以控制第一设备101，但不能将第一设备101的控制权授权给其他设备。
之后，当第二设备102控制第一设备101时，由于第一设备101确定第二设备102拥有从控制权，而非主控制权，则可以周期性地向第二设备102发起控制权校验，如指示第二设备102获取最新的控制密钥。此时，如果第三设备103没有取消授权，如没有在云平台104上取消将第一设备101的控制权授权给第二设备102，则第二设备102通过云平台104能够完成控制权校验，如从云平台104获取最新的控制密钥，从而使用最新的控制密钥继续控制第二设备102。但是，倘若第三设备103取消授权，如在云平台104上取消将第一设备101的控制权授权给第二设备102，则第二设备102通过云平台104便不能完成控制权校验，如无法从云平台104获取最新的控制密钥。这样，第一设备101会因第二设备102未获取最新的控制密钥，而断开与第二设备102的通信连接，从而避免第一设备101被第二设备102劫持。
需要说明的是，上述第一设备101绑定第三设备103，可以是绑定第三设备103对应的第一用户，如建立第一设备101的标识与第一用户的标识，或者说第一用户的账号的对应关系。如此，上述第三设备103拥有第一设备101的控制权，可以认为是第一用户拥有第一设备101的控制权。这种情况下，如果第一用户使用不同设备登录同一账号，则其仍然可以通过第一用户的绑定关系控制第一设备，无需第一用户重新注册和重选绑定，从而可以提高用户的使用体验。同理，上述第一设备101绑定第二设备102，也可以为是绑定第二设备102对应的第二用户，如建立第一设备101的标识与第二用户的标识，或者说第二用户的账号的对应关系。如此，上述第二设备102拥有第一设备101的控制权，也可以认为是第二用户拥有第一设备101的控制权。这种情况下，如果第二用户使用不同设备登录同一账号，则其仍然可以通过第二用户的绑定关系控制第一设备，无需第一用户重新授权，从而也可以提高用户的使用体验。此外，对于第一设备101而言，拥有主控制权的用户(如第一用户)可以具有唯一性，如有且仅有一个，但拥有从控制权的用户(如第二用户)可以具有多样性，如可以有一个或多个，以便于拥有主控制权的用户，可以对拥有从控制权的用户的控制权限进行统一管理，如授权和取消授权，从而可以提高管理效率。
图2为本申请实施例提供的一种终端设备(例如手机)的结构示意图。如图2所示，第二设备102可以包括：处理器210，外部存储器接口220，内部存储器221，通用串行总线(universal serial bus，USB)接口230，天线1，天线2，移动通信模块250， 无线通信模块260，音频模块270，扬声器270A，受话器270B，麦克风270C，耳机接口270D，传感器模块280等。
处理器210可以包括：一个或多个处理单元，例如，处理器210可以包括：应用处理器(application processor，AP)，调制解调处理器，图形处理器(graphics processing unit，GPU)，图像信号处理器(image signal processor，ISP)，控制器，存储器，视频编解码器，数字信号处理器(digital signal processor，DSP)，基带处理器，和/或神经网络处理器(neural-network processing unit，NPU)等。其中，不同的处理单元可以是独立的器件，也可以集成在一个或多个处理器中。
处理器210中还可以设置存储器，用于存储指令和数据。在一些实施例中，处理器210中的存储器为高速缓冲存储器。该存储器可以保存处理器210刚用过或循环使用的指令或数据。如果处理器210需要再次使用该指令或数据，可从所述存储器中直接调用。避免了重复存取，减少了处理器210的等待时间，因而提高了系统的效率。
终端设备的无线通信功能可以通过天线1，天线2，移动通信模块250，无线通信模块260，调制解调处理器以及基带处理器等实现。
天线1和天线2用于发射和接收电磁波信号。终端设备中的每个天线可用于覆盖单个或多个通信频带。不同的天线还可以复用，以提高天线的利用率。例如：可以将天线1复用为无线局域网的分集天线。在另外一些实施例中，天线可以和调谐开关结合使用。
移动通信模块250可以提供应用在终端设备上的包括：2G/3G/4G/5G等无线通信的解决方案。移动通信模块250可以包括：至少一个滤波器，开关，功率放大器，低噪声放大器(low noise amplifier，LNA)等。移动通信模块250可以由天线1接收电磁波，并对接收的电磁波进行滤波，放大等处理，传送至调制解调处理器进行解调。移动通信模块250还可以对经调制解调处理器调制后的信号放大，经天线1转为电磁波辐射出去。在一些实施例中，移动通信模块250的至少部分功能模块可以被设置于处理器210中。在一些实施例中，移动通信模块250的至少部分功能模块可以与处理器210的至少部分模块被设置在同一个器件中。
无线通信模块260可以提供应用在终端设备上的包括：无线局域网(wireless local area networks，WLAN)，如Wi-Fi网络，BLE，全球导航卫星系统(global navigation satellite system，GNSS)，调频(frequency modulation，FM)，NFC，红外技术(infrared，IR)等无线通信的解决方案。无线通信模块260可以是集成至少一个通信处理模块的一个或多个器件。无线通信模块260经由天线2接收电磁波，将电磁波信号调频以及滤波处理，将处理后的信号发送到处理器210。无线通信模块260还可以从处理器210接收待发送的信号，对其进行调频，放大，经天线2转为电磁波辐射出去。
在一些实施例中，终端设备的天线1和移动通信模块250耦合，天线2和无线通信模块260耦合，使得终端设备可以通过无线通信技术与网络以及其他设备通信。该无线通信技术可以包括：GSM，GPRS，CDMA，WCDMA，TD-SCDMA，LTE，BT，GNSS，WLAN，NFC，FM，和/或IR技术等。该GNSS可以包括：全球卫星定位系统(global positioning system，GPS)，全球导航卫星系统(global navigation satellite system，GLONASS)，北斗卫星导航系统(beidou navigation satellite system，BDS)，准天顶 卫星系统(quasi-zenith satellite system，QZSS)和/或星基增强系统(satellite based augmentation systems，SBAS)。
终端设备通过GPU，显示屏294，以及应用处理器等实现显示功能。GPU为图像处理的微处理器，连接显示屏294和应用处理器。GPU用于执行数学和几何计算，用于图形渲染。处理器210可包括：一个或多个GPU，其执行程序指令以生成或改变显示信息。
显示屏294用于显示图像，视频等。显示屏294包括：显示面板。显示面板可以采用液晶显示屏(liquid crystal display，LCD)，有机发光二极管(organic light-emitting diode，OLED)，有源矩阵有机发光二极体或主动矩阵有机发光二极体(active-matrix organic light emitting diode的，AMOLED)，柔性发光二极管(flex light-emitting diode，FLED)，Miniled，MicroLed，Micro-oLed，量子点发光二极管(quantum dot light emitting diodes，QLED)等。在一些实施例中，终端设备可以包括：1个或N个显示屏194，N为大于1的正整数。
终端设备可以通过ISP，摄像头293，视频编解码器，GPU，显示屏294以及应用处理器等实现拍摄功能。
ISP用于处理摄像头293反馈的数据。例如，拍照时，打开快门，光线通过镜头被传递到摄像头感光元件上，光信号转换为电信号，摄像头感光元件将所述电信号传递给ISP处理，转化为肉眼可见的图像。ISP还可以对图像的噪点，亮度，肤色进行算法优化。ISP还可以对拍摄场景的曝光，色温等参数优化。在一些实施例中，ISP可以设置在摄像头293中。
摄像头293用于捕获静态图像或视频。物体通过镜头生成光学图像投射到感光元件。感光元件可以是电荷耦合器件(charge coupled device，CCD)或互补金属氧化物半导体(complementary metal-oxide-semiconductor，CMOS)光电晶体管。感光元件把光信号转换成电信号，之后将电信号传递给ISP转换成数字图像信号。ISP将数字图像信号输出到DSP加工处理。DSP将数字图像信号转换成标准的RGB，YUV等格式的图像信号。在一些实施例中，终端设备可以包括：1个或N个摄像头293，N为大于1的正整数。
数字信号处理器用于处理数字信号，除了可以处理数字图像信号，还可以处理其他数字信号。例如，当终端设备在做频点选择时，数字信号处理器用于对频点能量进行傅里叶变换等。
视频编解码器用于对数字视频压缩或解压缩。终端设备可以支持一种或多种视频编解码器。这样，终端设备可以播放或录制多种编码格式的视频，例如：动态图像专家组(moving picture experts group，MPEG)1，MPEG2，MPEG3，MPEG4等。
外部存储器接口220可以用于连接外部存储卡，例如Micro SD卡，实现扩展终端设备的存储能力。外部存储卡通过外部存储器接口220与处理器210通信，实现数据存储功能。例如将音乐，视频等文件保存在外部存储卡中。
内部存储器221可以用于存储计算机可执行程序代码，所述可执行程序代码包括指令。处理器210通过运行存储在内部存储器221的指令，从而执行终端设备的各种功能应用以及数据处理。内部存储器221可以包括：存储程序区和存储数据区。其中， 存储程序区可存储操作系统，至少一个功能所需的应用程序(比如声音播放功能，图像播放功能等)等。存储数据区可存储终端设备使用过程中所创建的数据(比如音频数据，电话本等)等。此外，内部存储器221可以包括：高速随机存取存储器，还可以包括：非易失性存储器，例如至少一个磁盘存储器件，闪存器件，通用闪存存储器(universal flash storage，UFS)等。
终端设备可以通过音频模块270，扬声器270A，受话器270B，麦克风270C，耳机接口270D，以及应用处理器等实现音频功能。例如音乐播放，录音等。
音频模块270用于将数字音频信息转换成模拟音频信号输出，也用于将模拟音频输入转换为数字音频信号。音频模块270还可以用于对音频信号编码和解码。在一些实施例中，音频模块270可以设置于处理器210中，或将音频模块270的部分功能模块设置于处理器210中。
扬声器270A，也称“喇叭”，用于将音频电信号转换为声音信号。终端设备可以通过扬声器270A收听音乐，或收听免提通话。
受话器270B，也称“听筒”，用于将音频电信号转换成声音信号。当终端设备接听电话或语音信息时，可以通过将受话器270B靠近人耳接听语音。
麦克风270C，也称“话筒”、“传声器”，用于将声音信号转换为电信号。当拨打电话或发送语音信息时，用户可以通过人嘴靠近麦克风270C发声，将声音信号输入到麦克风270C。终端设备可以设置至少一个麦克风270C。在另一些实施例中，终端设备可以设置两个麦克风270C，除了采集声音信号，还可以实现降噪功能。在另一些实施例中，终端设备还可以设置三个，四个或更多麦克风270C，实现采集声音信号，降噪，还可以识别声音来源，实现定向录音功能等。
耳机接口270D用于连接有线耳机。耳机接口270D可以是USB接口230，也可以是3.5mm的开放移动电子设备平台(open mobile terminal platform，OMTP)标准接口，美国蜂窝电信工业协会(cellular telecommunications industry association of the USA，CTIA)标准接口。
传感器模块280中可以包括：压力传感器，陀螺仪传感器，气压传感器，磁传感器，加速度传感器，距离传感器，接近光传感器，指纹传感器，温度传感器，触摸传感器，环境光传感器，骨传导传感器等。
当然，终端设备还可以包括：充电管理模块、电源管理模块、电池、按键、指示器以及1个或多个SIM卡接口等，本申请实施例对此不做任何限制。
可以理解的是，本发明实施例示意的结构并不构成对终端设备的具体限定。在本申请另一些实施例中，终端设备可以包括比图示更多或更少的部件，或者组合某些部件，或者拆分某些部件，或者不同的部件布置。图示的部件可以以硬件，软件或软件和硬件的组合实现。此外，本申请实施例所述的设备的连接，可以是直接连接，或者也可以是间接连接，如经由其他设备中转的连接，对此不限定。本申请实施例所述的发送，可以是直接发送，或者也可以是间接发送，如经由其他设备转发的发送，对此不限定。
图3为本申请实施例提供的一种IoT设备(例如音箱)的结构示意图，如图3所示，IoT设备可以包括：处理器310、存储器320、无线通信模块330以及电源340。
其中，存储器320可以用于存储应用程序代码，如用于IoT设备与上述手机进行配对连接的应用程序代码。处理器310可以控制执行上述应用程序代码，以实现本申请实施例中校验控制权的功能。
存储器320中还可以存储有用于唯一标识该IoT设备的地址。另外，该存储器320中还可以存储有与该IoT设备之前成功配对过的设备的连接数据。例如，该连接数据可以为与该IoT设备成功配对过的设备的地址。基于该连接数据，该IoT设备能够与该设备自动配对，而不必配置与其之间的连接，如进行合法性验证等。上述地址可以为媒体访问控制(media access control，MAC)地址。
无线通信模块330，用于支持IoT设备与各种设备，如上述手机之间的短距离数据交换。在一些实施例中，该无线通信模块340可以为收发器。IoT设备可以通过该收发器与上述手机之间建立无线连接，如蓝牙、Wi-Fi、NFC连接等等，以实现两者之间的短距离数据交换。
电源340，可以用于向IoT设备包含的各个部件供电。在一些实施例中，该电源340可以是电池，如可充电电池。
可以理解的是，本申请实施例示意的结构并不构成对IoT设备的具体限定。若IoT设备为不同类型的设备，则可以具有比图3中所示出的更多的或者更少的部件，可以组合两个或更多的部件，或者可以具有不同的部件配置。比如，若IoT设备为音箱，IoT设备还可以包括：扬声器、麦克风等；若IoT设备为电视，IoT设备还可以包括：显示屏、扬声器等；若IoT设备为空调，IoT设备还可以包括：压缩机、冷凝管等等，对此不限定。此外，图3中所示出的各种部件可以在包括一个或多个信号处理或专用集成电路在内的硬件、软件、或硬件和软件的组合中实现。
图4为本申请实施例提供的一种设备控制方法的应用场景示意图。
图5-图12为本申请实施例提供的交互界面图。
下面以第三设备为手机1、第二设备为手机2、第一设备为音箱3为例，对本申请实施例提供的设备控制方法的进行具体介绍。
示例性地，假设将手机1对应的用户，或者说手机1的使用者称作“用户A”、将手机2对应的用户，或者说手机2的使用者称作“用户B”，如果音箱3是新的设备，如用户A之前未控制过的设备，用户A需要先通过手机1绑定音箱3，如建立用户A的标识(identity document，ID)，如账号标识，与音箱3的标识的对应关系，以获得音箱3的控制权。其中，用户A的账号标识可以是用户A注册到云平台后，云平台为用户A的注册账号分配的标识。音箱3的标识可以是音箱3注册到云平台时，云平台为音箱3分配的标识。如此，在用户A与音箱3绑定的情况下，用户A可以通过手机1将音箱3的控制权授权给用户B，以便用户B通过手机2也可以控制音箱3，下面具体介绍。
本申请实施例中，如图5中的(a)所示，手机1可以显示主界面501。其中，主界面501可以是手机1开机后显示的界面，但不作为限定，也可以是其他界面，如后台界面，如负一屏。主界面501中可以包括手机1安装的各种应用(application，APP)，比如，可以包括手机1自带的APP的图标，如时钟、日历、图库、备忘录、应用商城、设置、音乐播放器、计算器、运动健康、相机、电话、信息、通讯录、智慧生活502等 等，又比如，也可以包括第三方的APP，如微信、QQ、支付宝、网络游戏等等。
若用户A希望绑定某个设备，则用户A可以点击主界面501中的智慧生活502。响应于该操作，手机1可以从主界面501跳转至智慧生活502的APP界面503(图5中的(b)所示)。APP界面503中，“2个设备”可用于指示用户A已绑定2个设备，如电视4和电视5，且电视4和电视5的图标可以显示在“2个设备”附近，如下方，以便用户A知晓已绑定的设备的具体类型。“+”504和“用户A的家”505都可用于绑定新的设备，以及将已绑定的设备的控制权授权给其他设备，但区别在于，“+”504是以设备为粒度实现上述功能，“用户A的家”505是以群组为粒度实现上述功能，下面分别介绍。
A、以设备为粒度绑定新的设备：
如图5中的(b)所示，若用户A想要单独添加并绑定某个设备，则可以点击“+”504。响应于该操作，手机1可以在“+”504的附近显示二级菜单601(图6A所示)。二级菜单601可以包括：添加设备602、授权设备等等。其中，添加设备602可以用于绑定新的设备，授权设备可以用于将已绑定的设备的控制权授权给其他用户(具体实现可以参考下述图9和图10的相关介绍)。
应理解，采用二级菜单601仅为一种示例性地实现方式，不作为限定。比如，手机1响应于点击“+”504的操作，可以从APP界面503跳转至一个新的界面，如设备添加/授权界面，且该设备添加/授权界面也包括：上述添加设备602、授权设备等等，以实现上述绑定设备，以及授权控制权的功能。
进一步地，若用户A点击添加设备602，则响应于该操作，一方面，手机1可以从APP界面603跳转至设备搜索界面604(图6B所示)，另一方面，手机1可以搜索附近的设备，如搜索到音箱3，从而在设备搜索界面604中显示音箱3的图标605。如此，若用户A点击图标605，则响应于该操作，一方面，手机1可以建立用户A与音箱3的绑定关系，如建立用户A的标识，与音箱3的标识的对应关系，另一方面，手机1可以从设备搜索界面604跳转回APP界面606(如图6C所示)。应理解，由于用户A与音箱3已经绑定，APP界面606中的图标，可由先前的“2个设备”改变为“3个设备”，用以表示用户A已绑定3个设备，如音箱3、电视4和电视5，且音箱3的图标可以新增显示在“3个设备附近，如下方，以方便用户A知晓新绑定的设备的具体类型。
B、以群组为粒度绑定新的设备：
如图5中的(b)所示，若用户A想要在组群中添加并绑定某个设备，则可以点击“用户A的家”505。响应于该操作，手机1可以从APP界面503跳转至群组管理界面701(图7中的(a)所示)。其中，群组管理界面701中可包括各群组的图标，如个人、客厅702、卧室。并且，每个群组的图标内还可以显示该群组内的设备数量，如个人包括0个设备，客厅702包括1个设备、卧室包括1个设备，以方便用户管理。以客厅702为例，若用户A想要在客厅702中绑定新的设备，则可以点击客厅702。响应于该操作，手机1可以从群组管理界面701跳转至如图7中的(b)所示的客厅管理界面703。其中，客厅管理界面703中可以包括：客厅702中的设备的图标，如电视4，以及还可以包括：新增设备704和授权设备。其中，新增设备602可以用于在 客厅702在绑定新的设备，授权设备可以用于将客厅702中已绑定的设备，如电视4的控制权授权给其他用户(具体实现可以参考下述图9和图10的相关介绍)。
进一步地，若用户A点击新增设备704，则响应于该操作，一方面，手机1可以从客厅管理界面703跳转至设备搜索界面801(图8中的(a)所示)，另一方面，手机1可以搜索附近的设备，如搜索到音箱3，从而在设备搜索界面801中显示音箱3的图标802。如此，若用户A点击图标802，则响应于该操作，手机1可以建立用户A与音箱3的绑定关系，如用户A的标识与音箱3的标识的对应关系，并且，手机1也可以从设备搜索界面801跳转回APP界面803(如图8中的(b)所示)。应理解，由于用户A与音箱3已经绑定，APP界面803中的图标，可由先前的“2个设备”改变为“3个设备”，用以表示用户A已绑定3个设备，如客厅中的音箱3和电视4，卧室中的电视5，且音箱3的图标可以新增显示在“3个设备”附近，如下方，以便用户A知晓新绑定的设备的具体类型。
需要注意的是，以音箱3为例，根据图6C以及图8中的(b)可以看出，若以设备为粒度绑定音箱3，则绑定后的音箱3为独立的绑定设备，不归属于某个群组，若以群组为粒度绑定音箱3，则绑定后的音箱3可归属于相应的群组，如属于客厅。换言之，用户可以根据实际需求，选择相应的绑定方式。比如，若用户想要独立控制某个设备，则可以采用上述设备粒度的绑定方式，若用户想要控制某个群组，如群分享，群播放等，则可以采用上述群组粒度的绑定方式。
进一步地，仍以音箱3为例，云平台可根据用户A与音箱3的绑定关系，确定用户A拥有音箱3的主控制权，从而为手机1分配音箱3的控制密钥，如密钥1。如此，手机1可以向音箱3发送密钥1，以及用户A与音箱3的绑定关系。相应地，对于音箱3而言，音箱3可根据用户A与音箱3的绑定关系，确定用户A拥有音箱3的控制权。如此，音箱3和手机1可以使用密钥1建立会话，以通过会话进行加密通信，以实现加密控制，以确保控制的安全性，避免控制权被窃取。应理解，云平台可以为同一用户的不同设备对应分配不同的控制密钥，以便每个设备使用的控制密钥与其他设备使用的控制密钥不同，从而互不干扰，以进一步提高加密通信的安全性。比如，云平台为用户A的手机1分配密钥1，并为用户A的其他设备，如手机3(图4中未示出)分配密钥X，且密钥1和密钥X不同。如此，手机1与音箱3可以使用密钥1建立会话，手机3与音箱3则可以使用密钥X建立会话。
进一步地，用户A与音箱3绑定后，可以将已绑定的设备，如音箱3的控制权授权给其他用户，如用户B。其中，根据前述图5的相关介绍可知，用户A可以以设备为粒度授权控制权，或者以群组为粒度授权控制权，下面分别介绍。
1、设备为粒度授权控制权：
如图6C所示，若用户A想要将某个设备的控制权授权给其他用户，则可以点击“+”607。响应于该操作，手机1可以在“+”607的附近显示二级菜单901(图9中的(a)所示)。然后，用户A可以点击授权设备902，响应于该操作，手机1可以从APP界面903跳转至设备授权界面904(图9中的(b)所示)。设备授权界面904中可以包括用户A所有已绑定的设备的图标，如客厅的电视4，卧室的电视5，以及未分组的音箱3。进一步地，用户A可以在设备授权界面904中，选中相应的设备，如 通过长按或点击选中相应的设备。其中，被选中的设备附近可以显示选中标记，以便用户A可以取消选中，以修改选错的设备。或者，被选中的设备的图标也可以以高亮、抖动等方式显示，以示区别。其中，用户A可以选中某个设备，如选中音箱3，或者也可以选中多个设备，如选中音箱3、电视4和电视5。以选中音箱3为例，用户A可以点击确定授权905，响应于该操作，手机1可以从设备授权界面904跳转至用户选择界面1001(图10中的(a)所示)。此外，如果用户A想要取消授权，也可以点击取消授权907，响应于该操作，手机1可以从设备授权界面904回退到APP界面903。
进一步地，一方面，用户选择界面1001中可包括曾经授权过的用户的图标，如用户B的图标1002、用户C的图标等等。如此，若用户A想要把音箱3的控制权授权给用户B，则可以直接点击用户B的图标1002，以实现更便捷地将控制权，如音箱3的控制权授权给曾经授权过的用户，如用户B。此外，曾经授权过的用户的图标还可以按授权频率排序，如按授权频率从高到低的顺序，从上往下依次排列，以便用户A可以更便捷地选中经常授权的用户，以进一步提升用户体验。比如，若用户A授权给用户B的频率高于授权给用户C的频率，则按上往下依次为：用户B的图标1002、用户C的图标。另一方面，用户选择界面1001中还可以包括用户输入框1003，以便用户A可以将控制权授权给未授权过的用户。比如，若用户A想要把音箱3的控制权授权给未授权过的用户，如用户D，则可以在用户输入框1003内输入用户D的账号，然后点击授权1004，以实现将音箱3的控制权授权给用户D。
应理解，上述授权方式仅为示例，不作为限定。比如，用户A点击确定授权905后，响应于该操作，手机1可直接将音箱3的控制权授权给手机1当前连接的手机对应的用户。比如，若手机1当前通过蓝牙、NFC或Wi-Fi与用户B的手机连接，则手机1可以直接将音箱3的控制权授权给用户B。
可选地，如果授权成功，则手机1可以在当前界面，如用户选择界面1001上显示授权成功的提示信息，如音箱3已授权给用户B，以便用户能够及时知晓控制权授权成功，从而为用户后续取消授权提供决策依据。并且，手机1还可以从用户选择界面1001跳转到授权管理界面1005(图10中的(b)所示)。其中，授权管理界面1005中可以包括：用户B的图标、授权控制权的设备，如音箱3的图标，以及取消授权1006。当然，如果授权失败，则手机1可以在当前界面，如用户选择界面1001上显示授权失败的提示信息，如音箱3未授权成功，以便用户能够及时知晓，并重新授权。
2、以群组为粒度授权控制权：
如图8中的(b)所示，若用户A想要将群组中某个或某些设备的控制权授权给其他用户，则可以点击“用户A的家”804。响应于该操作，手机1可以从APP界面803跳转至群组管理界面1101(图11中的(a)所示)，以便用户A可以将各群组中某个或某些设备的控制权，如客厅1102中音箱3和/或电视4的控制权，和/或，卧室中电视5的控制权，授权给其他用户。以客厅1102为例，若用户A想要将客厅1102中音箱3和/或电视4的控制权授权给其他用户，则可以点击客厅1102。响应于该操作，手机1可以从群组管理界面1101跳转至客厅管理界面1103(图11中的(b)所示)。进一步地，用户A可以在客厅管理界面1103中，选中相应设备的图标，如通过长按图标选中相应的设备。其中，被选中的设备附近可以显示选中标记，以便用户A 可以取消选中，以修改选错的设备。或者，被选中的设备的图标也可以以高亮、抖动等方式显示，以示区别。其中，用户A可以选中某个设备，如选中音箱3，或者也可以选中多个设备，如选中音箱3和电视4。以选中音箱3为例，用户A可以点击授权设备1104，响应于该操作，手机1可以从客厅管理界面1103跳转至用户选择界面1201(图12中的(a)所示)。
进一步地，用户选择界面1201中可以包括“用户A的家”对应的用户群内所有用户的图标，如用户B的图标1202、用户C的图标等等。如此，若用户A想要把音箱3的控制权授权给用户B，则可以直接点击用户B的图标1202，以便捷地将控制权，如音箱3的控制权授权给用户群内的用户，如用户B。此外，用户群内所有用户的图标还可以按授权频率排序，如按授权频率从高到低的顺序，从上往下依次排列，以便用户A可以更便捷地将控制权授权给用户群内经常授权的用户，以进一步提升用户体验。此外，用户选择界面1201中还可以包括用户输入框1203，以便用户A可以将控制权授权给非用户群内的用户。比如，若用户D为非用户群内的用户，则用户A可以在用户输入框1203输入用户D的账号，然后点击授权1204，以实现将音箱3的控制权授权给用户D。
应理解，上述授权方式仅为示例，不作为限定。比如，图11所示，在群组管理界面1101中，用户A可以直接选中某个群组，如长按选中客厅1102。响应于该长按操作，手机1可确定被选中群组内的所有设备均需要授权控制权，如电视4和音箱3，从而可以从群组管理界面1101直接跳转至用户选择界面1201，以减少界面跳转次数，从而提升用户使用体验。又比如，用户A点击授权设备1104后，响应于该操作，手机1可直接将音箱3的控制权授权给用户群内且手机1当前连接的用户，以减少用户的操作，从而提升用户使用体验。比如，若用户群内用户包括：用户B和用户C，且手机1当前通过蓝牙、NFC或Wi-Fi与用户B的手机连接，则手机1可以直接将音箱3的控制权授权给用户B。
可选地，如果授权成功，则手机1可以在当前界面，如用户选择界面1201上显示授权成功的提示信息，如音箱3已授权给用户B，以便用户能够及时知晓控制权授权成功，从而为用户后续取消授权提供决策依据。并且，手机1还可以从用户选择界面1201跳转到授权管理界面1205(图12中的(b)所示)。其中，授权管理界面1205中可以包括：用户B的图标、授权控制权的设备，如音箱3(客厅)的图标，以及取消授权1206。当然，如果授权失败，则手机1可以在当前界面，如用户选择界面1201上显示授权失败的提示信息，如音箱3未授权成功，以便用户能够及时知晓，并重新授权。
进一步地，仍以授权给用户B为例，手机1可以向云平台发送用户B的标识，以及音箱3的标识。对于云平台而言，由于云平台已确定用户A拥有音箱3的主控制权，则云平台可以根据用户B的标识，以及音箱3的标识，确定用户B拥有音箱3的从控制权，从而可以向手机2发送音箱3的标识。如此，手机2可以向音箱3发送音箱3的标识，以及用户B的标识，以发起对音箱3的控制。相应地，对于音箱3而言，由于音箱3本地记录有用户A与音箱3的绑定关系，则音箱3可以根据用户B的标识，以及音箱3的标识，确定发起控制的用户不是用户A，从而确定用户B拥有音箱3的 从控制权。这样，音箱3可以周期性地向用户B发起控制权校验，以避免被用户B劫持。比如，对于某个周期而言，音箱3可以随机生成校验值，如校验值1。而后，一方面，音箱3可以根据校验值1、密钥1以及用户B的标识，确定最新的控制密钥，如密钥3，另一方面，音箱3可以通知手机2获取该最新的控制密钥，如向手机2发送校验值1，以便手机2向云平台转发该校验值1。如此，如果用户A没有在云平台上取消用户B的控制权授权，则云平台接收到校验值1后，仍确定用户B拥有音箱3的从控制权，从而可以根据校验值1、密钥1以及用户B的标识确定最新的控制密钥，即密钥3，并向手机2发送该密钥3，以便手机2可以获得与音箱3相同的密钥，从而使用密钥3继续与音箱3建立会话，从而继续控制音箱3。反之，如图10中的(b)，或者图12中的(b)所示，若用户A想要结束取消授权，则可以点击结束授权1006，或者结束授权1206。响应于该操作，手机1可以在云平台上取消用户B的控制权授权，以便云平台不再根据校验值1、密钥1以及用户B的标识确定密钥3。这样，手机2便不能获得与音箱3相同的控制密钥，从而无法继续控制音箱3，以避免手机2将音箱3劫持。
以上结合图4-图12介绍了本申请实施例提供的设备控制方法的应用场景和交互界面，为便于理解，下面具体介绍设备控制方法的实现原理。
示例性地，仍以第三设备为手机1、第二设备为手机2、第一设备为音箱3为例，本申请实施例提供的设备控制方法的整体流程可以包括：手机1可以将音箱3注册到云平台，以便云平台可以绑定音箱3与手机1(或者说绑定音箱3与用户A)。然后，手机1可以通知音箱3绑定用户A。其中，由于用户A是首个绑定音箱3的用户，则用户A拥有音箱3的主控制权，从而可以在云平台上将音箱3的控制权授权给用户B，以便云平台可以绑定音箱3与用户B。其中，由于用户B不是首个绑定音箱3的用户，则用户B拥有音箱3的从控制权。如此，用户B可以通过手机2发起对音箱3的控制。此时，音箱3可以根据音箱3与用户A的绑定关系，确定当前发起控制的用户不是拥有主控制权的用户，即用户A，从而可以周期性地向用户B发起控制权校验。比如，对于某个周期而言，音箱3可以通知手机2获取最新的控制密钥。手机2接收到音箱3发送的要求手机2获取最新的控制密钥的通知后，手机2可以请求云平台为手机2确定最新的控制密钥。此时，如果用户A没有在云平台上取消用户B的控制权授权，即云平台仍记录有音箱3与用户B的绑定关系，则云平台确定用户B拥有音箱3的从控制权，从而云平台确定最新的控制密钥并将最新的控制密钥发送给手机2，以便用户B可以继续使用手机2控制音箱3。反之，如果用户A已在云平台上取消用户B的控制权授权，即云平台已删除音箱3与用户B的绑定关系，则云平台确定用户B没有音箱3的从控制权，从而云平台不确定最新的控制密钥，手机2不能获取最新的控制密钥。这样，音箱3可以确定手机2未获取最新的控制密钥，如音箱3超时未接收到来自手机2最新的控制密钥，从而音箱3断开与手机2连接。
延续上述示例，在本申请实施例提供的设备控制方法中，音箱3会周期性地向手机2(或者说用户B)发起控制权校验，来确定手机2当前是否仍旧具有音箱3的控制权；如果音箱3确定手机2当前不再具有音箱3的控制权，则音箱3会主动断开与手机2的连接，避免被手机2劫持。在一种实现方式中，音箱3发起控制权校验，可 以是通过通知手机2去获取最新的控制密钥实现的，而本申请实施例提供的设备控制方法中，可以确定最新的控制密钥的设备，包括音箱3和云平台，而不包括手机2，从而手机2要想获取最新的控制密钥，就需要去跟云平台请求最新的控制密钥，而不能够自行确认最新的控制密钥。同时，每当手机1的用户A取消了对用户B的音箱3控制权授权，就会同步告知给云平台，从而云平台能够及时获取到当前用户B是否仍旧具有音箱3的控制权信息。从而，在云平台确定用户B当前不再具有音箱3的控制权的情况下，云平台即使收到了手机2发送的请求最新的控制密钥的消息，云平台也不会把最新的控制密钥发送给手机2，或者，云平台也不会执行确定最新的控制密钥的步骤。从而手机2不能够获取最新的控制密钥，进而音箱3确定手机2控制权校验失败，音箱3主动断开与手机2的连接，避免了被手机2劫持。
基于以上对本申请实施例提供的设备控制方法的整体流程的介绍，接下来，详细描述本申请实施例提供的设备控制方法的几种可能的实现方式。
图13为本申请实施例提供的设备控制方法的流程示意图一，如图13所示，该设备控制方法的具体流程可以包括：
S1301，手机1发现音箱3。
手机1可以通过扫描，如通过蓝牙，Wi-Fi，或NFC等方式进行扫描，以发现音箱3，从而获取音箱3的设备信息，设备信息可以包括以下至少一项：设备类型、设备型号、设备版本、或设备厂商等，本申请实施例对此不限定。
S1302，手机1将音箱3注册到云平台。
其中，音箱3注册到云平台可以是云平台记录音箱3，为音箱3分配相应的标识，以及确定手机1的控制密钥，如密钥1(或者说第二控制密钥)。其中，密钥1可以用于手机1与音箱3建立会话(如控制会话)，以便手机1通过会话控制音箱3。以及，密钥1可以用于云平台确定其他控制密钥，如密钥3(或者说第一控制密钥)，用以除手机1外的其他设备(如手机2)与音箱3建立会话，以便其他设备通过会话控制音箱3，具体实现可以参考下述S1313，在此不再赘述。
具体而言，手机1可以向云平台发送音箱3的设备信息，以及上述用户A的标识，如账号标识。相应地，云平台可以根据音箱3的设备信息，确定音箱3是未注册的设备，从而为音箱3分配音箱3的标识以及上述密钥1，以完成音箱3的注册。之后，一方面，云平台可以建立用户A与音箱3的绑定关系，如用户A的标识与音箱3的标识的对应关系，从而确定用户A拥有音箱3的主控制权。另一方面，云平台可以向手机1发送，如打包发送或者分开发送音箱3的标识，以及密钥1，以便手机1也可以建立用户A与音箱3的绑定关系。
S1303，手机1通知音箱3绑定用户A。
其中，由于音箱3当前未绑定任何用户，则手机1在完成注册时，还可以通知音箱3绑定用户A。比如，手机1向音箱3发送用户A的标识、音箱3的标识以及密钥1(可承载在第二信息中)，以便音箱3可以根据用户A的标识，以及音箱3的标识，准确绑定其需要绑定的用户，即建立用户A与音箱3的绑定关系，如用户A的标识与音箱3的标识的对应关系，以避免误绑定。此外，由于用户A是首个绑定音箱3的用户，也即首个拥有音箱3的控制权(或者说主控制权)的用户。如此一来，如果后续 有其他用户想要控制音箱3，则音箱3可以根据用户A拥有主控制权，从而向其他用户发起控制权校验，而不需要向用户A发起控制权校验，从而避免误校验；也就是说，音箱3可不向拥有主控制权的用户发起控制权校验。
S1304，手机1向音箱3发送会话协商请求，音箱3接收来自手机1的会话协商请求。
其中，会话协商请求可以用于请求音箱3配合手机1建立控制会话(session)，如手机1与音箱3的控制会话，以便手机1后续可通过控制会话对音箱3进行控制。具体地，会话协商请求可以包括：用户A的标识，以及随机数(random number，RN)，如RN1。其中，RN1可以由手机1随机生成，用于音箱3生成控制会话的会话密钥，如密钥2，具体实现可以参考下述S1305中的相关介绍，在此不再赘述。
S1305，音箱3确定会话密钥。
音箱3接收到会话协商请求后，可以根据会话协商请求中用户A的标识，以及已建立的用户A与音箱3的绑定关系，确定当前请求建立控制会话的用户A的身份，即为拥有音箱3的主控制权的用户。如此，音箱3可以根据密钥1、会话协商请求中的RN1，以及RN2，确定会话密钥，如密钥2。其中，RN2可以由音箱3随机生成。
S1306，音箱3向手机1发送会话协商响应，手机1接收来自音箱3的会话协商响应。
其中。会话协商响应可以用于指示音箱3已接受手机1的请求，音箱3可以配合手机1建立控制会话。会话协商响应可包括RN2。
应理解，S1305与S1306中，音箱3确定会话密钥，与发送会话协商响应的执行顺序不限定。
S1307，手机1确定会话密钥。
手机1接收到会话协商响应后，可以根据密钥1、RN1、以及会话协商响应中的RN2，确定会话密钥，如密钥2。如此，手机1与音箱3便具有相同的会话密钥，从而可认为控制会话建立完成。之后，手机1与音箱3可以使用密钥2进行加密通信，以便音箱3可以响应手机1的控制，执行相应操作，如播放音频，调整播放音量等等。
应理解，上述S1304-S1307为建立控制会话的一种示例性方式，不作为限定，其他控制会话的建立方式也可以适用于本申请实施例。例如，手机1与音箱3还可以采用安全远程口令(secure remote password，SRP)协议建立控制会话。具体来说，上述密钥1可以认为是SRP协议中的口令，这样，手机1可以确定RN3，并根据RN3和口令，确定公私钥对，如公私(publickey)1和私钥(privatekey)1。同理，音箱3可以确定RN4，并根据RN4和口令，确定公私钥对，如公私2和私钥2。如此，手机1与音箱3可以互相交换各自的公钥，从而完成控制会话的建立。
此外，上述S1304-S1307为可选步骤，比如，在手机1绑定音箱3后，若需要控制音箱3，或者需要向音箱3传输数据，则可以执行S1304-S1307，否则，可以不执行S1304-S1307。
S1308，手机1向云平台发送授权信息，云平台接收来自手机1的授权信息。
其中，授权信息可以用于指示手机1将音箱3的控制权授权给用户B，可包括：用户B的标识，如账号标识，以及音箱3的标识。其中，用户B的标识可以是手机1 预先保存的标识，或者也可以是手机1实时获取的标识，如用户A输入用户B的标识。换言之，手机1可以发送用户B的标识和音箱3的标识，以指示将音箱3的控制权授权给用户B。
在一些实现方式中，步骤S1308的执行是由上述图5-图12所示的用户操作(如用户A的操作)触发的。
S1309，云平台确定用户B拥有音箱3的从控制权。
云平台接收到授权信息后，可以根据授权信息中用户B的标识，以及音箱3的标识，判断用户B拥有音箱3的主控制权，还是从控制权。其中，由于云平台记录有音箱3与用户A的绑定关系(或者说主绑定关系)，即用户A拥有音箱3的主控制权，则云平台可以确定用户B拥有音箱3的从控制权，并建立用户B(如用户B标识)与音箱3(如音箱3的标识)的绑定关系(或者说从绑定关系)。
S1310，云平台向手机2发送第一通知信息，手机2接收来自云平台的第一通知信息。
其中，第一通知信息可以用于指示手机2需要控制的设备为音箱3，可包括音箱3的标识。
可选地，云平台可以直接向手机2发送第一通知信息，或者也可以在手机2上线时，如登录云平台时，再向手机2发送第一通知信息，对此不限定。
S1311，手机2向音箱3发送控制请求，音箱3接收来自手机2的控制请求。
其中，控制请求(或者说第三信息)可以用于请求控制音箱3，可以包括：用户B的标识，以及音箱3的标识。
S1312，音箱3确定用户B拥有从控制权。
与云平台的判断原理类似，音箱3接收到控制请求后，可以根据控制请求中用户B的标识，判断用户B拥有音箱3的主控制权，还是从控制权。其中，由于音箱3已记录有音箱3与用户A的绑定关系，即用户A拥有音箱3的主控制权，则音箱3可以确定发起控制的用户不是拥有音箱3的主控制权的用户，即确定用户B拥有音箱3的从控制权。对于拥有音箱3的从控制权的用户，音箱3需要周期性地发起针对用户B的控制权校验，验证用户B当前是否仍然拥有音箱3的从控制权，以避免被用户B劫持，具体实现可以参考下述S1313-S1324中的相关介绍，在此不再赘述。
S1313，音箱3确定最新的控制密钥。
以第一个周期为例，在该周期开始之前，如开始之前的第一预设时间点，音箱3可以生成校验值，如随机生成校验值1，从而音箱3根据密钥1、用户B的标识以及校验值1，确定最新的控制密钥，如密钥3，以便音箱3可以根据密钥3，确定手机2是否能够获取相同的密钥，从而实现对用户B的控制权进行校验。
S1314，音箱3向手机2发送第一校验信息，手机2接收来自音箱3的第一校验信息。
仍以第一个周期为例，在该周期开始之前，如开始之前的第二预设时间点，音箱3向手机2发送第一校验信息(或者说第一信息)，用以通知手机2获取最新的控制密钥，如密钥3。其中，第一校验信息还可以包括上述校验值1。
应理解，第一预设时间点与第二预设时间点可以相同，也可以不同，对此不限定。
S1315，手机2向云平台发送第一校验请求，云平台接收来自手机2的第一校验请求。
其中，第一校验请求(或者说第四信息)可以用于请求云平台为手机2确定最新的控制密钥。第一校验请求可以包括：上述校验值1、音箱3的标识以及用户B的标识。此外，第一校验请求可以是手机2根据第一校验信息生成的。
S1316，云平台确定用户B有音箱3的从控制权。
云平台接收到第一校验请求后，可以根据第一校验请求中用户B的标识，判断用户B是否有音箱3的从控制权。其中，由于用户A此时没有在云平台上取消用户B的控制权授权，即云平台仍记录有用户B与音箱3的绑定关系，则云平台确定用户B拥有音箱3的从控制权，从而可以根据密钥1、用户B的标识以及校验值1，确定最新的控制密钥，如密钥3。
S1317，云平台向手机2发送最新的控制密钥，手机2接收来自云平台的最新的控制密钥。
如此，可实现用户B在拥有音箱3的控制权的情况下，继续控制音箱3。
应理解，S1317的发送时间点应当在第一个周期开始之前。也就是说，此外，上述第二预设时间点，与第一个周期开始时的时间间隔，需要满足S1317在第一个周期开始之前执行。
S1318，手机2和音箱3根据最新的控制密钥，建立第一个周期内的控制会话。
其中，S1318的具体实现可以参考上述S1305-S1307中的相关介绍。也就是说，手机2和音箱3建立控制会话的过程，与前述手机1和音箱3建立控制会话的过程，是类似的，因此在此不再赘述。
S1319，手机1向云平台发送授权取消信息，云平台接收来自手机1的授权取消信息。
其中，授权取消信息可以用于指示用户A需要取消用户B的控制权授权，可以包括用户A的标识、用户B的标识、以及音箱3的标识。换言之，授权取消信息可通过用户A的标识、用户B的标识、以及音箱3的标识，指示用户A需要取消用户B音箱3的控制权授权。相应地，云平台可以根据授权取消信息，删除用户B与音箱3的绑定关系，或者，确定用户B不再拥有音箱3的控制权。
在一些实现方式中，步骤S1319的执行是由上述图10中的(b)，或者图12中的(b)所示的用户操作(如用户A的操作)触发的。
S1320，音箱3更新控制密钥。
其中，在第二个周期开始之前，如开始之前的第三预设时间点，也即第一个周期结束前的某个时间点，音箱3可以继续生成校验值，如随机生成校验值2，从而根据密钥1、用户B的标识以及校验值2，以更新控制密钥，如将密钥3更新为密钥4，以便音箱3可以根据密钥4，确定手机2是否能够获取相同的密钥，从而实现继续对用户B的控制权进行校验。
S1321，音箱3向手机2发送第二校验信息，手机2接收来自音箱3的第二校验信息。
其中，在第二个周期开始之前，如开始之前的第四预设时间点，也即第一个周期 内对应的时间点，音箱3还可以向手机2发送第二校验信息(或者说第一信息)，用以通知手机2需要获取最新的控制密钥，如密钥4。第二校验信息还可以包括上述校验值2。
应理解，第三预设时间点与第四预设时间点可以相同，也可以不同，对此不限定。
S1322，手机2向云平台发送第二校验请求，云平台接收来自手机2的第二校验请求。
其中，第二校验请求(或者说第四信息)可以用于请求云平台为手机2确定最新的控制密钥。第二校验请求还可以包括：上述校验值2、音箱3的标识以及用户B的标识。此外，第二校验请求可以是手机2根据第二校验信息生成。
此外，S1319与S1320-S1322的执行顺序不限定。也就是说，S1319可以发生在S1323之前，即可以在云平台确定最新的控制密钥之前，取消用户B的控制权授权。
S1323，云平台确定用户B没有音箱3的从控制权。
其中，云平台接收到第二校验请求后，可以根据第二校验请求中用户B的标识，判断用户B是否还拥有音箱3的从控制权。其中，根据S1319中的相关介绍可知，由于用户A已经在云平台上取消用户B的控制权授权，即用户B与音箱3的从绑定关系已删除，则云平台可以确定用户B没有音箱3的控制权。
应理解，若云平台确定用户B没有音箱3的控制权，则不生成最新的控制密钥(如密钥4)，以避免误生成最新的控制密钥，如在用户A取消授权的情况下，仍生成最新的控制密钥。
S1324，云平台向手机2发送第二通知信息，手机2接收来自云平台的第二通知信息。
其中，第二通知信息可以用于通知用户B没有音箱3的从控制权。
应理解，S1324为可选步骤，即云平台可以主动通知用户B没有音箱3的从控制权；或者也可以不通知，如此，手机2可以基于超时，如在第二个周期开始时，仍未接收到来自云平台的控制密钥，确定用户B没有音箱3的从控制权。
S1325，音箱3断开与手机2的连接。
其中，若音箱3确定手机2未获取到密钥4，如在第二个周期开始时，仍未接收到来手机2的密钥4，则确定用户B没有音箱3的从控制权，从而可以主动断开与手机2的连接，以配合手机1取消授权。
此外，另一些实现方式中，手机2也可以主动断开与音箱3的连接，如根据第二通知信息，断开与手机2的连接。
应当指出，图13所示流程中，由于上述密钥1分别保存在音箱3和云平台本地，且音箱3和云平台均未向手机2发送密钥1，手机2自始至终未获取密钥1，因此手机2便无法根据密钥1自行确定最新的控制密钥(如密钥3、密钥4)，从而可以避免在手机2没有控制权的情况下，通过自行确定最新的控制密钥而劫持音箱3，进而可以提高授权的可靠性。
应理解，音箱3、云平台确定最新的控制密钥的方法，可以不同于图13实施例示例性展示的方法。即密钥3可以不是根据密钥1、用户B的标识、校验值1确定的，密钥4可以不是根据密钥1、用户B的标识、校验值2确定的。密钥3、密钥4还可 以是根据不同于图13实施例示例性展示的方法确定的，本申请实施例对密钥3、密钥4的确定方式不做限定。任意一种可由音箱3、云平台确定控制密钥而不可由手机1确定控制密钥的控制密钥确定方式，都不超出本申请实施例覆盖的范围。也就是说，若某种控制密钥确定方法，能够使得音箱3、云平台具备确定控制密钥的能力的同时，也使得手机2不具备确定控制密钥的能力，那么这种控制密钥确定方法就不超出本申请实施例覆盖的范围。
图14为本申请实施例提供的设备控制方法的流程示意图二，如图14所示，该设备控制方法可以应用于第一设备(上述音箱3)、第二设备(上述手机2)、第三设备(上述手机1)以及第四设备(上述云平台)，具体流程可以包括：
S1401，第三设备确定第二控制密钥。
其中，上述第二控制密钥用于第三设备与第一设备建立会话(如控制会话)，以便第三设备可以通过会话控制第一设备。以及，第二控制密钥还用于第一设备确定第一控制密钥，第一控制密钥用于除第三设备外的设备与第一设备建立会话，以便除第三设备外的设备可以通过会话控制第一设备。
作为一种可选方式，第三设备可以接收来自第四设备的第二控制密钥，或者第三设备可以自行确定第二控制密钥，对此不限定。
S1402，第三设备向第一设备发送第二信息，第一设备接收来自第三设备的第二信息。
其中，第二信息包括第二控制密钥，且第二信息用于指示第一设备绑定第三设备。如此，第一设备可以根据第二信息，绑定第三设备。比如，如果第一设备根据第二信息，确定未建立第一设备的对应关系，即第一设备当前没有绑定其他设备，则建立第一设备与第三设备的第一对应关系，即绑定第三设备。换言之，第三设备是首个绑定第一设备的设备，也即首个拥有第一设备的控制权(或者说主控制权)的设备。如此一来，如果后续有其他设备想要控制第一设备，则第一设备可以根据第三设备拥有主控制权，从而向其他设备发起控制权校验，而不是向第三设备发起控制权校验，从而避免误校验。
作为第一设备绑定第三设备的一种实现方式，第二信息还可以包括：第三设备的标识和第一用户的标识。如此，第一设备可以根据第二信息，准确绑定其需要绑定的设备，如建立第三设备的标识与第三设备对应的用户，如第一用户的标识的第一对应关系，以避免误绑定。此外，需要指出的是，第一设备绑定第三设备为绑定该第三设备对应的第一用户的标识(如第一用户的账号)。这种情况下，如果第一用户使用不同设备登录同一账号，则其仍然可以通过第一用户的绑定关系控制第一设备，无需第一用户重新注册和重新绑定，从而可以提高用户的使用体验。
应理解，第三设备向第一设备发送第二信息之后，第三设备还可以向第四设备发送第五信息。其中，第五信息用于指示第三设备将第一设备的控制权授权给第二设备。
如此，一方面，第四设备可以根据第五信息，绑定第一设备与第二设备，从而确定第二设备有第一设备的控制权。具体而言，第四设备可以根据第五信息，确定第一设备与第二设备的第二对应关系。其中，第二对应关系可以用于指示第一设备的标识与第二用户的标识对应。换言之，第一设备绑定第二设备为绑定该第二设备对应的第 一用户的标识(如第二用户的账号)。这种情况下，如果第二用户使用不同设备登录同一账号，则其仍然可以通过第二用户的绑定关系控制第一设备，无需第一用户重新授权，从而可以提高用户的使用体验。
另一方面，第四设备还可以通知第二设备，以便第二设备可以向第一设备发送第三信息。其中，第三信息可以用于第二设备请求控制第一设备，可以包括：第二用户的标识和第一设备的标识，该第二用户可以为第二设备对应的用户。
S1403，第一设备向第二设备发送第一信息，第二设备接收来自第一设备的第一信息。
其中，第一信息用于通知第二设备获取第一控制密钥，或者说用于第一设备发起对第二设备的控制权进行校验。第一信息可以包括校验值，该校验值可以用于确定第一控制密钥。
具体来说，对于第一设备而言，由于第一设备已绑定第三设备，第一设备接收到第三信息后，可确定第三信息中第一设备的标识对应的第二用户的标识，与第一对应关系中第一设备的标识对应的第一用户的标识不同，从而确定第二设备不是首个拥有第一设备的控制权的设备，进而确定向第二设备发起控制权校验，而不是向其他设备发起控制权校验，从而可以避免误校验。
S1404，第二设备向第四设备发送第四信息，第四设备接收来自第三设备的第四信息。
其中，第四信息用于请求第四设备确定第一控制密钥。第四信息可以包括：第一设备的标识、第二用户的标识以及校验值。
S1405，第四设备解析第四信息。
其中，第四设备可以根据第四信息，确定第二设备是否有第一设备的控制权。
具体而言，在第四设备保存有上述第一对应关系的情况下，第四设备可确定第四信息中第一设备的标识对应的第二用户的标识，与第一对应关系中第一设备的标识对应的第一用户的标识不同，从而确定第二用户不是首个拥有第一设备的控制权的设备。如此，第四设备可以进一步确定第二用户是否有第一设备的控制权，或者说第一用户是否取消第一设备的控制权授权，从而根据第一设备是否取消授权，确定是否生成第二控制密钥，以避免误生成第二控制密钥，如在第一设备取消授的情况下，仍生成第二控制密钥。
比如，若第二设备在确定第二用户是否有第一设备的控制权之前，接收到来自第一设备的第六信息。其中，第六信息可以用于指示第三设备取消将第一设备的控制权授权给第二设备。相应地，第四设备可以根据第六信息，第一设备与第二设备取消绑定，如删除第一设备与第二设备的第二对应关系。如此，第二设备在确定第二用户是否有第一设备的控制权，可以根据第一设备未绑定第二设备，确定第二设备没有第一设备的控制权，从而不为第二设备确定第一控制密钥，以便第二设备无法继续控制第一设备，避免第二设备劫持第一设备。并且，可选地，第四设备可以向第二设备发送第七信息，用以指示第二设备没有第一设备的控制权。
S1406，若第一设备确定第二设备未获取第一控制密钥，则断开与第二设备的连接。
应理解，上述S1405-S1406是以第二设备没有第一设备的控制权为例，但不限定。 比如，若第二设备在确定第二用户是否有第一设备的控制权之前，为接收到来自第一设备的第六信息，则第四设备确定第二设备有第一设备的控制权，即第一设备已绑定第二设备，从而确定第一控制密钥，如根据校验值、第二控制密钥以及第二用户的标识确定第一控制密钥。如此，第四设备可以向第二设备发送第一控制密钥，以便第二设备向第一设备转发第一控制密钥。
进一步地，对于第一设备而言，由于第一设备也可根据校验值、第二控制密钥以及第二用户的标识确定第一控制密钥。如此，第一设备可以确定来自第二设备的第一控制密钥，与自身确定的第一控制密钥相同，从而确定第二设备获取第一控制密钥，进而保持与第二设备的连接，以实现第二设备在拥有第一设备的控制权的情况下，可以继续控制第一设备。
还应理解，由于第二控制密钥分别保存在第一设备和第四设备本地，且第一设备和第四设备均未向第二设备发送第二控制密钥，使得第二设备无法自行确定第一控制密钥，从而可以避免在第二设备没有控制权的情况下，通过自行确定第一控制密钥而劫持第一设备。
综上，根据图14所述的设备控制方法可知，在某个IoT设备(如第一设备)已绑定某个设备(如第三设备)，即第三设备已拥有第一设备的控制权的情况，如果另一个设备，如第二设备想要继续控制第一设备，则第一设备可以向第二设备发起控制权校验，即发送第一信息，用以指示第二设备获取最新的控制密钥(如第一控制密钥)。如此一来，如果第二设备未获取第一控制密钥，即没有第一设备的控制权，则第一设备可以断开与第二设备的连接，以避免第一设备被第二设备劫持。
如图15所示，本申请实施例公开了一种电子设备，例如上述实施例中的手机1、手机2或音箱3。该电子设备具体可以包括：显示屏1507；一个或多个处理器1502；存储器1503；通信模块1508；一个或多个应用程序(未示出)；以及一个或多个计算机程序1504，上述各器件可以通过一个或多个通信总线1505连接。其中，该一个或多个计算机程序1504被存储在上述存储器1503中并被配置为被该一个或多个处理器1502执行，该一个或多个计算机程序1504包括指令，该指令可以用于执行上述实施例中手机执行的相关步骤。该电子设备还可以包括触摸传感器1506(触摸传感器1506与显示屏1507可集成为触摸屏1501)、鼠标等输入设备。
示例性地，本申请实施例公开了一种芯片系统。该芯片系统应用于包括存储器和通信模块的电子设备；芯片系统包括一个或多个接口电路和一个或多个处理器；接口电路和处理器通过线路互联；接口电路用于从电子设备的存储器接收信号，并向处理器发送信号，信号包括存储器中存储的计算机指令；当处理器执行计算机指令时，电子设备执行上述设备控制方法。
应理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况，其中A,B可以是单数或者复数。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系，但也可能表示的是一种“和/或”的关系，具体可参考前后文进行理解。
本申请中，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“以 下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a,b,或c中的至少一项(个)，可以表示：a,b,c,a-b,a-c,b-c,或a-b-c，其中a,b,c可以是单个，也可以是多个。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将装置的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。上述描述的系统，装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请实施例各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
上述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请实施例的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)或处理器执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：快闪存储器、移动硬盘、只读存储器、随机存取存储器、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请实施例的具体实施方式，但本申请实施例的保护范围并不局限于此，任何在本申请实施例揭露的技术范围内的变化或替换，都应涵盖在本申请实施例的保护范围之内。因此，本申请实施例的保护范围应以所述权利要求的保护范围为准。

Claims (32)

  1. 一种设备控制方法，其特征在于，包括：
    第一设备向第二设备发送第一信息，其中，所述第一设备已绑定第三设备，所述第一信息用于通知所述第二设备获取第一控制密钥，所述第一控制密钥用于所述第二设备与所述第一设备建立会话；
    若所述第一设备确定所述第二设备未获取所述第一控制密钥，则断开与所述第二设备的连接。
  2. 根据权利要求1所述的方法，其特征在于，在所述第一设备向第二设备发送第一信息之前，所述方法还包括：
    所述第一设备接收来自所述第三设备的第二信息，其中，所述第二信息用于指示所述第一设备需要绑定所述第三设备；
    所述第一设备根据所述第二信息，绑定所述第三设备。
  3. 根据权利要求2所述的方法，其特征在于，所述第一设备根据所述第二信息，绑定所述第三设备，包括：
    所述第一设备根据所述第二信息，确定未建立第一设备的对应关系；
    所述第一设备建立所述第一设备与所述第三设备的第一对应关系。
  4. 根据权利要求3所述的方法，其特征在于，所述第二信息包括：所述第一设备的标识、第一用户的标识、以及第二控制密钥，其中，所述第一用户为所述第三设备对应的用户，所述第一设备的对应关系为所述第一设备的标识与用户的标识的对应关系，所述第一对应关系为所述第一设备的标识与所述第一用户的标识的对应关系，所述第二控制密钥用于所述第三设备与所述第一设备建立会话。
  5. 根据权利要求1-4中任一项所述的方法，其特征在于，在所述第一设备向第二设备发送第一信息之前，所述方法还包括：
    所述第一设备接收来自所述第二设备的第三信息，其中，所述第三信息用于所述第二设备请求控制所述第一设备。
  6. 根据权利要求5所述的方法，其特征在于，所述第三信息包括：第二用户的标识和所述第一设备的标识，所述第二用户为所述第二设备对应的用户。
  7. 根据权利要求1-3中任一项所述的方法，其特征在于，所述第一信息包括：校验值，所述校验值用于确定所述第一控制密钥。
  8. 根据权利要求7所述的设备控制方法，其特征在于，所述第一控制密钥为根据所述校验值、第二控制密钥以及第二用户的标识确定，所述第二控制密钥用于所述第三设备与所述第一设备建立会话，所述第二用户为所述第二设备对应的用户。
  9. 一种设备控制方法，其特征在于，包括：
    第二设备接收来自第一设备的第一信息，其中，所述第一信息用于通知所述第二设备获取第一控制密钥，所述第一控制密钥用于所述第二设备与所述第一设备建立会话；
    所述第二设备向第四设备发送第四信息，其中，所述第四信息用于请求所述第四设备确定所述第一控制密钥。
  10. 根据权利要求9所述的方法，其特征在于，所述第一信息包括：校验值，所述 校验值用于所述第四设备确定所述第一控制密钥。
  11. 根据权利要求10所述的方法，其特征在于，所述第四信息包括：所述第一设备的标识、第二用户的标识以及所述校验值，其中，所述第二用户为所述第二设备对应的用户。
  12. 根据权利要求11所述的方法，其特征在于，在所述第二设备向第四设备发送所述第四信息之后，所述方法还包括：
    所述第二设备接收来自所述第四设备的所述第一控制密钥；
    所述第二设备向所述第一设备发送所述第一控制密钥。
  13. 根据权利要求9-12任一项所述的方法，其特征在于，在所述第二设备接收来自第一设备的第一信息之前，所述方法还包括：
    所述第二设备向所述第一设备发送的第三信息，其中，所述第三信息用于所述第二设备请求控制所述第一设备。
  14. 根据权利要求13所述的方法，其特征在于，所述第三信息包括：第二用户的标识和所述第一设备的标识，所述第二用户为所述第二设备对应的用户。
  15. 一种设备控制方法，其特征在于，包括：
    第三设备确定第二控制密钥，其中，所述第二控制密钥用于所述第三设备与第一设备建立会话，以及还用于所述第一设备确定第一控制密钥，所述第一控制密钥用于除所述第三设备外的设备与所述第一设备建立会话；
    所述第三设备向所述第一设备发送第二信息，其中，所述第二信息包括所述第二控制密钥，且所述第二信息用于指示所述第一设备绑定所述第三设备。
  16. 根据权利要求15所述的方法，其特征在于，所述第二信息包括：所述第三设备的标识和第一用户的标识，所述第一用户为第三设备对应的用户。
  17. 根据权利要求15或16所述的方法，其特征在于，在所述第三设备向第一设备发送第二信息之后，所述方法还包括：
    所述第三设备向第四设备发送第五信息，其中，所述第五信息用于指示所述第三设备将第一设备的控制权授权给第二设备。
  18. 根据权利要求17所述的方法，其特征在于，在所述第三设备向所述第四设备发送第五信息之后，所述方法还包括：
    所述第三设备向所述第四设备发送第六信息，其中，所述第六信息用于指示所述第三设备取消将所述控制权授权给所述第二设备。
  19. 一种设备控制方法，其特征在于，包括：
    第四设备接收来自第二设备的第四信息，其中，所述第四信息用于请求所述第四设备确定第一控制密钥，所述第一控制密钥用于所述第二设备与第一设备建立会话，所述第一设备已绑定第三设备；
    所述第四设备解析所述第四信息。
  20. 根据权利要求19所述的方法，其特征在于，在所述第四设备解析所述第四信息之后，所述方法还包括：
    若所述第四设备根据所述第四信息，确定所述第二设备有所述第一设备的控制权，则根据所述第四信息，确定所述第一控制密钥；
    所述第四设备向所述第二设备发送所述第一控制密钥。
  21. 根据权利要求20所述的方法，其特征在于，所述第四信息包括所述第一设备的标识、第二用户的标识以及校验值，所述第一控制密钥为根据所述校验值、第二控制密钥以及所述第二用户的标识确定，所述第二控制密钥用于所述第三设备与所述第一设备建立会话，所述第二用户为所述第二设备对应的用户。
  22. 根据权利要求20或21所述的方法，其特征在于，所述第二设备有所述第一设备的控制权是指：所述第一设备已绑定所述第二设备。
  23. 根据权利要求21所述的方法，其特征在于，在所述第四设备确定所述第二设备有所述第一设备的控制权之前，所述方法还包括：
    所述第四设备接收来自所述第三设备的第五信息，其中，所述第五信息用于指示所述第三设备将控制权授权给所述第二设备，所述控制权为第一设备的控制权；
    所述第四设备根据所述第五信息，将所述第一设备与所述第二设备绑定。
  24. 根据权利要求23所述的方法，其特征在于，所述第四设备根据所述第五信息，将所述第一设备与所述第二设备绑定，包括：
    所述第四设备根据所述第五信息，确定所述第一设备与所述第二设备的第二对应关系，其中，所述第二对应关系用于指示所述第一设备的标识与所述第二用户的标识对应。
  25. 根据权利要求19所述的方法，其特征在于，在所述第四设备解析所述第四信息之后，所述方法还包括：
    若所述第四设备根据所述第四信息，确定所述第二设备没有所述第一设备的控制权，则向所述第二设备发送第七信息，所述第七信息用于指示所述第二设备没有所述第一设备的控制权。
  26. 根据权利要求25所述的方法，其特征在于，所述第二设备没有所述第一设备的控制权是指：所述第一设备未绑定所述第二设备。
  27. 根据权利要求25或26所述的方法，其特征在于，在所述第四设备确定所述第二设备没有所述第一设备的控制权之前，所述方法还包括：
    所述第四设备接收来自所述第三设备的第六信息，其中，所述第六信息用于指示所述第三设备取消将所述控制权授权给所述第二设备；
    所述第四设备根据所述第六信息，将所述第一设备与所述第二设备取消绑定。
  28. 根据权利要求27所述的方法，其特征在于，所述第四设备根据所述第六信息，将所述第一设备与所述第二设备取消绑定，包括：
    所述第四设备根据所述第六信息，删除所述第一设备与所述第二设备的第二对应关系，其中，所述第二对应关系用于指示所述第一设备的标识与第二用户的标识对应，所述第二用户为所述第二设备对应的用户。
  29. 一种电子设备，其特征在于，所述电子设备包括：
    一个或多个处理器；
    存储器；
    通信模块；
    其中，所述存储器中存储有一个或多个计算机程序，所述一个或多个计算机程序 包括指令，当所述指令被所述电子设备执行时，使得所述电子设备执行如权利要求1-8中任一项所述的方法，或者，执行如权利要求9-14中任一项所述的方法，或者，执行如权利要求15-18中任一项所述的方法，或者，执行如权利要求19-28中任一项所述的方法。
  30. 一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，其特征在于，当所述指令在电子设备上运行时，使得所述电子设备执行如权利要求1-8中任一项所述的方法，或者，执行如权利要求9-14中任一项所述的方法，或者，执行如权利要求15-18中任一项所述的方法，或者，执行如权利要求19-28中任一项所述的方法。
  31. 一种计算机程序产品，其特征在于，所述计算机程序产品包括：计算机程序或指令，当所述计算机程序或指令在计算机上运行时，使得所述计算机执行如权利要求1-8中任一项所述的方法，或者，执行如权利要求9-14中任一项所述的方法，或者，执行如权利要求15-18中任一项所述的方法，或者，执行如权利要求19-28中任一项所述的方法。
  32. 一种芯片系统，其特征在于，所述芯片系统应用于包括存储器和通信模块的电子设备；所述芯片系统包括一个或多个接口电路和一个或多个处理器；所述接口电路和所述处理器通过线路互联；所述接口电路用于从所述电子设备的存储器接收信号，并向所述处理器发送所述信号，所述信号包括所述存储器中存储的计算机指令；当所述处理器执行所述计算机指令时，所述电子设备执行如权利要求1-8中任一项所述的方法，或者，执行如权利要求9-14中任一项所述的方法，或者，执行如权利要求15-18中任一项所述的方法，或者，执行如权利要求19-28中任一项所述的方法。
PCT/CN2022/084073 2021-06-30 2022-03-30 设备控制方法及装置 WO2023273458A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP22831289.8A EP4336801A1 (en) 2021-06-30 2022-03-30 Device control method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110736672.9A CN115567565A (zh) 2021-06-30 2021-06-30 设备控制方法及装置
CN202110736672.9 2021-06-30

Publications (1)

Publication Number Publication Date
WO2023273458A1 true WO2023273458A1 (zh) 2023-01-05

Family

ID=84692444

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/084073 WO2023273458A1 (zh) 2021-06-30 2022-03-30 设备控制方法及装置

Country Status (3)

Country Link
EP (1) EP4336801A1 (zh)
CN (1) CN115567565A (zh)
WO (1) WO2023273458A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060159268A1 (en) * 2005-01-20 2006-07-20 Samsung Electronics Co., Ltd. Method and system for device authentication in home network
CN105141584A (zh) * 2015-07-29 2015-12-09 宇龙计算机通信科技(深圳)有限公司 一种智能家居系统的设备认证方法及装置
WO2017053048A1 (en) * 2015-09-25 2017-03-30 Pcms Holdings, Inc. Domain based iot authorization and authentication
CN108712246A (zh) * 2018-03-27 2018-10-26 王晓华 一种智能家居设备和系统以及访客密码获取方法
CN110706379A (zh) * 2019-09-20 2020-01-17 广州广电运通金融电子股份有限公司 基于区块链的门禁访问控制方法和装置
CN112987581A (zh) * 2019-12-16 2021-06-18 华为技术有限公司 用于智能家居设备的控制方法及其介质和终端

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060159268A1 (en) * 2005-01-20 2006-07-20 Samsung Electronics Co., Ltd. Method and system for device authentication in home network
CN105141584A (zh) * 2015-07-29 2015-12-09 宇龙计算机通信科技(深圳)有限公司 一种智能家居系统的设备认证方法及装置
WO2017053048A1 (en) * 2015-09-25 2017-03-30 Pcms Holdings, Inc. Domain based iot authorization and authentication
CN108712246A (zh) * 2018-03-27 2018-10-26 王晓华 一种智能家居设备和系统以及访客密码获取方法
CN110706379A (zh) * 2019-09-20 2020-01-17 广州广电运通金融电子股份有限公司 基于区块链的门禁访问控制方法和装置
CN112987581A (zh) * 2019-12-16 2021-06-18 华为技术有限公司 用于智能家居设备的控制方法及其介质和终端

Also Published As

Publication number Publication date
EP4336801A1 (en) 2024-03-13
CN115567565A (zh) 2023-01-03

Similar Documents

Publication Publication Date Title
WO2021147745A1 (zh) 蓝牙连接方法、系统和电子设备
US11979251B2 (en) Home device control method and device
US9730268B2 (en) Communication between host and accessory devices using accessory protocols via wireless transport
CN109905318B (zh) 设备控制方法、装置及存储介质
US10608988B2 (en) Method and apparatus for bluetooth-based identity recognition
CN113360108B (zh) 一种投屏连接控制方法及电子设备
WO2020042119A1 (zh) 一种消息传输方法及设备
KR20200112299A (ko) 계정 관련 정보에 기반하여 장치를 설정하는 방법 및 그 전자 장치
CN107147656B (zh) 远程控制的建立方法、系统及可读存储介质
WO2021093855A1 (zh) 一种移动设备管理方法及设备
WO2020216160A1 (zh) 一种se的自动路由方法及电子设备
US11089443B2 (en) Electronic device and method for connecting short range communication
KR20210051932A (ko) 블루투스 연결 정보 공유를 통한 소스 기기 전환 방법 및 장치
CN113365274B (zh) 一种网络接入方法和电子设备
WO2021227942A1 (zh) 一种分享信息的方法、电子设备和系统
US10834595B2 (en) Service providing apparatus configured to control communication mode between communication terminals, service communicating system, service providing method and recording medium configured to perform same
WO2023273458A1 (zh) 设备控制方法及装置
WO2023098468A1 (zh) 设备注册方法、中枢设备及装置
EP4344162A1 (en) Information processing method, device, and storage medium
WO2022161071A1 (zh) 一种群组成员或好友的添加方法、电子设备
WO2021051964A1 (zh) 配对方法及设备
WO2023025059A1 (zh) 一种通信系统及通信方法
WO2023029990A1 (zh) 蓝牙连接方法及电子设备
WO2021037208A1 (zh) 一种蓝牙连接的方法和电子设备
WO2023185593A1 (zh) 设备登录方法、电子设备及系统

Legal Events

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

Ref document number: 22831289

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2022831289

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2022831289

Country of ref document: EP

Effective date: 20231205

NENP Non-entry into the national phase

Ref country code: DE