WO2019019014A1 - 一种NB-IoT设备绑定方法和一种物联网控制系统 - Google Patents

一种NB-IoT设备绑定方法和一种物联网控制系统 Download PDF

Info

Publication number
WO2019019014A1
WO2019019014A1 PCT/CN2017/094292 CN2017094292W WO2019019014A1 WO 2019019014 A1 WO2019019014 A1 WO 2019019014A1 CN 2017094292 W CN2017094292 W CN 2017094292W WO 2019019014 A1 WO2019019014 A1 WO 2019019014A1
Authority
WO
WIPO (PCT)
Prior art keywords
management platform
device identifier
cloud management
management terminal
iot
Prior art date
Application number
PCT/CN2017/094292
Other languages
English (en)
French (fr)
Inventor
洪伟
Original Assignee
北京小米移动软件有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京小米移动软件有限公司 filed Critical 北京小米移动软件有限公司
Priority to PCT/CN2017/094292 priority Critical patent/WO2019019014A1/zh
Priority to CN201780000683.2A priority patent/CN108521857B/zh
Publication of WO2019019014A1 publication Critical patent/WO2019019014A1/zh
Priority to US16/726,874 priority patent/US11005944B2/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/12—Digital output to print unit, e.g. line printer, chain printer
    • G06F3/1201—Dedicated interfaces to print systems
    • G06F3/1223—Dedicated interfaces to print systems specifically adapted to use a particular technique
    • G06F3/1229—Printer resources management or printer maintenance, e.g. device status, power levels
    • G06F3/1231—Device related settings, e.g. IP address, Name, Identification
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/12—Digital output to print unit, e.g. line printer, chain printer
    • G06F3/1201—Dedicated interfaces to print systems
    • G06F3/1202—Dedicated interfaces to print systems specifically adapted to achieve a particular effect
    • G06F3/1203—Improving or facilitating administration, e.g. print management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/12—Digital output to print unit, e.g. line printer, chain printer
    • G06F3/1201—Dedicated interfaces to print systems
    • G06F3/1202—Dedicated interfaces to print systems specifically adapted to achieve a particular effect
    • G06F3/1218—Reducing or saving of used resources, e.g. avoiding waste of consumables or improving usage of hardware resources
    • G06F3/1219—Reducing or saving of used resources, e.g. avoiding waste of consumables or improving usage of hardware resources with regard to consumables, e.g. ink, toner, paper
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/12—Digital output to print unit, e.g. line printer, chain printer
    • G06F3/1201—Dedicated interfaces to print systems
    • G06F3/1223—Dedicated interfaces to print systems specifically adapted to use a particular technique
    • G06F3/1237—Print job management
    • G06F3/1239—Restricting the usage of resources, e.g. usage or user levels, credit limit, consumables, special fonts
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/12—Digital output to print unit, e.g. line printer, chain printer
    • G06F3/1201—Dedicated interfaces to print systems
    • G06F3/1278—Dedicated interfaces to print systems specifically adapted to adopt a particular infrastructure
    • G06F3/1285—Remote printer device, e.g. being remote from client or server
    • G06F3/1287—Remote printer device, e.g. being remote from client or server via internet
    • 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/10—Protocols in which an application is distributed across nodes in the network
    • 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/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/12—Digital output to print unit, e.g. line printer, chain printer
    • G06F3/1201—Dedicated interfaces to print systems
    • G06F3/1223—Dedicated interfaces to print systems specifically adapted to use a particular technique
    • G06F3/1236—Connection management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/12—Digital output to print unit, e.g. line printer, chain printer
    • G06F3/1201—Dedicated interfaces to print systems
    • G06F3/1278—Dedicated interfaces to print systems specifically adapted to adopt a particular infrastructure
    • G06F3/1292—Mobile client, e.g. wireless printing

Definitions

  • the present disclosure relates to the field of communications technologies, and in particular, to an NB-IoT device binding method and an Internet of Things control system.
  • 5G Fifth-Generation, fifth-generation mobile communication
  • 5G technology in addition to the connection between the conventional mobile phone and the base station, it also penetrates into the field of Internet of Things.
  • 5G technology can be used to connect various devices in the home such as computers, tablets, mobile phones, air conditioners, rice cookers, refrigerators, televisions, washing machines, and sensors to the Internet of Things. interconnected”.
  • NB-IoT Near Band Internet of Things
  • 5G technology is proposed in 5G technology
  • NB-IoT technology is an emerging technology.
  • NB-IoT is built into a mobile cellular network to support data connections between lower intelligence devices in the WAN's mobile cellular network.
  • the communication of low-level intelligent devices in NB-IoT is simply communication, only transmitting some key interactive information, instead of using large-scale data in the process of browsing the web and video on the Internet like using a high-level smart device such as a mobile phone. It takes a lot of bandwidth.
  • implementing the Internet of Things in NB-IoT requires only about 180KHz of bandwidth.
  • a low-level smart device such as air conditioners, rice cookers, refrigerators, televisions, washing machines, and sensors through high-end smart devices such as mobile phones.
  • a high-level smart device such as a mobile phone
  • the device in turn, enables higher intelligence devices to manage the bound low-level smart devices.
  • a low-level smart device is bound to a higher-level smart device, which is generally implemented by Wi-Fi.
  • a lower intelligence device can be bound to a higher intelligence device in the same Wi-Fi environment.
  • low-level smart devices are gradually no longer supporting Wi-Fi technology, and instead begin to support NB-IoT technology. Therefore, for a lower-level smart device that only supports NB-IoT technology, the scheme of binding it to a higher-level smart device through Wi-Fi is not available.
  • a NB-IoT device binding method is provided, where the method is applied to an Internet of Things control system, where the Internet of Things control system comprises an NB-IoT device, a cloud management platform of a core network, and a management terminal;
  • the NB-IoT device When detecting the first operation instruction, the NB-IoT device sends a first binding message to the cloud management platform, where the first binding message carries device information of the NB-IoT device and the first Equipment Identity;
  • the cloud management platform stores the device information corresponding to the first device identifier
  • the management terminal When the management terminal detects the second operation instruction, the management terminal acquires the first device identifier of the NB-IoT device to be bound, and the management terminal sends a second binding message to the cloud management platform, where the The second binding message carries the first device identifier;
  • the cloud management platform searches for the device information corresponding to the first device identifier locally, and sends the device information to the management terminal, based on the first device identifier that is carried in the second binding message. ;
  • the management terminal stores the device information as device information bound to the NB-IoT device.
  • the NB-IoT device and the management terminal can communicate with each other, and the NB-IoT device can be bound to the management terminal, so that the subsequent management terminal manages the NB-IoT device.
  • the device information includes any one or more of the following: a device type, a device name, and an operating parameter.
  • the method further includes:
  • the management terminal determines a control parameter based on the device information, and sends a control request to the cloud management platform, where the control request carries the control parameter and the first device identifier;
  • the cloud management platform sends the control request to the NB-IoT device corresponding to the first device identifier.
  • the management terminal can control the NB-IoT device by the above optional method.
  • the second binding message further carries a second device identifier of the management terminal
  • the cloud management platform adds the second device identifier to the pre-established device binding relationship corresponding to the first device identifier.
  • the method further includes:
  • the NB-IoT device sends a data report message to the cloud management platform, where the data report message carries target data and the first device identifier;
  • the cloud management platform sends the data report message to the management terminal corresponding to the second device identifier.
  • the NB-IoT device When the NB-IoT device needs to send a data report message to the management terminal, the NB-IoT device can be implemented through the foregoing optional methods.
  • the first device identifier of the NB-IoT device to be bound is obtained, including:
  • an Internet of Things control system includes an NB-IoT device, a cloud management platform of the core network, and a management terminal;
  • the NB-IoT device is configured to send a first binding message to the cloud management platform when the first operation instruction is detected, where the first binding message carries device information of the NB-IoT device And the first device identification;
  • the cloud management platform is configured to store the device information and the first device identifier correspondingly;
  • the management terminal is configured to: when detecting the second operation instruction, acquire the first device identifier of the NB-IoT device to be bound, and the management terminal sends a second binding message to the cloud management platform, The second binding message carries the first device identifier;
  • the cloud management platform is configured to search for the device information corresponding to the first device identifier locally, and send the device information to the device according to the first device identifier that is carried in the second binding message.
  • the management terminal is configured to store the device information as device information bound to the NB-IoT device.
  • the device information includes any one or more of the following: a device type, a device name, and an operating parameter.
  • the management terminal is further configured to: determine, according to the device information, a control parameter, and send a control request to the cloud management platform, where the control request carries the control parameter and the first device identifier ;
  • the cloud management platform is further configured to send the control request to the NB-IoT device corresponding to the first device identifier.
  • the second binding message further carries a second device identifier of the management terminal
  • the cloud management platform is further configured to add the second device identifier to the pre-established device binding relationship corresponding to the first device identifier.
  • the NB-IoT device is further configured to send a data report message to the cloud management platform, where the data report message carries target data and the first device identifier;
  • the cloud management platform is further configured to determine, according to the device binding relationship, the second device identifier corresponding to the first device identifier;
  • the cloud management platform is further configured to send the data report message to the management terminal corresponding to the second device identifier.
  • the management terminal is configured to acquire a first device identifier of the NB-IoT device to be bound by a user.
  • the NB-IoT device and the management terminal can communicate with each other, and the NB-IoT device can be bound to the management terminal, so that the subsequent management terminal manages the NB-IoT device.
  • FIG. 1 is a flowchart of a NB-IoT device binding method according to an embodiment of the present disclosure
  • FIG. 2 is a schematic diagram of interaction in an Internet of Things control system according to an embodiment of the present disclosure
  • FIG. 3 is a schematic structural diagram of an Internet of Things control system according to an embodiment of the present disclosure.
  • FIG. 4 is a schematic structural diagram of a terminal according to an embodiment of the present disclosure.
  • the embodiment of the invention provides a NB-IoT device binding method, which can be applied to an Internet of Things control system, and the Internet of Things control system includes a NB-IoT device, a core network cloud management platform and management. terminal.
  • the NB-IoT device may be a device equipped with an NB-IoT chip to access the network through the NB-IoT chip.
  • the cloud management platform is a device of the core network, and is used to manage various devices that access the cloud management platform, and may be a server with processing capabilities.
  • the management terminal can be a mobile phone, a tablet, or the like. It should be noted that the NB-IoT device and the management terminal sometimes cannot communicate directly, and need to communicate through the cloud management platform.
  • the communication between the NB-IoT device, the management terminal and the cloud management platform is performed by the base station.
  • the base station In the process of communication, the base station only acts as a forwarding information and does not perform any processing on the information.
  • the interaction between the NB-IoT device, the cloud management platform of the core network, and the management terminal is described in detail without regard to the role of the base station.
  • the above management terminal may include a transceiver, a processor, a memory, and the like.
  • the transceiver is a component that can be used for communication with the cloud management platform, for example, sending a second binding message to the cloud management platform, and the transceiver can include a radio frequency circuit, a Bluetooth component, and a WiFi (Wireless-Fidelity). Components, antennas, matching circuits, modems, etc.
  • the processor may be a CPU (Central Processing Unit), etc., and may be used to obtain a first device identifier of the NB-IoT device to be bound, and the like.
  • the memory may be a RAM (Random Access Memory), a Flash (flash memory), etc., and may be used to store received data, data required for processing, data generated during processing, and the like, such as binding NB. - Device information of the IoT device, etc.
  • the terminal may also include an input component, a display component, an audio output component, and the like.
  • the input component can be a touch screen, a keyboard, a mouse, or the like.
  • the audio output unit can be a speaker, a headphone, or the like.
  • the NB-IoT device binding method provided by the present disclosure may be performed.
  • FIG. 1 is a flowchart of a NB-IoT device binding method according to an embodiment of the present disclosure. Referring to Figure 1, the method includes:
  • step S110 the NB-IoT device sends a first binding message to the cloud management platform when the first operation instruction is detected.
  • the first binding message carries the device information of the NB-IoT device and the first device identifier.
  • the first operation instruction may be an instruction generated by the NB-IoT device triggered by detecting a preset operation by the user.
  • the preset operation may be to press and hold the power button and the sleep button at the same time, press and hold the power button for 5 seconds, and press the power button for 3 times.
  • the first binding message may be generated based on the first operation instruction.
  • the NB-IoT device sends the pre-stored device information and the first device identifier to the cloud management platform. It should be noted that the communication between the NB-IoT device and the cloud management platform is based on NB-IoT. The agreement was carried out.
  • the NB-IoT device when the NB-IoT device is powered on, it can directly camp on the NB-IoT network of the carrier to which the NB-IoT device belongs.
  • the device information includes but is not limited to any one or more of the following: a device type, a device name, and an operating parameter.
  • the device type of the NB-IoT device is "LaserJet".
  • the name of the printer can be the HP LaserJet Professionnal M1213nf MFP.
  • the operating parameter of the printer may be an operating parameter "Ink Shortage” indicating whether or not there is paper in the printer.
  • the device identification of the printer can be "CNJ8F7F46S”.
  • Step S120 The cloud management platform stores the device information corresponding to the first device identifier.
  • the cloud management platform may receive the device information sent by the NB-IoT device and the first device identifier, and store them correspondingly.
  • the cloud management platform can create a list of device information in the memory, in which each piece of data can be divided into a header and a tail. The header and the tail correspond to each other.
  • the first device identification can be stored at the head of the data and the device information stored at the end of the data.
  • Step S130 The management terminal acquires the first device identifier of the NB-IoT device to be bound, and the management terminal sends a second binding message to the cloud management platform, where the second binding message is carried in the second binding message. First device identification.
  • the step of acquiring the first device identifier of the NB-IoT device to be bound includes: acquiring the first device identifier of the NB-IoT device to be bound by the user.
  • the first operation instruction may be generated based on a user triggering by a preset operation in the management device.
  • the user can open an application dedicated to managing the NB-IoT device in the management terminal, and input the first device identifier of the NB-IoT device to be bound to the device binding operation interface of the application.
  • the device ID of the bound device is entered in the input window.
  • the management terminal can obtain the first device identifier of the NB-IoT device to be bound by the user, such as “CNJ8F7F46S”.
  • the management terminal may send a second binding message including the first device identifier such as “CNJ8F7F46S” to the cloud management platform.
  • management terminal and the NB-IoT device may not communicate based on the same communication mode. Therefore, the management terminal and the NB-IoT device cannot directly communicate with each other, and thus cannot be directly bound. They can communicate through the cloud management platform as an intermediary.
  • Step S140 The cloud management platform searches for device information corresponding to the first device identifier locally, and sends the device information to the management terminal, based on the first device identifier carried in the second binding message.
  • a device information list may be established in the cloud management platform, and a plurality of data including a correspondence between the first device identifier and the device information are pre-stored in the table.
  • the cloud management platform receives the second binding message, the first device identifier carried in the second binding message, such as “CNJ8F7F46S”, is extracted.
  • the device information list query for "CNJ8F7F46S” and find the corresponding device information: Equipment Type - LaserJet, Equipment Name - HP LaserJet Professionnal M1213nf MFP, Operating Parameter - Ink Shortage. After the cloud management platform finds the device information, it can send them to the management terminal.
  • Step S150 The management terminal stores the device information as device information bound to the NB-IoT device.
  • the management terminal may receive device information sent by the cloud management platform, and store the device information as device information bound to the NB-IoT device, so that the management terminal uses the device when the NB-IoT device is subsequently managed. Information is achieved for the purpose of NB-IoT device management.
  • the management device manages the NB-IoT device in the following manner.
  • the method provided by the disclosure further includes: the management terminal determines the control parameter based on the device information, and sends a control request to the cloud management platform, where the control request carries the control parameter and the first device identifier; the cloud management platform sends the control request To the NB-IoT device corresponding to the first device identification.
  • the control parameter may be determined based on an operating parameter in the device information.
  • the management terminal receives an operating parameter “Operating Parameter-Ink Shortage” of an NB-IoT device, such as a printer, and the management terminal can determine, based on the operating parameter, that the printer is in an ink-deficient state, and at this time, if the management terminal is based on the printer, The operating parameters determine that the printer is in the print job state and then determine that the control parameter is "Stop Printing.” Because, if the printer is out of ink, even if the printer still performs the print job, it will only make the printed image unclear or without any image.
  • the corresponding decision logic can be set to cause the management terminal to interrupt the printer to perform any print job while detecting that the printer is out of ink.
  • the management terminal determines the control parameter "Stop Printing”
  • it sends a control request to the cloud management platform, where the request carries the control parameter "Stop Printing” and hits
  • the machine identification of the printer is "CNJ8F7F46S”.
  • the cloud management platform After receiving the control request, the cloud management platform extracts the device identifier "CNJ8F7F46S" of the printer in the control request to determine which control request the management terminal is for the bound NB-IoT device. When the cloud management platform determines that the control request is made for the printer whose device identifier is "CNJ8F7F46S", the control request is sent to the printer corresponding to "CNJ8F7F46S".
  • the NB-IoT device when the NB-IoT device needs to send a data report message to the management terminal, the NB-IoT device can be implemented in the following manner.
  • the second binding message further carries the second device identifier of the management terminal; the cloud management platform adds the second device identifier to the pre-established device binding relationship corresponding to the first device identifier.
  • the second device identifier of the management terminal may be added to the second binding message.
  • the cloud management platform receives the second binding message
  • the second device identifier and the first device identifier may be extracted.
  • the second device identifier corresponds to the management terminal
  • the first device identifier corresponds to the NB-IoT device.
  • a device binding relationship list may be established in the cloud management platform, where the second device identifier may be stored in association with the first device identifier to save the binding relationship between the management terminal and the NB-IoT device. It should be noted that generally one management terminal corresponds to multiple NB-IoT devices that need to be managed.
  • the method provided in this embodiment further includes: the NB-IoT device sends a data report message to the cloud management platform, where the data report message carries the target data and the first device identifier; the cloud management platform determines the device binding relationship according to the device binding relationship. The second device identifier corresponding to the first device identifier; the cloud management platform sends the data report message to the management terminal corresponding to the second device identifier.
  • the NB-IoT device can generate a data report message locally, where the data report message carries the target data and the first device identifier.
  • the cloud management platform receives the data report message, the first device identifier is extracted to determine which NB-IoT device the data report message is sent.
  • the cloud management platform may query the second device identifier of the management terminal bound to the NB-IoT device in the local device binding relationship list.
  • the cloud management platform sends the data report message to the management terminal corresponding to the second device identifier.
  • the management terminal processes the report information to determine what control operations are performed subsequently.
  • the correspondence between the second device identifier and the first device identifier may not be established in the cloud management platform, but the management terminal that needs to receive the data report message when the NB-IoT device sends a data report message to the management terminal.
  • the identifier is placed in the data report message, and the cloud management platform may determine, according to the second device identifier in the data report message, which management terminal to send the data report message to.
  • the process performed by the embodiment of the present disclosure is as follows: First, when detecting the first operation instruction, the NB-IoT device sends a first binding message to the cloud management platform. Then, cloud management platform The device information is stored corresponding to the first device identifier. Then, the management terminal acquires the first device identifier of the NB-IoT device to be bound from the user when the second operation instruction is detected, and the management terminal sends the second binding message to the cloud management platform. Then, the cloud management platform searches for the device information corresponding to the first device identifier locally, and sends the device information to the management terminal, based on the first device identifier carried in the second binding message. Finally, the management terminal stores the device information as device information bound to the NB-IoT device.
  • the NB-IoT device and the management terminal can communicate with each other, and the NB-IoT device can be bound to the management terminal, so that the subsequent management terminal manages the NB-IoT device.
  • FIG. 3 is a schematic structural diagram of an Internet of Things control system according to an embodiment of the present disclosure.
  • the system includes an NB-IoT device 310, a cloud management platform 320 of the core network, and a management terminal 330.
  • the NB-IoT device 310 is configured to send a first binding message to the cloud management platform 320 when the first operation instruction is detected, where the first binding message carries the NB-IoT device 310.
  • the cloud management platform 320 is configured to store the device information and the first device identifier correspondingly;
  • the management terminal 330 is configured to acquire, when the second operation instruction is detected, the first device identifier of the NB-IoT device 310 to be bound, and the management terminal 330 sends the second device to the cloud management platform 320. Binding a message, where the second binding message carries the first device identifier;
  • the cloud management platform 320 is configured to search for the device information corresponding to the first device identifier locally, and send the device information to the first device identifier that is carried in the second binding message.
  • the management terminal 330 is configured to store the device information as device information bound to the NB-IoT device 310.
  • the device information includes any one or more of the following: a device type, a device name, and an operating parameter.
  • the management terminal 330 is further configured to: determine, according to the device information, a control parameter, and send a control request to the cloud management platform 320, where the control request carries the control parameter and the first Equipment Identity;
  • the cloud management platform 320 is further configured to send the control request to the NB-IoT device 310 corresponding to the first device identifier.
  • the second binding message further carries the second device identifier of the management terminal 330.
  • the cloud management platform 320 is further configured to add the second device identifier to the pre-established device binding relationship corresponding to the first device identifier.
  • the NB-IoT device 310 is further configured to send a data report message to the cloud management platform 320, where the data report message carries the target data and the first device identifier.
  • the cloud management platform 320 is further configured to determine, according to the device binding relationship, the second device identifier corresponding to the first device identifier.
  • the cloud management platform 320 is further configured to send the data report message to the management terminal 330 corresponding to the second device identifier.
  • the management terminal 330 is configured to acquire a first device identifier of the NB-IoT device 310 to be bound by a user.
  • the NB-IoT device and the management terminal can communicate with each other, and the NB-IoT device can be bound to the management terminal, so that the subsequent management terminal manages the NB-IoT device.
  • the terminal 1000 may include one or more of the following components: a processing component 1002, a memory 1004, a power component 1006, a multimedia component 1008, an audio component 1010, an input/output (I/O) interface 1012, and a sensor component 1014. And a communication component 1016.
  • Processing component 1002 typically controls the overall operation of terminal 1000, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations.
  • Processing component 1002 can include one or more processors 1020 to execute instructions to perform all or part of the steps of the above described methods.
  • processing component 1002 can include one or more modules to facilitate interaction between component 1002 and other components.
  • processing component 1002 can include a multimedia module to facilitate interaction between multimedia component 1008 and processing component 1002.
  • the memory 1004 is configured to store various types of data to support operations at the terminal 1000. Examples of such data include instructions for any application or method operating on terminal 1000, contact data, phone book data, messages, pictures, videos, and the like.
  • the memory 1004 can be implemented by any type of volatile or non-volatile storage device, or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read only memory (EEPROM), erasable.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read only memory
  • EPROM Programmable Read Only Memory
  • ROM Read Only Memory
  • Magnetic Memory Flash Memory
  • Disk Disk
  • Optical Disk Optical Disk
  • Communication component 1016 is configured to facilitate wired or wireless communication between terminal 1000 and other devices.
  • the terminal 1000 can access a wireless network based on a communication standard such as WiFi, 2G or 3G, or a combination thereof.
  • the communication component 1016 receives a broadcast signal or broadcast associated information from an external broadcast management system via a broadcast channel.
  • the communication component 1016 also includes a near field communication (NFC) module to facilitate short range communication.
  • NFC near field communication
  • the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.
  • RFID radio frequency identification
  • IrDA infrared data association
  • UWB ultra-wideband
  • Bluetooth Bluetooth
  • Power component 1006 provides power to various components of terminal 1000.
  • Power component 1006 can include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for audio output device 1000.
  • the multimedia component 1008 includes a screen providing an output interface between the terminal 1000 and a user.
  • the screen can include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen can be implemented as a touch screen to receive input signals from the user.
  • the touch panel includes one or more touch sensors to sense touches, slides, and gestures on the touch panel. The touch sensor may sense not only the boundary of the touch or sliding action, but also the duration and pressure associated with the touch or slide operation.
  • the multimedia component 1008 includes a front camera and/or a rear camera. When the terminal 1000 is in an operation mode such as a shooting mode or a video mode, the front camera and/or the rear camera can receive external multimedia data. Each front and rear camera can be a fixed optical lens system or have focal length and optical zoom capabilities.
  • the audio component 1010 is configured to output and/or input an audio signal.
  • the audio component 1010 includes a microphone (MIC) that is configured to receive an external audio signal when the audio output device 1000 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode.
  • the received audio signal may be further stored in memory 1004 or transmitted via communication component 1016.
  • the I/O interface 1012 provides an interface between the processing component 1002 and the peripheral interface module, which may be a keyboard, a click wheel, a button, or the like. These buttons may include, but are not limited to, a home button, a volume button, a start button, and a lock button.
  • Sensor assembly 1014 includes one or more sensors for providing terminal 1000 with various aspects of status assessment.
  • the sensor component 1014 can detect the on/off state of the terminal 1000, The relative positioning of the components, such as the display and the keypad of the terminal 1000, the sensor component 1014 can also detect the change in position of one component of the terminal 1000 or the terminal 1000, the presence or absence of contact of the user with the terminal 1000, the orientation of the terminal 1000 or Acceleration/deceleration and temperature change of the terminal 1000.
  • Sensor assembly 1014 can include a proximity sensor configured to detect the presence of nearby objects without any physical contact.
  • Sensor assembly 1014 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
  • the sensor assembly 1014 can also include an acceleration sensor, a gyro sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
  • terminal 1000 may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable A gate array (FPGA), controller, microcontroller, microprocessor, or other electronic component implementation for performing the above methods.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGA field programmable A gate array
  • controller microcontroller, microprocessor, or other electronic component implementation for performing the above methods.
  • a person skilled in the art may understand that all or part of the steps of implementing the above embodiments may be completed by hardware, or may be instructed by a program to execute related hardware, and the program may be stored in a computer readable storage medium.
  • the storage medium mentioned may be a read only memory, a magnetic disk or an optical disk or the like.

Abstract

本公开实施例公开了一种NB-IoT设备绑定方法和一种物联网控制系统，属于通信技术领域。该方法包括：NB-IoT设备在检测到第一操作指令时，向云管理平台发送第一绑定消息，第一绑定消息中携带有NB-IoT设备的设备信息和第一设备标识；云管理平台将设备信息与第一设备标识对应存储；管理终端在检测到第二操作指令时，获取待绑定的NB-IoT设备的第一设备标识，管理终端向云管理平台发送第二绑定消息，第二绑定消息中携带有第一设备标识；云管理平台基于第二绑定消息中携带的第一设备标识，在本地查找第一设备标识对应的设备信息，将设备信息发送给管理终端；管理终端将设备信息存储为绑定NB-IoT设备的设备信息。通过本公开可以将NB-IoT设备绑定在管理终端上。

Description

一种NB-IoT设备绑定方法和一种物联网控制系统 技术领域
本公开涉及通讯技术领域，特别涉及一种NB-IoT设备绑定方法和一种物联网控制系统。
背景技术
在5G(5th-Generation，第五代移动通信)技术中，除了涵盖常规的手机与基站之间的连接之外，还要渗入到物联网领域。在物联网领域中，可以通过5G技术使得家庭中的各种设备如电脑、平板电脑、手机、空调、电饭煲、冰箱、电视机、洗衣机以及传感器等都能够接入到物联网中，实现“万物互联”。
为了使得“万物互联”，就需要在5G技术中实现大规模的物与物之间的连接。针对上述问题，在5G技术中提出了NB-IoT(Narrow Band Internet of Things，窄带物联网)技术，NB-IoT技术是一个新兴的技术。NB-IoT构建于移动蜂窝网络中，支持低等智能设备在广域网的移动蜂窝网络中的数据连接。NB-IoT中低等智能设备的通讯只是简单的通讯，只传输一些关键的交互信息，而不像利用高等智能设备如手机一样在上网浏览网页、视频的过程中，需要传输大规模的数据而需要很大的带宽。一般在NB-IoT中实现物联网只需消耗大约180KHz的带宽。
在物联网的应用中，可以通过手机等高等智能设备去管理其他低等智能设备如空调、电饭煲、冰箱、电视机、洗衣机以及传感器等。在使得手机等高等智能设备可以管理其他低等智能设备之前，需要将这些低等智能设备绑定到高等智能设备中的管理模块中，以使得高等智能设备能够识别它所需要管理的低等智能设备，进而使得高等智能设备可以去管理绑定好的低等智能设备。在相关技术中，将一个低等智能设备绑定到一个高等智能设备中，一般是通过Wi-Fi实现的。例如，一个低等智能设备可以绑定到处于同一Wi-Fi环境下的一个高等智能设备中。然而在相关技术中，低等智能设备渐渐不再支持Wi-Fi技术了，转而开始支持NB-IoT技术。因此对于只支持NB-IoT技术的低等智能设备，再通过Wi-Fi实现将其绑定到一个高等智能设备的方案就不可用了。
发明内容
本公开实施例提供的技术方案如下：
第一方面，提供了一种NB-IoT设备绑定方法，所述方法应用于物联网控制系统，所述物联网控制系统包括NB-IoT设备、核心网的云管理平台和管理终端；
所述NB-IoT设备在检测到第一操作指令时，向所述云管理平台发送第一绑定消息，所述第一绑定消息中携带有所述NB-IoT设备的设备信息和第一设备标识；
所述云管理平台将所述设备信息与所述第一设备标识对应存储；
所述管理终端在检测到第二操作指令时，获取待绑定的所述NB-IoT设备的第一设备标识，所述管理终端向所述云管理平台发送第二绑定消息，所述第二绑定消息中携带有所述第一设备标识；
所述云管理平台基于所述第二绑定消息中携带的所述第一设备标识，在本地查找所述第一设备标识对应的所述设备信息，将所述设备信息发送给所述管理终端；
所述管理终端将所述设备信息存储为绑定NB-IoT设备的设备信息。
通过本公开实施例，通过云管理平台使得NB-IoT设备和管理终端，可以相互通信，进而可以将NB-IoT设备绑定在管理终端上，以便后续管理终端对NB-IoT设备进行管理。
可选地，所述设备信息包括以下任一项或多项：设备类型、设备名称、运行参数。
可选地，所述方法还包括：
所述管理终端基于所述设备信息确定控制参数，向所述云管理平台发送控制请求，其中，所述控制请求中携带有所述控制参数和所述第一设备标识；
所述云管理平台将所述控制请求发送至与所述第一设备标识对应的所述NB-IoT设备。
管理终端可以通过上述可选方法对NB-IoT设备进行控制。
可选地，所述第二绑定消息还携带有所述管理终端的第二设备标识；
所述云管理平台将所述第二设备标识与所述第一设备标识对应地添加到预先建立的设备绑定关系中。
可选地，所述方法还包括：
所述NB-IoT设备向所述云管理平台发送数据上报消息，所述数据上报消息中携带有目标数据和所述第一设备标识；
所述云管理平台根据所述设备绑定关系，确定所述第一设备标识对应的所述第二设备标识；
所述云管理平台将所述数据上报消息发送至与所述第二设备标识对应的所述管理终端。
当NB-IoT设备需要向管理终端发送数据上报消息时，可以通过上述可选方式实现。
可选地，获取待绑定的所述NB-IoT设备的第一设备标识，包括：
获取用户输入的待绑定的所述NB-IoT设备的第一设备标识。
第二方面，提供一种物联网控制系统，所述系统包括NB-IoT设备、核心网的云管理平台和管理终端；
所述NB-IoT设备，用于在检测到第一操作指令时，向所述云管理平台发送第一绑定消息，所述第一绑定消息中携带有所述NB-IoT设备的设备信息和第一设备标识；
所述云管理平台，用于将所述设备信息与所述第一设备标识对应存储；
所述管理终端，用于在检测到第二操作指令时，获取待绑定的所述NB-IoT设备的第一设备标识，所述管理终端向所述云管理平台发送第二绑定消息，所述第二绑定消息中携带有所述第一设备标识；
所述云管理平台，用于基于所述第二绑定消息中携带的所述第一设备标识，在本地查找所述第一设备标识对应的所述设备信息，将所述设备信息发送给所述管理终端；
所述管理终端，用于将所述设备信息存储为绑定NB-IoT设备的设备信息。
可选地，所述设备信息包括以下任一项或多项：设备类型、设备名称、运行参数。
可选地，所述管理终端还用于基于所述设备信息确定控制参数，向所述云管理平台发送控制请求，其中，所述控制请求中携带有所述控制参数和所述第一设备标识；
所述云管理平台还用于将所述控制请求发送至与所述第一设备标识对应的所述NB-IoT设备。
可选地，所述第二绑定消息还携带有所述管理终端的第二设备标识；
所述云管理平台还用于将所述第二设备标识与所述第一设备标识对应地添加到预先建立的设备绑定关系中。
可选地，所述NB-IoT设备还用于向所述云管理平台发送数据上报消息，所述数据上报消息中携带有目标数据和所述第一设备标识；
所述云管理平台还用于根据所述设备绑定关系，确定所述第一设备标识对应的所述第二设备标识；
所述云管理平台还用于将所述数据上报消息发送至与所述第二设备标识对应的所述管理终端。
可选地，所述管理终端用于获取用户输入的待绑定的所述NB-IoT设备的第一设备标识。
本公开实施例提供的技术方案带来的有益效果是：
通过本公开实施例，通过云管理平台使得NB-IoT设备和管理终端，可以相互通信，进而可以将NB-IoT设备绑定在管理终端上，以便后续管理终端对NB-IoT设备进行管理。
附图说明
为了更清楚地说明本公开实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本公开的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本公开实施例提供的一种NB-IoT设备绑定方法的流程图；
图2是本公开实施例提供的一种物联网控制系统中交互的示意图；
图3是本公开实施例提供的一种物联网控制系统的结构示意图；
图4是本公开实施例提供的一种终端的结构示意图。
具体实施方式
为使本公开的目的、技术方案和优点更加清楚，下面将结合附图对本公开实施方式作进一步地详细描述。
本发明实施例提供了一种NB-IoT设备绑定方法，该方法可以应用于物联网控制系统，物联网控制系统包括NB-IoT设备、核心网的云管理平台和管理 终端。其中，NB-IoT设备可以是配备NB-IoT芯片的设备，以通过NB-IoT芯片接入网络。云管理平台是核心网的设备，用于管理接入云管理平台的各种设备，可以是有处理能力的服务器等。管理终端可以是手机、平板电脑等。需要说明的是，NB-IoT设备与管理终端有时不能直接通信，需要通过云管理平台进行通信。而NB-IoT设备、管理终端与云管理平台的通信是通过基站进行的。基站在通信过程中，只作转发信息的作用，不对信息进行任何处理。在本公开的实施例的描述中，不考虑基站的作用，只对NB-IoT设备、核心网的云管理平台和管理终端的相互作用进行详细说明。
上述管理终端可以包括收发器、处理器、存储器等部件。收发器，是可以用于与云管理平台进行通信的部件，例如，向云管理平台发送第二绑定消息，收发器可以包括射频电路、蓝牙部件、WiFi(Wireless-Fidelity，无线高保真技术)部件、天线、匹配电路、调制解调器等。处理器，可以为CPU(Central Processing Unit，中央处理单元)等，可以用于获取待绑定的NB-IoT设备的第一设备标识，等处理。存储器，可以为RAM(Random Access Memory，随机存取存储器)，Flash(闪存)等，可以用于存储接收到的数据、处理过程所需的数据、处理过程中生成的数据等，如绑定NB-IoT设备的设备信息等。
终端还可以包括输入部件、显示部件、音频输出部件等。输入部件可以是触摸屏、键盘、鼠标等。音频输出部件可以是音箱、耳机等。
需要说明的是，当用户将一台NB-IoT设备新购置家中时，为了通过管理终端对该NB-IoT设备进行管理，可以执行本公开提供的NB-IoT设备绑定方法。
图1是本公开实施例提供的一种NB-IoT设备绑定方法的流程图。参见图1，所述方法包括：
步骤S110，NB-IoT设备在检测到第一操作指令时，向云管理平台发送第一绑定消息，第一绑定消息中携带有NB-IoT设备的设备信息和第一设备标识。
其中，第一操作指令可以是NB-IoT设备在检测到用户进行预设的操作所触发生成的指令。预设的操作可以是同时按住开机键和休眠键、按住开机键5秒、连续按开机键3次等操作。总之，在检测到用户进行预设的操作时，认为用户想要将NB-IoT设备与一管理终端进行绑定。此时，可以基于第一操作指令生成第一绑定消息。NB-IoT设备将预存的设备信息和第一设备标识发送至云管理平台。需要说明的是，NB-IoT设备与云管理平台的通信是基于NB-IoT 协议进行的。
需要说明的是，NB-IoT设备在开机时，可以直接驻入到NB-IoT设备所属的运营商NB-IoT网络。
可选地，设备信息包括但不限于以下任一项或多项：设备类型、设备名称、运行参数。
例如，NB-IoT设备是一台打印机，则NB-IoT设备的设备类型是“LaserJet(打印机)”。该打印机的名称可以是HP LaserJet Professionnal M1213nf MFP。该打印机的运行参数可以是表示打印机中是否有纸张的运行参数“Ink Shortage(缺少墨水)”。该打印机的设备标识可以是“CNJ8F7F46S”。
步骤S120，云管理平台将设备信息与第一设备标识对应存储。
在实施中，云管理平台可以接收NB-IoT设备发送的设备信息与第一设备标识，并将它们对应存储。例如，接上例，云管理平台可以在存储器中建立一张设备信息列表，在该列表中每条数据可以分为头部和尾部。头部与尾部是对应的，当在设备信息列表中对数据的头部进行检索时，可以得到整条数据的内容。在该公开实施例中，可以将第一设备标识存储在数据的头部，将设备信息存储在数据的尾部。当有新的NB-IoT设备将其设备信息与设备标识发过来时，可以建立第二条数据，也通过上述方式进行设备信息与设备标识存储。至此，可以得到一张包括多条数据的设备信息列表。当然，还存在其他将设备信息与第一设备标识对应存储的方法，在本公开中不一一举例。
步骤S130，管理终端在检测到第二操作指令时，获取待绑定的NB-IoT设备的第一设备标识，管理终端向云管理平台发送第二绑定消息，第二绑定消息中携带有第一设备标识。
可选地，获取待绑定的NB-IoT设备的第一设备标识的步骤包括：获取用户输入的待绑定的NB-IoT设备的第一设备标识。
其中，第一操作指令可以基于用户在管理设备中通过预设的操作触发而生成。可选地，用户可以在管理终端打开一个专用于管理NB-IoT设备的应用程序，在该应用程序的设备绑定操作界面，将待绑定的NB-IoT设备的第一设备标识输入到待绑定设备的设备标识输入窗口中。管理终端可以获取到用户输入的待绑定的NB-IoT设备的第一设备标识如“CNJ8F7F46S”。最后，管理终端可以将包含有第一设备标识如“CNJ8F7F46S”的第二绑定消息发送至云管理平台。需要说明的是，管理终端和NB-IoT设备可能不基于同一通信模式进行通 信，因此，管理终端和NB-IoT设备不能直接互相通信，也就不能直接进行绑定了。它们可以通过云管理平台作为中介，进行通信。
步骤S140，云管理平台基于第二绑定消息中携带的第一设备标识，在本地查找第一设备标识对应的设备信息，将设备信息发送给管理终端。
在实施例中，如上所述，可以在云管理平台建立一张设备信息列表，在该表中预先存储了多条包括第一设备标识与设备信息对应关系的数据。当云管理平台接收到第二绑定消息时，提取第二绑定消息中携带的第一设备标识如“CNJ8F7F46S”。在设备信息列表中针对“CNJ8F7F46S”进行查询，查找到与之对应的设备信息：Equipment Type(设备类型)-LaserJet、Equipment Name(设备名称)-HP LaserJet Professionnal M1213nf MFP、Operating Parameter(运行参数)-Ink Shortage。云管理平台在查找到这些设备信息之后，可以将它们发送至管理终端。
步骤S150，管理终端将设备信息存储为绑定NB-IoT设备的设备信息。
在实施中，管理终端可以接收云管理平台发送的设备信息，并将设备信息存储为绑定NB-IoT设备的设备信息，以便于管理终端在后续对NB-IoT设备进行管理时，使用这些设备信息达到对NB-IoT设备管理的目的。
可选地，管理设备通过下述方式对NB-IoT设备进行管理。相应地，本公开提供的方法还包括：管理终端基于设备信息确定控制参数，向云管理平台发送控制请求，其中，控制请求中携带有控制参数和第一设备标识；云管理平台将控制请求发送至与第一设备标识对应的NB-IoT设备。
其中，控制参数可以是基于设备信息中的运行参数确定的。例如，管理终端接收到一NB-IoT设备如打印机的运行参数“Operating Parameter-Ink Shortage”，管理终端可以基于该运行参数判断，打印机处于缺墨状态，而此时如果管理终端基于该打印机的其他运行参数确定打印机处于打印任务状态，则确定控制参数为“Stop Printing(停止打印)”。因为，如果打印机处于缺墨状态，即使打印机依然执行打印任务，只会使得打印出来的图像的颜色不清晰或者是没有任何图像。如果是图像的颜色不清晰，则会浪费纸张，需要换纸重新打印。如果是没有任何图像，则浪费打印机执行打印任务所消耗的电能。总之，可以设置相应的判断逻辑，以使管理终端在检测打印机缺墨的时候，中断打印机执行任何打印任务。在上述例子中，当管理终端确定控制参数“Stop Printing”后，向云管理平台发送控制请求，在该请求中携带有控制参数“Stop Printing”和打 印机的设备标识“CNJ8F7F46S”。当云管理平台接收到控制请求后，提取出控制请求中打印机的设备标识“CNJ8F7F46S”，以确定管理终端是针对哪一绑定的NB-IoT设备提出的控制请求。当云管理平台确定该条控制请求是针对设备标识为“CNJ8F7F46S”的打印机所提出的，将控制请求发送至“CNJ8F7F46S”对应的打印机。
可选地，当NB-IoT设备需要向管理终端发送数据上报消息时，可以通过下述方式实现。第二绑定消息还携带有管理终端的第二设备标识；云管理平台将第二设备标识与第一设备标识对应地添加到预先建立的设备绑定关系中。
在实施中，可以在第二绑定消息中增加管理终端的第二设备标识。当云管理平台接收到第二绑定消息时，可以提取出第二设备标识和第一设备标识。第二设备标识对应着管理终端，第一设备标识对应着NB-IoT设备。在云管理平台中可以建立一张设备绑定关系列表，在该列表中可以将第二设备标识与第一设备标识对应存储，以保存管理终端与NB-IoT设备的绑定关系。需要说明的是，一般一个管理终端会对应多个需要管理的NB-IoT设备。
可选地，本实施例提供的方法还包括：NB-IoT设备向云管理平台发送数据上报消息，数据上报消息中携带有目标数据和第一设备标识；云管理平台根据设备绑定关系，确定第一设备标识对应的第二设备标识；云管理平台将数据上报消息发送至与第二设备标识对应的管理终端。
在实施中，NB-IoT设备可以在本地生成数据上报消息，该数据上报消息中携带有目标数据和第一设备标识。当云管理平台接收到数据上报消息时，提取出第一设备标识，以确定数据上报消息是哪个NB-IoT设备发送过来的。当提取出第一设备标识后，云管理平台可以在本地中的设备绑定关系列表查询与NB-IoT设备绑定的管理终端的第二设备标识。云管理平台将数据上报消息发送至与第二设备标识对应的管理终端。管理终端接收到数据上报信息后，对上报信息进行处理，以确定后续执行什么控制操作等。需要说明的是，可以不在云管理平台中建立第二设备标识与第一设备标识的对应关系，而是使NB-IoT设备向管理终端发送数据上报消息时，将需要接收数据上报消息的管理终端的标识放入数据上报消息中，云管理平台可以根据数据上报消息中的第二设备标识判断将数据上报消息发送至哪个管理终端。
综上，在图2中，本公开实施例执行的过程如下：首先，NB-IoT设备在检测到第一操作指令时，向云管理平台发送第一绑定消息。接着，云管理平台 将设备信息与第一设备标识对应存储。然后，管理终端在检测到第二操作指令时，从用户处获取待绑定的NB-IoT设备的第一设备标识，管理终端向云管理平台发送第二绑定消息。随后，云管理平台基于第二绑定消息中携带的第一设备标识，在本地查找第一设备标识对应的设备信息，将设备信息发送给管理终端。最后，管理终端将设备信息存储为绑定NB-IoT设备的设备信息。
通过本公开实施例，通过云管理平台使得NB-IoT设备和管理终端，可以相互通信，进而可以将NB-IoT设备绑定在管理终端上，以便后续管理终端对NB-IoT设备进行管理。
图3是本公开实施例提供的一种物联网控制系统的结构示意图。参见图3，所述系统包括NB-IoT设备310、核心网的云管理平台320和管理终端330；
所述NB-IoT设备310，用于在检测到第一操作指令时，向所述云管理平台320发送第一绑定消息，所述第一绑定消息中携带有所述NB-IoT设备310的设备信息和第一设备标识；
所述云管理平台320，用于将所述设备信息与所述第一设备标识对应存储；
所述管理终端330，用于在检测到第二操作指令时，获取待绑定的所述NB-IoT设备310的第一设备标识，所述管理终端330向所述云管理平台320发送第二绑定消息，所述第二绑定消息中携带有所述第一设备标识；
所述云管理平台320，用于基于所述第二绑定消息中携带的所述第一设备标识，在本地查找所述第一设备标识对应的所述设备信息，将所述设备信息发送给所述管理终端330；
所述管理终端330，用于将所述设备信息存储为绑定NB-IoT设备310的设备信息。
可选地，所述设备信息包括以下任一项或多项：设备类型、设备名称、运行参数。
可选地，所述管理终端330还用于基于所述设备信息确定控制参数，向所述云管理平台320发送控制请求，其中，所述控制请求中携带有所述控制参数和所述第一设备标识；
所述云管理平台320还用于将所述控制请求发送至与所述第一设备标识对应的所述NB-IoT设备310。
可选地，所述第二绑定消息还携带有所述管理终端330的第二设备标识；
所述云管理平台320还用于将所述第二设备标识与所述第一设备标识对应地添加到预先建立的设备绑定关系中。
可选地，所述NB-IoT设备310还用于向所述云管理平台320发送数据上报消息，所述数据上报消息中携带有目标数据和所述第一设备标识；
所述云管理平台320还用于根据所述设备绑定关系，确定所述第一设备标识对应的所述第二设备标识；
所述云管理平台320还用于将所述数据上报消息发送至与所述第二设备标识对应的所述管理终端330。
可选地，所述管理终端330用于获取用户输入的待绑定的所述NB-IoT设备310的第一设备标识。
通过本公开实施例，通过云管理平台使得NB-IoT设备和管理终端，可以相互通信，进而可以将NB-IoT设备绑定在管理终端上，以便后续管理终端对NB-IoT设备进行管理。
需要说明的是：上述实施例提供的物联网控制系统与NB-IoT设备绑定方法实施例属于同一构思，其具体实现过程详见方法实施例，这里不再赘述。
本公开再一示例性实施例示出了一种终端的结构示意图。其中，终端可以是上述实施例中的管理终端。参照图4，终端1000可以包括以下一个或多个组件：处理组件1002，存储器1004，电源组件1006，多媒体组件1008，音频组件1010，输入/输出(I/O)的接口1012，传感器组件1014，以及通信组件1016。
处理组件1002通常控制终端1000的整体操作，诸如与显示，电话呼叫，数据通信，相机操作和记录操作相关联的操作。处理元件1002可以包括一个或多个处理器1020来执行指令，以完成上述的方法的全部或部分步骤。此外，处理组件1002可以包括一个或多个模块，便于处理组件1002和其他组件之间的交互。例如，处理部件1002可以包括多媒体模块，以方便多媒体组件1008和处理组件1002之间的交互。
存储器1004被配置为存储各种类型的数据以支持在终端1000的操作。这些数据的示例包括用于在终端1000上操作的任何应用程序或方法的指令，联系人数据，电话簿数据，消息，图片，视频等。存储器1004可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储 器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
通信组件1016被配置为便于终端1000和其他设备之间有线或无线方式的通信。终端1000可以接入基于通信标准的无线网络，如WiFi，2G或3G，或它们的组合。在一个示例性实施例中，通信部件1016经由广播信道接收来自外部广播管理系统的广播信号或广播相关信息。在一个示例性实施例中，所述通信部件1016还包括近场通信(NFC)模块，以促进短程通信。例如，在NFC模块可基于射频识别(RFID)技术，红外数据协会(IrDA)技术，超宽带(UWB)技术，蓝牙(BT)技术和其他技术来实现。
电力组件1006为终端1000的各种组件提供电力。电力组件1006可以包括电源管理系统，一个或多个电源，及其他与为音频输出设备1000生成、管理和分配电力相关联的组件。
多媒体组件1008包括在所述终端1000和用户之间的提供一个输出接口的屏幕。在一些实施例中，屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板，屏幕可以被实现为触摸屏，以接收来自用户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸面板上的手势。所述触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与所述触摸或滑动操作相关的持续时间和压力。在一些实施例中，多媒体组件1008包括一个前置摄像头和/或后置摄像头。当终端1000处于操作模式，如拍摄模式或视频模式时，前置摄像头和/或后置摄像头可以接收外部的多媒体数据。每个前置摄像头和后置摄像头可以是一个固定的光学透镜系统或具有焦距和光学变焦能力。
音频组件1010被配置为输出和/或输入音频信号。例如，音频组件1010包括一个麦克风(MIC)，当音频输出设备1000处于操作模式，如呼叫模式、记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器1004或经由通信组件1016发送。
I/O接口1012为处理组件1002和外围接口模块之间提供接口，上述外围接口模块可以是键盘，点击轮，按钮等。这些按钮可包括但不限于：主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件1014包括一个或多个传感器，用于为终端1000提供各个方面的状态评估。例如，传感器组件1014可以检测到终端1000的打开/关闭状态， 组件的相对定位，例如所述组件为终端1000的显示器和小键盘，传感器组件1014还可以检测终端1000或终端1000一个组件的位置改变，用户与终端1000接触的存在或不存在，终端1000方位或加速/减速和终端1000的温度变化。传感器组件1014可以包括接近传感器，被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件1014还可以包括光传感器，如CMOS或CCD图像传感器，用于在成像应用中使用。在一些实施例中，该传感器组件1014还可以包括加速度传感器，陀螺仪传感器，磁传感器，压力传感器或温度传感器。
在示例性实施例中，终端1000可以被一个或多个应用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现，用于执行上述方法。
本领域普通技术人员可以理解实现上述实施例的全部或部分步骤可以通过硬件来完成，也可以通过程序来指令相关的硬件完成，所述的程序可以存储于一种计算机可读存储介质中，上述提到的存储介质可以是只读存储器，磁盘或光盘等。
以上所述仅为本公开的较佳实施例，并不用以限制本公开，凡在本公开的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本公开的保护范围之内。

Claims (12)

  1. 一种窄带物联网NB-IoT设备绑定方法，其特征在于，所述方法应用于物联网控制系统，所述物联网控制系统包括NB-IoT设备、核心网的云管理平台和管理终端；
    所述NB-IoT设备在检测到第一操作指令时，向所述云管理平台发送第一绑定消息，所述第一绑定消息中携带有所述NB-IoT设备的设备信息和第一设备标识；
    所述云管理平台将所述设备信息与所述第一设备标识对应存储；
    所述管理终端在检测到第二操作指令时，获取待绑定的所述NB-IoT设备的第一设备标识，所述管理终端向所述云管理平台发送第二绑定消息，所述第二绑定消息中携带有所述第一设备标识；
    所述云管理平台基于所述第二绑定消息中携带的所述第一设备标识，在本地查找所述第一设备标识对应的所述设备信息，将所述设备信息发送给所述管理终端；
    所述管理终端将所述设备信息存储为绑定NB-IoT设备的设备信息。
  2. 根据权利要求1所述的方法，其特征在于，所述设备信息包括以下任一项或多项：设备类型、设备名称、运行参数。
  3. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述管理终端基于所述设备信息确定控制参数，向所述云管理平台发送控制请求，其中，所述控制请求中携带有所述控制参数和所述第一设备标识；
    所述云管理平台将所述控制请求发送至与所述第一设备标识对应的所述NB-IoT设备。
  4. 根据权利要求1所述的方法，其特征在于，所述第二绑定消息还携带有所述管理终端的第二设备标识；
    所述云管理平台将所述第二设备标识与所述第一设备标识对应地添加到预先建立的设备绑定关系中。
  5. 根据权利要求4所述的方法，其特征在于，所述方法还包括：
    所述NB-IoT设备向所述云管理平台发送数据上报消息，所述数据上报消息中携带有目标数据和所述第一设备标识；
    所述云管理平台根据所述设备绑定关系，确定所述第一设备标识对应的所 述第二设备标识；
    所述云管理平台将所述数据上报消息发送至与所述第二设备标识对应的所述管理终端。
  6. 根据权利要求1所述的方法，其特征在于，获取待绑定的所述NB-IoT设备的第一设备标识，包括：
    获取用户输入的待绑定的所述NB-IoT设备的第一设备标识。
  7. 一种物联网控制系统，其特征在于，所述系统包括NB-IoT设备、核心网的云管理平台和管理终端；
    所述NB-IoT设备，用于在检测到第一操作指令时，向所述云管理平台发送第一绑定消息，所述第一绑定消息中携带有所述NB-IoT设备的设备信息和第一设备标识；
    所述云管理平台，用于将所述设备信息与所述第一设备标识对应存储；
    所述管理终端，用于在检测到第二操作指令时，获取待绑定的所述NB-IoT设备的第一设备标识，所述管理终端向所述云管理平台发送第二绑定消息，所述第二绑定消息中携带有所述第一设备标识；
    所述云管理平台，用于基于所述第二绑定消息中携带的所述第一设备标识，在本地查找所述第一设备标识对应的所述设备信息，将所述设备信息发送给所述管理终端；
    所述管理终端，用于将所述设备信息存储为绑定NB-IoT设备的设备信息。
  8. 根据权利要求7所述的系统，其特征在于，所述设备信息包括以下任一项或多项：设备类型、设备名称、运行参数。
  9. 根据权利要求7所述的系统，其特征在于，所述管理终端还用于基于所述设备信息确定控制参数，向所述云管理平台发送控制请求，其中，所述控制请求中携带有所述控制参数和所述第一设备标识；
    所述云管理平台还用于将所述控制请求发送至与所述第一设备标识对应的所述NB-IoT设备。
  10. 根据权利要求7所述的系统，其特征在于，所述第二绑定消息还携带有所述管理终端的第二设备标识；
    所述云管理平台还用于将所述第二设备标识与所述第一设备标识对应地添加到预先建立的设备绑定关系中。
  11. 根据权利要求10所述的系统，其特征在于，所述NB-IoT设备还用于向所述云管理平台发送数据上报消息，所述数据上报消息中携带有目标数据和所述第一设备标识；
    所述云管理平台还用于根据所述设备绑定关系，确定所述第一设备标识对应的所述第二设备标识；
    所述云管理平台还用于将所述数据上报消息发送至与所述第二设备标识对应的所述管理终端。
  12. 根据权利要求7所述的系统，其特征在于，所述管理终端用于获取用户输入的待绑定的所述NB-IoT设备的第一设备标识。
PCT/CN2017/094292 2017-07-25 2017-07-25 一种NB-IoT设备绑定方法和一种物联网控制系统 WO2019019014A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
PCT/CN2017/094292 WO2019019014A1 (zh) 2017-07-25 2017-07-25 一种NB-IoT设备绑定方法和一种物联网控制系统
CN201780000683.2A CN108521857B (zh) 2017-07-25 2017-07-25 一种NB-IoT设备绑定方法和一种物联网控制系统
US16/726,874 US11005944B2 (en) 2017-07-25 2019-12-25 Method for binding NB-IoT device, and internet of things control system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/094292 WO2019019014A1 (zh) 2017-07-25 2017-07-25 一种NB-IoT设备绑定方法和一种物联网控制系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/726,874 Continuation US11005944B2 (en) 2017-07-25 2019-12-25 Method for binding NB-IoT device, and internet of things control system

Publications (1)

Publication Number Publication Date
WO2019019014A1 true WO2019019014A1 (zh) 2019-01-31

Family

ID=63434396

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/094292 WO2019019014A1 (zh) 2017-07-25 2017-07-25 一种NB-IoT设备绑定方法和一种物联网控制系统

Country Status (3)

Country Link
US (1) US11005944B2 (zh)
CN (1) CN108521857B (zh)
WO (1) WO2019019014A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114222319A (zh) * 2021-12-08 2022-03-22 天翼物联科技有限公司 一种物联网终端的数据传输方法、装置和存储介质

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109341025B (zh) * 2018-10-22 2020-06-19 四川虹美智能科技有限公司 一种智能空调集中管控系统及方法
CN111491322B (zh) * 2019-01-28 2023-07-21 中国移动通信有限公司研究院 一种处理方法及设备
CN109639842B (zh) * 2019-02-26 2021-09-28 四川爱联科技股份有限公司 Nb-iot设备软件升级系统及方法
US20220321290A1 (en) * 2019-06-28 2022-10-06 Beijing Xiaomi Mobile Software Co., Ltd. Control resource configuration method and apparatus, control resource determination method and apparatus, communication device, and storage medium
CN112443868B (zh) * 2019-08-29 2022-03-18 宁波方太厨具有限公司 一种楼宇集中式排烟系统中室内吸油烟机遥控终端绑定方法
CN112443867B (zh) * 2019-08-29 2022-11-29 宁波方太厨具有限公司 楼宇集中式排烟系统中室内吸油烟机遥控终端绑定方法
TWI713325B (zh) * 2019-09-17 2020-12-11 宜鼎國際股份有限公司 可遠端控制電子設備的系統及方法
CN110677248B (zh) * 2019-10-30 2022-09-30 宁波奥克斯电气股份有限公司 一种基于窄带物联网的安全绑定方法和系统
CN110830966B (zh) * 2019-10-31 2023-08-11 青岛海信移动通信技术有限公司 一种物联网设备的绑定方法及物联网系统
CN113703324A (zh) * 2020-05-20 2021-11-26 阿里巴巴集团控股有限公司 物联网IoT设备控制系统、方法、装置及设备
CN112737849B (zh) * 2020-12-29 2023-02-03 青岛海尔科技有限公司 一种设备信息处理方法及装置
CN112804102B (zh) * 2021-01-12 2023-05-16 北京嘀嘀无限科技发展有限公司 设备绑定方法、装置和终端
CN113542360A (zh) * 2021-06-17 2021-10-22 深圳市元征未来汽车技术有限公司 信息关联方法、关联装置、电子设备及可读存储介质
CN113596090B (zh) * 2021-06-25 2023-10-24 青岛海尔科技有限公司 终端设备的绑定方法、装置、计算机设备和存储介质
CN113472587B (zh) * 2021-07-12 2022-09-13 山东大学 一种基于网络通信的物联网设备与物模型绑定方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120127011A1 (en) * 2010-11-24 2012-05-24 Industrial Technology Research Institute Method, System and Devices for Remote Control and Be-Controlled
CN103763392A (zh) * 2014-01-29 2014-04-30 百度在线网络技术（北京）有限公司 设备的控制方法、装置及系统
CN104601714A (zh) * 2015-01-29 2015-05-06 太仓市同维电子有限公司 手机应用程序管理三层网络终端的实现方法
CN105812491A (zh) * 2016-05-12 2016-07-27 腾讯科技（深圳）有限公司 设备远程绑定方法和装置

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10616739B2 (en) * 2014-12-17 2020-04-07 Nokia Technologies Oy Method and apparatus for local data monitoring and actuator control in an internet of things network
CN104994073B (zh) * 2015-05-29 2019-03-19 北京奇虎科技有限公司 手机终端、服务器及其帐号与设备绑定控制、执行方法
CN104935583B (zh) * 2015-05-29 2018-09-25 四川长虹电器股份有限公司 一种云端服务平台、信息处理方法及数据处理系统
CN105741525B (zh) * 2016-02-24 2019-10-01 北京小米移动软件有限公司 遥控器绑定的处理方法、装置和设备
CN105871821A (zh) * 2016-03-24 2016-08-17 浙江风向标科技有限公司 设备绑定的方法
KR101688813B1 (ko) * 2016-04-18 2016-12-22 (주)케이사인 IoT 기기와 소유자 사이의 관계 확립을 위한 방법 및 시스템
JP2020519166A (ja) * 2017-05-01 2020-06-25 エルジー エレクトロニクス インコーポレイティド 無線通信システムにおける端末のｄ２ｄ動作方法及びその方法を利用する端末

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120127011A1 (en) * 2010-11-24 2012-05-24 Industrial Technology Research Institute Method, System and Devices for Remote Control and Be-Controlled
CN103763392A (zh) * 2014-01-29 2014-04-30 百度在线网络技术（北京）有限公司 设备的控制方法、装置及系统
CN104601714A (zh) * 2015-01-29 2015-05-06 太仓市同维电子有限公司 手机应用程序管理三层网络终端的实现方法
CN105812491A (zh) * 2016-05-12 2016-07-27 腾讯科技（深圳）有限公司 设备远程绑定方法和装置

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114222319A (zh) * 2021-12-08 2022-03-22 天翼物联科技有限公司 一种物联网终端的数据传输方法、装置和存储介质
CN114222319B (zh) * 2021-12-08 2024-03-26 天翼物联科技有限公司 一种物联网终端的数据传输方法、装置和存储介质

Also Published As

Publication number Publication date
US11005944B2 (en) 2021-05-11
CN108521857B (zh) 2021-08-03
US20200137168A1 (en) 2020-04-30
CN108521857A (zh) 2018-09-11

Similar Documents

Publication Publication Date Title
WO2019019014A1 (zh) 一种NB-IoT设备绑定方法和一种物联网控制系统
WO2017177572A1 (zh) 无线接入点的接入方法和装置
EP3136793B1 (en) Method and apparatus for awakening electronic device
WO2016206293A1 (zh) 运营商网络的接入方法和装置
JP6214812B2 (ja) 振込処理方法および装置
WO2017201861A1 (zh) Zigbee设备的升级方法和装置
US10608988B2 (en) Method and apparatus for bluetooth-based identity recognition
WO2016183992A1 (zh) 对账户与设备的控制关系进行管理的方法、装置和系统
WO2017036037A1 (zh) 拍摄控制方法和装置
CN104660685A (zh) 设备信息获取方法及装置
WO2016058334A1 (zh) 一种升级方法、装置及设备
JP2017529030A (ja) Ｍｃｕチップのウェイクアップ方法及び装置
EP3076745B1 (en) Methods and apparatuses for controlling wireless access point
TWI659662B (zh) 定位資訊收集方法、裝置及移動終端
JP6284687B2 (ja) Ｍｃｕウェイクアップ方法及び装置
US20170013456A1 (en) Method and device for testing a terminal
WO2019000414A1 (zh) 蜂窝网络中实现边缘计算的方法、装置、设备及基站
WO2018120778A1 (zh) 区域配置的方法及装置
WO2021081796A1 (zh) 寻呼信令接收方法和装置、寻呼信令发送方法和装置
WO2019019164A1 (zh) 无人机管理方法及装置、通信连接建立方法及装置
WO2017088588A1 (zh) 触摸屏报点的处理方法及装置
EP3647970A1 (en) Method and apparatus for sharing information
CN104461358A (zh) 点亮屏幕的方法及装置
CN105578391B (zh) 信息处理方法、装置、系统及终端设备
CN105653186A (zh) 终端控制方法及装置

Legal Events

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

Ref document number: 17919527

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17919527

Country of ref document: EP

Kind code of ref document: A1