WO2016111916A1 - Système et procédé de mise en œuvre d'applications de commande à distance de l'internet des objets (ido) - Google Patents

Système et procédé de mise en œuvre d'applications de commande à distance de l'internet des objets (ido) Download PDF

Info

Publication number
WO2016111916A1
WO2016111916A1 PCT/US2016/012021 US2016012021W WO2016111916A1 WO 2016111916 A1 WO2016111916 A1 WO 2016111916A1 US 2016012021 W US2016012021 W US 2016012021W WO 2016111916 A1 WO2016111916 A1 WO 2016111916A1
Authority
WO
WIPO (PCT)
Prior art keywords
lot
hub
user
service
remote control
Prior art date
Application number
PCT/US2016/012021
Other languages
English (en)
Inventor
Joe BRITT
Justin Lee
Shin MATSUMURA
Houman FOROOD
Scott Zimmerman
Phillip Myles
Sean ZAWICKI
Daisuke KUTAMI
Original Assignee
Afero, Inc.
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
Priority claimed from US14/590,700 external-priority patent/US10816944B2/en
Priority claimed from US14/590,719 external-priority patent/US9729340B2/en
Priority claimed from US14/590,686 external-priority patent/US9933768B2/en
Priority claimed from US14/590,765 external-priority patent/US20160197769A1/en
Priority claimed from US14/590,663 external-priority patent/US9774497B2/en
Priority claimed from US14/590,649 external-priority patent/US20160198536A1/en
Priority claimed from US14/590,708 external-priority patent/US9860681B2/en
Priority claimed from US14/590,799 external-priority patent/US9774507B2/en
Application filed by Afero, Inc. filed Critical Afero, Inc.
Priority to CN201680010500.0A priority Critical patent/CN107251530B/zh
Priority to KR1020177021721A priority patent/KR102524513B1/ko
Publication of WO2016111916A1 publication Critical patent/WO2016111916A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2803—Home automation networks
    • H04L12/2816—Controlling appliance services of a home automation network by calling their functionalities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2803—Home automation networks
    • H04L12/283—Processing of data at an internetworking point of a home automation network
    • H04L12/2832—Interconnection of the control functionalities between home networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • 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/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
    • 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/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/565—Conversion or adaptation of application format or content
    • H04L67/5651—Reducing the amount or size of exchanged application data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • 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

Definitions

  • This invention relates generally to the field of computer systems. More particularly, the invention relates to a system and method for implementing loT remote control applications.
  • the "Internet of Things” refers to the interconnection of uniquely-identifiable embedded devices within the Internet infrastructure. Ultimately, loT is expected to result in new, wide-ranging types of applications in which virtually any type of physical thing may provide information about itself or its surroundings and/or may be controlled remotely via client devices over the Internet.
  • loT development and adoption has been slow due to issues related to connectivity, power, and a lack of standardization.
  • one obstacle to loT development and adoption is that no standard platform exists to allow developers to design and offer new loT devices and services.
  • a developer In order enter into the loT market, a developer must design the entire loT platform from the ground up, including the network protocols and infrastructure, hardware, software and services required to support the desired loT implementation.
  • each provider of loT devices uses proprietary techniques for designing and connecting the loT devices, making the adoption of multiple types of loT devices burdensome for end users.
  • Another obstacle to loT adoption is the difficulty associated with connecting and powering loT devices.
  • Connecting appliances such as refrigerators, garage door openers, environmental sensors, home security sensors/controllers, etc, for example, requires an electrical source to power each connected loT device, and such an electrical source is often not conveniently located (e.g., an AC outlet is generally not found within a refrigerator).
  • FIGS. 1 A-B illustrates different embodiments of an loT system architecture
  • FIG. 2 illustrates an loT device in accordance with one embodiment of the invention
  • FIG. 3 illustrates an loT hub in accordance with one embodiment of the invention
  • FIG. 4A-B illustrate embodiments of the invention for controlling and collecting data from loT devices, and generating notifications
  • FIG. 5 illustrates embodiments of the invention for collecting data from loT devices and generating notifications from an loT hub and/or loT service
  • FIG. 6 illustrates embodiments of the invention for detecting loss of hub connectivity and notifying a user
  • FIGS. 7A-C illustrate different embodiments of a miniature loT hub device with LED lights and USB ports
  • FIG. 8 illustrates a method for controlling electronics and other equipment with loT devices
  • FIG. 9 illustrates one embodiment of an loT hub for selecting between different cell carriers
  • FIG. 10 illustrates one embodiment of a method for selecting between different cell carriers
  • FIG. 11 illustrates one embodiment of an loT hub filtering events from loT devices
  • FIG. 12 illustrates one embodiment of an loT hub collecting data related to user behavior within an loT system
  • FIG. 13 illustrates a high level view of one embodiment of a security architecture
  • FIG. 14 illustrates one embodiment of an architecture in which a subscriber identity module (SIM) is used to store keys on loT devices;
  • SIM subscriber identity module
  • FIG. 15A illustrates one embodiment in which loT devices are registered using barcodes or QR codes
  • FIG. 15B illustrates one embodiment in which pairing is performed using barcodes or QR codes
  • FIG. 16 illustrates one embodiment of a method for programming a SIM using an loT hub
  • FIG. 17 illustrates one embodiment of a method for registering an loT device with an loT hub and loT service
  • FIG. 18 illustrates one embodiment of a method for encrypting data to be transmitted to an loT device.
  • One embodiment of the invention comprises an Internet of Things (loT) platform which may be utilized by developers to design and build new loT devices and applications.
  • a base hardware/software platform for loT devices including a predefined networking protocol stack and an loT hub through which the loT devices are coupled to the Internet.
  • one embodiment includes an loT service through which the loT hubs and connected loT devices may be accessed and managed as described below.
  • the loT platform includes an loT app or Web application (e.g., executed on a client device) to access and configured the loT service, hub and connected devices.
  • existing online retailers and other Website operators may leverage the loT platform described herein to readily provide unique loT functionality to existing user bases.
  • Figure 1 A illustrates an overview of an architectural platform on which embodiments of the invention may be implemented.
  • the illustrated embodiment includes a plurality of loT devices 101 -105 communicatively coupled over local communication channels 130 to a central loT hub 1 10 which is itself
  • the loT service 120 includes an end user database 122 for maintaining user account information and data collected from each user's loT devices.
  • the loT devices include sensors (e.g., temperature sensors, accelerometers, heat sensors, motion detectore, etc)
  • the database 122 may be continually updated to store the data collected by the loT devices 101 -105.
  • the data stored in the database 122 may then be made accessible to the end user via the loT app or browser installed on the user's device 135 (or via a desktop or other client computer system) and to web clients (e.g., such as websites 130 subscribing to the loT service 120).
  • the loT devices 101 -105 may be equipped with various types of sensors to collect information about themselves and their surroundings and provide the collected information to the loT service 120, user devices 135 and/or external Websites 130 via the loT hub 1 10. Some of the loT devices 101 -105 may perform a specified function in response to control commands sent through the loT hub 1 10. Various specific examples of information collected by the loT devices 101 -105 and control commands are provided below.
  • the loT device 101 is a user input device designed to record user selections and send the user selections to the loT service 120 and/or Website.
  • the loT hub 1 10 includes a cellular radio to establish a connection to the Internet 220 via a cellular service 1 15 such as a 4G (e.g., Mobile WiMAX, LTE) or 5G cellular data service.
  • a cellular service 1 15 such as a 4G (e.g., Mobile WiMAX, LTE) or 5G cellular data service.
  • the loT hub 1 10 may include a WiFi radio to establish a WiFi connection through a WiFi access point or router 1 16 which couples the loT hub 1 10 to the Internet (e.g., via an Internet Service Provider providing Internet service to the end user).
  • a WiFi radio to establish a WiFi connection through a WiFi access point or router 1 16 which couples the loT hub 1 10 to the Internet (e.g., via an Internet Service Provider providing Internet service to the end user).
  • the underlying principles of the invention are not limited to any particular type of communication channel or protocol.
  • the loT devices 101 -105 are ultra low-power devices capable of operating for extended periods of time on battery power (e.g., years).
  • the local communication channels 130 may be implemented using a low-power wireless communication technology such as Bluetooth Low Energy (LE).
  • LE Bluetooth Low Energy
  • each of the loT devices 101 -105 and the loT hub 1 10 are equipped with Bluetooth LE radios and protocol stacks.
  • the loT platform includes an loT app or Web application executed on user devices 135 to allow users to access and configure the connected loT devices 101 -105, loT hub 1 10, and/or loT service 120.
  • the app or web application may be designed by the operator of a Website 130 to provide loT functionality to its user base.
  • the Website may maintain a user database 131 containing account records related to each user.
  • FIG 1 B illustrates additional connection options for a plurality of loT hubs 1 10-1 1 1 , 190
  • a single user may have multiple hubs 1 10-1 1 1 installed onsite at a single user premises 180 (e.g., the user's home or business). This may be done, for example, to extend the wireless range needed to connect all of the loT devices 101 -105.
  • a user may be connected via a local communication channel (e.g., Wifi, Ethernet, Power Line Networking, etc).
  • each of the hubs 1 10-1 1 1 may establish a direct connection to the loT service 120 through a cellular 1 15 or WiFi 1 16 connection (not explicitly shown in Figure 1 B).
  • one of the loT hubs such as loT hub 1 10 may act as a "master" hub which provides connectivity and/or local services to all of the other loT hubs on the user premises 180, such as loT hub 1 1 1 (as indicated by the dotted line connecting loT hub 1 10 and loT hub 1 1 1 ).
  • the master loT hub 1 10 may be the only loT hub to establish a direct connection to the loT service 120.
  • only the "master" loT hub 1 10 is equipped with a cellular communication interface to establish the connection to the loT service 120. As such, all communication between the loT service 120 and the other loT hubs 1 1 1 will flow through the master loT hub 1 10.
  • the master loT hub 1 10 may be provided with additional program code to perform filtering operations on the data exchanged between the other loT hubs 1 1 1 and loT service 120 (e.g., servicing some data requests locally when possible).
  • the loT service 120 will logically associate the hubs with the user and combine all of the attached loT devices 101 -105 under a single comprehensive user interface, accessible via a user device with the installed app 135 (and/or a browser-based interface).
  • the master loT hub 1 10 and one or more slave loT hubs 1 1 1 may connect over a local network which may be a WiFi network 1 16, an Ethernet network, and/or a using power-line communications (PLC) networking (e.g., where all or portions of the network are run through the user's power lines).
  • a local network which may be a WiFi network 1 16, an Ethernet network, and/or a using power-line communications (PLC) networking (e.g., where all or portions of the network are run through the user's power lines).
  • PLC power-line communications
  • each of the loT devices 101 -105 may be interconnected with the loT hubs 1 10-1 1 1 using any type of local network channel such as WiFi, Ethernet, PLC, or Bluetooth LE, to name a few.
  • Figure 1 B also shows an loT hub 190 installed at a second user premises 181 .
  • loT hubs 190 may be installed and configured to collect data from loT devices 191 -192 at user premises around the world.
  • the two user premises 180-181 may be configured for the same user.
  • one user premises 180 may be the user's primary home and the other user premises 181 may be the user's vacation home.
  • an exemplary embodiment of an loT device 101 includes a memory 210 for storing program code and data 201 -203 and a low power microcontroller 200 for executing the program code and processing the data.
  • the memory 210 may be a volatile memory such as dynamic random access memory (DRAM) or may be a non-volatile memory such as Flash memory.
  • a non-volatile memory may be used for persistent storage and a volatile memory may be used for execution of the program code and data at runtime.
  • the memory 210 may be integrated within the low power microcontroller 200 or may be coupled to the low power microcontroller 200 via a bus or communication fabric. The underlying principles of the invention are not limited to any particular implementation of the memory 210.
  • the program code may include application program code 203 defining an application-specific set of functions to be performed by the loT device 201 and library code 202 comprising a set of predefined building blocks which may be utilized by the application developer of the loT device 101 .
  • the library code 202 comprises a set of basic functions required to implement an loT device such as a communication protocol stack 201 for enabling communication between each loT device 101 and the loT hub 1 10.
  • the loT device such as a communication protocol stack 201 for enabling communication between each loT device 101 and the loT hub 1 10.
  • Bluetooth LE radio and antenna 207 may be integrated within the low power microcontroller 200.
  • the underlying principles of the invention are not limited to any particular communication protocol.
  • the particular embodiment shown in Figure 2 also includes a plurality of input devices or sensors 210 to receive user input and provide the user input to the low power microcontroller, which processes the user input in accordance with the
  • each of the input devices include an LED 209 to provide feedback to the end user.
  • the illustrated embodiment includes a battery 208 for supplying power to the low power microcontroller.
  • a battery 208 for supplying power to the low power microcontroller.
  • a non-chargeable coin cell battery is used.
  • an integrated rechargeable battery may be used (e.g., rechargeable by connecting the loT device to an AC power supply (not shown)).
  • a speaker 205 is also provided for generating audio.
  • the low power microcontroller 299 includes audio decoding logic for decoding a compressed audio stream (e.g., such as an MPEG-4/Advanced Audio Coding (AAC) stream) to generate audio on the speaker 205.
  • AAC Advanced Audio Coding
  • the low power microcontroller 200 and/or the application code/data 203 may include digitally sampled snippets of audio to provide verbal feedback to the end user as the user enters selections via the input devices 210.
  • one or more other/alternate I/O devices or sensors 250 may be included on the loT device 101 based on the particular application for which the loT device 101 is designed.
  • an environmental sensor may be included to measure temperature, pressure, humidity, etc.
  • a security sensor and/or door lock opener may be included if the loT device is used as a security device.
  • these examples are provided merely for the purposes of illustration.
  • the underlying principles of the invention are not limited to any particular type of loT device.
  • an application developer may readily develop new application code 203 and new I/O devices 250 to interface with the low power microcontroller for virtually any type of loT application.
  • the low power microcontroller 200 also includes a secure key store for storing encryption keys for encrypting communications and/or generating signatures.
  • the keys may be secured in a subscriber identity module (SIM).
  • SIM subscriber identity module
  • a wakeup receiver 207 is included in one embodiment to wake the loT device from an ultra low power state in which it is consuming virtually no power.
  • the wakeup receiver 207 is configured to cause the loT device 101 to exit this low power state in response to a wakeup signal received from a wakeup transmitter 307 configured on the loT hub 1 10 as shown in Figure 3.
  • the transmitter 307 and receiver 207 together form an electrical resonant transformer circuit such as a Tesla coil. In operation, energy is transmitted via radio frequency signals from the transmitter 307 to the receiver 207 when the hub 1 10 needs to wake the loT device 101 from a very low power state.
  • the loT device 101 may be configured to consume virtually no power when it is in its low power state because it does not need to continually "listen" for a signal from the hub (as is the case with network protocols which allow devices to be awakened via a network signal). Rather, the microcontroller 200 of the loT device 101 may be configured to wake up after being effectively powered down by using the energy electrically transmitted from the transmitter 307 to the receiver 207.
  • the loT hub 1 10 also includes a memory 317 for storing program code and data 305 and hardware logic 301 such as a microcontroller for executing the program code and processing the data.
  • a wide area network (WAN) interface 302 and antenna 310 couple the loT hub 1 10 to the cellular service 1 15.
  • WAN wide area network
  • the loT hub 1 10 may also include a local network interface (not shown) such as a WiFi interface (and WiFi antenna) or Ethernet interface for establishing a local area network communication channel.
  • the hardware logic 301 also includes a secure key store for storing encryption keys for encrypting communications and generating/verifying signatures. Alternatively, the keys may be secured in a subscriber identity module (SIM).
  • SIM subscriber identity module
  • a local communication interface 303 and antenna 31 1 establishes local communication channels with each of the loT devices 101 -105.
  • the local communication interface 303/antenna 31 1 implements the Bluetooth LE standard.
  • the underlying principles of the invention are not limited to any particular protocols for establishing the local communication channels with the loT devices 101 -105.
  • the WAN interface 302 and/or local communication interface 303 may be embedded within the same chip as the hardware logic 301 .
  • the program code and data includes a communication protocol stack 308 which may include separate stacks for communicating over the local communication interface 303 and the WAN interface 302.
  • device pairing program code and data 306 may be stored in the memory to allow the loT hub to pair with new loT devices.
  • each new loT device 101 -105 is assigned a unique code which is communicated to the loT hub 1 10 during the pairing process.
  • the unique code may be embedded in a barcode on the loT device and may be read by the barcode reader 106 or may be communicated over the local
  • the unique ID code can be transmitted, such as via radio frequency ID (RFID) or near field communication (NFC), from the loT device and the loT hub has a suitable receiver to detect the code when the loT device 101 is moved within a few inches of the loT hub 1 10.
  • RFID radio frequency ID
  • NFC near field communication
  • the loT hub 1 10 may verify the unique ID by querying a local database (not shown), performing a hash to verify that the code is acceptable, and/or communicating with the loT service 120, user device 135 and/or Website 130 to validate the ID code. Once validated, in one embodiment, the loT hub 1 10 pairs the loT device 101 and stores the pairing data in memory 317 (which, as mentioned, may include non-volatile memory). Once pairing is complete, the loT hub 1 10 may connect with the loT device 101 to perform the various loT functions described herein.
  • the organization running the loT service 120 may provide the loT hub 1 10 and a basic hardware/software platform to allow developers to easily design new loT services.
  • developers may be provided with a software development kit (SDK) to update the program code and data 305 executed within the hub 1 10.
  • the SDK may include an extensive set of library code 202 designed for the base loT hardware (e.g., the low power microcontroller 200 and other components shown in Figure 2) to facilitate the design of various different types of applications 101 .
  • the SDK includes a graphical design interface in which the developer needs only to specify input and outputs for the loT device.
  • the SDK also includes a library code base to facilitate the design of apps for mobile devices (e.g., iPhone and Android devices).
  • the SDK also includes a library code base to facilitate the design of applications and APIs which reside within the IOT Service 120 or Website 130.
  • the loT hub 1 10 manages a continuous bi-directional stream of data between the loT devices 101 -105 and the loT service 120.
  • the loT hub may maintain an open TCP socket to provide regular updates to the user device 135 and/or external Websites 130.
  • the specific networking protocol used to provide updates may be tweaked based on the needs of the underlying application. For example, in some cases, where may not make sense to have a continuous bi-directional stream, a simple request/response protocol may be used to gather information when needed.
  • both the loT hub 1 10 and the loT devices 101 -105 are automatically upgradeable over the network.
  • a new update is available for the loT hub 1 10 it may automatically download and install the update from the loT service 120. It may first copy the updated code into a local memory, run and verify the update before swapping out the older program code.
  • updates are available for each of the loT devices 101 -105, they may initially be downloaded by the loT hub 1 10 and pushed out to each of the loT devices 101 -105. Each loT device 101 -105 may then apply the update in a similar manner as described above for the loT hub and report back the results of the update to the loT hub 1 10. If the update is successful, then the loT hub 1 10 may delete the update from its memory and record the latest version of code installed on each loT device (e.g., so that it may continue to check for new updates for each loT device).
  • the loT hub 1 10 is powered via A/C power.
  • the loT hub 1 10 may include a power unit 390 with a transformer for transforming A/C voltage supplied via an A/C power cord to a lower DC voltage.
  • FIG. 4A illustrates one embodiment of the invention for performing universal remote control operations using the loT system.
  • a set of loT devices 101 -103 are equipped with infrared (IR) and/or radio frequency (RF) blasters 401 -403, respectively, for transmitting remote control codes to control various different types of electronics equipment including air
  • IR infrared
  • RF radio frequency
  • the loT devices 101 -103 are also equipped with sensors 404-406, respectively, for detecting the operation of the devices which they control, as described below.
  • sensor 404 in loT device 101 may be a temperature and/or humidity sensor for sensing the current temperature/humidity and responsively controlling the air conditioner/heater 430 based on a current desired temperature.
  • the air conditioner/heater 430 is one which is designed to be controlled via a remote control device (typically a remote control which itself has a temperature sensor embedded therein).
  • the user provides the desired temperature to the loT hub 1 10 via an app or browser installed on a user device 135.
  • Control logic 412 executed on the loT hub 1 10 receives the current
  • temperature/humidity data from the sensor 404 and responsively transmits commands to the loT device 101 to control the IR/RF blaster 401 in accordance with the desired temperature/humidity. For example, if the temperature is below the desired
  • control logic 412 may transmit a command to the air
  • the command may include the necessary remote control code stored in a database 413 on the loT hub 1 10.
  • the loT service 421 may implement control logic 421 to control the electronics equipment 430-432 based on specified user preferences and stored control codes 422.
  • loT device 102 in the illustrated example is used to control lighting 431 .
  • sensor 405 in loT device 102 may photosensor or photodetector configured to detect the current brightness of the light being produced by a light fixture 431 (or other lighting apparatus).
  • the user may specify a desired lighting level (including an indication of ON or OFF) to the loT hub 1 10 via the user device 135.
  • the control logic 412 will transmit commands to the IR/RF blaster 402 to control the current brightness level of the lights 431 (e.g., increasing the lighting if the current brightness is too low or decreasing the lighting if the current brightness is too high; or simply turning the lights ON or OFF).
  • loT device 103 in the illustrated example is configured to control audiovisual equipment 432 (e.g., a television, A/V receiver, cable/satellite receiver, AppleTVTM, etc).
  • Sensor 406 in loT device 103 may be an audio sensor (e.g., a microphone and associated logic) for detecting a current ambient volume level and/or a photosensor to detect whether a television is on or off based on the light generated by the television (e.g., by measuring the light within a specified spectrum).
  • sensor 406 may include a temperature sensor connected to the audiovisual equipment to detect whether the audio equipment is on or off based on the detected temperature.
  • the control logic 412 may transmit commands to the audiovisual equipment via the IR blaster 403 of the loT device 103.
  • the sensor data and commands are sent over the Bluetooth LE channel.
  • the underlying principles of the invention are not limited to Bluetooth LE or any other communication standard.
  • control codes required to control each of the pieces of electronics equipment are stored in a database 413 on the loT hub 1 10 and/or a database 422 on the loT service 120.
  • the control codes may be provided to the loT hub 1 10 from a master database of control codes 422 for different pieces of equipment maintained on the loT service 120.
  • the end user may specify the types of electronic (or other) equipment to be controlled via the app or browser executed on the user device 135 and, in response, a remote control code learning module 491 on the loT hub may retrieve the required IR/RF codes from the remote control code database 492 on the loT service 120 (e.g., identifying each piece of electronic equipment with a unique ID).
  • the loT hub 1 10 is equipped with an IR/RF interface 490 to allow the remote control code learning module 491 to "learn" new remote control codes directly from the original remote control 495 provided with the electronic equipment.
  • the remote control code learning module 491 may interact with the loT hub 1 10 via the app/browser on the user device 135 to teach the loT hub 1 10 the various control codes generated by the original remote control (e.g., increase temperature, decrease temperature, etc).
  • the remote control codes may be stored in the control code database 413 on the loT hub 1 10 and/or sent back to the loT service 120 to be included in the central remote control code database 492 (and subsequently used by other users with the same air conditioner unit 430).
  • each of the loT devices 101 -103 have an extremely small form factor and may be affixed on or near their respective electronics equipment 430-432 using double-sided tape, a small nail, a magnetic attachment, etc.
  • the loT device 101 For control of a piece of equipment such as the air conditioner 430, it would be desirable to place the loT device 101 sufficiently far away so that the sensor 404 can accurately measure the ambient temperature in the home (e.g., placing the loT device directly on the air conditioner would result in a temperature measurement which would be too low when the air conditioner was running or too high when the heater was running).
  • the loT device 102 used for controlling lighting may be placed on or near the lighting fixture 431 for the sensor 405 to detect the current lighting level.
  • loT hub 1 10 and/or loT service 120 transmits notifications to the end user related to the current status of each piece of electronics equipment.
  • notifications may then be displayed on the display of the user's mobile device 135.
  • the loT hub 1 10 and/or loT service 120 may send the user a notification that the air conditioner is not functioning properly.
  • the user is not home (which may be detected via motion sensors or based on the user's current detected location), and the sensors 406 indicate that audiovisual equipment 430 is on or sensors 405 indicate that the lights are on, then a notification may be sent to the user, asking if the user would like to turn off the audiovisual equipment 432 and/or lights 431 .
  • the same type of notification may be sent for any equipment type.
  • the user may remotely control the electronics equipment 430-432 via the app or browser on the user device 135.
  • the user device 135 is a touchscreen device and the app or browser displays an image of a remote control with user-selectable buttons for controlling the equipment 430-432.
  • the user may open the graphical remote control and turn off or adjust the various different pieces of equipment.
  • the user's selections may be forwarded from the loT service 120 to the loT hub 1 10 which will then control the equipment via the control logic 412.
  • the user input may be sent directly to the loT hub 1 10 from the user device 135.
  • the user may program the control logic 412 on the loT hub 1 10 to perform various automatic control functions with respect to the electronics equipment 430-432.
  • the control logic 412 may automatically turn off the electronics equipment if certain conditions are detected. For example, if the control logic 412 detects that the user is not home and that the air conditioner is not functioning, it may automatically turn off the air conditioner. Similarly, if the user is not home, and the sensors 406 indicate that audiovisual equipment 430 is on or sensors 405 indicate that the lights are on, then the control logic 412 may automatically transmit commands via the IR/RF blasters 403 and 402, to turn off the audiovisual equipment and lights, respectively.
  • FIG. 5 illustrates additional embodiments of loT devices 104-105 equipped with sensors 503-504 for monitoring electronic equipment 530-531 .
  • the loT device 104 of this embodiment includes a temperature sensor 503 which may be placed on or near a stove 530 to detect when the stove has been left on.
  • the loT device 104 transmits the current temperature measured by the temperature sensor 503 to the loT hub 1 10 and/or the loT service 120. If the stove is determined to be on for more than a threshold time period (e.g., based on the measured temperature during this time period), then control logic 512 may transmit a notification to the end user's device 135 informing the user that the stove 530 is on.
  • a threshold time period e.g., based on the measured temperature during this time period
  • an app or browser-based code on the end user's device 135 displays the notification and provides the user with the ability to control the stove 530 (e.g., sending a command to turn the stove off).
  • the loT device 104 may include a control module 501 to turn off the stove, either in response to receiving an instruction from the user or automatically (if the control logic 512 is programmed to do so by the user).
  • the control logic 501 comprises a switch to cut off electricity or gas to the stove 530.
  • the control logic 501 may be integrated within the stove itself.
  • FIG. 5 also illustrates an loT device 105 with a motion sensor 504 for detecting the motion of certain types of electronics equipment such as a washer and/or dryer.
  • a motion sensor 504 for detecting the motion of certain types of electronics equipment such as a washer and/or dryer.
  • Another sensor that may be used is an audio sensor (e.g., microphone and logic) for detecting an ambient volume level.
  • this embodiment may transmit notifications to the end user if certain specified conditions are met (e.g., if motion is detected for an extended period of time, indicating that the washer/dryer are not turning off).
  • loT device 105 may also be equipped with a control module to turn off the washer/dryer 531 (e.g., by switching off electric/gas), automatically, and/or in response to user input.
  • a first loT device with control logic and a switch may be configured to turn off all power in the user's home and a second loT device with control logic and a switch may be configured to turn off all gas in the user's home.
  • loT devices with sensors may then be positioned on or near electronic or gas-powered equipment in the user's home. If the user is notified that a particular piece of equipment has been left on (e.g., the stove 530), the user may then send a command to turn off all electricity or gas in the home to prevent damage.
  • the control logic 512 in the loT hub 1 10 and/or the loT service 120 may be configured to automatically turn off electricity or gas in such situations.
  • the loT hub 1 10 and loT service 120 communicate at periodic intervals. If the loT service 120 detects that the connection to the loT hub 1 10 has been lost (e.g., by failing to receive a request or response from the loT hub for a specified duration), it will communicate this information to the end user's device 135 (e.g., by sending a text message or app-specific notification). This feature is illustrated graphically in Figure 6 which shows that the connection between the loT hub 1 10 and loT service 120 has been disabled.
  • Connection monitoring and notification logic 600 on the loT service 120 detects that the connection has been disabled and, in response, transmits a notification to the end user's device 135 (e.g., over a cellular communication channel, WiFi, or any other communication channel used by the device 135), informing the user of the connection status.
  • the connection monitoring logic detects when the first communication channel between the loT service and the loT hub has become inoperative and the notification logic transmits a
  • the user may then take steps to determine the cause of the connection problem.
  • the loT hub is connected via the cellular network or WiFi
  • the user may simply need to reboot the loT hub device 1 10.
  • connection monitoring and notification logic 600 may ping the hub 1 10 in an attempt to determine the hub's status. After several unsuccessful attempts (i.e., without a response from the hub) it may transmit the notification to the end user's device 135.
  • this mechanism may be used to detect failure of either connection, and may use the remaining good, redundant connection to maintain communication with the loT Hub 1 10.
  • the loT hub 1 10 is implemented with an extremely compact form factor (e.g., the size of a cell phone charger).
  • the loT hub 1 10 may be packaged as a 1 .5 inch (or less) cube.
  • Various alternate sizes are also contemplated such as a depth of between 1 - 2 inches (or less) and a height/length of between 1 - 3 inches or any cube having a side of 2 inches or less.
  • FIGS 7A-C illustrate one particular embodiment in which the loT hub is integrated within a small package designed to be plugged directly into an A/C outlet via A/C input interface 702.
  • the loT hub 1 10 may be strategically positioned for ideal reception anywhere in the user's home where a power outlet exists.
  • the loT hub 1 10 includes a transformer for transforming the high voltage A/C input into a lower voltage D/C signal.
  • the loT hub 1 10 includes all of the features described herein for connecting with an loT service 120 and with a plurality of loT devices 101 -105.
  • the loT hub 1 10 may include multiple communication interfaces (e.g., antennas and software) for communicating with the loT devices and loT service.
  • the loT hub 1 10 includes a powerline communication (PLC) or similar network interface for establishing communication with the loT devices 101 -105 over the A/C power lines.
  • PLC powerline communication
  • the embodiment of the loT hub shown in Figures 7A-C is equipped with light emitting diodes (LEDs) which, in addition to notifying the user of the current status of the hub 1 10, may be used for a night-light.
  • LEDs light emitting diodes
  • the user may place the loT hub in hallway, bathroom, or child's room and use the hub as a dual purpose night-light/loT hub device.
  • the user may program the night light feature via a programming interface on app or browser on the user's device 135. For example, the user may program the night light to come on at a particular time in the evening and to turn off at a particular time in the morning.
  • different, independently controlled colored LEDs are integrated the loT hub. The user may program the colors to be illuminated on the loT hub at different times of the day and evening.
  • LEDs 701 may be turned on/off by the loT hub's integrated low power uC 200.
  • the loT hub has an integrated photodetector to cause the night light to turn on in response to the ambient brightness falling below a specified threshold.
  • the loT hub has one or more integrated USB ports 710 to be used for charging other devices (e.g., such as the user's mobile device 135).
  • the underlying principles of the invention are not limited to an loT hub 1 10 with integrated USB chargers.
  • loT devices are positioned/configured on or near equipment to be controlled.
  • the loT devices are equipped with double-sided tape to allow the user to easily affix the loT devices to various types of equipment.
  • each loT device may include one or more mounting holes into which small nails or screws may be inserted to affix the loT devices to a wall or other surface.
  • some loT devices may include magnetic material to allow the loT devices to be affixed to a metal surface.
  • the loT devices may be programmed at 802 via the user device 135 and loT hub 1 10.
  • the user may connect to the loT hub 1 10 with the app or browser installed on the user device 135 (either directly or through the loT service 120).
  • the app or browser-executable code may comprise a user interface allowing the user to identify and program each loT device.
  • the loT device is selected, for example, the user may be provided with a list of different types of equipment from which to select (e.g., different models of remote controllable air conditioners/heaters, A/V equipment, etc).
  • the remote control codes are stored on the loT hub as described above and transmitted to the IR/RF blasters on the loT devices to control the equipment at 803.
  • various automatic control functions may be implemented by the loT hub.
  • the loT service 120 may enter into agreements with multiple cell carriers 901 to provide connectivity to the loT hubs 1 10 in different geographical regions.
  • the loT service 120 may have agreements with both Verizon and AT&T to provide loT hub connectivity. Consequently, an loT hub 1 10 may be in a location serviced by two or more supported cell carriers.
  • the loT hub 901 includes cellular carrier selection logic 901 for selecting between two or more available cell carriers 915-916.
  • the cell carrier selection logic is programmed with a set of rules 918 for making the selection between the two or more cell carriers 915-916. Once a particular cell carrier has been selected, the cell carrier selection logic 901 instructs the radio/network stack 902 of the loT hub 1 10 to connect with that cell carrier.
  • Various different types of selection rules 918 may be implemented.
  • a first cell carrier 915 e.g., a lower agreed-upon rate/cost 912
  • a second cell carrier 916 e.g., a higher agreed-upon rate/cost 912
  • one rule may simply be to connect with the first cell carrier 915 assuming all other variables are equal or within specified thresholds (e.g., assuming that the second cell carrier's signal strength is sufficient).
  • the selection rules 918 implemented by the cell carrier selection logic 901 may factor in other variables related to cell carrier connectivity and cost including, for example, the current or historical signal strength 91 1 of each cell carrier 915-916 measured at the loT hub 1 10. For example, even if the loT service 120 has a more beneficial arrangement with the first cell carrier 915 as mentioned above, the cell carrier selection logic 901 may still connect to the second cell carrier 916 if the signal strength to the first carrier is below a specified threshold.
  • the cell carrier selection logic 901 may evaluate
  • the cell carrier selection logic 901 may select the second cell carrier (notwithstanding the more beneficial agreement with the first cell carrier).
  • the reliability/performance data 913 and the cell service signal strength data 91 1 may be collected over time by the loT hub 1 10.
  • the loT hub 1 10 may continually monitor signal strength, connection status, bandwidth, and other connection variables with each cell carrier 915-916 and may make connection decisions based (at least in part) on this recorded data.
  • the loT service 120 may provide updates to the loT hub including new/updated selection rules 918 related to the existing cell carriers 915-916 and/or new cell carriers with which it has established agreements. For example, if the agreement between the loT service 120 and the second cell carrier 916 is updated, resulting in a lower cost to connect through second cell carrier 916, then new selection rules 918 and/or new cell service rates 912 including this data may be transmitted from the loT service 120 to the loT hub 1 10.
  • the cell carrier selection logic 901 may then factor in these new rules/rates when rendering cell carrier selection decisions (e.g., tending to favor connection with the second cell carrier 916 if it is more cost-effective to do so).
  • the loT hub 1 10 may be pre-provisioned by the loT service 120 to connect with all available cell carriers 915-916 (i.e., provided with a subscriber identity module (SIM) 903 or other authentication data needed for connecting with the cell carriers 915-916).
  • SIM subscriber identity module
  • a single SIM 903 or other authentication device may be provisioned for multiple cell carriers 915-916.
  • the loT hub 1 10 may still fall back to second cell carrier 916 if the first cell carrier 915 is unavailable.
  • the loT hub 1 10 may switch from the first cell carrier 915 to the second cell carrier 916 in response to changes in current conditions (e.g., a reduction in signal strength to the first cell carrier 915 and/or a reduction in cost for the second cell carrier 916) and/or new selection rules 918 sent from the loT service 120.
  • changes in current conditions e.g., a reduction in signal strength to the first cell carrier 915 and/or a reduction in cost for the second cell carrier 916
  • new selection rules 918 sent from the loT service 120.
  • the loT hub 1 10 may dynamically switch between them throughout the day in accordance with changing parameters. For example, the cost associated with each cellular carrier 915-916 may change throughout the day (e.g., the first carrier 915 may be more expensive during heavy use periods such as rush hour and the second carrier 916 may be more expensive in the evenings). Similarly, the cell towers of one carrier may become overloaded during certain times of the day or evening, resulting in reduced connectivity. Using the techniques described herein, the cell carrier selection logic 901 may continually evaluate these conditions and dynamically switch between carriers as conditions change.
  • FIG. 10 A method in accordance with one embodiment of the invention is illustrated in Figure 10. The method may be implemented within the context of the architecture shown in Figure 9, but is not limited to any particular system architecture.
  • the loT hub is provisioned for multiple cell carriers and programmed with rules related to connecting to the different cell carriers. For example, one rule may cause the loT hub to connect to a first service provider over a second service provider (all other variables being equal or within defined thresholds).
  • data is collected related to cell carrier connectivity, cost, and/or other pertinent variables. For example, as discussed above, each cell carrier's signal strength may be used to render connection decisions.
  • the rules are executed using the collected data to determine the primary cell carrier to which to connect the loT hub. For example, all other variables being equal (or within specified thresholds), the loT hub may initially connect with the lower cost cell carrier. As mentioned, the initial primary cell carrier may be
  • the loT hub connects with the primary cell carrier, potentially using the secondary cell carrier as a fallback connection.
  • the loT hub may then wait a specified time period at 1005 (e.g., an hour, day, week, etc) during which the loT hub may collect additional data related to connectivity, cost, etc. After the delay, the process repeats and, if the rules/data has changed significantly, the loT hub may connect with a new primary cell carrier at 1004.
  • various different types of events 1 101 , 1 102-N may be generated by the loT devices and sent to the loT hub 1 10.
  • the events 1 101 , 1 102-N may include security events such as a door or window being opened in the user's home without a security code or other necessary authentication, a temperature reaching a specified threshold (e.g., indicating that a stove burner has been left on or a potential fire), a motion detector being triggered when the user and the user's family is not home, a smoke detector being triggered, a sensor on a sprinkler system indicating that the sprinkler has been running longer than a specified period of time, and a refrigerator sensor or pantry sensor indicating that the user is low on a particular food item, to name just a few.
  • a specified threshold e.g., indicating that a stove burner has been left on or a potential fire
  • a motion detector being triggered when the user and the user's family is not home
  • a smoke detector being triggered
  • the loT service 120 and/or one or more external services 1 120-1 122 may interface with the loT hub 1 10 via an API to receive the events 1 101 , 1 102-N generated by the various loT devices and may take various actions in response to the events including sending notifications to the user 1 1 15 (e.g., via the user's mobile device).
  • an external grocery service may receive events related to the level of different food items in the user's refrigerator or pantry and automatically update the user's online grocery list or schedule an order.
  • An external security service may receive events related to security at the user's home and attempt to notify the user in response to an alarm. Another service may notify the fire department and/or send a notification to the user if a temperature sensor rises above a particular threshold. Note that these specific examples are provided merely for the purpose of illustration. The underlying principles of the invention are not limited to any particular type of events or event responses.
  • the events generated by the loT devices may be innocuous and may not need to be transmitted to the loT service 120 and/or the external services 1 120-1 122.
  • the user's loT thermostat device may periodically report the current temperature of the user's home and other loT devices may periodically report events which merely indicate measurements within acceptable thresholds.
  • one embodiment of the loT hub 1 10 includes an event filter 1 1 10 which does not forward certain types of events to the loT service 120 and/or external services 1 120-1 122.
  • each event 1 101 , 1 102-N is assigned an identification code indicating an event type.
  • certain event types are filtered out by the event filter (e.g., dropped or simply not forwarded) while other event types are stored on the loT hub 1 10 and forwarded to the loT service 120 and/or other external services 1 120- 1 122.
  • the event filter e.g., dropped or simply not forwarded
  • the external services 1 120-1 122 and/or loT service 120 may be configured to notify the end user of certain types of events by transmitting
  • the loT service 120 may transmit a notification to the end user's device informing the user about the potential problem.
  • the loT hub 1 10 may transmit notifications directly to the end user (in addition to sending the events directly to the loT service 120 and/or external services 1 120-1 122).
  • the external services 1 120-1 122 and loT service 120 utilize an application programming interface (API) exposed by the loT hub 1 10.
  • API application programming interface
  • a particular service may register via the API to receive a particular set of events.
  • the loT service 120 knows which APIs (and therefore, which events), each external service 1 120-1 122 is configured to receive, it may dynamically send filter rules updates 1 1 1 1 to cause the event filter 1 1 10 to forward only those events which have been subscribed to by itself and the various external services 1 120-1 122.
  • the loT hub 1 10 may maintain a log of all events (including those events which are not forwarded to outside services) or may simply drop events which are not forwarded.
  • the loT service 120 includes an event filter for filtering events in accordance with a set of filtering rules as described herein (either in addition to or instead of the event filter 1 1 10 on the loT hub 1 10).
  • each of the external services 1 120-1 122 may subscribe to receive certain types of events through an API exposed by the loT service 120. Events are generated from the loT hub 1 10 (possibly filtered with a local event filter 1 1 10), sent to the loT service 120
  • loT service filter may be configured in a similar manner as the loT hub filter described herein (i.e., only forwarding certain types of events/notifications in accordance with a set of filtering rules).
  • FIG. 12 illustrates an exemplary embodiment in which two users 1201 -1202 control loT devices 101 -102, in a home via loT device control logic 412 on the loT hub 1 10. While, only two loT devices 101 -102 and two users 1201 -1202 are shown for simplicity, there may be many more loT devices and/or users communicatively coupled via the loT hub 1 10. As mentioned, the users 1201 -1201 may interact with the loT devices 101 -102 via an app or browser installed on each user's data processing device (e.g., a smartphone, personal computer, etc). As mentioned, the app may be specifically designed to interface with the loT service 120 and/or the loT hub 1 10 to allow the user to review data provided from the various loT devices 101 -102 and to control the loT devices 101 -102.
  • the app may be specifically designed to interface with the loT service 120 and/or the loT hub 1 10 to allow the user to review data provided from the various loT devices 101 -102 and to control the loT devices 101 -102
  • user behavior data collection logic 1200 executed on the loT hub 1 10 monitors and collects the information viewed by each user (e.g.,
  • one of the two users 1201 -1202 may be a gardener and may periodically review data related to the amount of water consumed in the garden (collected via sensors on an loT device).
  • This user may also control the sprinkler system via the loT device, for example, by programming the loT device control 412 to control the loT device to automatically turn the sprinkler system on and off.
  • the other user may not be involved with gardening but may do the laundry and/or cook in the home.
  • Information related to each of these activities may be collected via the user behavior data collection logic 1200 to generate a user profile for each user.
  • the behavior data is sent from the loT hub 1 10 to the loT service 120 where it is analyzed to determine each user's preferences. Targeted content may then be transmitted to each individual user 1201 -1202 in accordance with these preferences.
  • the user who gardens may receive information related to sales on gardening supplies and the user who cooks may receive information related to kitchen appliances and/or recipes.
  • the owner/operator of the loT service 120 may enter into arrangements with online advertising companies to generate the targeted information for transmission to each of the user's data processing devices.
  • the loT service 120 sends the user behavior data to one or more external services 1 120-1 122 which then generate targeted notifications and content to the end user's data processing device.
  • user behavior data is also collected directly from the loT Service 120 or one of the External Services 1 120-1 122.
  • a user's purchases and other activities outside the context of the loT system may be recorded at the loT service 120 and/or external services 1 120-1 122 and may be used to as part of the analysis to determine the targeted notifications/content.
  • This type of micro-targeting has not been previously performed because the specific real-world behaviors captured via the loT system described herein were not previously available.
  • current targeted advertising is based on a user's browsing history and/or purchase history, but no data is available related to a user's real-world activity (e.g., such as gardening, cooking, and home maintenance).
  • Such data can be particularly beneficial when providing targeted information to end users as described herein because it is based on a user's actual activity related to particular products and/or services.
  • the low power microcontroller 200 of each loT device 101 and the low power logic/microcontroller 301 of the loT hub 1 10 include a secure key store for storing encryption keys used by the embodiments described below (see, e.g., Figures 13-15 and associated text).
  • the keys may be secured in a subscriber identity module (SIM) as discussed below.
  • SIM subscriber identity module
  • Figure 13 illustrates a high level architecture which uses public key infrastructure (PKI) techniques and/or symmetric key exchange/encryption techniques to encrypt communications between the loT Service 120, the loT hub 1 10 and the loT devices 101 -102.
  • PKI public key infrastructure
  • Embodiments which use public/private key pairs will first be described, followed by embodiments which use symmetric key exchange/encryption techniques.
  • a unique public/private key pair is associated with each loT device 101 -102, each loT hub 1 10 and the loT service 120.
  • a new loT hub 1 10 when a new loT hub 1 10 is set up, its public key is provided to the loT service 120 and when a new loT device 101 is set up, it's public key is provided to both the loT hub 1 10 and the loT service 120.
  • Various techniques for securely exchanging the public keys between devices are described below.
  • all public keys are signed by a master key known to all of the receiving devices (i.e., a form of certificate) so that any receiving device can verify the validity of the public keys by validating the signatures.
  • a master key known to all of the receiving devices (i.e., a form of certificate) so that any receiving device can verify the validity of the public keys by validating the signatures.
  • each loT device 101 , 102 includes a secure key storage 1301 , 1303, respectively, for securely storing each device's private key.
  • Security logic 1302, 1304 then utilizes the securely stored private keys to perform the encryption/decryption operations described herein.
  • the loT hub 1 10 includes a secure storage 131 1 for storing the loT hub private key and the public keys of the loT devices 101 -102 and the loT service 120; as well as security logic 1312 for using the keys to perform encryption/decryption operations.
  • the loT service 120 may include a secure storage 1321 for security storing its own private key, the public keys of various loT devices and loT hubs, and a security logic 1313 for using the keys to encrypt/decrypt communication with loT hubs and devices.
  • a secure storage 1321 for security storing its own private key, the public keys of various loT devices and loT hubs, and a security logic 1313 for using the keys to encrypt/decrypt communication with loT hubs and devices.
  • the loT hub 1 10 when the loT hub 1 10 receives a public key certificate from an loT device it can verify it (e.g., by validating the signature using the master key as described above), and then extract the public key from within it and store that public key in its secure key store 131 1 .
  • the security logic 1313 encrypts the data/command using the public key of the loT device 101 to generate an encrypted loT device packet. In one embodiment, it then encrypts the loT device packet using the public key of the loT hub 1 10 to generate an loT hub packet and transmits the loT hub packet to the loT hub 1 10.
  • the service 120 signs the encrypted message with its private key or the master key mentioned above so that the device 101 can verify it is receiving an unaltered message from a trusted source.
  • the device 101 may then validate the signature using the public key corresponding to the private key and/or the master key.
  • symmetric key exchange/encryption techniques may be used instead of public/private key encryption.
  • the devices may each be provided with a copy of the same symmetric key to be used for encryption and to validate signatures.
  • AES Advanced Encryption Standard
  • each device 101 enters into a secure key exchange protocol to exchange a symmetric key with the loT hub 1 10.
  • a secure key provisioning protocol such as the Dynamic Symmetric Key Provisioning Protocol (DSKPP) may be used to exchange the keys over a secure communication channel (see, e.g., Request for Comments (RFC) 6063).
  • RRC Request for Comments
  • the underlying principles of the invention are not limited to any particular key provisioning protocol.
  • the symmetric keys may be used by each device 101 and the loT hub 1 10 to encrypt communications.
  • the loT hub 1 10 and loT service 120 may perform a secure symmetric key exchange and then use the exchanged symmetric keys to encrypt communications.
  • a new symmetric key is exchanged periodically between the devices 101 and the hub 1 10 and between the hub 1 10 and the loT service 120.
  • a new symmetric key is exchanged with each new communication session between the devices 101 , the hub 1 10, and the service 120 (e.g., a new key is generated and securely exchanged for each communication session).
  • the service 120 could negotiate a session key with the hub security module 1312 and then the security module 1312 would negotiate a session key with each device 120. Messages from the service 120 would then be decrypted and verified in the hub security module 1312 before being re-encrypted for transmission to the device 101 .
  • a one-time (permanent) installation key may be negotiated between the device 101 and service 120 at installation time.
  • the service 120 could first encrypt/MAC with this device installation key, then encrypt/MAC that with the hub's session key.
  • the hub 1 10 would then verify and extract the encrypted device blob and send that to the device.
  • a counter mechanism is implemented to prevent replay attacks.
  • each successive communication from the device 101 to the hub 1 10 may be assigned a continually increasing counter value.
  • Both the hub 1 10 and device 101 will track this value and verify that the value is correct in each successive communication between the devices.
  • the same techniques may be implemented between the hub 1 10 and the service 120. Using a counter in this manner would make it more difficult to spoof the communication between each of the devices (because the counter value would be incorrect). However, even without this a shared installation key between the service and device would prevent network (hub) wide attacks to all devices.
  • the loT hub 1 10 when using public/private key encryption, uses its private key to decrypt the loT hub packet and generate the encrypted loT device packet, which it transmits to the associated loT device 101 .
  • the loT device 101 then uses its private key to decrypt the loT device packet to generate the
  • each device would encrypt and decrypt with the shared symmetric key. If either case, each transmitting device may also sign the message with its private key so that the receiving device can verify its authenticity.
  • a different set of keys may be used to encrypt communication from the loT device 101 to the loT hub 1 10 and to the loT service 120.
  • the security logic 1302 on the loT device 101 uses the public key of the loT hub 1 10 to encrypt data packets sent to the loT hub 1 10.
  • the security logic 1312 on the loT hub 1 10 may then decrypt the data packets using the loT hub's private key.
  • the security logic 1302 on the loT device 101 and/or the security logic 1312 on the loT hub 1 10 may encrypt data packets sent to the loT service 120 using the public key of the loT service 120 (which may then be decrypted by the security logic 1313 on the loT service 120 using the service's private key).
  • the device 101 and hub 1 10 may share a symmetric key while the hub and service 120 may share a different symmetric key.
  • data/command itself is not encrypted, but a key is used to generate a signature over the data/command (or other data structure). The recipient may then use its key to validate the signature.
  • the secure key storage on each loT device 101 is implemented using a programmable subscriber identity module (SIM) 1401 .
  • SIM subscriber identity module
  • the loT device 101 may initially be provided to the end user with an un-programmed SIM card 1401 seated within a SIM interface 1400 on the loT device 101 .
  • the user takes the programmable SIM card 1401 out of the SIM interface 500 and inserts it into a SIM programming interface 1402 on the loT hub 1 10.
  • Programming logic 1425 on the loT hub then securely programs the SIM card 1401 to register/pair the loT device 101 with the loT hub 1 10 and loT service 120.
  • a public/private key pair may be randomly generated by the programming logic 1425 and the public key of the pair may then be stored in the loT hub's secure storage device 41 1 while the private key may be stored within the programmable SIM 1401 .
  • the programming logic 1425 may store the public keys of the loT hub 1 10, the loT service 120, and/or any other loT devices 101 on the SIM card 1401 (to be used by the security logic 1302 on the loT device 101 to encrypt outgoing data).
  • the new loT device 101 may be provisioned with the loT Service 120 using the SIM as a secure identifier (e.g., using existing techniques for registering a device using a SIM). Following provisioning, both the loT hub 1 10 and the loT service 120 will securely store a copy of the loT device's public key to be used when encrypting communication with the loT device 101 .
  • the techniques described above with respect to Figure 14 provide enormous flexibility when providing new loT devices to end users. Rather than requiring a user to directly register each SIM with a particular service provider upon sale/purchase (as is currently done), the SIM may be programmed directly by the end user via the loT hub 1 10 and the results of the programming may be securely communicated to the loT service 120. Consequently, new loT devices 101 may be sold to end users from online or local retailers and later securely provisioned with the loT service 120.
  • SIM Subscriber Identity Module
  • the underlying principles of the invention are not limited to a "SIM" device. Rather, the underlying principles of the invention may be implemented using any type of device having secure storage for storing a set of encryption keys.
  • the embodiments above include a removable SIM device, in one embodiment, the SIM device is not removable but the loT device itself may be inserted within the programming interface 1402 of the loT hub 1 10.
  • the SIM is pre-programmed into the loT device 101 , prior to distribution to the end user.
  • various techniques described herein may be used to securely exchange encryption keys between the loT hub 1 10/loT service 120 and the new loT device 101 .
  • each loT device 101 or SIM 401 may be packaged with a barcode or QR code 1501 uniquely identifying the loT device 101 and/or SIM 1401 .
  • the barcode or QR code 1501 comprises an encoded representation of the public key for the loT device 101 or SIM 1401 .
  • the barcode or QR code 1501 may be used by the loT hub 1 10 and/or loT service 120 to identify or generate the public key (e.g., used as a pointer to the public key which is already stored in secure storage).
  • the barcode or QR code 1501 may be printed on a separate card (as shown in Figure 15A) or may be printed directly on the loT device itself.
  • the loT hub 1 10 is equipped with a barcode reader 206 for reading the barcode and providing the resulting data to the security logic 1312 on the loT hub 1 10 and/or the security logic 1313 on the loT service 120.
  • the security logic 1312 on the loT hub 1 10 may then store the public key for the loT device within its secure key storage 131 1 and the security logic 1313 on the loT service 120 may store the public key within its secure storage 1321 (to be used for subsequent encrypted communication).
  • the data contained in the barcode or QR code 1501 may also be captured via a user device 135 (e.g., such as an iPhone or Android device) with an installed loT app or browser-based applet designed by the loT service provider.
  • a user device 135 e.g., such as an iPhone or Android device
  • the barcode data may be securely communicated to the loT service 120 over a secure connection (e.g., such as a secure sockets layer (SSL) connection).
  • SSL secure sockets layer
  • the barcode data may also be provided from the client device 135 to the loT hub 1 10 over a secure local connection (e.g., over a local WiFi or Bluetooth LE connection).
  • the security logic 1302 on the loT device 101 and the security logic 1312 on the loT hub 1 10 may be implemented using hardware, software, firmware or any combination thereof.
  • the security logic 1302, 1312 is implemented within the chips used for establishing the local communication channel 130 between the loT device 101 and the loT hub 1 10 (e.g., the Bluetooth LE chip if the local channel 130 is Bluetooth LE).
  • the security logic 1302, 1312 is designed to establish a secure execution environment for executing certain types of program code. This may be implemented, for example, by using TrustZone technology (available on some ARM processors) and/or Trusted Execution Technology (designed by Intel).
  • TrustZone technology available on some ARM processors
  • Trusted Execution Technology designed by Intel.
  • the underlying principles of the invention are not limited to any particular type of secure execution technology.
  • the barcode or QR code 1501 may be used to pair each loT device 101 with the loT hub 1 10.
  • a pairing code embedded within the barcode or QR code 1501 may be provided to the loT hub 1 10 to pair the loT hub with the corresponding loT device.
  • Figure 15B illustrates one embodiment in which the barcode reader 206 on the loT hub 1 10 captures the barcode/QR code 1501 associated with the loT device 101 .
  • the barcode/QR code 1501 may be printed directly on the loT device 101 or may be printed on a separate card provided with the loT device 101 .
  • the barcode reader 206 reads the pairing code from the barcode/QR code 1501 and provides the pairing code to the local communication module 1580.
  • the local communication module 1580 is a Bluetooth LE chip and associated software, although the underlying principles of the invention are not limited to any particular protocol standard.
  • the pairing code is received, it is stored in a secure storage containing pairing data 1585 and the loT device 101 and loT hub 1 10 are automatically paired. Each time the loT hub is paired with a new loT device in this manner, the pairing data for that pairing is stored within the secure storage 1585.
  • the local communication module 1580 of the loT hub 1 10 may use the code as a key to encrypt communications over the local wireless channel with the loT device 101 .
  • the local communication module 1590 stores pairing data within a local secure storage device 1595 indicating the pairing with the loT hub.
  • the pairing data 1595 may include the pre-programmed pairing code identified in the barcode/QR code 1501 .
  • the pairing data 1595 may also include pairing data received from the local communication module 1580 on the loT hub 1 10 required for establishing a secure local communication channel (e.g., an additional key to encrypt communication with the loT hub 1 10).
  • the barcode/QR code 1501 may be used to perform local pairing in a far more secure manner than current wireless pairing protocols because the pairing code is not transmitted over the air.
  • the same barcode/QR code 1501 used for pairing may be used to identify encryption keys to build a secure connection from the loT device 101 to the loT hub 1 10 and from the loT hub 1 10 to the loT service 120.
  • FIG. 16 A method for programming a SIM card in accordance with one embodiment of the invention is illustrated in Figure 16. The method may be implemented within the system architecture described above, but is not limited to any particular system architecture.
  • a user receives a new loT device with a blank SIM card and, at 1602, the user inserts the blank SIM card into an loT hub.
  • the user programs the blank SIM card with a set of one or more encryption keys.
  • the loT hub may randomly generate a
  • a programmable device other than a "SIM" card may be used to perform the same functions as the SIM card in the method shown in Figure 16.
  • a user receives a new loT device to which an encryption key has been pre-assigned.
  • the key is securely provided to the loT hub.
  • this involves reading a barcode associated with the loT device to identify the public key of a public/private key pair assigned to the device.
  • the barcode may be read directly by the loT hub or captured via a mobile device via an app or bowser.
  • a secure communication channel such as a near field communication (NFC) channel or a secure WiFi channel may be established between the loT device and the loT hub to exchange the key. Regardless of how the key is transmitted, once received, it is stored in the secure keystore of the loT hub device.
  • NFC near field communication
  • WiFi secure WiFi
  • the loT hub may store and protect the key such as Secure Enclaves, Trusted Execution Technology (TXT), and/or Trustzone.
  • TXT Trusted Execution Technology
  • the key is securely transmitted to the loT service which stores the key in its own secure keystore. It may then use the key to encrypt communication with the loT device.
  • the exchange may be implemented using a certificate/signed key.
  • the hub 1 10 it is particularly important to prevent modification/addition/ removal of the stored keys.
  • FIG. 18 A method for securely communicating commands/data to an loT device using public/private keys is illustrated in Figure 18. The method may be implemented within the system architecture described above, but is not limited to any particular system architecture.
  • the loT service encrypts the data/commands using the loT device public key to create an loT device packet. It then encrypts the loT device packet using loT hub's public key to create the loT hub packet (e.g., creating an loT hub wrapper around the loT device packet).
  • the loT service transmits the loT hub packet to the loT hub.
  • the loT hub decrypts the loT hub packet using the loT hub's private key to generate the loT device packet.
  • a symmetric key exchange may be negotiated between each of the devices (e.g., each device and the hub and between the hub and the service). Once the key exchange is complete, each of the devices (e.g., each device and the hub and between the hub and the service). Once the key exchange is complete, each of the devices (e.g., each device and the hub and between the hub and the service). Once the key exchange is complete, each of the devices (e.g., each device and the hub and between the hub and the service). Once the key exchange is complete, each of the devices (e.g., each device and the hub and between the hub and the service). Once the key exchange is complete, each of the devices (e.g., each device and the hub and between the hub and the service). Once the key exchange is complete, each of the devices (e.g., each device and the hub and between the hub and the service). Once the key exchange is complete, each of the devices (e.g., each device and the hub and between the hub and the service). Once the key exchange is complete, each of the
  • transmitting device encrypts and/or signs each transmission using the symmetric key before transmitting data to the receiving device.
  • Embodiments of the invention may include various steps, which have been described above.
  • the steps may be embodied in machine-executable instructions which may be used to cause a general-purpose or special-purpose processor to perform the steps.
  • these steps may be performed by specific hardware components that contain hardwired logic for performing the steps, or by any combination thereof
  • instructions may refer to specific configurations of hardware such as application specific integrated circuits (ASICs) configured to perform certain operations or having a predetermined functionality or software instructions stored in memory embodied in a non-transitory computer readable medium.
  • ASICs application specific integrated circuits
  • the techniques shown in the figures can be implemented using code and data stored and executed on one or more electronic devices (e.g., an end station, a network element, etc.).
  • Such electronic devices store and communicate (internally and/or with other electronic devices over a network) code and data using computer machine-readable media, such as non-transitory computer machine-readable storage media (e.g., magnetic disks; optical disks; random access memory; read only memory; flash memory devices; phase-change memory) and transitory computer machine-readable
  • non-transitory computer machine-readable storage media e.g., magnetic disks; optical disks; random access memory; read only memory; flash memory devices; phase-change memory
  • Such electronic devices typically include a set of one or more processors coupled to one or more other components, such as one or more storage devices (non-transitory machine- readable storage media), user input/output devices (e.g., a keyboard, a touchscreen, and/or a display), and network connections.
  • the coupling of the set of processors and other components is typically through one or more busses and bridges (also termed as bus controllers).
  • the storage device of a given electronic device typically stores code and/or data for execution on the set of one or more processors of that electronic device.
  • code and/or data for execution on the set of one or more processors of that electronic device.
  • one or more parts of an embodiment of the invention may be implemented using different combinations of software, firmware, and/or hardware.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computing Systems (AREA)
  • Automation & Control Theory (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Selective Calling Equipment (AREA)
  • Telephonic Communication Services (AREA)

Abstract

La présente invention concerne un concentrateur d'Internet des Objets (IdO) comprenant une interface réseau pour coupler le concentrateur IdO à un service IdO sur un réseau étendu (WAN), et au moins un dispositif IdO couplé de manière communicative au concentrateur IdO sur un canal de communication sans fil. Le dispositif IdO comprenant un boîtier émetteur infrarouge (IR) ou radiofréquence (RF) pour contrôler l'équipement électronique spécifié via une communication IR ou RF avec l'équipement électronique. Le dispositif IdO comprenant en outre au moins un capteur pour détecter des conditions courantes associées au fonctionnement de l'équipement électronique, le dispositif IdO transmettant une indication de la situation courante au concentrateur IdO sur le canal de communication sans fil. Le concentrateur IdO comprend une base de données de codes de commande à distance pour stocker des codes de commande à distance utilisables pour commander l'équipement électronique. Le concentrateur IdO comprend une logique de commande pour produire des instructions de commande à distance en utilisant les codes de commande à distance, les instructions de commande à distance sélectionnées par la logique de commande en réponse aux conditions courantes et entrées par un utilisateur final fournies par l'intermédiaire d'un dispositif d'utilisateur.
PCT/US2016/012021 2015-01-06 2016-01-04 Système et procédé de mise en œuvre d'applications de commande à distance de l'internet des objets (ido) WO2016111916A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201680010500.0A CN107251530B (zh) 2015-01-06 2016-01-04 用于实现物联网(IoT)远程控制应用的系统和方法
KR1020177021721A KR102524513B1 (ko) 2015-01-06 2016-01-04 사물 인터넷(IoT) 원격 제어 애플리케이션을 구현하기 위한 시스템 및 방법

Applications Claiming Priority (16)

Application Number Priority Date Filing Date Title
US14/590,719 2015-01-06
US14/590,700 2015-01-06
US14/590,686 2015-01-06
US14/590,700 US10816944B2 (en) 2015-01-06 2015-01-06 System and method for using data collected from internet-of-things (IoT) sensors to disable IoT-enabled home devices
US14/590,719 US9729340B2 (en) 2015-01-06 2015-01-06 System and method for notifying a user of conditions associated with an internet-of-things (IoT) hub
US14/590,686 US9933768B2 (en) 2015-01-06 2015-01-06 System and method for implementing internet of things (IOT) remote control applications
US14/590,649 2015-01-06
US14/590,799 2015-01-06
US14/590,708 2015-01-06
US14/590,765 2015-01-06
US14/590,765 US20160197769A1 (en) 2015-01-06 2015-01-06 System and method for filtering events at an iot hub
US14/590,663 US9774497B2 (en) 2015-01-06 2015-01-06 System and method for implementing internet of things (IOT) remote control applications
US14/590,649 US20160198536A1 (en) 2015-01-06 2015-01-06 Internet-of-things (iot) hub apparatus and method
US14/590,708 US9860681B2 (en) 2015-01-06 2015-01-06 System and method for selecting a cell carrier to connect an IOT hub
US14/590,663 2015-01-06
US14/590,799 US9774507B2 (en) 2015-01-06 2015-01-06 System and method for collecting and utilizing user behavior data within an IoT system

Publications (1)

Publication Number Publication Date
WO2016111916A1 true WO2016111916A1 (fr) 2016-07-14

Family

ID=56356332

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2016/012021 WO2016111916A1 (fr) 2015-01-06 2016-01-04 Système et procédé de mise en œuvre d'applications de commande à distance de l'internet des objets (ido)

Country Status (3)

Country Link
KR (1) KR102524513B1 (fr)
CN (1) CN107251530B (fr)
WO (1) WO2016111916A1 (fr)

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106899688A (zh) * 2017-03-15 2017-06-27 中国联合网络通信集团有限公司 一种物联网数据交互方法、物联网设备和物联网平台
KR20180079828A (ko) * 2017-01-02 2018-07-11 엘지전자 주식회사 네트워크용 허브 기기, 동작용 서브 기기 및 이를 이용한 커뮤니케이션 로봇
CN108694306A (zh) * 2017-03-29 2018-10-23 三星电子株式会社 管理和控制外部物联网设备的方法和支持其的电子设备
WO2019157433A1 (fr) * 2018-02-12 2019-08-15 Afero, Inc. Système et procédé de configuration sécurisée d'un nouveau dispositif avec des authentifiants réseau
US10697811B2 (en) 2016-10-31 2020-06-30 Nokia Technologies Oy Method, apparatus and computer program product for providing sensor data collection and sensor configuration
WO2021167141A1 (fr) * 2020-02-21 2021-08-26 엘지전자 주식회사 Dispositif et procédé d'affichage
CN114629516A (zh) * 2020-12-11 2022-06-14 辉达公司 用于手持式无线设备的射频功率适配
WO2023055120A1 (fr) * 2021-09-30 2023-04-06 Samsung Electronics Co., Ltd. Procédé et appareil pour commander un dispositif à distance dans un environnement d'internet des objets (ido)
EP4250680A1 (fr) * 2022-03-23 2023-09-27 Orange Procedes relatifs aux utilisations de codes de commande et a l association de terminaux, premier terminal, deuxieme terminal et dispositif de gestion de codes de commande
WO2024080542A1 (fr) * 2022-10-14 2024-04-18 삼성전자주식회사 Dispositif électronique et son procédé de commande

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107938257A (zh) * 2017-11-23 2018-04-20 广州市首试科技有限公司 一种具有蓝牙通信功能的洗衣机
JP7155605B2 (ja) * 2018-05-22 2022-10-19 富士フイルムビジネスイノベーション株式会社 情報処理装置及びプログラム
JP7106984B2 (ja) * 2018-05-22 2022-07-27 富士フイルムビジネスイノベーション株式会社 情報処理装置、情報処理システム及びプログラム
CN112313920B (zh) * 2018-07-03 2023-09-08 亚萨合莱有限公司 为多个iot设备提供连接性
KR20200084294A (ko) 2019-01-02 2020-07-10 (주)카네비컴 핫스팟 추출을 이용하여 코드 블록을 탐색하는 운용 서버 및 이를 포함하는 운용 플랫폼 시스템
CN109862104A (zh) * 2019-02-27 2019-06-07 江西昊潮科技有限公司 一种基于NB-IoT的智能商用洗衣系统及其使用方法
KR102389710B1 (ko) * 2019-12-19 2022-04-22 주식회사 오성전자 상황인지를 통한 레거시 가전 제어 방법 및 이를 지원하는 시스템
KR102367186B1 (ko) * 2020-01-17 2022-02-24 숭실대학교산학협력단 저전력 무선 리모콘을 이용한 IoT 장치 제어 방법, IoT 허브 및 IoT 시스템
CN114007198A (zh) * 2020-07-13 2022-02-01 深圳市利维坦技术有限公司 用于环境感知自配置物流硬件的系统和方法
KR102566016B1 (ko) * 2020-08-21 2023-08-09 조윤호 조명제어와 자가방범을 위한 기기 통합 제어 시스템
CN114172925B (zh) * 2020-09-10 2023-03-24 华为技术有限公司 配网方法及设备
CN112305962A (zh) * 2020-10-21 2021-02-02 麒麟软件有限公司 一种基于支持Trustzone的ARM平台的无线设备管控方法
CN112905416B (zh) * 2021-02-24 2023-08-15 河南永安电气消防检测有限公司 一种基于物联网的消防设施检测方法、装置及介质
KR102464535B1 (ko) * 2021-11-11 2022-11-09 주식회사 디나텍 세대 방송 및 음성 분석 기능이 있는 IoT Home Gateway 시스템 및 이를 이용한 방법
KR20240042909A (ko) * 2022-09-26 2024-04-02 삼성전자주식회사 외부 장치를 제어하기 위한 전자 장치 및 그의 제어 방법

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20010045819A1 (en) * 2000-03-15 2001-11-29 Harris Glen Mclean State-based remote control system
US20030066080A1 (en) * 2001-10-02 2003-04-03 John Kamieniecki Method and apparatus for automatic set-up of electronic devices
US20050096753A1 (en) * 2003-11-04 2005-05-05 Universal Electronics Inc. Home appliance control system and methods in a networked environment
US20050156730A1 (en) * 2004-01-08 2005-07-21 Maple Chase Company System and method for controlling ignition sources and ventilating systems during high carbon monoxide conditions
US20080250441A1 (en) * 2007-04-06 2008-10-09 Ajay Sharma Messaging for communications systems
US20110189956A1 (en) * 2010-02-02 2011-08-04 Gandolfo Pierre T Modular, reconfigurable and cognitive microsystem for the monitoring and remote control of smart communicating objects
US20130263802A1 (en) * 2012-04-10 2013-10-10 Hyundai Motor Company Engine cooling system, electronic thermostat control system and control method for the same
US20140376919A1 (en) * 2011-03-24 2014-12-25 Robert P. Stratton Remote Control System and Method

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7129855B2 (en) * 2003-09-26 2006-10-31 Openpeak Inc. Device control system, method, and apparatus
US20110287757A1 (en) * 2008-05-08 2011-11-24 Unify4Life Corporation Remote control system and method
KR101377065B1 (ko) * 2012-08-20 2014-03-24 (주)유타스 모바일 기기를 이용한 홈오토메이션 시스템
CN203910015U (zh) * 2014-05-05 2014-10-29 邯郸美的制冷设备有限公司 红外贴和红外控制系统
CN203851157U (zh) * 2014-05-30 2014-09-24 王诵捷 一种传统家电接入互联网的接口装置
CN104063227B (zh) * 2014-06-30 2017-04-05 合肥工业大学 一种基于物联网的指令学习方法

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20010045819A1 (en) * 2000-03-15 2001-11-29 Harris Glen Mclean State-based remote control system
US20030066080A1 (en) * 2001-10-02 2003-04-03 John Kamieniecki Method and apparatus for automatic set-up of electronic devices
US20050096753A1 (en) * 2003-11-04 2005-05-05 Universal Electronics Inc. Home appliance control system and methods in a networked environment
US20050156730A1 (en) * 2004-01-08 2005-07-21 Maple Chase Company System and method for controlling ignition sources and ventilating systems during high carbon monoxide conditions
US20080250441A1 (en) * 2007-04-06 2008-10-09 Ajay Sharma Messaging for communications systems
US20110189956A1 (en) * 2010-02-02 2011-08-04 Gandolfo Pierre T Modular, reconfigurable and cognitive microsystem for the monitoring and remote control of smart communicating objects
US20140376919A1 (en) * 2011-03-24 2014-12-25 Robert P. Stratton Remote Control System and Method
US20130263802A1 (en) * 2012-04-10 2013-10-10 Hyundai Motor Company Engine cooling system, electronic thermostat control system and control method for the same

Cited By (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10697811B2 (en) 2016-10-31 2020-06-30 Nokia Technologies Oy Method, apparatus and computer program product for providing sensor data collection and sensor configuration
US11585685B2 (en) 2016-10-31 2023-02-21 Nokia Technologies Oy Method, apparatus and computer program product for providing sensor data collection and sensor configuration
KR20180079828A (ko) * 2017-01-02 2018-07-11 엘지전자 주식회사 네트워크용 허브 기기, 동작용 서브 기기 및 이를 이용한 커뮤니케이션 로봇
KR101898589B1 (ko) * 2017-01-02 2018-09-13 엘지전자 주식회사 네트워크용 허브 기기, 동작용 서브 기기 및 이를 이용한 커뮤니케이션 로봇
CN106899688A (zh) * 2017-03-15 2017-06-27 中国联合网络通信集团有限公司 一种物联网数据交互方法、物联网设备和物联网平台
CN108694306A (zh) * 2017-03-29 2018-10-23 三星电子株式会社 管理和控制外部物联网设备的方法和支持其的电子设备
CN108694306B (zh) * 2017-03-29 2024-03-15 三星电子株式会社 管理和控制外部物联网设备的方法和支持其的电子设备
US11626974B2 (en) 2018-02-12 2023-04-11 Afero, Inc. System and method for securely configuring a new device with network credentials
WO2019157433A1 (fr) * 2018-02-12 2019-08-15 Afero, Inc. Système et procédé de configuration sécurisée d'un nouveau dispositif avec des authentifiants réseau
US10587400B2 (en) 2018-02-12 2020-03-10 Afero, Inc. System and method for securely configuring a new device with network credentials
WO2021167141A1 (fr) * 2020-02-21 2021-08-26 엘지전자 주식회사 Dispositif et procédé d'affichage
CN114629516A (zh) * 2020-12-11 2022-06-14 辉达公司 用于手持式无线设备的射频功率适配
WO2023055120A1 (fr) * 2021-09-30 2023-04-06 Samsung Electronics Co., Ltd. Procédé et appareil pour commander un dispositif à distance dans un environnement d'internet des objets (ido)
EP4250680A1 (fr) * 2022-03-23 2023-09-27 Orange Procedes relatifs aux utilisations de codes de commande et a l association de terminaux, premier terminal, deuxieme terminal et dispositif de gestion de codes de commande
FR3133963A1 (fr) * 2022-03-23 2023-09-29 Orange procédés relatifs aux utilisations de codes de commande et à l’association de terminaux, premier terminal, deuxième terminal et dispositif de gestion de codes de commande
WO2024080542A1 (fr) * 2022-10-14 2024-04-18 삼성전자주식회사 Dispositif électronique et son procédé de commande

Also Published As

Publication number Publication date
CN107251530B (zh) 2021-07-06
KR20170102937A (ko) 2017-09-12
KR102524513B1 (ko) 2023-04-20
CN107251530A (zh) 2017-10-13

Similar Documents

Publication Publication Date Title
US9774497B2 (en) System and method for implementing internet of things (IOT) remote control applications
US10816944B2 (en) System and method for using data collected from internet-of-things (IoT) sensors to disable IoT-enabled home devices
US9774507B2 (en) System and method for collecting and utilizing user behavior data within an IoT system
US9729340B2 (en) System and method for notifying a user of conditions associated with an internet-of-things (IoT) hub
US9933768B2 (en) System and method for implementing internet of things (IOT) remote control applications
US9860681B2 (en) System and method for selecting a cell carrier to connect an IOT hub
KR102524513B1 (ko) 사물 인터넷(IoT) 원격 제어 애플리케이션을 구현하기 위한 시스템 및 방법
US20160198536A1 (en) Internet-of-things (iot) hub apparatus and method
US20160197769A1 (en) System and method for filtering events at an iot hub
US10798523B2 (en) System and method for accurately sensing user location in an IoT system
US10420151B2 (en) Apparatus and method for intermediary device data collection
US9704318B2 (en) System and method for accurately sensing user location in an IoT system
US9717012B2 (en) Internet of things (IOT) automotive device, system, and method
US10171462B2 (en) System and method for secure internet of things (IOT) device provisioning
US10260765B2 (en) Smart register apparatus and method
US20180048710A1 (en) Internet of things (iot) storage device, system and method
WO2018075427A1 (fr) Système de l'internet des objets (iot) et procédé de sélection d'un canal de communication secondaire
WO2016161027A1 (fr) Système et procédé pour authentification automatique de réseau sans fil
US20160323156A1 (en) System and method for performing wireless spectrum analysis and configuring wireless networks using an internet of things (iot) system
US10004183B2 (en) System and method for an internet of things (IoT) moisture sensor
WO2017106224A1 (fr) Système et procédé d'approvisionnement sécurisé d'un dispositif d'internet des objets (iot)
US20160349127A1 (en) System and method for using internet of things (iot) devices to capture and play back a massage
CN107430499B (zh) 在IoT系统中精确地感测用户位置的系统和方法

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: 16735249

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20177021721

Country of ref document: KR

Kind code of ref document: A

122 Ep: pct application non-entry in european phase

Ref document number: 16735249

Country of ref document: EP

Kind code of ref document: A1