WO2022017256A1 - 一种设备绑定方法及装置 - Google Patents

一种设备绑定方法及装置 Download PDF

Info

Publication number
WO2022017256A1
WO2022017256A1 PCT/CN2021/106573 CN2021106573W WO2022017256A1 WO 2022017256 A1 WO2022017256 A1 WO 2022017256A1 CN 2021106573 W CN2021106573 W CN 2021106573W WO 2022017256 A1 WO2022017256 A1 WO 2022017256A1
Authority
WO
WIPO (PCT)
Prior art keywords
devices
information
binding
device list
list
Prior art date
Application number
PCT/CN2021/106573
Other languages
English (en)
French (fr)
Inventor
齐观毅
Original Assignee
青岛易来智能科技股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 青岛易来智能科技股份有限公司 filed Critical 青岛易来智能科技股份有限公司
Publication of WO2022017256A1 publication Critical patent/WO2022017256A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0803Configuration setting
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/50Address allocation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/08Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0876Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/80Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00Indexing scheme associated with group H04L61/00
    • H04L2101/60Types of network addresses
    • H04L2101/618Details of network addresses
    • H04L2101/622Layer-2 addresses, e.g. medium access control [MAC] addresses
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00Reducing energy consumption in communication networks
    • Y02D30/70Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present invention relates to the field of information processing, and in particular, to a device binding method and device.
  • a low-power network topology for many-to-many device communication can be established based on the Bluetooth Mesh network.
  • Bluetooth Mesh Based on Bluetooth Mesh, a large network based on multiple devices can be created.
  • the network can contain dozens, hundreds or even thousands of Bluetooth Low Energy (Bluetooth Low E, BLE) Mesh devices, which can communicate with each other. transmission.
  • Device access is the process of connecting a Bluetooth Mesh device to a Mesh network.
  • Smart home is to connect various devices in the home through Internet of Things technology, manage and control these devices through software, and realize equipment automation and intelligence.
  • Traditional smart home implementations require the device to be powered up and then scanned via Bluetooth to find the device for configuration.
  • Embodiments of the present invention provide a device binding method and device, so as to at least solve the technical problem in the related art that devices need to be bound one by one after installation, resulting in low network access efficiency of devices in a Mesh network.
  • a device binding method including:
  • the device list includes virtual device information of multiple unbound devices
  • the device identification information of the part or all of the devices is bound with the virtual device information.
  • binding the device identification information of the part or all of the devices with the virtual device information includes:
  • the identities of some or all of the devices are bound with the virtual device information according to the binding instruction, wherein the device identification information includes the MAC address and the identity.
  • the method further includes:
  • performing network configuration on some or all of the devices includes:
  • the network configuration information is sent to the part or all of the devices according to the Bluetooth connection.
  • performing network configuration on some or all of the devices includes at least one of the following:
  • the method further includes:
  • the device state corresponding to the virtual device information of the part or all of the devices in the device list is adjusted to be bound.
  • the method further includes:
  • the device state corresponding to the virtual device information of the part or all of the devices in the device list is adjusted to the scanned code state.
  • acquiring the device list from the cloud server includes:
  • the device list sent by the cloud server when the verification code is verified and the verification result is passed is received.
  • a device binding apparatus including:
  • an obtaining module configured to obtain a device list from a cloud server, wherein the device list includes virtual device information of multiple unbound devices;
  • a reading module configured to read the device identification information of some or all of the devices in the device list through the identification code
  • the binding module is configured to bind the device identification information of the part or all of the devices with the virtual device information after the part or all of the devices are installed in the corresponding physical locations and powered on.
  • the binding module includes:
  • the first receiving sub-module is set to receive the binding instruction triggered by the binding control
  • a binding submodule configured to bind the identities of the part or all of the devices with the virtual device information according to the binding instruction, wherein the device identification information includes the MAC address and the identity .
  • the device further includes:
  • a network configuration module configured to perform network configuration on some or all of the devices.
  • the network configuration module includes:
  • an obtaining submodule configured to obtain the network configuration information of the part or all of the devices from the cloud server;
  • the first sending submodule is configured to send the network configuration information to the part or all of the devices according to the Bluetooth connection.
  • the network configuration module is further configured to perform network configuration on some or all of the devices including at least one of the following:
  • the device further includes:
  • the first adjustment module is configured to adjust the device state corresponding to the virtual device information of the part or all of the devices in the device list to be bound.
  • the device further includes:
  • the second adjustment module is configured to adjust the device state corresponding to the virtual device information of the part or all of the devices in the device list to the scanned code state.
  • the obtaining module includes:
  • the second sending submodule is configured to send an acquisition request for acquiring the device list to the cloud server, wherein the acquisition request carries a verification code
  • the second receiving sub-module is configured to receive the device list sent by the cloud server when the verification code is verified and the verification result is passed.
  • a computer-readable storage medium is also provided, where a computer program is stored in the storage medium, wherein the computer program is configured to execute any one of the above method embodiments when running steps in .
  • an electronic device comprising a memory and a processor, wherein the memory stores a computer program, the processor is configured to run the computer program to execute any of the above Steps in Method Examples.
  • the device list is obtained from the cloud server, wherein the device list includes virtual device information of multiple unbound devices; the device of some or all of the devices in the device list is read through the identification code Identification information; after the part or all of the devices are installed in the corresponding physical locations and powered on, the device identification information of the part or all of the devices is bound with the virtual device information, which can solve the problem that in the related art, the devices need to be installed one by one. Binding leads to the technical problem of low network access efficiency of devices in the Mesh network. After the device is installed, some or all devices are bound at one time, which improves the network access efficiency of the device.
  • FIG. 1 is a block diagram of a hardware structure of a mobile terminal of a device binding method according to an embodiment of the present invention
  • FIG. 2 is a flowchart of a device binding method according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram 1 of a scanning binding device according to an embodiment of the present invention.
  • FIG. 4 is a second schematic diagram of a scanning binding device according to an embodiment of the present invention.
  • FIG. 5 is a schematic diagram 3 of a scanning and binding device according to an embodiment of the present invention.
  • FIG. 6 is a schematic diagram 4 of a scanning binding device according to an embodiment of the present invention.
  • FIG. 7 is a structural block diagram of a device binding apparatus according to an embodiment of the present invention.
  • FIG. 1 is a block diagram of the hardware structure of a mobile terminal of a device binding method according to an embodiment of the present invention.
  • the mobile terminal may include one or more (only shown in FIG. a) a processor 102 (the processor 102 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA, etc.) and a memory 104 for storing data, optionally, the above-mentioned mobile terminal may also include a Communication function transmission device 106 and input and output device 108.
  • a processor 102 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA, etc.
  • a memory 104 for storing data
  • the above-mentioned mobile terminal may also include a Communication function transmission device 106 and input and output device 108.
  • FIG. 1 is only for illustration, and does not limit the structure of the above-mentioned mobile terminal.
  • the mobile terminal may also include more or fewer components than those shown in FIG. 1 , or have a different configuration than that shown in FIG. 1 .
  • the memory 104 may be used to store computer programs, for example, software programs and modules of application software, such as computer programs corresponding to the device binding method in the embodiment of the present invention.
  • the processor 102 executes the computer programs stored in the memory 104 by running the computer programs.
  • Various functional applications and data processing implement the above method.
  • Memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory.
  • the memory 104 may further include memory located remotely from the processor 102, and these remote memories may be connected to the mobile terminal through a network. Examples of such networks include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.
  • Transmission means 106 are used to receive or transmit data via a network.
  • the specific example of the above-mentioned network may include a wireless network provided by a communication provider of the mobile terminal.
  • the transmission device 106 includes a network adapter (Network Interface Controller, NIC for short), which can be connected to other network devices through a base station so as to communicate with the Internet.
  • the transmission device 106 may be a radio frequency (Radio Frequency, RF for short) module, which is used to communicate with the Internet in a wireless manner.
  • RF Radio Frequency
  • FIG. 2 is a flowchart of a device binding method according to an embodiment of the present invention. As shown in FIG. 2 , the process includes the following step:
  • Step S202 obtaining a device list from the cloud server, wherein the device list includes virtual device information of multiple unbound devices;
  • step S202 may specifically include: sending an acquisition request for acquiring the device list to the cloud server, wherein the acquisition request carries a verification code; receiving the cloud server to verify the verification code And the device list sent when the verification result is passed. Initiate an installation application to the cloud server. After obtaining the user's consent, the cloud server can send a message to the user APP. After receiving the user's consent instruction, it can determine that the user is authorized and send a verification code to the APP. The APP sends an acquisition request with the verification code to the cloud server, and the cloud server sends the device list only after the verification code is authenticated.
  • Step S204 read the device identification information of some or all of the devices in the device list through the identification code
  • Step S206 after the part or all of the devices are installed in the corresponding physical locations and powered on, the device identification information of the part or all of the devices is bound with the virtual device information.
  • step S206 may specifically include: establishing a Bluetooth connection with the part or all of the devices according to the MAC address; receiving a binding instruction triggered by a binding control; The identifier is bound with the virtual device information, wherein the device identifier information includes the MAC address and the identity identifier.
  • a device list is obtained from the cloud server, wherein the device list includes virtual device information of multiple unbound devices; the identification code is used to read the information of some or all devices in the device list.
  • Device identification information after the part or all of the devices are installed in the corresponding physical locations and powered on, the device identification information of the part or all of the devices is bound with the virtual device information, which can solve the need for post-installation devices in the related art Binding one by one leads to the technical problem of low network access efficiency of devices in the Mesh network. After the device is installed, part or all of the devices are bound at one time, which improves the network access efficiency of the devices.
  • network configuration is performed on the part or all of the devices.
  • performing network configuration on the part or all of the devices may specifically include: acquiring network configuration information of the part or all of the devices from the cloud server; configuring the network according to the Bluetooth connection; Configuration information is sent to some or all of the devices.
  • performing network configuration on some or all of the devices includes at least one of the following: configuring Mesh network information for some or all of the devices; configuring a Mesh network address for some or all of the devices; Set node properties for some or all of the devices; set properties for some or all of the device configurations.
  • the device state corresponding to the virtual device information of the part or all of the devices in the device list is adjusted to be bound.
  • the device status corresponding to the virtual device information of the part or all of the devices in the device list to have scanned the code. state.
  • the device scanning and device installation are decoupled, and the device installation and device configuration are decoupled, so as to improve the efficiency of smart home implementation.
  • Scanning the code to access the network specifically includes:
  • the APP obtains the device list from the cloud.
  • the devices in the device list are all unbound in the APP.
  • the external QR code on each device is used as the unique identifier of the device.
  • the APP uses the code scanning function to read the identification information. And find the device in the APP device list, and change the device to the scanned code status in the APP. After the device scans the code, install it to the corresponding physical location. After all/part of the device is installed, power on in batches, select the corresponding device from the APP device list, and perform device configuration.
  • the device configuration is: the APP obtains the network configuration of the device from the cloud. information, write the configuration information to the device, and change the device to the bound state in the APP.
  • the device includes the following three states: unscanned code (ie, unbound state), scanned code, successful binding, and displaying binding or waiting during the binding process.
  • FIG. 3 is a schematic diagram 1 of a scanning binding device according to an embodiment of the present invention. As shown in FIG. 3 , by clicking "de-scan code", the device in the unscanned state is controlled to enter the scanning code page.
  • Fig. 4 is a schematic diagram 2 of a scanning binding device according to an embodiment of the present invention. As shown in Fig. 4, after the code scanning is completed, it becomes the scanned code state. In the scanned code state, you can click Configure Now to complete the device configuration, or you can redo the configuration. Scan the code or clear the scan code information.
  • FIG. 5 is a schematic diagram 3 of scanning and binding devices according to an embodiment of the present invention. As shown in FIG. 5 , clicking All Binding will perform device binding one by one in sequence, and the binding is displayed as being bound, and the binding has not been performed yet. will appear as Waiting.
  • Fig. 6 is a schematic diagram 4 of a scanning and binding device according to an embodiment of the present invention.
  • the configuration is completed and the programming is bound successfully (that is, the bound state), and the device can be debugged in the bound state.
  • the equipment scan code is handed over to the installation master for installation.
  • the installation master completes the equipment installation according to the drawings. After the installation master completes the installation of an area, power on to check whether the circuit is unobstructed. For the power-on area, the configuration personnel select the items scanned before the code through the APP to configure, After the configuration is completed, the effect acceptance is carried out.
  • the three steps of device scanning, device installation, and device network access are decoupled, and each step can be independently completed by a dedicated person, which greatly solves the problem of implementation efficiency.
  • the threshold for installation masters is lowered, and the master only needs to concentrate on completing the equipment installation; after the equipment is powered on, the equipment is configured, and the APP can automatically find the equipment and complete the equipment configuration, reducing the cost of manpower search.
  • a device binding apparatus is also provided, and the apparatus is used to implement the above-mentioned embodiments and preferred implementation manners, and what has been described will not be repeated.
  • the term "module” may be a combination of software and/or hardware that implements a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, implementations in hardware, or a combination of software and hardware, are also possible and contemplated.
  • FIG. 7 is a structural block diagram of a device binding apparatus according to an embodiment of the present invention, as shown in FIG. 7 , including:
  • the obtaining module 72 is configured to obtain a device list from the cloud server, wherein the device list includes virtual device information of multiple unbound devices;
  • the reading module 74 is configured to read the device identification information of some or all devices in the device list through the identification code;
  • the binding module 76 is configured to bind the device identification information of the part or all of the devices with the virtual device information after the part or all of the devices are installed in the corresponding physical locations and powered on.
  • the binding module 76 includes:
  • the first receiving sub-module is set to receive the binding instruction triggered by the binding control
  • a binding submodule configured to bind the identities of the part or all of the devices with the virtual device information according to the binding instruction, wherein the device identification information includes the MAC address and the identity .
  • the device further includes:
  • a network configuration module configured to perform network configuration on some or all of the devices.
  • the network configuration module includes:
  • Obtaining a submodule configured to obtain the network configuration information of the part or all of the equipment from the cloud server;
  • the first sending submodule is configured to send the network configuration information to the part or all of the devices according to the Bluetooth connection.
  • the network configuration module is further configured to perform network configuration on some or all of the devices including at least one of the following:
  • the device further includes:
  • the first adjustment module is configured to adjust the device state corresponding to the virtual device information of some or all of the devices in the device list to be bound.
  • the device further includes:
  • the second adjustment module is configured to adjust the device state corresponding to the virtual device information of the part or all of the devices in the device list to the scanned code state.
  • the obtaining module includes:
  • the second sending submodule is configured to send an acquisition request for acquiring the device list to the cloud server, wherein the acquisition request carries a verification code
  • the second receiving sub-module is configured to receive the device list sent by the cloud server when the verification code is verified and the verification result is passed.
  • the above modules can be implemented by software or hardware, and the latter can be implemented in the following ways, but not limited to this: the above modules are all located in the same processor; or, the above modules can be combined in any combination The forms are located in different processors.
  • Embodiments of the present invention further provide a computer-readable storage medium, where a computer program is stored in the storage medium, wherein the computer program is configured to execute the steps in any of the above method embodiments when running.
  • the above-mentioned storage medium may be configured to store a computer program for executing the following steps:
  • S1 obtain a device list from a cloud server, wherein the device list includes virtual device information of multiple unbound devices;
  • the above-mentioned storage medium may include but is not limited to: a USB flash drive, a read-only memory (Read-Only Memory, referred to as ROM), a random access memory (Random Access Memory, referred to as RAM), Various media that can store computer programs, such as removable hard disks, magnetic disks, or optical disks.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • An embodiment of the present invention also provides an electronic device, comprising a memory and a processor, where a computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any of the above method embodiments.
  • the above-mentioned electronic device may further include a transmission device and an input-output device, wherein the transmission device is connected to the above-mentioned processor, and the input-output device is connected to the above-mentioned processor.
  • the above-mentioned processor may be configured to execute the following steps through a computer program:
  • S1 obtain a device list from a cloud server, wherein the device list includes virtual device information of multiple unbound devices;
  • modules or steps of the present invention can be implemented by a general-purpose computing device, and they can be centralized on a single computing device or distributed in a network composed of multiple computing devices Alternatively, they may be implemented in program code executable by a computing device, such that they may be stored in a storage device and executed by the computing device, and in some cases, in a different order than here
  • the steps shown or described are performed either by fabricating them separately into individual integrated circuit modules, or by fabricating multiple modules or steps of them into a single integrated circuit module.
  • the present invention is not limited to any particular combination of hardware and software.

Abstract

本发明实施例提供了一种设备绑定方法及装置,其中,该方法包括:从云服务器获取设备列表,其中,所述设备列表中包括多个未被绑定设备的虚拟设备信息;通过身份识别码读取所述设备列表中部分或全部设备的设备标识信息;在所述部分或全部设备安装到对应物理位置并通电之后,将所述部分或全部设备的设备标识信息与所述虚拟设备信息进行绑定,可以解决相关技术中设备安装后需要逐一绑定,导致Mesh网络中设备的入网效率较低的技术问题,设备安装后通过一次绑定部分或全部设备,提高了设备入网效率。

Description

一种设备绑定方法及装置 技术领域
本发明涉及信息处理领域,具体而言,涉及一种设备绑定方法及装置。
背景技术
在物联网智能家居场景中,可以基于蓝牙Mesh网络建立多对多设备通信的低功耗的网络拓扑。基于蓝牙Mesh可以创建基于多个设备的大型网络,网络中可以包含数十台,数百台甚至数千台蓝牙低功耗(Bluetooth Low E,BLE)Mesh设备,这些设备之间可以相互进行信息的传递。设备入网就是将蓝牙Mesh设备接入到某一Mesh网络的过程。
智能家居,是通过物联网技术将家中的各种设备连接在一起,通过软件来管理和控制这些设备,实现设备自动化、智能化。传统的智能家居实施需要先将设备通电,然后通过蓝牙扫描找到设备进行配置。当附近存在多个相同型号设备时很难加以区分,只能逐一通电,尤其是设备没有独立开关的情况下只能逐一安装设备,这个过程过于繁琐,严重影响实施速度。
针对相关技术中设备安装后需要逐一绑定,导致Mesh网络中设备的入网效率较低的技术问题,尚未提出有效的技术方案。
发明内容
本发明实施例提供了一种设备绑定方法及装置,以至少解决相关技术中设备安装后需要逐一绑定,导致Mesh网络中设备的入网效率较低的技术问题。
根据本发明的一个实施例,提供了一种设备绑定方法,包括:
从云服务器获取设备列表,其中,所述设备列表中包括多个未被绑定设备的虚拟设备信息;
通过身份识别码读取所述设备列表中部分或全部设备的设备标识信 息;
在所述部分或全部设备安装到对应物理位置并通电之后,将所述部分或全部设备的设备标识信息与所述虚拟设备信息进行绑定。
可选地,将所述部分或全部设备的设备标识信息与所述虚拟设备信息进行绑定包括:
根据MAC地址与所述部分或全部设备建立蓝牙连接;
接收通过绑定控件触发的绑定指令;
根据所述绑定指令将所述部分或全部设备的身份标识与所述虚拟设备信息进行绑定,其中,所述设备标识信息包括所述MAC地址与所述身份标识。
可选地,在根据所述绑定指令将所述部分或全部设备的身份标识与所述虚拟设备信息进行绑定之后,所述方法还包括:
对所述部分或全部设备进行网络配置。
可选地,对所述部分或全部设备进行网络配置包括:
从所述云服务器中获取所述部分或全部设备的网络配置信息;
根据所述蓝牙连接将所述网络配置信息发送给所述部分或全部设备。
可选地,对所述部分或全部设备进行网络配置至少包括以下之一:
为所述部分或全部设备配置Mesh网络信息;
为所述部分或全部设备配置Mesh网络地址;
为所述部分或全部设备设置节点属性;
为所述部分或全部设备配置设置属性。
可选地,在对所述部分或全部设备进行网络配置之后,所述方法还包括:
将所述设备列表中所述部分或全部设备的虚拟设备信息对应的设备状态调整为已绑定。
可选地,在通过身份识别码读取所述设备列表中部分或全部设备的标识信息之后,所述方法还包括:
将所述设备列表中所述部分或全部设备的虚拟设备信息对应的设备状态调整为已扫码状态。
可选地,从所述云服务器获取所述设备列表包括:
向所述云服务器发送获取所述设备列表的获取请求,其中,所述获取请求中携带有验证码;
接收所述云服务器在对所述验证码进行验证且验证结果为通过的情况下发送的所述设备列表。
根据本发明的另一个实施例,还提供了一种设备绑定装置,包括:
获取模块,设置为从云服务器获取设备列表,其中,所述设备列表中包括多个未被绑定设备的虚拟设备信息;
读取模块,设置为通过身份识别码读取所述设备列表中部分或全部设备的设备标识信息;
绑定模块,设置为在所述部分或全部设备安装到对应物理位置并通电之后,将所述部分或全部设备的设备标识信息与所述虚拟设备信息进行绑定。
可选地,所述绑定模块包括:
建立子模块,设置为根据MAC地址与所述部分或全部设备建立蓝牙连接;
第一接收子模块,设置为接收通过绑定控件触发的绑定指令;
绑定子模块,设置为根据所述绑定指令将所述部分或全部设备的身份标识与所述虚拟设备信息进行绑定,其中,所述设备标识信息包括所述MAC地址与所述身份标识。
可选地,所述装置还包括:
网络配置模块,设置为对所述部分或全部设备进行网络配置。
可选地,所述网络配置模块包括:
获取子模块,设置为从所述云服务器中获取所述部分或全部设备的网络配置信息;
第一发送子模块,设置为根据所述蓝牙连接将所述网络配置信息发送给所述部分或全部设备。
可选地,所述网络配置模块,还设置为对所述部分或全部设备进行网络配置至少包括以下之一:
为所述部分或全部设备配置Mesh网络信息;
为所述部分或全部设备配置Mesh网络地址;
为所述部分或全部设备设置节点属性;
为所述部分或全部设备配置设置属性。
可选地,所述装置还包括:
第一调整模块,设置为将所述设备列表中所述部分或全部设备的虚拟设备信息对应的设备状态调整为已绑定。
可选地,所述装置还包括:
第二调整模块,设置为将所述设备列表中所述部分或全部设备的虚拟设备信息对应的设备状态调整为已扫码状态。
可选地,所述获取模块包括:
第二发送子模块,设置为向所述云服务器发送获取所述设备列表的获取请求,其中,所述获取请求中携带有验证码;
第二接收子模块,设置为接收所述云服务器在对所述验证码进行验证且验证结果为通过的情况下发送的所述设备列表。
根据本发明的又一个实施例,还提供了一种计算机可读的存储介质,所述存储介质中存储有计算机程序,其中,所述计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
根据本发明的又一个实施例,还提供了一种电子装置,包括存储器和处理器,所述存储器中存储有计算机程序,所述处理器被设置为运行所述计算机程序以执行上述任一项方法实施例中的步骤。
通过本发明实施例,从云服务器获取设备列表,其中,所述设备列表中包括多个未被绑定设备的虚拟设备信息;通过身份识别码读取所述设备列表中部分或全部设备的设备标识信息;在所述部分或全部设备安装到对应物理位置并通电之后,将所述部分或全部设备的设备标识信息与所述虚拟设备信息进行绑定,可以解决相关技术中设备安装后需要逐一绑定,导致Mesh网络中设备的入网效率较低的技术问题,设备安装后通过一次绑定部分或全部设备,提高了设备入网效率。
附图说明
此处所说明的附图用来提供对本发明实施例的进一步理解,构成本申请的一部分,本发明的示意性实施例及其说明用于解释本发明,并不构成对本发明的不当限定。在附图中:
图1是本发明实施例的设备绑定方法的移动终端的硬件结构框图;
图2是根据本发明实施例的设备绑定方法的流程图;
图3是根据本发明实施例的扫描绑定设备的示意图一;
图4是根据本发明实施例的扫描绑定设备的示意图二;
图5是根据本发明实施例的扫描绑定设备的示意图三;
图6是根据本发明实施例的扫描绑定设备的示意图四;
图7是根据本发明实施例的设备绑定装置的结构框图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是,在不冲突的情况下,本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是,本发明的说明书和权利要求书及上述附图中的术语 “第一”、“第二”等是用于区别类似的对象,而不必用于描述特定的顺序或先后次序。
实施例1
本申请实施例一所提供的方法实施例可以在移动终端、计算机终端或者类似的运算装置中执行。以运行在移动终端上为例,图1是本发明实施例的设备绑定方法的移动终端的硬件结构框图,如图1所示,移动终端可以包括一个或多个(图1中仅示出一个)处理器102(处理器102可以包括但不限于微处理器MCU或可编程逻辑器件FPGA等的处理装置)和用于存储数据的存储器104,可选地,上述移动终端还可以包括用于通信功能的传输设备106以及输入输出设备108。本领域普通技术人员可以理解,图1所示的结构仅为示意,其并不对上述移动终端的结构造成限定。例如,移动终端还可包括比图1中所示更多或者更少的组件,或者具有与图1所示不同的配置。
存储器104可用于存储计算机程序,例如,应用软件的软件程序以及模块,如本发明实施例中的设备绑定方法对应的计算机程序,处理器102通过运行存储在存储器104内的计算机程序,从而执行各种功能应用以及数据处理,即实现上述的方法。存储器104可包括高速随机存储器,还可包括非易失性存储器,如一个或者多个磁性存储装置、闪存、或者其他非易失性固态存储器。在一些实例中,存储器104可进一步包括相对于处理器102远程设置的存储器,这些远程存储器可以通过网络连接至移动终端。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
传输装置106用于经由一个网络接收或者发送数据。上述的网络具体实例可包括移动终端的通信供应商提供的无线网络。在一个实例中,传输装置106包括一个网络适配器(Network Interface Controller,简称为NIC),其可通过基站与其他网络设备相连从而可与互联网进行通讯。在一个实例中,传输装置106可以为射频(Radio Frequency,简称为RF)模 块,其用于通过无线方式与互联网进行通讯。
在本实施例中提供了一种运行于上述移动终端或网络架构的设备绑定方法,图2是根据本发明实施例的设备绑定方法的流程图,如图2所示,该流程包括如下步骤:
步骤S202,从云服务器获取设备列表,其中,所述设备列表中包括多个未被绑定设备的虚拟设备信息;
进一步的,上述步骤S202具体可以包括:向所述云服务器发送获取所述设备列表的获取请求,其中,所述获取请求中携带有验证码;接收所述云服务器在对所述验证码进行验证且验证结果为通过的情况下发送的所述设备列表。向云服务器发起安装申请,云服务器在得到用户同意后,具体可以向用户APP发送消息,接收到用户的同意指令即可确定得到用户授权,向APP发送验证码。APP向云服务器发送携带验证码的获取请求,云服务器对验证码完成身份验证后,才发送设备列表。
步骤S204,通过身份识别码读取所述设备列表中部分或全部设备的设备标识信息;
步骤S206,在所述部分或全部设备安装到对应物理位置并通电之后,将所述部分或全部设备的设备标识信息与所述虚拟设备信息进行绑定。
进一步的,上述步骤S206具体可以包括:根据MAC地址与所述部分或全部设备建立蓝牙连接;接收通过绑定控件触发的绑定指令;根据所述绑定指令将所述部分或全部设备的身份标识与所述虚拟设备信息进行绑定,其中,所述设备标识信息包括所述MAC地址与所述身份标识。
通过上述步骤S202至S206,从云服务器获取设备列表,其中,所述设备列表中包括多个未被绑定设备的虚拟设备信息;通过身份识别码读取所述设备列表中部分或全部设备的设备标识信息;在所述部分或全部设备安装到对应物理位置并通电之后,将所述部分或全部设备的设备标识信息与所述虚拟设备信息进行绑定,可以解决相关技术中设备安装后需要逐一绑定,导致Mesh网络中设备的入网效率较低的技术问题,设备安装后通 过一次绑定部分或全部设备,提高了设备入网效率。
本发明实施例中,在根据所述绑定指令将所述部分或全部设备的身份标识与所述虚拟设备信息进行绑定之后,对所述部分或全部设备进行网络配置。
在一可选的实施例中,对所述部分或全部设备进行网络配置具体可以包括:从所述云服务器中获取所述部分或全部设备的网络配置信息;根据所述蓝牙连接将所述网络配置信息发送给所述部分或全部设备。
在另一可选的实施例中,对所述部分或全部设备进行网络配置至少包括以下之一:为所述部分或全部设备配置Mesh网络信息;为所述部分或全部设备配置Mesh网络地址;为所述部分或全部设备设置节点属性;为所述部分或全部设备配置设置属性。
可选地,在对所述部分或全部设备进行网络配置之后,将所述设备列表中所述部分或全部设备的虚拟设备信息对应的设备状态调整为已绑定。
可选地,在通过身份识别码读取所述设备列表中部分或全部设备的标识信息之后,将所述设备列表中所述部分或全部设备的虚拟设备信息对应的设备状态调整为已扫码状态。
本发明实施例,将设备扫描与设备安装解耦、设备安装与设备配置解耦,实现智能家居实施效率提升,扫码入网具体包括:
APP从云端获取设备列表,其中,设备列表中的设备在APP中均为未绑定状态,每个设备上外置二维码作为该设备唯一标识,APP使用扫码功能读取该标识信息,并在APP设备列表中查找该设备,将设备在APP中变更为已扫码状态。设备完成扫码后,安装到对应的物理位置,设备全部/部分安装完成后,批量通电,从APP设备列表选择相应的设备,进行设备配置,设备配置即:APP端从云端获取设备的网络配置信息,并将该配置信息写入设备,并将设备在APP中变更为已绑定状态。
本发明实施例中,设备包括以下三种状态:未扫码(即未绑定状态)、已扫码、绑定成功,在绑定过程中显示绑定中或等待中。
图3是根据本发明实施例的扫描绑定设备的示意图一,如图3所示,通过点击“去扫码”,控制处于未扫码状态的设备进入扫码页面。图4是根据本发明实施例的扫描绑定设备的示意图二,如图4所示,扫码完成之后变成已扫码状态,已扫码状态可以点击现在配置完成设备配置,也可以重新进行扫码或清除扫码信息。
图5是根据本发明实施例的扫描绑定设备的示意图三,如图5所示,点击全部绑定将按顺序逐一进行设备绑定,正在绑定显示为绑定中,还没有进行绑定的会显示为等待中。
图6是根据本发明实施例的扫描绑定设备的示意图四,如图6所示,配置完成编程绑定成功(即已绑定状态),已绑定状态可以进行设备调试,扫码人员完成设备扫码交由安装师傅安装,安装师傅按照图纸完成设备安装,安装师傅完成一个区域的安装之后通电检查电路是否通畅,对于已通电区域,配置人员通过APP点选之前扫码的条目进行配置,配置完成后进行效果验收。
通过本发明实施例,设备扫码、设备安装、设备入网三个步骤得以解耦,每个步骤都可以由专人来独立完成,极大解决了实施效率问题。降低了安装师傅门槛,师傅只需要专心完成设备安装即可;设备通电后进行设备配置,APP可自动寻找设备并完成设备配置,减少了人力查找成本。
通过以上的实施方式的描述,本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现,当然也可以通过硬件,但很多情况下前者是更佳的实施方式。基于这样的理解,本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中,包括若干指令用以使得一台终端设备(可以是手机,计算机,服务器,或者网络设备等)执行本发明各个实施例所述的方法。
实施例2
在本实施例中还提供了一种设备绑定装置,该装置用于实现上述实施例及优选实施方式,已经进行过说明的不再赘述。如以下所使用的,术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现,但是硬件,或者软件和硬件的组合的实现也是可能并被构想的。
图7是根据本发明实施例的设备绑定装置的结构框图,如图7所示,包括:
获取模块72,设置为从云服务器获取设备列表,其中,所述设备列表中包括多个未被绑定设备的虚拟设备信息;
读取模块74,设置为通过身份识别码读取所述设备列表中部分或全部设备的设备标识信息;
绑定模块76,设置为在所述部分或全部设备安装到对应物理位置并通电之后,将所述部分或全部设备的设备标识信息与所述虚拟设备信息进行绑定。
可选地,所述绑定模块76包括:
建立子模块,设置为根据MAC地址与所述部分或全部设备建立蓝牙连接;
第一接收子模块,设置为接收通过绑定控件触发的绑定指令;
绑定子模块,设置为根据所述绑定指令将所述部分或全部设备的身份标识与所述虚拟设备信息进行绑定,其中,所述设备标识信息包括所述MAC地址与所述身份标识。
可选地,所述装置还包括:
网络配置模块,设置为对所述部分或全部设备进行网络配置。
可选地,所述网络配置模块包括:
获取子模块,设置为从所述云服务器中获取所述部分或全部设备的网 络配置信息;
第一发送子模块,设置为根据所述蓝牙连接将所述网络配置信息发送给所述部分或全部设备。
可选地,所述网络配置模块,还设置为对所述部分或全部设备进行网络配置至少包括以下之一:
为所述部分或全部设备配置Mesh网络信息;
为所述部分或全部设备配置Mesh网络地址;
为所述部分或全部设备设置节点属性;
为所述部分或全部设备配置设置属性。
可选地,所述装置还包括:
第一调整模块,设置为将所述设备列表中所述部分或全部设备的虚拟设备信息对应的设备状态调整为已绑定。
可选地,所述装置还包括:
第二调整模块,设置为将所述设备列表中所述部分或全部设备的虚拟设备信息对应的设备状态调整为已扫码状态。
可选地,所述获取模块包括:
第二发送子模块,设置为向所述云服务器发送获取所述设备列表的获取请求,其中,所述获取请求中携带有验证码;
第二接收子模块,设置为接收所述云服务器在对所述验证码进行验证且验证结果为通过的情况下发送的所述设备列表。
需要说明的是,上述各个模块是可以通过软件或硬件来实现的,对于后者,可以通过以下方式实现,但不限于此:上述模块均位于同一处理器中;或者,上述各个模块以任意组合的形式分别位于不同的处理器中。
实施例3
本发明的实施例还提供了一种计算机可读的存储介质,该存储介质中存储有计算机程序,其中,该计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
可选地,在本实施例中,上述存储介质可以被设置为存储用于执行以下步骤的计算机程序:
S1,从云服务器获取设备列表,其中,所述设备列表中包括多个未被绑定设备的虚拟设备信息;
S2,通过身份识别码读取所述设备列表中部分或全部设备的设备标识信息;
S3,在所述部分或全部设备安装到对应物理位置并通电之后,将所述部分或全部设备的设备标识信息与所述虚拟设备信息进行绑定。
可选地,在本实施例中,上述存储介质可以包括但不限于:U盘、只读存储器(Read-Only Memory,简称为ROM)、随机存取存储器(Random Access Memory,简称为RAM)、移动硬盘、磁碟或者光盘等各种可以存储计算机程序的介质。
实施例4
本发明的实施例还提供了一种电子装置,包括存储器和处理器,该存储器中存储有计算机程序,该处理器被设置为运行计算机程序以执行上述任一项方法实施例中的步骤。
可选地,上述电子装置还可以包括传输设备以及输入输出设备,其中,该传输设备和上述处理器连接,该输入输出设备和上述处理器连接。
可选地,在本实施例中,上述处理器可以被设置为通过计算机程序执行以下步骤:
S1,从云服务器获取设备列表,其中,所述设备列表中包括多个未被绑定设备的虚拟设备信息;
S2,通过身份识别码读取所述设备列表中部分或全部设备的设备标识信息;
S3,在所述部分或全部设备安装到对应物理位置并通电之后,将所述部分或全部设备的设备标识信息与所述虚拟设备信息进行绑定。
可选地,本实施例中的具体示例可以参考上述实施例及可选实施方式中所描述的示例,本实施例在此不再赘述。
显然,本领域的技术人员应该明白,上述的本发明的各模块或各步骤可以用通用的计算装置来实现,它们可以集中在单个的计算装置上,或者分布在多个计算装置所组成的网络上,可选地,它们可以用计算装置可执行的程序代码来实现,从而,可以将它们存储在存储装置中由计算装置来执行,并且在某些情况下,可以以不同于此处的顺序执行所示出或描述的步骤,或者将它们分别制作成各个集成电路模块,或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样,本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已,并不用于限制本发明,对于本领域的技术人员来说,本发明可以有各种更改和变化。凡在本发明的原则之内,所作的任何修改、等同替换、改进等,均应包含在本发明的保护范围之内。

Claims (11)

  1. 一种设备绑定方法,包括:
    从云服务器获取设备列表,其中,所述设备列表中包括多个未被绑定设备的虚拟设备信息;
    通过身份识别码读取所述设备列表中部分或全部设备的设备标识信息;
    在所述部分或全部设备安装到对应物理位置并通电之后,将所述部分或全部设备的设备标识信息与所述虚拟设备信息进行绑定。
  2. 根据权利要求1所述的方法,其中,将所述部分或全部设备的设备标识信息与所述虚拟设备信息进行绑定包括:
    根据MAC地址与所述部分或全部设备建立蓝牙连接;
    接收通过绑定控件触发的绑定指令;
    根据所述绑定指令将所述部分或全部设备的身份标识与所述虚拟设备信息进行绑定,其中,所述设备标识信息包括所述MAC地址与所述身份标识。
  3. 根据权利要求2所述的方法,其中,在根据所述绑定指令将所述部分或全部设备的身份标识与所述虚拟设备信息进行绑定之后,所述方法还包括:
    对所述部分或全部设备进行网络配置。
  4. 根据权利要求3所述的方法,其中,对所述部分或全部设备进行网络配置包括:
    从所述云服务器中获取所述部分或全部设备的网络配置信息;
    根据所述蓝牙连接将所述网络配置信息发送给所述部分或全部设备。
  5. 根据权利要求3所述的方法,其中,对所述部分或全部设备进行网络配置至少包括以下之一:
    为所述部分或全部设备配置Mesh网络信息;
    为所述部分或全部设备配置Mesh网络地址;
    为所述部分或全部设备设置节点属性;
    为所述部分或全部设备配置设置属性。
  6. 根据权利要求3至5中任一项所述的方法,其中,在对所述部分或全部设备进行网络配置之后,所述方法还包括:
    将所述设备列表中所述部分或全部设备的虚拟设备信息对应的设备状态调整为已绑定。
  7. 根据权利要求1至5中任一项所述的方法,其中,在通过身份识别码读取所述设备列表中部分或全部设备的标识信息之后,所述方法还包括:
    将所述设备列表中所述部分或全部设备的虚拟设备信息对应的设备状态调整为已扫码状态。
  8. 根据权利要求1至5中任一项所述的方法,其中,从所述云服务器获取所述设备列表包括:
    向所述云服务器发送获取所述设备列表的获取请求,其中,所述获取请求中携带有验证码;
    接收所述云服务器在对所述验证码进行验证且验证结果为通过 的情况下发送的所述设备列表。
  9. 一种设备绑定装置,包括:
    获取模块,设置为从云服务器获取设备列表,其中,所述设备列表中包括多个未被绑定设备的虚拟设备信息;
    读取模块,设置为通过身份识别码读取所述设备列表中部分或全部设备的设备标识信息;
    绑定模块,设置为在所述部分或全部设备安装到对应物理位置并通电之后,将所述部分或全部设备的设备标识信息与所述虚拟设备信息进行绑定。
  10. 一种计算机可读的存储介质,所述存储介质中存储有计算机程序,其中,所述计算机程序被设置为运行时执行所述权利要求1至8任一项中所述的方法。
  11. 一种电子装置,包括存储器和处理器,所述存储器中存储有计算机程序,所述处理器被设置为运行所述计算机程序以执行所述权利要求1至8任一项中所述的方法。
PCT/CN2021/106573 2020-07-20 2021-07-15 一种设备绑定方法及装置 WO2022017256A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010700584.9A CN111885144B (zh) 2020-07-20 2020-07-20 一种设备绑定方法及装置
CN202010700584.9 2020-07-20

Publications (1)

Publication Number Publication Date
WO2022017256A1 true WO2022017256A1 (zh) 2022-01-27

Family

ID=73155060

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/106573 WO2022017256A1 (zh) 2020-07-20 2021-07-15 一种设备绑定方法及装置

Country Status (2)

Country Link
CN (1) CN111885144B (zh)
WO (1) WO2022017256A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114786238A (zh) * 2022-03-29 2022-07-22 广东芬尼克兹节能设备有限公司 Lora终端设备入网方法、装置、终端设备、系统及存储介质
CN116056016A (zh) * 2022-06-29 2023-05-02 荣耀终端有限公司 样机信息上报方法和电子设备

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111885144B (zh) * 2020-07-20 2022-09-16 青岛易来智能科技股份有限公司 一种设备绑定方法及装置
CN112737816B (zh) * 2020-12-15 2023-08-22 青岛海尔科技有限公司 一种设备绑定方法及装置
CN113839991A (zh) * 2021-08-30 2021-12-24 青岛海尔科技有限公司 设备信息的确认方法、装置、存储介质及电子装置
CN114124915A (zh) * 2021-10-25 2022-03-01 青岛海尔科技有限公司 绑定关系的建立方法和装置、存储介质及电子装置
CN115221379A (zh) * 2022-07-14 2022-10-21 苏州欧普照明有限公司 设备绑定方法、系统及应用
CN117574348A (zh) * 2024-01-15 2024-02-20 浙江口碑网络技术有限公司 图形标识码的管理方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015116863A1 (en) * 2014-02-03 2015-08-06 Exablox Corporation Private cloud connected device cluster architecture
CN105739314A (zh) * 2016-01-29 2016-07-06 北京小米移动软件有限公司 与可控制设备建立绑定的方法和装置
US20160269527A1 (en) * 2015-03-13 2016-09-15 Xiaomi Inc. Methods and apparatuses for binding with device
CN111885144A (zh) * 2020-07-20 2020-11-03 青岛易来智能科技股份有限公司 一种设备绑定方法及装置

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104122808A (zh) * 2013-04-29 2014-10-29 黄杰 智能家居控制系统
CN104968032B (zh) * 2015-05-04 2018-05-29 广东欧珀移动通信有限公司 一种mp节点进网方法、mp节点及mpp节点
CN106936675A (zh) * 2017-03-27 2017-07-07 欧普照明股份有限公司 一种设备绑定系统
CN109510796B (zh) * 2017-09-14 2022-02-01 杭州萤石网络股份有限公司 一种设备绑定方法及系统
CN107733749B (zh) * 2017-09-15 2020-08-28 欧普照明股份有限公司 一种终端设备绑定系统和方法
CN110366044B (zh) * 2018-04-11 2021-12-14 腾讯科技(深圳)有限公司 获取目标物的方法、装置和系统
CN108810861B (zh) * 2018-05-28 2021-06-04 北京小米移动软件有限公司 智能设备的连接方法、装置及存储介质
CN109121124A (zh) * 2018-07-05 2019-01-01 杭州涂鸦信息技术有限公司 一种基于客户端的蓝牙mesh设备入网流程实现方法
CN110177015A (zh) * 2019-05-24 2019-08-27 杭州迪普科技股份有限公司 一种管理终端接入网络的方法及装置
CN110794693B (zh) * 2019-09-30 2023-09-26 深圳绿米联创科技有限公司 设备配置方法、装置、电子设备及存储介质
CN111641997B (zh) * 2020-06-16 2023-03-10 青岛亿联客信息技术有限公司 基于蓝牙Mesh网络的设备入网方法和装置、存储介质

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015116863A1 (en) * 2014-02-03 2015-08-06 Exablox Corporation Private cloud connected device cluster architecture
US20160269527A1 (en) * 2015-03-13 2016-09-15 Xiaomi Inc. Methods and apparatuses for binding with device
CN105739314A (zh) * 2016-01-29 2016-07-06 北京小米移动软件有限公司 与可控制设备建立绑定的方法和装置
CN111885144A (zh) * 2020-07-20 2020-11-03 青岛易来智能科技股份有限公司 一种设备绑定方法及装置

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114786238A (zh) * 2022-03-29 2022-07-22 广东芬尼克兹节能设备有限公司 Lora终端设备入网方法、装置、终端设备、系统及存储介质
CN116056016A (zh) * 2022-06-29 2023-05-02 荣耀终端有限公司 样机信息上报方法和电子设备

Also Published As

Publication number Publication date
CN111885144A (zh) 2020-11-03
CN111885144B (zh) 2022-09-16

Similar Documents

Publication Publication Date Title
WO2022017256A1 (zh) 一种设备绑定方法及装置
CN104137439B (zh) 对等发现
EP3118700B1 (en) Intelligent home control method and system based on alljoyn technology
WO2020207043A1 (zh) 基站开站方法、装置、计算机存储介质及设备
CN105637498A (zh) eUICC的管理方法、eUICC、SM平台和系统
CN109041140B (zh) 快速切换无线网络方法、智能硬件及终端设备
CN111641997B (zh) 基于蓝牙Mesh网络的设备入网方法和装置、存储介质
EP3648525A1 (en) Network management method and system
CN105319973B (zh) 一种通过扫描二维码更换智能家居设备的方法及装置
WO2019057011A1 (zh) 一种网络切片模板的处理方法及管理设备
CN103957580A (zh) 一种用于智能硬件的wifi快速组网配对方法及模块
CN112953774B (zh) 一种网络拓扑生成方法、系统、设备及计算机存储介质
CN106506717A (zh) 一种自动发现方法及设备
CN111641996B (zh) 基于蓝牙Mesh网络的设备入网方法和装置、存储介质
CN110830336A (zh) 一种智能家居的WiFi设备管理的方法及装置
CN109981421A (zh) 一种智能设备配网方法和装置
CN113438314A (zh) 一种设备控制方法、装置、存储介质及电子装置
CN114285695B (zh) 通信方法、装置、设备、系统和存储介质
WO2021047561A1 (zh) 用户签约参数集Profile的迁移方法、装置、用户管理-数据准备网元及运营商后台系统
CN108259523A (zh) 一种数据传输方法及物联网系统、网络访问方法
WO2020024264A1 (zh) 一种维修设备管理方法及用户终端、服务器
WO2014036902A1 (zh) 网关管理终端的方法及装置
CN104104701A (zh) 在线服务的配置更新的方法和系统
CN113434422A (zh) 虚拟设备的调试方法及装置、虚拟设备的调试系统
CN111866856A (zh) Mesh设备的控制方法和系统、存储介质及电子装置

Legal Events

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

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21846333

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 21846333

Country of ref document: EP

Kind code of ref document: A1