WO2016111916A1

WO2016111916A1 - System and method for implementing internet of things (iot) remote control applications

Info

Publication number: WO2016111916A1
Application number: PCT/US2016/012021
Authority: WO
Inventors: Joe BRITT; Justin Lee; Shin MATSUMURA; Houman FOROOD; Scott Zimmerman; Phillip Myles; Sean ZAWICKI; Daisuke KUTAMI
Original assignee: Afero, Inc.
Priority date: 2015-01-06
Filing date: 2016-01-04
Publication date: 2016-07-14
Also published as: CN107251530A; KR102524513B1; CN107251530B; KR20170102937A

Abstract

An Internet of Things (loT) hub comprising a network interface to couple the loT hub to an loT service over a wide area network (WAN), and at least one loT device communicatively coupled to the loT hub over a wireless communication channel. The loT device comprises an infrared (IR) or radio frequency (RF) blaster to control specified electronics equipment via IR or RF communication with the electronics equipment. The loT device comprises at least one sensor to detect current conditions associated with the operation of the electronics equipment, which are transmitted to the loT hub over the wireless communication channel. The loT hub comprises a remote control code database to store remote control codes usable to control the electronics equipment. The loT hub includes control logic to generate remote control commands using the remote control codes, in response to the current conditions and input from an end user provided via a user device.

Description

SYSTEM AND METHOD FOR IMPLEMENTING INTERNET

OF THINGS (loT) REMOTE CONTROL APPLICATIONS

BACKGROUND

Field of the Invention

[0001] 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.

Description of the Related Art

[0002] 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.

[0003] loT development and adoption has been slow due to issues related to connectivity, power, and a lack of standardization. For example, 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. 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. As a result, 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).

BRIEF DESCRIPTION OF THE DRAWINGS

[0004] A better understanding of the present invention can be obtained from the following detailed description in conjunction with the following drawings, in which:

[0005] FIGS. 1 A-B illustrates different embodiments of an loT system architecture;

[0006] FIG. 2 illustrates an loT device in accordance with one embodiment of the invention; [0007] FIG. 3 illustrates an loT hub in accordance with one embodiment of the invention;

[0008] FIG. 4A-B illustrate embodiments of the invention for controlling and collecting data from loT devices, and generating notifications;

[0009] FIG. 5 illustrates embodiments of the invention for collecting data from loT devices and generating notifications from an loT hub and/or loT service;

[0010] FIG. 6 illustrates embodiments of the invention for detecting loss of hub connectivity and notifying a user;

[0011] FIGS. 7A-C illustrate different embodiments of a miniature loT hub device with LED lights and USB ports;

[0012] FIG. 8 illustrates a method for controlling electronics and other equipment with loT devices;

[0013] FIG. 9 illustrates one embodiment of an loT hub for selecting between different cell carriers;

[0014] FIG. 10 illustrates one embodiment of a method for selecting between different cell carriers;

[0015] FIG. 11 illustrates one embodiment of an loT hub filtering events from loT devices;

[0016] FIG. 12 illustrates one embodiment of an loT hub collecting data related to user behavior within an loT system;

[0017] FIG. 13 illustrates a high level view of one embodiment of a security architecture;

[0018] FIG. 14 illustrates one embodiment of an architecture in which a subscriber identity module (SIM) is used to store keys on loT devices;

[0019] FIG. 15A illustrates one embodiment in which loT devices are registered using barcodes or QR codes;

[0020] FIG. 15B illustrates one embodiment in which pairing is performed using barcodes or QR codes;

[0021] FIG. 16 illustrates one embodiment of a method for programming a SIM using an loT hub;

[0022] FIG. 17 illustrates one embodiment of a method for registering an loT device with an loT hub and loT service; and

[0023] FIG. 18 illustrates one embodiment of a method for encrypting data to be transmitted to an loT device. DETAILED DESCRIPTION

[0024] In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the invention described below. It will be apparent, however, to one skilled in the art that the embodiments of the invention may be practiced without some of these specific details. In other instances, well-known structures and devices are shown in block diagram form to avoid obscuring the underlying principles of the embodiments of the invention.

[0025] 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. In particular, one embodiment includes 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. In addition, one embodiment includes an loT service through which the loT hubs and connected loT devices may be accessed and managed as described below. In addition, one embodiment of 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.

[0026] Figure 1 A illustrates an overview of an architectural platform on which embodiments of the invention may be implemented. In particular, 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

communicatively coupled to an loT service 120 over the Internet 220. Each of the loT devices 101 -105 may initially be paired to the loT hub 1 10 (e.g., using the pairing techniques described below) in order to enable each of the local communication channels 130. In one embodiment, the loT service 120 includes an end user database 122 for maintaining user account information and data collected from each user's loT devices. For example, if 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). [0027] 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. In one embodiment described 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.

[0028] In one embodiment, 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. Alternatively, or in addition, 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). Of course, it should be noted that the underlying principles of the invention are not limited to any particular type of communication channel or protocol.

[0029] In one embodiment, the loT devices 101 -105 are ultra low-power devices capable of operating for extended periods of time on battery power (e.g., years). To conserve power, the local communication channels 130 may be implemented using a low-power wireless communication technology such as Bluetooth Low Energy (LE). In this embodiment, each of the loT devices 101 -105 and the loT hub 1 10 are equipped with Bluetooth LE radios and protocol stacks.

[0030] As mentioned, in one embodiment, 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. In one embodiment, the app or web application may be designed by the operator of a Website 130 to provide loT functionality to its user base. As illustrated, the Website may maintain a user database 131 containing account records related to each user.

[0031] Figure 1 B illustrates additional connection options for a plurality of loT hubs 1 10-1 1 1 , 190 In this embodiment 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. As indicated, if a user has multiple hubs 1 10, 1 1 1 they may be connected via a local communication channel (e.g., Wifi, Ethernet, Power Line Networking, etc). In one embodiment, 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). Alternatively, or in addition, 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 ). For example, the master loT hub 1 10 may be the only loT hub to establish a direct connection to the loT service 120. In one embodiment, 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. In this role, 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).

[0032] Regardless of how the loT hubs 1 10-1 1 1 are connected, in one embodiment, 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).

[0033] In this embodiment, 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). In addition, to the loT hubs 1 10-1 1 1 , 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.

[0034] Figure 1 B also shows an loT hub 190 installed at a second user premises 181 . A virtually unlimited number of such loT hubs 190 may be installed and configured to collect data from loT devices 191 -192 at user premises around the world. In one embodiment, the two user premises 180-181 may be configured for the same user. For example, one user premises 180 may be the user's primary home and the other user premises 181 may be the user's vacation home. In such a case, the loT service 120 will logically associate the loT hubs 1 10-1 1 1 , 190 with the user and combine all of the attached loT devices 101 -105, 191 -192 under a single comprehensive user interface, accessible via a user device with the installed app 135 (and/or a browser-based interface). [0035] As illustrated in Figure 2, 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. In one embodiment, 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. Moreover, 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.

[0036] As illustrated, 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 . In one embodiment, 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. As mentioned, in one embodiment, the

communication protocol stack 201 comprises a Bluetooth LE protocol stack. In this embodiment, Bluetooth LE radio and antenna 207 may be integrated within the low power microcontroller 200. However, the underlying principles of the invention are not limited to any particular communication protocol.

[0037] 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

application code 203 and library code 202. In one embodiment, each of the input devices include an LED 209 to provide feedback to the end user.

[0038] In addition, the illustrated embodiment includes a battery 208 for supplying power to the low power microcontroller. In one embodiment, a non-chargeable coin cell battery is used. However, in an alternate embodiment, an integrated rechargeable battery may be used (e.g., rechargeable by connecting the loT device to an AC power supply (not shown)).

[0039] A speaker 205 is also provided for generating audio. In one embodiment, 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. Alternatively, 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.

[0040] In one embodiment, 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. For example, 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. Of course, 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. In fact, given the highly programmable nature of the low power microcontroller 200 equipped with the library code 202, 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.

[0041] In one embodiment, the low power microcontroller 200 also includes a secure key store for storing encryption keys for encrypting communications and/or generating signatures. Alternatively, the keys may be secured in a subscriber identity module (SIM).

[0042] 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. In one embodiment, 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. In particular, in one embodiment, 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. Because of the energy transfer, 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. [0043] As illustrated in Figure 3, 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.

Alternatively, as mentioned above, 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. In one embodiment, 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).

[0044] A local communication interface 303 and antenna 31 1 establishes local communication channels with each of the loT devices 101 -105. As mentioned above, in one embodiment, the local communication interface 303/antenna 31 1 implements the Bluetooth LE standard. However, 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. Although illustrated as separate units in Figure 3, the WAN interface 302 and/or local communication interface 303 may be embedded within the same chip as the hardware logic 301 .

[0045] In one embodiment, 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. In addition, device pairing program code and data 306 may be stored in the memory to allow the loT hub to pair with new loT devices. In one embodiment, each new loT device 101 -105 is assigned a unique code which is communicated to the loT hub 1 10 during the pairing process. For example, 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

communication channel 130. In an alternate embodiment, 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.

[0046] In one embodiment, once the unique ID has been communicated, 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.

[0047] In one embodiment, 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. In particular, in addition to the loT hub 1 10, developers may be provided with a software development kit (SDK) to update the program code and data 305 executed within the hub 1 10. In addition, for loT devices 101 , 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 . In one embodiment, the SDK includes a graphical design interface in which the developer needs only to specify input and outputs for the loT device. All of the networking code, including the communication stack 201 that allows the loT device 101 to connect to the hub 1 10 and the service 120, is already in place for the developer. In addition, in one embodiment, the SDK also includes a library code base to facilitate the design of apps for mobile devices (e.g., iPhone and Android devices). In addition, in one embodiment, 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.

[0048] In one embodiment, the loT hub 1 10 manages a continuous bi-directional stream of data between the loT devices 101 -105 and the loT service 120. In

circumstances where updates to/from the loT devices 101 -105 are required in real time (e.g., where a user needs to view the current status of security devices or environmental readings), 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.

[0049] In one embodiment, both the loT hub 1 10 and the loT devices 101 -105 are automatically upgradeable over the network. In particular, when 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. Similarly, when 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).

[0050] In one embodiment, the loT hub 1 10 is powered via A/C power. In particular, 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.

[0051] Figure 4A illustrates one embodiment of the invention for performing universal remote control operations using the loT system. In particular, in this embodiment, 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

conditioners/heaters 430, lighting systems 431 , and audiovisual equipment 432 (to name just a few). In the embodiment shown in Figure 4A, 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.

[0052] For example, 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. In this embodiment, 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). In one embodiment, 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

temperature, then the control logic 412 may transmit a command to the air

conditioner/heater via the IR/RF blaster 401 to increase the temperature (e.g., either by turning off the air conditioner or turning on the heater). The command may include the necessary remote control code stored in a database 413 on the loT hub 1 10.

Alternatively, or in addition, 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.

[0053] loT device 102 in the illustrated example is used to control lighting 431 . In particular, 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. In response, 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).

[0054] loT device 103 in the illustrated example is configured to control audiovisual equipment 432 (e.g., a television, A/V receiver, cable/satellite receiver, AppleTV™, 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). Alternatively, 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. Once again, in response to user input via the user device 135, the control logic 412 may transmit commands to the audiovisual equipment via the IR blaster 403 of the loT device 103.

[0055] It should be noted that the foregoing are merely illustrative examples of one embodiment of the invention. The underlying principles of the invention are not limited to any particular type of sensors or equipment to be controlled by loT devices.

[0056] In an embodiment in which the loT devices 101 -103 are coupled to the loT hub 1 10 via a Bluetooth LE connection, the sensor data and commands are sent over the Bluetooth LE channel. However, the underlying principles of the invention are not limited to Bluetooth LE or any other communication standard.

[0057] In one embodiment, the 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. As illustrated in Figure 4B, 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).

[0058] In addition, in one embodiment, 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. For example, if control codes for the original remote control provided with the air conditioner 430 is not included in the remote control database, the user 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). Once the remote control codes are learned they 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).

[0059] In one embodiment, 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. 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). In contrast, 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.

[0060] In addition to providing general control functions as described, one

embodiment of the 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. The

notifications, which may be text messages and/or app-specific notifications, may then be displayed on the display of the user's mobile device 135. For example, if the user's air conditioner has been on for an extended period of time but the temperature has not changed, the loT hub 1 10 and/or loT service 120 may send the user a notification that the air conditioner is not functioning properly. If 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.

[0061] Once the user receives a notification, he/she may remotely control the electronics equipment 430-432 via the app or browser on the user device 135. In one embodiment, 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. Upon receiving a notification, the user may open the graphical remote control and turn off or adjust the various different pieces of equipment. If connected via the loT service 120, 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. Alternatively, the user input may be sent directly to the loT hub 1 10 from the user device 135.

[0062] In one embodiment, 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. In addition to maintaining a desired temperature, brightness level, and volume level as described above, 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.

[0063] Figure 5 illustrates additional embodiments of loT devices 104-105 equipped with sensors 503-504 for monitoring electronic equipment 530-531 . In particular, 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. In one embodiment, 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. In one

embodiment, 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).

[0064] In addition, in one embodiment, 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). In one embodiment, the control logic 501 comprises a switch to cut off electricity or gas to the stove 530. However, in other embodiments, the control logic 501 may be integrated within the stove itself.

[0065] Figure 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. Another sensor that may be used is an audio sensor (e.g., microphone and logic) for detecting an ambient volume level. As with the other embodiments described above, 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). Although not shown in Figure 5, 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.

[0066] In one embodiment, 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. Alternatively, 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.

[0067] In one embodiment, 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. In particular, in one embodiment, 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

notification to a data processing device 135 of a user responsive to the connection monitoring logic detecting that the first communication channel has become inoperative.

[0068] The user may then take steps to determine the cause of the connection problem. In an embodiment in which the loT hub is connected via the cellular network or WiFi, the user may simply need to reboot the loT hub device 1 10. In one

embodiment, if the connection monitoring and notification logic 600 has not received a communication from the loT hub for a specified period of time, it 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.

[0069] In an embodiment in which the loT hub is connected via both the cellular network and a broadband connection in the user's home, 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.

[0070] One embodiment of the loT hub 1 10 is implemented with an extremely compact form factor (e.g., the size of a cell phone charger). For example, 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.

[0071] Figures 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. In this manner, the loT hub 1 10 may be strategically positioned for ideal reception anywhere in the user's home where a power outlet exists. In one embodiment, the loT hub 1 10 includes a transformer for transforming the high voltage A/C input into a lower voltage D/C signal. Although having a small form factor, in one embodiment, 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. For example, although not explicitly shown in Figures 7A-C, in one embodiment, the loT hub 1 10 may include multiple communication interfaces (e.g., antennas and software) for communicating with the loT devices and loT service. In one embodiment, 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.

[0072] In addition, 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. Thus, 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.

[0073] In one embodiment, 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. In addition, in one embodiment, 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.

[0074] Once programmed, LEDs 701 may be turned on/off by the loT hub's integrated low power uC 200. In one embodiment, 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. In addition, in one embodiment, 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). Of course, the underlying principles of the invention are not limited to an loT hub 1 10 with integrated USB chargers.

[0075] A method in accordance with one embodiment of the invention is illustrated in Figure 8. At 801 , loT devices are positioned/configured on or near equipment to be controlled. As mentioned, in one embodiment, the loT devices are equipped with double-sided tape to allow the user to easily affix the loT devices to various types of equipment. Alternatively, or in addition, 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. In addition, some loT devices may include magnetic material to allow the loT devices to be affixed to a metal surface.

[0076] Once the loT devices are affixed in position, they may be programmed at 802 via the user device 135 and loT hub 1 10. For example, 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. Once 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). Once the correct equipment is selected, 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. In addition, as mentioned above, various automatic control functions may be implemented by the loT hub.

[0077] In one embodiment of the invention, 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. For example, in the United States 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.

[0078] As illustrated in Figure 9, in one embodiment of the invention, the loT hub 901 includes cellular carrier selection logic 901 for selecting between two or more available cell carriers 915-916. In one embodiment, 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.

[0079] Various different types of selection rules 918 may be implemented. By way of example, if the loT service 120 has a more beneficial agreement with a first cell carrier 915 (e.g., a lower agreed-upon rate/cost 912) compared with a second cell carrier 916, then 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).

[0080] In one embodiment, 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.

[0081] Similarly, the cell carrier selection logic 901 may evaluate

reliability/performance data 913 of each of the cell carriers 915-916 when making a decision. For example, if the first cell carrier 915 is known to be unreliable in a particular region and/or provides significantly lower performance than the second cell carrier 916 (e.g., a reduced data rate), then the cell carrier selection logic 901 may select the second cell carrier (notwithstanding the more beneficial agreement with the first cell carrier). In one embodiment, 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. For example, 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.

[0082] In one embodiment, 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).

[0083] In one embodiment, 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). In one embodiment, a single SIM 903 (or other authentication device) may be provisioned for multiple cell carriers 915-916. Thus, after selecting a first cell carrier 915 (e.g., based on the selection rules 918 and other variables), the loT hub 1 10 may still fall back to second cell carrier 916 if the first cell carrier 915 is unavailable. Similarly, 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.

[0084] Once the loT hub 1 10 is provisioned for the multiple carriers 915-916, it 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.

[0085] 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.

[0086] At 1001 , 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). At 1002, 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.

[0087] At 1003, 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

subsequently changed in response to changes in conditions and/or new/updated rules sent from the loT service. At 1004, 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.

[0088] As illustrated in Figure 11 , in one embodiment, 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. By way of example and not limitation, 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.

[0089] In one embodiment, 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). For example, 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.

[0090] In some cases, 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. For example, 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.

Consequently, in order to reduce the number of events transmitted over the cellular carrier's network (or via the user's Internet connection), 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. In one embodiment, each event 1 101 , 1 102-N is assigned an identification code indicating an event type. Based on a set of filtering rules 1 1 1 1 provided by the loT service 120 and/or the end user 1 1 15 (e.g., configured via an app/browser) 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.

[0091] As mentioned, 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

notifications over the Internet 220 to the user's device. For example, if a temperature sensor is above a specified threshold, the loT service 120 may transmit a notification to the end user's device informing the user about the potential problem. In addition, in some instances, 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).

[0092] In one embodiment, the external services 1 120-1 122 and loT service 120 utilize an application programming interface (API) exposed by the loT hub 1 10. For example, a particular service may register via the API to receive a particular set of events. Because 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.

Depending on the configuration, 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.

[0093] In one embodiment, 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). In this embodiment, 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

(potentially filtered by an loT service filter) and forwarded to the external services 1 120- 1 122 and/or the end user's devices. The 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).

[0094] The techniques for filtering events on the loT hub 1 10 and/or loT service 120 as described above is beneficial because it reduces a significant amount of

unnecessary traffic over the cell carrier's network and/or the user's/service's Internet connection. These embodiments may be particularly beneficial for homes which are fully implemented with a large number of loT devices (and which therefore general a large number of events).

[0095] One embodiment of the invention collects user behavior data related to each user's interaction with the various loT devices and responsively provides targeted content updates uniquely tailored to the interests of each user. Figure 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.

[0096] In one embodiment, user behavior data collection logic 1200 executed on the loT hub 1 10 monitors and collects the information viewed by each user (e.g.,

information provided by the various loT devices 101 -102) as well as the loT devices controlled by each user. For example, 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.

[0097] 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. For example, in one embodiment, 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. For example, 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. In one embodiment, 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. In one embodiment, 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.

[0098] In one embodiment, user behavior data is also collected directly from the loT Service 120 or one of the External Services 1 120-1 122. For example, 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. [0099] 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. For example, 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.

[00100] In one embodiment, 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). Alternatively, the keys may be secured in a subscriber identity module (SIM) as discussed below.

[00101] 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.

[00102] Embodiments which use public/private key pairs will first be described, followed by embodiments which use symmetric key exchange/encryption techniques. In particular, in an embodiment which uses PKI, a unique public/private key pair is associated with each loT device 101 -102, each loT hub 1 10 and the loT service 120. In one embodiment, 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. In one embodiment, 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. Thus, these certificates would be exchanged rather than merely exchanging the raw public keys.

[00103] As illustrated, in one embodiment, 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. Similarly, 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. Finally, 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. In one embodiment, 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 .

[00104] By way of example, in one embodiment, when the loT service 120 needs to transmit a command or data to an loT device 101 (e.g., a command to unlock a door, a request to read a sensor, data to be processed/displayed by the loT device, etc) 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. In one embodiment, 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. As mentioned above, symmetric key exchange/encryption techniques may be used instead of public/private key encryption. In these embodiments, rather than privately storing one key and providing a corresponding public key to other devices, the devices may each be provided with a copy of the same symmetric key to be used for encryption and to validate signatures. One example of a symmetric key algorithm is the Advanced Encryption Standard (AES), although the underlying principles of the invention are not limited to any type of specific symmetric keys.

[00105] Using a symmetric key implementation, 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). However, the underlying principles of the invention are not limited to any particular key provisioning protocol.

[00106] Once the symmetric keys have been exchanged, they may be used by each device 101 and the loT hub 1 10 to encrypt communications. Similarly, 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. In one embodiment 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. In one embodiment, 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). In one embodiment, if the security module 1312 in the loT hub is trusted, 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 .

[00107] In one embodiment, to prevent a compromise on the hub security module 1312 a one-time (permanent) installation key may be negotiated between the device 101 and service 120 at installation time. When sending a message to a device 101 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.

[00108] In one embodiment of the invention, a counter mechanism is implemented to prevent replay attacks. For example, each successive communication from the device 101 to the hub 1 10 (or vice versa) 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.

[00109] In one embodiment, when using public/private key encryption, the loT hub 1 10 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

command/data originated from the loT service 120. It may then process the data and/or execute the command. Using symmetric encryption, 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.

[00110] 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. For example, using a public/private key arrangement, in one embodiment, 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. Similarly, 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). Using symmetric keys, the device 101 and hub 1 10 may share a symmetric key while the hub and service 120 may share a different symmetric key.

[00111] While certain specific details are set forth above in the description above, it should be noted that the underlying principles of the invention may be implemented using various different encryption techniques. For example, while some embodiments discussed above use asymmetric public/private key pairs, an alternate embodiment may use symmetric keys securely exchanged between the various loT devices 101 -102, loT hubs 1 10, and the loT service 120. Moreover, in some embodiments, the

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.

[00112] As illustrated in Figure 14, in one embodiment, the secure key storage on each loT device 101 is implemented using a programmable subscriber identity module (SIM) 1401 . In this embodiment, 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 . In order to program the SIM with a set of one or more encryption keys, 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. In one embodiment, 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 . In addition, 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). Once the SIM 1401 is programmed, 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 .

[00113] 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.

[00114] While the registration and encryption techniques are described above within the specific context of a 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. Moreover, while 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.

[00115] In one embodiment, rather than requiring the user to program the SIM (or other device), the SIM is pre-programmed into the loT device 101 , prior to distribution to the end user. In this embodiment, when the user sets up the loT device 101 , 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 .

[00116] For example, as illustrated in Figure 15A 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 . In one embodiment, the barcode or QR code 1501 comprises an encoded representation of the public key for the loT device 101 or SIM 1401 .

Alternatively, 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. Regardless of where the barcode is printed, in one embodiment, 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).

[00117] In one embodiment, 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. Once captured, 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). 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).

[00118] 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. For example, in one embodiment, 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). Regardless of the specific location of the security logic 1302, 1312, in one embodiment, 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). Of course, the underlying principles of the invention are not limited to any particular type of secure execution technology.

[00119] In one embodiment, the barcode or QR code 1501 may be used to pair each loT device 101 with the loT hub 1 10. For example, rather than using the standard wireless pairing process currently used to pair Bluetooth LE devices, 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.

[00120] 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 . As mentioned, 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 . In either case, 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. In one embodiment, 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. Once 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. In one embodiment, once the local communication module 1580 of the loT hub 1 10 receives the pairing code, it may use the code as a key to encrypt communications over the local wireless channel with the loT device 101 .

[00121] Similarly, on the loT device 101 side, 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).

[00122] Thus, 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. In addition, in one embodiment, 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.

[00123] 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.

[00124] At 1601 , 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. At 1603, the user programs the blank SIM card with a set of one or more encryption keys. For example, as mentioned above, in one embodiment, the loT hub may randomly generate a

public/private key pair and store the private key on the SIM card and the public key in its local secure storage. In addition, at 1604, at least the public key is transmitted to the loT service so that it may be used to identify the loT device and establish encrypted communication with the loT device. As mentioned above, in one embodiment, 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.

[00125] A method for integrating a new loT device into a network is illustrated in

Figure 17. The method may be implemented within the system architecture described above, but is not limited to any particular system architecture.

[00126] At 1701 , a user receives a new loT device to which an encryption key has been pre-assigned. At 1702, the key is securely provided to the loT hub. As mentioned above, in one embodiment, 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. In an alternate embodiment, 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. As mentioned above, various secure execution technologies may be used on the loT hub to store and protect the key such as Secure Enclaves, Trusted Execution Technology (TXT), and/or Trustzone. In addition, at 1703, 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. One again, the exchange may be implemented using a certificate/signed key. Within the hub 1 10 it is particularly important to prevent modification/addition/ removal of the stored keys.

[00127] 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.

[00128] At 1801 , 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). At 1802, the loT service transmits the loT hub packet to the loT hub. At 1803, the loT hub decrypts the loT hub packet using the loT hub's private key to generate the loT device packet. At 1804 it then transmits the loT device packet to the loT device which, at 1805, decrypts the loT device packet using the loT device private key to generate the data/commands. At 1806, the loT device processes the data/commands. [00129] In an embodiment which uses symmetric keys, 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

transmitting device encrypts and/or signs each transmission using the symmetric key before transmitting data to the receiving device.

[00130] 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. Alternatively, these steps may be performed by specific hardware components that contain hardwired logic for performing the steps, or by any

combination of programmed computer components and custom hardware components.

[00131] As described herein, 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. Thus, 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

communication media (e.g., electrical, optical, acoustical or other form of propagated signals - such as carrier waves, infrared signals, digital signals, etc.). In addition, 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 and signals carrying the network traffic

respectively represent one or more machine-readable storage media and machine- readable communication media. Thus, 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. Of course, one or more parts of an embodiment of the invention may be implemented using different combinations of software, firmware, and/or hardware.

[00132] Throughout this detailed description, for the purposes of explanation, numerous specific details were set forth in order to provide a thorough understanding of the present invention. It will be apparent, however, to one skilled in the art that the invention may be practiced without some of these specific details. In certain instances, well known structures and functions were not described in elaborate detail in order to avoid obscuring the subject matter of the present invention. Accordingly, the scope and spirit of the invention should be judged in terms of the claims which follow.

Claims

CLAIMS What is claimed is:

1 . A system comprising:

an Internet of Things (loT) hub comprising a network interface to couple the loT hub to an loT service over a wide area network (WAN), and

at least one loT device communicatively coupled to the loT hub over a wireless communication channel, the loT device comprising an infrared (IR) or radio frequency (RF) blaster to control specified electronics equipment via IR or RF communication with the electronics equipment, the loT device further comprising at least one sensor to detect current conditions associated with the operation of the electronics equipment, the loT device to transmit an indication of the current conditions to the loT hub over the wireless communication channel; and

the loT hub comprising a remote control code database to store remote control codes usable to control the electronics equipment, the loT hub further comprising control logic to generate remote control commands using the remote control codes, the remote control commands selected by the control logic in response to the current conditions and input from an end user provided via a user device, the loT hub to transmit the commands to the loT device over the wireless communication channel; and the loT device to responsively transmit the remote control commands to the electronics equipment to control the electronics equipment.

2. The system as in claim 1 wherein the electronics equipment comprises an air conditioner and/or heater, the sensor comprises temperature sensor, and the current conditions comprises a temperature.

3. The system as in claim 2 wherein the input from the end user provided by the user device comprises a desired temperature, wherein the control logic generates the remote control commands to turn on or off the air conditioner and/or heater to achieve the desired temperature.

4. The system as in claim 1 wherein the electronics equipment comprises audiovisual equipment, lights, a stove, a washer and/or a dryer.

5. The system as in claim 1 wherein the loT hub comprises a remote control code learning logic to retrieve remote control codes from a master control code database on the loT service responsive to the user entering information identifying the electronics equipment.

6. The system as in claim 5 wherein the remote control code learning logic is communicatively coupled to an IR/RF interface integrated on the loT hub, the remote control code learning logic to learn remote control codes directly from original remote controls designed for operation with the electronics equipment by capturing the remote control codes from the original remote controls via the IR/RF interface.

7. The system as in claim 6 wherein the remote control code learning logic is to store the captured remote control codes in the remote control code database on the loT hub.

8. The system as in claim 1 wherein the input from the user is provided to the loT hub through the loT service.

9. The system as in claim 1 wherein the wireless communication channel comprises a Bluetooth Low Energy (BTLE) communication channel.

10. The system as in claim 1 wherein the loT hub is communicatively coupled to the loT service over a cellular network connection coupling the loT hub to the WAN.

1 1 . The system as in claim 1 further comprising:

a plurality of additional loT devices communicatively coupled to the loT hub, each of the loT devices comprising an IR or RF blaster to control different types of electronics equipment via IR or RF communication with the electronics equipment, each loT device further comprising at least one sensor to detect current conditions associated with the operation of the different electronics equipment, each loT device to transmit an indication of the current conditions to the loT hub over the wireless communication channel.

12. A method comprising:

communicatively coupling an Internet of Things (loT) hub to an loT service over a wide area network (WAN), and communicatively coupling at least one loT device to the loT hub over a wireless communication channel, the loT device comprising an infrared (IR) or radio frequency (RF) blaster to control specified electronics equipment via IR or RF communication with the electronics equipment;

sensing current conditions with a sensor on the loT device, the current conditions associated with the operation of the electronics equipment;

transmitting the current conditions over the wireless communication channel from the loT device to the loT hub;

analyzing the current conditions in combination with user input to select remote control commands using the remote control codes at the loT hub,

transmitting the remote control commands from the loT hub to the loT device over the wireless communication channel, the loT device responsively transmitting the remote control commands to the electronics equipment to control the electronics equipment.

13. The method as in claim 12 wherein the electronics equipment comprises an air conditioner and/or heater, the sensor comprises temperature sensor, and the current conditions comprises a temperature.

14. The method as in claim 13 wherein the input from the end user provided by the user device comprises a desired temperature, wherein the control logic generates the remote control commands to turn on or off the air conditioner and/or heater to achieve the desired temperature.

15. The method as in claim 12 wherein the electronics equipment comprises audiovisual equipment, lights, a stove, a washer and/or a dryer.

16. The method as in claim 12 wherein the loT hub comprises a remote control code learning logic to retrieve remote control codes from a master control code database on the loT service responsive to the user entering information identifying the electronics equipment.

17. The method as in claim 16 wherein the remote control code learning logic is communicatively coupled to an IR/RF interface integrated on the loT hub, the remote control code learning logic to learn remote control codes directly from original remote controls designed for operation with the electronics equipment by capturing the remote control codes from the original remote controls via the IR/RF interface.

18. The method as in claim 17 wherein the remote control code learning logic is to store the captured remote control codes in the remote control code database on the loT hub.

19. The method as in claim 12 wherein the input from the user is provided to the loT hub through the loT service.

20. The method as in claim 12 wherein the wireless communication channel comprises a Bluetooth Low Energy (BTLE) communication channel.

21 . The method as in claim 12 wherein the loT hub is communicatively coupled to the loT service over a cellular network connection coupling the loT hub to the WAN.

22. The method as in claim 12 further comprising:

communicatively coupling a plurality of additional loT devices to the loT hub, each of the loT devices comprising an IR or RF blaster to control different types of electronics equipment via IR or RF communication with the electronics equipment, each loT device further comprising at least one sensor to detect current conditions associated with the operation of the different electronics equipment, each loT device to transmit an indication of the current conditions to the loT hub over the wireless communication channel.

23. A system comprising:

at least one loT device communicatively coupled to the loT hub over a wireless communication channel, the loT device comprising an infrared (IR) or radio frequency (RF) blaster to control environmental control equipment via IR or RF communication with the environmental control equipment, the loT device further comprising at least one sensor to measure current environmental conditions capable of being controlled by the environmental control equipment, the loT device to transmit an indication of the current conditions to the loT hub over the wireless communication channel; and

the loT hub comprising a remote control code database to store remote control codes usable to control the environmental control equipment, the loT hub further comprising control logic to generate remote control commands using the remote control codes, the remote control commands selected by the control logic in response to the current environmental conditions measured by the sensor and input from an end user provided via a user device indicating a desired environmental condition, the loT hub to transmit the commands to the loT device over the wireless communication channel; the loT device to responsively transmit the remote control commands to the environmental control equipment to attempt to control the environmental control equipment;

wherein the loT hub is configured to continually or periodically monitor the current environmental conditions measured by the sensor and wherein, if the desired environmental condition is not achieved after a specified period of time, then generate a notification from the loT hub indicating that the environmental control equipment may not be functioning properly.

24. The system as in claim 23 wherein the environmental control equipment comprises an air conditioner and/or heater, the sensor comprises temperature sensor, the current environmental conditions comprises a first temperature, and the desired environmental condition comprises a second temperature different from the first temperature.

25. The system as in claim 24 wherein the notification is sent from the loT hub to a data processing device of the user.

26. The system as in claim 25 wherein if the desired environmental condition is not achieved after the specified period of time, the loT hub is further configured to transmit one or more remote control commands to turn off the environmental control equipment.

27. The system as in claim 23 wherein the loT hub comprises a remote control code learning logic to retrieve remote control codes from a master control code database on the loT service responsive to the user entering information identifying the environmental control equipment .

28. The system as in claim 24 wherein the remote control code learning logic is communicatively coupled to an IR/RF interface integrated on the loT hub, the remote control code learning logic to learn remote control codes directly from original remote controls designed for operation with the environmental control equipment by capturing the remote control codes from the original remote controls via the IR/RF interface.

29. The system as in claim 28 wherein the remote control code learning logic is to store the captured remote control codes in the remote control code database on the loT hub.

30. The system as in claim 23 wherein the input from the user is provided to the loT hub through the loT service.

31 . The system as in claim 23 wherein the wireless communication channel comprises a Bluetooth Low Energy (BTLE) communication channel.

32. The system as in claim 23 wherein the loT hub is communicatively coupled to the loT service over a cellular network connection coupling the loT hub to the WAN.

33. The system as in claim 23 further comprising:

a plurality of additional loT devices communicatively coupled to the loT hub, each of the loT devices comprising an IR or RF blaster to control different types of

environmental control equipment via IR or RF communication with the environmental control equipment, each loT device further comprising at least one sensor to detect current conditions associated with the operation of the different environmental control equipment, each loT device to transmit an indication of the current conditions to the loT hub over the wireless communication channel.

34. A method comprising:

communicatively coupling an Internet of Things (loT) hub to an loT service over a wide area network (WAN), and communicatively coupling at least one loT device to the loT hub over a wireless communication channel, the loT device comprising an infrared (IR) or radio frequency (RF) blaster to control environmental control equipment via IR or RF communication with the environmental control equipment, the loT device further comprising at least one sensor to measure current environmental conditions capable of being controlled by the environmental control equipment, the loT device to transmit an indication of the current conditions to the loT hub over the wireless communication channel; and

storing remote control codes usable to control the environmental control equipment in a remote control database of the loT hub,

generating remote control commands using the remote control codes, the remote control commands selected by control logic in response to the current environmental conditions measured by the sensor and input from an end user provided via a user device indicating a desired environmental condition,

transmitting commands from the loT hub to the loT device over the wireless communication channel;

responsively transmitting the remote control commands from the loT device to the environmental control equipment to attempt to control the environmental control equipment;

wherein the loT hub is configured to continually or periodically monitor the current environmental conditions measured by the sensor and wherein, if the desired environmental condition is not achieved after a specified period of time, then generating a notification indicating that the environmental control equipment may not be functioning properly.

35. The method as in claim 34 wherein the environmental control equipment comprises an air conditioner and/or heater, the sensor comprises temperature sensor, the current environmental conditions comprises a first temperature, and the desired environmental condition comprises a second temperature different from the first temperature.

36. The method as in claim 35 wherein the notification is sent from the loT hub to a data processing device of the user.

37. The method as in claim 36 wherein if the desired environmental condition is not achieved after the specified period of time, the loT hub is further configured to transmit one or more remote control commands to turn off the environmental control equipment.

38. The method as in claim 34 wherein the loT hub comprises a remote control code learning logic to retrieve remote control codes from a master control code database on the loT service responsive to the user entering information identifying the environmental control equipment .

39. The method as in claim 38 wherein the remote control code learning logic is communicatively coupled to an IR/RF interface integrated on the loT hub, the remote control code learning logic to learn remote control codes directly from original remote controls designed for operation with the environmental control equipment by capturing the remote control codes from the original remote controls via the IR/RF interface.

40. The method as in claim 39 wherein the remote control code learning logic is to store the captured remote control codes in the remote control code database on the loT hub.

41 . The method as in claim 34 wherein the input from the user is provided to the loT hub through the loT service.

42. The method as in claim 12 wherein the wireless communication channel comprises a Bluetooth Low Energy (BTLE) communication channel.

43. The method as in claim 12 wherein the loT hub is communicatively coupled to the loT service over a cellular network connection coupling the loT hub to the WAN.

44. The method as in claim 12 further comprising:

45. A system comprising:

an loT device communicatively coupled to the loT hub over a wireless

communication channel;

the loT device comprising a sensor to measure a local condition affected by a local device in a user's home, the local device being potentially hazardous if

accidentally left on, the loT device communicating one or more measurements of the local condition to the loT hub over the wireless communication channel;

control logic on the loT hub to receive the one or more measurements of the local condition from the sensor and to evaluate the one or more measurements to determine whether the local device has been accidentally left on, the control logic to general a signal to turn off the local device in response to a determination that the local device has been accidentally left on.

46. The system as in claim 45 wherein the local condition comprises a temperature and wherein the control logic determines that the local device has been accidentally left on if the temperature is above a first specified threshold for longer than a specified amount of time.

47. The system as in claim 46 wherein the local device comprises a stove.

48. The system as in claim 47 wherein the control logic is to transmit the signal to the loT device to cause the loT device turn off the stove.

49. The system as in claim 48 wherein the loT device is to turn off the stove by cutting a source of electricity or gas provided to the stove.

50. The system as in claim 48 wherein the loT device is to turn off the stove by wirelessly transmitting a signal to the stove.

51 . The system as in claim 46 wherein the control logic determines that the local device has been accidentally left on if the temperature ever rises above a second specified threshold regardless of amount of time.

52. The system as in claim 50 wherein the wireless signals comprises an infrared (IR) or radio frequency (RF) signals generated from a blaster on the loT device.

53. The system as in claim 46 wherein the local device comprises an electric or gas heater.

54. The system as in claim 45 wherein the loT hub is configured to notify the loT service that the local device has been accidentally left on, the loT service to transmit a notification to a data processing device of the user to notify the user that the local device has been accidentally left on.

55. The system as in claim 54 wherein the data processing device comprises an app or browser-executable code to display the notification and provide the user with the ability to control the local device.

56. A method comprising:

providing an Internet of Things (loT) hub comprising a network interface to couple the loT hub to an loT service over a wide area network (WAN), and

providing an loT device communicatively coupled to the loT hub over a wireless communication channel, the loT device comprising a sensor to measure a local condition affected by a local device in a user's home, the local device being potentially hazardous if accidentally left on, the loT device communicating one or more

measurements of the local condition to the loT hub over the wireless communication channel;

receiving by control logic on the loT hub the one or more measurements of the local condition from the sensor and to evaluate the one or more measurements to determine whether the local device has been accidentally left on, the control logic to general a signal to turn off the local device in response to a determination that the local device has been accidentally left on.

57. The method as in claim 56 wherein the local condition comprises a temperature and wherein the control logic determines that the local device has been accidentally left on if the temperature is above a first specified threshold for longer than a specified amount of time.

58. The method as in claim 57 wherein the local device comprises a stove.

59. The method as in claim 58 wherein the control logic is to transmit the signal to the loT device to cause the loT device turn off the stove.

60. The method as in claim 59 wherein the loT device is to turn off the stove by cutting a source of electricity or gas provided to the stove.

61 . The method as in claim 59 wherein the loT device is to turn off the stove by wirelessly transmitting a signal to the stove.

62. The method as in claim 57 wherein the control logic determines that the local device has been accidentally left on if the temperature ever rises above a second specified threshold regardless of amount of time.

63. The method as in claim 61 wherein the wireless signals comprises an infrared (IR) or radio frequency (RF) signals generated from a blaster on the loT device.

64. The method as in claim 57 wherein the local device comprises an electric or gas heater.

65. The method as in claim 56 wherein the loT hub is configured to notify the loT service that the local device has been accidentally left on, the loT service to transmit a notification to a data processing device of the user to notify the user that the local device has been accidentally left on.

66. The method as in claim 54 wherein the data processing device comprises an app or browser-executable code to display the notification and provide the user with the ability to control the local device.

67. An loT system comprising:

an Internet of Things (loT) hub comprising a network interface to couple the loT hub to an loT service over a first communication channel;

at least one loT device communicatively coupled to the loT hub over a second communication channel;

connection monitoring logic to detect when the first communication channel between the loT service and the loT hub has become inoperative;

notification logic to transmit a notification to a data processing device of a user of the loT system responsive to the connection monitoring logic detecting that the first communication channel has become inoperative.

68. The system as in claim 67 wherein the connection monitoring logic and the notification logic are implemented on the loT service.

69. The system as in claim 68 wherein the connection monitoring logic is configured to periodically transmit a request to the loT hub and determines that the first communication channel has become inoperative after the loT hub has failed to transmit a response.

70. The system as in claim 69 wherein the connection monitoring logic determines that the first communication channel has become inoperative after the loT hub has failed to transmit a response after a specified number of requests.

71 . The system as in claim 67 wherein the first communication channel comprises a cellular network connection and wherein the loT hub is also

communicatively coupled to the loT service over a home Internet connection, wherein the connection monitoring logic is configured to detect a failure over either connection and the notification logic is configured to responsively notify the user of the failed connection.

72. The system as in claim 71 wherein the loT service is configured to continue to communicate with the loT hub over the home Internet connection if the cellular network connection has been determined to be inoperative and is configured to communicate with the loT hub over the cellular connection if the home Internet connection has become inoperative.

73. The system as in claim 72 wherein the notification logic transmits the notification over the Internet to the user's data processing device, the data processing device having an app or browser-based program code executed thereon to receive the notification and generate a visual notification to the user, the visual notification containing an indication of the current status of the first communication channel.

74. A method comprising:

providing an Internet of Things (loT) hub comprising a network interface to couple the loT hub to an loT service over a first communication channel;

providing at least one loT device communicatively coupled to the loT hub over a second communication channel;

detecting when the first communication channel between the loT service and the loT hub has become inoperative;

transmitting a notification to a data processing device of a user responsive to the connection monitoring logic detecting that the first communication channel has become inoperative.

75. The method as in claim 74 wherein the operations of detecting and transmitting are performed on the loT service.

76. The method as in claim 75 wherein detecting comprises periodically transmitting a request from the loT service to the loT hub and determining that the first communication channel has become inoperative after the loT hub has failed to transmit a response.

77. The method as in claim 76 wherein a determination is made that the first communication channel has become inoperative after the loT hub has failed to transmit a response to the loT service after a specified number of requests transmitted from the loT service.

78. The method as in claim 74 wherein the first communication channel comprises a cellular network connection and wherein the loT hub is also communicatively coupled to the loT service over a home Internet connection, wherein a failure is over either connection and the notification logic is to responsively notify the user of the failed connection.

79. The method as in claim 78 wherein the loT service is configured to continue to communicate with the loT hub over the home Internet connection if the cellular network connection has been determined to be inoperative and is configured to communicate with the loT hub over the cellular connection if the home Internet connection has become inoperative.

80. The method as in claim 74 wherein the notification is transmitted over the Internet to the user's data processing device, the data processing device having an app or browser-based program code executed thereon to receive the notification and generate a visual notification to the user, the visual notification containing an indication of the current status of the first communication channel.

81 . A miniature Internet of Things (loT) hub comprising:

a housing having a compact form factor;

a first network interface integrated within the housing to couple the loT hub to an loT service over a first communication channel;

a second network interface integrated within the housing to couple the loT hub to at least one loT device over a second communication channel, the second

communication channel being a local wireless communication channel;

an alternating current (A/C) input interface to couple the miniature loT hub to an A/C power outlet;

a transformer integrated within the housing to transform the A/C power from the A/C input interface into a lower voltage D/C signal; and

at least one light emitting diode (LED) powered by the lower voltage D/C signal, the LED to notify a user of a current status of the loT hub and additionally configurable as a user-programmable night-light.

82. The loT hub as in claim 81 wherein the housing comprises a 1 .5 inch or smaller cube.

83. The loT hub as in claim 81 wherein the housing comprises a depth of between 1 - 2 inches or less and a height of between 1 - 3 inches.

84. The loT hub as in claim 81 further comprising a third network interface coupled to the A/C input interface to establish a third communication channel over the A/C power outlet.

85. The loT hub as in claim 81 further comprising program code executable on a user's data processing device to allow the user to program when the LED is to turn on and off.

86. The loT hub as in claim 85 wherein the program code provides the user the option to turn on the LED at a first specified time and turn off the LED at a second specified time.

87. The loT hub as in claim 86 further comprising:

a low power microcontroller programmable via the program code and configured to cause the LED to turn on and off at the first and second specified times, respectively.

88. The loT hub as in claim 87 further comprising:

a photodetector integrated on the loT hub to detect ambient visible light, the photodetector communicatively coupled to the low power microcontroller, wherein the low power microcontroller is configured to turn on the LED responsive to the

photodetector measuring ambient visible light below or equal to a specified threshold value.

89. The loT hub as in claim 88 wherein the low power microcontroller is further configured to turn off the LED response to the photodetector measuring ambient visible light above a specified threshold value.

90. The loT hub as in claim 81 further comprising:

one or more universal serial bus (USB) ports providing a voltage and current usable for charging other electronic devices.

91 . A method comprising:

providing a miniature Internet of Things (loT) hub comprising a housing having a compact form factor;

communicatively coupling the loT hub to an loT service over a first

communication channel;

communicatively coupling the loT hub to at least one loT device over a second communication channel, the second communication channel being a local wireless communication channel;

electrically coupling the miniature loT hub to an alternating current (A/C) power outlet to receive A/C power via an integrated A/C input interface;

transforming the A/C power from the A/C input interface into a lower voltage D/C signal;

powering at least one light emitting diode (LED) with the lower voltage D/C signal; and

notifying a user of a current status of the loT hub with the LED and additionally executing program code to program the LED to be a programmable night-light.

92. The method as in claim 91 wherein the housing comprises a 1 .5 inch or smaller cube.

93. The method as in claim 91 wherein the housing comprises a depth of between 1 - 2 inches or less and a height of between 1 - 3 inches.

94. The method as in claim 91 further comprising communicatively coupling a third network interface to the A/C input interface to establish a third communication channel over the A/C power outlet.

95. The method as in claim 91 further comprising executing program code on a user's data processing device to allow the user to program when the LED is to turn on and off.

96. The method as in claim 95 wherein the program code provides the user the option to turn on the LED at a first specified time and turn off the LED at a second specified time.

97. The method as in claim 96 further comprising:

programming a low power microcontroller within the loT hub via the program code and to cause the LED to turn on and off at the first and second specified times, respectively.

98. The method as in claim 97 further comprising:

detecting ambient visible light via a photodetector integrated on the loT hub, the photodetector communicatively coupled to the low power microcontroller, wherein the low power microcontroller is configured to turn on the LED responsive to the

99. The method as in claim 98 wherein the low power microcontroller is further configured to turn off the LED response to the photodetector measuring ambient visible light above a specified threshold value.

100. The method as in claim 91 further comprising providing one or more universal serial bus (USB) ports on the loT hub for providing a voltage and current usable for charging other electronic devices.

101 . A system comprising:

an Internet of Things (loT) hub comprising a network interface to couple the loT hub to an loT service through a cellular (cell) carrier, the loT hub further comprising a local communication interface to communicatively couple the loT hub to a plurality of loT devices over local communication channels;

cell carrier selection logic on the loT hub to implement a set of rules to select between two or more cell carriers through which to connect the loT hub to the loT service, the rules being based, at least in part, on a cost associated with connecting to each of the two or more cell carriers and connectivity data associated with cell connections between the loT hub and each of the two or more cell carriers.

102. The system as in claim 101 wherein upon selecting a first cell carrier, the cell carrier selection logic is to cause the network interface to connect the loT hub to the first cell carrier.

103. The system as in claim 101 wherein the connectivity data comprises signal strength between the loT hub and each of the cell carriers.

104. The system as in claim 103 wherein the connectivity data further comprises reliability and/or performance data associated with connections between the loT hub and each of the cell carriers.

105. The system as in claim 103 wherein the rules specify that the cell carrier selection logic is to connect with the lowest cost cell carrier as long as the connectivity data indicates that the signal strength and/or other connectivity variables associated with the lowest cost cell carrier are above specified thresholds.

106. The system as in claim 101 wherein the loT hub is pre-provisioned with the ability to connect to each of the two or more cell carriers.

107. The system as in claim 101 wherein the set of rules are periodically updated on the loT hub from the loT service.

108. The system as in claim 101 wherein the local communication channels comprise Bluetooth Low Energy (LE) communication channels.

109. The system as in claim 108 wherein one or more of the loT devices comprise an IR or RF blaster to control different types of electronics equipment via IR or RF communication with the electronics equipment, each loT device further comprising at least one sensor to detect current conditions associated with the operation of the different electronics equipment, each loT device to transmit an indication of the current conditions to the loT hub over the wireless communication channel.

1 10. A method comprising:

programming an loT hub with rules related to connecting with cell carriers including rules related to cell carrier cost and/or connectivity;

collecting data related to cell carrier cost and/or connectivity;

executing the rules using the collected data to determine a primary cell carrier over which to connect the loT hub; and

connecting the loT hub to the primary cell carrier.

1 1 1 . The method as in claim 1 10 wherein upon selecting a first cell carrier, the cell carrier selection logic is to cause the network interface to connect the loT hub to the first cell carrier.

1 12. The method as in claim 1 10 wherein the connectivity data comprises signal strength between the loT hub and each of the cell carriers.

1 13. The method as in claim 1 12 wherein the connectivity data further comprises reliability and/or performance data associated with connections between the loT hub and each of the cell carriers.

1 14. The method as in claim 1 12 wherein the rules specify that the cell carrier selection logic is to connect with the lowest cost cell carrier as long as the connectivity data indicates that the signal strength and/or other connectivity variables associated with the lowest cost cell carrier are above specified thresholds.

1 15. The method as in claim 1 10 wherein the loT hub is pre-provisioned with the ability to connect to each of the two or more cell carriers.

1 16. The method as in claim 1 10 wherein the set of rules are periodically updated on the loT hub from the loT service.

1 17. The method as in claim 1 10 wherein the local communication channels comprise Bluetooth Low Energy (LE) communication channels.

1 18. The method as in claim 1 17 wherein one or more of the loT devices comprise an IR or RF blaster to control different types of electronics equipment via IR or RF communication with the electronics equipment, each loT device further comprising at least one sensor to detect current conditions associated with the operation of the different electronics equipment, each loT device to transmit an indication of the current conditions to the loT hub over the wireless communication channel.

1 19. A system comprising:

an Internet of Things (loT) hub comprising a network interface to couple the loT hub to an loT service, the loT hub further comprising a local communication interface to communicatively couple the loT hub to a plurality of loT devices over local

communication channels;

the loT hub to receive a plurality of different events of different event types from each of the loT devices, the loT hub further comprising:

an event filter to evaluate each event and responsively determine whether to forward the event to one or more external services over the network interface in accordance with a set of event filtering rules programmed on the loT hub, the event filtering rules provided by the loT service and specifying how different event types are to be processed by the loT hub.

120. The system as in claim 1 19 wherein the event filtering rules are specified, at least in part, by a user of the loT hub.

121 . The system as in claim 1 19 wherein the one or more external services interface with the loT hub via an application programming interface (API) exposed by the loT hub, the one or more external services registering to receive notifications of particular types of events through the API.

122. The system as in claim 121 wherein the loT service is configured to detect the events for which the one or more external services have registered, the loT service to responsively update the event filtering rules and provide the updated event filtering rules to the event filter.

123. The system as in claim 122 wherein at least one of the events to be forwarded by the event filter comprises an event for which a notification is to be sent to the end user's data processing device as well as to the external service.

124. The system as in claim 1 19 wherein the plurality of loT devices are configured to generate events of different types including events having detected values above and below specified thresholds.

125. The system as in claim 124 wherein the event filter forwards events having values above the specified thresholds to the loT service and/or the one or more external services and wherein the event filter does not forward events having values below the specified thresholds.

126. The system as in claim 127 wherein at least some of the events comprise security-related events.

127. The system as in claim 1 19 wherein the loT service comprises an event filter to evaluate each event transmitted from the loT hub and responsively determine whether to forward the event to one or more external services and/or user devices in accordance with a set of event filtering rules programmed on the loT service.

128. The system as in claim 127 wherein each of the external services subscribe to receive events through an API exposed by the loT service.

129. A method comprising:

communicatively coupling an Internet of Things (loT) hub over a network interface to an loT service;

communicatively coupling the loT hub to a plurality of loT devices over local communication channels;

receiving a plurality of different events of different event types from each of the loT devices at the loT hub;

evaluating each event by an event filter on the loT hub and responsively determining whether to forward the event to one or more external services over the network interface in accordance with a set of event filtering rules programmed on the loT hub, the event filtering rules provided by the loT service and specifying how different event types are to be processed by the loT hub.

130. The method as in claim 129 wherein the event filtering rules are specified, at least in part, by a user of the loT hub.

131 . The method as in claim 129 wherein the one or more external services interface with the loT hub via an application programming interface (API) exposed by the loT hub, the one or more external services registering to receive notifications of particular types of events through the API.

132. The method as in claim 131 wherein the loT service is configured to detect the events for which the one or more external services have registered, the loT service to responsively update the event filtering rules and provide the updated event filtering rules to the event filter.

133. The method as in claim 132 wherein at least one of the events to be forwarded by the event filter comprises an event for which a notification is to be sent to the end user's data processing device as well as to the external service.

134. The method as in claim 131 wherein the plurality of loT devices are configured to generate events of different types including events having detected values above and below specified thresholds.

135. The method as in claim 134 wherein the event filter forwards events having values above the specified thresholds to the loT service and/or the one or more external services and wherein the event filter does not forward events having values below the specified thresholds.

136. The method as in claim 135 wherein at least some of the events comprise security-related events.

137. A system comprising:

communication channels;

the loT hub to receive a plurality of different events of different event types from each of the loT devices and forward the events to an loT service;

the loT service comprising an event filter to evaluate each event and

responsively determine whether to forward the event to one or more external services and/or user devices in accordance with a set of event filtering rules programmed on the loT service, the event filtering rules specifying how different event types are to be processed by the loT service.

138. The system as in claim 137 wherein the event filtering rules are specified, at least in part, by a user of the loT hub.

139. The system as in claim 137 wherein the one or more external services interface with the loT service via an application programming interface (API) exposed by the loT service, the one or more external services registering to receive notifications of particular types of events through the API.

140. The system as in claim 139 wherein the loT service is configured to detect the events for which the one or more external services have registered, the loT service to responsively update the event filtering rules and provide the updated event filtering rules to the event filter.

141 . The system as in claim 140 wherein at least one of the events to be forwarded by the event filter comprises an event for which a notification is to be sent to the end user's data processing device as well as to the external service.

142. The system as in claim 1 19 wherein the plurality of loT devices are configured to generate events of different types including events having detected values above and below specified thresholds.

143. The system as in claim 142 wherein the event filter forwards events having values above the specified thresholds to the external services and wherein the event filter does not forward events having values below the specified thresholds.

144. An loT system comprising:

communication channels;

the loT hub comprising logic to collect data from each of the loT devices and to control the loT devices responsive to user input from a plurality of different users; user behavior data collection logic to collect user behavior data within the loT system, the user behavior data collection logic to monitor and record the data accessed by each user from each of the loT devices and the loT devices controlled by each user; user profile generation logic to analyze the user behavior data to determine a profile for each user; and

targeted content generation logic to generate targeted content to be transmitted to each user in accordance with each determined profile.

145. The system as in claim 144 wherein the user behavior data collection logic is executed on the loT hub and the user behavior data is transmitted to the loT service.

146. The system as in claim 145 wherein the user profile generation logic is executed on the loT service or on an external service to generate the profile for each user.

147. The system as in claim 146 wherein the targeted content generation logic is executed on the loT service or on an external service to generate the targeted content to be transmitted to each user.

148. The system as in claim 144 wherein the profile is generated for each user in accordance with data accessed by each user within the loT system and loT devices controlled by each user within the loT system.

149. The system as in claim 144 further comprising an app or browser- executable code executed on a data processing device of a user, the app or browser- executable code to allow the user to control the loT devices and access data collected by the loT devices within the loT system.

150. The system as in claim 149 wherein the app or browser-executable code is further configured to receive the targeted content generated based on the user's profile and to display the targeted content for the user.

151 . The system as in claim 150 wherein the targeted content includes one or more network links to allow the user to access additional information related to the targeted content.

152. The system as in claim 144 wherein the loT service transmits the user behavior data to one or more external services which execute the user profile

generation logic to generate the profile for each user and with targeted content generation logic to generate targeted content based on each user profile.

153. The system as in claim 152 wherein one or more of the external services transmit the targeted content to a data processing device operated by a user.

154. A method executed within an loT system comprising:

communicatively coupling an Internet of Things (loT) hub comprising a network interface to an loT service,

communicatively coupling the loT hub via a local communication interface to a plurality of loT devices over local communication channels;

collecting data from each of the loT devices and controlling each of the loT devices responsive to user input from a plurality of different users;

collect user behavior data within the loT system by monitoring and recording the data accessed by each user from each of the loT devices and the loT devices controlled by each user;

analyzing the user behavior data to determine a profile for each user; and generating targeted content to be transmitted to each user in accordance with each determined profile.

155. The method as in claim 154 wherein the operation of collecting user behavior data is performed by the loT hub which transmits the user behavior data to the loT service.

156. The method as in claim 155 wherein the operation of analyzing the user behavior data to generate a profile for each user performed by the loT service or on an external service.

157. The method as in claim 156 wherein operation of generating targeted content is performed by the loT service or on an external service.

158. The method as in claim 154 wherein the profile is generated for each user in accordance with data accessed by each user within the loT system and loT devices controlled by each user within the loT system.

159. The method as in claim 154 further comprising providing an app or browser-executable code executed on a data processing device of a user, the app or browser-executable code to allow the user to control the loT devices and access data collected by the loT devices within the loT system.

160. The method as in claim 159 wherein the app or browser-executable code is further configured to receive the targeted content generated based on the user's profile and to display the targeted content for the user.

161 . The method as in claim 160 wherein the targeted content includes one or more network links to allow the user to access additional information related to the targeted content.

162. The method as in claim 154 wherein the loT service transmits the user behavior data to one or more external services which execute the user profile generation logic to generate the profile for each user and with targeted content generation logic to generate targeted content based on each user profile.

163. The method as in claim 162 wherein one or more of the external services transmit the targeted content to a data processing device operated by a user.