WO2022056878A1 - 控制方法、设备及存储介质 - Google Patents

控制方法、设备及存储介质 Download PDF

Info

Publication number
WO2022056878A1
WO2022056878A1 PCT/CN2020/116316 CN2020116316W WO2022056878A1 WO 2022056878 A1 WO2022056878 A1 WO 2022056878A1 CN 2020116316 W CN2020116316 W CN 2020116316W WO 2022056878 A1 WO2022056878 A1 WO 2022056878A1
Authority
WO
WIPO (PCT)
Prior art keywords
binding relationship
account
chip device
configuration device
chip
Prior art date
Application number
PCT/CN2020/116316
Other languages
English (en)
French (fr)
Inventor
包永明
茹昭
吕小强
Original Assignee
Oppo广东移动通信有限公司
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 Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to PCT/CN2020/116316 priority Critical patent/WO2022056878A1/zh
Priority to EP20953736.4A priority patent/EP4216512A4/en
Priority to CN202080103396.6A priority patent/CN116114235A/zh
Publication of WO2022056878A1 publication Critical patent/WO2022056878A1/zh
Priority to US18/146,157 priority patent/US20230208716A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0894—Policy-based network configuration management
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/03—Protecting confidentiality, e.g. by encryption
    • H04W12/033—Protecting confidentiality, e.g. by encryption of the user plane, e.g. user's traffic
    • 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/041—Key generation or derivation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/30—Security of mobile devices; Security of mobile applications
    • H04W12/35—Protecting application or service provisioning, e.g. securing SIM application provisioning

Definitions

  • the present invention relates to the Internet of Things technology, and in particular, to a control method, device and storage medium, wherein the device involved in the present invention includes at least one of the following: a CHIP device, a configuration device and a server.
  • an IP connected home (Connected Home Over IP, CHIP) device can only be configured by a configuration device using the account, that is, only one account can be bound. Since only the configuration device using the bound account has the right to configure the CHIP device, after the CHIP device has a binding relationship with an account, the CHIP device cannot be configured by the configuration device using other accounts .
  • CHIP Connected Home Over IP
  • Embodiments of the present invention provide a control method, device, and storage medium, which can realize switching of configuration devices.
  • an embodiment of the present invention provides a control method, including:
  • the first binding relationship with the first account is established by connecting the home CHIP device through the Internet protocol, the conditions for releasing the original binding relationship are satisfied, the first binding relationship is released, and the second binding relationship is established with the second account. relationship to configure the CHIP device by a second configuration device using the second account.
  • an embodiment of the present invention provides a control method, including:
  • the first configuration device receives a request for releasing the original binding relationship for instructing to release the first binding relationship;
  • the first binding relationship is the binding relationship between the CHIP device and the first account used by the first configuration device;
  • the first configuration device releases the stored first binding relationship, so that the CHIP device can establish a second binding relationship with the second account, so that the second configuration device using the second account can establish a second binding relationship with the second account. Configure the CHIP device.
  • an embodiment of the present invention provides a control method, including:
  • the second configuration device distributes the network to the CHIP device
  • the second configuration device sends an indication of releasing the original binding relationship to the CHIP device; instructing the CHIP device to release the first binding relationship, and establishing a second binding relationship with the second account used by the second configuration device, so that the CHIP device can be configured by the second configuration device .
  • an embodiment of the present invention provides a control method, including:
  • the server receives the original binding relationship deletion request; the server deletes the first binding relationship between the CHIP device and the first account; the terminal device satisfies the release of the original binding relationship when the first binding relationship is established condition, release the first binding relationship, and establish a second binding relationship with the second account, so that the terminal device is configured by the second configuration device using the second account.
  • an embodiment of the present invention provides a CHIP device, including:
  • a release module configured to release the first binding relationship and establish a second binding relationship with the second account when the first binding relationship with the first account is established and the conditions for releasing the original binding relationship are satisfied
  • the CHIP device is configured with a second configuration device using the second account.
  • an embodiment of the present invention provides a CHIP device, including:
  • the second receiving module is configured to receive a request for releasing the original binding relationship for instructing to release the first binding relationship;
  • the first binding relationship is the binding between the CHIP device and the first account used by the first configuration device relation;
  • An execution module configured to release the stored first binding relationship, so that the CHIP device can establish a second binding relationship with a second account, so that the CHIP device can be configured with the second account using the second account. device to configure.
  • an embodiment of the present invention provides a configuration device, including:
  • Distribution network module configured to distribute network to CHIP equipment
  • the third sending module is configured to send an indication of releasing the original binding relationship to the CHIP device when it is determined that the CHIP device has established a first binding relationship with the first account, the indication of releasing the original binding relationship It is used to instruct the CHIP device to release the first binding relationship and establish a second binding relationship with the second account used by the second configuration device, so that the CHIP device can be performed by the second configuration device. configuration.
  • an embodiment of the present invention provides a server, including:
  • a fourth receiving module configured to receive the original binding relationship deletion request
  • a deletion module configured to delete the first binding relationship between the CHIP device and the first account; when the terminal device has established the first binding relationship, it satisfies the conditions for releasing the original binding relationship, and the first binding relationship is released.
  • a binding relationship is established, and a second binding relationship is established with the second account, so that the terminal device is configured by the second configuration device using the second account.
  • an embodiment of the present invention provides a CHIP device, comprising a processor and a memory for storing a computer program that can be run on the processor, wherein the processor is configured to execute the above CHIP when running the computer program The steps of the control method performed by the device.
  • an embodiment of the present invention provides a configuration device, including a processor and a memory for storing a computer program that can be run on the processor, wherein the processor is configured to execute the above configuration when running the computer program The steps of the control method performed by the device.
  • an embodiment of the present invention provides a server, including a processor and a memory for storing a computer program that can be executed on the processor, wherein the processor is configured to execute the server when the computer program is executed. Execute the steps of the control method.
  • an embodiment of the present invention provides a storage medium that stores an executable program, and when the executable program is executed by a processor, implements the above-mentioned control method for executing a CHIP device.
  • an embodiment of the present invention provides a storage medium that stores an executable program, and when the executable program is executed by a processor, implements the above-mentioned control method executed by a configuration device.
  • an embodiment of the present invention provides a storage medium storing an executable program, and when the executable program is executed by a processor, the above-mentioned control method for server execution is implemented.
  • the control method provided by the embodiment of the present invention includes: when a CHIP device has established a first binding relationship with a first account, and satisfies a condition for releasing the original binding relationship, cancels the first binding relationship, and communicates with the second account.
  • the account establishes a second binding relationship to configure the CHIP device by a second configuration device using the second account. Because the CHIP device releases the original binding relationship in the IoT system before establishing the binding relationship with the new account, so as to ensure the establishment of a new binding relationship, so that the CHIP device can be configured by the new configuration device.
  • FIG. 1 is an optional schematic flowchart of a CHIP device access platform provided by an embodiment of the present invention
  • FIG. 2 is an optional schematic structural diagram of an Internet of Things system provided by an embodiment of the present invention.
  • FIG. 3 is an optional schematic structural diagram of an Internet of Things system provided by an embodiment of the present invention.
  • FIG. 6 is an optional schematic flowchart of a control method provided by an embodiment of the present invention.
  • FIG. 11 is an optional schematic flowchart of a control method provided by an embodiment of the present invention.
  • FIG. 13 is an optional schematic flowchart of a control method provided by an embodiment of the present invention.
  • 16 is an optional schematic structural diagram of a configuration device provided by an embodiment of the present invention.
  • FIG. 17 is an optional schematic structural diagram of a configuration device provided by an embodiment of the present invention.
  • FIG. 18 is an optional schematic structural diagram of a server provided by an embodiment of the present invention.
  • FIG. 19 is an optional schematic structural diagram of an electronic device provided by an embodiment of the present invention.
  • the platform assigns an operation identifier to a CHIP device, and establishes an association relationship between the assigned operation identifier and the account to be bound, so as to establish a binding relationship between the CHIP device and the account.
  • the CHIP device is bound with the account, and secure communication is performed between the CHIP device and the configuration device using the account.
  • a CHIP device can only be bound to one account at a time, and the CHIP device can only be configured by the configuration device using the bound account.
  • the binding of the CHIP device and the account is performed during the process of the CHIP device accessing the platform.
  • the platform is an information processing system running on a server, and different platforms may be independent of each other. Among them, for the same CHIP device, applications of different shopping malls can be run, and the platform of the merchant only supports the access of the applications of the merchant.
  • the platform is the cloud platform of the ecological cloud.
  • the CHIP device generates a key
  • the CHIP device When the CHIP device leaves the factory, it calculates the Personal Identification Number Code (PIN Code) according to the key derivation algorithm, generates a secret, and stores the generated secret into the CHIP device.
  • PIN Code Personal Identification Number Code
  • the key derivation algorithm may be a Password-Based Key Derivation Function (PBKDF).
  • PBKDF Password-Based Key Derivation Function
  • the user gets the CHIP device and can scan the QR code on the CHIP device through the APP on the configuration device to obtain the PIN Code of the CHIP device.
  • the CHIP device does not have a QR code
  • the user can also manually enter the PIN Code on the configuration device.
  • the APP on the configuration device assumes the role of the configurator of the CHIP device.
  • the CHIP device side After configuring the device to generate the key, encrypt the data communicated with the CHIP device through the password-based Authentication Key Exchange (PAKE) algorithm according to the generated secret, and the CHIP device side verifies the data through PAKE according to the secret. to establish a secure channel between the configuration device and the CHIP device for secure communication.
  • PAKE password-based Authentication Key Exchange
  • steps S104 to S105 perform secure communication based on the established secure channel.
  • S104 configure the device to distribute the network to the CHIP device
  • the configuration device sends the service set identifier (SSID) and password of the access point (Access Point, AP) to the CHIP device, and the CHIP device passes the received SSID and The password is successfully connected to the AP, and the AP assigns information such as IP addresses to the connected CHIP devices, so that the CHIP devices can access the AP and access the platform on the network side through the AP.
  • SSID service set identifier
  • AP access point
  • the CHIP device and the configuration device perform secure communication according to the certificate.
  • the execution of S105 includes:
  • the configuration device sends a request for obtaining an Operational Certificate Signing Request (OpCSR) to the CHIP device;
  • OpCSR Operational Certificate Signing Request
  • the request sent by the configuration device carries a nonce.
  • the CHIP device generates an OpCSR, and signs the OpCSR;
  • the CHIP device generates an operation key pair (Op Key Pair) including an operation public key and an operation private key (Op Private Key), and forms an OpCSR.
  • OpCSR includes: the operation public key of the CHIP device, the announcement sent by the configuration device, and the information that the CHIP device needs to be authenticated; wherein, the information that the CHIP device needs to be authenticated includes: Product Attestation (PA) certificate, PA Intermediate certificates, device authentication blocks, and the PA certificate carry the authentication public key.
  • PA Product Attestation
  • the CHIP device After the CHIP device forms the OpCSR, use the CHIP device operation private key to sign the OpCSR once, and then use the CHIP device authentication private key (Att Private Key) to sign the OpCSR once signed.
  • the CHIP device returns the OpCSR data to the mobile phone.
  • the CHIP device After the CHIP device completes the signature, it sends the OpCSR and the data signed by the OpCSR to the configuration device.
  • the OpCSR and the data signed by the OpCSR are called OpCSR data.
  • S1054 configure the device to verify the validity of the authentication.
  • the configuration device After the configuration device obtains the OpCSR data, it uses the authentication public key stored in the PA certificate of the CHIP device to verify the validity of the authentication (Attestation). Wherein, this step is an optional step.
  • S1055 configure the device to send the OpCSR data to the server.
  • the configuration device sends the OpCSR and the data signed by the OpCSR to the implementation server, where the server runs the platform to which the APP of the configuration device belongs.
  • the platform can be a cloud platform, that is, an ecological cloud.
  • the server verifies the CHIP device, and after the verification passes, generates an operation identifier (Op ID) and an operation certificate (Op Cert);
  • the server verifies whether the CHIP device holds the operation private key by operating the public key, so as to perform operation verification on the CHIP device. After the operation verification is successful, the server will generate Op ID and Op Cert for the CHIP device.
  • the server may further verify the validity of the authentication by using the authentication public key. It should be noted that when the configuration device side performs authentication validity verification, the server side does not perform authentication validity verification. When the validity verification of the authentication is not performed on the configuration device side, the validity verification of the authentication can be performed on the server side.
  • the server After generating the Op ID for the CHIP device, the server establishes an association relationship between the Op ID and the account used by the configuration device, thereby binding the CHIP device and the account of the configuration device.
  • Op ID is used for the platform to identify the CHIP device.
  • the account used by the configuration device is used for the configuration device to access the account under the platform running on the server.
  • the server returns the Op ID, Op Cert, and Operation Intermediate Certificate (s), ICs) to the configuration device;
  • S1058 configure the device to send the Op ID, Op Cert and ICs to the CHIP device;
  • the CHIP device checks whether the Op Cert matches the authentication public key, and stores the Op ID, Op Cert and ICs when matching.
  • the CHIP device verifies the Op Cert through the authentication private key.
  • the configuration terminal in FIG. 1 may be a terminal that can configure the CHIP device, such as a mobile terminal,
  • a CHIP device is an IoT device that can access a home network based on an IP address and implement some of the most basic functions, such as switches, door locks, refrigerators, etc.
  • the CHIP device after the CHIP device is bound to the account of the current configuration device, it can only be configured by the configuration device, and based on the configuration device to access the network, the CHIP device cannot be configured by the configuration device using other accounts. Or access the network based on other configuration devices.
  • the present invention provides a control method.
  • the control method in the embodiment of the present invention can be applied to the IoT system 200 shown in FIG. 2 or FIG.
  • the configuration device 202 uses a first account
  • the configuration device 203 uses a second account, where the first account is an account under the first platform, and the second account is an account under the second platform.
  • the first platform and the second platform are the same platform, and the platform runs on the server 204 .
  • the first platform and the second platform are different platforms, the first platform runs on the server 204 and the second platform runs on the server 205 .
  • the configuration device 202 using the first account can configure the CHIP device 201 , and the CHIP device 201 interacts with the first platform based on the configuration device 202 .
  • the configuration device 203 using the second account can configure the CHIP device 201 , and the CHIP device 201 interacts with the second platform based on the configuration device 203 .
  • the CHIP device 201, the configuration device 202 or the configuration device 203 may refer to an access terminal, a user equipment (UE), a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, Terminal, wireless communication device, user agent or user equipment.
  • the access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, CHIP devices in 5G networks or devices in future evolved PLMNs, etc.
  • FIG. 2 exemplarily shows two configuration devices and one platform
  • FIG. 3 exemplarily shows two configuration devices and two platforms
  • the IoT system 200 may include more than two configuration devices And with more than two platforms, this is not limited in the embodiment of the present invention, and the number of accounts under one platform is not limited in any way.
  • the CHIP device shown in FIG. 2 or FIG. 3 may also include IoT devices such as sensors, laser scanning systems, and smart home appliances.
  • the server shown in FIG. 2 or FIG. 3 may be an independent computer device, or may be a server cluster composed of multiple computer devices.
  • An optional processing flow of the control method provided by the embodiment of the present invention, as shown in FIG. 4 includes the following steps:
  • the CHIP device currently stores the operation identifier generated by the first platform to which the first account belongs, and the operation identifier and the first account have an associated relationship, that is, the CHIP device has established an operation identifier with the first account.
  • the first binding relationship is, the CHIP device has established an operation identifier with the first account.
  • the CHIP device detects at least one of the following events, the condition for releasing the original binding relationship is satisfied:
  • Event 1 Complete the network configuration of the second configuration device
  • Event 2 An instruction to instruct to restore the factory settings is received.
  • the CHIP device detects event 1 in the following scenarios: In scenario 1, the CHIP device is networked by the second device.
  • the CHIP device establishes a secure channel with the second configuration device when a binding relationship with the first account is established, and performs network configuration through the second configuration device based on the established secure channel to access the network .
  • the second configuration device obtains the PIN code of the CHIP device, generates a secret required for a secure channel with the CHIP device based on the PIN code, and then configures the CHIP device.
  • the second configuration device sends the SSID and password of the accessed AP to the CHIP device, the CHIP device successfully connects to the AP through the received SSID and password, and the AP is the connected CHIP device Allocate IP addresses and other information to enable CHIP devices to access the AP and access the platform on the network side through the AP.
  • the manner in which the second configuration device obtains the PIN code of the CHIP device may include one of the following manners:
  • Method 1 Scan the QR code on the CHIP device; wherein, the information carried by the QR code on the CHIP device includes the PIN code of the CHIP device.
  • Mode 2 Receive the user's input operation; wherein, the input content of the user's input operation is the PIN code of the CHIP device.
  • the CHIP device detects event 2 in the following scenarios: scenario 2, restore factory settings.
  • the CHIP device receives an instruction to restore the factory settings according to the factory settings restoration operation input by the user. In an example, the CHIP device receives an instruction sent by the first configuration device using the first account to instruct to restore the factory settings.
  • the CHIP device releases the first binding relationship, and establishes a second binding relationship with the second account.
  • the CHIP device When the CHIP device establishes the first binding relationship and satisfies the conditions for releasing the original binding relationship, the original first binding relationship is released, and a new binding relationship is established with the second account used by the second configuration device.
  • the fixed relationship is the second binding relationship.
  • the CHIP device when the CHIP device has a binding relationship with the account A used by the configuration device A, it releases the binding relationship with the account A and establishes the binding relationship with the account B by using the configuration device B of the account B to configure the network. .
  • the first account and the second account are accounts under different platforms.
  • the first account and the second account are accounts under the same platform.
  • releasing the first account relationship by the CHIP device includes: deleting the stored first binding relationship, and instructing the first configuration device and/or the first platform using the first account to release the stored first binding relation.
  • the sequence of deleting the stored first binding relationship by the CHIP device and instructing the first configuration device and/or the first platform to release the stored first binding relationship is not limited.
  • the CHIP device instructs the first configuration device and/or the first platform to release the stored first binding relationship.
  • the CHIP device instructs the first configuration device and/or the first platform to cancel the stored first binding relationship, delete the stored first binding relationship.
  • the CHIP device instructing the first configuration device and/or the first platform to release the first binding relationship includes: the CHIP device sends a request to release the original binding relationship to the first configuration device and/or the first server, wherein , the first server runs with the first platform.
  • the CHIP device sends a request for releasing the original binding relationship to the first configuration device.
  • the CHIP device sends a request for releasing the original binding relationship to the first server, and the first server forwards the request for releasing the original binding relationship to the first configuration device.
  • the CHIP device sends a request for releasing the original binding relationship to the first configuration device, and sends a request for releasing the original binding relationship to the first server.
  • the operation identifier of the CHIP device and the first account number are carried in the request for releasing the original binding relationship, so as to indicate to release the association relationship between the operation identifier and the first account number, thereby releasing the CHIP device and the first account number. the first binding relationship.
  • the CHIP device After releasing the first binding relationship, the CHIP device establishes a second binding relationship with the second account, so that the second configuration device configures the CHIP device.
  • the CHIP device completes the establishment of the second binding relationship during the device authentication process with the second configuration device.
  • the CHIP device when the CHIP device is connected to the Internet, it receives an instruction to restore the factory settings and releases the stored first binding relationship; when the CHIP device is not connected to the Internet, it receives an instruction to restore the factory settings and uses the first Configure the SSID and password sent by the device to connect to the Internet, switch from the unconnected state to the connected state, and release the stored first binding relationship in the connected state.
  • the CHIP device After releasing the first binding relationship, the CHIP device restores the factory settings, and after completing the restoration of the factory settings, establishes a secure channel with the second configuration device. After the CHIP device establishes a secure channel with the second configuration device, it configures the network through the second configuration device and performs device authentication with the second configuration device.
  • the CHIP device sends identification information and/or platform information to the second configuration device;
  • the identification information is used to characterize the CHIP device, and optionally, the identification information includes: an operation identifier, device information, and the like.
  • the platform information is used to represent the platform to which the first account belongs.
  • the platform information includes: a platform identifier for uniquely identifying the platform, status information of the platform, information associated with the CHIP device, and the like.
  • the information associated with the CHIP device includes: account information, Op Cert and ICs, etc.
  • the second configuration device After receiving the identification information and/or platform information sent by the CHIP device, the second configuration device detects whether the account bound to the CHIP device is the second account according to the received identification information and/or platform information. When the second configuration device determines that the account bound to the CHIP device is not the second account without storing the operation identifier or the account information in the platform information, it is considered that the CHIP device has established a binding relationship.
  • the second configuration device sends an instruction to release the original binding relationship to the CHIP device to instruct the CHIP device to release the established binding relationship, that is, the first binding relationship, and A second binding relationship with the second account is established.
  • the CHIP device receives an indication of releasing the original binding relationship sent by the second configuration device
  • the execution of S402 includes S4021: in the case of receiving the indication of releasing the original binding relationship, the CHIP device releases the first binding relationship, and establishes a second binding relationship with the second account.
  • the implementation of releasing the first binding relationship in S402 includes one of the following two implementations:
  • Embodiment 1 Send a request to release the original binding relationship to a first server; and receive a successful response to release the original binding relationship sent by the first server.
  • the first server runs on the first platform to which the first account belongs.
  • Embodiment 2 Send a request to release the original binding relationship to the first configuration device using the first account; and receive a successful response to release the original binding relationship sent by the first configuration device.
  • the CHIP device sends a request for releasing the original binding relationship to the first server to instruct the first platform to delete the first binding relationship, and the first server instructs the first configuration device to release the stored first binding relationship. binding relationship.
  • the first server forwards the request for releasing the original binding relationship to the first configurator to instruct the first configurator to release the stored first binding relationship; the first configuration
  • the device returns the original binding relationship deletion request to the first server to instruct the first server to cancel the stored first binding relationship;
  • the first server returns the original binding relationship cancellation success response to the first configuration device to indicate that the first configuration device has canceled the first binding relationship.
  • a binding relationship is established, and the first binding relationship is deleted in the first server, thereby completing the release of the first binding relationship in the Internet of Things system.
  • the CHIP device sends a request to remove the original binding relationship to the first configurator to instruct the first configuration device to release the stored first binding relationship, and the first configuration device instructs the first platform to delete the relationship.
  • the first binding relationship Taking the implementation of S402 as Embodiment 2 as an example, the CHIP device sends a request to remove the original binding relationship to the first configurator to instruct the first configuration device to release the stored first binding relationship, and the first configuration device instructs the first platform to delete the relationship.
  • the first binding relationship is a request to remove the original binding relationship to the first configurator to instruct the first configuration device to release the stored first binding relationship.
  • the first configurator releases the stored first binding relationship in the case of receiving the request for canceling the original binding relationship, and sends the request to the first configurator.
  • the first server returns the original binding relationship deletion request to instruct the first server to release the stored first binding relationship; in the case of receiving the original binding relationship deletion request, the first server deletes the first binding relationship, Return the original binding relationship release success response to the CHIP device to indicate that the first binding relationship is released in the first configurator, and the first binding relationship is deleted in the first server, thereby completing the first binding relationship in the IoT system. The release of the binding relationship.
  • the CHIP device further performs the following steps after receiving the successful response of the original binding relationship release: sending a notification that the original binding relationship is successfully released to the second configuration device.
  • the CHIP device After determining that the first binding relationship has been released in the IoT system, the CHIP device sends a notification of successful release of the original binding relationship to the second configuration device to instruct the second configuration device to complete the release of the first binding relationship, and the second configuration device In the case of receiving the notification of successful release of the original binding relationship, device authentication is performed with the CHIP device.
  • the second platform to which the second account used by the second device belongs configures a new operation identifier to the CHIP device, and establishes a relationship between the new operation identifier and the second account.
  • An association relationship is established to establish a binding relationship, that is, a second binding relationship, between the CHIP device and the second account.
  • the first binding relationship In this embodiment of the present invention, the first binding relationship.
  • An optional processing flow of the control method provided by the embodiment of the present invention, as shown in FIG. 6 includes the following steps:
  • the first configuration device receives a request for releasing the original binding relationship for instructing to release the first binding relationship
  • the first binding relationship is a binding relationship between the CHIP device and the first account used by the first configuration device.
  • the CHIP device When the CHIP device establishes the first binding relationship and satisfies the conditions for releasing the original binding relationship, the first binding relationship needs to be released.
  • the CHIP device deletes the stored first binding relationship, and instructs the first configuration device and/or the first platform to release the first binding relationship.
  • the request for releasing the original binding relationship is received from the CHIP device or the first server.
  • the CHIP device instructing the first configuration device and/or the first platform to release the first binding relationship includes: the CHIP device sends a request to release the original binding relationship to the first configuration device and/or the first server, wherein the first server Running the first platform to which the first account belongs.
  • the CHIP device sends a request for releasing the original binding relationship to the first configuration device, and at this time, the first configuration device receives the request for releasing the original binding relationship sent by the CHIP device.
  • the CHIP device sends a request for releasing the original binding relationship to the first server, and the first server forwards the request for releasing the original binding relationship to the first configuration device.
  • the first configuration device receives the release request sent by the first server. The original binding relationship request.
  • the first configuration device releases the stored first binding relationship.
  • the first configuration device releases the stored first binding relationship, so that the CHIP device can establish a second binding relationship with the second account, so that the CHIP device can be configured by the second configuration device using the second account .
  • the first configuration device cancels the stored association relationship between the operation identifier and the first account, so as to complete the release of the stored first binding relationship.
  • the operation identifier in the first binding relationship is an operation identifier configured by the first server for the CHIP device.
  • the first configuration device may output a prompt for releasing the first binding relationship.
  • the first configuration device obtains the authorization of the user in the case of receiving the user's determination operation of the prompt for releasing the first binding relationship, and releases the stored first binding relationship under the condition of obtaining the authorization of the user.
  • the method further includes: in the case of releasing the stored first binding relationship, sending a request for deleting the original binding relationship to the first server to which the first account belongs, and the The original binding relationship deletion request is used to instruct the first server to delete the first binding relationship.
  • the first configuration device After completing the release of the stored first binding relationship, the first configuration device sends an original binding relationship deletion request to the first server, instructing the first server to delete the stored first binding relationship.
  • the first server in the case where the first configuration device receives a request for releasing the original binding relationship sent by the first server, the first server returns the original binding relationship release to the CHIP device after completing the upper deletion of the first binding relationship. Successful response.
  • the first server returns the original binding relationship to the first configuration device after completing the upper deletion of the first binding relationship.
  • the first configuration device forwards the successful response of the original binding relationship release to the CHIP device.
  • the first account and the second account are accounts under different platforms.
  • the first account is an account under the first platform
  • the second account is an account under the second platform
  • the first server running the first platform and the second server running the second account are different servers.
  • the first account and the second account are accounts under the same platform.
  • the first account is an account under the first platform
  • the second account is an account under the second platform
  • the first server running the first platform and the second server running the second account are the same server.
  • An optional processing flow of the control method provided by the embodiment of the present invention, as shown in FIG. 7 includes the following steps:
  • the second configuration device configures the network to the CHIP device
  • the second configuration device sends an indication of releasing the original binding relationship to the CHIP device when it is determined that the CHIP device has established a first binding relationship with the first account.
  • the indication of releasing the original binding relationship is used to instruct the CHIP device to release the first binding relationship, and establish a second binding relationship with the second account used by the second configuration device, so that the The second configuration device configures the CHIP device.
  • the second configuration device before S701, receives identification information and/or platform information sent by the CHIP device; the identification information and/or the platform information are used to detect whether the CHIP device is The first binding relationship is established.
  • the platform information is used to represent the platform to which the first account belongs.
  • the platform information includes: a platform identifier that uniquely identifies the platform, status information of the platform, information associated with the operation identifier, and the like.
  • the information associated with the operation identifier may include: account information, Op Cert and ICs, etc.
  • the account information includes: a first account.
  • the second configuration device After receiving the identification information and/or platform information sent by the CHIP device, the second configuration device determines whether the account bound to the CHIP device is the second account according to the received identification information and/or platform information. The second configuration device determines that the account bound to the CHIP device is not the second account without storing the received operation identifier or the account information in the platform information, and considers that the CHIP device has established a binding relationship.
  • the second configuration device sends an instruction to release the original binding relationship to the CHIP device to instruct the CHIP device to release the established binding relationship, that is, the first binding relationship, and A second binding relationship with the second account is established.
  • first account and the second account are accounts under different platforms.
  • first account and the second account are accounts under the same platform.
  • the second configuration device receives the original account cancellation success notification sent by the CHIP device, and the original account cancellation success notification indicates that the CHIP device has completed the cancellation of the first binding relationship, and the second configuration device receives the original account cancellation success notification.
  • notification of account cancellation perform device authentication with CHIP devices.
  • An optional processing flow of the control method provided by the embodiment of the present invention, as shown in FIG. 8 includes the following steps:
  • the server receives the original binding relationship deletion request
  • the server deletes the first binding relationship between the CHIP device and the first account.
  • the server deletes the first binding relationship between the CHIP device and the first account under the request of the received original binding relationship deletion request.
  • the CHIP device satisfies the conditions for releasing the original binding relationship, then the first binding relationship is released, and a second binding relationship is established with the second account, so that the The CHIP device is configured using the second configuration device of the second account.
  • the server here is the first server, and the first server runs the first platform to which the first account belongs.
  • the first account and the second account are accounts under different platforms.
  • the first account is an account under the first platform
  • the second account is an account under the second platform
  • the first server running the first platform and the second server running the second account are different servers.
  • the first account and the second account are accounts under the same platform.
  • the first account is an account under the first platform
  • the second account is an account under the second platform
  • the first server running the first platform and the second server running the second account are the same server.
  • the CHIP device deletes the stored first binding relationship, and instructs the first configuration device and/or the first platform to release the first binding relationship.
  • the CHIP device instructing the first configuration device to release the first binding relationship includes: the CHIP device sending a request for releasing the original binding relationship to the server.
  • the server receives a request for unbinding the original binding relationship from the CHIP device; the server forwards the original binding relationship request to the first configuration device using the first account to instruct the first configuration device to use the first account.
  • a configuration device releases the stored first binding relationship.
  • the CHIP device instructs the first configuration device to release the stored first binding relationship, including:
  • the CHIP device sends a request to cancel the original binding relationship to the first configuration device
  • the CHIP device sends a request for unbinding the original binding relationship to the server, and the server forwards the received request for unbinding the original binding relationship to the server.
  • the first configuration device cancels the stored first binding relationship under the request of canceling the original binding relationship request received from the CHIP device or the server, and sends the original binding relationship deletion to the server after the stored first binding relationship is released. request, the server receives the original binding relationship deletion request sent by the first configuration device.
  • the server After completing the first binding relationship deletion request, the server sends a successful response of the original binding relationship cancellation. Taking the indication mode 1 as an example, the server sends a successful response to the first configuration device for releasing the original binding relationship, and forwards the received response to the first configuration device for releasing the original binding relationship to the CHIP device, indicating that the server and the first configuration device are successfully released. The deletion or release of the first binding relationship is completed. In the second indication manner, the server sends the CHIP device a successful response to release the original binding relationship, instructing the server and the first configuration device to complete the deletion or release of the first binding relationship.
  • the control method provided by the embodiment of the present invention includes: when a CHIP device establishes a first binding relationship with a first account, and configures a network by using a second configuration device of a second account, releasing the first binding A relationship is established, and a second binding relationship is established with the second account, so that the CHIP device is configured by the second configuration device.
  • the CHIP device is connected to the network by other configuration devices when a binding relationship is established, the original binding relationship is deleted, and the original configuration device and the server are instructed to release the original binding relationship, and the CHIP device , In the case of releasing the original binding relationship between the original configuration device and the server, establish a binding relationship with the account of the new configuration device. Since the new configuration device can configure the CHIP device, the CHIP device is released. The restriction that a device is configured by only one configuration device.
  • the configuration device is a mobile phone and the CHIP device is a CHIP device as an example, and the provided control method is described through different application scenarios.
  • Account A of mobile phone A is an account on platform A; account B of mobile phone B is an account on platform B.
  • the CHIP device has established a binding relationship with account B, and stores information such as the Op ID configured by platform B for the CHIP device, platform information of platform B and other information, and the steps for releasing the binding relationship between the CHIP device and account B are shown in Figure 9 shown, including:
  • S901, CHIP device and mobile phone A establish a secure connection through PIN code
  • mobile phone A is the CHIP device distribution network
  • Mobile phone A hopes to connect the CHIP device to platform A, and reconfigure the CHIP device to the network.
  • the CHIP device sends the Op ID and the platform information of the platform B to the mobile phone A;
  • the CHIP device After the CHIP device is connected to the network, it sends the Op ID and platform information of platform B to mobile phone A.
  • the mobile phone A determines that the CHIP device does not belong to the platform A through the Op ID and the platform information of the platform B;
  • the mobile phone A sends an indication of unbinding the device to the CHIP device;
  • the indication of releasing the device binding relationship may also be referred to as the indication of releasing the original binding relationship.
  • the CHIP device sends a request to platform B to release the device binding relationship
  • platform B sends a request for releasing the device binding relationship to mobile phone B;
  • the request for canceling the confirmation of the device binding relationship may also be referred to as a request for canceling the original binding relationship.
  • the mobile phone B executes the release of the binding relationship between the CHIP device and the mobile phone B;
  • the mobile phone B After the mobile phone B receives the request to release the device binding relationship from the platform B, the mobile phone B authorizes and determines to execute the release of the binding relationship between the CHIP device and the mobile phone B.
  • the mobile phone B sends a request to delete the binding relationship to the platform B;
  • Sending a request to delete a binding relationship may also be referred to as a request to delete the original binding relationship.
  • platform B deletes the binding relationship between the CHIP device and mobile phone B;
  • platform B returns a successful response that the binding relationship has been released to the CHIP device
  • the CHIP device sends the state that the relationship with the platform B has been released to the mobile phone A;
  • the sent status may be carried in the notification of successful release of the original binding relationship.
  • the binding relationship between the CHIP device and the account A is established during the device authentication process between the platform A and the CHIP device.
  • Account A of mobile phone A is an account on platform A; account B of mobile phone B is an account on platform B.
  • the CHIP device has established a binding relationship with account B, and stores information such as the Op ID configured for CHIP device by platform B, platform information of platform B and other information.
  • the steps of releasing the binding relationship between CHIP device and account B are shown in Figure 10 shown, including:
  • S1001, CHIP device and mobile phone A establish a secure connection through PIN code
  • Mobile phone A hopes to connect the CHIP device to platform A, and reconfigure the CHIP device to the network.
  • the CHIP device sends the Op ID and the platform information of the platform B to the mobile phone A;
  • the CHIP device After the CHIP device is connected to the network, it sends the Op ID and platform information of platform B to mobile phone A.
  • the mobile phone A determines that the CHIP device does not belong to the platform A through the Op ID and the platform information of the platform B;
  • the mobile phone A sends an indication of unbinding the device to the CHIP device;
  • the release of the original binding relationship indication is used to instruct the CHIP device to release the binding relationship between the CHIP device and account B.
  • the CHIP device sends a request for releasing the device binding relationship to the mobile phone B;
  • the mobile phone B executes the release of the binding relationship between the CHIP device and the mobile phone B;
  • the mobile phone B After the mobile phone B receives the request for releasing the binding relationship from the CHIP device, the mobile phone B authorizes it and determines to execute the cancellation of the binding relationship between the CHIP device and the mobile phone B.
  • the mobile phone B sends a request to delete the binding relationship to the platform B;
  • platform B deletes the binding relationship between the CHIP device and mobile phone B;
  • platform B returns a successful response that the binding relationship has been released to mobile phone B;
  • the mobile phone B returns a successful response that the binding relationship has been released to the CHIP device;
  • the CHIP device sends the state that the relationship with the platform B has been released to the mobile phone A;
  • the account A1 of the mobile phone A1 and the account A2 of the mobile phone A2 are accounts on the platform A.
  • the CHIP device has established a binding relationship with account A2, and stores the Op ID configured by platform A for the CHIP device, the platform information of platform A and other information.
  • the steps of releasing the binding relationship between the CHIP device and account A2 are shown in Figure 11 shown, including:
  • CHIP device establishes a secure connection with mobile phone A1 through PIN code
  • Mobile phone A1 wants to bind the CHIP device to account A1, and reconfigure the CHIP device to the network.
  • the CHIP device sends the Op ID and the platform information of the platform A to the mobile phone A1;
  • the CHIP device After the CHIP device is connected to the network, it sends the Op ID and platform information of platform 1 to the mobile phone A1.
  • the mobile phone A1 determines that the CHIP device has been bound to the account A1 through the Op ID and the platform information of the platform A;
  • the mobile phone A1 sends an indication of unbinding the device to the CHIP device;
  • the release of the original binding relationship indication is used to instruct the CHIP device to release the binding relationship between the CHIP device and the account A2.
  • the CHIP device sends a request for releasing the device binding relationship to platform A;
  • the platform A sends a request for canceling the confirmation of the device binding relationship to the mobile phone A2;
  • the mobile phone A2 executes the release of the binding relationship between the CHIP device and the mobile phone A2;
  • the mobile phone A2 After the mobile phone A2 receives the request for releasing the binding relationship from the platform A, the mobile phone A2 authorizes and determines to execute the cancellation of the binding relationship between the CHIP device and the mobile phone A2.
  • the mobile phone A2 sends a request to delete the binding relationship to the platform A;
  • platform A deletes the binding relationship between the CHIP device and mobile phone A2;
  • platform A returns a successful response that the binding relationship has been released to the CHIP device
  • the CHIP device sends the state that the relationship with the account A2 has been released to the mobile phone A1;
  • the mobile phone A1 confirms that the CHIP device has no binding relationship with other mobile phones
  • the mobile phone A1 is authenticated with the CHIP device
  • the account A1 of the mobile phone A1 and the account A2 of the mobile phone A2 are accounts on the platform A.
  • the CHIP device has established a binding relationship with account A2, and stores the Op ID configured by platform A for the CHIP device, platform information of platform A and other information, and the steps of releasing the binding relationship between the CHIP device and account A2 are shown in Figure 12 shown, including:
  • S1201, CHIP device and mobile phone A1 establish a secure connection through PIN code
  • Mobile phone A1 wants to bind the CHIP device to account A1, and reconfigure the CHIP device to the network.
  • the CHIP device sends the Op ID and the platform information of the platform A to the mobile phone A1;
  • the CHIP device After the CHIP device is connected to the network, it sends the Op ID and platform information of platform A to mobile phone A1.
  • the mobile phone A1 determines that the CHIP device has been bound to the account A1 through the Op ID and the platform information of the platform B;
  • the mobile phone A1 sends an indication of unbinding the device to the CHIP device;
  • the release of the original binding relationship indication is used to instruct the CHIP device to release the binding relationship between the CHIP device and the account A2.
  • the CHIP device sends a request for releasing the device binding relationship to the mobile phone A1;
  • the mobile phone A1 executes the release of the binding relationship between the CHIP device and the mobile phone A2;
  • the mobile phone A2 After the mobile phone A2 receives the request for releasing the binding relationship from the CHIP device, the mobile phone A2 authorizes it and determines to execute the cancellation of the binding relationship between the CHIP device and the mobile phone A2.
  • the mobile phone A2 sends a request to delete the binding relationship to the platform A;
  • platform A deletes the binding relationship between the CHIP device and mobile phone A2;
  • the platform A returns a successful response that the binding relationship has been released to the mobile phone A2;
  • the mobile phone A2 returns a successful response that the binding relationship has been released to the CHIP device;
  • the CHIP device sends the state that the relationship with the account A2 has been released to the mobile phone A;
  • the mobile phone A1 confirms that the CHIP device has no binding relationship with other mobile phones
  • Account A used by mobile phone A is an account under platform A
  • account B used by mobile phone B is an account under platform B.
  • the CHIP device has established a binding relationship with account B, and stores information such as the Op ID configured by platform B for the CHIP device, platform information of platform B and other information, and the steps for releasing the binding relationship between the CHIP device and account B are shown in Figure 13 shown, including:
  • the CHIP device receives an instruction instructing to restore factory settings
  • the CHIP device sends a request for releasing the device binding relationship to platform B;
  • the platform B sends a request for canceling the confirmation of the device binding relationship to the mobile phone B;
  • the mobile phone B executes the release of the binding relationship between the CHIP device and the mobile phone B;
  • the mobile phone B After the mobile phone B receives the request to unbind the relationship from the platform B, the mobile phone B authorizes and decides to execute the unbinding relationship between the CHIP device and the mobile phone B.
  • the binding relationship deletion request instructs platform B to delete the binding relationship between the CHIP device and mobile phone B.
  • platform B deletes the binding relationship between the CHIP device and mobile phone B;
  • platform B returns a successful response that the binding relationship has been released to the CHIP device
  • platform A performs device authentication with the CHIP device.
  • Account A used by mobile phone A is an account under platform A
  • account B used by mobile phone B is an account under platform B.
  • the CHIP device has established a binding relationship with account B, and stored information such as the Op ID configured for the CHIP device by platform B, platform information of platform B and other information.
  • the steps of releasing the binding relationship between the CHIP device and account B are shown in Figure 14 shown, including:
  • the CHIP device receives an instruction instructing to restore the factory settings
  • the CHIP device sends a request for releasing the device binding relationship to the mobile phone B;
  • the mobile phone B executes the release of the binding relationship between the CHIP device and the mobile phone B;
  • mobile phone B After mobile phone B receives the request for unbinding from platform B, mobile phone B obtains authorization and executes the unbinding relationship between the CHIP device and mobile phone B.
  • the binding relationship deletion request instructs platform B to delete the binding relationship between the CHIP device and mobile phone B.
  • platform B deletes the binding relationship between the CHIP device and mobile phone B;
  • platform B returns a successful response that the binding relationship has been released to mobile phone B;
  • the mobile phone B returns a successful response that the binding relationship has been released to the CHIP device;
  • the platform A performs device authentication for the CHIP device.
  • the CHIP device can only have the configuration device configuration using the bound account.
  • the CHIP device cannot establish a binding relationship with other accounts.
  • the control method provided by the embodiment of the present invention when When the CHIP device has established a binding relationship and needs to establish a new binding relationship with other accounts, it will release the established binding relationship itself and release the binding relationship stored in the original configuration device. , and delete the binding relationship in the original platform, so as to completely delete the original binding relationship from the Internet of Things system, and avoid configuring the device and the account resources in the original platform only when the original binding relationship is released in the CHIP device. Invalid take, and release operator resources.
  • an embodiment of the present invention further provides a CHIP device 201, as shown in FIG. 15, including:
  • the release module 1501 is configured to release the first binding relationship and establish a second binding relationship with the second account when the first binding relationship with the first account is established and the conditions for releasing the original binding relationship are satisfied.
  • a relationship is established to configure the CHIP device by a second configuration device using the second account.
  • the release module 1501 is further configured to detect at least one of the following events, and determine that the original binding relationship release condition is satisfied:
  • the first account and the second account are accounts under different platforms.
  • the first account and the second account are accounts under the same platform.
  • the CHIP device further includes:
  • a first sending module configured to send identification information and/or platform information to the second configuration device
  • the first receiving module is configured to receive an indication of releasing the original binding relationship sent by the second configuration device.
  • the dismantling module 1501 is further configured to:
  • the first server runs the first platform to which the first account belongs;
  • a successful response for releasing the original binding relationship sent by the first server is received.
  • the dismantling module 1501 is further configured to:
  • the dismantling module 1501 is further configured to:
  • An embodiment of the present invention further provides a CHIP device, including a processor and a memory for storing a computer program that can be run on the processor, wherein the processor is configured to execute the program executed by the CHIP device when running the computer program. The steps of the control method.
  • an embodiment of the present invention further provides a configuration device 202, as shown in FIG. 16, including:
  • the second receiving module 1601 is configured to receive a request for releasing the original binding relationship for instructing to release the first binding relationship;
  • the first binding relationship is the binding between the CHIP device and the first account used by the first configuration device relationship;
  • Executing module 1602 configured to release the stored first binding relationship, so that the CHIP device can establish a second binding relationship with a second account, so that the second configuration device using the second account can set up the second binding relationship with the second account. Configure the CHIP device.
  • the configuration device 202 further includes:
  • the second sending module is configured to send the original binding relationship deletion request to the first server to which the first account belongs; the first server runs the first platform to which the first account belongs.
  • the request for releasing the original binding relationship is received from the CHIP device or the first server.
  • the first account and the second account are accounts under different platforms.
  • the first account and the second account are accounts under the same platform.
  • An embodiment of the present invention further provides a configuration device, including a processor and a memory for storing a computer program that can be executed on the processor, wherein the processor is configured to execute the above-mentioned first configuration device when running the computer program Execute the steps of the control method.
  • an embodiment of the present invention further provides a configuration device 203, as shown in FIG. 17, including:
  • the distribution network module 1701 is configured to distribute the network to the CHIP device
  • the third sending module 1702 is configured to send an indication of releasing the original binding relationship to the CHIP device when it is determined that the CHIP device has established a first binding relationship with the first account, the releasing the original binding relationship
  • the instruction is used to instruct the CHIP device to release the first binding relationship and establish a second binding relationship with the second account used by the second configuration device, so that the CHIP device can be assigned to the CHIP device by the second configuration device. to configure.
  • the configuration device 203 further includes:
  • the third receiving module is configured to receive the identification information and/or platform information sent by the CHIP device; the operation identifier and the platform information are used to determine whether the CHIP device has established the first binding relationship.
  • the first account and the second account are accounts under different platforms.
  • the first account and the second account are accounts under the same platform.
  • An embodiment of the present invention further provides a configuration device, including a processor and a memory for storing a computer program that can be run on the processor, wherein the processor is configured to execute the above-mentioned second configuration device when running the computer program Execute the steps of the control method.
  • an embodiment of the present invention further provides a server 204, as shown in FIG. 18, including:
  • the fourth receiving module 1801 configures the received original binding relationship deletion request
  • the deletion module 1802 is configured to delete the first binding relationship between the CHIP device and the first account; when the CHIP device has established the first binding relationship, it satisfies the conditions for releasing the original binding relationship, and releases the first binding relationship. A binding relationship is established, and a second binding relationship is established with the second account, so that the CHIP device is configured by the second configuration device using the second account.
  • the server 204 further includes:
  • the fifth receiving module is configured to receive the original binding relationship deletion request sent by the first configuration device.
  • the server 204 further includes:
  • a sixth receiving module configured to receive a request for releasing the original binding relationship from the CHIP device
  • the fourth sending module is configured to forward the original binding relationship request to the first configuration device using the first account.
  • the first account and the second account are accounts under different platforms.
  • the first account and the second account are accounts under the same platform.
  • An embodiment of the present invention further provides a configuration device, including a processor and a memory for storing a computer program that can be executed on the processor, wherein the processor is configured to execute the control performed by the above server when the computer program is executed steps of the method.
  • the electronic device 1900 includes: at least one processor 1901 , memory 1902 and at least one network interface 1904 .
  • the various components in electronic device 1900 are coupled together by bus system 1905 .
  • bus system 1905 is used to implement the connection communication between these components.
  • the bus system 1905 also includes a power bus, a control bus, and a status signal bus.
  • the various buses are labeled as bus system 1905 in FIG. 19 .
  • the memory 1902 may be either volatile memory or non-volatile memory, and may include both volatile and non-volatile memory.
  • the non-volatile memory can be ROM, Programmable Read-Only Memory (PROM, Programmable Read-Only Memory), Erasable Programmable Read-Only Memory (EPROM, Erasable Programmable Read-Only Memory), Electrically Erasable Programmable Read-Only Memory Programmable read-only memory (EEPROM, Electrically Erasable Programmable Read-Only Memory), magnetic random access memory (FRAM, ferromagnetic random access memory), flash memory (Flash Memory), magnetic surface memory, optical disk, or CD-ROM -ROM, Compact Disc Read-Only Memory); magnetic surface memory can be disk memory or tape memory.
  • RAM Random Access Memory
  • SRAM Static Random Access Memory
  • SSRAM Synchronous Static Random Access Memory
  • DRAM Dynamic Random Access Memory
  • SDRAM Synchronous Dynamic Random Access Memory
  • DDRSDRAM Double Data Rate Synchronous Dynamic Random Access Memory
  • ESDRAM Enhanced Type Synchronous Dynamic Random Access Memory
  • SLDRAM Synchronous Link Dynamic Random Access Memory
  • DRRAM Direct Rambus Random Access Memory
  • the memory 1902 described in the embodiments of the present invention is intended to include, but not be limited to, these and any other suitable types of memory.
  • the memory 1902 in the embodiment of the present invention is used to store various types of data to support the operation of the electronic device 1900 .
  • Examples of such data include: any computer program for operating on the electronic device 1900 , such as the application program 19021 , the program implementing the methods of the embodiments of the present invention may be included in the application program 19021 .
  • the methods disclosed in the above embodiments of the present invention may be applied to the processor 1901 or implemented by the processor 1901 .
  • the processor 1901 may be an integrated circuit chip with signal processing capability. In the implementation process, each step of the above-mentioned method can be completed by an integrated logic circuit of hardware in the processor 1901 or an instruction in the form of software.
  • the above-mentioned processor 1901 may be a general-purpose processor, a digital signal processor (DSP, Digital Signal Processor), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like.
  • DSP Digital Signal Processor
  • the processor 1901 may implement or execute the methods, steps, and logical block diagrams disclosed in the embodiments of the present invention.
  • a general purpose processor may be a microprocessor or any conventional processor or the like.
  • the steps of the method disclosed in combination with the embodiments of the present invention can be directly embodied as being executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor.
  • the software module may be located in a storage medium, the storage medium is located in the memory 1902, the processor 1901 reads the information in the memory 1902, and completes the steps of the foregoing method in combination with its hardware.
  • electronic device 1900 may be implemented by one or more of Application Specific Integrated Circuit (ASIC), DSP, Programmable Logic Device (PLD), Complex Programmable Logic Device (CPLD) , Complex Programmable Logic Device), FPGA, general-purpose processor, controller, MCU, MPU, or other electronic component implementation for performing the aforementioned method.
  • ASIC Application Specific Integrated Circuit
  • DSP Digital Signal processor
  • PLD Programmable Logic Device
  • CPLD Complex Programmable Logic Device
  • FPGA general-purpose processor
  • controller MCU, MPU, or other electronic component implementation for performing the aforementioned method.
  • the embodiment of the present invention also provides a storage medium for storing a computer program.
  • the storage medium can be applied to the CHIP device in the embodiment of the present invention, and the computer program enables the computer to execute the corresponding processes in each method of the embodiment of the present invention, which is not repeated here for brevity.
  • the storage medium can be applied to the configuration device in the embodiment of the present invention, and the computer program enables the computer to execute the corresponding processes in each method of the embodiment of the present invention, which is not repeated here for brevity.
  • the storage medium can be applied to the server in the embodiment of the present invention, and the computer program causes the computer to execute the corresponding processes in each method of the embodiment of the present invention, which is not repeated here for brevity.
  • These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory result in an article of manufacture comprising instruction means, the instructions
  • the apparatus implements the functions specified in the flow or flow of the flowcharts and/or the block or blocks of the block diagrams.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Storage Device Security (AREA)
  • Retry When Errors Occur (AREA)

Abstract

本发明实施例提供一种控制方法，包括：CHIP设备在建立有与第一账号的第一绑定关系的情况下，满足原绑定关系解除条件，解除所述第一绑定关系，与第二账号建立第二绑定关系，以由使用所述第二账号的第二配置设备对所述CHIP设备进行配置。本发明实施例还提供另一种控制方法以及设备、存储介质。

Description

控制方法、设备及存储介质 技术领域
本发明涉及物联网技术，尤其涉及一种控制方法、设备及存储介质，其中，本发明涉及的设备包括以下至少之一：CHIP设备、配置设备和服务器。
背景技术
相关技术中，IP互联家庭(Connected Home Over IP，CHIP)设备只能由使用该账号的配置设备进行配置，即只能被绑定一个账号。由于只由使用绑定的账号的配置设备具有对CHIP设备进行配置的权限，因此，在CHIP设备已经具有与一个账号的绑定关系后，无法由使用其他账号的配置设备对该CHIP设备进行配置。
发明内容
本发明实施例提供一种控制方法、设备及存储介质，能够实现配置设备的切换。
本发明实施例的技术方案是这样实现的：
第一方面，本发明实施例提供一种控制方法，包括：
通过互联网协议连接家庭CHIP设备在建立有与第一账号的第一绑定关系的情况下，满足原绑定关系解除条件，解除所述第一绑定关系，与第二账号建立第二绑定关系，以由使用所述第二账号的第二配置设备对所述CHIP设备进行配置。
第二方面，本发明实施例提供一种控制方法，包括：
第一配置设备接收用于指示解除第一绑定关系的解除原绑定关系请求；所述第一绑定关系为CHIP设备与所述第一配置设备使用的第一账号的绑定关系；
所述第一配置设备解除存储的所述第一绑定关系，使得所述CHIP设备能够与第二账号建立第二绑定关系，以由使用所述第二账号的第二配置设备对所述CHIP设备进行配置。
第三方面，本发明实施例提供一种控制方法，包括：
第二配置设备对CHIP设备配网；
所述第二配置设备在确定所述CHIP设备建立有与第一账号的第一绑定关系的情况下，向所述CHIP设备发送解除原绑定关系指示；所述解除原绑定关系指示用于指示所述CHIP设备解除所述第一绑定关系，建立与所述第二配置设备使用的第二账号的第二绑定关系，以由所述第二配置设备对所述CHIP设备进行配置。
第四方面，本发明实施例提供一种控制方法，包括：
服务器接收原绑定关系删除请求；所述服务器删除CHIP设备与第一账号的第一绑定关系；所述终端设备在建立有所述第一绑定关系的情况下，满足原绑定关系解除条件，解除所述第一绑定关系，与第二账号建立第二绑定关系，以由使用所述第二账号的第二配置设备对所述终端设备进行配置。
第五方面，本发明实施例提供一种CHIP设备，包括：
解除模块，配置为在建立有与第一账号的第一绑定关系的情况下，满足原绑定关系解除条件，解除所述第一绑定关系，与第二账号建立第二绑定关系，以由使用所述第二账号的第二配置设备对所述CHIP设备进行配置。
第六方面，本发明实施例提供一种CHIP设备，包括：
第二接收模块，配置为接收用于指示解除第一绑定关系的解除原绑定关系请求；所述第一绑定关系为CHIP设备与所述第一配置设备使用的第一账号的绑定关系；
执行模块，配置为解除存储的所述第一绑定关系，使得所述CHIP设备能够与第二账号建立第 二绑定关系，以由使用所述第二账号的第二配置设备对所述CHIP设备进行配置。
第七方面，本发明实施例提供一种配置设备，包括：
配网模块，配置为对CHIP设备配网；
第三发送模块，配置为在确定所述CHIP设备建立有与第一账号的第一绑定关系的情况下，向所述CHIP设备发送解除原绑定关系指示，所述解除原绑定关系指示用于指示所述CHIP设备解除所述第一绑定关系，建立与所述第二配置设备使用的第二账号的第二绑定关系，以由所述第二配置设备对所述CHIP设备进行配置。
第八方面，本发明实施例提供一种服务器，包括：
第四接收模块，配置为接收原绑定关系删除请求；
删除模块，配置为删除CHIP设备与第一账号的第一绑定关系；所述终端设备在建立有所述第一绑定关系的情况下，满足原绑定关系解除条件，解除所述第一绑定关系，与第二账号建立第二绑定关系，以由使用所述第二账号的第二配置设备对所述终端设备进行配置。
第九方面，本发明实施例提供一种CHIP设备，包括处理器和用于存储能够在处理器上运行的计算机程序的存储器，其中，所述处理器用于运行所述计算机程序时，执行上述CHIP设备执行的控制方法的步骤。
第十方面，本发明实施例提供一种配置设备，包括处理器和用于存储能够在处理器上运行的计算机程序的存储器，其中，所述处理器用于运行所述计算机程序时，执行上述配置设备执行的控制方法的步骤。
第十一方面，本发明实施例提供一种服务器，包括处理器和用于存储能够在处理器上运行的计算机程序的存储器，其中，所述处理器用于运行所述计算机程序时，执行上述服务器执行的控制方法的步骤。
第十二方面，本发明实施例提供一种存储介质，存储有可执行程序，所述可执行程序被处理器执行时，实现上述CHIP设备执行的控制方法。
第十三方面，本发明实施例提供一种存储介质，存储有可执行程序，所述可执行程序被处理器执行时，实现上述配置设备执行的控制方法。
第十四方面，本发明实施例提供一种存储介质，存储有可执行程序，所述可执行程序被处理器执行时，实现上述服务器执行的控制方法。
本发明实施例提供的控制方法，包括：CHIP设备在建立有与第一账号的第一绑定关系的情况下，满足原绑定关系解除条件，解除所述第一绑定关系，与第二账号建立第二绑定关系，以由使用所述第二账号的第二配置设备对所述CHIP设备进行配置。由于CHIP设备在建立与新的账号的绑定关系之前，将物联网系统中原有的绑定关系解除，从而保证新的绑定关系的建立，使得CHIP设备能够被新的配置设备配置。
附图说明
图1是本发明实施例提供的CHIP设备接入平台的一个可选的流程示意图；
图2是本发明实施例提供的物联网系统的一个可选的结构示意图
图3是本发明实施例提供的物联网系统的一个可选的结构示意图；
图4是本发明实施例提供的控制方法的一个可选的流程示意图；
图5是本发明实施例提供的控制方法的一个可选的流程示意图；
图6是本发明实施例提供的控制方法的一个可选的流程示意图；
图7是本发明实施例提供的控制方法的一个可选的流程示意图；
图8是本发明实施例提供的控制方法的一个可选的流程示意图；
图9是本发明实施例提供的控制方法的一个可选的流程示意图；
图10是本发明实施例提供的控制方法的一个可选的流程示意图；
图11是本发明实施例提供的控制方法的一个可选的流程示意图；
图12是本发明实施例提供的控制方法的一个可选的流程示意图；
图13是本发明实施例提供的控制方法的一个可选的流程示意图；
图14是本发明实施例提供的控制方法的一个可选的流程示意图；
图15是本发明实施例提供的CHIP设备的一个可选的结构示意图；
图16是本发明实施例提供的配置设备的一个可选的结构示意图；
图17是本发明实施例提供的配置设备的一个可选的结构示意图；
图18是本发明实施例提供的服务器的一个可选的结构示意图；
图19是本发明实施例提供的电子设备的一个可选的结构示意图。
具体实施方式
为了使本发明的目的、技术方案和优点更加清楚，下面将结合附图对本发明作进一步地详细描述，所描述的实施例不应视为对本发明的限制，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其它实施例，都属于本发明保护的范围。
在对本发明实施例提供的控制方法进行详细说明之前，先对CHIP设备和配置设备的绑定进行简要说明。
在物联网中，平台为CHIP设备分配操作标识符，且在所分配的操作标识符和待绑定的账号之间建立关联关系，从而在该CHIP设备和该账号之间建立绑定关系，将该CHIP设备和该账号进行绑定，在该CHIP设备和使用该账号的配置设备之间进行安全通信。一个CHIP设备一次只能绑定一个账号，只能由使用所绑定的账号的配置设备对该CHIP设备进行配置。CHIP设备和账号的绑定在CHIP设备接入平台的过程中执行。
本发明实施例中，平台为运行在服务器上的信息处理系统，不同的平台之间可相互独立。其中，对于同一CHIP设备，可运行不同商场的应用程序，该商家的平台仅支持该商家的应用程序的接入。可选地，平台为生态云的云平台。
CHIP设备接入平台的方法如图1所示，包括：
S101、CHIP设备生成密钥；
CHIP设备出厂时通过根据密钥派生算法对个人识别密码(Personal Identification Number Code，PIN Code)进行计算，生成密钥(secret)，并将生成的secret)存入CHIP设备中。
这里，密钥派生算法可为基于密码的密钥派生功能(Password-Based Key Derivation Function，PBKDF)。
S102、配置设备获取CHIP设备的PIN Code；
这里，用户拿到该CHIP设备，可通过配置设备上的APP扫描CHIP设备上的二维码以获取该CHIP设备的PIN Code。在CHIP设备无二维码的情况下，用户也可在配置设备上手动输入PIN Code。配置设备上的APP承担CHIP设备的配置器角色。
S103、配置设备根据PIN Code生成密钥；
配置设备通过密钥派生算法对PIN Code进行计算，生成secret。
配置设备生成密钥后，根据生成的secret通过基于口令认证密钥交换(Password-based Authentication Key Exchange，PAKE)算法对与CHIP设备通信的数据进行加密，CHIP设备侧根据secret通过PAKE对数据进行校验，从而建立配置设备与CHIP设备间的安全信道，进行安全通信。
其中，下述步骤S104至S105基于建立的安全信道进行安全通信。
S104、配置设备对CHIP设备进行配网；
在安全信道建立的基础上，配置设备将所接入的接入点(Access Point，AP)的服务集标识(Service Set Identifier，SSID)和密码发送至CHIP设备，CHIP设备通过接收到的SSID和密码成功连接至AP，AP为所连接的CHIP设备分配IP地址等信息，使得CHIP设备接入AP，通过AP访问网络侧的平台。
S105、CHIP设备在配网成功后，进行设备认证。
S106、设备认证成功后，CHIP设备与配置设备根据证书进行安全通信。
其中，S105的执行包括：
S1051、配置设备向CHIP设备发送获取操作证书签名请求(Operational Certificate Signing Request，OpCSR)的请求；
配置设备发送的请求携带随机数(nonce)。
S1052、CHIP设备生成OpCSR，并对OpCSR签名；
CHIP设备生成包括操作公钥和操作私钥(Op Private Key)的操作密钥对(Op Key Pair)，并形成OpCSR。其中，OpCSR包括：CHIP设备的操作公钥、配置设备发来的nounce和CHIP设备需要 被认证的信息；其中，CHIP设备需要被认证的信息包括：设备产品认证(Product Attestation，PA)证书、PA中间证书、设备认证块，PA证书中携带认证公钥。
CHIP设备形成OpCSR后，使用CHIP设备操作私钥对OpCSR进行一次签名，再通过CHIP设备认证私钥(Att Private Key)对经过一次签名的OpCSR进行二次签名。
S1053、CHIP设备将OpCSR数据返回给手机。
CHIP设备在完成签名后，将OpCSR和对OpCSR签名后的数据发送至配置设备，这里，将OpCSR和对OpCSR签名后的数据称为OpCSR数据。
S1054、配置设备对认证进行有效性验证。
配置设备获取到OpCSR数据后，通过CHIP设备PA证书中存放的认证公钥，对认证(Attestation)进行有效性验证。其中，该步骤为可选步骤。
S1055、配置设备将OpCSR数据发送给服务器。
配置设备将OpCSR和对OpCSR签名后的数据发送给实施为服务器，其中，该服务器运行有配置设备的APP所属的平台。这里，平台可为云平台即生态云。
S1056、服务器对CHIP设备进行校验，并在校验通过后，生成操作标识符(Op ID)和操作证书(Op Cert)；
服务器通过操作公钥核实CHIP设备是否持有操作私钥，以对CHIP设备进行操作校验。服务器通在操作校验成功后，为CHIP设备生成Op ID和Op Cert。
在S1056中，服务器还可通过认证公钥对认证进行有效性验证。需要说明的是，当配置设备侧执行认证的有效性验证，则服务器侧不执行认证的有效性验证。当配置设备侧未执行认证的有效性验证，则服务器侧可执行认证的有效性验证。
在S1056中，服务器为该CHIP设备生成Op ID后，在Op ID和配置设备使用的账号之间建立关联关系，从而将该CHIP设备和该配置设备的账号绑定。其中，Op ID用于平台对该CHIP设备进行识别。其中，配置设备使用的账号用于该配置设备访问服务器上所运行的平台下的账号。
S1057、服务器将Op ID、Op Cert、操作中间证书(Operation Intermediate Certificate(s)，ICs)返回给配置设备；
S1058、配置设备将Op ID、Op Cert和ICs发送至CHIP设备；
S1059、CHIP设备校验Op Cert是否与认证公钥匹配，在匹配时存储Op ID、Op Cert和ICs。
其中，CHIP设备通过认证私钥对Op Cert进行校验。
图1中的配置终端可为移动终端等能够对CHIP设备进行配置的终端，
CHIP设备是能够基于IP地址接入家庭网络，且实现某项最基本功能的物联网设备，如开关、门锁、冰箱等。
上述方案中，CHIP设备与当前的配置设备的账号绑定后，只能由该配置设备进行配置，并基于该配置设备接入网络，无法由使用其他账号的配置设备对该CHIP设备进行配置，或基于其他的配置设备接入网络。
基于上述问题，本发明提供一种控制方法，本发明实施例的控制方法可以应用于图2或图3所示的物联网系统200，包括：CHIP设备201、配置设备202、配置设备203。其中，配置设备202使用第一账号，配置设备203使用第二账号，第一账号为第一平台下的账号，第二账号为第二平台下的账号。
在一示例中，如图2所示，第一平台和第二平台为同一平台，且该平台运行在服务器204上。
在一示例中，如图3所示，第一平台和第二平台为不同的平台，第一平台运行在服务器204上，第二平台运行在服务器205上。
当CHIP设备201与第一账号绑定，则使用第一账号的配置设备202能够对CHIP设备201进行配置，且CHIP设备201基于配置设备202与第一平台进行交互。
当CHIP设备201与第二账号绑定，则使用第二账号的配置设备203能够对CHIP设备201进行配置，且CHIP设备201基于配置设备203与第二平台进行交互。
CHIP设备201、配置设备202或配置设备203可以指接入终端、用户设备(User Equipment，UE)、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。接入终端可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、5G网络中的CHIP设备或者未来演进的PLMN中的设备等。
图2示例性地示出了两个配置设备和一个平台，图3示例性地示出了两个配置设备和两个平台，可选地，该物联网系统200可以包括两个以上的配置设备以及与两个以上的平台，本发明实施例对此不做限定，且一个平台下的账号的数量不进行任何的限制。
图2或图3所示的CHIP设备还可包括：传感器、激光扫描系统和智能家电等物联网设备。
图2或图3所示的服务器可为一个独立的计算机设备，也可为一个由多个计算机设备构成的服务器集群。
本发明实施例提供的控制方法的一种可选的处理流程，如图4所示，包括以下步骤：
S401、CHIP设备在建立有与第一账号的第一绑定关系的情况下，满足原绑定关系解除条件。
本发明实施例中，CHIP设备当前存储有由第一账号所属的第一平台生成的操作标识符，且操作标识符与第一账号之间具有关联关系，即CHIP设备建立有与第一账号的第一绑定关系。
可选地，CHIP设备检测到以下事件至少之一，则满足原绑定关系解除条件：
事件一、完成所述第二配置设备的配网；
事件二、接收到用于指示恢复出厂设置的指令。
以CHIP设备检测到事件一为例，CHIP设备在以下场景检测到事件一：场景一、CHIP设备由第二设备配网。
在场景一下，CHIP设备在建立有与第一账号的绑定关系的情况下，与第二配置设备建立安全信道，并基于所建立的安全信道通过第二配置设备进行配网，以接入网络。
这里，第二配置设备获取CHIP设备的PIN code，并基于PIN code生成与CHIP设备进行安全信道所需的secret后，对CHIP设备进行配网。其中，在安全信道建立的基础上，第二配置设备将所接入的AP的SSID和密码发送至CHIP设备，CHIP设备通过接收到的SSID和密码成功连接至AP，AP为所连接的CHIP设备分配IP地址等信息，使得CHIP设备接入AP，通过AP访问网络侧的平台。
这里，第二配置设备获取CHIP设备的PIN code的方式可包括以下方式之一：
方式一、扫描CHIP设备上的二维码；其中，CHIP设备上的二维码携带的信息包括CHIP设备的PIN code。
方式二、接收用户的输入操作；其中，用户的输入操作的输入内容为CHIP设备的PIN code。
以CHIP设备检测到事件二为例，CHIP设备在以下场景检测到事件二：场景二、恢复出厂设置。
在一示例中，CHIP设备根据用户输入的出厂设置恢复操作接收到指示恢复出厂设置指令。在一示例中，CHIP设备接收到使用第一账号的第一配置设备发送的指示恢复出厂设置的指令。
S402、CHIP设备解除所述第一绑定关系，与所述第二账号建立第二绑定关系。
在CHIP设备在建立有第一绑定关系的情况下，满足原绑定关系解除条件的情况下，解除原有的第一绑定关系，与第二配置设备使用的第二账号建立新的绑定关系即第二绑定关系。
比如：CHIP设备在与配置设备A使用的账号A建立有绑定关系的情况下，通过使用账号B的配置设备B配网，解除与账号A的绑定关系，建立与账号B的绑定关系。
可选地，所述第一账号与所述第二账号为不同平台下的账号。
可选地，所述第一账号和第二账号为同一平台下的账号。
本发明实施例中，CHIP设备解除第一账号关系，包括：删除存储的第一绑定关系，并指示使用第一账号的第一配置设备和/或第一平台解除所存储的第一绑定关系。其中，CHIP设备删除存储的第一绑定关系与指示第一配置设备和/或第一平台解除所存储的第一绑定关系的先后顺序不进行限定。
可选地，CHIP设备删除存储的第一绑定关系后，指示第一配置设备和/或第一平台解除所存储的第一绑定关系。可选地，CHIP设备指示第一配置设备和/或第一平台解除所存储的第一绑定关系后，删除存储的第一绑定关系。
可选地，CHIP设备指示在第一配置设备和/或第一平台中解除第一绑定关系，包括：CHIP设备向第一配置设备和/或第一服务器发送解除原绑定关系请求，其中，第一服务器运行有第一平台。可选地，CHIP设备向第一配置设备发送解除原绑定关系请求。可选地，CHIP设备向第一服务器发送解除原绑定关系请求，第一服务器将解除原绑定关系请求转发至第一配置设备。可选地，CHIP设备向第一配置设备发送解除原绑定关系请求，向第一服务器发送解除原绑定关系请求。
本发明实施例中，解除原绑定关系请求中携带有CHIP设备的操作标识符和第一账号，以指示 解除操作标识符和第一账号之间的关联关系，从而解除CHIP设备和第一账号的第一绑定关系。
CHIP设备在解除第一绑定关系之后，建立与第二账号的第二绑定关系，使得第二配置设备对所述CHIP设备进行配置。其中，CHIP设备在与第二配置设备进行设备认证过程中，完成第二绑定关系的建立。
在场景一下，CHIP设备在联网状态下，接收到指示恢复出厂设置的指令，解除存储的第一绑定关系；CHIP设备在未联网状态下，接收到指示恢复出厂设置的指令，则使用第一配置设备发送的SSID和密码联网，从未联网状态切换为联网状态，并在联网状态下解除存储的第一绑定关系。
CHIP设备在解除第一绑定关系之后，恢复出厂设置，在完成出厂设置恢复后，与第二配置设备建立安全信道。CHIP设备与第二配置设备建立安全信道后，通过第二配置设备配网，与第二配置设备进行设备认证。
在本发明实施例中，在场景二下，如图5所示，在S402之前，包括：
S403，所述CHIP设备将标识信息和/或平台信息发送至所述第二配置设备；
标识信息用于表征CHIP设备，可选地，标识信息包括：操作标识符、设备信息等。平台信息用于表征第一账号所属的平台。可选地，平台信息包括：对平台进行唯一标识的平台标识符、平台的状态信息、与CHIP设备关联的信息等。其中，与CHIP设备关联的信息包括：账号信息、Op Cert和ICs等。
当第二配置设备接收到CHIP设备发送的标识信息和/或平台信息后，根据接收的标识信息和/或平台信息，检测CHIP设备绑定的账号是否为第二账号。第二配置设备在未存储操作标识符或平台信息中的账号信息的情况下，确定CHIP设备绑定的账号不是第二账号，则认为CHIP设备已建立绑定关系。
第二配置设备在确定CHIP设备绑定的账号不是第二账号的情况下，向CHIP设备发送解除原绑定关系指示，以指示CHIP设备解除已建立的绑定关系即第一绑定关系，并建立与第二账号的第二绑定关系。
S404，所述CHIP设备接收所述第二配置设备发送的解除原绑定关系指示；
S402的执行包括S4021：CHIP设备在接收到所述解除原绑定关系指示的情况下，解除所述第一绑定关系，与所述第二账号建立第二绑定关系。
本发明实施例中，S402中解除第一绑定关系的实施包括以下两种实施方式之一：
实施方式一、向第一服务器发送解除原绑定关系请求；接收所述第一服务器发送的原绑定关系解除成功响应。第一服务器器运行有第一账号所属的第一平台。
实施方式二、向使用所述第一账号的第一配置设备发送解除原绑定关系请求；接收所述第一配置设备发送的原绑定关系解除成功响应。
以S402的实施为实施方式一为例，CHIP设备向第一服务器发送解除原绑定关系请求以指示第一平台删除第一绑定关系，由第一服务器指示第一配置设备解除存储的第一绑定关系。
可选地，当第一服务器接收到解除原绑定关系请求后，将解除原绑定关系请求转发至第一配置器，以指示第一配置器解除存储的第一绑定关系；第一配置器在接收到解除原绑定关系请求的情况下，解除存储的第一绑定关系后，向第一服务器返回原绑定关系删除请求，以指示第一服务器解除存储的第一绑定关系；第一服务器在接收到的原绑定关系删除请求的情况下，删除第一绑定关系后，向第一配置设备返回原绑定关系解除成功响应，以指示在第一配置器中解除了第一绑定关系，且在第一服务器中删除第一绑定关系，从而在物联网系统中完成第一绑定关系的解除。
以S402的实施为实施方式二为例，CHIP设备向第一配置器发送解除原绑定关系请求以指示第一配置设备解除存储的第一绑定关系，由第一配置设备指示第一平台删除第一绑定关系。
可选地，当第一配置器接收到解除原绑定关系请求后，第一配置器在接收到的解除原绑定关系请求的情况下，解除存储的所述第一绑定关系后，向第一服务器返回原绑定关系删除请求，以指示第一服务器解除存储的第一绑定关系；第一服务器在接收到的原绑定关系删除请求的情况下，删除第一绑定关系后，向CHIP设备返回原绑定关系解除成功响应，以指示在第一配置器中解除了第一绑定关系，且在第一服务器中删除第一绑定关系，从而在物联网系统中完成第一绑定关系的解除。
本发明实施例中，在场景二下，CHIP设备在接收到原绑定关系解除成功响应后，还执行以下步骤：发送原绑定关系解除成功通知至所述第二配置设备。
CHIP设备在确定物联网系统中完成第一绑定关系的解除后，向第二配置设备发送原绑定关系解除成功通知，以指示第二配置设备第一绑定关系完成解除，第二配置设备在接收到原绑定关系解除 成功通知的情况下，与CHIP设备进行设备认证。在CHIP设备与第二配置设备的认证过程中，第二设备设备使用的第二账号所属的第二平台向CHIP设备配置新操作标识符，并在新的操作标识符和第二账号之间建立关联关系，以在CHIP设备和第二账号之间建立绑定关系即第二绑定关系。
本发明实施例中，在解除原绑定关系请求、解除原绑定关系指示、删除原绑定关系请求、原绑定关系解除成功响应和/或原绑定关系解除成功通知中可携带第一绑定关系。
本发明实施例提供的控制方法的一种可选的处理流程，如图6所示，包括以下步骤：
S601、第一配置设备接收用于指示解除第一绑定关系的解除原绑定关系请求；
所述第一绑定关系为CHIP设备与所述第一配置设备使用的第一账号的绑定关系。
CHIP设备在建立有第一绑定关系的情况下，满足原绑定关系解除条件，则需要解除第一绑定关系。其中，CHIP设备删除存储的第一绑定关系，并指示在第一配置设备和/或第一平台中解除第一绑定关系。
本发明实施例中，所述解除原绑定关系请求是从所述CHIP设备或第一服务器接收的。
CHIP设备指示在第一配置设备和/或第一平台中解除第一绑定关系，包括：CHIP设备向第一配置设备和/或第一服务器发送解除原绑定关系请求，其中，第一服务器运行有第一账号所属的第一平台。
可选地，CHIP设备向第一配置设备发送解除原绑定关系请求，此时，第一配置设备接收到CHIP设备发送的解除原绑定关系请求。
可选地，CHIP设备向第一服务器发送解除原绑定关系请求，第一服务器将解除原绑定关系请求转发至第一配置设备，此时，第一配置设备接收到第一服务器发送的解除原绑定关系请求。
S602、所述第一配置设备解除存储的所述第一绑定关系。
第一配置设备解除存储的第一绑定关系，使得所述CHIP设备能够与第二账号建立第二绑定关系，以由使用所述第二账号的第二配置设备对所述CHIP设备进行配置。
第一配置设备将存储的操作标识和第一账号之间的关联关系取消，以完成存储的第一绑定关系的解除。其中，第一绑定关系中的操作标识符为第一服务器为CHIP设备配置的操作标识符。
本发明实施例中，第一配置设备在解除存储的第一绑定关系之前，可输出第一绑定关系解除提示。第一配置设备在接收到用户针对第一绑定关系解除提示的确定操作的情况下，得到用户的授权，并在得到用户的授权的情况下解除存储的第一绑定关系。
本发明实施例中，在S602之后，还包括：在存储的所述第一绑定关系的解除的情况下，发送原绑定关系删除请求至所述第一账号所属的第一服务器，所述原绑定关系删除请求用于指示所述第一服务器删除所述第一绑定关系。
第一配置设备完成存储的第一绑定关系的解除后，向第一服务器发送原绑定关系删除请求，指示第一服务器删除存储的第一绑定关系。
可选地，在第一配置设备接收到第一服务器发送的解除原绑定关系请求的情况下，第一服务器在完成第一绑定关系的上删除后，向CHIP设备返回原绑定关系解除成功响应。
可选地，在第一配置设备接收到CHIP设备发送的解除原绑定关系请求的情况下，第一服务器在完成第一绑定关系的上删除后，向第一配置设备返回原绑定关系解除成功响应，第一配置设备将原绑定关系解除成功响应转发至CHIP设备。
可选地，所述第一账号与所述第二账号为不同平台下的账号。此时，第一账号为第一平台下的账号，第二账号为第二平台下的账号，运行第一平台的第一服务器与运行第二账号的第二服务器为不同的服务器。
可选地，所述第一账号与所述第二账号为同一平台下的账号。此时，第一账号为第一平台下的账号，第二账号为第二平台下的账号，运行第一平台的第一服务器与运行第二账号的第二服务器为同一服务器。
本发明实施例提供的控制方法的一种可选的处理流程，如图7所示，包括以下步骤：
S701、第二配置设备向CHIP设备配网；
S702、所述第二配置设备在确定所述CHIP设备建立有与第一账号的第一绑定关系的情况下，向所述CHIP设备发送解除原绑定关系指示。
所述解除原绑定关系指示用于指示所述CHIP设备解除所述第一绑定关系，并建立与所述第二配置设备使用的第二账号的第二绑定关系，以由所述第二配置设备对所述CHIP设备进行配置。
本发明实施例中，在S701之前，所述第二配置设备接收所述CHIP设备发送的标识信息和/或平台信息；所述标识信息和/或所述平台信息用于检测所述CHIP设备是否建立有所述第一绑定关系。
平台信息用于表征第一账号所属的平台。可选地，平台信息包括：对平台进行唯一标识的平台标识符、平台的状态信息、与操作标识符关联的信息等。其中，与操作标识符关联的信息可包括：账号信息、Op Cert和ICs等。可选地，账号信息包括：第一账号。
当第二配置设备接收到CHIP设备发送的标识信息和/或平台信息后，根据接收的标识信息和/或平台信息，判断CHIP设备绑定的账号是否为第二账号。第二配置设备在未存储接收的操作标识符或平台信息中的账号信息的情况下，确定CHIP设备绑定的账号不是第二账号，则认为CHIP设备已建立绑定关系。
第二配置设备在确定CHIP设备绑定的账号不是第二账号的情况下，向CHIP设备发送解除原绑定关系指示，以指示CHIP设备解除已建立的绑定关系即第一绑定关系，并建立与第二账号的第二绑定关系。
可选地，所述第一账号与所述第二账号为不同平台下的账号。可选地，所述第一账号与所述第二账号为同一平台下的账号。
可选地，在场景一下，第二配置设备接收CHIP设备发送的原账号解除成功通知，原账号解除成功通知指示CHIP设备已完成第一绑定关系的解除，第二配置设备在接收到的原账号解除通知的情况下，与CHIP设备进行设备认证。
本发明实施例提供的控制方法的一种可选的处理流程，如图8所示，包括以下步骤：
S801、服务器接收原绑定关系删除请求；
S802、服务器删除CHIP设备与第一账号的第一绑定关系。
服务器在接收的原绑定关系删除请求的请求下，删除CHIP设备与第一账号的第一绑定关系。
所述CHIP设备在建立有所述第一绑定关系的情况下，满足原绑定关系解除条件，则解除所述第一绑定关系，并与第二账号建立第二绑定关系，以由使用所述第二账号的第二配置设备对所述CHIP设备进行配置。
这里的服务器为第一服务器，第一服务器运行有第一账号所属的第一平台。
可选地，所述第一账号与所述第二账号为不同平台下的账号。此时，第一账号为第一平台下的账号，第二账号为第二平台下的账号，运行第一平台的第一服务器与运行第二账号的第二服务器为不同的服务器。
可选地，所述第一账号与所述第二账号为同一平台下的账号。此时，第一账号为第一平台下的账号，第二账号为第二平台下的账号，运行第一平台的第一服务器与运行第二账号的第二服务器为同一服务器。
CHIP设备在解除第一绑定关系的过程中，删除存储的第一绑定关系，并指示第一配置设备和/或第一平台解除第一绑定关系。
可选地，CHIP设备指示第一配置设备解除第一绑定关系，包括：CHIP设备向服务器发送解除原绑定关系请求。此时，所述服务器从所述CHIP设备接收解除原绑定关系请求；所述服务器将所述原绑定关系请求，转发至使用所述第一账号的第一配置设备，以指示所述第一配置设备解除存储的所述第一绑定关系。
可选地，CHIP设备指示第一配置设备解除存储的第一绑定关系，包括：
指示方式一、CHIP设备向第一配置设备发送解除原绑定关系请求；
指示方式二、CHIP设备向服务器发送解除原绑定关系请求，服务器将接收的解除原绑定关系请求转发至服务器。
第一配置设备在从CHIP设备或服务器接收的解除原绑定关系请求的请求下，解除存储的第一绑定关系，在存储的第一绑定关系解除后，向服务器发送原绑定关系删除请求，所述服务器接收所述第一配置设备发送的原绑定关系删除请求。
服务器在完成第一绑定关系删除请求后，发出原绑定关系解除成功响应。以指示方式一为例，服务器向第一配置设备发送原绑定关系解除成功响应，且向第一配置设备将接收的原绑定关系解除成功响应转发至CHIP设备，指示服务器和第一配置设备完成第一绑定关系的删除或解除。指示方式二为例，服务器向CHIP设备发送原绑定关系解除成功响应，指示服务器和第一配置设备完成第一绑定关系的删除或解除。
本发明实施例提供的控制方法，包括：CHIP设备在建立有与第一账号的第一绑定关系的情况下，通过使用第二账号的第二配置设备配网，则解除所述第一绑定关系，并与所述第二账号建立第二绑定关系，以由所述第二配置设备对所述CHIP设备进行配置。使得CHIP设备在建立有绑定关系的情况下，被其他配置设备配网，则删除原有的绑定关系，并指示原有的配置设备和服务器解除原有的 绑定关系，并在CHIP设备、原有的配置设备和服务器中分别解除原有的绑定关系的情况下，建立与新的配置设备的账号建立绑定关系，由于新的配置设备能够对该CHIP设备进行配置，解除了CHIP设备仅由一个配置设备进行配置的限制。
下面，本发明实施例以配置设备为手机、CHIP设备为CHIP设备为例，通过不同的应用场景对提供的控制方法进行说明。
实例一
手机A的账号A为平台A上的账号；手机B的账号B为平台B上的账号。其中，CHIP设备已经与账号B建立绑定关系，并存储了B平台为CHIP设备配置的Op ID、B平台的平台信息等信息，CHIP设备解除与账号B的绑定关系的步骤，如图9所示，包括：
S901，CHIP设备与手机A通过PIN code建立安全连接；
S902，手机A为CHIP设备配网；
手机A希望将CHIP设备接入到平台A，对CHIP设备进行重新配网。
S903，CHIP设备向手机A发送Op ID和平台B的平台信息；
CHIP设备连上网络后，向手机A发送Op ID和平台B的平台信息。
S904，手机A通过Op ID和平台B的平台信息，判断该CHIP设备不属于平台A；
S905，手机A向CHIP设备发送解除设备绑定关系指示；
其中，解除设备绑定关系指示也可称为解除原绑定关系指示。
S906，CHIP设备向平台B发送解除设备绑定关系的请求；
S907，平台B向手机B发送解除设备绑定关系的请求；
其中，解除设备绑定关系确认的请求也可称为解除原绑定关系请求。
S908，手机B执行CHIP设备与手机B绑定关系的解除；
手机B接收平台B发来的解除设备绑定关系的请求后，手机B授权，并确定执行CHIP设备与手机B绑定关系的解除。
S909，手机B向平台B发送删除绑定关系的请求；
送删除绑定关系的请求也可称为原绑定关系删除请求。
S9010，平台B删除CHIP设备与手机B间的绑定关系；
S9011，平台B向CHIP设备返回绑定关系已解除成功响应；
S9012，CHIP设备将与平台B间关系已解除的状态发送给手机A；
这里，所发送的状态可携带在原绑定关系解除成功通知中。
S9013，手机A确认CHIP设备已经与其它手机不存在绑定关系；
S9014，平台A与CHIP设备进行设备认证；
其中，平台A与CHIP设备进行设备认证过程中，建立CHIP设备与账号A的绑定关系。
实例二
手机A的账号A为平台A上的账号；手机B的账号B为平台B上的账号。其中，CHIP设备已经与账号B建立绑定关系，并存储了B平台为CHIP设备配置的Op ID、B平台的平台信息等信息，CHIP设备解除与账号B的绑定关系的步骤，如图10所示，包括：
S1001，CHIP设备与手机A通过PIN code建立安全连接；
S1002，手机A为CHIP设备配网；
手机A希望将CHIP设备接入到平台A，对CHIP设备进行重新配网。
S1003，CHIP设备向手机A发送Op ID和平台B的平台信息；
CHIP设备连上网络后，向手机A发送Op ID和平台B的平台信息。
S1004，手机A通过Op ID和平台B的平台信息，判断该CHIP设备不属于平台A；
S1005，手机A向CHIP设备发送解除设备绑定关系指示；
解除原绑定关系指示用于指示CHIP设备解除CHIP设备与账号B的绑定关系。
S1006，CHIP设备向手机B发送解除设备绑定关系的请求；
S1007，手机B执行CHIP设备与手机B绑定关系的解除；
手机B接收CHIP设备发来的解除绑定关系的请求后，手机B授权，并确定执行CHIP设备与手机B绑定关系的解除。
S1008，手机B向平台B发送删除绑定关系的请求；
S1009，平台B删除CHIP设备与手机B间的绑定关系；
S1010，平台B向手机B返回绑定关系已解除成功响应；
S1011，手机B向CHIP设备返回绑定关系已解除成功响应；
S1012，CHIP设备将与平台B间关系已解除的状态发送给手机A；
S1013，手机A确认CHIP设备已经与其它手机不存在绑定关系；
S1014，平台A与CHIP设备进行设备认证；
其中，平台A与CHIP设备进行认证过程中，建立CHIP设备与账号A的绑定关系。
实例三
手机A1的账号A1和手机A2的账号A2为平台A上的账号。其中，CHIP设备已经与账号A2建立绑定关系，并存储了A平台为CHIP设备配置的Op ID、A平台的平台信息等信息，CHIP设备解除与账号A2的绑定关系的步骤，如图11所示，包括：
S1101，CHIP设备与手机A1通过PIN code建立安全连接；
S1102，手机A1为CHIP设备配网；
手机A1希望将CHIP设备与账号A1绑定，对CHIP设备进行重新配网。
S1103，CHIP设备向手机A1发送Op ID和平台A的平台信息；
CHIP设备连上网络后，向手机A1发送Op ID和平台1的平台信息。
S1104，手机A1通过Op ID和平台A的平台信息，判断该CHIP设备已经与账号A1绑定；
S1105，手机A1向CHIP设备发送解除设备绑定关系指示；
解除原绑定关系指示用于指示CHIP设备解除CHIP设备与账号A2的绑定关系。
S1106，CHIP设备向平台A发送解除设备绑定关系的请求；
S1107，平台A向手机A2发送解除设备绑定关系确认的请求；
S1108，手机A2执行CHIP设备与手机A2绑定关系的解除；
手机A2接收平台A发来的解除绑定关系的请求后，手机A2授权，并确定执行CHIP设备与手机A2绑定关系的解除。
S1109，手机A2向平台A发送删除绑定关系的请求；
S1110，平台A删除CHIP设备与手机A2间的绑定关系；
S1111，平台A向CHIP设备返回绑定关系已解除成功响应；
S1112，CHIP设备将与账号A2间关系已解除的状态发送给手机A1；
S1113，手机A1确认CHIP设备已经与其它手机不存在绑定关系；
S1114，手机A1与CHIP设备进行认证；
其中，手机A1与CHIP设备进行认证过程中，建立CHIP设备与账号A1的绑定关系。
实例四
手机A1的账号A1和手机A2的账号A2为平台A上的账号。其中，CHIP设备已经与账号A2建立绑定关系，并存储了A平台为CHIP设备配置的Op ID、A平台的平台信息等信息，CHIP设备解除与账号A2的绑定关系的步骤，如图12所示，包括：
S1201，CHIP设备与手机A1通过PIN code建立安全连接；
S1202，手机A1为CHIP设备配网；
手机A1希望将CHIP设备与账号A1绑定，对CHIP设备进行重新配网。
S1203，CHIP设备向手机A1发送Op ID和平台A的平台信息；
CHIP设备连上网络后，向手机A1发送Op ID和平台A的平台信息。
S1204，手机A1通过Op ID和平台B的平台信息，判断该CHIP设备已经与账号A1绑定；
S1205，手机A1向CHIP设备发送解除设备绑定关系指示；
解除原绑定关系指示用于指示CHIP设备解除CHIP设备与账号A2的绑定关系。
S1206，CHIP设备向手机A1发送解除设备绑定关系的请求；
S1207，手机A1执行CHIP设备与手机A2绑定关系的解除；
手机A2接收CHIP设备发来的解除绑定关系的请求后，手机A2授权，并确定执行CHIP设备与手机A2绑定关系的解除。
S1208，手机A2向平台A发送删除绑定关系的请求；
S1209，平台A删除CHIP设备与手机A2间的绑定关系；
S1210，平台A向手机A2返回绑定关系已解除成功响应；
S1211，手机A2向CHIP设备返回绑定关系已解除成功响应；
S1212，CHIP设备将与账号A2间关绑定系已解除的状态发送给手机A；
S1213，手机A1确认CHIP设备已经与其它手机不存在绑定关系；
S1214，手机A1与CHIP设备进行认证；
其中，手机A1与CHIP设备进行认证过程中，建立CHIP设备与账号A1的绑定关系。
实例五
手机A使用的账号A为平台A下的账号；手机B使用的账号B为平台B下的账号。其中，CHIP设备已经与账号B建立绑定关系，并存储了B平台为CHIP设备配置的Op ID、B平台的平台信息等信息，CHIP设备解除与账号B的绑定关系的步骤，如图13所示，包括：
S1301，CHIP设备接收到指示恢复出厂设置的指令；
S1302，CHIP设备联网；
S1303，CHIP设备向平台B发送解除设备绑定关系的请求；
S1304，平台B向手机B发送解除设备绑定关系确认的请求；
S1305，手机B执行CHIP设备与手机B绑定关系的解除；
手机B接收平台B发来的解除绑定关系的请求后，手机B授权，并确定执行CHIP设备与手机B绑定关系的解除。
S1306，手机B向平台B发送绑定关系删除请求；
绑定关系删除请求指示平台B删除CHIP设备与手机B间的绑定关系。
S1307，平台B删除CHIP设备与手机B间的绑定关系；
S1308，平台B向CHIP设备返回绑定关系已解除成功响应；
S1309，CHIP设备解除自身的绑定关系；
S1310，手机A与CHIP设备建立安全通道；
S1311，手机A为CHIP设备配网；
S1312，平台A与CHIP设备进行设备认证。
实例六
手机A使用的账号A为平台A下的账号；手机B使用的账号B为平台B下的账号。其中，CHIP设备已经与账号B建立绑定关系，并存储了B平台为CHIP设备配置的Op ID、B平台的平台信息等信息，CHIP设备解除与账号B的绑定关系的步骤，如图14所示，包括：
S1401，CHIP设备接收到指示恢复出厂设置的指令；
S1402，CHIP设备联网；
S1403，CHIP设备向手机B发送解除设备绑定关系的请求；
S1404，手机B执行CHIP设备与手机B绑定关系的解除；
手机B接收平台B发来的解除绑定关系的请求后，手机B取得授权，并执行CHIP设备与手机B绑定关系的解除。
S1405，手机B向平台B发送绑定关系删除请求；
绑定关系删除请求指示平台B删除CHIP设备与手机B间的绑定关系。
S1406，平台B删除CHIP设备与手机B间的绑定关系；
S1407，平台B向手机B返回绑定关系已解除成功响应；
S1408，手机B向CHIP设备返回绑定关系已解除成功响应；
S1409，CHIP设备解除自身的绑定关系；
S1410，手机A与CHIP设备建立安全通道；
S1411，手机A为CHIP设备配网；
S1412，平台A为CHIP设备进行设备认证。
CHIP设备只能有使用所绑定的账号的配置设备配置，当CHIP设备已建立有绑定关系的情况下，无法建立与其它的账号的绑定关系，本发明实施例提供的控制方法，当CHIP设备已建立有绑定关系的情况下，需要与其他的账号建立新的绑定关系，则在自身将已建立的绑定关系解除，且将原有的配置设备中存储的绑定关系解除，以及将原平台中的绑定关系删除，从而彻底将原绑定关系从物联网系统中删除，避免仅在CHIP设备中解除原绑定关系的情况下，配置设备和原平台中账号资源的无效占用，并释放操作符资源。
为实现上述控制方法，本发明实施例还提供一种CHIP设备201，如图15所示，包括：
解除模块1501，配置为在建立有与第一账号的第一绑定关系的情况下，满足原绑定关系解除条件，解除所述第一绑定关系，与所述第二账号建立第二绑定关系，以由使用所述第二账号的第二配置设备对所述CHIP设备进行配置。
本发明实施例中，解除模块1501，还配置为检测到以下事件至少之一，则确定满足原绑定关系解除条件：
完成所述第二配置设备的配网；
接收到用于指示恢复出厂设置的指令。
本发明实施例中，所述第一账号与所述第二账号为不同平台下的账号。
本发明实施例中，所述第一账号与所述第二账号为同一平台下的账号。
本发明实施例中，所述CHIP设备还包括：
第一发送模块，配置为将标识信息和/或平台信息发送至所述第二配置设备；
第一接收模块，配置为接收所述第二配置设备发送的解除原绑定关系指示。
本发明实施例中，解除模块1501，还配置为：
向第一服务器发送解除原绑定关系请求；所述第一服务器运行有第一账号所属的第一平台；
接收所述第一服务器发送的原绑定关系解除成功响应。
本发明实施例中，解除模块1501，还配置为：
向使用所述第一账号的第一配置设备发送解除原绑定关系请求；
接收所述第一配置设备发送的原绑定关系解除成功响应。
本发明实施例中，解除模块1501，还配置为：
发送原绑定关系解除成功通知至所述第二配置设备。
本发明实施例还提供一种CHIP设备，包括处理器和用于存储能够在处理器上运行的计算机程序的存储器，其中，所述处理器用于运行所述计算机程序时，执行上述CHIP设备执行的控制方法的步骤。
为实现上述控制方法，本发明实施例还提供一种配置设备202，如图16所示，包括：
第二接收模块1601，配置为接收用于指示解除第一绑定关系的解除原绑定关系请求；所述第一绑定关系为CHIP设备与所述第一配置设备使用的第一账号的绑定关系；
执行模块1602，配置为解除存储的所述第一绑定关系，使得所述CHIP设备能够与第二账号建立第二绑定关系，以由使用所述第二账号的第二配置设备对所述CHIP设备进行配置。
本发明实施例中，配置设备202还包括：
第二发送模块，配置为发送原绑定关系删除请求至所述第一账号所属的第一服务器；所述第一服务器运行有所述第一账号所属的第一平台。
本发明实施例中，所述解除原绑定关系请求是从所述CHIP设备或第一服务器接收的。
本发明实施例中，所述第一账号与所述第二账号为不同平台下的账号。
本发明实施例中，所述第一账号与所述第二账号为同一平台下的账号。
本发明实施例还提供一种配置设备，包括处理器和用于存储能够在处理器上运行的计算机程序的存储器，其中，所述处理器用于运行所述计算机程序时，执行上述第一配置设备执行的控制方法的步骤。
为实现上述控制方法，本发明实施例还提供一种配置设备203，如图17所示，包括：
配网模块1701，配置为向CHIP设备配网；
第三发送模块1702，配置为在确定所述CHIP设备建立有与第一账号的第一绑定关系的情况下，向所述CHIP设备发送解除原绑定关系指示，所述解除原绑定关系指示用于指示所述CHIP设备解除所述第一绑定关系，建立与所述第二配置设备使用的第二账号的第二绑定关系，以由所述第二配置设备对所述CHIP设备进行配置。
本发明实施例中，配置设备203还包括：
第三接收模块，配置为接收所述CHIP设备发送的标识信息和/或平台信息；所述操作标识符和所述平台信息用于判断所述CHIP设备是否建立有所述第一绑定关系。
本发明实施例中，所述第一账号与所述第二账号为不同平台下的账号。
本发明实施例中，所述第一账号与所述第二账号为同一平台下的账号。
本发明实施例还提供一种配置设备，包括处理器和用于存储能够在处理器上运行的计算机程序的存储器，其中，所述处理器用于运行所述计算机程序时，执行上述第二配置设备执行的控制方法的步骤。
为实现上述控制方法，本发明实施例还提供一种服务器204，如图18所示，包括：
第四接收模块1801，配置接收的原绑定关系删除请求，
删除模块1802，配置为删除CHIP设备与第一账号的第一绑定关系；所述CHIP设备在建立有所述第一绑定关系的情况下，满足原绑定关系解除条件，解除所述第一绑定关系，与第二账号建立第二绑定关系，以由使用所述第二账号的第二配置设备对所述CHIP设备进行配置。
本发明实施例中，服务器204还包括：
第五接收模块，配置为接收所述第一配置设备发送的原绑定关系删除请求。
本发明实施例中，服务器204还包括：
第六接收模块，配置为从所述CHIP设备接收解除原绑定关系请求；
第四发送模块，配置为将所述原绑定关系请求，转发至使用所述第一账号的第一配置设备。
本发明实施例中，所述第一账号与所述第二账号为不同平台下的账号。
本发明实施例中，所述第一账号与所述第二账号为同一平台下的账号。
本发明实施例还提供一种配置设备，包括处理器和用于存储能够在处理器上运行的计算机程序的存储器，其中，所述处理器用于运行所述计算机程序时，执行上述服务器执行的控制方法的步骤。
图19是本发明实施例的电子设备(CHIP设备、配置上设备或服务器)的硬件组成结构示意图，电子设备1900包括：至少一个处理器1901、存储器1902和至少一个网络接口1904。电子设备1900中的各个组件通过总线系统1905耦合在一起。可理解，总线系统1905用于实现这些组件之间的连接通信。总线系统1905除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。但是为了清楚说明起见，在图19中将各种总线都标为总线系统1905。
可以理解，存储器1902可以是易失性存储器或非易失性存储器，也可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是ROM、可编程只读存储器(PROM，Programmable Read-Only Memory)、可擦除可编程只读存储器(EPROM，Erasable Programmable Read-Only Memory)、电可擦除可编程只读存储器(EEPROM，Electrically Erasable Programmable Read-Only Memory)、磁性随机存取存储器(FRAM，ferromagnetic random access memory)、快闪存储器(Flash Memory)、磁表面存储器、光盘、或只读光盘(CD-ROM，Compact Disc Read-Only Memory)；磁表面存储器可以是磁盘存储器或磁带存储器。易失性存储器可以是随机存取存储器(RAM，Random Access Memory)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(SRAM，Static Random Access Memory)、同步静态随机存取存储器(SSRAM，Synchronous Static Random Access Memory)、动态随机存取存储器(DRAM，Dynamic Random Access Memory)、同步动态随机存取存储器(SDRAM，Synchronous Dynamic Random Access Memory)、双倍数据速率同步动态随机存取存储器(DDRSDRAM，Double Data Rate Synchronous Dynamic Random Access Memory)、增强型同步动态随机存取存储器(ESDRAM，Enhanced Synchronous Dynamic Random Access Memory)、同步连接动态随机存取存储器(SLDRAM，SyncLink Dynamic Random Access Memory)、直接内存总线随机存取存储器(DRRAM，Direct Rambus Random Access Memory)。本发明实施例描述的存储器1902旨在包括但不限于这些和任意其它适合类型的存储器。
本发明实施例中的存储器1902用于存储各种类型的数据以支持电子设备1900的操作。这些数据的示例包括：用于在电子设备1900上操作的任何计算机程序，如应用程序19021实现本发明实施例方法的程序可以包含在应用程序19021中。
上述本发明实施例揭示的方法可以应用于处理器1901中，或者由处理器1901实现。处理器1901可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器1901中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器1901可以是通用处理器、数字信号处理器(DSP，Digital Signal Processor)，或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。处理器1901可以实现或者执行本发明实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合本发明实施例所公开的方法的步骤，可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于存储介质中，该存储介质位于存储器1902，处理器1901读取存储器1902中的信息，结合其硬件完成前述方法的步骤。
在示例性实施例中，电子设备1900可以被一个或多个应用专用集成电路(ASIC，Application Specific Integrated Circuit)、DSP、可编程逻辑器件(PLD，Programmable Logic Device)、复杂可编程逻辑器件(CPLD，Complex Programmable Logic Device)、FPGA、通用处理器、控制器、MCU、MPU、或其他电子元件实现，用于执行前述方法。
本发明实施例还提供了一种存储介质，用于存储计算机程序。
可选的，该存储介质可应用于本发明实施例中的CHIP设备，并且该计算机程序使得计算机执行本发明实施例的各个方法中的相应流程，为了简洁，在此不再赘述。
可选的，该存储介质可应用于本发明实施例中的配置设备，并且该计算机程序使得计算机执行本发明实施例的各个方法中的相应流程，为了简洁，在此不再赘述。
可选的，该存储介质可应用于本发明实施例中的服务器，并且该计算机程序使得计算机执行本发明实施例的各个方法中的相应流程，为了简洁，在此不再赘述。
本发明是参照根据本发明实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
以上所述，仅为本发明的较佳实施例而已，并非用于限定本发明的保护范围，凡在本发明的精神和原则之内所作的任何修改、等同替换和改进等，均应包含在本发明的保护范围之内。

Claims (52)

  1. 一种控制方法，包括：
    CHIP设备在建立有与第一账号的第一绑定关系的情况下，满足原绑定关系解除条件，解除所述第一绑定关系，与第二账号建立第二绑定关系，以由使用所述第二账号的第二配置设备对所述CHIP设备进行配置。
  2. 根据权利要求1所述的方法，其中，检测到以下事件至少之一，确定满足原绑定关系解除条件：
    完成所述第二配置设备的配网；
    接收到用于指示恢复出厂设置的指令。
  3. 根据权利要求1或2所述的方法，其中，所述第一账号与所述第二账号为不同平台下的账号。
  4. 根据权利要求1或2所述的方法，其中，所述第一账号与所述第二账号为同一平台下的账号。
  5. 根据权利要求2所述的方法，在通过所述第二配置设备配网的情况下，所述方法还包括：
    所述CHIP设备将标识信息和/或平台信息发送至所述第二配置设备；
    所述CHIP设备接收所述第二配置设备发送的解除原绑定关系指示。
  6. 根据权利要求1至5任一项所述的方法，其中，所述解除所述第一绑定关系，包括：
    向第一服务器发送解除原绑定关系请求；所述第一服务器运行有所述第一账号所属的第一平台；
    接收所述第一服务器发送的原绑定关系解除成功响应。
  7. 根据权利要求1至5任一项所述的方法，其中，所述解除所述第一绑定关系，包括：
    向使用所述第一账号的第一配置设备发送解除原绑定关系请求；
    接收所述第一配置设备发送的原绑定关系解除成功响应。
  8. 根据权利要求6或7所述的方法，其中，在通过所述第二配置设备配网的情况下，所述解除所述第一绑定关系，还包括：
    发送原绑定关系解除成功通知至所述第二配置设备。
  9. 一种控制方法，包括：
    第一配置设备接收用于指示解除第一绑定关系的解除原绑定关系请求；所述第一绑定关系为CHIP设备与所述第一配置设备使用的第一账号的绑定关系；
    所述第一配置设备解除存储的所述第一绑定关系，使得所述CHIP设备能够与第二账号建立第二绑定关系，以由使用所述第二账号的第二配置设备对所述CHIP设备进行配置。
  10. 根据权利要求9所述的方法，其中，所述方法还包括：
    所述第一配置设备发送原绑定关系删除请求至第一服务器；所述第一服务器运行有所述第一账号所属的第一平台。
  11. 根据权利要求9或10所述的方法，其中，所述解除原绑定关系请求是从所述CHIP设备或第一服务器接收的。
  12. 根据权利要求9或10所述的方法，其中，所述第一账号与所述第二账号为不同平台下的账号。
  13. 根据权利要求9或10所述的方法，其中，所述第一账号与所述第二账号为同一平台下的账号。
  14. 一种控制方法，包括：
    第二配置设备向CHIP设备配网；
    所述第二配置设备在确定所述CHIP设备建立有与第一账号的第一绑定关系的情况下，向所述CHIP设备发送解除原绑定关系指示；所述解除原绑定关系指示用于指示所述CHIP设备解除所述第一绑定关系，建立与所述第二配置设备使用的第二账号的第二绑定关系，以由所述第二配置设备对所述CHIP设备进行配置。
  15. 根据权利要求14所述的方法，其中，所述方法还包括：
    所述第二配置设备接收所述CHIP设备发送的标识信息和/或平台信息。
  16. 根据权利要求14或15所述的方法，其中，所述第一账号与所述第二账号为不同平台下的账号。
  17. 根据权利要求14或15所述的方法，其中，所述第一账号与所述第二账号为同一平台下的 账号。
  18. 一种控制方法，包括：
    服务器接收原绑定关系删除请求；
    所述服务器删除CHIP设备与第一账号的第一绑定关系；所述终端设备在建立有所述第一绑定关系的情况下，满足原绑定关系解除条件，解除所述第一绑定关系，与第二账号建立第二绑定关系，以由使用所述第二账号的第二配置设备对所述终端设备进行配置。
  19. 根据权利要求18所述的方法，其中，所述方法还包括：
    所述服务器接收所述第一配置设备发送的原绑定关系删除请求。
  20. 根据权利要求18或19所述的方法，其中，所述方法还包括：
    所述服务器从所述CHIP设备接收解除原绑定关系请求；
    所述服务器将所述原绑定关系请求，转发至使用所述第一账号的第一配置设备。
  21. 根据权利要求18至20任一项所述的方法，其中，所述第一账号与所述第二账号为不同平台下的账号。
  22. 根据权利要求18至20任一项所述的方法，其中，所述第一账号与所述第二账号为同一平台下的账号。
  23. 一种CHIP设备，包括：
    解除模块，配置为在建立有与第一账号的第一绑定关系的情况下，满足原绑定关系解除条件，解除所述第一绑定关系，与第二账号建立第二绑定关系，以由使用所述第二账号的第二配置设备对所述CHIP设备进行配置。
  24. 根据权利要求23所述的CHIP设备，其中，所述解除模块，配置为检测到以下事件至少之一，则确定满足原绑定关系解除条件：
    完成所述第二配置设备的配网；
    接收到用于指示恢复出厂设置的指令。
  25. 根据权利要求23或24所述的CHIP设备，其中，所述第一账号与所述第二账号为不同平台下的账号。
  26. 根据权利要求23或24所述的CHIP设备，其中，所述第一账号与所述第二账号为同一平台下的账号。
  27. 根据权利要求24所述的CHIP设备，其中，所述CHIP设备还包括：
    第一发送模块，配置为将标识信息和/或平台信息发送至所述第二配置设备；
    第一接收模块，配置为接收所述第二配置设备发送的解除原绑定关系指示。
  28. 根据权利要求23至27任一项所述的CHIP设备，其中，所述解除模块，还配置为：
    向所第一服务器发送解除原绑定关系请求；所述第一服务器运行有所述第一账号所属的第一平台；
    接收所述第一服务器发送的原绑定关系解除成功响应。
  29. 根据权利要求23至27任一项所述的CHIP设备，其中，所述解除模块，还配置为：
    向使用所述第一账号的第一配置设备发送解除原绑定关系请求；
    接收所述第一配置设备发送的原绑定关系解除成功响应。
  30. 根据权利要求28或29所述的CHIP设备，其中，所述解除模块，还配置为：
    发送原绑定关系解除成功通知至所述第二配置设备。
  31. 一种配置设备，包括：
    第二接收模块，配置为接收用于指示解除第一绑定关系的解除原绑定关系请求；所述第一绑定关系为CHIP设备与所述第一配置设备使用的第一账号的绑定关系；
    执行模块，配置为解除存储的所述第一绑定关系，使得所述CHIP设备能够与第二账号建立第二绑定关系，以由使用所述第二账号的第二配置设备对所述CHIP设备进行配置。
  32. 根据权利要求31所述的配置设备，其中，所述配置设备还包括：
    第二发送模块，配置为发送原绑定关系删除请求至第一服务器；所述第一服务器运行有所述第一账号所属的第一平台。
  33. 根据权利要求31或32所述的配置设备，其中，所述解除原绑定关系请求是从所述CHIP设备或第一服务器接收的。
  34. 根据权利要求31或32所述的配置设备，其中，所述第一账号与所述第二账号为不同平台下的账号。
  35. 根据权利要求31或32所述的配置设备，其中，所述第一账号与所述第二账号为同一平台下的账号。
  36. 一种配置设备，包括：
    配网模块，配置为向CHIP设备配网；
    第三发送模块，配置为在确定所述CHIP设备建立有与第一账号的第一绑定关系的情况下，向所述CHIP设备发送解除原绑定关系指示，所述解除原绑定关系指示用于指示所述CHIP设备解除所述第一绑定关系，建立与所述第二配置设备使用的第二账号的第二绑定关系，以由所述第二配置设备对所述CHIP设备进行配置。
  37. 根据权利要求36所述的配置设备，其中，所述配置设备还包括：
    第三接收模块，配置为接收所述CHIP设备发送的标识信息和/或平台信息。
  38. 根据权利要求36或37所述的配置设备，其中，所述第一账号与所述第二账号为不同平台下的账号。
  39. 根据权利要求36或37所述的配置设备，其中，所述第一账号与所述第二账号为同一平台下的账号。
  40. 一种服务器，包括：
    第四接收模块，配置为接收的原绑定关系删除请求，
    删除模块，配置为删除CHIP设备与第一账号的第一绑定关系；所述终端设备在建立有所述第一绑定关系的情况下，满足原绑定关系解除条件，解除所述第一绑定关系，与第二账号建立第二绑定关系，以由使用所述第二账号的第二配置设备对所述终端设备进行配置。
  41. 根据权利要求40所述的服务器，其中，所述服务器还包括：
    第五接收模块，配置为接收所述第一配置设备发送的原绑定关系删除请求。
  42. 根据权利要求40或41所述的服务器，其中，所述服务器还包括：
    第六接收模块，配置为从所述CHIP设备接收解除原绑定关系请求；
    第四发送模块，配置为将所述原绑定关系请求，转发至使用所述第一账号的第一配置设备。
  43. 根据权利要求40至42任一项所述的服务器，其中，所述第一账号与所述第二账号为不同平台下的账号。
  44. 根据权利要求40至42任一项所述的服务器，其中，所述第一账号与所述第二账号为同一平台下的账号。
  45. 一种CHIP设备，包括处理器和用于存储能够在处理器上运行的计算机程序的存储器，其中，
    所述处理器用于运行所述计算机程序时，执行权利要求1至8任一项所述的控制方法的步骤。
  46. 一种配置设备，包括处理器和用于存储能够在处理器上运行的计算机程序的存储器，其中，
    所述处理器用于运行所述计算机程序时，执行权利要求9至13任一项所述的控制方法的步骤。
  47. 一种配置设备，包括处理器和用于存储能够在处理器上运行的计算机程序的存储器，其中，
    所述处理器用于运行所述计算机程序时，执行权利要求14至17任一项所述的控制方法的步骤。
  48. 一种服务器，包括处理器和用于存储能够在处理器上运行的计算机程序的存储器，其中，
    所述处理器用于运行所述计算机程序时，执行权利要求18至22任一项所述的控制方法的步骤。
  49. 一种存储介质，存储有可执行程序，所述可执行程序被处理器执行时，实现权利要求1至8任一项所述的控制方法。
  50. 一种存储介质，存储有可执行程序，所述可执行程序被处理器执行时，实现权利要求9至13任一项所述的控制方法。
  51. 一种存储介质，存储有可执行程序，所述可执行程序被处理器执行时，实现权利要求14至17任一项所述的控制方法。
  52. 一种存储介质，存储有可执行程序，所述可执行程序被处理器执行时，实现权利要求18至22任一项所述的控制方法。
PCT/CN2020/116316 2020-09-18 2020-09-18 控制方法、设备及存储介质 WO2022056878A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
PCT/CN2020/116316 WO2022056878A1 (zh) 2020-09-18 2020-09-18 控制方法、设备及存储介质
EP20953736.4A EP4216512A4 (en) 2020-09-18 Control method, device and storage medium
CN202080103396.6A CN116114235A (zh) 2020-09-18 2020-09-18 控制方法、设备及存储介质
US18/146,157 US20230208716A1 (en) 2020-09-18 2022-12-23 Control method, device and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/116316 WO2022056878A1 (zh) 2020-09-18 2020-09-18 控制方法、设备及存储介质

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/146,157 Continuation US20230208716A1 (en) 2020-09-18 2022-12-23 Control method, device and storage medium

Publications (1)

Publication Number Publication Date
WO2022056878A1 true WO2022056878A1 (zh) 2022-03-24

Family

ID=80777419

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/116316 WO2022056878A1 (zh) 2020-09-18 2020-09-18 控制方法、设备及存储介质

Country Status (3)

Country Link
US (1) US20230208716A1 (zh)
CN (1) CN116114235A (zh)
WO (1) WO2022056878A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3086539A1 (en) * 2015-03-31 2016-10-26 Xiaomi Inc. Method and device for deleting smart scene
CN108449770A (zh) * 2018-04-04 2018-08-24 上海网互物联网科技有限公司 一种智能硬件Wifi配网方式
CN108600259A (zh) * 2018-05-08 2018-09-28 普联技术有限公司 设备的认证和绑定方法及计算机存储介质、服务器
CN109219036A (zh) * 2018-09-13 2019-01-15 北京小米移动软件有限公司 解绑设备的方法及装置、电子设备
CN110703622A (zh) * 2019-11-05 2020-01-17 四川虹美智能科技有限公司 一种智能家电的控制装置、方法及系统
CN111599428A (zh) * 2020-05-15 2020-08-28 北京京东方健康科技有限公司 一种基于物联网的健康数据管理系统

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3086539A1 (en) * 2015-03-31 2016-10-26 Xiaomi Inc. Method and device for deleting smart scene
CN108449770A (zh) * 2018-04-04 2018-08-24 上海网互物联网科技有限公司 一种智能硬件Wifi配网方式
CN108600259A (zh) * 2018-05-08 2018-09-28 普联技术有限公司 设备的认证和绑定方法及计算机存储介质、服务器
CN109219036A (zh) * 2018-09-13 2019-01-15 北京小米移动软件有限公司 解绑设备的方法及装置、电子设备
CN110703622A (zh) * 2019-11-05 2020-01-17 四川虹美智能科技有限公司 一种智能家电的控制装置、方法及系统
CN111599428A (zh) * 2020-05-15 2020-08-28 北京京东方健康科技有限公司 一种基于物联网的健康数据管理系统

Also Published As

Publication number Publication date
EP4216512A1 (en) 2023-07-26
CN116114235A (zh) 2023-05-12
US20230208716A1 (en) 2023-06-29

Similar Documents

Publication Publication Date Title
CN111865598B (zh) 网络功能服务的身份校验方法及相关装置
TWI420921B (zh) 異質無線網路之間的快速鑑別
CN109919579B (zh) 电子文书签约方法、装置、存储介质和设备
WO2017054292A1 (zh) 一种虚拟sim卡服务授权方法、终端、服务器以及系统
CN102761870B (zh) 一种终端身份验证和服务鉴权的方法、系统和终端
WO2021143280A1 (zh) 登录认证方法、装置与系统
CA2552917C (en) A method of obtaining the user identification for the network application entity
CN103370915A (zh) 安全用户平面定位（supl）系统中的认证
CN104660405B (zh) 一种业务设备认证方法及设备
WO2018176441A1 (zh) 用户鉴权方法和装置
JP2018522323A (ja) 音声通信処理方法及びシステム、電子装置、並びに記憶媒体
WO2021109753A1 (zh) 一种应用于极简网络的机卡验证方法和相关设备
WO2017076216A1 (zh) 服务器、移动终端、网络实名认证系统及方法
CN108683690A (zh) 鉴权方法、用户设备、鉴权装置、鉴权服务器和存储介质
CN103067342A (zh) 一种使用eap进行外部认证的设备、系统及方法
CN107094127A (zh) 安全信息的处理方法及装置、获取方法及装置
WO2015089996A1 (zh) 一种安全认证方法及鉴权认证服务器
CN105790942A (zh) 一种安全通话的方法、终端和系统
CN109561413B (zh) 一种ble设备的蓝牙认证授权方法及授权系统
CN107274182B (zh) 业务处理方法及装置
CN112202770A (zh) 设备联网方法及装置、设备、存储介质
CN107819766B (zh) 安全认证方法、系统及计算机可读存储介质
JP6357778B2 (ja) 通信装置、通信システム及びプログラム
CN101355485B (zh) 一种网络接入认证转换的方法及系统和装置
CN103945378B (zh) 一种终端协同的认证方法及设备中间件

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020953736

Country of ref document: EP

Effective date: 20230417